From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Cc: billyd <billydw@comcast.net>
Subject: Re: [gentoo-user] No longer getting elog messages
Date: Sat, 24 Apr 2010 00:37:06 +0200 [thread overview]
Message-ID: <201004240037.06418.alan.mckinnon@gmail.com> (raw)
In-Reply-To: <201004231212.45850.billydw@comcast.net>
On Friday 23 April 2010 19:12:45 billyd wrote:
> Hi, all:
>
> I used to get info, error and warn messages in /var/log/portage/elog after
> emerging packages or doing emerge -uNDvp world. Beginning about 2 weeks
> ago, I noticed I am no longer getting those elog entries. Additionally, I
> noticed that I am getting duplicate entries for each package that is
> emerged in /var/log/portage (of course, these are the compile logs).
Have you checked the obvious things, like sufficient disk space in elog/ ?
What version of portage and python are you running?
>
> I have Gentoo installed on 2 computers, both using arch ~amd64. All 3
> installations have KDE 4 (latest in portage for ~amd64 arch).
>
> PC #1 uses this profile: default/linux/amd64/10.0/desktop/kde
> PC #2 has two installs:
>
> Install #1 uses profile: default/linux/amd64/10.0/desktop
> Install #2 uses profile: default/linux/amd64/10.0/no-multilib
>
> This problem is happening on all 3 of my Gentoo installations and all
> started at the same time. The only changes have been through doing
> updates. I sync nearly every day followed my # emerge -uNDvp world. Other
> than issues with xorg-server 1.8.0 and the nvidia-drivers, all my updates
> have been successful.
>
> Note: I have masked xorg-server 1.8.0 in /etc/portage/package.mask until
> the nvidia-drivers catch up.
>
> I have searched the forums, checked bugzilla and googled on this topic and
> have yet to find a solution. My Gentoo installs are working just fine
> except for this issue.
>
> I have attached /etc/make.conf from only one of the installs as they are
> all the same. Here are the 3 lines I have in my make.conf files as they
> relate to logging the elog messages:
>
> PORT_LOGDIR="/var/log/portage"
> PORTAGE_ELOG_CLASSES="log warn error"
> PORTAGE_ELOG_SYSTEM="save"
>
> Thank you for the help.
>
> billyd
--
alan dot mckinnon at gmail dot com
next prev parent reply other threads:[~2010-04-23 22:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-23 17:12 [gentoo-user] No longer getting elog messages billyd
2010-04-23 22:37 ` Alan McKinnon [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-04-24 2:40 billyd
2010-04-24 8:51 ` Alan McKinnon
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=201004240037.06418.alan.mckinnon@gmail.com \
--to=alan.mckinnon@gmail.com \
--cc=billydw@comcast.net \
--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