From: Mark Knecht <markknecht@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Mythtv problems
Date: Wed, 26 Oct 2011 09:36:59 -0700 [thread overview]
Message-ID: <CAK2H+edj0BcEEFM_ZwCAMEXPY2hPCvkj1WJUOBuf4ivE5=8qMw@mail.gmail.com> (raw)
In-Reply-To: <4EA83571.1060100@gmail.com>
On Wed, Oct 26, 2011 at 9:29 AM, Michael Sullivan <msulli1355@gmail.com> wrote:
> On 10/26/11 11:07, Neil Bothwick wrote:
>> On Wed, 26 Oct 2011 09:23:30 -0500, Michael Sullivan wrote:
>>
>>> At first I thought that sometime that installed since Oct 12 was causing
>>> the segfault, so I tried unmerging the 350+ packages that had installed
>>> since then and listing them in package.mask, but that blew up in my face
>>> because I don't know a command that forces portage to ignore masked
>>> packages and install next-highest stable versions.
>>
>> Mask higher versions in package mask
>>
>>> cat/pkg-version.you.want
>>
>>
>
> I did, but as I said there where 350+ of them. And every time I tried
> to emerge anything else, I couldn't because some package I needed was
> listed in package mask. I got the package list that I added to
> package.mask from /var/log/portage-logs for files dated from October 12
> till 24. It was an epic fail. I couldn't even emerge -e world because
> of those stupid masked package versions...
OK, I haven't used Myth now in over a year so take this with a grain
of salt. From the log file it appears that your client isn't
connecting to the server which likely explains why you don't see the
programs. I wonder if you've tested connecting to mythconverg manually
via a terminal? Maybe something like /etc/my.cnf or one of the Myth
config files got messed up in the update.
Good luck,
Mark
next prev parent reply other threads:[~2011-10-26 16:40 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-26 14:23 [gentoo-user] Mythtv problems Michael Sullivan
2011-10-26 14:45 ` [gentoo-user] " Michael Sullivan
2011-10-26 18:20 ` Raffaele BELARDI
2011-10-26 16:07 ` [gentoo-user] " Neil Bothwick
2011-10-26 16:29 ` Michael Sullivan
2011-10-26 16:36 ` Mark Knecht [this message]
2011-10-26 18:31 ` Michael Sullivan
2011-10-26 19:03 ` Michael Sullivan
2011-10-26 19:05 ` Michael Sullivan
2011-10-26 19:45 ` Michael Sullivan
2011-10-26 19:51 ` Michael Sullivan
2011-10-26 20:01 ` Michael Sullivan
2011-10-26 21:19 ` Michael Sullivan
2011-10-27 10:17 ` Matt Harrison
2011-10-27 0:03 ` kashani
2011-10-27 0:15 ` Michael Sullivan
2011-10-26 18:46 ` Neil Bothwick
2011-10-26 20:08 ` Michael Sullivan
2011-10-26 21:25 ` Michael Sullivan
2011-10-26 21:46 ` Michael Schreckenbauer
2011-10-26 21:51 ` Michael Sullivan
2011-10-26 22:06 ` Michael Schreckenbauer
2011-10-26 22:14 ` Michael Sullivan
2011-10-26 22:32 ` Michael Schreckenbauer
2011-10-26 22:42 ` Michael Sullivan
2011-10-26 22:53 ` Michael Schreckenbauer
2011-10-26 22:59 ` Michael Sullivan
2011-10-26 23:08 ` Michael Schreckenbauer
2011-10-26 22:09 ` Michael Schreckenbauer
2011-10-26 22:30 ` Michael Sullivan
2011-10-26 22:36 ` Michael Schreckenbauer
2011-10-26 22:33 ` Michael Sullivan
2011-10-26 22:58 ` Michael Schreckenbauer
2011-10-26 23:10 ` Michael Sullivan
2011-10-26 23:16 ` Michael Schreckenbauer
2011-10-27 1:13 ` [gentoo-user] Mythtv problems [SOLVED] Michael Sullivan
2011-10-27 10:08 ` Michael Schreckenbauer
2011-10-26 22:44 ` [gentoo-user] Mythtv problems Neil Bothwick
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAK2H+edj0BcEEFM_ZwCAMEXPY2hPCvkj1WJUOBuf4ivE5=8qMw@mail.gmail.com' \
--to=markknecht@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox