Your message dated Mon, 25 Jun 2012 21:24:21 -0430
with message-id <20120626015421.ga1...@valeria.miguel.cc>
and subject line Not a FTBFS anymore
has caused the Debian Bug report #643191,
regarding libjamon-java: FTBFS: dpkg-buildpackage: error: dpkg-source -b 
libjamon-java-2.7 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 ow...@bugs.debian.org
immediately.)


-- 
643191: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643191
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libjamon-java
Version: 2.7-2
Severity: important
Tags: wheezy sid
User: debian...@lists.debian.org
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:
> make[1]: Entering directory `/build/libjamon-java-jJ609m/libjamon-java-2.7'
> make[1]: Nothing to be done for `reverse-config'.
> make[1]: Leaving directory `/build/libjamon-java-jJ609m/libjamon-java-2.7'
> if [ -d "." ]; then \
>         cd . && 
> QUILT_PATCHES=/build/libjamon-java-jJ609m/libjamon-java-2.7/debian/patches 
> quilt --quiltrc /dev/null pop -a -R || test $? = 2 ; \
>       fi
> Removing patch debian-changes-2.7-2
> Removing build.properties
> Removing build.xml
> 
> Removing patch api-fix.diff
> Restoring src/java/com/jamontomcat/JAMonTomcat4Valve.java
> Restoring src/java/com/jamonapi/proxy/JAMonDataSource.java
> 
> No patches applied
> rm -rf ./.pc
> rm -f debian/stamp-patch*
>  dpkg-source -b libjamon-java-2.7
> dpkg-source: info: using source format `3.0 (quilt)'
> dpkg-source: info: patches are not applied, applying them now
> dpkg-source: info: applying api-fix.diff
> dpkg-source: info: applying debian-changes-2.7-2
> dpkg-source: info: building libjamon-java using existing 
> ./libjamon-java_2.7.orig.tar.gz
> dpkg-source: info: local changes detected, the modified files are:
>  libjamon-java-2.7/build.properties
>  libjamon-java-2.7/build.xml
> dpkg-source: error: aborting due to unexpected upstream changes, see 
> /tmp/libjamon-java_2.7-2.diff.q8NR35
> dpkg-source: info: you can integrate the local changes with dpkg-source 
> --commit
> dpkg-buildpackage: error: dpkg-source -b libjamon-java-2.7 gave error exit 
> status 2
> ────────────────────────────────────────────────────────────────────────────────
> Build finished at 20110924-0038

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2011/09/23/libjamon-java_2.7-2_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 ---
dpkg-source doesn't fail anymore on package with a patch named debian-changes-*.

If you can reproduce this issue, feel free to reopen.

-- 
Miguel Landaeta, miguel at miguel.cc
secure email with PGP 0x6E608B637D8967E9 available at http://keyserver.pgp.com/
"Faith means not wanting to know what is true." -- Nietzsche

Attachment: signature.asc
Description: Digital signature


--- End Message ---
__
This is the maintainer address of Debian's Java team
<http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers>. 
Please use
debian-j...@lists.debian.org for discussions and questions.

Reply via email to