From: Chris Bainbridge <C.J.Bainbridge@ed.ac.uk>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] emerge -U world with mixed stable/unstable ebuilds
Date: Wed, 26 Mar 2003 11:35:49 +0000 [thread overview]
Message-ID: <200303261135.49930.C.J.Bainbridge@ed.ac.uk> (raw)
I have some unstable ~x86 ebuilds installed. When I emerge -U world I get
errors like:
# emerge -U world --deep -p
>>> --upgradeonly implies --update... adding --update to options.
These are the packages that I would merge, in order:
Calculating world dependencies \
!!! all ebuilds that could satisfy ">=app-sci/lard-20030204" have been masked.
!!! (dependency required by "app-sci/tbass-20030318" [ebuild])
!!! Problem with ebuild app-sci/tbass-20030318
!!! Possibly a DEPEND/*DEPEND problem.
!!! Depgraph creation failed.
I could modify my local portage tree after syncing to mark every ebuild I want
stable, but is there an easier way? Preferably some way to update all stable
ebuilds to the latest stable version and all unstable ones to the latest
unstable...?
--
gentoo-dev@gentoo.org mailing list
next reply other threads:[~2003-03-26 11:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-26 11:35 Chris Bainbridge [this message]
2003-03-26 14:04 ` [gentoo-dev] emerge -U world with mixed stable/unstable ebuilds Marshall T. Vandegrift
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=200303261135.49930.C.J.Bainbridge@ed.ac.uk \
--to=c.j.bainbridge@ed.ac.uk \
--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