| View previous topic :: View next topic |
| Author |
Message |
Loke
Apprentice
Joined: 25 May 2002
Posts: 274
Location: Norway
|
 Posted: Fri Jul 19, 2002 2:13 am Post subject: emerge clean deleted itself - thats not very elegant |
 |
|
Ok,
Might be me who's stupid here, but after doing a 'emerge -p clean' and looking over every package to see that I *didnt* delete anything which didnt have a newer version installed. After issuing the command, the portage package was emerged aswell - not smart, but this thread helped me recover easily:
https://forums.gentoo.org/viewtopic.php?t=8711&highlight=emerge
Now after inspecting 'emerge -p clean' again, I notice:
sys-apps/portage
selected: 2.0.13 1.9.13 1.9.13-r1
protected: 2.0.1
omitted: none
Thats strange. Why is 2.0.1 protected and not the latest version? |
|
| Back to top |
|
 |
rac
Bodhisattva
Joined: 30 May 2002
Posts: 6553
Location: Japanifornia
|
| Posted: Sat Jul 20, 2002 8:49 am Post subject: |
|
|
Could you run the following commands, please? | Code: | $ ls -l /etc/make.profile
$ grep sys-apps/portage /etc/make.profile/packages |
If your database isn't corrupt, perhaps something is locking you to an outdated portage version.
_________________
For every higher wall, there is a taller ladder |
|
| Back to top |
|
|
handsomepete
Guru
Joined: 21 Apr 2002
Posts: 548
Location: Kansas City, MO
|
| Posted: Sat Jul 20, 2002 8:56 pm Post subject: |
|
|
| Maybe check your package.mask and try re-emerging portage and try it again. Mine shows 2.0.13 protected as it should be. |
|
| Back to top |
|
|
BoBB
Tux's lil' helper
Joined: 15 Jun 2002
Posts: 143
Location: Mesa, AZ
|
| Posted: Sat Jul 20, 2002 9:44 pm Post subject: |
|
|
| try an emerge --clean first? this will update your package.mask and update your tree, obviously emerge -p clean doesn't know about 2.0.13 |
|
| Back to top |
|
|
Naan Yaar
Bodhisattva
Joined: 27 Jun 2002
Posts: 1549
|
| Posted: Sun Jul 21, 2002 1:37 am Post subject: |
|
|
I believe 2.0.13 came into emerge and was masked for a bit after that. Depending on when you rsync'ed, you may have this result. Try:
| Code: |
emerge --clean rsync
|
and it should be OK. I usually check the datestamp on /usr/portage/profiles/package.mask to check whether the mirror I synced with is up to date. It does not always have to be and things that are off by a day or two can cause weird results like what you cite above.
| BoBB wrote: | | try an emerge --clean first? this will update your package.mask and update your tree, obviously emerge -p clean doesn't know about 2.0.13 |
|
|
| Back to top |
|
|
|
Other Things Gentoo
