Bug #768286 describes a problem where python{,3}-zope.interface-dbg does not
properly handle the transition of their /usr/share/doc/PACKAGE paths from
symlinks to directories. After hacking my local /usr/sbin/piuparts to work
around its bug #766921, I was able to reproduce the failure locally.
I *think* I have a fix in zope.interface's svn, but it's been darn difficult
for me to test piuparts with the new debs. All my other local tests are
happy, but I cannot seem to run piuparts with the locally built debs. Maybe
I'm misreading the manpage, but I would have thought this should work:
$ piuparts -d wheezy -d jessie ./python3-zope.interface_4.1.1-3_amd64.deb
but all that happens is that piuparts fails with:
9m35.9s DEBUG: Starting command: ['chroot', '/tmp/tmpGpZMFD', 'dpkg-query',
'-f', '${Package} ${Status}\n', '-W', 'python3-zope.interface-dbg']
9m35.9s DUMP:
dpkg-query: no packages found matching python3-zope.interface-dbg
9m35.9s DEBUG: Command failed (status=1), but ignoring error: ['chroot',
'/tmp/tmpGpZMFD', 'dpkg-query', '-f', '${Package} ${Status}\n', '-W',
'python3-zope.interface-dbg']
9m35.9s ERROR: Could not install python3-zope.interface-dbg.
So I thought that maybe explicit .deb paths are incompatible with multiple -d
options. Surely this example straight from the manpage should work:
$ piuparts ./python3-zope.interface_4.1.1-3_amd64.deb
Nope, same failure.
So anyway, if you're a piuparts expert, or just have a few moments to review
the package's svn, I appreciate any feedback you can provide. Otherwise I'll
upload and hope for the best. ;)
Cheers,
-Barry
signature.asc
Description: PGP signature
