Bug#877476: libuim-dev: copyright file missing after upgrade (policy 12.5)

[Andreas Beckmann]

Package: libuim-dev
Version: 1:1.8.6+gh20161003.0.d63dadd-5
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

a test with piuparts revealed that your package misses the copyright
file after an upgrade, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile

After the upgrade /usr/share/doc/$PACKAGE/ is just an empty directory.

This was observed on the following upgrade paths:

  testing -> sid
  stable -> sid

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

0m17.2s ERROR: WARN: Inadequate results from running adequate!
  libuim-dev:amd64: broken-symlink /usr/share/doc/libuim-dev -> uim-common
  libuim-dev:amd64: missing-copyright-file /usr/share/doc/libuim-dev/copyright

0m18.0s DUMP: 
  MISSING COPYRIGHT FILE: /usr/share/doc/libuim-dev/copyright
  # ls -lad /usr/share/doc/libuim-dev
  lrwxrwxrwx 1 root root 10 Aug 16 10:10 /usr/share/doc/libuim-dev -> uim-common
  # ls -la /usr/share/doc/libuim-dev/
  ls: cannot access '/usr/share/doc/libuim-dev/': No such file or directory


Additional info may be available here:
https://wiki.debian.org/MissingCopyrightFile

Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase

It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.maintscript.
Do not forget to add 'Pre-Depends: ${misc:Pre-Depends}' in d/control.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.


cheers,

Andreas


libuim-dev_1:1.8.6+gh20161003.0.d63dadd-5.log.gz
Description: application/gzip

Processed: fixed 877220 in 6.25.0+dfsg-11

[Debian Bug Tracking System]

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

> fixed 877220 6.25.0+dfsg-11
Bug #877220 [node-babel] node-babel: B-D npm not available in testing
There is no source info for the package 'node-babel' at version 
'6.25.0+dfsg-11' with architecture ''
Unable to make a source version for version '6.25.0+dfsg-11'
Marked as fixed in versions 6.25.0+dfsg-11.
> thanks
Stopping processing here.

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

Processed: fixed 877221 in 6.18.0-2

[Debian Bug Tracking System]

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

> fixed 877221 6.18.0-2
Bug #877221 [node-babylon] node-babylon: B-D npm not available in testing
Marked as fixed in versions node-babylon/6.18.0-2.
> thanks
Stopping processing here.

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

Processed: fixed 877218 in 7.0.0-2

[Debian Bug Tracking System]

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

> fixed 877218 7.0.0-2
Bug #877218 [node-gulp-babel] node-gulp-babel: B-D npm not available in testing
Marked as fixed in versions node-gulp-babel/7.0.0-2.
> thanks
Stopping processing here.

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

Bug#876940: boinc: Depends on libwxgtk-webview3.0-0v5 which depends on webkit1

[Olly Betts]

On Thu, Sep 28, 2017 at 10:42:03AM +0200, Christian Beer wrote:
> I'm waiting on the recent upload to unstable on my desktop to test out
> your patch with the debian package. If this is working I would like to
> integrate this upstream. The big difference I see between Olly's patch
> and jengelh's patch is the use of "wxUSE_WEBVIEW" which we need for the
> Windows and Mac version since we don't want to drop webview support
> there.

You probably want to keep using wxWebView on Linux when it's available
too.

I'm afraid I didn't try to make the change optional, which is OK for a
patch in a Debian package, but obviously not suitable for merging
upstream as-is.

Cheers,
Olly

Processed: reassign 868429 to release.debian.org, severity of 868429 is normal ..., usertagging 868429

[Debian Bug Tracking System]

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

> reassign 868429 release.debian.org
Bug #868429 [gstreamer1.0-vaapi] gstreamer1.0-vaapi 1.12.3-1 is uninstallable 
on sid
Bug reassigned from package 'gstreamer1.0-vaapi' to 'release.debian.org'.
No longer marked as found in versions gstreamer-vaapi/1.12.3-1 and 
gstreamer-vaapi/1.12.2-1.
Ignoring request to alter fixed versions of bug #868429 to the same values 
previously set
> severity 868429 normal
Bug #868429 [release.debian.org] gstreamer1.0-vaapi 1.12.3-1 is uninstallable 
on sid
Severity set to 'normal' from 'serious'
> retitle 868429 nmu: gstreamer-vaapi_1.12.3-1
Bug #868429 [release.debian.org] gstreamer1.0-vaapi 1.12.3-1 is uninstallable 
on sid
Changed Bug title to 'nmu: gstreamer-vaapi_1.12.3-1' from 'gstreamer1.0-vaapi 
1.12.3-1 is uninstallable on sid'.
> user release.debian@packages.debian.org
Setting user to release.debian@packages.debian.org (was a...@debian.org).
> usertags 868429 binnmu
There were no usertags set.
Usertags are now: binnmu.
> thanks
Stopping processing here.

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

Processed: user debian...@lists.debian.org, usertagging 872493, usertagging 812138, affects 812138 ...

[Debian Bug Tracking System]

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

> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was a...@debian.org).
> usertags 872493 piuparts
There were no usertags set.
Usertags are now: piuparts.
> usertags 812138 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 812138 + python-qwt3d-qt4
Bug #812138 [pyqwt3d] pyqwt3d: FTBFS with GCC 6: narrowing conversion
Added indication that 812138 affects python-qwt3d-qt4
> usertags 868927 piuparts
Usertags were: qa-ftbfs qa-ftbfs-20170719.
Usertags are now: qa-ftbfs qa-ftbfs-20170719 piuparts.
> affects 868927 + python3-pybedtools
Bug #868927 [src:python-pybedtools] python-pybedtools FTBFS with more than one 
supported Python3 version
Added indication that 868927 affects python3-pybedtools
> usertags 868962 piuparts
Usertags were: qa-ftbfs qa-ftbfs-20170719.
Usertags are now: qa-ftbfs qa-ftbfs-20170719 piuparts.
> affects 868962 + python3-skbio
Bug #868962 [src:python-skbio] python-skbio: FTBFS: Test failures
Added indication that 868962 affects python3-skbio
> usertags 873501 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 873501 + python3-kivy
Bug #873501 [src:kivy] kivy FTBFS with Cython 0.26
Added indication that 873501 affects python3-kivy
> usertags 867558 piuparts
Usertags were: piuparts.
Usertags are now: piuparts.
> affects 867558 + python3-flask-ldapconn
Bug #867558 [src:flask-ldapconn] flask-ldapconn FTBFS: build dependencies 
python-ldap3/python3-ldap3 are only available in more recent versions
Added indication that 867558 affects python3-flask-ldapconn
> usertags 876566 piuparts
There were no usertags set.
Usertags are now: piuparts.
> usertags 869155 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 869155 + design-desktop-graphics
Bug #869155 [src:debian-design] design-desktop-graphics: Please replace gcolor2 
with gpick
Added indication that 869155 affects design-desktop-graphics
> usertags 872494 piuparts
There were no usertags set.
Usertags are now: piuparts.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
812138: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812138
867558: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867558
868927: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868927
868962: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868962
869155: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869155
872494: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872494
873501: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873501
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: node-websocket: sourceful upload needed for the nodejs-abi-48 transition

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + libjs-websocket
Bug #877469 [src:node-websocket] node-websocket: sourceful upload needed for 
the nodejs-abi-48 transition
Added indication that 877469 affects libjs-websocket

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

Bug#877469: node-websocket: sourceful upload needed for the nodejs-abi-48 transition

[Andreas Beckmann]

Source: node-websocket
Version: 1.0.23-3
Severity: serious
Tags: sid buster
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + libjs-websocket

The arch:all package libjs-websocket still depends on nodejs-abi-46,
this requires a sourceful upload (but no changes) to fix.

Is it even correct to have an arch:all package depend on a virtual
abi package?


Andreas

Bug#877463: haskell-vector-algorithms: B-D libghc-vector-dev (< 0.12) but 0.12.0.1-1 is to be installed

[Andreas Beckmann]

Source: haskell-vector-algorithms
Version: 0.7.0.1-6
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

haskell-vector-algorithms cannot be built in sid any more since it
build-depends on a no longer available version of libghc-vector-dev.

Andreas

Processed: notfound 857529 in libgpgmepp-dev, found 857529 in 1.9.0-5, severity of 877454 is serious ...

[Debian Bug Tracking System]

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

> notfound 857529 libgpgmepp-dev
Bug #857529 [libgpgmepp-dev] libgpgmepp-dev: broken symlink: 
/usr/share/doc/libgpgmepp-dev/README.qgpgme -> ../libqgpgme/README
There is no source info for the package 'libgpgmepp-dev' at version 
'libgpgmepp-dev' with architecture ''
Unable to make a source version for version 'libgpgmepp-dev'
No longer marked as found in versions libgpgmepp-dev.
> found 857529 1.9.0-5
Bug #857529 [libgpgmepp-dev] libgpgmepp-dev: broken symlink: 
/usr/share/doc/libgpgmepp-dev/README.qgpgme -> ../libqgpgme/README
Marked as found in versions gpgme1.0/1.9.0-5.
> severity 877454 serious
Bug #877454 [kopano-dev] kopano-dev: missing Depends: kopano-libs (= 
${binary:Version})
Severity set to 'serious' from 'normal'
> found 875419 2.1-1
Bug #875419 [manpages-de] manpages-de: broken symlinks: 
/usr/share/man/de/man4/{tty, console}_ioctl.4.gz -> ../man2/ioctl_{tty, 
console}.2.gz
Marked as found in versions manpages-de/2.1-1.
> found 857409 52.4.0esr-2
Bug #857409 [firefox-esr-dev] firefox-esr-dev: broken symlink: 
/usr/lib/firefox-esr-devel-45/sdk/bin/run-mozilla.sh -> 
../../../firefox-esr/run-mozilla.sh
Marked as found in versions firefox-esr/52.4.0esr-2.
> found 877276 1.18.0+dfsg1-4
Bug #877276 [rust-doc] rust-doc: broken symlink: 
/usr/share/doc/rust-doc/html/highlight.css -> 
../../../javascript/highlight.js/styles/atelier-dune.light.css
Marked as found in versions rustc/1.18.0+dfsg1-4.
> found 859149 0.19.0-1
Bug #859149 [python-sklearn-doc] python-sklearn-doc: broken symlink: 
/usr/share/doc/python-sklearn-doc/html/_static/underscore.js -> 
../../../../javascript/jquery/underscore.js
Marked as found in versions scikit-learn/0.19.0-1.
> found 857404 dvi2dvi/2.0alpha-10
Bug #857404 [dvi2ps-fontdata-ja] dvi2ps-fontdata-ja: broken symlinks: 
/usr/share/texmf/fonts/vf/ptex/a2{wada, vfl, wl, wadaz} -> a2mor2
Marked as found in versions dvi2dvi/2.0alpha-10.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
857404: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857404
857409: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857409
857529: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857529
859149: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859149
875419: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875419
877276: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877276
877454: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877454
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: NMU for zeitgeist 1.0-0.1

[Debian Bug Tracking System]

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

> tags 873868 +pending
Bug #873868 [src:zeitgeist] zeitgeist FTBFS with vala 0.36
Added tag(s) pending.
>
End of message, stopping processing here.

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

Bug#876845: webkit2-sharp FTBFS: dh_makeshlibs: unknown option or error during option parsing; aborting

[Jeremy Bicha]

Control: tags -1 +patch

I'm attaching a trivial patch to fix this bug.

Thanks,
Jeremy Bicha
--- a/debian/rules
+++ b/debian/rules
@@ -18,7 +18,7 @@ override_dh_auto_install:
 	dh_auto_install --parallel --destdir=$(CURDIR)/debian/tmp
 
 override_dh_makeshlibs:
-	dh_makeshlibs -n -plibwebkitgtk3.0-cil
+	dh_makeshlibs -n -plibwebkit2-sharp-4.0-cil
 	dh_makeshlibs --remaining-packages
 
 %:

Processed: Re: webkit2-sharp FTBFS: dh_makeshlibs: unknown option or error during option parsing; aborting

[Debian Bug Tracking System]

Processing control commands:

> tags -1 +patch
Bug #876845 [src:webkit2-sharp] webkit2-sharp FTBFS: dh_makeshlibs: unknown 
option or error during option parsing; aborting
Added tag(s) patch.

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

Bug#877461: logol: broken symlinks: /usr/share/logol/lib/{activation,drmaa}.jar -> ../../java/*.jar

[Andreas Beckmann]

Package: logol
Version: 1.7.5-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

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

1m29.3s ERROR: FAIL: Broken symlinks:
  /usr/share/logol/lib/drmaa.jar -> ../../java/drmaa.jar
  /usr/share/logol/lib/activation.jar -> ../../java/activation.jar

Is logol missing a dependency on libdrmaa1.0-java?
I cannot find activation.jar in the archive at all.

Assuming that logol does not work without these, I'm setting
the severity to serious.


cheers,

Andreas


logol_1.7.5-1.log.gz
Description: application/gzip

Bug#877459: wrong asm in header files causes openjdk ftbfs on i386

[Matthias Klose]

Package: src:systemtap
Version: 3.1-2
Tags: sid buster patch
Severity: serious
Affects: openjdk-8

openjdk-8 currently ftbfs on i386, caused by a wrong asm in a systemtap header.
Please see https://gcc.gnu.org/PR80115 for details.  It is fixed upstream.

Bug#769158: marked as done (munin, munin-node: fails to upgrade from 'sid' - trying to overwrite /usr/share/man/man5/munin.conf.5.gz)

[Debian Bug Tracking System]

Your message dated Mon, 02 Oct 2017 00:19:14 +
with message-id 
and subject line Bug#769158: fixed in munin 2.999.6-4
has caused the Debian Bug report #769158,
regarding munin, munin-node: fails to upgrade from 'sid' - trying to overwrite 
/usr/share/man/man5/munin.conf.5.gz
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.)


-- 
769158: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769158
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: munin,munin-node
Version: 2.1.9-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
http://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

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

  Selecting previously unselected package munin.
  Preparing to unpack .../archives/munin_2.1.9-1_all.deb ...
  Unpacking munin (2.1.9-1) ...
  dpkg: error processing archive /var/cache/apt/archives/munin_2.1.9-1_all.deb 
(--unpack):
   trying to overwrite '/usr/share/man/man5/munin.conf.5.gz', which is also in 
package munin-doc 2.0.24-1
  Errors were encountered while processing:
   /var/cache/apt/archives/munin_2.1.9-1_all.deb

  Selecting previously unselected package munin-node.
  Preparing to unpack .../munin-node_2.1.9-1_all.deb ...
  Unpacking munin-node (2.1.9-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/munin-node_2.1.9-1_all.deb (--unpack):
   trying to overwrite '/usr/share/man/man5/munin-node.conf.5.gz', which is 
also in package munin-doc 2.0.24-1
  Errors were encountered while processing:
   /var/cache/apt/archives/munin-node_2.1.9-1_all.deb


cheers,

Andreas


munin-doc=2.0.24-1_munin=2.1.9-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: munin
Source-Version: 2.999.6-4

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

Debian distribution maintenance software
pp.
Holger Levsen  (supplier of updated munin 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: Mon, 02 Oct 2017 01:53:30 +0200
Source: munin
Binary: munin-node munin-plugins-core munin-plugins-extra munin-plugins-http 
munin-plugins-mysql munin-plugins-pgsql munin-plugins-snmp munin-plugins-ldap 
munin-plugins-irc munin-plugins-dns munin-plugins-mail munin-plugins-time 
munin-plugins-network munin-plugins-jenkins libmunin-perl libmunin-master-perl 
libmunin-node-perl libmunin-plugin-perl libmunin-plugin-http-perl 
libmunin-plugin-snmp-perl libmunin-plugin-pgsql-perl munin munin-common 
munin-async munin-doc
Architecture: source
Version: 2.999.6-4
Distribution: experimental
Urgency: medium
Maintainer: Munin Debian Maintainers 
Changed-By: Holger Levsen 
Description:
 libmunin-master-perl - perl modules for munin master
 libmunin-node-perl - perl module Munin::Node
 libmunin-perl - common perl modules for munin
 libmunin-plugin-http-perl - perl bindings for HTTP munin plugins
 libmunin-plugin-perl - perl bindings for munin plugins
 libmunin-plugin-pgsql-perl - perl bindings for Postgresql munin plugins
 libmunin-plugin-snmp-perl - perl bindings for SNMP munin plugins
 munin  - network-wide graphing framework (grapher/gatherer)
 munin-async - network-wide graphing framework (async master/client)
 munin-common - network-wide graphing framework (common)
 munin-doc  - network-wide graphing framework (documentation)
 munin-node - network-wide graphing framework (node)
 munin-plugins-core - network-wide graphing framework (plugins for node)
 munin-plugins-dns - munin plugins for monitoring DNS servers
 munin-plugins-extra - community contributed plugins for munin node
 munin-plugins-http - munin plugins for monitoring web 

Bug#877457: trafficserver-dev: missing Depends: trafficserver (= ${binary:Version})

[Andreas Beckmann]

Package: trafficserver-dev
Version: 7.0.0-5
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

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

0m23.5s ERROR: FAIL: Broken symlinks:
  /usr/lib/trafficserver/libtsutil.so -> libtsutil.so.7.0.0
  /usr/lib/trafficserver/libtsmgmt.so -> libtsmgmt.so.7.0.0
  /usr/lib/trafficserver/libtsconfig.so -> libtsconfig.so.7.0.0
  /usr/lib/trafficserver/libatscppapi.so -> libatscppapi.so.7.0.0


Given that these are in a package subdirectory, maybe they are not intended
to be used by other packages and should not have .so links in the -dev
package at all.

Otherwise if would probably be useful to split out to shared libraries
into (a) separate package(s).


cheers,

Andreas


trafficserver-dev_7.0.0-5.log.gz
Description: application/gzip

Bug#876810: marked as done (engauge-digitizer FTBFS with libopenjp2-7-dev 2.2.0-1)

[Debian Bug Tracking System]

Your message dated Mon, 02 Oct 2017 00:19:03 +
with message-id 
and subject line Bug#876810: fixed in engauge-digitizer 10.3+ds.1-3
has caused the Debian Bug report #876810,
regarding engauge-digitizer FTBFS with libopenjp2-7-dev 2.2.0-1
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.)


-- 
876810: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876810
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: engauge-digitizer
Version: 10.3+ds.1-2
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/engauge-digitizer.html

...
In file included from src/main/MainWindow.cpp:73:0:
src/Jpeg2000/Jpeg2000.h:10:10: fatal error: openjpeg.h: No such file or 
directory
 #include "openjpeg.h" // Before Jpeg2000Convert.h
  ^~~~
compilation terminated.
Makefile:12595: recipe for target 'src/.objs/MainWindow.o' failed
make[2]: *** [src/.objs/MainWindow.o] Error 1
--- End Message ---
--- Begin Message ---
Source: engauge-digitizer
Source-Version: 10.3+ds.1-3

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

Debian distribution maintenance software
pp.
Tobias Winchen  (supplier of updated engauge-digitizer 
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, 01 Oct 2017 20:38:24 +0200
Source: engauge-digitizer
Binary: engauge-digitizer engauge-digitizer-doc
Architecture: source
Version: 10.3+ds.1-3
Distribution: unstable
Urgency: medium
Maintainer: Tobias Winchen 
Changed-By: Tobias Winchen 
Description:
 engauge-digitizer - interactively extracts numbers from bitmap graphs or maps
 engauge-digitizer-doc - engauge-digitizer user manual and tutorial
Closes: 876810
Changes:
 engauge-digitizer (10.3+ds.1-3) unstable; urgency=medium
 .
   * Automatized include location for openjpeg (Closes: #876810)
Checksums-Sha1:
 87201bfaed6d9c0f22f067c98ef7815ff8eebf13 2219 engauge-digitizer_10.3+ds.1-3.dsc
 024f716b67a70b41893b29e1e4fdae8b4e426f0b 8052 
engauge-digitizer_10.3+ds.1-3.debian.tar.xz
 c4c4e19682783574c9d52b19d4900b8a82e78911 5435 
engauge-digitizer_10.3+ds.1-3_source.buildinfo
Checksums-Sha256:
 e19b81b0f121124d8d610f5e8b46d2de6714d10c001229959eab23dbfda0b969 2219 
engauge-digitizer_10.3+ds.1-3.dsc
 c5336832251d56a858417ec4383b4a13c2f4a9fe7a5a3ff33870b90da950ab40 8052 
engauge-digitizer_10.3+ds.1-3.debian.tar.xz
 1c09cc31f7cdc4cdb01a3974075dd07abd4300a170f4e43261383f383569b061 5435 
engauge-digitizer_10.3+ds.1-3_source.buildinfo
Files:
 9af6451491dec9212025874b51a594db 2219 science optional 
engauge-digitizer_10.3+ds.1-3.dsc
 ac349f41f3f4f41e93825c5a4bb9449e 8052 science optional 
engauge-digitizer_10.3+ds.1-3.debian.tar.xz
 5ad44ac4ac43c4ef001b33d3b61bafda 5435 science optional 
engauge-digitizer_10.3+ds.1-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAlnRgUcACgkQweDZLphv
fH5PPRAApcxjNA+Pd8U0+SnSAGDQIc+KN+d1sIzFs1ORed+P641p6s8EJlEv8dqw
vqwhJLRatftzv+L1TnVIiIR+iHC7m27pYEYgG7QNUN/dWtzmtovVOucSWr+DxokO
pFv8TCex0nB0yVf8uZNSv16Pg+fm1XnAnwpDZuwMp23JCYsERVVQFQp3PBwI+vMZ
0yBJPUnMcg4rBkSbAJTrXyIOkukyIKfH8hsGk/SmidkUap3QigJlRzBq8NE0E0Zz
bUklAdlbjwDGd02IqSL2LmXdVTg0iVWIVwNLZvy7KLGZ/Ytq+jT73Hey3n/SY41O
RhXX47wORmtPb6lIwzS4la2IDvTDo/9a3GuJ6jnspODrDYS31VSgmPQc2/P63oL0
NiF2hz+xluuXDVcWHShH++XO0V3f6wD9qQVystNhHpS51suL6gshS3PY3GyK5NXb
11tsiTnRmsTtjd8xMRAdYf4H40TWMUviWCli1dxiyMD1K+NXD8xnsFo4zRt0/n3o
HECA/XaH30GjRO/6O05pf11SRNvUBamsXQnvLP/ZpyjvuiHbP9faBuy1FJmi93Ad
aAgpoB0kBgypb6EFmOjCcrIRfh5+0Y0LATGbKXXDTk1iQ64iHcGebFyhjF6yPd5K
0KyAykqY3z8SjUrQgve4vLY0QPWYh1aP5e3tUc40lP/wEhOf99Y=
=Z3C9
-END PGP SIGNATURE End Message ---

Bug#877449: gcc-5-cross FTBFS with debhelper 10.9

[Matthias Klose]

Control: tags -1 + pending

On 02.10.2017 00:26, Adrian Bunk wrote:
> Source: gcc-5-cross
> Version: 26
> Severity: serious
> 
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/gcc-5-cross.html
> 
> ...
> dh_installdirs -plibgfortran-5-dev usr/lib/gcc-cross/s390x-linux-gnu/5
> dh_installdirs: Requested unknown package libgfortran-5-dev via -p/--package, 
> expected one of: gcc-5-s390x-linux-gnu-base gcc-5-cross-base 
> libgcc-5-dev-s390x-cross libgcc4-s390x-cross libgcc4-dbg-s390x-cross 
> lib64gcc-5-dev-s390x-cross lib32gcc-5-dev-s390x-cross 
> libn32gcc-5-dev-s390x-cross libx32gcc-5-dev-s390x-cross gcc-5-s390x-linux-gnu 
> gcc-5-multilib-s390x-linux-gnu gcc-5-plugin-dev-s390x-linux-gnu 
> gcc-5-hppa64-linux-gnu cpp-5-s390x-linux-gnu g++-5-s390x-linux-gnu 
> g++-5-multilib-s390x-linux-gnu gobjc++-5-s390x-linux-gnu 
> gobjc++-5-multilib-s390x-linux-gnu gobjc-5-s390x-linux-gnu 
> gobjc-5-multilib-s390x-linux-gnu libobjc-5-dev-s390x-cross 
> lib64objc-5-dev-s390x-cross lib32objc-5-dev-s390x-cross 
> libn32objc-5-dev-s390x-cross libx32objc-5-dev-s390x-cross 
> gfortran-5-s390x-linux-gnu gfortran-5-multilib-s390x-linux-gnu 
> libgfortran-5-dev-s390x-cross lib64gfortran-5-dev-s390x-cross 
> lib32gfortran-5-dev-s390x-cross libn32gfortran-5-dev-s390x-cross 
> libx32gfortran-5-dev-s390x-cross gccgo-5-s390x-l
>  inux-gnu gccgo-5-multilib-s390x-linux-gnu libgo7-s390x-cross 
> libgo7-dbg-s390x-cross lib64go7-s390x-cross lib64go7-dbg-s390x-cross 
> lib32go7-s390x-cross lib32go7-dbg-s390x-cross libn32go7-s390x-cross 
> libn32go7-dbg-s390x-cross libx32go7-s390x-cross libx32go7-dbg-s390x-cross 
> gcj-5-s390x-linux-gnu libstdc++-5-dev-s390x-cross libstdc++-5-pic-s390x-cross 
> libstdc++6-5-dbg-s390x-cross lib32stdc++-5-dev-s390x-cross 
> lib32stdc++6-5-dbg-s390x-cross lib64stdc++-5-dev-s390x-cross 
> lib64stdc++6-5-dbg-s390x-cross libn32stdc++-5-dev-s390x-cross 
> libn32stdc++6-5-dbg-s390x-cross libx32stdc++-5-dev-s390x-cross 
> libx32stdc++6-5-dbg-s390x-cross gnat-5-s390x-linux-gnu 
> gnat-5-sjlj-s390x-linux-gnu libgnat-5-s390x-cross libgnat-5-dbg-s390x-cross 
> libgnatvsn5-dev-s390x-cross libgnatvsn5-s390x-cross 
> libgnatvsn5-dbg-s390x-cross libgnatprj5-dev-s390x-cross 
> libgnatprj5-s390x-cross libgnatprj5-dbg-s390x-cross gdc-5-s390x-linux-gnu 
> gdc-5-multilib-s390x-linux-gnu gcc-5-source
> dh_installdirs: unknown option or error during option parsing; aborting
> debian/rules.d/binary-fortran.mk:252: recipe for target 
> 'stamps/08-binary-stamp-libgfortran-dev' failed
> make[2]: *** [stamps/08-binary-stamp-libgfortran-dev] Error 25

Bug#872233: lib{, x}32objc-5-dev: broken symlink: /usr/lib/gcc/x86_64-linux-gnu/5/{, x}32/libobjc_gc.so -> ../../../../../lib32/libobjc_gc.so.4

[Matthias Klose]

Control: tags -1 + pending

On 02.10.2017 01:57, Andreas Beckmann wrote:
> Followup-For: Bug #872233
> Control: affects -1 + lib64objc-5-dev
> 
> There is also a similar broken symlink in lib64objc-5-dev
> 
> 0m40.2s ERROR: FAIL: Broken symlinks:
>   /usr/lib/gcc/i686-linux-gnu/5/64/libobjc_gc.so -> 
> ../../../../../lib64/libobjc_gc.so.4

yes, known.

Processed: Re: Bug#872233: lib{, x}32objc-5-dev: broken symlink: /usr/lib/gcc/x86_64-linux-gnu/5/{, x}32/libobjc_gc.so -> ../../../../../lib32/libobjc_gc.so.4

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #872233 [lib32objc-5-dev,libx32objc-5-dev] lib{, x}32objc-5-dev: broken 
symlink: /usr/lib/gcc/x86_64-linux-gnu/5/{, x}32/libobjc_gc.so -> 
../../../../../lib32/libobjc_gc.so.4
Added tag(s) pending.

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

Processed: Re: Bug#877449: gcc-5-cross FTBFS with debhelper 10.9

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #877449 [src:gcc-5-cross] gcc-5-cross FTBFS with debhelper 10.9
Added tag(s) pending.

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

Bug#877456: freerdp2-dev: missing Depends: libfreerdp-shadow-subsystem2-2 (= ${binary:Version})

[Andreas Beckmann]

Package: freerdp2-dev
Version: 2.0.0~git20170725.1.1648deb+dfsg1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

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

1m18.6s ERROR: FAIL: Broken symlinks:
  /usr/lib/i386-linux-gnu/libfreerdp-shadow-subsystem2.so -> 
libfreerdp-shadow-subsystem2.so.2


cheers,

Andreas


freerdp2-dev_2.0.0~git20170725.1.1648deb+dfsg1-1.log.gz
Description: application/gzip

Bug#872233: lib{, x}32objc-5-dev: broken symlink: /usr/lib/gcc/x86_64-linux-gnu/5/{, x}32/libobjc_gc.so -> ../../../../../lib32/libobjc_gc.so.4

[Andreas Beckmann]

Followup-For: Bug #872233
Control: affects -1 + lib64objc-5-dev

There is also a similar broken symlink in lib64objc-5-dev

0m40.2s ERROR: FAIL: Broken symlinks:
  /usr/lib/gcc/i686-linux-gnu/5/64/libobjc_gc.so -> 
../../../../../lib64/libobjc_gc.so.4


Andreas

Processed: Re: lib{, x}32objc-5-dev: broken symlink: /usr/lib/gcc/x86_64-linux-gnu/5/{, x}32/libobjc_gc.so -> ../../../../../lib32/libobjc_gc.so.4

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + lib64objc-5-dev
Bug #872233 [lib32objc-5-dev,libx32objc-5-dev] lib{, x}32objc-5-dev: broken 
symlink: /usr/lib/gcc/x86_64-linux-gnu/5/{, x}32/libobjc_gc.so -> 
../../../../../lib32/libobjc_gc.so.4
Added indication that 872233 affects lib64objc-5-dev

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

Bug#853349: marked as done (codeblocks: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Sun, 01 Oct 2017 23:49:07 +
with message-id 
and subject line Bug#853349: fixed in codeblocks 16.01+dfsg-2.1
has caused the Debian Bug report #853349,
regarding codeblocks: ftbfs with GCC-7
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.)


-- 
853349: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853349
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:codeblocks
Version: 16.01+dfsg-2
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/codeblocks_16.01+dfsg-2_unstable_gcc7.log
The last lines of the build log are at the end of this report.

To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-7/porting_to.html

[...]
../../../../src/include/scripting/sqplus/sqplus.h: In member function 'bool 
SqPlus::ScriptStringVar::compareCaseInsensitive(const 
SqPlus::ScriptStringVar&)':
../../../../src/include/scripting/sqplus/sqplus.h:153:12: error: there are no 
arguments to '_stricmp' that depend on a template parameter, so a declaration 
of '_stricmp' must be available [-fpermissive]
 return _stricmp(s,_s.s) == 0;
^~~~
In file included from SquirrelBindingsUtils.cpp:1:0:
../../../../src/include/scripting/sqplus/sqplus.h: In member function 'bool 
SqPlus::ScriptStringVar::operator==(const 
SqPlus::ScriptStringVar&)':
../../../../src/include/scripting/sqplus/sqplus.h:150:12: error: there are no 
arguments to '_strcmp' that depend on a template parameter, so a declaration of 
'_strcmp' must be available [-fpermissive]
 return _strcmp(s,_s.s) == 0;
^~~
../../../../src/include/scripting/sqplus/sqplus.h:150:12: note: (if you use 
'-fpermissive', G++ will accept your code, but allowing the use of an 
undeclared name is deprecated)
../../../../src/include/scripting/sqplus/sqplus.h: In member function 'bool 
SqPlus::ScriptStringVar::compareCaseInsensitive(const 
SqPlus::ScriptStringVar&)':
../../../../src/include/scripting/sqplus/sqplus.h:153:12: error: there are no 
arguments to '_stricmp' that depend on a template parameter, so a declaration 
of '_stricmp' must be available [-fpermissive]
 return _stricmp(s,_s.s) == 0;
^~~~
In file included from SqPlus.cpp:1:0:
../../../../src/include/scripting/sqplus/sqplus.h: In member function 'bool 
SqPlus::ScriptStringVar::operator==(const 
SqPlus::ScriptStringVar&)':
../../../../src/include/scripting/sqplus/sqplus.h:150:12: error: there are no 
arguments to '_strcmp' that depend on a template parameter, so a declaration of 
'_strcmp' must be available [-fpermissive]
 return _strcmp(s,_s.s) == 0;
^~~
../../../../src/include/scripting/sqplus/sqplus.h:150:12: note: (if you use 
'-fpermissive', G++ will accept your code, but allowing the use of an 
undeclared name is deprecated)
../../../../src/include/scripting/sqplus/sqplus.h: In member function 'bool 
SqPlus::ScriptStringVar::compareCaseInsensitive(const 
SqPlus::ScriptStringVar&)':
../../../../src/include/scripting/sqplus/sqplus.h:153:12: error: there are no 
arguments to '_stricmp' that depend on a template parameter, so a declaration 
of '_stricmp' must be available [-fpermissive]
 return _stricmp(s,_s.s) == 0;
^~~~
Makefile:501: recipe for target 'SquirrelObject.lo' failed
make[5]: *** [SquirrelObject.lo] Error 1
make[5]: *** Waiting for unfinished jobs
Makefile:501: recipe for target 'SquirrelBindingsUtils.lo' failed
make[5]: *** [SquirrelBindingsUtils.lo] Error 1
Makefile:501: recipe for target 'SquirrelVM.lo' failed
make[5]: *** 

Bug#875794: marked as done (ruby-sentry-raven: /usr/bin/raven already provided by python3-raven)

[Debian Bug Tracking System]

Your message dated Sun, 01 Oct 2017 23:05:05 +
with message-id 
and subject line Bug#875794: fixed in ruby-sentry-raven 2.6.3-1
has caused the Debian Bug report #875794,
regarding ruby-sentry-raven: /usr/bin/raven already provided by python3-raven
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.)


-- 
875794: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875794
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby-sentry-raven
Version: 2.5.3-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files.

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

  Selecting previously unselected package ruby-sentry-raven.
  Preparing to unpack .../78-ruby-sentry-raven_2.5.3-1_all.deb ...
  Unpacking ruby-sentry-raven (2.5.3-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-J44vvD/78-ruby-sentry-raven_2.5.3-1_all.deb (--unpack):
   trying to overwrite '/usr/bin/raven', which is also in package python3-raven 
6.0.0-1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-J44vvD/78-ruby-sentry-raven_2.5.3-1_all.deb


cheers,

Andreas


python3-raven=6.0.0-1_ruby-sentry-raven=2.5.3-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: ruby-sentry-raven
Source-Version: 2.6.3-1

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

Debian distribution maintenance software
pp.
Cédric Boutillier  (supplier of updated ruby-sentry-raven 
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, 01 Oct 2017 23:35:32 +0200
Source: ruby-sentry-raven
Binary: ruby-sentry-raven
Architecture: source
Version: 2.6.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Cédric Boutillier 
Description:
 ruby-sentry-raven - client interface for the Sentry error logger
Closes: 875794
Changes:
 ruby-sentry-raven (2.6.3-1) unstable; urgency=medium
 .
   * Team upload
   * New upstream version 2.6.3
   * Bump Standards-Version to 4.1.1 (no changes needed)
   * Refresh disable-tests-requiring-rubocop.patch
   * Install raven script as example instead of in /usr/bin (Closes: #875794)
Checksums-Sha1:
 ba4aaed321925a0893c8d263727294e2a793ccdd 1921 ruby-sentry-raven_2.6.3-1.dsc
 6e4b30a53aa2f5b51ecd15a36fa8b015a3e19879 97528 
ruby-sentry-raven_2.6.3.orig.tar.gz
 379862c67954a2e0bf22736cfc0adbf2d560f88f 2904 
ruby-sentry-raven_2.6.3-1.debian.tar.xz
 958d61472e98b75fc52a3c0c7632099908239651 7857 
ruby-sentry-raven_2.6.3-1_source.buildinfo
Checksums-Sha256:
 aa52488bbbe87557287136d8be3717daebb7bdbe086e3b72217b355a89c4639b 1921 
ruby-sentry-raven_2.6.3-1.dsc
 1f62aabd24956c2c26829f3673903c76442f746a7c7e50ae44504142bbecbb60 97528 
ruby-sentry-raven_2.6.3.orig.tar.gz
 47cc2411bd82744adbe89e3fde698f007903dfd8d6612edd352c1275c6d998f5 2904 
ruby-sentry-raven_2.6.3-1.debian.tar.xz
 577d15856bb2aaf8f63afda13a816fa47083938ef240f7c5d8462b879bb544ba 7857 
ruby-sentry-raven_2.6.3-1_source.buildinfo
Files:
 a722f89890f581a5f0777274a5ee7c4c 1921 ruby optional 
ruby-sentry-raven_2.6.3-1.dsc
 9a70feec1e804e34e3f7c2c75ddec482 97528 ruby optional 
ruby-sentry-raven_2.6.3.orig.tar.gz
 bbfbd585d74babccd7c0b40af6b97448 2904 ruby optional 
ruby-sentry-raven_2.6.3-1.debian.tar.xz
 4c20e978207bfc97a87e479d24c1692d 7857 ruby optional 
ruby-sentry-raven_2.6.3-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEEnM1rMZ2/jkCrGr0aia+CtznNIXoFAlnRcWEACgkQia+CtznN
IXp+iwf5AbpEWgRUnq1zvFCJzyRX5tPb/zuW305nVHywXePnd7ct1Gse4AX/ltgn
vi5bHZbj6AgS6DEW5gYYIqTN9zdUsGZhZg8NfANcDshOUMtNvghBJzR1el1YhZ1O
y5oRxYsr6rUPqZp6/9rzR/lDQj9OaxIvKHhAwXw1rl23QMgpzSW0RW7Q3sVv068O
bwKI3MnyR0hPbNIjIPvtsNA3dwtA6tKVlRYd4efsUJ0xMdy/g5gXq7BXJ1w1PRKV

Bug#875794: marked as pending

[Cédric Boutillier]

tag 875794 pending
thanks

Hello,

Bug #875794 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:


https://anonscm.debian.org/cgit/pkg-ruby-extras/ruby-sentry-raven.git/commit/?id=b8f8a6c

---
commit b8f8a6caca7a7b4cc585ce8ff98ae4f1a939c1c4
Author: Cédric Boutillier 
Date:   Sun Oct 1 23:36:01 2017 +0200

target unstable

diff --git a/debian/changelog b/debian/changelog
index f84b6c0..4433f71 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,13 @@
+ruby-sentry-raven (2.6.3-1) unstable; urgency=medium
+
+  * Team upload
+  * New upstream version 2.6.3
+  * Bump Standards-Version to 4.1.1 (no changes needed)
+  * Refresh disable-tests-requiring-rubocop.patch
+  * Install raven script as example instead of in /usr/bin (Closes: #875794)
+
+ -- Cédric Boutillier   Sun, 01 Oct 2017 23:35:32 +0200
+
 ruby-sentry-raven (2.5.3-1) unstable; urgency=medium
 
   * Team upload

Processed: Bug#875794 marked as pending

[Debian Bug Tracking System]

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

> tag 875794 pending
Bug #875794 [ruby-sentry-raven] ruby-sentry-raven: /usr/bin/raven already 
provided by python3-raven
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#877134: marked as done (assimp: FTBFS on i386: can't cd to obj-i386-linux-gnu/doc)

[Debian Bug Tracking System]

Your message dated Sun, 01 Oct 2017 22:34:09 +
with message-id 
and subject line Bug#877134: fixed in assimp 4.0.1~dfsg-1~exp2
has caused the Debian Bug report #877134,
regarding assimp: FTBFS on i386: can't cd to obj-i386-linux-gnu/doc
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.)


-- 
877134: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877134
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: assimp
Version: 4.0.1~dfsg-1~exp1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

assimp FTBFS on i386:

https://buildd.debian.org/status/fetch.php?pkg=assimp=i386=4.0.1%7Edfsg-1%7Eexp1=1505108449=0

[...]
[100%] Linking CXX executable assimp
cd "/<>/obj-i686-linux-gnu/tools/assimp_cmd" && /usr/bin/cmake -E 
cmake_link_script CMakeFiles/assimp_cmd.dir/link.txt --verbose=1
/usr/bin/c++  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fopenmp -g -fvisibility=hidden -fPIC -Wall -std=c++0x  
-Wl,-z,relro -Wl,-z,now -Wl,--as-needed -rdynamic 
CMakeFiles/assimp_cmd.dir/CompareDump.cpp.o 
CMakeFiles/assimp_cmd.dir/ImageExtractor.cpp.o 
CMakeFiles/assimp_cmd.dir/Main.cpp.o CMakeFiles/assimp_cmd.dir/WriteDumb.cpp.o 
CMakeFiles/assimp_cmd.dir/Info.cpp.o CMakeFiles/assimp_cmd.dir/Export.cpp.o  -o 
assimp  -L"/<>/obj-i686-linux-gnu"  
-L"/<>/obj-i686-linux-gnu/lib" 
-Wl,-rpath,"/<>/obj-i686-linux-gnu:/<>/obj-i686-linux-gnu/lib:/<>/obj-i686-linux-gnu/code:"
 ../../code/libassimp.so.4.0.1 -lz ../../contrib/irrXML/libIrrXML.a -lminizip 
-lrt 
make[4]: Leaving directory '/<>/obj-i686-linux-gnu'
[100%] Built target assimp_cmd
make[3]: Leaving directory '/<>/obj-i686-linux-gnu'
/usr/bin/cmake -E cmake_progress_start 
"/<>/obj-i686-linux-gnu/CMakeFiles" 0
make[2]: Leaving directory '/<>/obj-i686-linux-gnu'
dh_auto_build --buildsystem=pybuild -- \
-d port/PyAssimp/
I: pybuild base:184: /usr/bin/python setup.py build 
running build
running build_py
creating /<>/.pybuild/pythonX.Y_2.7/build/pyassimp
copying pyassimp/helper.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/pyassimp
copying pyassimp/postprocess.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/pyassimp
copying pyassimp/structs.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/pyassimp
copying pyassimp/core.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/pyassimp
copying pyassimp/material.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/pyassimp
copying pyassimp/errors.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/pyassimp
copying pyassimp/formats.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/pyassimp
copying pyassimp/__init__.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/pyassimp
I: pybuild base:184: /usr/bin/python3.6 setup.py build 
running build
running build_py
creating /<>/.pybuild/pythonX.Y_3.6/build/pyassimp
copying pyassimp/helper.py -> 
/<>/.pybuild/pythonX.Y_3.6/build/pyassimp
copying pyassimp/postprocess.py -> 
/<>/.pybuild/pythonX.Y_3.6/build/pyassimp
copying pyassimp/structs.py -> 
/<>/.pybuild/pythonX.Y_3.6/build/pyassimp
copying pyassimp/core.py -> 
/<>/.pybuild/pythonX.Y_3.6/build/pyassimp
copying pyassimp/material.py -> 
/<>/.pybuild/pythonX.Y_3.6/build/pyassimp
copying pyassimp/errors.py -> 
/<>/.pybuild/pythonX.Y_3.6/build/pyassimp
copying pyassimp/formats.py -> 
/<>/.pybuild/pythonX.Y_3.6/build/pyassimp
copying pyassimp/__init__.py -> 
/<>/.pybuild/pythonX.Y_3.6/build/pyassimp
I: pybuild base:184: /usr/bin/python3 setup.py build 
running build
running build_py
creating /<>/.pybuild/pythonX.Y_3.5/build/pyassimp
copying pyassimp/helper.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/pyassimp
copying pyassimp/postprocess.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/pyassimp
copying pyassimp/structs.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/pyassimp
copying pyassimp/core.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/pyassimp
copying pyassimp/material.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/pyassimp
copying pyassimp/errors.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/pyassimp
copying pyassimp/formats.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/pyassimp
copying pyassimp/__init__.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/pyassimp
cd obj-i386-linux-gnu/doc && doxygen Doxyfile
/bin/sh: 1: cd: can't cd to obj-i386-linux-gnu/doc
debian/rules:52: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2

Looks there is a mixture of DEB_*_MULTIARCH and DEB_*_GNU_TYPE being used
by the build process. These are not identical on i386.


Andreas
--- End Message ---
--- Begin Message ---
Source: assimp
Source-Version: 

Bug#877449: gcc-5-cross FTBFS with debhelper 10.9

[Adrian Bunk]

Source: gcc-5-cross
Version: 26
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/gcc-5-cross.html

...
dh_installdirs -plibgfortran-5-dev usr/lib/gcc-cross/s390x-linux-gnu/5
dh_installdirs: Requested unknown package libgfortran-5-dev via -p/--package, 
expected one of: gcc-5-s390x-linux-gnu-base gcc-5-cross-base 
libgcc-5-dev-s390x-cross libgcc4-s390x-cross libgcc4-dbg-s390x-cross 
lib64gcc-5-dev-s390x-cross lib32gcc-5-dev-s390x-cross 
libn32gcc-5-dev-s390x-cross libx32gcc-5-dev-s390x-cross gcc-5-s390x-linux-gnu 
gcc-5-multilib-s390x-linux-gnu gcc-5-plugin-dev-s390x-linux-gnu 
gcc-5-hppa64-linux-gnu cpp-5-s390x-linux-gnu g++-5-s390x-linux-gnu 
g++-5-multilib-s390x-linux-gnu gobjc++-5-s390x-linux-gnu 
gobjc++-5-multilib-s390x-linux-gnu gobjc-5-s390x-linux-gnu 
gobjc-5-multilib-s390x-linux-gnu libobjc-5-dev-s390x-cross 
lib64objc-5-dev-s390x-cross lib32objc-5-dev-s390x-cross 
libn32objc-5-dev-s390x-cross libx32objc-5-dev-s390x-cross 
gfortran-5-s390x-linux-gnu gfortran-5-multilib-s390x-linux-gnu 
libgfortran-5-dev-s390x-cross lib64gfortran-5-dev-s390x-cross 
lib32gfortran-5-dev-s390x-cross libn32gfortran-5-dev-s390x-cross 
libx32gfortran-5-dev-s390x-cross gccgo-5-s390x-l
 inux-gnu gccgo-5-multilib-s390x-linux-gnu libgo7-s390x-cross 
libgo7-dbg-s390x-cross lib64go7-s390x-cross lib64go7-dbg-s390x-cross 
lib32go7-s390x-cross lib32go7-dbg-s390x-cross libn32go7-s390x-cross 
libn32go7-dbg-s390x-cross libx32go7-s390x-cross libx32go7-dbg-s390x-cross 
gcj-5-s390x-linux-gnu libstdc++-5-dev-s390x-cross libstdc++-5-pic-s390x-cross 
libstdc++6-5-dbg-s390x-cross lib32stdc++-5-dev-s390x-cross 
lib32stdc++6-5-dbg-s390x-cross lib64stdc++-5-dev-s390x-cross 
lib64stdc++6-5-dbg-s390x-cross libn32stdc++-5-dev-s390x-cross 
libn32stdc++6-5-dbg-s390x-cross libx32stdc++-5-dev-s390x-cross 
libx32stdc++6-5-dbg-s390x-cross gnat-5-s390x-linux-gnu 
gnat-5-sjlj-s390x-linux-gnu libgnat-5-s390x-cross libgnat-5-dbg-s390x-cross 
libgnatvsn5-dev-s390x-cross libgnatvsn5-s390x-cross libgnatvsn5-dbg-s390x-cross 
libgnatprj5-dev-s390x-cross libgnatprj5-s390x-cross libgnatprj5-dbg-s390x-cross 
gdc-5-s390x-linux-gnu gdc-5-multilib-s390x-linux-gnu gcc-5-source
dh_installdirs: unknown option or error during option parsing; aborting
debian/rules.d/binary-fortran.mk:252: recipe for target 
'stamps/08-binary-stamp-libgfortran-dev' failed
make[2]: *** [stamps/08-binary-stamp-libgfortran-dev] Error 25

Bug#877300: marked as done (digikam FTBFS: undefined references)

[Debian Bug Tracking System]

Your message dated Mon, 2 Oct 2017 01:05:10 +0300
with message-id <20171001220510.a6wowhmtmon4gqo4@localhost>
and subject line digikam 4:5.6.0-1 builds
has caused the Debian Bug report #877300,
regarding digikam FTBFS: undefined references
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.)


-- 
877300: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877300
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: digikam
Version: 4:5.3.0-3
Severity: serious

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

...
../models/CMakeFiles/digikamdatabasemodels_src.dir/imagemodel.cpp.o: In 
function `Digikam::ImageModel::ImageModel(QObject*)':
./obj-x86_64-linux-gnu/core/libs/models/./core/libs/models/imagemodel.cpp:134: 
undefined reference to `vtable for Digikam::ImageModel'
../models/CMakeFiles/digikamdatabasemodels_src.dir/imagemodel.cpp.o: In 
function `Digikam::ImageModel* qobject_cast(QObject*)':
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:514: undefined reference to 
`Digikam::ImageModel::staticMetaObject'
../models/CMakeFiles/digikamdatabasemodels_src.dir/imagemodel.cpp.o: In 
function `int qRegisterNormalizedMetaType(QByteArray 
const&, Digikam::ImageModel**, 
QtPrivate::MetaTypeDefinedHelper::Defined&&(!QMetaTypeId2::IsBuiltIn)>::DefinedType)':
/usr/include/x86_64-linux-gnu/qt5/QtCore/qmetatype.h:1682: undefined reference 
to `Digikam::ImageModel::staticMetaObject'
../models/CMakeFiles/digikamdatabasemodels_src.dir/imagemodel.cpp.o: In 
function `Digikam::ImageModel* qobject_cast(QObject*)':
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:514: undefined reference to 
`Digikam::ImageModel::staticMetaObject'
../models/CMakeFiles/digikamdatabasemodels_src.dir/imagemodel.cpp.o: In 
function `int qRegisterNormalizedMetaType(QByteArray 
const&, Digikam::ImageModel**, 
QtPrivate::MetaTypeDefinedHelper::Defined&&(!QMetaTypeId2::IsBuiltIn)>::DefinedType)':
/usr/include/x86_64-linux-gnu/qt5/QtCore/qmetatype.h:1682: undefined reference 
to `Digikam::ImageModel::staticMetaObject'
../models/CMakeFiles/digikamdatabasemodels_src.dir/imagemodel.cpp.o: In 
function `Digikam::ImageModel::~ImageModel()':
./obj-x86_64-linux-gnu/core/libs/models/./core/libs/models/imagemodel.cpp:143: 
undefined reference to `vtable for Digikam::ImageModel'
../models/CMakeFiles/digikamdatabasemodels_src.dir/imagemodel.cpp.o: In 
function `int qRegisterNormalizedMetaType(QByteArray 
const&, Digikam::ImageModel**, 
QtPrivate::MetaTypeDefinedHelper::Defined&&(!QMetaTypeId2::IsBuiltIn)>::DefinedType)':
/usr/include/x86_64-linux-gnu/qt5/QtCore/qmetatype.h:1682: undefined reference 
to `Digikam::ImageModel::staticMetaObject'
../models/CMakeFiles/digikamdatabasemodels_src.dir/imagemodel.cpp.o: In 
function `Digikam::ImageModel::slotImageChange(Digikam::ImageChangeset const&)':
./obj-x86_64-linux-gnu/core/libs/models/./core/libs/models/imagemodel.cpp:1337: 
undefined reference to 
`Digikam::ImageModel::imageChange(Digikam::ImageChangeset const&, 
QItemSelection const&)'
../models/CMakeFiles/digikamdatabasemodels_src.dir/imagemodel.cpp.o: In 
function `Digikam::ImageModel::slotImageTagChange(Digikam::ImageTagChangeset 
const&)':
./obj-x86_64-linux-gnu/core/libs/models/./core/libs/models/imagemodel.cpp:1364: 
undefined reference to 
`Digikam::ImageModel::imageTagChange(Digikam::ImageTagChangeset const&, 
QItemSelection const&)'
../models/CMakeFiles/digikamdatabasemodels_src.dir/imagemodel.cpp.o: In 
function `Digikam::ImageModel::publiciseInfos(QList const&, 
QList const&)':
./obj-x86_64-linux-gnu/core/libs/models/./core/libs/models/imagemodel.cpp:807: 
undefined reference to 
`Digikam::ImageModel::imageInfosAboutToBeAdded(QList 
const&)'
./obj-x86_64-linux-gnu/core/libs/models/./core/libs/models/imagemodel.cpp:827: 
undefined reference to 
`Digikam::ImageModel::imageInfosAdded(QList const&)'
../models/CMakeFiles/digikamdatabasemodels_src.dir/imagemodel.cpp.o: In 
function `Digikam::ImageModel::removeRowPairs(QList > const&)':
./obj-x86_64-linux-gnu/core/libs/models/./core/libs/models/imagemodel.cpp:1057: 
undefined reference to 
`Digikam::ImageModel::imageInfosRemoved(QList const&)'

Bug#873778: Fix for the mozjs52 build on armel

[Michael Biebl]

Am 01.10.2017 um 20:03 schrieb Simon McVittie:
> Control: clone -1 -2 Control: retitle -2 FTBFS on mips64el: various
> test failures
> 
> On Sat, 23 Sep 2017 at 12:29:08 +0200, Emilio Pozuelo Monfort wrote:
>> Let's track the mips64el failure in a different bug, as it's 
>> completely different from this.
> 
> Cloned away. I haven't investigated those failures at all.
> 
>> The remaining problem seems to be a big-endian issue (mips, s390x, 
>> hppa, powerpc, sparc64). ppc64 fails in a slightly different
>> manner, might just be it's failing earlier for a different reason
>> but would also suffer from this bug.

[..]

Fwiw, we had on #debian-gnome the other
day, where we also identified the icu data file as a culprit.
Unfortunately that alone doesn't fix the s390x build. Pulling the
patches from firefox-esr (especially the s390x atomics patch), get's us
down to 10 unexpected test-suite failures on s390x.
As you already found out though is, that generating the icu data file is
not easily possible, as the mozjs package seems to miss the
tools/scripts to do so.

Anyway, copying the full IRC log for completeness sake


> [00:09:22]  so, what's going to happen with mozjs? Any progress on 
> that front?
> [00:39:02]  get permission to ignore the build failures on mips & 
> s390x?
> [01:03:37]  has firefox/mozja or mhommey been notified about this?
> [01:15:40]  I haven't talked to mhomney about mozjs
> [01:16:31]  I believe ptomato (the gjs maintainer) knows about our 
> build issues on others arches
> [01:34:20]  jbicha: I see that the firefox-esr package as specific 
> rules for big/little endian
> [01:35:36]  
> https://anonscm.debian.org/cgit/pkg-mozilla/iceweasel.git/tree/debian/rules?h=esr52/master#n142
>  ff
> [01:35:49]  pochu suspected an endian issue, right?
> [01:36:46]  
> https://anonscm.debian.org/cgit/pkg-mozilla/iceweasel.git/tree/debian/rules?h=esr52/master#n285
> [01:38:02]  I wonder if we shouldn't simply use firefox-esr as basis 
> for building the mozjs library
> [01:38:28]  maybe we could convince mike to provide a bit of 
> debian/rules magic which would disable the non-mozjs parts
> [01:39:02]  and we simply reupload src:firefox-esr with a different 
> source name
> [01:40:11]  building libmozjs directly from src:firefox-esr is 
> probably not a good idea, given that stable get's new major updates of it
> [01:41:24]  somehow it would be awesome though to benefit from 
> mike's experience and knowledge with the firefox package
> [01:41:29]  Ubuntu 17.04's mozjs38 actually uses the final Firefox 38 
> ESR tarball because Mozilla has so far been pretty bad about making mozjs 
> releases
> [01:41:38]  mbiebl_: The architectures with the "Exception: Failed to 
> test XUL condition" error are the big endian architectures except 
> m68k/powerpcspe (build with nocheck).
> [01:42:01]  I stripped the tarball down because the full tarball is 
> very slow to work with
> [01:42:02]  mips64el looks unrelated.
> [01:42:35]  I believe mips64el is a minor issue we can easily work 
> around
> [01:45:38]  jbicha: I suppose that 17.04 does not directly build the 
> libmozjs binary packages from src:firefox-esr but uses a different src 
> package name?
> [01:46:35]  yes, it uses a slightly different version of 
> https://anonscm.debian.org/git/pkg-gnome/mozjs38.git which is just an older 
> version of our mozjs52 packaging
> [01:46:45]  Ubuntu does not offer firefox-esr
> [02:10:36]  the be icu from firefox-esr seems to be a bingo
> [02:10:52]  I'm now getting further with mozjs52 on s390x
> [02:12:58]  further as in the test-suite passes and you get a .deb 
> or the test-suite fails at a later point?
> [02:14:31]  the test suite starts (I have to double-check the 
> unexpected failures with a clean build)
> [02:22:33]  bunk: glandium also pointed me to 
> https://sources.debian.net/patches/firefox-esr/52.3.0esr-2/porting/Fix-crashes-in-AtomicOperations-none-on-s390x.patch/
> [02:24:06]  that patch alone didn't help on Ubuntu but maybe in 
> combination with other stuff…
> [02:26:10]  Ubuntu hasn't been able to build Firefox on s390x in like 
> a year
> [02:27:39]  glandium also suggests to disable jit on mips*
> [02:30:37]  he advises against using src:firefox-esr as a basis to 
> build the libmozjs libraries
> [02:31:05]  but we should have a look at the patches he ships in 
> firefox-esr which touch src/js
> [02:31:17]  js/src, I mean
> [02:58:58]  counting TEST-UNEXPECTED-FAIL:
> [02:59:04]  ppc64el: 2
> [02:59:08]  mips64el: 3
> [02:59:14]  s390x (icu): 104
> [02:59:19]  s390x (icu+atomic): 10
> [02:59:24]  s390x (icu+atomic+gcc-6): 10
> [03:07:18]  there's an unofficial 52.4 release we could grab too
> [10:31:31]  FTR, what I used for "the be icu" was cp 
> firefox-esr-52.4.0esr/config/external/icu/data/icudt58b.dat 
> ./mozjs52-52.3.1/config/external/icu/data/icudt58l.dat
> [10:34:48]  adding s390x to the list of architectures where test 
> results are ignored gives me a successful build with debs
> 

Bug#877433: marked as done (missing dependency on r-cran-arm)

[Debian Bug Tracking System]

Your message dated Sun, 01 Oct 2017 21:37:08 +
with message-id 
and subject line Bug#877433: fixed in r-cran-mi 1.0-5
has caused the Debian Bug report #877433,
regarding missing dependency on r-cran-arm
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.)


-- 
877433: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877433
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: r-cran-mi
Version: 1.9-3-1
Severity: serious

Loading the package with r-cran-arm uninstalled fails:

> library(mi)
Loading required package: Matrix
Loading required package: stats4
Error in loadNamespace(j <- i[[1L]], c(lib.loc, .libPaths()), versionCheck = 
vI[[j]]) :
  there is no package called 'arm'
Error: package or namespace load failed for 'mi'
>

Cheers,

-- 
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  http://sebastien.villemot.name
⠈⠳⣄  http://www.debian.org


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: r-cran-mi
Source-Version: 1.0-5

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

Debian distribution maintenance software
pp.
Sébastien Villemot  (supplier of updated r-cran-mi 
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, 01 Oct 2017 21:31:08 +0200
Source: r-cran-mi
Binary: r-cran-mi
Architecture: source
Version: 1.0-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Sébastien Villemot 
Description:
 r-cran-mi  - GNU R package for Missing Data Imputation and Model Checking -- m
Closes: 877433
Changes:
 r-cran-mi (1.0-5) unstable; urgency=medium
 .
   * Team upload.
   * Rebuild for r-api-3.4 transition.
   * Convert to dh-r.
 Incidentally, this implies that r-cran-arm is a Depends. (Closes: #877433)
   * Bump to debhelper compat level 10.
   * Use canonical CRAN homepage.
   * Use secure URLs for Vcs-* fields.
   * Use secure URL for Format field of d/copyright.
   * Bump to Standards-Version 4.1.1.
   * d/watch: do not mangle upstream version number, bump to file format v4.
   * d/copyright: fix ordering of paragraphs.
   * Add README.source documenting the .rda files.
   * Add autopkgtest for unit tests.
   * tests-no-betareg.patch: new patch, makes tests succeed without betareg.
Checksums-Sha1:
 bc74877913df97128e02002cf0d0bf68ee8aa722 2054 r-cran-mi_1.0-5.dsc
 970ded4f4a23d19c252ad4f7d6a23c41d1bbaf22 3288 r-cran-mi_1.0-5.debian.tar.xz
 1eb80b73dbd68e142c45c6b966226edbebebf5e0 8954 r-cran-mi_1.0-5_source.buildinfo
Checksums-Sha256:
 ef7ed71ca5cac2d80e0dc0508e202f8be707dadb4bbe25d1b00194d32b44ee20 2054 
r-cran-mi_1.0-5.dsc
 72344739822254db89e932e66e5aff56d9114f7a894b41e5c0584c52a25e1dd4 3288 
r-cran-mi_1.0-5.debian.tar.xz
 d4f1ab22bf03978fd2265db05a3c17930232a0364c2db25fe730afc934e2b4b7 8954 
r-cran-mi_1.0-5_source.buildinfo
Files:
 cc66867c61ff5b6a2d06b0bef97185f8 2054 gnu-r optional r-cran-mi_1.0-5.dsc
 00862a4a01fba1c439850b75ca6cec36 3288 gnu-r optional 
r-cran-mi_1.0-5.debian.tar.xz
 87bfe8a6988ec4f6096af8c8ee7eef7b 8954 gnu-r optional 
r-cran-mi_1.0-5_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEU5UdlScuDFuCvoxKLOzpNQ7OvkoFAlnRSbUACgkQLOzpNQ7O
vkqGUA/+PYdkLUT/mroNLKIuFjmkfupiy2mOJwV800GFF3PY0XZliykvvKvkFVNK
sUyXvBD3LRfm4NSbLfVPE4s4W97qrUgx9l7L3vwp5Uqbx6Ku7rpv6J0i9ZFOxE13
18UgqTaaMkf9eaWKdNRKDOcKKw4i33HDiJ2azclNoKdpJAn4tMLbAyAM7EbECJiC
ytUu/c81I7dDEoAZv6zZUPFD6u1+iz3c3wrH/ZxGDXUcrHclZGnvALjhGWPe9+em
v2FvAZY/xL4FlaAKhzyqWmTSiMxCRxhI5gfHBp80YcxjnXsGPCKh2+7C8/fhNrb4
RCyZvLJFEwFyEEPBirbLykvji+PhzjDRimdYJSy5Ql7hYMx6vTUY6BxIobDJhzKY
LhZQvNkFDLpggnUORNvKkIb4pqZT5qjWBjxBdBlL2TAUFZhZx8yfWDWAREhyJPgu
lHzw8O5ui/OWXGbPMqbTy1FdVTW0QpSvUrfJAfGItDOR9rquKhpJ/+1aE+iPQPCe
JjqXHAf76TA22H4YCKHy4vUfcjeejbzyYT2BsNMxYXltwhfCG5Sb1cnZayXOxHxN
RABiyDbrvHBDBeojeWr5XNuCuVm58VQh+4gtjiky407t/6lWCCjJESd3xuNpNUSR
lhLv3ccHehkH4docxFGlbktl0tTJrq0WppJwSLOHf1lmaLG2Zrw=
=4uPq
-END 

Processed: forcibly merging 869060 869067 869066 869061 869056 869054 869048 869033

[Debian Bug Tracking System]

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

> forcemerge 869060 869067 869066 869061 869056 869054 869048 869033
Bug #869060 {Done: Cédric Boutillier } 
[ruby-rails-dom-testing] too strict version dependency on nokogiri declared in 
gemspecs
Bug #869032 {Done: Cédric Boutillier } 
[ruby-rails-dom-testing] ruby-api-pagination: FTBFS: ERROR: Test "ruby2.3" 
failed.
Bug #869034 {Done: Cédric Boutillier } 
[ruby-rails-dom-testing] too strict version dependency on nokogiri declared in 
gemspecs
Bug #869035 {Done: Cédric Boutillier } 
[ruby-rails-dom-testing] ruby-simple-form: FTBFS: ERROR: Test "ruby2.3" failed.
Bug #869037 {Done: Cédric Boutillier } 
[ruby-rails-dom-testing] too strict version dependency on nokogiri declared in 
gemspecs
Bug #869061 [ruby-rails-dom-testing] ruby-cucumber-rails: FTBFS: ERROR: Test 
"ruby2.3" failed.
Marked Bug as done
Marked as fixed in versions ruby-rails-dom-testing/1.0.6-2.
Marked as found in versions ruby-rails-dom-testing/1.0.6-1.
Bug #869033 [ruby-rails-dom-testing] ruby-actionpack-action-caching: FTBFS: 
ERROR: Test "ruby2.3" failed.
Marked Bug as done
Marked as fixed in versions ruby-rails-dom-testing/1.0.6-2.
Marked as found in versions ruby-rails-dom-testing/1.0.6-1.
Bug #869048 [ruby-rails-dom-testing] ruby-actionpack-xml-parser: FTBFS: ERROR: 
Test "ruby2.3" failed.
Marked Bug as done
Marked as fixed in versions ruby-rails-dom-testing/1.0.6-2.
Marked as found in versions ruby-rails-dom-testing/1.0.6-1.
Bug #869066 [ruby-rails-dom-testing] ruby-diaspora-federation-rails: FTBFS: 
ERROR: Test "ruby2.3" failed.
Marked Bug as done
Marked as fixed in versions ruby-rails-dom-testing/1.0.6-2.
Marked as found in versions ruby-rails-dom-testing/1.0.6-1.
Bug #869067 [ruby-rails-dom-testing] ruby-devise-lastseenable: FTBFS: ERROR: 
Test "ruby2.3" failed.
Marked Bug as done
Marked as fixed in versions ruby-rails-dom-testing/1.0.6-2.
Marked as found in versions ruby-rails-dom-testing/1.0.6-1.
Bug #869056 [ruby-rails-dom-testing] ruby-rails-admin: FTBFS: ERROR: Test 
"ruby2.3" failed.
Marked Bug as done
Marked as fixed in versions ruby-rails-dom-testing/1.0.6-2.
Marked as found in versions ruby-rails-dom-testing/1.0.6-1.
Bug #869054 [ruby-rails-dom-testing] ruby-dalli: FTBFS: ERROR: Test "ruby2.3" 
failed.
Marked Bug as done
Marked as fixed in versions ruby-rails-dom-testing/1.0.6-2.
Marked as found in versions ruby-rails-dom-testing/1.0.6-1.
Bug #869032 {Done: Cédric Boutillier } 
[ruby-rails-dom-testing] ruby-api-pagination: FTBFS: ERROR: Test "ruby2.3" 
failed.
Bug #869034 {Done: Cédric Boutillier } 
[ruby-rails-dom-testing] too strict version dependency on nokogiri declared in 
gemspecs
Bug #869035 {Done: Cédric Boutillier } 
[ruby-rails-dom-testing] ruby-simple-form: FTBFS: ERROR: Test "ruby2.3" failed.
Bug #869037 {Done: Cédric Boutillier } 
[ruby-rails-dom-testing] too strict version dependency on nokogiri declared in 
gemspecs
Merged 869032 869033 869034 869035 869037 869048 869054 869056 869060 869061 
869066 869067
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
869032: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869032
869033: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869033
869034: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869034
869035: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869035
869037: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869037
869048: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869048
869054: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869054
869056: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869056
869060: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869060
869061: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869061
869066: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869066
869067: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869067
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: reassign 869048 to ruby-rails-dom-testing

[Debian Bug Tracking System]

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

> reassign 869048 ruby-rails-dom-testing
Bug #869048 [src:ruby-actionpack-xml-parser] ruby-actionpack-xml-parser: FTBFS: 
ERROR: Test "ruby2.3" failed.
Bug reassigned from package 'src:ruby-actionpack-xml-parser' to 
'ruby-rails-dom-testing'.
No longer marked as found in versions ruby-actionpack-xml-parser/1.0.2-2.
Ignoring request to alter fixed versions of bug #869048 to the same values 
previously set
> thanks
Stopping processing here.

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

Processed: reassign 869033 to ruby-rails-dom-testing

[Debian Bug Tracking System]

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

> reassign 869033 ruby-rails-dom-testing
Bug #869033 [src:ruby-actionpack-action-caching] 
ruby-actionpack-action-caching: FTBFS: ERROR: Test "ruby2.3" failed.
Bug reassigned from package 'src:ruby-actionpack-action-caching' to 
'ruby-rails-dom-testing'.
No longer marked as found in versions ruby-actionpack-action-caching/1.1.1-4.
Ignoring request to alter fixed versions of bug #869033 to the same values 
previously set
> thanks
Stopping processing here.

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

Processed: reassign 869056 to ruby-rails-dom-testing

[Debian Bug Tracking System]

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

> reassign 869056 ruby-rails-dom-testing
Bug #869056 [src:ruby-rails-admin] ruby-rails-admin: FTBFS: ERROR: Test 
"ruby2.3" failed.
Bug reassigned from package 'src:ruby-rails-admin' to 'ruby-rails-dom-testing'.
No longer marked as found in versions ruby-rails-admin/0.8.1+dfsg-3.
Ignoring request to alter fixed versions of bug #869056 to the same values 
previously set
> thanks
Stopping processing here.

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

Processed: reassign 869054 to ruby-rails-dom-testing

[Debian Bug Tracking System]

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

> reassign 869054 ruby-rails-dom-testing
Bug #869054 [src:ruby-dalli] ruby-dalli: FTBFS: ERROR: Test "ruby2.3" failed.
Bug reassigned from package 'src:ruby-dalli' to 'ruby-rails-dom-testing'.
No longer marked as found in versions ruby-dalli/2.7.4-1.
Ignoring request to alter fixed versions of bug #869054 to the same values 
previously set
> thanks
Stopping processing here.

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

Processed: reassign 869061 to ruby-rails-dom-testing

[Debian Bug Tracking System]

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

> reassign 869061 ruby-rails-dom-testing
Bug #869061 [src:ruby-cucumber-rails] ruby-cucumber-rails: FTBFS: ERROR: Test 
"ruby2.3" failed.
Bug reassigned from package 'src:ruby-cucumber-rails' to 
'ruby-rails-dom-testing'.
No longer marked as found in versions ruby-cucumber-rails/1.4.3-1.
Ignoring request to alter fixed versions of bug #869061 to the same values 
previously set
> thanks
Stopping processing here.

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

Processed: reassign 869066 to ruby-rails-dom-testing

[Debian Bug Tracking System]

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

> reassign 869066 ruby-rails-dom-testing
Bug #869066 [src:ruby-diaspora-federation-rails] 
ruby-diaspora-federation-rails: FTBFS: ERROR: Test "ruby2.3" failed.
Bug reassigned from package 'src:ruby-diaspora-federation-rails' to 
'ruby-rails-dom-testing'.
No longer marked as found in versions ruby-diaspora-federation-rails/0.1.4-2.
Ignoring request to alter fixed versions of bug #869066 to the same values 
previously set
> thanks
Stopping processing here.

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

Processed: reassign 869067 to ruby-rails-dom-testing

[Debian Bug Tracking System]

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

> reassign 869067 ruby-rails-dom-testing
Bug #869067 [src:ruby-devise-lastseenable] ruby-devise-lastseenable: FTBFS: 
ERROR: Test "ruby2.3" failed.
Bug reassigned from package 'src:ruby-devise-lastseenable' to 
'ruby-rails-dom-testing'.
No longer marked as found in versions ruby-devise-lastseenable/0.0.6-1.
Ignoring request to alter fixed versions of bug #869067 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#872275: marked as done (slic3r-prusa: Loadable library and perl binary mismatch)

[Debian Bug Tracking System]

Your message dated Sun, 01 Oct 2017 21:09:15 +
with message-id 
and subject line Bug#872275: fixed in slic3r-prusa 1.37.1+dfsg2-2
has caused the Debian Bug report #872275,
regarding slic3r-prusa: Loadable library and perl binary mismatch
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.)


-- 
872275: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872275
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: slic3r-prusa
Version: 1.31.4-1
Severity: important

Dear Maintainer,

After an upgrade, it no longer works and throws this error:

"buildtmp/XS.c: loadable library and perl binaries are mismatched (got
handshake key 0xdb80080, needed 0xde00080)"

Could this be a dependency problem?



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

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

Versions of packages slic3r-prusa depends on:
ii  libboost-geometry-utils-perl   0.15-2+b6
ii  libboost-system1.62.0  1.62.0+dfsg-4+b1
ii  libboost-thread1.62.0  1.62.0+dfsg-4+b1
ii  libc6  2.24-12
ii  libencode-locale-perl  1.05-1
ii  libgcc11:7.1.0-10
ii  libio-stringy-perl 2.111-2
ii  libmath-convexhull-monotonechain-perl  0.1-1+b6
ii  libmath-geometry-voronoi-perl  1.3-2+b5
ii  libmath-planepath-perl 124-1
ii  libmoo-perl2.003002-1
ii  libperl5.26 [libtime-hires-perl]   5.26.0-5
ii  libstdc++6 7.1.0-10
pn  libstorable-perl   
ii  perl   5.26.0-5

Versions of packages slic3r-prusa recommends:
ii  libclass-xsaccessor-perl  1.19-2+b9
ii  libio-all-perl0.86-2
ii  libopengl-perl0.7000+dfsg-1
ii  libpdf-api2-perl  2.030-1
ii  libsvg-perl   2.64-1
ii  libwx-glcanvas-perl   0.09-3+b5
ii  libwx-perl1:0.9932-2
ii  libxml-sax-expatxs-perl   1.33-2+b4

slic3r-prusa suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: slic3r-prusa
Source-Version: 1.37.1+dfsg2-2

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

Debian distribution maintenance software
pp.
Chow Loong Jin  (supplier of updated slic3r-prusa 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, 02 Oct 2017 02:24:50 +0800
Source: slic3r-prusa
Binary: slic3r-prusa
Architecture: source amd64
Version: 1.37.1+dfsg2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian 3-D Printing Packages 
<3dprinter-gene...@lists.alioth.debian.org>
Changed-By: Chow Loong Jin 
Description:
 slic3r-prusa - G-code generator for 3D printers
Closes: 869638 872275
Changes:
 slic3r-prusa (1.37.1+dfsg2-2) unstable; urgency=medium
 .
   * [7337428] Ack 1.37.0+dfsg-1.1 NMU:
 - Fix "Loadable library and perl binary mismatch":
   add override_dh_perl in debian/rules to make dh_perl search for perl
   modules in the private directory as well. (Closes: #872275)
   * [b962ed5] Import patch that fixes big-endian support in admesh
 (Closes: #869638)
   * [96ddc54] Bump Standards-Version
   * [8fd9f76] Update StartupWMClass.
   * [d077f2a] Update slic3r-prusa's desktop to open files
Checksums-Sha1:
 8bf0818d047b6c43ab76e4d5125f51d86e82151c 2587 slic3r-prusa_1.37.1+dfsg2-2.dsc
 08621945160499809be6c874faef1f82d90ffa23 29364 
slic3r-prusa_1.37.1+dfsg2-2.debian.tar.xz
 2b305263b950b0bac196a773105e9d6199425476 24124598 
slic3r-prusa-dbgsym_1.37.1+dfsg2-2_amd64.deb
 07d3f981b5015136449a19bc1f5b840e3631ae91 19235 

Processed: forcibly merging 869034 869035 869032

[Debian Bug Tracking System]

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

> forcemerge 869034 869035 869032
Bug #869034 {Done: Cédric Boutillier } 
[ruby-rails-dom-testing] too strict version dependency on nokogiri declared in 
gemspecs
Bug #869037 {Done: Cédric Boutillier } 
[ruby-rails-dom-testing] too strict version dependency on nokogiri declared in 
gemspecs
Bug #869060 {Done: Cédric Boutillier } 
[ruby-rails-dom-testing] too strict version dependency on nokogiri declared in 
gemspecs
Bug #869032 [ruby-rails-dom-testing] ruby-api-pagination: FTBFS: ERROR: Test 
"ruby2.3" failed.
Marked Bug as done
Marked as fixed in versions ruby-rails-dom-testing/1.0.6-2.
Marked as found in versions ruby-rails-dom-testing/1.0.6-1.
Bug #869035 [ruby-rails-dom-testing] ruby-simple-form: FTBFS: ERROR: Test 
"ruby2.3" failed.
Marked Bug as done
Marked as fixed in versions ruby-rails-dom-testing/1.0.6-2.
Marked as found in versions ruby-rails-dom-testing/1.0.6-1.
Bug #869037 {Done: Cédric Boutillier } 
[ruby-rails-dom-testing] too strict version dependency on nokogiri declared in 
gemspecs
Bug #869060 {Done: Cédric Boutillier } 
[ruby-rails-dom-testing] too strict version dependency on nokogiri declared in 
gemspecs
Merged 869032 869034 869035 869037 869060
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
869032: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869032
869034: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869034
869035: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869035
869037: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869037
869060: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869060
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#869638: marked as done (slic3r-prusa FTBFS on big endian: admesh works correctly on little endian machines only)

[Debian Bug Tracking System]

Your message dated Sun, 01 Oct 2017 21:09:15 +
with message-id 
and subject line Bug#869638: fixed in slic3r-prusa 1.37.1+dfsg2-2
has caused the Debian Bug report #869638,
regarding slic3r-prusa FTBFS on big endian: admesh works correctly on little 
endian machines only
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.)


-- 
869638: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869638
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: slic3r-prusa
Version: 1.36.0+dfsg-1
Severity: serious

https://buildd.debian.org/status/package.php?p=slic3r-prusa=sid

...
mips-linux-gnu-gcc -I/usr/lib/mips-linux-gnu/perl/5.26/CORE -fPIC -D_REENTRANT 
-D_GNU_SOURCE -DDEBIAN -fwrapv -fno-strict-aliasing -pipe -I/usr/local/include 
-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -xc++ -Isrc/libslic3r 
-I/usr/include/eigen3 -I/usr/lib/mips-linux-gnu/wx/include/gtk2-unicode-3.0 
-I/usr/include/wx-3.0 -D_GLIBCXX_USE_C99 -DHAS_BOOL -DNOGDI -DSLIC3RXS 
-DBOOST_ASIO_DISABLE_KQUEUE -std=c++11 -DSLIC3R_GUI -DSLIC3R_PRUS -DUNICODE 
-D_FILE_OFFSET_BITS=64 -DWXUSINGDLL -D__WXGTK__ -pthread -DBOOST_LOG_DYN_LINK 
-DBOOST_LIBS -DNDEBUG -Isrc -Ibuildtmp -c -D_REENTRANT -D_GNU_SOURCE -DDEBIAN 
-fwrapv -fno-strict-aliasing -pipe -I/usr/local/include -D_LARGEFILE_SOURCE 
-D_FILE_OFFSET_BITS=64 -g -O2 
-fdebug-prefix-map=/<>/slic3r-prusa-1.36.0+dfsg=. 
-fstack-protector-strong -Wformat -Werror=format-security -g -O2 
-fdebug-prefix-map=/<>/slic3r-prusa-1.36.0+dfsg=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -o src/admesh/n
 ormals.o src/admesh/normals.c
In file included from src/admesh/normals.c:28:0:
src/admesh/stl.h:32:2: error: #error "admesh works correctly on little endian 
machines only!"
 #error "admesh works correctly on little endian machines only!"
  ^
error building src/admesh/normals.o from 'src/admesh/normals.c' at 
/usr/share/perl/5.26/ExtUtils/CBuilder/Base.pm line 174.
dh_auto_build: perl Build --install_path arch=/usr/lib/slic3r-prusa/ returned 
exit code 2
debian/rules:17: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2



If this is not fixable with reasonable effort, an RM bug for the old mips
binary should be sent against ftp.debian.org and this bug downgraded to
important.
--- End Message ---
--- Begin Message ---
Source: slic3r-prusa
Source-Version: 1.37.1+dfsg2-2

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

Debian distribution maintenance software
pp.
Chow Loong Jin  (supplier of updated slic3r-prusa 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, 02 Oct 2017 02:24:50 +0800
Source: slic3r-prusa
Binary: slic3r-prusa
Architecture: source amd64
Version: 1.37.1+dfsg2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian 3-D Printing Packages 
<3dprinter-gene...@lists.alioth.debian.org>
Changed-By: Chow Loong Jin 
Description:
 slic3r-prusa - G-code generator for 3D printers
Closes: 869638 872275
Changes:
 slic3r-prusa (1.37.1+dfsg2-2) unstable; urgency=medium
 .
   * [7337428] Ack 1.37.0+dfsg-1.1 NMU:
 - Fix "Loadable library and perl binary mismatch":
   add override_dh_perl in debian/rules to make dh_perl search for perl
   modules in the private directory as well. (Closes: #872275)
   * [b962ed5] Import patch that fixes big-endian support in admesh
 (Closes: #869638)
   * [96ddc54] Bump Standards-Version
   * [8fd9f76] Update StartupWMClass.
   * [d077f2a] Update slic3r-prusa's desktop to open files
Checksums-Sha1:
 8bf0818d047b6c43ab76e4d5125f51d86e82151c 2587 slic3r-prusa_1.37.1+dfsg2-2.dsc
 08621945160499809be6c874faef1f82d90ffa23 29364 
slic3r-prusa_1.37.1+dfsg2-2.debian.tar.xz
 2b305263b950b0bac196a773105e9d6199425476 24124598 
slic3r-prusa-dbgsym_1.37.1+dfsg2-2_amd64.deb
 07d3f981b5015136449a19bc1f5b840e3631ae91 19235 
slic3r-prusa_1.37.1+dfsg2-2_amd64.buildinfo
 

Processed: reassign 869035 to ruby-rails-dom-testing

[Debian Bug Tracking System]

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

> reassign 869035 ruby-rails-dom-testing
Bug #869035 [src:ruby-simple-form] ruby-simple-form: FTBFS: ERROR: Test 
"ruby2.3" failed.
Bug reassigned from package 'src:ruby-simple-form' to 'ruby-rails-dom-testing'.
No longer marked as found in versions ruby-simple-form/3.2.0-1.
Ignoring request to alter fixed versions of bug #869035 to the same values 
previously set
> thanks
Stopping processing here.

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

Processed: reassign 869032 to ruby-rails-dom-testing

[Debian Bug Tracking System]

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

> reassign 869032 ruby-rails-dom-testing
Bug #869032 [src:ruby-api-pagination] ruby-api-pagination: FTBFS: ERROR: Test 
"ruby2.3" failed.
Bug reassigned from package 'src:ruby-api-pagination' to 
'ruby-rails-dom-testing'.
No longer marked as found in versions ruby-api-pagination/4.2.0-1.
Ignoring request to alter fixed versions of bug #869032 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#873868: NMU for zeitgeist 1.0-0.1

[Jeremy Bicha]

Dear maintainer,

I've prepared an NMU for zeitgeist (versioned as 1.0-0.1) to fix
this RC bug and uploaded it to DELAYED/10. Please feel free to tell me
if I should delay it longer.

I have temporarily pushed my packaging changes to
https://anonscm.debian.org/git/collab-maint/zeitgeist.git?h=debian%2Fwip-jbicha-zg1

Here's the changelog entry:

  [ Jeremy Bicha ]
  * Non-maintainer upload.
  * New upstream release (Closes: #873868) (LP: #1665902)
  * Bump debhelper compat to 10
  * Bump Standards-Version to 4.1.1
  * Convert to automatic dbgsym package
  * debian/control:
- Drop Build-Depends on intltool
- Have library suggest instead of recommend zeitgeist
  * debian/rules:
- Don't ignore test failures
- Use dh_install --fail-missing instead of --skip-missing
  * Drop patches applied in new release
- Give-the-D-Bus-service-files-the-correct-names.patch
- Add-a-systemd-user-service-for-each-D-Bus-session-se.patch
- fix_autocomplete.diff
- fix-test-crash.patch
- thread-default-context.patch

  [ Iain Lane ]
  * Fix debian/patches/startup-database-vacuum.patch
- The vacuum mode is now included upstream
- Move the wrapper script to a file in debian/ and install that
- Call the wrapper and allow it to fail so that zeitgeist starts for new
  users (LP: #1666495)
  * debian/patches/0001-Fix-placeholder-in-systemd-service-template.patch:
Cherry-pick. Fix substitution in systemd unit file.

Thanks,
Jeremy Bicha

Bug#876811: marked as done (qsstv FTBFS with libopenjp2-7-dev 2.2.0-1)

[Debian Bug Tracking System]

Your message dated Sun, 01 Oct 2017 21:08:27 +
with message-id 
and subject line Bug#876811: fixed in qsstv 9.2.4+repack-2
has caused the Debian Bug report #876811,
regarding qsstv FTBFS with libopenjp2-7-dev 2.2.0-1
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.)


-- 
876811: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876811
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qsstv
Version: 9.2.4+repack-1
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/qsstv.html

...
In file included from widgets/imageviewer.cpp:28:0:
utils/jp2io.h:3:10: fatal error: openjpeg.h: No such file or directory
 #include "openjpeg.h"
  ^~~~
compilation terminated.
Makefile:2763: recipe for target 'imageviewer.o' failed
make[3]: *** [imageviewer.o] Error 1
--- End Message ---
--- Begin Message ---
Source: qsstv
Source-Version: 9.2.4+repack-2

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

Debian distribution maintenance software
pp.
Dave Hibberd  (supplier of updated qsstv 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, 01 Oct 2017 20:35:46 +0100
Source: qsstv
Binary: qsstv
Architecture: source amd64
Version: 9.2.4+repack-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Hamradio Maintainers 
Changed-By: Dave Hibberd 
Description:
 qsstv  - Qt-based slow-scan TV and fax
Closes: 876811
Changes:
 qsstv (9.2.4+repack-2) unstable; urgency=medium
 .
   * Fix openjpeg 2.2 compatibility
 - Closes: #876811
   * Updated to Debian Standards 4.1.1.0
Checksums-Sha1:
 f0e246621223bd9b2f90eedb92ddf3e8bb5647f7 1811 qsstv_9.2.4+repack-2.dsc
 836f92088297791fabd69379409c7cb9f8dbe71b 6736 
qsstv_9.2.4+repack-2.debian.tar.xz
 617ee0e381fe1c4953821931c06ebc824484a454 23360458 
qsstv-dbgsym_9.2.4+repack-2_amd64.deb
 af343f1c5ea16d49d879537079ad0cfd3cfb64ed 11300 
qsstv_9.2.4+repack-2_amd64.buildinfo
 dde77af19c21004f66b8afd188cc40e30d87d3b9 788714 qsstv_9.2.4+repack-2_amd64.deb
Checksums-Sha256:
 835e6d2babe34f4e9615b810d092a1f421ad44cd1aafc828976a454de4b339ce 1811 
qsstv_9.2.4+repack-2.dsc
 a4b387792b856b8379fb8db427d8557775a78acac77c678da49248ea2289bc17 6736 
qsstv_9.2.4+repack-2.debian.tar.xz
 9409c21b73617385bb2bd75db655ea2294da630cbef11016be8f58bfe5a5aac8 23360458 
qsstv-dbgsym_9.2.4+repack-2_amd64.deb
 68c2f4939e60eb14b7620d3c3d2c8a577745d73b215408292865379a7989bc85 11300 
qsstv_9.2.4+repack-2_amd64.buildinfo
 c5430149b1f2689b0e4fadeb66a8552787170341a07f65ac53e5ada84cd06f2d 788714 
qsstv_9.2.4+repack-2_amd64.deb
Files:
 60df19b2935095b84d86cb8a96fc9943 1811 hamradio optional 
qsstv_9.2.4+repack-2.dsc
 8c353b6d11b9ec2f6dc01de29ce19462 6736 hamradio optional 
qsstv_9.2.4+repack-2.debian.tar.xz
 6d3b734f637ce3a78dc93127d79ed066 23360458 debug optional 
qsstv-dbgsym_9.2.4+repack-2_amd64.deb
 48ca521d3c949d1db13189e40284aeb2 11300 hamradio optional 
qsstv_9.2.4+repack-2_amd64.buildinfo
 201eb50789070fde2c98729cd4d1c03d 788714 hamradio optional 
qsstv_9.2.4+repack-2_amd64.deb

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEXk9UUZPolpyKWbgKA6H7ehkEdxsFAlnRUo8ACgkQA6H7ehkE
dxt9KggApCccJzSy07HCno2GhnEg864rkQkgubu4SRSn//FvBRM509mWJc5YTSPq
41QQL3TVxXfB6LiGB79GLAq71hv9KACnZLeQIkiZALYoUXjGp0wQlNfTx/pScl3U
crvgoxbqSS0AoNzpPxZjjdIe/lgJxEMTJejkOIARSUzyU2FqYHI2n2SIjNebO3fG
fU4WEqifr4EtZMGJDct795Zfn2X+hpOySmHUarrJfShuqIa/+GgJk1yCV3j21D07
EWea24BO7ZAorU5Rk6rrbJFTrJuMM0VakbCVCoqyecpHXOjIUkAbHCcCqjBg+WP4
7aXF4Ur9PpjdeBWBKv7XOAvr1AVm2w==
=AjNM
-END PGP SIGNATURE End Message ---

Bug#871155: marked as done (brltty: FTBFS: cc1: error: -Wformat-security ignored without -Wformat [-Werror=format-security])

[Debian Bug Tracking System]

Your message dated Sun, 01 Oct 2017 21:04:59 +
with message-id 
and subject line Bug#871155: fixed in brltty 5.5-2
has caused the Debian Bug report #871155,
regarding brltty: FTBFS: cc1: error: -Wformat-security ignored without -Wformat 
[-Werror=format-security]
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.)


-- 
871155: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871155
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: brltty
Version: 5.4-7
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170805 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> gcc -shared -Wl,-soname,libbrlapi.so.0.6 -o libbrlapi.so brlapi_client.o 
> -lpthread -lsupc++ 
> ar rc libbrlapi.a brlapi_client.o
> /usr/bin/ranlib libbrlapi.a
> make[2]: Leaving directory '/<>/build-py2.7/Programs'
> set -- --quiet build --build-temp .; \
> [ "linux-gnu" != "mingw32" ] || set -- "${@}" --compiler mingw32; \
> /usr/bin/python2.7 ./setup.py "${@}"
> cc1: error: -Wformat-security ignored without -Wformat 
> [-Werror=format-security]
> cc1: some warnings being treated as errors
> error: command 'x86_64-linux-gnu-gcc' failed with exit status 1
> Makefile:72: recipe for target 'brlapi.so' failed
> make[1]: *** [brlapi.so] Error 1

The full build log is available from:
   http://aws-logs.debian.net/2017/08/05/brltty_5.4-7_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: brltty
Source-Version: 5.5-2

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

Debian distribution maintenance software
pp.
Samuel Thibault  (supplier of updated brltty 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, 01 Oct 2017 22:09:51 +0200
Source: brltty
Binary: brltty libbrlapi0.6 libbrlapi-dev libbrlapi-jni libbrlapi-java 
brltty-flite brltty-speechd brltty-espeak brltty-udeb brltty-x11 xbrlapi 
cl-brlapi python-brlapi python3-brlapi
Architecture: source
Version: 5.5-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Accessibility Team 
Changed-By: Samuel Thibault 
Description:
 brltty - Access software for a blind person using a braille display
 brltty-espeak - Access software for a blind person - espeak driver
 brltty-flite - Access software for a blind person - Flite speech driver
 brltty-speechd - Access software for a blind person - Speech Dispatcher driver
 brltty-udeb - Access software for a blind person using a braille display (udeb)
 brltty-x11 - Access software for a blind person using a braille display - X11
 cl-brlapi  - Common Lisp bindings for BrlAPI
 libbrlapi-dev - Library for communication with BRLTTY - static libs and headers
 libbrlapi-java - Java bindings for BrlAPI
 libbrlapi-jni - Java bindings for BrlAPI (native library)
 libbrlapi0.6 - braille display access via BRLTTY - shared library
 python-brlapi - Braille display access via BRLTTY - Python bindings
 python3-brlapi - Braille display access via BRLTTY - Python3 bindings
 xbrlapi- Access software for a blind person using a braille display - xbrl
Closes: 864670 869972 871155
Changes:
 brltty (5.5-2) unstable; urgency=medium
 .
   * Upload to unstable (Closes: #871155)
   * patches/git-07ecca2240c680373e9c2e5e38241edde9d1a677: Apply upstream patch
 to fix finnish table (Closes: Bug#864670).
   * control: Update maintainer mailing list.
   * libbrlapi-dev.install: Also install device-specific brldefs headers
 (Closes: Bug#869972).
   * 

Processed: retitle 869034 to too strict version dependency on nokogiri declared in gemspecs

[Debian Bug Tracking System]

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

> retitle 869034 too strict version dependency on nokogiri declared in gemspecs
Bug #869034 {Done: Cédric Boutillier } 
[ruby-rails-dom-testing] ruby-combustion: FTBFS: ERROR: Test "ruby2.3" failed.
Bug #869037 {Done: Cédric Boutillier } 
[ruby-rails-dom-testing] ruby-haml-rails: FTBFS: ERROR: Test "ruby2.3" failed.
Bug #869060 {Done: Cédric Boutillier } 
[ruby-rails-dom-testing] ruby-web-console: FTBFS: ERROR: Test "ruby2.3" failed.
Changed Bug title to 'too strict version dependency on nokogiri declared in 
gemspecs' from 'ruby-combustion: FTBFS: ERROR: Test "ruby2.3" failed.'.
Changed Bug title to 'too strict version dependency on nokogiri declared in 
gemspecs' from 'ruby-haml-rails: FTBFS: ERROR: Test "ruby2.3" failed.'.
Changed Bug title to 'too strict version dependency on nokogiri declared in 
gemspecs' from 'ruby-web-console: FTBFS: ERROR: Test "ruby2.3" failed.'.
> thanks
Stopping processing here.

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

Processed: forcibly merging 869034 869037

[Debian Bug Tracking System]

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

> forcemerge 869034 869037
Bug #869034 {Done: Cédric Boutillier } 
[ruby-rails-dom-testing] ruby-combustion: FTBFS: ERROR: Test "ruby2.3" failed.
Bug #869037 [ruby-rails-dom-testing] ruby-haml-rails: FTBFS: ERROR: Test 
"ruby2.3" failed.
Marked Bug as done
Marked as fixed in versions ruby-rails-dom-testing/1.0.6-2.
Marked as found in versions ruby-rails-dom-testing/1.0.6-1.
Merged 869034 869037
> thanks
Stopping processing here.

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

Processed: forcibly merging 869034 869060

[Debian Bug Tracking System]

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

> forcemerge 869034 869060
Bug #869034 {Done: Cédric Boutillier } 
[ruby-rails-dom-testing] ruby-combustion: FTBFS: ERROR: Test "ruby2.3" failed.
Bug #869037 {Done: Cédric Boutillier } 
[ruby-rails-dom-testing] ruby-haml-rails: FTBFS: ERROR: Test "ruby2.3" failed.
Bug #869060 [ruby-rails-dom-testing] ruby-web-console: FTBFS: ERROR: Test 
"ruby2.3" failed.
Marked Bug as done
Marked as fixed in versions ruby-rails-dom-testing/1.0.6-2.
Marked as found in versions ruby-rails-dom-testing/1.0.6-1.
Bug #869037 {Done: Cédric Boutillier } 
[ruby-rails-dom-testing] ruby-haml-rails: FTBFS: ERROR: Test "ruby2.3" failed.
Merged 869034 869037 869060
> thanks
Stopping processing here.

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

Processed: reassign 869037 to ruby-rails-dom-testing

[Debian Bug Tracking System]

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

> reassign 869037 ruby-rails-dom-testing
Bug #869037 [src:ruby-haml-rails] ruby-haml-rails: FTBFS: ERROR: Test "ruby2.3" 
failed.
Bug reassigned from package 'src:ruby-haml-rails' to 'ruby-rails-dom-testing'.
No longer marked as found in versions ruby-haml-rails/0.9.0-4.
Ignoring request to alter fixed versions of bug #869037 to the same values 
previously set
> thanks
Stopping processing here.

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

Processed: reassign 869060 to ruby-rails-dom-testing

[Debian Bug Tracking System]

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

> reassign 869060 ruby-rails-dom-testing
Bug #869060 [src:ruby-web-console] ruby-web-console: FTBFS: ERROR: Test 
"ruby2.3" failed.
Bug reassigned from package 'src:ruby-web-console' to 'ruby-rails-dom-testing'.
No longer marked as found in versions ruby-web-console/2.2.1-2.
Ignoring request to alter fixed versions of bug #869060 to the same values 
previously set
> thanks
Stopping processing here.

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

Processed: gcc-8: missing Breaks+Replaces against several gcc-7 packages

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + lib32stdc++6-8-dbg libgccjit-8-doc libstdc++-8-doc 
> libstdc++6-8-dbg libx32stdc++6-8-dbg
Bug #877441 [src:gcc-8] gcc-8: missing Breaks+Replaces against several gcc-7 
packages
Added indication that 877441 affects lib32stdc++6-8-dbg, libgccjit-8-doc, 
libstdc++-8-doc, libstdc++6-8-dbg, and libx32stdc++6-8-dbg

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

Bug#877441: gcc-8: missing Breaks+Replaces against several gcc-7 packages

[Andreas Beckmann]

Source: gcc-8
Version: 8-20170923-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + lib32stdc++6-8-dbg libgccjit-8-doc libstdc++-8-doc 
libstdc++6-8-dbg libx32stdc++6-8-dbg

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

Not attaching the logs, just listing the packages with their conflicting
files:

lib32stdc++6-7-dbg=7.2.0-7 lib32stdc++6-8-dbg=8-20170923-1
usr/lib32/debug/libstdc++.a
usr/lib32/debug/libstdc++.so
usr/lib32/debug/libstdc++.so.6
usr/lib32/debug/libstdc++fs.a

libgccjit-7-doc=7.2.0-7 libgccjit-8-doc=8-20170923-1
usr/share/info/libgccjit.info.gz

libstdc++-7-doc=7.2.0-7 libstdc++-8-doc=8-20170923-1
usr/share/man/man3/*.3cxx.gz

libstdc++6-7-dbg=7.2.0-7 libstdc++6-8-dbg=8-20170923-1
usr/lib/x86_64-linux-gnu/debug/libstdc++.a
usr/lib/x86_64-linux-gnu/debug/libstdc++.so
usr/lib/x86_64-linux-gnu/debug/libstdc++.so.6
usr/lib/x86_64-linux-gnu/debug/libstdc++fs.a

libx32stdc++6-7-dbg=7.2.0-7 libx32stdc++6-8-dbg=8-20170923-1
usr/libx32/debug/libstdc++.a
usr/libx32/debug/libstdc++.so
usr/libx32/debug/libstdc++.so.6
usr/libx32/debug/libstdc++fs.a


cheers,

Andreas

Processed: bug 877411 is forwarded to https://github.com/flycheck/flycheck/issues/1341

[Debian Bug Tracking System]

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

> forwarded 877411 https://github.com/flycheck/flycheck/issues/1341
Bug #877411 [src:flycheck] flycheck FTBFS and Debci failure with elpa-buttercup 
1.9
Set Bug forwarded-to-address to 
'https://github.com/flycheck/flycheck/issues/1341'.
> thanks
Stopping processing here.

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

Bug#877253: marked as done (python-oslo.config: FTBFS tests fail: ImportError: No module named oslotest)

[Debian Bug Tracking System]

Your message dated Sun, 01 Oct 2017 19:35:37 +
with message-id 
and subject line Bug#877253: fixed in python-oslo.config 1:4.11.0-2
has caused the Debian Bug report #877253,
regarding python-oslo.config: FTBFS  tests fail: ImportError: No module named 
oslotest
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.)


-- 
877253: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877253
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-oslo.config
Version: 1:4.11.0-1
Severity: serious
Justification: fails to build from source

Hi,

python-oslo.config/experimental FTBFS in a current sid+experimental
environment:

   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/python-oslo.config-4.11.0'
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions
pkgos-dh_auto_test 
'oslo_config\.tests\.(?!.*test_generator\.IgnoreDoublesTestCase\.test_list_ignores_doubles.*)'
+ pyversions -vr
+ PYTHONS=2.7
+ py3versions -vr
+ PYTHON3S=3.6 3.5
+ cut -d. -f1
+ echo 2.7
+ PYMAJOR=2
+ echo ===> Testing with python (python2)
===> Testing with python (python2)
+ rm -rf .testrepository
+ testr-python2 init
+ mktemp -t
+ TEMP_REZ=/tmp/tmp.k9nsT4s2dI
+ subunit2pyunit
+ tee /tmp/tmp.k9nsT4s2dI
+ pwd
+ PYTHONPATH=/build/python-oslo.config-4.11.0 PYTHON=python2.7 testr-python2 
run --subunit 
oslo_config\.tests\.(?!.*test_generator\.IgnoreDoublesTestCase\.test_list_ignores_doubles.*)
running=OS_STDOUT_CAPTURE=1 OS_STDERR_CAPTURE=1 OS_TEST_TIMEOUT=60 
${PYTHON:-python} -m subunit.run discover -t ./ ./oslo_config --list 
-Non-zero exit code (2) from test listing.
-- import errors ---
Failed to import test module: oslo_config.tests.test_cfg
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 456, in 
_find_test_path
module = self._get_module_from_name(name)
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 395, in 
_get_module_from_name
__import__(name)
  File "oslo_config/tests/test_cfg.py", line 26, in 
from oslotest import base
ImportError: No module named oslotest

Failed to import test module: oslo_config.tests.test_cfgfilter
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 456, in 
_find_test_path
module = self._get_module_from_name(name)
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 395, in 
_get_module_from_name
__import__(name)
  File "oslo_config/tests/test_cfgfilter.py", line 15, in 
from oslotest import base as test_base
ImportError: No module named oslotest

Failed to import test module: oslo_config.tests.test_fixture
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 456, in 
_find_test_path
module = self._get_module_from_name(name)
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 395, in 
_get_module_from_name
__import__(name)
  File "oslo_config/tests/test_fixture.py", line 18, in 
from oslotest import base
ImportError: No module named oslotest

Failed to import test module: oslo_config.tests.test_generator
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 456, in 
_find_test_path
module = self._get_module_from_name(name)
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 395, in 
_get_module_from_name
__import__(name)
  File "oslo_config/tests/test_generator.py", line 19, in 
from oslotest import base
ImportError: No module named oslotest

Failed to import test module: oslo_config.tests.test_sphinxconfiggen
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 456, in 
_find_test_path
module = self._get_module_from_name(name)
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 395, in 
_get_module_from_name
__import__(name)
  File "oslo_config/tests/test_sphinxconfiggen.py", line 15, in 
from oslotest import base
ImportError: No module named oslotest

Failed to import test module: oslo_config.tests.test_sphinxext
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 456, in 
_find_test_path
module = self._get_module_from_name(name)
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 395, 

Bug#877253: marked as pending

[Thomas Goirand]

tag 877253 pending
thanks

Hello,

Bug #877253 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:


https://anonscm.debian.org/cgit/openstack/oslo/python-oslo.config.git/commit/?id=05b1854

---
commit 05b1854e0d50fc9c46c0927f6818d249cc388f73
Author: Thomas Goirand 
Date:   Sun Oct 1 19:06:17 2017 +

Add missing build-depends: python{3,}-oslotest (Closes: #877253).

diff --git a/debian/changelog b/debian/changelog
index b0cdb89..389f2e8 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+python-oslo.config (1:4.11.0-2) experimental; urgency=medium
+
+  * Add missing build-depends: python{3,}-oslotest (Closes: #877253).
+
+ -- Thomas Goirand   Sun, 01 Oct 2017 19:04:46 +
+
 python-oslo.config (1:4.11.0-1) experimental; urgency=medium
 
   [ Ondřej Nový ]

Bug#872237: marked as done (liblldb-4.0-dev: broken symlink: /usr/lib/llvm-4.0/lib/liblldb-4.0.so -> liblldb-4.0.so.1)

[Debian Bug Tracking System]

Your message dated Sun, 01 Oct 2017 19:21:31 +
with message-id 
and subject line Bug#872237: fixed in llvm-toolchain-4.0 1:4.0.1-6
has caused the Debian Bug report #872237,
regarding liblldb-4.0-dev: broken symlink: /usr/lib/llvm-4.0/lib/liblldb-4.0.so 
-> liblldb-4.0.so.1
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.)


-- 
872237: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872237
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: liblldb-4.0-dev
Version: 1:4.0.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + python-lldb-4.0 lldb-4.0

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

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

0m36.6s ERROR: FAIL: Broken symlinks:
  /usr/lib/llvm-4.0/lib/liblldb-4.0.so -> liblldb-4.0.so.1
  /usr/lib/llvm-4.0/lib/liblldb-4.0.1.so -> liblldb-4.0.so

But there is /usr/lib/x86_64-linux-gnu/liblldb-4.0.so.1 in liblldb-4.0.


cheers,

Andreas


lldb-4.0_1:4.0.1-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: llvm-toolchain-4.0
Source-Version: 1:4.0.1-6

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

Debian distribution maintenance software
pp.
Sylvestre Ledru  (supplier of updated llvm-toolchain-4.0 
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, 01 Oct 2017 15:24:14 +0200
Source: llvm-toolchain-4.0
Binary: clang-4.0 clang-format-4.0 clang-tidy-4.0 clang-4.0-doc libclang1-4.0 
libclang1-4.0-dbg libclang-4.0-dev libclang-common-4.0-dev libfuzzer-4.0-dev 
python-clang-4.0 clang-4.0-examples libllvm4.0 libllvm4.0-dbg llvm-4.0 
llvm-4.0-runtime llvm-4.0-dev llvm-4.0-tools libllvm-4.0-ocaml-dev llvm-4.0-doc 
llvm-4.0-examples lld-4.0 liblld-4.0 liblld-4.0-dbg liblld-4.0-dev lldb-4.0 
liblldb-4.0 liblldb-4.0-dbg python-lldb-4.0 liblldb-4.0-dev
Architecture: source amd64 all
Version: 1:4.0.1-6
Distribution: unstable
Urgency: medium
Maintainer: LLVM Packaging Team 
Changed-By: Sylvestre Ledru 
Description:
 clang-4.0  - C, C++ and Objective-C compiler (LLVM based)
 clang-4.0-doc - C, C++ and Objective-C compiler (LLVM based) - Documentation
 clang-4.0-examples - Clang examples
 clang-format-4.0 - Tool to format C/C++/Obj-C code
 clang-tidy-4.0 - clang-based C++ linter tool
 libclang-4.0-dev - clang library - Development package
 libclang-common-4.0-dev - clang library - Common development package
 libclang1-4.0 - C interface to the clang library
 libclang1-4.0-dbg - clang library
 libfuzzer-4.0-dev - Library for coverage-guided fuzz testing
 liblld-4.0 - LLVM-based linker, library
 liblld-4.0-dbg - LLVM-based linker, debugging libraries
 liblld-4.0-dev - LLVM-based linker, header files
 liblldb-4.0 - Next generation, high-performance debugger, library
 liblldb-4.0-dbg - Next generation, high-performance debugger, debugging 
libraries
 liblldb-4.0-dev - Next generation, high-performance debugger, header files
 libllvm-4.0-ocaml-dev - Modular compiler and toolchain technologies, OCaml 
bindings
 libllvm4.0 - Modular compiler and toolchain technologies, runtime library
 libllvm4.0-dbg - Modular compiler and toolchain technologies, debugging 
libraries
 lld-4.0- LLVM-based linker
 lldb-4.0   - Next generation, high-performance debugger
 llvm-4.0   - Modular compiler and toolchain technologies
 llvm-4.0-dev - Modular compiler and toolchain technologies, libraries and 
header
 llvm-4.0-doc - Modular compiler and toolchain technologies, documentation
 llvm-4.0-examples - Modular compiler and toolchain technologies, examples
 llvm-4.0-runtime - Modular compiler and toolchain technologies, IR interpreter
 llvm-4.0-tools - Modular compiler and toolchain technologies, tools
 python-clang-4.0 - Clang Python Bindings
 python-lldb-4.0 - Next generation, high-performance debugger, python lib
Closes: 857653 

Bug#857653: marked as done (liblld-4.0: missing liblld-4.0.so.1)

[Debian Bug Tracking System]

Your message dated Sun, 01 Oct 2017 19:21:31 +
with message-id 
and subject line Bug#857653: fixed in llvm-toolchain-4.0 1:4.0.1-6
has caused the Debian Bug report #857653,
regarding liblld-4.0: missing liblld-4.0.so.1
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.)


-- 
857653: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857653
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: liblld-4.0
Version: missing liblld-4.0.so.1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

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

0m24.5s ERROR: FAIL: Broken symlinks:
  /usr/lib/llvm-4.0/lib/liblld.so.1 -> ../../x86_64-linux-gnu/liblld-4.0.so.1
  /usr/lib/x86_64-linux-gnu/liblld-4.0.so -> liblld-4.0.so.1
  /usr/lib/python2.7/dist-packages/lld-4.0/_lld.so -> 
../../../x86_64-linux-gnu/liblld-4.0.so

liblld-4.0.so.1 does not seem to exist anywhere, I could only find
  /usr/lib/llvm-4.0/lib/liblld.so.1

liblld-5.0 has the same problems.


cheers,

Andreas


liblld-4.0_1:4.0-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: llvm-toolchain-4.0
Source-Version: 1:4.0.1-6

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

Debian distribution maintenance software
pp.
Sylvestre Ledru  (supplier of updated llvm-toolchain-4.0 
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, 01 Oct 2017 15:24:14 +0200
Source: llvm-toolchain-4.0
Binary: clang-4.0 clang-format-4.0 clang-tidy-4.0 clang-4.0-doc libclang1-4.0 
libclang1-4.0-dbg libclang-4.0-dev libclang-common-4.0-dev libfuzzer-4.0-dev 
python-clang-4.0 clang-4.0-examples libllvm4.0 libllvm4.0-dbg llvm-4.0 
llvm-4.0-runtime llvm-4.0-dev llvm-4.0-tools libllvm-4.0-ocaml-dev llvm-4.0-doc 
llvm-4.0-examples lld-4.0 liblld-4.0 liblld-4.0-dbg liblld-4.0-dev lldb-4.0 
liblldb-4.0 liblldb-4.0-dbg python-lldb-4.0 liblldb-4.0-dev
Architecture: source amd64 all
Version: 1:4.0.1-6
Distribution: unstable
Urgency: medium
Maintainer: LLVM Packaging Team 
Changed-By: Sylvestre Ledru 
Description:
 clang-4.0  - C, C++ and Objective-C compiler (LLVM based)
 clang-4.0-doc - C, C++ and Objective-C compiler (LLVM based) - Documentation
 clang-4.0-examples - Clang examples
 clang-format-4.0 - Tool to format C/C++/Obj-C code
 clang-tidy-4.0 - clang-based C++ linter tool
 libclang-4.0-dev - clang library - Development package
 libclang-common-4.0-dev - clang library - Common development package
 libclang1-4.0 - C interface to the clang library
 libclang1-4.0-dbg - clang library
 libfuzzer-4.0-dev - Library for coverage-guided fuzz testing
 liblld-4.0 - LLVM-based linker, library
 liblld-4.0-dbg - LLVM-based linker, debugging libraries
 liblld-4.0-dev - LLVM-based linker, header files
 liblldb-4.0 - Next generation, high-performance debugger, library
 liblldb-4.0-dbg - Next generation, high-performance debugger, debugging 
libraries
 liblldb-4.0-dev - Next generation, high-performance debugger, header files
 libllvm-4.0-ocaml-dev - Modular compiler and toolchain technologies, OCaml 
bindings
 libllvm4.0 - Modular compiler and toolchain technologies, runtime library
 libllvm4.0-dbg - Modular compiler and toolchain technologies, debugging 
libraries
 lld-4.0- LLVM-based linker
 lldb-4.0   - Next generation, high-performance debugger
 llvm-4.0   - Modular compiler and toolchain technologies
 llvm-4.0-dev - Modular compiler and toolchain technologies, libraries and 
header
 llvm-4.0-doc - Modular compiler and toolchain technologies, documentation
 llvm-4.0-examples - Modular compiler and toolchain technologies, examples
 llvm-4.0-runtime - Modular compiler and toolchain technologies, IR interpreter
 llvm-4.0-tools - Modular compiler and toolchain technologies, tools
 python-clang-4.0 - Clang Python Bindings
 

Bug#877254: marked as done (python-oslo.vmware: FTBFS: tests fail: ImportError: No module named lxml)

[Debian Bug Tracking System]

Your message dated Sun, 01 Oct 2017 19:21:58 +
with message-id 
and subject line Bug#877254: fixed in python-oslo.vmware 2.23.0-2
has caused the Debian Bug report #877254,
regarding python-oslo.vmware: FTBFS: tests fail: ImportError: No module named 
lxml
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.)


-- 
877254: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877254
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-oslo.vmware
Version: 2.23.0-1
Severity: serious
Justification: fails to build from source

Hi,

python-oslo.vmware/experimental FTBFS in a current sid+experimental
environment:

   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/python-oslo.vmware-2.23.0'
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions
===> Running tests
set -e ; set -x ; for i in 2.7 3.6 3.5 ; do \
PYMAJOR=`echo $i | cut -d'.' -f1` ; \
echo "===> Testing with python$i (python$PYMAJOR)" ; \
rm -rf .testrepository ; \
testr-python$PYMAJOR init ; \
TEMP_REZ=`mktemp -t` ; \
PYTHONPATH=/build/python-oslo.vmware-2.23.0 PYTHON=python$i 
testr-python$PYMAJOR run --subunit 
'oslo_vmware\.tests\.(?!.*test_service\.MemoryCacheTest\.test_shared_cache.*)' 
| tee $TEMP_REZ | subunit2pyuni
t ; \
cat $TEMP_REZ | subunit-filter -s --no-passthrough | subunit-stats ; \
rm -f $TEMP_REZ ; \
testr-python$PYMAJOR slowest ; \
done
+ echo 2.7
+ cut -d. -f1
+ PYMAJOR=2
+ echo ===> Testing with python2.7 (python2)
===> Testing with python2.7 (python2)
+ rm -rf .testrepository
+ testr-python2 init
+ mktemp -t
+ TEMP_REZ=/tmp/tmp.qV0v7hpqwZ
+ PYTHONPATH=/build/python-oslo.vmware-2.23.0 PYTHON=python2.7 testr-python2 
run --subunit 
oslo_vmware\.tests\.(?!.*test_service\.MemoryCacheTest\.test_shared_cache.*)
+ tee /tmp/tmp.qV0v7hpqwZ
+ subunit2pyunit
running=OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \
OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-60} \
${PYTHON:-python} -m subunit.run discover -t ./ . --list 
--- import errNon-zero exit code (2) from test listing.
ors ---
Failed to import test module: oslo_vmware.tests.test_image_transfer
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 456, in 
_find_test_path
module = self._get_module_from_name(name)
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 395, in 
_get_module_from_name
__import__(name)
  File "oslo_vmware/tests/test_image_transfer.py", line 24, in 
from oslo_vmware import image_transfer
  File "oslo_vmware/image_transfer.py", line 31, in 
from oslo_vmware import image_util
  File "oslo_vmware/image_util.py", line 16, in 
from lxml import etree  # nosec (bandit bug 1582516)
ImportError: No module named lxml

Failed to import test module: oslo_vmware.tests.test_image_util
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 456, in 
_find_test_path
module = self._get_module_from_name(name)
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 395, in 
_get_module_from_name
__import__(name)
  File "oslo_vmware/tests/test_image_util.py", line 22, in 
from oslo_vmware import image_util
  File "oslo_vmware/image_util.py", line 16, in 
from lxml import etree  # nosec (bandit bug 1582516)
ImportError: No module named lxml

--
Ran 0 tests in 0.704s

OK
+ cat /tmp/tmp.qV0v7hpqwZ
+ subunit-filter -s --no-passthrough
+ subunit-stats
Total tests:   0
Passed tests:  0
Failed tests:  0
Skipped tests: 0
Seen tags: 
+ rm -f /tmp/tmp.qV0v7hpqwZ
+ testr-python2 slowest
debian/rules:20: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 3
make[1]: Leaving directory '/build/python-oslo.vmware-2.23.0'


Andreas


python-oslo.vmware_2.23.0-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: python-oslo.vmware
Source-Version: 2.23.0-2

We believe that the bug you reported is fixed in the latest version of
python-oslo.vmware, 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 

Processed: Bug#877253 marked as pending

[Debian Bug Tracking System]

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

> tag 877253 pending
Bug #877253 [src:python-oslo.config] python-oslo.config: FTBFS  tests fail: 
ImportError: No module named oslotest
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#877129: marked as done (python-cliff: FTBFS: test fail: ModuleNotFoundError: No module named 'docutils')

[Debian Bug Tracking System]

Your message dated Sun, 01 Oct 2017 19:21:49 +
with message-id 
and subject line Bug#877129: fixed in python-cliff 2.8.0-2
has caused the Debian Bug report #877129,
regarding python-cliff: FTBFS: test fail: ModuleNotFoundError: No module named 
'docutils'
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.)


-- 
877129: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877129
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-cliff
Version: 2.8.0-1
Severity: serious
Justification: fails to build from source

Hi,

python-cliff/experimental FTBFS with

[...]
cliff.tests.test_show.TestShow.test_formatter_args
cliff.tests.test_show.TestShow.test_formatter_args ... ok
cliff.tests.test_show.TestShow.test_no_exist_column
cliff.tests.test_show.TestShow.test_no_exist_column ... ok
unittest2.loader._FailedTest.cliff.tests.test_sphinxext
unittest2.loader._FailedTest.cliff.tests.test_sphinxext ... FAIL
cliff.tests.test_utils.TestTerminalWidth.test
cliff.tests.test_utils.TestTerminalWidth.test ... ok
cliff.tests.test_utils.TestTerminalWidth.test_get_terminal_size
cliff.tests.test_utils.TestTerminalWidth.test_get_terminal_size ... ok
cliff.tests.test_utils.TestTerminalWidth.test_ioctl
cliff.tests.test_utils.TestTerminalWidth.test_ioctl ... skipped u'only needed 
for python 3.2 and before'
cliff.tests.test_utils.TestTerminalWidth.test_windows
cliff.tests.test_utils.TestTerminalWidth.test_windows ... skipped u'only needed 
for python 3.2 and before'
running=OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \
OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-60} \
${PYTHON:-python} -m subunit.run discover -t ./ ./cliff  

==
FAIL: unittest2.loader._FailedTest.cliff.tests.test_sphinxext
unittest2.loader._FailedTest.cliff.tests.test_sphinxext
--
_StringException: Traceback (most recent call last):
ImportError: Failed to import test module: cliff.tests.test_sphinxext
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/unittest2/loader.py", line 456, in 
_find_test_path
module = self._get_module_from_name(name)
  File "/usr/lib/python3/dist-packages/unittest2/loader.py", line 395, in 
_get_module_from_name
__import__(name)
  File "/build/python-cliff-2.8.0/cliff/tests/test_sphinxext.py", line 18, in 

from cliff import sphinxext
  File "/build/python-cliff-2.8.0/cliff/sphinxext.py", line 19, in 
from docutils import nodes
ModuleNotFoundError: No module named 'docutils'


--
Ran 152 tests in 1.107s

FAILED (failures=1, skipped=2)
debian/rules:35: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1


Full log attached.


Andreas


python-cliff_2.8.0-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: python-cliff
Source-Version: 2.8.0-2

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated python-cliff 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, 01 Oct 2017 18:57:32 +
Source: python-cliff
Binary: python-cliff python-cliff-doc python3-cliff
Architecture: source all
Version: 2.8.0-2
Distribution: experimental
Urgency: medium
Maintainer: Debian OpenStack 
Changed-By: Thomas Goirand 
Description:
 python-cliff - command line interface formulation framework - Python 2.x
 python-cliff-doc - command line interface formulation framework documentation
 python3-cliff - command line interface formulation framework - Python 3.x
Closes: 877129
Changes:
 python-cliff (2.8.0-2) experimental; urgency=medium
 .
   * Add missing (build-)dep: python{3,}-docutils (Closes: #877129).
Checksums-Sha1:
 

Bug#876787: marked as done (afl: FTBFS /usr/bin/ld: unrecognized option '--no-keep-files-mapped')

[Debian Bug Tracking System]

Your message dated Sun, 01 Oct 2017 19:21:31 +
with message-id 
and subject line Bug#876787: fixed in llvm-toolchain-4.0 1:4.0.1-6
has caused the Debian Bug report #876787,
regarding afl: FTBFS /usr/bin/ld: unrecognized option '--no-keep-files-mapped'
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.)


-- 
876787: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876787
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:afl
Version: 2.50b-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Control: block 873404 by -1

AFL begun to FTBFS recently with a clang error:


[+] All set and ready to build.
clang-3.9  -Wall -D_FORTIFY_SOURCE=2 -g -Wno-pointer-sign 
-DAFL_PATH=\"/usr/lib/afl\" -DBIN_PATH=\"/usr/bin\" -DVERSION=\"2.50b\"  
afl-clang-fast.c -o ../afl-clang-fast -Wl,-z,relro -Wl,-z,now
ln -sf afl-clang-fast ../afl-clang-fast++
clang++-3.9 `llvm-config-3.9 --cxxflags` -fno-rtti -fpic  -Wall 
-D_FORTIFY_SOURCE=2 -g -Wno-pointer-sign -DVERSION=\"2.50b\" 
-Wno-variadic-macros -shared afl-llvm-pass.so.cc -o ../afl-llvm-pass.so 
`llvm-config-3.9 --ldflags` -Wl,-z,relro -Wl,-z,now
warning: unknown warning option '-Wno-maybe-uninitialized'; did you mean 
'-Wno-uninitialized'? [-Wunknown-warning-option]
1 warning generated.
/usr/bin/ld: unrecognized option '--no-keep-files-mapped'
/usr/bin/ld: use the --help option for usage information
clang: error: linker command failed with exit code 1 (use -v to see invocation)
Makefile:83: recipe for target '../afl-llvm-pass.so' failed


This seems to be a problem in the build toolchain (this is going to be
reassigned). The same error appears also with clang-4.0 and clang-5.0, thus
blocking the llvm-toolchain update of AFL.

DS

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

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

Versions of packages afl depends on:
ii  build-essential  12.4
ii  libc62.24-17

Versions of packages afl recommends:
ii  afl-clang  2.50b-1
ii  afl-doc2.50b-1

Versions of packages afl suggests:
ii  gnuplot   5.0.7+dfsg1-1
ii  gnuplot-qt [gnuplot]  5.0.7+dfsg1-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: llvm-toolchain-4.0
Source-Version: 1:4.0.1-6

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

Debian distribution maintenance software
pp.
Sylvestre Ledru  (supplier of updated llvm-toolchain-4.0 
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, 01 Oct 2017 15:24:14 +0200
Source: llvm-toolchain-4.0
Binary: clang-4.0 clang-format-4.0 clang-tidy-4.0 clang-4.0-doc libclang1-4.0 
libclang1-4.0-dbg libclang-4.0-dev libclang-common-4.0-dev libfuzzer-4.0-dev 
python-clang-4.0 clang-4.0-examples libllvm4.0 libllvm4.0-dbg llvm-4.0 
llvm-4.0-runtime llvm-4.0-dev llvm-4.0-tools libllvm-4.0-ocaml-dev llvm-4.0-doc 
llvm-4.0-examples lld-4.0 liblld-4.0 liblld-4.0-dbg liblld-4.0-dev lldb-4.0 
liblldb-4.0 liblldb-4.0-dbg python-lldb-4.0 liblldb-4.0-dev
Architecture: source amd64 all
Version: 1:4.0.1-6
Distribution: unstable
Urgency: medium
Maintainer: LLVM Packaging Team 
Changed-By: Sylvestre Ledru 
Description:
 clang-4.0  - C, C++ and Objective-C compiler (LLVM based)
 clang-4.0-doc - C, C++ and Objective-C compiler (LLVM based) - Documentation
 clang-4.0-examples - Clang examples
 clang-format-4.0 - Tool to format C/C++/Obj-C code
 clang-tidy-4.0 - clang-based C++ linter tool
 libclang-4.0-dev - clang library - Development package
 libclang-common-4.0-dev - clang library - Common development package
 libclang1-4.0 - C interface to the clang 

Bug#877180: [Pkg-e-devel] Bug#877180: libector-dev: missing Depends: libector1 (= ${binary:Version})

[Ross Vandegrift]

On Sun, Oct 01, 2017 at 04:02:32PM +0200, Andreas Metzler wrote:
> Control: tags -1 patch
> 
> On 2017-09-29 Andreas Beckmann  wrote:
> > Package: libector-dev
> > Version: 1.18.4-1
> > Severity: serious
> > User: debian...@lists.debian.org
> > Usertags: piuparts
> > 
> > Hi,
> > 
> > during a test with piuparts I noticed your package ships (or creates)
> > a broken symlink.
> > 
> > From the attached log (scroll to the bottom...):
> > 
> > 1m1.9s ERROR: FAIL: Broken symlinks:
> >   /usr/lib/x86_64-linux-gnu/libector.so -> libector.so.1.18.4
> 
> Thank you, Andreas.
> 
> Ross, find attached patches two fix this issue and another similar one.

Thanks: both are applied in my tree for 1.20.4-2.

Ross

Processed: mpb doesn't build on the autobuilders on mipsel

[Debian Bug Tracking System]

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

> severity 846923 serious
Bug #846923 [src:mpb] mpb: FTBFS on mipsel - hanging on autconf test for BLAS 
zdotc
Severity set to 'serious' from 'normal'
> tags 846923 stretch buster sid
Bug #846923 [src:mpb] mpb: FTBFS on mipsel - hanging on autconf test for BLAS 
zdotc
Added tag(s) buster, stretch, and sid.
> thanks
Stopping processing here.

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

Processed: Bug#877254 marked as pending

[Debian Bug Tracking System]

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

> tag 877254 pending
Bug #877254 [src:python-oslo.vmware] python-oslo.vmware: FTBFS: tests fail: 
ImportError: No module named lxml
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#877254: marked as pending

[Thomas Goirand]

tag 877254 pending
thanks

Hello,

Bug #877254 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:


https://anonscm.debian.org/cgit/openstack/oslo/python-oslo.vmware.git/commit/?id=5241f6e

---
commit 5241f6e7bb2d3f63339d2e99d4a9d63414f218e5
Author: Thomas Goirand 
Date:   Sun Oct 1 19:02:50 2017 +

Add missing (build-)depends python{3,}-lxml (Closes: #877254).

diff --git a/debian/changelog b/debian/changelog
index 9951c63..dcd571b 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+python-oslo.vmware (2.23.0-2) experimental; urgency=medium
+
+  * Add missing (build-)depends python{3,}-lxml (Closes: #877254).
+
+ -- Thomas Goirand   Sun, 01 Oct 2017 19:01:25 +
+
 python-oslo.vmware (2.23.0-1) experimental; urgency=medium
 
   [ Ondřej Nový ]

Processed: found 877436 in 1.10.8-2

[Debian Bug Tracking System]

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

> found 877436 1.10.8-2
Bug #877436 [src:botan1.10] botan1.10: CVE-2017-14737: A cryptographic 
cache-based side channel in the RSA implementation allows local attacker to 
recover information about RSA secret keys
Marked as found in versions botan1.10/1.10.8-2.
> thanks
Stopping processing here.

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

Processed: tagging 877436

[Debian Bug Tracking System]

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

> tags 877436 + fixed-upstream
Bug #877436 [src:botan1.10] botan1.10: CVE-2017-14737: A cryptographic 
cache-based side channel in the RSA implementation allows local attacker to 
recover information about RSA secret keys
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Processed: retitle 877436 to botan1.10: CVE-2017-14737: A cryptographic cache-based side channel in the RSA implementation allows local attacker to recover information about RSA secret keys

[Debian Bug Tracking System]

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

> retitle 877436 botan1.10: CVE-2017-14737: A cryptographic cache-based side 
> channel in the RSA implementation allows local attacker to recover 
> information about RSA secret keys
Bug #877436 [src:botan1.10] botan1.10: CVE-2017-14737:A cryptographic 
cache-based side channel in the RSA implementation allows local attacker to 
recover information about RSA secret keys
Changed Bug title to 'botan1.10: CVE-2017-14737: A cryptographic cache-based 
side channel in the RSA implementation allows local attacker to recover 
information about RSA secret keys' from 'botan1.10: CVE-2017-14737:A 
cryptographic cache-based side channel in the RSA implementation allows local 
attacker to recover information about RSA secret keys'.
> thanks
Stopping processing here.

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

Processed: Bug#877129 marked as pending

[Debian Bug Tracking System]

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

> tag 877129 pending
Bug #877129 [src:python-cliff] python-cliff: FTBFS: test fail: 
ModuleNotFoundError: No module named 'docutils'
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#877129: marked as pending

[Thomas Goirand]

tag 877129 pending
thanks

Hello,

Bug #877129 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:


https://anonscm.debian.org/cgit/openstack/python/python-cliff.git/commit/?id=45f1b4d

---
commit 45f1b4de0c5ffe8d1f723d2abca0229cca2ad158
Author: Thomas Goirand 
Date:   Sun Oct 1 18:59:07 2017 +

Add missing (build-)dep: python{3,}-docutils (Closes: #877129).

diff --git a/debian/changelog b/debian/changelog
index 8362426..1a69f20 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+python-cliff (2.8.0-2) experimental; urgency=medium
+
+  * Add missing (build-)dep: python{3,}-docutils (Closes: #877129).
+
+ -- Thomas Goirand   Sun, 01 Oct 2017 18:57:32 +
+
 python-cliff (2.8.0-1) experimental; urgency=medium
 
   [ Ondřej Nový ]

Processed: notfound 877433 in 1.9-3-1, found 877433 in 1.0-4

[Debian Bug Tracking System]

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

> notfound 877433 1.9-3-1
Bug #877433 [r-cran-mi] missing dependency on r-cran-arm
There is no source info for the package 'r-cran-mi' at version '1.9-3-1' with 
architecture ''
Unable to make a source version for version '1.9-3-1'
No longer marked as found in versions 1.9-3-1.
> found 877433 1.0-4
Bug #877433 [r-cran-mi] missing dependency on r-cran-arm
Marked as found in versions r-cran-mi/1.0-4.
> thanks
Stopping processing here.

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

Bug#877436: botan1.10: CVE-2017-14737:A cryptographic cache-based side channel in the RSA implementation allows local attacker to recover information about RSA secret keys

[Salvatore Bonaccorso]

Source: botan1.10
Version: 1.10.16-1
Severity: grave
Tags: patch upstream security
Forwarded: https://github.com/randombit/botan/issues/1222

Hi,

the following vulnerability was published for botan1.10.

CVE-2017-14737[0]:
| A cryptographic cache-based side channel in the RSA implementation in
| Botan before 1.10.17, and 1.11.x and 2.x before 2.3.0, allows a local
| attacker to recover information about RSA secret keys, as demonstrated
| by CacheD. This occurs because an array is indexed with bits derived
| from a secret key.

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-14737
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-14737
[1] https://github.com/randombit/botan/issues/1222

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Processed: openvas-libraries: "pcap-config --libs" workaround no longer required

[Debian Bug Tracking System]

Processing control commands:

> close 876093
Bug #876093 [src:openvas-libraries] openvas-libraries FTBFS on amd64: 
override_dh_auto_configure failed
Marked Bug as done

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

Bug#877433: missing dependency on r-cran-arm

[Sébastien Villemot]

Package: r-cran-mi
Version: 1.9-3-1
Severity: serious

Loading the package with r-cran-arm uninstalled fails:

> library(mi)
Loading required package: Matrix
Loading required package: stats4
Error in loadNamespace(j <- i[[1L]], c(lib.loc, .libPaths()), versionCheck = 
vI[[j]]) :
  there is no package called 'arm'
Error: package or namespace load failed for 'mi'
>

Cheers,

-- 
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  http://sebastien.villemot.name
⠈⠳⣄  http://www.debian.org


signature.asc
Description: PGP signature

Processed: fixed 872258 in 1.37.1+dfsg2-1, closing 872258

[Debian Bug Tracking System]

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

> fixed 872258 1.37.1+dfsg2-1
Bug #872258 [slic3r-prusa] slic3r-prusa: Not working: Your vendor has not 
defined OpenGL macro GL_MULTISAMPLE...
Marked as fixed in versions slic3r-prusa/1.37.1+dfsg2-1.
> close 872258
Bug #872258 [slic3r-prusa] slic3r-prusa: Not working: Your vendor has not 
defined OpenGL macro GL_MULTISAMPLE...
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#518429: marked as done (libmpd-dev: should depend on libglib2.0-dev)

[Debian Bug Tracking System]

Your message dated Sun, 01 Oct 2017 18:19:28 +
with message-id 
and subject line Bug#518429: fixed in libmpd 0.20.0-2
has caused the Debian Bug report #518429,
regarding libmpd-dev: should depend on libglib2.0-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.)


-- 
518429: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=518429
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libmpd-dev
Version: 0.17.0-1
Severity: normal

/usr/lib/pkgconfig/libmpd.pc contains:

Requires: glib-2.0

Thus libmpd-dev should list libglib2.0-dev as dependency.

Regards,
Jakob


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

Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages libmpd-dev depends on:
ii  libmpd0   0.17.0-1   High-level client library for
acce ii  pkg-config0.22-1 manage compile and link
flags for 

libmpd-dev recommends no packages.

libmpd-dev suggests no packages.

-- no debconf information


-- 
ceterum censeo microsoftem esse delendam.


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: libmpd
Source-Version: 0.20.0-2

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated libmpd 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, 01 Oct 2017 20:27:24 +0300
Source: libmpd
Binary: libmpd1 libmpd1-dbg libmpd-dev
Architecture: source
Version: 0.20.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Adrian Bunk 
Description:
 libmpd-dev - High-level client library for accessing Music Player Daemon
 libmpd1- High-level client library for accessing Music Player Daemon
 libmpd1-dbg - High-level client library for accessing Music Player Daemon
Closes: 518429
Changes:
 libmpd (0.20.0-2) unstable; urgency=medium
 .
   * QA upload.
   * Set maintainer to Debian QA Group. (see #876951)
   * libmpd-dev: Add the missing dependency on libglib2.0-dev.
 (Closes: #518429)
Checksums-Sha1:
 45c6ca702a47bca9e043257a0c4c96865b165d4d 1816 libmpd_0.20.0-2.dsc
 eced17626dd75373e2daf3e94ffa0baaae956fd9 3814 libmpd_0.20.0-2.diff.gz
Checksums-Sha256:
 4b552018a429e85426198761cc6c280c9b9da6bf46a760126b4db22e5dc80943 1816 
libmpd_0.20.0-2.dsc
 9b3ecc272b7315e48a125d1a907848f9fe05817a215a65064673d08eb3be9051 3814 
libmpd_0.20.0-2.diff.gz
Files:
 fb577c4b860fde1c99cef501bfe833af 1816 libs optional libmpd_0.20.0-2.dsc
 ca28a4b01cf1493e89e5accc5fdd7674 3814 libs optional libmpd_0.20.0-2.diff.gz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAlnRK0sACgkQiNJCh6LY
mLEQkhAAyXFeey4DrFvgq8mFU2IVWN0rXUFmXQNslmpj0Iwii5BIvC6g7oaMwS2s
o1t5crP9uzEjE0Xkgn+NkeYWObe5+iq1A6aab7PAfuVQYoDWyfG+TBtVWZpIkaOG
KvQTFgvn+vz1Kl7AYnEa8JObQwDkoxshydkUmvqm8XaHzGvlVwZ0O51cCh8PLDv8
LQgovvR+Jg/Xiy9UnaUwV+RNi2/bR09XmtkvB89rstj1s1g4APNuEe3sUQShdTRi
59vEFgyIi8Z5xNA40Ca2gw+exImvM86RDDKicERGMXa9qH7WpHniMZhzS124Mvuv
C5VBrSnIZXsydBfsu3ZxRWElyNkvcMJnf4aG25HPaeQNPx8IdFlZQS6Li4lgWyp4
4PrpUQSNWhdka/xQoJkeV/p9cvDB637z2ugdYhndA2FF4E61zGRIYpLbNDR1ILaK
nC0E/xbWu565iIIekqgLoIbgkIEI39ZP0OPKIIiUWuEqicd2Ku7YgC/t/Iue7Q9D
yh16GhXsvv5gwWKSkWHwafrG1IEA8w7RzdjowDafpO61hdcrJPubjXjEaLRXss+L
nlS/t8UKhCdPTRntMBEK+KA22N01BRIMiKIl9LIWAysRi0dGhOwUW225TsmoM/cx
mfDQn6xwt+i2V6iz9UNbT6+g4jpFkituiDSsOv8LiDr9lm4OkpA=
=cedS
-END PGP SIGNATURE End Message ---

Processed: Re: Bug#873778: Fix for the mozjs52 build on armel

[Debian Bug Tracking System]

Processing control commands:

> clone -1 -2
Bug #873778 [src:mozjs52] mozjs52: FTBFS on big-endian: Exception: Failed to 
test XUL condition 'Android'; output was '', stderr was ''
Bug 873778 cloned as bug 877428
> retitle -2 FTBFS on mips64el: various test failures
Bug #877428 [src:mozjs52] mozjs52: FTBFS on big-endian: Exception: Failed to 
test XUL condition 'Android'; output was '', stderr was ''
Changed Bug title to 'FTBFS on mips64el: various test failures' from 'mozjs52: 
FTBFS on big-endian: Exception: Failed to test XUL condition 'Android'; output 
was '', stderr was '''.

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

Bug#873778: Fix for the mozjs52 build on armel

[Simon McVittie]

Control: clone -1 -2
Control: retitle -2 FTBFS on mips64el: various test failures

On Sat, 23 Sep 2017 at 12:29:08 +0200, Emilio Pozuelo Monfort wrote:
> Let's track the mips64el failure in a different bug, as it's
> completely different from this.

Cloned away. I haven't investigated those failures at all.

> The remaining problem seems to be a big-endian issue (mips, s390x,
> hppa, powerpc, sparc64). ppc64 fails in a slightly different manner,
> might just be it's failing earlier for a different reason but would
> also suffer from this bug.

I traced into this a bit and came to the same conclusion. It turns out
the failure mode is that the embedded code copy of libicu v58 fails
to initialize, because the embedded binary copy of the ICU data is
hard-coded to be the little-endian one by the build system (also it's
bundled in the source package rather than being built from source),
and at runtime libicu insists on its data files being of equal endianness.

This results in ./js/src/js/src/shell/js silently exiting 1 because
it makes no attempt at error reporting during initialization (insert
table flip here). ./js/src/js/src/shell/js is the standalone JavaScript
shell, similar to /usr/bin/js24 and analogous to /usr/bin/gjs-console - it
isn't installed any more in mozjs52 (I don't think) but it's still built
and used for build-time testing.

It is correct that this is release-critical, because it makes mozjs
completely useless on the affected architectures, as far as I can see.

To be less nasty to debug, I suspect the dh_auto_test override should
do something like this:

./js/src/js/src/shell/js -e 'print("hello, world") || { \
echo "js shell doesn't appear to work"; \
exit 1; \
}

before it even attempts to run upstream tests - and it should probably
try this even on architectures where the full test suite is skipped or
known-broken, because, again, if this fails then mozjs being available
is just a trap for the unwary.

These Firefox changes look promising:
https://anonscm.debian.org/cgit/pkg-mozilla/iceweasel.git/tree/debian/patches/debian-hacks/Allow-to-override-ICU_DATA_FILE-from-the-environment.patch
https://anonscm.debian.org/cgit/pkg-mozilla/iceweasel.git/log/?qt=grep=endian
although unfortunately the standalone mozjs doesn't have this:
https://anonscm.debian.org/cgit/pkg-mozilla/iceweasel.git/tree/intl/icu_sources_data.py
so we would need to insert a copy.

If libicu v59 (currently in experimental) is going to be uploaded to
unstable soon, then we might be able to reduce the level of wtf by using
the system libicu instead. Laszlo, what are your plans for icu v59?

Regards,
smcv

Processed: Missing dependencies are RC

[Debian Bug Tracking System]

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

> severity 518429 serious
Bug #518429 [libmpd-dev] libmpd-dev: should depend on libglib2.0-dev
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#853349: codeblocks: Patch for the build-failure

[Andreas Moog]

On Sat, Sep 30, 2017 at 09:21:43PM +0200, David Paleino wrote:

> Please go ahead, I currently don't have time :(

Ok, thanks for the reply. I filed a request for sponsorship as #877376.

Cheers,
  Andreas
-- 
PGP-encrypted mails preferred
PGP Fingerprint: 74CD D9FE 5BCB FE0D 13EE 8EEA 61F3 4426 74DE 6624


signature.asc
Description: PGP signature

Bug#871083: Bug#871083: python-pysam: FTBFS: Test failures

[Andreas Tille]

On Sun, Oct 01, 2017 at 12:38:33PM -0400, Afif Elghraoui wrote:
> 
> Okay, I've just skipped that one failing test and uploaded the new
> version in order to move things along.

Thanks a lot, Andreas.

-- 
http://fam-tille.de

Bug#876587: marked as done (gnutls28 FTBFS with gtk-doc-tools 1.26: gtkdoc-mktmpl is no longer available)

[Debian Bug Tracking System]

Your message dated Sun, 01 Oct 2017 17:20:21 +
with message-id 
and subject line Bug#876587: fixed in gnutls28 3.6.0-2
has caused the Debian Bug report #876587,
regarding gnutls28 FTBFS with gtk-doc-tools 1.26: gtkdoc-mktmpl is no longer 
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.)


-- 
876587: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876587
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnutls28
Version: 3.5.15-2
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/gnutls28.html

...
Making all in reference
make[6]: Entering directory '/build/1st/gnutls28-3.5.15/doc/reference'
  DOC   Scanning header files
  DOC   Rebuilding template files
/bin/bash: gtkdoc-mktmpl: command not found
Makefile:1671: recipe for target 'tmpl-build.stamp' failed
make[6]: *** [tmpl-build.stamp] Error 127
--- End Message ---
--- Begin Message ---
Source: gnutls28
Source-Version: 3.6.0-2

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

Debian distribution maintenance software
pp.
Andreas Metzler  (supplier of updated gnutls28 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, 01 Oct 2017 18:04:16 +0200
Source: gnutls28
Binary: libgnutls28-dev libgnutls30 gnutls-bin gnutls-doc libgnutlsxx28 
libgnutls-openssl27 libgnutls-dane0
Architecture: source
Version: 3.6.0-2
Distribution: experimental
Urgency: medium
Maintainer: Debian GnuTLS Maintainers 
Changed-By: Andreas Metzler 
Closes: 876587
Description: 
 gnutls-bin - GNU TLS library - commandline utilities
 gnutls-doc - GNU TLS library - documentation and examples
 libgnutls28-dev - GNU TLS library - development files
 libgnutls30 - GNU TLS library - main runtime library
 libgnutls-dane0 - GNU TLS library - DANE security support
 libgnutls-openssl27 - GNU TLS library - OpenSSL wrapper
 libgnutlsxx28 - GNU TLS library - C++ runtime library
Changes:
 gnutls28 (3.6.0-2) experimental; urgency=medium
 .
   * 35_modernize_gtkdoc.diff from upstream GIT master: Modernize gtk-doc
 support. Update gtk-doc.make, m4/gtk-doc.m4 and doc/reference/Makefile.am
 from gtk-doc git head (that is 1.26 +
 c08cc78562c59082fc83b55b58747177510b7a70). Disable gtkdoc-check.
 Closes: #876587
Checksums-Sha1: 
 16dc64a2bd06b505fb0a0a17ba04401a9d5a7041 3300 gnutls28_3.6.0-2.dsc
 6b19f5b611f253a25adaa92f19ad5510498da73e 106884 gnutls28_3.6.0-2.debian.tar.xz
Checksums-Sha256: 
 7e6b407151c710680e67fe890fcca0b032dd33731af80fb282f9d0b158e6a86a 3300 
gnutls28_3.6.0-2.dsc
 2dde9b7244aab27f75f26024d9a25a913f13b97b89d3af19ce11ca1bd82f391a 106884 
gnutls28_3.6.0-2.debian.tar.xz
Files: 
 252ae13b2ef77735e186835306f6d72f 3300 libs optional gnutls28_3.6.0-2.dsc
 dde07b6919cc2688c3c908d9d384ddc8 106884 libs optional 
gnutls28_3.6.0-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE0uCSA5741Jbt9PpepU8BhUOCFIQFAlnRHdIACgkQpU8BhUOC
FIQRaA/9GlOx7qJ3SyLCp++k7uuP+05SW8oFRGs9Jvwnuwf/0w9ez6FrsqWyZjyL
LU/2w3MBno1+H6ccXFAAoEwzEqR/9bVNiOeFylS13YhWUrAkB867Ql9Gy/b6Z7zu
GGk57RCkqp/uJevq2qz/5HakcL+TcxNsee+YOswm6sTUvlR+WNOrVjnw2pAgwmBH
hXV1NJscl/qAOEeZY0V15lSRfvK2pJF8v1Pi8LQ9BfZkArASFcYrjHAuyW1zjvyr
1PPGZ/w45NvArKp9uF88LZWTar9/uB/zwVIS24zmYfJwSPw8Uof1gCZDVXxhv5RB
x3pn3NhqF+sq7QHP3ndPgR98/xujzIurbhP8En7IPx60I1ZLe99ksVmaYktpoXux
jrXIMY81O7XuY5JdO8fpjzDf+mgYk4IkB0Sfn/6O2NdVbnc7DBA6CtKCWy8Nqbcf
801jlZ+Z9sjjn8xgngtoSZDEfC3rnflgHbpn3SVCkoeZu2KTfhMbdkUMJEeUmOTU
NEDt6aBTRn/AdotH3hxHdp8FcoQN3v8vWBnLRNvrNw0uWDKdj5mPNIMUVvnlWefU
n6r+giBgS+3OX7Eo0zjlkA9/oIIjEnabu+31BnXncGaFLljGEPTISy5uAR9+fl48
ce/VfN2k0yez4CoETvoDSgqhDVYM4C0GigywrvoS68wZPwo4ObQ=
=63C7
-END PGP SIGNATURE End Message ---

Bug#871083: marked as done (python-pysam: FTBFS: Test failures)

[Debian Bug Tracking System]

Your message dated Sun, 01 Oct 2017 16:50:00 +
with message-id 
and subject line Bug#871083: fixed in python-pysam 0.12.0.1+ds-1
has caused the Debian Bug report #871083,
regarding python-pysam: FTBFS: Test failures
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.)


-- 
871083: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871083
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-pysam
Version: 0.11.2.2+ds-3
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170805 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> --
> Traceback (most recent call last):
>   File "/<>/python-pysam-0.11.2.2+ds/tests/samtools_test.py", line 
> 149, in setUp
> self.check_version()
>   File "/<>/python-pysam-0.11.2.2+ds/tests/samtools_test.py", line 
> 139, in check_version
> samtools_version))
> ValueError: versions of pysam.samtools and samtools differ: 1.4.1 != 1.5
> 
> --
> Ran 760 tests in 56.829s
> 
> FAILED (SKIP=5, errors=2)
> (0, 0)
> E: pybuild pybuild:283: test: plugin distutils failed with: exit code=1: cd 
> /<>/python-pysam-0.11.2.2+ds/.pybuild/pythonX.Y_2.7/build; 
> python2.7 -m nose 
> dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13
> debian/rules:39: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   http://aws-logs.debian.net/2017/08/05/python-pysam_0.11.2.2+ds-3_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: python-pysam
Source-Version: 0.12.0.1+ds-1

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

Debian distribution maintenance software
pp.
Afif Elghraoui  (supplier of updated python-pysam 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, 01 Oct 2017 12:30:30 -0400
Source: python-pysam
Binary: python-pysam python3-pysam python-pysam-tests
Architecture: source
Version: 0.12.0.1+ds-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Afif Elghraoui 
Description:
 python-pysam - interface for the SAM/BAM sequence alignment and mapping format 
(
 python-pysam-tests - interface for the SAM/BAM sequence alignment and mapping 
format (
 python3-pysam - interface for the SAM/BAM sequence alignment and mapping 
format (
Closes: 834856 871083
Changes:
 python-pysam (0.12.0.1+ds-1) unstable; urgency=medium
 .
   [ Andreas Tille ]
   * Drop patch applied upstream
   * Standards-Version: 4.1.0 (no changes needed)
   * Apply upstream patch to fix test suite
   * Use pytest instead of nosetest
 .
   [ Afif Elghraoui ]
   * New upstream version
 Closes: #871083, #834856
   * Bump htslib suite minimum versions
   * Use Build Profiles to mark build-dependencies needed only for tests
   * Temporarily skip a failing test (reported upstream)
 .
   [ Steffen Moeller ]
   * created debian/upstream/metadata: references to registries
Checksums-Sha1:
 e5015d8272b4afe9140d65096ee2cc278a89061e 2719 python-pysam_0.12.0.1+ds-1.dsc
 260fae1b00dd50f3e9c4857d8b1949252621a593 2497809 
python-pysam_0.12.0.1+ds.orig.tar.gz
 0dc19cd5d9258e653c45e670591b5acbd32b9775 9208 
python-pysam_0.12.0.1+ds-1.debian.tar.xz
 cf12f5fe2baa5339f44820a5280ebeca87e2c984 7770 
python-pysam_0.12.0.1+ds-1_source.buildinfo
Checksums-Sha256:
 

Bug#877191: (no subject)

[Paulo Henrique de Lima Santana]

severity 877191 grave
thanks

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

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


pgpjG3ibsEn_0.pgp
Description: PGP signature

Bug#877320: marked as done (ruby-kramdown FTBFS and Debci failure: test failures)

[Debian Bug Tracking System]

Your message dated Sun, 01 Oct 2017 16:42:03 +
with message-id 
and subject line Bug#877320: fixed in ruby-kramdown 1.15.0-1
has caused the Debian Bug report #877320,
regarding ruby-kramdown FTBFS and Debci failure: test failures
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.)


-- 
877320: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877320
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-kramdown
Version: 1.14.0-1
Severity: serious

Some recent change in unstable makes ruby-kramdown FTBFS and Debci fail:

https://ci.debian.net/packages/r/ruby-kramdown/unstable/amd64/
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ruby-kramdown.html

...
  1) Failure:
TestFiles#test_/build/1st/ruby-kramdown-1_14_0/test/testcases/block/06_codeblock/rouge/multiple_text_to_html
 [/build/1st/ruby-kramdown-1.14.0/test/test_files.rb:69]:
--- expected
+++ actual
@@ -1,12 +1,12 @@
-"puts \"Hello\"
+"puts \"Hello\"
 
-
+
 
-puts \"World\"
+puts \"World\"
 
-
+
 
-$foo = new Bar;
+$foo = new Bar;
 
-
+
 "


  2) Failure:
TestFiles#test_/build/1st/ruby-kramdown-1_14_0/test/testcases/block/06_codeblock/rouge/simple_text_to_html
 [/build/1st/ruby-kramdown-1.14.0/test/test_files.rb:69]:
--- expected
+++ actual
@@ -1,11 +1,11 @@
-"x = 
Class.new
+"x = 
Class.new
 
-
-ahref/a
+
+ahref/a
 
-
+
 
-$foo = new Bar;
+$foo = new Bar;
 
-
+
 "


  3) Failure:
TestFiles#test_gfm_/build/1st/ruby-kramdown-1_14_0/test/testcases/block/06_codeblock/rouge/simple_text_to_html
 [/build/1st/ruby-kramdown-1.14.0/test/test_files.rb:380]:
--- expected
+++ actual
@@ -1,11 +1,11 @@
-"x = 
Class.new
+"x = 
Class.new
 
-
-ahref/a
+
+ahref/a
 
-
+
 
-$foo = new Bar;
+$foo = new Bar;
 
-
+
 "


  4) Failure:
TestFiles#test_gfm_/build/1st/ruby-kramdown-1_14_0/test/testcases/block/06_codeblock/rouge/multiple_text_to_html
 [/build/1st/ruby-kramdown-1.14.0/test/test_files.rb:380]:
--- expected
+++ actual
@@ -1,12 +1,12 @@
-"puts \"Hello\"
+"puts \"Hello\"
 
-
+
 
-puts \"World\"
+puts \"World\"
 
-
+
 
-$foo = new Bar;
+$foo = new Bar;
 
-
+
 "


2686 runs, 187391 assertions, 4 failures, 0 errors, 0 skips
rake aborted!
Command failed with status (1): [ruby -w -I"lib"  
"/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" "test/test_files.rb" 
"test/test_location.rb" "test/test_string_scanner_kramdown.rb" ]

Tasks: TOP => default => test
(See full trace by running task with --trace)
ERROR: Test "ruby2.3" failed. Exiting.
dh_auto_install: dh_ruby --install 
/build/1st/ruby-kramdown-1.14.0/debian/ruby-kramdown returned exit code 1
debian/rules:6: recipe for target 'binary' failed
make: *** [binary] Error 1
--- End Message ---
--- Begin Message ---
Source: ruby-kramdown
Source-Version: 1.15.0-1

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

Debian distribution maintenance software
pp.
Cédric Boutillier  (supplier of updated ruby-kramdown 
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, 01 Oct 2017 15:38:06 +0200
Source: ruby-kramdown
Binary: ruby-kramdown
Architecture: source
Version: 1.15.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Cédric Boutillier 
Description:
 ruby-kramdown - Fast, pure-Ruby Markdown-superset converter
Closes: 877320
Changes:
 ruby-kramdown (1.15.0-1) unstable; urgency=medium
 .
   * Team upload
   * New upstream version 1.15.0
 * Add full support for ruby-rouge >= 2 in tests (Closes: #877320)
   * Drop rouge2.patch, not needed any more
   * Bump Standards-Version to 4.1.1 (no changes needed)
Checksums-Sha1:
 7b78385fc289292ba6a4275ccb4b71970e6ad7b5 1914 ruby-kramdown_1.15.0-1.dsc
 1dc8c085b4d7dba13556f3d63a6cd26220ae9e0b 255426 
ruby-kramdown_1.15.0.orig.tar.gz
 07a9cb8dafcd6261d1e3d3ff324afd402e1f344f 4936 
ruby-kramdown_1.15.0-1.debian.tar.xz
 cc6677f3064c86627f96c98e53a8da82c3e99962 9136 

Bug#876479: marked as done (tilix fails to start up, conflicting dependencies on libphobos with libgtkd-3-0)

[Debian Bug Tracking System]

Your message dated Sun, 01 Oct 2017 16:42:14 +
with message-id 
and subject line Bug#876479: fixed in tilix 1.6.4-2
has caused the Debian Bug report #876479,
regarding tilix fails to start up, conflicting dependencies on libphobos with 
libgtkd-3-0
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.)


-- 
876479: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876479
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tilix
Version: 1.6.4-1+b1
Severity: important

Dear Maintainer,

There is a dependency conflict that makes tilix fail to startup
currently.

The problem seems to be that libgtkd-3-0 is built with libphobos2-ldc72,
whereas tilix is built with libphobos2-ldc74

This naturally causes the libraries to conflict, like so:

$ tilix
Fatal Error while loading '/usr/lib/x86_64-linux-gnu/libdruntime-ldc.so.72':
The module 'core.atomic' is already defined in 
'/usr/lib/x86_64-linux-gnu/libdruntime-ldc.so.74'.

Thanks!
Abhijit


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

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

Versions of packages tilix depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.26.0-2+b1
ii  libc62.25-0experimental3
ii  libgtkd-3-0  3.6.5-2
ii  libphobos2-ldc74 1:1.4.0-1
ii  libvted-3-0  3.6.5-2
ii  libx11-6 2:1.6.4-3
ii  tilix-common 1.6.4-1

tilix recommends no packages.

tilix suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: tilix
Source-Version: 1.6.4-2

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

Debian distribution maintenance software
pp.
Matthias Klumpp  (supplier of updated tilix 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, 01 Oct 2017 18:06:48 +0200
Source: tilix
Binary: tilix tilix-common
Architecture: source all amd64
Version: 1.6.4-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Matthias Klumpp 
Description:
 tilix  - Tiling terminal emulator for GNOME
 tilix-common - Tiling terminal emulator - data files
Closes: 873246 876479
Changes:
 tilix (1.6.4-2) unstable; urgency=medium
 .
   * Suggest python-nautilus (Closes: #873246)
   * Bump standards version: No changes needed
   * Ensure Tilix is built with the latest LDC and GtkD (Closes: #876479)
Checksums-Sha1:
 179b178d1491f1bf8c80198241dc7074e1dffd15 2093 tilix_1.6.4-2.dsc
 ec94620d739290bcda5661beb7d974784223 15100 tilix_1.6.4-2.debian.tar.xz
 ff44bf1420046a4e62db51b5fdde533a1a8504d6 197316 tilix-common_1.6.4-2_all.deb
 f1196f4782d6d28310aaed214612c77860c1d66f 1113954 tilix-dbgsym_1.6.4-2_amd64.deb
 95e96e35e2e4d7aaee888a497e98ddcfc9d7668f 14088 tilix_1.6.4-2_amd64.buildinfo
 58ccd544abc2783ae3a05a7115554aab59ba2e4f 471110 tilix_1.6.4-2_amd64.deb
Checksums-Sha256:
 7620038352c8a5fda49a36e0b371e810c93e40d1b8098b4cec17bbd6d18cde88 2093 
tilix_1.6.4-2.dsc
 7c1c386c60f45bf7aac3042e1a8acd186e56773952dc51afe1ff375f552af6dc 15100 
tilix_1.6.4-2.debian.tar.xz
 7d230efb839b0d4d13b1b63b2ede1fe2742fb378e13336579955d2d21a862288 197316 
tilix-common_1.6.4-2_all.deb
 30a0750c104138a1b7bcc72f2659d0663ec84ed84c89845cb56834b9e1b98398 1113954 
tilix-dbgsym_1.6.4-2_amd64.deb
 9234af594a23d5b7a7de9918247ddb327af16934156282d8ec5f9a079a7452d7 14088 
tilix_1.6.4-2_amd64.buildinfo
 

Processed: etl: diff for NMU version 0.04.19-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 853674 + patch
Bug #853674 [etl-dev] etl-dev: /usr/include/ETL/_surface.h error with gcc 7
Bug #853675 [etl-dev] etl-dev: /usr/include/ETL/_surface.h error with gcc 7
Added tag(s) patch.
Added tag(s) patch.
> tags 853674 + pending
Bug #853674 [etl-dev] etl-dev: /usr/include/ETL/_surface.h error with gcc 7
Bug #853675 [etl-dev] etl-dev: /usr/include/ETL/_surface.h error with gcc 7
Added tag(s) pending.
Added tag(s) pending.

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

Bug#853674: etl: diff for NMU version 0.04.19-1.1

[Adrian Bunk]

Control: tags 853674 + patch
Control: tags 853674 + pending

Dear maintainer,

I've prepared an NMU for etl (versioned as 0.04.19-1.1) and uploaded
it to DELAYED/10. Please feel free to tell me if I should cancel it.

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

diff -Nru etl-0.04.19/debian/changelog etl-0.04.19/debian/changelog
--- etl-0.04.19/debian/changelog	2015-09-29 10:56:18.0 +0300
+++ etl-0.04.19/debian/changelog	2017-10-01 19:19:36.0 +0300
@@ -1,3 +1,12 @@
+etl (0.04.19-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add upstream gcc 7 fix. (Closes: #853674)
+  * Make test failures fatal to catch such errors earlier.
+  * Stop setting the (already default) xz compression.
+
+ -- Adrian Bunk   Sun, 01 Oct 2017 19:19:36 +0300
+
 etl (0.04.19-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru etl-0.04.19/debian/patches/0001-Fix-ETL-compilation-error-at-GCC-7-Fix-396.patch etl-0.04.19/debian/patches/0001-Fix-ETL-compilation-error-at-GCC-7-Fix-396.patch
--- etl-0.04.19/debian/patches/0001-Fix-ETL-compilation-error-at-GCC-7-Fix-396.patch	1970-01-01 02:00:00.0 +0200
+++ etl-0.04.19/debian/patches/0001-Fix-ETL-compilation-error-at-GCC-7-Fix-396.patch	2017-10-01 19:19:11.0 +0300
@@ -0,0 +1,26 @@
+From b256ca29cc986a20266c40a47d031b8de90dcb8b Mon Sep 17 00:00:00 2001
+From: Ivan Mahonin 
+Date: Sat, 5 Aug 2017 14:57:33 +0700
+Subject: Fix ETL compilation error at GCC 7 (Fix #396)
+
+https://github.com/synfig/synfig/issues/396
+---
+ ETL/ETL/_surface.h | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/ETL/ETL/_surface.h b/ETL/ETL/_surface.h
+index 6513b608e..723d95b37 100644
+--- a/ETL/_surface.h
 b/ETL/_surface.h
+@@ -190,7 +190,7 @@ private:
+ 
+ 	value_prep_type cooker_;
+ 
+-	void swap(const surface )
++	void swap(surface )
+ 	{
+ 		std::swap(data_,x.data_);
+ 		std::swap(zero_pos_,x.zero_pos_);
+-- 
+2.11.0
+
diff -Nru etl-0.04.19/debian/patches/series etl-0.04.19/debian/patches/series
--- etl-0.04.19/debian/patches/series	1970-01-01 02:00:00.0 +0200
+++ etl-0.04.19/debian/patches/series	2017-10-01 19:19:36.0 +0300
@@ -0,0 +1 @@
+0001-Fix-ETL-compilation-error-at-GCC-7-Fix-396.patch
diff -Nru etl-0.04.19/debian/rules etl-0.04.19/debian/rules
--- etl-0.04.19/debian/rules	2013-05-15 02:56:37.0 +0300
+++ etl-0.04.19/debian/rules	2017-10-01 19:19:36.0 +0300
@@ -5,10 +5,3 @@
 
 %:
 	dh $@ --with autoreconf
-
-override_dh_auto_test:
-	# do not stop if test(s) failed
-	-dh_auto_test
-
-override_dh_builddeb:
-	dh_builddeb -- -Zxz
diff -Nru etl-0.04.19/debian/source/options etl-0.04.19/debian/source/options
--- etl-0.04.19/debian/source/options	2013-05-15 02:56:37.0 +0300
+++ etl-0.04.19/debian/source/options	1970-01-01 02:00:00.0 +0200
@@ -1 +0,0 @@
-compression = "xz"

Processed: your mail

[Debian Bug Tracking System]

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

> severity 877191 grave
Bug #877191 [python3-openflow] Package is not installing
Severity set to 'grave' from 'critical'
> thanks
Stopping processing here.

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

Bug#871083: [Debian-med-packaging] Bug#871083: python-pysam: FTBFS: Test failures

[Afif Elghraoui]

على السبت 30 أيلول 2017 ‫21:52، كتب peter green:
> My understanding is that the new version of python 2.7 removed a module 
> called "_PyFPE" and that C extensions referencing symbols from this module 
> need to be rebuilt. This has been enforced by breaks in the python2.7 
> package. Your package is on said list.
> 
> So for the new python2.7 to migrate to testing the FTBFS in python-pysam 
> needs to be fixed.

Okay, I've just skipped that one failing test and uploaded the new
version in order to move things along.

regards
Afif

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

Processed: tagging 877412

[Debian Bug Tracking System]

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

> tags 877412 + confirmed
Bug #877412 [src:beginend-el] beginend-el FTBFS with elpa-buttercup 1.9
Added tag(s) confirmed.
> thanks
Stopping processing here.

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

Processed: Bug#876479 marked as pending

[Debian Bug Tracking System]

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

> tag 876479 pending
Bug #876479 [tilix] tilix fails to start up, conflicting dependencies on 
libphobos with libgtkd-3-0
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#876479: marked as pending

[Matthias Klumpp]

tag 876479 pending
thanks

Hello,

Bug #876479 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:

https://anonscm.debian.org/cgit/pkg-gnome/tilix.git/commit/?id=988902c

---
commit 988902ca7a0fc22e879b709a7b022db6357ee956
Author: Matthias Klumpp 
Date:   Sun Oct 1 18:07:24 2017 +0200

Finalize changelog for 1.6.4-2

diff --git a/debian/changelog b/debian/changelog
index 9df65f7..347720d 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+tilix (1.6.4-2) unstable; urgency=medium
+
+  * Suggest python-nautilus (Closes: #873246)
+  * Bump standards version: No changes needed
+  * Ensure Tilix is built with the latest LDC and GtkD (Closes: #876479)
+
+ -- Matthias Klumpp   Sun, 01 Oct 2017 18:06:48 +0200
+
 tilix (1.6.4-1) unstable; urgency=medium
 
   * New upstream version: 1.6.4

Processed: your mail

[Debian Bug Tracking System]

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

> severity 877193 grave
Bug #877193 [kytos-utils] Package is not installing
Severity set to 'grave' from 'critical'
> thanks
Stopping processing here.

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