Re: unable to unpack some package
>Michael Schmitz <SCHMITZ@LCBVAX.CCHEM.BERKELEY.EDU> writes:
>> Just use 2.0.x for the time being (or try to figure out how to
>> change the postinst scripts to do the Right Thing).
>a) it has nothing to do with postinst's but is about the internal
>workings of dpkg, b) dpkg is doing the Right Thing, it's the kernel
>which changed a syscall in a needlessly incompatible manner.
I was guessing again :-) are you sure the syscall is going to be fixed
in a future release, or will we have to resolve the link and chown() the
result (still assuming this actually is the syscall in question)?
To UNSUBSCRIBE, email to firstname.lastname@example.org
with a subject of "unsubscribe". Trouble? Contact email@example.com