Your message dated Fri, 02 Nov 2007 11:47:03 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#447088: fixed in mercurial 0.9.5-2
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: mercurial
Version: 0.9.4-1
Severity: normal
File: /etc/mercurial/hgrc.d/hgext.rc

Currently,

- by default, /etc/mercurial/hgrc.d/hgext.rc loads several extensions;

- a user whose $HOME is shared across multiple (heterogeneous) hosts
  is likely to want to enable these extensions explicitly in her
  ~/.hgrc;

- loading an extension twice under a different "name" causes hg to
  complain to stderr (because the bindings shadow themselves):

    $ grep mq ~/.hgrc /etc/mercurial/hgrc.d/hgext.rc
    /home/twb/.hgrc:hgext.mq=
    /etc/mercurial/hgrc.d/hgext.rc:hgext/mq=
    $ hg help >/dev/null
    extension 'hgext/mq' overrides commands: qheader qnew ^qpop qrestore 
qapplied qguard qclone ^strip qgoto qprev qunapplied ^qrefresh qtop ^qdiff 
qseries qcommit|qci qfold qnext qdelete|qremove|qrm ^qimport qselect ^qpush 
^qinit qrename|qmv qsave
    $

- mercurial.el includes this in the modeline, i.e. instead of

    (Fundamental Hg:0)

  one gets

    (Fundamental Hg:module hgext/mq overrides qheader+module hgext/mq
                 overrides qnew+module hgext/mq overrides ^qpop+modul

This situation is undesirable.  I see a number of potential solutions:

- user removes offending entries from hgext.rc.  This is not feasible
  because it requires root access.

- user removes offending entries from ~/.hgrc, then copies hgext.rc to
  every other systems (e.g. BSD, OS X) on she uses.  This is not
  feasible because it requires root access.

- Debian maintainer notes in README.Debian that putting foo= or
  hgext.foo= in ~/.hgrc causes problems, and users SHOULD use
  hgext/foo= instead.  User follows instructions, and we all hope that
  no other distribution uses the hgext.foo= notation in its site-wide
  rc file.

- Debian maintainer removes hgext.rc, so extensions are off by default
  under Debian.

- Debian/upstream modifies mercurial.el to discard shadowing warnings.
  This would solve the immediate issue, but of course anyone running
  hg(1) directly on the command line would still see obnoxious
  warnings on stderr.

- Debian/upstream modifies hg so that it understands that foo,
  hgext/foo and hgext.foo are the same extension, and not to emit a
  warning.

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (990, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.22-2-amd64 (SMP w/1 CPU core)
Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages mercurial depends on:
ii  libc6                         2.6.1-5    GNU C Library: Shared libraries
ii  python                        2.4.4-6    An interactive high-level object-o
ii  python-support                0.7.4      automated rebuilding support for p
ii  python2.5                     2.5.1-5    An interactive high-level object-o

Versions of packages mercurial recommends:
ii  rcs                           5.7-20     The GNU Revision Control System
ii  tk8.4 [wish]                  8.4.16-1   Tk toolkit for Tcl and X11, v8.4 -

-- no debconf information



--- End Message ---
--- Begin Message ---
Source: mercurial
Source-Version: 0.9.5-2

We believe that the bug you reported is fixed in the latest version of
mercurial, which is due to be installed in the Debian FTP archive:

mercurial_0.9.5-2.diff.gz
  to pool/main/m/mercurial/mercurial_0.9.5-2.diff.gz
mercurial_0.9.5-2.dsc
  to pool/main/m/mercurial/mercurial_0.9.5-2.dsc
mercurial_0.9.5-2_i386.deb
  to pool/main/m/mercurial/mercurial_0.9.5-2_i386.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Vincent Danjean <[EMAIL PROTECTED]> (supplier of updated mercurial package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Fri, 02 Nov 2007 11:59:03 +0100
Source: mercurial
Binary: mercurial
Architecture: i386 source 
Version: 0.9.5-2
Distribution: unstable
Urgency: low
Maintainer: Vincent Danjean <[EMAIL PROTECTED]>
Changed-By: Vincent Danjean <[EMAIL PROTECTED]>
Description: 
 mercurial  - Scalable distributed version control system
Closes: 447088
Changes: 
 mercurial (0.9.5-2) unstable; urgency=low
 .
   * Apply patch to change 'hgext/' into 'hgext.' when loading an extension
     Current config files use the documented syntax (ie 'hgext.extname=')
     Users can use 'hgext/extname=' in their hgrc if they want to
     (Closes: #447088)
Files: 
 d25512ca5c1666cbcb52723c8c3f3a56 17166 devel optional mercurial_0.9.5-2.diff.gz
 d36948279b5983b282d1637b365a8cc2 688 devel optional mercurial_0.9.5-2.dsc
 de816322d1e13a2b93167432be6ae55e 463826 devel optional 
mercurial_0.9.5-2_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFHKwtDC/d4Z50CXocRAs6YAJ9fwLLESbSH6VhCwwyP83CR7jfBIwCfc1W0
sR5cnOChvWAV6EqZkr73I/4=
=zooC
-----END PGP SIGNATURE-----



--- End Message ---

Reply via email to