Processed: Re: [Pkg-javascript-devel] Bug#841274: node-define-property: FTBFS: Error: Cannot find module 'wrappy'

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 node-once
Bug #841274 [node-once] node-once: missing dependency on node-wrappy makes a 
lot of packages to FTBFS
Bug #841321 [node-once] node-once: missing dependency on node-wrappy makes a 
lot of packages to FTBFS
Bug #841322 [node-once] node-once: missing dependency on node-wrappy makes a 
lot of packages to FTBFS
Bug #841323 [node-once] node-once: missing dependency on node-wrappy makes a 
lot of packages to FTBFS
Bug #841324 [node-once] node-once: missing dependency on node-wrappy makes a 
lot of packages to FTBFS
Bug #841325 [node-once] node-once: missing dependency on node-wrappy makes a 
lot of packages to FTBFS
Bug #841326 [node-once] node-once: missing dependency on node-wrappy makes a 
lot of packages to FTBFS
Bug #841327 [node-once] node-once: missing dependency on node-wrappy makes a 
lot of packages to FTBFS
Bug #841328 [node-once] node-once: missing dependency on node-wrappy makes a 
lot of packages to FTBFS
Bug #841329 [node-once] node-once: missing dependency on node-wrappy makes a 
lot of packages to FTBFS
Bug #841330 [node-once] node-once: missing dependency on node-wrappy makes a 
lot of packages to FTBFS
Bug #841331 [node-once] node-once: missing dependency on node-wrappy makes a 
lot of packages to FTBFS
Bug #841332 [node-once] node-once: missing dependency on node-wrappy makes a 
lot of packages to FTBFS
Bug #841333 [node-once] node-once: missing dependency on node-wrappy makes a 
lot of packages to FTBFS
Bug #841334 [node-once] node-once: missing dependency on node-wrappy makes a 
lot of packages to FTBFS
Bug #841335 [node-once] node-once: missing dependency on node-wrappy makes a 
lot of packages to FTBFS
Bug #841336 [node-once] node-once: missing dependency on node-wrappy makes a 
lot of packages to FTBFS
Bug #841337 [node-once] node-once: missing dependency on node-wrappy makes a 
lot of packages to FTBFS
Bug #841338 [node-once] node-once: missing dependency on node-wrappy makes a 
lot of packages to FTBFS
Ignoring request to reassign bug #841274 to the same package
Ignoring request to reassign bug #841321 to the same package
Ignoring request to reassign bug #841322 to the same package
Ignoring request to reassign bug #841323 to the same package
Ignoring request to reassign bug #841324 to the same package
Ignoring request to reassign bug #841325 to the same package
Ignoring request to reassign bug #841326 to the same package
Ignoring request to reassign bug #841327 to the same package
Ignoring request to reassign bug #841328 to the same package
Ignoring request to reassign bug #841329 to the same package
Ignoring request to reassign bug #841330 to the same package
Ignoring request to reassign bug #841331 to the same package
Ignoring request to reassign bug #841332 to the same package
Ignoring request to reassign bug #841333 to the same package
Ignoring request to reassign bug #841334 to the same package
Ignoring request to reassign bug #841335 to the same package
Ignoring request to reassign bug #841336 to the same package
Ignoring request to reassign bug #841337 to the same package
Ignoring request to reassign bug #841338 to the same package

-- 
841274: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841274
841321: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841321
841322: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841322
841323: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841323
841324: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841324
841325: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841325
841326: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841326
841327: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841327
841328: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841328
841329: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841329
841330: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841330
841331: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841331
841332: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841332
841333: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841333
841334: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841334
841335: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841335
841336: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841336
841337: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841337
841338: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841338
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#841274: [Pkg-javascript-devel] Bug#841274: node-define-property: FTBFS: Error: Cannot find module 'wrappy'

[Sruthi Chandran]

control: reassign -1 node-once

Its caused by node-once missing dependency on node-wrappy
>   make[1]: Entering directory 
> '/home/lamby/temp/cdt.20161019103506.HYMipgpTLB.db.node-define-property/node-define-property-0.2.5'
>   mocha
>   module.js:327
>   throw err;
>   ^
>   
>   Error: Cannot find module 'wrappy'
>   at Function.Module._resolveFilename (module.js:325:15)
>   at Function.Module._load (module.js:276:25)
>   at Module.require (module.js:353:17)
>   at require (internal/module.js:12:17)
>   at Object. (/usr/lib/nodejs/once.js:1:76)
>   at Module._compile (module.js:409:26)
>   at Object.Module._extensions..js (module.js:416:10)
>   at Module.load (module.js:343:32)
>   at Function.Module._load (module.js:300:12)
>   at Module.require (module.js:353:17)
>   debian/rules:13: recipe for target 'override_dh_auto_test' failed
>   make[1]: *** [override_dh_auto_test] Error 1
>   make[1]: Leaving directory 
> '/home/lamby/temp/cdt.20161019103506.HYMipgpTLB.db.node-define-property/node-define-property-0.2.5'
>   debian/rules:8: recipe for target 'build' failed
>   make: *** [build] Error 2
>
>   […]
>

Bug#841281: marked as done (gkeyring: Missing dependency on python-gnomekeyring)

[Debian Bug Tracking System]

Your message dated Thu, 20 Oct 2016 05:00:06 +
with message-id 
and subject line Bug#841290: Removed package(s) from unstable
has caused the Debian Bug report #841281,
regarding gkeyring: Missing dependency on python-gnomekeyring
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
841281: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841281
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gkeyring
Version: 0.4-1-gf4ce4c7-1
Severity: serious
Justification: Policy 7.2

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

The package appears to be missing a dependency on python-gnomekeyring.

- -- System Information:
Debian Release: stretch/sid
  APT prefers testing-debug
  APT policy: (550, 'testing-debug'), (550, 'testing'), (520, 
'unstable-debug'), (520, 'unstable'), (510, 'experimental-debug'), (510, 
'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages gkeyring depends on:
pn  python:any  

gkeyring recommends no packages.

gkeyring suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIvBAEBCAAZBQJYB0SIEhxzYW1Acm9ib3RzLm9yZy51awAKCRDSC0ICXNonufja
EACNfRWaUPARQ3P9aNAXsnvyLAf8Sq4H1Zop3XM6Ap1NyBJMz0nE6BV4Sk9PODSx
bL8nozWwvc3W7GMmnmQjDuOPxiUU0OHRxpY+u4RGNTRpBuZeu+6kCyUoGT1xGu3L
UNk6raVN2zrxjt+eChlwnCwlzyGBZV83eatTDw4qBL5UMv+Rgp58XctuBM44OI4G
ED187AlinugBIsAtyUvTkqpKLDc+93UPXz7X+zXWc2eZkmv4KrPWKLNk+a4PppGl
IZrIwH5cDSncQi+wPqh2YttrSG80HTJJ5OHNT6j4HcRy5beed33CGGPKRJrcGLO0
YPmd9S/RE9W9hPLRpbDXjqRrv6CwmVF8ovytf3tbHnZfEQ7Dv2krUU8TNySl8wwl
EDXR8n8vitEgLYQX40WPWHVxyBHwVKafqDw2YTZLs3v++XPEn5wY3sHFzPKv3w9m
yNcrKzDAfk0NA82+CUHbKyNUbTwHB7m0bynWZHDLRs/TgHGcc9xQDOD4NbJ4zpPJ
ZmtH7eOW9BogHjRBHcYZruBPebNFYgKgSacsPDHOprkTfFith16Y8INnw2MP2VZh
uM/daBsC7WHYfs1iYz5yP0RRvkxMy83NAUvi0fa5AjWtXRzgKrGwMOQbfQJkV54/
WhsS3zRCQXbHxCKhjVERghSRKgGsCvWmoFzS73yOMVssHw==
=97s1
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Version: 0.4-1-gf4ce4c7-1+rm

Dear submitter,

as the package gkeyring has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/841290

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Processed: severity of 840575 is normal

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 840575 normal
Bug #840575 [sbuild] sbuild should Depends: gnupg (>= 2.1)
Severity set to 'normal' from 'grave'
> thanks
Stopping processing here.

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

Bug#841374: cf-python: FTBFS: dh: unable to load addon sphinxdoc

[Aaron M. Ucko]

Source: cf-python
Version: 1.3.2+dfsg1-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Builds of cf-python in minimal environments geared towards building
only its architecture-dependent python-cf binary package (as on the
autobuilders) have been failing:

   fakeroot debian/rules clean
  dh clean  --with python2,sphinxdoc --buildsystem=pybuild
  dh: unable to load addon sphinxdoc: Can't locate 
Debian/Debhelper/Sequence/sphinxdoc.pm in @INC (you may need to install the 
Debian::Debhelper::Sequence::sphinxdoc module) (@INC contains: [...]) at (eval 
12) line 2.
  BEGIN failed--compilation aborted at (eval 12) line 2.
  
  debian/rules:11: recipe for target 'clean' failed
  make: *** [clean] Error 2

Please either conditionalize the usage of --with-sphinxdoc
appropriately or move python-sphinx from Build-Depends-Indep to
Build-Depends.

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#840177: marked as done (qconf: FTBFS: mkdir: cannot create directory '/usr/share/qconf/': Permission denied)

[Debian Bug Tracking System]

Your message dated Thu, 20 Oct 2016 01:29:17 +
with message-id 
and subject line Bug#840177: fixed in qconf 2.1-1
has caused the Debian Bug report #840177,
regarding qconf: FTBFS: mkdir: cannot create directory '/usr/share/qconf/': 
Permission denied
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
840177: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840177
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qconf
Version: 1.5-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

qconf fails to build from source in unstable/amd64:

  [..]

  Unpacking libqtcore4:amd64 (4:4.8.7+dfsg-9) ...
  Selecting previously unselected package libqt4-xml:amd64.
  Preparing to unpack .../03-libqt4-xml_4%3a4.8.7+dfsg-9_amd64.deb ...
  Unpacking libqt4-xml:amd64 (4:4.8.7+dfsg-9) ...
  Selecting previously unselected package libqtdbus4:amd64.
  Preparing to unpack .../04-libqtdbus4_4%3a4.8.7+dfsg-9_amd64.deb ...
  Unpacking libqtdbus4:amd64 (4:4.8.7+dfsg-9) ...
  Selecting previously unselected package qtchooser.
  Preparing to unpack .../05-qtchooser_58-gfab25f1-1_amd64.deb ...
  Unpacking qtchooser (58-gfab25f1-1) ...
  Selecting previously unselected package qdbus.
  Preparing to unpack .../06-qdbus_4%3a4.8.7+dfsg-9_amd64.deb ...
  Unpacking qdbus (4:4.8.7+dfsg-9) ...
  Selecting previously unselected package libqt4-dbus:amd64.
  Preparing to unpack .../07-libqt4-dbus_4%3a4.8.7+dfsg-9_amd64.deb ...
  Unpacking libqt4-dbus:amd64 (4:4.8.7+dfsg-9) ...
  Selecting previously unselected package libqt4-network:amd64.
  Preparing to unpack .../08-libqt4-network_4%3a4.8.7+dfsg-9_amd64.deb ...
  Unpacking libqt4-network:amd64 (4:4.8.7+dfsg-9) ...
  Selecting previously unselected package libqt4-script:amd64.
  Preparing to unpack .../09-libqt4-script_4%3a4.8.7+dfsg-9_amd64.deb ...
  Unpacking libqt4-script:amd64 (4:4.8.7+dfsg-9) ...
  Selecting previously unselected package libqt4-sql:amd64.
  Preparing to unpack .../10-libqt4-sql_4%3a4.8.7+dfsg-9_amd64.deb ...
  Unpacking libqt4-sql:amd64 (4:4.8.7+dfsg-9) ...
  Selecting previously unselected package libqt4-xmlpatterns:amd64.
  Preparing to unpack .../11-libqt4-xmlpatterns_4%3a4.8.7+dfsg-9_amd64.deb ...
  Unpacking libqt4-xmlpatterns:amd64 (4:4.8.7+dfsg-9) ...
  Selecting previously unselected package libpng16-16:amd64.
  Preparing to unpack .../12-libpng16-16_1.6.25-1_amd64.deb ...
  Unpacking libpng16-16:amd64 (1.6.25-1) ...
  Selecting previously unselected package libfreetype6:amd64.
  Preparing to unpack .../13-libfreetype6_2.6.3-3+b1_amd64.deb ...
  Unpacking libfreetype6:amd64 (2.6.3-3+b1) ...
  Selecting previously unselected package ucf.
  Preparing to unpack .../14-ucf_3.0036_all.deb ...
  Moving old data out of the way
  Unpacking ucf (3.0036) ...
  Selecting previously unselected package fonts-dejavu-core.
  Preparing to unpack .../15-fonts-dejavu-core_2.37-1_all.deb ...
  Unpacking fonts-dejavu-core (2.37-1) ...
  Selecting previously unselected package fontconfig-config.
  Preparing to unpack .../16-fontconfig-config_2.11.0-6.7_all.deb ...
  Unpacking fontconfig-config (2.11.0-6.7) ...
  Selecting previously unselected package libfontconfig1:amd64.
  Preparing to unpack .../17-libfontconfig1_2.11.0-6.7_amd64.deb ...
  Unpacking libfontconfig1:amd64 (2.11.0-6.7) ...
  Selecting previously unselected package fontconfig.
  Preparing to unpack .../18-fontconfig_2.11.0-6.7_amd64.deb ...
  Unpacking fontconfig (2.11.0-6.7) ...
  Selecting previously unselected package libxau6:amd64.
  Preparing to unpack .../19-libxau6_1%3a1.0.8-1_amd64.deb ...
  Unpacking libxau6:amd64 (1:1.0.8-1) ...
  Selecting previously unselected package x11-common.
  Preparing to unpack .../20-x11-common_1%3a7.7+16_all.deb ...
  Unpacking x11-common (1:7.7+16) ...
  Selecting previously unselected package libice6:amd64.
  Preparing to unpack .../21-libice6_2%3a1.0.9-1+b1_amd64.deb ...
  Unpacking libice6:amd64 (2:1.0.9-1+b1) ...
  Selecting previously unselected package libsm6:amd64.
  Preparing to unpack .../22-libsm6_2%3a1.2.2-1+b1_amd64.deb ...
  Unpacking libsm6:amd64 (2:1.2.2-1+b1) ...
  Selecting previously unselected package libxdmcp6:amd64.
  Preparing to unpack .../23-libxdmcp6_1%3a1.1.2-1.1_amd64.deb ...
  Unpacking libxdmcp6:amd64 (1:1.1.2-1.1) ...
  Selecting previously unselected package libxcb1:amd64.
  Preparing to unpack .../24-libxcb1_1.12-1_amd64.deb ...
  

Bug#841341: bd "Bad substitution" if /bin/sh is not bash

[Paulo Henrique de Lima Santana]

Hi Gerardo,

Thanks! I'm fixing it.

Best regards,

-- 
Paulo Henrique de Lima Santana (phls)
Membro da Comunidade Curitiba Livre
Fone: +55 (41) 9198-1897
Site: http://www.phls.com.br
GNU/Linux user: 228719  GPG ID: 0443C450

Apoie a campanha pela igualdade de gênero #HeForShe (#ElesPorElas)  
http://www.heforshe.org/pt

Bug#841373: mv: cannot stat 'unpackchrome/opt/google/chrome/PepperFlash/libpepflashplayer.so': No such file or directory

[Trent W. Buck]

Package: pepperflashplugin-nonfree
Version: 1.8.1+deb8u1
Severity: critical

Install is currently failing.
Maybe the paths within the upstream deb have changed?

Here's what the postinst said:

Setting up pepperflashplugin-nonfree (1.8.1+deb8u1) ...
converted 
'http://dl.google.com/linux/chrome/deb/pool/main/g/google-chrome-stable/google-chrome-stable_54.0.2840.59-1_amd64.deb'
 (ANSI_X3.4-1968) -> 
'http://dl.google.com/linux/chrome/deb/pool/main/g/google-chrome-stable/google-chrome-stable_54.0.2840.59-1_amd64.deb'
 (UTF-8)
--2016-10-20 11:49:21--  
http://dl.google.com/linux/chrome/deb/pool/main/g/google-chrome-stable/google-chrome-stable_54.0.2840.59-1_amd64.deb
Resolving proxy (proxy)... 203.7.155.12
Connecting to proxy (proxy)|203.7.155.12|:8080... connected.
Proxy request sent, awaiting response... 200 OK
Length: 45527232 (43M) [application/x-debian-package]
Saving to: 
'/tmp/pepperflashplugin-nonfree.LdNEpJHj9m/google-chrome-stable_54.0.2840.59-1_amd64.deb'

 0K .. .. .. .. ..  0%  156K 
4m44s
[...]
 44400K .. .. .. .. .. 99%  444K 0s
 44450K ..100% 38.8M=60s

2016-10-20 11:50:22 (739 KB/s) - 
'/tmp/pepperflashplugin-nonfree.LdNEpJHj9m/google-chrome-stable_54.0.2840.59-1_amd64.deb'
 saved [45527232/45527232]

mv: cannot stat 
'unpackchrome/opt/google/chrome/PepperFlash/libpepflashplayer.so': No such file 
or directory
Setting up plymouth (0.9.0-9) ...


Because errors in the postinst's call to update-pepperflashplugin-nonfree 
aren't fatal,
my build scripts explicitly rerun it.  Here's the same problem:

# Work around https://bugs.debian.org/823005; also #31001
[[ -e $t/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so ]] ||
(   wget -O $t/usr/lib/pepperflashplugin-nonfree/pubkey-google.txt 
https://dl.google.com/linux/linux_signing_key.pub
chroot $t update-pepperflashplugin-nonfree -ifq )

+ [[ -e live/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so ]]
+ wget -O live/usr/lib/pepperflashplugin-nonfree/pubkey-google.txt 
https://dl.google.com/linux/linux_signing_key.pub
converted 'https://dl.google.com/linux/linux_signing_key.pub' 
(ANSI_X3.4-1968) -> 'https://dl.google.com/linux/linux_signing_key.pub' (UTF-8)
--2016-10-20 11:51:10--  https://dl.google.com/linux/linux_signing_key.pub
Resolving dl.google.com (dl.google.com)... 172.217.25.46, 
2404:6800:4006:807::200e
Connecting to dl.google.com (dl.google.com)|172.217.25.46|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 5840 (5.7K) [application/octet-stream]
Saving to: 'live/usr/lib/pepperflashplugin-nonfree/pubkey-google.txt'

 0K . 100% 
1.02M=0.005s

2016-10-20 11:51:12 (1.02 MB/s) - 
'live/usr/lib/pepperflashplugin-nonfree/pubkey-google.txt' saved [5840/5840]

+ chroot live update-pepperflashplugin-nonfree -ifq
mv: cannot stat 
'unpackchrome/opt/google/chrome/PepperFlash/libpepflashplayer.so': No such file 
or directory

When I look inside the deb myself, I don't see libpepflashplayer.so:

$ dpkg -c google-chrome-stable_54.0.2840.59-1_amd64.deb | grep -F .so
-rw-r--r-- root/root   7964784 2016-10-12 15:41 
./opt/google/chrome/libwidevinecdm.so
-rw-r--r-- root/root 71984 2016-10-12 15:41 
./opt/google/chrome/libwidevinecdmadapter.so

Bug#831143: marked as done (hmat-oss: FTBFS with GCC 6: compression.cpp:717:25: error: there are no arguments to 'isnan' that depend on a template parameter, so a declaration of 'isnan' must be availa

[Debian Bug Tracking System]

Your message dated Thu, 20 Oct 2016 00:24:44 +
with message-id 
and subject line Bug#831143: fixed in hmat-oss 1.2.0-1
has caused the Debian Bug report #831143,
regarding hmat-oss: FTBFS with GCC 6: compression.cpp:717:25: error: there are 
no arguments to 'isnan' that depend on a template parameter, so a declaration 
of 'isnan' must be available [-fpermissive]
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
831143: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831143
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: hmat-oss
Version: 1.0.4-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160713 qa-ftbfs
Justification: FTBFS with GCC 6 on amd64

Hi,

During a rebuild of all packages in sid using the gcc-defaults package
available in experimental to make GCC default to version 6, your package failed
to build on amd64. For more information about GCC 6 and Stretch, see:
- https://wiki.debian.org/GCC6
- https://lists.debian.org/debian-devel-announce/2016/06/msg7.html

Relevant part (hopefully):
> /usr/bin/c++   -D_GNU_SOURCE -Dhmat_oss_EXPORTS -I/«PKGBUILDDIR»/include 
> -I/«PKGBUILDDIR»/obj-x86_64-linux-gnu -I/«PKGBUILDDIR»/src  -fopenmp  -g -O2 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 -ffast-math -funsafe-math-optimizations -fopenmp -fPIC   
> -UNDEBUG -o CMakeFiles/hmat-oss.dir/src/compression.cpp.o -c 
> /«PKGBUILDDIR»/src/compression.cpp
> /«PKGBUILDDIR»/src/compression.cpp: In function 'RkMatrix Types::dp>* compress(CompressionMethod, const AssemblyFunction&, const 
> ClusterData*, const ClusterData*)':
> /«PKGBUILDDIR»/src/compression.cpp:717:25: error: there are no arguments to 
> 'isnan' that depend on a template parameter, so a declaration of 'isnan' must 
> be available [-fpermissive]
>  if (isnan(approxNorm)) {
>  ^
> /«PKGBUILDDIR»/src/compression.cpp:717:25: note: (if you use '-fpermissive', 
> G++ will accept your code, but allowing the use of an undeclared name is 
> deprecated)
> /«PKGBUILDDIR»/src/compression.cpp: In instantiation of 'RkMatrix Types::dp>* compress(CompressionMethod, const AssemblyFunction&, const 
> ClusterData*, const ClusterData*) [with T = float; typename Types::dp = 
> double]':
> /«PKGBUILDDIR»/src/compression.cpp:786:156:   required from here
> /«PKGBUILDDIR»/src/compression.cpp:717:14: error: 'isnan' was not declared in 
> this scope
>  if (isnan(approxNorm)) {
>  ~^~~~
> /«PKGBUILDDIR»/src/compression.cpp:717:14: note: suggested alternative:
> In file included from /«PKGBUILDDIR»/src/compression.cpp:26:0:
> /usr/include/c++/6/cmath:655:5: note:   'std::isnan'
>  isnan(_Tp __x)
>  ^
> /«PKGBUILDDIR»/src/compression.cpp: In instantiation of 'RkMatrix Types::dp>* compress(CompressionMethod, const AssemblyFunction&, const 
> ClusterData*, const ClusterData*) [with T = double; typename Types::dp = 
> double]':
> /«PKGBUILDDIR»/src/compression.cpp:787:156:   required from here
> /«PKGBUILDDIR»/src/compression.cpp:717:14: error: 'isnan' was not declared in 
> this scope
>  if (isnan(approxNorm)) {
>  ~^~~~
> /«PKGBUILDDIR»/src/compression.cpp:717:14: note: suggested alternative:
> In file included from /«PKGBUILDDIR»/src/compression.cpp:26:0:
> /usr/include/c++/6/cmath:655:5: note:   'std::isnan'
>  isnan(_Tp __x)
>  ^
> /«PKGBUILDDIR»/src/compression.cpp: In instantiation of 'RkMatrix Types::dp>* compress(CompressionMethod, const AssemblyFunction&, const 
> ClusterData*, const ClusterData*) [with T = std::complex; typename 
> Types::dp = std::complex]':
> /«PKGBUILDDIR»/src/compression.cpp:788:156:   required from here
> /«PKGBUILDDIR»/src/compression.cpp:717:14: error: 'isnan' was not declared in 
> this scope
>  if (isnan(approxNorm)) {
>  ~^~~~
> /«PKGBUILDDIR»/src/compression.cpp:717:14: note: suggested alternative:
> In file included from /«PKGBUILDDIR»/src/compression.cpp:26:0:
> /usr/include/c++/6/cmath:655:5: note:   'std::isnan'
>  isnan(_Tp __x)
>  ^
> /«PKGBUILDDIR»/src/compression.cpp: In instantiation of 'RkMatrix Types::dp>* compress(CompressionMethod, const AssemblyFunction&, const 
> ClusterData*, const ClusterData*) [with T = std::complex; typename 
> Types::dp = std::complex]':
> /«PKGBUILDDIR»/src/compression.cpp:789:156:   required from here
> /«PKGBUILDDIR»/src/compression.cpp:717:14: error: 'isnan' was not declared in 
> this scope
>  if 

Bug#789988: marked as done (FTBFS: The import org.eclipse.egit.ui.internal.FilteredCheckboxTree cannot be resolved)

[Debian Bug Tracking System]

Your message dated Thu, 20 Oct 2016 00:21:55 +
with message-id 
and subject line Bug#789988: fixed in eclipse-mylyn-tasks-github 3.3.0-2
has caused the Debian Bug report #789988,
regarding FTBFS: The import org.eclipse.egit.ui.internal.FilteredCheckboxTree 
cannot be resolved
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
789988: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789988
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: eclipse-mylyn-tasks-github
Version: 3.3.0-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Dear Maintainer,

The package fails to build, probably because egit has changed:

@dot:
[mkdir] Created dir: 
/tmp/buildd/eclipse-mylyn-tasks-github-3.3.0/debian/.eclipse-build/org.eclipse.mylyn.github.ui/@dot
[javac] Compiling 50 source files to 
/tmp/buildd/eclipse-mylyn-tasks-github-3.3.0/debian/.eclipse-build/org.eclipse.mylyn.github.ui/@dot



[javac] 29. ERROR in 
/tmp/buildd/eclipse-mylyn-tasks-github-3.3.0/debian/.eclipse-build/org.eclipse.mylyn.github.ui/src/org/eclipse/mylyn/internal/github/ui/RepositorySelectionWizardPage.java
 (at line 27)
[javac] import org.eclipse.egit.ui.internal.FilteredCheckboxTree;
[javac]^
[javac] The import org.eclipse.egit.ui.internal.FilteredCheckboxTree cannot 
be resolved
[javac] --
[javac] 30. ERROR in 
/tmp/buildd/eclipse-mylyn-tasks-github-3.3.0/debian/.eclipse-build/org.eclipse.mylyn.github.ui/src/org/eclipse/mylyn/internal/github/ui/RepositorySelectionWizardPage.java
 (at line 184)
[javac] private FilteredCheckboxTree tree;
[javac] 
[javac] FilteredCheckboxTree cannot be resolved to a type

etc.

Full build log:
https://reproducible.debian.net/rb-pkg/testing/amd64/eclipse-mylyn-tasks-github.html

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.19.0-21-generic (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: eclipse-mylyn-tasks-github
Source-Version: 3.3.0-2

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

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 789...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Emmanuel Bourg  (supplier of updated 
eclipse-mylyn-tasks-github package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 20 Oct 2016 01:12:28 +0200
Source: eclipse-mylyn-tasks-github
Binary: eclipse-mylyn-tasks-github
Architecture: source all
Version: 3.3.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Emmanuel Bourg 
Description:
 eclipse-mylyn-tasks-github - Mylyn GitHub Connector
Closes: 789988
Changes:
 eclipse-mylyn-tasks-github (3.3.0-2) unstable; urgency=medium
 .
   * Team upload.
   * Fixed the build failure caused by eclipse-egit 3.7 (Closes: #789988)
   * Compile with javac instead of the Eclipse compiler
   * Standards-Version updated to 3.9.8
   * Use secure Vcs-* URLs
   * Fixed the watch file
Checksums-Sha1:
 305c7cce25c3bfa9ee4f3a4117892501412e3a6b 2205 
eclipse-mylyn-tasks-github_3.3.0-2.dsc
 6490eae4704dc39d03f9ed2931c0ff1f83734916 6468 
eclipse-mylyn-tasks-github_3.3.0-2.debian.tar.xz
 690520409ee270f116958a1c28e19e8f3d7f6f88 663810 
eclipse-mylyn-tasks-github_3.3.0-2_all.deb
Checksums-Sha256:
 e464a8dd979f8b69685c323131cb5e1e2da9ac995339af1e812ffdbc7d720d43 2205 
eclipse-mylyn-tasks-github_3.3.0-2.dsc
 668fa8ebfa477f18f4034551e0418bf5dd3f966575ff624505aaaf05295752ab 6468 
eclipse-mylyn-tasks-github_3.3.0-2.debian.tar.xz
 15da15e5f1a94a7aa8aae4a2a5915d0a20272ed05f95d843d6b8ad618712b58f 663810 

Bug#841363: marked as done (maven-enforcer: makes several packages to FTBFS with "Plugin org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies could not be resolved")

[Debian Bug Tracking System]

Your message dated Wed, 19 Oct 2016 23:09:40 +
with message-id 
and subject line Bug#841197: fixed in maven-enforcer 1.4.1-2
has caused the Debian Bug report #841197,
regarding maven-enforcer: makes several packages to FTBFS with "Plugin 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies 
could not be resolved"
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
841197: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841197
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:junit4
Version: 4.12-4
Severity: serious

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --parallel --buildsystem=maven
   dh_testdir -i -O--parallel -O--buildsystem=maven
   dh_update_autotools_config -i -O--parallel -O--buildsystem=maven
   dh_auto_configure -i -O--parallel -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 -pjunit4 --debian-build --keep-pom-version 
--maven-repo=/<>/debian/maven-repo
   dh_auto_build -i -O--parallel -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
[INFO] Scanning for projects...
[WARNING] The POM for org.apache.maven.plugins:maven-enforcer-plugin:jar:1.4.1 
is invalid, transitive dependencies (if any) will not be available, enable 
debug logging for more details
[WARNING] Failed to retrieve plugin descriptor for 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1: Plugin 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies 
could not be resolved: Failed to read artifact descriptor for 
org.apache.maven.plugins:maven-enforcer-plugin:jar:1.4.1
[WARNING] The POM for org.apache.maven.plugins:maven-enforcer-plugin:jar:1.4.1 
is invalid, transitive dependencies (if any) will not be available, enable 
debug logging for more details
[WARNING] Failed to retrieve plugin descriptor for 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1: Plugin 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies 
could not be resolved: Failed to read artifact descriptor for 
org.apache.maven.plugins:maven-enforcer-plugin:jar:1.4.1
[INFO] 
[INFO] 
[INFO] Building JUnit 4.12
[INFO] 
[WARNING] The POM for org.apache.maven.plugins:maven-enforcer-plugin:jar:1.4.1 
is invalid, transitive dependencies (if any) will not be available, enable 
debug logging for more details
[WARNING] Failed to retrieve plugin descriptor for 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1: Plugin 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies 
could not be resolved: Failed to read artifact descriptor for 
org.apache.maven.plugins:maven-enforcer-plugin:jar:1.4.1
[WARNING] The POM for org.apache.maven.plugins:maven-enforcer-plugin:jar:1.4.1 
is invalid, transitive dependencies (if any) will not be available, enable 
debug logging for more details
[INFO] 
[INFO] 
[INFO] Skipping JUnit
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] BUILD FAILURE
[INFO] 

Bug#841296: marked as done (maven-enforcer: makes several packages to FTBFS with "Plugin org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies could not be resolved")

[Debian Bug Tracking System]

Your message dated Wed, 19 Oct 2016 23:09:40 +
with message-id 
and subject line Bug#841197: fixed in maven-enforcer 1.4.1-2
has caused the Debian Bug report #841197,
regarding maven-enforcer: makes several packages to FTBFS with "Plugin 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies 
could not be resolved"
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
841197: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841197
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:openjpa
Version: 2.4.0-3
Severity: serious

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --parallel --buildsystem=maven
   dh_testdir -i -O--parallel -O--buildsystem=maven
   dh_update_autotools_config -i -O--parallel -O--buildsystem=maven
   dh_auto_configure -i -O--parallel -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 -plibopenjpa-java --debian-build --keep-pom-version 
--maven-repo=/<>/debian/maven-repo
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build -- install
/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 install -DskipTests 
-Dnotimestamp=true -Dlocale=en_US

[... snipped ...]

[INFO] Replacing /<>/openjpa/target/openjpa-2.4.0.jar with 
/<>/openjpa/target/openjpa-2.4.0-shaded.jar
[INFO] Dependency-reduced POM written at: 
/<>/openjpa/dependency-reduced-pom.xml
[INFO] 
[INFO] --- maven-install-plugin:2.5.2:install (default-install) @ openjpa ---
[INFO] Installing /<>/openjpa/target/openjpa-2.4.0.jar to 
/<>/debian/maven-repo/org/apache/openjpa/openjpa/2.4.0/openjpa-2.4.0.jar
[INFO] Installing /<>/openjpa/dependency-reduced-pom.xml to 
/<>/debian/maven-repo/org/apache/openjpa/openjpa/2.4.0/openjpa-2.4.0.pom
[INFO] 
[INFO] --- maven-bundle-plugin:2.5.4:install (default-install) @ openjpa ---
[INFO] Writing OBR metadata
[INFO] Installing org/apache/openjpa/openjpa/2.4.0/openjpa-2.4.0.jar
[INFO] Writing OBR metadata
[INFO] 
[INFO] 
[INFO] Building OpenJPA Parent POM 2.4.0
[INFO] 
[WARNING] The POM for org.apache.maven.plugins:maven-enforcer-plugin:jar:1.4.1 
is invalid, transitive dependencies (if any) will not be available, enable 
debug logging for more details
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] OpenJPA Utilities Library .. SUCCESS [  8.801 s]
[INFO] OpenJPA Kernel . SUCCESS [ 12.904 s]
[INFO] OpenJPA JDBC ... SUCCESS [  7.667 s]
[INFO] OpenJPA Persistence  SUCCESS [  4.218 s]
[INFO] OpenJPA Persistence JDBC ... SUCCESS [  1.028 s]
[INFO] OpenJPA XML Store .. SUCCESS [  0.481 s]
[INFO] OpenJPA Slice .. SUCCESS [  0.709 s]
[INFO] OpenJPA JEST ... SUCCESS [  0.609 s]
[INFO] OpenJPA Aggregate Jar .. SUCCESS [  6.807 s]
[INFO] OpenJPA Parent POM . FAILURE [  0.007 s]
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 44.824 s
[INFO] Finished at: 2016-10-19T13:58:12+02:00
[INFO] Final 

Bug#841197: marked as done (maven-enforcer: makes several packages to FTBFS with "Plugin org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies could not be resolved")

[Debian Bug Tracking System]

Your message dated Wed, 19 Oct 2016 23:09:40 +
with message-id 
and subject line Bug#841197: fixed in maven-enforcer 1.4.1-2
has caused the Debian Bug report #841197,
regarding maven-enforcer: makes several packages to FTBFS with "Plugin 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies 
could not be resolved"
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
841197: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841197
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libhibernate3-java
Version: 3.6.10.Final-5
Severity: serious

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --buildsystem=maven
   dh_testdir -i -O--buildsystem=maven
   dh_update_autotools_config -i -O--buildsystem=maven
   dh_auto_configure -i -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 -plibhibernate3-java --debian-build --keep-pom-version 
--maven-repo=/<>/debian/maven-repo
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
rm -Rf debian/maven-repo/org/hibernate/hibernate
rm -Rf debian/maven-repo/org/hibernate/hibernate-parent

[... snipped ...]

[WARNING] 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.
[WARNING] The POM for org.apache.maven.plugins:maven-site-plugin:jar:3.3 is 
missing, no dependency information available
[WARNING] 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.
[INFO] 
[INFO] 
[INFO] Building Hibernate Core Parent POM 3.6.10.Final
[INFO] 
[WARNING] The POM for org.apache.maven.plugins:maven-enforcer-plugin:jar:1.4.1 
is invalid, transitive dependencies (if any) will not be available, enable 
debug logging for more details
[INFO] 
[INFO] 
[INFO] Skipping Hibernate Core Aggregator
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] Hibernate Core Parent POM .. FAILURE [  0.010 s]
[INFO] Hibernate Core . SKIPPED
[INFO] Hibernate Testing .. SKIPPED
[INFO] Hibernate Testsuite  SKIPPED
[INFO] Hibernate Ehcache Integration .. SKIPPED
[INFO] Hibernate OSCache Integration .. SKIPPED
[INFO] Hibernate SwarmCache Integration ... SKIPPED
[INFO] Hibernate C3P0 ConnectionProvider .. SKIPPED
[INFO] Hibernate Proxool ConnectionProvider ... SKIPPED
[INFO] Hibernate JDBC3-JdbcSupport Testing  SKIPPED
[INFO] Hibernate Entity Manager ... SKIPPED
[INFO] Hibernate JDBC4-JdbcSupport Testing  SKIPPED
[INFO] Hibernate Core Aggregator .. SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 

Bug#841362: marked as done (maven-enforcer: makes several packages to FTBFS with "Plugin org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies could not be resolved")

[Debian Bug Tracking System]

Your message dated Wed, 19 Oct 2016 23:09:40 +
with message-id 
and subject line Bug#841197: fixed in maven-enforcer 1.4.1-2
has caused the Debian Bug report #841197,
regarding maven-enforcer: makes several packages to FTBFS with "Plugin 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies 
could not be resolved"
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
841197: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841197
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:activemq-protobuf
Version: 1.1-4
Severity: serious

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --parallel --buildsystem=maven
   dh_testdir -i -O--parallel -O--buildsystem=maven
   dh_update_autotools_config -i -O--parallel -O--buildsystem=maven
   dh_auto_configure -i -O--parallel -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 -plibactivemq-protobuf-java --debian-build 
--keep-pom-version --maven-repo=/<>/debian/maven-repo
   dh_auto_build -i -O--parallel -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
[INFO] Scanning for projects...
[WARNING] 

[... snipped ...]

[WARNING] The POM for org.apache.maven.plugins:maven-release-plugin:jar:2.3.2 
is missing, no dependency information available
[WARNING] Failed to retrieve plugin descriptor for 
org.apache.maven.plugins:maven-release-plugin:2.3.2: Plugin 
org.apache.maven.plugins:maven-release-plugin:2.3.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-release-plugin:jar:2.3.2 has not been downloaded 
from it before.
[INFO] 
[INFO] 
[INFO] Building ActiveMQ Protocol Buffers POM 1.1
[INFO] 
[WARNING] The POM for org.apache.maven.plugins:maven-enforcer-plugin:jar:1.4.1 
is invalid, transitive dependencies (if any) will not be available, enable 
debug logging for more details
[WARNING] Failed to retrieve plugin descriptor for 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1: Plugin 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies 
could not be resolved: Failed to read artifact descriptor for 
org.apache.maven.plugins:maven-enforcer-plugin:jar:1.4.1
[WARNING] The POM for org.apache.maven.plugins:maven-deploy-plugin:jar:2.7 is 
missing, no dependency information available
[WARNING] 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.
[WARNING] The POM for org.apache.maven.plugins:maven-site-plugin:jar:3.3 is 
missing, no dependency information available
[WARNING] 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 

Processed: tagging 809566

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 809566 + help
Bug #809566 [src:eclipse-mylyn] eclipse-mylyn: FTBFS: Unsatisfied import 
package javax.mail_0.0.0.
Added tag(s) help.
> thanks
Stopping processing here.

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

Processed: tagging 808485

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 808485 + help
Bug #808485 [src:eclipse-pydev] eclipse-pydev: FTBFS: Missing required plug-in 
org.python_0.0.0.
Added tag(s) help.
> thanks
Stopping processing here.

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

Bug#831857: marked as done (libupnp: CVE-2016-6255: write files via POST)

[Debian Bug Tracking System]

Your message dated Wed, 19 Oct 2016 22:47:26 +
with message-id 
and subject line Bug#831857: fixed in libupnp 1:1.6.19+git20160116-1.1
has caused the Debian Bug report #831857,
regarding libupnp: CVE-2016-6255: write files via POST
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
831857: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831857
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libupnp
Version: 1:1.6.17-1
Severity: grave
Tags: security upstream
Justification: user security hole

Hi

See http://www.openwall.com/lists/oss-security/2016/07/18/13 and
https://twitter.com/mjg59/status/755062278513319936 .

Proposed fix:
https://github.com/mjg59/pupnp-code/commit/be0a01bdb83395d9f3a5ea09c1308a4f1a972cbd

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: libupnp
Source-Version: 1:1.6.19+git20160116-1.1

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

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 831...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
James Cowgill  (supplier of updated libupnp package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 19 Oct 2016 21:03:51 +0100
Source: libupnp
Binary: libupnp6 libupnp6-dev libupnp-dev libupnp6-dbg libupnp6-doc
Architecture: source
Version: 1:1.6.19+git20160116-1.1
Distribution: unstable
Urgency: high
Maintainer: Nick Leverton 
Changed-By: James Cowgill 
Description:
 libupnp-dev - Portable SDK for UPnP Devices (development files)
 libupnp6   - Portable SDK for UPnP Devices, version 1.6 (shared libraries)
 libupnp6-dbg - debugging symbols for libupnp6
 libupnp6-dev - Portable SDK for UPnP Devices, version 1.6 (development files)
 libupnp6-doc - Documentation for the Portable SDK for UPnP Devices, version 1.6
Closes: 831857
Changes:
 libupnp (1:1.6.19+git20160116-1.1) unstable; urgency=high
 .
   * Non-maintainer upload.
   * Don't allow unhandled POSTs to write to the filesystem by
 default (Closes: #831857) (CVE-2016-6255)
 Thanks to Matthew Garrett for the patch.
Checksums-Sha1:
 8f31c49dbce41876d8b24c2da80251ea01336680 2063 
libupnp_1.6.19+git20160116-1.1.dsc
 c1c0a4ec12985d7c05622de385089eb1b1499118 27556 
libupnp_1.6.19+git20160116-1.1.debian.tar.xz
Checksums-Sha256:
 f5f1ebe446db23082da1cfd02f0c7402c31e61e94758d332154282901f65fec6 2063 
libupnp_1.6.19+git20160116-1.1.dsc
 b046b9278c828dc2d6507dd470b8bf9ef81710b711748799d1812489df5672a7 27556 
libupnp_1.6.19+git20160116-1.1.debian.tar.xz
Files:
 a0befa3ea459b2448280b273709c81d8 2063 net optional 
libupnp_1.6.19+git20160116-1.1.dsc
 5ef9b6f217cd269cf186b68527ba4244 27556 net optional 
libupnp_1.6.19+git20160116-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJYB9WHAAoJEMfxZ23qLQHv2lIQAKIiJkq6VIsfVMXs7KA+0cu3
oql7QnodK/loAHXx+4DTi6ccqxCAXe05eILRDESwxBHkE+xUZMZQ2zAqmIt9cJIs
FPYRDJ6n7nAxejj2cgTa4ZxNcJRqpaInF/1R3lwD5U4Bn5mBRrCrTtDAZhjZKJhs
Mo33hCHPqVRRY2wTul1p7Ypp9oYtw/Y8ri3po43WSVVDTVp8TDoVJZ2+3lCL80tr
5eDcmCXBqnhp8BkCwOg368UBUi/fqfFj4CNnQ95P0V2RBD6jPZC35Ge5L1Yfi5dh
oXZBWYDqwRaLwCO1pH1PFpLKWrNAPNWW/N29yXhYHp69b2WRKB+YoBKx5qCv2M6C
OG0H6lEyvPyR3ot3uexlf2l/I5zzusQ50UCcQYGEKNlJPNYPgIaeU+bSP+KjywEQ
e/kUgPOHj2kLd1eqyerBGBIjOpt6GJyKoTCgDlOF15VXj2LnS2QPRgvDVAjvSK1P
OhzqkmIwa3hva1P92wJeTsQrCtBOUIocrSzAWXkZYKNX52JHMfziHbBHxb1FZ+4N
KwM52FJFujdZJ2yYe4RHjldtmH7jJudcnzOQpiUZCukBx35hxVnsm7oUtFWhdCXa
Gp81QE/Z/Bn5T9WyCDbVw/DUUdCf29WWiW4MO/bcJ/r1XuV2X2FE1PFdeGjVBGnd
j20rlFVcmlff870I1PJo
=b/rE
-END PGP SIGNATURE End Message ---

Processed: tagging 831097

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 831097 + pending
Bug #831097 [src:eclipse-pydev] eclipse-pydev: FTBFS with GCC 6: 
plugins/org.python.pydev/pysrc/pydevd_attach_to_process/linux/attach_linux.c:237:25:
 error: expected initializer before 'pydevdTracingMod'
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: affects and retitle

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> affects 841197 
> src:activemq,src:activemq-activeio,src:activemq-protobuf,src:animal-sniffer,src:annotation-indexer,src:async-http-client,src:checkstyle,src:jacoco,src:jboss-logmanager,src:jboss-modules,src:junit4,src:libhibernate3-java,src:maven-jar-plugin,src:openjpa,src:wagon
Bug #841197 [maven-enforcer] libhibernate3-java: FTBFS (Plugin 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies 
could not be resolved)
Bug #841296 [maven-enforcer] openjpa: FTBFS (Plugin 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies 
could not be resolved)
Bug #841362 [maven-enforcer] activemq-protobuf: FTBFS (Plugin 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies 
could not be resolved)
Bug #841363 [maven-enforcer] junit4: FTBFS (Plugin 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies 
could not be resolved)
Added indication that 841197 affects src:activemq, src:activemq-activeio, 
src:activemq-protobuf, src:animal-sniffer, src:annotation-indexer, 
src:async-http-client, src:checkstyle, src:jacoco, src:jboss-logmanager, 
src:jboss-modules, src:junit4, src:libhibernate3-java, src:maven-jar-plugin, 
src:openjpa, and src:wagon
Added indication that 841296 affects src:activemq, src:activemq-activeio, 
src:activemq-protobuf, src:animal-sniffer, src:annotation-indexer, 
src:async-http-client, src:checkstyle, src:jacoco, src:jboss-logmanager, 
src:jboss-modules, src:junit4, src:libhibernate3-java, src:maven-jar-plugin, 
src:openjpa, and src:wagon
Added indication that 841362 affects src:activemq, src:activemq-activeio, 
src:activemq-protobuf, src:animal-sniffer, src:annotation-indexer, 
src:async-http-client, src:checkstyle, src:jacoco, src:jboss-logmanager, 
src:jboss-modules, src:junit4, src:libhibernate3-java, src:maven-jar-plugin, 
src:openjpa, and src:wagon
Added indication that 841363 affects src:activemq, src:activemq-activeio, 
src:activemq-protobuf, src:animal-sniffer, src:annotation-indexer, 
src:async-http-client, src:checkstyle, src:jacoco, src:jboss-logmanager, 
src:jboss-modules, src:junit4, src:libhibernate3-java, src:maven-jar-plugin, 
src:openjpa, and src:wagon
> retitle 841197 maven-enforcer: makes several packages to FTBFS with "Plugin 
> org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its 
> dependencies could not be resolved"
Bug #841197 [maven-enforcer] libhibernate3-java: FTBFS (Plugin 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies 
could not be resolved)
Bug #841296 [maven-enforcer] openjpa: FTBFS (Plugin 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies 
could not be resolved)
Bug #841362 [maven-enforcer] activemq-protobuf: FTBFS (Plugin 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies 
could not be resolved)
Bug #841363 [maven-enforcer] junit4: FTBFS (Plugin 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies 
could not be resolved)
Changed Bug title to 'maven-enforcer: makes several packages to FTBFS with 
"Plugin org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its 
dependencies could not be resolved"' from 'libhibernate3-java: FTBFS (Plugin 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies 
could not be resolved)'.
Changed Bug title to 'maven-enforcer: makes several packages to FTBFS with 
"Plugin org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its 
dependencies could not be resolved"' from 'openjpa: FTBFS (Plugin 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies 
could not be resolved)'.
Changed Bug title to 'maven-enforcer: makes several packages to FTBFS with 
"Plugin org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its 
dependencies could not be resolved"' from 'activemq-protobuf: FTBFS (Plugin 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies 
could not be resolved)'.
Changed Bug title to 'maven-enforcer: makes several packages to FTBFS with 
"Plugin org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its 
dependencies could not be resolved"' from 'junit4: FTBFS (Plugin 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies 
could not be resolved)'.
> thanks
Stopping processing here.

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

Bug#813419: marked as done (eclipse-egit: FTBFS: generateScript: Some inter-plug-in dependencies have not been satisfied.)

[Debian Bug Tracking System]

Your message dated Wed, 19 Oct 2016 22:27:57 +
with message-id 
and subject line Bug#813419: fixed in eclipse-egit 3.7.0-2
has caused the Debian Bug report #813419,
regarding eclipse-egit: FTBFS: generateScript: Some inter-plug-in dependencies 
have not been satisfied.
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
813419: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813419
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: eclipse-egit
Version: 3.7.0-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

eclipse-egit fails to build from source in unstable/amd64:

  [..]
  
  init:
  
  generateScript:
  [eclipse.buildScript] Some inter-plug-in dependencies have not been satisfied.
  [eclipse.buildScript] Bundle org.eclipse.egit.mylyn.ui.test:
  [eclipse.buildScript] Host plug-in org.eclipse.egit.mylyn.ui_0.0.0 
has not been found.
  [eclipse.buildScript] Missing required plug-in 
org.apache.log4j_[1.0.0,2.0.0).
  [eclipse.buildScript] Missing required plug-in 
org.hamcrest_[1.1.0,2.0.0).
  [eclipse.buildScript] Bundle org.eclipse.egit.core:
  [eclipse.buildScript] Unsatisfied import package 
org.eclipse.jgit.api_[3.7.0,3.8.0).
  [eclipse.buildScript] Unsatisfied import package 
org.eclipse.jgit.api.errors_[3.7.0,3.8.0).
  [eclipse.buildScript] Unsatisfied import package 
org.eclipse.jgit.diff_[3.7.0,3.8.0).
  [eclipse.buildScript] Unsatisfied import package 
org.eclipse.jgit.dircache_[3.7.0,3.8.0).
  [eclipse.buildScript] Unsatisfied import package 
org.eclipse.jgit.errors_[3.7.0,3.8.0).
  [eclipse.buildScript] Unsatisfied import package 
org.eclipse.jgit.events_[3.7.0,3.8.0).
  [eclipse.buildScript] Unsatisfied import package 
org.eclipse.jgit.internal.storage.file_[3.7.0,3.8.0).
  [eclipse.buildScript] Unsatisfied import package 
org.eclipse.jgit.lib_[3.7.0,3.8.0).
  [eclipse.buildScript] Unsatisfied import package 
org.eclipse.jgit.merge_[3.7.0,3.8.0).
  [eclipse.buildScript] Unsatisfied import package 
org.eclipse.jgit.patch_[3.7.0,3.8.0).
  [eclipse.buildScript] Unsatisfied import package 
org.eclipse.jgit.revwalk_[3.7.0,3.8.0).
  [eclipse.buildScript] Unsatisfied import package 
org.eclipse.jgit.revwalk.filter_[3.7.0,3.8.0).
  [eclipse.buildScript] Unsatisfied import package 
org.eclipse.jgit.storage.file_[3.7.0,3.8.0).
  [eclipse.buildScript] Unsatisfied import package 
org.eclipse.jgit.submodule_[3.7.0,3.8.0).
  [eclipse.buildScript] Unsatisfied import package 
org.eclipse.jgit.transport_[3.7.0,3.8.0).
  [eclipse.buildScript] Unsatisfied import package 
org.eclipse.jgit.treewalk_[3.7.0,3.8.0).
  [eclipse.buildScript] Unsatisfied import package 
org.eclipse.jgit.treewalk.filter_[3.7.0,3.8.0).
  [eclipse.buildScript] Unsatisfied import package 
org.eclipse.jgit.util_[3.7.0,3.8.0).
  [eclipse.buildScript] Unsatisfied import package 
org.eclipse.jgit.util.io_[3.7.0,3.8.0).
  [eclipse.buildScript] Bundle org.eclipse.egit.ui.test:
  [eclipse.buildScript] Host plug-in org.eclipse.egit.ui_0.0.0 has not 
been found.
  [eclipse.buildScript] Missing required plug-in 
org.apache.log4j_[1.0.0,2.0.0).
  [eclipse.buildScript] Missing required plug-in 
org.hamcrest_[1.1.0,2.0.0).
  [eclipse.buildScript] Missing required plug-in 
org.mockito_[1.8.0,1.9.0).
  [eclipse.buildScript] Unsatisfied import package 
org.eclipse.egit.core.test_[3.7.0,3.8.0).
  [eclipse.buildScript] Unsatisfied import package 
org.eclipse.jgit.api_[3.7.0,3.8.0).
  [eclipse.buildScript] Unsatisfied import package 
org.eclipse.jgit.api.errors_[3.7.0,3.8.0).
  [eclipse.buildScript] Unsatisfied import package 
org.eclipse.jgit.junit_[3.7.0,3.8.0).
  [eclipse.buildScript] Unsatisfied import package 
org.eclipse.jgit.junit.http_[3.7.0,3.8.0).
  [eclipse.buildScript] Unsatisfied import package 
org.eclipse.jgit.lib_[3.7.0,3.8.0).
  [eclipse.buildScript] Unsatisfied import package 
org.eclipse.jgit.revwalk_[3.7.0,3.8.0).
  [eclipse.buildScript] Unsatisfied import package 
org.eclipse.jgit.storage.file_[3.7.0,3.8.0).
  [eclipse.buildScript] Unsatisfied import package 
org.eclipse.jgit.transport_[3.7.0,3.8.0).
  [eclipse.buildScript] Unsatisfied 

Bug#817880: marked as done (eclipse-cdt: FTBFS: [javac] 209 problems (1 error, 208 warnings))

[Debian Bug Tracking System]

Your message dated Wed, 19 Oct 2016 22:27:45 +
with message-id 
and subject line Bug#817880: fixed in eclipse-cdt 8.6.0-2
has caused the Debian Bug report #817880,
regarding eclipse-cdt: FTBFS: [javac] 209 problems (1 error, 208 warnings)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
817880: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817880
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: eclipse-cdt
Version: 8.6.0-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

eclipse-cdt fails to build from source in unstable/amd64:

  [..]

  [javac] 206. WARNING in 
/home/lamby/temp/cdt.20160311083107.Icvjb99HY1/eclipse-cdt-8.6.0/debian/.eclipse-build/org.eclipse.cdt.core/utils/org/eclipse/cdt/utils/CygPath.java
 (at line 20)
  [javac]   import org.eclipse.cdt.internal.core.Cygwin;
  [javac]  
  [javac] The import org.eclipse.cdt.internal.core.Cygwin is never used
  [javac] --
  [javac] --
  [javac] 207. WARNING in 
/home/lamby/temp/cdt.20160311083107.Icvjb99HY1/eclipse-cdt-8.6.0/debian/.eclipse-build/org.eclipse.cdt.core/utils/org/eclipse/cdt/utils/EFSExtensionManager.java
 (at line 23)
  [javac]   import org.eclipse.core.runtime.Path;
  [javac]  ^
  [javac] The import org.eclipse.core.runtime.Path is never used
  [javac] --
  [javac] --
  [javac] 208. WARNING in 
/home/lamby/temp/cdt.20160311083107.Icvjb99HY1/eclipse-cdt-8.6.0/debian/.eclipse-build/org.eclipse.cdt.core/utils/org/eclipse/cdt/utils/envvar/StorableEnvironment.java
 (at line 22)
  [javac]   import 
org.eclipse.cdt.utils.envvar.StorableEnvironmentLoader.ISerializeInfo;
  [javac]  
^
  [javac] The import 
org.eclipse.cdt.utils.envvar.StorableEnvironmentLoader.ISerializeInfo is never 
used
  [javac] --
  [javac] --
  [javac] 209. WARNING in 
/home/lamby/temp/cdt.20160311083107.Icvjb99HY1/eclipse-cdt-8.6.0/debian/.eclipse-build/org.eclipse.cdt.core/utils/org/eclipse/cdt/utils/envvar/StorableEnvironmentLoader.java
 (at line 36)
  [javac]   import org.eclipse.core.runtime.preferences.IEclipsePreferences;
  [javac]  
  [javac] The import 
org.eclipse.core.runtime.preferences.IEclipsePreferences is never used
  [javac] --
  [javac] 209 problems (1 error, 208 warnings)
  [javac] Compilation failed. Compiler errors are available in 
/home/lamby/temp/cdt.20160311083107.Icvjb99HY1/eclipse-cdt-8.6.0/debian/.eclipse-build/org.eclipse.cdt.core/@dot.log
  
  BUILD FAILED
  
/usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/scripts/build.xml:36:
 The following error occurred while executing this line:
  
/usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/scripts/build.xml:105:
 The following error occurred while executing this line:
  
/usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/templates/package-build/customTargets.xml:19:
 The following error occurred while executing this line:
  
/usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/scripts/genericTargets.xml:118:
 The following error occurred while executing this line:
  
/usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/scripts/genericTargets.xml:123:
 The following error occurred while executing this line:
  
/home/lamby/temp/cdt.20160311083107.Icvjb99HY1/eclipse-cdt-8.6.0/debian/.eclipse-build/build/features/org.eclipse.cdt.platform/build.xml:65:
 The following error occurred while executing this line:
  
/home/lamby/temp/cdt.20160311083107.Icvjb99HY1/eclipse-cdt-8.6.0/debian/.eclipse-build/build/features/org.eclipse.cdt.platform/build.xml:20:
 The following error occurred while executing this line:
  
/home/lamby/temp/cdt.20160311083107.Icvjb99HY1/eclipse-cdt-8.6.0/debian/.eclipse-build/org.eclipse.cdt.core/build.xml:213:
 The following error occurred while executing this line:
  
/home/lamby/temp/cdt.20160311083107.Icvjb99HY1/eclipse-cdt-8.6.0/debian/.eclipse-build/org.eclipse.cdt.core/build.xml:119:
 Compile failed; see the compiler error output for details.
  
  Total time: 24 seconds
  An error has occurred. 

Bug#841362: activemq-protobuf: FTBFS (Plugin org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies could not be resolved)

[Emmanuel Bourg]

Le 20/10/2016 à 00:06, Santiago Vila a écrit :

> You are absolutely right. Sorry for the duplicates.

No need to be sorry. Your reports and the reproducible build
notifications help us greatly to detect and fix the build issues
quickly, thanks a lot for your time.

Emmanuel Bourg

Bug#841364: partial workaround: purging config files

[Adam Borowski]

It appears that there are two parts to this bug:

1. failure to deal with config files written by older versions.  Nuking
~/.config/Clementine then manually redoing all of your config makes
Clementine at least continue and put its sound _somewhere_.  Whether you'll
actually hear something depends on whether the first device is something
good or some crap like "HDA-Intel - HDA NVidia".  I guess that, had I
connected some HDMI TV or maybe a monitor with built-in speakers, I would
hear something.

2. routing regression gone further -- 1.3.1 merely didn't provide GUI
controls to select an audio sink but it still worked if set by an earlier
version or by manually by editing the config file


-- 
A MAP07 (Dead Simple) raspberry tincture recipe: 0.5l 95% alcohol, 1kg
raspberries, 0.4kg sugar; put into a big jar for 1 month.  Filter out and
throw away the fruits (can dump them into a cake, etc), let the drink age
at least 3-6 months.

Bug#841362: activemq-protobuf: FTBFS (Plugin org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies could not be resolved)

[Santiago Vila]

On Wed, Oct 19, 2016 at 10:50:33PM +0200, Emmanuel Bourg wrote:
> Le 19/10/2016 à 22:31, Santiago Vila a écrit :
> 
> > I have already reported a bug like this in other packages.
> > See Bug #841197 for a likely fix.
> 
> ...and you'll get the same issue with all reverse dependencies of
> maven-enforcer. These bugs are duplicates of the same issue, they should
> be assigned to maven-enforcer, merged, and marked as affecting the
> reverse dependencies:
> [...]

You are absolutely right. Sorry for the duplicates.

I read a message from Markus yesterday, but I read it too fast and
didn't realize he already said this was a bug in maven-enforcer.

I see that he already did the merge and the reassign.

I'm going to make the "affects" with the list of reverse depends you
have provided. This definitely helps me to avoid duplicate bugs.

Thanks a lot.

Processed: Re: Bug#841288: tigervnc-common: amd64 has dep libgnutls-deb0-28

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #841288 [tigervnc-common] tigervnc-common: amd64 has dep libgnutls-deb0-28
Severity set to 'serious' from 'normal'

-- 
841288: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841288
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: bug 841304 is forwarded to https://sourceware.org/ml/libc-alpha/2016-10/msg00325.html

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 841304 https://sourceware.org/ml/libc-alpha/2016-10/msg00325.html
Bug #841304 [glibc] invalid code in glibc tests
Changed Bug forwarded-to-address to 
'https://sourceware.org/ml/libc-alpha/2016-10/msg00325.html' from 
'https://gcc.gnu.org/PR78039'.
> thanks
Stopping processing here.

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

Bug#832838: eclipse-xsd: FTBFS: Duplicate methods named spliterator with the parameters () and () are inherited from the types List and Collection

[Emmanuel Bourg]

Control: notfound -1 2.9.0-1
Control: close -1

This issue was a side effect of #757536. It went away with the upload of
eclipse/3.8.1-9

Processed: Re: Bug#832838: eclipse-xsd: FTBFS: Duplicate methods named spliterator with the parameters () and () are inherited from the types List and Collection

[Debian Bug Tracking System]

Processing control commands:

> notfound -1 2.9.0-1
Bug #832838 [src:eclipse-xsd] eclipse-xsd: FTBFS: Duplicate methods named 
spliterator with the parameters () and () are inherited from the types 
List and Collection
No longer marked as found in versions eclipse-xsd/2.9.0-1.
> close -1
Bug #832838 [src:eclipse-xsd] eclipse-xsd: FTBFS: Duplicate methods named 
spliterator with the parameters () and () are inherited from the types 
List and Collection
Marked Bug as done

-- 
832838: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832838
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#841364: clementine: no sound at all, "GStreamer encountered a general stream error."

[Adam Borowski]

Package: clementine
Version: 1.3.1+git240-g1a2f6e2+dfsg-1
Severity: grave
Justification: renders package unusable


Since today's upload, Clementine fails to produce any sound at all, instead
popping up a window with endlessly repeating:

GStreamer encountered a general stream error.
---
GStreamer encountered a general stream error.
---
GStreamer encountered a general stream error.
---
GStreamer encountered a general stream error.


No amount of messing with user-available settings (which have been dumbed
down to just "Output device" with "Choose automatically" and a handful of
"Default device on ") seems to help.  Settings that are apparently
not meant to be adjusted by the user (~/.config/Clementine/Clementine.conf)
are undocumented at all, with nary a comment; what I remember from past
versions (cf #823301) doesn't seem to work anymore.

This is reproducible on different hardware, even of different architectures
(I just happen to have exactly one non-remote amd64 box but plenty of arms),
all using plain ALSA.



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

Kernel: Linux 4.9.0-rc1-debug-pp2+ (SMP w/6 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages clementine depends on:
ii  gstreamer1.0-plugins-base   1.8.3-1
ii  gstreamer1.0-plugins-good   1.8.3-1+b1
ii  gstreamer1.0-plugins-ugly   1.8.3-1
ii  libc6   2.24-5
ii  libcdio13   0.83-4.2+b1
ii  libchromaprint1 1.3.2-2
ii  libcrypto++65.6.4-1
ii  libfftw3-double33.3.5-1
ii  libgcc1 1:6.2.0-7
ii  libgdk-pixbuf2.0-0  2.36.0-1
ii  libglib2.0-02.50.1-1
ii  libgpod40.8.3-8
ii  libgstreamer-plugins-base1.0-0  1.8.3-1
ii  libgstreamer1.0-0   1.8.3-1
ii  libimobiledevice6   1.2.0+dfsg-3
ii  liblastfm1  1.0.9-1
ii  libmtp9 1.1.12-1
ii  libmygpo-qt11.0.9~git20151122-1
ii  libplist3   1.12-3.1
ii  libprojectm2v5  2.1.0+dfsg-4+b1
ii  libprotobuf10   3.0.0-7
ii  libpulse0   9.0-4.0nosystemd1
ii  libqjson0   0.8.1-3
ii  libqt4-dbus 4:4.8.7+dfsg-9
ii  libqt4-network  4:4.8.7+dfsg-9
ii  libqt4-opengl   4:4.8.7+dfsg-9
ii  libqt4-sql  4:4.8.7+dfsg-9
ii  libqt4-sql-sqlite   4:4.8.7+dfsg-9
ii  libqt4-xml  4:4.8.7+dfsg-9
ii  libqtcore4  4:4.8.7+dfsg-9
ii  libqtgui4   4:4.8.7+dfsg-9
ii  libqxt-gui0 0.6.2-3
ii  libsqlite3-03.15.0-1
ii  libstdc++6  6.2.0-7
ii  libtag1v5   1.11+dfsg.1-0.3
ii  libx11-62:1.6.3-1
ii  projectm-data   2.1.0+dfsg-4
ii  zlib1g  1:1.2.8.dfsg-2+b1

Versions of packages clementine recommends:
ii  gstreamer1.0-alsa  1.8.3-1

Versions of packages clementine suggests:
ii  gstreamer1.0-plugins-bad  1.8.3-1+b3

-- no debconf information

Bug#841362: activemq-protobuf: FTBFS (Plugin org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies could not be resolved)

[Emmanuel Bourg]

Le 19/10/2016 à 22:31, Santiago Vila a écrit :

> I have already reported a bug like this in other packages.
> See Bug #841197 for a likely fix.

...and you'll get the same issue with all reverse dependencies of
maven-enforcer. These bugs are duplicates of the same issue, they should
be assigned to maven-enforcer, merged, and marked as affecting the
reverse dependencies:

  activemq
  activemq-activeio
  activemq-protobuf
  animal-sniffer
  annotation-indexer
  async-http-client
  checkstyle
  jacoco
  jboss-logmanager
  jboss-modules
  junit4
  libhibernate3-java
  maven-jar-plugin
  openjpa
  wagon

Emmanuel Bourg

Processed: maven-enforcer: Missing dependency version causes FTBFS

[Debian Bug Tracking System]

Processing control commands:

> reassign 841197 maven-enforcer
Bug #841197 [src:libhibernate3-java] libhibernate3-java: FTBFS (Plugin 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies 
could not be resolved)
Bug reassigned from package 'src:libhibernate3-java' to 'maven-enforcer'.
No longer marked as found in versions libhibernate3-java/3.6.10.Final-5.
Ignoring request to alter fixed versions of bug #841197 to the same values 
previously set
> reassign 841296 maven-enforcer
Bug #841296 [src:openjpa] openjpa: FTBFS (Plugin 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies 
could not be resolved)
Bug reassigned from package 'src:openjpa' to 'maven-enforcer'.
No longer marked as found in versions openjpa/2.4.0-3.
Ignoring request to alter fixed versions of bug #841296 to the same values 
previously set
> reassign 841362 maven-enforcer
Bug #841362 [src:activemq-protobuf] activemq-protobuf: FTBFS (Plugin 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies 
could not be resolved)
Bug reassigned from package 'src:activemq-protobuf' to 'maven-enforcer'.
No longer marked as found in versions activemq-protobuf/1.1-4.
Ignoring request to alter fixed versions of bug #841362 to the same values 
previously set
> reassign 841363 maven-enforcer
Bug #841363 [src:junit4] junit4: FTBFS (Plugin 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies 
could not be resolved)
Bug reassigned from package 'src:junit4' to 'maven-enforcer'.
No longer marked as found in versions junit4/4.12-4.
Ignoring request to alter fixed versions of bug #841363 to the same values 
previously set
> forcemerge 841197 841296 841362 841363
Bug #841197 [maven-enforcer] libhibernate3-java: FTBFS (Plugin 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies 
could not be resolved)
Bug #841296 [maven-enforcer] openjpa: FTBFS (Plugin 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies 
could not be resolved)
Bug #841362 [maven-enforcer] activemq-protobuf: FTBFS (Plugin 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies 
could not be resolved)
Bug #841363 [maven-enforcer] junit4: FTBFS (Plugin 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies 
could not be resolved)
Merged 841197 841296 841362 841363
> tags 841197 patch pending
Bug #841197 [maven-enforcer] libhibernate3-java: FTBFS (Plugin 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies 
could not be resolved)
Bug #841296 [maven-enforcer] openjpa: FTBFS (Plugin 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies 
could not be resolved)
Bug #841362 [maven-enforcer] activemq-protobuf: FTBFS (Plugin 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies 
could not be resolved)
Bug #841363 [maven-enforcer] junit4: FTBFS (Plugin 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies 
could not be resolved)
Added tag(s) pending and patch.
Added tag(s) patch and pending.
Added tag(s) patch and pending.
Added tag(s) patch and pending.

-- 
841197: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841197
841296: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841296
841362: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841362
841363: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841363
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#841197: maven-enforcer: Missing dependency version causes FTBFS

[Markus Koschany]

Control: reassign 841197 maven-enforcer
Control: reassign 841296 maven-enforcer
Control: reassign 841362 maven-enforcer
Control: reassign 841363 maven-enforcer
Control: forcemerge 841197 841296 841362 841363
Control: tags 841197 patch pending

I am going to reassign this issue to maven-enforcer and patch the pom file.

Markus



signature.asc
Description: OpenPGP digital signature

Bug#841363: junit4: FTBFS (Plugin org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies could not be resolved)

[Santiago Vila]

Package: src:junit4
Version: 4.12-4
Severity: serious

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --parallel --buildsystem=maven
   dh_testdir -i -O--parallel -O--buildsystem=maven
   dh_update_autotools_config -i -O--parallel -O--buildsystem=maven
   dh_auto_configure -i -O--parallel -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 -pjunit4 --debian-build --keep-pom-version 
--maven-repo=/<>/debian/maven-repo
   dh_auto_build -i -O--parallel -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
[INFO] Scanning for projects...
[WARNING] The POM for org.apache.maven.plugins:maven-enforcer-plugin:jar:1.4.1 
is invalid, transitive dependencies (if any) will not be available, enable 
debug logging for more details
[WARNING] Failed to retrieve plugin descriptor for 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1: Plugin 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies 
could not be resolved: Failed to read artifact descriptor for 
org.apache.maven.plugins:maven-enforcer-plugin:jar:1.4.1
[WARNING] The POM for org.apache.maven.plugins:maven-enforcer-plugin:jar:1.4.1 
is invalid, transitive dependencies (if any) will not be available, enable 
debug logging for more details
[WARNING] Failed to retrieve plugin descriptor for 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1: Plugin 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies 
could not be resolved: Failed to read artifact descriptor for 
org.apache.maven.plugins:maven-enforcer-plugin:jar:1.4.1
[INFO] 
[INFO] 
[INFO] Building JUnit 4.12
[INFO] 
[WARNING] The POM for org.apache.maven.plugins:maven-enforcer-plugin:jar:1.4.1 
is invalid, transitive dependencies (if any) will not be available, enable 
debug logging for more details
[WARNING] Failed to retrieve plugin descriptor for 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1: Plugin 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies 
could not be resolved: Failed to read artifact descriptor for 
org.apache.maven.plugins:maven-enforcer-plugin:jar:1.4.1
[WARNING] The POM for org.apache.maven.plugins:maven-enforcer-plugin:jar:1.4.1 
is invalid, transitive dependencies (if any) will not be available, enable 
debug logging for more details
[INFO] 
[INFO] 
[INFO] Skipping JUnit
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 0.345 s
[INFO] Finished at: 2016-10-19T20:46:35+02:00
[INFO] Final Memory: 8M/90M
[INFO] 
[ERROR] Plugin org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of 
its dependencies could not be resolved: Failed to read artifact descriptor for 
org.apache.maven.plugins:maven-enforcer-plugin:jar:1.4.1: 1 problem was 
encountered while building the effective model for 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1
[ERROR] [ERROR] 'dependencies.dependency.version' for 
org.apache.maven.plugin-tools:maven-plugin-annotations:jar is missing. @
[ERROR] -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 

Bug#841362: activemq-protobuf: FTBFS (Plugin org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies could not be resolved)

[Santiago Vila]

Package: src:activemq-protobuf
Version: 1.1-4
Severity: serious

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --parallel --buildsystem=maven
   dh_testdir -i -O--parallel -O--buildsystem=maven
   dh_update_autotools_config -i -O--parallel -O--buildsystem=maven
   dh_auto_configure -i -O--parallel -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 -plibactivemq-protobuf-java --debian-build 
--keep-pom-version --maven-repo=/<>/debian/maven-repo
   dh_auto_build -i -O--parallel -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
[INFO] Scanning for projects...
[WARNING] 

[... snipped ...]

[WARNING] The POM for org.apache.maven.plugins:maven-release-plugin:jar:2.3.2 
is missing, no dependency information available
[WARNING] Failed to retrieve plugin descriptor for 
org.apache.maven.plugins:maven-release-plugin:2.3.2: Plugin 
org.apache.maven.plugins:maven-release-plugin:2.3.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-release-plugin:jar:2.3.2 has not been downloaded 
from it before.
[INFO] 
[INFO] 
[INFO] Building ActiveMQ Protocol Buffers POM 1.1
[INFO] 
[WARNING] The POM for org.apache.maven.plugins:maven-enforcer-plugin:jar:1.4.1 
is invalid, transitive dependencies (if any) will not be available, enable 
debug logging for more details
[WARNING] Failed to retrieve plugin descriptor for 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1: Plugin 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies 
could not be resolved: Failed to read artifact descriptor for 
org.apache.maven.plugins:maven-enforcer-plugin:jar:1.4.1
[WARNING] The POM for org.apache.maven.plugins:maven-deploy-plugin:jar:2.7 is 
missing, no dependency information available
[WARNING] 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.
[WARNING] The POM for org.apache.maven.plugins:maven-site-plugin:jar:3.3 is 
missing, no dependency information available
[WARNING] 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.
[WARNING] The POM for org.apache.maven.plugins:maven-antrun-plugin:jar:1.7 is 
missing, no dependency information available
[WARNING] Failed to retrieve plugin descriptor for 
org.apache.maven.plugins:maven-antrun-plugin:1.7: Plugin 
org.apache.maven.plugins:maven-antrun-plugin:1.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-antrun-plugin:jar:1.7 has not been downloaded 
from it before.
[WARNING] The POM for 
org.apache.maven.plugins:maven-assembly-plugin:jar:2.2-beta-4 is missing, no 
dependency information available
[WARNING] Failed to retrieve plugin descriptor for 
org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-4: Plugin 
org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-4 or one of its 
dependencies could not be resolved: Cannot access central 
(https://repo.maven.apache.org/maven2) in offline 

Bug#831857: libupnp: CVE-2016-6255: write files via POST

[James Cowgill]

Control: tags -1 patch pending

Hi,

I am about to upload the attached NMU to finally fix this bug. I've also
attached a patch suitable for jessie-security, and a test script I used
to create a libupnp server for testing the fix with.

Thanks,
James
/*
 * Upnp CVE-2016-6255 test program
 *
 * This program runs the webserver from libupnp serving files from the current
 * directory. If libupnp is vulnerable to CVE-2016-6255, it will allow uploading
 * files.
 *
 * Example:
 *
 * $ gcc -I/usr/include/upnp cve-2016-6255-test.c -lupnp -ocve-2016-6255-test
 * $ cat testfile
 * cat: testfile: No such file or directory
 * $ ./cve-2016-6255-test > /dev/null &
 * [2] 32309
 * $ curl -i --data $'FAIL\n' http://localhost:49152/testfile
 * $ cat testfile
 * FAIL
 */

#define _GNU_SOURCE
#include 
#include 
#include 

int main(void)
{
	char* wd = get_current_dir_name();

	// Setup upnp
	printf("Init = %d\n", UpnpInit("127.0.0.1", 0));
	printf("SetRoot = %d\n", UpnpSetWebServerRootDir(wd));
	free(wd);

	// Hang
	for (;;)
		pause();
}
diff -Nru libupnp-1.6.19+git20141001/debian/changelog 
libupnp-1.6.19+git20141001/debian/changelog
--- libupnp-1.6.19+git20141001/debian/changelog 2014-10-23 21:48:01.0 
+0100
+++ libupnp-1.6.19+git20141001/debian/changelog 2016-10-19 21:02:05.0 
+0100
@@ -1,3 +1,12 @@
+libupnp (1:1.6.19+git20141001-1+deb8u1) jessie-security; urgency=high
+
+  * Non-maintainer upload.
+  * Don't allow unhandled POSTs to write to the filesystem by
+default (Closes: #831857) (CVE-2016-6255)
+Thanks to Matthew Garrett for the patch.
+
+ -- James Cowgill   Wed, 19 Oct 2016 21:02:05 +0100
+
 libupnp (1:1.6.19+git20141001-1) unstable; urgency=low
 
   * Ack both NMUs, thankyou for your care of this package.
diff -Nru libupnp-1.6.19+git20141001/debian/patches/CVE-2016-6255.patch 
libupnp-1.6.19+git20141001/debian/patches/CVE-2016-6255.patch
--- libupnp-1.6.19+git20141001/debian/patches/CVE-2016-6255.patch   
1970-01-01 01:00:00.0 +0100
+++ libupnp-1.6.19+git20141001/debian/patches/CVE-2016-6255.patch   
2016-10-19 21:00:38.0 +0100
@@ -0,0 +1,61 @@
+From c91a8a3903367e1163765b73eb4d43be7d7927fa Mon Sep 17 00:00:00 2001
+From: Matthew Garrett 
+Date: Tue, 23 Feb 2016 13:53:20 -0800
+Subject: [PATCH] Don't allow unhandled POSTs to write to the filesystem by
+ default
+
+If there's no registered handler for a POST request, the default behaviour
+is to write it to the filesystem. Several million deployed devices appear
+to have this behaviour, making it possible to (at least) store arbitrary
+data on them. Add a configure option that enables this behaviour, and change
+the default to just drop POSTs that aren't directly handled.
+
+Signed-off-by: Marcelo Roberto Jimenez 
+---
+ configure.ac | 4 
+ upnp/inc/upnpconfig.h.in | 5 +
+ upnp/src/genlib/net/http/webserver.c | 4 
+ 3 files changed, 13 insertions(+)
+
+--- a/configure.ac
 b/configure.ac
+@@ -495,6 +495,10 @@ if test "x$enable_blocking_tcp_connectio
+ AC_DEFINE(UPNP_ENABLE_BLOCKING_TCP_CONNECTIONS, 1, [see upnpconfig.h])
+ fi
+ 
++RT_BOOL_ARG_ENABLE([postwrite], [no], [write to the filesystem on otherwise 
unhandled POST requests])
++if test "x$enable_postwrite" = xyes ; then
++AC_DEFINE(UPNP_ENABLE_POST_WRITE, 1, [see upnpconfig.h])
++fi
+ 
+ RT_BOOL_ARG_ENABLE([samples], [yes], [compilation of upnp/sample/ code])
+ 
+--- a/upnp/inc/upnpconfig.h.in
 b/upnp/inc/upnpconfig.h.in
+@@ -131,5 +131,10 @@
+  * header (i.e. configure --enable-unspecified_server) */
+ #undef UPNP_ENABLE_UNSPECIFIED_SERVER
+ 
++/** Defined to 1 if the library has been compiled to support filesystem 
writes on POST
++ *  (i.e. configure --enable-postwrite) */
++#undef UPNP_ENABLE_POST_WRITE
++
++
+ #endif /* UPNP_CONFIG_H */
+ 
+--- a/upnp/src/genlib/net/http/webserver.c
 b/upnp/src/genlib/net/http/webserver.c
+@@ -1366,9 +1366,13 @@ static int http_RecvPostMessage(
+   if (Fp == NULL)
+   return HTTP_INTERNAL_SERVER_ERROR;
+   } else {
++#ifdef UPNP_ENABLE_POST_WRITE
+   Fp = fopen(filename, "wb");
+   if (Fp == NULL)
+   return HTTP_UNAUTHORIZED;
++#else
++  return HTTP_NOT_FOUND;
++#endif
+   }
+   parser->position = POS_ENTITY;
+   do {
diff -Nru libupnp-1.6.19+git20141001/debian/patches/series 
libupnp-1.6.19+git20141001/debian/patches/series
--- libupnp-1.6.19+git20141001/debian/patches/series2014-10-04 
05:26:29.0 +0100
+++ libupnp-1.6.19+git20141001/debian/patches/series2016-10-19 
21:00:43.0 +0100
@@ -5,3 +5,4 @@
 18-url-upnpstrings.patch
 19_fix_tests.patch
 21_fix-1.6.19+git.patch
+CVE-2016-6255.patch
diff -Nru libupnp-1.6.19+git20160116/debian/changelog 
libupnp-1.6.19+git20160116/debian/changelog
--- libupnp-1.6.19+git20160116/debian/changelog 2016-01-17 

Processed: Bug#831857: libupnp: CVE-2016-6255: write files via POST

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch pending
Bug #831857 [src:libupnp] libupnp: CVE-2016-6255: write files via POST
Added tag(s) pending and patch.

-- 
831857: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831857
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#841313: latex-cjk-japanese-wadalab: FTBFS: Create .afm and .pfa fonts from dg. \n Segmentation fault (core dumped)

[Hilmar Preuße]

Am 19.10.2016 um 17:20 schrieb Danai SAE-HAN (韓達耐):

Hi all,


It looks like a problem with the wftodm binary.  This is an important piece
in the creation of the fonts.
I will only have access to my PC next week Thursday (27 October 2016) to
check the C source code and replicate it on amd64.  Please bear with me for
a while.


I *think* I can reproduce the bug.

Here is the gdb backtrace:

Program terminated with signal SIGSEGV, Segmentation fault.
#0  strlen () at ../sysdeps/x86_64/strlen.S:106
106 ../sysdeps/x86_64/strlen.S: No such file or directory.
(gdb) bt
#0  strlen () at ../sysdeps/x86_64/strlen.S:106
#1  0x2ba08dfdbda3 in _IO_vfprintf_internal (s=s@entry=0x7ffd926eb3f0,
format=, format@entry=0x5643d866b22e "/StdHW [ %s ] 
|-\n",

ap=ap@entry=0x7ffd926eb518) at vfprintf.c:1637
#2  0x2ba08dffcacb in __IO_vsprintf (
string=0x7ffd926eb620 "/StdHW [ re{16 16} |-\n",
format=0x5643d866b22e "/StdHW [ %s ] |-\n", 
args=args@entry=0x7ffd926eb518)

at iovsprintf.c:42
#3  0x2ba08dfe2327 in __sprintf (s=, 
format=)

at sprintf.c:32
#4  0x5643d866a8e2 in e_printf (form=, i0=out>,

i1=, i2=, i3=,
i4=, i5=1936353124, i6=-1838284703, i7=0, 
i8=-1909291776,

i9=0) at wftodm.c:306
#5  0x5643d866aa77 in output_pfa (file=1) at wftodm.c:255
#6  0x5643d8669d3a in main (ac=, ag=)
at wftodm.c:158

And here is the function e_printf() in question:

e_printf(form,i0,i1,i2,i3,i4,i5,i6,i7,i8,i9)
char *form;
{
  int len,i;
  unsigned char buf[4096];
  sprintf(buf,form,i0,i1,i2,i3,i4,i5,i6,i7,i8,i9);
  len=strlen(buf);
  for(i=0;i

Processed: forwarded zshdb ftbfs bug

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 841342 https://github.com/rocky/zshdb/issues/8
Bug #841342 [src:zshdb] zshdb: FTBFS under some locales (eg. fr_CH.UTF-8)
Set Bug forwarded-to-address to 'https://github.com/rocky/zshdb/issues/8'.
> kthxbye
Stopping processing here.

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

Processed: node-once: missing dependency on node-wrappy makes a lot of packages to FTBFS

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 841274 + patch
Bug #841274 [node-once] node-once: missing dependency on node-wrappy makes a 
lot of packages to FTBFS
Bug #841321 [node-once] node-once: missing dependency on node-wrappy makes a 
lot of packages to FTBFS
Bug #841322 [node-once] node-once: missing dependency on node-wrappy makes a 
lot of packages to FTBFS
Bug #841323 [node-once] node-once: missing dependency on node-wrappy makes a 
lot of packages to FTBFS
Bug #841324 [node-once] node-once: missing dependency on node-wrappy makes a 
lot of packages to FTBFS
Bug #841325 [node-once] node-once: missing dependency on node-wrappy makes a 
lot of packages to FTBFS
Bug #841326 [node-once] node-once: missing dependency on node-wrappy makes a 
lot of packages to FTBFS
Bug #841327 [node-once] node-once: missing dependency on node-wrappy makes a 
lot of packages to FTBFS
Bug #841328 [node-once] node-once: missing dependency on node-wrappy makes a 
lot of packages to FTBFS
Bug #841329 [node-once] node-once: missing dependency on node-wrappy makes a 
lot of packages to FTBFS
Bug #841330 [node-once] node-once: missing dependency on node-wrappy makes a 
lot of packages to FTBFS
Bug #841331 [node-once] node-once: missing dependency on node-wrappy makes a 
lot of packages to FTBFS
Bug #841332 [node-once] node-once: missing dependency on node-wrappy makes a 
lot of packages to FTBFS
Bug #841333 [node-once] node-once: missing dependency on node-wrappy makes a 
lot of packages to FTBFS
Bug #841334 [node-once] node-once: missing dependency on node-wrappy makes a 
lot of packages to FTBFS
Bug #841335 [node-once] node-once: missing dependency on node-wrappy makes a 
lot of packages to FTBFS
Bug #841336 [node-once] node-once: missing dependency on node-wrappy makes a 
lot of packages to FTBFS
Bug #841337 [node-once] node-once: missing dependency on node-wrappy makes a 
lot of packages to FTBFS
Bug #841338 [node-once] node-once: missing dependency on node-wrappy makes a 
lot of packages to FTBFS
Added tag(s) patch.
Added tag(s) patch.
Added tag(s) patch.
Added tag(s) patch.
Added tag(s) patch.
Added tag(s) patch.
Added tag(s) patch.
Added tag(s) patch.
Added tag(s) patch.
Added tag(s) patch.
Added tag(s) patch.
Added tag(s) patch.
Added tag(s) patch.
Added tag(s) patch.
Added tag(s) patch.
Added tag(s) patch.
Added tag(s) patch.
Added tag(s) patch.
Added tag(s) patch.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
841274: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841274
841321: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841321
841322: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841322
841323: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841323
841324: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841324
841325: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841325
841326: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841326
841327: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841327
841328: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841328
841329: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841329
841330: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841330
841331: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841331
841332: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841332
841333: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841333
841334: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841334
841335: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841335
841336: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841336
841337: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841337
841338: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841338
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#841274: node-once: missing dependency on node-wrappy makes a lot of packages to FTBFS

[Santiago Vila]

tags 841274 + patch
thanks

Trivial patch attached.

(Not that I know anything about node, this is just the message from
Bas but translated to patch).

Thanks.--- a/debian/control
+++ b/debian/control
@@ -15,6 +15,7 @@ Package: node-once
 Architecture: all
 Depends:
  ${misc:Depends}
+ , node-wrappy
  , nodejs
 Description: Run a function only once with this module for Node.js
  node-once is useful to make sure a listener for multiple events is

Processed: Re: node-define-property: FTBFS: Error: Cannot find module 'wrappy'

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 841274 node-once
Bug #841274 [node-define-property] node-define-property: FTBFS: Error: Cannot 
find module 'wrappy'
Bug #841321 [node-define-property] node-collection-visit: FTBFS (Error: Cannot 
find module wrappy)
Bug #841322 [node-define-property] node-component-emitter: FTBFS (Error: Cannot 
find module wrappy)
Bug #841323 [node-define-property] node-copy-descriptor: FTBFS (Error: Cannot 
find module wrappy)
Bug #841324 [node-define-property] node-extend-shallow: FTBFS (Error: Cannot 
find module wrappy)
Bug #841325 [node-define-property] node-filename-regex: FTBFS (Error: Cannot 
find module wrappy)
Bug #841326 [node-define-property] node-fill-range: FTBFS (Error: Cannot find 
module wrappy)
Bug #841327 [node-define-property] node-glob-parent: FTBFS (Error: Cannot find 
module wrappy)
Bug #841328 [node-define-property] node-has-values: FTBFS (Error: Cannot find 
module wrappy)
Bug #841329 [node-define-property] node-hosted-git-info: FTBFS (Error: Cannot 
find module wrappy)
Bug #841330 [node-define-property] node-is-dotfile: FTBFS (Error: Cannot find 
module wrappy)
Bug #841331 [node-define-property] node-is-primitive: FTBFS (Error: Cannot find 
module wrappy)
Bug #841332 [node-define-property] node-isexe: FTBFS (Error: Cannot find module 
wrappy)
Bug #841333 [node-define-property] node-isobject: FTBFS (Error: Cannot find 
module wrappy)
Bug #841334 [node-define-property] node-map-cache: FTBFS (Error: Cannot find 
module wrappy)
Bug #841335 [node-define-property] node-map-visit: FTBFS (Error: Cannot find 
module wrappy)
Bug #841336 [node-define-property] node-normalize-path: FTBFS (Error: Cannot 
find module wrappy)
Bug #841337 [node-define-property] node-pascalcase: FTBFS (Error: Cannot find 
module wrappy)
Bug #841338 [node-define-property] node-repeat-element: FTBFS (Error: Cannot 
find module wrappy)
Bug reassigned from package 'node-define-property' to 'node-once'.
Bug reassigned from package 'node-define-property' to 'node-once'.
Bug reassigned from package 'node-define-property' to 'node-once'.
Bug reassigned from package 'node-define-property' to 'node-once'.
Bug reassigned from package 'node-define-property' to 'node-once'.
Bug reassigned from package 'node-define-property' to 'node-once'.
Bug reassigned from package 'node-define-property' to 'node-once'.
Bug reassigned from package 'node-define-property' to 'node-once'.
Bug reassigned from package 'node-define-property' to 'node-once'.
Bug reassigned from package 'node-define-property' to 'node-once'.
Bug reassigned from package 'node-define-property' to 'node-once'.
Bug reassigned from package 'node-define-property' to 'node-once'.
Bug reassigned from package 'node-define-property' to 'node-once'.
Bug reassigned from package 'node-define-property' to 'node-once'.
Bug reassigned from package 'node-define-property' to 'node-once'.
Bug reassigned from package 'node-define-property' to 'node-once'.
Bug reassigned from package 'node-define-property' to 'node-once'.
Bug reassigned from package 'node-define-property' to 'node-once'.
Bug reassigned from package 'node-define-property' to 'node-once'.
No longer marked as found in versions node-define-property/0.2.5-1.
No longer marked as found in versions node-define-property/0.2.5-1.
No longer marked as found in versions node-define-property/0.2.5-1.
No longer marked as found in versions node-define-property/0.2.5-1.
No longer marked as found in versions node-define-property/0.2.5-1.
No longer marked as found in versions node-define-property/0.2.5-1.
No longer marked as found in versions node-define-property/0.2.5-1.
No longer marked as found in versions node-define-property/0.2.5-1.
No longer marked as found in versions node-define-property/0.2.5-1.
No longer marked as found in versions node-define-property/0.2.5-1.
No longer marked as found in versions node-define-property/0.2.5-1.
No longer marked as found in versions node-define-property/0.2.5-1.
No longer marked as found in versions node-define-property/0.2.5-1.
No longer marked as found in versions node-define-property/0.2.5-1.
No longer marked as found in versions node-define-property/0.2.5-1.
No longer marked as found in versions node-define-property/0.2.5-1.
No longer marked as found in versions node-define-property/0.2.5-1.
No longer marked as found in versions node-define-property/0.2.5-1.
No longer marked as found in versions node-define-property/0.2.5-1.
Ignoring request to alter fixed versions of bug #841274 to the same values 
previously set
Ignoring request to alter fixed versions of bug #841321 to the same values 
previously set
Ignoring request to alter fixed versions of bug #841322 to the same values 
previously set
Ignoring request to alter fixed versions of bug #841323 to the same values 
previously set
Ignoring request to alter fixed versions of bug #841324 to the same values 
previously set
Ignoring request to alter fixed versions of bug #841325 to the same values 

Bug#841274: node-define-property: FTBFS: Error: Cannot find module 'wrappy'

[Santiago Vila]

reassign 841274 node-once
found 841274 1.4.0-1
retitle 841274 node-once: missing dependency on node-wrappy makes a lot of 
packages to FTBFS
thanks

On Wed, Oct 19, 2016 at 08:47:35PM +0200, Sebastiaan Couwenberg wrote:
> On Wed, 19 Oct 2016 20:06:54 +0200 (CEST) Santiago Vila wrote:
> > If anybody reading this could tell me how we arrived at having so many
> > one-day-old unbuildable packages in unstable, I'm still curious about it.
> 
> Because node-once was updated to a new upstream release which now
> requires node-wrappy but didn't add this to its dependencies.

Ok, so if I understood correctly, the above commands should better
reflect the reality.

Thanks a lot.

Bug#841274: node-define-property: FTBFS: Error: Cannot find module 'wrappy'

[Sebastiaan Couwenberg]

On Wed, 19 Oct 2016 20:06:54 +0200 (CEST) Santiago Vila wrote:
> If anybody reading this could tell me how we arrived at having so many
> one-day-old unbuildable packages in unstable, I'm still curious about it.

Because node-once was updated to a new upstream release which now
requires node-wrappy but didn't add this to its dependencies.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Processed: Re: ocaml: Please build libasmrun.a with -fPIC

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #837359 [src:ocaml] ocaml: Please build libasmrun.a and libcamlrun.a with 
-fPIC
Severity set to 'serious' from 'important'
> affects -1 + botch
Bug #837359 [src:ocaml] ocaml: Please build libasmrun.a and libcamlrun.a with 
-fPIC
Added indication that 837359 affects botch

-- 
837359: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837359
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#841340: marked as done (invalid code in virtualbox sources)

[Debian Bug Tracking System]

Your message dated Wed, 19 Oct 2016 18:36:18 +
with message-id 
and subject line Bug#841340: fixed in virtualbox 5.1.8-dfsg-3
has caused the Debian Bug report #841340,
regarding invalid code in virtualbox sources
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
841340: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841340
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gcc
Version: 6.2.0-7
Severity: serious

As said, I built virtualbox correctly with 6.2.0-6 and then uploaded on 
unstable.
The new gcc 6.2.0-7 broke the build with the following error:


kmk_builtin_rm -f -- /«PKGBUILDDIR»/out/obj/VBoxVMM/dtrace/dtrace/VBoxVMM.h.dep 
/«PKGBUILDDIR»/out/obj/VBoxVMM/dtrace/dtrace/VBoxVMM.h
/«PKGBUILDDIR»/out/obj/VBoxTpG/VBoxTpG -64 -h --host-64-bit  --ring-3-context 
-o "/«PKGBUILDDIR»/out/obj/VBoxVMM/dtrace/dtrace/VBoxVMM.h" -s 
"/«PKGBUILDDIR»/src/VBox/VMM/VBoxVMM.d"
kBuild: Generating VBoxDD - 
/«PKGBUILDDIR»/out/obj/VBoxDD/dtrace/dtrace/VBoxDD.h from 
/«PKGBUILDDIR»/src/VBox/Devices/build/VBoxDD.d
kmk_builtin_rm -f -- /«PKGBUILDDIR»/out/obj/VBoxDD/dtrace/dtrace/VBoxDD.h.dep 
/«PKGBUILDDIR»/out/obj/VBoxDD/dtrace/dtrace/VBoxDD.h
/«PKGBUILDDIR»/out/obj/VBoxTpG/VBoxTpG -64 -h --host-64-bit  --ring-3-context 
-o "/«PKGBUILDDIR»/out/obj/VBoxDD/dtrace/dtrace/VBoxDD.h" -s 
"/«PKGBUILDDIR»/src/VBox/Devices/build/VBoxDD.d"
VBoxTpG: warning: Please avoid using the type 'unsigned int' for probe 
arguments!
VBoxTpG: warning: Please avoid using the type 'unsigned int' for probe 
arguments!
VBoxTpG: warning: Please avoid using the type 'unsigned int' for probe 
arguments!
VBoxTpG: warning: Please avoid using the type 'unsigned int' for probe 
arguments!
VBoxTpG: warning: Please avoid using the type 'unsigned int' for probe 
arguments!
kBuild: Installing VBoxOGLcrutil => 
/«PKGBUILDDIR»/out/bin/additions/VBoxOGLcrutil.so 
kmk_builtin_install --hard-link-files-when-possible-- 
/«PKGBUILDDIR»/out/obj/VBoxOGLcrutil/VBoxOGLcrutil.so 
/«PKGBUILDDIR»/out/bin/additions/VBoxOGLcrutil.so
kBuild: Linking VBoxOGLerrorspu => 
/«PKGBUILDDIR»/out/obj/VBoxOGLerrorspu/VBoxOGLerrorspu.so
kmk_builtin_rm -f -- /«PKGBUILDDIR»/out/obj/VBoxOGLerrorspu/VBoxOGLerrorspu.dep 
/«PKGBUILDDIR»/out/obj/VBoxOGLerrorspu/VBoxOGLerrorspu.so  
/«PKGBUILDDIR»/out/obj/VBoxOGLerrorspu/VBoxOGLerrorspu.map 
gcc -shared-fPIC  -Wl,-z,noexecstack,-z,relro -Wl,--as-needed 
-m64   -o /«PKGBUILDDIR»/out/obj/VBoxOGLerrorspu/VBoxOGLerrorspu.so 
-Wl,-soname=VBoxOGLerrorspu.so 
/«PKGBUILDDIR»/out/obj/VBoxOGLerrorspu/gen/VBoxOGLgen/errorspu.o 
/«PKGBUILDDIR»/out/obj/VBoxOGLerrorspu/error/errorspu_init.o 
/«PKGBUILDDIR»/out/bin/additions/VBoxOGLcrutil.so   
/«PKGBUILDDIR»/out/lib/additions/RuntimeGuestR3Shared.a   
/«PKGBUILDDIR»/out/lib/additions/VBoxGuestR3LibShared.a   
/«PKGBUILDDIR»/out/lib/additions/RuntimeGuestR3Shared.a   -lpthread   -lrt   
-lm   -ldl 
kBuild: Linking VBoxOGL => /«PKGBUILDDIR»/out/obj/VBoxOGL/VBoxOGL.so
kmk_builtin_rm -f -- /«PKGBUILDDIR»/out/obj/VBoxOGL/VBoxOGL.dep 
/«PKGBUILDDIR»/out/obj/VBoxOGL/VBoxOGL.so  
/«PKGBUILDDIR»/out/obj/VBoxOGL/VBoxOGL.map 
gcc -shared-fPIC -Wl,-z,nodelete  -Wl,-z,noexecstack,-z,relro 
-Wl,--as-needed -Wl,-e,LibMain -m64   -o 
/«PKGBUILDDIR»/out/obj/VBoxOGL/VBoxOGL.so -Wl,-soname=libGL.so.1 
/«PKGBUILDDIR»/out/obj/VBoxOGL/load.o /«PKGBUILDDIR»/out/obj/VBoxOGL/stub.o 
/«PKGBUILDDIR»/out/obj/VBoxOGL/context.o 
/«PKGBUILDDIR»/out/obj/VBoxOGL/gen/VBoxOGLgen/getprocaddress.o 
/«PKGBUILDDIR»/out/obj/VBoxOGL/gen/VBoxOGLgen/NULLfuncs.o 
/«PKGBUILDDIR»/out/obj/VBoxOGL/gen/VBoxOGLgen/tsfuncs.o 
/«PKGBUILDDIR»/out/obj/VBoxOGL/glx.o /«PKGBUILDDIR»/out/obj/VBoxOGL/xfont.o 
/«PKGBUILDDIR»/out/obj/VBoxOGL/gen/VBoxOGLgen/linux_exports.o 
/«PKGBUILDDIR»/out/lib/additions/RuntimeGuestR3Shared.a   
/«PKGBUILDDIR»/out/lib/additions/VBoxGuestR3LibShared.a   
/«PKGBUILDDIR»/out/bin/additions/VBoxOGLcrutil.so   
/«PKGBUILDDIR»/out/lib/additions/VBoxOGLspuload.a   -lXcomposite   -lXdamage   
-lXfixes   -lXext   /«PKGBUILDDIR»/out/lib/additions/RuntimeGuestR3Shared.a   
/«PKGBUILDDIR»/out/lib/additions/VBoxGuestR3LibShared.a   
/«PKGBUILDDIR»/out/lib/additions/RuntimeGuestR3Shared.a   -lpthread   -lrt   
-lm   -ldl 
/usr/bin/ld: warning: cannot find entry symbol LibMain; defaulting to 
00058030
kBuild: Linking VBoxOGLarrayspu => 
/«PKGBUILDDIR»/out/obj/VBoxOGLarrayspu/VBoxOGLarrayspu.so
kmk_builtin_rm -f -- /«PKGBUILDDIR»/out/obj/VBoxOGLarrayspu/VBoxOGLarrayspu.dep 

Bug#841352: libnftnl: FTBFS (testsuite error) on Big Endian Architectures

[Gianfranco Costamagna]

Source: libnftnl
Version: 1.0.6-2
Severity: serious

Hi, as you know, the current package is not migrating because of testsuite 
failures on BE architectures.

Unfortunately I don't have a patch, but in Ubuntu we are excluding them from 
the testsuite

diff -Nru libnftnl-1.0.6/debian/rules libnftnl-1.0.6/debian/rules
--- libnftnl-1.0.6/debian/rules 2016-10-10 11:36:28.0 +0200
+++ libnftnl-1.0.6/debian/rules 2016-10-19 11:36:06.0 +0200
@@ -4,6 +4,7 @@
#export DH_VERBOSE=1

DEB_HOST_MULTIARCH ?= $(shell dpkg-architecture -qDEB_HOST_MULTIARCH)
+DEB_BUILD_ARCH_ENDIAN ?= $(shell dpkg-architecture -qDEB_BUILD_ARCH_ENDIAN)


%:
@@ -17,4 +18,6 @@

override_dh_auto_test:
dh_auto_test
+ifeq (little,$(DEB_BUILD_ARCH_ENDIAN))
sh -c "cd tests; set -e; ./test-script.sh"
+endif


I'm not tagging the bug patch, because this isn't obviously a real patch.

cheers,

Gianfranco

Bug#841274: node-define-property: FTBFS: Error: Cannot find module 'wrappy'

[Santiago Vila]

Hi.

The bugs I filed should now all be merged into this one, and I've used
affects with src: so that any clone of myself in a parallel universe
can see them and not file more duplicates.

If anybody reading this could tell me how we arrived at having so many
one-day-old unbuildable packages in unstable, I'm still curious about it.

Thanks.

Processed: Tidy up. Stage four

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> found 841274 0.2.5-1
Bug #841274 [node-define-property] node-define-property: FTBFS: Error: Cannot 
find module 'wrappy'
Bug #841321 [node-define-property] node-collection-visit: FTBFS (Error: Cannot 
find module wrappy)
Bug #841322 [node-define-property] node-component-emitter: FTBFS (Error: Cannot 
find module wrappy)
Bug #841323 [node-define-property] node-copy-descriptor: FTBFS (Error: Cannot 
find module wrappy)
Bug #841324 [node-define-property] node-extend-shallow: FTBFS (Error: Cannot 
find module wrappy)
Bug #841325 [node-define-property] node-filename-regex: FTBFS (Error: Cannot 
find module wrappy)
Bug #841326 [node-define-property] node-fill-range: FTBFS (Error: Cannot find 
module wrappy)
Bug #841327 [node-define-property] node-glob-parent: FTBFS (Error: Cannot find 
module wrappy)
Bug #841328 [node-define-property] node-has-values: FTBFS (Error: Cannot find 
module wrappy)
Bug #841329 [node-define-property] node-hosted-git-info: FTBFS (Error: Cannot 
find module wrappy)
Bug #841330 [node-define-property] node-is-dotfile: FTBFS (Error: Cannot find 
module wrappy)
Bug #841331 [node-define-property] node-is-primitive: FTBFS (Error: Cannot find 
module wrappy)
Bug #841332 [node-define-property] node-isexe: FTBFS (Error: Cannot find module 
wrappy)
Bug #841333 [node-define-property] node-isobject: FTBFS (Error: Cannot find 
module wrappy)
Bug #841334 [node-define-property] node-map-cache: FTBFS (Error: Cannot find 
module wrappy)
Bug #841335 [node-define-property] node-map-visit: FTBFS (Error: Cannot find 
module wrappy)
Bug #841336 [node-define-property] node-normalize-path: FTBFS (Error: Cannot 
find module wrappy)
Bug #841337 [node-define-property] node-pascalcase: FTBFS (Error: Cannot find 
module wrappy)
Bug #841338 [node-define-property] node-repeat-element: FTBFS (Error: Cannot 
find module wrappy)
Marked as found in versions node-define-property/0.2.5-1.
Marked as found in versions node-define-property/0.2.5-1.
Marked as found in versions node-define-property/0.2.5-1.
Marked as found in versions node-define-property/0.2.5-1.
Marked as found in versions node-define-property/0.2.5-1.
Marked as found in versions node-define-property/0.2.5-1.
Marked as found in versions node-define-property/0.2.5-1.
Marked as found in versions node-define-property/0.2.5-1.
Marked as found in versions node-define-property/0.2.5-1.
Marked as found in versions node-define-property/0.2.5-1.
Marked as found in versions node-define-property/0.2.5-1.
Marked as found in versions node-define-property/0.2.5-1.
Marked as found in versions node-define-property/0.2.5-1.
Marked as found in versions node-define-property/0.2.5-1.
Marked as found in versions node-define-property/0.2.5-1.
Marked as found in versions node-define-property/0.2.5-1.
Marked as found in versions node-define-property/0.2.5-1.
Marked as found in versions node-define-property/0.2.5-1.
Marked as found in versions node-define-property/0.2.5-1.
> affects 841274 = 
> src:node-collection-visit,src:node-component-emitter,src:node-copy-descriptor,src:node-define-property,src:node-extend-shallow,src:node-filename-regex,src:node-fill-range,src:node-glob-parent,src:node-has-values,src:node-hosted-git-info,src:node-is-accessor-descriptor,src:node-is-descriptor,src:node-is-dotfile,src:node-isexe,src:node-is-extendable,src:node-is-number,src:node-isobject,src:node-is-primitive,src:node-map-cache,src:node-map-visit,src:node-normalize-path,src:node-pascalcase,src:node-repeat-element,src:node-to-regex-range,
Bug #841274 [node-define-property] node-define-property: FTBFS: Error: Cannot 
find module 'wrappy'
Bug #841321 [node-define-property] node-collection-visit: FTBFS (Error: Cannot 
find module wrappy)
Bug #841322 [node-define-property] node-component-emitter: FTBFS (Error: Cannot 
find module wrappy)
Bug #841323 [node-define-property] node-copy-descriptor: FTBFS (Error: Cannot 
find module wrappy)
Bug #841324 [node-define-property] node-extend-shallow: FTBFS (Error: Cannot 
find module wrappy)
Bug #841325 [node-define-property] node-filename-regex: FTBFS (Error: Cannot 
find module wrappy)
Bug #841326 [node-define-property] node-fill-range: FTBFS (Error: Cannot find 
module wrappy)
Bug #841327 [node-define-property] node-glob-parent: FTBFS (Error: Cannot find 
module wrappy)
Bug #841328 [node-define-property] node-has-values: FTBFS (Error: Cannot find 
module wrappy)
Bug #841329 [node-define-property] node-hosted-git-info: FTBFS (Error: Cannot 
find module wrappy)
Bug #841330 [node-define-property] node-is-dotfile: FTBFS (Error: Cannot find 
module wrappy)
Bug #841331 [node-define-property] node-is-primitive: FTBFS (Error: Cannot find 
module wrappy)
Bug #841332 [node-define-property] node-isexe: FTBFS (Error: Cannot find module 
wrappy)
Bug #841333 [node-define-property] node-isobject: FTBFS (Error: Cannot find 
module wrappy)
Bug #841334 [node-define-property] node-map-cache: FTBFS (Error: Cannot find 
module 

Bug#806613: marked as done (eclipse: FTBFS when built with dpkg-buildpackage -A (dh_install: eclipse-jdt missing files))

[Debian Bug Tracking System]

Your message dated Wed, 19 Oct 2016 17:40:51 +
with message-id 
and subject line Bug#806613: fixed in eclipse 3.8.1-9
has caused the Debian Bug report #806613,
regarding eclipse: FTBFS when built with dpkg-buildpackage -A (dh_install: 
eclipse-jdt missing files)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
806613: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806613
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:eclipse
Version: 3.8.1-8
User: sanv...@debian.org
Usertags: binary-indep
Severity: important

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(i.e. only architecture-independent packages), and it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_testdir -i
   dh_auto_configure -i
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build -- provision.cvs
ant provision.cvs
Buildfile: /<>/build.xml
 [echo] Build log is available in build_20151025202140.log
 [echo] uname -m: x86_64. Build eclipse on x86_64 for x86_64.


[... snipped ...]

   [delete] Deleting 
/<>/debian/tmp/usr/lib/eclipse/configuration/org.eclipse.osgi/bundles/81/data/672778795/artifacts.xml
   [delete] Deleting 
/<>/debian/tmp/usr/lib/eclipse/configuration/org.eclipse.osgi/bundles/81/data/672778795/content.jar
   [delete] Deleting 
/<>/debian/tmp/usr/lib/eclipse/configuration/org.eclipse.osgi/bundles/90/data/cache.timestamps
   [delete] Deleting 
/<>/debian/tmp/usr/lib/eclipse/configuration/org.eclipse.osgi/bundles/90/data/listener_1925729951/artifacts.jar
   [delete] Deleting 
/<>/debian/tmp/usr/lib/eclipse/configuration/org.eclipse.osgi/bundles/90/data/listener_1925729951/content.jar
   [delete] Deleting 
/<>/debian/tmp/usr/lib/eclipse/configuration/org.eclipse.osgi/bundles/90/data/timestamps190749078
   [delete] Deleting 
/<>/debian/tmp/usr/lib/eclipse/configuration/org.eclipse.update/history/144580191.xml
   [delete] Deleting 
/<>/debian/tmp/usr/lib/eclipse/configuration/org.eclipse.update/platform.xml
   [delete] Deleting 
/<>/debian/tmp/usr/lib/eclipse/configuration/org.eclipse.osgi/bundles/90/data/listener_1925729951
   [delete] Deleting 
/<>/debian/tmp/usr/lib/eclipse/configuration/org.eclipse.osgi/bundles/90/data
   [delete] Deleting 
/<>/debian/tmp/usr/lib/eclipse/configuration/org.eclipse.osgi/bundles/81/data/672778795
   [delete] Deleting 
/<>/debian/tmp/usr/lib/eclipse/configuration/org.eclipse.osgi/bundles/81/data
   [delete] Deleting 
/<>/debian/tmp/usr/lib/eclipse/configuration/org.eclipse.osgi/bundles/61/data
   [delete] Deleting 
/<>/debian/tmp/usr/lib/eclipse/configuration/org.eclipse.osgi/bundles/101/data/3818263
   [delete] Deleting 
/<>/debian/tmp/usr/lib/eclipse/configuration/org.eclipse.osgi/bundles/101/data/232360089
   [delete] Deleting 
/<>/debian/tmp/usr/lib/eclipse/configuration/org.eclipse.osgi/bundles/101/data/1185816634
   [delete] Deleting 
/<>/debian/tmp/usr/lib/eclipse/configuration/org.eclipse.osgi/bundles/101/data
   [delete] Deleting 
/<>/debian/tmp/usr/lib/eclipse/configuration/org.eclipse.update/history
   [delete] Deleting 
/<>/debian/tmp/usr/lib/eclipse/configuration/org.eclipse.update
[apply] Applied sed to 5 files and 0 directories.
 [echo] /<>/build/eclipse-3.8.1-src/installation
[apply] Applied gunzip to 1 file and 0 directories.
[apply] Applied sed to 1 file and 0 directories.
[apply] Applied gzip to 1 file and 0 directories.
[apply] Applied sed to 3 files and 0 directories.
[mkdir] Created dir: /<>/debian/tmp/etc
 [move] Moving 1 file to /<>/debian/tmp/etc

BUILD SUCCESSFUL
Total time: 1 minute 28 seconds
make[1]: Leaving directory '/<>'
   debian/rules override_dh_install-indep
make[1]: Entering directory '/<>'
dh_install --indep
dh_install: eclipse-jdt missing files 
(usr/share/eclipse/dropins/jdt/plugins/org.eclipse.ant.launching_*.jar), 
aborting
debian/rules:105: recipe for target 'override_dh_install-indep' failed
make[1]: *** [override_dh_install-indep] Error 2
make[1]: Leaving directory '/<>'
debian/rules:6: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep gave error exit 
status 2


Sorry not to have a fix, as I am reporting many bugs similar to
this one. The common hints are:

* If the only architecture-independent packages are dummy 

Bug#757536: marked as done (eclipse: FTBFS with Java 8: Duplicate methods named spliterator with the parameters () and ())

[Debian Bug Tracking System]

Your message dated Wed, 19 Oct 2016 17:40:51 +
with message-id 
and subject line Bug#757536: fixed in eclipse 3.8.1-9
has caused the Debian Bug report #757536,
regarding eclipse: FTBFS with Java 8: Duplicate methods named spliterator with 
the parameters () and ()
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
757536: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757536
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: eclipse
Version: 3.8.1-5.1
Severity: important
User: debian-j...@lists.debian.org
Usertags: openjdk-8-transition

Hi,

During a rebuild of all Java packages in sid with OpenJDK 8,
this package failed to build with the following error:

[mkdir] Created dir: 
/«PKGBUILDDIR»/build/eclipse-3.8.1-src/plugins/org.eclipse.equinox.event/@dot
[javac] Compiling 14 source files to 
/«PKGBUILDDIR»/build/eclipse-3.8.1-src/plugins/org.eclipse.equinox.event/@dot
[javac] javac: invalid target release: jsr14
[javac] Usage: javac  
[javac] use -help for a list of possible options

A fix for this issue has been committed in the Git repository on Alioth,
but another error still breaks the build with Java 8:

 [exec] org.eclipse.osgi error loading hook: 
org.eclipse.core.runtime.internal.adaptor.EclipseLogHook
 [exec] java.lang.Error: Unresolved compilation problem:
 [exec] Duplicate methods named spliterator with the parameters () and 
() are inherited from the types Collection and Iterable
 [exec]
 [exec] at 
org.eclipse.osgi.internal.baseadaptor.ArrayMap.(ArrayMap.java:23)
 [exec] at 
org.eclipse.equinox.log.internal.ExtendedLogReaderServiceFactory.(ExtendedLogReaderServiceFactory.java:53)
 [exec] at 
org.eclipse.equinox.log.internal.LogServiceManager.(LogServiceManager.java:27)
 [exec] at 
org.eclipse.core.runtime.internal.adaptor.EclipseLogHook.(EclipseLogHook.java:71)
 [exec] at 
sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

Note that unlike the similar errors in the eclipse-* packages,
this one is not fixed by upgrading the ecj package to the version 3.10.0.



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: eclipse
Source-Version: 3.8.1-9

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

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 757...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Emmanuel Bourg  (supplier of updated eclipse package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 19 Oct 2016 18:56:11 +0200
Source: eclipse
Binary: eclipse eclipse-jdt eclipse-pde eclipse-platform eclipse-platform-data 
eclipse-rcp libequinox-osgi-java
Architecture: source all amd64
Version: 3.8.1-9
Distribution: unstable
Urgency: medium
Maintainer: Debian Orbital Alignment Team 

Changed-By: Emmanuel Bourg 
Description:
 eclipse- Extensible Tool Platform and Java IDE
 eclipse-jdt - Eclipse Java Development Tools (JDT)
 eclipse-pde - Eclipse Plug-in Development Environment (PDE)
 eclipse-platform - Eclipse platform without development plug-ins
 eclipse-platform-data - Eclipse platform without development plug-ins (data)
 eclipse-rcp - Eclipse Rich Client Platform (RCP)
 libequinox-osgi-java - Equinox OSGi framework
Closes: 743521 757536 759641 770568 806613
Changes:
 eclipse (3.8.1-9) unstable; urgency=medium
 .
   * Team upload.
   * Fixed the build failure with Java 8 (Closes: #757536)
   * Fixed the build failure with dpkg-buildpackage -A (Closes: #806613)
   * Transition to libservlet3.1-java and libtomcat8-java (Closes: #759641)
   * eclipse-jdt no longer recommends sun-java6-jdk
   * Standards-Version updated to 3.9.8
   * Use a secure Vcs-Git URL
   * Removed Andres Mejia from the uploaders (Closes: #743521)
   * Removed Niels Thykier from the uploaders (Closes: #770568)
   * debian/copyright: Updated the Format URI
Checksums-Sha1:
 da04a6dfdf24ef2c55c193b63dc05ee4214a9970 

Processed: Tidy up. Stage three

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 841274 node-define-property
Bug #841274 [src:node-define-property] node-define-property: FTBFS: Error: 
Cannot find module 'wrappy'
Bug reassigned from package 'src:node-define-property' to 
'node-define-property'.
No longer marked as found in versions node-define-property/0.2.5-1.
Ignoring request to alter fixed versions of bug #841274 to the same values 
previously set
> affects 841274 src:node-define-property
Bug #841274 [node-define-property] node-define-property: FTBFS: Error: Cannot 
find module 'wrappy'
Added indication that 841274 affects src:node-define-property
> forcemerge 841274 841321 841322 841323 841324 841325 841326 841327 841328 
> 841329 841330 841331 841332 841333 841334 841335 841336 841337 841338
Bug #841274 [node-define-property] node-define-property: FTBFS: Error: Cannot 
find module 'wrappy'
Bug #841333 [node-define-property] node-isobject: FTBFS (Error: Cannot find 
module wrappy)
Removed indication that 841333 affects src:node-isobject
Added indication that 841333 affects 
node-to-regex-range,node-is-number,node-collection-visit,node-repeat-element,node-extend-shallow,node-is-extendable,node-map-visit,src:node-define-property,node-copy-descriptor,node-has-values,node-is-accessor-descriptor,node-is-descriptor,node-component-emitter,node-isobject
Bug #841327 [node-define-property] node-glob-parent: FTBFS (Error: Cannot find 
module wrappy)
Removed indication that 841327 affects src:node-glob-parent
Added indication that 841327 affects 
node-to-regex-range,node-is-number,node-collection-visit,node-repeat-element,node-extend-shallow,node-is-extendable,node-map-visit,src:node-define-property,node-copy-descriptor,node-has-values,node-is-accessor-descriptor,node-is-descriptor,node-component-emitter,node-isobject
Bug #841322 [node-define-property] node-component-emitter: FTBFS (Error: Cannot 
find module wrappy)
Removed indication that 841322 affects src:node-component-emitter
Added indication that 841322 affects 
node-to-regex-range,node-is-number,node-collection-visit,node-repeat-element,node-extend-shallow,node-is-extendable,node-map-visit,src:node-define-property,node-copy-descriptor,node-has-values,node-is-accessor-descriptor,node-is-descriptor,node-component-emitter,node-isobject
Bug #841324 [node-define-property] node-extend-shallow: FTBFS (Error: Cannot 
find module wrappy)
Removed indication that 841324 affects src:node-extend-shallow
Added indication that 841324 affects 
node-to-regex-range,node-is-number,node-collection-visit,node-repeat-element,node-extend-shallow,node-is-extendable,node-map-visit,src:node-define-property,node-copy-descriptor,node-has-values,node-is-accessor-descriptor,node-is-descriptor,node-component-emitter,node-isobject
Bug #841326 [node-define-property] node-fill-range: FTBFS (Error: Cannot find 
module wrappy)
Removed indication that 841326 affects src:node-fill-range
Added indication that 841326 affects 
node-to-regex-range,node-is-number,node-collection-visit,node-repeat-element,node-extend-shallow,node-is-extendable,node-map-visit,src:node-define-property,node-copy-descriptor,node-has-values,node-is-accessor-descriptor,node-is-descriptor,node-component-emitter,node-isobject
Bug #841332 [node-define-property] node-isexe: FTBFS (Error: Cannot find module 
wrappy)
Removed indication that 841332 affects src:node-isexe
Added indication that 841332 affects 
node-to-regex-range,node-is-number,node-collection-visit,node-repeat-element,node-extend-shallow,node-is-extendable,node-map-visit,src:node-define-property,node-copy-descriptor,node-has-values,node-is-accessor-descriptor,node-is-descriptor,node-component-emitter,node-isobject
Bug #841321 [node-define-property] node-collection-visit: FTBFS (Error: Cannot 
find module wrappy)
Removed indication that 841321 affects src:node-collection-visit
Added indication that 841321 affects 
node-to-regex-range,node-is-number,node-collection-visit,node-repeat-element,node-extend-shallow,node-is-extendable,node-map-visit,src:node-define-property,node-copy-descriptor,node-has-values,node-is-accessor-descriptor,node-is-descriptor,node-component-emitter,node-isobject
Bug #841337 [node-define-property] node-pascalcase: FTBFS (Error: Cannot find 
module wrappy)
Removed indication that 841337 affects src:node-pascalcase
Added indication that 841337 affects 
node-to-regex-range,node-is-number,node-collection-visit,node-repeat-element,node-extend-shallow,node-is-extendable,node-map-visit,src:node-define-property,node-copy-descriptor,node-has-values,node-is-accessor-descriptor,node-is-descriptor,node-component-emitter,node-isobject
Bug #841336 [node-define-property] node-normalize-path: FTBFS (Error: Cannot 
find module wrappy)
Removed indication that 841336 affects src:node-normalize-path
Added indication that 841336 affects 

Processed (with 1 error): Tidy up. Stage two

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forcemerge 841274 841321 841322 841323 841324 841325 841326 841327 841328 
> 841329 841330 841331 841332 841333 841334 841335 841336 841337 841338
Bug #841274 [src:node-define-property] node-define-property: FTBFS: Error: 
Cannot find module 'wrappy'
Unable to merge bugs because:
package of #841336 is 'node-define-property' not 'src:node-define-property'
package of #841329 is 'node-define-property' not 'src:node-define-property'
package of #841324 is 'node-define-property' not 'src:node-define-property'
package of #841326 is 'node-define-property' not 'src:node-define-property'
package of #841337 is 'node-define-property' not 'src:node-define-property'
package of #841321 is 'node-define-property' not 'src:node-define-property'
package of #841331 is 'node-define-property' not 'src:node-define-property'
package of #841330 is 'node-define-property' not 'src:node-define-property'
package of #841333 is 'node-define-property' not 'src:node-define-property'
package of #841332 is 'node-define-property' not 'src:node-define-property'
package of #841323 is 'node-define-property' not 'src:node-define-property'
package of #841327 is 'node-define-property' not 'src:node-define-property'
package of #841328 is 'node-define-property' not 'src:node-define-property'
package of #841334 is 'node-define-property' not 'src:node-define-property'
package of #841335 is 'node-define-property' not 'src:node-define-property'
package of #841322 is 'node-define-property' not 'src:node-define-property'
package of #841325 is 'node-define-property' not 'src:node-define-property'
package of #841338 is 'node-define-property' not 'src:node-define-property'
Failed to forcibly merge 841274: Did not alter merged bugs.

> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
841274: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841274
841321: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841321
841322: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841322
841323: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841323
841324: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841324
841325: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841325
841326: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841326
841327: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841327
841328: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841328
841329: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841329
841330: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841330
841331: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841331
841332: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841332
841333: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841333
841334: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841334
841335: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841335
841336: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841336
841337: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841337
841338: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841338
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Tidy up. Stage one

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 841321 node-define-property
Bug #841321 [src:node-collection-visit] node-collection-visit: FTBFS (Error: 
Cannot find module wrappy)
Bug reassigned from package 'src:node-collection-visit' to 
'node-define-property'.
No longer marked as found in versions node-collection-visit/0.2.3-1.
Ignoring request to alter fixed versions of bug #841321 to the same values 
previously set
> reassign 841322 node-define-property
Bug #841322 [src:node-component-emitter] node-component-emitter: FTBFS (Error: 
Cannot find module wrappy)
Bug reassigned from package 'src:node-component-emitter' to 
'node-define-property'.
No longer marked as found in versions node-component-emitter/1.2.1-1.
Ignoring request to alter fixed versions of bug #841322 to the same values 
previously set
> reassign 841323 node-define-property
Bug #841323 [src:node-copy-descriptor] node-copy-descriptor: FTBFS (Error: 
Cannot find module wrappy)
Bug reassigned from package 'src:node-copy-descriptor' to 
'node-define-property'.
No longer marked as found in versions node-copy-descriptor/0.1.1-1.
Ignoring request to alter fixed versions of bug #841323 to the same values 
previously set
> reassign 841324 node-define-property
Bug #841324 [src:node-extend-shallow] node-extend-shallow: FTBFS (Error: Cannot 
find module wrappy)
Bug reassigned from package 'src:node-extend-shallow' to 'node-define-property'.
No longer marked as found in versions node-extend-shallow/2.0.1-1.
Ignoring request to alter fixed versions of bug #841324 to the same values 
previously set
> reassign 841325 node-define-property
Bug #841325 [src:node-filename-regex] node-filename-regex: FTBFS (Error: Cannot 
find module wrappy)
Bug reassigned from package 'src:node-filename-regex' to 'node-define-property'.
No longer marked as found in versions node-filename-regex/2.0.0-1.
Ignoring request to alter fixed versions of bug #841325 to the same values 
previously set
> reassign 841326 node-define-property
Bug #841326 [src:node-fill-range] node-fill-range: FTBFS (Error: Cannot find 
module wrappy)
Bug reassigned from package 'src:node-fill-range' to 'node-define-property'.
No longer marked as found in versions node-fill-range/3.0.3-1.
Ignoring request to alter fixed versions of bug #841326 to the same values 
previously set
> reassign 841327 node-define-property
Bug #841327 [src:node-glob-parent] node-glob-parent: FTBFS (Error: Cannot find 
module wrappy)
Bug reassigned from package 'src:node-glob-parent' to 'node-define-property'.
No longer marked as found in versions node-glob-parent/3.0.0-1.
Ignoring request to alter fixed versions of bug #841327 to the same values 
previously set
> reassign 841328 node-define-property
Bug #841328 [src:node-has-values] node-has-values: FTBFS (Error: Cannot find 
module wrappy)
Bug reassigned from package 'src:node-has-values' to 'node-define-property'.
No longer marked as found in versions node-has-values/0.1.4-1.
Ignoring request to alter fixed versions of bug #841328 to the same values 
previously set
> reassign 841329 node-define-property
Bug #841329 [src:node-hosted-git-info] node-hosted-git-info: FTBFS (Error: 
Cannot find module wrappy)
Bug reassigned from package 'src:node-hosted-git-info' to 
'node-define-property'.
No longer marked as found in versions node-hosted-git-info/2.1.5-1.
Ignoring request to alter fixed versions of bug #841329 to the same values 
previously set
> reassign 841330 node-define-property
Bug #841330 [src:node-is-dotfile] node-is-dotfile: FTBFS (Error: Cannot find 
module wrappy)
Bug reassigned from package 'src:node-is-dotfile' to 'node-define-property'.
No longer marked as found in versions node-is-dotfile/1.0.2-1.
Ignoring request to alter fixed versions of bug #841330 to the same values 
previously set
> reassign 841331 node-define-property
Bug #841331 [src:node-is-primitive] node-is-primitive: FTBFS (Error: Cannot 
find module wrappy)
Bug reassigned from package 'src:node-is-primitive' to 'node-define-property'.
No longer marked as found in versions node-is-primitive/2.0.0-1.
Ignoring request to alter fixed versions of bug #841331 to the same values 
previously set
> reassign 841332 node-define-property
Bug #841332 [src:node-isexe] node-isexe: FTBFS (Error: Cannot find module 
wrappy)
Bug reassigned from package 'src:node-isexe' to 'node-define-property'.
No longer marked as found in versions node-isexe/1.1.2-1.
Ignoring request to alter fixed versions of bug #841332 to the same values 
previously set
> reassign 841333 node-define-property
Bug #841333 [src:node-isobject] node-isobject: FTBFS (Error: Cannot find module 
wrappy)
Bug reassigned from package 'src:node-isobject' to 'node-define-property'.
No longer marked as found in versions node-isobject/2.1.0-1.
Ignoring request to alter fixed versions of bug #841333 to the same values 
previously set
> reassign 841334 node-define-property
Bug #841334 [src:node-map-cache] node-map-cache: FTBFS (Error: Cannot find 

Bug#841274: node-define-property: FTBFS: Error: Cannot find module 'wrappy'

[Chris Lamb]

Santiago Vila wrote:

> Thanks and sorry for the noise.

Really don't worry about it; was just an FYI. :)

> Assuming that this one is the real cause for all the bugs I reported,
> I'm going to merge them all into this one.

Awesome - great work.


Regards,

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

Bug#841274: node-define-property: FTBFS: Error: Cannot find module 'wrappy'

[Santiago Vila]

On Wed, 19 Oct 2016, Chris Lamb wrote:

> affects 841274 node-is-accessor-descriptor node-is-descriptor 
> node-is-extendable node-is-number node-to-regex-range
> thanks

Hi.

The quoted text above is the reason I didn't see any of those bugs.

I was looking here:

https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=node-collection-visit

When a package FTBFS, the bug is really in the source package (src:whatever)
because the binary packages, being it a FTBFS bug, do not even exist.

Assuming that this one is the real cause for all the bugs I reported,
I'm going to merge them all into this one.

Thanks and sorry for the noise.

Bug#835752: marked as done (dolphin: FTBFS: dh_install: missing files, aborting)

[Debian Bug Tracking System]

Your message dated Wed, 19 Oct 2016 18:53:04 +0200
with message-id <20161019165304.bgtsfayewrtnc...@gnuservers.com.ar>
and subject line Re: Bug#835752: dolphin: FTBFS: dh_install: missing files, 
aborting
has caused the Debian Bug report #835752,
regarding dolphin: FTBFS: dh_install: missing files, aborting
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
835752: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835752
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dolphin
Version: 4:16.04.2-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 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[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
> make[3]: Nothing to be done for 'preinstall'.
> make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
> Install the project...
> /usr/bin/cmake -P cmake_install.cmake
> -- Install configuration: "Debian"
> -- Installing: 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/cmake/DolphinVcs/DolphinVcsConfig.cmake
> -- Installing: 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/cmake/DolphinVcs/DolphinVcsConfigVersion.cmake
> -- Installing: 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/cmake/DolphinVcs/DolphinVcsTargets.cmake
> -- Installing: 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/cmake/DolphinVcs/DolphinVcsTargets-debian.cmake
> -- Installing: 
> /<>/debian/tmp/usr/include/Dolphin/dolphinvcs_version.h
> -- Installing: 
> /<>/debian/tmp/usr/share/dbus-1/services/org.kde.dolphin.FileManager1.service
> -- Installing: 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libdolphinvcs.so.5.0.0
> -- Installing: 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libdolphinvcs.so.5
> -- Installing: 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libdolphinvcs.so
> -- Installing: 
> /<>/debian/tmp/usr/share/kservicetypes5/fileviewversioncontrolplugin.desktop
> -- Installing: /<>/debian/tmp/usr/include/dolphin_export.h
> -- Installing: 
> /<>/debian/tmp/usr/include/Dolphin/KVersionControlPlugin
> -- Installing: 
> /<>/debian/tmp/usr/include/Dolphin/kversioncontrolplugin.h
> -- Installing: 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libdolphinprivate.so.5.0.0
> -- Installing: 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libdolphinprivate.so.5
> -- Set runtime path of 
> "/<>/debian/tmp/usr/lib/x86_64-linux-gnu/libdolphinprivate.so.5.0.0"
>  to ""
> -- Installing: 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/qt5/plugins/dolphinpart.so
> -- Set runtime path of 
> "/<>/debian/tmp/usr/lib/x86_64-linux-gnu/qt5/plugins/dolphinpart.so"
>  to ""
> -- Installing: 
> /<>/debian/tmp/usr/share/kxmlgui5/dolphinpart/dolphinpart.rc
> -- Installing: 
> /<>/debian/tmp/usr/share/kservices5/dolphinpart.desktop
> -- Installing: 
> /<>/debian/tmp/usr/share/dbus-1/interfaces/org.freedesktop.FileManager1.xml
> -- Installing: 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libkdeinit5_dolphin.so
> -- Set runtime path of 
> "/<>/debian/tmp/usr/lib/x86_64-linux-gnu/libkdeinit5_dolphin.so" 
> to ""
> -- Installing: /<>/debian/tmp/usr/bin/dolphin
> -- Set runtime path of "/<>/debian/tmp/usr/bin/dolphin" to ""
> -- Installing: 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/qt5/plugins/kcm_dolphinviewmodes.so
> -- Set runtime path of 
> "/<>/debian/tmp/usr/lib/x86_64-linux-gnu/qt5/plugins/kcm_dolphinviewmodes.so"
>  to ""
> -- Installing: 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/qt5/plugins/kcm_dolphinnavigation.so
> -- Set runtime path of 
> "/<>/debian/tmp/usr/lib/x86_64-linux-gnu/qt5/plugins/kcm_dolphinnavigation.so"
>  to ""
> -- Installing: 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/qt5/plugins/kcm_dolphinservices.so
> -- Set runtime path of 
> "/<>/debian/tmp/usr/lib/x86_64-linux-gnu/qt5/plugins/kcm_dolphinservices.so"
>  to ""
> -- Installing: 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/qt5/plugins/kcm_dolphingeneral.so
> -- Set runtime path of 
> "/<>/debian/tmp/usr/lib/x86_64-linux-gnu/qt5/plugins/kcm_dolphingeneral.so"
>  to ""
> -- Installing: 
> /<>/debian/tmp/usr/share/applications/org.kde.dolphin.desktop
> -- Installing: 
> /<>/debian/tmp/usr/share/config.kcfg/dolphin_directoryviewpropertysettings.kcfg
> -- Installing: 
> /<>/debian/tmp/usr/share/config.kcfg/dolphin_generalsettings.kcfg
> -- Installing: 
> /<>/debian/tmp/usr/share/config.kcfg/dolphin_compactmodesettings.kcfg
> -- Installing: 
> /<>/debian/tmp/usr/share/config.kcfg/dolphin_iconsmodesettings.kcfg
> -- Installing: 
> /<>/debian/tmp/usr/share/config.kcfg/dolphin_detailsmodesettings.kcfg
> -- 

Bug#839791: marked as done (qtcreator: builds with clang support on armel)

[Debian Bug Tracking System]

Your message dated Wed, 19 Oct 2016 16:55:33 +
with message-id 
and subject line Bug#839791: fixed in qtcreator 4.1.0-2
has caused the Debian Bug report #839791,
regarding qtcreator: builds with clang support on armel
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
839791: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839791
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qtcreator
Version: 4.1.0-1
Severity: serious

Hi!

qtcreator builds with LLVM 3.8 on armel, however LLVM 3.8 is not
available there. (Well, there is an old version still in the archive,
built from a snapshot from llvm-toolchain-snapshot, which hasn't been
removed yet, that will happen soon in #839033.

Note this is blocking testing migration:

qtcreator (4.0.3-1 to 4.1.0-1)
Maintainer: Debian Qt/KDE Maintainers
26 days old (needed 5 days)
Invalidated by dependency
Depends: qtcreator llvm-toolchain-snapshot (not considered)
Not considered

So please, drop the clang support on armel, so that your package can migrate
and so that we can drop the old llvm binaries.

FWIW, I'm doing the same thing in gnome-builder.

Thanks,
Emilio

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (800, 'unstable'), (700, 'experimental'), (650, 'testing'), (500, 
'unstable-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: qtcreator
Source-Version: 4.1.0-2

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

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 839...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Lisandro Damián Nicanor Pérez Meyer  (supplier of updated 
qtcreator package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 19 Oct 2016 11:23:57 -0300
Source: qtcreator
Binary: qtcreator qtcreator-data qtcreator-doc
Architecture: source
Version: 4.1.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers 
Changed-By: Lisandro Damián Nicanor Pérez Meyer 
Description:
 qtcreator  - integrated development environment (IDE) for Qt
 qtcreator-data - application data for Qt Creator IDE
 qtcreator-doc - documentation for Qt Creator IDE
Closes: 839791
Changes:
 qtcreator (4.1.0-2) unstable; urgency=medium
 .
   * Do not build clang support on armel (Closes: #839791). Thanks Emilio for
 the bug!
   * Switch to libclang-dev, which currently depends on libclang-3.8-dev.
 Listing both versions of libclang-3.*-dev is futile as buildds will
 only consider the first one.
Checksums-Sha1:
 2e1f2bbbc5afc545ff2a03fd9373cf3324132e33 2797 qtcreator_4.1.0-2.dsc
 50334ac9bdc5e044f2327e90f97e2924b609fd62 20316 qtcreator_4.1.0-2.debian.tar.xz
Checksums-Sha256:
 c0b70bdb6801e3180ec683ac5e2589847a12f75725a4f3cec19ca6a317245ce1 2797 
qtcreator_4.1.0-2.dsc
 9200042df01e945d6dce0c9be6e4e42771b51beb111e4dd5705b78ccf5412d8e 20316 
qtcreator_4.1.0-2.debian.tar.xz
Files:
 c1ef0c6372a27efe0e6b032249890ac0 2797 devel optional qtcreator_4.1.0-2.dsc
 4f568299b50ab45ef63042dbd661e919 20316 devel optional 
qtcreator_4.1.0-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIxBAEBCAAbBQJYB4SlFBxsaXNhbmRyb0BkZWJpYW4ub3JnAAoJEKtkX0BihqfQ
IDUQAJJG6xuBxpXS/kkjXZAXbMOJAS/+SOjkW/cMJbsSs7/gWrMye40+eTUy5B43
wbIi7x05dtnfsN4nfh+6zr7BR4T+RRoicHIOVsdWelMUa9LDd7rvGzganuGliyV1
uvFBmmYl9mh4vN/D8QPijeUn03wZkeX3C/FIc+sse2TcbU2Rq4QZkXU4wL5Cnugl
NQ7275e7kXQIAuXQIYjFlSmTSFA6qhTwmQNs8V/qo5qbIcW+LscFqgr8a3fMm2KY
AqV2I9P+LJf8okp4naJu37mBYw/rwToDZFr5DcsJB7ZR2WgmsGTorXqYKiPBg1Xs
QKom2QX/Ocvq8VXVHvYV9Rxg03oT4cbkINj8bjgnnHtJ5sdGSQmzlj+bYFG80rQd
8aeXuLMMftDMLEsShbq6S16UrzCQ9ZFmpv3znhczmmNC7Lk6Bbz9tG2OQA+jzfX+
sWyLtGLIYUbRiWehj0I+qFvFCO6CtSJTowzfKxWn7/uagcU2Epr5+mKRvTxzeRGY

Bug#835726: marked as done (kate: FTBFS: dh_install: missing files, aborting)

[Debian Bug Tracking System]

Your message dated Wed, 19 Oct 2016 18:55:50 +0200
with message-id <20161019165550.bzcl3j3dmgtb6...@gnuservers.com.ar>
and subject line Re: Bug#835726: kate: FTBFS: dh_install: missing files, 
aborting
has caused the Debian Bug report #835726,
regarding kate: FTBFS: dh_install: missing files, aborting
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
835726: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835726
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kate
Version: 4:16.04.2-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 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[4]: Entering directory '/<>/obj-x86_64-linux-gnu'
> make[4]: Nothing to be done for 'preinstall'.
> make[4]: Leaving directory '/<>/obj-x86_64-linux-gnu'
> Install the project...
> /usr/bin/cmake -P cmake_install.cmake
> -- Install configuration: "Debian"
> -- Installing: /<>/debian/tmp/usr/bin/kwrite
> -- Installing: 
> /<>/debian/tmp/usr/share/applications/org.kde.kwrite.desktop
> -- Installing: 
> /<>/debian/tmp/usr/share/metainfo/org.kde.kwrite.appdata.xml
> -- Installing: 
> /<>/debian/tmp/usr/share/icons/hicolor/16x16/apps/kwrite.png
> -- Installing: 
> /<>/debian/tmp/usr/share/icons/hicolor/22x22/apps/kwrite.png
> -- Installing: 
> /<>/debian/tmp/usr/share/icons/hicolor/32x32/apps/kwrite.png
> -- Installing: 
> /<>/debian/tmp/usr/share/icons/hicolor/48x48/apps/kwrite.png
> -- Installing: 
> /<>/debian/tmp/usr/share/icons/hicolor/64x64/apps/kwrite.png
> -- Installing: 
> /<>/debian/tmp/usr/share/icons/hicolor/128x128/apps/kwrite.png
> -- Installing: 
> /<>/debian/tmp/usr/share/icons/hicolor/scalable/apps/kwrite.svgz
> -- Installing: /<>/debian/tmp/usr/bin/kate
> -- Installing: 
> /<>/debian/tmp/usr/share/applications/org.kde.kate.desktop
> -- Installing: 
> /<>/debian/tmp/usr/share/metainfo/org.kde.kate.appdata.xml
> -- Installing: 
> /<>/debian/tmp/usr/share/icons/hicolor/16x16/apps/kate.png
> -- Installing: 
> /<>/debian/tmp/usr/share/icons/hicolor/22x22/apps/kate.png
> -- Installing: 
> /<>/debian/tmp/usr/share/icons/hicolor/32x32/apps/kate.png
> -- Installing: 
> /<>/debian/tmp/usr/share/icons/hicolor/48x48/apps/kate.png
> -- Installing: 
> /<>/debian/tmp/usr/share/icons/hicolor/64x64/apps/kate.png
> -- Installing: 
> /<>/debian/tmp/usr/share/icons/hicolor/128x128/apps/kate.png
> -- Installing: 
> /<>/debian/tmp/usr/share/icons/hicolor/scalable/apps/kate.svgz
> -- Installing: 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/qt5/plugins/ktexteditor/katefiletreeplugin.so
> -- Installing: 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/qt5/plugins/ktexteditor/katesearchplugin.so
> -- Installing: 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/qt5/plugins/ktexteditor/tabswitcherplugin.so
> -- Installing: 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/qt5/plugins/ktexteditor/katectagsplugin.so
> -- Installing: 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/qt5/plugins/ktexteditor/katebacktracebrowserplugin.so
> -- Installing: 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/qt5/plugins/ktexteditor/katefilebrowserplugin.so
> -- Installing: 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/qt5/plugins/ktexteditor/katexmltoolsplugin.so
> -- Installing: 
> /<>/debian/tmp/usr/share/kxmlgui5/katexmltools/ui.rc
> -- Installing: 
> /<>/debian/tmp/usr/share/katexmltools/html4-loose.dtd.xml
> -- Installing: 
> /<>/debian/tmp/usr/share/katexmltools/html4-strict.dtd.xml
> -- Installing: 
> /<>/debian/tmp/usr/share/katexmltools/kde-docbook.dtd.xml
> -- Installing: 
> /<>/debian/tmp/usr/share/katexmltools/simplify_dtd.xsl
> -- Installing: 
> /<>/debian/tmp/usr/share/katexmltools/xhtml1-frameset.dtd.xml
> -- Installing: 
> /<>/debian/tmp/usr/share/katexmltools/xhtml1-strict.dtd.xml
> -- Installing: 
> /<>/debian/tmp/usr/share/katexmltools/xhtml1-transitional.dtd.xml
> -- Installing: 
> /<>/debian/tmp/usr/share/katexmltools/xslt-1.0.dtd.xml
> -- Installing: 
> /<>/debian/tmp/usr/share/katexmltools/testcases.xml
> -- Installing: 
> /<>/debian/tmp/usr/share/katexmltools/language.dtd.xml
> -- Installing: 
> /<>/debian/tmp/usr/share/katexmltools/kpartgui.dtd.xml
> -- Installing: /<>/debian/tmp/usr/share/katexmltools/kcfg.dtd.xml
> -- Installing: 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/qt5/plugins/ktexteditor/kateopenheaderplugin.so
> -- Installing: 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/qt5/plugins/ktexteditor/kategdbplugin.so
> -- Installing: 
> 

Bug#840425: marked as done (mkosi: FTBFS when built with dpkg-buildpackage -A (debian/mkosi.1: No such file or directory))

[Debian Bug Tracking System]

Your message dated Wed, 19 Oct 2016 16:51:31 +
with message-id 
and subject line Bug#840425: fixed in mkosi 0~20161012-1
has caused the Debian Bug report #840425,
regarding mkosi: FTBFS when built with dpkg-buildpackage -A (debian/mkosi.1: No 
such file or directory)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
840425: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840425
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:mkosi
Version: 0~20161004-1
Severity: serious
Tags: patch

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --with python3 --buildsystem=pybuild
   dh_testdir -i -O--buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_autoreconf -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:184: python3.5 setup.py config 
running config
   dh_auto_build -i -O--buildsystem=pybuild
I: pybuild base:184: /usr/bin/python3 setup.py build 
running build
running build_scripts
creating build
creating build/scripts-3.5
copying and adjusting mkosi -> build/scripts-3.5
changing mode of build/scripts-3.5/mkosi from 664 to 775
   dh_auto_test -i -O--buildsystem=pybuild
I: pybuild base:184: cd '/<>/.pybuild/pythonX.Y_3.5/build'; 
python3.5 -m unittest discover -v 

--
Ran 0 tests in 0.000s

OK
 fakeroot debian/rules binary-indep
dh binary-indep --with python3 --buildsystem=pybuild
   dh_testroot -i -O--buildsystem=pybuild
   dh_prep -i -O--buildsystem=pybuild
   dh_auto_install -i -O--buildsystem=pybuild
I: pybuild base:184: /usr/bin/python3 setup.py install --root 
'/<>/debian/mkosi' 
running install
running build
running build_scripts
running install_egg_info
running egg_info
creating mkosi.egg-info
writing mkosi.egg-info/PKG-INFO
writing dependency_links to mkosi.egg-info/dependency_links.txt
writing top-level names to mkosi.egg-info/top_level.txt
writing manifest file 'mkosi.egg-info/SOURCES.txt'
reading manifest file 'mkosi.egg-info/SOURCES.txt'
writing manifest file 'mkosi.egg-info/SOURCES.txt'
Copying mkosi.egg-info to 
/<>/debian/mkosi/usr/lib/python3.5/dist-packages/mkosi-1.egg-info
Skipping SOURCES.txt
running install_scripts
creating /<>/debian/mkosi/usr/bin
copying build/scripts-3.5/mkosi -> /<>/debian/mkosi/usr/bin
changing mode of /<>/debian/mkosi/usr/bin/mkosi to 775
   dh_installdocs -i -O--buildsystem=pybuild
   dh_installchangelogs -i -O--buildsystem=pybuild
   dh_installman -i -O--buildsystem=pybuild
debian/mkosi.1: No such file or directory at /usr/bin/dh_installman line 131.
debian/rules:10: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep gave error exit 
status 2


This happens because there is a "build" target but there is not a "build-indep" 
target,
so the build paths for "dpkg-buildpackage" and "dpkg-buildpackage -A" are 
different.

I suggest the patch below to fix this. It makes debian/rules a little bit 
shorter
and maybe a little bit more dh-style.

I would also suggest that you try source-only uploads (even for
Arch:all packages like this one). That way, we would get pretty
official build logs here:

https://buildd.debian.org/status/package.php?p=mkosi

and we would also detect bugs like this one before they propagate to testing.

Thanks.

--- a/debian/rules
+++ b/debian/rules
@@ -9,15 +9,10 @@ export PYBUILD_NAME=mkosi
 %:
dh $@ --with python3 --buildsystem=pybuild
 
-# need explicit target to be able to mark as phony
-build: debian/mkosi.1
-   dh $@ --with python3 --buildsystem=pybuild
-
-debian/mkosi.1:
+override_dh_auto_build:
+   dh_auto_build
help2man --name "Create legacy-free OS images" \
--version-string "mkosi $(DEB_VERSION_UPSTREAM)" \
--no-info \
-o debian/mkosi.1 \
./mkosi
-
-.PHONY: build
--- End Message ---
--- Begin Message ---
Source: mkosi
Source-Version: 0~20161012-1

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

A summary of the changes between this version and the previous 

Bug#841338: node-repeat-element: FTBFS (Error: Cannot find module wrappy)

[Santiago Vila]

On Wed, Oct 19, 2016 at 05:17:20PM +0100, Chris Lamb wrote:
> Hi,
> 
> > node-repeat-element: FTBFS (Error: Cannot find module wrappy)
> 
> This (and others) appears to be a duplicate of #841274. I used
> "affects" there, perhaps incorrectly, but at least it avoids
> duplicates.

Do you mean node-define-property is in the build-depends for all the
bugs I've just reported?

(I don't see that's the case. Maybe it happens transitively?)

I'm more than willing to merge all the bugs and save the maintainers
the work, but I'd like to be sure that they are indeed the same bug
and not just a missing build-depends in each and every of them.

Thanks.

Bug#841307: marked as done (docker-compose: Wrong dependency version for python-docker)

[Debian Bug Tracking System]

Your message dated Wed, 19 Oct 2016 16:37:08 +
with message-id 
and subject line Bug#841307: fixed in docker-compose 1.8.0-2
has caused the Debian Bug report #841307,
regarding docker-compose: Wrong dependency version for python-docker
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
841307: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841307
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: docker-compose
Version: 1.8.0-1
Severity: important
Tags: patch

Dear Maintainer,

the dependency for docker-compose 1.8 on python-docker (>= 1.3.0) seems to be
wrong. Instead it needs version >= 1.8.0 .

I installed docker-compose and got an error while trying it. I searched for the
error and got to [1], where someone had the same error and the reason was, that
docker-compose needed version 1.8.0 of docker-py.

So I tried and installed the current version of python-docker package from Sid
(which is 1.9.0-1) and now the error is gone.

Yours
  David


[1] https://github.com/docker/compose/issues/3342



-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

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

Versions of packages docker-compose depends on:
ii  python-cached-property  1.3.0-2
ii  python-docker   1.9.0-1
ii  python-dockerpty0.4.1-1
ii  python-docopt   0.6.2-1
ii  python-enum34   1.1.6-1
ii  python-jsonschema   2.5.1-6
ii  python-requests 2.11.1-1
ii  python-six  1.10.0-3
ii  python-texttable0.8.4-2
ii  python-websocket0.37.0-2
ii  python-yaml 3.12-1
pn  python:any  

Versions of packages docker-compose recommends:
pn  docker.io  

docker-compose suggests no packages.
--- End Message ---
--- Begin Message ---
Source: docker-compose
Source-Version: 1.8.0-2

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

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 841...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Felipe Sateler  (supplier of updated docker-compose 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 19 Oct 2016 11:26:05 -0300
Source: docker-compose
Binary: docker-compose
Architecture: source
Version: 1.8.0-2
Distribution: unstable
Urgency: medium
Maintainer: Felipe Sateler 
Changed-By: Felipe Sateler 
Description:
 docker-compose - Punctual, lightweight development environments using Docker
Closes: 841307
Changes:
 docker-compose (1.8.0-2) unstable; urgency=medium
 .
   * Also Bump runtime dependencies of python-docker and python-dockerpty
 Closes: #841307
Checksums-Sha1:
 0107a6e16f7ef86736d27bf51cd072c533106ad3 2270 docker-compose_1.8.0-2.dsc
 29700ca73b205da14737e46a2293699e9ff6d7da 5560 
docker-compose_1.8.0-2.debian.tar.xz
Checksums-Sha256:
 4ba465cb510e37d8e36d78928110c1044d24d07d0a53b6c2b900acad51508f2b 2270 
docker-compose_1.8.0-2.dsc
 bf2f700356ca6c74db213ffc1de90b874b30b953faa873c7e5412c5a0eb56cfe 5560 
docker-compose_1.8.0-2.debian.tar.xz
Files:
 e35a6096b8164f872f8a68fbb0a3b52d 2270 admin optional docker-compose_1.8.0-2.dsc
 9f99e2157e1e3daec71d01fb024f5109 5560 admin optional 
docker-compose_1.8.0-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIxBAEBCAAbBQJYB4PeFBxmc2F0ZWxlckBkZWJpYW4ub3JnAAoJEKO6uuJAjdbP
JfkP/03L4Zj/QDemBQJFTNCaeMseXQDlZFU4wCFyD00dAnuUv5kH1aGOqIKcB3YJ
LIxWP/N2x7ibZSNHLt0KSoPEFA5szDmeIKGqHYBoGwLo2+XFYTtTgRHQW6hmLdxE
57eWgNwR+802TeJ3s0DhqJCDlXuu1Eklgw9aKx1Qwv0R/K8joTzrnbqYL5v/SM+6
uTWV7e7Tn7Etr817v8g/urjLAVLA2ZbEAE8Cr3j7g6+hC8hTVZGp2OiDNzrSbTTK
Pm+nF06oYoi8r8WxFEBOaeIi3btNahVoARjl1Ql8JY5jBeCzmF/iFFOthslslybN
qcAUIpIfgIWOCPyF1VQSvPbhLPGVkCN7OdQkydN5U0SaLC5hk8aAmeERpQgnaqb0
kXpQCdqCr7ueHKL4+aXJmxKb0mMNHd9hFMORqF6ZaHFiv2qhvLoHO/ILp2b0QJR9

Bug#841343: rakudo: FTBFS on arm64, powerpc and ppc64 - testsuite errors

[James Cowgill]

Source: rakudo
Version: 2016.09-2
Severity: serious
Tags: sid stretch

Hi,

rakudo FTBFS on arm64, powerpc and ppc64 with errors in the testsuite.

arm64 times out during the 't/04-nativecall/02-simple-args.t' test.

For powerpc the errors are:
t/04-nativecall/01-argless.t . ok
t/04-nativecall/02-simple-args.t . ok
t/04-nativecall/03-simple-returns.t ..
Dubious, test returned 4 (wstat 1024, 0x400)
Failed 4/11 subtests
t/04-nativecall/04-pointers.t  ok
t/04-nativecall/05-arrays.t .. ok
t/04-nativecall/06-struct.t .. ok
t/04-nativecall/07-writebarrier.t  ok
t/04-nativecall/08-callbacks.t ... ok
t/04-nativecall/09-nativecast.t .. ok
t/04-nativecall/10-cglobals.t  ok
t/04-nativecall/11-cpp.t . ok
t/04-nativecall/12-sizeof.t .. ok
t/04-nativecall/13-cpp-mangling.t  ok
t/04-nativecall/13-union.t ... ok
t/04-nativecall/14-rw-attrs.t 
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/16 subtests
t/04-nativecall/15-rw-args.t .
Dubious, test returned 4 (wstat 1024, 0x400)
Failed 4/22 subtests
t/04-nativecall/16-rt125408.t  ok
t/04-nativecall/16-rt125729.t  ok
t/04-nativecall/17-libnames.t  ok
t/04-nativecall/18-routine-sig-sanity.t .. ok
t/04-nativecall/19-function-pointers.t ... ok

Test Summary Report
---
t/04-nativecall/03-simple-returns.t(Wstat: 1024 Tests: 11 Failed: 4)
  Failed tests:  2-3, 9-10
  Non-zero exit status: 4
t/04-nativecall/14-rw-attrs.t  (Wstat: 256 Tests: 16 Failed: 1)
  Failed test:  15
  Non-zero exit status: 1
t/04-nativecall/15-rw-args.t   (Wstat: 1024 Tests: 22 Failed: 4)
  Failed tests:  2, 4, 14, 16
  Non-zero exit status: 4
Files=45, Tests=600, 139 wallclock secs ( 0.30 usr  0.06 sys + 136.86
cusr  1.64 csys = 138.86 CPU)
Result: FAIL

The ppc64 errors are all in the nativecall tests as well.

Full build logs:
https://buildd.debian.org/status/package.php?p=rakudo

Thanks,
James



signature.asc
Description: OpenPGP digital signature

Bug#841341: bd "Bad substitution" if /bin/sh is not bash

[Gerardo Martin Chaves]

Package: bd
Version: 1.01-1
Severity: grave
Tags: patch
Justification: renders package unusable

bd fails if /bin/sh is not bash on line 39

elif [ "${@: -1}" = -v ]



-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'stable-updates'), (500, 'unstable'), 
(500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

-- no debconf information
*** bd.orig	2016-10-19 13:22:02.361683645 -0300
--- bd	2016-10-19 13:22:18.265769346 -0300
***
*** 36,42 
  if [ $# -eq 0 ]
  then
usage_error
! elif [ "${@: -1}" = -v ]
  then
usage_error
  else
--- 36,42 
  if [ $# -eq 0 ]
  then
usage_error
! elif [ "${@}" = -v -o "${@}" = "" ]
  then
usage_error
  else

Bug#841342: zshdb: FTBFS under some locales (eg. fr_CH.UTF-8)

[Chris Lamb]

Source: zshdb
Version: 0.92-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs locale
Tags: patch
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org


Dear Maintainer,

zshdb fails to build from source in unstable/amd64 under some
locales (eg. LANG="fr_CH.UTF-8").

The code already tries to work around this:

  54 # set the constants readonly
  55 shunit_constants_=`set |grep '^__SHUNIT_' |cut -d= -f1`
  56 echo "${shunit_constants_}" |grep '^Binary file' >/dev/null && \
  57 shunit_constants_=`set |grep -a '^__SHUNIT_' |cut -d= -f1`

… but this doesn't work if the "Binary file" message is in, say, French :)

Changing this:

  - shunit_constants_=`set |grep '^__SHUNIT_' |cut -d= -f1`
  + shunit_constants_=`set |LC_ALL=C grep '^__SHUNIT_' |cut -d= -f1`

… makes this appear to work, but then you get other errors:

--- /tmp/setshow-filtered.check 2016-10-19 18:22:06.324491603 +0200
+++ zshdb-0.92/test/data/setshow.right  2016-07-06 18:47:42.0 +0200
@@ -1,4 +1,3 @@
-** pas un tty is not reputed to be a tty.
 (dbg-test2.sh:6):
 fn1 () { echo "fn1 here" x=5 fn3 }

etc. etc.

One solution (attached) is to simply set LC_ALL=C when running the
tests, but that suggests it would still fail at runtime and we are
just masking that issue? I would speak to upstream.

The full build log is attached.


Regards,

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


zshdb.0.92-1.unstable.amd64.log.txt.gz
Description: Binary data
diff --git a/debian/rules b/debian/rules
index 5639f0e..a3b5d33 100755
--- a/debian/rules
+++ b/debian/rules
@@ -11,5 +11,5 @@ override_dh_auto_test:
# The tests make use of things like the history file, they need a dummy
# home directory.
mkdir test_homedir
-   HOME=$(shell pwd)/test_homedir dh_auto_test
+   LC_ALL=C HOME=$(shell pwd)/test_homedir dh_auto_test
rm -rf test_homedir

Bug#841338: node-repeat-element: FTBFS (Error: Cannot find module wrappy)

[Chris Lamb]

Hi,

> node-repeat-element: FTBFS (Error: Cannot find module wrappy)

This (and others) appears to be a duplicate of #841274. I used
"affects" there, perhaps incorrectly, but at least it avoids
duplicates.


Regards,

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

Bug#841316: gcc: the last 6.2.0-7 broke the virtualbox build

[Matthias Klose]

clone 841316 -1
reassign -1 src:virtualbox
retitle -1 invalid code in virtualbox sources
severity 841316 important
forwarded 841316 https://gcc.gnu.org/PR78039
forcemerge 841292 841316
thanks

This code will be rejected with GCC 7; there is still discussion upstream how
much to revert in this backport to GCC 6.

Processed (with 1 error): Re: Bug#841316: gcc: the last 6.2.0-7 broke the virtualbox build

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> clone 841316 -1
Bug #841316 [src:gcc-6] gcc: the last 6.2.0-7 broke the virtualbox build
Bug 841316 cloned as bug 841340
> reassign -1 src:virtualbox
Bug #841340 [src:gcc-6] gcc: the last 6.2.0-7 broke the virtualbox build
Bug reassigned from package 'src:gcc-6' to 'src:virtualbox'.
Ignoring request to alter found versions of bug #841340 to the same values 
previously set
Ignoring request to alter fixed versions of bug #841340 to the same values 
previously set
> retitle -1 invalid code in virtualbox sources
Bug #841340 [src:virtualbox] gcc: the last 6.2.0-7 broke the virtualbox build
Changed Bug title to 'invalid code in virtualbox sources' from 'gcc: the last 
6.2.0-7 broke the virtualbox build'.
> severity 841316 important
Bug #841316 [src:gcc-6] gcc: the last 6.2.0-7 broke the virtualbox build
Severity set to 'important' from 'serious'
> forwarded 841316 https://gcc.gnu.org/PR78039
Bug #841316 [src:gcc-6] gcc: the last 6.2.0-7 broke the virtualbox build
Set Bug forwarded-to-address to 'https://gcc.gnu.org/PR78039'.
> forcemerge 841292 841316
Bug #841292 [gcc-6] gcc-6: flexible array support broken
Unable to merge bugs because:
package of #841316 is 'src:gcc-6' not 'gcc-6'
Failed to forcibly merge 841292: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Bug#841331: node-is-primitive: FTBFS (Error: Cannot find module wrappy)

[Santiago Vila]

Package: src:node-is-primitive
Version: 2.0.0-1
Severity: serious

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep
   dh_testdir -i
   dh_update_autotools_config -i
   dh_auto_configure -i
   dh_auto_build -i
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
mocha -R spec
module.js:327
throw err;
^

Error: Cannot find module 'wrappy'
at Function.Module._resolveFilename (module.js:325:15)
at Function.Module._load (module.js:276:25)
at Module.require (module.js:353:17)
at require (internal/module.js:12:17)
at Object. (/usr/lib/nodejs/once.js:1:76)
at Module._compile (module.js:409:26)
at Object.Module._extensions..js (module.js:416:10)
at Module.load (module.js:343:32)
at Function.Module._load (module.js:300:12)
at Module.require (module.js:353:17)
debian/rules:13: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
debian/rules:8: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


The relevant part of the build log is included above.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

Thanks.

Bug#841338: node-repeat-element: FTBFS (Error: Cannot find module wrappy)

[Santiago Vila]

Package: src:node-repeat-element
Version: 1.1.2+github-1
Severity: serious

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep
   dh_testdir -i
   dh_update_autotools_config -i
   dh_auto_configure -i
   dh_auto_build -i
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>/node-repeat-element-1.1.2+github'
mocha
module.js:327
throw err;
^

Error: Cannot find module 'wrappy'
at Function.Module._resolveFilename (module.js:325:15)
at Function.Module._load (module.js:276:25)
at Module.require (module.js:353:17)
at require (internal/module.js:12:17)
at Object. (/usr/lib/nodejs/once.js:1:76)
at Module._compile (module.js:409:26)
at Object.Module._extensions..js (module.js:416:10)
at Module.load (module.js:343:32)
at Function.Module._load (module.js:300:12)
at Module.require (module.js:353:17)
debian/rules:13: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>/node-repeat-element-1.1.2+github'
debian/rules:8: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


The relevant part of the build log is included above.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

Thanks.

Bug#841333: node-isobject: FTBFS (Error: Cannot find module wrappy)

[Santiago Vila]

Package: src:node-isobject
Version: 2.1.0-1
Severity: serious

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep
   dh_testdir -i
   dh_update_autotools_config -i
   dh_auto_configure -i
   dh_auto_build -i
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
mocha
module.js:327
throw err;
^

Error: Cannot find module 'wrappy'
at Function.Module._resolveFilename (module.js:325:15)
at Function.Module._load (module.js:276:25)
at Module.require (module.js:353:17)
at require (internal/module.js:12:17)
at Object. (/usr/lib/nodejs/once.js:1:76)
at Module._compile (module.js:409:26)
at Object.Module._extensions..js (module.js:416:10)
at Module.load (module.js:343:32)
at Function.Module._load (module.js:300:12)
at Module.require (module.js:353:17)
debian/rules:13: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
debian/rules:8: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


The relevant part of the build log is included above.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

Thanks.

Bug#841321: node-collection-visit: FTBFS (Error: Cannot find module wrappy)

[Santiago Vila]

Package: src:node-collection-visit
Version: 0.2.3-1
Severity: serious

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep
   dh_testdir -i
   dh_update_autotools_config -i
   dh_auto_configure -i
   dh_auto_build -i
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
mocha
module.js:327
throw err;
^

Error: Cannot find module 'wrappy'
at Function.Module._resolveFilename (module.js:325:15)
at Function.Module._load (module.js:276:25)
at Module.require (module.js:353:17)
at require (internal/module.js:12:17)
at Object. (/usr/lib/nodejs/once.js:1:76)
at Module._compile (module.js:409:26)
at Object.Module._extensions..js (module.js:416:10)
at Module.load (module.js:343:32)
at Function.Module._load (module.js:300:12)
at Module.require (module.js:353:17)
debian/rules:13: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
debian/rules:8: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


The relevant part of the build log is included above.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

Thanks.

Bug#841337: node-pascalcase: FTBFS (Error: Cannot find module wrappy)

[Santiago Vila]

Package: src:node-pascalcase
Version: 0.1.1-1
Severity: serious

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep
   dh_testdir -i
   dh_update_autotools_config -i
   dh_auto_configure -i
   dh_auto_build -i
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
mocha
module.js:327
throw err;
^

Error: Cannot find module 'wrappy'
at Function.Module._resolveFilename (module.js:325:15)
at Function.Module._load (module.js:276:25)
at Module.require (module.js:353:17)
at require (internal/module.js:12:17)
at Object. (/usr/lib/nodejs/once.js:1:76)
at Module._compile (module.js:409:26)
at Object.Module._extensions..js (module.js:416:10)
at Module.load (module.js:343:32)
at Function.Module._load (module.js:300:12)
at Module.require (module.js:353:17)
debian/rules:13: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
debian/rules:8: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


The relevant part of the build log is included above.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

Thanks.

Bug#841336: node-normalize-path: FTBFS (Error: Cannot find module wrappy)

[Santiago Vila]

Package: src:node-normalize-path
Version: 2.0.1-1
Severity: serious

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep
   dh_testdir -i
   dh_update_autotools_config -i
   dh_auto_configure -i
   dh_auto_build -i
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
mocha
module.js:327
throw err;
^

Error: Cannot find module 'wrappy'
at Function.Module._resolveFilename (module.js:325:15)
at Function.Module._load (module.js:276:25)
at Module.require (module.js:353:17)
at require (internal/module.js:12:17)
at Object. (/usr/lib/nodejs/once.js:1:76)
at Module._compile (module.js:409:26)
at Object.Module._extensions..js (module.js:416:10)
at Module.load (module.js:343:32)
at Function.Module._load (module.js:300:12)
at Module.require (module.js:353:17)
debian/rules:13: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
debian/rules:8: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


The relevant part of the build log is included above.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

Thanks.

Bug#841320: node-collection-visit: FTBFS (Error: Cannot find module wrappy)

[Santiago Vila]

Package: src:node-collection-visit
Version: 0.2.3-1
Severity: serious

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep
   dh_testdir -i
   dh_update_autotools_config -i
   dh_auto_configure -i
   dh_auto_build -i
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
mocha
module.js:327
throw err;
^

Error: Cannot find module 'wrappy'
at Function.Module._resolveFilename (module.js:325:15)
at Function.Module._load (module.js:276:25)
at Module.require (module.js:353:17)
at require (internal/module.js:12:17)
at Object. (/usr/lib/nodejs/once.js:1:76)
at Module._compile (module.js:409:26)
at Object.Module._extensions..js (module.js:416:10)
at Module.load (module.js:343:32)
at Function.Module._load (module.js:300:12)
at Module.require (module.js:353:17)
debian/rules:13: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
debian/rules:8: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


The relevant part of the build log is included above.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

Thanks.

Bug#841324: node-extend-shallow: FTBFS (Error: Cannot find module wrappy)

[Santiago Vila]

Package: src:node-extend-shallow
Version: 2.0.1-1
Severity: serious

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep
   dh_testdir -i
   dh_update_autotools_config -i
   dh_auto_configure -i
   dh_auto_build -i
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
mocha
module.js:327
throw err;
^

Error: Cannot find module 'wrappy'
at Function.Module._resolveFilename (module.js:325:15)
at Function.Module._load (module.js:276:25)
at Module.require (module.js:353:17)
at require (internal/module.js:12:17)
at Object. (/usr/lib/nodejs/once.js:1:76)
at Module._compile (module.js:409:26)
at Object.Module._extensions..js (module.js:416:10)
at Module.load (module.js:343:32)
at Function.Module._load (module.js:300:12)
at Module.require (module.js:353:17)
debian/rules:13: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
debian/rules:8: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


The relevant part of the build log is included above.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

Thanks.

Bug#841323: node-copy-descriptor: FTBFS (Error: Cannot find module wrappy)

[Santiago Vila]

Package: src:node-copy-descriptor
Version: 0.1.1-1
Severity: serious

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep
   dh_testdir -i
   dh_update_autotools_config -i
   dh_auto_configure -i
   dh_auto_build -i
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
mocha
module.js:327
throw err;
^

Error: Cannot find module 'wrappy'
at Function.Module._resolveFilename (module.js:325:15)
at Function.Module._load (module.js:276:25)
at Module.require (module.js:353:17)
at require (internal/module.js:12:17)
at Object. (/usr/lib/nodejs/once.js:1:76)
at Module._compile (module.js:409:26)
at Object.Module._extensions..js (module.js:416:10)
at Module.load (module.js:343:32)
at Function.Module._load (module.js:300:12)
at Module.require (module.js:353:17)
debian/rules:13: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
debian/rules:8: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


The relevant part of the build log is included above.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

Thanks.

Bug#841328: node-has-values: FTBFS (Error: Cannot find module wrappy)

[Santiago Vila]

Package: src:node-has-values
Version: 0.1.4-1
Severity: serious

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep
   dh_testdir -i
   dh_update_autotools_config -i
   dh_auto_configure -i
   dh_auto_build -i
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
mocha
module.js:327
throw err;
^

Error: Cannot find module 'wrappy'
at Function.Module._resolveFilename (module.js:325:15)
at Function.Module._load (module.js:276:25)
at Module.require (module.js:353:17)
at require (internal/module.js:12:17)
at Object. (/usr/lib/nodejs/once.js:1:76)
at Module._compile (module.js:409:26)
at Object.Module._extensions..js (module.js:416:10)
at Module.load (module.js:343:32)
at Function.Module._load (module.js:300:12)
at Module.require (module.js:353:17)
debian/rules:13: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
debian/rules:8: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


The relevant part of the build log is included above.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

Thanks.

Bug#841326: node-fill-range: FTBFS (Error: Cannot find module wrappy)

[Santiago Vila]

Package: src:node-fill-range
Version: 3.0.3-1
Severity: serious

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep
   dh_testdir -i
   dh_update_autotools_config -i
   dh_auto_configure -i
   dh_auto_build -i
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
mocha
module.js:327
throw err;
^

Error: Cannot find module 'wrappy'
at Function.Module._resolveFilename (module.js:325:15)
at Function.Module._load (module.js:276:25)
at Module.require (module.js:353:17)
at require (internal/module.js:12:17)
at Object. (/usr/lib/nodejs/once.js:1:76)
at Module._compile (module.js:409:26)
at Object.Module._extensions..js (module.js:416:10)
at Module.load (module.js:343:32)
at Function.Module._load (module.js:300:12)
at Module.require (module.js:353:17)
debian/rules:13: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
debian/rules:8: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


The relevant part of the build log is included above.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

Thanks.

Bug#841320: marked as done (node-collection-visit: FTBFS (Error: Cannot find module wrappy))

[Debian Bug Tracking System]

Your message dated Wed, 19 Oct 2016 17:52:50 +0200
with message-id <20161019155250.i6n2tydvt3ovulpy@nuc>
and subject line Re: Bug#841320: node-collection-visit: FTBFS (Error: Cannot 
find module wrappy)
has caused the Debian Bug report #841320,
regarding node-collection-visit: FTBFS (Error: Cannot find module wrappy)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
841320: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841320
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:node-collection-visit
Version: 0.2.3-1
Severity: serious

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep
   dh_testdir -i
   dh_update_autotools_config -i
   dh_auto_configure -i
   dh_auto_build -i
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
mocha
module.js:327
throw err;
^

Error: Cannot find module 'wrappy'
at Function.Module._resolveFilename (module.js:325:15)
at Function.Module._load (module.js:276:25)
at Module.require (module.js:353:17)
at require (internal/module.js:12:17)
at Object. (/usr/lib/nodejs/once.js:1:76)
at Module._compile (module.js:409:26)
at Object.Module._extensions..js (module.js:416:10)
at Module.load (module.js:343:32)
at Function.Module._load (module.js:300:12)
at Module.require (module.js:353:17)
debian/rules:13: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
debian/rules:8: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


The relevant part of the build log is included above.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

Thanks.
--- End Message ---
--- Begin Message ---
Sorry for this one. Closing duplicate.

(It said "in stretch" but it's not true).--- End Message ---

Bug#841329: node-hosted-git-info: FTBFS (Error: Cannot find module wrappy)

[Santiago Vila]

Package: src:node-hosted-git-info
Version: 2.1.5-1
Severity: serious

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep
   dh_testdir -i
   dh_update_autotools_config -i
   dh_auto_configure -i
   dh_auto_build -i
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
tap test/*.js
module.js:327
throw err;
^

Error: Cannot find module 'wrappy'
at Function.Module._resolveFilename (module.js:325:15)
at Function.Module._load (module.js:276:25)
at Module.require (module.js:353:17)
at require (internal/module.js:12:17)
at Object. (/usr/lib/nodejs/once.js:1:76)
at Module._compile (module.js:409:26)
at Object.Module._extensions..js (module.js:416:10)
at Module.load (module.js:343:32)
at Function.Module._load (module.js:300:12)
at Module.require (module.js:353:17)
debian/rules:13: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
debian/rules:8: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


The relevant part of the build log is included above.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

Thanks.

Bug#841330: node-is-dotfile: FTBFS (Error: Cannot find module wrappy)

[Santiago Vila]

Package: src:node-is-dotfile
Version: 1.0.2-1
Severity: serious

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep
   dh_testdir -i
   dh_update_autotools_config -i
   dh_auto_configure -i
   dh_auto_build -i
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
mocha -R spec
module.js:327
throw err;
^

Error: Cannot find module 'wrappy'
at Function.Module._resolveFilename (module.js:325:15)
at Function.Module._load (module.js:276:25)
at Module.require (module.js:353:17)
at require (internal/module.js:12:17)
at Object. (/usr/lib/nodejs/once.js:1:76)
at Module._compile (module.js:409:26)
at Object.Module._extensions..js (module.js:416:10)
at Module.load (module.js:343:32)
at Function.Module._load (module.js:300:12)
at Module.require (module.js:353:17)
debian/rules:13: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
debian/rules:8: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


The relevant part of the build log is included above.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

Thanks.

Bug#841332: node-isexe: FTBFS (Error: Cannot find module wrappy)

[Santiago Vila]

Package: src:node-isexe
Version: 1.1.2-1
Severity: serious

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep
   dh_testdir -i
   dh_update_autotools_config -i
   dh_auto_configure -i
   dh_auto_build -i
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
tap test/*.js --branches=100 --statements=100 --functions=100 --lines=100
module.js:327
throw err;
^

Error: Cannot find module 'wrappy'
at Function.Module._resolveFilename (module.js:325:15)
at Function.Module._load (module.js:276:25)
at Module.require (module.js:353:17)
at require (internal/module.js:12:17)
at Object. (/usr/lib/nodejs/once.js:1:76)
at Module._compile (module.js:409:26)
at Object.Module._extensions..js (module.js:416:10)
at Module.load (module.js:343:32)
at Function.Module._load (module.js:300:12)
at Module.require (module.js:353:17)
debian/rules:13: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
debian/rules:8: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


The relevant part of the build log is included above.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

Thanks.

Bug#841335: node-map-visit: FTBFS (Error: Cannot find module wrappy)

[Santiago Vila]

Package: src:node-map-visit
Version: 0.1.5-1
Severity: serious

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep
   dh_testdir -i
   dh_update_autotools_config -i
   dh_auto_configure -i
   dh_auto_build -i
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
mocha
module.js:327
throw err;
^

Error: Cannot find module 'wrappy'
at Function.Module._resolveFilename (module.js:325:15)
at Function.Module._load (module.js:276:25)
at Module.require (module.js:353:17)
at require (internal/module.js:12:17)
at Object. (/usr/lib/nodejs/once.js:1:76)
at Module._compile (module.js:409:26)
at Object.Module._extensions..js (module.js:416:10)
at Module.load (module.js:343:32)
at Function.Module._load (module.js:300:12)
at Module.require (module.js:353:17)
debian/rules:13: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
debian/rules:8: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


The relevant part of the build log is included above.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

Thanks.

Bug#841334: node-map-cache: FTBFS (Error: Cannot find module wrappy)

[Santiago Vila]

Package: src:node-map-cache
Version: 0.2.2-1
Severity: serious

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep
   dh_testdir -i
   dh_update_autotools_config -i
   dh_auto_configure -i
   dh_auto_build -i
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
mocha
module.js:327
throw err;
^

Error: Cannot find module 'wrappy'
at Function.Module._resolveFilename (module.js:325:15)
at Function.Module._load (module.js:276:25)
at Module.require (module.js:353:17)
at require (internal/module.js:12:17)
at Object. (/usr/lib/nodejs/once.js:1:76)
at Module._compile (module.js:409:26)
at Object.Module._extensions..js (module.js:416:10)
at Module.load (module.js:343:32)
at Function.Module._load (module.js:300:12)
at Module.require (module.js:353:17)
debian/rules:13: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
debian/rules:8: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


The relevant part of the build log is included above.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

Thanks.

Bug#841327: node-glob-parent: FTBFS (Error: Cannot find module wrappy)

[Santiago Vila]

Package: src:node-glob-parent
Version: 3.0.0-1
Severity: serious

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep
   dh_testdir -i
   dh_update_autotools_config -i
   dh_auto_configure -i
   dh_auto_build -i
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
mocha -R spec
module.js:327
throw err;
^

Error: Cannot find module 'wrappy'
at Function.Module._resolveFilename (module.js:325:15)
at Function.Module._load (module.js:276:25)
at Module.require (module.js:353:17)
at require (internal/module.js:12:17)
at Object. (/usr/lib/nodejs/once.js:1:76)
at Module._compile (module.js:409:26)
at Object.Module._extensions..js (module.js:416:10)
at Module.load (module.js:343:32)
at Function.Module._load (module.js:300:12)
at Module.require (module.js:353:17)
debian/rules:13: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
debian/rules:8: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


The relevant part of the build log is included above.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

Thanks.

Bug#841325: node-filename-regex: FTBFS (Error: Cannot find module wrappy)

[Santiago Vila]

Package: src:node-filename-regex
Version: 2.0.0-1
Severity: serious

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep
   dh_testdir -i
   dh_update_autotools_config -i
   dh_auto_configure -i
   dh_auto_build -i
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
mocha -R spec
module.js:327
throw err;
^

Error: Cannot find module 'wrappy'
at Function.Module._resolveFilename (module.js:325:15)
at Function.Module._load (module.js:276:25)
at Module.require (module.js:353:17)
at require (internal/module.js:12:17)
at Object. (/usr/lib/nodejs/once.js:1:76)
at Module._compile (module.js:409:26)
at Object.Module._extensions..js (module.js:416:10)
at Module.load (module.js:343:32)
at Function.Module._load (module.js:300:12)
at Module.require (module.js:353:17)
debian/rules:13: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
debian/rules:8: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


The relevant part of the build log is included above.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

Thanks.

Bug#841322: node-component-emitter: FTBFS (Error: Cannot find module wrappy)

[Santiago Vila]

Package: src:node-component-emitter
Version: 1.2.1-1
Severity: serious

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep
   dh_testdir -i
   dh_update_autotools_config -i
   dh_auto_configure -i
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
# Skip upstream Makefile
make[1]: Leaving directory '/<>'
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
mocha --require should --reporter spec
module.js:327
throw err;
^

Error: Cannot find module 'wrappy'
at Function.Module._resolveFilename (module.js:325:15)
at Function.Module._load (module.js:276:25)
at Module.require (module.js:353:17)
at require (internal/module.js:12:17)
at Object. (/usr/lib/nodejs/once.js:1:76)
at Module._compile (module.js:409:26)
at Object.Module._extensions..js (module.js:416:10)
at Module.load (module.js:343:32)
at Function.Module._load (module.js:300:12)
at Module.require (module.js:353:17)
debian/rules:14: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
debian/rules:8: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


The relevant part of the build log is included above.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

Thanks.

Bug#841313: latex-cjk-japanese-wadalab: FTBFS: Create .afm and .pfa fonts from dg. \n Segmentation fault (core dumped)

[韓達耐]

Hi Chris

It looks like a problem with the wftodm binary.  This is an important piece
in the creation of the fonts.
I will only have access to my PC next week Thursday (27 October 2016) to
check the C source code and replicate it on amd64.  Please bear with me for
a while.

Thanks for your bug report.

Regards

-- 
Danai

On 19 Oct 2016 16:34, "Chris Lamb"  wrote:

Source: latex-cjk-japanese-wadalab
Version: 0.20050817-16
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

latex-cjk-japanese-wadalab fails to build from source in unstable/amd64:

  […]

  Setting up libopenjp2-7:amd64 (2.1.2-1) ...
  Setting up libptexenc1:amd64 (2016.20160513.41080-7) ...
  Setting up libjpeg62-turbo:amd64 (1:1.5.1-1) ...
  Processing triggers for mime-support (3.60) ...
  Setting up libpng16-16:amd64 (1.6.25-2) ...
  Setting up liblcms2-2:amd64 (2.7-1) ...
  Setting up libjbig0:amd64 (2.1-3.1) ...
  Setting up fonts-dejavu-core (2.37-1) ...
  Setting up poppler-data (0.4.7-7) ...
  Setting up libtiff5:amd64 (4.0.6-2) ...
  Setting up libnspr4:amd64 (2:4.12-6) ...
  Setting up ucf (3.0036) ...
  Setting up libfreetype6:amd64 (2.6.3-3+b1) ...
  Setting up libgraphite2-3:amd64 (1.3.8-1) ...
  Setting up libjbig2dec0:amd64 (0.13-3) ...
  Setting up libpixman-1-0:amd64 (0.34.0-1) ...
  Processing triggers for libc-bin (2.24-5) ...
  Processing triggers for systemd (231-9) ...
  Setting up libijs-0.35:amd64 (0.35-12) ...
  Setting up libpotrace0 (1.13-2) ...
  Processing triggers for man-db (2.7.5-1) ...
  Setting up libxdmcp6:amd64 (1:1.1.2-1.1) ...
  Setting up libzzip-0-13:amd64 (0.13.62-3) ...
  Setting up x11-common (1:7.7+16) ...
  update-rc.d: warning: start and stop actions are no longer supported;
falling back to defaults
  invoke-rc.d: could not determine current runlevel
  invoke-rc.d: policy-rc.d denied execution of start.
  Setting up xdg-utils (1.1.1-1) ...
  Setting up libtexluajit2:amd64 (2016.20160513.41080-7) ...
  Setting up libx11-data (2:1.6.3-1) ...
  Setting up libxau6:amd64 (1:1.0.8-1) ...
  Setting up libdbus-1-3:amd64 (1.10.12-1) ...
  Setting up libavahi-common-data:amd64 (0.6.32-1) ...
  Setting up libpaper1:amd64 (1.1.24+nmu4) ...

  Creating config file /etc/papersize with new version
  Setting up libpaper-utils (1.1.24+nmu4) ...
  Setting up fontconfig-config (2.11.0-6.7) ...
  Setting up tex-common (6.05) ...
  update-language: texlive-base not installed and configured, doing nothing!
  Setting up libnss3:amd64 (2:3.26-2) ...
  Setting up libharfbuzz0b:amd64 (1.2.7-1+b1) ...
  Setting up libice6:amd64 (2:1.0.9-1+b1) ...
  Setting up libavahi-common3:amd64 (0.6.32-1) ...
  Setting up libxcb1:amd64 (1.12-1) ...
  Setting up libfontconfig1:amd64 (2.11.0-6.7) ...
  Setting up libsm6:amd64 (2:1.2.2-1+b1) ...
  Setting up libxcb-render0:amd64 (1.12-1) ...
  Setting up libharfbuzz-icu0:amd64 (1.2.7-1+b1) ...
  Setting up libx11-6:amd64 (2:1.6.3-1) ...
  Setting up libxcb-shm0:amd64 (1.12-1) ...
  Setting up libxpm4:amd64 (1:3.5.11-1+b1) ...
  Setting up libxt6:amd64 (1:1.1.5-1) ...
  Setting up libxrender1:amd64 (1:0.9.9-2) ...
  Setting up libavahi-client3:amd64 (0.6.32-1) ...
  Setting up libpoppler61:amd64 (0.44.0-3) ...
  Setting up libcups2:amd64 (2.2.1-1) ...
  Setting up libxext6:amd64 (2:1.3.3-1) ...
  Setting up libxmu6:amd64 (2:1.1.2-2) ...
  Setting up libcupsimage2:amd64 (2.2.1-1) ...
  Setting up libgs9:amd64 (9.19~dfsg-3) ...
  Setting up libxi6:amd64 (2:1.7.6-1) ...
  Setting up libxaw7:amd64 (2:1.0.13-1) ...
  Setting up libcairo2:amd64 (1.14.6-1+b1) ...
  Setting up texlive-binaries (2016.20160513.41080-7) ...
  update-alternatives: using /usr/bin/xdvi-xaw to provide /usr/bin/xdvi.bin
(xdvi.bin) in auto mode
  update-alternatives: using /usr/bin/bibtex.original to provide
/usr/bin/bibtex (bibtex) in auto mode
  Processing triggers for tex-common (6.05) ...
  update-language: texlive-base not installed and configured, doing nothing!
  texlive-base is not ready, skipping fmtutil --all call
  Setting up texlive-base (2016.20161008-1) ...
  mktexlsr: Updating /var/lib/texmf/ls-R-TEXLIVEDIST...
  mktexlsr: Updating /var/lib/texmf/ls-R-TEXMFMAIN...
  mktexlsr: Updating /var/lib/texmf/ls-R...
  mktexlsr: Done.
  /usr/bin/tl-paper: setting paper size for dvips to a4.
  /usr/bin/tl-paper: setting paper size for dvipdfmx to a4.
  /usr/bin/tl-paper: setting paper size for xdvi to a4.
  /usr/bin/tl-paper: setting paper size for pdftex to a4.
  Processing triggers for tex-common (6.05) ...
  Running updmap-sys. This may take some time... done.
  Running mktexlsr /var/lib/texmf ... done.
  Building format(s) --all.
This may take some time... done.
  Setting up texlive-font-utils (2016.20161008-1) ...
  Setting up latex-cjk-japanese-wadalab-build-deps (0.20050817-16) ...
  Processing triggers for libc-bin (2.24-5) ...
  

Bug#841316: gcc: the last 6.2.0-7 broke the virtualbox build

[James Cowgill]

Hi,

On Wed, 19 Oct 2016 14:47:48 + (UTC) Gianfranco Costamagna
 wrote:
> Source: gcc
> Version: 6.2.0-7
> Severity: serious
> 
> As said, I built virtualbox correctly with 6.2.0-6 and then uploaded on 
> unstable.
> The new gcc 6.2.0-7 broke the build with the following error:
[...]
> /usr/include/x86_64-linux-gnu/sys/inotify.h:34:13: error: flexible array 
> member 'inotify_event::name' not at end of 'struct InotifyEventWithName'

Relevant parts:

cdefs.h
---
# define __flexarr  []

inotify.h

/* Structure describing an inotify event.  */
struct inotify_event
{
  int wd;   /* Watch descriptor.  */
  uint32_t mask;/* Watch mask.  */
  uint32_t cookie;  /* Cookie to synchronize two events.  */
  uint32_t len; /* Length (including NULs) of name.  */
  char name __flexarr;  /* Name.  */
};

HostDnsServiceLinux.cpp:

struct InotifyEventWithName
{
struct inotify_event e;
char name[NAME_MAX];
};

While I do not know if this is a GCC bug or not, doing the above is a
bit dodgy (and prohibited by C99). What is the offset of
InotifyEventWithName::name supposed to be (given sizeof(inotify_event)
is undefined)?

This report has some info about GCC 6 changes in this regard:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69550

Since it's closed as WONTFIX, I expect this will not be changed in gcc.

Thanks,
James




signature.asc
Description: OpenPGP digital signature

Processed: your mail

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 841316 src:gcc-6
Bug #841316 [src:gcc] gcc: the last 6.2.0-7 broke the virtualbox build
Warning: Unknown package 'src:gcc'
Bug reassigned from package 'src:gcc' to 'src:gcc-6'.
No longer marked as found in versions gcc/6.2.0-7.
Ignoring request to alter fixed versions of bug #841316 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#840853: Workaround

[Hilko Bengen]

Neil,

while working a bit on libguestfs 1.34 the other day, I noticed that
the problem exists there, too.

Whereas installing the sgabios package gives us somewhat meaningful
console output, linuxboot_dma.bin is still missing. I suppose that the
newer qemu version wants to use linuxboot_dma.bin instead of
linuxboot.bin from the seabios package.

After creating a symlink

/usr/share/seabios/linuxboot_dma.bin -> linuxboot.bin

... libguestfs-test-tool will work just fine here. Could you please
verify that the workaround does the trick for you, too?

If so, the bug should probably be reassigned to the qemu package.

Cheers,
-Hilko

Bug#841316: gcc: the last 6.2.0-7 broke the virtualbox build

[Gianfranco Costamagna]

Source: gcc
Version: 6.2.0-7
Severity: serious

As said, I built virtualbox correctly with 6.2.0-6 and then uploaded on 
unstable.
The new gcc 6.2.0-7 broke the build with the following error:


kmk_builtin_rm -f -- /«PKGBUILDDIR»/out/obj/VBoxVMM/dtrace/dtrace/VBoxVMM.h.dep 
/«PKGBUILDDIR»/out/obj/VBoxVMM/dtrace/dtrace/VBoxVMM.h
/«PKGBUILDDIR»/out/obj/VBoxTpG/VBoxTpG -64 -h --host-64-bit  --ring-3-context 
-o "/«PKGBUILDDIR»/out/obj/VBoxVMM/dtrace/dtrace/VBoxVMM.h" -s 
"/«PKGBUILDDIR»/src/VBox/VMM/VBoxVMM.d"
kBuild: Generating VBoxDD - 
/«PKGBUILDDIR»/out/obj/VBoxDD/dtrace/dtrace/VBoxDD.h from 
/«PKGBUILDDIR»/src/VBox/Devices/build/VBoxDD.d
kmk_builtin_rm -f -- /«PKGBUILDDIR»/out/obj/VBoxDD/dtrace/dtrace/VBoxDD.h.dep 
/«PKGBUILDDIR»/out/obj/VBoxDD/dtrace/dtrace/VBoxDD.h
/«PKGBUILDDIR»/out/obj/VBoxTpG/VBoxTpG -64 -h --host-64-bit  --ring-3-context 
-o "/«PKGBUILDDIR»/out/obj/VBoxDD/dtrace/dtrace/VBoxDD.h" -s 
"/«PKGBUILDDIR»/src/VBox/Devices/build/VBoxDD.d"
VBoxTpG: warning: Please avoid using the type 'unsigned int' for probe 
arguments!
VBoxTpG: warning: Please avoid using the type 'unsigned int' for probe 
arguments!
VBoxTpG: warning: Please avoid using the type 'unsigned int' for probe 
arguments!
VBoxTpG: warning: Please avoid using the type 'unsigned int' for probe 
arguments!
VBoxTpG: warning: Please avoid using the type 'unsigned int' for probe 
arguments!
kBuild: Installing VBoxOGLcrutil => 
/«PKGBUILDDIR»/out/bin/additions/VBoxOGLcrutil.so 
kmk_builtin_install --hard-link-files-when-possible-- 
/«PKGBUILDDIR»/out/obj/VBoxOGLcrutil/VBoxOGLcrutil.so 
/«PKGBUILDDIR»/out/bin/additions/VBoxOGLcrutil.so
kBuild: Linking VBoxOGLerrorspu => 
/«PKGBUILDDIR»/out/obj/VBoxOGLerrorspu/VBoxOGLerrorspu.so
kmk_builtin_rm -f -- /«PKGBUILDDIR»/out/obj/VBoxOGLerrorspu/VBoxOGLerrorspu.dep 
/«PKGBUILDDIR»/out/obj/VBoxOGLerrorspu/VBoxOGLerrorspu.so  
/«PKGBUILDDIR»/out/obj/VBoxOGLerrorspu/VBoxOGLerrorspu.map 
gcc -shared-fPIC  -Wl,-z,noexecstack,-z,relro -Wl,--as-needed 
-m64   -o /«PKGBUILDDIR»/out/obj/VBoxOGLerrorspu/VBoxOGLerrorspu.so 
-Wl,-soname=VBoxOGLerrorspu.so 
/«PKGBUILDDIR»/out/obj/VBoxOGLerrorspu/gen/VBoxOGLgen/errorspu.o 
/«PKGBUILDDIR»/out/obj/VBoxOGLerrorspu/error/errorspu_init.o 
/«PKGBUILDDIR»/out/bin/additions/VBoxOGLcrutil.so   
/«PKGBUILDDIR»/out/lib/additions/RuntimeGuestR3Shared.a   
/«PKGBUILDDIR»/out/lib/additions/VBoxGuestR3LibShared.a   
/«PKGBUILDDIR»/out/lib/additions/RuntimeGuestR3Shared.a   -lpthread   -lrt   
-lm   -ldl 
kBuild: Linking VBoxOGL => /«PKGBUILDDIR»/out/obj/VBoxOGL/VBoxOGL.so
kmk_builtin_rm -f -- /«PKGBUILDDIR»/out/obj/VBoxOGL/VBoxOGL.dep 
/«PKGBUILDDIR»/out/obj/VBoxOGL/VBoxOGL.so  
/«PKGBUILDDIR»/out/obj/VBoxOGL/VBoxOGL.map 
gcc -shared-fPIC -Wl,-z,nodelete  -Wl,-z,noexecstack,-z,relro 
-Wl,--as-needed -Wl,-e,LibMain -m64   -o 
/«PKGBUILDDIR»/out/obj/VBoxOGL/VBoxOGL.so -Wl,-soname=libGL.so.1 
/«PKGBUILDDIR»/out/obj/VBoxOGL/load.o /«PKGBUILDDIR»/out/obj/VBoxOGL/stub.o 
/«PKGBUILDDIR»/out/obj/VBoxOGL/context.o 
/«PKGBUILDDIR»/out/obj/VBoxOGL/gen/VBoxOGLgen/getprocaddress.o 
/«PKGBUILDDIR»/out/obj/VBoxOGL/gen/VBoxOGLgen/NULLfuncs.o 
/«PKGBUILDDIR»/out/obj/VBoxOGL/gen/VBoxOGLgen/tsfuncs.o 
/«PKGBUILDDIR»/out/obj/VBoxOGL/glx.o /«PKGBUILDDIR»/out/obj/VBoxOGL/xfont.o 
/«PKGBUILDDIR»/out/obj/VBoxOGL/gen/VBoxOGLgen/linux_exports.o 
/«PKGBUILDDIR»/out/lib/additions/RuntimeGuestR3Shared.a   
/«PKGBUILDDIR»/out/lib/additions/VBoxGuestR3LibShared.a   
/«PKGBUILDDIR»/out/bin/additions/VBoxOGLcrutil.so   
/«PKGBUILDDIR»/out/lib/additions/VBoxOGLspuload.a   -lXcomposite   -lXdamage   
-lXfixes   -lXext   /«PKGBUILDDIR»/out/lib/additions/RuntimeGuestR3Shared.a   
/«PKGBUILDDIR»/out/lib/additions/VBoxGuestR3LibShared.a   
/«PKGBUILDDIR»/out/lib/additions/RuntimeGuestR3Shared.a   -lpthread   -lrt   
-lm   -ldl 
/usr/bin/ld: warning: cannot find entry symbol LibMain; defaulting to 
00058030
kBuild: Linking VBoxOGLarrayspu => 
/«PKGBUILDDIR»/out/obj/VBoxOGLarrayspu/VBoxOGLarrayspu.so
kmk_builtin_rm -f -- /«PKGBUILDDIR»/out/obj/VBoxOGLarrayspu/VBoxOGLarrayspu.dep 
/«PKGBUILDDIR»/out/obj/VBoxOGLarrayspu/VBoxOGLarrayspu.so  
/«PKGBUILDDIR»/out/obj/VBoxOGLarrayspu/VBoxOGLarrayspu.map 
gcc -shared-fPIC  -Wl,-z,noexecstack,-z,relro -Wl,--as-needed 
-m64   -o /«PKGBUILDDIR»/out/obj/VBoxOGLarrayspu/VBoxOGLarrayspu.so 
-Wl,-soname=VBoxOGLarrayspu.so 
/«PKGBUILDDIR»/out/obj/VBoxOGLarrayspu/array/arrayspu.o 
/«PKGBUILDDIR»/out/obj/VBoxOGLarrayspu/array/arrayspu_config.o 
/«PKGBUILDDIR»/out/obj/VBoxOGLarrayspu/array/arrayspu_init.o 
/«PKGBUILDDIR»/out/bin/additions/VBoxOGLcrutil.so   
/«PKGBUILDDIR»/out/lib/additions/VBoxOGLspuload.a   
/«PKGBUILDDIR»/out/lib/additions/VBoxOGLcrstate.a   
/«PKGBUILDDIR»/out/lib/additions/RuntimeGuestR3Shared.a   
/«PKGBUILDDIR»/out/lib/additions/VBoxGuestR3LibShared.a   
/«PKGBUILDDIR»/out/lib/additions/RuntimeGuestR3Shared.a   -lpthread   -lrt   
-lm   -ldl 
kBuild: Linking VBoxOGLpassthroughspu => 

Processed: severity of 841082 is serious

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 841082 serious
Bug #841082 [epiphany-browser] epiphany-browser: bump dependency on 
epiphany-browser-data
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: Re: Bug#841307: docker-compose: Wrong dependency version for python-docker

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #841307 [docker-compose] docker-compose: Wrong dependency version for 
python-docker
Severity set to 'serious' from 'important'

-- 
841307: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841307
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#841285: freemat: FTBFS (cannot find -lclangTidyReadabilityModule)

[Gianfranco Costamagna]

Hi Santiago

>Ok, I could agree that freemat is probably not to be blamed for this.



as an llvm team member, I can say that we are already working on removing 3.6 
from testing.
Yesterday 3.8 migrated, and today we already opened 4 bugs against 
ftp.debian.org to make llvm-defaults migrate too.

let me quote #devel discussion here (with no nicks)


[15:11:36] seems that llvm-defaults needs some care to migrate...
[15:13:04] i.e. the armel binaries removed?
[15:13:24] including rdeps
[15:25:45] I think they are still here :/ sorry about that
[15:28:22] (I just filed a RM for the obsolete lldb binaries, not related to 
testing migration, but just for cleaning up the view)
[15:56:11] llvm 3.8 migrated, so if you can do that part with mapreri, we can 
remove 3.6 from testing too
[15:56:24] see e.g. #841303
[15:56:27] -zwiebelbot/22#debian-devel- Debian#841303: RM: aspectc++ qtcreator 
libclang-perl [armel] -- RoQA; FTBFS - https://bugs.debian.org/841303
[15:58:09] maybe we can ask  to kick llvm-3.6 out of testing?
[15:59:34] britney is trying to remove it already, but it can't happen until 
llvm-toolchain-3.9 gets fixed
[15:59:59] oh... ok
[16:00:12] (if you can look at llvm 3.9/arm64, that'd be good)
[16:02:27] yeah, -defaults won't migrate until it gets removed from armel
[16:02:37] can youfile an RM bug for that?
[16:03:09] also, a bug for python-lldb-3.9 decruft on powerpc/ppc64el/s390x
[16:03:53] ppc64el?
[16:04:01] I filed one for ppc/s390x some minutes ago
[16:04:08] ah, nvm
[16:05:39] sent (decruft of python-lldb-3.9)
[16:07:07] still need one for llvm-defaults/armel
[16:08:11] checking dak rm output
[16:08:19] # Broken Depends:
[16:08:19] emscripten: emscripten
[16:08:27] could be worse
[16:08:47] a package with 5 RC bugs, probably nobody cares anyway :>
[16:08:52] 4*
[16:09:06] it was ok to remove it from armel
[16:09:24] I guess, RM it before, then
[16:09:33] yes
[16:09:45] file both, make the llvm-defaults block on the emscripten bug
[16:09:48] see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839033#15
[16:09:48] yes yes
[16:09:51] -zwiebelbot/22#debian-devel- Debian#839033: RM: 
llvm-toolchain-snapshot [armel mips64el] -- RoQA; FTBFS, outdated snapshot - 
https://bugs.debian.org/839033
[16:19:04] #841298 #841305 #841306 #841308 — these should take care of 
everything from what I see.
[16:19:50] I hope ftpmasters will process the last one correctly and not cause 
sourceless binaries by forgetting -B (ISTR removals.html generator doesn't add 
it, or something)

G.

Bug#841313: latex-cjk-japanese-wadalab: FTBFS: Create .afm and .pfa fonts from dg. \n Segmentation fault (core dumped)

[Chris Lamb]

Source: latex-cjk-japanese-wadalab
Version: 0.20050817-16
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

latex-cjk-japanese-wadalab fails to build from source in unstable/amd64:

  […]

  Setting up libopenjp2-7:amd64 (2.1.2-1) ...
  Setting up libptexenc1:amd64 (2016.20160513.41080-7) ...
  Setting up libjpeg62-turbo:amd64 (1:1.5.1-1) ...
  Processing triggers for mime-support (3.60) ...
  Setting up libpng16-16:amd64 (1.6.25-2) ...
  Setting up liblcms2-2:amd64 (2.7-1) ...
  Setting up libjbig0:amd64 (2.1-3.1) ...
  Setting up fonts-dejavu-core (2.37-1) ...
  Setting up poppler-data (0.4.7-7) ...
  Setting up libtiff5:amd64 (4.0.6-2) ...
  Setting up libnspr4:amd64 (2:4.12-6) ...
  Setting up ucf (3.0036) ...
  Setting up libfreetype6:amd64 (2.6.3-3+b1) ...
  Setting up libgraphite2-3:amd64 (1.3.8-1) ...
  Setting up libjbig2dec0:amd64 (0.13-3) ...
  Setting up libpixman-1-0:amd64 (0.34.0-1) ...
  Processing triggers for libc-bin (2.24-5) ...
  Processing triggers for systemd (231-9) ...
  Setting up libijs-0.35:amd64 (0.35-12) ...
  Setting up libpotrace0 (1.13-2) ...
  Processing triggers for man-db (2.7.5-1) ...
  Setting up libxdmcp6:amd64 (1:1.1.2-1.1) ...
  Setting up libzzip-0-13:amd64 (0.13.62-3) ...
  Setting up x11-common (1:7.7+16) ...
  update-rc.d: warning: start and stop actions are no longer supported; falling 
back to defaults
  invoke-rc.d: could not determine current runlevel
  invoke-rc.d: policy-rc.d denied execution of start.
  Setting up xdg-utils (1.1.1-1) ...
  Setting up libtexluajit2:amd64 (2016.20160513.41080-7) ...
  Setting up libx11-data (2:1.6.3-1) ...
  Setting up libxau6:amd64 (1:1.0.8-1) ...
  Setting up libdbus-1-3:amd64 (1.10.12-1) ...
  Setting up libavahi-common-data:amd64 (0.6.32-1) ...
  Setting up libpaper1:amd64 (1.1.24+nmu4) ...
  
  Creating config file /etc/papersize with new version
  Setting up libpaper-utils (1.1.24+nmu4) ...
  Setting up fontconfig-config (2.11.0-6.7) ...
  Setting up tex-common (6.05) ...
  update-language: texlive-base not installed and configured, doing nothing!
  Setting up libnss3:amd64 (2:3.26-2) ...
  Setting up libharfbuzz0b:amd64 (1.2.7-1+b1) ...
  Setting up libice6:amd64 (2:1.0.9-1+b1) ...
  Setting up libavahi-common3:amd64 (0.6.32-1) ...
  Setting up libxcb1:amd64 (1.12-1) ...
  Setting up libfontconfig1:amd64 (2.11.0-6.7) ...
  Setting up libsm6:amd64 (2:1.2.2-1+b1) ...
  Setting up libxcb-render0:amd64 (1.12-1) ...
  Setting up libharfbuzz-icu0:amd64 (1.2.7-1+b1) ...
  Setting up libx11-6:amd64 (2:1.6.3-1) ...
  Setting up libxcb-shm0:amd64 (1.12-1) ...
  Setting up libxpm4:amd64 (1:3.5.11-1+b1) ...
  Setting up libxt6:amd64 (1:1.1.5-1) ...
  Setting up libxrender1:amd64 (1:0.9.9-2) ...
  Setting up libavahi-client3:amd64 (0.6.32-1) ...
  Setting up libpoppler61:amd64 (0.44.0-3) ...
  Setting up libcups2:amd64 (2.2.1-1) ...
  Setting up libxext6:amd64 (2:1.3.3-1) ...
  Setting up libxmu6:amd64 (2:1.1.2-2) ...
  Setting up libcupsimage2:amd64 (2.2.1-1) ...
  Setting up libgs9:amd64 (9.19~dfsg-3) ...
  Setting up libxi6:amd64 (2:1.7.6-1) ...
  Setting up libxaw7:amd64 (2:1.0.13-1) ...
  Setting up libcairo2:amd64 (1.14.6-1+b1) ...
  Setting up texlive-binaries (2016.20160513.41080-7) ...
  update-alternatives: using /usr/bin/xdvi-xaw to provide /usr/bin/xdvi.bin 
(xdvi.bin) in auto mode
  update-alternatives: using /usr/bin/bibtex.original to provide 
/usr/bin/bibtex (bibtex) in auto mode
  Processing triggers for tex-common (6.05) ...
  update-language: texlive-base not installed and configured, doing nothing!
  texlive-base is not ready, skipping fmtutil --all call
  Setting up texlive-base (2016.20161008-1) ...
  mktexlsr: Updating /var/lib/texmf/ls-R-TEXLIVEDIST... 
  mktexlsr: Updating /var/lib/texmf/ls-R-TEXMFMAIN... 
  mktexlsr: Updating /var/lib/texmf/ls-R... 
  mktexlsr: Done.
  /usr/bin/tl-paper: setting paper size for dvips to a4.
  /usr/bin/tl-paper: setting paper size for dvipdfmx to a4.
  /usr/bin/tl-paper: setting paper size for xdvi to a4.
  /usr/bin/tl-paper: setting paper size for pdftex to a4.
  Processing triggers for tex-common (6.05) ...
  Running updmap-sys. This may take some time... done.
  Running mktexlsr /var/lib/texmf ... done.
  Building format(s) --all.
This may take some time... done.
  Setting up texlive-font-utils (2016.20161008-1) ...
  Setting up latex-cjk-japanese-wadalab-build-deps (0.20050817-16) ...
  Processing triggers for libc-bin (2.24-5) ...
  Processing triggers for systemd (231-9) ...
  
  
**
  ** Environment
  **
  
**
  
  

Bug#841312: cacti-spine: FTBFS: configure: error: MySQL libraries not found

[Chris Lamb]

Source: cacti-spine
Version: 0.8.8h-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

cacti-spine fails to build from source in unstable/amd64:

  […]

  Unpacking zlib1g-dev:amd64 (1:1.2.8.dfsg-2+b1) ...
  Selecting previously unselected package libmysqlclient-dev.
  Preparing to unpack .../03-libmysqlclient-dev_5.7.15-1_amd64.deb ...
  Unpacking libmysqlclient-dev (5.7.15-1) ...
  Selecting previously unselected package libpci3:amd64.
  Preparing to unpack .../04-libpci3_1%3a3.3.1-1.1_amd64.deb ...
  Unpacking libpci3:amd64 (1:3.3.1-1.1) ...
  Selecting previously unselected package libsensors4:amd64.
  Preparing to unpack .../05-libsensors4_1%3a3.4.0-3_amd64.deb ...
  Unpacking libsensors4:amd64 (1:3.4.0-3) ...
  Selecting previously unselected package libwrap0:amd64.
  Preparing to unpack .../06-libwrap0_7.6.q-25_amd64.deb ...
  Unpacking libwrap0:amd64 (7.6.q-25) ...
  Selecting previously unselected package libsnmp-base.
  Preparing to unpack .../07-libsnmp-base_5.7.3+dfsg-1.5_all.deb ...
  Unpacking libsnmp-base (5.7.3+dfsg-1.5) ...
  Selecting previously unselected package libsnmp30:amd64.
  Preparing to unpack .../08-libsnmp30_5.7.3+dfsg-1.5+b1_amd64.deb ...
  Unpacking libsnmp30:amd64 (5.7.3+dfsg-1.5+b1) ...
  Selecting previously unselected package libwrap0-dev:amd64.
  Preparing to unpack .../09-libwrap0-dev_7.6.q-25_amd64.deb ...
  Unpacking libwrap0-dev:amd64 (7.6.q-25) ...
  Selecting previously unselected package libssl-dev:amd64.
  Preparing to unpack .../10-libssl-dev_1.0.2j-1_amd64.deb ...
  Unpacking libssl-dev:amd64 (1.0.2j-1) ...
  Selecting previously unselected package libsensors4-dev.
  Preparing to unpack .../11-libsensors4-dev_1%3a3.4.0-3_amd64.deb ...
  Unpacking libsensors4-dev (1:3.4.0-3) ...
  Selecting previously unselected package libudev-dev:amd64.
  Preparing to unpack .../12-libudev-dev_231-9_amd64.deb ...
  Unpacking libudev-dev:amd64 (231-9) ...
  Selecting previously unselected package libpci-dev.
  Preparing to unpack .../13-libpci-dev_1%3a3.3.1-1.1_amd64.deb ...
  Unpacking libpci-dev (1:3.3.1-1.1) ...
  Selecting previously unselected package libsnmp-dev.
  Preparing to unpack .../14-libsnmp-dev_5.7.3+dfsg-1.5+b1_amd64.deb ...
  Unpacking libsnmp-dev (5.7.3+dfsg-1.5+b1) ...
  Selecting previously unselected package help2man.
  Preparing to unpack .../15-help2man_1.47.4_amd64.deb ...
  Unpacking help2man (1.47.4) ...
  Setting up mysql-common (5.8+1.0.0) ...
  update-alternatives: using /etc/mysql/my.cnf.fallback to provide 
/etc/mysql/my.cnf (my.cnf) in auto mode
  Processing triggers for libc-bin (2.24-5) ...
  Setting up help2man (1.47.4) ...
  Setting up libsensors4:amd64 (1:3.4.0-3) ...
  Processing triggers for man-db (2.7.5-1) ...
  Setting up libmysqlclient20:amd64 (5.7.15-1) ...
  Setting up libpci3:amd64 (1:3.3.1-1.1) ...
  Setting up libudev-dev:amd64 (231-9) ...
  Setting up libwrap0:amd64 (7.6.q-25) ...
  Setting up zlib1g-dev:amd64 (1:1.2.8.dfsg-2+b1) ...
  Setting up libsnmp-base (5.7.3+dfsg-1.5) ...
  Setting up libsnmp30:amd64 (5.7.3+dfsg-1.5+b1) ...
  Setting up libmysqlclient-dev (5.7.15-1) ...
  Setting up libwrap0-dev:amd64 (7.6.q-25) ...
  Setting up libssl-dev:amd64 (1.0.2j-1) ...
  Setting up libsensors4-dev (1:3.4.0-3) ...
  Setting up libpci-dev (1:3.3.1-1.1) ...
  Setting up libsnmp-dev (5.7.3+dfsg-1.5+b1) ...
  Setting up cacti-spine-build-deps (0.8.8h-1) ...
  Processing triggers for libc-bin (2.24-5) ...
  
  
**
  ** Environment
  **
  
**
  
  
PATH=/home/lamby/git/projects/dotfiles/dotfiles/..//bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
  HOSTNAME=988541d05689
  TERM=xterm
  PAGER=more
  DISPLAY=:0
  DOCKER_IMAGE=lamby-debian-sid
  DEB_BUILD_OPTIONS=parallel=9
  PIP_DOWNLOAD_CACHE=/home/lamby/.cache/pip
  HOME=/home/lamby
  LOGNAME=lamby
  SHLVL=1
  
PWD=/home/lamby/temp/cdt.20161019163212.J91Hw9gpQ6.db.cacti-spine/cacti-spine-0.8.8h
  OLDPWD=/home/lamby/temp/cdt.20161019163212.J91Hw9gpQ6.db.cacti-spine
  GPG_TTY=/dev/console
  QUILT_PATCHES=debian/patches
  QUILT_NO_DIFF_INDEX=1
  QUILT_REFRESH_ARGS=-p ab --no-timestamps --no-index
  DEBEMAIL=la...@debian.org
  DEBFULLNAME=Chris Lamb
  EDITOR=vim
  LESS=-cgiFx4M
  GPG_KEY=1E953E27D4311E58
  BLASTER=A220 I5 D1 H5 P330 T6
  _=/usr/bin/env
  
  
**
  ** Building cacti-spine 0.8.8h-1 on amd64 
  **
  
**
  
   dpkg-buildpackage -rfakeroot -D -us -uc -b
  dpkg-buildpackage: 

Processed: tag as pending

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tag 839791 pending
Bug #839791 [src:qtcreator] qtcreator: builds with clang support on armel
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: Re: node-define-property: FTBFS: Error: Cannot find module 'wrappy'

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> affects 841274 node-collection-visit node-component-emitter 
> node-copy-descriptor node-extend-shallow node-has-values node-isobject 
> node-map-visit node-repeat-element
Bug #841274 [src:node-define-property] node-define-property: FTBFS: Error: 
Cannot find module 'wrappy'
Added indication that 841274 affects node-collection-visit, 
node-component-emitter, node-copy-descriptor, node-extend-shallow, 
node-has-values, node-isobject, node-map-visit, and node-repeat-element
> thanks
Stopping processing here.

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

Processed: Re: Bug#840329: taglib-extras: FTBFS: CMake Error at cmake/modules/FindTaglib.cmake:132 (message): Could not find Taglib

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #840329 [src:taglib-extras] taglib-extras: FTBFS: CMake Error at 
cmake/modules/FindTaglib.cmake:132 (message):   Could not find Taglib
Added tag(s) patch.

-- 
840329: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840329
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems