date:20170719

Bug#803924: [Pkg-samba-maint] Bug#803924: -HUP needs to be sent more broadly

2017-07-19 Thread Mathieu Parent

2017-07-20 2:07 GMT+02:00 Andrew Bartlett :
> Thinking about this some more, in the multi-process architecture of the
> AD DC, the -HUP will need to go to every samba process - just making
> the master process reload won't do anything for the children, as far as
> I'm aware.
>
> That said, wildly sending SIGHUP with killall wouldn't be wise either.
> This is going to need code changes to do properly - adding the reopen-
> logs smbcontrol as I mention, and having the parent process be
> responsible for telling the children, or broadcast it, if that hasn't
> been rewritten out.

Is there an equivalent to "smbcontrol * reload-config" for the samba
(AD DC) daemon?

Note that under systemd, we can use:
systemctl kill --kill-who all --signal=SIGHUP samba

thoughts?

Regards

-- 
Mathieu Parent

Bug#869029: Discussion in Simutrans forum

2017-07-19 Thread Julius Andrikonis

Some possible causes of this bug are discussed in this Simutrans forum post:
http://forum.simutrans.com/index.php?topic=17182.0

Julius



signature.asc
Description: OpenPGP digital signature

Bug#796562: lintian: Please identify lack of sanitation compiler/linker flags

2017-07-19 Thread Niels Thykier

intrigeri:
> Hi Chris,
> 
> Chris Lamb:
>>> lintian: Please identify lack of sanitation compiler/linker flags
> 
>> Is this not covered by the following tags?
> 
>>   hardening-no-bindnow
>>   hardening-no-fortify-functions
>>   hardening-no-pie
>>   hardening-no-relro
> 
> Nope: this bug report is about another debugging/hardening option
> (ASan and friends).
> 
>> (etc.)
> 
> Maybe :)
> 
> Cheers,
> 

Hi,

Having read http://www.openwall.com/lists/oss-security/2016/02/17/9
which Jakub Wilk linked to,  I do not think the sanitizers in their
current form are ready for arbitrary cases.

If we could have most of the advantages of these sanitizers without
introducing trivial "local-user-to-root-via-setuid" exploits and some of
the other issues, then I would personally be much more supportive of this.

Thanks,
~Niels

Bug#866400: ifupdown: networking.service fails to start allow-hotplug interfaces at boot

2017-07-19 Thread Guus Sliepen

On Thu, Jul 20, 2017 at 12:33:49AM +0200, Sven-Haegar Koch wrote:

> > I tried that and the only result of that was that network interfaces
> > added to the VM after booting were not renamed, the ones at boot time
> > still were. The only thing that prevented everything from being renamed
> > was to add net.ifnames=0 to the kernel command line.
> 
> Which is a pain to add from custom package postinst scripts without any 
> allowed user-interaction - but I will try that.

Well, you could add a /etc/grub.d/ file maybe, but it's indeed a hassle.

> > It still shouldn't be necessary. What's in your
> > /etc/udev/rules.d/80-ifupdown.rules?
> 
> /etc/udev/rules.d/80-ifupdown.rules does not exist.
> 
> ch-00-sims:~# cat /lib/udev/rules.d/80-ifupdown.rules
[...]

Ah yes, that's the one I meant.

> But the biggest strange this is that now it works, even with disabling 
> all my workarounds!
> 
> Something changed between the initial stretch upgrade with broken 
> network, and now, I don't know what - could even be something timing 
> related.
> 
> Guus, thanks for your help!
> 
> I will close this bug for now as "Unreproduceable".

Well, keep an eye on it. If the problem comes back, let me know!

-- 
Met vriendelijke groet / with kind regards,
  Guus Sliepen 


signature.asc
Description: PGP signature

Bug#868878: [Pkg-libvirt-maintainers] Bug#868878: virt-manager: Please consider dropping dependency on gconf2

2017-07-19 Thread intrigeri

Guido Günther:
> Negligence on my part, sorry. Fixed in git since early March.

Amazing, thanks :)

> I wonder if we can make it any simpler to check current git besides

>  gbp clone vcsgit:virt-manager

I honestly don't know why I did `apt-get source' while I would usually
debcheckout the source package. Old habits occasionally resurfacing,
I guess.

I don't think we can make it simpler, especially since `apt-get
source' already suggests using the VCS instead:

  NOTICE: 'virt-manager' packaging is maintained in the 'Git' version control 
system at:
  https://anonscm.debian.org/git/pkg-libvirt/virt-manager.git
'

Bug#796562: lintian: Please identify lack of sanitation compiler/linker flags

2017-07-19 Thread intrigeri

Control: retitle -1 Please identify lack of UBSAN compiler/linker flags

Jakub Wilk:
> Relevant thread on oss-security:
> http://www.openwall.com/lists/oss-security/2016/02/17/9

Right, I was aware of this additional info but failed to update this
bug report accordingly. Sorry!

tl;dr: "only the UBSAN sanitizer is safe for 'daily use'", as Seth
(Cc'ed) summed up in http://openwall.com/lists/oss-security/2017/07/11/1.

So I'm retitling this bug report to make it about UBSAN only,
i.e. compiling and linking programs with -fsanitize=undefined.
Note that by default, UBSAN only displays an error message at runtime
when a problem is detected, and then resumes execution.

Seth: are you aware of ways to check if a given binary has UBSAN
enabled? Or is this something we should add to blhc instead
of Lintian?

Jakub, does this make sense to you? Do you think this is enough to
drop the moreinfo tag?

Cheers,
-- 
intrigeri

Bug#869030: elixir: Please package v1.4

2017-07-19 Thread Matthias Urlichs

Package: elixir
Version: 1.3.3-2
Severity: wishlist

The upstream version of rabbitmq-server depends on elixir 1.4.

-- System Information:
Debian Release: 9.0
  APT prefers stable
  APT policy: (700, 'stable'), (600, 'unstable'), (550, 'experimental'), (500, 
'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

Kernel: Linux 4.9.0-rc5-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages elixir depends on:
ii  erlang-base  1:19.2.1+dfsg-2

elixir recommends no packages.

elixir suggests no packages.

-- no debconf information

Bug#869028: linux-image-4.12.0-trunk: Please enable CONFIG_IOSCHED_BFQ

2017-07-19 Thread Andre Heider


Source: linux
Version: 4.12.0-trunk
Severity: wishlist

Hi,

new blq-mq i/o scheduler in 4.12, please enable.

Thanks,
Andre

Bug#868927: python-pybedtools FTBFS with more than one supported Python3 version

2017-07-19 Thread Andreas Tille

Hi Adrian,

On Wed, Jul 19, 2017 at 10:47:09PM +0300, Adrian Bunk wrote:
> 
> That's #867017/#867018, which seems to require that you update 
> python-pysam to 0.11.2.2

Yes, I'm aware of it but I need to start the chain of dependencies
at htslib - samtools - python-pysam.

I'll try to work on this today.

Kind regards

  Andreas.

-- 
http://fam-tille.de

Bug#869027: haskell-yaml: FTBFS: build-dependency not installable: libghc-aeson-qq-dev

2017-07-19 Thread Lucas Nussbaum

Source: haskell-yaml
Version: 0.8.23.1-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170719 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):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: cdbs, debhelper (>= 9), ghc (>= 8), ghc-prof, 
> haskell-devscripts (>= 0.13), libghc-aeson-dev (>= 0.7), libghc-aeson-prof, 
> libghc-aeson-qq-dev, libghc-attoparsec-dev (>= 0.11.3.0), 
> libghc-attoparsec-prof, libghc-base-compat-dev, libghc-conduit-dev (<< 1.3), 
> libghc-conduit-dev (>= 1.1.0), libghc-conduit-prof, libghc-hunit-dev, 
> libghc-hspec-dev (>= 1.3), libghc-mockery-dev, libghc-resourcet-dev (>= 0.3), 
> libghc-resourcet-dev (<< 1.2), libghc-resourcet-prof, libghc-scientific-dev, 
> libghc-scientific-prof, libghc-semigroups-dev, libghc-semigroups-prof, 
> libghc-temporary-dev, libghc-text-dev, libghc-text-prof, 
> libghc-unordered-containers-dev, libghc-unordered-containers-prof, 
> libghc-vector-dev, libghc-vector-prof, libyaml-dev, pkg-config, ghc-doc, 
> libghc-aeson-doc, libghc-attoparsec-doc, libghc-conduit-doc, 
> libghc-resourcet-doc, libghc-scientific-doc, libghc-semigroups-doc, 
> libghc-text-doc, libghc-unordered-containers-doc, libghc-vector-doc
> Filtered Build-Depends: cdbs, debhelper (>= 9), ghc (>= 8), ghc-prof, 
> haskell-devscripts (>= 0.13), libghc-aeson-dev (>= 0.7), libghc-aeson-prof, 
> libghc-aeson-qq-dev, libghc-attoparsec-dev (>= 0.11.3.0), 
> libghc-attoparsec-prof, libghc-base-compat-dev, libghc-conduit-dev (<< 1.3), 
> libghc-conduit-dev (>= 1.1.0), libghc-conduit-prof, libghc-hunit-dev, 
> libghc-hspec-dev (>= 1.3), libghc-mockery-dev, libghc-resourcet-dev (>= 0.3), 
> libghc-resourcet-dev (<< 1.2), libghc-resourcet-prof, libghc-scientific-dev, 
> libghc-scientific-prof, libghc-semigroups-dev, libghc-semigroups-prof, 
> libghc-temporary-dev, libghc-text-dev, libghc-text-prof, 
> libghc-unordered-containers-dev, libghc-unordered-containers-prof, 
> libghc-vector-dev, libghc-vector-prof, libyaml-dev, pkg-config, ghc-doc, 
> libghc-aeson-doc, libghc-attoparsec-doc, libghc-conduit-doc, 
> libghc-resourcet-doc, libghc-scientific-doc, libghc-semigroups-doc, 
> libghc-text-doc, libghc-unordered-containers-doc, libghc-vector-doc
> dpkg-deb: building package 'sbuild-build-depends-haskell-yaml-dummy' in 
> '/<>/resolver-yHa5RV/apt_archive/sbuild-build-depends-haskell-yaml-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-core-dummy 
> sbuild-build-depends-haskell-yaml-dummy
> dpkg-scanpackages: info: Wrote 2 entries to output Packages file.
> Ign:1 copy:/<>/resolver-yHa5RV/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-yHa5RV/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/resolver-yHa5RV/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-yHa5RV/apt_archive ./ Sources [792 B]
> Get:5 copy:/<>/resolver-yHa5RV/apt_archive ./ Packages [838 B]
> Fetched 2593 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install haskell-yaml build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-haskell-yaml-dummy : Depends: libghc-aeson-qq-dev but 
> it is not going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://aws-logs.debian.net/2017/07/19/haskell-yaml_0.8.23.1-1_unstable.log

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 EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Bug#869023: cccc: FTBFS: cp: cannot stat 'cccc/CCCC': No such file or directory

2017-07-19 Thread Lucas Nussbaum

Source: 
Version: 1:3.1.4-9
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170719 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 '/<>'
> dh_installdocs '/ User Guide.html'
> cp: cannot stat '/': No such file or directory
> dh_installdocs: cp --reflink=auto -a / debian//usr/share/doc/ 
> returned exit code 1
> debian/rules:41: recipe for target 'override_dh_installdocs' failed
> make[1]: *** [override_dh_installdocs] Error 2

The full build log is available from:
   http://aws-logs.debian.net/2017/07/19/_3.1.4-9_unstable.log

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 EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Bug#869025: exec-maven-plugin: FTBFS: find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers//.jar': No such file or directory

2017-07-19 Thread Lucas Nussbaum

Source: exec-maven-plugin
Version: 1.1.1+dfsg-3
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170719 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):
>  debian/rules build
> test -x debian/rules
> mkdir -p "."
> /usr/share/maven-debian-helper/copy-repo.sh 
> /<>/exec-maven-plugin-1.1.1+dfsg/debian
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compiler/*/*.jar': No 
> such file or directory
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compilers/*/*.jar': 
> No such file or directory
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': 
> No such file or directory
> mh_patchpoms -plibmaven-exec-plugin-java --debian-build --keep-pom-version 
> --maven-repo=/<>/exec-maven-plugin-1.1.1+dfsg/debian/maven-repo  
> --build-no-docs
> touch debian/stamp-poms-patched
> # before-build target may be used to unpatch the pom files, so we need to 
> check if
> # patching the pom files is needed here, normally not
> if [ ! -f pom.xml.save ]; then \
>   /usr/bin/make -f debian/rules patch-poms; \
> fi
> cd . && /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
>  
> -Dproperties.file.manual=/<>/exec-maven-plugin-1.1.1+dfsg/debian/maven.properties
>  -Dclassworlds.conf=/etc/maven/m2-debian.conf -Dmaven.home=/usr/share/maven 
> -Dmaven.multiModuleProjectDirectory=/<>/exec-maven-plugin-1.1.1+dfsg
>  org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml 
> -Dmaven.repo.local=/<>/exec-maven-plugin-1.1.1+dfsg/debian/maven-repo
>   package -DskipTests
> [[1;34mINFO[m] Scanning for projects...
> [[1;34mINFO[m] 
> [[1;34mINFO[m] 
> [1m[m
> [[1;34mINFO[m] [1mBuilding Exec Maven Plugin 1.1.1[m
> [[1;34mINFO[m] 
> [1m[m
> [[1;34mINFO[m] 
> [[1;34mINFO[m] [1m--- [0;32mmaven-resources-plugin:3.0.0:resources[m 
> [1m(default-resources)[m @ [36mexec-maven-plugin[0;1m ---[m
> [[1;33mWARNING[m] Using platform encoding (ANSI_X3.4-1968 actually) to copy 
> filtered resources, i.e. build is platform dependent!
> [[1;34mINFO[m] skip non existing resourceDirectory 
> /<>/exec-maven-plugin-1.1.1+dfsg/src/main/resources
> [[1;34mINFO[m] 
> [[1;34mINFO[m] [1m--- [0;32mmaven-compiler-plugin:3.6.1:compile[m 
> [1m(default-compile)[m @ [36mexec-maven-plugin[0;1m ---[m
> [[1;33mWARNING[m] The POM for 
> org.codehaus.plexus:plexus-compiler-api:jar:2.x is invalid, transitive 
> dependencies (if any) will not be available, enable debug logging for more 
> details
> [[1;33mWARNING[m] The POM for 
> org.codehaus.plexus:plexus-compiler-javac:jar:2.x is invalid, transitive 
> dependencies (if any) will not be available, enable debug logging for more 
> details
> [[1;34mINFO[m] Changes detected - recompiling the module!
> [[1;33mWARNING[m] File encoding has not been set, using platform encoding 
> ANSI_X3.4-1968, i.e. build is platform dependent!
> [[1;34mINFO[m] Compiling 7 source files to 
> /<>/exec-maven-plugin-1.1.1+dfsg/target/classes
> Use of target 1.5 is no longer supported, switching to 1.7
> Use of source 1.5 is no longer supported, switching to 1.7
> [[1;34mINFO[m] 
> /<>/exec-maven-plugin-1.1.1+dfsg/src/main/java/org/codehaus/mojo/exec/ExecJavaMojo.java:
>  
> /<>/exec-maven-plugin-1.1.1+dfsg/src/main/java/org/codehaus/mojo/exec/ExecJavaMojo.java
>  uses or overrides a deprecated API.
> [[1;34mINFO[m] 
> /<>/exec-maven-plugin-1.1.1+dfsg/src/main/java/org/codehaus/mojo/exec/ExecJavaMojo.java:
>  Recompile with -Xlint:deprecation for details.
> [[1;34mINFO[m] 
> /<>/exec-maven-plugin-1.1.1+dfsg/src/main/java/org/codehaus/mojo/exec/Classpath.java:
>  Some input files use unchecked or unsafe operations.
> [[1;34mINFO[m] 
> /<>/exec-maven-plugin-1.1.1+dfsg/src/main/java/org/codehaus/mojo/exec/Classpath.java:
>  Recompile with -Xlint:unchecked for details.
> [[1;34mINFO[m] 
> [[1;34mINFO[m] [1m--- [0;32mmaven-plugin-plugin:3.5:descriptor[m 
> [1m(default-descriptor)[m @ [36mexec-maven-plugin[0;1m ---[m
> [[1;33mWARNING[m] Using platform encoding (ANSI_X3.4-1968 actually) to read 
> mojo source files, i.e. build is platform dependent!
> [[1;33mWARNING[m] org.codehaus.mojo.exec.ExecJavaMojo#arguments:
> [[1;33mWARNING[m]   The syntax
> [[1;33mWARNI

Bug#869014: oscache: FTBFS: find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers//.jar': No such file or directory

2017-07-19 Thread Lucas Nussbaum

Source: oscache
Version: 2.4.1+ds1-5
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170719 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):
>  debian/rules build
> dh build --buildsystem=maven
>dh_testdir -O--buildsystem=maven
>dh_update_autotools_config -O--buildsystem=maven
>dh_auto_configure -O--buildsystem=maven
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compiler/*/*.jar': No 
> such file or directory
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compilers/*/*.jar': 
> No such file or directory
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': 
> No such file or directory
>   mh_patchpoms -pliboscache-java --debian-build --keep-pom-version 
> --maven-repo=/<>/oscache-2.4.1\+ds1/debian/maven-repo
>dh_auto_build -O--buildsystem=maven
>   /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=/<>/oscache-2.4.1\+ds1 
> -Dclassworlds.conf=/etc/maven/m2-debian.conf 
> -Dproperties.file.manual=/<>/oscache-2.4.1\+ds1/debian/maven.properties
>  org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml 
> -Ddebian.dir=/<>/oscache-2.4.1\+ds1/debian 
> -Dmaven.repo.local=/<>/oscache-2.4.1\+ds1/debian/maven-repo package 
> -DskipTests -Dnotimestamp=true -Dlocale=en_US
> [[1;34mINFO[m] Scanning for projects...
> [[1;33mWARNING[m] 
> [[1;33mWARNING[m] Some problems were encountered while building the 
> effective model for opensymphony:oscache:jar:2.4.1
> [[1;33mWARNING[m] The expression ${pom.url} is deprecated. Please use 
> ${project.url} instead.
> [[1;33mWARNING[m] 
> [[1;33mWARNING[m] It is highly recommended to fix these problems because 
> they threaten the stability of your build.
> [[1;33mWARNING[m] 
> [[1;33mWARNING[m] For this reason, future Maven versions might no longer 
> support building such malformed projects.
> [[1;33mWARNING[m] 
> [[1;34mINFO[m] 
> [[1;34mINFO[m] 
> [1m[m
> [[1;34mINFO[m] [1mBuilding OSCache 2.4.1[m
> [[1;34mINFO[m] 
> [1m[m
> [[1;34mINFO[m] 
> [[1;34mINFO[m] [1m--- [0;32mmaven-resources-plugin:3.0.0:resources[m 
> [1m(default-resources)[m @ [36moscache[0;1m ---[m
> [[1;33mWARNING[m] Using platform encoding (ANSI_X3.4-1968 actually) to copy 
> filtered resources, i.e. build is platform dependent!
> [[1;34mINFO[m] Copying 0 resource
> [[1;34mINFO[m] Copying 1 resource
> [[1;34mINFO[m] 
> [[1;34mINFO[m] [1m--- [0;32mmaven-compiler-plugin:3.6.1:compile[m 
> [1m(default-compile)[m @ [36moscache[0;1m ---[m
> [[1;33mWARNING[m] The POM for 
> org.codehaus.plexus:plexus-compiler-api:jar:2.x is invalid, transitive 
> dependencies (if any) will not be available, enable debug logging for more 
> details
> [[1;33mWARNING[m] The POM for 
> org.codehaus.plexus:plexus-compiler-javac:jar:2.x is invalid, transitive 
> dependencies (if any) will not be available, enable debug logging for more 
> details
> [[1;34mINFO[m] Changes detected - recompiling the module!
> [[1;33mWARNING[m] File encoding has not been set, using platform encoding 
> ANSI_X3.4-1968, i.e. build is platform dependent!
> [[1;34mINFO[m] Compiling 65 source files to 
> /<>/oscache-2.4.1+ds1/target/classes
> Use of target 1.4 is no longer supported, switching to 1.7
> Use of source 1.4 is no longer supported, switching to 1.7
> [parsing started 
> RegularFileObject[/<>/oscache-2.4.1+ds1/src/java/com/opensymphony/oscache/plugins/clustersupport/JMS10BroadcastingListener.java]]
> [parsing completed 73ms]
> [parsing started 
> RegularFileObject[/<>/oscache-2.4.1+ds1/src/java/com/opensymphony/oscache/base/events/CacheMapAccessEventListener.java]]
> [parsing completed 1ms]
> [parsing started 
> RegularFileObject[/<>/oscache-2.4.1+ds1/src/java/com/opensymphony/oscache/base/events/CacheEventListener.java]]
> [parsing completed 0ms]
> [parsing started 
> RegularFileObject[/<>/oscache-2.4.1+ds1/src/java/com/opensymphony/oscache/base/AbstractCacheAdministrator.java]]
> [parsing completed 6ms]
> [parsing started 
> RegularFileObject[/<>/oscache-2.4.1+ds1/src/java/com/opensymphony/oscache/plugins/diskpersistence/AbstractDiskPersistenceListener.java]]
> [parsing completed 6ms]

Bug#869026: netty: FTBFS: [exec] Execute failed: java.io.IOException: Cannot run program "git" (in directory "/<>/common"): error=2, No such file or directory

2017-07-19 Thread Lucas Nussbaum

Source: netty
Version: 1:4.1.7-2
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170719 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 '/<>'
> # Replace the missing groovy-maven-plugin
> mkdir -p common/target
> groovy -Dcollection.template.dir=common/src/main/templates \
>-Dcollection.template.test.dir=common/src/test/templates \
>-Dcollection.src.dir=common/target/generated-sources/collections/java \
>
> -Dcollection.testsrc.dir=common/target/generated-test-sources/collections/java
>  \
>common/src/main/script/codegen.groovy
>  [copy] Copying 3 files to 
> /<>/common/target/generated-sources/collections/java
>  [copy] Copying 3 files to 
> /<>/common/target/generated-sources/collections/java
>  [copy] Copying 3 files to 
> /<>/common/target/generated-sources/collections/java
>  [copy] Copying 3 files to 
> /<>/common/target/generated-sources/collections/java
>  [copy] Copying 3 files to 
> /<>/common/target/generated-sources/collections/java
>  [copy] Copying 1 file to 
> /<>/common/target/generated-test-sources/collections/java
>  [copy] Copying 1 file to 
> /<>/common/target/generated-test-sources/collections/java
>  [copy] Copying 1 file to 
> /<>/common/target/generated-test-sources/collections/java
>  [copy] Copying 1 file to 
> /<>/common/target/generated-test-sources/collections/java
>  [copy] Copying 1 file to 
> /<>/common/target/generated-test-sources/collections/java
> dh_auto_build -- package -Dbuild.date='2017-01-23 08:32:14'
>   /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 
> "-Dbuild.date=2017-01-23 08:32:14" -DskipTests -Dnotimestamp=true 
> -Dlocale=en_US
> [[1;34mINFO[m] Scanning for projects...
> [[1;34mINFO[m] 
> [1m[m
> [[1;34mINFO[m] [1mReactor Build Order:[m
> [[1;34mINFO[m] 
> [[1;34mINFO[m] Netty
> [[1;34mINFO[m] Netty/Common
> [[1;34mINFO[m] Netty/Buffer
> [[1;34mINFO[m] Netty/Resolver
> [[1;34mINFO[m] Netty/Transport
> [[1;34mINFO[m] Netty/Codec
> [[1;34mINFO[m] Netty/Codec/DNS
> [[1;34mINFO[m] Netty/Codec/HAProxy
> [[1;34mINFO[m] Netty/Handler
> [[1;34mINFO[m] Netty/Codec/HTTP
> [[1;34mINFO[m] Netty/Codec/HTTP2
> [[1;34mINFO[m] Netty/Codec/Memcache
> [[1;34mINFO[m] Netty/Codec/MQTT
> [[1;34mINFO[m] Netty/Codec/Redis
> [[1;34mINFO[m] Netty/Codec/SMTP
> [[1;34mINFO[m] Netty/Codec/Socks
> [[1;34mINFO[m] Netty/Codec/Stomp
> [[1;34mINFO[m] Netty/Resolver/DNS
> [[1;34mINFO[m] Netty/Transport/SCTP
> [[1;34mINFO[m] Netty/Handler/Proxy
> [[1;34mINFO[m] Netty/Transport/Native/Epoll
> [[1;34mINFO[m] Netty/All-in-One
> [[1;34mINFO[m] 
> [[1;34mINFO[m] 
> [1m[m
> [[1;34mINFO[m] [1mBuilding Netty 4.1.7.Final[m
> [[1;34mINFO[m] 
> [1m[m
> [[1;33mWARNING[m] The artifact javassist:javassist:jar:debian has been 
> relocated to org.javassist:javassist:jar:debian
> [[1;34mINFO[m] 
> [[1;34mINFO[m] [1m--- 
> [0;32mbuild-helper-maven-plugin:1.8:parse-version[m [1m(parse-version)[m 
> @ [36mnetty-parent[0;1m ---[m
> [[1;34mINFO[m] 
> [[1;34mINFO[m] [1m--- [0;32mmaven-antrun-plugin:1.8:run[m 
> [1m(write-version-properties)[m @ [36mnetty-parent[0;1m ---[m
> [[1;33mWARNING[m] The POM for ant-contrib:ant-contrib:jar:debian is 
> invalid, transitive dependencies (if any) will not be available, enable debug 
> logging for more details
> [[1;34mINFO[m] Executing tasks
> 
> main:
>  [exec] Execute failed: java.io.IOException: Cannot run program "git" (in 
> directory "/<>"): error=2, No such file or directory
>  [exec] Execute failed: java.io.IOException: Cannot run program "git" (in 
> directory "/<>"): error=2, No such file or directory
>

Bug#869021: jetty9: FTBFS: find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers//.jar': No such file or directory

2017-07-19 Thread Lucas Nussbaum

Source: jetty9
Version: 9.2.22-2
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170719 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):
>  debian/rules build
> dh build --with javahelper
>dh_testdir
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compiler/*/*.jar': No 
> such file or directory
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compilers/*/*.jar': 
> No such file or directory
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': 
> No such file or directory
>   mh_patchpoms -plibjetty9-java --debian-build --keep-pom-version 
> --maven-repo=/<>/debian/maven-repo
> [ERROR] Cannot find parent dependency 
> org.eclipse.jetty:jetty-project:pom:9.2.14.v20151106, use --no-parent option 
> to resolve this issue or install the parent POM in the Maven repository
> [ERROR] Cannot find parent dependency 
> org.eclipse.jetty.rhttp:jetty-rhttp-project:pom:9.2.14.v20151106, use 
> --no-parent option to resolve this issue or install the parent POM in the 
> Maven repository
> [ERROR] Cannot find parent dependency 
> org.eclipse.jetty.rhttp:jetty-rhttp-project:pom:9.2.14.v20151106, use 
> --no-parent option to resolve this issue or install the parent POM in the 
> Maven repository
> [ERROR] Cannot find parent dependency 
> org.eclipse.jetty.rhttp:jetty-rhttp-project:pom:9.2.14.v20151106, use 
> --no-parent option to resolve this issue or install the parent POM in the 
> Maven repository
>jh_linkjars
>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
> [[1;34mINFO[m] Scanning for projects...
> [[1;33mWARNING[m] 
> [[1;33mWARNING[m] Some problems were encountered while building the 
> effective model for org.eclipse.jetty:jetty-util:jar:9.2.22.v20170531
> [[1;33mWARNING[m] 'build.plugins.plugin.version' for 
> org.apache.maven.plugins:maven-jar-plugin is missing. @ line 43, column 12
> [[1;33mWARNING[m] 
> [[1;33mWARNING[m] Some problems were encountered while building the 
> effective model for org.eclipse.jetty:jetty-jmx:jar:9.2.22.v20170531
> [[1;33mWARNING[m] 'build.plugins.plugin.version' for 
> org.apache.maven.plugins:maven-jar-plugin is missing. @ line 43, column 12
> [[1;33mWARNING[m] 
> [[1;33mWARNING[m] Some problems were encountered while building the 
> effective model for org.eclipse.jetty:jetty-io:jar:9.2.22.v20170531
> [[1;33mWARNING[m] 'build.plugins.plugin.version' for 
> org.apache.maven.plugins:maven-jar-plugin is missing. @ line 49, column 12
> [[1;33mWARNING[m] 
> [[1;33mWARNING[m] Some problems were encountered while building the 
> effective model for org.eclipse.jetty:jetty-http:jar:9.2.22.v20170531
> [[1;33mWARNING[m] 'build.plugins.plugin.version' for 
> org.apache.maven.plugins:maven-jar-plugin is missing. @ line 49, column 12
> [[1;33mWARNING[m] 
> [[1;33mWARNING[m] Some problems were encountered while building the 
> effective model for org.eclipse.jetty:jetty-continuation:jar:9.2.22.v20170531
> [[1;33mWARNING[m] 'build.plugins.plugin.version' for 
> org.apache.maven.plugins:maven-jar-plugin is missing. @ line 38, column 12
> [[1;33mWARNING[m] 
> [[1;33mWARNING[m] Some problems were encountered while building the 
> effective model for org.eclipse.jetty:jetty-server:jar:9.2.22.v20170531
> [[1;33mWARNING[m] 'build.plugins.plugin.version' for 
> org.apache.maven.plugins:maven-jar-plugin is missing. @ line 45, column 12
> [[1;33mWARNING[m] 
> [[1;33mWARNING[m] Some problems were encountered while building the 
> effective model for org.eclipse.jetty:jetty-xml:jar:9.2.22.v20170531
> [[1;33mWARNING[m] 'build.plugins.plugin.version' for 
> org.apache.maven.plugins:maven-jar-plugin is missing. @ line 38, column 12
> [[1;33mWARNING[m] 
> [[1;33mWARNING[m] Some problems were encountered while building the 
> effective model for org.eclipse.jetty:jetty-security:jar:9.2.22.v20170531
> [[1;33mWARNING[m] &

Bug#869019: maven-war-plugin: FTBFS: find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers//.jar': No such file or directory

2017-07-19 Thread Lucas Nussbaum

Source: maven-war-plugin
Version: 2.2-2
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170719 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):
>  debian/rules build
> test -x debian/rules
> mkdir -p "."
> /usr/share/maven-debian-helper/copy-repo.sh /<>/debian
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compiler/*/*.jar': No 
> such file or directory
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compilers/*/*.jar': 
> No such file or directory
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': 
> No such file or directory
> mh_patchpoms -plibmaven-war-plugin-java --debian-build --keep-pom-version 
> --maven-repo=/<>/debian/maven-repo  --build-no-docs
> touch debian/stamp-poms-patched
> # before-build target may be used to unpatch the pom files, so we need to 
> check if
> # patching the pom files is needed here, normally not
> if [ ! -f pom.xml.save ]; then \
>   /usr/bin/make -f debian/rules patch-poms; \
> fi
> cd . && /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
>  -Dproperties.file.manual=/<>/debian/maven.properties 
> -Dclassworlds.conf=/etc/maven/m2-debian.conf -Dmaven.home=/usr/share/maven 
> -Dmaven.multiModuleProjectDirectory=/<> 
> org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml 
> -Dmaven.repo.local=/<>/debian/maven-repo  package -DskipTests
> [[1;34mINFO[m] Scanning for projects...
> [[1;34mINFO[m] 
> [[1;34mINFO[m] 
> [1m[m
> [[1;34mINFO[m] [1mBuilding Maven WAR Plugin 2.2[m
> [[1;34mINFO[m] 
> [1m[m
> [[1;34mINFO[m] 
> [[1;34mINFO[m] [1m--- [0;32mmaven-resources-plugin:3.0.0:resources[m 
> [1m(default-resources)[m @ [36mmaven-war-plugin[0;1m ---[m
> [[1;33mWARNING[m] Using platform encoding (ANSI_X3.4-1968 actually) to copy 
> filtered resources, i.e. build is platform dependent!
> [[1;34mINFO[m] skip non existing resourceDirectory 
> /<>/src/main/resources
> [[1;34mINFO[m] 
> [[1;34mINFO[m] [1m--- [0;32mmaven-compiler-plugin:3.6.1:compile[m 
> [1m(default-compile)[m @ [36mmaven-war-plugin[0;1m ---[m
> [[1;33mWARNING[m] The POM for 
> org.codehaus.plexus:plexus-compiler-api:jar:2.x is invalid, transitive 
> dependencies (if any) will not be available, enable debug logging for more 
> details
> [[1;33mWARNING[m] The POM for 
> org.codehaus.plexus:plexus-compiler-javac:jar:2.x is invalid, transitive 
> dependencies (if any) will not be available, enable debug logging for more 
> details
> [[1;34mINFO[m] Changes detected - recompiling the module!
> [[1;33mWARNING[m] File encoding has not been set, using platform encoding 
> ANSI_X3.4-1968, i.e. build is platform dependent!
> [[1;34mINFO[m] Compiling 26 source files to /<>/target/classes
> Use of target 1.3 is no longer supported, switching to 1.7
> Use of source 1.3 is no longer supported, switching to 1.7
> [[1;34mINFO[m] 
> /<>/src/main/java/org/apache/maven/plugin/war/AbstractWarMojo.java:
>  Some input files use unchecked or unsafe operations.
> [[1;34mINFO[m] 
> /<>/src/main/java/org/apache/maven/plugin/war/AbstractWarMojo.java:
>  Recompile with -Xlint:unchecked for details.
> [[1;34mINFO[m] 
> [[1;34mINFO[m] [1m--- [0;32mmaven-plugin-plugin:3.5:descriptor[m 
> [1m(default-descriptor)[m @ [36mmaven-war-plugin[0;1m ---[m
> [[1;33mWARNING[m] Using platform encoding (ANSI_X3.4-1968 actually) to read 
> mojo source files, i.e. build is platform dependent!
> [[1;33mWARNING[m] 
> org.apache.maven.plugin.war.WarManifestMojo#archiveClasses:
> [[1;33mWARNING[m]   The syntax
> [[1;33mWARNING[m] @parameter expression="${property}"
> [[1;33mWARNING[m]   is deprecated, please use
> [[1;33mWARNING[m] @parameter property="property"
> [[1;33mWARNING[m]   instead.
> [[1;33mWARNING[m] 
> org.apache.maven.plugin.war.WarManifestMojo#containerConfigXML:
> [[1;33mWARNING[m]   The syntax
> [[1;33mWARNING[m] @parameter expression="${property}"
> [[1;33mWARNING[m]   is deprecated, please use
> [[1;33mWARNING[m] @parameter property="property"
> [[1;33mWARNING[m]   instead.
> [[1;33mWARNING[m] org.apache.maven.plugin.war.WarManifestMojo#escapeString:
> [[1;33mWARNING[m]   The synta

Bug#869015: maven-deploy-plugin: FTBFS: dh_auto_test: /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.

2017-07-19 Thread Lucas Nussbaum

Source: maven-deploy-plugin
Version: 2.8.2-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170719 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):
>  debian/rules build
> dh build --buildsystem=maven
>dh_testdir -O--buildsystem=maven
>dh_update_autotools_config -O--buildsystem=maven
>dh_auto_configure -O--buildsystem=maven
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compiler/*/*.jar': No 
> such file or directory
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compilers/*/*.jar': 
> No such file or directory
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': 
> No such file or directory
>   mh_patchpoms -plibmaven-deploy-plugin-java --debian-build 
> --keep-pom-version --maven-repo=/<>/debian/maven-repo
>dh_auto_build -O--buildsystem=maven
>   /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
> [[1;34mINFO[m] Scanning for projects...
> [[1;34mINFO[m] 
> [[1;34mINFO[m] 
> [1m[m
> [[1;34mINFO[m] [1mBuilding Apache Maven Deploy Plugin 2.8.2[m
> [[1;34mINFO[m] 
> [1m[m
> [[1;34mINFO[m] 
> [[1;34mINFO[m] [1m--- [0;32mmaven-plugin-plugin:3.5:helpmojo[m 
> [1m(help-goal)[m @ [36mmaven-deploy-plugin[0;1m ---[m
> [[1;33mWARNING[m] Using platform encoding (ANSI_X3.4-1968 actually) to read 
> mojo source files, i.e. build is platform dependent!
> [[1;34mINFO[m] java-javadoc mojo extractor found 0 mojo descriptor.
> [[1;34mINFO[m] java-annotations mojo extractor found 0 mojo descriptor.
> [[1;34mINFO[m] 
> [[1;34mINFO[m] [1m--- [0;32mmaven-resources-plugin:3.0.0:resources[m 
> [1m(default-resources)[m @ [36mmaven-deploy-plugin[0;1m ---[m
> [[1;33mWARNING[m] Using platform encoding (ANSI_X3.4-1968 actually) to copy 
> filtered resources, i.e. build is platform dependent!
> [[1;34mINFO[m] skip non existing resourceDirectory 
> /<>/src/main/resources
> [[1;34mINFO[m] 
> [[1;34mINFO[m] [1m--- [0;32mmaven-compiler-plugin:3.6.1:compile[m 
> [1m(default-compile)[m @ [36mmaven-deploy-plugin[0;1m ---[m
> [[1;33mWARNING[m] The POM for 
> org.codehaus.plexus:plexus-compiler-api:jar:2.x is invalid, transitive 
> dependencies (if any) will not be available, enable debug logging for more 
> details
> [[1;33mWARNING[m] The POM for 
> org.codehaus.plexus:plexus-compiler-javac:jar:2.x is invalid, transitive 
> dependencies (if any) will not be available, enable debug logging for more 
> details
> [[1;34mINFO[m] Changes detected - recompiling the module!
> [[1;33mWARNING[m] File encoding has not been set, using platform encoding 
> ANSI_X3.4-1968, i.e. build is platform dependent!
> [[1;34mINFO[m] Compiling 5 source files to /<>/target/classes
> Use of target 1.5 is no longer supported, switching to 1.7
> Use of source 1.5 is no longer supported, switching to 1.7
> [[1;34mINFO[m] 
> [[1;34mINFO[m] [1m--- [0;32mmaven-plugin-plugin:3.5:descriptor[m 
> [1m(default-descriptor)[m @ [36mmaven-deploy-plugin[0;1m ---[m
> [[1;33mWARNING[m] Using platform encoding (ANSI_X3.4-1968 actually) to read 
> mojo source files, i.e. build is platform dependent!
> [[1;34mINFO[m] java-javadoc mojo extractor found 0 mojo descriptor.
> [[1;34mINFO[m] java-annotations mojo extractor found 3 mojo descriptors.
> [[1;34mINFO[m] 
> [[1;34mINFO[m] [1m--- [0;32mmaven-plugin-plugin:3.5:descriptor[m 
> [1m(mojo-descriptor)[m @ [36mmaven-deploy-plugin[0;1m ---[m
> [[1;33mWARNING[m] Using platform encoding (ANSI_X3.4-1968 actually) to read 
> mojo source files, i.e. build is platform dependent!
> [[1;34mINFO[m] java-javadoc mojo extractor found 0 mojo descriptor.
> [[1;34mINFO[m] java-annotations mojo extractor found 3 mojo descriptors.
> [[1;34mINFO[m] 
> [[1;34mINFO[m] [1m--- [0;32mmaven-resources-plugin:3.0.0:testResources[m 
> [1m(default-testResources)[m @ [36mmaven-deploy-plugin[0;1m ---[m
> [[1;33mWAR

Bug#869018: easymock: FTBFS: find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers//.jar': No such file or directory

2017-07-19 Thread Lucas Nussbaum

Source: easymock
Version: 3.4+ds-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170719 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):
>  debian/rules build
> dh build
>dh_testdir
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compiler/*/*.jar': No 
> such file or directory
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compilers/*/*.jar': 
> No such file or directory
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': 
> No such file or directory
>   mh_patchpoms -plibeasymock-java --debian-build --keep-pom-version 
> --maven-repo=/<>/easymock-3.4\+ds/debian/maven-repo
>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=/<>/easymock-3.4\+ds 
> -Dclassworlds.conf=/etc/maven/m2-debian.conf 
> -Dproperties.file.manual=/<>/easymock-3.4\+ds/debian/maven.properties
>  org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml 
> -Ddebian.dir=/<>/easymock-3.4\+ds/debian 
> -Dmaven.repo.local=/<>/easymock-3.4\+ds/debian/maven-repo package 
> javadoc:jar javadoc:aggregate -DskipTests -Dnotimestamp=true -Dlocale=en_US
> [[1;34mINFO[m] Scanning for projects...
> [[1;33mWARNING[m] The project org.easymock:easymock-parent:pom:3.4 uses 
> prerequisites which is only intended for maven-plugin projects but not for 
> non maven-plugin projects. For such purposes you should use the 
> maven-enforcer-plugin. See 
> https://maven.apache.org/enforcer/enforcer-rules/requireMavenVersion.html
> [[1;34mINFO[m] 
> [1m[m
> [[1;34mINFO[m] [1mReactor Build Order:[m
> [[1;34mINFO[m] 
> [[1;34mINFO[m] EasyMock Parent
> [[1;34mINFO[m] EasyMock
> [[1;33mWARNING[m] The POM for 
> org.apache.maven.plugins:maven-deploy-plugin:jar:2.7 is missing, no 
> dependency information available
> [[1;33mWARNING[m] Failed to retrieve plugin descriptor for 
> org.apache.maven.plugins:maven-deploy-plugin:2.7: Plugin 
> org.apache.maven.plugins:maven-deploy-plugin:2.7 or one of its dependencies 
> could not be resolved: Cannot access central 
> (https://repo.maven.apache.org/maven2) in offline mode and the artifact 
> org.apache.maven.plugins:maven-deploy-plugin:jar:2.7 has not been downloaded 
> from it before.
> [[1;33mWARNING[m] The POM for 
> org.apache.maven.plugins:maven-antrun-plugin:jar:1.8 is missing, no 
> dependency information available
> [[1;33mWARNING[m] Failed to retrieve plugin descriptor for 
> org.apache.maven.plugins:maven-antrun-plugin:1.8: Plugin 
> org.apache.maven.plugins:maven-antrun-plugin:1.8 or one of its dependencies 
> could not be resolved: Cannot access central 
> (https://repo.maven.apache.org/maven2) in offline mode and the artifact 
> org.apache.maven.plugins:maven-antrun-plugin:jar:1.8 has not been downloaded 
> from it before.
> [[1;33mWARNING[m] The POM for 
> org.apache.maven.plugins:maven-assembly-plugin:jar:2.5.5 is missing, no 
> dependency information available
> [[1;33mWARNING[m] Failed to retrieve plugin descriptor for 
> org.apache.maven.plugins:maven-assembly-plugin:2.5.5: Plugin 
> org.apache.maven.plugins:maven-assembly-plugin:2.5.5 or one of its 
> dependencies could not be resolved: Cannot access central 
> (https://repo.maven.apache.org/maven2) in offline mode and the artifact 
> org.apache.maven.plugins:maven-assembly-plugin:jar:2.5.5 has not been 
> downloaded from it before.
> [[1;33mWARNING[m] The POM for 
> org.apache.maven.plugins:maven-dependency-plugin:jar:2.8 is missing, no 
> dependency information available
> [[1;33mWARNING[m] Failed to retrieve plugin descriptor for 
> org.apache.maven.plugins:maven-dependency-plugin:2.8: Plugin 
> org.apache.maven.plugins:maven-dependency-plugin:2.8 or one of its 
> dependencies could not be resolved: Cannot access central 
> (https://repo.maven.apache.org/maven2) in offline mode and the artifact 
> org.apache.maven.plugins:maven-dependency-plugin:jar:2.8 has not been 
> downloaded from it before.
> [[1;33mWARNING[m] The POM for 
> org.apache.maven.plugins:maven-release-plugin:jar:2.3.2 is missing, no 
> dependency information available
> [[1;33mWARNING[m] Failed to retrieve plugin descriptor for 
> org.apache.maven.plugins:maven-release-plugin:2.3.2: Plu

Bug#796562: lintian: Please identify lack of sanitation compiler/linker flags

2017-07-19 Thread intrigeri

Hi Chris,

Chris Lamb:
>> lintian: Please identify lack of sanitation compiler/linker flags

> Is this not covered by the following tags?

>   hardening-no-bindnow
>   hardening-no-fortify-functions
>   hardening-no-pie
>   hardening-no-relro

Nope: this bug report is about another debugging/hardening option
(ASan and friends).

> (etc.)

Maybe :)

Cheers,
-- 
intrigeri

Bug#869012: maven-dependency-plugin: FTBFS: dh_auto_test: /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 -Dma

2017-07-19 Thread Lucas Nussbaum

Source: maven-dependency-plugin
Version: 2.8-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170719 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):
>  debian/rules build
> dh build --buildsystem=maven
>dh_testdir -O--buildsystem=maven
>dh_update_autotools_config -O--buildsystem=maven
>dh_auto_configure -O--buildsystem=maven
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compiler/*/*.jar': No 
> such file or directory
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compilers/*/*.jar': 
> No such file or directory
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': 
> No such file or directory
>   mh_patchpoms -plibmaven-dependency-plugin-java --debian-build 
> --keep-pom-version --maven-repo=/<>/debian/maven-repo
>dh_auto_build -O--buildsystem=maven
>   /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
> [[1;34mINFO[m] Scanning for projects...
> [[1;33mWARNING[m] 
> [[1;33mWARNING[m] Some problems were encountered while building the 
> effective model for 
> org.apache.maven.plugins:maven-dependency-plugin:maven-plugin:2.8
> [[1;33mWARNING[m] 
> 'dependencies.dependency.(groupId:artifactId:type:classifier)' must be 
> unique: org.apache.maven.plugin-testing:maven-plugin-testing-harness:jar -> 
> duplicate declaration of version debian @ line 228, column 15
> [[1;33mWARNING[m] 
> [[1;33mWARNING[m] It is highly recommended to fix these problems because 
> they threaten the stability of your build.
> [[1;33mWARNING[m] 
> [[1;33mWARNING[m] For this reason, future Maven versions might no longer 
> support building such malformed projects.
> [[1;33mWARNING[m] 
> [[1;34mINFO[m] 
> [[1;34mINFO[m] 
> [1m[m
> [[1;34mINFO[m] [1mBuilding Maven Dependency Plugin 2.8[m
> [[1;34mINFO[m] 
> [1m[m
> [[1;34mINFO[m] 
> [[1;34mINFO[m] [1m--- [0;32mmaven-plugin-plugin:3.5:helpmojo[m 
> [1m(help-goal)[m @ [36mmaven-dependency-plugin[0;1m ---[m
> [[1;33mWARNING[m] Using platform encoding (ANSI_X3.4-1968 actually) to read 
> mojo source files, i.e. build is platform dependent!
> [[1;34mINFO[m] java-javadoc mojo extractor found 0 mojo descriptor.
> [[1;33mWARNING[m] Unable to get sources artifact for 
> org.apache.maven.reporting:maven-reporting-impl:debian. Some javadoc tags 
> (@since, @deprecated and comments) won't be used
> [[1;34mINFO[m] java-annotations mojo extractor found 0 mojo descriptor.
> [[1;34mINFO[m] 
> [[1;34mINFO[m] [1m--- [0;32mmaven-resources-plugin:3.0.0:resources[m 
> [1m(default-resources)[m @ [36mmaven-dependency-plugin[0;1m ---[m
> [[1;33mWARNING[m] Using platform encoding (ANSI_X3.4-1968 actually) to copy 
> filtered resources, i.e. build is platform dependent!
> [[1;34mINFO[m] Copying 6 resources
> [[1;34mINFO[m] 
> [[1;34mINFO[m] [1m--- [0;32mmaven-compiler-plugin:3.6.1:compile[m 
> [1m(default-compile)[m @ [36mmaven-dependency-plugin[0;1m ---[m
> [[1;33mWARNING[m] The POM for 
> org.codehaus.plexus:plexus-compiler-api:jar:2.x is invalid, transitive 
> dependencies (if any) will not be available, enable debug logging for more 
> details
> [[1;33mWARNING[m] The POM for 
> org.codehaus.plexus:plexus-compiler-javac:jar:2.x is invalid, transitive 
> dependencies (if any) will not be available, enable debug logging for more 
> details
> [[1;34mINFO[m] Changes detected - recompiling the module!
> [[1;33mWARNING[m] File encoding has not been set, using platform encoding 
> ANSI_X3.4-1968, i.e. build is platform dependent!
> [[1;34mINFO[m] Compiling 49 source files to /<>/target/classes
> Use of target 1.5 is no longer supported, switching to 1.7
> Use of source 1.5 is no longer supported, switching to 1.7
> [[1;34mINFO[m] 
> /<>/src/main/java/org/apache/maven/plugin/dependency/fromDependencies/CopyDependenciesMojo.java:
>  
> /<>/src/main/java/org/

Bug#869020: logback: FTBFS: find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers//.jar': No such file or directory

2017-07-19 Thread Lucas Nussbaum

Source: logback
Version: 1:1.1.9-4
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170719 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):
>  debian/rules build
> dh build --build-system=maven
>dh_testdir -O--build-system=maven
>dh_update_autotools_config -O--build-system=maven
>dh_autoreconf -O--build-system=maven
>dh_auto_configure -O--build-system=maven
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compiler/*/*.jar': No 
> such file or directory
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compilers/*/*.jar': 
> No such file or directory
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': 
> No such file or directory
>   mh_patchpoms -pliblogback-java --debian-build --keep-pom-version 
> --maven-repo=/<>/debian/maven-repo
>dh_auto_build -O--build-system=maven
>   /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 javadoc:jar 
> javadoc:aggregate -DskipTests -Dnotimestamp=true -Dlocale=en_US
> [[1;34mINFO[m] Scanning for projects...
> [[1;34mINFO[m] 
> [1m[m
> [[1;34mINFO[m] [1mReactor Build Order:[m
> [[1;34mINFO[m] 
> [[1;34mINFO[m] Logback-Parent
> [[1;34mINFO[m] Logback Core Module
> [[1;34mINFO[m] Logback Classic Module
> [[1;34mINFO[m] Logback Access Module
> [[1;33mWARNING[m] The POM for 
> org.apache.maven.plugins:maven-deploy-plugin:jar:2.7 is missing, no 
> dependency information available
> [[1;33mWARNING[m] Failed to retrieve plugin descriptor for 
> org.apache.maven.plugins:maven-deploy-plugin:2.7: Plugin 
> org.apache.maven.plugins:maven-deploy-plugin:2.7 or one of its dependencies 
> could not be resolved: Cannot access central 
> (https://repo.maven.apache.org/maven2) in offline mode and the artifact 
> org.apache.maven.plugins:maven-deploy-plugin:jar:2.7 has not been downloaded 
> from it before.
> [[1;33mWARNING[m] The POM for 
> org.apache.maven.plugins:maven-site-plugin:jar:3.3 is missing, no dependency 
> information available
> [[1;33mWARNING[m] Failed to retrieve plugin descriptor for 
> org.apache.maven.plugins:maven-site-plugin:3.3: Plugin 
> org.apache.maven.plugins:maven-site-plugin:3.3 or one of its dependencies 
> could not be resolved: Cannot access central 
> (https://repo.maven.apache.org/maven2) in offline mode and the artifact 
> org.apache.maven.plugins:maven-site-plugin:jar:3.3 has not been downloaded 
> from it before.
> [[1;33mWARNING[m] The POM for 
> org.apache.maven.plugins:maven-assembly-plugin:jar:2.4.1 is missing, no 
> dependency information available
> [[1;33mWARNING[m] Failed to retrieve plugin descriptor for 
> org.apache.maven.plugins:maven-assembly-plugin:2.4.1: Plugin 
> org.apache.maven.plugins:maven-assembly-plugin:2.4.1 or one of its 
> dependencies could not be resolved: Cannot access central 
> (https://repo.maven.apache.org/maven2) in offline mode and the artifact 
> org.apache.maven.plugins:maven-assembly-plugin:jar:2.4.1 has not been 
> downloaded from it before.
> [[1;33mWARNING[m] The POM for 
> org.apache.maven.plugins:maven-deploy-plugin:jar:2.7 is missing, no 
> dependency information available
> [[1;33mWARNING[m] Failed to retrieve plugin descriptor for 
> org.apache.maven.plugins:maven-deploy-plugin:2.7: Plugin 
> org.apache.maven.plugins:maven-deploy-plugin:2.7 or one of its dependencies 
> could not be resolved: Cannot access central 
> (https://repo.maven.apache.org/maven2) in offline mode and the artifact 
> org.apache.maven.plugins:maven-deploy-plugin:jar:2.7 has not been downloaded 
> from it before.
> [[1;33mWARNING[m] The POM for 
> org.apache.maven.plugins:maven-site-plugin:jar:3.3 is missing, no dependency 
> information available
> [[1;33mWARNING[m] Failed to retrieve plugin descriptor for 
> org.apache.maven.plugins:maven-site-plugin:3.3: Plugin 
> org.apache.maven.plugins:maven-site-plugin:3.3 or one of its dependencies 
> could not be resolved: Cannot access central 
> (https://repo.maven.apache.org/maven2) in offline mode and the artifac

Bug#869024: nsis: FTBFS: cp: cannot stat 'build/README.Modern': No such file or directory

2017-07-19 Thread Lucas Nussbaum

Source: nsis
Version: 2.51-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170719 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 '/<>'
> scons -j 16 VERSION=2.51-1 PREFIX=/usr PREFIX_CONF=/etc CHMDOCS=0 STRIP_CP=no 
>  PREFIX_PLUGINAPI_INC=/usr/i686-w64-mingw32/include/ 
> PREFIX_PLUGINAPI_LIB=/usr/i686-w64-mingw32/lib/ 
> XGCC_W32_PREFIX=i686-w64-mingw32- 
> SKIPUTILS='Library/LibraryLocal,MakeLangId,Makensisw,NSIS 
> Menu,SubStart,VPatch/Source/GenPat,zip2exe' SKIPDOC=COPYING 
> PREFIX_DEST="/<>/debian/nsis-common" install-stubs 
> install-plugins install-data install-utils || exit 1;  scons -j 16 
> VERSION=2.51-1 PREFIX=/usr PREFIX_CONF=/etc CHMDOCS=0 STRIP_CP=no  
> PREFIX_PLUGINAPI_INC=/usr/i686-w64-mingw32/include/ 
> PREFIX_PLUGINAPI_LIB=/usr/i686-w64-mingw32/lib/ 
> XGCC_W32_PREFIX=i686-w64-mingw32- 
> SKIPUTILS='Library/LibraryLocal,MakeLangId,Makensisw,NSIS 
> Menu,SubStart,VPatch/Source/GenPat,zip2exe' SKIPDOC=COPYING 
> PREFIX_DEST="/<>/debian/nsis-pluginapi" install-pluginapi || 
> exit 1;scons APPEND_CCFLAGS="-fgnu89-inline -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" 
> APPEND_LINKFLAGS="-Wl,-z,relro" -j 16 VERSION=2.51-1 PREFIX=/usr 
> PREFIX_CONF=/etc CHMDOCS=0 STRIP_CP=no  
> PREFIX_PLUGINAPI_INC=/usr/i686-w64-mingw32/include/ 
> PREFIX_PLUGINAPI_LIB=/usr/i686-w64-mingw32/lib/ 
> XGCC_W32_PREFIX=i686-w64-mingw32- 
> SKIPUTILS='Library/RegTool,MakeLangId,Makensisw,NSIS 
> Menu,UIs,SubStart,zip2exe' SKIPDOC=COPYING 
> PREFIX_DEST="/<>/debian/nsis-doc" install-examples install-doc 
> || exit 1;
> scons: Reading SConscript files ...
> Mkdir("build/release/config")
> Delete("nsis-2.51-1")
> Delete(".instdist")
> Delete(".test")
> Using GNU tools configuration
> Checking for linker flag $MAP_FLAG... yes
> Checking for linker flag $MAP_FLAG... yes
> Checking for memcpy requirement... no
> Checking for memset requirement... no
> Checking for linker flag -pthread... yes
> Checking for __BIG_ENDIAN__... no
> Checking for C library gdi32... no
> Checking for C library user32... no
> Checking for C library pthread... yes
> Checking for C library iconv... no
> Checking for C library z... yes
> Checking for C library dl... yes
> Checking for C library gdi32... no
> Checking for C library iconv... no
> Checking for C library pthread... yes
> Checking for C library user32... no
> Checking for C library z... yes
> Checking for C++ library cppunit... yes
> scons: done reading SConscript files.
> scons: Building targets ...
> Install file: "build/release/stub_bzip2/stub_bzip2.exe" as 
> "debian/nsis-common/usr/share/nsis/Stubs/bzip2"
> Install file: "build/release/stub_bzip2_solid/stub_bzip2.exe" as 
> "debian/nsis-common/usr/share/nsis/Stubs/bzip2_solid"
> Install file: "build/release/stub_lzma/stub_lzma.exe" as 
> "debian/nsis-common/usr/share/nsis/Stubs/lzma"
> Install file: "build/release/stub_lzma_solid/stub_lzma.exe" as 
> "debian/nsis-common/usr/share/nsis/Stubs/lzma_solid"
> Install file: "build/release/stub_zlib/stub_zlib.exe" as 
> "debian/nsis-common/usr/share/nsis/Stubs/zlib"
> Install file: "build/release/stub_zlib_solid/stub_zlib.exe" as 
> "debian/nsis-common/usr/share/nsis/Stubs/zlib_solid"
> Install file: "Source/exehead/uninst.ico" as 
> "debian/nsis-common/usr/share/nsis/Stubs/uninst"
> Install file: "build/release/AdvSplash/AdvSplash.dll" as 
> "debian/nsis-common/usr/share/nsis/Plugins/AdvSplash.dll"
> Install file: "build/release/Banner/Banner.dll" as 
> "debian/nsis-common/usr/share/nsis/Plugins/Banner.dll"
> Install file: "build/release/BgImage/BgImage.dll" as 
> "debian/nsis-common/usr/share/nsis/Plugins/BgImage.dll"
> Install file: "build/release/Dialer/Dialer.dll" as 
> "debian/nsis-common/usr/share/nsis/Plugins/Dialer.dll"
> Install file: "build/release/InstallOptions/InstallOptions.dll" as 
> "debian/nsis-common/usr/share/nsis/Plugins/InstallOptions.dll"
> Install file: "build/release/LangDLL/LangDLL.dll" as 
> "debian/nsis-common/usr/share/nsis/Plugins/LangDLL.dll"
> Install file: "build/release/Library/TypeLib/TypeLib.dll" as 
> "debian

Bug#869022: guice: FTBFS: find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers//.jar': No such file or directory

2017-07-19 Thread Lucas Nussbaum

Source: guice
Version: 4.0-4
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170719 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):
>  debian/rules build
> dh build --buildsystem=maven
>dh_testdir -O--buildsystem=maven
>dh_update_autotools_config -O--buildsystem=maven
>dh_autoreconf -O--buildsystem=maven
>dh_auto_configure -O--buildsystem=maven
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compiler/*/*.jar': No 
> such file or directory
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compilers/*/*.jar': 
> No such file or directory
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': 
> No such file or directory
>   mh_patchpoms -plibguice-java --debian-build --keep-pom-version 
> --maven-repo=/<>/debian/maven-repo
>dh_auto_build -O--buildsystem=maven
>   /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 javadoc:jar 
> javadoc:aggregate -DskipTests -Dnotimestamp=true -Dlocale=en_US
> [[1;34mINFO[m] Scanning for projects...
> [[1;33mWARNING[m] The project com.google.inject:guice-parent:pom:4.0 uses 
> prerequisites which is only intended for maven-plugin projects but not for 
> non maven-plugin projects. For such purposes you should use the 
> maven-enforcer-plugin. See 
> https://maven.apache.org/enforcer/enforcer-rules/requireMavenVersion.html
> [[1;34mINFO[m] 
> [1m[m
> [[1;34mINFO[m] [1mReactor Build Order:[m
> [[1;34mINFO[m] 
> [[1;34mINFO[m] Google Guice
> [[1;34mINFO[m] Google Guice - Bill of Materials
> [[1;34mINFO[m] Google Guice - Core Library
> [[1;34mINFO[m] Google Guice - Extensions
> [[1;34mINFO[m] Google Guice - Extensions - AssistedInject
> [[1;34mINFO[m] Google Guice - Extensions - MultiBindings
> [[1;34mINFO[m] Google Guice - Extensions - Grapher
> [[1;34mINFO[m] Google Guice - Extensions - JMX
> [[1;34mINFO[m] Google Guice - Extensions - JNDI
> [[1;34mINFO[m] Google Guice - Extensions - Servlet
> [[1;34mINFO[m] Google Guice - Extensions - Spring
> [[1;34mINFO[m] Google Guice - Extensions - ThrowingProviders
> [[1;34mINFO[m] 
> [[1;34mINFO[m] 
> [1m[m
> [[1;34mINFO[m] [1mBuilding Google Guice 4.0[m
> [[1;34mINFO[m] 
> [1m[m
> [[1;34mINFO[m] 
> [[1;34mINFO[m] [1m--- [0;32mmaven-javadoc-plugin:2.10.4:jar[m 
> [1m(default)[m @ [36mguice-parent[0;1m ---[m
> [[1;34mINFO[m] Not executing Javadoc as the project is not a Java 
> classpath-capable package
> [[1;34mINFO[m] 
> [[1;34mINFO[m] [1m--- [0;32mmaven-javadoc-plugin:2.10.4:jar[m 
> [1m(default-cli)[m @ [36mguice-parent[0;1m ---[m
> [[1;34mINFO[m] Not executing Javadoc as the project is not a Java 
> classpath-capable package
> [[1;34mINFO[m] 
> [[1;34mINFO[m] 
> [1m[m
> [[1;34mINFO[m] [1mBuilding Google Guice - Bill of Materials 4.0[m
> [[1;34mINFO[m] 
> [1m[m
> [[1;34mINFO[m] 
> [[1;34mINFO[m] [1m--- [0;32mmaven-javadoc-plugin:2.10.4:jar[m 
> [1m(default)[m @ [36mguice-bom[0;1m ---[m
> [[1;34mINFO[m] Not executing Javadoc as the project is not a Java 
> classpath-capable package
> [[1;34mINFO[m] 
> [[1;34mINFO[m] [1m--- [0;32mmaven-javadoc-plugin:2.10.4:jar[m 
> [1m(default-cli)[m @ [36mguice-bom[0;1m ---[m
> [[1;34mINFO[m] Not executing Javadoc as the project is not a Java 
> classpath-capable package
> [[1;34mINFO[m] 
> [[1;34mINFO[m] 
> [1m[m
> [[1;34mINFO[m] [1mBuilding Google Guice - Core Library 4.0[m
> [[1;34mINFO[m] 
> [1m[m
> [[1;33mWARNING[m] The artifact org.springframework:spring-beans:jar:3.x has 
> been relocated to org.springframework:

Bug#869016: pyqt5: FTBFS: build-dependency not installable: qtwebengine5-dev (>= 5.7.1+dfsg-3~)

2017-07-19 Thread Lucas Nussbaum

Source: pyqt5
Version: 5.7+dfsg-5
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170719 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):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 9), dh-python, dpkg-dev (>= 1.16.1~), 
> libdbus-1-dev (>= 1.0.2), libglib2.0-dev, libicu-dev, libpulse-dev, 
> libqt5opengl5-dev (>= 5.7.0), libqt5sensors5-dev (>= 5.7.0), 
> libqt5serialport5-dev (>= 5.7.0), libqt5svg5-dev (>= 5.7.0), 
> libqt5webchannel5-dev (>= 5.7.1), libqt5webkit5-dev (>= 5.7.0), 
> libqt5websockets5-dev (>= 5.7.0), libqt5x11extras5-dev (>= 5.7.0), 
> libqt5xmlpatterns5-dev (>= 5.7.0), libsqlite3-dev, libudev-dev, libxml2-dev, 
> libxslt1-dev, python-all-dbg, python-all-dev (>= 2.6.6-3~), python-dbus, 
> python-dbus-dbg, python-dbus-dev, python-sip-dbg, python-sip-dev (>= 4.18), 
> python3-all-dbg, python3-all-dev (>= 3.3.2-5~), python3-dbus, 
> python3-dbus-dbg, python3-sip-dbg, python3-sip-dev (>= 4.18), 
> qtdeclarative5-dev (>= 5.7.0), qtlocation5-dev (>= 5.7.0), qtmultimedia5-dev 
> (>= 5.7.0), qtpositioning5-dev (>= 5.7.0), qttools5-dev (>= 5.7.0), 
> qtwebengine5-dev (>= 5.7.1+dfsg-3~), fdupes, python3-sphinx (>= 1.3)
> Filtered Build-Depends: debhelper (>= 9), dh-python, dpkg-dev (>= 1.16.1~), 
> libdbus-1-dev (>= 1.0.2), libglib2.0-dev, libicu-dev, libpulse-dev, 
> libqt5opengl5-dev (>= 5.7.0), libqt5sensors5-dev (>= 5.7.0), 
> libqt5serialport5-dev (>= 5.7.0), libqt5svg5-dev (>= 5.7.0), 
> libqt5webchannel5-dev (>= 5.7.1), libqt5webkit5-dev (>= 5.7.0), 
> libqt5websockets5-dev (>= 5.7.0), libqt5x11extras5-dev (>= 5.7.0), 
> libqt5xmlpatterns5-dev (>= 5.7.0), libsqlite3-dev, libudev-dev, libxml2-dev, 
> libxslt1-dev, python-all-dbg, python-all-dev (>= 2.6.6-3~), python-dbus, 
> python-dbus-dbg, python-dbus-dev, python-sip-dbg, python-sip-dev (>= 4.18), 
> python3-all-dbg, python3-all-dev (>= 3.3.2-5~), python3-dbus, 
> python3-dbus-dbg, python3-sip-dbg, python3-sip-dev (>= 4.18), 
> qtdeclarative5-dev (>= 5.7.0), qtlocation5-dev (>= 5.7.0), qtmultimedia5-dev 
> (>= 5.7.0), qtpositioning5-dev (>= 5.7.0), qttools5-dev (>= 5.7.0), 
> qtwebengine5-dev (>= 5.7.1+dfsg-3~), fdupes, python3-sphinx (>= 1.3)
> dpkg-deb: building package 'sbuild-build-depends-pyqt5-dummy' in 
> '/<>/resolver-Yj9i1S/apt_archive/sbuild-build-depends-pyqt5-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-core-dummy 
> sbuild-build-depends-pyqt5-dummy
> dpkg-scanpackages: info: Wrote 2 entries to output Packages file.
> Ign:1 copy:/<>/resolver-Yj9i1S/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-Yj9i1S/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/resolver-Yj9i1S/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-Yj9i1S/apt_archive ./ Sources [815 B]
> Get:5 copy:/<>/resolver-Yj9i1S/apt_archive ./ Packages [864 B]
> Fetched 2642 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install pyqt5 build dependencies (apt-based resolver)
> -
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-pyqt5-dummy : Depends: qtwebengine5-dev (>= 
> 5.7.1+dfsg-3~) but it is not going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://aws-logs.debian.net/2017/07/19/pyqt5_5.7+dfsg-5_unstable.log

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 EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Bug#869017: powermock: FTBFS: find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers//.jar': No such file or directory

2017-07-19 Thread Lucas Nussbaum

Source: powermock
Version: 1.6.6-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170719 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):
>  debian/rules build
> dh build
>dh_testdir
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compiler/*/*.jar': No 
> such file or directory
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compilers/*/*.jar': 
> No such file or directory
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': 
> No such file or directory
>   mh_patchpoms -plibpowermock-java --debian-build --keep-pom-version 
> --maven-repo=/<>/debian/maven-repo
>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
> [[1;34mINFO[m] Scanning for projects...
> [[1;34mINFO[m] 
> [1m[m
> [[1;34mINFO[m] [1mReactor Build Order:[m
> [[1;34mINFO[m] 
> [[1;34mINFO[m] powermock
> [[1;34mINFO[m] powermock-reflect
> [[1;34mINFO[m] powermock-core
> [[1;34mINFO[m] powermock-api
> [[1;34mINFO[m] powermock-api-support
> [[1;34mINFO[m] powermock-api-easymock
> [[1;34mINFO[m] powermock-api-mockito-common
> [[1;34mINFO[m] powermock-api-mockito
> [[1;34mINFO[m] powermock-modules
> [[1;34mINFO[m] powermock-module-junit4-common
> [[1;34mINFO[m] powermock-module-junit4
> [[1;34mINFO[m] powermock-classloading-base
> [[1;34mINFO[m] powermock-module-junit4-rule
> [[1;34mINFO[m] powermock-module-javaagent
> [[1;34mINFO[m] powermock-module-junit4-rule-agent
> [[1;34mINFO[m] powermock-module-testng-common
> [[1;34mINFO[m] powermock-module-testng
> [[1;34mINFO[m] powermock-module-testng-agent
> [[1;34mINFO[m] powermock-modules-impl
> [[1;34mINFO[m] powermock-classloading-module
> [[1;34mINFO[m] powermock-classloading-objenesis
> [[1;34mINFO[m] powermock-classloading-xstream
> [[1;34mINFO[m] 
> [[1;34mINFO[m] 
> [1m[m
> [[1;34mINFO[m] [1mBuilding powermock 1.6.6[m
> [[1;34mINFO[m] 
> [1m[m
> [[1;34mINFO[m] 
> [[1;34mINFO[m] [1m--- [0;32mmaven-bundle-plugin:2.5.4:manifest[m 
> [1m(bundle-manifest)[m @ [36mpowermock[0;1m ---[m
> [[1;33mWARNING[m] Ignoring project type pom - supportedProjectTypes = [jar, 
> bundle]
> [[1;34mINFO[m] 
> [[1;34mINFO[m] 
> [1m[m
> [[1;34mINFO[m] [1mBuilding powermock-reflect 1.6.6[m
> [[1;34mINFO[m] 
> [1m[m
> [[1;34mINFO[m] 
> [[1;34mINFO[m] [1m--- [0;32mmaven-resources-plugin:3.0.0:resources[m 
> [1m(default-resources)[m @ [36mpowermock-reflect[0;1m ---[m
> [[1;33mWARNING[m] Using platform encoding (ANSI_X3.4-1968 actually) to copy 
> filtered resources, i.e. build is platform dependent!
> [[1;34mINFO[m] skip non existing resourceDirectory 
> /<>/reflect/src/main/resources
> [[1;34mINFO[m] 
> [[1;34mINFO[m] [1m--- [0;32mmaven-compiler-plugin:3.6.1:compile[m 
> [1m(default-compile)[m @ [36mpowermock-reflect[0;1m ---[m
> [[1;33mWARNING[m] The POM for 
> org.codehaus.plexus:plexus-compiler-api:jar:2.x is invalid, transitive 
> dependencies (if any) will not be available, enable debug logging for more 
> details
> [[1;33mWARNING[m] The POM for 
> org.codehaus.plexus:plexus-compiler-javac:jar:2.x is invalid, transitive 
> dependencies (if any) will not be available, enable debug logging for more 
> details
> [[1;34mINFO[m] Changes detected - recompiling the module!
> [[1;33mWARNING[m] File encoding has not been set, using platform encoding 
> ANSI_X3.4-1968, i.e. build is platform dependent!
> [[1;34mINFO[m] Compiling 27 source files to 
> /<>/reflect/target/classes
> [[1;34mINFO[m] 
> /<>/reflect/src/main

Bug#869006: jnr-unixsocket: FTBFS: find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers//.jar': No such file or directory

2017-07-19 Thread Lucas Nussbaum

Source: jnr-unixsocket
Version: 0.18-2
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170719 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):
>  debian/rules build
> dh build --buildsystem=maven --with javahelper
>dh_testdir -O--buildsystem=maven
>dh_update_autotools_config -O--buildsystem=maven
>dh_autoreconf -O--buildsystem=maven
>dh_auto_configure -O--buildsystem=maven
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compiler/*/*.jar': No 
> such file or directory
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compilers/*/*.jar': 
> No such file or directory
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': 
> No such file or directory
>   mh_patchpoms -plibjnr-unixsocket-java --debian-build --keep-pom-version 
> --maven-repo=/<>/debian/maven-repo
> Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8
>jh_linkjars -O--buildsystem=maven
>dh_auto_build -O--buildsystem=maven
>   /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 
> org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
> -Dmaven.repo.local=/<>/debian/maven-repo package javadoc:jar 
> javadoc:aggregate -DskipTests -Dnotimestamp=true -Dlocale=en_US
> Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8
> [[1;34mINFO[m] Scanning for projects...
> [[1;34mINFO[m] 
> [[1;34mINFO[m] 
> [1m[m
> [[1;34mINFO[m] [1mBuilding jnr-unixsocket 0.18[m
> [[1;34mINFO[m] 
> [1m[m
> [[1;34mINFO[m] 
> [[1;34mINFO[m] [1m--- [0;32mmaven-resources-plugin:3.0.0:resources[m 
> [1m(default-resources)[m @ [36mjnr-unixsocket[0;1m ---[m
> [[1;33mWARNING[m] Using platform encoding (UTF-8 actually) to copy filtered 
> resources, i.e. build is platform dependent!
> [[1;34mINFO[m] skip non existing resourceDirectory 
> /<>/src/main/resources
> [[1;34mINFO[m] 
> [[1;34mINFO[m] [1m--- [0;32mmaven-compiler-plugin:3.6.1:compile[m 
> [1m(default-compile)[m @ [36mjnr-unixsocket[0;1m ---[m
> [[1;33mWARNING[m] The POM for 
> org.codehaus.plexus:plexus-compiler-api:jar:2.x is invalid, transitive 
> dependencies (if any) will not be available, enable debug logging for more 
> details
> [[1;33mWARNING[m] The POM for 
> org.codehaus.plexus:plexus-compiler-javac:jar:2.x is invalid, transitive 
> dependencies (if any) will not be available, enable debug logging for more 
> details
> [[1;34mINFO[m] Changes detected - recompiling the module!
> [[1;33mWARNING[m] File encoding has not been set, using platform encoding 
> UTF-8, i.e. build is platform dependent!
> [[1;34mINFO[m] Compiling 17 source files to /<>/target/classes
> [[1;34mINFO[m] /<>/src/main/java/jnr/unixsocket/Common.java: 
> /<>/src/main/java/jnr/unixsocket/Common.java uses unchecked or 
> unsafe operations.
> [[1;34mINFO[m] /<>/src/main/java/jnr/unixsocket/Common.java: 
> Recompile with -Xlint:unchecked for details.
> [[1;34mINFO[m] 
> [[1;34mINFO[m] [1m--- [0;32mmaven-bundle-plugin:2.5.4:manifest[m 
> [1m(bundle-manifest)[m @ [36mjnr-unixsocket[0;1m ---[m
> [[1;34mINFO[m] 
> [[1;34mINFO[m] [1m--- [0;32mmaven-resources-plugin:3.0.0:testResources[m 
> [1m(default-testResources)[m @ [36mjnr-unixsocket[0;1m ---[m
> [[1;33mWARNING[m] Using platform encoding (UTF-8 actually) to copy filtered 
> resources, i.e. build is platform dependent!
> [[1;34mINFO[m] Copying 1 resource
> [[1;34mINFO[m] 
> [[1;34mINFO[m] [1m--- [0;32mmaven-compiler-plugin:3.6.1:testCompile[m 
> [1m(default-testCompile)[m @ [36mjnr-unixsocket[0;1m ---[m
> [[1;34mINFO[m] Changes detected - recompiling the module!
> [[1;33mWARNING[m] File encoding has not been set, using platform encoding 
> UTF-8, i.e. build is platform dependent!
> [[1;34mINFO[m] Compiling 10 source files to 
> /<>/target/test-classes
> [[1;34mINFO[m] 
> /<>/src/test/java/jnr/unixsocket/UnixDatagramChannelTest.java: 
> Some input files use or override a deprecated API.
> [[1;34mINFO[m] 
> /<>/src/test/java/jnr/unixsocket/UnixDatagramChannelTest.java: 
> Recompile with -Xlint:deprecation for details.
> [

Bug#869011: maven-install-plugin: FTBFS: dh_auto_test: /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

2017-07-19 Thread Lucas Nussbaum

Source: maven-install-plugin
Version: 2.5.2-2
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170719 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):
>  debian/rules build
> dh build
>dh_testdir
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compiler/*/*.jar': No 
> such file or directory
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compilers/*/*.jar': 
> No such file or directory
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': 
> No such file or directory
>   mh_patchpoms -plibmaven-install-plugin-java --debian-build 
> --keep-pom-version --maven-repo=/<>/debian/maven-repo
>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
> [[1;34mINFO[m] Scanning for projects...
> [[1;34mINFO[m] 
> [[1;34mINFO[m] 
> [1m[m
> [[1;34mINFO[m] [1mBuilding Apache Maven Install Plugin 2.5.2[m
> [[1;34mINFO[m] 
> [1m[m
> [[1;34mINFO[m] 
> [[1;34mINFO[m] [1m--- [0;32mmaven-resources-plugin:3.0.0:resources[m 
> [1m(default-resources)[m @ [36mmaven-install-plugin[0;1m ---[m
> [[1;33mWARNING[m] Using platform encoding (ANSI_X3.4-1968 actually) to copy 
> filtered resources, i.e. build is platform dependent!
> [[1;34mINFO[m] skip non existing resourceDirectory 
> /<>/src/main/resources
> [[1;34mINFO[m] 
> [[1;34mINFO[m] [1m--- [0;32mmaven-compiler-plugin:3.6.1:compile[m 
> [1m(default-compile)[m @ [36mmaven-install-plugin[0;1m ---[m
> [[1;33mWARNING[m] The POM for 
> org.codehaus.plexus:plexus-compiler-api:jar:2.x is invalid, transitive 
> dependencies (if any) will not be available, enable debug logging for more 
> details
> [[1;33mWARNING[m] The POM for 
> org.codehaus.plexus:plexus-compiler-javac:jar:2.x is invalid, transitive 
> dependencies (if any) will not be available, enable debug logging for more 
> details
> [[1;34mINFO[m] Changes detected - recompiling the module!
> [[1;33mWARNING[m] File encoding has not been set, using platform encoding 
> ANSI_X3.4-1968, i.e. build is platform dependent!
> [[1;34mINFO[m] Compiling 5 source files to /<>/target/classes
> [[1;34mINFO[m] 
> /<>/src/main/java/org/apache/maven/plugin/install/InstallFileMojo.java:
>  
> /<>/src/main/java/org/apache/maven/plugin/install/InstallFileMojo.java
>  uses or overrides a deprecated API.
> [[1;34mINFO[m] 
> /<>/src/main/java/org/apache/maven/plugin/install/InstallFileMojo.java:
>  Recompile with -Xlint:deprecation for details.
> [[1;34mINFO[m] 
> [[1;34mINFO[m] [1m--- [0;32mmaven-plugin-plugin:3.5:descriptor[m 
> [1m(default-descriptor)[m @ [36mmaven-install-plugin[0;1m ---[m
> [[1;33mWARNING[m] Using platform encoding (ANSI_X3.4-1968 actually) to read 
> mojo source files, i.e. build is platform dependent!
> [[1;34mINFO[m] java-javadoc mojo extractor found 0 mojo descriptor.
> [[1;34mINFO[m] java-annotations mojo extractor found 2 mojo descriptors.
> [[1;34mINFO[m] 
> [[1;34mINFO[m] [1m--- [0;32mmaven-plugin-plugin:3.5:descriptor[m 
> [1m(mojo-descriptor)[m @ [36mmaven-install-plugin[0;1m ---[m
> [[1;33mWARNING[m] Using platform encoding (ANSI_X3.4-1968 actually) to read 
> mojo source files, i.e. build is platform dependent!
> [[1;34mINFO[m] java-javadoc mojo extractor found 0 mojo descriptor.
> [[1;34mINFO[m] java-annotations mojo extractor found 2 mojo descriptors.
> [[1;34mINFO[m] 
> [[1;34mINFO[m] [1m--- [0;32mmaven-resources-plugin:3.0.0:testResources[m 
> [1m(default-testResources)[m @ [36mmaven-install-plugin[0;1m ---[m
> [[1;33mWARNING[m] Using platform encoding (ANSI_X3.4-1968 actually) to copy 
> filtered resources, i.e. build is platform dependent!
> [[1;34mINFO[m] Copying 22 resources
> [[1;34mINFO[m] 
> [[1;34mINFO[m] [1m--- [0;32mmaven-compiler-plugin:3.6.1:test

Bug#869007: libslf4j-java: FTBFS: find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers//.jar': No such file or directory

2017-07-19 Thread Lucas Nussbaum

Source: libslf4j-java
Version: 1.7.25-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170719 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):
>  debian/rules build
> dh build
>dh_testdir
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compiler/*/*.jar': No 
> such file or directory
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compilers/*/*.jar': 
> No such file or directory
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': 
> No such file or directory
>   mh_patchpoms -plibslf4j-java --debian-build --keep-pom-version 
> --maven-repo=/<>/debian/maven-repo
>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 
> 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
> [[1;34mINFO[m] Scanning for projects...
> [[1;33mWARNING[m] 
> [[1;33mWARNING[m] Some problems were encountered while building the 
> effective model for org.slf4j:slf4j-api:jar:1.7.25
> [[1;33mWARNING[m] Reporting configuration should be done in  
> section, not in maven-site-plugin  as reportPlugins parameter.
> [[1;33mWARNING[m] 
> [[1;33mWARNING[m] Some problems were encountered while building the 
> effective model for org.slf4j:slf4j-simple:jar:1.7.25
> [[1;33mWARNING[m] Reporting configuration should be done in  
> section, not in maven-site-plugin  as reportPlugins parameter.
> [[1;33mWARNING[m] 
> [[1;33mWARNING[m] Some problems were encountered while building the 
> effective model for org.slf4j:slf4j-nop:jar:1.7.25
> [[1;33mWARNING[m] Reporting configuration should be done in  
> section, not in maven-site-plugin  as reportPlugins parameter.
> [[1;33mWARNING[m] 
> [[1;33mWARNING[m] Some problems were encountered while building the 
> effective model for org.slf4j:slf4j-jdk14:jar:1.7.25
> [[1;33mWARNING[m] Reporting configuration should be done in  
> section, not in maven-site-plugin  as reportPlugins parameter.
> [[1;33mWARNING[m] 
> [[1;33mWARNING[m] Some problems were encountered while building the 
> effective model for org.slf4j:slf4j-log4j12:jar:1.7.25
> [[1;33mWARNING[m] Reporting configuration should be done in  
> section, not in maven-site-plugin  as reportPlugins parameter.
> [[1;33mWARNING[m] 
> [[1;33mWARNING[m] Some problems were encountered while building the 
> effective model for org.slf4j:slf4j-jcl:jar:1.7.25
> [[1;33mWARNING[m] Reporting configuration should be done in  
> section, not in maven-site-plugin  as reportPlugins parameter.
> [[1;33mWARNING[m] 
> [[1;33mWARNING[m] Some problems were encountered while building the 
> effective model for org.slf4j:jcl-over-slf4j:jar:1.7.25
> [[1;33mWARNING[m] Reporting configuration should be done in  
> section, not in maven-site-plugin  as reportPlugins parameter.
> [[1;33mWARNING[m] 
> [[1;33mWARNING[m] Some problems were encountered while building the 
> effective model for org.slf4j:log4j-over-slf4j:jar:1.7.25
> [[1;33mWARNING[m] Reporting configuration should be done in  
> section, not in maven-site-plugin  as reportPlugins parameter.
> [[1;33mWARNING[m] 
> [[1;33mWARNING[m] Some problems were encountered while building the 
> effective model for org.slf4j:jul-to-slf4j:jar:1.7.25
> [[1;33mWARNING[m] Reporting configuration should be done in  
> section, not in maven-site-plugin  as reportPlugins parameter.
> [[1;33mWARNING[m] 
> [[1;33mWARNING[m] Some problems were encountered while building the 
> effective model for org.slf4j:slf4j-migrator:jar:1.7.25
> [[1;33mWARNING[m] Reporting configuration should be done in  
> section, not in maven-site-plugin  as reportPlugins parameter.
> [[1;33mWARNING[m] 
> [[1;33mWARNING[m] Some problems were encountered while building the 
> effective model for org.slf4j:slf4j-parent:pom:1.7.25
> [[1;33mWARNING[m] Reporting configuration should be done in  
> section, not in maven-site-plugin  as reportPlugins parameter. 
> @ line 180, column 20
> [[1;33mWARNING[m] 
> [[1;33mWARNING[m] It is highly recommended to fix these problems because 
> they threaten the stability of your build.
> [[1;

Bug#869005: plexus-utils2: FTBFS: find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers//.jar': No such file or directory

2017-07-19 Thread Lucas Nussbaum

Source: plexus-utils2
Version: 3.0.24-2
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170719 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):
>  debian/rules build
> dh build
>dh_testdir
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compiler/*/*.jar': No 
> such file or directory
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compilers/*/*.jar': 
> No such file or directory
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': 
> No such file or directory
>   mh_patchpoms -plibplexus-utils2-java --debian-build --keep-pom-version 
> --maven-repo=/<>/debian/maven-repo
>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 
> org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
> -Dmaven.repo.local=/<>/debian/maven-repo package javadoc:jar 
> javadoc:aggregate -DskipTests -Dnotimestamp=true -Dlocale=en_US
> [[1;34mINFO[m] Scanning for projects...
> [[1;33mWARNING[m] The POM for 
> org.apache.maven.plugins:maven-install-plugin:jar:2.5.2 is missing, no 
> dependency information available
> [[1;33mWARNING[m] Failed to retrieve plugin descriptor for 
> org.apache.maven.plugins:maven-install-plugin:2.5.2: Plugin 
> org.apache.maven.plugins:maven-install-plugin:2.5.2 or one of its 
> dependencies could not be resolved: Cannot access central 
> (https://repo.maven.apache.org/maven2) in offline mode and the artifact 
> org.apache.maven.plugins:maven-install-plugin:jar:2.5.2 has not been 
> downloaded from it before.
> [[1;33mWARNING[m] The POM for 
> org.apache.maven.plugins:maven-deploy-plugin:jar:2.7 is missing, no 
> dependency information available
> [[1;33mWARNING[m] Failed to retrieve plugin descriptor for 
> org.apache.maven.plugins:maven-deploy-plugin:2.7: Plugin 
> org.apache.maven.plugins:maven-deploy-plugin:2.7 or one of its dependencies 
> could not be resolved: Cannot access central 
> (https://repo.maven.apache.org/maven2) in offline mode and the artifact 
> org.apache.maven.plugins:maven-deploy-plugin:jar:2.7 has not been downloaded 
> from it before.
> [[1;33mWARNING[m] The POM for 
> org.apache.maven.plugins:maven-site-plugin:jar:3.3 is missing, no dependency 
> information available
> [[1;33mWARNING[m] Failed to retrieve plugin descriptor for 
> org.apache.maven.plugins:maven-site-plugin:3.3: Plugin 
> org.apache.maven.plugins:maven-site-plugin:3.3 or one of its dependencies 
> could not be resolved: Cannot access central 
> (https://repo.maven.apache.org/maven2) in offline mode and the artifact 
> org.apache.maven.plugins:maven-site-plugin:jar:3.3 has not been downloaded 
> from it before.
> [[1;33mWARNING[m] The POM for 
> org.apache.maven.plugins:maven-antrun-plugin:jar:1.8 is missing, no 
> dependency information available
> [[1;33mWARNING[m] Failed to retrieve plugin descriptor for 
> org.apache.maven.plugins:maven-antrun-plugin:1.8: Plugin 
> org.apache.maven.plugins:maven-antrun-plugin:1.8 or one of its dependencies 
> could not be resolved: Cannot access central 
> (https://repo.maven.apache.org/maven2) in offline mode and the artifact 
> org.apache.maven.plugins:maven-antrun-plugin:jar:1.8 has not been downloaded 
> from it before.
> [[1;33mWARNING[m] The POM for 
> org.apache.maven.plugins:maven-assembly-plugin:jar:2.4.1 is missing, no 
> dependency information available
> [[1;33mWARNING[m] Failed to retrieve plugin descriptor for 
> org.apache.maven.plugins:maven-assembly-plugin:2.4.1: Plugin 
> org.apache.maven.plugins:maven-assembly-plugin:2.4.1 or one of its 
> dependencies could not be resolved: Cannot access central 
> (https://repo.maven.apache.org/maven2) in offline mode and the artifact 
> org.apache.maven.plugins:maven-assembly-plugin:jar:2.4.1 has not been 
> downloaded from it before.
> [[1;33mWARNING[m] The POM for 
> org.apache.maven.plugins:maven-dependency-plugin:jar:2.8 is missing, no 
> dependency information available
> [[1;33mWARNING[m] Failed to retrieve plugin descriptor for 
> org.apache.maven.plugins:maven-dependency-plugin:2.8: Plugin 
> org.apache.maven.plugins:maven-dependency-plugin:2.8 or one of its 
> dependencies could not be resolved: Cannot access central 
> (http

Bug#869008: qtwebengine-opensource-src: FTBFS: unsatisfiable build-dependencies: libqt5opengl5-dev (>= 5.9.0~), libqt5webchannel5-dev (>= 5.9.0~), libqt5xmlpatterns5-dev (>= 5.9.0~), qtbase5-private-d

2017-07-19 Thread Lucas Nussbaum

Source: qtwebengine-opensource-src
Version: 5.9.0+dfsg-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170719 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):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: autotools-dev, bison, chrpath, closure-compiler, 
> debhelper (>= 10), dh-autoreconf, flex, gperf, yasm, ninja-build, 
> khronos-api, libasound2-dev, libavcodec-dev, libavformat-dev, libavutil-dev, 
> libcap-dev, libdbus-1-dev, libegl1-mesa-dev, libgl1-mesa-dri, libevent-dev, 
> libflac-dev, libfontconfig1-dev, libgl1-mesa-dev | libgl-dev, libglib2.0-dev, 
> libglu1-mesa-dev | libglu-dev, libgstreamer-plugins-base1.0-dev, 
> libgstreamer1.0-dev, libharfbuzz-dev, libicu-dev, libjpeg-dev, 
> libjsoncpp-dev, libminizip-dev, libnss3-dev, libopus-dev, liblcms2-dev, 
> libpci-dev, libpng-dev, libprotobuf-dev, libpulse-dev, libqt5opengl5-dev (>= 
> 5.9.0~), libqt5webchannel5-dev (>= 5.9.0~), libqt5xmlpatterns5-dev (>= 
> 5.9.0~), libre2-dev (>= 20161101+dfsg-2), libsnappy-dev, libsqlite3-dev, 
> libsrtp-dev, libusb-1.0-0-dev, libvpx-dev, libwebp-dev, libxcomposite-dev, 
> libxcursor-dev, libxml2-dev, libxnvctrl-dev, libxrandr-dev, libxrender-dev, 
> libxslt1-dev, libxss-dev, libxtst-dev, mesa-common-dev, pkg-config, 
> pkg-kde-tools, protobuf-compiler, python, qtbase5-private-dev (>= 5.9.0~), 
> qtdeclarative5-private-dev (>= 5.9.0~), qtlocation5-dev, 
> qtscript5-private-dev (>= 5.9.0~), re2c, ruby, xauth, xvfb, yui-compressor, 
> libqt5sql5-sqlite (>= 5.9.0~), qtbase5-doc-html (>= 5.9.0~), 
> qttools5-dev-tools (>= 5.9.0~)
> Filtered Build-Depends: autotools-dev, bison, chrpath, closure-compiler, 
> debhelper (>= 10), dh-autoreconf, flex, gperf, yasm, ninja-build, 
> khronos-api, libasound2-dev, libavcodec-dev, libavformat-dev, libavutil-dev, 
> libcap-dev, libdbus-1-dev, libegl1-mesa-dev, libgl1-mesa-dri, libevent-dev, 
> libflac-dev, libfontconfig1-dev, libgl1-mesa-dev, libglib2.0-dev, 
> libglu1-mesa-dev, libgstreamer-plugins-base1.0-dev, libgstreamer1.0-dev, 
> libharfbuzz-dev, libicu-dev, libjpeg-dev, libjsoncpp-dev, libminizip-dev, 
> libnss3-dev, libopus-dev, liblcms2-dev, libpci-dev, libpng-dev, 
> libprotobuf-dev, libpulse-dev, libqt5opengl5-dev (>= 5.9.0~), 
> libqt5webchannel5-dev (>= 5.9.0~), libqt5xmlpatterns5-dev (>= 5.9.0~), 
> libre2-dev (>= 20161101+dfsg-2), libsnappy-dev, libsqlite3-dev, libsrtp-dev, 
> libusb-1.0-0-dev, libvpx-dev, libwebp-dev, libxcomposite-dev, libxcursor-dev, 
> libxml2-dev, libxnvctrl-dev, libxrandr-dev, libxrender-dev, libxslt1-dev, 
> libxss-dev, libxtst-dev, mesa-common-dev, pkg-config, pkg-kde-tools, 
> protobuf-compiler, python, qtbase5-private-dev (>= 5.9.0~), 
> qtdeclarative5-private-dev (>= 5.9.0~), qtlocation5-dev, 
> qtscript5-private-dev (>= 5.9.0~), re2c, ruby, xauth, xvfb, yui-compressor, 
> libqt5sql5-sqlite (>= 5.9.0~), qtbase5-doc-html (>= 5.9.0~), 
> qttools5-dev-tools (>= 5.9.0~)
> dpkg-deb: building package 
> 'sbuild-build-depends-qtwebengine-opensource-src-dummy' in 
> '/<>/resolver-jqtx5w/apt_archive/sbuild-build-depends-qtwebengine-opensource-src-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-core-dummy 
> sbuild-build-depends-qtwebengine-opensource-src-dummy
> dpkg-scanpackages: info: Wrote 2 entries to output Packages file.
> Ign:1 copy:/<>/resolver-jqtx5w/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-jqtx5w/apt_archive ./ Release [969 B]
> Ign:3 copy:/<>/resolver-jqtx5w/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-jqtx5w/apt_archive ./ Sources [1070 B]
> Get:5 copy:/<>/resolver-jqtx5w/apt_archive ./ Packages [1067 B]
> Fetched 3106 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install qtwebengine-opensource-src build dependencies (apt-based resolver)
> --
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribu

Bug#869000: maven-invoker-plugin: FTBFS: dh_auto_test: /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

2017-07-19 Thread Lucas Nussbaum

Source: maven-invoker-plugin
Version: 2.0.0-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170719 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):
>  debian/rules build
> dh build --buildsystem=maven
>dh_testdir -O--buildsystem=maven
>dh_update_autotools_config -O--buildsystem=maven
>dh_auto_configure -O--buildsystem=maven
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compiler/*/*.jar': No 
> such file or directory
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compilers/*/*.jar': 
> No such file or directory
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': 
> No such file or directory
>   mh_patchpoms -plibmaven-invoker-plugin-java --debian-build 
> --keep-pom-version --maven-repo=/<>/debian/maven-repo
>dh_auto_build -O--buildsystem=maven
>   /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 
> 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
> [[1;34mINFO[m] Scanning for projects...
> [[1;34mINFO[m] 
> [[1;34mINFO[m] 
> [1m[m
> [[1;34mINFO[m] [1mBuilding Apache Maven Invoker Plugin 2.0.0[m
> [[1;34mINFO[m] 
> [1m[m
> [[1;34mINFO[m] 
> [[1;34mINFO[m] [1m--- [0;32mmodello-maven-plugin:1.9.1:xpp3-reader[m 
> [1m(standard)[m @ [36mmaven-invoker-plugin[0;1m ---[m
> [[1;34mINFO[m] outputDirectory: 
> /<>/target/generated-sources/modello
> [[1;34mINFO[m] Working on model: src/main/mdo/invocation.mdo
> [[1;34mINFO[m] Generating current version: 1.0.0
> [[1;34mINFO[m] 
> [[1;34mINFO[m] [1m--- [0;32mmodello-maven-plugin:1.9.1:xpp3-writer[m 
> [1m(standard)[m @ [36mmaven-invoker-plugin[0;1m ---[m
> [[1;34mINFO[m] outputDirectory: 
> /<>/target/generated-sources/modello
> [[1;34mINFO[m] Working on model: src/main/mdo/invocation.mdo
> [[1;34mINFO[m] Generating current version: 1.0.0
> [[1;34mINFO[m] 
> [[1;34mINFO[m] [1m--- [0;32mmodello-maven-plugin:1.9.1:java[m 
> [1m(standard)[m @ [36mmaven-invoker-plugin[0;1m ---[m
> [[1;34mINFO[m] outputDirectory: 
> /<>/target/generated-sources/modello
> [[1;34mINFO[m] Working on model: src/main/mdo/invocation.mdo
> [[1;34mINFO[m] Generating current version: 1.0.0
> [[1;34mINFO[m] 
> [[1;34mINFO[m] [1m--- [0;32mmaven-resources-plugin:3.0.0:resources[m 
> [1m(default-resources)[m @ [36mmaven-invoker-plugin[0;1m ---[m
> [[1;33mWARNING[m] Using platform encoding (ANSI_X3.4-1968 actually) to copy 
> filtered resources, i.e. build is platform dependent!
> [[1;34mINFO[m] Copying 4 resources
> [[1;34mINFO[m] 
> [[1;34mINFO[m] [1m--- [0;32mmaven-compiler-plugin:3.6.1:compile[m 
> [1m(default-compile)[m @ [36mmaven-invoker-plugin[0;1m ---[m
> [[1;33mWARNING[m] The POM for 
> org.codehaus.plexus:plexus-compiler-api:jar:2.x is invalid, transitive 
> dependencies (if any) will not be available, enable debug logging for more 
> details
> [[1;33mWARNING[m] The POM for 
> org.codehaus.plexus:plexus-compiler-javac:jar:2.x is invalid, transitive 
> dependencies (if any) will not be available, enable debug logging for more 
> details
> [[1;34mINFO[m] Changes detected - recompiling the module!
> [[1;33mWARNING[m] File encoding has not been set, using platform encoding 
> ANSI_X3.4-1968, i.e. build is platform dependent!
> [[1;34mINFO[m] Compiling 18 source files to /<>/target/classes
> [[1;34mINFO[m] 
> /<>/src/main/java/org/apache/maven/plugin/invoker/InstallMojo.java:
>  
> /<>/src/main/java/org/apache/maven/plugin/invoker/InstallMojo.java
>  uses or overrides a deprecated API.
> [[1;34mINFO[m] 
> /<>/src/main/java/org/apache/maven/plugin/invoker/InstallMojo.java:
>  Recompile with -Xlint:deprecation for details.
> [[1;34mINFO[m] 
> /<>/src/main/java/org/apache/maven/plugin/invoker/AbstractInvokerMojo.java:
>  Some input files use unchecked or unsafe operations.
> [[1;34mINFO[m] 
> /<>/src/main/java/org/apache/maven/plugin/invoker/AbstractInvokerMojo.java:
>  Recompile with -Xlint:unc

Bug#869002: apache-log4j2: FTBFS: find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers//.jar': No such file or directory

2017-07-19 Thread Lucas Nussbaum

Source: apache-log4j2
Version: 2.8.2-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170719 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):
>  debian/rules build
> dh build
>dh_testdir
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compiler/*/*.jar': No 
> such file or directory
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compilers/*/*.jar': 
> No such file or directory
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': 
> No such file or directory
>   mh_patchpoms -pliblog4j2-java --debian-build --keep-pom-version 
> --maven-repo=/<>/debian/maven-repo
>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 javadoc:jar 
> javadoc:aggregate -DskipTests -Dnotimestamp=true -Dlocale=en_US
> [[1;34mINFO[m] Scanning for projects...
> [[1;34mINFO[m] 
> [1m[m
> [[1;34mINFO[m] [1mReactor Build Order:[m
> [[1;34mINFO[m] 
> [[1;34mINFO[m] Apache Log4j 2
> [[1;34mINFO[m] Apache Log4j API
> [[1;34mINFO[m] Apache Log4j Core
> [[1;34mINFO[m] Apache Log4j 1.x Compatibility API
> [[1;34mINFO[m] Apache Log4j to SLF4J Adapter
> [[1;34mINFO[m] Apache Log4j Commons Logging Bridge
> [[1;34mINFO[m] Apache Log4j BOM
> [[1;34mINFO[m] Apache Log4j NoSQL
> [[1;34mINFO[m] Apache Log4j Web
> [[1;34mINFO[m] Apache Log4j JUL Adapter
> [[1;33mWARNING[m] The POM for 
> org.apache.maven.plugins:maven-doap-plugin:jar:1.2 is missing, no dependency 
> information available
> [[1;33mWARNING[m] Failed to retrieve plugin descriptor for 
> org.apache.maven.plugins:maven-doap-plugin:1.2: Plugin 
> org.apache.maven.plugins:maven-doap-plugin:1.2 or one of its dependencies 
> could not be resolved: Cannot access apache 
> (https://repository.apache.org/content/repositories/releases/) in offline 
> mode and the artifact org.apache.maven.plugins:maven-doap-plugin:jar:1.2 has 
> not been downloaded from it before.
> [[1;33mWARNING[m] The POM for 
> org.apache.maven.plugins:maven-deploy-plugin:jar:2.7 is missing, no 
> dependency information available
> [[1;33mWARNING[m] Failed to retrieve plugin descriptor for 
> org.apache.maven.plugins:maven-deploy-plugin:2.7: Plugin 
> org.apache.maven.plugins:maven-deploy-plugin:2.7 or one of its dependencies 
> could not be resolved: Cannot access apache 
> (https://repository.apache.org/content/repositories/releases/) in offline 
> mode and the artifact org.apache.maven.plugins:maven-deploy-plugin:jar:2.7 
> has not been downloaded from it before.
> [[1;33mWARNING[m] The POM for 
> org.apache.maven.plugins:maven-antrun-plugin:jar:1.8 is missing, no 
> dependency information available
> [[1;33mWARNING[m] Failed to retrieve plugin descriptor for 
> org.apache.maven.plugins:maven-antrun-plugin:1.8: Plugin 
> org.apache.maven.plugins:maven-antrun-plugin:1.8 or one of its dependencies 
> could not be resolved: Cannot access apache 
> (https://repository.apache.org/content/repositories/releases/) in offline 
> mode and the artifact org.apache.maven.plugins:maven-antrun-plugin:jar:1.8 
> has not been downloaded from it before.
> [[1;33mWARNING[m] The POM for 
> org.apache.maven.plugins:maven-assembly-plugin:jar:2.4.1 is missing, no 
> dependency information available
> [[1;33mWARNING[m] Failed to retrieve plugin descriptor for 
> org.apache.maven.plugins:maven-assembly-plugin:2.4.1: Plugin 
> org.apache.maven.plugins:maven-assembly-plugin:2.4.1 or one of its 
> dependencies could not be resolved: Cannot access apache 
> (https://repository.apache.org/content/repositories/releases/) in offline 
> mode and the artifact 
> org.apache.maven.plugins:maven-assembly-plugin:jar:2.4.1 has not been 
> downloaded from it before.
> [[1;33mWARNING[m] The POM for 
> org.apache.maven.plugins:maven-dependency-plugin:jar:2.8 is missing, no 
> dependency information available
> [[1;33mWARNING[m] Failed to retrieve plugin descriptor for 
> org.apache.maven.plugins:maven-depende

Bug#869010: cglib: FTBFS: find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers//.jar': No such file or directory

2017-07-19 Thread Lucas Nussbaum

Source: cglib
Version: 3.2.5-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170719 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):
>  debian/rules build
> dh build --buildsystem=maven
>dh_testdir -O--buildsystem=maven
>dh_update_autotools_config -O--buildsystem=maven
>dh_auto_configure -O--buildsystem=maven
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compiler/*/*.jar': No 
> such file or directory
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compilers/*/*.jar': 
> No such file or directory
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': 
> No such file or directory
>   mh_patchpoms -plibcglib-java --debian-build --keep-pom-version 
> --maven-repo=/<>/debian/maven-repo
>dh_auto_build -O--buildsystem=maven
>   /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 
> org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
> -Dmaven.repo.local=/<>/debian/maven-repo package javadoc:jar 
> javadoc:aggregate -DskipTests -Dnotimestamp=true -Dlocale=en_US
> [[1;34mINFO[m] Scanning for projects...
> [[1;33mWARNING[m] 
> [[1;33mWARNING[m] Some problems were encountered while building the 
> effective model for cglib:cglib-nodep:jar:3.2.5
> [[1;33mWARNING[m] 'build.plugins.plugin.version' for 
> org.sonatype.plugins:jarjar-maven-plugin is missing. @ line 27, column 12
> [[1;33mWARNING[m] 
> [[1;33mWARNING[m] It is highly recommended to fix these problems because 
> they threaten the stability of your build.
> [[1;33mWARNING[m] 
> [[1;33mWARNING[m] For this reason, future Maven versions might no longer 
> support building such malformed projects.
> [[1;33mWARNING[m] 
> [[1;34mINFO[m] 
> [1m[m
> [[1;34mINFO[m] [1mReactor Build Order:[m
> [[1;34mINFO[m] 
> [[1;34mINFO[m] Code Generation Library
> [[1;34mINFO[m] cglib
> [[1;34mINFO[m] cglib-nodep
> [[1;33mWARNING[m] The POM for 
> org.apache.maven.plugins:maven-install-plugin:jar:2.5.2 is missing, no 
> dependency information available
> [[1;33mWARNING[m] Failed to retrieve plugin descriptor for 
> org.apache.maven.plugins:maven-install-plugin:2.5.2: Plugin 
> org.apache.maven.plugins:maven-install-plugin:2.5.2 or one of its 
> dependencies could not be resolved: Cannot access central 
> (https://repo.maven.apache.org/maven2) in offline mode and the artifact 
> org.apache.maven.plugins:maven-install-plugin:jar:2.5.2 has not been 
> downloaded from it before.
> [[1;33mWARNING[m] The POM for 
> org.apache.maven.plugins:maven-deploy-plugin:jar:2.7 is missing, no 
> dependency information available
> [[1;33mWARNING[m] Failed to retrieve plugin descriptor for 
> org.apache.maven.plugins:maven-deploy-plugin:2.7: Plugin 
> org.apache.maven.plugins:maven-deploy-plugin:2.7 or one of its dependencies 
> could not be resolved: Cannot access central 
> (https://repo.maven.apache.org/maven2) in offline mode and the artifact 
> org.apache.maven.plugins:maven-deploy-plugin:jar:2.7 has not been downloaded 
> from it before.
> [[1;33mWARNING[m] The POM for 
> org.apache.maven.plugins:maven-site-plugin:jar:3.3 is missing, no dependency 
> information available
> [[1;33mWARNING[m] Failed to retrieve plugin descriptor for 
> org.apache.maven.plugins:maven-site-plugin:3.3: Plugin 
> org.apache.maven.plugins:maven-site-plugin:3.3 or one of its dependencies 
> could not be resolved: Cannot access central 
> (https://repo.maven.apache.org/maven2) in offline mode and the artifact 
> org.apache.maven.plugins:maven-site-plugin:jar:3.3 has not been downloaded 
> from it before.
> [[1;33mWARNING[m] The POM for 
> org.apache.maven.plugins:maven-antrun-plugin:jar:1.8 is missing, no 
> dependency information available
> [[1;33mWARNING[m] Failed to retrieve plugin descriptor for 
> org.apache.maven.plugins:maven-antrun-plugin:1.8: Plugin 
> org.apache.maven.plugins:maven-antrun-plugin:1.8 or one of its dependencies 
> could not be resolved: Cannot access central 
> (https://repo.maven.apache.org/maven2) in offline mode and the artifact 
> org.apache.maven.plugins:maven-antrun-plugin:jar:1.8 has not been downloaded 
> from it before.
> [[1;33mWARNING[m] The POM for 
> org.apache.mav

Bug#869009: mustache-java: FTBFS: find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers//.jar': No such file or directory

2017-07-19 Thread Lucas Nussbaum

Source: mustache-java
Version: 0.8.18-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170719 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):
>  debian/rules build
> dh build --buildsystem=maven
>dh_testdir -O--buildsystem=maven
>dh_update_autotools_config -O--buildsystem=maven
>dh_auto_configure -O--buildsystem=maven
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compiler/*/*.jar': No 
> such file or directory
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compilers/*/*.jar': 
> No such file or directory
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': 
> No such file or directory
>   mh_patchpoms -plibmustache-java --debian-build --keep-pom-version 
> --maven-repo=/<>/debian/maven-repo
>dh_auto_build -O--buildsystem=maven
>   /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
> [[1;34mINFO[m] Scanning for projects...
> [[1;34mINFO[m] 
> [1m[m
> [[1;34mINFO[m] [1mReactor Build Order:[m
> [[1;34mINFO[m] 
> [[1;34mINFO[m] mustache.java
> [[1;34mINFO[m] compiler
> [[1;34mINFO[m] codegen
> [[1;34mINFO[m] indy
> [[1;34mINFO[m] mustache-maven-plugin Maven Mojo
> [[1;34mINFO[m] 
> [[1;34mINFO[m] 
> [1m[m
> [[1;34mINFO[m] [1mBuilding mustache.java 0.8.18[m
> [[1;34mINFO[m] 
> [1m[m
> [[1;34mINFO[m] 
> [[1;34mINFO[m] 
> [1m[m
> [[1;34mINFO[m] [1mBuilding compiler 0.8.18[m
> [[1;34mINFO[m] 
> [1m[m
> [[1;34mINFO[m] 
> [[1;34mINFO[m] [1m--- [0;32mmaven-resources-plugin:3.0.0:resources[m 
> [1m(default-resources)[m @ [36mcompiler[0;1m ---[m
> [[1;34mINFO[m] Using 'UTF-8' encoding to copy filtered resources.
> [[1;34mINFO[m] skip non existing resourceDirectory 
> /<>/compiler/src/main/resources
> [[1;34mINFO[m] 
> [[1;34mINFO[m] [1m--- [0;32mmaven-compiler-plugin:3.6.1:compile[m 
> [1m(default-compile)[m @ [36mcompiler[0;1m ---[m
> [[1;33mWARNING[m] The POM for 
> org.codehaus.plexus:plexus-compiler-api:jar:2.x is invalid, transitive 
> dependencies (if any) will not be available, enable debug logging for more 
> details
> [[1;33mWARNING[m] The POM for 
> org.codehaus.plexus:plexus-compiler-javac:jar:2.x is invalid, transitive 
> dependencies (if any) will not be available, enable debug logging for more 
> details
> [[1;34mINFO[m] Changes detected - recompiling the module!
> [[1;34mINFO[m] Compiling 63 source files to 
> /<>/compiler/target/classes
> [[1;34mINFO[m] 
> /<>/compiler/src/main/java/com/github/mustachejava/reflect/BaseObjectHandler.java:
>  
> /<>/compiler/src/main/java/com/github/mustachejava/reflect/BaseObjectHandler.java
>  uses unchecked or unsafe operations.
> [[1;34mINFO[m] 
> /<>/compiler/src/main/java/com/github/mustachejava/reflect/BaseObjectHandler.java:
>  Recompile with -Xlint:unchecked for details.
> [[1;34mINFO[m] 
> [[1;34mINFO[m] [1m--- [0;32mmaven-compiler-plugin:3.6.1:compile[m 
> [1m(default)[m @ [36mcompiler[0;1m ---[m
> [[1;34mINFO[m] Changes detected - recompiling the module!
> [[1;34mINFO[m] Compiling 63 source files to 
> /<>/compiler/target/classes
> [[1;34mINFO[m] 
> /<>/compiler/src/main/java/com/github/mustachejava/reflect/BaseObjectHandler.java:
>  
> /<>/compiler/src/main/java/com/github/mustachejava/reflect/BaseObjectHandler.java
>  uses unchecked or unsafe operations.
> [[1;34mINFO[m] 
> /<>/compiler/src/main/java/com/github/mustachejava/reflect/BaseObjectHandler.java:
>  Recompile with -Xlint:unchecked for details.
> [[1;34mINFO[m] 
> [[1;34mINFO[m] [1m--- [0;32mmaven-bundle-plugin:2.5.4:manifest[m 
> [1m(bundle-mani

Bug#869003: haskell-texmath: FTBFS: unsatisfiable build-dependencies: libghc-pandoc-types-dev (>= 1.12.3.3), libghc-pandoc-types-dev (< 1.18), libghc-pandoc-types-prof

2017-07-19 Thread Lucas Nussbaum

Source: haskell-texmath
Version: 0.9.4-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170719 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):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: cdbs, debhelper (>= 9), ghc (>= 8), ghc-prof, 
> haskell-devscripts (>= 0.13), libghc-mtl-dev, libghc-mtl-prof, 
> libghc-network-uri-dev (>= 2.6), libghc-pandoc-types-dev (>= 1.12.3.3), 
> libghc-pandoc-types-dev (<< 1.18), libghc-pandoc-types-prof, 
> libghc-parsec3-dev (>= 3), libghc-parsec3-prof, libghc-syb-dev, 
> libghc-syb-prof, libghc-xml-dev, libghc-xml-prof, ghc-doc, libghc-mtl-doc, 
> libghc-pandoc-types-doc, libghc-parsec3-doc, libghc-syb-doc, libghc-xml-doc
> Filtered Build-Depends: cdbs, debhelper (>= 9), ghc (>= 8), ghc-prof, 
> haskell-devscripts (>= 0.13), libghc-mtl-dev, libghc-mtl-prof, 
> libghc-network-uri-dev (>= 2.6), libghc-pandoc-types-dev (>= 1.12.3.3), 
> libghc-pandoc-types-dev (<< 1.18), libghc-pandoc-types-prof, 
> libghc-parsec3-dev (>= 3), libghc-parsec3-prof, libghc-syb-dev, 
> libghc-syb-prof, libghc-xml-dev, libghc-xml-prof, ghc-doc, libghc-mtl-doc, 
> libghc-pandoc-types-doc, libghc-parsec3-doc, libghc-syb-doc, libghc-xml-doc
> dpkg-deb: building package 'sbuild-build-depends-haskell-texmath-dummy' in 
> '/<>/resolver-RS3FFe/apt_archive/sbuild-build-depends-haskell-texmath-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-core-dummy 
> sbuild-build-depends-haskell-texmath-dummy
> dpkg-scanpackages: info: Wrote 2 entries to output Packages file.
> Ign:1 copy:/<>/resolver-RS3FFe/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-RS3FFe/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/resolver-RS3FFe/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-RS3FFe/apt_archive ./ Sources [646 B]
> Get:5 copy:/<>/resolver-RS3FFe/apt_archive ./ Packages [716 B]
> Fetched 2325 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install haskell-texmath build dependencies (apt-based resolver)
> ---
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-haskell-texmath-dummy : Depends: 
> libghc-pandoc-types-dev (>= 1.12.3.3) but it is not going to be installed
>   Depends: 
> libghc-pandoc-types-dev (< 1.18) but it is not going to be installed
>   Depends: 
> libghc-pandoc-types-prof but it is not going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://aws-logs.debian.net/2017/07/19/haskell-texmath_0.9.4-1_unstable.log

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 EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Bug#868999: maven-resolver: FTBFS: find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers//.jar': No such file or directory

2017-07-19 Thread Lucas Nussbaum

Source: maven-resolver
Version: 1.0.3-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170719 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):
>  debian/rules build
> dh build --buildsystem=maven
>dh_testdir -O--buildsystem=maven
>dh_update_autotools_config -O--buildsystem=maven
>dh_autoreconf -O--buildsystem=maven
>dh_auto_configure -O--buildsystem=maven
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compiler/*/*.jar': No 
> such file or directory
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compilers/*/*.jar': 
> No such file or directory
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': 
> No such file or directory
>   mh_patchpoms -plibmaven-resolver-java --debian-build --keep-pom-version 
> --maven-repo=/<>/debian/maven-repo
>dh_auto_build -O--buildsystem=maven
>   /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
> [[1;34mINFO[m] Scanning for projects...
> [[1;33mWARNING[m] 
> [[1;33mWARNING[m] Some problems were encountered while building the 
> effective model for 
> org.apache.maven.resolver:maven-resolver-transport-wagon:jar:1.0.3
> [[1;33mWARNING[m] 'build.plugins.plugin.version' for 
> org.codehaus.plexus:plexus-component-metadata is missing. @ line 114, column 
> 12
> [[1;33mWARNING[m] 
> [[1;33mWARNING[m] It is highly recommended to fix these problems because 
> they threaten the stability of your build.
> [[1;33mWARNING[m] 
> [[1;33mWARNING[m] For this reason, future Maven versions might no longer 
> support building such malformed projects.
> [[1;33mWARNING[m] 
> [[1;34mINFO[m] 
> [1m[m
> [[1;34mINFO[m] [1mReactor Build Order:[m
> [[1;34mINFO[m] 
> [[1;34mINFO[m] Maven Artifact Resolver
> [[1;34mINFO[m] Maven Artifact Resolver API
> [[1;34mINFO[m] Maven Artifact Resolver SPI
> [[1;34mINFO[m] Maven Artifact Resolver Test Utilities
> [[1;34mINFO[m] Maven Artifact Resolver Utilities
> [[1;34mINFO[m] Maven Artifact Resolver Implementation
> [[1;34mINFO[m] Maven Artifact Resolver Connector Basic
> [[1;34mINFO[m] Maven Artifact Resolver Transport Classpath
> [[1;34mINFO[m] Maven Artifact Resolver Transport File
> [[1;34mINFO[m] Maven Artifact Resolver Transport HTTP
> [[1;34mINFO[m] Maven Artifact Resolver Transport Wagon
> [[1;34mINFO[m] 
> [[1;34mINFO[m] 
> [1m[m
> [[1;34mINFO[m] [1mBuilding Maven Artifact Resolver 1.0.3[m
> [[1;34mINFO[m] 
> [1m[m
> [[1;34mINFO[m] 
> [[1;34mINFO[m] 
> [1m[m
> [[1;34mINFO[m] [1mBuilding Maven Artifact Resolver API 1.0.3[m
> [[1;34mINFO[m] 
> [1m[m
> [[1;34mINFO[m] 
> [[1;34mINFO[m] [1m--- [0;32mmaven-resources-plugin:3.0.0:resources[m 
> [1m(default-resources)[m @ [36mmaven-resolver-api[0;1m ---[m
> [[1;33mWARNING[m] Using platform encoding (ANSI_X3.4-1968 actually) to copy 
> filtered resources, i.e. build is platform dependent!
> [[1;34mINFO[m] skip non existing resourceDirectory 
> /<>/maven-resolver-api/src/main/resources
> [[1;34mINFO[m] 
> [[1;34mINFO[m] [1m--- [0;32mmaven-compiler-plugin:3.6.1:compile[m 
> [1m(default-compile)[m @ [36mmaven-resolver-api[0;1m ---[m
> [[1;33mWARNING[m] The POM for 
> org.codehaus.plexus:plexus-compiler-api:jar:2.x is invalid, transitive 
> dependencies (if any) will not be available, enable debug logging for more 
> details
> [[1;33mWARNING[m] The POM for 
> org.codehaus.plexus:plexus-compiler-javac:jar:2.x is invalid, transitive 
> dependencies (if any) will not be available, enable debug logging for more 
> details
> [[1;34mINFO[m] Changes detected - recompiling the module!
> [[1;33mWARNING[m] File encoding has not been

Bug#869013: sisu-guice: FTBFS: find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers//.jar': No such file or directory

2017-07-19 Thread Lucas Nussbaum

Source: sisu-guice
Version: 3.2.6-3
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170719 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):
>  debian/rules build
> dh build --buildsystem=maven
>dh_testdir -O--buildsystem=maven
>dh_update_autotools_config -O--buildsystem=maven
>dh_auto_configure -O--buildsystem=maven
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compiler/*/*.jar': No 
> such file or directory
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compilers/*/*.jar': 
> No such file or directory
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': 
> No such file or directory
>   mh_patchpoms -plibsisu-guice-java --debian-build --keep-pom-version 
> --maven-repo=/<>/debian/maven-repo
>dh_auto_build -O--buildsystem=maven
>   /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
> [[1;34mINFO[m] Scanning for projects...
> [[1;33mWARNING[m] 
> [[1;33mWARNING[m] Some problems were encountered while building the 
> effective model for org.sonatype.sisu.inject:guice-testlib:jar:3.2.6
> [[1;33mWARNING[m] 'build.plugins.plugin.version' for 
> org.apache.maven.plugins:maven-surefire-plugin is missing. @ 
> org.sonatype.sisu.inject:guice-testlib:[unknown-version], 
> /<>/extensions/testlib/pom.xml, line 18, column 15
> [[1;33mWARNING[m] 
> [[1;33mWARNING[m] It is highly recommended to fix these problems because 
> they threaten the stability of your build.
> [[1;33mWARNING[m] 
> [[1;33mWARNING[m] For this reason, future Maven versions might no longer 
> support building such malformed projects.
> [[1;33mWARNING[m] 
> [[1;34mINFO[m] 
> [1m[m
> [[1;34mINFO[m] [1mReactor Build Order:[m
> [[1;34mINFO[m] 
> [[1;34mINFO[m] Sisu Guice
> [[1;34mINFO[m] Sisu Guice - Bill of Materials
> [[1;34mINFO[m] Sisu Guice - Core Library
> [[1;34mINFO[m] Sisu Guice - Extensions
> [[1;34mINFO[m] Sisu Guice - Extensions - AssistedInject
> [[1;34mINFO[m] Sisu Guice - Extensions - TestLib
> [[1;34mINFO[m] 
> [[1;34mINFO[m] 
> [1m[m
> [[1;34mINFO[m] [1mBuilding Sisu Guice 3.2.6[m
> [[1;34mINFO[m] 
> [1m[m
> [[1;34mINFO[m] 
> [[1;34mINFO[m] 
> [1m[m
> [[1;34mINFO[m] [1mBuilding Sisu Guice - Bill of Materials 3.2.6[m
> [[1;34mINFO[m] 
> [1m[m
> [[1;34mINFO[m] 
> [[1;34mINFO[m] 
> [1m[m
> [[1;34mINFO[m] [1mBuilding Sisu Guice - Core Library 3.2.6[m
> [[1;34mINFO[m] 
> [1m[m
> [[1;34mINFO[m] 
> [[1;34mINFO[m] [1m--- [0;32mmaven-resources-plugin:3.0.0:resources[m 
> [1m(default-resources)[m @ [36msisu-guice[0;1m ---[m
> [[1;34mINFO[m] Using 'UTF-8' encoding to copy filtered resources.
> [[1;34mINFO[m] Copying 0 resource
> [[1;34mINFO[m] 
> [[1;34mINFO[m] [1m--- [0;32mmaven-compiler-plugin:3.6.1:compile[m 
> [1m(default-compile)[m @ [36msisu-guice[0;1m ---[m
> [[1;33mWARNING[m] The POM for 
> org.codehaus.plexus:plexus-compiler-api:jar:2.x is invalid, transitive 
> dependencies (if any) will not be available, enable debug logging for more 
> details
> [[1;33mWARNING[m] The POM for 
> org.codehaus.plexus:plexus-compiler-javac:jar:2.x is invalid, transitive 
> dependencies (if any) will not be available, enable debug logging for more 
> details
> [[1;34mINFO[m] Changes detected - recompiling the module!
> [[1;34mINFO[m] Compiling 193 source files to 
> /<>/core/target/classes
> [[1;34mINFO[m] 
> /<>/core/src/com/google/inject/internal/Errors.java: Some input 
> files use or ove

Bug#869001: maven-site-plugin: FTBFS: dh_auto_test: /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.ho

2017-07-19 Thread Lucas Nussbaum

Source: maven-site-plugin
Version: 2.2-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170719 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):
>  debian/rules build
> dh build --buildsystem=maven
>dh_testdir -O--buildsystem=maven
>dh_update_autotools_config -O--buildsystem=maven
>dh_autoreconf -O--buildsystem=maven
>dh_auto_configure -O--buildsystem=maven
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compiler/*/*.jar': No 
> such file or directory
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compilers/*/*.jar': 
> No such file or directory
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': 
> No such file or directory
>   mh_patchpoms -plibmaven-site-plugin-java --debian-build 
> --keep-pom-version --maven-repo=/<>/debian/maven-repo
>dh_auto_build -O--buildsystem=maven
>   /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
> [[1;34mINFO[m] Scanning for projects...
> [[1;34mINFO[m] 
> [[1;34mINFO[m] 
> [1m[m
> [[1;34mINFO[m] [1mBuilding Maven Site Plugin 2.2[m
> [[1;34mINFO[m] 
> [1m[m
> [[1;34mINFO[m] 
> [[1;34mINFO[m] [1m--- [0;32mmaven-resources-plugin:3.0.0:resources[m 
> [1m(default-resources)[m @ [36mmaven-site-plugin[0;1m ---[m
> [[1;33mWARNING[m] Using platform encoding (ANSI_X3.4-1968 actually) to copy 
> filtered resources, i.e. build is platform dependent!
> [[1;34mINFO[m] Copying 25 resources
> [[1;34mINFO[m] 
> [[1;34mINFO[m] [1m--- [0;32mmaven-compiler-plugin:3.6.1:compile[m 
> [1m(default-compile)[m @ [36mmaven-site-plugin[0;1m ---[m
> [[1;33mWARNING[m] The POM for 
> org.codehaus.plexus:plexus-compiler-api:jar:2.x is invalid, transitive 
> dependencies (if any) will not be available, enable debug logging for more 
> details
> [[1;33mWARNING[m] The POM for 
> org.codehaus.plexus:plexus-compiler-javac:jar:2.x is invalid, transitive 
> dependencies (if any) will not be available, enable debug logging for more 
> details
> [[1;34mINFO[m] Changes detected - recompiling the module!
> [[1;33mWARNING[m] File encoding has not been set, using platform encoding 
> ANSI_X3.4-1968, i.e. build is platform dependent!
> [[1;34mINFO[m] Compiling 18 source files to /<>/target/classes
> Use of target 1.5 is no longer supported, switching to 1.7
> Use of source 1.5 is no longer supported, switching to 1.7
> [[1;31mERROR[m] 
> /<>/src/main/java/org/apache/maven/plugins/site/EffectiveSiteMojo.java:[48,53]
>  unmappable character for encoding ASCII
> [[1;31mERROR[m] 
> /<>/src/main/java/org/apache/maven/plugins/site/EffectiveSiteMojo.java:[48,54]
>  unmappable character for encoding ASCII
> [[1;34mINFO[m] 
> /<>/src/main/java/org/apache/maven/plugins/site/AbstractSiteMojo.java:
>  Some input files use unchecked or unsafe operations.
> [[1;34mINFO[m] 
> /<>/src/main/java/org/apache/maven/plugins/site/AbstractSiteMojo.java:
>  Recompile with -Xlint:unchecked for details.
> [[1;34mINFO[m] 
> [[1;34mINFO[m] [1m--- [0;32mmaven-plugin-plugin:3.5:descriptor[m 
> [1m(default-descriptor)[m @ [36mmaven-site-plugin[0;1m ---[m
> [[1;33mWARNING[m] Using platform encoding (ANSI_X3.4-1968 actually) to read 
> mojo source files, i.e. build is platform dependent!
> [[1;33mWARNING[m] org.apache.maven.plugins.site.SiteJarMojo#attach:
> [[1;33mWARNING[m]   The syntax
> [[1;33mWARNING[m] @parameter expression="${property}"
> [[1;33mWARNING[m]   is deprecated, please use
> [[1;33mWARNING[m] @parameter property="property"
> [[1;33mWARNING[m]   instead.
> [[1;33mWARNING[m] org.apache.maven.plugins.site.SiteJarMojo#attributes:
> [[1;33mWARNING[m]   The syntax
> [[1;33mWARNING[m] @parameter expression="${property}"
> [[1;33mWARNING[m]   is deprecated, please use
> [[1;33mWARNING[m] @parameter property="p

Bug#869004: wagon2: FTBFS: make[1]: svnadmin: Command not found

2017-07-19 Thread Lucas Nussbaum

Source: wagon2
Version: 2.12-2
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170719 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
> make[1]: svnadmin: Command not found
> debian/rules:9: recipe for target 'override_dh_auto_build' failed
> make[1]: [override_dh_auto_build] Error 127 (ignored)
> 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
> [[1;34mINFO[m] Scanning for projects...
> [[1;33mWARNING[m] 
> [[1;33mWARNING[m] Some problems were encountered while building the 
> effective model for org.apache.maven.wagon:wagon-provider-api:jar:2.12
> [[1;33mWARNING[m] 'build.plugins.plugin.version' for 
> org.codehaus.plexus:plexus-component-metadata is missing. @ 
> org.apache.maven.wagon:wagon:2.12, /<>/pom.xml, line 367, column 
> 12
> [[1;33mWARNING[m] 
> [[1;33mWARNING[m] Some problems were encountered while building the 
> effective model for org.apache.maven.wagon:wagon-file:jar:2.12
> [[1;33mWARNING[m] 'build.plugins.plugin.version' for 
> org.codehaus.plexus:plexus-component-metadata is missing. @ 
> org.apache.maven.wagon:wagon:2.12, /<>/pom.xml, line 367, column 
> 12
> [[1;33mWARNING[m] 
> [[1;33mWARNING[m] Some problems were encountered while building the 
> effective model for org.apache.maven.wagon:wagon-ftp:jar:2.12
> [[1;33mWARNING[m] 'build.plugins.plugin.version' for 
> org.codehaus.plexus:plexus-component-metadata is missing. @ 
> org.apache.maven.wagon:wagon:2.12, /<>/pom.xml, line 367, column 
> 12
> [[1;33mWARNING[m] 
> [[1;33mWARNING[m] Some problems were encountered while building the 
> effective model for org.apache.maven.wagon:wagon-http:jar:2.12
> [[1;33mWARNING[m] 'build.plugins.plugin.(groupId:artifactId)' must be 
> unique but found duplicate declaration of plugin 
> org.apache.maven.plugins:maven-surefire-plugin @ line 174, column 12
> [[1;33mWARNING[m] 'build.plugins.plugin.version' for 
> org.apache.maven.plugins:maven-surefire-plugin is missing. @ line 174, column 
> 12
> [[1;33mWARNING[m] 'build.plugins.plugin.version' for 
> org.codehaus.plexus:plexus-component-metadata is missing. @ 
> org.apache.maven.wagon:wagon:2.12, /<>/pom.xml, line 367, column 
> 12
> [[1;33mWARNING[m] 
> [[1;33mWARNING[m] Some problems were encountered while building the 
> effective model for org.apache.maven.wagon:wagon-http-shared:jar:2.12
> [[1;33mWARNING[m] 'build.plugins.plugin.version' for 
> org.codehaus.plexus:plexus-component-metadata is missing. @ 
> org.apache.maven.wagon:wagon:2.12, /<>/pom.xml, line 367, column 
> 12
> [[1;33mWARNING[m] 
> [[1;33mWARNING[m] Some problems were encountered while building the 
> effective model for org.apache.maven.wagon:wagon-http-lightweight:jar:2.12
> [[1;33mWARNING[m] 'build.plugins.plugin.version' for 
> org.apache.maven.plugins:maven-surefire-plugin is missing. @ line 81, column 
> 12
> [[1;33mWARNING[m] 'build.plugins.plugin.version' for 
> org.codehaus.plexus:plexus-component-metadata is missing. @ 
> org.apache.maven.wagon:wagon:2.12, /<>/pom.xml, line 367, column 
> 12
> [[1;33mWARNING[m] 
> [[1;33mWARNING[m] Some problems were encountered while building the 
> effective model for org.apache.maven.wagon:wagon-providers:pom:2.12
> [[1;33mWARNING[m] 'build.plugins.plugin.version' for 
> org.codehaus.plexus:plexus-component-metadata is missing. @ 
> org.apache.maven.wagon:wagon:2.12, /<>/pom.xml, line 367, column 
> 12
> [[1;33mWARNING[m] 
> [[1;33mWARNING[m] Some problems were encountered while building the 
> effective model for org.apache.maven.wagon:wagon-provider-test:jar:2.12
> [[1;33mWARNING[m] 'build.plugins.plugin.version' for 
> org.codehaus.plexus:plexus-component-metadata is missing. @ 
> org.apache

Bug#778878: apt update cannot verify public keys (clean install).

2017-07-19 Thread Mark Henwood

One other person on the Debian Stack Exchange had this problem. Moving
(renaming) the trusted.gpg file fixed it.
On Wed, Jul 19, 2017 at 17:15 Mark Henwood  wrote:

> Package: apt
> Version: 1.4.6
> Followup-For: Bug #778878
>
> Clean install of SMP Debian 4.9.30-2+deb9u2 (2017-06-26) x86_64 GNU/Linux
> on an
> HP G62-144DX with 4G of memory, 500G HD and Intel® Core™ i3 CPU M 330 @
> 2.13GHz
> × 4 Everything working fine. I had updated the apt repository a couple of
> times
> to make sure there were no updates so I know it was working before I tried
> to
> add non-free.
>
> After choosing "DFSG-compatible Softwear with Non-Free Dependencies
> (contrib)"
> in synaptic apt became "unhappy." I have tried looking for answers but am
> either in the wrong places or it's just me (i.e. Murphy's law).
>
> When apt-get update is called I get the following:
>
> # apt update
> Ign:1 http://ftp.us.debian.org/debian stretch InRelease
> Hit:2 http://ftp.us.debian.org/debian stretch-updates InRelease
> Hit:3 http://ftp.us.debian.org/debian stretch Release
> Err:2 http://ftp.us.debian.org/debian stretch-updates InRelease
>   The following signatures couldn't be verified because the public key is
> not
> available: NO_PUBKEY 8B48AD6246925553 NO_PUBKEY 7638D0442B90D010
> Hit:4 http://security.debian.org/debian-security stretch/updates InRelease
> Err:5 http://ftp.us.debian.org/debian stretch Release.gpg
>   The following signatures couldn't be verified because the public key is
> not
> available: NO_PUBKEY 8B48AD6246925553 NO_PUBKEY 7638D0442B90D010 NO_PUBKEY
> CBF8D6FD518E17E1 NO_PUBKEY EF0F382A1A7B6500
> Err:4 http://security.debian.org/debian-security stretch/updates InRelease
>   The following signatures couldn't be verified because the public key is
> not
> available: NO_PUBKEY 9D6D8F6BC857C906 NO_PUBKEY 8B48AD6246925553
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> All packages are up to date.
> W: An error occurred during the signature verification. The repository is
> not
> updated and the previous index files will be used. GPG error:
> http://ftp.us.debian.org/debian stretch-updates InRelease: The following
> signatures couldn't be verified because the public key is not available:
> NO_PUBKEY 8B48AD6246925553 NO_PUBKEY 7638D0442B90D010
> W: An error occurred during the signature verification. The repository is
> not
> updated and the previous index files will be used. GPG error:
> http://ftp.us.debian.org/debian stretch Release: The following signatures
> couldn't be verified because the public key is not available: NO_PUBKEY
> 8B48AD6246925553 NO_PUBKEY 7638D0442B90D010 NO_PUBKEY CBF8D6FD518E17E1
> NO_PUBKEY EF0F382A1A7B6500
> W: An error occurred during the signature verification. The repository is
> not
> updated and the previous index files will be used. GPG error:
> http://security.debian.org/debian-security stretch/updates InRelease: The
> following signatures couldn't be verified because the public key is not
> available: NO_PUBKEY 9D6D8F6BC857C906 NO_PUBKEY 8B48AD6246925553
> W: Failed to fetch http://security.debian.org/debian-
> security/dists/stretch/updates/InRelease  The following signatures
> couldn't be
> verified because the public key is not available: NO_PUBKEY
> 9D6D8F6BC857C906
> NO_PUBKEY 8B48AD6246925553
> W: Failed to fetch http://ftp.us.debian.org/debian/dists/stretch-
> updates/InRelease
>   The
> following signatures couldn't be verified because the
> public key is not available: NO_PUBKEY 8B48AD6246925553 NO_PUBKEY
> 7638D0442B90D010
> W: Failed to fetch
> http://ftp.us.debian.org/debian/dists/stretch/Release.gpg
> The following signatures couldn't be verified because the public key is not
> available: NO_PUBKEY 8B48AD6246925553 NO_PUBKEY 7638D0442B90D010 NO_PUBKEY
> CBF8D6FD518E17E1 NO_PUBKEY EF0F382A1A7B6500
> W: Some index files failed to download. They have been ignored, or old ones
> used instead.
>
> I tried going back by unchecking the option in Synaptic and by copying
> sources.list.saved to sources.list with no luck.
> As far as I can tell apt-key has all the keys that update is griping about.
> Here are the relavent outputs I can think of:
>
> Sources.list after the fall:
>
> #
>
> # deb cdrom:[Debian GNU/Linux 9.0.0 _Stretch_ - Official amd64 NETINST
> 20170617-13:06]/ stretch main
>
> # deb cdrom:[Debian GNU/Linux 9.0.0 _Stretch_ - Official amd64 NETINST
> 20170617-13:06]/ stretch main
>
> deb http://ftp.us.debian.org/debian/ stretch main contrib
> deb-src http://ftp.us.debian.org/debian/ stretch main contrib
>
> deb http://security.debian.org/debian-security stretch/updates main
> contrib
> deb-src http://security.debian.org/debian-security stretch/updates main
> contrib
>
> # stretch-updates, previously known as 'volatile'
> deb http://ftp.us.debian.org/debian/ stretch-updates main contrib
> deb-src http://ftp.us.debian.org/debian/ stretch-updates main contrib
>

Bug#782075: gnome-tweak-tool: Crashes Gnome when reducing Number of Workspaces

2017-07-19 Thread intrigeri

The Mutter 3.24.4 announcement says that
https://bugzilla.gnome.org/show_bug.cgi?id=784223 has been fixed.
I suspect this is the same bug as this one.

So anyone affected: please try to reproduce once Mutter 3.24.4 is in
Debian :) Thanks in advance!

Bug#868971: [Python-modules-team] Bug#868971: python-feather-format: FTBFS: feather/ext.cpp:28:20: fatal error: Python.h: No such file or directory

2017-07-19 Thread Scott Kitterman



On July 19, 2017 3:45:23 PM EDT, Lucas Nussbaum  wrote:
>Source: python-feather-format
>Version: 0.3.1+dfsg1-1
>Severity: serious
>Tags: buster sid
>User: debian...@lists.debian.org
>Usertags: qa-ftbfs-20170719 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):
>> x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall
>-Wstrict-prototypes -g -O2
>-fdebug-prefix-map=/<>/python-feather-format-0.3.1+dfsg1=.
>-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
>-D_FORTIFY_SOURCE=2 -fPIC -Ifeather
>-I/usr/lib/python3/dist-packages/numpy/core/include
>-I/<>/python-feather-format-0.3.1+dfsg1/src
>-I/usr/include/python3.6m -c feather/ext.cpp -o
>build/temp.linux-amd64-3.6/feather/ext.o -std=c++11 -O3
>> cc1plus: warning: command line option ‘-Wstrict-prototypes’ is valid
>for C/ObjC but not for C++
>> feather/ext.cpp:28:20: fatal error: Python.h: No such file or
>directory
>>  #include "Python.h"
>> ^
>> compilation terminated.
>> error: command 'x86_64-linux-gnu-gcc' failed with exit status 1
>> E: pybuild pybuild:283: build: plugin distutils failed with: exit
>code=1: /usr/bin/python3.6 setup.py build 
>> dh_auto_build: pybuild --build -i python{version} -p 3.6 3.5 returned
>exit code 13
>> debian/rules:8: recipe for target 'build' failed
>> make: *** [build] Error 25
>
>The full build log is available from:
>http://aws-logs.debian.net/2017/07/19/python-feather-format_0.3.1+dfsg1-1_unstable.log

From the log, it looks like missing build-depends on python3-all-dev.

Scott K

Bug#868753: [Pkg-openldap-devel] Bug#868753: slapd: Please include several upstream fixes

2017-07-19 Thread Ryan Tandy


Hi Sven,

Thank you very much for the detailed report.

I've been trying to reproduce these issues, in order to test the results 
of isolating and backporting the ITS patches, but no luck so far. 
However I did discover and report ITS#8696 while working on this, so 
that's something...


I hate to ask for more of your time when you've clearly put a lot into 
this already; but if you're able to help out at all with reducing the 
test cases for any of these (for example eliminating gssapi from the 
mix), that could help save us some time.


I'm also hoping that your test environment is persistent enough, or 
straightforward enough to set up, that you might be able to help with 
testing if I propose a package for a stable update?

Bug#867717: catdoc: diff for NMU version 1:0.95-2.1

2017-07-19 Thread Salvatore Bonaccorso

Control: tags 867717 + patch
Control: tags 867717 + pending

Dear Martin,

I've prepared an NMU for catdoc (versioned as 1:0.95-2.1) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.

Regards,
Salvatore
diff -Nru catdoc-0.95/debian/changelog catdoc-0.95/debian/changelog
--- catdoc-0.95/debian/changelog	2017-05-19 12:16:07.0 +0200
+++ catdoc-0.95/debian/changelog	2017-07-20 06:32:01.0 +0200
@@ -1,3 +1,10 @@
+catdoc (1:0.95-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * CVE-2017-0: Heap buffer overflow in ole_init (Closes: #867717)
+
+ -- Salvatore Bonaccorso   Thu, 20 Jul 2017 06:32:01 +0200
+
 catdoc (1:0.95-2) unstable; urgency=medium
 
   * Re-enable patch that was disabled by mistake.
diff -Nru catdoc-0.95/debian/patches/05-CVE-2017-0.patch catdoc-0.95/debian/patches/05-CVE-2017-0.patch
--- catdoc-0.95/debian/patches/05-CVE-2017-0.patch	1970-01-01 01:00:00.0 +0100
+++ catdoc-0.95/debian/patches/05-CVE-2017-0.patch	2017-07-20 06:32:01.0 +0200
@@ -0,0 +1,32 @@
+Description: CVE-2017-0: Heap buffer overflow in ole_init 
+Origin: vendor, https://build.opensuse.org/package/view_file/openSUSE:Maintenance:6985/catdoc.openSUSE_Leap_42.2_Update/CVE-2017-0.patch?rev=d437c3be72c2e5a3516b75f4e9de6b35
+Bug-Debian: https://bugs.debian.org/867717
+Bug-SuSE: https://bugzilla.novell.com/show_bug.cgi?id=1047877
+Forwarded: no
+Author: Andreas Stieger 
+Reviewed-by: Salvatore Bonaccorso 
+Last-Update: 2017-07-20
+
+--- a/src/ole.c
 b/src/ole.c
+@@ -106,6 +106,11 @@ FILE* ole_init(FILE *f, void *buffer, si
+ 		return NULL;
+ 	}
+  	sectorSize = 1<=4 for CVE-2017-0 */
+ 		 1, sectorSize, newfile) != sectorSize) {
+ 			fprintf(stderr, "Error read MSAT!\n");
+ 			ole_finish();
diff -Nru catdoc-0.95/debian/patches/series catdoc-0.95/debian/patches/series
--- catdoc-0.95/debian/patches/series	2017-05-19 12:16:07.0 +0200
+++ catdoc-0.95/debian/patches/series	2017-07-20 06:32:01.0 +0200
@@ -2,3 +2,4 @@
 02-Fail_on_build_failure.patch
 03-Type_fixes.patch
 04-XLS_parsing_improvements.patch
+05-CVE-2017-0.patch

Bug#867213: [Syslog-ng-maintainers] Bug#867213: syslog-ng-incubator: FTBFS: error: unknown type name 'SBGString'

2017-07-19 Thread GCS

Control: tags -1 +pending

Hi Niko,

On Tue, Jul 4, 2017 at 9:59 PM, Niko Tyni  wrote:
> This package fails to build on current sid/amd64.
[...]
>   libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../.. -Wdate-time 
> -D_FORTIFY_SOURCE=2 -I/usr/include/lua5.2 -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/eventlog 
> -I/usr/include/syslog-ng -I/usr/include/eventlog -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I../../modules/lua 
> -I./modules/lua -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -c 
> ../../modules/lua/lua-parser.c  -fPIC -DPIC -o 
> modules/lua/.libs/modules_lua_liblua_la-lua-parser.o
>   ../../modules/lua/lua-dest.c: In function 'lua_dd_queue':
>   ../../modules/lua/lua-dest.c:145:3: error: unknown type name 'SBGString'
>  SBGString *str = sb_gstring_acquire();
>  ^
 I've fixed it locally, wanted to ask upstream for confirmation first,
but will upload it in the afternoon.

Regards,
Laszlo/GCS

Bug#868998: debhelper: dh_installman doesn't support paths with space characters

2017-07-19 Thread 林博仁

Package: debhelper
Version: 10.6.4
Severity: normal

Dear Maintainer,

   * What led up to the situation?

I am practicing maint-guide chapter 5 and implemented a manpage after the
template

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
I placed the manpage at "Manual Pages" directory under the source root
directory and added the following line(s) to debian/.manpages:

* Manual Pages/.1

   * What was the outcome of this action?

dh_installman complains of missing "Manual" file:

```
dh_installman
"Manual: No such file or directory at /usr/bin/dh_installman line 131.
debian/rules:19: recipe for target 'binary' failed
make: *** [binary] Error 2
```

   * What outcome did you expect instead?

manpage correctly installed either in the following forms in
debian/.manpages:

* Manual Pages/.1
* Manual\ Pages/.1
* "Manual Pages/.1"


Thanks!



-- System Information:
Debian Release: stretch/sid
  APT prefers xenial-updates
  APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500, 
'xenial'), (100, 'xenial-backports'), (99, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.8.0-58-generic (SMP w/4 CPU cores)
Locale: LANG=zh_TW.UTF-8, LC_CTYPE=zh_TW.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages debhelper depends on:
ii  autotools-dev20150820.1
ii  binutils 2.26.1-1ubuntu1~16.04.3
ii  dh-autoreconf14
ii  dh-strip-nondeterminism  0.038-1
ii  dpkg 1.18.4ubuntu1.2
ii  dpkg-dev 1.18.4ubuntu1.2
ii  file 1:5.25-2ubuntu1
ii  libdpkg-perl 1.18.4ubuntu1.2
ii  man-db   2.7.5-1
ii  perl 5.22.1-9
ii  po-debconf   1.0.19

debhelper recommends no packages.

Versions of packages debhelper suggests:
pn  dh-make  

-- no debconf information

Bug#868987: gopass: FTBFS w/gccgo: TestVersion* fails

2017-07-19 Thread Aaron M. Ucko

Alexandre Viau  writes:

> I have tried fixing the issue with the 1.0.6-1 upload, but it looks like

Thanks for the quick fix!

> the build is now failing in other places, which I don't control.

FTR, it looks like 1.0.6-1 did succeed on mips64el and the non-release
architecture powerpc, but not on the remaining gccgo architectures.

> I'll upload 1.0.6-2 which will depend on golang-go :(.

OK, thanks.

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Bug#865897: unattended-upgrades FTBFS: FAIL: test_pep8_clean

2017-07-19 Thread Petter Reinholdtsen

[Adrian Bunk]
> FAIL: test_pep8_clean (__main__.PackagePep8TestCase)

Perhaps this is fixed in Ubuntu?  Found this in the latest Ubuntu diff:

unattended-upgrades (0.93.1ubuntu7) artful; urgency=medium

  * Fix PEP8 failures (replace except: with except Exception:)

 -- Julian Andres Klode   Sat, 01 Jul 2017 00:36:13 +0200
-- 
Happy hacking
Petter Reinholdtsen

Bug#868997: thunderbird: Ctrl-K deletes text instead of inserting hyperlinks when composing

2017-07-19 Thread Bin Guo

Package: thunderbird
Version: 1:52.2.1-4
Severity: normal

Dear Maintainer,

  I recently upgraded thunderbird from 1:45.8.0-3 to 1:52.2.1-4, and
noticed that the shortcut to insert link when composing changed from
Ctrl-L to Ctrl-K, but it doesn't actually work --- it in fact deletes
text. Also other keys like Ctrl-F is not searching, but moving forward.

  This happens even in safe mode, while a windows version works fine.
Inserting hyperlinks is a common operation when composing, Ctrl-K should
work as expected to display the insert hyperlink dialog.


-- System Information:
Debian Release: buster/sid
  APT prefers oldstable-updates
  APT policy: (500, 'oldstable-updates'), (500, 'testing'), (500, 'oldstable'), 
(400, 'unstable'), (300, 'stable'), (200, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.11.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), 
LANGUAGE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages thunderbird depends on:
ii  debianutils   4.8.1.1
ii  fontconfig2.12.3-0.2
ii  libatk1.0-0   2.22.0-1
ii  libc6 2.24-12
ii  libcairo-gobject2 1.14.10-1
ii  libcairo2 1.14.10-1
ii  libdbus-1-3   1.10.20-1
ii  libdbus-glib-1-2  0.108-2
ii  libevent-2.0-52.0.21-stable-3
ii  libffi6   3.2.1-6
ii  libfontconfig12.12.3-0.2
ii  libfreetype6  2.8-0.2
ii  libgcc1   1:7.1.0-9
ii  libgdk-pixbuf2.0-02.36.5-2
ii  libglib2.0-0  2.52.3-1
ii  libgtk-3-03.22.16-1
ii  libhunspell-1.6-0 1.6.1-2
ii  libpango-1.0-01.40.6-1
ii  libpangocairo-1.0-0   1.40.6-1
ii  libpangoft2-1.0-0 1.40.6-1
ii  libpixman-1-0 0.34.0-1
ii  libstartup-notification0  0.12-4+b2
ii  libstdc++67.1.0-9
ii  libvpx4   1.6.1-3
ii  libx11-6  2:1.6.4-3
ii  libx11-xcb1   2:1.6.4-3
ii  libxcb-shm0   1.12-1
ii  libxcb1   1.12-1
ii  libxcomposite11:0.4.4-2
ii  libxdamage1   1:1.1.4-2+b3
ii  libxext6  2:1.3.3-1+b2
ii  libxfixes31:5.0.3-1
ii  libxrender1   1:0.9.10-1
ii  libxt61:1.1.5-1
ii  psmisc23.1-1
ii  x11-utils 7.7+3+b1
ii  zlib1g1:1.2.8.dfsg-5

Versions of packages thunderbird recommends:
ii  hunspell-en-us [hunspell-dictionary]  20070829-7
ii  lightning 1:52.2.1-4

Versions of packages thunderbird suggests:
pn  apparmor  
pn  fonts-lyx 
ii  libgssapi-krb5-2  1.15-1

-- no debconf information

Bug#868987: gopass: FTBFS w/gccgo: TestVersion* fails

2017-07-19 Thread Alexandre Viau

On 19/07/17 08:46 PM, Aaron M. Ucko wrote:
> Could you please take a look, and either fix these builds or
> specifically build depend on golang-go?

I have tried fixing the issue with the 1.0.6-1 upload, but it looks like
the build is now failing in other places, which I don't control.

I'll upload 1.0.6-2 which will depend on golang-go :(.

Cheers,

-- 
Alexandre Viau
av...@debian.org

signature.asc
Description: OpenPGP digital signature

Bug#848838: sugar-write-activity: constant flicker of cursor and document

2017-07-19 Thread James Cameron

Well, #851052 is a duplicate of #848838, as mine was first.  ;-)

Upstream bug in Sugar is
https://bugs.sugarlabs.org/ticket/4915

-- 
James Cameron
http://quozl.netrek.org/

Bug#868995: installation-reports: blank screen after kernel boots and does the nouveau modeset Corporation GF108GL Quadro 600 rev a1

2017-07-19 Thread Jason Lewis

Package: installation-reports
Severity: important

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


-- Package-specific info:

Boot method: usb flash
Image version: DISTRIB_RELEASE="9 (stretch) - installer build 20170615" 
Date: 

Machine: Dell T5600
Partitions: 


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [o ]
Detect network card:[o ]
Configure network:  [o ]
Detect CD:  [o ]
Load installer modules: [o ]
Clock/timezone setup:   [o ]
User/password setup:[o ]
Detect hard drives: [o ]
Partition hard drives:  [o ]
Install base system:[o ]
Install tasks:  [o ]
Install boot loader:[o ]
Overall install:[E ]

Comments/Problems:

After installing, when the kernel switches graphics mode, the screen goes black 
and as far as I could tell becomes unresponsive.
I didn't do further testing to see if I could ssh into it sorry.

adding nouveau.modeset=0 to the kernel boot paramaters solves the problem
Graphics card: VGA compatible controller: NVIDIA Corporation GF108GL [Quadro 
600] (rev a1)


-- 

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

Once you have filled out this report, mail it to sub...@bugs.debian.org.

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="9 (stretch) - installer build 20170615"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux vmhost01 4.9.0-3-amd64 #1 SMP Debian 4.9.30-2 (2017-06-12) 
x86_64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Xeon E5/Core i7 DMI2 
[8086:3c00] (rev 07)
lspci -knn: Subsystem: Dell Device [1028:0496]
lspci -knn: 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E5/Core i7 IIO 
PCI Express Root Port 1a [8086:3c02] (rev 07)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:01.1 PCI bridge [0604]: Intel Corporation Xeon E5/Core i7 IIO 
PCI Express Root Port 1b [8086:3c03] (rev 07)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:02.0 PCI bridge [0604]: Intel Corporation Xeon E5/Core i7 IIO 
PCI Express Root Port 2a [8086:3c04] (rev 07)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:03.0 PCI bridge [0604]: Intel Corporation Xeon E5/Core i7 IIO 
PCI Express Root Port 3a in PCI Express Mode [8086:3c08] (rev 07)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:05.0 System peripheral [0880]: Intel Corporation Xeon E5/Core i7 
Address Map, VTd_Misc, System Management [8086:3c28] (rev 07)
lspci -knn: Subsystem: Dell Device [1028:0496]
lspci -knn: 00:05.2 System peripheral [0880]: Intel Corporation Xeon E5/Core i7 
Control Status and Global Errors [8086:3c2a] (rev 07)
lspci -knn: Subsystem: Dell Device [1028:0496]
lspci -knn: 00:05.4 PIC [0800]: Intel Corporation Xeon E5/Core i7 I/O APIC 
[8086:3c2c] (rev 07)
lspci -knn: Subsystem: Dell Device [1028:0496]
lspci -knn: 00:16.0 Communication controller [0780]: Intel Corporation C600/X79 
series chipset MEI Controller #1 [8086:1d3a] (rev 05)
lspci -knn: Subsystem: Dell Device [1028:0496]
lspci -knn: 00:16.3 Serial controller [0700]: Intel Corporation C600/X79 series 
chipset KT Controller [8086:1d3d] (rev 05)
lspci -knn: Subsystem: Dell Device [1028:0496]
lspci -knn: Kernel driver in use: serial
lspci -knn: 00:19.0 Ethernet controller [0200]: Intel Corporation 82579LM 
Gigabit Network Connection [8086:1502] (rev 05)
lspci -knn: Subsystem: Dell Device [1028:0496]
lspci -knn: Kernel driver in use: e1000e
lspci -knn: Kernel modules: e1000e
lspci -knn: 00:1a.0 USB controller [0c03]: Intel Corporation C600/X79 series 
chipset USB2 Enhanced Host Controller #2 [8086:1d2d] (rev 05)
lspci -knn: Subsystem: Dell Device [1028:0496]
lspci -knn: Kernel driver in use: ehci-pci
lspci -knn: Kernel modules: ehci_pci
lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation C600/X79 series 
chipset High Definition Audio Controller [8086:1d20] (rev 05)
lspci -knn: Subsystem: Dell Device [1028:0496]
lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation C600/X79 series 
chipset PCI Express Root Port 4 [8086:1d16] (rev b5)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.2 PCI bridge [0604]: Intel Corporation C600/X79 series 
chipset PCI Express Root Port 3 [8086:1d

Bug#868996: tracker.debian.org: broken entry for linux package in old-upd (3.16.7-ckt25-2)

2017-07-19 Thread Boyuan Yang

Package: tracker.debian.org
Severity: normal

Please, check out the "versions" section on
 https://tracker.debian.org/pkg/linux

You can see one line called:

 old-upd: 3.16.7-ckt25-2

Which provides a broken link on packages.debian.org .

I am wondering why this link is not removed now that ckt- kernel has been
removed from Debian for such a long time.



-- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.11.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#868939: texlive-fonts-extra: please, use alternative depends on ttf-adf- packages that are now fonts-adf-

2017-07-19 Thread Norbert Preining

Hi Rogério,

> Can you change the depends on ttf-adf-* fonts to be (at least) alternative
> depends on fonts-adf-* packages?

Are the two shipping the same fonts? And if yes, why isn't ttf-adf-* not
a transitional package depending on fonts-adf-?

I can surely change the deps, but since I link the fonts into the
TeX Live tree so that hte adf latex packages work, I need to be sure
that the fonts actually agree and work?

Thanks

Norbert

--
PREINING Norbert   http://www.preining.info
Accelia Inc. +JAIST +TeX Live +Debian Developer
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#868994: text too small to read on text based installer on high resolution screen

2017-07-19 Thread Jason Lewis

Package: installation-reports

Boot method: usb stick
Image version:
http://saimei.ftp.acc.umu.se/cdimage/unofficial/non-free/cd-including-firmware/9.0.0+nonfree/amd64/iso-cd/firmware-9.0.0-amd64-netinst.iso
Date: 2017-07-20

Machine: Dell Precision 5520
Processor: Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz
Memory: 32gb
Partitions: n/a

Output of lspci -knn (or lspci -nn):
00:00.0 Host bridge [0600]: Intel Corporation Device [8086:5910] (rev 05)
Subsystem: Dell Device [1028:07bf]
00:01.0 PCI bridge [0604]: Intel Corporation Skylake PCIe Controller
(x16) [8086:1901] (rev 05)
Kernel driver in use: pcieport
00:02.0 VGA compatible controller [0300]: Intel Corporation Device
[8086:591b] (rev 04)
Subsystem: Dell Device [1028:07bf]
00:04.0 Signal processing controller [1180]: Intel Corporation Skylake
Processor Thermal Subsystem [8086:1903] (rev 05)
Subsystem: Dell Device [1028:07bf]
00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-H USB 3.0
xHCI Controller [8086:a12f] (rev 31)
Subsystem: Dell Device [1028:07bf]
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci
00:14.2 Signal processing controller [1180]: Intel Corporation Sunrise
Point-H Thermal subsystem [8086:a131] (rev 31)
Subsystem: Dell Device [1028:07bf]
00:15.0 Signal processing controller [1180]: Intel Corporation Sunrise
Point-H Serial IO I2C Controller #0 [8086:a160] (rev 31)
Subsystem: Dell Device [1028:07bf]
00:15.1 Signal processing controller [1180]: Intel Corporation Sunrise
Point-H Serial IO I2C Controller #1 [8086:a161] (rev 31)
Subsystem: Dell Device [1028:07bf]
00:16.0 Communication controller [0780]: Intel Corporation Sunrise
Point-H CSME HECI #1 [8086:a13a] (rev 31)
Subsystem: Dell Device [1028:07bf]
00:16.3 Serial controller [0700]: Intel Corporation Sunrise Point-H KT
Redirection [8086:a13d] (rev 31)
Subsystem: Dell Device [1028:07bf]
Kernel driver in use: serial
00:17.0 SATA controller [0106]: Intel Corporation Sunrise Point-H SATA
controller [AHCI mode] [8086:a102] (rev 31)
Subsystem: Dell Device [1028:07bf]
Kernel driver in use: ahci
Kernel modules: ahci
00:1c.0 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express
Root Port #1 [8086:a110] (rev f1)
Kernel driver in use: pcieport
00:1c.1 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express
Root Port #2 [8086:a111] (rev f1)
Kernel driver in use: pcieport
00:1d.0 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express
Root Port #9 [8086:a118] (rev f1)
Kernel driver in use: pcieport
00:1d.4 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express
Root Port #13 [8086:a11c] (rev f1)
00:1d.6 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express
Root Port #15 [8086:a11e] (rev f1)
Kernel driver in use: pcieport
00:1f.0 ISA bridge [0601]: Intel Corporation Sunrise Point-H LPC
Controller [8086:a154] (rev 31)
Subsystem: Dell Device [1028:07bf]
00:1f.2 Memory controller [0580]: Intel Corporation Sunrise Point-H PMC
[8086:a121] (rev 31)
Subsystem: Dell Device [1028:07bf]
00:1f.3 Audio device [0403]: Intel Corporation Device [8086:a171] (rev 31)
Subsystem: Dell Device [1028:07bf]
00:1f.4 SMBus [0c05]: Intel Corporation Sunrise Point-H SMBus
[8086:a123] (rev 31)
Subsystem: Dell Device [1028:07bf]
01:00.0 3D controller [0302]: NVIDIA Corporation Device [10de:13b6] (rev a2)
Subsystem: Dell Device [1028:07bf]
02:00.0 Network controller [0280]: Intel Corporation Device [8086:24fd]
(rev 78)
Subsystem: Intel Corporation Device [8086:0050]
Kernel modules: iwlwifi
03:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A
PCI Express Card Reader [10ec:525a] (rev 01)
Subsystem: Dell Device [1028:07bf]
Kernel driver in use: rtsx_pci
Kernel modules: rtsx_pci
04:00.0 Non-Volatile memory controller [0108]: Toshiba America Info
Systems Device [1179:010f] (rev 01)
Subsystem: Toshiba America Info Systems Device [1179:0001]
Kernel driver in use: nvme
Kernel modules: nvme
06:00.0 PCI bridge [0604]: Intel Corporation DSL6340 Thunderbolt 3
Bridge [Alpine Ridge 2C 2015] [8086:1576]
Kernel driver in use: pcieport
07:00.0 PCI bridge [0604]: Intel Corporation DSL6340 Thunderbolt 3
Bridge [Alpine Ridge 2C 2015] [8086:1576]
Kernel driver in use: pcieport
07:01.0 PCI bridge [0604]: Intel Corporation DSL6340 Thunderbolt 3
Bridge [Alpine Ridge 2C 2015] [8086:1576]
Kernel driver in use: pcieport
07:02.0 PCI bridge [0604]: Intel Corporation DSL6340 Thunderbolt 3
Bridge [Alpine Ridge 2C 2015] [8086:1576]
Kernel driver in use: pcieport
0a:00.0 USB controller [0c03]: Intel Corporation DSL6340 USB 3.1
Controller [Alpine Ridge] [8086:15b5]
Subsystem: Device [:]
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci



Base System In

Bug#868993: qtvirtualkeyboard-opensource-src: FTBFS: test crashes

2017-07-19 Thread Aaron M. Ucko

Source: qtvirtualkeyboard-opensource-src
Version: 5.7.1+dfsg-2
Severity: important
Justification: fails to build from source

Builds of qtvirtualkeyboard-opensource-src failed on several
architectures because tst_inputpanel crashed, with "Illegal
instruction" on armhf and "Segmentation fault" on mips, mips64el, and
the non-release architecture sparc64.  (The mipsel build succeeded,
though.)

Could you please take a look?

Thanks!

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Bug#868992: python-ltfatpy: FTBFS on hurd-i386: No module named 'matplotlib._path'

2017-07-19 Thread Aaron M. Ucko

Source: python-ltfatpy
Version: 1.0.9-1
Severity: important
Justification: fails to build from source

Thanks for taking care of #861094.  Alas, the build of python-ltfatpy
on hurd-i386 (admittedly not a release architecture) is still failing:

  E   ModuleNotFoundError: No module named 'matplotlib._path'

I see that hurd-i386 still just has matplotlib 1.5.x, whereas the
other architectures have 2.x; please version the build dependencies on
python(3)-matplotlib accordingly.

Thanks!

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Bug#756397: Link to the new tracker: new patch

2017-07-19 Thread Paul Wise

On Wed, 2017-07-19 at 15:12 +0200, Muri Nicanor wrote:

> Not sure about "Developer Information" though, the tracker gives
> information about packages, not about developers, imo

The phrase is supposed to indicate information for developers rather
than information about developers, AFAICT.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part

Bug#868991: libgpuarray: FTBFS with cython 0.23

2017-07-19 Thread Aaron M. Ucko

Source: libgpuarray
Version: 0.6.8-1
Severity: important
Justification: fails to build from source

Builds of libgpuarray for the non-release architectures hurd-i386 and
x32 (on both of which cython 0.23.x is the latest available version):

  Exception: cython is too old or not installed (at least 0.25 required)

Please version the build dependency on cython accordingly.

Thanks!

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Bug#868990: lazarus: FTBFS: Architecture mips(el) is not available for elf format

2017-07-19 Thread Aaron M. Ucko

Source: lazarus
Version: 1.8.0~rc3+dfsg-2
Severity: important
Justification: fails to build from source

Builds of lazarus for mips and mipsel failed with errors of the form

  Error: Architecture mips(el) is not available for elf format
  lazbuild.lpr(1871) Error: (9029) Error while compiling resources
  lazbuild.lpr(1871) Fatal: (10026) There were 1 errors compiling module, 
stopping
  Fatal: (1018) Compilation aborted
  Makefile:3967: recipe for target 'lazbuild' failed
  make[3]: *** [lazbuild] Error 1

Could you please take a look?

Thanks!

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Bug#868989: haskell-doctemplates: FTBFS: unknown RTS option: -N

2017-07-19 Thread Aaron M. Ucko

Source: haskell-doctemplates
Version: 0.1.0.2-1
Severity: important
Justification: fails to build from source

Builds of haskell-doctemplates failed on arm64, armel, mips, mips64,
mipsel, and s390x with the error

  doctemplates-test: unknown RTS option: -N

Could you please either limit the use of this option to the
architectures that support it or leave it off altogether?

Thanks!

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Bug#855887: python3-parsedate in unstable

2017-07-19 Thread Jelmer Vernooĳ

FYI python3-parsedate has now made it to unstable.
https://packages.debian.org/sid/python3-parsedatetime


signature.asc
Description: PGP signature

Bug#868988: phamm: CVE-2017-0378 reflected XSS in phamm

2017-07-19 Thread John Lightsey

Source: phamm
Severity: important
Tags: upstream security

While looking through codesearch.debian.net I noticed that phamm's 
views/helpers.php uses $_SERVER['PHP_SELF'] in a way that is vulnerable to 
reflected XSS attacks.

To reproduce the problem, load a URL like this in Firefox:

http://127.0.0.1/phamm/main.php/%22%3E%3Cscript%3Ealert%28123%29%3C/script%3E

The Debian Security team assigned this issue CVE-2017-0378

Upstream bug report is here: https://github.com/lota/phamm/issues/21

-- System Information:
Debian Release: 9.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#868987: gopass: FTBFS w/gccgo: TestVersion* fails

2017-07-19 Thread Aaron M. Ucko

Source: gopass
Version: 1.0.5-1
Severity: important
Justification: fails to build from source

Builds of gopass on those architectures on which only gccgo is
available have been failing, generally because TestVersionNotUnknown
and TestVersionNoLetters report assertion failures:

  === RUN   TestVersionNotUnknown
  --- FAIL: TestVersionNotUnknown (0.00s)
assertions.go:239: 

Error Trace:version_test.go:28

Error:  Should not be: "UNKNOWN"
  === RUN   TestVersionNoLetters
  --- FAIL: TestVersionNoLetters (0.00s)
assertions.go:239: 

Error Trace:version_test.go:33

Error:  Should be false

(The second error repeats six more times.)

Specifically, I observe this behavior on mips, mips64el, s390x, and
the non-release architectures alpha and powerpc.  (As for the
remaining gccgo-only platforms, the toolchain crashes on mipsel and
sparc64, and the standard library fails to show up on x32.  I don't
think any of that's specific to gopass, though.)

Could you please take a look, and either fix these builds or
specifically build depend on golang-go?

Thanks!

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Bug#868986: debmake: Debmake provided Upstart template has wrong filename

2017-07-19 Thread 林博仁

Package: debmake
Version: 4.2.9-1
Severity: minor

Dear Maintainer,

`debmake -x 3` provided `.upstrat.ex` file, which should be named
`.upstart.ex`.

Thanks,
林博仁 



-- System Information:
Debian Release: stretch/sid
  APT prefers xenial-updates
  APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500, 
'xenial'), (100, 'xenial-backports'), (99, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.8.0-58-generic (SMP w/4 CPU cores)
Locale: LANG=zh_TW.UTF-8, LC_CTYPE=zh_TW.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages debmake depends on:
ii  devscripts   2.16.2ubuntu3
ii  dpkg-dev 1.18.4ubuntu1.2
pn  python3:any  
ii  rsync3.1.1-3ubuntu1

Versions of packages debmake recommends:
ii  build-essential  12.1ubuntu2
ii  curl 7.47.0-1ubuntu2.2
ii  strace   4.11-1ubuntu3
ii  wget 1.17.1-1ubuntu1.2

Versions of packages debmake suggests:
ii  autotools-dev 20150820.1
pn  ccache
ii  cmake 3.5.1-1ubuntu3
pn  cowbuilder
ii  dh-autoreconf 11
ii  dh-python 2.20151103ubuntu1.1
pn  eatmydata 
pn  gem2deb   
ii  git   1:2.7.4-0ubuntu1.1
pn  git-buildpackage  
pn  gitk  
pn  javahelper
ii  lintian   2.5.43ubuntu0.1
ii  mc3:4.8.15-2
pn  pbuilder  
ii  quilt 0.63-3
pn  rpm2cpio  

-- no debconf information

Bug#866389: transition: perl 5.26

2017-07-19 Thread Paul Wise

On Thu, Jul 20, 2017 at 5:04 AM, gregor herrmann wrote:

> #867213: syslog-ng-incubator: one rdep (syslog-ng). No reaction on
>  the bug report, unrelated build failure; I guess syslog-ng*
>  can be removed from testing if noone fixes the problem in
>  time.

I'd like to point out that DSA relies on syslog-ng on debian.org
hosts, so it would be appreciated if the issues could be fixed or
worked around rather than removing syslog-ng from buster. Of course
buster is not in use on any debian.org hosts yet.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

Bug#790198: banshee: depends on libwebkitgtk-1.0-0 which is deprecated

2017-07-19 Thread Jeremy Bicha

Control: reopen -1
Control: found -1 2.6.2-6.1

It is inappropriate to close this bug until this bug is actually fixed
in unstable.

Why don't you try backporting this commit instead?

https://anonscm.debian.org/cgit/pkg-cli-apps/packages/banshee.git/commit/?id=5f5d89

Thanks,
Jeremy Bicha

Bug#868985: RM: libgrip -- RoQA; superseded by GTK+ touch support

2017-07-19 Thread Jeremy Bicha

Package: ftp.debian.org
X-Debbugs-Cc:libg...@packages.debian.org

Please remove libgrip from Debian unstable.

librip was removed from testing 2 years ago because it fails to build
from source (#789940)

libgrip was a Canonical project but it was removed from Ubuntu earlier
this year because it is not used any more now that GTK+ has improved
its native touch support.
https://launchpad.net/bugs/1623858

Thank you,
Jeremy Bicha

Bug#778878: apt update cannot verify public keys (clean install).

2017-07-19 Thread Mark Henwood

Package: apt
Version: 1.4.6
Followup-For: Bug #778878

Clean install of SMP Debian 4.9.30-2+deb9u2 (2017-06-26) x86_64 GNU/Linux on an
HP G62-144DX with 4G of memory, 500G HD and Intel® Core™ i3 CPU M 330 @ 2.13GHz
× 4 Everything working fine. I had updated the apt repository a couple of times
to make sure there were no updates so I know it was working before I tried to
add non-free.

After choosing "DFSG-compatible Softwear with Non-Free Dependencies (contrib)"
in synaptic apt became "unhappy." I have tried looking for answers but am
either in the wrong places or it's just me (i.e. Murphy's law).

When apt-get update is called I get the following:

# apt update
Ign:1 http://ftp.us.debian.org/debian stretch InRelease
Hit:2 http://ftp.us.debian.org/debian stretch-updates InRelease
Hit:3 http://ftp.us.debian.org/debian stretch Release
Err:2 http://ftp.us.debian.org/debian stretch-updates InRelease
  The following signatures couldn't be verified because the public key is not
available: NO_PUBKEY 8B48AD6246925553 NO_PUBKEY 7638D0442B90D010
Hit:4 http://security.debian.org/debian-security stretch/updates InRelease
Err:5 http://ftp.us.debian.org/debian stretch Release.gpg
  The following signatures couldn't be verified because the public key is not
available: NO_PUBKEY 8B48AD6246925553 NO_PUBKEY 7638D0442B90D010 NO_PUBKEY
CBF8D6FD518E17E1 NO_PUBKEY EF0F382A1A7B6500
Err:4 http://security.debian.org/debian-security stretch/updates InRelease
  The following signatures couldn't be verified because the public key is not
available: NO_PUBKEY 9D6D8F6BC857C906 NO_PUBKEY 8B48AD6246925553
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.
W: An error occurred during the signature verification. The repository is not
updated and the previous index files will be used. GPG error:
http://ftp.us.debian.org/debian stretch-updates InRelease: The following
signatures couldn't be verified because the public key is not available:
NO_PUBKEY 8B48AD6246925553 NO_PUBKEY 7638D0442B90D010
W: An error occurred during the signature verification. The repository is not
updated and the previous index files will be used. GPG error:
http://ftp.us.debian.org/debian stretch Release: The following signatures
couldn't be verified because the public key is not available: NO_PUBKEY
8B48AD6246925553 NO_PUBKEY 7638D0442B90D010 NO_PUBKEY CBF8D6FD518E17E1
NO_PUBKEY EF0F382A1A7B6500
W: An error occurred during the signature verification. The repository is not
updated and the previous index files will be used. GPG error:
http://security.debian.org/debian-security stretch/updates InRelease: The
following signatures couldn't be verified because the public key is not
available: NO_PUBKEY 9D6D8F6BC857C906 NO_PUBKEY 8B48AD6246925553
W: Failed to fetch http://security.debian.org/debian-
security/dists/stretch/updates/InRelease  The following signatures couldn't be
verified because the public key is not available: NO_PUBKEY 9D6D8F6BC857C906
NO_PUBKEY 8B48AD6246925553
W: Failed to fetch http://ftp.us.debian.org/debian/dists/stretch-
updates/InRelease  The following signatures couldn't be verified because the
public key is not available: NO_PUBKEY 8B48AD6246925553 NO_PUBKEY
7638D0442B90D010
W: Failed to fetch http://ftp.us.debian.org/debian/dists/stretch/Release.gpg
The following signatures couldn't be verified because the public key is not
available: NO_PUBKEY 8B48AD6246925553 NO_PUBKEY 7638D0442B90D010 NO_PUBKEY
CBF8D6FD518E17E1 NO_PUBKEY EF0F382A1A7B6500
W: Some index files failed to download. They have been ignored, or old ones
used instead.

I tried going back by unchecking the option in Synaptic and by copying
sources.list.saved to sources.list with no luck.
As far as I can tell apt-key has all the keys that update is griping about.
Here are the relavent outputs I can think of:

Sources.list after the fall:

#

# deb cdrom:[Debian GNU/Linux 9.0.0 _Stretch_ - Official amd64 NETINST
20170617-13:06]/ stretch main

# deb cdrom:[Debian GNU/Linux 9.0.0 _Stretch_ - Official amd64 NETINST
20170617-13:06]/ stretch main

deb http://ftp.us.debian.org/debian/ stretch main contrib
deb-src http://ftp.us.debian.org/debian/ stretch main contrib

deb http://security.debian.org/debian-security stretch/updates main contrib
deb-src http://security.debian.org/debian-security stretch/updates main contrib

# stretch-updates, previously known as 'volatile'
deb http://ftp.us.debian.org/debian/ stretch-updates main contrib
deb-src http://ftp.us.debian.org/debian/ stretch-updates main contrib

apt-key list:

# apt-key list
/etc/apt/trusted.gpg.d/debian-archive-jessie-automatic.gpg
--
pub   rsa4096 2014-11-21 [SC] [expires: 2022-11-19]
  126C 0D24 BD8A 2942 CC7D  F8AC 7638 D044 2B90 D010
uid   [ unknown] Debian Archive Automatic Signing Key (8/jessie)


/etc/apt/trusted.gpg.d/debian-archive-jessie-security-automatic.gpg
---

Bug#803924: -HUP needs to be sent more broadly

2017-07-19 Thread Andrew Bartlett

Thinking about this some more, in the multi-process architecture of the
AD DC, the -HUP will need to go to every samba process - just making
the master process reload won't do anything for the children, as far as
I'm aware. 

That said, wildly sending SIGHUP with killall wouldn't be wise either. 
This is going to need code changes to do properly - adding the reopen-
logs smbcontrol as I mention, and having the parent process be
responsible for telling the children, or broadcast it, if that hasn't
been rewritten out.

Andrew Bartlett
-- 
Andrew Bartlett   http://samba.org/~abartlet/
Authentication Developer, Samba Team  http://samba.org
Samba Developer, Catalyst IT  http://catalyst.net.nz/services/samba

Bug#848838: sugar-write-activity: constant flicker of cursor and document

2017-07-19 Thread Jeremy Bicha

This is likely a duplicate of https://bugs.debian.org/851052 since
sugar-read-activity depends on the Abiword GObject Introspection
package.

Thanks,
Jeremy Bicha

Bug#864074: defaults.vim: broken configuration

2017-07-19 Thread Martin Steigerwald

James, did you intend to send this just to me? To be on safe side, I reply to 
you only, but I really think this should also go to the bug report.

James McCoy - 18.07.17, 20:21:
> On Sat, Jul 08, 2017 at 11:36:07PM +0200, Martin Steigerwald wrote:
> > James McCoy - 05.07.17, 21:09:
[…]
> > My order wasn´t complete. I think it should be:
> > 
> > 1. Global vim configuration
> > 2. /etc/vim/vimrc.local
> > 3. $HOME/.vimrc
> > 4. defaults.vim
> > 
> > so that defaults.vim can only ever set any setting that has *not* been set
> > by any of the other configuration files.
> 
> Then you would actually want defaults.vim to be first, so that anything
> else set overrides it.  You can do exactly that by putting this in your
> /etc/vim/vimrc.local:
> 
> " Explicitly source defaults.vim so you can override its settings
> source $VIMRUNTIME/defaults.vim
> " Prevent it from being loaded again later if the user doesn't have
> " a vimrc
> let skip_defaults_vim = 1

And all that just to restore some sanity to the VIM configuration… well…

> > It is completely unintuitive that defaults.vim overwrites settings in
> > vimrc.local by default. If I write "set mouse=" in there, I mean it. I
> > really dislike software that pretends it knows better than me unless I
> > tell that software to stop that behavior.
> > 
> > Never *ever* overwrite user/admin made settings.
> 
> Yes, that was another part that Bram just punted on when he was deciding
> how defaults.vim would work.

I may look at a vim fork that doesn´t adopt this nonsense.

> > > defaults.vim is intentionally loaded _after_ $HOME/.vimrc so that Vim
> > > can choose not to load it when $HOME/.vimrc exists.  The situation
> > > you're running into is that you don't have $HOME/.vimrc and therefore
> > > are having the system-wide values adjusted by defaults.vim.
> > 
> > Alternatively vim should not load defaults.vim if vimrc.local exists I
> > think.
> /etc/vim/vimrc is the only thing Vim knows about.  It just happens to
> have a snippet at the end which sources /etc/vim/vimrc.local.
> 
> If anything, I'll add a commented out version of the code I posted
> above to /etc/vim/vimrc.  I thought this sort of stuff would be easily
> figured out for people that wanted to customize the behavior, but
> apparently I was wrong.

This is… I already use "let skip_defaults_vim = 1". I found this before 
already, and I think apt-listchanges showed me your update to NEWS.Debian.

But the issue with this is: Now by default the VIM configuration is *broken* in 
several ways which I described on *every* newly installed *or* upgraded Debian 
system. Which needs adapting the configuration every newly installed system.

For *what* benefit?

Well, I bet I´d need to file an issue with upstream about that.

Thanks,
-- 
Martin

Bug#868722: transition: notmuch

2017-07-19 Thread David Bremner

Emilio Pozuelo Monfort  writes:
>
> Up to you what happens with notmuch-addrlookup, as long as it gets fixed. With
> that said, you can go ahead.
>

I have uploaded an NMU of notmuch-addrlookup to delayed/5

Bug#864074: defaults.vim: broken configuration

2017-07-19 Thread James McCoy

On Sat, Jul 08, 2017 at 11:36:07PM +0200, Martin Steigerwald wrote:
> James McCoy - 05.07.17, 21:09:
> > This _is_ the behavior.  The _only_ way that defaults.vim is used is
> > when $HOME/.vimrc doesn't exist.
> > 
> > Note that /etc/vim/vimrc.local is a Debian-specific extension of the
> > system-wide vimrc, to avoid conffile prompts during upgrades, so 1 & 2
> > are the same thing.
> 
> My order wasn´t complete. I think it should be:
> 
> 1. Global vim configuration
> 2. /etc/vim/vimrc.local
> 3. $HOME/.vimrc
> 4. defaults.vim
> 
> so that defaults.vim can only ever set any setting that has *not* been set by 
> any of the other configuration files.

Then you would actually want defaults.vim to be first, so that anything
else set overrides it.  You can do exactly that by putting this in your
/etc/vim/vimrc.local:

" Explicitly source defaults.vim so you can override its settings
source $VIMRUNTIME/defaults.vim
" Prevent it from being loaded again later if the user doesn't have
" a vimrc
let skip_defaults_vim = 1
" Disable the settings you don't like
set mouse=

> It is completely unintuitive that defaults.vim overwrites settings in 
> vimrc.local by default. If I write "set mouse=" in there, I mean it. I really 
> dislike software that pretends it knows better than me unless I tell that 
> software to stop that behavior.
> 
> Never *ever* overwrite user/admin made settings.

Yes, that was another part that Bram just punted on when he was deciding
how defaults.vim would work.

> > defaults.vim is intentionally loaded _after_ $HOME/.vimrc so that Vim
> > can choose not to load it when $HOME/.vimrc exists.  The situation
> > you're running into is that you don't have $HOME/.vimrc and therefore
> > are having the system-wide values adjusted by defaults.vim.
> 
> Alternatively vim should not load defaults.vim if vimrc.local exists I think.

/etc/vim/vimrc is the only thing Vim knows about.  It just happens to
have a snippet at the end which sources /etc/vim/vimrc.local.

If anything, I'll add a commented out version of the code I posted
above to /etc/vim/vimrc.  I thought this sort of stuff would be easily
figured out for people that wanted to customize the behavior, but
apparently I was wrong.

Cheers,
-- 
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7  2D23 DFE6 91AE 331B A3DB

Bug#864074: defaults.vim: broken configuration

2017-07-19 Thread James McCoy

On Wed, Jul 19, 2017 at 11:38:40PM +0200, Martin Steigerwald wrote:
> James, did you intend to send this just to me?

I didn't.

> To be on safe side, I reply to 
> you only, but I really think this should also go to the bug report.

Agreed. I'll bounce the last two messages to the bug.

> James McCoy - 18.07.17, 20:21:
> > On Sat, Jul 08, 2017 at 11:36:07PM +0200, Martin Steigerwald wrote:
> > > James McCoy - 05.07.17, 21:09:
> […]
> > > My order wasn´t complete. I think it should be:
> > > 
> > > 1. Global vim configuration
> > > 2. /etc/vim/vimrc.local
> > > 3. $HOME/.vimrc
> > > 4. defaults.vim
> > > 
> > > so that defaults.vim can only ever set any setting that has *not* been set
> > > by any of the other configuration files.
> > 
> > Then you would actually want defaults.vim to be first, so that anything
> > else set overrides it.  You can do exactly that by putting this in your
> > /etc/vim/vimrc.local:
> > 
> > " Explicitly source defaults.vim so you can override its settings
> > source $VIMRUNTIME/defaults.vim
> > " Prevent it from being loaded again later if the user doesn't have
> > " a vimrc
> > let skip_defaults_vim = 1
> 
> And all that just to restore some sanity to the VIM configuration… well…

I understand the feeling, but I also dislike deviating from default
configurations since that makes it harder for people to switch between
systems.  That's why I've suggested raising the issue upstream.

> > > It is completely unintuitive that defaults.vim overwrites settings in
> > > vimrc.local by default. If I write "set mouse=" in there, I mean it. I
> > > really dislike software that pretends it knows better than me unless I
> > > tell that software to stop that behavior.
> > > 
> > > Never *ever* overwrite user/admin made settings.
> > 
> > Yes, that was another part that Bram just punted on when he was deciding
> > how defaults.vim would work.
> 
> I may look at a vim fork that doesn´t adopt this nonsense.

Neovim bakes in saner defaults, which avoids all this jumping through
hoops when you want to deviate from them.

> But the issue with this is: Now by default the VIM configuration is *broken* 
> in 
> several ways which I described on *every* newly installed *or* upgraded 
> Debian 
> system. Which needs adapting the configuration every newly installed system.
> 
> For *what* benefit?

Many of the changes *are* useful to enable, but 'mouse' in particular
was a poor choice and the interaction with system-wide vimrc was an even
poorer one.

Cheers,
-- 
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7  2D23 DFE6 91AE 331B A3DB

Bug#868664: git repo

2017-07-19 Thread David Bremner


In case it's useful, my work from making the NMU can be found in

   https://anonscm.debian.org/git/users/bremner/notmuch-addrlookup.git

Bug#844933: Unable to reproduce FTBFS with network

2017-07-19 Thread Rudy Godoy Guillén

I'm unable to reproduce the FTBFS under up to date amd64 sid environment.
The error is most likely due network unavailability to access
testmerchant.org for the PaymentServer::processPaymentRequest test case
when building automatically.

One solution is to exclude this test for the Qt client since automated
building doesn't assume network availability.

-- 
Rudy Godoy
http://stone-head.org

Bug#860413: closed by Matthias Klose (Re: Bug#860413: use names that won't collide with other programs')

2017-07-19 Thread 積丹尼 Dan Jacobson

B> I can't see any other package / upstream software providing a 2to3-2.7
B> executable.

Yes, but it is a bad habit. Imagine if every package did this this. /usr/bin
would be littered...

Bug#868664: notmuch-addrlookup: diff for NMU version 8-0.1

2017-07-19 Thread David Bremner

Control: tags 868664 + patch
Control: tags 868664 + pending

Dear maintainer,

I've prepared an NMU for notmuch-addrlookup (versioned as 8-0.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

Although it's a bit unusual to NMU a new upstream version, the actual
diff is relatively small.

d
diff -Nru notmuch-addrlookup-5/CHANGELOG.md notmuch-addrlookup-8/CHANGELOG.md
--- notmuch-addrlookup-5/CHANGELOG.md	1969-12-31 20:00:00.0 -0400
+++ notmuch-addrlookup-8/CHANGELOG.md	2017-02-07 06:24:11.0 -0400
@@ -0,0 +1,61 @@
+# Change Log
+All notable changes to this project will be documented in this file.
+
+## [Unreleased]
+
+## [8] - 2017-02-07
+### Fixed
+- Avoid a segmentation fault when `notmuch_message_get_header()` returns
+  `NULL`. (Patch by Víctor M. Jáquez
+  <[vjaq...@igalia.com](mailto:vjaq...@igalia.com)>).
+
+## [7] - 2016-01-09
+### Fixed
+- Do not use functions deprecated starting with `libnotmuch` 4.3; building
+  against older versions is still possible.
+
+## [6] - 2015-11-06
+### Added
+- This change log file.
+
+### Fixed
+- Fix sorting of results. (Patch by Jeremy Simon
+  <[jtsy...@gmail.com](mailto:jtsy...@gmail.com)>.)
+
+## [5] - 2015-06-05
+### Fixed
+- Normal output was missing angle brackets around e-mail addresses. This issue
+  is fixed in this release.
+
+## [4] - 2015-05-21
+### Fixed
+- Allow building with versions of Glib older than 2.44. (Patch by `cellscape`
+  <[m...@nooff.info](mailto:m...@nooff.info)>.)
+
+## [3] - 2015-05-19
+### Added
+- Support output in a Mutt-compatible format. This allows using
+  `notmuch-addrlookup --mutt` directly in for Mutt's `query_command`
+  setting.
+
+### Changed
+- Parsing of command line arguments is now done using Glib.
+
+## [2] - 2015-05-12
+### Fixed
+- Reverse sorting of results, so most frequently contacted addresses are
+  sorted first. (Patch by Leonhard Markert.)
+
+## [1] - 2015-01-05
+### Added
+- First working version of `notmuch-addrlookup`.
+
+[Unreleased]: https://github.com/aperezdc/notmuch-addrlookup-c/compare/v8...HEAD
+[8]: https://github.com/aperezdc/notmuch-addrlookup-c/compare/v7...v8
+[7]: https://github.com/aperezdc/notmuch-addrlookup-c/compare/v6...v7
+[6]: https://github.com/aperezdc/notmuch-addrlookup-c/compare/v5...v6
+[5]: https://github.com/aperezdc/notmuch-addrlookup-c/compare/v4...v5
+[4]: https://github.com/aperezdc/notmuch-addrlookup-c/compare/v3...v4
+[3]: https://github.com/aperezdc/notmuch-addrlookup-c/compare/v2...v3
+[2]: https://github.com/aperezdc/notmuch-addrlookup-c/compare/v1...v2
+[1]: https://github.com/aperezdc/notmuch-addrlookup-c/compare/a9364d4...v1
diff -Nru notmuch-addrlookup-5/debian/changelog notmuch-addrlookup-8/debian/changelog
--- notmuch-addrlookup-5/debian/changelog	2015-06-19 06:12:31.0 -0300
+++ notmuch-addrlookup-8/debian/changelog	2017-07-19 07:32:40.0 -0300
@@ -1,3 +1,11 @@
+notmuch-addrlookup (8-0.1) unstable; urgency=medium
+
+  * Non maintainer upload
+  * New upstream release
+  * Stop using deprecated/removed API (Closes: #868664).
+
+ -- David Bremner   Wed, 19 Jul 2017 07:32:40 -0300
+
 notmuch-addrlookup (5-1) unstable; urgency=low
 
   * Initial release (Closes: #790873)
diff -Nru notmuch-addrlookup-5/notmuch-addrlookup.c notmuch-addrlookup-8/notmuch-addrlookup.c
--- notmuch-addrlookup-5/notmuch-addrlookup.c	2015-06-05 08:02:50.0 -0300
+++ notmuch-addrlookup-8/notmuch-addrlookup.c	2017-02-07 06:24:11.0 -0400
@@ -1,6 +1,6 @@
 /*
  * notmuch-addrlookup.c
- * Copyright (C) 2014-2015 Adrian Perez 
+ * Copyright (C) 2014-2016 Adrian Perez 
  *
  * Distributed under terms of the MIT license.
  */
@@ -164,9 +164,20 @@
   queries[1] = notmuch_query_create (db, sbuf);
   g_free (sbuf);
 
+#if LIBNOTMUCH_MAJOR_VERSION >= 4 && LIBNOTMUCH_MINOR_VERSION >= 3
+  unsigned int count = 0;
+  unsigned int tmp;
+  if (notmuch_query_count_messages_st (queries[0], &tmp) == NOTMUCH_STATUS_SUCCESS)
+  count += tmp;
+  if (notmuch_query_count_messages_st (queries[1], &tmp) == NOTMUCH_STATUS_SUCCESS)
+  count += tmp;
+#else
+  unsigned int count = notmuch_query_count_messages (queries[0])
+ + notmuch_query_count_messages (queries[1]);
+#endif
+
   /* Pass 3: With only a few hits, add all the "from:" addresses */
-  if (notmuch_query_count_messages (queries[0]) +
-  notmuch_query_count_messages (queries[1]) < 10)
+  if (count < 10)
 {
   qs = g_string_new ("");
   if (name)
@@ -217,16 +228,24 @@
 continue;
 
   const gchar **headers = (i == 1) ? headers_pass1 : headers_pass0;
+  notmuch_messages_t *messages = NULL;
+
+#if LIBNOTMUCH_MAJOR_VERSION >= 4 && LIBNOTMUCH_MINOR_VERSION >= 3
+  if (notmuch_query_search_messages_st (queries[i], &messages) != NOTMUCH_STATUS_SUCCESS)
+  continue;
+#else
+  if (!(messages = notmuch_query_search_messages (queries[i])))
+  continue;
+#endif
 
-  for (notmuch_messages_t *messages = notmuc

Bug#868984: RM: xombrero -- RoQA; RC-buggy, dead upstream

2017-07-19 Thread Adam Borowski

Package: ftp.debian.org
Severity: normal


xombrero's upstream sez:
xombrero has been retired and is no longer under development and
supported.

A browser that has no security support, is unmaintained both upstream and in
Debian, and depends on an old version of webkit...  it's time for it to go.

Bug#868960: FTBFS with ocaml 4.05.0

2017-07-19 Thread Stéphane Glondu

tags 868960 + patch
thanks

On 20/07/2017 00:32, Stéphane Glondu wrote:
> A possible fix is to compile files in ./src/xml2modelica without the "-I
> ./src/modelica_compiler" option.

Attached is a patch (to be dropped in debian/patches) that does that. It
should be compatible with the ocaml currently in unstable. Please upload
as soon as possible, to ease the future OCaml transition.

Cheers,

-- 
Stéphane
Description: Fix FTBFS with OCaml 4.05.0
Author: StÃ©phane Glondu 
Bug-Debian: https://bugs.debian.org/868960
Last-Update: 2017-07-19

--- scilab-5.5.2.orig/modules/scicos/Makefile.modelica.am
+++ scilab-5.5.2/modules/scicos/Makefile.modelica.am
@@ -98,6 +98,7 @@ MLIS_modelicac = $(MLS:.ml=.mli)
 BASE_PATH_MODELICAC = $(srcdir)/src/modelica_compiler
 
 INCLUDE = -I $(BASE_PATH_MODELICAC) -I $(BASE_PATH_XML2Modelica)
+INCLUDE_xml2modelica = -I $(BASE_PATH_XML2Modelica)
 
 ## COMMON
 SUFFIXES += .ml .mli .mll .mly .cmo .cmi .cmx
@@ -108,6 +109,9 @@ SUFFIXES += .ml .mli .mll .mly .cmo .cmi
 	@if echo "$<"|grep src/translator; then \
 		echo $(OCAMLC) $(INCLUDE_modelicat) $(OCAMLCFLAGS) -c $*.ml; \
 		$(OCAMLC) $(INCLUDE_modelicat) $(OCAMLCFLAGS) -c $*.ml; \
+	elif echo "$<"|grep src/xml2modelica; then \
+		echo $(OCAMLC) $(INCLUDE_xml2modelica) $(OCAMLCFLAGS) -c $*.ml; \
+		$(OCAMLC) $(INCLUDE_xml2modelica) $(OCAMLCFLAGS) -c $*.ml; \
 	else \
 		echo $(OCAMLC) $(INCLUDE) $(OCAMLCFLAGS) -c $*.ml; \
 		$(OCAMLC) $(INCLUDE) $(OCAMLCFLAGS) -c $*.ml; \
@@ -117,6 +121,9 @@ SUFFIXES += .ml .mli .mll .mly .cmo .cmi
 	@if echo "$<"|grep src/translator; then \
 		echo $(OCAMLOPT) $(INCLUDE_modelicat) $(OCAMLOPTFLAGS) -c $*.ml; \
 		$(OCAMLOPT) $(INCLUDE_modelicat) $(OCAMLOPTFLAGS) -c $*.ml; \
+	elif echo "$<"|grep src/xml2modelica; then \
+		echo $(OCAMLOPT) $(INCLUDE_xml2modelica) $(OCAMLOPTFLAGS) -c $*.ml; \
+		$(OCAMLOPT) $(INCLUDE_xml2modelica) $(OCAMLOPTFLAGS) -c $*.ml; \
 	else \
 		echo $(OCAMLOPT) $(INCLUDE) $(OCAMLOPTFLAGS) -c $*.ml; \
 		$(OCAMLOPT) $(INCLUDE) $(OCAMLOPTFLAGS) -c $*.ml; \
@@ -126,6 +133,9 @@ SUFFIXES += .ml .mli .mll .mly .cmo .cmi
 	@if echo "$<"|grep src/translator; then \
 		echo $(OCAMLC) $(INCLUDE_modelicat) $(OCAMLCFLAGS) -c $<; \
 		$(OCAMLC) $(INCLUDE_modelicat) $(OCAMLCFLAGS) -c $<; \
+	elif echo "$<"|grep src/xml2modelica; then \
+		echo $(OCAMLC) $(INCLUDE_xml2modelica) $(OCAMLCFLAGS) -c $<; \
+		$(OCAMLC) $(INCLUDE_xml2modelica) $(OCAMLCFLAGS) -c $<; \
 	else \
 		echo $(OCAMLC) $(INCLUDE) $(OCAMLCFLAGS) -c $<; \
 		$(OCAMLC) $(INCLUDE) $(OCAMLCFLAGS) -c $<; \
@@ -135,6 +145,9 @@ SUFFIXES += .ml .mli .mll .mly .cmo .cmi
 	@if echo "$<"|grep src/translator; then \
 		echo $(OCAMLC) $(INCLUDE_modelicat) $(OCAMLCFLAGS) -i $< > $@; \
 		$(OCAMLC) $(INCLUDE_modelicat) $(OCAMLCFLAGS) -i $< > $@; \
+	elif echo "$<"|grep src/xml2modelica; then \
+		echo $(OCAMLC) $(INCLUDE_xml2modelica) $(OCAMLCFLAGS) -i $< > $@; \
+		$(OCAMLC) $(INCLUDE_xml2modelica) $(OCAMLCFLAGS) -i $< > $@; \
 	else \
 		echo $(OCAMLC) $(INCLUDE) $(OCAMLCFLAGS) -i $< > $@; \
 		$(OCAMLC) $(INCLUDE) $(OCAMLCFLAGS) -i $< > $@; \

Bug#868960: FTBFS with ocaml 4.05.0

2017-07-19 Thread Stéphane Glondu

On 19/07/2017 23:21, Stéphane Glondu wrote:
> scilab FTBFS with ocaml 4.05.0. Relevant log:
>> [...]
>> ocamlopt -o XML2Modelica -I ./src/modelica_compiler -I ./src/xml2modelica  
>> nums.cmxa ./src/xml2modelica/xMLTree.cmx ./src/xml2modelica/linenum.cmx 
>> ./src/xml2modelica/stringParser.cmx ./src/xml2modelica/stringLexer.cmx 
>> ./src/xml2modelica/xMLParser.cmx ./src/xml2modelica/xMLLexer.cmx 
>> ./src/xml2modelica/modelicaCodeGenerator.cmx 
>> ./src/xml2modelica/xML2Modelica.cmx
>> File "_none_", line 1:
>> Error: Files ./src/xml2modelica/xMLParser.cmx
>>and ./src/xml2modelica/linenum.cmx
>>make inconsistent assumptions over implementation Linenum
>> Makefile:3387: recipe for target 'XML2Modelica' failed
>> make[3]: *** [XML2Modelica] Error 2
>> make[3]: Leaving directory '/tmp/scilab-5.5.2/modules/scicos'
>> Makefile:808: recipe for target 'all-recursive' failed
>> make[2]: *** [all-recursive] Error 1
>> make[2]: Leaving directory '/tmp/scilab-5.5.2/modules'
>> Makefile:1554: recipe for target 'all-recursive' failed
>> make[1]: *** [all-recursive] Error 1
>> make[1]: Leaving directory '/tmp/scilab-5.5.2'
>> /usr/share/cdbs/1/class/makefile.mk:77: recipe for target 
>> 'debian/stamp-makefile-build' failed
>> make: *** [debian/stamp-makefile-build] Error 2
>> dpkg-buildpackage: error: debian/rules build gave error exit status 2

An explanation: files in ./src/xml2modelica are compiled with "-I
./src/modelica_compiler -I ./src/xml2modelica". The file linenum.cmx
exists in both directory, and compiling xMLParser.cmx picks up the wrong
linenum.cmx with the new version of ocaml.

A possible fix is to compile files in ./src/xml2modelica without the "-I
./src/modelica_compiler" option.


Cheers,

-- 
Stéphane

Bug#868695: systemd: leaves empty LC_CTYPE what breaks X11 ssh password prompt

2017-07-19 Thread Robert Luberda

Michael Biebl writes:

Hi,

Sorry for not replying for your previous e-mails, I was too tired
yesterday after work, and planned to do this today, but probably it
doesn't make sense anymore as you've found the commit that caused the
issue. Anyway I was pretty sure that the LC_CTYPE settings are
relevant, because before reporting the bug I tried to comment them
out, what fixed the problem. But than I noticed that those settings
were present also in the previous version, but unfortunately missed
the difference in the Exec line of getty@.service, so I thought that
some change in systemd internals prevented it from clearing the
environment :(

> Am 17.07.2017 um 20:54 schrieb Robert Luberda:
>> Yes, LC_CTYPE and other LC_ variables are empty, because they are
>> set like this in /lib/systemd/system/getty@.service.
> 
> Afaics, this was broken by 
> https://github.com/systemd/systemd/pull/6023
> 
> Robert, can you try reverting the commit 
> https://github.com/systemd/systemd/commit/db6aedab9292678918f15807a0d835be35511667
>
>  and report back.

I've just replaced the getty@.service file with the version coming
from systemd 233-10, and yes, I confirm that doing this followed by
rebooting the system fixed the bug: LC_CTYPE is unset, and ssh client
shows the X11 gui prompt.

> I've created an upstream bug report in the mean time at 
> https://github.com/systemd/systemd/issues/6407
> 

Oh, I've just checked that according to
https://codesearch.debian.net/search?q=OPTION+lc-ctype
the empty LC_CTYPE might break a few other packages: kwalletcli,
scoute, and nss-passwords as well.

Thanks a lot,
robert

Bug#868983: trackballs: new upstream version available (new fork)

2017-07-19 Thread Henrique de Moraes Holschuh

Package: trackballs
Version: 1.1.4-4.3
Severity: important

According to: http://trackballs.sourceforge.net/, there is a new,
modernized fork of trackballs at: https://trackballs.github.io/.

The new versions likely fix several of the current bugs, including the
RC one that will result in this package being removed from Debian sooner
or later if it is not addressed.  Severity raised to "important" for
that reason.

Latest release: v1.2.2
https://github.com/trackballs/trackballs/releases/latest

-- System Information:
Debian Release: 9.1
  APT prefers stable-debug
  APT policy: (990, 'stable-debug'), (990, 'proposed-updates'), (990, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.38+ (SMP w/8 CPU cores)
Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-- 
  Henrique Holschuh

  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot

Bug#867718: CVE-2017-11108

2017-07-19 Thread Antoine Beaupre

For what it's worth, I can reproduce this in stretch by rebuilding with
ASAN (-lasan -fsanitize=address -fno-omit-frame-pointer).

I can also reproduce this in wheezy by running it in valgrind:

$ valgrind /usr/sbin/tcpdump -ntr poc
==26648== Memcheck, a memory error detector
==26648== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al.
==26648== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info
==26648== Command: /usr/sbin/tcpdump -ntr poc
==26648== 
reading from file poc, link-type EN10MB (Ethernet)
IP 192.168.1.94.61358 > 239.255.255.250.1900: UDP, length 133
ARP, Reply 192.168.1.1 is-at 00:e0:20:1c:27:77, length 46
==26648== Invalid read of size 2
==26648==at 0x1AA1F7: ??? (in /usr/sbin/tcpdump)
==26648==by 0x17C810: ??? (in /usr/sbin/tcpdump)
==26648==by 0x15E4F2: ??? (in /usr/sbin/tcpdump)
==26648==by 0x13FCBD: ??? (in /usr/sbin/tcpdump)
==26648==by 0x13C33E: ??? (in /usr/sbin/tcpdump)
==26648==by 0x404446F: ??? (in /usr/lib/x86_64-linux-gnu/libpcap.so.1.3.0)
==26648==by 0x4035ECE: pcap_loop (in 
/usr/lib/x86_64-linux-gnu/libpcap.so.1.3.0)
==26648==by 0x13AE68: main (in /usr/sbin/tcpdump)
==26648==  Address 0x59d168f is 3 bytes after a block of size 60 alloc'd
==26648==at 0x4C28BED: malloc (vg_replace_malloc.c:263)
==26648==by 0x4044F1B: ??? (in /usr/lib/x86_64-linux-gnu/libpcap.so.1.3.0)
==26648==by 0x4044722: pcap_fopen_offline (in 
/usr/lib/x86_64-linux-gnu/libpcap.so.1.3.0)
==26648==by 0x40448EF: pcap_open_offline (in 
/usr/lib/x86_64-linux-gnu/libpcap.so.1.3.0)
==26648==by 0x13AB4B: main (in /usr/sbin/tcpdump)
==26648== 
STP 802.1aq, Rapid STP, CIST Flags [Learn, Forward, Agreement], length 175[|stp 
175]
IP 192.168.1.131.5353 > 224.0.0.251.5353: 0 [2q] [2n][|domain]
IP 192.168.1.209.5353 > 224.0.0.251.5353: 0*- [0q] 2/0/0[|domain]

Also: there's something fishy with that POC file. I can extract the rar
file in a stretch virtualbox instance, but not out of the box, nor under
wheezy. Something odd there.

I'm trying to figure out exactly how to fix this, at this stage. It
doesn't look like upstream responded just yet, but I can already say the
following.

 1. tcpdump does try to derefence a pointer with an address value that
is user-controlled (mstp_len) in print-stp.c:478

 2. even when tcpdump doesn't crash, it fails to render the packet
properly. with -vvv, i get this:

STP 802.1aq, Rapid STP, CIST Flags [Learn, Forward, Agreement], length 175
port-role Designated, CIST root-id 8000.20:bb:c0:7b:d1:2e, CIST 
ext-pathcost 0
CIST regional-root-id 8000.20:bb:c0:7b:d1:2e, CIST port-id 8002,
message-age 0.00s, max-age 20.00s, hello-time 2.00s, 
forwarding-delay 15.00s
v3len 8, [|stp 175]

notice the trailing comma there: after the `v3len` field, there
would normally be other things there, but some overflow detection
kicks in stp_print_mstp_bpdu(), which, in turns, calls the magic
ND_TCHECK macro which detects the overflow and bails out properly

 3. therefore, -vvv doesn't trigger the bug

 4. conclusion: it may be simply a matter of calling the proper
ND_TCHECK macro before dereferencing the pointer.

Therefore, the following debdiff should fix this.

A.
diff -Nru tcpdump-4.9.0/debian/changelog tcpdump-4.9.0/debian/changelog
--- tcpdump-4.9.0/debian/changelog  2017-01-29 16:17:21.0 -0500
+++ tcpdump-4.9.0/debian/changelog  2017-07-19 18:18:26.0 -0400
@@ -1,3 +1,14 @@
+tcpdump (4.9.0-1~deb7u2) UNRELEASED; urgency=high
+
+  * Non-maintainer upload by the Security Team.
+  * CVE-2017-11108: tcpdump 4.9.0 allows remote attackers to cause a
+denial of service (heap-based buffer over-read and application crash)
+via crafted packet data. The crash occurs in the EXTRACT_16BITS
+function, called from the stp_print function for the Spanning Tree
+Protocol. (Closes: #867718)
+
+ -- Antoine Beaupré   Wed, 19 Jul 2017 18:18:26 -0400
+
 tcpdump (4.9.0-1~deb7u1) wheezy-security; urgency=high
 
   * Backport to wheezy.
diff -Nru tcpdump-4.9.0/debian/patches/CVE-2017-11108.patch 
tcpdump-4.9.0/debian/patches/CVE-2017-11108.patch
--- tcpdump-4.9.0/debian/patches/CVE-2017-11108.patch   1969-12-31 
19:00:00.0 -0500
+++ tcpdump-4.9.0/debian/patches/CVE-2017-11108.patch   2017-07-19 
18:16:26.0 -0400
@@ -0,0 +1,10 @@
+--- ./print-stp.c.orig 2017-07-19 18:13:41.163742974 -0400
 ./print-stp.c  2017-07-19 18:13:52.043952596 -0400
+@@ -475,6 +475,7 @@
+ if (stp_bpdu->protocol_version == STP_PROTO_SPB)
+ {
+   /* Validate v4 length */
++  ND_TCHECK_16BITS(p + MST_BPDU_VER3_LEN_OFFSET + mstp_len);
+   spb_len = EXTRACT_16BITS (p + MST_BPDU_VER3_LEN_OFFSET + 
mstp_len);
+   spb_len += 2;
+   if (length < (sizeof(struct stp_bpdu_) + mstp_len + spb_len) ||
diff -Nru tcpdump-4.9.0/debian/patches/series 
tcpdump-4.9.0/debian/pat

Bug#868982: RM: mtpfs -- RoQA; broken, missed two releases, has alternatives

2017-07-19 Thread Adam Borowski

Package: ftp.debian.org
Severity: normal


mtpfs stopped working in Jan 2012 due to some unrelated change elsewhere
(#654939), and no one bothered to fix it during all those years. 
Considering that a functioning alternative (jmtpfs) exists, it's probably
time for it to go.

It has a surprisingly high popcon (989) but a small vote (93), I'd guess
it's due to users in wheezy when the package still worked.

Bug#807461: lintian: check years in debian/copyright are not in the future

2017-07-19 Thread Chris Lamb

tags 807461 + pending
thanks

Fixed in Git:

  
https://anonscm.debian.org/git/lintian/lintian.git/commit/?id=9689d3c64c75162381539826953facc36f263d64


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb, Debian Project Leader
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#868366: python2.7: Exports `md5_init', causing conflicts with extension modules

2017-07-19 Thread Mark Wooding

Matthias Klose  writes:

> python uses _init for extension modules / builtins to
> initilize these.  So it's part of the ABI as well. Not sure how to
> change that.

No, it uses `initMODULE' for that:

:
: imp.load_dynamic(name, pathname[, file])
:
: [...] The name argument is used to construct the name of the
: initialization function: an external C function called initname() in
: the shared library is called. [...]

This convention isn't especially good, but at least it's documented, and
I'm not especially concerned about it.  But since you bring the subject
up: Python finds initialization functions for dynamically loaded
extension modules by calling `dlsym(obj, "initMODULE")', having
previously opened the dynamic object with `dlopen' using the flags
maintained by `sys.[gs]etdlopenflags' (Python/dynload_shlib.c:
_PyImport_GetDynLoadFunc) which default to omitting `RTLD_GLOBAL'
(Python/pystate.c:PyInterpreterState_New), so the symbol remains local
to the extension module.  For built-in extension modules, the
interpreter searches a simple table mapping module names to
initialization functions (somewhat of a tangle in Python/import.c), so
nothing legitimately depends on the dynamic symbol names.

Anyway, I don't really have a problem with `init_md5'
(Modules/md5module.c), which initializes the (builtin since 2.7.3-16)
`_md5' module, but I do have a problem with `md5_init' (Modules/md5.c),
which just initializes a hash context.

-- [mdw]

Bug#868981: gnome-system-tools: Includes obsolete pixmap files

2017-07-19 Thread Jeremy Bicha

Package: gnome-system-tools
Version: 3.0.0-6
Severity: low

gnome-system-tools ships several pixmaps but they aren't used any more
now that the menu file has been dropped. You can drop debian/pixmaps/
and debian/gnome-system-tools.install

Thanks,
Jeremy Bicha

Bug#868979: original-awk: please provide nawk symlink to awk

2017-07-19 Thread Sven Joachim

Package: original-awk
Version: 2012-12-20-6
Severity: wishlist

Even 30 years after the "new awk" appeared in Bell Labs, people seem to
think that /usr/bin/awk might be provided by an ancient program lacking
standard features, and prefer nawk over awk.

https://codesearch.debian.net/search?q=%23%21%2Fusr%2Fbin%2Fnawk

One such example is a 14 year old helper script in dpatch for which I
have just reported bug #868978.  While such problems should be fixed,
maybe it would make sense for original-awk to provide a /usr/bin/nawk
symlink like mawk and gawk do.


-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (101, 'experimental')
Architecture: i386 (x86_64)
Foreign Architectures: amd64

Kernel: Linux 4.12.2-nouveau (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE= (charmap=UTF-8), LANGUAGE= (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages original-awk depends on:
ii  libc6  2.24-12

original-awk recommends no packages.

original-awk suggests no packages.

-- no debconf information

Bug#868980: ITP: casync -- content addressable data synchronizer

2017-07-19 Thread Felipe Sateler

Package: wnpp
Severity: wishlist
Owner: Felipe Sateler 

* Package name: casync
  Version : 1
  Upstream Author : Lennart Poettering 
* URL : https://github.com/systemd/casync
* License : LGPL-2.1
  Programming Lang: C
  Description : content addressable data synchronizer

 casync is
 .
 1. A combination of the rsync algorithm and content-addressable storage
 2. An efficient way to store and retrieve multiple related versions of
large file systems or directory trees
 3. An efficient way to deliver and update OS and container images over
the Internet
 4. An efficient backup system
 .
 casync uses well-known concepts implemented in a variety of other projects
 (primarily git and rsync), and puts them together in a moderately new, nice
 way.

I plan to maintain this within the pkg-systemd umbrella. Co-maintainers
welcome!

Bug#868978: dpatch: FTBFS if original-awk provides awk

2017-07-19 Thread Sven Joachim

Package: dpatch
Version: 2.0.38

If original-awk is set as the default awk provider (because the admin
has changed the awk alternative manually, or they removed all other
providers), dpatch FTBFS:

,
| DPATCH_REVISION="2.0.38" \
|   SYSCONFDIR="/etc" ../tools/shpp.awk dpatch
| /bin/sh: 1: ../tools/shpp.awk: not found
`

That's because original-awk, unlike mawk and gawk, does not provide
/usr/bin/nawk as symlink to awk.  Attached is a one-character fix.


-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (101, 'experimental')
Architecture: i386 (x86_64)
Foreign Architectures: amd64

Kernel: Linux 4.12.2-nouveau (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE= (charmap=UTF-8), LANGUAGE= (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages dpatch depends on:
ii  bash  4.4-5
ii  dpkg-dev  1.19.0
ii  perl  5.24.1-7

Versions of packages dpatch recommends:
ii  fakeroot1.21-3.1
ii  patchutils  0.3.4-2

Versions of packages dpatch suggests:
ii  curl  7.52.1-5

-- no debconf information

diff -Nru dpatch-2.0.38/tools/shpp.awk dpatch-2.0.38local1/tools/shpp.awk
--- dpatch-2.0.38/tools/shpp.awk	2015-11-30 11:34:18.0 +0100
+++ dpatch-2.0.38local1/tools/shpp.awk	2017-07-19 23:31:58.0 +0200
@@ -1,4 +1,4 @@
-#!/usr/bin/nawk -f
+#!/usr/bin/awk -f
 # shpp.awk -- Simple preprocessor for shell scripts
 #
 #  Copyright (C) 2003  Miles Bader

Bug#868955: breaks entire system

2017-07-19 Thread Mark Hedges

On a different, also current system, I was able to install without
problems if I used dbconfig.  It did not ask me this time about what
instances I wanted to configure.  I was able to uninstall without
trouble.

If I don't use dbconfig, now I get this error:

root@markvm-walnut:~# apt-get install redmine redmine-sqlite
Reading package lists... Done
Building dependency tree
Reading state information... Done
redmine-sqlite is already the newest version (3.3.1-4).
redmine-sqlite set to manually installed.
The following packages were automatically installed and are no longer required:
  libraw15 python-pyasn1
Use 'apt autoremove' to remove them.
Suggested packages:
  bzr cvs darcs mercurial ruby-fcgi subversion
The following NEW packages will be installed:
  redmine
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/1,221 kB of archives.
After this operation, 9,315 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Preconfiguring packages ...
Selecting previously unselected package redmine.
(Reading database ... 164935 files and directories currently installed.)
Preparing to unpack .../redmine_3.3.1-4_all.deb ...
Unpacking redmine (3.3.1-4) ...
Setting up redmine (3.3.1-4) ...
dbconfig-common: writing config to
/etc/dbconfig-common/redmine/instances/default.conf

Creating config file
/etc/dbconfig-common/redmine/instances/default.conf with new version

Creating config file /etc/redmine/default/database.yml with new version
`/var/www` is not writable.
Bundler will use `/tmp/bundler/home/hedges' as your home directory temporarily.
rake aborted!
SQLite3::CantOpenException: unable to open database file
/usr/share/redmine/app/models/custom_field.rb:36:in `'
/usr/share/redmine/app/models/custom_field.rb:18:in `'
/usr/share/redmine/lib/redmine/field_format.rb:90:in `field_attributes'
/usr/share/redmine/lib/redmine/field_format.rb:93:in `'
/usr/share/redmine/lib/redmine/field_format.rb:50:in `'
/usr/share/redmine/lib/redmine/field_format.rb:21:in `'
/usr/share/redmine/lib/redmine/field_format.rb:20:in `'
/usr/share/redmine/lib/redmine.rb:40:in `'
/usr/share/redmine/config/initializers/30-redmine.rb:6:in `'
/usr/share/redmine/config/environment.rb:14:in `'
Tasks: TOP => db:migrate => environment
(See full trace by running task with --trace)
dpkg: error processing package redmine (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 redmine
E: Sub-process /usr/bin/dpkg returned an error code (1)

On Wed, Jul 19, 2017 at 2:35 PM, Mark Hedges  wrote:
> I could not reproduce the installation problem.  The only thing not
> mentioned in the initial report was that I tried to configure a second
> instance when dpkg prompted me.
>
> Mark
>
> On Wed, Jul 19, 2017 at 2:10 PM, Mark Hedges  wrote:
>> tags 868955 patch
>> thanks
>>
>> Uninstall problem seems to be snowballed from not being able to
>> install in the first place.
>>
>> /var/lib/dpkg/info/redmine.postrm line 10:
>>
>>instances=$(ls -1 /etc/redmine/*/database.yml | xargs dirname |
>> xargs -n 1 basename)
>>
>> If there are no directories, this fails.
>>
>> I attached a patch for /var/lib/dpkg/info/redmine.postrm ... not sure
>> about the installation problem yet though.
>>
>> Mark

Bug#868945: Pending fixes for bugs in the libtest-redisserver-perl package

2017-07-19 Thread pkg-perl-maintainers

tag 868945 + pending
thanks

Some bugs in the libtest-redisserver-perl package are closed in
revision 4adcf585e374ed43e8dfe1e5a59885a809d99f85 in branch 'master'
by Jonas Smedegaard

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-perl/packages/libtest-redisserver-perl.git/commit/?id=4adcf58

Commit message:

Modernize cdbs: Do copyright-check in maintainer script (not during build). 
Closes: Bug#868945. Thanks to Lucas Nussbaum.

Bug#868955: breaks entire system

2017-07-19 Thread Mark Hedges

I could not reproduce the installation problem.  The only thing not
mentioned in the initial report was that I tried to configure a second
instance when dpkg prompted me.

Mark

On Wed, Jul 19, 2017 at 2:10 PM, Mark Hedges  wrote:
> tags 868955 patch
> thanks
>
> Uninstall problem seems to be snowballed from not being able to
> install in the first place.
>
> /var/lib/dpkg/info/redmine.postrm line 10:
>
>instances=$(ls -1 /etc/redmine/*/database.yml | xargs dirname |
> xargs -n 1 basename)
>
> If there are no directories, this fails.
>
> I attached a patch for /var/lib/dpkg/info/redmine.postrm ... not sure
> about the installation problem yet though.
>
> Mark

Bug#868975: horizon: FTBFS: Test failures

2017-07-19 Thread Lucas Nussbaum

Source: horizon
Version: 3:10.0.1-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170719 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):
>   File "/<>/openstack_dashboard/usage/base.py", line 22, in 
> 
> from horizon import forms
>   File "/<>/horizon/forms/__init__.py", line 29, in 
> from horizon.forms.fields import DynamicChoiceField  # noqa
>   File "/<>/horizon/forms/fields.py", line 363, in 
> class ThemableCheckboxChoiceInput(widgets.CheckboxChoiceInput):
> AttributeError: 'module' object has no attribute 'CheckboxChoiceInput'
> 
> --
> Ran 752 tests in 1.126s
> 
> FAILED (SKIP=1, errors=751)
>  OK
> Destroying test database for alias 'default' (':memory:')...
> Tests failed.
> debian/rules:60: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   http://aws-logs.debian.net/2017/07/19/horizon_10.0.1-1_unstable.log

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 EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Bug#868971: python-feather-format: FTBFS: feather/ext.cpp:28:20: fatal error: Python.h: No such file or directory

2017-07-19 Thread Lucas Nussbaum

Source: python-feather-format
Version: 0.3.1+dfsg1-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170719 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):
> x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall 
> -Wstrict-prototypes -g -O2 
> -fdebug-prefix-map=/<>/python-feather-format-0.3.1+dfsg1=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 -fPIC -Ifeather 
> -I/usr/lib/python3/dist-packages/numpy/core/include 
> -I/<>/python-feather-format-0.3.1+dfsg1/src 
> -I/usr/include/python3.6m -c feather/ext.cpp -o 
> build/temp.linux-amd64-3.6/feather/ext.o -std=c++11 -O3
> cc1plus: warning: command line option ‘-Wstrict-prototypes’ is valid for 
> C/ObjC but not for C++
> feather/ext.cpp:28:20: fatal error: Python.h: No such file or directory
>  #include "Python.h"
> ^
> compilation terminated.
> error: command 'x86_64-linux-gnu-gcc' failed with exit status 1
> E: pybuild pybuild:283: build: plugin distutils failed with: exit code=1: 
> /usr/bin/python3.6 setup.py build 
> dh_auto_build: pybuild --build -i python{version} -p 3.6 3.5 returned exit 
> code 13
> debian/rules:8: recipe for target 'build' failed
> make: *** [build] Error 25

The full build log is available from:
   
http://aws-logs.debian.net/2017/07/19/python-feather-format_0.3.1+dfsg1-1_unstable.log

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 EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Bug#868972: alembic: FTBFS: Test failures

2017-07-19 Thread Lucas Nussbaum

Source: alembic
Version: 0.8.8-2
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170719 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):
> 
> tests/test_oracle.py::OpTest::()::test_alter_column_rename_oracle
>   /<>/alembic/util/langhelpers.py:122: UserWarning: Argument 
> 'name' is now named 'new_column_name' for method alter_column().
> oldname, newname, fn_name
> 
> tests/test_oracle.py::OpTest::()::test_alter_do_everything
>   /<>/alembic/util/langhelpers.py:122: UserWarning: Argument 
> 'name' is now named 'new_column_name' for method alter_column().
> oldname, newname, fn_name
> 
> tests/test_sqlite.py::SQLiteTest::()::test_add_column_implicit_constraint
>   /<>/alembic/util/messaging.py:69: UserWarning: Skipping 
> unsupported ALTER for creation of implicit constraint
> warnings.warn(msg)
> 
> -- Docs: http://doc.pytest.org/en/latest/warnings.html
>  2 failed, 805 passed, 160 skipped, 17 warnings in 6.18 seconds 
> 
> debian/rules:20: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   http://aws-logs.debian.net/2017/07/19/alembic_0.8.8-2_unstable.log

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 EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Bug#868970: rcs-blame: FTBFS: ./lib/argp.h:587: multiple definition of `argp_usage'

2017-07-19 Thread Lucas Nussbaum

Source: rcs-blame
Version: 1.3.1-4
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170719 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):
> gcc -Wall -W -Wno-format-y2k -g -O3 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong  -Wl,-z,relro -o blame  blame.o date.o delta.o 
> hash.o keyword.o lexer.o lines.o parser.o rcs.o util.o vector.o working.o 
> ../lib/libmisc.a 
> ../lib/libmisc.a(argp-eexst.o): In function `argp_usage':
> ./lib/argp.h:587: multiple definition of `argp_usage'
> blame.o:./src/../lib/argp.h:587: first defined here
> ../lib/libmisc.a(argp-eexst.o): In function `_option_is_short':
> ./lib/argp.h:593: multiple definition of `_option_is_short'
> blame.o:./src/../lib/argp.h:593: first defined here
> ../lib/libmisc.a(argp-eexst.o): In function `_option_is_end':
> ./lib/argp.h:605: multiple definition of `_option_is_end'
> blame.o:./src/../lib/argp.h:605: first defined here
> ../lib/libmisc.a(argp-help.o): In function `_option_is_short':
> ./lib/argp.h:593: multiple definition of `_option_is_short'
> blame.o:./src/../lib/argp.h:593: first defined here
> ../lib/libmisc.a(argp-help.o): In function `_option_is_end':
> ./lib/argp.h:605: multiple definition of `_option_is_end'
> blame.o:./src/../lib/argp.h:605: first defined here
> ../lib/libmisc.a(argp-help.o): In function `argp_state_help':
> ./lib/argp-help.c:1745: multiple definition of `argp_usage'
> blame.o:./src/../lib/argp.h:587: first defined here
> ../lib/libmisc.a(argp-parse.o): In function `argp_usage':
> ./lib/argp.h:587: multiple definition of `argp_usage'
> blame.o:./src/../lib/argp.h:587: first defined here
> ../lib/libmisc.a(argp-parse.o): In function `_option_is_short':
> ./lib/argp.h:593: multiple definition of `_option_is_short'
> blame.o:./src/../lib/argp.h:593: first defined here
> ../lib/libmisc.a(argp-parse.o): In function `_option_is_end':
> ./lib/argp.h:605: multiple definition of `_option_is_end'
> blame.o:./src/../lib/argp.h:605: first defined here
> ../lib/libmisc.a(argp-pvh.o): In function `argp_usage':
> ./lib/argp.h:587: multiple definition of `argp_usage'
> blame.o:./src/../lib/argp.h:587: first defined here
> ../lib/libmisc.a(argp-pvh.o): In function `_option_is_short':
> ./lib/argp.h:593: multiple definition of `_option_is_short'
> blame.o:./src/../lib/argp.h:593: first defined here
> ../lib/libmisc.a(argp-pvh.o): In function `_option_is_end':
> ./lib/argp.h:605: multiple definition of `_option_is_end'
> blame.o:./src/../lib/argp.h:605: first defined here
> ../lib/libmisc.a(argp-fmtstream.o): In function `argp_fmtstream_set_lmargin':
> ./lib/argp-fmtstream.h:243: multiple definition of 
> `argp_fmtstream_set_lmargin'
> ../lib/libmisc.a(argp-help.o):./lib/argp-fmtstream.h:243: first defined here
> ../lib/libmisc.a(argp-fmtstream.o): In function `argp_fmtstream_set_rmargin':
> ./lib/argp-fmtstream.h:255: multiple definition of 
> `argp_fmtstream_set_rmargin'
> ../lib/libmisc.a(argp-help.o):./lib/argp-fmtstream.h:255: first defined here
> ../lib/libmisc.a(argp-fmtstream.o): In function `argp_fmtstream_set_wmargin':
> ./lib/argp-fmtstream.h:267: multiple definition of 
> `argp_fmtstream_set_wmargin'
> ../lib/libmisc.a(argp-help.o):./lib/argp-fmtstream.h:267: first defined here
> ../lib/libmisc.a(argp-fmtstream.o): In function `argp_fmtstream_point':
> ./lib/argp-fmtstream.h:280: multiple definition of `argp_fmtstream_point'
> ../lib/libmisc.a(argp-help.o):./lib/argp-fmtstream.h:280: first defined here
> ../lib/libmisc.a(argp-fmtstream.o): In function `argp_fmtstream_write':
> ./lib/argp-fmtstream.h:207: multiple definition of `argp_fmtstream_write'
> ../lib/libmisc.a(argp-help.o):./lib/argp-fmtstream.h:207: first defined here
> ../lib/libmisc.a(argp-fmtstream.o): In function `argp_fmtstream_putc':
> ./lib/argp-fmtstream.h:233: multiple definition of `argp_fmtstream_putc'
> ../lib/libmisc.a(argp-help.o):./lib/argp-fmtstream.h:233: first defined here
> ../lib/libmisc.a(argp-fmtstream.o): In function `argp_fmtstream_puts':
> ./lib/argp-fmtstream.h:220: multiple definition of `argp_fmtstream_puts'
> ../lib/libmisc.a(argp-help.o):./lib/argp-fmtstream.h:220: first defined here
> collect2: error: ld returned 1 exit status

The full build log is available from:
   http://aws-logs.debian.net/2017/07/19/rcs-blame_1.3.1-4_unstable.log

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 EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Bug#868976: python-pbr: FTBFS: Test failures

2017-07-19 Thread Lucas Nussbaum

Source: python-pbr
Version: 1.10.0-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170719 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):
> 
> Traceback (most recent call last):
>   File "pbr/tests/test_core.py", line 81, in test_setup_py_build_sphinx
> self.assertEqual(return_code, 0)
>   File "/usr/lib/python2.7/dist-packages/testtools/testcase.py", line 350, in 
> assertEqual
> self.assertThat(observed, matcher, message)
>   File "/usr/lib/python2.7/dist-packages/testtools/testcase.py", line 435, in 
> assertThat
> raise mismatch_error
> testtools.matchers._impl.MismatchError: 1 != 0
> 
> 
> --
> Ran 165 tests in 61.048s
> 
> FAILED (failures=1, skipped=20)
> debian/rules:24: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   http://aws-logs.debian.net/2017/07/19/python-pbr_1.10.0-1_unstable.log

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 EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

1 2 3 4 >

1 - 100 of 347 matches

Mail list logo