Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 223063 - Portage isn't emerging itself first when there is a portage update
Summary: Portage isn't emerging itself first when there is a portage update
Status: RESOLVED FIXED
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Core (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Portage team
URL:
Whiteboard:
Keywords: REGRESSION
Depends on:
Blocks: 216231
  Show dependency tree
 
Reported: 2008-05-21 13:52 UTC by Wilbur Pan
Modified: 2008-05-21 18:56 UTC (History)
0 users

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 Wilbur Pan 2008-05-21 13:52:46 UTC
In all the time I've been using Gentoo, I've been used to portage updating itself first before any other upgrades when I do "emerge -DNuv world".  This doesn't seem to be happening with recent versions of portage.

Reproducible: Always

Steps to Reproduce:
1.  emerge --sync (pulls in a portage upgrade)
2.  emerge -DNuvp world



Actual Results:  
Here's the output:

[snip]

xfce-extra/xfkc/
xfce-extra/xfwm4-themes/

Number of files: 125936
Number of files transferred: 383
Total file size: 158195425 bytes
Total transferred file size: 2131379 bytes
Literal data: 2131379 bytes
Matched data: 0 bytes
File list size: 3070794
File list generation time: 5.932 seconds
File list transfer time: 0.000 seconds
Total bytes sent: 53807
Total bytes received: 3826008

sent 53807 bytes  received 3826008 bytes  221703.71 bytes/sec
total size is 158195425  speedup is 40.77


Performing Global Updates: /usr/portage/profiles/updates/2Q-2008
(Could take a couple of minutes if you have a lot of binary packages.)
  .='update pass'  *='binary update'  @='/var/db move'
  s='/var/db SLOT move' S='binary SLOT move' p='update /etc/portage/package.*'
................................



 * An update to portage is available. It is _highly_ recommended
 * that you update portage now, before any other packages are updated.

 * To update portage, run 'emerge portage' now.

$ sudo emerge -DNuvp world

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

Calculating dependencies... done!
[ebuild     U ] net-libs/gnutls-2.2.5 [2.2.3] USE="nls -bindist -doc -guile -lzo -zlib" 4,806 kB 
[ebuild     U ] dev-lang/python-2.5.2-r4 [2.5.2-r3] USE="berkdb gdbm ipv6 ncurses readline ssl threads -bootstrap -build -doc -examples -sqlite -tk -ucs2 -wininst" 19 kB 
[ebuild     U ] sys-apps/portage-2.1.5.2 [2.1.5] USE="-build -doc -epydoc (-selinux)" LINGUAS="-pl" 5 kB 

Total: 3 packages (3 upgrades), Size of downloads: 4,829 kB



Expected Results:  
In this case, would expect portage to upgrade first, before gnutls and python.

Portage behavior may have changed in this regard, but I haven't seen any documentation to this effect.
Comment 1 Zac Medico gentoo-dev 2008-05-21 18:56:15 UTC
This is fixed in portage-2.1.5.2.