On 22/08/2011 20:36, Peter Pöschl wrote:
> The last two lines are from the mercurial invocation via etckeeper.
> Could it be that the qct package is somehow broken, which then breaks
> mercurial?
This is perhaps due to the dh_python2 transition. See #637401 for more
info. I just uploaded qct 1.7-3 that breaks mercurial version that cannot
work with the new qct packages. Can you tell me if this package solve
your problem ?
About etckeeper, apt does not give any certitude that a package such
as mercurial will not be broken during the upgrade. So, I'm not sure
what can really be done here (always upgrade mercurial before any other
packages ?) For qct, the "break" line I just added should ensure that
a compatible mercurial is always available.
Regards,
Vincent
--
Vincent Danjean GPG key ID 0x9D025E87 [email protected]
GPG key fingerprint: FC95 08A6 854D DB48 4B9A 8A94 0BF7 7867 9D02 5E87
Unofficial packages: http://moais.imag.fr/membres/vincent.danjean/deb.html
APT repo: deb http://people.debian.org/~vdanjean/debian unstable main
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
