On Sat, Aug 23, 2003 at 03:11:41PM +0200, Frank Hellmuth wrote: > Hi! > > since a few days I find in every outpit of "emerge -Dup world" the following > lines: > > [ebuild U ] sys-libs/db-3.2.9-r8 [4.0.14-r2] > [ebuild U ] dev-perl/libnet-1.16 [1.13] >
You can see from this output that portage wants to upgrade db-3.2.9-r8 but version 4.0.14-r2 is also installed and it's not listed as a downgrade. That means that the two versions are in separate slots meaning both are installed for compatibility reasons. > If I do a "emerge libnet db" it end with > > >>> original instance of package unmerged safely. > >>> Regenerating /etc/ld.so.cache... > >>> sys-libs/db-4.0.14-r2 merged. > This shows that you reinstalled version 4.0.14-r2, when you issued the command 'emerge libnet db', rather than the newer version of version 3. In order to solve this you can either give portage the full path and version of the version of db that you want to upgrade, such as 'emerge sys-libs/db-3.2.9-r8' or just use 'emerge -Du world' which will handle this for you. > and of course the corresponding lines for libnet. Doing a "emerge -Dup world" > I see the same line as above again. > > Why does portage think the upgrade didn't happen? > > Frank > -- Bryan Traywick ([EMAIL PROTECTED]) -- [EMAIL PROTECTED] mailing list
