From: Ryan Breen <ryan@porivo.com>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] potential update world bug
Date: Wed, 19 Jun 2002 21:13:41 -0400 [thread overview]
Message-ID: <200206192113.41772.ryan@porivo.com> (raw)
Greetings,
I've been using Gentoo for the last several months, and I've noticed for the
last month that 'emerge update world' after an 'emerge --clean rsync' never
yields any updates. I currently have 75 packages in my /var/cache/edb/world
file, and I have verified several occasions where rsync has noted an update
to one of the packages that is not handled by an 'update world'.
I have also verified that the packages were not masked and
/etc/make.conf/profiles looked like it was setup properly for those packages.
Manual calls to update those packages work fine. I noticed this with updates
to xmms, avifile, pan, and kde (3.0-3.01).
I've only begun to dig into this problem, but I was wondering if anyone on
this list could give me pointers to likely causes, enlightening log files,
etc that could trim my debug time.
Thanks in advance,
Ryan
next reply other threads:[~2002-06-20 1:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-20 1:13 Ryan Breen [this message]
2002-06-20 8:36 ` [gentoo-dev] potential update world bug George Shapovalov
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=200206192113.41772.ryan@porivo.com \
--to=ryan@porivo.com \
--cc=gentoo-dev@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