Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 252985 - After upgrading to portage 2.1.6.4, massive reinstall is needed
Summary: After upgrading to portage 2.1.6.4, massive reinstall is needed
Status: RESOLVED FIXED
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Core - Interface (emerge) (show other bugs)
Hardware: AMD64 Linux
: High normal (vote)
Assignee: Portage team
URL: http://www.gentoo.org
Whiteboard:
Keywords:
: 254221 (view as bug list)
Depends on:
Blocks: 254662
  Show dependency tree
 
Reported: 2008-12-29 12:24 UTC by Francisco Lloret
Modified: 2009-01-12 20:11 UTC (History)
4 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Francisco Lloret 2008-12-29 12:24:54 UTC
After a emerge --sync, a message that says a new version of portage is available is shown. I do a emerge portage and then the package is updated to portage-2.1.6.4.

Then, a emerge -p world shows that the system need a 3 package update (busybox, whois and automake) and a 161 package Reinstall.

I downgrade portage to 2.1.4.5 and then the need of reinstall dissapears:

# emerge -pv world

These are the packages that would be merged, in order:

Calculating world dependencies... done!

[ebuild     U ] sys-apps/portage-2.1.6.4 [2.1.4.5] USE="-build -doc -epydoc (-selinux)" LINGUAS="-pl" 0 kB 
*** Portage will stop merging at this point and reload itself,
    then resume the merge.
[ebuild     U ] sys-apps/busybox-1.12.2-r1 [1.11.1] USE="pam -debug -make-symlinks -savedconfig (-selinux) -static" 1,974 kB 
[ebuild     U ] net-misc/whois-4.7.27 [4.7.26] USE="nls" 67 kB 
[ebuild     U ] sys-devel/automake-1.10.2 [1.10.1-r1] 915 kB 

Total: 4 packages (4 upgrades), Size of downloads: 2,955 kB
Comment 1 Allen Brooker (AllenJB) 2008-12-29 12:46:55 UTC
The default action for the world and system sets has changed. Use the --update (-u) option to perform an update check.

(I believe this is a side-effect of the upcoming sets functionality)
Comment 2 Francisco Lloret 2008-12-29 15:05:43 UTC
Thanks
Comment 3 martin holzer 2008-12-30 10:34:51 UTC
there's no info about this changes in any way

in this kind gentoo messes up completly
Comment 4 Luca Santarelli 2008-12-30 14:28:16 UTC
(In reply to comment #3)
> there's no info about this changes in any way
> 
> in this kind gentoo messes up completly

Sadly, I second that. I was lucky that somebody in the forums pointed me to this bug report, I couldn't understand the reason for this. However, using "emerge world -D", if I use --update I get a lesser number of updates than the ones reported without the --update option (namely rpm2targz). This makes things even more strange and broken - if not really broken, at least from a user-point-of-view.

What's the proper way to have the old behaviour?
Comment 5 Oleg Popov 2008-12-30 17:41:12 UTC
(In reply to comment #1)
> The default action for the world and system sets has changed. Use the --update
> (-u) option to perform an update check.
> 
> (I believe this is a side-effect of the upcoming sets functionality)
> 

I thing -n will be a better way to have old behaviour than -u
Comment 6 Oleg Popov 2008-12-30 17:41:54 UTC
(In reply to comment #5)
*think
Comment 7 Allen Brooker (AllenJB) 2008-12-30 17:44:42 UTC
You probably want to use -uD (update, deep dependency checking)

The problem with -n is that (I believe) it will add packages to your world set, which is not what you want to do (all the dependencies will now be in the world set, which will basically leave you in a big mess in terms of package management).
Comment 8 Zac Medico gentoo-dev 2008-12-30 18:49:08 UTC
Either -u or -n is fine. When used with world or system sets, those options won't cause anything to be added to the world file.
Comment 9 Zac Medico gentoo-dev 2008-12-30 21:19:30 UTC
I've added a note about this in the ChangeLog and in an ewarn message. The ewarn message that looks like this:

 *
 * In portage-2.1.6, the default behavior has changed for `emerge world`
 * and `emerge system` commands. These commands will reinstall all
 * packages from the given set unless an option such as --noreplace,
 * --update, or --newuse is specified.
 *
Comment 10 Luca Santarelli 2008-12-31 11:45:01 UTC
(In reply to comment #9)
> I've added a note about this in the ChangeLog and in an ewarn message. The
> ewarn message that looks like this:

Thank you very much. The message sounds clear on what the user has to do, maybe this bug can be closed now.
Comment 11 Lars Wendler (Polynomial-C) (RETIRED) gentoo-dev 2009-01-08 12:58:47 UTC
*** Bug 254221 has been marked as a duplicate of this bug. ***
Comment 12 Lars Wendler (Polynomial-C) (RETIRED) gentoo-dev 2009-01-08 13:35:55 UTC
*** Bug 254221 has been marked as a duplicate of this bug. ***
Comment 13 Zac Medico gentoo-dev 2009-01-12 20:11:50 UTC
In 2.1.6.5, there's a note about this in the RELEASE-NOTES file (and the ewarn message is still shown after upgrade from 2.1.x).