begin quote On Sat, 12 Jul 2003 21:25:59 -0400 gabriel <[EMAIL PROTECTED]> wrote:
i had a purpose in mind: i wanted the latest version of k3b 'cause 0.8 didn't work properly. > > so i tried > > # USE="~x86" emerge k3b Here is where you go wrong, the setting you are after is ACCEPT_KEYWORDS="~x86" emerge k3b not USE, useflags define functionality, not stability in this case. <SNIP> > and now i have a working k3b with dvd ripping/encoding support. yay! > but then today i tried the usual: > > # emerge --update --deep world <SNIP> > doing adding the "--upgradeonly" option didn't work either, so now i'm > stuck with a crippled system until i either (a) downgrade my software, > or (b) figure out wht someone is supposed to do in this position. > anyone care to fill me in? Yes, you did install packages that your system will not accept as stable, and thus will find a lot of trouble supporting. The problem is probably (I'm not that much an expert on how the more intrikate workings of portage to really be confident ) that you only satisfied partial dependencies in the builds, and since you didn't install the dependencies, or set all of your tree to accept testing packages, it is struck with an installed package that wants something it can't get. try: ACCEPT_KEYWORDS="~x86" emerge -p transcode (no -u there.. only emerge that package and its direct dependencies) and I think you should be ok off. Regards, //Spider -- begin .signature This is a .signature virus! Please copy me into your .signature! See Microsoft KB Article Q265230 for more information. end
pgp00000.pgp
Description: PGP signature
