Your message dated Wed, 05 Oct 2011 22:17:21 +0000
with message-id <[email protected]>
and subject line Bug#643172: fixed in jta 2.6+dfsg-4
has caused the Debian Bug report #643172,
regarding jta: FTBFS: dpkg-buildpackage: error: dpkg-source -b jta-2.6+dfsg 
gave error exit status 2
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.)


-- 
643172: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643172
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: jta
Version: 2.6+dfsg-3
Severity: important
Tags: wheezy sid
User: [email protected]
Usertags: qa-ftbfs-20110923 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
>  fakeroot debian/rules clean
> test -x debian/rules
> dh_testroot
> rm -rf jar doc/source doc/api
> dh_clean 
> cd . && /usr/lib/jvm/default-java/bin/java -classpath 
> /usr/share/ant/lib/ant.jar:/usr/share/ant/lib/ant-launcher.jar:/usr/share/ant/lib/ant-launcher.jar:/usr/share/java/jdom1.jar:/usr/lib/jvm/default-java/lib/tools.jar
>   -Dant.home=/usr/share/ant org.apache.tools.ant.Main -Dpackage=jta 
> -Dversion=2.6+dfsg   -buildfile build.xml  clean
> Buildfile: /build/jta-c1iXdr/jta-2.6+dfsg/build.xml
> 
> init:
> 
> clean:
> 
> BUILD SUCCESSFUL
> Total time: 0 seconds
> rm -f debian/stamp-ant-build
>  dpkg-source -b jta-2.6+dfsg
> dpkg-source: info: using source format `3.0 (quilt)'
> dpkg-source: info: building jta using existing ./jta_2.6+dfsg.orig.tar.gz
> dpkg-source: info: local changes detected, the modified files are:
>  jta-2.6+dfsg/Makefile
>  jta-2.6+dfsg/de/mud/jta/Build.java
> dpkg-source: error: aborting due to unexpected upstream changes, see 
> /tmp/jta_2.6+dfsg-3.diff.BHjUCH
> dpkg-source: info: you can integrate the local changes with dpkg-source 
> --commit
> dpkg-buildpackage: error: dpkg-source -b jta-2.6+dfsg gave error exit status 2
> ────────────────────────────────────────────────────────────────────────────────
> Build finished at 20110924-0033

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2011/09/23/jta_2.6+dfsg-3_lsid64.buildlog

This error is due to recent dpkg changes "“dpkg-source -b” on a “2.0”
or “3.0 (quilt)” source package will fail if it detects upstream changes
which are not managed by a quilt patch." [0] 

[0] http://lists.debian.org/debian-devel-announce/2011/09/msg00001.html

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot.  Internet was not
accessible from the build systems.



--- End Message ---
--- Begin Message ---
Source: jta
Source-Version: 2.6+dfsg-4

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

jta-doc_2.6+dfsg-4_all.deb
  to main/j/jta/jta-doc_2.6+dfsg-4_all.deb
jta_2.6+dfsg-4.debian.tar.gz
  to main/j/jta/jta_2.6+dfsg-4.debian.tar.gz
jta_2.6+dfsg-4.dsc
  to main/j/jta/jta_2.6+dfsg-4.dsc
jta_2.6+dfsg-4_all.deb
  to main/j/jta/jta_2.6+dfsg-4_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.
Miguel Landaeta <[email protected]> (supplier of updated jta 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, 27 Sep 2011 19:32:24 -0430
Source: jta
Binary: jta jta-doc
Architecture: source all
Version: 2.6+dfsg-4
Distribution: unstable
Urgency: low
Maintainer: Debian Java Maintainers 
<[email protected]>
Changed-By: Miguel Landaeta <[email protected]>
Description: 
 jta        - Java telnet/ssh applet - documentation
 jta-doc    - Java telnet/ssh applet
Closes: 643172
Changes: 
 jta (2.6+dfsg-4) unstable; urgency=low
 .
   * Team upload.
   * Put changes to upstream code in a patch as is required since dpkg 1.16.1.
     (Closes: 643172).
   * Bump Standards-Version to 3.9.2. No changes were required.
   * Fix several lintian warnings.
Checksums-Sha1: 
 7d5a38a212baaedf1f3588ddeb230b75f242d5a4 1389 jta_2.6+dfsg-4.dsc
 2b7de12ff125ab5e5e595e1078249c5938ff9898 5549 jta_2.6+dfsg-4.debian.tar.gz
 16e0fd767b5b33874dc9fbc4a154ff86089639c6 247132 jta_2.6+dfsg-4_all.deb
 1c740c88fb54cbe443c52838c33adf124cd85623 177090 jta-doc_2.6+dfsg-4_all.deb
Checksums-Sha256: 
 409990c7af98d718ad93d020be3109c2307ebc77f38d506aadc652c14c7a374f 1389 
jta_2.6+dfsg-4.dsc
 df7fa7bc21f28c26698f281b2750dcdb93ef7d6c72d50a855696d6a61a52aba4 5549 
jta_2.6+dfsg-4.debian.tar.gz
 20678e84872f0cb15392ca969ab72f22118b698e090e00c3cf9585d7748d152d 247132 
jta_2.6+dfsg-4_all.deb
 ed40b5e9efdb82a346d9063c5050863f8826a95c4b5dbdeecf6d7fa0ca2baeef 177090 
jta-doc_2.6+dfsg-4_all.deb
Files: 
 0790deba95d743987c029d5570d2bf14 1389 net optional jta_2.6+dfsg-4.dsc
 1fa160ccda78eecf163f7ab2b93b409f 5549 net optional jta_2.6+dfsg-4.debian.tar.gz
 00b41c38e440a166a48fd61e7b697905 247132 net optional jta_2.6+dfsg-4_all.deb
 77471219b96fee73aebff637eb591813 177090 doc optional jta-doc_2.6+dfsg-4_all.deb

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

iEYEARECAAYFAk6M1aYACgkQfY3dicTPjsPk+gCfadT6FUNIsERTEGkv+zrqlQtS
AxUAniqnP5d+MG+wkjGbmU2XU5Bszms5
=YzXW
-----END PGP SIGNATURE-----



--- End Message ---

Reply via email to