Re: [gentoo-user] emerge -pv world output: strange differences after Portage upgrade

2007-02-16 Thread brullo nulla
On second thought this does make sense. Portage 2.1.2 allows an upgrade within the same slot despite the block. And the reason it doesn't get pulled in by `emerge -pv world` is because dbus isn't in world and the later version isn't required by anything in world. You need to use --update to

Re: [gentoo-user] emerge -pv world output: strange differences after Portage upgrade

2007-02-16 Thread Bo Ørsted Andresen
On Friday 16 February 2007 09:19:11 brullo nulla wrote: Ok. Now the question is: is the new dbus really installable indeed? I think yes from your explanation, but I want to be triple-sure. Of course. You showed that when you provided `emerge -pv dbus` (it didn't say masked by anything)...

Re: [gentoo-user] emerge -pv world output: strange differences after Portage upgrade

2007-02-15 Thread Etaoin Shrdlu
On Thursday 15 February 2007 23:21, b.n. wrote: Hi, I recently upgraded Portage (and a couple of other unrelated packages). After the upgrade, I noticed that emerge -pv world before and after give two very different results. In particular: 1) I had a lot of sound-related packages that are

Re: [gentoo-user] emerge -pv world output: strange differences after Portage upgrade

2007-02-15 Thread Bo Ørsted Andresen
On Thursday 15 February 2007 23:21:02 b.n. wrote: Hi, I recently upgraded Portage (and a couple of other unrelated packages). After the upgrade, I noticed that emerge -pv world before and after give two very different results. In particular: 1) I had a lot of sound-related packages that are

Re: [gentoo-user] emerge -pv world output: strange differences after Portage upgrade

2007-02-15 Thread b.n.
Etaoin Shrdlu ha scritto: My guess is that at least one of your issues has something to do with the new portage behavior regarding buid time dependencies. This is the relevant message displayed when upgrading: In portage-2.1.2, installation actions do not necessarily pull in build time

Re: [gentoo-user] emerge -pv world output: strange differences after Portage upgrade

2007-02-15 Thread Bo Ørsted Andresen
On Friday 16 February 2007 01:09:30 b.n. wrote: In portage-2.1.2, installation actions do not necessarily pull in build time dependencies that are not strictly required.  This behavior is adjustable via the new --with-bdeps option that is documented in the emerge(1) man page. For more

Re: [gentoo-user] emerge -pv world output: strange differences after Portage upgrade

2007-02-15 Thread b.n.
Bo Ørsted Andresen ha scritto: 1) I had a lot of sound-related packages that are no more in portage still installed. Okay, I should get rid of them. BEFORE: emerge -pv warned me of all these packages. AFTER: emerge -pv warns me of only one package (djplay) Due to bug #48195 [1] being fixed.

Re: [gentoo-user] emerge -pv world output: strange differences after Portage upgrade

2007-02-15 Thread Bo Ørsted Andresen
On Friday 16 February 2007 01:33:00 b.n. wrote: 2) I still have to upgrade dbus to 1.0.2 BEFORE: the dbus upgrade was in the -pv output AFTER: It seems the dbus upgrade is no more in emerge -pv world. This seems weird. What's the output of `emerge -pv dbus` with portage 2.1.2? These

Re: [gentoo-user] emerge -pv world output: strange differences after Portage upgrade

2007-02-15 Thread Bo Ørsted Andresen
On Friday 16 February 2007 00:44:16 Bo Ørsted Andresen wrote: On Friday 16 February 2007 01:33:00 b.n. wrote: 2) I still have to upgrade dbus to 1.0.2 BEFORE: the dbus upgrade was in the -pv output AFTER: It seems the dbus upgrade is no more in emerge -pv world. This seems weird.

Re: [gentoo-user] emerge -pv world output: strange differences after Portage upgrade

2007-02-15 Thread Bo Ørsted Andresen
On Friday 16 February 2007 02:00:26 Bo Ørsted Andresen wrote: On Friday 16 February 2007 00:44:16 Bo Ørsted Andresen wrote: On Friday 16 February 2007 01:33:00 b.n. wrote: 2) I still have to upgrade dbus to 1.0.2 BEFORE: the dbus upgrade was in the -pv output AFTER: It seems the