At 13:33 7/10/2002 +0800, you wrote: >On Mon, 2002-10-07 at 12:57, Chris McCormick wrote: > > At 12:41 7/10/2002 +0800, you wrote: > > >On Mon, 2002-10-07 at 12:34, Chris McCormick wrote: > > > > >You could try comparing straces of the dpkg command when it works and > > > > >when it doesn't work > > > > > > > > > >strace -fF dpkg -X packagename.deb /path/to/testdir 2>strace.output > > > > > > > > Excellent suggestion - at the moment I can't get it to run > correctly ever > > > > though. :( > > > > > > > > running: > > > > strace -fF dpkg --unpack libc6_2.1.3-24_i386.deb > > > > doesn't tell me anything i can understand. if someone more knowledgable > > > > wants to look at the copy of the output i can send it to them. > > > > > >Can you dump it on a webpage and post the URL to the list? > > > > Sure, > > http://203.59.70.242/strace_dpkg_output.txt > >[pid 4582] ptrace(PTRACE_ATTACH, 4580, 0, 0) = -1 EPERM (Operation not >permitted) >[pid 4582] ptrace(PTRACE_ATTACH, 4577, 0, 0) = -1 EPERM (Operation not >permitted) > >this is something tar is trying to do and failing, thus breaking the >pipe... > >The same happens on the gzip call... > >from man ptrace > >ERRORS > EPERM The specified process cannot be traced. This could > be because the parent has insufficient privileges; > non-root processes cannot trace processes that they > cannot send signals to or those running setuid/set > gid programs, for obvious reasons. Alternatively, > the process may already be being traced, or be init > (pid 1). > > >Not that that helps much. > >If you go > >dpkg-deb --fsys-tarfile packagename.deb > packagename.tar > >and then > >/bin/tar xvf packagename.tar > >Does it untar ok?
Hi Crispin, Yeah that seems to work fine. >Is it a broken package that is cached? try... > >rm -rf /var/cache/apt/archives/*.deb >rm -rf /var/cache/apt/archives/partial/*.deb I have tried that countless times unfortunately :/ >Does dselect fix the problems. Try running dselect, choose update, the >select. Add no new packages, just press return, then select install. Just tried this and got the same error - it's failing on the untar. e.g. dpkg-deb: wait for tar failed: No child processes >All just vague stabs in the dark really... That's cool, thanks for all the suggestions anyway! I'm suspecting i might have some kind of broken glibc action going on. I think that it might not be able to re-attach to tar because of an actual corruption in the library binaries that handle that kind of thing. Maybe it's half installed and some of the hooks to do with process attaching aren't there or some weirdness like that. Hopefully it isn't something sinister. I really want to see if i can solve this without a complete re-install. A re-install of this particular system would not be too awesome at all. If anyone else has any hints that would be great. Thanks! Chris. ______________________________________________________ Chris McCormick - Systems Developer - PerthWeb Pty Ltd Internet Solutions for your business! Level 9/105 St George's Tc - Perth - Western Australia Ph: (08) 9226 1366 Fax: (08) 9226 1375 Visit Perth online! : www.perthweb.com.au PGP Key = http://www.perthweb.com.au/~chris/public.txt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
