Your message dated Sat, 03 Dec 2005 14:02:22 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#340301: fixed in devscripts 2.9.10
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)
--------------------------------------
Received: (at submit) by bugs.debian.org; 22 Nov 2005 15:17:28 +0000
>From [EMAIL PROTECTED] Tue Nov 22 07:17:28 2005
Return-path: <[EMAIL PROTECTED]>
Received: from mail.metronet.co.uk ([213.162.97.75])
by spohr.debian.org with esmtp (Exim 4.50)
id 1EeZtf-0008LP-Mk
for [EMAIL PROTECTED]; Tue, 22 Nov 2005 07:17:28 -0800
Received: from riva.pelham.vpn.ucam.org
(83-216-156-196.colinw664.adsl.metronet.co.uk [83.216.156.196])
by smtp.metronet.co.uk (MetroNet Mail) with ESMTP id C286D42E718
for <[EMAIL PROTECTED]>; Tue, 22 Nov 2005 15:14:42 +0000 (GMT)
Received: from cjwatson by riva.pelham.vpn.ucam.org with local (Exim 3.36 #1
(Debian))
for [EMAIL PROTECTED]
id 1EeZrB-00009J-00; Tue, 22 Nov 2005 15:14:53 +0000
Date: Tue, 22 Nov 2005 15:14:53 +0000
From: Colin Watson <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: debcommit: bzr support
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="DocE+STaALJfprDB"
Content-Disposition: inline
User-Agent: Mutt/1.5.9i
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2005_01_02
--DocE+STaALJfprDB
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Package: devscripts
Version: 2.9.9
Severity: wishlist
Tags: patch
Yeah, I know, yet another revision control system ... anyway, patch
attached. At the moment --release just does a commit and not a (useful)
tag because there's no symbolic tag support in bzr yet.
Thanks,
--
Colin Watson [EMAIL PROTECTED]
--DocE+STaALJfprDB
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename="debcommit-bzr.patch"
Index: debcommit.pl
===================================================================
--- debcommit.pl (revision 274)
+++ debcommit.pl (working copy)
@@ -11,8 +11,9 @@
=head1 DESCRIPTION
debcommit generates a commit message based on new text in debian/changelog,
-and commits the change to a package's cvs, svn, svk, or arch repository. It
-must be run in a cvs, svn, svk, or arch working copy for the package.
+and commits the change to a package's cvs, svn, svk, arch, or bzr
+repository. It must be run in a cvs, svn, svk, arch, or bzr working copy for
+the package.
=head1 OPTIONS
@@ -22,6 +23,8 @@
Commit a release of the package. The version number is determined from
debian/changelog, and is used to tag the package in cvs, svn, svk, or arch.
+bzr does not yet support symbolic tags, so you will only get a normal
+commit.
Note that svn/svk tagging conventions vary, so debcommit uses
L<svnpath(1)> to determine where the tag should be placed in the
@@ -100,6 +103,9 @@
return "tla";
}
}
+ elsif (-d ".bzr") {
+ return "bzr";
+ }
else {
# svk has no useful directories so try to run it.
my $svkpath=`svk info . 2>/dev/null| grep -i '^Depot Path:' |
cut -d ' ' -f 2`;
@@ -107,7 +113,7 @@
return "svk";
}
- die "not in a cvs, subversion, arch, or svk working copy\n";
+ die "not in a cvs, subversion, arch, bzr, or svk working
copy\n";
}
}
@@ -126,7 +132,7 @@
sub commit {
my $message=shift;
- if ($prog eq 'cvs' || $prog eq 'svn' || $prog eq 'svk') {
+ if ($prog eq 'cvs' || $prog eq 'svn' || $prog eq 'svk' || $prog eq
'bzr') {
if (! action($prog, "commit", "-m", $message)) {
die "commit failed\n";
}
@@ -191,16 +197,19 @@
die "failed tagging with $tag\n";
}
}
+ elsif ($prog eq 'bzr') {
+ warn "No support for symbolic tags in bzr yet.\n";
+ }
}
sub getmessage {
my $ret;
if ($prog eq 'cvs' || $prog eq 'svn' || $prog eq 'svk' ||
- $prog eq 'tla' || $prog eq 'baz') {
+ $prog eq 'tla' || $prog eq 'baz' || $prog eq 'bzr') {
$ret='';
my $subcommand;
- if ($prog eq 'cvs' || $prog eq 'svn' || $prog eq 'svk') {
+ if ($prog eq 'cvs' || $prog eq 'svn' || $prog eq 'svk' || $prog
eq 'bzr') {
$subcommand = 'diff';
} else {
$subcommand = 'file-diff';
--DocE+STaALJfprDB--
---------------------------------------
Received: (at 340301-close) by bugs.debian.org; 3 Dec 2005 22:13:32 +0000
>From [EMAIL PROTECTED] Sat Dec 03 14:13:32 2005
Return-path: <[EMAIL PROTECTED]>
Received: from katie by spohr.debian.org with local (Exim 4.50)
id 1EifSY-0007LZ-6y; Sat, 03 Dec 2005 14:02:22 -0800
From: Julian Gilbey <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.60 $
Subject: Bug#340301: fixed in devscripts 2.9.10
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Sat, 03 Dec 2005 14:02:22 -0800
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2005_01_02
Source: devscripts
Source-Version: 2.9.10
We believe that the bug you reported is fixed in the latest version of
devscripts, which is due to be installed in the Debian FTP archive:
devscripts_2.9.10.dsc
to pool/main/d/devscripts/devscripts_2.9.10.dsc
devscripts_2.9.10.tar.gz
to pool/main/d/devscripts/devscripts_2.9.10.tar.gz
devscripts_2.9.10_i386.deb
to pool/main/d/devscripts/devscripts_2.9.10_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.
Julian Gilbey <[EMAIL PROTECTED]> (supplier of updated devscripts 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: Sat, 3 Dec 2005 20:24:38 +0000
Source: devscripts
Binary: devscripts
Architecture: source i386
Version: 2.9.10
Distribution: unstable
Urgency: low
Maintainer: Julian Gilbey <[EMAIL PROTECTED]>
Changed-By: Julian Gilbey <[EMAIL PROTECTED]>
Description:
devscripts - Scripts to make the life of a Debian Package maintainer easier
Closes: 232000 237726 246006 326881 339657 340301
Changes:
devscripts (2.9.10) unstable; urgency=low
.
* bts: handle 8-bit encodings in DEBFULLNAME for "From:" field of emails
sent (Closes: #339657)
* bts: submitter and reassign accept multiple bug numbers (Closes:
#237726)
* bts: document "it" for referring to previous bug number
* debchange: provide -m/--maintmaint switch to use the maintainer name
from the most recent changelog entry rather than using the environment
variables (Closes: #232000)
* debcommit: add support for bzr (Closes: #340301)
* debuild: improve examples in manpage (Closes: #326881)
* dpkg-depcheck: completely rewrite symlink handling code to fix bug
where /usr was a symlink (Closes: #246006)
Files:
afaa47564f99155bc7c81657b7dc4f40 685 devel optional devscripts_2.9.10.dsc
c6d7511ec922247696b2f9da14d1c838 337329 devel optional devscripts_2.9.10.tar.gz
d5b455fd3535f4aab3ed34d28f93c68c 293406 devel optional
devscripts_2.9.10_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
iD8DBQFDkgtWDU59w/205FkRAqu0AJ9r4degG5vvYbeweUzYP7Im/WR8jACeOd+8
2TJ+KmA4bv0atc39+D7WWM8=
=lvtT
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
