On Mo August 22 2011, Vincent Danjean wrote:
> 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 ?
Running '# aptitude -t sid install qct' upgraded
mercurial 1.8.3-1 --> mercurial_1.9.1-2 amd64
mercurial-common 1.8.3-1 --> mercurial-common_1.9.1-2 all
qct 1.7-2 --> qct_1.7-3 all
without problems, but didn't reinstate /etc/mercurial/hgrc.d/qct.rc.
After backing out the deletion from the repo, mercurial still works without
errors, so yes, problem solved.
> 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.
I didn't intend to give misleading information. I only mentioned etckeeper,
because for me it was the sign that something in the preceding update broke
mercurial.
Regards,
Peter Pöschl
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
