[gentoo-user] emerge --update - why doesn't it update my kde packages
Hi, the following situation puzzles me a lot. My 'standard' way of updating is emerge --keep-going -j4 -1 --ask --update --newuse --deep --tree @system @world but it didn't update anything. Still, eix confirmed there were quite a lot of kde packages which have newer versions, and indeed, emerge -auv1 -j4 --keep-going $(qlist -IC kde-base/) upgraded 24 packages. Where does this discrepancy come from? Many thanks for a hint, Helmut. -- Helmut Jarausch Lehrstuhl fuer Numerische Mathematik RWTH - Aachen University D 52056 Aachen, Germany
Re: [gentoo-user] emerge --update - why doesn't it update my kde packages
On Tue, May 04, 2010 at 10:57:10AM +0200, Helmut Jarausch wrote: Hi, the following situation puzzles me a lot. My 'standard' way of updating is emerge --keep-going -j4 -1 --ask --update --newuse --deep --tree @system @world but it didn't update anything. Still, eix confirmed there were quite a lot of kde packages which have newer versions, and indeed, emerge -auv1 -j4 --keep-going $(qlist -IC kde-base/) upgraded 24 packages. Where does this discrepancy come from? Do you have --with-bdep set in /etc/make.conf? Many thanks for a hint, Helmut. -- Helmut Jarausch Lehrstuhl fuer Numerische Mathematik RWTH - Aachen University D 52056 Aachen, Germany
Re: [gentoo-user] emerge --update - why doesn't it update my kde packages
On 4 May, Bert Swart wrote: On Tue, May 04, 2010 at 10:57:10AM +0200, Helmut Jarausch wrote: Hi, the following situation puzzles me a lot. My 'standard' way of updating is emerge --keep-going -j4 -1 --ask --update --newuse --deep --tree @system @world but it didn't update anything. Still, eix confirmed there were quite a lot of kde packages which have newer versions, and indeed, emerge -auv1 -j4 --keep-going $(qlist -IC kde-base/) upgraded 24 packages. Where does this discrepancy come from? Do you have --with-bdep set in /etc/make.conf? No. Are you saying that emerge --keep-going -j4 -1 --ask --update --newuse --deep --tree --with-bdeps y @system @world would have updated my kde packages, as well? Thanks, Helmut. -- Helmut Jarausch Lehrstuhl fuer Numerische Mathematik RWTH - Aachen University D 52056 Aachen, Germany
Re: [gentoo-user] emerge --update - why doesn't it update my kde packages
On Tue, May 04, 2010 at 12:09:25PM +0200, Helmut Jarausch wrote: On 4 May, Bert Swart wrote: On Tue, May 04, 2010 at 10:57:10AM +0200, Helmut Jarausch wrote: Hi, the following situation puzzles me a lot. My 'standard' way of updating is emerge --keep-going -j4 -1 --ask --update --newuse --deep --tree @system @world but it didn't update anything. Still, eix confirmed there were quite a lot of kde packages which have newer versions, and indeed, emerge -auv1 -j4 --keep-going $(qlist -IC kde-base/) upgraded 24 packages. Where does this discrepancy come from? Do you have --with-bdep set in /etc/make.conf? No. Are you saying that emerge --keep-going -j4 -1 --ask --update --newuse --deep --tree --with-bdeps y @system @world would have updated my kde packages, as well? Probably. Sometimes, not all packages are included as dependency if they are not strictly required. If you do want them to be upgraded, add --with-bdeps to EMERGE_DEFAULT_OPTS in /etc/make.conf. Or, like you did, upgrade them manually... See also http://www.gentoo.org/proj/en/portage/doc/faq.xml Thanks, Helmut. -- Helmut Jarausch Lehrstuhl fuer Numerische Mathematik RWTH - Aachen University D 52056 Aachen, Germany
Re: [gentoo-user] emerge --update - why doesn't it update my kde packages
Am 04.05.2010 12:17, schrieb Bert Swart: On Tue, May 04, 2010 at 12:09:25PM +0200, Helmut Jarausch wrote: On 4 May, Bert Swart wrote: On Tue, May 04, 2010 at 10:57:10AM +0200, Helmut Jarausch wrote: Hi, the following situation puzzles me a lot. My 'standard' way of updating is emerge --keep-going -j4 -1 --ask --update --newuse --deep --tree @system @world but it didn't update anything. Still, eix confirmed there were quite a lot of kde packages which have newer versions, and indeed, emerge -auv1 -j4 --keep-going $(qlist -IC kde-base/) upgraded 24 packages. Where does this discrepancy come from? Do you have --with-bdep set in /etc/make.conf? No. Are you saying that emerge --keep-going -j4 -1 --ask --update --newuse --deep --tree --with-bdeps y @system @world would have updated my kde packages, as well? Probably. Sometimes, not all packages are included as dependency if they are not strictly required. If you do want them to be upgraded, add --with-bdeps to EMERGE_DEFAULT_OPTS in /etc/make.conf. Or, like you did, upgrade them manually... See also http://www.gentoo.org/proj/en/portage/doc/faq.xml Those are packages only required during buildtime. You could unmerge them after upgrading without loosing a funktion. Adding --with-bdeps to EMERGE_DEFAULT_OPTS might only wast some time and energy. You can also run depclean --with-bdeps (yes/no or something like that) to savely remove them. My point is: If glsa doesn't list one of those packages I don't touch them. Regards kh Thanks, Helmut. -- Helmut Jarausch Lehrstuhl fuer Numerische Mathematik RWTH - Aachen University D 52056 Aachen, Germany
Re: [gentoo-user] emerge --update - why doesn't it update my kde packages
Helmut Jarausch writes: My 'standard' way of updating is emerge --keep-going -j4 -1 --ask --update --newuse --deep --tree @system @world but it didn't update anything. Still, eix confirmed there were quite a lot of kde packages which have newer versions, and indeed, emerge -auv1 -j4 --keep-going $(qlist -IC kde-base/) upgraded 24 packages. Where does this discrepancy come from? I guess those packages are not in your /var/lib/portage/world file (or in a set in /var/lib/portage/world_sets), and nothing in there depends on them. Try emerge -p --depclean and see if they are listed. If so, use emerge -n to add them to world. Wonko
Re: [gentoo-user] emerge --update - why doesn't it update my kde packages
On Tue, 04 May 2010 11:00:01 +0200, Helmut Jarausch wrote about
[gentoo-user] emerge --update - why doesn't it update my kde packages:
[snip]
Still, eix confirmed there were quite a lot of kde packages which have
newer versions, and indeed,
emerge -auv1 -j4 --keep-going $(qlist -IC kde-base/)
upgraded 24 packages.
Where does this discrepancy come from?
I think Portage does not consider packages that are not in your world
file, if the update is on world (or system).
To overcome this, I wrote a little script, called update_orphans.sh.
Here it is:
---cut--- update_orphans.sh --cut-
#!/bin/sh
eix -u | gawk '/^\[U\] / { print $2; }' | xargs -r emerge -v1uD
exit $?
---cut---cutcut-
I run it immediately after the main emerge, when I have rsync'ed the
Portage tree.
--
Regards,
Dave [RLU #314465]
==
dwn...@ntlworld.com (David W Noon)
==
signature.asc
Description: PGP signature
Re: [gentoo-user] emerge --update - why doesn't it update my kde packages
Am 04.05.2010 16:59, schrieb David W Noon:
On Tue, 04 May 2010 11:00:01 +0200, Helmut Jarausch wrote about
[gentoo-user] emerge --update - why doesn't it update my kde packages:
[snip]
Still, eix confirmed there were quite a lot of kde packages which have
newer versions, and indeed,
emerge -auv1 -j4 --keep-going $(qlist -IC kde-base/)
upgraded 24 packages.
Where does this discrepancy come from?
I think Portage does not consider packages that are not in your world
file, if the update is on world (or system).
To overcome this, I wrote a little script, called update_orphans.sh.
Here it is:
---cut--- update_orphans.sh--cut-
#!/bin/sh
eix -u | gawk '/^\[U\] / { print $2; }' | xargs -r emerge -v1uD
exit $?
---cut---cutcut-
I run it immediately after the main emerge, when I have rsync'ed the
Portage tree.
No. --with-bdeps is not default anymore because it is considered to be a
bug if portage updates packages not used in any way. This is only if a
package is needed for buildtime.
Program A is version 1.5. To build it, it needs program B which at this
time is version 4.7
B is not needed for anything else!
Now there is an update to B-4.9 . Portage will not update B as long as
there is no update to A.
B is not in the world file. It is not a runtime dependency nore is it a
orphan.
kh
Re: [gentoo-user] emerge --update - why doesn't it update my kde packages
On Tue, May 4, 2010 at 3:57 AM, Helmut Jarausch jarau...@igpm.rwth-aachen.de wrote: Hi, the following situation puzzles me a lot. My 'standard' way of updating is emerge --keep-going -j4 -1 --ask --update --newuse --deep --tree @system @world but it didn't update anything. Still, eix confirmed there were quite a lot of kde packages which have newer versions, and indeed, emerge -auv1 -j4 --keep-going $(qlist -IC kde-base/) upgraded 24 packages. Where does this discrepancy come from? Are they in your world, or depended upon by something in your world? In other words, if you emerge --ask --depclean does it want to remove those packages?
Re: [gentoo-user] emerge --update - why doesn't it update my kde packages
Am 04.05.2010 18:19, schrieb Paul Hartman: On Tue, May 4, 2010 at 3:57 AM, Helmut Jarausch jarau...@igpm.rwth-aachen.de wrote: Hi, the following situation puzzles me a lot. My 'standard' way of updating is emerge --keep-going -j4 -1 --ask --update --newuse --deep --tree @system @world but it didn't update anything. Still, eix confirmed there were quite a lot of kde packages which have newer versions, and indeed, emerge -auv1 -j4 --keep-going $(qlist -IC kde-base/) upgraded 24 packages. Where does this discrepancy come from? Are they in your world, or depended upon by something in your world? In other words, if you emerge --ask --depclean does it want to remove those packages? Hi, do you see the diff in here: emerge -av --depclean These are the packages that would be unmerged: sys-kernel/gentoo-sources selected: 2.6.31-r10 protected: none omitted: 2.6.30-r5 2.6.32-r7 'Selected' packages are slated for removal. 'Protected' and 'omitted' packages will not be removed. Would you like to unmerge these packages? [Yes/No] n Quitting. Packages installed: 847 Packages in world:139 Packages in system: 50 Required packages:846 Number to remove: 1 and emerge -av --depclean --with-bdeps n These are the packages that would be unmerged: dev-util/cmake selected: 2.6.4-r3 protected: none omitted: none app-arch/rpm2targz selected: 9.0.0.3g protected: none omitted: none x11-proto/xf86bigfontproto selected: 1.2.0 protected: none omitted: none dev-java/javacc selected: 4.0-r4 protected: none omitted: none [...] perl-core/Compress-Raw-Zlib selected: 2.021 protected: none omitted: none 'Selected' packages are slated for removal. 'Protected' and 'omitted' packages will not be removed. Would you like to unmerge these packages? [Yes/No] n Quitting. Packages installed: 847 Packages in world:139 Packages in system: 50 Required packages:774 Number to remove: 73 And the other way round emerge -Duav world These are the packages that would be merged, in order: Calculating dependencies... done! Total: 0 packages, Size of downloads: 0 kB Nothing to merge; would you like to auto-clean packages? [Yes/No] n Quitting. emerge -Duav --with-bdeps y world These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild U ] dev-perl/yaml-0.71 [0.68] 111 kB [ebuild U ] app-arch/cabextract-1.2-r1 [1.2] USE=-extra-tools% 190 kB [ebuild U ] dev-perl/Archive-Zip-1.30 [1.20] 193 kB [ebuild U ] perl-core/ExtUtils-ParseXS-2.22.03 [2.20.0401] 40 kB [ebuild U ] virtual/perl-ExtUtils-ParseXS-2.22.03 [2.20.0401] 0 kB Total: 5 packages (5 upgrades), Size of downloads: 533 kB Would you like to merge these packages? [Yes/No] n Quitting. This is normal and expected behavior kh
Re: [gentoo-user] emerge --update - why doesn't it update my kde packages
KH wrote:
Am 04.05.2010 16:59, schrieb David W Noon:
On Tue, 04 May 2010 11:00:01 +0200, Helmut Jarausch wrote about
[gentoo-user] emerge --update - why doesn't it update my kde packages:
[snip]
Still, eix confirmed there were quite a lot of kde packages which have
newer versions, and indeed,
emerge -auv1 -j4 --keep-going $(qlist -IC kde-base/)
upgraded 24 packages.
Where does this discrepancy come from?
I think Portage does not consider packages that are not in your world
file, if the update is on world (or system).
To overcome this, I wrote a little script, called update_orphans.sh.
Here it is:
---cut--- update_orphans.sh--cut-
#!/bin/sh
eix -u | gawk '/^\[U\] / { print $2; }' | xargs -r emerge -v1uD
exit $?
---cut---cutcut-
I run it immediately after the main emerge, when I have rsync'ed the
Portage tree.
No. --with-bdeps is not default anymore because it is considered to be
a bug if portage updates packages not used in any way. This is only if
a package is needed for buildtime.
Program A is version 1.5. To build it, it needs program B which at
this time is version 4.7
B is not needed for anything else!
Now there is an update to B-4.9 . Portage will not update B as long as
there is no update to A.
B is not in the world file. It is not a runtime dependency nore is it
a orphan.
kh
I have with-bdeps set in my make.conf so that it is enabled each time.
I just ran the command given above and it found over 40 packages that
need to be upgraded. I'm not even going to claim that I understand all
the chicken scratch in that command but apparently stuff needed to be
upgraded on my system that was being missed.
It appears to do something good even if it is not related to the OPs
problem.
Dale
:-) :-)
Re: [gentoo-user] emerge --update - why doesn't it update my kde packages
Am 04.05.2010 21:41, schrieb Dale:
---cut--- update_orphans.sh--cut-
#!/bin/sh
eix -u | gawk '/^\[U\] / { print $2; }' | xargs -r emerge -v1uD
exit $?
---cut---cutcut-
I run it immediately after the main emerge, when I have rsync'ed the
Portage tree.
No. --with-bdeps is not default anymore because it is considered to be
a bug if portage updates packages not used in any way. This is only if
a package is needed for buildtime.
Program A is version 1.5. To build it, it needs program B which at
this time is version 4.7
B is not needed for anything else!
Now there is an update to B-4.9 . Portage will not update B as long as
there is no update to A.
B is not in the world file. It is not a runtime dependency nore is it
a orphan.
kh
I have with-bdeps set in my make.conf so that it is enabled each time.
I just ran the command given above and it found over 40 packages that
need to be upgraded. I'm not even going to claim that I understand all
the chicken scratch in that command but apparently stuff needed to be
upgraded on my system that was being missed.
It appears to do something good even if it is not related to the OPs
problem.
Dale
Hi,
For me it does try to update the same packages as --with-bdeps, but it
tries to pull in like 39 new packages.
How and where have you integrated with-bdeps in make.conf?
kh
Re: [gentoo-user] emerge --update - why doesn't it update my kde packages
KH writes: Am 04.05.2010 21:41, schrieb Dale: I have with-bdeps set in my make.conf so that it is enabled each time. I just ran the command given above and it found over 40 packages that need to be upgraded. I'm not even going to claim that I understand all the chicken scratch in that command but apparently stuff needed to be upgraded on my system that was being missed. If a deep @system @world upgrade with --with-bdeps=y does not upgrade the packages, then I think that they are either unnecessary packages that should be depcleaned, or they should go into the world file. This update_orphans.sh script is nice and I used a similar one when I had the problem that a world update did not work due to blockers or something, but normally it should not be necessary. And I believe these problems should better be fixed another way. For me it does try to update the same packages as --with-bdeps, but it tries to pull in like 39 new packages. How and where have you integrated with-bdeps in make.conf? From /usr/share/portage/config/make.conf.example: # EMERGE_DEFAULT_OPTS allows emerge to act as if certain options are # specified on every run. Useful options include --ask, --verbose, # --usepkg and many others. Options that are not useful, such as --help, # are not filtered. #EMERGE_DEFAULT_OPTS= I have it set like this: EMERGE_DEFAULT_OPTS=--with-bdeps y Wonko
Re: [gentoo-user] emerge --update - why doesn't it update my kde packages
Alex Schuster wrote: KH writes: Am 04.05.2010 21:41, schrieb Dale: I have with-bdeps set in my make.conf so that it is enabled each time. I just ran the command given above and it found over 40 packages that need to be upgraded. I'm not even going to claim that I understand all the chicken scratch in that command but apparently stuff needed to be upgraded on my system that was being missed. If a deep @system @world upgrade with --with-bdeps=y does not upgrade the packages, then I think that they are either unnecessary packages that should be depcleaned, or they should go into the world file. This update_orphans.sh script is nice and I used a similar one when I had the problem that a world update did not work due to blockers or something, but normally it should not be necessary. And I believe these problems should better be fixed another way. I run emerge -a --depclean on a regular basis and they do not need to be removed according to it. Something somewhere depends on them or at least portage thinks it does. Point is, it updated them when portage didn't for some reason. For me it does try to update the same packages as --with-bdeps, but it tries to pull in like 39 new packages. How and where have you integrated with-bdeps in make.conf? From /usr/share/portage/config/make.conf.example: # EMERGE_DEFAULT_OPTS allows emerge to act as if certain options are # specified on every run. Useful options include --ask, --verbose, # --usepkg and many others. Options that are not useful, such as --help, # are not filtered. #EMERGE_DEFAULT_OPTS= I have it set like this: EMERGE_DEFAULT_OPTS=--with-bdeps y Wonko I think mine is the same as yours. Mine is: EMERGE_DEFAULT_OPTS=--with-bdeps y It's been there for a good long while. Dale :-) :-)
