Bug#818787: Mass Bug Filing: Missing Build-Depends: graphviz

[Bas Wijnen]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Sun, Mar 20, 2016 at 08:07:55PM +0100, Adam Borowski wrote:
> On Sun, Mar 20, 2016 at 06:51:23PM +, Bas Wijnen wrote:
> > That also means that programs calling dot will need graphviz in their
> > Build-Depends, no matter what the default is.
> 
> As is, a number of them do call dot without the build-dependency.

Yes, so that's a bug in those programs, not in doxygen.  It would be "fixed" by
adding graphviz as a Depends to doxygen, but that would be incorrect.

> > > The disappoining moral for this is that nobody looks at their build 
> > > logs...
> > 
> > I don't think that's disappointing at all!  It means we have built a system
> > that will let us know when something is wrong.
> 
> That would be the case if doxygen propagated the error, which it does not.

And that _is_ a bug in doxygen, IMO.  If it cannot produce the requested
output, it should abort with an error.

Thanks,
Bas
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJW74DXAAoJEJzRfVgHwHE6jBIP/RbYo/q85gRUI5YIyEwAETF0
RLpIWDvWFvJRhg9TGfVA3VfeAmLrsOG59V6cwuszObY1I1VX1NVpJi1RoUTiZ9O2
d7l3boQ8YRb8ll3e49LLsfHoIWw6Tp30KjbrrvsOWjH/18NDZkEK89uXFzK+/U8/
kDMADNsFvpo6/5MzSp59LSn7+YvKKuOOSypkPR2K1DzYhCL8lPno3lq8lCX6uAz/
oXjwIuFMR1KNJx/pxL9DeM+bP+9qwe0xQlL48C7kuGzvyT0ZF2gofETtlHvAbrQe
Mg3y7EbBKU6hNLi7hs9KqI8G9h+9FuyI5jeyNv0ixQQrtbDWlY8j2LBOQbwBGnNO
PeSQ0e+HmcRQgPCqBcysGxmCfTpJmfS+lAC5Q3ip62sVHIQzot/GnQBUBVZLUi2W
JGBF+JJirQ33cIw8v67Uguy4GO3/ba/I+NZFKug4poPvskmuVhMJHB0gU5Nr3mL0
Sn3dC54mzPtQk6Eq8oace9hZl39v3dHhWG/Oce/dL8sKhwkIUhc19LGk/mc0aHCQ
FC2bTVLMeCM3ZjCso1piXA10WeD5JFK2hg4B4sQCtbePQLfWXTsLsKSkNdEWqpU3
NeEeMtVaQwyMV0WRQD5JKSoClpTSsQf7cF+c+U3IKVOhkZJpwh8TKUQASo9f6Ywe
Rj66EyyM2s72+7qVxS9Z
=fTpp
-END PGP SIGNATURE-

Bug#818844: marked as done (gridengine-{common, client}: fails to upgrade from 'sid' - trying to overwrite /usr/share/man/man3/jsv_script_interface.3.gz, /usr/lib/gridengine/gethostbyaddr /usr/lib/gri

[Debian Bug Tracking System]

Your message dated Mon, 21 Mar 2016 02:49:59 +
with message-id 
and subject line Bug#818844: fixed in gridengine 8.1.8+dfsg-3
has caused the Debian Bug report #818844,
regarding gridengine-{common, client}: fails to upgrade from 'sid' - trying to 
overwrite /usr/share/man/man3/jsv_script_interface.3.gz, 
/usr/lib/gridengine/gethostbyaddr /usr/lib/gridengine/qrsh_starter
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.)


-- 
818844: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818844
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gridengine-common,gridengine-client
Version: 8.1.8+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package gridengine-common.
  Preparing to unpack .../gridengine-common_8.1.8+dfsg-1_all.deb ...
  Unpacking gridengine-common (8.1.8+dfsg-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/gridengine-common_8.1.8+dfsg-1_all.deb (--unpack):
   trying to overwrite '/usr/share/man/man3/jsv_script_interface.3.gz', which 
is also in package gridengine-drmaa-dev 6.2u5-7.4

  Selecting previously unselected package gridengine-client.
  Preparing to unpack .../gridengine-client_8.1.8+dfsg-1_amd64.deb ...
  Unpacking gridengine-client (8.1.8+dfsg-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/gridengine-client_8.1.8+dfsg-1_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/gridengine/gethostbyaddr', which is also in 
package gridengine-master 6.2u5-7.4

  Selecting previously unselected package gridengine-client.
  Preparing to unpack .../gridengine-client_8.1.8+dfsg-1_amd64.deb ...
  Unpacking gridengine-client (8.1.8+dfsg-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/gridengine-client_8.1.8+dfsg-1_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/gridengine/qrsh_starter', which is also in 
package gridengine-exec 6.2u5-7.4


cheers,

Andreas


gridengine-drmaa-dev=6.2u5-7.4_gridengine-common=8.1.8+dfsg-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: gridengine
Source-Version: 8.1.8+dfsg-3

We believe that the bug you reported is fixed in the latest version of
gridengine, 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 818...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Afif Elghraoui  (supplier of updated gridengine 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: Sun, 20 Mar 2016 19:38:41 -0700
Source: gridengine
Binary: gridengine-common gridengine-client gridengine-qmon gridengine-master 
gridengine-exec gridengine-drmaa1.0 libdrmaa1.0-java libdrmaa1.0-java-doc 
gridengine-drmaa-dev libdrmaa1.0-ruby
Architecture: source
Version: 8.1.8+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Grid Engine Maintainers 

Changed-By: Afif Elghraoui 
Description:
 gridengine-client - Utilities for Grid Engine queue management
 gridengine-common - Distributed resource management - common files
 gridengine-drmaa-dev - Distributed resource management Application API library 
- develop
 gridengine-drmaa1.0 - Distributed resource management Application API library
 gridengine-exec - Distributed resource management - Execution Server
 gridengine-master - Distributed resource management - Master Server
 gridengine-qmon - Graphical utilities for Grid Engine queue management
 libdrmaa1.0-java - Distributed resource management Application API library - 
Java bi
 libdrmaa1.0-java-doc - Distributed resource management Application API library 
- Java bi
 libdrmaa1.0-ruby - Distributed 

Bug#818857: metview: FTBFS: debian/build/share/metview/etc/ObjectListAll: cannot open [No such file or directory] metview: EXIT on ERROR (line 1)

[Chris Lamb]

Source: metview
Version: 4.6.1-5
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,

metview fails to build from source in unstable/amd64:

  [..]

   creating Metview user directories in /tmp/metview...
   creating sample drawers
   created !
  
/home/lamby/temp/cdt.20160321101640.544LpJl4fm/metview-4.6.1/debian/build/bin/metview[879]:
 .: 
/home/lamby/temp/cdt.20160321101640.544LpJl4fm/metview-4.6.1/debian/build/share/metview/etc/ObjectListAll:
 cannot open [No such file or directory]
  metview: EXIT on ERROR (line 1), exit status 1, starting 'cleanup'
  share/metview/etc/CMakeFiles/macro_built_in_functions.dir/build.make:67: 
recipe for target 'share/metview/etc/macro_built_in_functions.txt' failed
  make[3]: *** [share/metview/etc/macro_built_in_functions.txt] Error 1
  make[3]: Leaving directory 
'/home/lamby/temp/cdt.20160321101640.544LpJl4fm/metview-4.6.1/debian/build'
  CMakeFiles/Makefile2:5398: recipe for target 
'share/metview/etc/CMakeFiles/macro_built_in_functions.dir/all' failed
  make[2]: *** [share/metview/etc/CMakeFiles/macro_built_in_functions.dir/all] 
Error 2
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20160321101640.544LpJl4fm/metview-4.6.1/debian/build'
  Makefile:163: recipe for target 'all' failed
  make[1]: *** [all] Error 2
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160321101640.544LpJl4fm/metview-4.6.1/debian/build'
  dh_auto_build: make -j1 returned exit code 2
  debian/rules:35: recipe for target 'build' failed
  make: *** [build] Error 2

  [..]

The full build log is attached.


Regards,

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


metview.4.6.1-5.unstable.amd64.log.txt.gz
Description: Binary data

Processed: notfixed 813078 in 0.4.8-2+b1, found 813078 in 0.4.8-2, tagging 813078

[Debian Bug Tracking System]

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

> # unconfuse the bts - it does not understand binNMUs and having no found 
> version makes this afhis affect (old)stable as well
> notfixed 813078 0.4.8-2+b1
Bug #813078 {Done: Richard Hartmann } 
[libghc-network-protocol-xmpp-dev] git-annex: FTBFS: libgnutls-deb0.so.28: 
cannot open shared object file: No such file or directory
Bug #814055 {Done: Richard Hartmann } 
[libghc-network-protocol-xmpp-dev] has broken binding to libgnutls-deb0.so.28
No longer marked as fixed in versions 0.4.8-2+b1.
No longer marked as fixed in versions 0.4.8-2+b1.
> found 813078 0.4.8-2
Bug #813078 {Done: Richard Hartmann } 
[libghc-network-protocol-xmpp-dev] git-annex: FTBFS: libgnutls-deb0.so.28: 
cannot open shared object file: No such file or directory
Bug #814055 {Done: Richard Hartmann } 
[libghc-network-protocol-xmpp-dev] has broken binding to libgnutls-deb0.so.28
Marked as found in versions haskell-network-protocol-xmpp/0.4.8-2.
Marked as found in versions haskell-network-protocol-xmpp/0.4.8-2.
> tags 813078 + sid
Bug #813078 {Done: Richard Hartmann } 
[libghc-network-protocol-xmpp-dev] git-annex: FTBFS: libgnutls-deb0.so.28: 
cannot open shared object file: No such file or directory
Bug #814055 {Done: Richard Hartmann } 
[libghc-network-protocol-xmpp-dev] has broken binding to libgnutls-deb0.so.28
Added tag(s) sid.
Added tag(s) sid.
> thanks
Stopping processing here.

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

Processed: tagging 816719, tagging 818412

[Debian Bug Tracking System]

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

> tags 816719 + sid stretch
Bug #816719 [src:chealpix] chealpix: FTBFS on mips: timed out
Added tag(s) stretch and sid.
> tags 818412 + sid stretch
Bug #818412 {Done: Prach Pongpanich } [debpear] Please adapt 
code for the PHP 7.0 transition
Added tag(s) sid and stretch.
> thanks
Stopping processing here.

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

Bug#818365: marked as done (libgnuradio-osmosdr0.1.4: Links to libboost 1.58 and libboost 1.54 libraries. 1.54 is not available)

[Debian Bug Tracking System]

Your message dated Mon, 21 Mar 2016 01:11:26 +0100
with message-id <56ef3c2e.1020...@student.uni-luebeck.de>
and subject line Bug#818365: Acknowledgement (libgnuradio-osmosdr0.1.4: Links 
to libboost 1.58 and libboost 1.54 libraries. 1.54 is not available)
has caused the Debian Bug report #818365,
regarding libgnuradio-osmosdr0.1.4: Links to libboost 1.58 and libboost 1.54 
libraries. 1.54 is not available
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.)


-- 
818365: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818365
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgnuradio-osmosdr0.1.4
Version: 0.1.4-8
Severity: grave
Justification: renders package unusable

Dear Maintainer,

libgnuradio-osmosdr seems to link to an old version of libboost that
isn't available anymore and is not in the dependencies. This breaks
everything in gnuradio that is using osmosdr components. I verified that
I don't use an old version by accident. Attached you'll find the ldd
output on my system.

Regards
  Janosch Rux

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

Kernel: Linux 4.3.0-1-amd64 (SMP w/4 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 libgnuradio-osmosdr0.1.4 depends on:
ii  libairspy01.0.7-1
ii  libbladerf1   0.2016.01~rc1-3
ii  libboost-system1.58.0 1.58.0+dfsg-5+b1
ii  libboost-thread1.58.0 1.58.0+dfsg-5+b1
ii  libc6 2.21-9
ii  libgcc1   1:5.3.1-11
ii  libgnuradio-blocks3.7.9   3.7.9.1-1
ii  libgnuradio-fcd3.7.9  3.7.9.1-1
ii  libgnuradio-fcdproplus0   3.7.24.cf5db38-5
ii  libgnuradio-iqbalance00.37.2-5
ii  libgnuradio-pmt3.7.9  3.7.9.1-1
ii  libgnuradio-runtime3.7.9  3.7.9.1-1
ii  libgnuradio-uhd3.7.9  3.7.9.1-1
ii  libhackrf02015.07.2-6
ii  libmirisdr0   0.0.4.59ba37-4
ii  libosmosdr0   0.1.8.effcaa7-5
ii  librtlsdr00.5.3-5
ii  libstdc++65.3.1-11
ii  libuhd003 3.9.2-1

libgnuradio-osmosdr0.1.4 recommends no packages.

libgnuradio-osmosdr0.1.4 suggests no packages.

-- no debconf information
linux-vdso.so.1 (0x7ffc1a3f)
libboost_thread.so.1.58.0 => 
/usr/lib/x86_64-linux-gnu/libboost_thread.so.1.58.0 (0x7eff83da4000)
libboost_system.so.1.58.0 => 
/usr/lib/x86_64-linux-gnu/libboost_system.so.1.58.0 (0x7eff83ba)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7eff83982000)
libgnuradio-runtime.so.3.7.9 => 
/usr/lib/x86_64-linux-gnu/libgnuradio-runtime.so.3.7.9 (0x7eff83683000)
libgnuradio-pmt.so.3.7.9 => 
/usr/lib/x86_64-linux-gnu/libgnuradio-pmt.so.3.7.9 (0x7eff8343)
libgnuradio-blocks.so.3.7.9 => 
/usr/lib/x86_64-linux-gnu/libgnuradio-blocks.so.3.7.9 (0x7eff82f45000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7eff82d3d000)
libgnuradio-iqbalance.so.0 => 
/usr/lib/x86_64-linux-gnu/libgnuradio-iqbalance.so.0 (0x7eff82b29000)
libosmosdr.so.0 => /usr/lib/x86_64-linux-gnu/libosmosdr.so.0 
(0x7eff82923000)
libgnuradio-fcd.so.3.7.9 => 
/usr/lib/x86_64-linux-gnu/libgnuradio-fcd.so.3.7.9 (0x7eff8270b000)
libgnuradio-fcdproplus.so.0 => 
/usr/lib/x86_64-linux-gnu/libgnuradio-fcdproplus.so.0 (0x7eff824f6000)
librtlsdr.so.0 => /usr/lib/librtlsdr.so.0 (0x7eff822e7000)
libgnuradio-uhd.so.3.7.9 => 
/usr/lib/x86_64-linux-gnu/libgnuradio-uhd.so.3.7.9 (0x7eff82098000)
libuhd.so.003 => /usr/lib/libuhd.so.003 (0x7eff81a57000)
libmirisdr.so.0 => /usr/lib/x86_64-linux-gnu/libmirisdr.so.0 
(0x7eff81851000)
libhackrf.so.0 => /usr/lib/libhackrf.so.0 (0x7eff8164d000)
libbladeRF.so.1 => /usr/lib/x86_64-linux-gnu/libbladeRF.so.1 
(0x7eff8141c000)
libairspy.so.0 => /usr/lib/x86_64-linux-gnu/libairspy.so.0 
(0x7eff81214000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 
(0x7eff80e99000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7eff80b94000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x7eff8097d000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7eff805d9000)
/lib64/ld-linux-x86-64.so.2 (0x55d492f53000)
libvolk.so.1.1 => 

Bug#818844: gridengine-{common, client}: fails to upgrade from 'sid' - trying to overwrite /usr/share/man/man3/jsv_script_interface.3.gz, /usr/lib/gridengine/gethostbyaddr /usr/lib/gridengine/qrsh_sta

[Andreas Beckmann]

Package: gridengine-common,gridengine-client
Version: 8.1.8+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package gridengine-common.
  Preparing to unpack .../gridengine-common_8.1.8+dfsg-1_all.deb ...
  Unpacking gridengine-common (8.1.8+dfsg-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/gridengine-common_8.1.8+dfsg-1_all.deb (--unpack):
   trying to overwrite '/usr/share/man/man3/jsv_script_interface.3.gz', which 
is also in package gridengine-drmaa-dev 6.2u5-7.4

  Selecting previously unselected package gridengine-client.
  Preparing to unpack .../gridengine-client_8.1.8+dfsg-1_amd64.deb ...
  Unpacking gridengine-client (8.1.8+dfsg-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/gridengine-client_8.1.8+dfsg-1_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/gridengine/gethostbyaddr', which is also in 
package gridengine-master 6.2u5-7.4

  Selecting previously unselected package gridengine-client.
  Preparing to unpack .../gridengine-client_8.1.8+dfsg-1_amd64.deb ...
  Unpacking gridengine-client (8.1.8+dfsg-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/gridengine-client_8.1.8+dfsg-1_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/gridengine/qrsh_starter', which is also in 
package gridengine-exec 6.2u5-7.4


cheers,

Andreas


gridengine-drmaa-dev=6.2u5-7.4_gridengine-common=8.1.8+dfsg-1.log.gz
Description: application/gzip

Bug#818426: marked as done (kfreebsd-10: CVE-2016-1885: incorrect argument validation in sysarch(2))

[Debian Bug Tracking System]

Your message dated Sun, 20 Mar 2016 23:25:31 +
with message-id 
and subject line Bug#818426: fixed in kfreebsd-10 10.3~svn296998-1
has caused the Debian Bug report #818426,
regarding kfreebsd-10: CVE-2016-1885: incorrect argument validation in 
sysarch(2)
to be marked as done.

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

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


-- 
818426: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818426
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:kfreebsd-10
Version: 10.1~svn274115-4+kbsd8u2
Severity: grave
Tags: upstream patch

A local unprivileged user could trigger a kernel panic or DoS attack
on kfreebsd-amd64 via sysarch(2) sysctls:

https://security.freebsd.org/advisories/FreeBSD-SA-16:15.sysarch.asc

This affects kfreebsd-10, and also kfreebsd-9 in wheezy.

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

Kernel: kFreeBSD 10.1-0-amd64
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
Source: kfreebsd-10
Source-Version: 10.3~svn296998-1

We believe that the bug you reported is fixed in the latest version of
kfreebsd-10, 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 818...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Steven Chamberlain  (supplier of updated kfreebsd-10 
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: Sat, 19 Mar 2016 20:49:47 +
Source: kfreebsd-10
Binary: kfreebsd-source-10.3 kfreebsd-headers-10.3-0 
kfreebsd-image-10.3-0-amd64 kfreebsd-image-10-amd64 
kfreebsd-headers-10.3-0-amd64 kfreebsd-headers-10-amd64 
kernel-image-10.3-0-amd64-di nic-modules-10.3-0-amd64-di 
nic-wireless-modules-10.3-0-amd64-di nic-shared-modules-10.3-0-amd64-di 
serial-modules-10.3-0-amd64-di usb-serial-modules-10.3-0-amd64-di 
ppp-modules-10.3-0-amd64-di cdrom-modules-10.3-0-amd64-di 
scsi-core-modules-10.3-0-amd64-di scsi-modules-10.3-0-amd64-di 
scsi-extra-modules-10.3-0-amd64-di plip-modules-10.3-0-amd64-di 
floppy-modules-10.3-0-amd64-di loop-modules-10.3-0-amd64-di 
ipv6-modules-10.3-0-amd64-di nls-core-modules-10.3-0-amd64-di 
ext2-modules-10.3-0-amd64-di isofs-modules-10.3-0-amd64-di 
reiserfs-modules-10.3-0-amd64-di fat-modules-10.3-0-amd64-di 
zfs-modules-10.3-0-amd64-di nfs-modules-10.3-0-amd64-di 
nullfs-modules-10.3-0-amd64-di md-modules-10.3-0-amd64-di 
parport-modules-10.3-0-amd64-di nic-usb-modules-10.3-0-amd64-di
 sata-modules-10.3-0-amd64-di acpi-modules-10.3-0-amd64-di 
i2c-modules-10.3-0-amd64-di crypto-modules-10.3-0-amd64-di 
crypto-dm-modules-10.3-0-amd64-di mmc-core-modules-10.3-0-amd64-di 
mmc-modules-10.3-0-amd64-di sound-modules-10.3-0-amd64-di 
zlib-modules-10.3-0-amd64-di kfreebsd-image-10.3-0-486 kfreebsd-image-10-486 
kfreebsd-headers-10.3-0-486 kfreebsd-headers-10-486 kfreebsd-image-10.3-0-686 
kfreebsd-image-10-686 kfreebsd-headers-10.3-0-686 kfreebsd-headers-10-686 
kfreebsd-image-10.3-0-xen kfreebsd-image-10-xen kfreebsd-headers-10.3-0-xen 
kfreebsd-headers-10-xen kernel-image-10.3-0-486-di nic-modules-10.3-0-486-di 
nic-wireless-modules-10.3-0-486-di nic-shared-modules-10.3-0-486-di 
serial-modules-10.3-0-486-di usb-serial-modules-10.3-0-486-di 
ppp-modules-10.3-0-486-di cdrom-modules-10.3-0-486-di 
scsi-core-modules-10.3-0-486-di scsi-modules-10.3-0-486-di 
scsi-extra-modules-10.3-0-486-di plip-modules-10.3-0-486-di 
floppy-modules-10.3-0-486-di
 loop-modules-10.3-0-486-di ipv6-modules-10.3-0-486-di 
nls-core-modules-10.3-0-486-di ext2-modules-10.3-0-486-di 
isofs-modules-10.3-0-486-di reiserfs-modules-10.3-0-486-di 
fat-modules-10.3-0-486-di zfs-modules-10.3-0-486-di nfs-modules-10.3-0-486-di 
nullfs-modules-10.3-0-486-di md-modules-10.3-0-486-di 
parport-modules-10.3-0-486-di nic-usb-modules-10.3-0-486-di 
sata-modules-10.3-0-486-di acpi-modules-10.3-0-486-di i2c-modules-10.3-0-486-di 
crypto-modules-10.3-0-486-di crypto-dm-modules-10.3-0-486-di 
mmc-core-modules-10.3-0-486-di mmc-modules-10.3-0-486-di 

Processed: bug 817929 is forwarded to https://github.com/mobile-shell/mosh/issues/727

[Debian Bug Tracking System]

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

> forwarded 817929 https://github.com/mobile-shell/mosh/issues/727
Bug #817929 [mosh] mosh fails to connect, giving a UDP error
Set Bug forwarded-to-address to 
'https://github.com/mobile-shell/mosh/issues/727'.
> thanks
Stopping processing here.

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

Bug#818787: doxygen: Changes default HAVE_DOT to YES without having graphviz in the Depends line.

[Santiago Vila]

I believe the attached patch is closer to the "right" fix.

Presumably, packages actually requiring the dot command will have an
override for this variable in their Doxyfiles.

Thanks.--- a/src/config.xml
+++ b/src/config.xml
@@ -3104,7 +3104,7 @@ where `loc1` and `loc2` can be relative or absolute paths 
or URLs.
 
   
   
-
+
   
 

Bug#818787: doxygen: Changes default HAVE_DOT to YES without having graphviz in the Depends line.

[Santiago Vila]

Note 2: The easy fix does not necessariñy have to be the right fix.

As Bas Wijnen points out in -devel:

> If the program can be used without it, it should not be a Depends.  That's 
> what
> Recommends are for.

Bug#818841: openhpiclient.conf in libopenhpi2 and libopenhpi3

[Martin Michlmayr]

Package: openhpi
Version: 3.6.1-1
Severity: serious

Preparing to unpack .../libopenhpi3_3.6.1-1_arm64.deb ...
Unpacking libopenhpi3 (3.6.1-1) ...
dpkg: error processing archive 
/var/cache/apt/archives/libopenhpi3_3.6.1-1_arm64.deb (--unpack):
 trying to overwrite '/etc/openhpi/openhpiclient.conf', which is also in 
package libopenhpi2 2.14.1-1.4+b1
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Preparing to unpack .../libopenhpi-dev_3.6.1-1_arm64.deb ...

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise

Bug#815485: marked as done ([geneweb] Geneweb 6.x should not be compiled with OCAML >=4.02 (build dependency problem))

[Debian Bug Tracking System]

Your message dated Sun, 20 Mar 2016 21:20:42 +
with message-id 
and subject line Bug#815485: fixed in geneweb 6.08+git20160228+dfsg-1
has caused the Debian Bug report #815485,
regarding [geneweb] Geneweb 6.x should not be compiled with OCAML >=4.02 (build 
dependency problem)
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.)


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

Package: geneweb
Version: 6.08dfsg-5
Severity: important

--- Please enter the report below this line. ---

Debian 6.x should not be compiled with OCAML >=4.02 (the current OCAML 
version in Stretch and Sid), as it causes problem like this:

- https://groups.yahoo.com/neo/groups/geneweb/conversations/messages/6557
- https://groups.yahoo.com/neo/groups/geneweb/conversations/messages/6560
- http://i63.tinypic.com/2aifuyu.jpg
Example : " Married%t to [: 26 July 1813, St. Mary, Kingsclere, ] 
Deborah Foster ca 1795-ca 1857 ( "


Even if release 6.08dfsg-5 seems to have solved the problem compilation 
with OCAML <=4.01 (for gwc2), the binaries distributed in Stretch and 
Sid are currently unusable.


To my best knowledge, the only upstream geneweb version that can be 
compiled with OCAML>=4.02 is this "fork" of the development code for 
Geneweb 7.00 : https://github.com/geneweb/geneweb


The geneweb version in Jessie is OK, since it is built using OCAML 4.01.0

--- System information. ---
Architecture: amd64
Kernel: Linux 3.16.0-4-amd64

Debian Release: 8.3
700 stable security.debian.org
700 stable ftp.ca.debian.org
600 unstable ftp.ca.debian.org
500 stable-updates ftp.ca.debian.org
100 jessie-backports ftp.ca.debian.org

--- Package information. ---
Depends (Version) | Installed
=-+-===
libc6 (>= 2.7) | 2.19-18+deb8u3
perl5-base |
lsb-base (>= 3.0-6) | 4.1+Debian13+nmu1


Package's Recommends field is empty.

Suggests (Version) | Installed
==-+-===
gwtp |
gwsetup | 6.08dfsg-5
lynx |
OR www-browser |
--- End Message ---
--- Begin Message ---
Source: geneweb
Source-Version: 6.08+git20160228+dfsg-1

We believe that the bug you reported is fixed in the latest version of
geneweb, 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 815...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Guillaume Brochu (Lévis,Québec,Canada)  (supplier 
of updated geneweb 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: Sun, 13 Mar 2016 11:37:55 -0400
Source: geneweb
Binary: geneweb gwtp gwsetup geneweb-gui
Architecture: source i386
Version: 6.08+git20160228+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Christian Perrier 
Changed-By: Guillaume Brochu (Lévis,Québec,Canada) 
Description:
 geneweb- genealogy software with web interface
 geneweb-gui - graphical user interface to Geneweb genealogy software
 gwsetup- utilities to configure and manipulate Geneweb databases
 gwtp   - web interface interacting with Geneweb databases
Closes: 815485 815528
Changes:
 geneweb (6.08+git20160228+dfsg-1) unstable; urgency=medium
 .
   * Team upload
 .
   [ Guillaume Brochu ]
   * New upstream release to fix compatibility problems with OCAML >=4.02
 
https://github.com/geneweb/geneweb/archive/f658e5836554624435b9e46b75c9b2ac0ac61029.tar.gz
 https://github.com/geneweb/geneweb/commits/distrib-6-08-ocaml-4-xx
 (Last commit : 2016-02-28)
 https://github.com/geneweb/geneweb/issues/9
 Thanks to Fabien/Ipfix for the preparation of this special version.
 Closes: #815485
 Closes: #815528
   * Add ocaml-findlib to Build-Depends to benefit from changes in configure
 .
   [ Christian Perrier ]
   * Bump debhelper compatibility level to 9 (no real change)
   * Bump Standards to 3.9.7 (checked, no change needed)
   * Do not define GPL-2 twice in debian/copyright
   * Adapt copyright lines for debian/*
Checksums-Sha1:
 ab4f232461a3890c63f897795db42b11fd422996 2218 

Processed: Re: #754851: int too large / paramiko upstream 353

[Debian Bug Tracking System]

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

> severity 754851 grave
Bug #754851 [python-paramiko] paramiko fails with int too long exception on 
32bit systems
Severity set to 'grave' from 'normal'
> found 754851 1.15.1-1
Bug #754851 [python-paramiko] paramiko fails with int too long exception on 
32bit systems
Marked as found in versions paramiko/1.15.1-1.
> fixed 754851 1.15.3-1
Bug #754851 [python-paramiko] paramiko fails with int too long exception on 
32bit systems
Marked as fixed in versions paramiko/1.15.3-1.
> retitle 754851 paramiko fails with int too long or returns broken filenames
Bug #754851 [python-paramiko] paramiko fails with int too long exception on 
32bit systems
Changed Bug title to 'paramiko fails with int too long or returns broken 
filenames' from 'paramiko fails with int too long exception on 32bit systems'
> thanks
Stopping processing here.

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

Bug#818787: Mass Bug Filing: Missing Build-Depends: graphviz

[Adam Borowski]

On Sun, Mar 20, 2016 at 06:51:23PM +, Bas Wijnen wrote:
> That also means that programs calling dot will need graphviz in their
> Build-Depends, no matter what the default is.

As is, a number of them do call dot without the build-dependency.

> > But this is inconsistent with having graphviz in the Suggests line for
> > doxygen.
> 
> I agree that if it is the default, it should be Recommends, not Suggests.  
> This
> doesn't change anything for the problem you're describing, however.
> 
> > The disappoining moral for this is that nobody looks at their build logs...
> 
> I don't think that's disappointing at all!  It means we have built a system
> that will let us know when something is wrong.

That would be the case if doxygen propagated the error, which it does not.

> That means we don't need to poll for errors, because they will be pushed
> to us.  (I think porters are still doing this manually at least some of
> the time; I think FTBFS bugs should be reported automatically.)
> 
> In other words, my solution to this bug would be to make doxygen exit with an
> error code when calling dot fails.  Then make will fail, it's an FTBFS, it 
> gets
> fixed, and everyone is happy.

I've started a rebuild of all 552 packages in unstable that build-depend on
doxygen or anything that recursively pulls doxygen (eclipse-eclox doxyqml
doxygen-latex doxygen-gui doxygen-dbg python3-breathe python-breathe).
My build environment has a /usr/bin/dot that aborts the build when called,
which should detect this error even if doxygen output is redirected or
mangled.  I'll let you know how widespread the FTBFS are when finished.

On a slow-ass machine, 57 builds done in 2.5 hours so far, so it'll take a
while.

-- 
A tit a day keeps the vet away.

Bug#813480: marked as done (shibboleth-sp2: B-D on obsolete libsystemd-daemon-dev, switch to libsystemd-dev)

[Debian Bug Tracking System]

Your message dated Sun, 20 Mar 2016 18:52:54 +
with message-id 
and subject line Bug#813480: fixed in shibboleth-sp2 2.5.6+dfsg1-1
has caused the Debian Bug report #813480,
regarding shibboleth-sp2: B-D on obsolete libsystemd-daemon-dev, switch to 
libsystemd-dev
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.)


-- 
813480: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813480
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: shibboleth-sp2
Version: 2.5.5+dfsg1-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

your package recently added a B-D on the obsolete libsystemd-daemon-dev,
please switch to libsystemd-dev instead.


Andreas
--- End Message ---
--- Begin Message ---
Source: shibboleth-sp2
Source-Version: 2.5.6+dfsg1-1

We believe that the bug you reported is fixed in the latest version of
shibboleth-sp2, 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 813...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ferenc Wágner  (supplier of updated shibboleth-sp2 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: Fri, 11 Mar 2016 16:19:29 +0100
Source: shibboleth-sp2
Binary: libapache2-mod-shib2 libshibsp6v5 libshibsp-plugins libshibsp-dev 
libshibsp-doc shibboleth-sp2-common shibboleth-sp2-utils
Architecture: source amd64 all
Version: 2.5.6+dfsg1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Shib Team 
Changed-By: Ferenc Wágner 
Description:
 libapache2-mod-shib2 - Federated web single sign-on system (Apache module)
 libshibsp-dev - Federated web single sign-on system (development)
 libshibsp-doc - Federated web single sign-on system (API docs)
 libshibsp-plugins - Federated web single sign-on system (plugins)
 libshibsp6v5 - Federated web single sign-on system (runtime)
 shibboleth-sp2-common - Federated web single sign-on system (common files)
 shibboleth-sp2-utils - Federated web single sign-on system (daemon and 
utilities)
Closes: 813480
Changes:
 shibboleth-sp2 (2.5.6+dfsg1-1) unstable; urgency=medium
 .
   * [60fd776] Replace obsolete libsystemd-daemon-dev B-D with libsystemd-dev
 (Closes: #813480)
   * [9dbea00] Move doxygen and graphviz into Build-Depends-Indep
   * [2dabf1d] Use systemd on Linux only
   * [f46e4ac] Rename files via dh-exec, now that we use it anyway
   * [36e1b4c] Let dh_fixperms make shib-keygen executable
   * [d90b945] New patch Add-Documentation-key-to-shibd-service-file.patch
   * [3e6b865] Install the Apache module by dh_install
   * [94c2670] Upstream version 2.5.6+dfsg1
   * [469e9f2] Remove two upstreamed patches, update the rest
   * [0047c9a] Update Standards-Version to 3.9.7 (no changes needed)
   * [cd08c31] Fix fallout from dh-exec migration
Checksums-Sha1:
 bbaaa8789dddc58ea7e4f357064826a19e179ea5 2496 shibboleth-sp2_2.5.6+dfsg1-1.dsc
 3f0f0c75c24c9526c0dab4a4ed8c259ca292ebc8 574388 
shibboleth-sp2_2.5.6+dfsg1.orig.tar.xz
 5a6e3ce781f44e756f42133c7f102702f49eb1d0 66604 
shibboleth-sp2_2.5.6+dfsg1-1.debian.tar.xz
 2718e144721357fbd1b18b04862433ade5aa8e4f 290162 
libapache2-mod-shib2-dbgsym_2.5.6+dfsg1-1_amd64.deb
 63af1c144cb85bc21306143243a01b69fc3175e4 64636 
libapache2-mod-shib2_2.5.6+dfsg1-1_amd64.deb
 b7e49bf71d0052f6983afa6fe938e67c38aa4d42 54326 
libshibsp-dev_2.5.6+dfsg1-1_amd64.deb
 b66a95e49f3ebe5d7066964489cc6328b36620f1 313292 
libshibsp-doc_2.5.6+dfsg1-1_all.deb
 9a663e25ec24677aa5ffc53587ce9041bce8c099 1947814 
libshibsp-plugins-dbgsym_2.5.6+dfsg1-1_amd64.deb
 3f6643ac459916d2ccd9aa0f635cf0bbf949dc04 156062 
libshibsp-plugins_2.5.6+dfsg1-1_amd64.deb
 28c8e75048bc1be9fca8f393a547907e7cd4d7d3 17615160 
libshibsp6v5-dbgsym_2.5.6+dfsg1-1_amd64.deb
 7e71fbe5cee45e4a56a76e6645a08de76dee398e 848322 
libshibsp6v5_2.5.6+dfsg1-1_amd64.deb
 29c1aae81d2ba969997b5943fcdcbe17d954c95b 44618 
shibboleth-sp2-common_2.5.6+dfsg1-1_all.deb
 91537f63a1d398af81d16769b4511b250fe00bef 399400 
shibboleth-sp2-utils-dbgsym_2.5.6+dfsg1-1_amd64.deb
 

Bug#818787: Mass Bug Filing: Missing Build-Depends: graphviz

[Bas Wijnen]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

I think you are mistaken about a few things.

On Sun, Mar 20, 2016 at 06:04:55PM +0100, Santiago Vila wrote:
> The maintainer points out that the default value for HAVE_DOT is NO,
> so he's reluctant to add the build-dependency.

If the program can be used without it, it should not be a Depends.  That's what
Recommends are for.  Default values have nothing to do with it; Depends are for
things that will make the program unusable if they aren't present, Recommends
are for things that should almost always be installed with the program.

That also means that programs calling dot will need graphviz in their
Build-Depends, no matter what the default is.

> But this is inconsistent with having graphviz in the Suggests line for
> doxygen.

I agree that if it is the default, it should be Recommends, not Suggests.  This
doesn't change anything for the problem you're describing, however.

> The disappoining moral for this is that nobody looks at their build logs...

I don't think that's disappointing at all!  It means we have built a system
that will let us know when something is wrong.  That means we don't need to
poll for errors, because they will be pushed to us.  (I think porters are still
doing this manually at least some of the time; I think FTBFS bugs should be
reported automatically.)

In other words, my solution to this bug would be to make doxygen exit with an
error code when calling dot fails.  Then make will fail, it's an FTBFS, it gets
fixed, and everyone is happy.

Thanks,
Bas
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJW7vEqAAoJEJzRfVgHwHE6Gm4QAKAhBvdYk+2kTZ6SKTjgH/B0
4OIBO8nSOJe+O5yTB3AordZq2zZS1afM0oWB3JiVfa6l6Ka9dfC8f9TOlvW5xGnm
pj0OO7b7jrH5oK5XToqj3DvDphNKpNwWnHKbeBWlJY779SVBa50kdwnbtg77wa5k
ZBl1NWLFlFeRgjbG6BQpn1l50NyRLMzTumLFtF+rpZACAwoiH+bkJVDlu83lfM72
/B4WLl9G7wxnhwhtfs2PcvRaYF8EzGuNDizu2PbwCp31CKUszF4+0q9JiqHtTwmV
VIFxB31fSU/RpmEIxI086wStd/Rax+Cn8HfAyTY6/tIOVBCeHYnNajWZkVEcNsoj
srsaGpPEGJouGr/MLqQIk5n6LLsiERq4aha5WpmccmgkNCxTIUXZlU62J6y5DzlT
lDkG5NXkEuf1qsk9bUJQEAbvdCKfbX6mtlbibxtGlSpeZ6LwfsQ+M9MoX300kH84
UYHMovo6M9CHXLdxt9AJOVBJTbERXbKVysnrov2pVlZSZiPFu7M/haz6Um13Vsku
AlIpYRYpfTRiNZ/dg1Tf0AtnMkSIqhy1441Jj+Egpe9EXAs9GfWaYNOa1yZYm1d8
1Wcbh0NdzakVDNmTWuPg47bGt7IOGUcgM74DQuRLCWxcaOOnErs0nI7+3x3kZ+5/
77few9WmaB+ZHhDWb+Vv
=AU0O
-END PGP SIGNATURE-

Bug#812646: cpluff: FTBFS - macro "cpi_lock_framework" passed 1 arguments, but takes just 0

[Balint Reczey]

Control: severity -1 normal
Control: tags -1 moreinfo

Hi Michael,

On Mon, 25 Jan 2016 17:45:56 + Michael Tautschnig  wrote:
> Package: cpluff
> Version: 0.1.3-3
> Severity: serious
> Usertags: goto-cc
> 
> During a rebuild of all Debian packages in a clean sid chroot (using 
> cowbuilder
> and pbuilder) the build failed with the following error.
> 
> [...]
> /bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -I..  
>  -Wdate-time -I.. -I../libcpluff -I../libcpluff -DNDEBUG -I. 
> -DCP_C_API=CP_EXPORT -DCP_HOST="\"x86_64-pc-linux-gnu\"" 
> -DCP_DATADIR="\"/usr/share\""  -g -O0 -fstack-protector-strong -Wformat 
> -Werror=format-security -c -o cpluff.lo cpluff.c
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -I.. 
> -I../libcpluff -I../libcpluff -DNDEBUG -I. -DCP_C_API=CP_EXPORT 
> -DCP_HOST=\"x86_64-pc-linux-gnu\" -DCP_DATADIR=\"/usr/share\" -g -O0 
> -fstack-protector-strong -Wformat -Werror=format-security -c cpluff.c  -fPIC 
> -DPIC -o .libs/cpluff.o
> cpluff.c:80:39: error: macro "cpi_lock_framework" passed 1 arguments, but 
> takes just 0
>  CP_HIDDEN void cpi_lock_framework(void) {
>^
> cpluff.c:80:41: error: expected '=', ',', ';', 'asm' or '__attribute__' 
> before '{' token
>  CP_HIDDEN void cpi_lock_framework(void) {
>  ^
> cpluff.c:88:41: error: macro "cpi_unlock_framework" passed 1 arguments, but 
> takes just 0
>  CP_HIDDEN void cpi_unlock_framework(void) {
>  ^
> cpluff.c:88:43: error: expected '=', ',', ';', 'asm' or '__attribute__' 
> before '{' token
>  CP_HIDDEN void cpi_unlock_framework(void) {
>^
> Makefile:535: recipe for target 'cpluff.lo' failed
> make[4]: *** [cpluff.lo] Error 1
> 
> 
> The full build log is attached; please do let me know if the problem is
> unreproducible, in which case I shall try to investigate further.
It looks like the POSIX threading is not detected properly in your build
environment but is detected on every buildd using sbuild.
I decrease the severity of the bug report because FTBFS does not occur
on any official buildd and it looks like a problem in goto-cc.

Cheers,
Balint

Processed: Re: cpluff: FTBFS - macro "cpi_lock_framework" passed 1 arguments, but takes just 0

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #812646 [cpluff] cpluff: FTBFS - macro "cpi_lock_framework" passed 1 
arguments, but takes just 0
Severity set to 'normal' from 'serious'
> tags -1 moreinfo
Bug #812646 [cpluff] cpluff: FTBFS - macro "cpi_lock_framework" passed 1 
arguments, but takes just 0
Added tag(s) moreinfo.

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

Bug#818797: haskell-shake: FTBFS on powerpc: timed out

[Emilio Pozuelo Monfort]

Source: haskell-shake
Version: 0.15.5+dfsg-4
Severity: serious

Your package failed to build on powerpc:

## FINISHED TESTING directory
## BUILD docs test
## TESTING docs
## BUILD docs --abbrev=output=$OUT -j3
# runhaskell (for $OUT/docs/dist/setup-config)
Configuring shake-0.15.5...
E: Caught signal ‘Terminated’: terminating immediately
make: *** wait: No child processes.  Stop.
make: *** Waiting for unfinished jobs
make: *** wait: No child processes.  Stop.
Build killed with signal TERM after 150 minutes of inactivity

Full logs at:

https://buildd.debian.org/status/logs.php?pkg=haskell-shake=0.15.5%2Bdfsg-4%2Bb1=powerpc

Emilio

Bug#818757: Bug#818757: orthanc-postgresql: does not start

[Karsten Hilbert]

On Sun, Mar 20, 2016 at 06:55:50PM +0100, Andreas Tille wrote:

> > > Have you added the "--upgrade" option so that Orthanc would automatically 
> > > upgrade the database schema?
> 
> I wonder whether this should be done in a postinst script.

Only if the database upgrade does not make a difference with
respect to client connectivity. Hence - for Orthanc this may
work (DICOM and REST access stay the same) while for GNUmed
this would not work AT ALL.

Karsten
-- 
GPG key ID E4071346 @ eu.pool.sks-keyservers.net
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346

Bug#816999: marked as done (presage: Build-Depends: swig2.0 (>= 2.0.4) but it is not installable in stretch)

[Debian Bug Tracking System]

Your message dated Sun, 20 Mar 2016 17:52:50 +
with message-id 
and subject line Bug#816999: fixed in presage 0.9.1-2
has caused the Debian Bug report #816999,
regarding presage: Build-Depends: swig2.0 (>= 2.0.4) but it is not installable 
in stretch
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.)


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

Dear maintainer:

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

But the failure is build-depends related, so it has nothing to do
with the fact that I was doing "dpkg-buildpackage -A", hence
the serious severity.


[...]
Installing build dependencies
Reading package lists...
Building dependency tree...
Reading state information...
The following NEW packages will be installed:
  sbuild-build-depends-core-dummy
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/770 B of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 file:/<>/resolver-i22sqO/apt_archive ./ 
sbuild-build-depends-core-dummy 0.invalid.0 [770 B]
debconf: delaying package configuration, since apt-utils is not installed
Selecting previously unselected package sbuild-build-depends-core-dummy.
(Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 14574 files and directories currently installed.)
Preparing to unpack .../sbuild-build-depends-core-dummy.deb ...
Unpacking sbuild-build-depends-core-dummy (0.invalid.0) ...
Setting up sbuild-build-depends-core-dummy (0.invalid.0) ...
W: No sandbox user '_apt' on the system, can not drop privileges
Merged Build-Depends: debhelper (>= 9~), autotools-dev, dh-autoreconf, 
pkg-config, libsqlite3-dev, sqlite3, libtinyxml-dev (>= 2.5.3), libncurses5-dev 
| libncurses-dev, help2man, libcppunit-dev (>= 1.9.6), python-all-dev (>= 
2.6.6-3~), swig2.0 (>= 2.0.4), libgtk2.0-dev (>= 2.12), python-dbus, 
python-wxgtk3.0, doxygen, graphviz
Filtered Build-Depends: debhelper (>= 9~), autotools-dev, dh-autoreconf, 
pkg-config, libsqlite3-dev, sqlite3, libtinyxml-dev (>= 2.5.3), libncurses5-dev 
| libncurses-dev, help2man, libcppunit-dev (>= 1.9.6), python-all-dev (>= 
2.6.6-3~), swig2.0 (>= 2.0.4), libgtk2.0-dev (>= 2.12), python-dbus, 
python-wxgtk3.0, doxygen, graphviz
dpkg-deb: building package 'sbuild-build-depends-presage-dummy' in 
'/<>/resolver-y_vejs/apt_archive/sbuild-build-depends-presage-dummy.deb'.
OK
Get:1 file:/<>/resolver-y_vejs/apt_archive ./ InRelease
Ign:1 file:/<>/resolver-y_vejs/apt_archive ./ InRelease
Get:2 file:/<>/resolver-y_vejs/apt_archive ./ Release [2119 B]
Get:2 file:/<>/resolver-y_vejs/apt_archive ./ Release [2119 B]
Get:3 file:/<>/resolver-y_vejs/apt_archive ./ Release.gpg [299 B]
Get:3 file:/<>/resolver-y_vejs/apt_archive ./ Release.gpg [299 B]
Get:4 file:/<>/resolver-y_vejs/apt_archive ./ Sources [366 B]
Get:5 file:/<>/resolver-y_vejs/apt_archive ./ Packages [672 B]
Reading package lists...
W: No sandbox user '_apt' on the system, can not drop privileges
Reading package lists...

+--+
| Install presage build dependencies (apt-based resolver)  |
+--+

Installing build dependencies
Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 sbuild-build-depends-presage-dummy : Depends: swig2.0 (>= 2.0.4) but it is not 
installable
E: 

Bug#818757: Bug#818757: orthanc-postgresql: does not start

[Andreas Tille]

On Sun, Mar 20, 2016 at 06:09:15PM +0100, Karsten Hilbert wrote:
> > 
> > Have you added the "--upgrade" option so that Orthanc would automatically 
> > upgrade the database schema?

I wonder whether this should be done in a postinst script.
 
> Also, would Debian benefit from an
> 
>   /usr/sbin/orthanc_upgrade
> 
> script which calls /usr/sbin/Orthanc --upgrade plus other options ?

That's the minimum I guess to make things simple for the user.

Kind regards

Andreas. 

-- 
http://fam-tille.de

Bug#818787: doxygen: Changes default HAVE_DOT to YES without having graphviz in the Depends line.

[Santiago Vila]

Note: The changelog says (year 2000) graphviz is in the Suggests
because it was non-free, which clearly is not the case anymore.

So, the easy fix for this bug is to move graphviz to the Depends line
(see the attached patch).

(Well, easy, but even after this, we would still have to rebuild all
the affected packages).

Thanks.--- a/debian/control
+++ b/debian/control
@@ -30,8 +30,8 @@ XS-Testsuite: autopkgtest
 Package: doxygen
 Architecture: any
 Multi-Arch: foreign
-Depends: ${shlibs:Depends}, ${misc:Depends}
-Suggests: doxygen-latex, doxygen-doc, doxygen-gui, graphviz
+Depends: ${shlibs:Depends}, ${misc:Depends}, graphviz
+Suggests: doxygen-latex, doxygen-doc, doxygen-gui
 Conflicts: graphviz (<< 1.12)
 Description: Documentation system for C, C++, Java, Python and other languages
  Doxygen is a documentation system for C, C++, Java, Objective-C, Python, IDL

Bug#818741: pulseaudio-module-x11: repeatable intermittent driver working

[Felipe Sateler]

Control: tags -1 important

On 20 March 2016 at 07:55, Richard Jasmin  wrote:
> Package: pulseaudio-module-x11
> Version: 5.0-13
> Severity: grave
> Tags: upstream
> Justification: renders package unusable
>
> Dear Maintainer,
>
> we have an issue. Because I know for a fact snd hda intel aka alc889 is
> fully supported at this time.kernel not only recognizes the hardware but so
> does the sound daemon.
>
> YET...
>
> either pulse is tripping acid hard or we have a more serious issue with the
> kernel driver that is going un unnoticed.THIS HARDWARE IS FULLY SUPPORTED.
>
> some days it wants to work, some days not.
> fldigi will punch out audio but heaven forbid I want to play musicnothing.
> Its not the app and the music seems to be all the way up.
>
> pulse reports "dummy audio" and no hda intel internal hardware. alsa says
> differently. not only does my 7850s have hdmi out on multiple channels but the
> ATI SB internal shows up too.
>
> YET...
>
> aplay a file and NOTHINGmy speakers are all the way up. NOTHING OUT.I
> should be waking my neighbors at this point.
>
> this needs to be addressed ASAP. Not having working audio is reason enough to
> ditch linux.And I dont want to ditch ANY Linux.
> I DONT WANT SIN. SIN is too vulnerable.

I don't understand you. Could you please try to explain again? Also,
please include a verbose log from pulseaudio[1], everything in
/etc/pulse/, and the output of the commands `aplay -L` and `pactl
info`

Also please describe when does the sound disappear, and what are you
doing at that point.

[1]https://wiki.ubuntu.com/PulseAudio/Log

Bug#818757: [Debian-med-packaging] Bug#818757: orthanc-postgresql: does not start

[Karsten Hilbert]

On Sun, Mar 20, 2016 at 05:55:10PM +0100, Sébastien Jodogne wrote:

> > 4) the existing orthanc_db is 0.8 and the jump is to Orthanc 1.0 (orthanc-pg
> > 2.0)
> 
> Have you added the "--upgrade" option so that Orthanc would automatically 
> upgrade the database schema?

I now did run Orthanc with --upgrade and it crashes with the
same error.

Karsten
-- 
GPG key ID E4071346 @ eu.pool.sks-keyservers.net
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346

Bug#818757: [Debian-med-packaging] Bug#818757: orthanc-postgresql: does not start

[Karsten Hilbert]

On Sun, Mar 20, 2016 at 05:55:10PM +0100, Sébastien Jodogne wrote:

> > 4) the existing orthanc_db is 0.8 and the jump is to Orthanc 1.0 (orthanc-pg
> > 2.0)
> 
> Have you added the "--upgrade" option so that Orthanc would automatically 
> upgrade the database schema?

I have not because

- it's not really me calling /usr/bin/Orthanc but /etc/init.d/orthanc
  (I only copied that call manually in order to get more information)

- I didn't know that option existed

- I would not have guessed that adding --upgrade might have made
  a difference to a failure that tells me "stack smashing detected"
  at the console :-)

- I knew from past experience that Orthanc auto-upgraded the schema
  (but that was on SQLite and from major to major w/o a version skip)

However, I will now add this option and report back.

Would you mind adding a line to the log indicating that
--upgrade might be needed when Orthanc detects that situation
at startup ?

Also, would Debian benefit from an

/usr/sbin/orthanc_upgrade

script which calls /usr/sbin/Orthanc --upgrade plus other options ?

Karsten
-- 
GPG key ID E4071346 @ eu.pool.sks-keyservers.net
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346

Bug#818787: doxygen: Changes default HAVE_DOT to YES without having graphviz in the Depends line.

[Santiago Vila]

Package: doxygen
Version: 1.8.11-1
Severity: serious

Hello again Matthias.

If packages having a "Build-Depends: doxygen" may assume that
graphviz is installed, then doxygen should have a line like this:

Depends: graphviz

Currently, this is only a Suggests.

If, on the other side, packages having a "Build-Depends: doxygen" may
not assume that graphviz is installed, then doxygen should respect the
default upstream value for HAVE_DOT which is NO.

Currently, this is changed in debian/patches/dot-config.diff
to 1, i.e. YES, which according to documentation it means
"doxygen will assume the dot tool is available from the path".


The current status where doxygen believes that dot is installed but
does not enforce it with a Depends line makes a lot of packages to
generate incorrect documentation, which combined with #818379 makes a
lot of packages already in the archive to be actually incorrect.

In fact, I was going to report a lot of bugs about packages
not having a Build-Depends: graphviz, but then I read this report:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778478

where I found about the HAVE_DOT variable.

I'm setting this to serious because it breaks a lot of packages.


Thanks.

Bug#818757: [Debian-med-packaging] Bug#818757: orthanc-postgresql: does not start

[Sébastien Jodogne]

Hello,

> 4) the existing orthanc_db is 0.8 and the jump is to Orthanc 1.0 (orthanc-pg
> 2.0)

Have you added the "--upgrade" option so that Orthanc would automatically 
upgrade the database schema?

Sébastien-

Bug#818715: marked as done (ros-image-common: FTBFS on several architectures: relocation R_X86_64_PC32 against symbol `_ZTVN7testing8internal17TestEventRepeaterE' can not be used when making a shared

[Debian Bug Tracking System]

Your message dated Sun, 20 Mar 2016 16:38:04 +
with message-id 
and subject line Bug#818715: fixed in ros-image-common 1.11.10-5
has caused the Debian Bug report #818715,
regarding ros-image-common: FTBFS on several architectures: relocation 
R_X86_64_PC32 against symbol `_ZTVN7testing8internal17TestEventRepeaterE' can 
not be used when making a shared object; recompile with -fPIC
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.)


-- 
818715: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818715
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ros-image-common
Version: 1.11.10-4
Severity: serious

Your package failed to build on several architectures:

/usr/bin/ld: CMakeFiles/gtest.dir/src/gtest-all.cc.o: relocation R_X86_64_PC32 
against symbol `_ZTVN7testing8internal17TestEventRepeaterE' can not be used 
when making a shared object; recompile with -fPIC
/usr/bin/ld: final link failed: Bad value
collect2: error: ld returned 1 exit status

It looks as if that file was compiled with -fPIC though:

cd /«PKGBUILDDIR»/obj-x86_64-linux-gnu/gtest && /usr/bin/c++   
-DGTEST_CREATE_SHARED_LIBRARY=1 -Dgtest_EXPORTS -I/usr/src/gtest/include 
-I/usr/src/gtest  -g -O2 -fPIE -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  -fPIC   -g -O2 -fPIE 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2  -Wall -Wshadow -DGTEST_HAS_PTHREAD=1 -fexceptions -Wextra 
-Wno-unused-parameter -Wno-missing-field-initializers -o 
CMakeFiles/gtest.dir/src/gtest-all.cc.o -c /usr/src/gtest/src/gtest-all.cc

On ppc64el the error is a bit different, but it also points to -fPIC so the
problem is likely the same:

/usr/bin/c++  -fPIC -g -O2 -fPIE -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2   -fPIE -pie 
-Wl,-z,relro -Wl,-z,now -shared -Wl,-soname,libgtest.so -o libgtest.so 
CMakeFiles/gtest.dir/src/gtest-all.cc.o  
-L/«PKGBUILDDIR»/obj-powerpc64le-linux-gnu/gtest/src -lpthread 
-Wl,-rpath,/«PKGBUILDDIR»/obj-powerpc64le-linux-gnu/gtest/src 
/usr/bin/ld: CMakeFiles/gtest.dir/src/gtest-all.cc.o: In function 
`testing::internal::FormatCxxExceptionMessage(char const*, char const*)':
/usr/src/gtest/src/gtest.cc:2030:(.text.unlikely+0x80): call to 
`testing::Message::Message()' lacks nop, can't restore toc; recompile with -fPIC
/usr/bin/ld: CMakeFiles/gtest.dir/src/gtest-all.cc.o: In function 
`testing::Message::GetString[abi:cxx11]() const':
/usr/src/gtest/src/gtest.cc:947:(.text.unlikely+0x150): call to 
`testing::internal::StringStreamToString(std::__cxx11::basic_stringstream*)' lacks nop, can't restore toc; 
recompile with -fPIC
/usr/bin/ld: final link failed: Bad value
collect2: error: ld returned 1 exit status

Full logs at:
https://buildd.debian.org/status/logs.php?pkg=ros-image-common=1.11.10-4

Cheers,
Emilio
--- End Message ---
--- Begin Message ---
Source: ros-image-common
Source-Version: 1.11.10-5

We believe that the bug you reported is fixed in the latest version of
ros-image-common, 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 818...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Mattia Rizzolo  (supplier of updated ros-image-common 
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: Sun, 20 Mar 2016 16:16:08 +
Source: ros-image-common
Binary: libcamera-calibration-parsers-dev libcamera-calibration-parsers0d 
camera-calibration-parsers-tools python-camera-calibration-parsers 
libcamera-info-manager-dev libcamera-info-manager0d libimage-transport-dev 
libimage-transport0d image-transport-tools libpolled-camera-dev 
libpolled-camera0d polled-camera-tool python-polled-camera cl-polled-camera
Architecture: source
Version: 1.11.10-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Mattia Rizzolo 
Description:
 camera-calibration-parsers-tools - Robot OS 

Bug#818069: marked as done (influxdb: FTBFS in stretch)

[Debian Bug Tracking System]

Your message dated Sun, 20 Mar 2016 16:20:15 +
with message-id 
and subject line Bug#818069: fixed in influxdb 0.10.2+dfsg1-2
has caused the Debian Bug report #818069,
regarding influxdb: FTBFS in stretch
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.)


-- 
818069: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818069
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:influxdb
Version: 0.10.0+dfsg1-1
Severity: serious

Dear maintainer: This package fails to build from source in stretch.

I'd love to say something about why it fails, but I really don't know.

The full build log is attached.

Thanks.

influxdb_0.10.0+dfsg1-1_amd64-20160313-1047.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: influxdb
Source-Version: 0.10.2+dfsg1-2

We believe that the bug you reported is fixed in the latest version of
influxdb, 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 818...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Alexandre Viau  (supplier of updated influxdb 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: SHA1

Format: 1.8
Date: Sun, 20 Mar 2016 11:11:21 -0400
Source: influxdb
Binary: golang-github-influxdb-influxdb-dev influxdb-dev influxdb 
influxdb-client
Architecture: source all amd64
Version: 0.10.2+dfsg1-2
Distribution: unstable
Urgency: medium
Maintainer: Alexandre Viau 
Changed-By: Alexandre Viau 
Description:
 golang-github-influxdb-influxdb-dev - Scalable datastore for metrics, events, 
and real-time analytics.
 influxdb   - Scalable datastore for metrics, events, and real-time analytics
 influxdb-client - command line interface for InfluxDB
 influxdb-dev - Transitional package for golang-github-influxdb-influxdb-dev
Closes: 818069
Changes:
 influxdb (0.10.2+dfsg1-2) unstable; urgency=medium
 .
   * Temporarly disable tests (Closes: #818069)
Checksums-Sha1:
 34f9bd5ae3f8d669eaa1105b33647520089f 3227 influxdb_0.10.2+dfsg1-2.dsc
 3792ea4dc774870fe469f935c7db6135135e7dba 120888 
influxdb_0.10.2+dfsg1-2.debian.tar.xz
 cc141850e50fb5d8351e163344d0fcef66ae85a6 730558 
golang-github-influxdb-influxdb-dev_0.10.2+dfsg1-2_all.deb
 b066706cf3b9d950e9d9fec42f0b84e5951d6fe3 2084810 
influxdb-client_0.10.2+dfsg1-2_amd64.deb
 b1c909c9558432d7f3537ad8cf95fd27be46cc31 36970 
influxdb-dev_0.10.2+dfsg1-2_all.deb
 70ce1d7238144c9d9a65063772cfff6bc29da9a4 3198082 
influxdb_0.10.2+dfsg1-2_amd64.deb
Checksums-Sha256:
 3d1e11a7552015278a1db3c7ef68f76e9cca2df7011bc5ce82ad71e966700389 3227 
influxdb_0.10.2+dfsg1-2.dsc
 77713991b71616a69b42e5f8f12562d38a989029e2ff7cd0fd4b5c5535750206 120888 
influxdb_0.10.2+dfsg1-2.debian.tar.xz
 0d657eb701b2dd7399edc0f4ce88774f62dfa423a339418cba4147032e697c6f 730558 
golang-github-influxdb-influxdb-dev_0.10.2+dfsg1-2_all.deb
 58ae56100a25a6bbc4a5f91c38e284f63eaff0f489c3a2baed1ad14ec0899251 2084810 
influxdb-client_0.10.2+dfsg1-2_amd64.deb
 7bc79fb89148d16dd574689637789b1078d6ab6cc4f6b02937d0037cc9ae131b 36970 
influxdb-dev_0.10.2+dfsg1-2_all.deb
 e37005077dc34811f9a5b2018f688b3d55038156c16f6c14eaee4c5da2bde318 3198082 
influxdb_0.10.2+dfsg1-2_amd64.deb
Files:
 8e9d36f2d056de91eaf2f4506f5fc21e 3227 database extra 
influxdb_0.10.2+dfsg1-2.dsc
 3b4e6cff32049987d3fc450a7a0222fe 120888 database extra 
influxdb_0.10.2+dfsg1-2.debian.tar.xz
 e17d098cc38fa97a972f2e95ce9c30f3 730558 database extra 
golang-github-influxdb-influxdb-dev_0.10.2+dfsg1-2_all.deb
 a2761fe16f88c8bc9175fb8cc173adf7 2084810 database extra 
influxdb-client_0.10.2+dfsg1-2_amd64.deb
 4d69d3025bf89b770579aaec87591bcf 36970 oldlibs extra 
influxdb-dev_0.10.2+dfsg1-2_all.deb
 61ad753975cf68e626ff9371852bb04c 3198082 database extra 
influxdb_0.10.2+dfsg1-2_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJW7sTPAAoJENqCgw48zDo65EAQAMtH4mQuRQpZje45M4fALau5
tRtirZnu+QOlR0hnCZ5jFtEMY0zt+ueNalaB7C9ZWsUJgxfp2CR08rtYboPk4KHA
qlvgkKpuLZkiZQG0KGYBERJtTQ9d3cmlvkvoYou7EuTWpWfzTRcAdN1B3hQYeAFc
f2j3EY1dzZ2urOD1gbODVtwiabj94qf+OPsZFxbU1ii6blXVyW5cLnhTKxusdd6D

Processed: your mail

[Debian Bug Tracking System]

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

> reassign 818597 casablanca
Bug #818597 {Done: Gianfranco Costamagna } 
[libcpprest2.7] libcpprest2.7: libcpprest.so.2.7 not installed
Bug reassigned from package 'libcpprest2.7' to 'casablanca'.
No longer marked as found in versions casablanca/2.8.0-1.
No longer marked as fixed in versions 2.8.0-2.
> fixed 818597 2.8.0-2
Bug #818597 {Done: Gianfranco Costamagna } 
[casablanca] libcpprest2.7: libcpprest.so.2.7 not installed
There is no source info for the package 'casablanca' at version '2.8.0-2' with 
architecture ''
Unable to make a source version for version '2.8.0-2'
Marked as fixed in versions 2.8.0-2.
> forcemerge 818597 818588
Bug #818597 {Done: Gianfranco Costamagna } 
[casablanca] libcpprest2.7: libcpprest.so.2.7 not installed
Bug #818588 {Done: Gianfranco Costamagna } 
[casablanca] Prevent casablanca migration
Severity set to 'grave' from 'serious'
Bug #818597 {Done: Gianfranco Costamagna } 
[casablanca] libcpprest2.7: libcpprest.so.2.7 not installed
There is no source info for the package 'casablanca' at version '2.8.0-1' with 
architecture ''
Unable to make a source version for version '2.8.0-1'
Marked as found in versions 2.8.0-1.
Merged 818588 818597
> severity 818597 serious
Bug #818597 {Done: Gianfranco Costamagna } 
[casablanca] libcpprest2.7: libcpprest.so.2.7 not installed
Bug #818588 {Done: Gianfranco Costamagna } 
[casablanca] Prevent casablanca migration
Severity set to 'serious' from 'grave'
Severity set to 'serious' from 'grave'
> thanks
Stopping processing here.

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

Processed: your mail

[Debian Bug Tracking System]

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

> notfound 817872 python-clang-3.8
Bug #817872 [python-clang-3.8,python-clang-3.9] python-clang-3.9 and 
python-clang-3.8: error when trying to install together
There is no source info for the package 'python-clang-3.8' at version 
'python-clang-3.8' with architecture ''
There is no source info for the package 'python-clang-3.9' at version 
'python-clang-3.8' with architecture ''
Unable to make a source version for version 'python-clang-3.8'
Ignoring request to alter found versions of bug #817872 to the same values 
previously set
> notfound 817873 python-lldb-3.8
Bug #817873 [python-lldb-3.8,python-lldb-3.9] python-lldb-3.9 and 
python-lldb-3.8: error when trying to install together
There is no source info for the package 'python-lldb-3.8' at version 
'python-lldb-3.8' with architecture ''
There is no source info for the package 'python-lldb-3.9' at version 
'python-lldb-3.8' with architecture ''
Unable to make a source version for version 'python-lldb-3.8'
Ignoring request to alter found versions of bug #817873 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#815290: marked as done (haskell-tf-random: FTBFS: dpkg-gencontrol: error: bad line in substvars file debian/libghc-tf-random-doc.substvars at line 8)

[Debian Bug Tracking System]

Your message dated Wed, 16 Mar 2016 16:13:13 +0100
with message-id <1458141193.1861.38.ca...@debian.org>
and subject line Re: haskell-haddock-library: FTBFS: dpkg-gencontrol: error: 
bad line in substvars file debian/libghc-haddock-library-doc.substvars at line 8
has caused the Debian Bug report #815290,
regarding haskell-tf-random: FTBFS: dpkg-gencontrol: error: bad line in 
substvars file debian/libghc-tf-random-doc.substvars at line 8
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.)


-- 
815290: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815290
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-tf-random
Version: 0.5-5
Severity: serious

>From my pbuilder build log:

...
dh_makeshlibs -plibghc-tf-random-doc -XlibHS 
dh_installdeb -plibghc-tf-random-doc 
dh_perl -plibghc-tf-random-doc 
dh_shlibdeps -plibghc-tf-random-doc   -XlibHS 
dh_gencontrol -plibghc-tf-random-doc  
dpkg-gencontrol: error: bad line in substvars file 
debian/libghc-tf-random-doc.substvars at line 8
dh_gencontrol: dpkg-gencontrol -plibghc-tf-random-doc -ldebian/changelog 
-Tdebian/libghc-tf-random-doc.substvars -Pdebian/libghc-tf-random-doc returned 
exit code 25
/usr/share/cdbs/1/rules/debhelper.mk:289: recipe for target 
'binary-makedeb-IMPL/libghc-tf-random-doc' failed
make: *** [binary-makedeb-IMPL/libghc-tf-random-doc] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
-- 
Daniel Schepler
--- End Message ---
--- Begin Message ---
Hi,

Am Samstag, den 12.03.2016, 07:42 + schrieb Niels Thykier:
> The fixed version of debhelper (20160306) is now in testing.  AFAICT
> this bug (and #815290) is no longer waiting for debhelper (if
> anything at all).

quite right.

Joachim

-- 
Joachim “nomeata” Breitner
Debian Developer
  nome...@debian.org • https://people.debian.org/~nomeata
  XMPP: nome...@joachim-breitner.de • GPG-Key: 0xF0FBF51F
  https://www.joachim-breitner.de/


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

Bug#809247: marked as done (xboxdrv: FTBFS: Checking for C++ library X11... no)

[Debian Bug Tracking System]

Your message dated Sun, 20 Mar 2016 15:39:21 +
with message-id 
and subject line Bug#809247: fixed in xboxdrv 0.8.8-1
has caused the Debian Bug report #809247,
regarding xboxdrv: FTBFS:  Checking for C++ library X11... no
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.)


-- 
809247: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809247
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xboxdrv
Version: 0.8.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,

xboxdrv fails to build from source in unstable/amd64:

  [..]

   dpkg-buildpackage -rfakeroot -D -us -uc -b
  dpkg-buildpackage: source package xboxdrv
  dpkg-buildpackage: source version 0.8.5-1
  dpkg-buildpackage: source distribution unstable
  dpkg-buildpackage: source changed by Andrey Rahmatullin 
   dpkg-source --before-build xboxdrv-0.8.5
  dpkg-buildpackage: host architecture amd64
   fakeroot debian/rules clean
  dh clean
 dh_testdir
 dh_auto_clean
make -j1 clean
  make[1]: Entering directory 
'/home/lamby/temp/cdt.20151228174715.Cxokh7su4k/xboxdrv-0.8.5'
  scons -c
  scons: Reading SConscript files ...
  Checking for C++ library X11... yes
  scons: done reading SConscript files.
  scons: Cleaning targets ...
  scons: done cleaning targets.
  rm -rf .sconf_temp/
  rm -f .sconsign.dblite
  rm -f config.log
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20151228174715.Cxokh7su4k/xboxdrv-0.8.5'
 dh_clean
   debian/rules build
  dh build
 dh_testdir
 dh_auto_configure
 debian/rules override_dh_auto_build
  make[1]: Entering directory 
'/home/lamby/temp/cdt.20151228174715.Cxokh7su4k/xboxdrv-0.8.5'
  scons CPPFLAGS="-Wdate-time -D_FORTIFY_SOURCE=2" CCFLAGS="-g -O2 -fPIE 
-fstack-protector-strong -Wformat -Werror=format-security" CXXFLAGS="-g -O2 
-fPIE -fstack-protector-strong -Wformat -Werror=format-security" 
LINKFLAGS="-fPIE -pie -Wl,-z,relro -Wl,-z,now"
  scons: Reading SConscript files ...
  Checking for C++ library X11... no
  libx11-dev must be installed!
  debian/rules:9: recipe for target 'override_dh_auto_build' failed
  make[1]: *** [override_dh_auto_build] Error 1
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20151228174715.Cxokh7su4k/xboxdrv-0.8.5'
  debian/rules:6: recipe for target 'build' failed
  make: *** [build] Error 2

  [..]

The full build log is attached.


Regards,

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


xboxdrv.0.8.5-1.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: xboxdrv
Source-Version: 0.8.8-1

We believe that the bug you reported is fixed in the latest version of
xboxdrv, 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 809...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andrey Rahmatullin  (supplier of updated xboxdrv 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: Sun, 20 Mar 2016 18:19:53 +0500
Source: xboxdrv
Binary: xboxdrv
Architecture: source
Version: 0.8.8-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Andrey Rahmatullin 
Description:
 xboxdrv- Xbox360 gamepad driver for the userspace
Closes: 809247
Changes:
 xboxdrv (0.8.8-1) unstable; urgency=medium
 .
   * New upstream version
   * debian/control:
 - bump Standards-Version to 3.9.7 (no change needed)
 - update Vcs-* fields
 - update my email
   * debian/copyright:
 - update my email and the copyright years
   * debian/docs:
 - update for README -> README.md rename
   * debian/patches/fix-build-flags-parsing.patch:
 - fix handling *FLAGS environment variables containing >1 flags (Closes:
   #809247), thanks to Bertrand Marc
   * debian/patches/fix-xboxdrv-manpage.patch:
 - fix new spelling problems
   * debian/rules:
 - 

Processed: retitle 817233 to brotli: CVE-2016-1624 CVE-2016-1968, tagging 817233

[Debian Bug Tracking System]

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

> retitle 817233 brotli: CVE-2016-1624 CVE-2016-1968
Bug #817233 [src:brotli] CVE-2016-1968
Changed Bug title to 'brotli: CVE-2016-1624 CVE-2016-1968' from 'CVE-2016-1968'
> tags 817233 + upstream fixed-upstream
Bug #817233 [src:brotli] brotli: CVE-2016-1624 CVE-2016-1968
Added tag(s) upstream and fixed-upstream.
> thanks
Stopping processing here.

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

Bug#818418: marked as done (goldencheetah: FTBFS: redefinition of 'int DataFilterlex_destroy()')

[Debian Bug Tracking System]

Your message dated Fri, 18 Mar 2016 00:19:36 +
with message-id 
and subject line Bug#818418: fixed in goldencheetah 3.3.0-2
has caused the Debian Bug report #818418,
regarding goldencheetah: FTBFS: redefinition of 'int DataFilterlex_destroy()'
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.)


-- 
818418: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818418
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: goldencheetah
Version: 3.3.0-1
Severity: serious

This package fails to build in unstable:

> sbuild (Debian sbuild) 0.68.0 (15 Jan 2016) on dl580gen9-02.hlinux
...
> g++ -c -m64 -pipe -g -O2 -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -W -D_REENTRANT 
> -fPIC -DGC_VIDEO_VLC -DGC_VERSION=\"3.3.0RC1\" -DGC_HAVE_KQOAUTH 
> -DGC_HAVE_QWTPLOT3D -DGC_HAVE_KML -DGC_HAVE_ICAL -DGC_HAVE_LIBUSB 
> -DGC_HAVE_VLC -DQXT_STATIC -DGC_HAVE_SOAP -DQT_NO_DEBUG -DQT_SVG_LIB 
> -DQT_WEBKITWIDGETS_LIB -DQT_MULTIMEDIAWIDGETS_LIB -DQT_OPENGL_LIB 
> -DQT_WIDGETS_LIB -DQT_WEBKIT_LIB -DQT_MULTIMEDIA_LIB -DQT_GUI_LIB 
> -DQT_XML_LIB -DQT_SQL_LIB -DQT_NETWORK_LIB -DQT_SCRIPT_LIB 
> -DQT_CONCURRENT_LIB -DQT_SERIALPORT_LIB -DQT_CORE_LIB -I. -I../qwt/src 
> -I../qxt/src -I../qtsolutions/json -I../qtsolutions/qwtcurve -I../kqoauth 
> -isystem /usr/include/qwtplot3d -isystem /usr/include -isystem 
> /usr/include/libical -isystem /usr/include -isystem /usr/include/vlc 
> -I../qtsolutions/soap -isystem /usr/include/x86_64-linux-gnu/qt5 -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtSvg -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtWebKitWidgets -isystem /us
> r/include/x86_64-linux-gnu/qt5/QtMultimediaWidgets -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtOpenGL -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtWebKit -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtMultimedia -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtXml -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtSql -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtScript -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtConcurrent -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtSerialPort -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtCore -I. 
> -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++-64 -o RideDB_lex.o 
> RideDB_lex.cpp
> lex.WithingsParser.c: In function 'int yy_get_next_buffer()':
> lex.WithingsParser.c:1229:44: warning: comparison between signed and unsigned 
> integer expressions [-Wsign-compare]
> lex.DataFilter.c: In function 'int yy_get_next_buffer()':
> lex.DataFilter.c:1483:44: warning: comparison between signed and unsigned 
> integer expressions [-Wsign-compare]
> DataFilter.l: In function 'int DataFilterlex_destroy()':
> DataFilter.l:105:5: error: redefinition of 'int DataFilterlex_destroy()'
>  #endif
>  ^
> lex.DataFilter.c:2128:5: note: 'int DataFilterlex_destroy()' previously 
> defined here
> Makefile:15206: recipe for target 'DataFilter_lex.o' failed
> make[2]: *** [DataFilter_lex.o] Error 1
> make[2]: *** Waiting for unfinished jobs
> lex.JsonRideFile.c: In function 'int yy_get_next_buffer(yyscan_t)':
> lex.JsonRideFile.c:1559:47: warning: comparison between signed and unsigned 
> integer expressions [-Wsign-compare]
> JsonRideFile.l: In function 'int JsonRideFilelex_destroy(void*)':
> JsonRideFile.l:166:5: error: redefinition of 'int 
> JsonRideFilelex_destroy(void*)'
>  #endif
>  ^
> lex.JsonRideFile.c:2358:5: note: 'int JsonRideFilelex_destroy(yyscan_t)' 
> previously defined here
> lex.RideDB.c: In function 'int yy_get_next_buffer(yyscan_t)':
> lex.RideDB.c:1290:47: warning: comparison between signed and unsigned integer 
> expressions [-Wsign-compare]
> RideDB.l: In function 'int RideDBlex_destroy(void*)':
> RideDB.l:119:5: error: redefinition of 'int RideDBlex_destroy(void*)'
>  #endif
>  ^
> lex.RideDB.c:2089:5: note: 'int RideDBlex_destroy(yyscan_t)' previously 
> defined here
> Makefile:15209: recipe for target 'JsonRideFile_lex.o' failed
> make[2]: *** [JsonRideFile_lex.o] Error 1
> Makefile:15215: recipe for target 'RideDB_lex.o' failed
> make[2]: *** [RideDB_lex.o] Error 1
> JsonRideFile.y:313:12: warning: 'jsonFileReaderRegistered' defined but not 
> used [-Wunused-variable]
>  static int jsonFileReaderRegistered =
> ^
> make[2]: Leaving directory '/<>/src'
> Makefile:130: recipe for target 'sub-src-make_first-ordered' failed

Bug#818265: Bug#818187: Bug#818265: Bug#818187: zeromq3 migrated without any transition being done

[GCS]

On Sun, Mar 20, 2016 at 12:27 PM, Julian Taylor
 wrote:
> On 20.03.2016 11:11, László Böszörményi (GCS) wrote:
>> On Sun, Mar 20, 2016 at 10:56 AM, Emilio Pozuelo Monfort
>>  wrote:
>>> Got a chance to look at this?
>>  Sorry, my life was chaotic. Yes and no, checked it. First, there's a
>> new upstream version of pyzmq (15.2) for two months. It seems to be
>> security related according to the release log[1]:
[...]
> The latest version does unfortunately not fix the problem. It is also
> not security related, it just could not send large data due to bugs in zmq.
> I guess a good approach would be to bisect zmq to see what they changed
> to cause it.
 Still any reason not to update it for Sid? Can you try Git master
branch for building? That contains several fixes.
While the same company develops ZeroMQ and the Python bindings as
well, do you have contact with their Python team? It may worth to ask
them, they may know what's the cause of the hang is.

Regards,
Laszlo/GCS

Bug#816535: marked as done (Missing dependencies)

[Debian Bug Tracking System]

Your message dated Wed, 16 Mar 2016 21:35:20 +
with message-id 
and subject line Bug#816535: fixed in botan1.10 1.10.12-1.1
has caused the Debian Bug report #816535,
regarding Missing dependencies
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.)


-- 
816535: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816535
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libbotan1.10-dev
Version: 1.10.12-1
Severity: serious

libbotan1-10-dev is missing dependencies. config requires quite a few libraries,

   $ botan-config-1.10 --libs
   -lbotan-1.10 -lbz2 -lcrypto -ldl -lgmp -lpthread -lrt -lz

but these are not listed,

Depends: libbotan-1.10-1 (= 1.10.12-1)

Please add required -dev dependencies to the -dev package.

Thanks,
Adam


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

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

Versions of packages libbotan1.10-dev depends on:
ii  libbotan-1.10-1  1.10.12-1

libbotan1.10-dev recommends no packages.

libbotan1.10-dev suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: botan1.10
Source-Version: 1.10.12-1.1

We believe that the bug you reported is fixed in the latest version of
botan1.10, 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 816...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Christian Hofstaedtler  (supplier of updated botan1.10 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: Mon, 14 Mar 2016 20:48:29 +
Source: botan1.10
Binary: botan1.10-dbg libbotan-1.10-1 libbotan1.10-dev
Architecture: source
Version: 1.10.12-1.1
Distribution: unstable
Urgency: medium
Maintainer: Ondřej Surý 
Changed-By: Christian Hofstaedtler 
Description:
 botan1.10-dbg - multiplatform crypto library (debug)
 libbotan-1.10-1 - multiplatform crypto library
 libbotan1.10-dev - multiplatform crypto library (development)
Closes: 813633 816535
Changes:
 botan1.10 (1.10.12-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Correctly disable test suite when building with nocheck (Closes: #813633)
   * Add missing dependencies to libbotan1.10-dev (Closes: #816535)
Checksums-Sha1:
 7500d0d992c55133515dec81c9d7bb1b19a8eddd 2045 botan1.10_1.10.12-1.1.dsc
 4bf6311b413cce23e6f93071c3a47259666b7113 40284 
botan1.10_1.10.12-1.1.debian.tar.xz
Checksums-Sha256:
 9957cc10eed4ef7f2de0a9e9cb9e7f002f567bb41654b3044b454215f553569c 2045 
botan1.10_1.10.12-1.1.dsc
 75897f1c187023da1703756df66bb16cff51de4f1ba895fa62edb7399ba7f925 40284 
botan1.10_1.10.12-1.1.debian.tar.xz
Files:
 5496096079556fc28314c347770338cf 2045 libs optional botan1.10_1.10.12-1.1.dsc
 93156ea5e2ace22f4c54af952c5b0b80 40284 libs optional 
botan1.10_1.10.12-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJW5yTBAAoJEFwT1tuTBS4DMz8QAI3Ep9a+ygMc6DqRj8isMW9y
AyELg2huwVVAjX8IelM7TkG2f1IC+C8j2/fOJR027fO8LAK26i2B2s18sBzY0NdO
j69Jr4N39vJ4JydbOQuyesf32BiOa1n5f8xOJx7uPqc2g4c1Q6Rk/pfQtqg3udIr
YczFeBwkJE7t0X819HqIkpysjAi5F3qKiCICAqftrKKYHgkdKdRJzvNtLI+Wzcm/
beUwdXykTPiWlGei172YdfYNrJiUoH25778vHOT2Gb2ackf+JB3fNe4t2jvjGYTq
iB1W7PK5PKYBNih5Wj8/j0WBH9Vve6Z4PLp+aox44fA3a9YR08A7inzQJdyrWr7S
5B1uGgeID9zjzRC4EaJN+5frUs0THVsT5XqcqX4uwbC2pcJdH8OEz/SW3+/RfDBK
Tx4Ami4WeJ1+gRsmof1ZVe+BUgWpVLKAzw3whYpf8fHDsvqMiP2Yk2uvGqbYq+S+
uqCOVCSLLNpZmvIk2II3JqQAVJxempVzIPtFZgmitOAb2Lz/UL4Fz2p8r+UABpwC
drvpI6+k3AFCzDAGpvV7rRpWZIFHi/HEIa2pDpXtMzLQfrX0jX+M+mG8kA0AFzGZ
+UInnKgApHxbjGQ9LrMXS5KHDcT75LsxYakNlhMqdABVstRnwrkwkA0Wt11aT13Y
CTnVxNWGZpC3itgbiO2V
=XUnd
-END PGP SIGNATURE End Message ---

Bug#818757: orthanc-postgresql: does not start

[Karsten Hilbert]

Package: orthanc-postgresql
Version: 2.0-1
Severity: grave
Tags: upstream
Justification: renders package unusable

Orthanc does not start when the backend is set to PostgreSQL.

1) I can successfully

su - orthanc
psql -d orthanc_db

2) Orthanc will start if set to using the sqlite backend

3) it worked before dist-upgrading jessie to stretch

4) the existing orthanc_db is 0.8 and the jump is to Orthanc 1.0 (orthanc-pg 
2.0)

Logs attached.

Karsten

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'stable-updates'), (500, 'unstable'), 
(500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 4.4.0-1-686-pae (SMP w/2 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 orthanc-postgresql depends on:
ii  libboost-system1.58.0  1.58.0+dfsg-5+b1
ii  libc6  2.22-3
ii  libgcc11:5.3.1-11
ii  libjsoncpp0v5  0.10.5-1
ii  libpq5 9.5.1-1
ii  libstdc++6 5.3.1-11
ii  libuuid1   2.27.1-6
ii  orthanc1.0.0+dfsg-1+b1

orthanc-postgresql recommends no packages.

Versions of packages orthanc-postgresql suggests:
ii  postgresql  9.5+172

-- Configuration Files:
/etc/orthanc/postgresql.json changed:
{
/**
 * Configuration to use PostgreSQL instead of the default SQLite
 * back-end of Orthanc. You will have to install the
 * "orthanc-postgresql" package to take advantage of this feature.
 * Have a look at "/usr/share/doc/orthanc-postgresql/README.Debian"
 * for a tutorial.
 **/
"PostgreSQL" : {
// Enable the use of PostgreSQL to store the Orthanc index?
"EnableIndex" : true,
// Enable the use of PostgreSQL to store the DICOM files?
"EnableStorage" : true,
// Option 1: Specify explicit authentication parameters
//"Host" : "localhost",
//"Port" : 5432,
//"Database" : "orthanc_db",
//"Username" : "orthanc_user",
//"Password" : "my_password",
// Option 2: Authenticate using PostgreSQL connection URI
// "ConnectionUri" : 
"postgresql://orthanc_user:my_password@localhost:5432/orthanc_db",
"ConnectionUri" : "postgresql:///orthanc_db?user=orthanc",
// Optional: Disable the locking of the PostgreSQL database
"Lock" : false
}
}


-- no debconf information
Skript gestartet auf So 20 Mär 2016 14:08:50 CET
root@hermes:~# /usr/sbin/Orthanc --trace --logdir=/var/log/orthanc /etc/orthanc/
*** stack smashing detected ***: /usr/sbin/Orthanc terminated
=== Backtrace: =
/lib/i386-linux-gnu/i686/cmov/libc.so.6(+0x692ab)[0xb691a2ab]
/lib/i386-linux-gnu/i686/cmov/libc.so.6(__fortify_fail+0x37)[0xb69a9fe7]
/lib/i386-linux-gnu/i686/cmov/libc.so.6(+0xf8fa8)[0xb69a9fa8]
/usr/share/orthanc/plugins/libOrthancPostgreSQLStorage.so(+0x11284)[0xb41fa284]
/usr/share/orthanc/plugins/libOrthancPostgreSQLStorage.so(+0xa9bf)[0xb41f39bf]
/usr/share/orthanc/plugins/libOrthancPostgreSQLStorage.so(OrthancPluginInitialize+0xab)[0xb41f9d7b]
/usr/sbin/Orthanc[0x8107c42]
/usr/sbin/Orthanc[0x8108aa3]
/usr/sbin/Orthanc[0x8107da9]
/usr/sbin/Orthanc[0x8068e48]
/lib/i386-linux-gnu/i686/cmov/libc.so.6(__libc_start_main+0xf7)[0xb68c9527]
/usr/sbin/Orthanc[0x806f2fa]
=== Memory map: 
08048000-082c9000 r-xp  08:01 12230893   /usr/sbin/Orthanc
082c9000-082ca000 r--p 0028 08:01 12230893   /usr/sbin/Orthanc
082ca000-082cb000 rw-p 00281000 08:01 12230893   /usr/sbin/Orthanc
082cb000-082cd000 rw-p  00:00 0 
0870b000-0894 rw-p  00:00 0  [heap]
b4147000-b4177000 r-xp  08:01 6898379
/usr/lib/i386-linux-gnu/libpq.so.5.8
b4177000-b4179000 r--p 0002f000 08:01 6898379
/usr/lib/i386-linux-gnu/libpq.so.5.8
b4179000-b417a000 rw-p 00031000 08:01 6898379
/usr/lib/i386-linux-gnu/libpq.so.5.8
b417a000-b41ae000 r-xp  08:01 6899772
/usr/lib/i386-linux-gnu/libjsoncpp.so.0.10.5
b41ae000-b41af000 r--p 00033000 08:01 6899772
/usr/lib/i386-linux-gnu/libjsoncpp.so.0.10.5
b41af000-b41b rw-p 00034000 08:01 6899772
/usr/lib/i386-linux-gnu/libjsoncpp.so.0.10.5
b41e9000-b420 r-xp  08:01 6283388
/usr/lib/libOrthancPostgreSQLStorage.so.2.0
b420-b4201000 r--p 00016000 08:01 6283388
/usr/lib/libOrthancPostgreSQLStorage.so.2.0
b4201000-b4202000 rw-p 00017000 08:01 6283388
/usr/lib/libOrthancPostgreSQLStorage.so.2.0
b4202000-b420b000 rw-p  00:00 0 
b420b000-b4212000 r-xp  08:01 6899295
/usr/lib/i386-linux-gnu/libffi.so.6.0.4
b4212000-b4213000 r--p 6000 08:01 6899295
/usr/lib/i386-linux-gnu/libffi.so.6.0.4
b4213000-b4214000 rw-p 7000 08:01 6899295
/usr/lib/i386-linux-gnu/libffi.so.6.0.4
b4214000-b4228000 r-xp  08:01 8151062
/lib/i386-linux-gnu/libgpg-error.so.0.17.0
b4228000-b4229000 r--p 00013000 

Bug#812087: maybe it's the yubikey ?

[Raphaël Rigo]

I'm also bitten by this bug and I'm using a Yubikey. Maybe it's related ?

My PC also has several readers.

I'll be happy to help debugging.

Raphaël

Bug#818401: tcpcrypt: FTBFS: pcap.h: No such file or directory

[Martin Michlmayr]

Package: tcpcrypt
Version: 0.4-2
Severity: serious

This package fails to build in unstable:

> sbuild (Debian sbuild) 0.68.0 (15 Jan 2016) on dl580gen9-02.hlinux
...
> gcc -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2 -I./src -I./include 
> -I./src -g -O2 -fstack-protector-strong -Wformat -Werror=format-security 
> -Wall -Wno-deprecated-declarations -c -o src/src_tcpcryptd-unix.o `test -f 
> 'src/unix.c' || echo './'`src/unix.c
> src/unix.c:23:18: fatal error: pcap.h: No such file or directory
> compilation terminated.
> Makefile:1279: recipe for target 'src/src_tcpcryptd-unix.o' failed
> make[2]: *** [src/src_tcpcryptd-unix.o] Error 1

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise

Bug#818747: courier-authdaemon: init script does not work

[Amos Jeffries]

Package: courier-authdaemon
Version: 0.66.4-5
Severity: grave


After a recent upgrade to courier-authdaemon the init scripts have
ceased controlling the daemon processes.

Producing the error :
 Unknown option '-'


NP: this is after the workaround to bug #818744 has been added to let
the init script actually run.


A full trace is included below. The lines producing this output are in
/lib/init/init-d-script:

+ start-stop-daemon --start --quiet --pidfile /run/courier/pid --startas
/usr/sbin/authdaemond --name authdaemond --exec /usr/sbin/authdaemond --test
+ start-stop-daemon --start --quiet --pidfile /run/courier/pid --startas
/usr/sbin/authdaemond --name authdaemond --exec /usr/sbin/authdaemond --
Unknown option '-'
+ return 2


The /usr/sbin/authdaemond script (aka $DAEMON) is expecting to receive
"start" or "stop", etc as its $1 parameter.

For some reason the /etc/init.d/courier-authdaemon script is ignoring
the error result from init-d-script and returning "exit 0" (success) anyway.


Running these commands manually with the extra daemon parameter works fine:

start-stop-daemon --start --quiet --pidfile /run/courier/pid --startas
/usr/sbin/authdaemond --name authdaemond --exec /usr/sbin/authdaemond --
start

start-stop-daemon --start --quiet --pidfile /run/courier/pid --startas
/usr/sbin/authdaemond --name authdaemond --exec /usr/sbin/authdaemond --
stop




The full output of "/etc/init.d/courier-authdaemon start" when -x is
added to its shell call is listed below:


# /etc/init.d/courier-authdaemon start
+ [ true !=  ]
+ set /etc/init.d/courier-authdaemon start
+ INIT_D_SCRIPT_SOURCED=true . /lib/init/init-d-script
+ . /lib/lsb/init-functions
+ run-parts --lsbsysinit --list /lib/lsb/init-functions.d
+ [ -r /lib/lsb/init-functions.d/01-upstart-lsb ]
+ . /lib/lsb/init-functions.d/01-upstart-lsb
+ unset UPSTART_SESSION
+ _RC_SCRIPT=/etc/init.d/courier-authdaemon
+ [ -r /etc/init//etc/init.d/courier-authdaemon.conf ]
+ _UPSTART_JOB=courier-authdaemon
+ [ -r /etc/init/courier-authdaemon.conf ]
+ [ -r /lib/lsb/init-functions.d/20-left-info-blocks ]
+ . /lib/lsb/init-functions.d/20-left-info-blocks
+ FANCYTTY=
+ [ -e /etc/lsb-base-logging.sh ]
+ true
+ PATH=/sbin:/usr/sbin:/bin:/usr/bin
+ export PATH
+ [  = true ]
+ SCRIPTNAME=/etc/init.d/courier-authdaemon
+ basename /etc/init.d/courier-authdaemon
+ scriptbasename=courier-authdaemon
+ [ courier-authdaemon != init-d-script ]
+ script=/etc/init.d/courier-authdaemon
+ shift
+ . /etc/init.d/courier-authdaemon
+ [ true != true ]
+ DAEMON=/usr/sbin/authdaemond
+ DESC=Courier authentication services
+ PIDFILE=/run/courier/pid
+ basename /usr/sbin/authdaemond
+ NAME=authdaemond
+ DESC=Courier authentication services
+ [ none = /run/courier/pid ]
+ [ -z /run/courier/pid ]
+ [ none != /usr/sbin/authdaemond ]
+ [ ! -x /usr/sbin/authdaemond ]
+ [ -r /etc/default/authdaemond ]
+ . /lib/init/vars.sh
+ TMPTIME=0
+ SULOGIN=no
+ DELAYLOGIN=no
+ UTC=yes
+ VERBOSE=no
+ FSCKFIX=no
+ [ -f /etc/default/rcS ]
+ . /etc/default/rcS
+ TMPTIME=0
+ SULOGIN=no
+ DELAYLOGIN=yes
+ VERBOSE=yes
+ FSCKFIX=no
+ unset EDITMOTD
+ unset RAMRUN
+ unset RAMLOCK
+ [ -r /proc/cmdline ]
+ cat /proc/cmdline
+ [  ]
+ [  ]
+ [ -t 0 ]
+ VERBOSE=yes
+ call do_start
+ cmd=do_start
+ shift
+ is_call_implemented do_start_override
+ command -V do_start_override
+ do_start
+ is_call_implemented do_start_prepare
+ command -V do_start_prepare
+ call do_start_prepare
+ cmd=do_start_prepare
+ shift
+ is_call_implemented do_start_prepare_override
+ command -V do_start_prepare_override
+ do_start_prepare
+ do_tmpfiles courier-authdaemon
+ local type path mode user group
+ TMPFILES=/usr/lib/tmpfiles.d/courier-authdaemon.conf
+ [ -r /usr/lib/tmpfiles.d/courier-authdaemon.conf ]
+ echo file: /usr/lib/tmpfiles.d/courier-authdaemon.conf
file: /usr/lib/tmpfiles.d/courier-authdaemon.conf
+ + readcat type path mode user group age arg
 /usr/lib/tmpfiles.d/courier-authdaemon.conf
+ [ #Type = d ]
+ read type path mode user group age arg
+ [ d = d ]
+ mkdir -p /run/courier
+ chmod 0775 /run/courier
+ chown root:courier /run/courier
+ [ -x /sbin/restorecon ]
+ read type path mode user group age arg
+ [ d = d ]
+ mkdir -p /run/courier/authdaemon
+ chmod 0755 /run/courier/authdaemon
+ chown courier:courier /run/courier/authdaemon
+ [ -x /sbin/restorecon ]
+ read type path mode user group age arg
+ [ yes != no ]
+ log_daemon_msg Starting Courier authentication services authdaemond
+ [ -z Starting Courier authentication services ]
+ log_daemon_msg_pre Starting Courier authentication services authdaemond
+ log_use_fancy_output
+ TPUT=/usr/bin/tput
+ EXPR=/usr/bin/expr
+ [ -t 1 ]
+ [ xxterm != x ]
+ [ xxterm != xdumb ]
+ [ -x /usr/bin/tput ]
+ [ -x /usr/bin/expr ]
+ /usr/bin/tput hpa 60
+ /usr/bin/tput setaf 1
+ [ -z ]
+ FANCYTTY=1
+ true
+ echo -n []
[] + [ -z authdaemond ]
+ echo -n Starting Courier authentication services: authdaemond
Starting Courier authentication services: authdaemond+
log_daemon_msg_post 

Processed: And yet again

[Debian Bug Tracking System]

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

> notfound 813078 haskell-network-protocol-xmpp/0.4.8-2
Bug #813078 {Done: Richard Hartmann } 
[libghc-network-protocol-xmpp-dev] git-annex: FTBFS: libgnutls-deb0.so.28: 
cannot open shared object file: No such file or directory
Bug #814055 {Done: Richard Hartmann } 
[libghc-network-protocol-xmpp-dev] has broken binding to libgnutls-deb0.so.28
No longer marked as found in versions haskell-network-protocol-xmpp/0.4.8-2.
No longer marked as found in versions haskell-network-protocol-xmpp/0.4.8-2.
> --
Stopping processing here.

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

Bug#818265: Bug#818187: Bug#818265: Bug#818187: zeromq3 migrated without any transition being done

[Julian Taylor]

On 20.03.2016 11:11, László Böszörményi (GCS) wrote:
> On Sun, Mar 20, 2016 at 10:56 AM, Emilio Pozuelo Monfort
>  wrote:
>> On Tue, 15 Mar 2016 23:37:26 +0100
>> =?UTF-8?B?TMOhc3psw7MgQsO2c3rDtnJtw6lueWkgKEdDUyk=?=  wrote:
>>> On Tue, Mar 15, 2016 at 11:24 PM, Julian Taylor
>>>  wrote:
 On 15.03.2016 22:48, László Böszörményi (GCS) wrote:
>>>  While I was checking the failing build logs, I see:
>>> build/temp.linux-armv7l-2.7/scratch/tmp/timer_createOfMQXG.o: In
>>> function `main':
>>> timer_createOfMQXG.c:(.text+0x14): undefined reference to `timer_create'
>>> collect2: error: ld returned 1 exit status
>>>
>>> It's not just the implicit declaration, but a linker error later. I
>>> can be wrong, but it seems it _may_ cause the test hang as there's no
>>> timer to look for / to wait its expiration. Sorry if it happens in
>>> normal logs as well; will check it tomorrow morning as it's almost
>>> midnight here. :(
>  Checked, it happens in normal build logs as well.
> 
>> Got a chance to look at this?
>  Sorry, my life was chaotic. Yes and no, checked it. First, there's a
> new upstream version of pyzmq (15.2) for two months. It seems to be
> security related according to the release log[1]:
> - FIX: unicode/bytes bug in password prompt in zmq.ssh on Python 3
> - workaround overflow bug in libzmq preventing receiving messages
> larger than MAX_INT
> 
> My computer is old and has problems; even the archive version hangs
> during self-tests. Still, it may help if Julian update the package to
> the latest version. With my Python Modules team member hat on, should
> I do it myself?
> Just for the record, upstream Git tree has even more fixes that not
> yet released as a new version.
> 

The latest version does unfortunately not fix the problem. It is also
not security related, it just could not send large data due to bugs in zmq.
I guess a good approach would be to bisect zmq to see what they changed
to cause it.

Bug#818318: git: CVE-2016-2324 and CVE-2016-2315 (currently unpublished) server and client RCE

[Jonathan Nieder]

On Thu, Mar 17, 2016 at 12:37:27AM +, Ben Hutchings wrote:
> On Wed, 2016-03-16 at 17:16 -0700, Jonathan Nieder wrote:
>> Ben Hutchings wrote:

>>> I intend to NMU git to fix these bugs in unstable, as they make most of
>>> my development activity unsafe.
>>>
>>> git maintainers, please let me know if you're already preparing an
>>> update.
>>
>> I'm already preparing an update.
>
> Thanks.  For what it's worth, I'm attaching my minimal fix for
> CVE-2016-2324.  All existing tests pass, but I don't have a reproducer
> for the security issue so I can't be certain it's fixed.

More patches are needed.  See 
https://git.kernel.org/cgit/git/git.git/log/?h=maint
(I mention this mostly for the sake of people backporting to stable,
testing, or oldstable.)

Bug#818525: [Pkg-xen-devel] Bug#818525: xen: FTBFS: error: unterminated comment

[Wei Liu]

On Thu, Mar 17, 2016 at 6:58 PM, Martin Michlmayr  wrote:
> Package: xen
> Version: 4.6.0-1+nmu2
> Severity: serious
>
> This package fails to build in unstable:
>
>> sbuild (Debian sbuild) 0.68.0 (15 Jan 2016) on dl580gen9-02.hlinux
> ...
>> mkdir -p compat
>> grep -v 'DEFINE_XEN_GUEST_HANDLE(long)' public/grant_table.h | \
>> python 
>> /<>/debian/build/build-hypervisor_amd64_amd64/xen/tools/compat-build-source.py
>>  >compat/grant_table.c.new
>> mv -f compat/grant_table.c.new compat/grant_table.c
>> gcc -E -O2 -fomit-frame-pointer -m64 -fno-strict-aliasing -std=gnu99 -Wall 
>> -Wstrict-prototypes -Wdeclaration-after-statement 
>> -Wno-unused-but-set-variable -Wno-unused-local-typedefs -DNDEBUG 
>> -I/<>/debian/build/build-hypervisor_amd64_amd64/xen/include 
>> -I/<>/debian/build/build-hypervisor_amd64_amd64/xen/include/asm-x86/mach-generic
>>  
>> -I/<>/debian/build/build-hypervisor_amd64_amd64/xen/include/asm-x86/mach-default
>>  -msoft-float -fno-stack-protector -fno-exceptions -Wnested-externs 
>> -DHAVE_GAS_VMX -DHAVE_GAS_EPT -DHAVE_GAS_FSGSBASE -mno-red-zone -mno-sse 
>> -fpic -fno-asynchronous-unwind-tables -DGCC_HAS_VISIBILITY_ATTRIBUTE 
>> -fno-builtin -fno-common -Werror -Wredundant-decls -Wno-pointer-arith -pipe 
>> -g -D__XEN__ -nostdinc -DCONFIG_SHADOW_PAGING -DHAS_ACPI -DHAS_GDBSX 
>> -DHAS_PASSTHROUGH -DHAS_MEM_ACCESS -DHAS_MEM_PAGING -DHAS_MEM_SHARING 
>> -DHAS_PCI -DHAS_IOPORTS -DHAS_PDX -O2 -fomit-frame-pointer -m64 
>> -fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prot
>> otypes -Wdeclaration-after-statement -Wno-unused-but-set-variable 
>> -Wno-unused-local-typedefs -include public/xen-compat.h -m32 -o 
>> compat/grant_table.i compat/grant_table.c
>> compat/grant_table.c:33:1: error: unterminated comment
>>  /*
>>  ^
>> compat/grant_table.c:28:0: error: unterminated #ifndef
>>  #ifndef __XEN_PUBLIC_GRANT_TABLE_H__
>>  ^
>> Makefile:61: recipe for target 'compat/grant_table.i' failed
>> make[5]: *** [compat/grant_table.i] Error 1
>> rm compat/features.i compat/callback.c compat/event_channel.i 
>> compat/elfnote.c compat/elfnote.i compat/features.c compat/event_channel.c 
>> compat/callback.i compat/grant_table.c
>

I think you need this patch from upstream xen.git.

commit 3f293c7caaefc2c37b61e44e8ebd5a7f1c554afb
Author: Dario Faggioli 
AuthorDate: Thu Feb 25 13:03:04 2016 +0100
Commit: Jan Beulich 
CommitDate: Thu Feb 25 13:03:04 2016 +0100

public: typo: use ' as apostrophe in grant_table.h


Wei.


> --
> Martin Michlmayr
> Linux for HPE Helion, Hewlett Packard Enterprise
>
> ___
> Pkg-xen-devel mailing list
> pkg-xen-de...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-xen-devel

Bug#815004: libengine-pkcs11-openssl: Engine is installed at wrong location (sparc64 as well)

[Anatoly Pugachev]

File path seems to be fixed in new / last version?

mator@deb4g:~$ dpkg -s libengine-pkcs11-openssl | grep Ver
Version: 0.2.1-2

mator@deb4g:~$ dpkg -L libengine-pkcs11-openssl | grep libpkcs11.so
/usr/lib/sparc64-linux-gnu/openssl-1.0.2/engines/libpkcs11.so


But still can't use pkcs11 module:

mator@deb4g:~$ openssl speed rsa2048 -engine pkcs11
Unable to load module (null)
can't use that engine
1892278191086816:error:80001401:PKCS11
library:PKCS11_CTX_load:Unable to load PKCS#11 module:p11_load.c:84:
1892278191086816:error:260B806D:engine
routines:ENGINE_TABLE_REGISTER:init failed:eng_table.c:175:
Unable to load module (null)
Doing 2048 bit private rsa's for 10s: 12687 2048 bit private RSA's in 10.00s
Doing 2048 bit public rsa's for 10s: 387140 2048 bit public RSA's in 10.00s
OpenSSL 1.0.2g  1 Mar 2016
built on: reproducible build, date unspecified
options:bn(64,32) rc4(ptr,char) des(ptr,risc1,16,int) aes(partial) blowfish(ptr)
compiler: gcc -I. -I.. -I../include  -fPIC -DOPENSSL_PIC
-DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -m64
-DB_ENDIAN -g -O2 -fstack-protector-strong -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro
-Wa,--noexecstack -Wall -DULTRASPARC -DBN_DIV2W -DOPENSSL_BN_ASM_MONT
-DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DMD5_ASM
-DAES_ASM -DGHASH_ASM
  signverifysign/s verify/s
rsa 2048 bits 0.000788s 0.26s   1268.7  38714.0

mator@deb4g:~$ openssl engine pkcs11 -t
(pkcs11) pkcs11 engine
Unable to load module (null)
 [ unavailable ]

mator@deb4g:~$ strace -e trace=file openssl engine pkcs11 -t
execve("/usr/bin/openssl", ["openssl", "engine", "pkcs11", "-t"], [/*
16 vars */]) = 0
access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or directory)
access("/etc/ld.so.preload", R_OK)  = -1 ENOENT (No such file or directory)
open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or directory)
open("/usr/lib/sparc64-linux-gnu/libssl.so.1.0.2", O_RDONLY|O_CLOEXEC) = 3
access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or directory)
open("/usr/lib/sparc64-linux-gnu/libcrypto.so.1.0.2", O_RDONLY|O_CLOEXEC) = 3
access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or directory)
open("/lib/sparc64-linux-gnu/libdl.so.2", O_RDONLY|O_CLOEXEC) = 3
access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or directory)
open("/lib/sparc64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
open("/usr/lib/ssl/openssl.cnf", O_RDONLY) = 3
open("/proc/meminfo", O_RDONLY|O_CLOEXEC) = 3
open("/usr/lib/sparc64-linux-gnu/openssl-1.0.2/engines/libpkcs11.so",
O_RDONLY|O_CLOEXEC) = 3
open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or directory)
open("/usr/lib/sparc64-linux-gnu/libp11.so.2", O_RDONLY|O_CLOEXEC) = 3
(pkcs11) pkcs11 engine
Unable to load module (null)
 [ unavailable ]
+++ exited with 0 +++
mator@deb4g:~$



on the other machine (fedora x86_64 , vmware guest):

[mator@node01 ~]$ openssl engine pkcs11 -t
(pkcs11) pkcs11 engine
 [ available ]

[mator@node01 ~]$ strace -e trace=file openssl engine pkcs11 -t
execve("/usr/bin/openssl", ["openssl", "engine", "pkcs11", "-t"], [/*
25 vars */]) = 0
access("/etc/ld.so.preload", R_OK)  = -1 ENOENT (No such file or directory)
open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
open("/lib64/libssl.so.10", O_RDONLY|O_CLOEXEC) = 3
open("/lib64/libgssapi_krb5.so.2", O_RDONLY|O_CLOEXEC) = 3
open("/lib64/libkrb5.so.3", O_RDONLY|O_CLOEXEC) = 3
open("/lib64/libcom_err.so.2", O_RDONLY|O_CLOEXEC) = 3
open("/lib64/libk5crypto.so.3", O_RDONLY|O_CLOEXEC) = 3
open("/lib64/libcrypto.so.10", O_RDONLY|O_CLOEXEC) = 3
open("/lib64/libdl.so.2", O_RDONLY|O_CLOEXEC) = 3
open("/lib64/libz.so.1", O_RDONLY|O_CLOEXEC) = 3
open("/lib64/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
open("/lib64/libkrb5support.so.0", O_RDONLY|O_CLOEXEC) = 3
open("/lib64/libkeyutils.so.1", O_RDONLY|O_CLOEXEC) = 3
open("/lib64/libresolv.so.2", O_RDONLY|O_CLOEXEC) = 3
open("/lib64/libpthread.so.0", O_RDONLY|O_CLOEXEC) = 3
open("/lib64/libselinux.so.1", O_RDONLY|O_CLOEXEC) = 3
open("/lib64/libpcre.so.1", O_RDONLY|O_CLOEXEC) = 3
statfs("/sys/fs/selinux", {f_type="SELINUX_MAGIC", f_bsize=4096,
f_blocks=0, f_bfree=0, f_bavail=0, f_files=0, f_ffree=0, f_fsid={0,
0}, f_namelen=255, f_frsize=4096, f_flags=4128}) = 0
statfs("/sys/fs/selinux", {f_type="SELINUX_MAGIC", f_bsize=4096,
f_blocks=0, f_bfree=0, f_bavail=0, f_files=0, f_ffree=0, f_fsid={0,
0}, f_namelen=255, f_frsize=4096, f_flags=4128}) = 0
access("/etc/selinux/config", F_OK) = 0
access("/etc/system-fips", F_OK)= -1 ENOENT (No such file or directory)
open("/etc/pki/tls/openssl.cnf", O_RDONLY) = 3
open("/proc/meminfo", O_RDONLY|O_CLOEXEC) = 3
open("/usr/lib64/openssl/engines/libpkcs11.so", O_RDONLY|O_CLOEXEC) = 3
open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
open("/lib64/libp11.so.2", 

Bug#818744: courier-authdaemon: init.d/courier-authdaemon script hangs

[Amos Jeffries]

Package: courier-authdaemon
Version: 0.66.4-5
Severity: grave


The /etc/init.d/courier-authdaemon script hangs on any use.

It contains the suspicious I/O loop:

if [ -r "$TMPFILES" ]; then
while read type path mode user group; do
if [ "$type" = "d" ]; then
mkdir -p "$path"
chmod "$mode" "$path"
chown "$user:$group" "$path"
[ -x /sbin/restorecon ] && /sbin/restorecon $path
fi
done
fi

which is attempting to read from stdio. But does not prompt the user
about what is expected to be typed in.


Looking at the file represented by $TMPFILES it appears that file is
supposed to be piped to the "while read" instead of waiting for user
input. This alteration makes the script finish and the package install
runs to completion;

if [ -r "$TMPFILES" ]; then
cat $TMPFILES | while read type path mode user group; do
if [ "$type" = "d" ]; then
mkdir -p "$path"
chmod "$mode" "$path"
chown "$user:$group" "$path"
[ -x /sbin/restorecon ] && /sbin/restorecon $path
fi
done
fi


Though I am not sure if the resulting installation is correct yet as
there are other issues somewhere preventing the init.d scripts from
actually doing anything.

"start" command appears to start daemons running. But "stop" command
does nothing despite reporting "[ok] success".

Amos

Bug#818741: pulseaudio-module-x11: repeatable intermittent driver working

[Richard Jasmin]

Package: pulseaudio-module-x11
Version: 5.0-13
Severity: grave
Tags: upstream
Justification: renders package unusable

Dear Maintainer,

we have an issue. Because I know for a fact snd hda intel aka alc889 is
fully supported at this time.kernel not only recognizes the hardware but so
does the sound daemon.

YET...

either pulse is tripping acid hard or we have a more serious issue with the
kernel driver that is going un unnoticed.THIS HARDWARE IS FULLY SUPPORTED.

some days it wants to work, some days not.
fldigi will punch out audio but heaven forbid I want to play musicnothing.
Its not the app and the music seems to be all the way up.

pulse reports "dummy audio" and no hda intel internal hardware. alsa says
differently. not only does my 7850s have hdmi out on multiple channels but the
ATI SB internal shows up too.

YET...

aplay a file and NOTHINGmy speakers are all the way up. NOTHING OUT.I
should be waking my neighbors at this point.

this needs to be addressed ASAP. Not having working audio is reason enough to
ditch linux.And I dont want to ditch ANY Linux.
I DONT WANT SIN. SIN is too vulnerable.



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

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

Versions of packages pulseaudio-module-x11 depends on:
ii  libc6 2.19-18+deb8u3
ii  libcap2   1:2.24-8
ii  libice6   2:1.0.9-1+b1
ii  libpulse0 5.0-13
ii  libsm62:1.2.2-1+b1
ii  libx11-6  2:1.6.2-3
ii  libx11-xcb1   2:1.6.2-3
ii  libxcb1   1.10-3+b1
ii  libxtst6  2:1.2.2-1+b1
ii  pulseaudio5.0-13
ii  pulseaudio-utils  5.0-13

pulseaudio-module-x11 recommends no packages.

pulseaudio-module-x11 suggests no packages.

-- no debconf information

Bug#818740: haskell-monad-par: FTBFS on powerpc: ERROR: thread blocked indefinitely in an MVar operation

[Emilio Pozuelo Monfort]

Source: haskell-monad-par
Version: 0.3.4.7-7
Severity: serious

Your package failed to build on powerpc:

lotsaRunPar: [Failed]
ERROR: thread blocked indefinitely in an MVar operation

Logs at 
https://buildd.debian.org/status/logs.php?pkg=haskell-monad-par=0.3.4.7-7%2Bb1=powerpc

Bug#818265: Bug#818187: Bug#818265: Bug#818187: zeromq3 migrated without any transition being done

[GCS]

On Sun, Mar 20, 2016 at 10:56 AM, Emilio Pozuelo Monfort
 wrote:
> On Tue, 15 Mar 2016 23:37:26 +0100
> =?UTF-8?B?TMOhc3psw7MgQsO2c3rDtnJtw6lueWkgKEdDUyk=?=  wrote:
>> On Tue, Mar 15, 2016 at 11:24 PM, Julian Taylor
>>  wrote:
>> > On 15.03.2016 22:48, László Böszörményi (GCS) wrote:
>>  While I was checking the failing build logs, I see:
>> build/temp.linux-armv7l-2.7/scratch/tmp/timer_createOfMQXG.o: In
>> function `main':
>> timer_createOfMQXG.c:(.text+0x14): undefined reference to `timer_create'
>> collect2: error: ld returned 1 exit status
>>
>> It's not just the implicit declaration, but a linker error later. I
>> can be wrong, but it seems it _may_ cause the test hang as there's no
>> timer to look for / to wait its expiration. Sorry if it happens in
>> normal logs as well; will check it tomorrow morning as it's almost
>> midnight here. :(
 Checked, it happens in normal build logs as well.

> Got a chance to look at this?
 Sorry, my life was chaotic. Yes and no, checked it. First, there's a
new upstream version of pyzmq (15.2) for two months. It seems to be
security related according to the release log[1]:
- FIX: unicode/bytes bug in password prompt in zmq.ssh on Python 3
- workaround overflow bug in libzmq preventing receiving messages
larger than MAX_INT

My computer is old and has problems; even the archive version hangs
during self-tests. Still, it may help if Julian update the package to
the latest version. With my Python Modules team member hat on, should
I do it myself?
Just for the record, upstream Git tree has even more fixes that not
yet released as a new version.

Regards,
Laszlo/GCS
[1] https://pyzmq.readthedocs.org/en/latest/changelog.html

Bug#808509: (no subject)

[Vasilis]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

This has been fixed in txtorcon 0.14.2:
https://github.com/meejah/txtorcon/issues/146
-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJW6t5nAAoJEF+/cLHRJgFiHDwP/RyPlaM6KUv5kBYsoLvZZZL8
AFvEckJA2K+J8+lUOctVmToa5NcTWRUGDX7eT+4wGCWvfhQN0Nc5sc+FXv+yjSbj
woPCKg38marhN/Y7l/jUi1584ceKlKQDh3SyvpDJL5cVXMlQ6Qr2KH9X7Gz9pCJn
fXOoSmhc1shgWsXIXzOmCX2aK0imNQJ4AbHqAmAHe1W4S2uF7UwTFdUGq85Ucemy
0D6KoqFeXhzUYcIRmi/LDtFvADqyn48h3L+wS+dIUJ1660Fw0GLUORRckRIxZXNa
wgxN1sF2KdAMzs5Ruu/yE5F+30njO52sv6HwaZl2biaiOrb2Ei0yvQipVrWFk89K
fEWalBq7+VS2oEVCrDmgPHQGNt80FqJnwOWKpFsR3oj++mnfTvDjIXmrRKDEmVB6
6RObX96VYHwxNRdSxdTxPKLyrlVU9VY90+y+b9XWoFlVcK6vOkshxwuccweee3YM
IZkPnKnPMiaevliKiGt8iMO5P1oGGJ1aDEsbQPjKPySE3pNLY4kQ8siLx/8SpKTg
hqOJJMcmWf69UpaULhjyvCbRjnbt4yJjXevm3Yx0Qr1jqWEAi3cqJE4jvSv9mKJq
nE87BvOVLlDOGirsZ38f+UripExt9RbKYNBSIcIVbzAmugyIEWpeyyX4Dq3D+yJQ
2QJRD6HC1kJAptn2QrQp
=/71Y
-END PGP SIGNATURE-

Processed: tagging 818392

[Debian Bug Tracking System]

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

> tags 818392 + pending
Bug #818392 [liblouisutdml] liblouisutdml: FTBFS: jni_md.h: No such file or 
directory
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#802380: closed by Alberto Garcia <be...@igalia.com> (Bug#802380: fixed in webkit2gtk 2.10.8-1)

[Alberto Garcia]

Control: reopen -1
Control: found -1 webkit2gtk/2.10.9-1
Control: tags -1 -fixed-upstream

On Sat, Mar 12, 2016 at 09:51:05AM +, Debian Bug Tracking System wrote:

> Source: webkit2gtk
> Source-Version: 2.10.8-1
> 
> We believe that the bug you reported is fixed in the latest version of
> webkit2gtk, which is due to be installed in the Debian FTP archive.

Unfortunately the fix for this bug broke several website, including
many very popular ones like Twitter or Facebook, so upstream decided
to revert it in 2.10.9.

I'm reopening it until there's a new fix available.

Berto

Bug#818730: [Python-modules-team] Bug#818730: FTBFS in unstable

[Brian May]

Steve Langasek  writes:

> django-pipeline fails to build in unstable with the following error:

Was this on a clean unstable system?

Am wondering if maybe there is something else installed that is badly
interacting with the build process.

Have traced through the code, and all it should be doing in the failing
test is:

to_class('pipeline.compressors.yuglify.YuglifyCompressor')

which in turn returns:

importlib.import_module('pipeline.compressors.yuglify').YuglifyCompressor

I don't see why this should be failing. Particularly as the message
makes it clear that this symbol can be loaded.
-- 
Brian May 

Bug#818265: Bug#818187: Bug#818265: Bug#818187: zeromq3 migrated without any transition being done

[Emilio Pozuelo Monfort]

On Tue, 15 Mar 2016 23:37:26 +0100 
=?UTF-8?B?TMOhc3psw7MgQsO2c3rDtnJtw6lueWkgKEdDUyk=?=  wrote:

On Tue, Mar 15, 2016 at 11:24 PM, Julian Taylor
 wrote:
> On 15.03.2016 22:48, László Böszörményi (GCS) wrote:
>>  This is known to pyzmq upstream[1] for about three years. It happens
>> on Ubuntu, Red Hat, CentOS and with ZeroMQ 4.0.x as well. While
>> timer_create() [4] is in librt, the standard GNU C library, it seems
>> pyzmq miss to link with it on the failing architectures.
[...]
> Are you saying linking against -lrt will fix the tests deadlocking?
>
> I don't quite see the relation between the hanging tests and the linked
> issues.
> The implicit declaration errors have always been there I think but only
> in a configure check so harmless (until now?).
 While I was checking the failing build logs, I see:
build/temp.linux-armv7l-2.7/scratch/tmp/timer_createOfMQXG.o: In
function `main':
timer_createOfMQXG.c:(.text+0x14): undefined reference to `timer_create'
collect2: error: ld returned 1 exit status

It's not just the implicit declaration, but a linker error later. I
can be wrong, but it seems it _may_ cause the test hang as there's no
timer to look for / to wait its expiration. Sorry if it happens in
normal logs as well; will check it tomorrow morning as it's almost
midnight here. :(


Got a chance to look at this?

Emilio

Processed: workaround for jessie-backports (bug exists in Jessie)

[Debian Bug Tracking System]

Processing control commands:

> found -1 1.2
Bug #808552 {Done: Axel Beckert } [dh-dist-zilla] 
dh-dist-zilla: builds fail in recent pbuilder versions
Marked as found in versions dh-dist-zilla/1.2.

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

Bug#808552: workaround for jessie-backports (bug exists in Jessie)

[Afif Elghraoui]

Control: found -1 1.2

Hi,
I ran into this bug while trying to backport a package to jessie.
Following the hint given in the bug log, I was able to work around the
problem by adding the following line to debian/rules:

export DZIL_GLOBAL_CONFIG_ROOT=/sbuild-nonexistent

Thanks and regards
Afif

-- 
Afif Elghraoui | عفيف الغراوي
http://afif.ghraoui.name

Processed: unarchiving 808552

[Debian Bug Tracking System]

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

> unarchive 808552
Bug #808552 {Done: Axel Beckert } [dh-dist-zilla] 
dh-dist-zilla: builds fail in recent pbuilder versions
Unarchived Bug 808552
> thanks
Stopping processing here.

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

Bug#818730: [Python-modules-team] Bug#818730: FTBFS in unstable

[Brian May]

Steve Langasek  writes:

> Since this is an Arch: all package with no build log, it's not clear what has
> changed to cause it to fail to build, but clearly something has.

Unfortunately, I cannot reproduce any build problems on a sid schroot
with i386 or amd64.

(otherwise was thinking the new upstream version would fix any problems)
-- 
Brian May 

Bug#818733: marked as done (cryptsetup failes in luksFormat: Failed to open key file)

[Debian Bug Tracking System]

Your message dated Sun, 20 Mar 2016 14:40:29 +0530
with message-id <56ee6905.5040...@onenetbeyond.org>
and subject line bad command line option
has caused the Debian Bug report #818733,
regarding cryptsetup failes in luksFormat: Failed to open key file
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.)


-- 
818733: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818733
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: cryptsetup
severity: grave
version: 2:1.6.6-5

# cryptsetup luksFormat /dev/data/diaspora diaspora

WARNING!

This will overwrite data on /dev/data/diaspora irrevocably.

Are you sure? (Type uppercase yes): YES
Failed to open key file.

# apt-cache policy cryptsetup
cryptsetup:
  Installed: 2:1.6.6-5
  Candidate: 2:1.6.6-5
  Version table:
 *** 2:1.6.6-5 0
500 http://ftp.fr.debian.org/debian/ jessie/main armhf Packages
100 /var/lib/dpkg/status

# uname -a
Linux backup-poddery-com 4.4.4-std-1 #1 SMP Sun Mar 6 18:34:13 UTC 2016
armv7l GNU/Linux




signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
closing this as bad command line option.



signature.asc
Description: OpenPGP digital signature
--- End Message ---

Bug#818520: ruby-tokyocabinet: FTBFS: [tokyocabinet.gemspec] isn't a Gem::Specification

[Martin Michlmayr]

Package: ruby-tokyocabinet
Version: 1.31-4
Severity: serious

This package fails to build in unstable:

> sbuild (Debian sbuild) 0.68.0 (15 Jan 2016) on dl580gen9-02.hlinux
...
>dh_testdir -O--buildsystem=ruby
>dh_auto_clean -O--buildsystem=ruby
>   dh_ruby --clean
> [tokyocabinet.gemspec] isn't a Gem::Specification (NilClass instead).
> [tokyocabinet.gemspec.gem2deb] isn't a Gem::Specification (NilClass instead).
> /usr/lib/ruby/vendor_ruby/gem2deb/metadata.rb:116:in `load_gemspec': E: 
> cannot load gemspec tokyocabinet.gemspec (RuntimeError)
>   from /usr/lib/ruby/vendor_ruby/gem2deb/metadata.rb:33:in `block in 
> initialize'
>   from /usr/lib/ruby/vendor_ruby/gem2deb/metadata.rb:32:in `chdir'
>   from /usr/lib/ruby/vendor_ruby/gem2deb/metadata.rb:32:in `initialize'
>   from /usr/lib/ruby/vendor_ruby/gem2deb/installer.rb:24:in `new'
>   from /usr/lib/ruby/vendor_ruby/gem2deb/installer.rb:24:in `initialize'
>   from /usr/lib/ruby/vendor_ruby/gem2deb/dh_ruby.rb:202:in `new'
>   from /usr/lib/ruby/vendor_ruby/gem2deb/dh_ruby.rb:202:in `block in 
> installers'
>   from /usr/lib/ruby/vendor_ruby/gem2deb/dh_ruby.rb:201:in `map'
>   from /usr/lib/ruby/vendor_ruby/gem2deb/dh_ruby.rb:201:in `installers'
>   from /usr/lib/ruby/vendor_ruby/gem2deb/dh_ruby.rb:43:in `clean'
>   from /usr/bin/dh_ruby:96:in `'
>dh_ruby --clean
> dh_auto_clean: dh_ruby --clean returned exit code 1
> debian/rules:18: recipe for target 'clean' failed

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise

Bug#818734: sorl-thumbnail: FTBFS: missing build-dependency on pytest et al.

[Steve Langasek]

Source: sorl-thumbnail
Version: 12.3-1
Severity: serious

The sorl-thumbnail package in the archive is not buildable in a current
clean sid chroot due to undeclared build-dependencies.  The build fails
with:

  for python in python2.7; do \
for name in pil pgmagick imagemagick graphicsmagick; do \
LOCPATH=/«PKGBUILDDIR»/tmp-locales LC_ALL=en_US.UTF-8 PYTHONPATH=. 
LOCAL_BUILD=1 DJANGO_SETTINGS_MODULE=tests.settings.$name $python -m pytest ; \
done; \
  done
  /usr/bin/python2.7: No module named pytest
  debian/rules:22: recipe for target 'override_dh_auto_test' failed

If you install python-pytest, the package then fails with other errors:

 ERRORS 
 ERROR collecting tests/thumbnail_tests/test_alternative_resolutions.py 
tests/thumbnail_tests/test_alternative_resolutions.py:11: in 
from .utils import BaseStorageTestCase
tests/thumbnail_tests/utils.py:18: in 
from .models import Item
tests/thumbnail_tests/models.py:6: in 
class Item(models.Model):
/usr/lib/python2.7/dist-packages/django/db/models/base.py:94: in __new__
app_config = apps.get_containing_app_config(module)
/usr/lib/python2.7/dist-packages/django/apps/registry.py:239: in 
get_containing_app_config
self.check_apps_ready()
/usr/lib/python2.7/dist-packages/django/apps/registry.py:124: in 
check_apps_ready
raise AppRegistryNotReady("Apps aren't loaded yet.")
E   AppRegistryNotReady: Apps aren't loaded yet.

I don't know if the latter failure is a missing build-dependency on
something else, or an incompatibility with current django.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: Digital signature

Bug#818733: cryptsetup failes in luksFormat: Failed to open key file

[Pirate Praveen]

package: cryptsetup
severity: grave
version: 2:1.6.6-5

# cryptsetup luksFormat /dev/data/diaspora diaspora

WARNING!

This will overwrite data on /dev/data/diaspora irrevocably.

Are you sure? (Type uppercase yes): YES
Failed to open key file.

# apt-cache policy cryptsetup
cryptsetup:
  Installed: 2:1.6.6-5
  Candidate: 2:1.6.6-5
  Version table:
 *** 2:1.6.6-5 0
500 http://ftp.fr.debian.org/debian/ jessie/main armhf Packages
100 /var/lib/dpkg/status

# uname -a
Linux backup-poddery-com 4.4.4-std-1 #1 SMP Sun Mar 6 18:34:13 UTC 2016
armv7l GNU/Linux




signature.asc
Description: OpenPGP digital signature

Bug#818349: exim4-base: Still warns about purging the environment, even with add_environment set

[Ben Hutchings]

Control: severity -1 important
Control: retitle -1 NEWS doesn't clearly explain config changes needed for 
CVE-2016-1531

On Wed, 2016-03-16 at 19:39 +0100, Andreas Metzler wrote:
> On 2016-03-16 Ben Hutchings  wrote:
> > 
> > Control: severity -1 serious
> > Control: tag -1 moreinfo
> > 
> > Upgrading severity.  I consider this release-critical because a package
> > should never:
> > 
> > 1. Send spurious error messages from its cron job
> > 2. Recommend changing the configuration in a way that would undo a
> > security fix
> Hello,
> 
> the situation is this:
> 
> * Upstream made a change (cleaning the environment by default) that in
>   their opinion could break existing systems. There is not a magic
>   switch that can be thrown to fix this. The safe default value (empty
>   environment) is exactly what causes the breakage. To point
>   admininistrators of failing system in the right direction exim prints
>   a warning when keep_environment is not set.
>
> * Afaik the Debian config works fine with empty environment which is why
>   we have added an explicit 'keep_environment=" to prevent the runtime
>   warning.

This is all good.

> * Otoh if you are running a custom configuration you will get
>   the warning exactly as upstream has intended and you will need to
>   decide whether you need to modify the environment. This also applies
>   to configuration based on the Debian configuration. - You'll need to
>   look at the configuration and decide whether modifying the runtime
>   environment is necessary. (You'll get a dpkg confile prompt and need
>   to merge the changes.)

The warning isn't really very clear, though.

> * In addition there is an entry in exim4-config.NEWS.

I saw that, but it also wasn't that clear about what changes were
needed.

> I am basically out of bright ideas on how to improve things from here.
> The whole thing is trade-off, on one side now some people get a warning
> message without experincing real breakage, on the other side if I patched
> out the warning message some people would just see a broken e-mail
> service without the helpful hint. Being in doubt I trusted upstream's
> choice.
> 
> See http://article.gmane.org/gmane.mail.exim.devel/9142 and following.

Please expand the NEWS item to say that if you have a custom
configuration you *must* update it, and also refer to
https://exim.org/s
tatic/doc/CVE-2016-1531.txt which briefly explains the new variables.

Ben.

-- 
Ben Hutchings
If you seem to know what you are doing, you'll be given more to do.

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

Processed: Re: zimlib: FTBFS: required file './compile' not found

[Debian Bug Tracking System]

Processing control commands:

> tag -1 +confirmed
Bug #818456 [zimlib] zimlib: FTBFS: required file './compile' not found
Added tag(s) confirmed.

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

Processed: Re: exim4-base: Still warns about purging the environment, even with add_environment set

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #818349 [exim4-base] exim4-base: Still warns about purging the environment, 
even with add_environment set
Severity set to 'serious' from 'important'
> tag -1 moreinfo
Bug #818349 [exim4-base] exim4-base: Still warns about purging the environment, 
even with add_environment set
Added tag(s) moreinfo.

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

Bug#818392: liblouisutdml: FTBFS: jni_md.h: No such file or directory

[Martin Michlmayr]

Package: liblouisutdml
Version: 2.5.0-2
Severity: serious

This package fails to build in unstable.  Note that there's some
conversation in #760301 about the compatibility link, but it seems
this is intentional.

> sbuild (Debian sbuild) 0.68.0 (15 Jan 2016) on dl580gen9-02.hlinux
...
> make[3]: Entering directory '/<>/liblouisutdml'
> /bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. 
> -DLBU_PATH=\"/usr/share/liblouisutdml/lbu_files/\" 
> -DLIBLOUIS_TABLES_PATH=\"/usr/share/liblouis/tables/\"  
> -I/usr/lib/jvm/default-java/include -I/usr/include/liblouis 
> -I/usr/include/libxml2 -O2 -MT liblouisutdml_la-Jliblouisutdml.lo -MD -MP -MF 
> .deps/liblouisutdml_la-Jliblouisutdml.Tpo -c -o 
> liblouisutdml_la-Jliblouisutdml.lo `test -f '../java/Jliblouisutdml.c' || 
> echo './'`../java/Jliblouisutdml.c
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. 
> -DLBU_PATH=\"/usr/share/liblouisutdml/lbu_files/\" 
> -DLIBLOUIS_TABLES_PATH=\"/usr/share/liblouis/tables/\" 
> -I/usr/lib/jvm/default-java/include -I/usr/include/liblouis 
> -I/usr/include/libxml2 -O2 -MT liblouisutdml_la-Jliblouisutdml.lo -MD -MP -MF 
> .deps/liblouisutdml_la-Jliblouisutdml.Tpo -c ../java/Jliblouisutdml.c  -fPIC 
> -DPIC -o .libs/liblouisutdml_la-Jliblouisutdml.o
> In file included from ../java/Jliblouisutdml.h:2:0,
>  from ../java/Jliblouisutdml.c:29:
> /usr/lib/jvm/default-java/include/jni.h:45:20: fatal error: jni_md.h: No such 
> file or directory
> compilation terminated.
> Makefile:800: recipe for target 'liblouisutdml_la-Jliblouisutdml.lo' failed
> make[3]: *** [liblouisutdml_la-Jliblouisutdml.lo] Error 1
> make[3]: Leaving directory '/<>/liblouisutdml'

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise

Bug#818391: marked as done (cqrlog: FTBFS: Can't find unit sslsockets used by fphttpclient)

[Debian Bug Tracking System]

Your message dated Thu, 17 Mar 2016 10:22:09 +
with message-id 
and subject line Bug#818391: fixed in cqrlog 1.9.1-2
has caused the Debian Bug report #818391,
regarding cqrlog: FTBFS: Can't find unit sslsockets used by fphttpclient
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.)


-- 
818391: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818391
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cqrlog
Version: 1.9.1-1
Severity: serious

This package fails to build in unstable:

> sbuild (Debian sbuild) 0.68.0 (15 Jan 2016) on dl580gen9-02.hlinux
...
> 1500 303.554/322.880 Kb Used
> (10001) PPU Loading 
> /usr/lib/fpc/3.0.0/units/x86_64-linux/fcl-net/sslsockets.ppu
> (10011) PPU Source: sslsockets.pp not available
> (10028) Recompiling sslsockets, checksum changed for OpenSSL
> Fatal: (10022) Can't find unit sslsockets used by fphttpclient
> Fatal: (1018) Compilation aborted
> Error: /usr/bin/ppcx64 returned an error exitcode
> Error: (lazarus) Compile Project, Target: cqrlog: stopped with exit code 256
> ERROR: failed compiling of project /<>/src/cqrlog.lpi
> Makefile:9: recipe for target 'cqrlog' failed
> make[1]: *** [cqrlog] Error 2
> make[1]: Leaving directory '/<>'
> dh_auto_build: make -j1 returned exit code 2

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Source: cqrlog
Source-Version: 1.9.1-2

We believe that the bug you reported is fixed in the latest version of
cqrlog, 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 818...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Colin Tuckley  (supplier of updated cqrlog 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, 17 Mar 2016 09:54:12 +
Source: cqrlog
Binary: cqrlog
Architecture: source amd64
Version: 1.9.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Hamradio Maintainers 
Changed-By: Colin Tuckley 
Description:
 cqrlog - Advanced logging program for hamradio operators
Closes: 818391
Changes:
 cqrlog (1.9.1-2) unstable; urgency=medium
 .
   * Remove local copy of openssl unit and add build-dependency
 on fp-units-net to resolve unit conflict (Closes: 818391)
 patch from Peter Green 
Checksums-Sha1:
 4786347f0a81f72ced51e71e249c0cf38b81052e 2090 cqrlog_1.9.1-2.dsc
 68dae539650cc8c131c047f2b379fcbc8169c1d5 11848 cqrlog_1.9.1-2.debian.tar.xz
 7e91ebffb50f032a65a5d1b7b202c4f972a2fa45 7254928 cqrlog_1.9.1-2_amd64.deb
Checksums-Sha256:
 bcf07c5c68e72bf9dba8a6ee84cb29d38920a30fccfd229db7a7a7562a0180a1 2090 
cqrlog_1.9.1-2.dsc
 85178cf37e07daa98a69da81877f9b650a86be433bb7617de2db9b9461f58cc0 11848 
cqrlog_1.9.1-2.debian.tar.xz
 1f22d9a5836fde0d814bdaa20854f51cf8ded4ecc062b7a479db833d6653c86a 7254928 
cqrlog_1.9.1-2_amd64.deb
Files:
 e0f64f4983b7a14704c84d0abf9d03ae 2090 hamradio extra cqrlog_1.9.1-2.dsc
 c2ae1ed4e74a58d5abc35a2d385c34e3 11848 hamradio extra 
cqrlog_1.9.1-2.debian.tar.xz
 4dc97f989b162d89ec96c9e6422e2abd 7254928 hamradio extra 
cqrlog_1.9.1-2_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJW6oJdAAoJEPoMQQc4ydkDmMcQAI5anxT+wjTj6varNmdtpyM5
Lc9VlzesECUN7w9FBYnBEIt97dcyfQATk/dyq2oGto10LJUYOwHkDnWFT+INa7tQ
g4Nh0Krjwzk9dzMNKJYx80Img/VUcutDjYwwoo6G0n0lBPgoWM0XHSTkxPbp8p8s
v0QrXAa2bbdfRIkjF1hwelGsS847JigbkOvq5PrAX8NQLEEIitulFXqyXnDxflwU
XCISr+dDidbZeIFwJGV5jkxRED0eRsgo1rPMnkCepCgsyB5B6zEF/piYn97lJiAM
32OumBxCRhxPRGQAVdKrzcG9lr505p1kAGgT+X9+pkGhgGtkGMjtm7DdlCP63zBA
V2g8wz/b+eLtBOhWCjQ+7lA6C9OjtxP0Rg/w3lr7rm5jzDYbk62KHlrutTu0jsoJ
hc3Z7f9HJfW8t/6rBprjLDXXnSZayFxqs6WFmZaeIUuIfMsm21qJ7YOPXDS7sdkk
1BcQXDKObYRSqj/9Ex/Qkyc5CxG53CPlw06UoSIUCItmBrTgOwP2sbP/BPjP8dWC
Ckw9UQfFQJPUDvgLI4M/R+AW/vkt0uO7mQ5KOnNREEh87yV5erv1K6TczGhH2j1e
EPvNEFxPZbcvRyp91J2QPAY7K8w62vdf0+RcHPr6PL7Ea/PXilGnjAQ3hOW+hsTa
77pVK6JT86QMgSsgnYmK
=xhtU
-END PGP SIGNATURE End Message ---

Processed: found 818318 in 1:1.7.10.4-1

[Debian Bug Tracking System]

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

> found 818318 1:1.7.10.4-1
Bug #818318 [git] git: CVE-2016-2324 and CVE-2016-2315 (currently unpublished) 
server and client RCE
Marked as found in versions git/1:1.7.10.4-1.
> thanks
Stopping processing here.

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

Bug#818730: FTBFS in unstable

[Steve Langasek]

Package: src:django-pipeline
Version: 1.6.4-1
Severity: serious

django-pipeline fails to build in unstable with the following error:

make[1]: Entering directory '/tmp/django-pipeline-1.6.4'
PYBUILD_SYSTEM=custom PYBUILD_TEST_ARGS="PYTHONPATH=. python{version} 
/usr/bin/django-admin test --settings=tests.settings" dh_auto_test
I: pybuild base:184: PYTHONPATH=. python2.7 /usr/bin/django-admin test 
--settings=tests.settings
.F...F
==
FAIL: test_css_compressor_class (tests.tests.test_compressor.CompressorTest)
--
Traceback (most recent call last):
  File "/tmp/django-pipeline-1.6.4/tests/tests/test_compressor.py", line 36, in 
test_css_compressor_class
self.assertEqual(self.compressor.css_compressor, YuglifyCompressor)
AssertionError: None != 

==
FAIL: test_js_compressor_class (tests.tests.test_compressor.CompressorTest)
--
Traceback (most recent call last):
  File "/tmp/django-pipeline-1.6.4/tests/tests/test_compressor.py", line 33, in 
test_js_compressor_class
self.assertEqual(self.compressor.js_compressor, YuglifyCompressor)
AssertionError: None != 

--
Ran 62 tests in 0.902s

FAILED (failures=2)

Since this is an Arch: all package with no build log, it's not clear what has
changed to cause it to fail to build, but clearly something has.

Processed: Re: Bug#811890: Not a GCC 6 issue, but libc 2.22

[Debian Bug Tracking System]

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

> severity 811890 serious
Bug #811890 [httpfs2] FTBFS with libc6 2.22 from experimental
Severity set to 'serious' from 'important'
> retitle 811890 FTBFS: storage size of 'hints' isn't known
Bug #811890 [httpfs2] FTBFS with libc6 2.22 from experimental
Changed Bug title to 'FTBFS: storage size of 'hints' isn't known' from 'FTBFS 
with libc6 2.22 from experimental'
> thanks
Stopping processing here.

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

Bug#815395: marked as done (python-kdcproxy: FTBFS: dh_auto_test: pybuild --test --test-pytest -i python{version} -p 2.7 --dir . returned exit code 13)

[Debian Bug Tracking System]

Your message dated Thu, 17 Mar 2016 10:02:19 +
with message-id 
and subject line Bug#815395: fixed in python-kdcproxy 0.3.2-2
has caused the Debian Bug report #815395,
regarding python-kdcproxy: FTBFS:  dh_auto_test: pybuild --test --test-pytest 
-i python{version} -p 2.7 --dir . returned exit code 13
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.)


-- 
815395: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815395
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-kdcproxy
Version: 0.3.2-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,

python-kdcproxy fails to build from source in unstable/amd64:

  [..]


 dh_auto_test -O--buildsystem=pybuild
  I: pybuild base:184: cd 
/home/lamby/temp/cdt.20160221091726.e0RWSToYdG/python-kdcproxy-0.3.2/.pybuild/pythonX.Y_2.7/build;
 python2.7 -m pytest 
  = test session starts 
==
  platform linux2 -- Python 2.7.11, pytest-2.8.7, py-1.4.31, pluggy-0.3.1
  rootdir: 
/home/lamby/temp/cdt.20160221091726.e0RWSToYdG/python-kdcproxy-0.3.2, inifile: 
tox.ini
  plugins: cov-2.2.1
  collected 0 items
  
  = no tests ran in 0.00 seconds 
=
  E: pybuild pybuild:274: test: plugin distutils failed with: exit code=5: cd 
/home/lamby/temp/cdt.20160221091726.e0RWSToYdG/python-kdcproxy-0.3.2/.pybuild/pythonX.Y_2.7/build;
 python2.7 -m pytest 
  dh_auto_test: pybuild --test --test-pytest -i python{version} -p 2.7 --dir . 
returned exit code 13
  debian/rules:7: recipe for target 'build' failed
  make: *** [build] Error 25

  [..]

The full build log is attached.


Regards,

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


python-kdcproxy.0.3.2-1.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: python-kdcproxy
Source-Version: 0.3.2-2

We believe that the bug you reported is fixed in the latest version of
python-kdcproxy, 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 815...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Timo Aaltonen  (supplier of updated python-kdcproxy 
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: SHA1

Format: 1.8
Date: Thu, 17 Mar 2016 10:08:03 +0200
Source: python-kdcproxy
Binary: python-kdcproxy python3-kdcproxy
Architecture: source
Version: 0.3.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian FreeIPA Team 
Changed-By: Timo Aaltonen 
Description:
 python-kdcproxy - Kerberos KDC HTTP proxy WSGI module for python
 python3-kdcproxy - Kerberos KDC HTTP proxy WSGI module for python3
Closes: 815395
Changes:
 python-kdcproxy (0.3.2-2) unstable; urgency=medium
 .
   * rules: Override dh_auto_test.
   * workaround-mock-bug.diff: Fix failing tests. (Closes: #815395)
Checksums-Sha1:
 d1adeab8f873899213282d8f6b0d07e7a0f06393 2184 python-kdcproxy_0.3.2-2.dsc
 5ffeabd293978fb6ecd01b1a25af11c7c82ddb8a 2588 
python-kdcproxy_0.3.2-2.debian.tar.xz
Checksums-Sha256:
 d036f4d6955250f84aba048fb7dbd299599929f6914756427483ed9094b1dc31 2184 
python-kdcproxy_0.3.2-2.dsc
 547c4af85eabfad2291ce73b96d7b49f74adfde46ea06a8e7b380f2ef5c582b3 2588 
python-kdcproxy_0.3.2-2.debian.tar.xz
Files:
 9bb1bfbfa74fac167cb9a4297e948c44 2184 python optional 
python-kdcproxy_0.3.2-2.dsc
 d245bcb731d80575fb27df590e3a9b41 2588 python optional 
python-kdcproxy_0.3.2-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJW6mYLAAoJEMtwMWWoiYTcbPQP/iMxZSV7snPq9/tPC5H2Af20
+HQADG65PEw9rUcw2o3iHM5frEM1o5OEds/qC2OO5tZ6rGMSs9N8IpAWduNoMkOD
BTQJoTWGf9JMIecwOfpgqykNGojdOYciqysDYYEOcMtGwijQTRnGviEv2MkC5jRY
oGBBOVsjl4QzpeIApK8+A2DcMR+uZkgtt1HY5biKdlylLke+UIdtfGcK+SM5f6rq
EHNJzky1pjRg0kOAaGCEIrIu/YPrlvYwMWQjFaWEczlSu9UIva15y6yZJ79h2A7M

Bug#818347: marked as done (stylish: FTBFS: python: can't open file '/sdk/bin/typelib.py': [Errno 2] No such file or directory)

[Debian Bug Tracking System]

Your message dated Sun, 20 Mar 2016 06:34:16 +
with message-id 
and subject line Bug#818347: fixed in stylish 2.0.3-1
has caused the Debian Bug report #818347,
regarding stylish: FTBFS: python: can't open file '/sdk/bin/typelib.py': [Errno 
2] 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.)


-- 
818347: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818347
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: stylish
Version: 2.0.2-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,

stylish fails to build from source in unstable/amd64:

  [..]

   fakeroot debian/rules clean
  I: stylish_2.0.23.9.6.
  dh clean --with xul-ext --buildsystem=xul_ext --parallel
 dh_testdir -O--buildsystem=xul_ext -O--parallel
 dh_auto_clean -O--buildsystem=xul_ext -O--parallel
rm -f xul-ext-stylish.xpi
 dh_clean -O--buildsystem=xul_ext -O--parallel
   debian/rules build
  I: stylish_2.0.23.9.6.
  dh build --with xul-ext --buildsystem=xul_ext --parallel
 dh_testdir -O--buildsystem=xul_ext -O--parallel
 dh_update_autotools_config -O--buildsystem=xul_ext -O--parallel
 dh_auto_configure -O--buildsystem=xul_ext -O--parallel
 debian/rules override_dh_auto_build
  make[1]: Entering directory 
'/home/lamby/temp/cdt.20160316084603.IHLK9gXQca/stylish-2.0.2'
  I: stylish_2.0.23.9.6.
  Package libxul was not found in the pkg-config search path.
  Perhaps you should add the directory containing `libxul.pc'
  to the PKG_CONFIG_PATH environment variable
  No package 'libxul' found
  Package libxul was not found in the pkg-config search path.
  Perhaps you should add the directory containing `libxul.pc'
  to the PKG_CONFIG_PATH environment variable
  No package 'libxul' found
  python /sdk/bin/typelib.py -I  -o components/stylishStyle.xpt 
idl/stylishStyle.idl
  python: can't open file '/sdk/bin/typelib.py': [Errno 2] No such file or 
directory
  debian/rules:15: recipe for target 'components/stylishStyle.xpt' failed
  make[1]: *** [components/stylishStyle.xpt] Error 2
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160316084603.IHLK9gXQca/stylish-2.0.2'
  debian/rules:12: recipe for target 'build' failed
  make: *** [build] Error 2

  [..]

The full build log is attached.


Regards,

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


stylish.2.0.2-1.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: stylish
Source-Version: 2.0.3-1

We believe that the bug you reported is fixed in the latest version of
stylish, 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 818...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Dmitry Smirnov  (supplier of updated stylish 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: Sun, 20 Mar 2016 17:14:25 +1100
Source: stylish
Binary: xul-ext-stylish
Architecture: source all
Version: 2.0.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Mozilla Extension Maintainers 

Changed-By: Dmitry Smirnov 
Description:
 xul-ext-stylish - styles manager to customize web sites with themes and skins
Closes: 818347
Changes:
 stylish (2.0.3-1) unstable; urgency=medium
 .
   * New upstream release [December 2015].
   * iceweasel-dev --> firefox-dev
 + ugly FTBFS fix (Closes: #818347).
   * Standards-Version: 3.9.7.
Checksums-Sha1:
 e36148a3f24c7aead76a8cbea32efefc6878b7c4 1962 stylish_2.0.3-1.dsc
 814e2dced1f5d2fdc433972cdba8e6ceb9bdb665 109642 stylish_2.0.3.orig.tar.gz
 9fadfa8c18f177a18fd12d4144cfceafba04f179 3056 stylish_2.0.3-1.debian.tar.xz
 65f94f6f7bc30dec5febffd62a6ad35ec1678304 92914 xul-ext-stylish_2.0.3-1_all.deb
Checksums-Sha256:
 f8abf5b6345358059b4ff6d821106832618bf73f6f695d8a8cd5f7236d85e25d 1962 
stylish_2.0.3-1.dsc
 

Bug#818725: picard-tools: FTBFS in unstable

[Steve Langasek]

Package: src:picard-tools
Version: 1.138+dfsg.1-1
Severity: serious

picard-tools fails to build in a clean unstable environment with the following 
error:

compile-picard:
[mkdir] Created dir: /tmp/picard-tools-1.138+dfsg.1/classes
[javac] /tmp/picard-tools-1.138+dfsg.1/build.xml:494: warning: 
'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to 
false for repeatable builds
[javac] Compiling 295 source files to /tmp/picard-tools-1.138+dfsg.1/classes
[javac] warning: [options] bootstrap class path not set in conjunction with 
-source 1.5
[javac] warning: [options] source value 1.5 is obsolete and will be removed 
in a future release
[javac] warning: [options] target value 1.5 is obsolete and will be removed 
in a future release
[javac] warning: [options] To suppress warnings about obsolete options, use 
-Xlint:-options.
[javac] 
/tmp/picard-tools-1.138+dfsg.1/src/java/picard/illumina/parser/readers/BclQualityEvaluationStrategy.java:35:
 warning: '_' used as an identifier
[javac] public AtomicInteger make(final Byte _) {
[javac]  ^
[javac]   (use of '_' as an identifier might not be supported in releases 
after Java SE 8)
[javac] 
/tmp/picard-tools-1.138+dfsg.1/src/java/picard/analysis/artifacts/ConvertSequencingArtifactToOxoG.java:56:
 error: incompatible types: List cannot be converted to 
List
[javac] final List 
preAdapterDetailMetricsList = (List) 
MetricsFile.readBeans(PRE_ADAPTER_IN);
[javac] 
   ^
[javac] 
/tmp/picard-tools-1.138+dfsg.1/src/java/picard/analysis/artifacts/ConvertSequencingArtifactToOxoG.java:57:
 error: incompatible types: List cannot be converted to 
List
[javac] final List baitBiasDetailMetricsList 
= (List) MetricsFile.readBeans(BAIT_BIAS_IN);
[javac] 
 ^
[javac] 
/tmp/picard-tools-1.138+dfsg.1/src/java/picard/sam/DownsampleSam.java:64: 
error: DownsamplingIterator is abstract; cannot be instantiated
[javac] final DownsamplingIterator iterator = new 
DownsamplingIterator(in.iterator(), r, PROBABILITY);
[javac]   ^
[javac] 
/tmp/picard-tools-1.138+dfsg.1/src/java/picard/sam/DownsampleSam.java:66: 
error: for-each not applicable to expression type
[javac] for (final SAMRecord rec : iterator) {
[javac]^
[javac]   required: array or java.lang.Iterable
[javac]   found:DownsamplingIterator
[javac] 
/tmp/picard-tools-1.138+dfsg.1/src/java/picard/sam/DownsampleSam.java:73: 
error: cannot find symbol
[javac] log.info("Finished! Kept " + iterator.getKeptReads() + " 
out of " + iterator.getTotalReads() + " reads.");
[javac]  ^
[javac]   symbol:   method getKeptReads()
[javac]   location: variable iterator of type DownsamplingIterator
[javac] 
/tmp/picard-tools-1.138+dfsg.1/src/java/picard/sam/DownsampleSam.java:73: 
error: cannot find symbol
[javac] log.info("Finished! Kept " + iterator.getKeptReads() + " 
out of " + iterator.getTotalReads() + " reads.");
[javac] 
^
[javac]   symbol:   method getTotalReads()
[javac]   location: variable iterator of type DownsamplingIterator
[javac] Note: Some input files use or override a deprecated API.
[javac] Note: Recompile with -Xlint:deprecation for details.
[javac] Note: Some input files use unchecked or unsafe operations.
[javac] Note: Recompile with -Xlint:unchecked for details.
[javac] 6 errors
[javac] 5 warnings

BUILD FAILED
/tmp/picard-tools-1.138+dfsg.1/build.xml:154: The following error occurred 
while executing this line:
/tmp/picard-tools-1.138+dfsg.1/build.xml:494: Compile failed; see the compiler 
error output for details.

Total time: 7 seconds
dh_auto_build: ant -Dant.build.javac.source=1.5 -Dant.build.javac.target=1.5 
-Djavac.target=1.5 -Ddebug=true picard-jar javadoc returned exit code 1
debian/rules:17: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2
make[1]: Leaving directory '/tmp/picard-tools-1.138+dfsg.1'
debian/rules:10: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
debuild: fatal error at line 1376:
dpkg-buildpackage -rfakeroot -D -us -uc -b failed


Possibly related to incompatibility with openjdk-8.

Bug#818518: twidge: FTBFS: At least the following dependencies are missing: text

[Martin Michlmayr]

Package: twidge
Version: 1.1.2
Severity: serious

This package fails to build in unstable:

> sbuild (Debian sbuild) 0.68.0 (15 Jan 2016) on dl580gen9-02.hlinux
...
> Linking setup ...
> ./setup configure
> Configuring twidge-1.1.2...
> setup: At least the following dependencies are missing:
> text >=0.11.2.0 && <0.12
> Makefile:6: recipe for target 'all' failed
> make[1]: *** [all] Error 1
> make[1]: Leaving directory '/<>'
> debian/rules:34: recipe for target 'build-stamp' failed

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise

Bug#785714: kexec-tools is broken when using systemd, danger of filesystem corruption

[Jan Stattegger-Sievers]

Hi,

for the second time we ran into this problem and lost again data on
several servers. First time, we assumed a firmware update we ran before
the reboot to be the cause.

This time, there was no firmware update and we looked further into this,
knowing now this is no singular issue. And it turns out: On every kexec
reboot you will loose data, if your servers are doing a significant
amount of work shortly before the reboot, since no umount is done
before the new kernel kicks in.

This definitely needs a fix!

Since the proposed fix changes the behavior of reboot and shutdown -r I
am cc'ing systemd-sysv maintainers.

Regards,
Jan

Bug#818280: upgrade-reports: System is unusable after "aptitute safe-upgrade" [SOLVED]

[Gilles Sadowski]

Hi.

It turned out that the problem was related to LVM partitions not being
"available" while "systemd" was trying to run "fsck" on them.

In maintenance mode, I just ran

 # vgchange -a y theVolumeGroupName

and they were automatically detected, and mounted.
Then the boot sequence could proceed normally.

Why couldn't "systemd" figure out the problem?


Regards,
Gilles

Bug#818294: marked as done (balsa: Please replace build dependency on libwebkit-dev with libwebkitgtk-dev)

[Debian Bug Tracking System]

Your message dated Wed, 16 Mar 2016 13:34:22 +
with message-id 
and subject line Bug#818294: fixed in balsa 2.4.12-3
has caused the Debian Bug report #818294,
regarding balsa: Please replace build dependency on libwebkit-dev with 
libwebkitgtk-dev
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.)


-- 
818294: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818294
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: balsa
Version: 2.4.12-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)

The libwebkit-dev package has been marked as transitional for a few
years now, and I would like to get rid of it soon.

Please replace the build dependency with libwebkitgtk-dev.

Thanks,

Berto

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

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

We believe that the bug you reported is fixed in the latest version of
balsa, 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 818...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Alberto Garcia  (supplier of updated balsa 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, 16 Mar 2016 15:07:46 +0200
Source: balsa
Binary: balsa balsa-dbg
Architecture: source amd64
Version: 2.4.12-3
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Alberto Garcia 
Description:
 balsa  - e-mail client for GNOME
 balsa-dbg  - e-mail client for GNOME - debugging symbols
Closes: 818294
Changes:
 balsa (2.4.12-3) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Michael Biebl ]
   * Remove Debian menu entry.
 .
   [ Alberto Garcia ]
   * debian/control.in:
 - Replace build dependency on libwebkit-dev with libwebkitgtk-dev
   (Closes: #818294).
   * debian/balsa.lintian-overrides:
 - Override 'possible-gpl-code-linked-with-openssl'. Balsa does allow
   linking the code against OpenSSL.
Checksums-Sha1:
 7e7a99532a13ff840530bf090cf625f400de070d 2693 balsa_2.4.12-3.dsc
 071426e035058e3afab8dd13bb921c77ca818e92 12524 balsa_2.4.12-3.debian.tar.xz
 39680d845c317401723d34413121dc7a82ab83b9 1535600 balsa-dbg_2.4.12-3_amd64.deb
 64528f2d0ba42fa75564f22ce39852a8c5931544 2689800 balsa_2.4.12-3_amd64.deb
Checksums-Sha256:
 be75ed60a68ccc49ea96bf91d9869bf7f33e53510fafcccb88c4a7e26eb92352 2693 
balsa_2.4.12-3.dsc
 f080bee6d3a86032816d658d6978380114b6d489b04c460764eafb7b97cbe5c8 12524 
balsa_2.4.12-3.debian.tar.xz
 2d68d0d6afdc3d324ea7eb712241d513df3a35b669d263151b1b5184d1cfad0a 1535600 
balsa-dbg_2.4.12-3_amd64.deb
 7e423f776e710d259b891f0fdde9614875ae948ddaddf00b6e458e89417a63c4 2689800 
balsa_2.4.12-3_amd64.deb
Files:
 c1f3ad2bf4011986bc02a476641cd487 2693 gnome optional balsa_2.4.12-3.dsc
 2cce7a18cca62189614d706c771c73a5 12524 gnome optional 
balsa_2.4.12-3.debian.tar.xz
 2d0dc623af4a3c82714a4b35a3c950a4 1535600 debug extra 
balsa-dbg_2.4.12-3_amd64.deb
 e1c0e18469b705cf45c863c530ae74d6 2689800 gnome optional 
balsa_2.4.12-3_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIVAwUBVulci74yGa8+1BNBAQjbXhAAkM2uD189rZkjOGYyigOpZLU5b5q0Su5J
kU6jwzmbk2qoaZEwpY4Ec2BmaH4PX8JrOtSHNgRXh5ZDzXQEK7zQDL6eLX6pYtCj
Tj6uXxTJb+dZPr0wJU49RWSlLYZ7tj0TG6Dx8OrZif/NUY9wIqIamWZQJSdEcL/y
d2qbAmhJcirzdCW3G/EbvvchLrIXKldk3H6okflZur100e/SeqtO9HyKgvaQNhAm
Q1sJv7N60I2LaVcIbED2NRc3s9wSbNaQAz8dYZZ4vAt1tohTHiZkmqsDEXYhx+ri
IxX0wlXGttLwIqR+MZhTxBi1DG5AzrHd752nuwJdevT90qWwJFSzIF2hVKl4e30O
4mjMk0Pwglwv87d9yocvozqmrdlEaxu3qqKlggpqv0KRaR6q39/lXiiuViEAyMAp
+IcVdNIqhVMfJ8Fm4XsSjBbkv1yDPemtcX5/9sKRdthKcIiDfxsnImhNlil0ZzYv
3Zd83begW7M18/6YZZK/Daq24lfAIQFvi61Q6ntIPLwLqQG4k3sYBXv6gWVLWvEc