From: "Petteri Räty" <betelgeuse@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Reminder about the need to revision bump virtual providers when migrating to new style virtuals
Date: Sun, 20 Aug 2006 13:19:18 +0300 [thread overview]
Message-ID: <44E83726.7050201@gentoo.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 778 bytes --]
When migrating to new style virtuals you must revision bump everything
providing the new style virtual to get rid of the PROVIDE files in
/var/db/pkg.
./app-admin/gamin-0.1.7/PROVIDE:virtual/fam
If you do not do this, Portage considers the virtual installed without
actually looking at the new style virtual. In cases where versioning is
not needed this probably does not cause problems but for java this
caused problems like the following:
# emerge -pu world
These are the packages that would be merged, in order:
Calculating world dependencies |
emerge: there are no ebuilds to satisfy ">=dev-java/blackdown-jdk-1.5".
(dependency required by "dev-util/eclipse-sdk-3.2" [ebuild])
http://bugs.gentoo.org/show_bug.cgi?id=140834
Regards,
Petteri
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
reply other threads:[~2006-08-20 10:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=44E83726.7050201@gentoo.org \
--to=betelgeuse@gentoo.org \
--cc=gentoo-dev@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