Bug#834744: marked as done (xmlgraphics-commons: FTBFS (missing build-depends on gnupg))

2016-09-07 Thread Debian Bug Tracking System 
Your message dated Thu, 08 Sep 2016 04:32:35 +
with message-id 
and subject line Bug#834744: fixed in xmlgraphics-commons 2.1-2
has caused the Debian Bug report #834744,
regarding xmlgraphics-commons: FTBFS (missing build-depends on gnupg)
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.)


-- 
834744: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834744
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:xmlgraphics-commons
Version: 2.1-1
Severity: serious
Tags: patch

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
BUILD FAILED
/<>/build.xml:620: The following error occurred while executing 
this line:
/<>/build.xml:591: Execute failed: java.io.IOException: Cannot run 
program "gpg" (in directory "/<>"): error=2, No such file or 
directory


The gnupg package is not essential. Therefore, whenever a package
requires it for building there should be a build-dependency on it.

Trivial (but untested) patch below.

Thanks.

--- a/debian/control
+++ b/debian/control
@@ -8,6 +8,7 @@ Build-Depends: debhelper (>= 9), javahelper
 Build-Depends-Indep: ant-optional,
  default-jdk,
  default-jdk-doc,
+ gnupg,
  junit4,
  libcommons-io-java (>= 1.3.1),
  libcommons-logging-java,
--- End Message ---
--- Begin Message ---
Source: xmlgraphics-commons
Source-Version: 2.1-2

We believe that the bug you reported is fixed in the latest version of
xmlgraphics-commons, which is due to be installed in the Debian FTP archive.

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 834...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated xmlgraphics-commons 
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 ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 08 Sep 2016 04:31:18 +0200
Source: xmlgraphics-commons
Binary: libxmlgraphics-commons-java libxmlgraphics-commons-java-doc
Architecture: source
Version: 2.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Markus Koschany 
Description:
 libxmlgraphics-commons-java - Reusable components used by Batik and FOP
 libxmlgraphics-commons-java-doc - Reusable components used by Batik and FOP 
(documentation)
Closes: 834744
Changes:
 xmlgraphics-commons (2.1-2) unstable; urgency=medium
 .
   * Team upload.
   * Add gnupg to Build-Depends. (Closes: #834744)
   * Declare compliance with Debian Policy 3.9.8.
   * Vcs-Browser: Use https.
Checksums-Sha1:
 2eb650caf7e573f976ce48ece74c3c838fb71544 2520 xmlgraphics-commons_2.1-2.dsc
 7697479fb6f2c08b76af2725c2f8d5ffab7b7da0 9172 
xmlgraphics-commons_2.1-2.debian.tar.xz
Checksums-Sha256:
 3806c4963f51f6235e8387df4e7ff5e3bad13265f0f34f90844bf3411ffd5de1 2520 
xmlgraphics-commons_2.1-2.dsc
 8926c4d5d7294301a6b98713f8cb10315e70b5c92242eb2776c8989b3fe6b6ba 9172 
xmlgraphics-commons_2.1-2.debian.tar.xz
Files:
 4fe30b56155cff8ab380d45cd9ba27cc 2520 java optional 
xmlgraphics-commons_2.1-2.dsc
 4202406c535574878627080ab98a6777 9172 java optional 
xmlgraphics-commons_2.1-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKMBAEBCgB2BQJX0M+rXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRBQ0YzRDA4OEVGMzJFREVGNkExQTgzNUZE
OUFEMTRCOTUxM0I1MUU0DxxhcG9AZGViaWFuLm9yZwAKCRDZrRS5UTtR5IzMEADL
5GII5wLn/D0B5pID4JK6Hw4FiM016Aek06kjrxCIv6LwH1SxzY8poIVguFOXpe+l
Lg38f3adzLPJf8E6V2fr7uPcaj97wcdb1s2j2ZilhwATbC5PVE1i62OSKE9RHl+C
dtTFhLMR9vvVdsS0my40Qru7jBbsBARo4Yk6z3QA1zB1Yj/dkFjjlTldJgoZNtdQ
Pqn09X+IIwxGq8lQQQefWtelnfr3zQ7RZ9ryrS/Or4pXuCbzK1ohfx7H0eqcAoDN
/3bmTzibGH9F3pLFgof/g042kJ1Ftz8tzQcJsFVP2Q7iDs0wO46JRAlOV308WU8b
QYb9FAbq2z8X1KuHDE9zJkMcg65Au/U7IBdHa0GPO7HXxkqJ5kAkpKq8N0XNwHLR
6u/Hp7kiqj9A+Num69oWA95lKBcoNHax1XqCSawXbpO13BtmKGD7ncFP9sIzJWSE

xmlgraphics-commons_2.1-2_source.changes ACCEPTED into unstable

2016-09-07 Thread Debian FTP Masters 


Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 08 Sep 2016 04:31:18 +0200
Source: xmlgraphics-commons
Binary: libxmlgraphics-commons-java libxmlgraphics-commons-java-doc
Architecture: source
Version: 2.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Markus Koschany 
Description:
 libxmlgraphics-commons-java - Reusable components used by Batik and FOP
 libxmlgraphics-commons-java-doc - Reusable components used by Batik and FOP 
(documentation)
Closes: 834744
Changes:
 xmlgraphics-commons (2.1-2) unstable; urgency=medium
 .
   * Team upload.
   * Add gnupg to Build-Depends. (Closes: #834744)
   * Declare compliance with Debian Policy 3.9.8.
   * Vcs-Browser: Use https.
Checksums-Sha1:
 2eb650caf7e573f976ce48ece74c3c838fb71544 2520 xmlgraphics-commons_2.1-2.dsc
 7697479fb6f2c08b76af2725c2f8d5ffab7b7da0 9172 
xmlgraphics-commons_2.1-2.debian.tar.xz
Checksums-Sha256:
 3806c4963f51f6235e8387df4e7ff5e3bad13265f0f34f90844bf3411ffd5de1 2520 
xmlgraphics-commons_2.1-2.dsc
 8926c4d5d7294301a6b98713f8cb10315e70b5c92242eb2776c8989b3fe6b6ba 9172 
xmlgraphics-commons_2.1-2.debian.tar.xz
Files:
 4fe30b56155cff8ab380d45cd9ba27cc 2520 java optional 
xmlgraphics-commons_2.1-2.dsc
 4202406c535574878627080ab98a6777 9172 java optional 
xmlgraphics-commons_2.1-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKMBAEBCgB2BQJX0M+rXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRBQ0YzRDA4OEVGMzJFREVGNkExQTgzNUZE
OUFEMTRCOTUxM0I1MUU0DxxhcG9AZGViaWFuLm9yZwAKCRDZrRS5UTtR5IzMEADL
5GII5wLn/D0B5pID4JK6Hw4FiM016Aek06kjrxCIv6LwH1SxzY8poIVguFOXpe+l
Lg38f3adzLPJf8E6V2fr7uPcaj97wcdb1s2j2ZilhwATbC5PVE1i62OSKE9RHl+C
dtTFhLMR9vvVdsS0my40Qru7jBbsBARo4Yk6z3QA1zB1Yj/dkFjjlTldJgoZNtdQ
Pqn09X+IIwxGq8lQQQefWtelnfr3zQ7RZ9ryrS/Or4pXuCbzK1ohfx7H0eqcAoDN
/3bmTzibGH9F3pLFgof/g042kJ1Ftz8tzQcJsFVP2Q7iDs0wO46JRAlOV308WU8b
QYb9FAbq2z8X1KuHDE9zJkMcg65Au/U7IBdHa0GPO7HXxkqJ5kAkpKq8N0XNwHLR
6u/Hp7kiqj9A+Num69oWA95lKBcoNHax1XqCSawXbpO13BtmKGD7ncFP9sIzJWSE
xtgFZliQQSIo5uY94hGxT83+X8ydIhC4Emc7Yw6GrYuwQdJvJZUPJUM5XgAj43Qx
qxkDxRsb7X26frHj8dREIdfgmQRL4XZE3FK1NzeNpUxfDZm2p3OjGhiXRQoX5lQC
god3getsuZ4aTaGwdEChRLxvFRn+ifhbjHHdSiKCyEfQYOHt2oGUnpOThQyOrHxa
FW6H/l8RaSMvR9H/JkDt+fK4Y1N8Rv8bUvv2+X9L+w==
=BLj9
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

reproducible.debian.net status changes for maven-bundle-plugin

2016-09-07 Thread Reproducible builds folks 
2016-09-07 03:06 
https://tests.reproducible-builds.org/debian/unstable/amd64/maven-bundle-plugin 
changed from reproducible -> unreproducible

__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

reproducible.debian.net status changes for maven-enforcer

2016-09-07 Thread Reproducible builds folks 
2016-09-06 02:23 
https://tests.reproducible-builds.org/debian/unstable/amd64/maven-enforcer 
changed from reproducible -> unreproducible

__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

reproducible.debian.net status changes for exec-maven-plugin

2016-09-07 Thread Reproducible builds folks 
2016-09-07 02:00 
https://tests.reproducible-builds.org/debian/unstable/amd64/exec-maven-plugin 
changed from reproducible -> unreproducible

__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

reproducible.debian.net status changes for msv

2016-09-07 Thread Reproducible builds folks 
2016-09-06 02:59 
https://tests.reproducible-builds.org/debian/unstable/amd64/msv changed from 
reproducible -> unreproducible

__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

reproducible.debian.net status changes for commons-math3

2016-09-07 Thread Reproducible builds folks 
2016-09-07 00:39 
https://tests.reproducible-builds.org/debian/unstable/amd64/commons-math3 
changed from reproducible -> unreproducible

__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

reproducible.debian.net status changes for maven-plugin-testing

2016-09-07 Thread Reproducible builds folks 
2016-09-06 02:34 
https://tests.reproducible-builds.org/debian/unstable/amd64/maven-plugin-testing
 changed from reproducible -> unreproducible

__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

Processing of xmlgraphics-commons_2.1-2_source.changes

2016-09-07 Thread Debian FTP Masters 
xmlgraphics-commons_2.1-2_source.changes uploaded successfully to localhost
along with the files:
  xmlgraphics-commons_2.1-2.dsc
  xmlgraphics-commons_2.1-2.debian.tar.xz

Greetings,

Your Debian queue daemon (running on host franck.debian.org)

__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

Processing of xmlgraphics-commons_2.1-2_source.changes

2016-09-07 Thread Debian FTP Masters 
xmlgraphics-commons_2.1-2_source.changes uploaded successfully to 
ftp-master.debian.org
along with the files:
  xmlgraphics-commons_2.1-2.dsc
  xmlgraphics-commons_2.1-2.debian.tar.xz

Greetings,

Your Debian queue daemon (running on host coccia.debian.org)

__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

reproducible.debian.net status changes for access-modifier-checker

2016-09-07 Thread Reproducible builds folks 
2016-09-06 19:10 
https://tests.reproducible-builds.org/debian/unstable/amd64/access-modifier-checker
 changed from reproducible -> unreproducible

__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

reproducible.debian.net status changes for maven-site-plugin

2016-09-07 Thread Reproducible builds folks 
2016-09-06 02:23 
https://tests.reproducible-builds.org/debian/unstable/amd64/maven-site-plugin 
changed from reproducible -> unreproducible

__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

reproducible.debian.net status changes for jnr-unixsocket

2016-09-07 Thread Reproducible builds folks 
2016-09-07 06:27 
https://tests.reproducible-builds.org/debian/unstable/amd64/jnr-unixsocket 
changed from reproducible -> unreproducible

__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

reproducible.debian.net status changes for plexus-compiler-1.0

2016-09-07 Thread Reproducible builds folks 
2016-09-07 06:26 
https://tests.reproducible-builds.org/debian/unstable/amd64/plexus-compiler-1.0 
changed from reproducible -> unreproducible

__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

reproducible.debian.net status changes for plexus-containers1.5

2016-09-07 Thread Reproducible builds folks 
2016-09-07 03:48 
https://tests.reproducible-builds.org/debian/unstable/amd64/plexus-containers1.5
 changed from reproducible -> unreproducible

__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

reproducible.debian.net status changes for maven-plugin-tools

2016-09-07 Thread Reproducible builds folks 
2016-09-06 02:23 
https://tests.reproducible-builds.org/debian/unstable/amd64/maven-plugin-tools 
changed from reproducible -> unreproducible

__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

reproducible.debian.net status changes for activemq-activeio

2016-09-07 Thread Reproducible builds folks 
2016-09-06 19:30 
https://tests.reproducible-builds.org/debian/unstable/amd64/activemq-activeio 
changed from reproducible -> unreproducible

__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

reproducible.debian.net status changes for commons-csv

2016-09-07 Thread Reproducible builds folks 
2016-09-07 00:29 
https://tests.reproducible-builds.org/debian/unstable/amd64/commons-csv changed 
from reproducible -> unreproducible

__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

reproducible.debian.net status changes for nailgun

2016-09-07 Thread Reproducible builds folks 
2016-09-06 02:56 
https://tests.reproducible-builds.org/debian/unstable/amd64/nailgun changed 
from reproducible -> unreproducible

__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

reproducible.debian.net status changes for jnr-enxio

2016-09-07 Thread Reproducible builds folks 
2016-09-07 06:27 
https://tests.reproducible-builds.org/debian/unstable/amd64/jnr-enxio changed 
from reproducible -> unreproducible

__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

reproducible.debian.net status changes for jboss-logging

2016-09-07 Thread Reproducible builds folks 
2016-09-06 09:47 
https://tests.reproducible-builds.org/debian/unstable/amd64/jboss-logging 
changed from reproducible -> unreproducible

__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

reproducible.debian.net status changes for commons-configuration

2016-09-07 Thread Reproducible builds folks 
2016-09-07 01:06 
https://tests.reproducible-builds.org/debian/unstable/amd64/commons-configuration
 changed from reproducible -> unreproducible

__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

reproducible.debian.net status changes for commons-io

2016-09-07 Thread Reproducible builds folks 
2016-09-07 00:36 
https://tests.reproducible-builds.org/debian/unstable/amd64/commons-io changed 
from FTBFS -> unreproducible

__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

reproducible.debian.net status changes for fest-test

2016-09-07 Thread Reproducible builds folks 
2016-09-07 23:58 
https://tests.reproducible-builds.org/debian/unstable/amd64/fest-test changed 
from reproducible -> unreproducible

__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

reproducible.debian.net status changes for sezpoz

2016-09-07 Thread Reproducible builds folks 
2016-09-07 04:28 
https://tests.reproducible-builds.org/debian/unstable/amd64/sezpoz changed from 
reproducible -> unreproducible

__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

reproducible.debian.net status changes for felix-utils

2016-09-07 Thread Reproducible builds folks 
2016-09-07 23:57 
https://tests.reproducible-builds.org/debian/unstable/amd64/felix-utils changed 
from reproducible -> unreproducible

__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

reproducible.debian.net status changes for libsequence-library-java

2016-09-07 Thread Reproducible builds folks 
2016-09-06 01:23 
https://tests.reproducible-builds.org/debian/unstable/amd64/libsequence-library-java
 changed from reproducible -> unreproducible

__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

reproducible.debian.net status changes for args4j

2016-09-07 Thread Reproducible builds folks 
2016-09-07 21:21 
https://tests.reproducible-builds.org/debian/unstable/amd64/args4j changed from 
reproducible -> unreproducible

__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

reproducible.debian.net status changes for maven-replacer-plugin

2016-09-07 Thread Reproducible builds folks 
2016-09-07 03:06 
https://tests.reproducible-builds.org/debian/unstable/amd64/maven-replacer-plugin
 changed from reproducible -> unreproducible

__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

reproducible.debian.net status changes for libxstream-java

2016-09-07 Thread Reproducible builds folks 
2016-09-06 02:01 
https://tests.reproducible-builds.org/debian/unstable/amd64/libxstream-java 
changed from reproducible -> unreproducible

__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

Bug#834682: mina2: FTBFS in testing (failing tests)

2016-09-07 Thread Santiago Vila 
On Wed, 7 Sep 2016, Markus Koschany wrote:

> I am attaching two build logs (cowbuilder and sbuild) that show no
> issues at all. The build succeeds.

Thanks a lot for trying to reproduce this.

There are still a lot of differences, we should better remove them all,
until our building environments are the same. Then it should fail
for you too (hopefully).

Would you please add this to the mix?:

* Use a stretch chroot (as reported).

* Build only arch-independent packages (as reported).
  This is the equivalent to "dpkg-buildpackage -A".
  In sbuild it's done with options "--arch-all --no-arch-any".

* The chroot should be as small as possible. Well, I don't do exactly
  that because most packages build-depend on debhelper, and I want
  to save disk I/O so I have debhelper by default, but on the other side
  I don't have gnupg installed.
  
  To simplify: Would you please install the packages in
  package-list.txt (attached) and only those?
  
[ This is of course only the starting point, sbuild should then
  automatically download and install the required packages ].

* I'm also using --resolve-alternatives option of sbuild. Don't know if
  it's relevant but we should try to minimize differences. There is at
  least one package that FTBFS if I didn't use this option, which is
  otherwise the default (AFAIK) in the official buildds.

* Build with only one CPU. This is achieved by putting this in .sbuildrc:

$ENV{'DEB_BUILD_OPTIONS'} = 'parallel=1';

* Finally, I'm building on machines with not a lot of memory, because
  monitoring /proc/meminfo tells me that I don't need more for this
  particular package (but maybe I'm wrong).
  
  Please try on a virtual machine having only 1GB RAM and 1 GB swap.


If you do all this, the probability that you will reproduce the bug
may only increase (but of course it may also continue to be zero).
In either case, we should try.

Thanks.adduser
apt
autoconf
automake
autopoint
autotools-dev
base-files
base-passwd
bash
binutils
bsdmainutils
bsdutils
build-essential
bzip2
coreutils
cpp
cpp-6
dash
debconf
debhelper
debian-archive-keyring
debianutils
dh-autoreconf
dh-strip-nondeterminism
diffutils
dmsetup
dpkg
dpkg-dev
e2fslibs
e2fsprogs
eatmydata
fakeroot
file
findutils
g++
g++-6
gcc
gcc-5-base
gcc-6
gcc-6-base
gettext
gettext-base
gpgv
grep
groff-base
gzip
hostname
init-system-helpers
initscripts
insserv
intltool-debian
less
libacl1
libapt-pkg5.0
libarchive-zip-perl
libasan3
libatomic1
libattr1
libaudit-common
libaudit1
libblkid1
libbsd0
libbz2-1.0
libc-bin
libc-dev-bin
libc-l10n
libc6
libc6-dev
libcap-ng0
libcc1-0
libcilkrts5
libcomerr2
libcroco3
libdb5.3
libdebconfclient0
libdevmapper1.02.1
libdpkg-perl
libeatmydata1
libfakeroot
libfdisk1
libffi6
libfile-stripnondeterminism-perl
libgcc-6-dev
libgcc1
libgcrypt20
libgdbm3
libglib2.0-0
libgmp10
libgomp1
libgpg-error0
libicu57
libisl15
libitm1
liblsan0
liblz4-1
liblzma5
libmagic-mgc
libmagic1
libmount1
libmpc3
libmpfr4
libmpx2
libncurses5
libncursesw5
libpam-modules
libpam-modules-bin
libpam-runtime
libpam0g
libpcre3
libperl5.22
libpipeline1
libquadmath0
libselinux1
libsemanage-common
libsemanage1
libsepol1
libsigsegv2
libsmartcols1
libss2
libstdc++-6-dev
libstdc++6
libsystemd0
libtimedate-perl
libtinfo5
libtool
libtsan0
libubsan0
libudev1
libunistring0
libustr-1.0-1
libuuid1
libxml2
linux-libc-dev
locales
login
lsb-base
m4
make
man-db
mawk
mount
multiarch-support
nano
ncurses-base
ncurses-bin
passwd
patch
perl
perl-base
perl-modules-5.22
po-debconf
sed
sensible-utils
startpar
sysv-rc
sysvinit-utils
tar
tzdata
util-linux
xz-utils
zlib1g
__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

Bug#834744: xmlgraphics-commons: FTBFS (missing build-depends on gnupg)

2016-09-07 Thread Lucas Nussbaum 
severity 834744 serious
thanks

On 07/09/16 at 14:17 +0100, Santiago Vila wrote:
> I suggest to raise the severity now

Yes.

Lucas

__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

Processed: Re: Bug#834744: xmlgraphics-commons: FTBFS (missing build-depends on gnupg)

2016-09-07 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> severity 834744 serious
Bug #834744 [src:xmlgraphics-commons] xmlgraphics-commons: FTBFS (missing 
build-depends on gnupg)
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
834744: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834744
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

Bug#837022: wagon2: FTBFS: dh_auto_test failed

2016-09-07 Thread Lucas Nussbaum 
Source: wagon2
Version: 2.10-4
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160906 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> mkdir -p /<>/wagon-providers/wagon-scm/target/test-classes/
> svnadmin create 
> /<>/wagon-providers/wagon-scm/target/test-classes/test-repo-svn
> dh_auto_build
>   /usr/lib/jvm/default-java/bin/java -noverify -cp 
> /usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
>  -Dmaven.home=/usr/share/maven 
> -Dmaven.multiModuleProjectDirectory=/<> 
> -Dclassworlds.conf=/etc/maven/m2-debian.conf 
> -Dproperties.file.manual=/<>/debian/maven.properties 
> org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
> -Dmaven.repo.local=/<>/debian/maven-repo package -DskipTests 
> -Dnotimestamp=true -Dlocale=en_US
> [INFO] Scanning for projects...
> [WARNING] 
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.maven.wagon:wagon-provider-api:jar:2.10
> [WARNING] 'build.plugins.plugin.version' for 
> org.codehaus.plexus:plexus-component-metadata is missing. @ 
> org.apache.maven.wagon:wagon:2.10, /<>/pom.xml, line 378, column 
> 12
> [WARNING] 
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.maven.wagon:wagon-file:jar:2.10
> [WARNING] 'build.plugins.plugin.version' for 
> org.codehaus.plexus:plexus-component-metadata is missing. @ 
> org.apache.maven.wagon:wagon:2.10, /<>/pom.xml, line 378, column 
> 12
> [WARNING] 
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.maven.wagon:wagon-ftp:jar:2.10
> [WARNING] 'build.plugins.plugin.version' for 
> org.codehaus.plexus:plexus-component-metadata is missing. @ 
> org.apache.maven.wagon:wagon:2.10, /<>/pom.xml, line 378, column 
> 12
> [WARNING] 
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.maven.wagon:wagon-http:jar:2.10
> [WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but 
> found duplicate declaration of plugin 
> org.apache.maven.plugins:maven-surefire-plugin @ line 143, column 12
> [WARNING] 'build.plugins.plugin.version' for 
> org.apache.maven.plugins:maven-surefire-plugin is missing. @ line 143, column 
> 12
> [WARNING] 'build.plugins.plugin.version' for 
> org.codehaus.plexus:plexus-component-metadata is missing. @ 
> org.apache.maven.wagon:wagon:2.10, /<>/pom.xml, line 378, column 
> 12
> [WARNING] 
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.maven.wagon:wagon-http-shared:jar:2.10
> [WARNING] 'build.plugins.plugin.version' for 
> org.codehaus.plexus:plexus-component-metadata is missing. @ 
> org.apache.maven.wagon:wagon:2.10, /<>/pom.xml, line 378, column 
> 12
> [WARNING] 
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.maven.wagon:wagon-http-lightweight:jar:2.10
> [WARNING] 'build.plugins.plugin.version' for 
> org.apache.maven.plugins:maven-surefire-plugin is missing. @ line 59, column 
> 12
> [WARNING] 'build.plugins.plugin.version' for 
> org.codehaus.plexus:plexus-component-metadata is missing. @ 
> org.apache.maven.wagon:wagon:2.10, /<>/pom.xml, line 378, column 
> 12
> [WARNING] 
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.maven.wagon:wagon-providers:pom:2.10
> [WARNING] 'build.plugins.plugin.version' for 
> org.codehaus.plexus:plexus-component-metadata is missing. @ 
> org.apache.maven.wagon:wagon:2.10, /<>/pom.xml, line 378, column 
> 12
> [WARNING] 
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.maven.wagon:wagon-provider-test:jar:2.10
> [WARNING] 'build.plugins.plugin.version' for 
> org.codehaus.plexus:plexus-component-metadata is missing. @ 
> org.apache.maven.wagon:wagon:2.10, /<>/pom.xml, line 378, column 
> 12
> [WARNING] 
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.maven.wagon:wagon-tck-http:jar:2.10
> [WARNING] 'build.plugins.plugin.version' for 
> org.codehaus.plexus:plexus-component-metadata is missing. @ 
> org.apache.maven.wagon:wagon:2.10, /<>/pom.xml, line 378, column 
> 12
> [WARNING] 
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.maven.wagon:wagon-tcks:pom:2.10
> [WARNING] 'build.plugins.plugin.version' for 
> org.codehaus.plexus:plexus-component-metadata is missing. @ 
> org.apache.maven.wagon:wagon:2.10, /<>/pom.xml, line 378, column 
> 12
> [WARNING] 
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.maven.wagon:wagon:pom:2.10
> [WARNING] 'build.plugins.plugin.version' for 
>

Bug#837021: openjfx: FTBFS: PosixPlatform.cpp:235:10: error: 'wait' was not declared in this scope

2016-09-07 Thread Lucas Nussbaum 
Source: openjfx
Version: 8u102-b14-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160906 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> g++ -Xlinker -s -static-libstdc++ -Wl,-O1 -shared -o libDumpRenderTreeJava.so 
> Release/obj/GCController.o Release/obj/TestRunner.o Release/obj/WorkQueue.o 
> Release/obj/DumpRenderTree.o Release/obj/GCControllerJava.o 
> Release/obj/JavaEnv.o Release/obj/TestRunnerJava.o 
> Release/obj/WorkQueueItemJava.o Release/obj/EventSender.o  
> -L../../Release/lib -lpthread -ljfxwebkit  
> mv -f libDumpRenderTreeJava.so ../../Release/lib/ 
> make[3]: Leaving directory 
> '/<>/modules/web/build/linux/Tools/DumpRenderTree'
> make[2]: Leaving directory '/<>/modules/web/build/linux/Release'
> 
> 
>  WebKit is now built (1h:03m:38s). 
>  To run FXLauncher with this newly-built code, use the
>  "Tools/Scripts/run-launcher" script.
> 
> :web:compileNativeLinux (Thread[main,5,main]) completed. Took 1 hrs 3 mins 
> 38.269 secs.
> :web:compileGeneratedLinux (Thread[main,5,main]) started.
> :web:compileGeneratedLinux
> Executing task ':web:compileGeneratedLinux' (up-to-date check took 0.075 
> secs) due to:
>   No history is available.
> All input files are considered out-of-date for incremental task 
> ':web:compileGeneratedLinux'.
> Compiling with Java command line compiler 
> '/usr/lib/jvm/java-8-openjdk-amd64/bin/javac'.
> Starting process 'command '/usr/lib/jvm/java-8-openjdk-amd64/bin/javac''. 
> Working directory: /<>/modules/web Command: 
> /usr/lib/jvm/java-8-openjdk-amd64/bin/javac 
> @/<>/modules/web/build/tmp/compileGeneratedLinux/java-compiler-args.txt
> Successfully started process 'command 
> '/usr/lib/jvm/java-8-openjdk-amd64/bin/javac''
> Note: Some input files use unchecked or unsafe operations.
> Note: Recompile with -Xlint:unchecked for details.
> :web:compileGeneratedLinux (Thread[main,5,main]) completed. Took 3.056 secs.
> :web:compileGenerated (Thread[main,5,main]) started.
> :web:compileGenerated
> Skipping task ':web:compileGenerated' as it has no actions.
> :web:compileGenerated (Thread[main,5,main]) completed. Took 0.0 secs.
> :web:drtJar (Thread[main,5,main]) started.
> :web:drtJar
> Executing task ':web:drtJar' (up-to-date check took 0.007 secs) due to:
>   No history is available.
> :web:drtJar (Thread[main,5,main]) completed. Took 0.028 secs.
> :web:jar (Thread[main,5,main]) started.
> :web:jar
> Executing task ':web:jar' (up-to-date check took 0.02 secs) due to:
>   No history is available.
> :web:jar (Thread[main,5,main]) completed. Took 0.166 secs.
> :builders:compileJava (Thread[main,5,main]) started.
> :builders:compileJava
> Executing task ':builders:compileJava' (up-to-date check took 0.046 secs) due 
> to:
>   No history is available.
> All input files are considered out-of-date for incremental task 
> ':builders:compileJava'.
> Compiling with Java command line compiler 
> '/usr/lib/jvm/java-8-openjdk-amd64/bin/javac'.
> Starting process 'command '/usr/lib/jvm/java-8-openjdk-amd64/bin/javac''. 
> Working directory: /<>/modules/builders Command: 
> /usr/lib/jvm/java-8-openjdk-amd64/bin/javac 
> @/<>/modules/builders/build/tmp/compileJava/java-compiler-args.txt
> Successfully started process 'command 
> '/usr/lib/jvm/java-8-openjdk-amd64/bin/javac''
> Note: 
> /<>/modules/builders/src/main/java/javafx/scene/web/WebViewBuilder.java
>  uses or overrides a deprecated API.
> Note: Recompile with -Xlint:deprecation for details.
> Note: Some input files use unchecked or unsafe operations.
> Note: Recompile with -Xlint:unchecked for details.
> :builders:compileJava (Thread[main,5,main]) completed. Took 3.794 secs.
> :builders:processResources (Thread[main,5,main]) started.
> :builders:processResources
> file or directory '/<>/modules/builders/src/main/resources', not 
> found
> Skipping task ':builders:processResources' as it has no source files.
> :builders:processResources UP-TO-DATE
> :builders:processResources (Thread[main,5,main]) completed. Took 0.001 secs.
> :builders:classes (Thread[main,5,main]) started.
> :builders:classes
> Skipping task ':builders:classes' as it has no actions.
> :builders:classes (Thread[main,5,main]) completed. Took 0.0 secs.
> :builders:jar (Thread[main,5,main]) started.
> :builders:jar
> Executing task ':builders:jar' (up-to-date check took 0.003 secs) due to:
>   No history is available.
> :builders:jar (Thread[main,5,main]) completed. Took 0.053 secs.
> :builders:assemble (Thread[main,5,main]) started.
> :builders:assemble
> Skipping task ':builders:assemble' as it has no actions.
> :builders:assemble (Thread[main,5,main]) completed. Took 0.0 secs.
> :controls:assemble (Thread[main,5,main]) started.
> :controls:assemble
> Skipping task

jsch 0.1.54-1 MIGRATED to testing

2016-09-07 Thread Debian testing watch 
FYI: The status of the jsch source package
in Debian's testing distribution has changed.

  Previous version: 0.1.53-1
  Current version:  0.1.54-1

-- 
This email is automatically generated once a day.  As the installation of
new packages into testing happens multiple times a day you will receive
later changes on the next day.
See https://release.debian.org/testing-watch/ for more information.

__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

Bug#834682: mina2: FTBFS in testing (failing tests)

2016-09-07 Thread Markus Koschany 
On 07.09.2016 14:33, Santiago Vila wrote:
> retitle 834682 mina2: FTBFS in testing (failing tests)
> thanks
> 
> On Fri, 26 Aug 2016, Markus Koschany wrote:
> 
>> I have rebuilt mina2 ten times in a row now but I can't reproduce the
>> failing test or the build failure in general.
> 
> Congratulations. I attach five build logs in five different autobuilders.
> 
> Apparently, it fails for me all the time.
> 
> [ So, instead of you asking me for a way to reproduce it, perhaps I
>   should be asking you for a way *not* to reproduce it... ]
> 
>> It appears this issue is not random
> 
> After my last five builds yesterday, that's what it seems, yes.
> Now it fails all the time, so it's not random anymore.
> 
> I'm changing the subject accordingly.

I am attaching two build logs (cowbuilder and sbuild) that show no
issues at all. The build succeeds.

I have fixed previous packages with random failing tests because I think
those tests are not helpful for us in general but I won't disable them
if I can't reproduce the randomness of the issue myself. I always try to
reproduce bug reports but I am getting more and more frustrated by the
way how you interact with us. It is just annoying and disrespectful.



mina2_2.0.13-1_amd64.build.gz
Description: application/gzip


mina2_2.0.13-1_amd64-2016-09-07T12:40:38Z.build.gz
Description: application/gzip


signature.asc
Description: OpenPGP digital signature
__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

Bug#834744: xmlgraphics-commons: FTBFS (missing build-depends on gnupg)

2016-09-07 Thread Santiago Vila 
On Wed, Sep 07, 2016 at 02:05:45PM +0200, Markus Koschany wrote:
> I have just filed
> 
> http://bugs.debian.org/836940
> 
> against cowbuilder and sbuild and asked both maintainers for a
> clarification. Apparently apt moved the dependency on gnupg from Depends
> to Recommends in version 1.3~exp1 and together with the recent gnupg2
> transition, this caused a behavioral change in sbuild.

IMHO, the bug is a waste of time, and I can easily imagine what sbuild
maintainer will probably tell you: If it's not required to have gnupg
inside the chroot, then there is no point in requiring it to be inside
the chroot.

> >   11) Drop requirement for gpg inside the chroot as external archive keys 
> > are
> >   now processed without gpg and signing of the internal repository is
> >   entirely optional with helpful warning and error messages in case
> >   signing failed.
> > 
> > 
> > Please note that this bug is not just "xmlgraphics-commons FTBFS".
> > 
> > This bug is "xmlgraphics-commons FTBFS if gnupg is not in chroot".
> 
> Actually this is not a specific issue in xmlgraphics-commons but affects
> all packages that relied on gnupg being installed by default.

There are not so many of them. These are the ones I remember:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834600
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834744
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835098

including this one. So "All packages" = 3 so far. This is after building
all 15000 source packages in stretch that generate "Arch: all" binary packages.

> This bug only surfaced three weeks ago. We could always rely on gnupg
> being installed by default.

No, actually you could not rely on gnupg being installed by default,
because gnupg was not essential and it was never was.

This bug was "hidden", so to speak, but it has always been a bug,
it's just now that we discovered it.

The "theory" has not changed: If you need a package during build, you
have to put it in build-depends. This is clearly written in policy.

If gnupg is installed by default and there is not a build-depends,
nobody will notice, but it's still a bug.

> This cannot be achieved by filing RC bugs against numerous affected
> packages.

Yes, it can, because they are RC bugs, they have always been, and
there are not so many packages affected.

I can count them with the fingers in my two hands, and I don't even
need to announce it as a mass bug filing.

> In my opinion this is inefficient and just increases the
> workload of contributors.

You are now worried by workload of contributors? How ironic.
My workload is increased every time I have to explain obvious
and well established things to people who ignore Debian Policy
regarding the set of build essential packages.

If you are really worried about workload of contributors, I suggest
you follow Debian Policy and raise this to serious, where it belongs.

> Debian Policy is not a document to force
> maintainers into implementing something, it rather reflects common best
> practices in this distribution.

I don't want to force anything. You don't have to fix this bug. Do
nothing and let the autoremoval procedure happen if you wish, but this
bug is serious because, as you say, that has been common best practice
for ages every time we have discovered a missing build-depends.

> By the way marking the bug as unreproducible just means that
> feedback from someone else is appreciated.

We already have "help" for that. When we know exactly and precisely
how to reproduce something (in this case, building without gnupg in
the chroot), we don't use unreproducible.

> > Before I take this to the Technical Committee, do you want to propose
> > a summary of the disagreement? This is not required but it's
> > recommended here in point 2:
> > 
> > https://www.debian.org/devel/tech-ctte
> > 
> > Thanks.
> 
> I suggest to wait until both cowbuilder and sbuild maintainers responded
> to #836940.

I suggest to raise the severity now, as I have already wasted too much
time explaining obvious things in this report, and don't like the idea
of wasting even more time.

Thanks.

__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

Processed: Re: mina2: FTBFS in testing (failing tests)

2016-09-07 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> retitle 834682 mina2: FTBFS in testing (failing tests)
Bug #834682 [src:mina2] mina2: FTBFS too much often (failing tests)
Changed Bug title to 'mina2: FTBFS in testing (failing tests)' from 'mina2: 
FTBFS too much often (failing tests)'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
834682: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834682
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

Bug#834744: xmlgraphics-commons: FTBFS (missing build-depends on gnupg)

2016-09-07 Thread Markus Koschany 
On 07.09.2016 13:06, Santiago Vila wrote:
> On Wed, 7 Sep 2016, Emmanuel Bourg wrote:
> 
>> I haven't been able to reproduce this issue either with a clean pbuilder
>> environment. For some reason gnupg was installed by default in the
>> environment, but maybe this changed recently?
> 
> I don't know if this changed recently with pbuilder, but recent
> versions of sbuild do not require gnupg to be present in the chroot.

I have just filed

http://bugs.debian.org/836940

against cowbuilder and sbuild and asked both maintainers for a
clarification. Apparently apt moved the dependency on gnupg from Depends
to Recommends in version 1.3~exp1 and together with the recent gnupg2
transition, this caused a behavioral change in sbuild.

> 
> This is from the NEWS file:
> 
>  * Major changes in 0.70.0:
> 
>   11) Drop requirement for gpg inside the chroot as external archive keys are
>   now processed without gpg and signing of the internal repository is
>   entirely optional with helpful warning and error messages in case
>   signing failed.
> 
> 
> Please note that this bug is not just "xmlgraphics-commons FTBFS".
> 
> This bug is "xmlgraphics-commons FTBFS if gnupg is not in chroot".

Actually this is not a specific issue in xmlgraphics-commons but affects
all packages that relied on gnupg being installed by default.


> If you or Markus insist on building xmlgraphics-commons with gnupg in
> the chroot, then it's not that you can't reproduce the bug, it's that
> you are not even *trying* to reproduce the bug.
> 
> By definition, to reproduce the bug you need a chroot not having
> gnupg installed. Successful builds with gnupg in the chroot do not
> give any information at all regarding the reproducibility or
> unreproducibility of this bug.
> 
> I think this was evident enough from my use of "missing build-depends"
> in the subject and the patch that I attached, so I'm really surprised
> (and disappointed) that I have to tell again what this bug is about.
> 
> I'm even more disappointed by the fact that this is a missing
> build-depends and it's downgraded to normal when we have considered
> missing build-depends as RC for *ages*.

This bug only surfaced three weeks ago. We could always rely on gnupg
being installed by default. Even the last official sbuild was
successful. [1] This kind of bug should be solved and clarified from
top-down starting with questioning if the apt change in 1.3~exp1 was
necessary and ensuring that our most important build tools behave
identically.

This cannot be achieved by filing RC bugs against numerous affected
packages. In my opinion this is inefficient and just increases the
workload of contributors. Debian Policy is not a document to force
maintainers into implementing something, it rather reflects common best
practices in this distribution. If gnupg was demonstrably always present
in a clean chroot environment, then we should also consider confirming
that and thinking about reverting this change in our tool chain which
would save many manhours and be much more effective.

We have an obvious contradiction at the moment when something has
changed which has always been true (gnupg being installed by default)
and where the most commonly used build tools cowbuild/pbuilder and
sbuild behave differently. This should be investigated with priority now
and in the light of these circumstances lowering the severity is
reasonable and completely up-to the maintainers. By the way marking the
bug as unreproducible just means that feedback from someone else is
appreciated.


> Before I take this to the Technical Committee, do you want to propose
> a summary of the disagreement? This is not required but it's
> recommended here in point 2:
> 
> https://www.debian.org/devel/tech-ctte
> 
> Thanks.

I suggest to wait until both cowbuilder and sbuild maintainers responded
to #836940.

Regards,

Markus

[1]
https://buildd.debian.org/status/fetch.php?pkg=xmlgraphics-commons=all=2.1-1=1454340725



signature.asc
Description: OpenPGP digital signature
__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

Bug#834744: xmlgraphics-commons: FTBFS (missing build-depends on gnupg)

2016-09-07 Thread Santiago Vila 
On Wed, 7 Sep 2016, Emmanuel Bourg wrote:

> I haven't been able to reproduce this issue either with a clean pbuilder
> environment. For some reason gnupg was installed by default in the
> environment, but maybe this changed recently?

I don't know if this changed recently with pbuilder, but recent
versions of sbuild do not require gnupg to be present in the chroot.

This is from the NEWS file:

 * Major changes in 0.70.0:

  11) Drop requirement for gpg inside the chroot as external archive keys are
  now processed without gpg and signing of the internal repository is
  entirely optional with helpful warning and error messages in case
  signing failed.


Please note that this bug is not just "xmlgraphics-commons FTBFS".

This bug is "xmlgraphics-commons FTBFS if gnupg is not in chroot".

If you or Markus insist on building xmlgraphics-commons with gnupg in
the chroot, then it's not that you can't reproduce the bug, it's that
you are not even *trying* to reproduce the bug.

By definition, to reproduce the bug you need a chroot not having
gnupg installed. Successful builds with gnupg in the chroot do not
give any information at all regarding the reproducibility or
unreproducibility of this bug.

I think this was evident enough from my use of "missing build-depends"
in the subject and the patch that I attached, so I'm really surprised
(and disappointed) that I have to tell again what this bug is about.

I'm even more disappointed by the fact that this is a missing
build-depends and it's downgraded to normal when we have considered
missing build-depends as RC for *ages*.

Before I take this to the Technical Committee, do you want to propose
a summary of the disagreement? This is not required but it's
recommended here in point 2:

https://www.debian.org/devel/tech-ctte

Thanks.

__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

Bug#834744: xmlgraphics-commons: FTBFS (missing build-depends on gnupg)

2016-09-07 Thread Santiago Vila 
On Wed, Sep 07, 2016 at 04:47:15AM +0200, Markus Koschany wrote:

> I disagree with your bug severity. The build does not fail in a clean
> cowbuilder environment. I'm attaching my build log as proof.

The build log is just a proof that the build succeeded, but *not* a proof
that the environment was clean.

If you are unable to do it with pbuilder, please post a build log made
with sbuild using a chroot not containing gnupg.

__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

Bug#834744: xmlgraphics-commons: FTBFS (missing build-depends on gnupg)

2016-09-07 Thread Santiago Vila 
On Wed, Sep 07, 2016 at 04:47:15AM +0200, Markus Koschany wrote:

> You should rather work towards defining a common build environment
> standard in Debian [...]

You must be joking. There is already a "common build environment standard",
and it's called the set of build essential packages, of which gnupg is not
(not the old gnupg, not the new gnupg, not the old gnupg2, and not the
new gnupg1).

Everything which is required to build and it's not in build essential
must go in build-depends.

What part of this standard (the build essential set of packages, the
one that really counts, not the list of packages in the package
builder of the day) is the one that you don't understand?

It's in Policy 4.2, here is a quote:

 If build-time dependencies are specified, it *must* be possible to
 build the package and produce working binaries on a system with
 *only* essential and build-essential packages installed and also
 those required to satisfy the build-time relationships (including
 any implied relationships).


This is what you are still not doing with your pbuilder example.

You say "unreproducible", I say unwillingess to reproduce.

This is a must directive in policy, and everybody agrees that missing
build-depends are RC. Do you still disagree that this is severity
serious?

__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

Bug#834744: xmlgraphics-commons: FTBFS (missing build-depends on gnupg)

2016-09-07 Thread Emmanuel Bourg 
I haven't been able to reproduce this issue either with a clean pbuilder
environment. For some reason gnupg was installed by default in the
environment, but maybe this changed recently?

Emmanuel Bourg

__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.