[Python-apps-team] Bug#968035: Cannot migrate to testing due to Breaks: mercurial-crecord (<= 0.20151121-2)

Laurent Bigonville bigon at debian.org
Fri Aug 7 08:34:35 BST 2020


Source: mercurial
Version: 5.4.1-2
Severity: serious

Hello,

mercurial cannot migrate to testing due to the Breaks against mercurial-crecord (<= 0.20151121-2)

It is discussed here[0] that mercurial-crecord 0.20151121-2 is now a
transitional package that is displaying a NEWS message during the update
to tell the users how they can enable the built-in feature.

So either, the mercurial-crecord should completely be removed or the
Breaks should be changed to mercurial-crecord (<< 0.20151121-2~)

Kind regards,

Laurent Bigonville

[0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804267#25

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.7.0-2-amd64 (SMP w/8 CPU threads)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy



More information about the Python-apps-team mailing list