Your message dated Tue, 03 Oct 2006 08:50:33 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Mercurial available in backport
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.6-1
Severity: wishlist
There is very little reason to use the cdbs patchsys-quilt.mk file.
simple-patchsys works just fine for what you need it to do. Switching
to a simpler tool will allow you to reduce the version dependency to
something obtainable on sarge, making backports much easier.
Personally, I try to construct control, build, and maintainer scripts so
that you can backport one version (the current stable version). There
is nothing in the mercurial software package that requires unstable
tools, so why make the packaging process dependent upon unstable?
-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.8-2-k7
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ANSI_X3.4-1968) (ignored: LC_ALL
set to C)
--- End Message ---
--- Begin Message ---
Since a few release, I backport mercurial in http://www.backports.org.
So latest releases of mercurial are available for stable. And so, I am
closing this bug (even if I use some other packages from backport
instead of totally repackaging the software with pure stable tools).
Best regards,
Vincent
--- End Message ---
