Is there a reason why update -h config only shows results if update is in /sbin? I modified the script to replace /sbin/update with $(dirname $0)/$(basename $0) and it worked fine. :P

Hmm, it's kinda the same reason as dir is now /root/emerge instead of $HOME; uberpinguin said he wanted it more secure, for installs for end-users (his wife I think;) You should be able to use "$prog" instead of "$(basename $0)" anywhere in the script (including config file); it's set to ${0##*/} (we don't need basename in BASH usually; see http://wooledge.org:8000/BashFAQ/073 or /msg greybot basename on freenode.) Might be worth sticking that in a var at beginning of file so admin can override. kk config file, but have you looked at update -h config recently? It's getting silly man ;p

Quote:

By the way, I made an elementary zsh completion for update

That rocks ppurka, nice one :-) I might even try zsh when I get some timeout, just to see what that's like.

Thanks. I think I will change that to simply $0 :P
If update is not in the $PATH, then simply using $prog will fail.

Heh, best check out http://wooledge.org/mywiki/BashFAQ/028
I was just pointing out that we're far more likely to use foo=${bar##*/} than foo=$(basename "$bar") in BASH and indeed POSIX SH nowadays; I understand basename can do a bit more, but it's not needed most of the time, and the parameter expansion is a lot quicker.
POSIX command-line API

Hi, I'm using 0.1.4.0_pre5, I got some problems about "-r" (resume). It seems 'update' wipes out state files when it receives signals. So I can't resume it after I press Ctrl+C or 'update --stop'. Is it intent by behavior (which is not the same with emerge), or it is a bug?

!! update: WARN Format Error for
>=sys-apps/shadow-4.1.2 <4.1.2 '' '' '' '' Shadow has new pam USE which may be required for reboot, and requires admin review of /etc/login.def
-- Nothing to build

when using Update 0.1.4_pre5 on a MIPs (default/linux/mips/2008.0 *) and Portage 2.1.6.2. Yesterday I got the same sort of error on openrc 0.4.0. Just to see if it was something specific to openrc, I did a normal old "emerge" on it and then found the next items in the list (shadow) now gives me the above error. Unfortunately, update gives up with this warning and forces me back to using "emerge." Anyway to get update working again? Is this a bug in update?

JackieKu that's a bug; if it's keywords or package.mask that was fixed a while back in git, along with a bit more support for --recover when resuming. Sorry I've just been pushing there as things have been hectic last few months and I haven't had any of the usual help (QA and coding both.)

git clone git://weaver.gentooenterprise.com/update.git will get you the latest one (in subdir 'update' of cwd). It should be fairly robust, as only minor tweaks have been added since then. If you can test it and let us know how you get on, that'll be great: I'll push that one out if you don't spot anything major (besides the issue Mike's pointed out which will be fixed before I push it to front page.) saveLog (blame Zorry;) is the only new feature.

iMike: yeah that's a bug, damn. Workaround is just comment out that line in /etc/warning or delete it if you're past the issue. (Make sure you've asked in #gentoo or your system may not reboots aiui.) Interesting, as I updated the ABI stuff, though I seem to recall uberp mentioning that one. I'll bbl and will get on it in next 24 (might take a day or so more to get done, depends on how much work is flying at me.)

What we really need is more people adding warnings somehow; I held off on the e2fslibs thing as I was told it had been sorted, but would have been worth just having the blocker in there from day one; easy enough to delete it once it was done. Hmm update -s should check if there's a new warning or indeed a new update (maybe have a release branch for that.. meh I'm useless at vcs.)

Happy New Year to you all and thanks for the feedback :-) Damn, I've missed the forums in the last few weeks..

BTW there's some BASH tips here and two posts further down, if anyone's interested in learning more; http://phpfi.com/385434 is the earliest backup of update I have, and I think I might go back to that to rework it for 2.2. So, if you feel like hacking, just do it; you can't break anyone else's system ;-) most that'll happen is emerge will get called to install something which can be CTRL-C'ed.

What is really going on here is that this script was written to anticipate the --quiet mode of the newest emerge, back in the day when emerge was unreasonably prolix. The result shows more output than the latest emerge quiet mode, but hugely less than the old emerge "show everything you can get" style. I quite like the compromise in update, which is informative, but fairly terse.

Hmm - why does SteveL ask you to convey something? Is this script still maintained? Haven't had any updates in the repository for quite some time ...

Well because he is a muppet and hasn't got his desktop fixed in MONTHS!!!! and since he relies on cookies to login he can't login to the forums - iirc he has recently asked for his passwd to be reset
as to is it being maintained, yes it is. This script of SteveL is key to another project he is working on so it is in his best interest to keep it upto date
git log shows last commit was on the 21st of Feb

swimmer wrote:

And since I'm writing here anyway: I have problems to change use-flags in the list of updates ... I always get this error:

This is just an example and happens with every package on which I'd like to
change the use-flags ...

Greetz
swimmer

ill point him to this thread when he next logs into irc_________________the table is made from wood. forget what you learnt, the table is made from carbon. forget what you learnt, the table is made from protons. forget what you learnt, the table is made from quarks. forget what you learnt, the table is good for shagging on

I can't reach the site:
The domain name weaver.gentooexperimental.org could not be resolved.

Yeah we've had some teething DNS problems; it should be working now, or in the next 24hours if DNS caches need to catch up.

This version (and older) has a slight problem with -C (depclean) which is run automatically after the usual -uDN world and glsa-check, before revdep-rebuild, when you give no target to install. Basically the world file needs to be alphabetically sorted, but it's not approved to edit it directly so we should call the installer (default: emerge) to do it. We'll add that in next day or two, and then I'll edit the front-post.

I can't reach the site:
The domain name weaver.gentooexperimental.org could not be resolved.

http://213.131.245.114/src/update/update-20110116.tar.bz2 until DNS sorts itself out_________________the table is made from wood. forget what you learnt, the table is made from carbon. forget what you learnt, the table is made from protons. forget what you learnt, the table is made from quarks. forget what you learnt, the table is good for shagging on

Me too facing some problem, although have copied the directly these threads, anyway trying to check, may be i had written something before it that is not working with it. :)

That should be fixed in the 0117 version. Let us know if you have the same (or another) problem again :)

With respect to the depclean issue,

steveL wrote:

Basically the world file needs to be alphabetically sorted

that's not true; we weren't considering versions kept and slots. The slotting issue has led to us having to deal with slots for ebuilds no longer in tree, which we can get from /var/db/pkg/ since they only come up for installed packages which are no longer in tree. So, we're working on that and will have a new version soon.

There's a problem with installing to world in prior versions; packages are only installed as pkg:slot even when only pkg is given. Further, the 20110204 release wasn't installing anything to world. Earlier versions I'm not sure about. Either way, if you've been using this to install to world, check your world file. The slot issue appears to be a relatively recent change to portage, as my old laptop has lots of stuff in world, all installed by update.

You should also review eg /etc/portage/package.keywords and .unmask etc on a regular basis. I have some unmasking stuff done by update going back to June 08(!) on my laptop, in keywords for ~arch packages; often just for one version which will already be obsolete.