On 10/21/06, Jonas Karlsson <[EMAIL PROTECTED]> wrote: > Having looked at the problem and patch again, I think it not has to do > with running SignProgram as superuser, but the opposite. The tar.bz2 is > unpacked as superuser, then the script switch to normal user and that user > may not have access to the newly unpacked directory.
The script was trying to unpack twice, first time as superuser, second time as regular user. > The solution is to > move Release_Superuser, to above the if-then-else, so the tar.bz2 is > unpacked so that the normal user can access and modify the structure. It solves the problem above, but forces the user to have write access to the dir where the package is placed. That's may be a little bit annoying, but is not a severe problem. The real problem is that, for some packages (in order to preserve permissions) the unpack and re-pack operations have to be done by the superuser. Anyway, SignProgram over .tar.bz2 files is more or less restricted to specific situations (like ours, when getting packages from chrootcompile and putting them into official repository), so I think having the functionality running completely as superuser is not a problem (and is a viable way of having the functionality working). Meanwhile, I'm keeping the changed version here in order to be able to work on the packages for 013. I'll not commit changes at this script ATM. -- Andre Detsch _______________________________________________ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
