It happened t ome quite often the last days on this system because splashutils does not build on it but I'm not sure whether the same happens as well on the other systems ... is this a known issue to you guys?

No it's not, thanks for reporting it swimmer; if you're on IRC, ask us in #friendly-coders but we'll put this on the list to sort out. We should get some failures from expat update ;)

Edit: do you have --verbose in your EMERGE_DEFAULT_OPTS by any chance? It looks like it's mistaking a prior version for an incoming one. There was another bug there, but I don't think that's what triggered that output.

I added a check for --verbose as well as --quiet, and it should now go up or down with -v or -q from there. (You could always do -vv or -qq but now they'll start off at -v or -q based on EMERGE_DEFAULT_OPTS in make.conf; so if it's set at --verbose and you use -q it'll go down to normal.)

I have found the problem. First param is set to "-uDN" and then it calls checkFlags which ads another minus '-'. Either param should just be set to uDN or checkFlags has to check that if param is not empty that it does not already has an minus in front.

Absolutely right; we did have this changed in working version (and I think I mentioned it to bunkacid on irc) but I totally forgot to put it into the beta release. My bad :S Sorry for not being awake before either ;)

No it's not, thanks for reporting it swimmer; if you're
on IRC, ask us in #friendly-coders but we'll put this on the list to
sort out. We should get some failures from expat update

Edit: do you have --verbose in your EMERGE_DEFAULT_OPTS by any chance?
It looks like it's mistaking a prior version for an incoming one. There
was another bug there, but I don't think that's what triggered that
output.

I added a check for --verbose as well as --quiet, and it should now go
up or down with -v or -q from there. (You could always do -vv or -qq but
now they'll start off at -v or -q based on EMERGE_DEFAULT_OPTS in
make.conf; so if it's set at --verbose and you use -q it'll go down to
normal.)

HTH.

Hi Steve

I do not use --verbose in my EMERGE_DEFAULT_OPTS ... but thanks for the fast
response and solution offered

I downloaded beta2b and will use it - the only problem is that I solved my
problem with splashutils and the emerge chain is now clean again ... no more
testcase :-/ Sorry about that.

I do not use --verbose in my EMERGE_DEFAULT_OPTS ... but thanks for the fast
response and solution offered :)

I downloaded beta2b and will use it - the only problem is that I solved my
problem with splashutils and the emerge chain is now clean again ... no more
testcase :-/ Sorry about that.

Hmm OK, that's odd then. I tried testing by setting it to fail automatically and it seemed to be ok; one problem was if one of the pkgs was blocked due to dep failing (eg device-mapper/udev) but it was giving us a message and had the package name highlighted. I'll tweak that for next beta.

Beta 2c, minor bugfix for resume display bug. While I was there, took new resume code from development version, as it was written a while ago, and has been refined a bit as well. I really like it-- you'll only see it when there's more than 10 packages to emerge. They are sorted according to category, with the categories in order of emerge, nicely coloured. Toolchain and rebuilds are broken out of the compact listing:

I use the same version on 4 PC's and alsa-lib failed on every single of them but the error above only showed up on *one* of them?!?
The only difference that I can see is that I use EMERGE_DEFAULT_OPTS="--color y" on the 'erroneous' PC - I'll disable it for now and will see if that has any influence ...

And there are more strange differences: after compiling all the packages *except* alsa-lib the update process stops on 3 of 4 PC's - only on 1 (not the same with the error above btw.) asks if I want to continue with a revdep-rebuild. Strange ...

EDIT: Stupid me, on the PC's revdep-rebuild does not come in I have an alias for update: "update -D" :-/ Is emerge -aUDNR still default?

Greetz
swimmer

PS: I normally download the script on my main PC and distribute it via scp to the others - should be no difference ...

Last edited by swimmer on Tue Sep 18, 2007 9:17 am; edited 1 time in total

Oh noes! ;P Glad it got sorted; added support for --color in EMERGE_DEFAULT_OPTS.

Quote:

Is emerge -aUDNR still default?

Yeah, as long as you don't specify a target (like world/system or some package) and only use (any of) the following options: sqvpaFSR.

Quote:

I normally download the script on my main PC and distribute it via scp to the others - should be no difference ...

None at all, it's just a text file. I think bunkacid had an ebuild, but we're not too worried about that til we get this version finished. Still got to do the config file update at some point, never mind depclean, prelink, eclean blah blah blah ;)

Quote:

As far as I can see the script handles only "--quiet" and "--verbose" - very other option specified let's it bail out ...

OK I've added --color y/n (or Y/N) support (found a small bug in resume while I was looking at this, when you're resuming after the main install has happened, or there never was a main install.) This was a little bit tricky because of the interaction with NOCOLOR, but hopefully it should all be good. I won't put it on front page til tested (gotta go out now, so can't stress it atm.)
md5: e537c100060fe7603bcb0c7864ea3757 http://phpfi.com/263554wget http://phpfi.com/263554?download -O /sbin/update
Wrt to the other options, can you specify which ones break it? It's a PITA checking them TBH.

Thanks for your troubleshooting, Swimmer, hope this one works better ;)

OK, you should know that the -m option does this too. size=256 should be in /etc/update and is the default, giving you 256MB of tmpfs. You can ofc set it to whatever you like (I haven't tested it for ages, but nothing's changed with it, so I don't see why it should have stopped working :)

New version. Gah didn't fix the outta space thing yet, sorry. This one has major changes (it's the one we've been working on for the last couple of months while only minor fixes have been going out.) As ever, bug reports welcome :)

I am stuck! The script stops while trying to install parted-1.8.7. I cannot emerge that version parted either but can emerge parted-1.8.8.
Would you please tell me where to change the package version as referenced by the update script?
Thanks a mill.

I am stuck! The script stops while trying to install parted-1.8.7. I cannot emerge that version parted either but can emerge parted-1.8.8.
Would you please tell me where to change the package version as referenced by the update script?
Thanks a mill.

if you just type emerge parted -vp what does it display_________________The best argument against democracy is a five-minute conversation with the average voter
Great Britain is a republic, with a hereditary president, while the United States is a monarchy with an elective king

I am stuck! The script stops while trying to install parted-1.8.7. I cannot emerge that version parted either but can emerge parted-1.8.8.
Would you please tell me where to change the package version as referenced by the update script?
Thanks a mill.

if you just type emerge parted -vp what does it display

This is what is displayed - thanks for the reply (I'm a noob with emerge ...)

When the script hung on installing parted-1.8.7 I stopped the script and tried an emerge and it too hung while trying to download parted-1.8.7.
I figured that the repository had changed as this world update had been running for about 20hrs. I did an emerge --sync (my bad I guess).
emerge -av parted does however install 1.8.8 which the update script tries to downgrade and hangs at the download stage?

"update" is at its core a wrapper around emerge (a very clever wrapper I might add ) so when you type "update foo" what it eventually does is "emerge foo" (sorry steveL for reducing the script to its core).

So two interesting things here

1) there is no timeout/retries on the source (iirc there is an /etc/make.conf option)
2) portage is trying to install a version of parted that is, as far as your profile is concerned, depreciated

The only reason why an older version of a certain package is being pulled in/installed is because another application has got a setting that say "no newer versions"

What is the EXACT line you are typing when you are using update and also what is the output of emerge world -uvDp <= this might show what the real package that is giving issues is_________________The best argument against democracy is a five-minute conversation with the average voter
Great Britain is a republic, with a hereditary president, while the United States is a monarchy with an elective king

need to see what update is trying to pull in AND in what order and for what reason. This is more a package dependency issue just causing problems with update/portage_________________The best argument against democracy is a five-minute conversation with the average voter
Great Britain is a republic, with a hereditary president, while the United States is a monarchy with an elective king

An "emerge -av =parted-1.8.7" also fails while trying to download while an "emerge -av parted" pulls in 1.8.8??

If it's really just the download stage you can download the file from ftp://ftp.gnu.org/gnu/parted/parted-1.8.7.tar.bz2 [1] and save it in /usr/portage/distfiles.
1.8.7 is marked unstable on most architectures, and 1.8.8 has been out for quite some time. Your best bet to sort this out is to log onto irc.freenode.org and ask in #gentoo, or we're in #friendly-coders. This really is a tree issue (the xorg thing is one too.) As Naib, said update is simply a fancy wrapper for emerge; as you've seen the problems show when you run vanilla emerge. (Not that update never borks; it just tends to shout with two red exclamation marks when something serious happens, and real bugs usually have a stack trace.)

To really see what's pulling it in, run emerge -puDNt world but do not post it directly here; it'll be pages and pages of output, and it takes some deciphering. Use a pastebin (I'd save it for a month) and post the link here or on irc.

You'll more likely get a quicker result on IRC tbh; there are always hundreds of people in #gentoo who are willing to help, and they're always up on what's going on in the tree.