Re: [gentoo-user] emerge -pv world output: strange differences after Portage upgrade
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 get direct dependencies upgraded or --deep to get all dependencies upgraded to the latest version. Just to close this entirely dbus-0.62-r2 has had most of it's keywords dropped. This means if you type: # emerge -pv =sys-apps/dbus-0.62-r2 you'll likely get a masked by: missing keyword message. So again bug #48195 explains why dbus-0.62-r2 is able to satisfy dependencies on dbus because it's installed with Portage 2.1.2 but isn't able to satisfy it with Portage 2.1.1 because it's not installable. :) 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. (In fact, a self-blocking packages looked very odd to me, but...) (and why has been 0.62-r2 been hard masked so fast?) m. -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] emerge -pv world output: strange differences after Portage upgrade
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)... (In fact, a self-blocking packages looked very odd to me, but...) (and why has been 0.62-r2 been hard masked so fast?) What is often referred to as hard masked isn't the same as masked by missing keyword. Also it wasn't *that* fast. But short answer: because the maintainer doesn't want to maintain old software... -- Bo Andresen pgpW5A4e9hjg4.pgp Description: PGP signature
Re: [gentoo-user] emerge -pv world output: strange differences after Portage upgrade
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 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) 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. 3) I am currently running GCC 4.1.x, but I am keeping gcc 3.3 and 3.4 installed (I could probably get rid of gcc 3.3.x, but whatever...) BEFORE: no gcc upgrade was required AFTER: Portage wants me to upgrade gcc 3.3.6 and 3.4.6 to their minor upgrades. 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 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 information regarding this change, please refer to bug #148870. -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] emerge -pv world output: strange differences after Portage upgrade
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 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. Installed packages can now satisfy a dependency even if it isn't in the tree or in an overlay that's present. 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? 3) I am currently running GCC 4.1.x, but I am keeping gcc 3.3 and 3.4 installed (I could probably get rid of gcc 3.3.x, but whatever...) BEFORE: no gcc upgrade was required AFTER: Portage wants me to upgrade gcc 3.3.6 and 3.4.6 to their minor upgrades. Due to bug #4698 [2] and some of the referenced bugs on that being fixed. Portage 2.1.1 only upgraded the latest installed slot of any slotted package. [1] https://bugs.gentoo.org/48195 [2] https://bugs.gentoo.org/4698 -- Bo Andresen pgpPxglx1szzg.pgp Description: PGP signature
Re: [gentoo-user] emerge -pv world output: strange differences after Portage upgrade
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 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 information regarding this change, please refer to bug #148870. This could explain the issue (2)about the disappearing of the dbus upgrade. Still it doesn't explain the (1) and the (3), imho. m. -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] emerge -pv world output: strange differences after Portage upgrade
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 information regarding this change, please refer to bug #148870. This could explain the issue (2)about the disappearing of the dbus upgrade. It could not as dbus is both a DEPEND and an RDEPEND of at the very least wine (the dbus USE flag is enabled) which is being upgraded... -- Bo Andresen pgpqN7VfOAsHG.pgp Description: PGP signature
Re: [gentoo-user] emerge -pv world output: strange differences after Portage upgrade
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. Installed packages can now satisfy a dependency even if it isn't in the tree or in an overlay that's present. Oh, ok. This may make sense. (I preferred the old behaviour, though. We grow accustomed to bugs as features) 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 are the packages that would be merged, in order: Calculating dependencies... done! [ebuild U ] sys-apps/dbus-1.0.2 [0.62-r2] USE=X -debug -doc (-selinux) (-gtk%*) (-mono%) (-python%*) (-qt3%*) (-qt4%*) 1,368 kB Total: 1 package (1 upgrade), Size of downloads: 1,368 kB Note that before dbus 0.62 was somehow blocking, now it is no more blocking. Etaoin Shrdlu referred to another bug that may explain this, but it's quite unclear to me. 3) I am currently running GCC 4.1.x, but I am keeping gcc 3.3 and 3.4 installed (I could probably get rid of gcc 3.3.x, but whatever...) BEFORE: no gcc upgrade was required AFTER: Portage wants me to upgrade gcc 3.3.6 and 3.4.6 to their minor upgrades. Due to bug #4698 [2] and some of the referenced bugs on that being fixed. Portage 2.1.1 only upgraded the latest installed slot of any slotted package. I thought it was a feature too. Although the new behaviour makes a lot of sense. m. -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] emerge -pv world output: strange differences after Portage upgrade
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 are the packages that would be merged, in order: Calculating dependencies... done! [ebuild U ] sys-apps/dbus-1.0.2 [0.62-r2] USE=X -debug -doc (-selinux) (-gtk%*) (-mono%) (-python%*) (-qt3%*) (-qt4%*) 1,368 kB Total: 1 package (1 upgrade), Size of downloads: 1,368 kB Note that before dbus 0.62 was somehow blocking, now it is no more blocking. Etaoin Shrdlu referred to another bug that may explain this, but it's quite unclear to me. I'll suggest you file a bug with emerge --info in a comment and emerge --debug -vp dbus attached. This clearly seems like like something is wrong and if nothing else at least we'll find an explanation. -- Bo Andresen pgpqxsfmS6R16.pgp Description: PGP signature
Re: [gentoo-user] emerge -pv world output: strange differences after Portage upgrade
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. What's the output of `emerge -pv dbus` with portage 2.1.2? These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild U ] sys-apps/dbus-1.0.2 [0.62-r2] USE=X -debug -doc (-selinux) (-gtk%*) (-mono%) (-python%*) (-qt3%*) (-qt4%*) 1,368 kB Total: 1 package (1 upgrade), Size of downloads: 1,368 kB Note that before dbus 0.62 was somehow blocking, now it is no more blocking. Etaoin Shrdlu referred to another bug that may explain this, but it's quite unclear to me. I'll suggest you file a bug with emerge --info in a comment and emerge --debug -vp dbus attached. This clearly seems like like something is wrong and if nothing else at least we'll find an explanation. 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 get direct dependencies upgraded or --deep to get all dependencies upgraded to the latest version. -- Bo Andresen pgpUugGLZWkBv.pgp Description: PGP signature
Re: [gentoo-user] emerge -pv world output: strange differences after Portage upgrade
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 dbus upgrade is no more in emerge -pv world. [SNIP] 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 get direct dependencies upgraded or --deep to get all dependencies upgraded to the latest version. Just to close this entirely dbus-0.62-r2 has had most of it's keywords dropped. This means if you type: # emerge -pv =sys-apps/dbus-0.62-r2 you'll likely get a masked by: missing keyword message. So again bug #48195 explains why dbus-0.62-r2 is able to satisfy dependencies on dbus because it's installed with Portage 2.1.2 but isn't able to satisfy it with Portage 2.1.1 because it's not installable. :) -- Bo Andresen pgp94W9pHhevk.pgp Description: PGP signature
