>> /sbin/upgradepkg: line 164: 438 Segmentation fault
>> removepkg $OLD-upgraded-$TIMESTAMP
>>
>> Package sysvinit-2.78-alpha-1 upgraded with new package
>> ./sysvinit-2.78-alpha-2.tgz.
>
>Try symlinking /bin/sh to /bin/bash1. That ought to fix >everythin right
>up. Doing a "make menuconfig" on the kernel will also result >in a
>segfault, which is also bash's fault. I'll be working on the >default
>shell issue here in a few days. But for now, this is because >of bash2.
I changed the symlink, and upgradepkg is now playing nice :-)
>> A related question: Am I interpreting the package names >>correctly? I
read
>> them as >'package_name'-'version_nr'-'architecture'-'build_nr'.tgz
>
>Yep. That's how we're doing package names on the ports. I >don't know if
>Slackware Intel is going to move towards that or not, but >those of us
in
>port land sure do like knowing which architecture we're >dealing with.
I agree 100% with that naming scheme, but it does have the annoying
sideeffect that upgradepkg can't detect what package to use for an
upgrade as they have different names (either version number or build nr).
It would be nice if 'upgradepkg' could be given the name of the /new/
package and then, if a package by the same name (disregarding version and
build number) was installed, automagically would upgrade the installed
package with the one specified. As it is now you are forced to use the
long syntax of 'upgradepkg oldpackagename%newpackagename'.
/Jesper Juhl - juhl@eisenstein.dk
This archive was generated by hypermail 2b30 : Fri May 09 2003 - 10:00:02 PDT