View previous topic :: View next topic |
Author |
Message |
Zarathustra[H] Guru
Joined: 30 Dec 2002 Posts: 389 Location: Cambridge, MA, USA
|
Posted: Wed Feb 19, 2003 4:32 am Post subject: Portage version... |
|
|
Hey...
I'm having wierd problems with portage...
It seems everytime I go to do an emerge -up world, the portage version has changed, and it reemerges it and says its important for me to update all my config files...
Problem is versions keep going up and down...
something like this...
2.0.46-r9 -> 2.0.46-r11 -> 2.0.46-r10 -> 2.0.46-r12 -> 2.0.47-r2 -> 2.0.46-r12
I'm at 2.0.47-r2 right now, and I'm getting the following message:
Code: | * An update to portage is available. It is _highly_ recommended
* that you update portage now, before any other packages are updated.
* Please do so and then update ALL of your configuration files.
|
but the "new" version it is referring to, is actually the OLD version 2.0.46-r12
AHHHHRG
Is something wrong with my system? How come it keeps insisting on merging newer versions and then going back down again?
Is it bad if I ignore the updated config files and just delete them all, casue thus far they have all looked the same as the old ones, and I am tired of editing soo many config files.
Appreciate any help!
Thanks,
Matt
[/code] _________________ ----
Athlon 64 3000+ / 1Gb Kingston Hyperx PC3500 / MSI K8N Neo / Geforce 6800GT
---- |
|
Back to top |
|
|
PT_LAmb Guru
Joined: 22 Apr 2002 Posts: 332 Location: Lisboa (Lisbon), Portugal
|
Posted: Wed Feb 19, 2003 4:58 am Post subject: |
|
|
Well,
I looked in /usr/lib/portage/bin/emerge, and found the following code:
Code: | mynewpv=portage.portdb.xmatch("bestmatch-visible","sys-apps/portage")
mycurpv=portage.best(portage.db[portage.root]["vartree"].dbapi.match("sys-apps/portage"))
if(mycurpv!=mynewpv):
print
print red(" * ")+bold("An update to portage is available.")+" It is _highly_ recommended"
print red(" * ")+"that you update portage now, before any other packages are updated."
print red(" * ")+"Please do so and then update "+bold("ALL")+" of your configuration files."
print |
I tried to go deaper, but I just can't understand some of python's syntax.
I hope someone can explain it...
Good luck,
Ricardo Cordeiro _________________ SETI@Home - http://setiathome.ssl.berkeley.edu/ |
|
Back to top |
|
|
masseya Bodhisattva
Joined: 17 Apr 2002 Posts: 2602 Location: Baltimore, MD
|
Posted: Wed Feb 19, 2003 4:59 am Post subject: |
|
|
I'm currently using 2.0.46-r12 and it's not asking me to upgrade to anything higher or lower than it is. Have you set your ~arch to something to allow for unstable packages to be emerged? Did you try emerge rsync'ing to eliminate the loop or do you think that rsync'ing is what caused the loop? _________________ if i never try anything, i never learn anything..
if i never take a risk, i stay where i am.. |
|
Back to top |
|
|
fudge Tux's lil' helper
Joined: 25 Jul 2002 Posts: 117
|
Posted: Wed Feb 19, 2003 6:31 am Post subject: |
|
|
I suspect that the portage developer releases it, then finds a problem with it and sets the portage version back to a known stable. Given the speed at which portage is rolled forward, and that it is *core* technology for Gentoo Linux, I would much rather see fewer portage releases that will work and never get taken back.
Don't get me wrong, I love Gentoo Linux and appreciate all the hard work that's put in, but every time I see that portage has been updated, I feel nervous. I was bitten by the gcc problem not too long ago and would advise caution over features with regards to the portage package.
Fudge |
|
Back to top |
|
|
fudge Tux's lil' helper
Joined: 25 Jul 2002 Posts: 117
|
Posted: Wed Feb 19, 2003 6:34 am Post subject: |
|
|
Also, I suspect that some of the rsync mirrors aren't as up to date as they can be... |
|
Back to top |
|
|
Schnacki Tux's lil' helper
Joined: 19 Feb 2003 Posts: 105
|
Posted: Wed Feb 19, 2003 8:10 am Post subject: Similar problem? |
|
|
I don't know, if this problem is related, but my portage tells me, that it want's to update to portage-2.0.47-r2. That's ok, so far, the problem is, that it's trying to download the sourcefile
portage-2.0.47-r2.tar.bz2
which is definitely not ok. I don't have any clue why that is. I didn't change the ebuild for portage but I looked at it's code, and the SRC_URI-line says this:
SRC_URI="mirror://gentoo/portage-2.0.47.tar.bz2 http://gentoo.twobit.net/portage/portage-2.0.47.tar.bz2"
Which leaves me even more confused, as I didn't find any reference to "portage-2.0.47-r2.tar.bz2" in the whole file.
Any ideas anyone? |
|
Back to top |
|
|
H-Pi Apprentice
Joined: 26 Jun 2002 Posts: 175 Location: Delft (NL)
|
Posted: Wed Feb 19, 2003 9:12 am Post subject: Re: Similar problem? |
|
|
Schnacki wrote: |
Which leaves me even more confused, as I didn't find any reference to "portage-2.0.47-r2.tar.bz2" in the whole file.
Any ideas anyone? |
well, -rx is never in the file because r2 means 2.0.47 with something changed in the ebuild, a patch or something, but the sourcefile is still just 2.0.47
hm I get may errors with 2.0.47-r2, I gonna downgrade back to 2.0.46-r9, the last portage that didn't gave me any trouble
edit: aargh it's removed from the tree, has anyone got a 2.0.46-r9 ebuild for me??
edi2: huh, with 3 retries, the errors were gone, I'm a bit confused, some sort of gentoo-god fixed it? thank you larry the cow |
|
Back to top |
|
|
Schnacki Tux's lil' helper
Joined: 19 Feb 2003 Posts: 105
|
Posted: Wed Feb 19, 2003 9:25 am Post subject: Re: Similar problem? |
|
|
H-Pi wrote: |
well, -rx is never in the file because r2 means 2.0.47 with something changed in the ebuild, a patch or something, but the sourcefile is still just 2.0.47
|
That's what I figured. The problem is, that trying to update portage tries to download portage-2.0.47-r2.tar.bz2 even though it should (obviously) not.
Ciao, Jan
edit: now it worked. Yay
Last edited by Schnacki on Wed Feb 19, 2003 9:58 pm; edited 1 time in total |
|
Back to top |
|
|
DuF Advocate
Joined: 09 Dec 2002 Posts: 2687 Location: Paris
|
Posted: Wed Feb 19, 2003 12:59 pm Post subject: |
|
|
I've updated from portage-2.0.46-r9 to portage-2.0.47-r2 and for the moment, I've no problem with portage, I can use it, update, install new packages... But at the first time to use it, it asks me to :
Code: | portage: 'portage' user or group missing. Please update baselayout
and merge portage user(250) and group(250) into your passwd
and group files. Non-root compilation is disabled until then.
For the defaults, line 1 goes into passwd, and 2 into group.
portage:x:250:250:portage:/var/tmp/portage:/bin/false
portage::250:portage |
I do it, and all seems to be OK ! |
|
Back to top |
|
|
PT_LAmb Guru
Joined: 22 Apr 2002 Posts: 332 Location: Lisboa (Lisbon), Portugal
|
Posted: Wed Feb 19, 2003 5:41 pm Post subject: Re: Similar problem? |
|
|
H-Pi wrote: | edi2: huh, with 3 retries, the errors were gone, I'm a bit confused, some sort of gentoo-god fixed it? thank you larry the cow |
Maybe the servers were busy.
Ricardo Cordeiro _________________ SETI@Home - http://setiathome.ssl.berkeley.edu/ |
|
Back to top |
|
|
killab n00b
Joined: 28 Dec 2002 Posts: 11
|
Posted: Mon Mar 03, 2003 4:43 am Post subject: <<n00b ALERT!!>> How do I do this? |
|
|
DuF wrote: | I've updated from portage-2.0.46-r9 to portage-2.0.47-r2 and for the moment, I've no problem with portage, I can use it, update, install new packages... But at the first time to use it, it asks me to :
Code: | portage: 'portage' user or group missing. Please update baselayout
and merge portage user(250) and group(250) into your passwd
and group files. Non-root compilation is disabled until then.
For the defaults, line 1 goes into passwd, and 2 into group.
portage:x:250:250:portage:/var/tmp/portage:/bin/false
portage::250:portage |
I do it, and all seems to be OK ! |
I get the same message every time I run emerge rsync, or try to update something. I see no changes in the behavior of portage, but I don't exactly know how to what it asks.
- both portage user and group exist in my system
- I've remerged baselayout
- I don't know what merge portage user and portage group in to passwd means. Are these files that I have to edit? Where do I find info on this?
Thanks |
|
Back to top |
|
|
Reformist Guru
Joined: 06 Oct 2002 Posts: 323
|
Posted: Mon Mar 03, 2003 4:58 am Post subject: |
|
|
Same here. I've restarted, emerge basedlayout. Doesn't seem to be working. _________________ -Phil Crosby |
|
Back to top |
|
|
cederberg Guru
Joined: 23 Jan 2003 Posts: 349 Location: Stockholm / Sweden
|
Posted: Mon Mar 03, 2003 12:44 pm Post subject: |
|
|
Ok, from the Python code above it looks like portage warns about available updates for both up- and downgrades. But I don't quite understand how that would explain the following weird interaction that I had just now:
Code: | # emerge sync
<snip>
* An update to portage is available. It is _highly_ recommended
* that you update portage now, before any other packages are updated.
* Please do so and then update ALL of your configuration files.
# emerge -up system
These are the packages that I would merge, in order:
Calculating system dependencies ...done!
[ebuild U ] sys-apps/cpio-2.5 [2.4.2-r4]
# emerge -up world
These are the packages that I would merge, in order:
Calculating world dependencies ...done!
[ebuild U ] media-libs/xine-lib-1_beta2 [0.9.13-r2]
[ebuild U ] sys-apps/cpio-2.5 [2.4.2-r4]
# emerge -up portage
These are the packages that I would merge, in order:
Calculating dependencies ...done!
# etc-update
Scanning Configuration files...
Exiting: No files to work on!
|
I'm running portage 2.0.47-r7 and it worked like expected some days ago (with the same portage version). |
|
Back to top |
|
|
PT_LAmb Guru
Joined: 22 Apr 2002 Posts: 332 Location: Lisboa (Lisbon), Portugal
|
Posted: Mon Mar 03, 2003 7:02 pm Post subject: |
|
|
It started to happen to me too... and I have portage-2.0.47-r7 as well. Weird...
I'll look at the problem, when I get some spare time.
Ricardo Cordeiro _________________ SETI@Home - http://setiathome.ssl.berkeley.edu/ |
|
Back to top |
|
|
cederberg Guru
Joined: 23 Jan 2003 Posts: 349 Location: Stockholm / Sweden
|
Posted: Mon Mar 03, 2003 8:17 pm Post subject: |
|
|
There seems to be some inverted logic for emerge sync (in 2.0.47-r7). Just ran emerge sync again without the update message showing up. However, afterwards:
Code: | # emerge -up system
These are the packages that I would merge, in order:
Calculating system dependencies ...done!
[ebuild U ] sys-apps/portage-2.0.47-r8 [2.0.47-r7]
*** Portage will stop merging at this point and reload itself,
recalculate dependancies, and complete the merge. |
|
|
Back to top |
|
|
NaiL Apprentice
Joined: 13 Feb 2003 Posts: 228 Location: Spain/BCN
|
Posted: Mon Mar 03, 2003 8:20 pm Post subject: |
|
|
it happens to me too.
i try to install the portage 2.0.47-r8 using...
Code: | emerge /usr/portage/sys-apps/portage/portage-2.0.47-r8.ebuild |
but then i do a...
Code: | emerge -up -deep world |
and it goes back to r7...
i would like to know where is the information used by emerge to choose what's the "stable" version |
|
Back to top |
|
|
PT_LAmb Guru
Joined: 22 Apr 2002 Posts: 332 Location: Lisboa (Lisbon), Portugal
|
Posted: Tue Mar 04, 2003 12:25 am Post subject: |
|
|
PT_LAmb wrote: | It started to happen to me too... and I have portage-2.0.47-r7 as well. Weird...
I'll look at the problem, when I get some spare time.
Ricardo Cordeiro |
Oops... The second emerge sync solved the problem.
Ricardo Cordeiro _________________ SETI@Home - http://setiathome.ssl.berkeley.edu/ |
|
Back to top |
|
|
cederberg Guru
Joined: 23 Jan 2003 Posts: 349 Location: Stockholm / Sweden
|
Posted: Tue Mar 04, 2003 1:00 am Post subject: |
|
|
You mean that it actually solved the problem? Or do you mean that you no longer see the warning whe doing emerge sync?
I don't see the warning about a portage upgrade when I do "emerge sync" any more. On the other hand, portage now shows up when I do "emerge -up system"... So. It is still wrong. The logic seems inverted, showing warnings when there are no upgrades and showing none when there are...
Are you sure this is not what happens to you? |
|
Back to top |
|
|
PT_LAmb Guru
Joined: 22 Apr 2002 Posts: 332 Location: Lisboa (Lisbon), Portugal
|
Posted: Wed Mar 05, 2003 4:43 pm Post subject: |
|
|
cederberg wrote: | I don't see the warning about a portage upgrade when I do "emerge sync" any more. On the other hand, portage now shows up when I do "emerge -up system"... |
Hum... That doesn't happen to me. Are you accepting unstable packages?
Ricardo Cordeiro _________________ SETI@Home - http://setiathome.ssl.berkeley.edu/ |
|
Back to top |
|
|
cederberg Guru
Joined: 23 Jan 2003 Posts: 349 Location: Stockholm / Sweden
|
Posted: Wed Mar 05, 2003 4:57 pm Post subject: |
|
|
No, I only run stable packages (with few exceptions).
Curiously, when I ran "emerge sync" previously today it started complaining about portage again, only that this time there is actually a portage update available. So, one out of three notifications (or lack thereof) have been correct so far...
I'll write this off as some rsync mirror strangeness if I don't see it again. (But will not upgrade portage for a while, as I'm getting tired of the too frequent upgrades.) |
|
Back to top |
|
|
rac Bodhisattva
Joined: 30 May 2002 Posts: 6553 Location: Japanifornia
|
Posted: Wed Mar 05, 2003 8:00 pm Post subject: |
|
|
The code that prints the notice that newer portage versions are available does not (last I checked) understand masking, so it may tell you that an upgrade is available, even when said upgrade is masked or marked unstable. _________________ For every higher wall, there is a taller ladder |
|
Back to top |
|
|
cederberg Guru
Joined: 23 Jan 2003 Posts: 349 Location: Stockholm / Sweden
|
Posted: Wed Mar 05, 2003 8:13 pm Post subject: |
|
|
rac wrote: | The code that prints the notice that newer portage versions are available does not (last I checked) understand masking, so it may tell you that an upgrade is available, even when said upgrade is masked or marked unstable. |
Ahh... That explains the whole issue.
Thanks for the explaination!!! Finally I'll be able to sleep well at night again... ;-) |
|
Back to top |
|
|
NaiL Apprentice
Joined: 13 Feb 2003 Posts: 228 Location: Spain/BCN
|
Posted: Wed Mar 05, 2003 8:52 pm Post subject: |
|
|
where we can see if a packet is masked or not?
how we can diference it? |
|
Back to top |
|
|
cederberg Guru
Joined: 23 Jan 2003 Posts: 349 Location: Stockholm / Sweden
|
Posted: Wed Mar 05, 2003 11:11 pm Post subject: |
|
|
Please see the FAQ, and specifically GF (Gentoo Fundamentals) #5 for an answer to your question.
A bit strange, though, that package unmasking isn't mentioned in the Portage user manual. But then I guess it should be avoided as much as possible... |
|
Back to top |
|
|
NaiL Apprentice
Joined: 13 Feb 2003 Posts: 228 Location: Spain/BCN
|
Posted: Thu Mar 06, 2003 8:56 pm Post subject: |
|
|
thnkiu! |
|
Back to top |
|
|
|