Re: dpkg-deb error (bug?)
On Sat, Oct 02, 1999 at 01:21:09PM -0600, Gary O'Neill wrote:
> When I start cross compiling the latest hurd packages from my linux box, I
> get the following error in the install.log file.
>
> dpkg-deb: "control directory has bad permissions 750 (must be >=0775 and
> <=0775)
> dpkg-deb: "building package '______' in temp_build/adduser.deb'.
>
> Now I've searched far and wide, and chmod'ed all possibly relevant
> directories to 0775, and this error still perists.
Are you using an unfriendly umask? Note that cross-install needs to unpack
and repack every package, so the files get written to your filesystem and
read back. tat's why it is so slow. I would prefer only to repack the
control.tar.gz files and leave the data.tar.gz alone, but currently there is
no way to repack those files to a correct ar archive that dpkg will
recognize (this is a bug, if you can fix it, good!).
> It causes the cross-install script to detect an error status (dpkg-hurd
> passes it on), and it subsequently breaks from the install loop.
Yeah, I can see why. Fix the problem, and this symptom will go away.
> I've seen this error (via a deja power search) in some very obscure
> *linux* bug postings, but never a solution.
Well, then you posted this probably to the wrong list, because we discuss
Hurd bugs here. (technically, bug reports about the install scripts go to
me or debian-hurd, but as this isn't a bug in those scripts, which work
fine for me and other people...)
I am still interested in a solution, in case other people have the same
problems. I am sorry that I can't help you, but I never saw this. A quick
and dirty solution could be to fix the perms in dpkg-hurd, before repacking.
> I've modified the cross-install file to compensate:
> around line 266 and line 302, I changed '|| break' to '&& break' because I
> know it always returns an error status.
This will probably lead to a broken install, depending on if the other
permissions in the package are also broken.
> I'm wondering if someone else has found a *real* solution to this error.
Mmmh. Not me, as I never saw it happen. A first step would be to monitor
where the wrong permissions come from. Try
dpkg-deb --extract ${file} ${ctrl}/..
dpkg-deb --control ${file} ${ctrl}
(wuth the correct variables, of course) and check if the permissions are
correct. If not, then you need to check why they are wrong. Probably monitor
with strace i chmod is called with the correct arguments and if it succeeds.
Also let us know which versions of dpkg and tar you use on Linux, as those
could be relevant.
Thanks,
Marcus
--
`Rhubarb is no Egyptian god.' Debian http://www.debian.org Check Key server
Marcus Brinkmann GNU http://www.gnu.org for public PGP Key
Marcus.Brinkmann@ruhr-uni-bochum.de PGP Key ID 36E7CD09
http://homepage.ruhr-uni-bochum.de/Marcus.Brinkmann/
Reply to: