Your message dated Mon, 09 Jun 2008 05:02:03 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#485335: fixed in trac-bzr 0.2+bzr31-6
has caused the Debian Bug report #485335,
regarding trac-bzr: FTBFS when converted to new source format 3.0 (quilt): 
invalid patch
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
485335: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=485335
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: trac-bzr
Version: 0.2+bzr31-5
Severity: minor
Usertags: 3.0-quilt-by-default

To prepare a possible switch to the new source package format "3.0
(quilt)" [1], I converted all source packages and tried to rebuild them.
Unfortunately, trac-bzr failed, you can try yourself with those
commands (and dpkg-dev >= 1.14.19 [2]) :

$ apt-get source trac-bzr
$ sed -i -e '/^Source:/ aFormat: 3.0 (quilt)' trac-bzr-0.2+bzr31/debian/control
$ dpkg-source -b trac-bzr-0.2+bzr31
$ dpkg-source -x trac-bzr_0.2+bzr31-5.dsc
$ cd trac-bzr-0.2+bzr31 && debuild -us -uc

In this process, if the .diff.gz contains changes to upstream files,
dpkg-source will have created a corresponding patch in
debian/patches/debian-changes-0.2+bzr31-5 and will have registered that
patch in a quilt series (debian/patches/series, it is created if needed).
All the patches listed in the "series" file are applied directly during
the extraction (dpkg-source -x). quilt itself is used if available (and
will thus lead to the creation of the .pc directory), otherwise
dpkg-source applies the patches by itself. For more information about the
new source package format see the manual page dpkg-source(1).

In the case of trac-bzr, the quilt series contains some invalid
patches. The stats in the headers (the line with @@) somehow do not
correspond to the reality of the patch below.

You can generally use quilt refresh to fix the broken patches (you might
want to refresh them all to be sure).

As a side note, you must also pay attention to the following points in
your quilt usage to guarantee compatibility with the new source package
format:
- all your patches must be applicable with the "-p1" option of patch
  (and you shouldn't use options in the series file to override this)
- the patches must be in debian/patches/ together with the "series" file
  (you can use QUILT_PATCHES=debian/patches if needed)
- you should not override QUILT_PC to change the location of quilt's
  internal directory (".pc" by default)
- your clean target must work even if the patches are already applied
- your build target must work with patches applied even if the clean
  target is supposed to unapply them (because dpkg-source -b might
  have applied them back)

Cheers,

[1] http://lists.debian.org/debian-devel-announce/2008/04/msg00004.html
[2] the upcoming dpkg-dev 1.14.20 is more tolerant with patches, you can
grab it here if you want to try with that version:
http://people.debian.org/~hertzog/packages/dpkg-dev_1.14.20_all.deb
-- 
Raphael Hertzog




--- End Message ---
--- Begin Message ---
Source: trac-bzr
Source-Version: 0.2+bzr31-6

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

trac-bzr_0.2+bzr31-6.diff.gz
  to pool/main/t/trac-bzr/trac-bzr_0.2+bzr31-6.diff.gz
trac-bzr_0.2+bzr31-6.dsc
  to pool/main/t/trac-bzr/trac-bzr_0.2+bzr31-6.dsc
trac-bzr_0.2+bzr31-6_all.deb
  to pool/main/t/trac-bzr/trac-bzr_0.2+bzr31-6_all.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.
Chris Lamb <[EMAIL PROTECTED]> (supplier of updated trac-bzr 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.8
Date: Tue, 13 May 2008 03:29:12 +0100
Source: trac-bzr
Binary: trac-bzr
Architecture: source all
Version: 0.2+bzr31-6
Distribution: unstable
Urgency: low
Maintainer: Debian Bazaar Maintainers <[EMAIL PROTECTED]>
Changed-By: Chris Lamb <[EMAIL PROTECTED]>
Description: 
 trac-bzr   - Bazaar version control (bzr) backend for Trac
Closes: 485335
Changes: 
 trac-bzr (0.2+bzr31-6) unstable; urgency=low
 .
   * Move package to pkg-bazaar group maintainership
     - Update "Maintainer" and "Uploaders" fields
     - Update Vcs-* to Vcs-Bzr
     - Add "DM-Upload-Allowed: yes"
   * Fix FTBFS when converted to new source format 3.0 (Closes: #485335)
   * debian/control:
     - Bump Standards-Version to 3.8.0
     - Add ${misc:Depends} to binary package
Checksums-Sha1: 
 a2455b782be17840281c29bddda770566686b83d 1283 trac-bzr_0.2+bzr31-6.dsc
 2d557793401ccacd04778ec20cf79b6313c2db0d 3288 trac-bzr_0.2+bzr31-6.diff.gz
 ea4810ccf7b7ff8d21ee0254c4428b849fc334a7 20134 trac-bzr_0.2+bzr31-6_all.deb
Checksums-Sha256: 
 e53cab15d0218d0e274a6a536f38e1aa5316d36686ccbf5eb6fb0e573fb84b80 1283 
trac-bzr_0.2+bzr31-6.dsc
 2e2e7804658574a50cb284fa001eae81b04589c7051599934b1c0f2a4c325bd7 3288 
trac-bzr_0.2+bzr31-6.diff.gz
 878c900240a4f546f30ef739d9f7bc08dc6cb45a5f5d082cd268646773804365 20134 
trac-bzr_0.2+bzr31-6_all.deb
Files: 
 ffd2accbeb643218bf0bb2deccc41f8f 1283 python optional trac-bzr_0.2+bzr31-6.dsc
 79a71526a847b8e4a51f7caebda47cbc 3288 python optional 
trac-bzr_0.2+bzr31-6.diff.gz
 abe4a8e05f2edc9879934f0635f89f96 20134 python optional 
trac-bzr_0.2+bzr31-6_all.deb

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

iEYEARECAAYFAkhMuIYACgkQ+C5cwEsrK57GYgCeLFAuxWsQiJyaaeqvtjQF02J+
MZwAnAqCRL9tes/1FJzOn4tA3VjXxkwP
=zWqn
-----END PGP SIGNATURE-----



--- End Message ---

Reply via email to