From: Jim Bowlin <bowlin@mindspring.com>
To: Denys Duchier <duchier@ps.uni-sb.de>, gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] another snag: emerge -Up --deep gtkhtml
Date: Wed, 30 Apr 2003 11:13:32 -0700 [thread overview]
Message-ID: <200304301113.39872.bowlin@mindspring.com> (raw)
In-Reply-To: <86znm8m4pk.fsf@speedy.ps.uni-sb.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wednesday 30 April 2003 07:37 am, Denys Duchier wrote:
> I hope my continued reports on "emerge -U" are neither out of place
> nor too tiresome. Today, I "emerge sync"'d, tried "emerge -Up --deep
> world" and got the following error: [snip]
I've been watching this thread http://forums.gentoo.org/viewtopic.php?p=303720
which echos what I've seen myself: -U seems to be flakey. I'd like to try
to fix this but I don't want to reinvent the wheel. Is someone already
working on this problem? Is version 2.0 about to come out?
If the answers are 'no' and 'no', does anyone know the current state?
It seems that a fix involves is_newer_ver_installed() in /usr/bin/emerge
and xmatch() in portage.py. They look a little cryptic.
It seems to me, perhaps nievely, that all that is needed is a list of
installed packages and a method for ordering version numbers.
Peace, Jim Bowlin
PS: If this is not the correct place to post this message please LMK.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE+sBJTdVDVBNqCHikRAkrcAKCByEeh5UXk5ifGO7c/jXkTKm4JlwCfWUtz
LzJlY+i+ytM7VpHBH+vr70c=
=OGUh
-----END PGP SIGNATURE-----
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-04-30 18:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-30 14:37 [gentoo-dev] another snag: emerge -Up --deep gtkhtml Denys Duchier
2003-04-30 18:13 ` Jim Bowlin [this message]
2003-05-01 0:20 ` Daniel Armyr
2003-05-01 7:00 ` Nick Jones
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=200304301113.39872.bowlin@mindspring.com \
--to=bowlin@mindspring.com \
--cc=duchier@ps.uni-sb.de \
--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