Bug#427829: qct: Removing causes Mercurial errors
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
Bug#427829: qct: Removing causes Mercurial errors
On 23/08/2011 21:01, Peter Pöschl wrote: 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. If you (the admin) removes it, it would be a dpkg error to reinstall it on upgrade. After backing out the deletion from the repo, mercurial still works without errors, so yes, problem solved. Ok, thanks for the feedback. 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. Yes, I understand that. I just wanted to say that, during an upgrade, there are no certitude that upgraded packages are always in a working state. So, if etckeeper relies on a working mercurial *during* an upgrade, it is possible that it will be sometimes broken (I do not know how etckeeper works, so the if is important). In this case, it seems that a missing break was the real culprit. Regards, Vincent 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
Bug#427829: qct: Removing causes Mercurial errors
A was just bitten by another variation of this bug: qct was and still is installed on my computer (amd64, testing). During an 'aptitude full-upgrade' qct was upgraded from 1.7-1 to 1.7-2. Since then, I get this error, too (It was immediately obvious, because I use mercurial as base for etckeeper). # LANG=C dpkg -l qct python-qt4 mercurial python python-support ii mercurial1.8.3-1 scalable distributed version control system ii python 2.6.7-3 interactive high-level object-oriented language ii python-qt4 4.8.3-4 Python bindings for Qt4 ii python-support 1.0.14automated rebuilding support for Python modules ii qct 1.7-2 GUI commit tool This is the complete output of the upgrade: # aptitude full-upgrade Die folgenden Pakete werden aktualisiert: cpp-4.4 gcc-4.4 gcc-4.4-base libarchive1 libasyncns0 libblas3gf libc-bin libc-dev-bin libc6 libc6-dev libglib-perl liblist-moreutils-perl libossp-uuid-perl libossp-uuid16 libsgutils2-2 libx264-116 libxapian22 libxss1 libxv1 lintian locales manpages multiarch-support openjdk-6-jre openjdk-6-jre-headless openjdk-6-jre-lib p7zip-full python python-doc python-minimal qct Die folgenden Pakete werden EMPFOHLEN, aber NICHT installiert: icedtea-6-jre-cacao icedtea-6-jre-jamvm manpages-dev 31 Pakete aktualisiert, 0 zusätzlich installiert, 0 werden entfernt und 0 nicht aktualisiert. Muss 57,6 MB an Archiven herunterladen. Nach dem Entpacken werden 422 kB zusätzlich belegt sein. Wollen Sie fortsetzen? [Y/n/?] Hole:1 http://ftp.debian.org/debian/ wheezy/main libc6-dev amd64 2.13-16 [2.634 kB] Hole:2 http://ftp.debian.org/debian/ wheezy/main libc-dev-bin amd64 2.13-16 [215 kB] Hole:3 http://ftp.debian.org/debian/ wheezy/main libc-bin amd64 2.13-16 [1.083 kB] Hole:4 http://ftp.debian.org/debian/ wheezy/main libc6 amd64 2.13-16 [4.317 kB] Hole:5 http://ftp.debian.org/debian/ wheezy/main libasyncns0 amd64 0.8-4 [13,6 kB] Hole:6 http://ftp.debian.org/debian/ wheezy/main libxss1 amd64 1:1.2.1-2 [16,9 kB] Hole:7 http://ftp.debian.org/debian/ wheezy/main libxv1 amd64 2:1.0.6-2 [20,7 kB] Hole:8 http://ftp.debian.org/debian/ wheezy/main multiarch-support amd64 2.13-16 [140 kB] Hole:9 http://ftp.debian.org/debian/ wheezy/main libxapian22 amd64 1.2.7-1 [1.201 kB] Hole:10 http://ftp.debian.org/debian/ wheezy/main manpages all 3.32-0.2 [750 kB] Hole:11 http://ftp.debian.org/debian/ wheezy/main gcc-4.4 amd64 4.4.6-8 [2.699 kB] Hole:12 http://ftp.debian.org/debian/ wheezy/main cpp-4.4 amd64 4.4.6-8 [3.871 kB] Hole:13 http://ftp.debian.org/debian/ wheezy/main gcc-4.4-base amd64 4.4.6-8 [126 kB] Hole:14 http://ftp.debian.org/debian/ wheezy/main locales all 2.13-16 [4.812 kB] Hole:15 http://ftp.debian.org/debian/ wheezy/main python-doc all 2.6.7-3 [20,8 kB] Hole:16 http://ftp.debian.org/debian/ wheezy/main python all 2.6.7-3 [177 kB] Hole:17 http://ftp.debian.org/debian/ wheezy/main python-minimal all 2.6.7-3 [39,2 kB] Hole:18 http://ftp.debian.org/debian/ wheezy/main libarchive1 amd64 2.8.4-2 [153 kB] Hole:19 http://ftp.debian.org/debian/ wheezy/main libblas3gf amd64 1.2.20110419-2 [292 kB] Hole:20 http://ftp.debian.org/debian/ wheezy/main libglib-perl amd64 2:1.224-1 [465 kB] Hole:21 http://ftp.debian.org/debian/ wheezy/main liblist-moreutils-perl amd64 0.33-1 [64,4 kB] Hole:22 http://ftp.debian.org/debian/ wheezy/main libossp-uuid16 amd64 1.6.2-1.1 [58,4 kB] Hole:23 http://ftp.debian.org/debian/ wheezy/main libossp-uuid-perl amd64 1.6.2-1.1 [34,8 kB] Hole:24 http://ftp.debian.org/debian/ wheezy/main libsgutils2-2 amd64 1.32-1 [82,4 kB] Hole:25 http://ftp.debian.org/debian/ wheezy/main libx264-116 amd64 2:0.116.2042+git178455c-1 [413 kB] Hole:26 http://ftp.debian.org/debian/ wheezy/main lintian all 2.5.2 [617 kB] Hole:27 http://ftp.debian.org/debian/
Bug#427829: qct: Removing causes Mercurial errors
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 vdanj...@debian.org 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 debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#427829: qct: Removing causes Mercurial errors
* Vincent Danjean [EMAIL PROTECTED] [20070725 14:21]: The problem occurs when qct package is removed but not purged. In this case, the conffile keep here. So mercurial try to load qct but cannot because the extension is not here anymore. I cannot remove /etc/mercurial/hgrc.d/qct.rc on 'remove' operation because this will go against debian policy. One solution I see would be to extend the syntax of extension loading in mercurial so that it would be possible to try to load the extension if present but not to fail if the extension is not present. Note that this cannot be the default: if a user requires a extension, it is better to fail immediately if the extension is not here. I'd like to have a syntax for defining optional extensions, too, to support one hgrc being used with different versions of Mercurial. Specifying more than one location to try might be helpful, too, for renamed extensions. What about borrwing shell syntax '||'? The '!' can aleeady be used to disable an extension. hgext.foo = || ! bar = /path/to/bar || /path/to/bar.py || ! Regards, Thomas -- [EMAIL PROTECTED] - http://intevation.de/~thomas/ - OpenPGP key: 0x5816791A Intevation GmbH, Osnabrueck - Register: Amtsgericht Osnabrueck, HR B 18998 Geschaeftsfuehrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#427829: qct: Removing causes Mercurial errors
tag 427829 +help thanks Hi, I do not see yet how this bug can be correctly handle. I will explain it more in detail for non-debian people. If anyone has an idea... mercurial read all files in /etc/mercurial/hgrc.d This allows other packages such as 'qct' to install here a configuration file so that mercurial will read this extension when installed. /etc/mercurial/hgrc.d/qct.rc is a debian conffile. That is : if the admin modifies it (so that qct is not system-wide enabled by default for example) it will not be overwritten on upgrade (the admin will have to choose between keeping the old version, getting the new one, watch the differences...) When a debian user wants to remove a package, he can 'remove' it or 'purge' it. The difference is about the conffiles: when removing the package, conffiles are let on the system (so that the admin keeps its modifications if any (if he want to reinstall the package later for example)). When purging, conffiles are also removed. The problem occurs when qct package is removed but not purged. In this case, the conffile keep here. So mercurial try to load qct but cannot because the extension is not here anymore. I cannot remove /etc/mercurial/hgrc.d/qct.rc on 'remove' operation because this will go against debian policy. One solution I see would be to extend the syntax of extension loading in mercurial so that it would be possible to try to load the extension if present but not to fail if the extension is not present. Note that this cannot be the default: if a user requires a extension, it is better to fail immediately if the extension is not here. Another solution would be that the error message from mercurial tells the user about the file that request this extension. In this case, I can add a comment in this file (/etc/mercurial/hgrc.d/qct.rc) to explain what to do (disabling the extension or purging the package) So, if you have any comment/idea, that would be great. Best regards, Vincent John Goerzen wrote: Package: qct Severity: important Removing this package causes all hg commands to spew: *** failed to import extension hgext.qct: No module named qct This appears to be due to the qct config file /etc/mercurial/hgrc.d/qct.rc this is an unmodified file. purging qct fixes the problem -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (99, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.18-4-k7 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=en_US (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages qct depends on: ii cvs 1:1.12.13-8 Concurrent Versions System ii mercurial 0.9.3-2 Scalable distributed version contr ii python 2.4.4-6 An interactive high-level object-o pn python-qt4 none (no description available) ii python-support 0.6.4automated rebuilding support for p ii subversion 1.4.2dfsg1-2 Advanced version control system qct recommends no packages. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#427829: qct: Removing causes Mercurial errors
Package: qct Severity: important Removing this package causes all hg commands to spew: *** failed to import extension hgext.qct: No module named qct This appears to be due to the qct config file /etc/mercurial/hgrc.d/qct.rc this is an unmodified file. purging qct fixes the problem -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (99, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.18-4-k7 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=en_US (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages qct depends on: ii cvs 1:1.12.13-8 Concurrent Versions System ii mercurial 0.9.3-2 Scalable distributed version contr ii python 2.4.4-6 An interactive high-level object-o pn python-qt4 none (no description available) ii python-support 0.6.4automated rebuilding support for p ii subversion 1.4.2dfsg1-2 Advanced version control system qct recommends no packages. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
