Processed: severity of 873907 is grave

[Debian Bug Tracking System]

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

> severity 873907 grave
Bug #873907 [src:asterisk] AST-2017-005 - Media takeover in RTP stack
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

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

Bug#873878: [gluster-packaging] Fwd: Bug#873878: glusterfs-client: mount.glusterfs needs bash as /bin/sh

[anoopcs]

On 2017-09-01 16:55, Patrick Matthäi wrote:

Am 01.09.2017 um 11:40 schrieb Niels de Vos:

On Fri, Sep 01, 2017 at 09:36:16AM +0200, Patrick Matthäi wrote:

Hi,

how should it be fixed for glusterfs now? Better shell code without
bashishm or do you want /bin/bash as shebang?

Do you have a preference? I do not know how much work is it is to
rewrite the mount.glusterfs script to remove all the Bashisms.


Apart from string indexing(which was caught here) sample run with 
`shellcheck` only complains about the usage of 'local' built-in which is 
undefined for POSIX sh.


At least in the Debian builds you may want to patch it to /bin/bash 
for the time

being.


I would prefer a patch, so that it works without bash. Luckily the bug
reporter just wrote a patch :)
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873878#10


The patch looks good to me. I have attached the patch to this thread for 
a quick look.



If you would merge it, I also would add it to the repository.


Can we get this patch get converted into a official change on 
review.gluster.org so that it can be officially reviewed and 
subsequently merged.



I have attached two other patches for 3.12.x, too.



Opinions welcome :) Thanks,
Niels




 Weitergeleitete Nachricht 
Betreff:Bug#873878: glusterfs-client: mount.glusterfs needs bash as
/bin/sh
Weitersenden-Datum: Thu, 31 Aug 2017 20:21:01 +
Weitersenden-Von:   Michael Lundkvist 
Weitersenden-An:debian-bugs-d...@lists.debian.org
Weitersenden-CC:Patrick Matthäi 
Datum:  Thu, 31 Aug 2017 21:46:18 +0200
Von:Michael Lundkvist 
Antwort an: Michael Lundkvist ,
873...@bugs.debian.org
An: Debian Bug Tracking System 



Package: glusterfs-client
Version: 3.12.0-1
Severity: serious
Tags: upstream
Justification: Policy 10.4

Version 3.12 of Glusterfs adds code in /sbin/mount.glusterfs that 
depends on bash.


With dash as /bin/sh, I get the following error message when trying 
to mount a glusterfs volume:

/sbin/mount.glusterfs: 667: /sbin/mount.glusterfs: Bad substitution

Line 667 is:
667 [ ${volume_str:0:1} = '/' ] && {

Modifying mount.glusterfs to use /bin/bash makes it possible to mount 
again.


/Micke


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

Kernel: Linux 4.12.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:en (charmap=UTF-8)

Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages glusterfs-client depends on:
ii  fuse  2.9.7-1
ii  glusterfs-common  3.12.0-1
ii  libc6 2.24-17
ii  libssl1.1 1.1.0f-5
ii  python2.7.13-2

glusterfs-client recommends no packages.

glusterfs-client suggests no packages.

-- no debconf information

___
packaging mailing list
packag...@gluster.org
http://lists.gluster.org/mailman/listinfo/packaging


___
packaging mailing list
packag...@gluster.org
http://lists.gluster.org/mailman/listinfo/packaging
diff --git a/xlators/mount/fuse/utils/mount.glusterfs.in b/xlators/mount/fuse/utils/mount.glusterfs.in
index 216d03c41..51792c479 100755
--- a/xlators/mount/fuse/utils/mount.glusterfs.in
+++ b/xlators/mount/fuse/utils/mount.glusterfs.in
@@ -673,8 +673,9 @@ main ()
 [ -n "$volume_str" ] && {
 volume_id=$volume_str
 volume_str_temp=$volume_str
-[ ${volume_str:0:1} = '/' ] && {
-volume_str_temp=${volume_str:1}
+	first_char=$(echo "$volume_str" | cut -c 1)
+[ ${first_char} = '/' ] && {
+volume_str_temp=$(echo "$volume_str" | cut -c 2-)
 }
 [ $(echo $volume_str_temp | grep -c "/") -eq 1 ] && {
 volume_id=$(echo "$volume_str_temp" | cut -f1 -d '/');

Bug#871147: marked as done (akonadi: FTBFS: collectionsync.cpp:836:10: fatal error: moc_collectionsync_p.cpp: No such file or directory)

[Debian Bug Tracking System]

Your message dated Sat, 02 Sep 2017 05:49:52 +
with message-id 
and subject line Bug#871147: fixed in akonadi 4:17.08.0-1
has caused the Debian Bug report #871147,
regarding akonadi: FTBFS: collectionsync.cpp:836:10: fatal error: 
moc_collectionsync_p.cpp: No such file or directory
to be marked as done.

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

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


-- 
871147: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871147
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: akonadi
Version: 4:16.04.3-5
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):
> /usr/bin/c++  -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -fvisibility=hidden 
> -fvisibility-inlines-hidden -Wdate-time -D_FORTIFY_SOURCE=2 -Wdate-time 
> -D_FORTIFY_SOURCE=2 -std=c++0x -Wall -Wextra -Wcast-align -Wchar-subscripts 
> -Wformat-security -Wno-long-long -Wpointer-arith -Wundef -Wnon-virtual-dtor 
> -Woverloaded-virtual -Werror=return-type -pedantic -std=c++0x 
> -Wnon-virtual-dtor -Wundef -Wcast-align -Wchar-subscripts -Wall -Wextra 
> -Wpointer-arith -Wformat-security -fno-common -fexceptions -fexceptions  
> -Wl,--enable-new-dtags -Wl,-z,relro -Wl,--as-needed -Wl,--no-undefined 
> -rdynamic CMakeFiles/akonadi-firstrun.dir/__/__/src/core/firstrun.cpp.o 
> CMakeFiles/akonadi-firstrun.dir/firstrunner.cpp.o 
> CMakeFiles/akonadi-firstrun.dir/__/__/src/core/akonadicore_debug.cpp.o 
> CMakeFiles/akonadi-firstrun.dir/akonadi-firstrun_autogen/mocs_compilation.cpp.o
>   -o akonadi-firstrun 
> -Wl,-rpath,/<>/obj-x86_64-linux-gnu/src/core:/<>/obj-x86_64-linux-gnu/src/private
>  /usr/lib/x86_64-linux-gnu/libQt5Test.so.5.7.1 
> ../../src/core/libKF5AkonadiCore.so.5.2.2 
> /usr/lib/x86_64-linux-gnu/libKF5DBusAddons.so.5.28.0 
> /usr/lib/x86_64-linux-gnu/libKF5ItemModels.so.5.28.0 
> /usr/lib/x86_64-linux-gnu/libKF5ConfigCore.so.5.28.0 
> /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5.7.1 
> /usr/lib/x86_64-linux-gnu/libKF5CoreAddons.so.5.28.0 
> /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5.7.1 
> /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5.7.1 
> /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.7.1 
> -Wl,-rpath-link,/<>/obj-x86_64-linux-gnu/src/private 
> In file included from 
> /<>/autotests/libs/collectionsynctest.cpp:30:0:
> /<>/obj-x86_64-linux-gnu/../src/core/collectionsync.cpp:836:10: 
> fatal error: moc_collectionsync_p.cpp: No such file or directory
>  #include "moc_collectionsync_p.cpp"
>   ^~
> compilation terminated.
> autotests/libs/CMakeFiles/collectionsynctest.dir/build.make:65: recipe for 
> target 
> 'autotests/libs/CMakeFiles/collectionsynctest.dir/collectionsynctest.cpp.o' 
> failed
> make[4]: *** 
> [autotests/libs/CMakeFiles/collectionsynctest.dir/collectionsynctest.cpp.o] 
> Error 1

The full build log is available from:
   http://aws-logs.debian.net/2017/08/05/akonadi_16.04.3-5_unstable.log

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

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

We believe that the bug you reported is fixed in the latest version of
akonadi, 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.
Maximiliano Curia  (supplier of updated akonadi 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: Fri, 01 Sep 2017 22:07:58 +0200
Source: akonadi
Binary: akonadi-backend-mysql akonadi-backend-postgresql akonadi-backend-sqlite 
akonadi-server libkf5akonadi-dev libkf5akonadi-dev-bin libkf5akonadiagentbase5 
libkf5akonadicore-bin libkf5akonadicore5 libkf5akonadiprivate5 
libkf5akonadis

Bug#873627: udisks2 in sid apparently left me with a borked system in plasma(?))

[Ben Caradoc-Davies]

I can confirm that udisks2 2.7.2-2 fixes the thunar problems that I 
reported above: I see only the "usual" filesystems and can mount and 
unmount removable devices as expected.


Kind regards,

--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

Bug#871347: marked as done (tycho: FTBFS: [ERROR] /<>/tycho-packaging-plugin/src/main/java/org/eclipse/tycho/packaging/LicenseFeatureHelper.java:[121,15] cannot find symbol)

[Debian Bug Tracking System]

Your message dated Sat, 02 Sep 2017 03:11:43 +
with message-id 
and subject line Bug#871347: fixed in tycho 0.25.0-2
has caused the Debian Bug report #871347,
regarding tycho: FTBFS: [ERROR] 
/<>/tycho-packaging-plugin/src/main/java/org/eclipse/tycho/packaging/LicenseFeatureHelper.java:[121,15]
 cannot find symbol
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.)


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

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build -- package -Dmaven.test.skip=true
>   /usr/lib/jvm/default-java/bin/java -noverify -cp 
> /usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
>  -Dmaven.home=/usr/share/maven 
> -Dmaven.multiModuleProjectDirectory=/<> 
> -Dclassworlds.conf=/etc/maven/m2-debian.conf 
> org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
> -Dmaven.repo.local=/<>/debian/maven-repo package 
> -Dmaven.test.skip=true -DskipTests -Dnotimestamp=true -Dlocale=en_US
> [INFO] Scanning for projects...
> [WARNING] 
> [WARNING] Some problems were encountered while building the 
> effective model for 
> org.eclipse.tycho:org.eclipse.osgi:jar:3.10.101.v20150820-1432
> [WARNING] Reporting configuration should be done in  
> section, not in maven-site-plugin  as reportPlugins parameter.
> [WARNING] 
> [WARNING] Some problems were encountered while building the 
> effective model for 
> org.eclipse.tycho:org.eclipse.jdt.core:jar:3.11.1.v20150902-1521
> [WARNING] Reporting configuration should be done in  
> section, not in maven-site-plugin  as reportPlugins parameter.
> [WARNING] 
> [WARNING] Some problems were encountered while building the 
> effective model for 
> org.eclipse.tycho:org.eclipse.osgi.compatibility.state:jar:1.0.100.v20150402-1551
> [WARNING] Reporting configuration should be done in  
> section, not in maven-site-plugin  as reportPlugins parameter.
> [WARNING] 
> [WARNING] Some problems were encountered while building the 
> effective model for 
> org.eclipse.tycho:org.eclipse.jdt.compiler.apt:jar:1.2.0.v20150514-0146
> [WARNING] Reporting configuration should be done in  
> section, not in maven-site-plugin  as reportPlugins parameter.
> [WARNING] 
> [WARNING] Some problems were encountered while building the 
> effective model for 
> org.eclipse.tycho:org.eclipse.tycho.embedder.shared:jar:0.25.0
> [WARNING] Reporting configuration should be done in  
> section, not in maven-site-plugin  as reportPlugins parameter.
> [WARNING] 
> [WARNING] Some problems were encountered while building the 
> effective model for org.eclipse.tycho:org.eclipse.tycho.core.shared:jar:0.25.0
> [WARNING] Reporting configuration should be done in  
> section, not in maven-site-plugin  as reportPlugins parameter.
> [WARNING] 
> [WARNING] Some problems were encountered while building the 
> effective model for 
> org.eclipse.tycho:org.eclipse.tycho.p2.resolver.shared:jar:0.25.0
> [WARNING] Reporting configuration should be done in  
> section, not in maven-site-plugin  as reportPlugins parameter.
> [WARNING] 
> [WARNING] Some problems were encountered while building the 
> effective model for 
> org.eclipse.tycho:org.eclipse.tycho.p2.tools.shared:jar:0.25.0
> [WARNING] Reporting configuration should be done in  
> section, not in maven-site-plugin  as reportPlugins parameter.
> [WARNING] 
> [WARNING] Some problems were encountered while building the 
> effective model for 
> org.eclipse.tycho:org.eclipse.tycho.p2.resolver.impl:jar:0.25.0
> [WARNING] Reporting configuration should be done in  
> section, not in maven-site-plugin  as reportPlugins parameter.
> [WARNING] 
> [WARNING] Some problems were encountered while building the 
> effective model for 
> org.eclipse.tycho:org.eclipse.tycho.p2.maven.repository:jar:0.25.0
> [WARNING] Reporting configuration should be done in  
> section, not in maven-site-plugin  as re

Bug#873091: marked as done (missing dependency on libffi-dev)

[Debian Bug Tracking System]

Your message dated Sat, 02 Sep 2017 03:06:20 +
with message-id 
and subject line Bug#873091: fixed in ecl 16.1.2-3
has caused the Debian Bug report #873091,
regarding missing dependency on libffi-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.)


-- 
873091: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873091
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ecl
Version: 15.3.7+dfsg1-2+b1
Severity: serious

Dear Maintainers,

It looks like ecl is missing a dependency on libffi-dev.

For example, with ecl and cl-ppcre installed (but not libffi-dev), the
compilation of cl-ppcre fails:

> (require "asdf")
[…]
> (require "cl-ppcre")
[…]
/usr/bin/ld: cannot find -lffi
collect2: error: ld returned 1 exit status
ASDF could not load cl-ppcre because Error code 1 when executing
(RUN-PROGRAM "gcc" ("-o"

".cache/common-lisp/ecl-15.3.7-unknown-linux-x64/usr/share/common-lisp/source/cl-asdf/build/asdf-TMP.fas"
"-L/usr/lib/" "/tmp/eclinit1NyJ3T.o"

".cache/common-lisp/ecl-15.3.7-unknown-linux-x64/usr/share/common-lisp/source/cl-asdf/build/asdf.o"
"-shared" "-lecl" "-lgmp" "-lgc" "-lffi" "-lpthread" "-ldl"
"-lm")).

Note that there is already a dependency of ecl on libffi6, but this is not 
enough.

Cheers,

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


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ecl
Source-Version: 16.1.2-3

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

Debian distribution maintenance software
pp.
Tobias Hansen  (supplier of updated ecl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 02 Sep 2017 02:19:44 +0100
Source: ecl
Binary: ecl
Architecture: source
Version: 16.1.2-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Common Lisp Team 

Changed-By: Tobias Hansen 
Description:
 ecl- Embeddable Common-Lisp: has an interpreter and can compile to C
Closes: 873091
Changes:
 ecl (16.1.2-3) unstable; urgency=medium
 .
   * Add dependency on libffi-dev for ecl (Closes: #873091).
   * Use debhelper compat level 8.
   * Update Standards-Version to 4.1.0.
Checksums-Sha1:
 21369e63a4328162a209f921c801b4ea6fb12d7a 2150 ecl_16.1.2-3.dsc
 1647ff901d48fdf681ebbcdd9c2ae77796e8027c 8588 ecl_16.1.2-3.debian.tar.xz
 8b4380856cbac14b6ed7c9358b183b938f16732f 6045 ecl_16.1.2-3_source.buildinfo
Checksums-Sha256:
 441c99cf44c53ecbff2eb1002a4ef4560f9d338032269dbbaa1eb44d6427167e 2150 
ecl_16.1.2-3.dsc
 fffe367c372d4287a3473b4f2aad0cee90badea5d8198b322421e4d43d4b95ab 8588 
ecl_16.1.2-3.debian.tar.xz
 43ae28bc40d25cf9d3a609f574ef9d40c79536b0f72249939a7bdc88b6936c6b 6045 
ecl_16.1.2-3_source.buildinfo
Files:
 9ff6e4391134e0ad4c2708d038361741 2150 devel optional ecl_16.1.2-3.dsc
 101825135dd1ab740ac13cb77a465722 8588 devel optional ecl_16.1.2-3.debian.tar.xz
 f9fd0c2c1cc9f6f58163fd87fc61ccf9 6045 devel optional 
ecl_16.1.2-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEoH46ol3M2u2mYo0kjIIWnY7OzSoFAlmqDsAACgkQjIIWnY7O
zSp8gQ/9F5PGMdyVISYS3+qFCvGaVu9lyIVge557+dE/O4RNV8OM8wZEHwXdK5qz
rolcT69ya/rzy+1SGxffW45mSFNlP4G+fSifkgK7JfHvMDSK1dCrpGQ2+8I9OgGJ
JlccaV87z+IJPncBA9DY/BlvYENL8EHTjt53PRwTklIfEd+uH6jXQYNjI8Sc/G8S
ijHscria1l/KYZTQe767HWy7J4C+ABBIoJmv9MUH3e8sL5/KQKhkctirZQ6cELt8
+wEwdaeMN/JVg8pXeEZQnGieqT8PYpefmD5Q8vGqYteXhuiL1RF0r85i2MXiUPo9
nEzN4U4KGncDjt/TP5CstCb+9akPoNBYIBikkCNCeVT/JJ4Gt/pYGkHphkyn/kwH
yFLp3nFfyrAXeDqN995xgwFXsGBetyyS4nk2yhJ5DZrovtm/9FAnFwawDssKKdLo
xa768qWJt8RLYSV7RQMjR7mAMPmiqQ10vee/v0MpboUz8sJhc5aIY7aOsjYSATAE
Ka93SpknRlsVMN/A9cGYz4WUw1SJ3nCPV7ugfGUvQNUYrCPs35C4z6N5X1Jfoatg
3QDWQKsOZ2+jPeevoMlTEhif91e2Sd4eHSI7Ma4zbpKP1znsgAyHPx5Lq6yTlpYp
x9fFtV7Zu/LLSVgAum6w0W68kexZ4ZfrwHrQ3JeDrGyxCubin2U=
=wqfi
-END PGP SIGNATURE End Message ---

Bug#871348: marked as done (robocode: FTBFS: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:2.8:unpack-dependencies (unpack-dependencies) on p

[Debian Bug Tracking System]

Your message dated Sat, 02 Sep 2017 00:37:11 +
with message-id 
and subject line Bug#871348: fixed in robocode 1.9.2.6-3
has caused the Debian Bug report #871348,
regarding robocode: FTBFS: [ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-dependency-plugin:2.8:unpack-dependencies
 (unpack-dependencies) on project robocode.tests.robots: 
Execution unpack-dependencies of goal 
org.apache.maven.plugins:maven-dependency-plugin:2.8:unpack-dependencies 
failed: A required class was missing while executing 
org.apache.maven.plugins:maven-dependency-plugin:2.8:unpack-dependencies: 
org/codehaus/plexus/util/MatchPatterns
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.)


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

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> sed -e 's/@RCVER@/1.9.2.6/g' < debian/misc/robocode.in > debian/misc/robocode
> sed -e 's/@RCVER@/1.9.2.6/g' < debian/misc/compiler.properties.in > 
> debian/misc/compiler.properties
> sed -e 's/@RCVER@/1.9.2.6/g' < debian/examples/roborumble.in > 
> debian/examples/roborumble
> sed -e 's/@RCVER@/1.9.2.6/g' < debian/maven.properties.in > 
> debian/maven.properties
> dh_auto_build
>   /usr/lib/jvm/default-java/bin/java -noverify -cp 
> /usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
>  -Dmaven.home=/usr/share/maven 
> -Dmaven.multiModuleProjectDirectory=/<> 
> -Dclassworlds.conf=/etc/maven/m2-debian.conf 
> -Dproperties.file.manual=/<>/debian/maven.properties 
> org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
> -Dmaven.repo.local=/<>/debian/maven-repo package -DskipTests 
> -Dnotimestamp=true -Dlocale=en_US
> [INFO] Scanning for projects...
> [WARNING] 
> [WARNING] Some problems were encountered while building the 
> effective model for net.sf.robocode:robocode.api:jar:1.9.2.6
> [WARNING] 'version' contains an expression but should be a 
> constant. @ net.sf.robocode:robocode.api:${robocode.version}, 
> /<>/robocode.api/pom.xml, line 6, column 11
> [WARNING] 'version' contains an expression but should be a 
> constant. @ net.sf.robocode:robocode:${robocode.version}, 
> /<>/pom.xml, line 6, column 11
> [WARNING] 
> [WARNING] Some problems were encountered while building the 
> effective model for net.sf.robocode:robocode.core:jar:1.9.2.6
> [WARNING] 'version' contains an expression but should be a 
> constant. @ net.sf.robocode:robocode.core:${robocode.version}, 
> /<>/robocode.core/pom.xml, line 6, column 11
> [WARNING] 
> [WARNING] Some problems were encountered while building the 
> effective model for net.sf.robocode:robocode.battle:jar:1.9.2.6
> [WARNING] 'version' contains an expression but should be a 
> constant. @ net.sf.robocode:robocode.battle:${robocode.version}, 
> /<>/robocode.battle/pom.xml, line 6, column 11
> [WARNING] 
> [WARNING] Some problems were encountered while building the 
> effective model for net.sf.robocode:robocode.host:jar:1.9.2.6
> [WARNING] 'version' contains an expression but should be a 
> constant. @ net.sf.robocode:robocode.host:${robocode.version}, 
> /<>/robocode.host/pom.xml, line 6, column 11
> [WARNING] 
> [WARNING] Some problems were encountered while building the 
> effective model for net.sf.robocode:robocode.ui:jar:1.9.2.6
> [WARNING] 'version' contains an expression but should be a 
> constant. @ net.sf.robocode:robocode.ui:${robocode.version}, 
> /<>/robocode.ui/pom.xml, line 6, column 11
> [WARNING] 
> [WARNING] Some problems were encountered while building the 
> effective model for net.sf.robocode:robocode.ui.editor:jar:1.9.2.6
> [WARNING] 'version' contains an expression but should be a 
> constant. @ net.sf.robocode:robocode.ui.editor:${robocode.version}, 
> /<>/robocode.ui.editor/pom.xml, line 6, column 11
> [WARNING] 
> [WARNING] Some problems were encountered while building the 
> effective model for net.sf.robocode:robocode.sound:jar:1.9.2.6
> [WARNING] 'ver

Bug#871348: Pending fixes for bugs in the robocode package

[pkg-java-maintainers]

tag 871348 + pending
thanks

Some bugs in the robocode package are closed in revision
c2f125d7105546b5d3dde983a3bc6721d48fc4c3 in branch 'master' by Markus
Koschany

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-java/robocode.git/commit/?id=c2f125d

Commit message:

Ignore robocode.distribution module to work around a FTBFS related to Maven

and the maven-assembly-plugin.

Closes: #871348

Processed: Pending fixes for bugs in the robocode package

[Debian Bug Tracking System]

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

> tag 871348 + pending
Bug #871348 [src:robocode] robocode: FTBFS: [ERROR] Failed to execute 
goal 
org.apache.maven.plugins:maven-dependency-plugin:2.8:unpack-dependencies
 (unpack-dependencies) on project robocode.tests.robots: 
Execution unpack-dependencies of goal 
org.apache.maven.plugins:maven-dependency-plugin:2.8:unpack-dependencies 
failed: A required class was missing while executing 
org.apache.maven.plugins:maven-dependency-plugin:2.8:unpack-dependencies: 
org/codehaus/plexus/util/MatchPatterns
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#873508: sparse test failures on ppc32le (and other not so common archs)

[Josh Triplett]

On Fri, Sep 01, 2017 at 09:57:09AM +0200, Uwe Kleine-König wrote:
> On Fri, Sep 01, 2017 at 12:02:12AM -0700, Josh Triplett wrote:
> > On Thu, Aug 31, 2017 at 08:47:55PM -0400, Christopher Li wrote:
> > > On Thu, Aug 31, 2017 at 4:55 PM, Uwe Kleine-König  Yes
> > > that works. So to address the Debian bug I can do:
> > > >
> > > >  - move sparse to /usr/lib
> > > >  - teach cgcc about the move of sparse
> > > >  - make /usr/bin/sparse call cgcc -no-compile "$@"
> > > 
> > > I don't like that. It means the user can't invoke sparse directly.
> > > 
> > > >
> > > > or is it easier to teach sparse about the architecture stuff?
> > > 
> > > First of all. It is not very trivial to teach sparse about the 
> > > architecture
> > > stuff. To my mind, we need to move all the cgcc logic into sparse.
> > 
> > Related to that: while it would mean we couldn't necessarily just rely
> > entirely on GCC's definitions for a target platform, I think in an ideal
> > world we could have a sparse binary that understood *all* target
> > platforms at once, such that you could ask Sparse on x86_64 to "compile"
> > as though targeting any arbitrary architecture. That would also have the
> > major advantage of making it easy to run the Sparse testsuite for
> > *every* target architecture without needing compilers for every such
> > architecture.
> 
> You'd need the target arch's system headers though.

Only for building userspace code, not for building standalone/kernel
code, or the Sparse testsuite.

- Josh Triplett

Bug#871172: marked as done (pulseview: FTBFS: devinst.h:54:38: error: dynamic exception specifications are deprecated in C++11 [-Werror=deprecated])

[Debian Bug Tracking System]

Your message dated Fri, 1 Sep 2017 23:11:37 +0100
with message-id <20170901221137.iz2cgeqbdnog2...@earth.li>
and subject line Fixed in experimental
has caused the Debian Bug report #871172,
regarding pulseview: FTBFS: devinst.h:54:38: error: dynamic exception 
specifications are deprecated in C++11 [-Werror=deprecated]
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.)


-- 
871172: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871172
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pulseview
Version: 0.2.0-1.2
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):
> /usr/bin/c++  -DENABLE_DECODE -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NO_DEBUG 
> -D__STDC_LIMIT_MACROS -isystem /usr/include/qt4 -isystem 
> /usr/include/qt4/QtGui -isystem /usr/include/qt4/QtCore 
> -I/<>/obj-x86_64-linux-gnu -I/<> 
> -I/usr/lib/x86_64-linux-gnu/libzip/include -I/usr/include/libusb-1.0 
> -I/usr/include/python3.5m -I/usr/include/x86_64-linux-gnu/python3.5m 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include  -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2   -Wall -Wextra 
> -Werror -o CMakeFiles/pulseview.dir/pv/dialogs/about.cpp.o -c 
> /<>/pv/dialogs/about.cpp
> In file included from /<>/pv/device/file.h:26:0,
>  from /<>/pv/device/inputfile.h:24,
>  from /<>/pv/device/inputfile.cpp:27:
> /<>/pv/device/devinst.h:54:38: error: dynamic exception 
> specifications are deprecated in C++11 [-Werror=deprecated]
>   virtual void use(SigSession *owner) throw(QString);
>   ^
> In file included from /<>/pv/device/file.h:26:0,
>  from /<>/pv/device/sessionfile.h:24,
>  from /<>/pv/device/sessionfile.cpp:21:
> /<>/pv/device/devinst.h:54:38: error: dynamic exception 
> specifications are deprecated in C++11 [-Werror=deprecated]
>   virtual void use(SigSession *owner) throw(QString);
>   ^
> In file included from /<>/pv/device/sessionfile.cpp:21:0:
> /<>/pv/device/sessionfile.h:36:38: error: dynamic exception 
> specifications are deprecated in C++11 [-Werror=deprecated]
>   virtual void use(SigSession *owner) throw(QString);
>   ^
> In file included from /<>/pv/device/inputfile.cpp:27:0:
> /<>/pv/device/inputfile.h:41:38: error: dynamic exception 
> specifications are deprecated in C++11 [-Werror=deprecated]
>   virtual void use(SigSession *owner) throw(QString);
>   ^
> /<>/pv/device/sessionfile.cpp:39:42: error: dynamic exception 
> specifications are deprecated in C++11 [-Werror=deprecated]
>  void SessionFile::use(SigSession *owner) throw(QString)
>   ^
> /<>/pv/device/inputfile.cpp:48:40: error: dynamic exception 
> specifications are deprecated in C++11 [-Werror=deprecated]
>  void InputFile::use(SigSession *owner) throw(QString)
> ^
> In file included from /<>/pv/device/device.h:24:0,
>  from /<>/pv/device/device.cpp:25:
> /<>/pv/device/devinst.h:54:38: error: dynamic exception 
> specifications are deprecated in C++11 [-Werror=deprecated]
>   virtual void use(SigSession *owner) throw(QString);
>   ^
> In file included from /<>/pv/device/device.cpp:25:0:
> /<>/pv/device/device.h:36:30: error: dynamic exception 
> specifications are deprecated in C++11 [-Werror=deprecated]
>   void use(SigSession *owner) throw(QString);
>   ^
> /<>/pv/device/device.cpp:44:37: error: dynamic exception 
> specifications are deprecated in C++11 [-Werror=deprecated]
>  void Device::use(SigSession *owner) throw(QString)
>  ^
> cc1plus: all warnings being treated as errors
> CMakeFiles/pulseview.dir/build.make:646: recipe for target 
> 'CMakeFiles/pulseview.dir/pv/device/sessionfile.cpp.o' failed
> make[3]: *** [CMakeFiles/pulseview.dir/pv/device/sessionfile.cpp.o] Error 1

The full build log is available from:
   http://aws-logs.debian.net/2017/08/05/pulseview_0.2.0-1.2_unstable.log

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

Bug#853687: marked as done (trinityrnaseq: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Fri, 01 Sep 2017 22:26:03 +
with message-id 
and subject line Bug#853687: fixed in trinityrnaseq 2.2.0+dfsg-3
has caused the Debian Bug report #853687,
regarding trinityrnaseq: 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.)


-- 
853687: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853687
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:trinityrnaseq
Version: 2.2.0+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/trinityrnaseq_2.2.0+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

[...]
make[4]: Leaving directory '/<>/trinityrnaseq-2.2.0+dfsg/Inchworm'
make[3]: Leaving directory '/<>/trinityrnaseq-2.2.0+dfsg/Inchworm'
make[2]: Leaving directory '/<>/trinityrnaseq-2.2.0+dfsg/Inchworm'
make -j64 install 
DESTDIR=/<>/trinityrnaseq-2.2.0\+dfsg/debian/tmp AM_UPDATE_INFO_DIR=no
make[2]: Entering directory 
'/<>/trinityrnaseq-2.2.0+dfsg/trinity-plugins/slclust'
X=`pwd`; \
for i in src; \
do echo '<<<' $i '>>>'; cd $X/$i; make install; done
<<< src >>>
make[3]: Entering directory 
'/<>/trinityrnaseq-2.2.0+dfsg/trinity-plugins/slclust/src'
mv slclust ../bin/
make[3]: Leaving directory 
'/<>/trinityrnaseq-2.2.0+dfsg/trinity-plugins/slclust/src'
make[2]: Leaving directory 
'/<>/trinityrnaseq-2.2.0+dfsg/trinity-plugins/slclust'
make[1]: Leaving directory '/<>/trinityrnaseq-2.2.0+dfsg'
   debian/rules override_dh_install-arch
make[1]: Entering directory '/<>/trinityrnaseq-2.2.0+dfsg'
dh_install -a
dh_install: Cannot find (any matches for) "Chrysalis/TranscriptomeFromVaryK" 
(tried in "." and "debian/tmp")
dh_install: trinityrnaseq missing files: Chrysalis/TranscriptomeFromVaryK
dh_install: Cannot find (any matches for) "Chrysalis/RunButterfly" (tried in 
"." and "debian/tmp")
dh_install: trinityrnaseq missing files: Chrysalis/RunButterfly
dh_install: Cannot find (any matches for) 
"Chrysalis/ReadsToTranscripts_MPI_chang" (tried in "." and "debian/tmp")
dh_install: trinityrnaseq missing files: Chrysalis/ReadsToTranscripts_MPI_chang
dh_install: Cannot find (any matches for) "Chrysalis/ReadsToTranscripts_MPI" 
(tried in "." and "debian/tmp")
dh_install: trinityrnaseq missing files: Chrysalis/ReadsToTranscripts_MPI
dh_install: Cannot find (any matches for) "Chrysalis/ReadsToTranscripts" (tried 
in "." and "debian/tmp")
dh_install: trinityrnaseq missing files: Chrysalis/ReadsToTranscripts
dh_install: Cannot find (any matches for) "Chrysalis/QuantifyGraph" (tried in 
"." and "debian/tmp")
dh_install: trinityrnaseq missing files: Chrysalis/QuantifyGraph
dh_install: Cannot find (any matches for) "Chrysalis/JoinTransByPairs" (tried 
in "." and "debian/tmp")
dh_install: trinityrnaseq missing files: Chrysalis/JoinTransByPairs
dh_install: Cannot find (any matches for) "Chrysalis/IsoformAugment" (tried in 
"." and "debian/tmp")
dh_install: trinityrnaseq missing files: Chrysalis/IsoformAugment
dh_install: Cannot find (any matches for) "Chrysalis/GraphFromFasta_MPI" (tried 
in "." and "debian/tmp")
dh_install: trinityrnaseq missing files: Chrysalis/GraphFromFasta_MPI
dh_install: Cannot find (any matches for) "Chrysalis/GraphFromFasta" (tried in 
"." and "debian/tmp")
dh_install: trinityrnaseq missing files: Chrysalis/GraphFromFasta
dh_install: Cannot find (any matches for) "Chrysalis/CreateIwormFastaBundle" 
(tried in "." and "debian/tmp")
dh_install: trinityrnaseq missing files: Chrysalis/CreateIwormFastaBundle
dh_install: Cannot

Bug#871647: marked as done (upx-ucl: uses convenience copy of LZMA library)

[Debian Bug Tracking System]

Your message dated Fri, 01 Sep 2017 22:26:14 +
with message-id 
and subject line Bug#871647: fixed in upx-ucl 3.94-3
has caused the Debian Bug report #871647,
regarding upx-ucl: uses convenience copy of LZMA library
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.)


-- 
871647: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871647
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: upx-ucl
Version: 3.93-1
Severity: serious
Justification: Policy §4.13
Control: found -1 3.94-2

Apparently upx-ucl reverted from using the system LZMA library
to its own. This, if not justified, is a Policy violation, for
various reasons, including maintainability and security.

Neither the changelog entry nor README.{Debian,source} contain
any justification, however.
--- End Message ---
--- Begin Message ---
Source: upx-ucl
Source-Version: 3.94-3

We believe that the bug you reported is fixed in the latest version of
upx-ucl, 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.
Robert Luberda  (supplier of updated upx-ucl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 01 Sep 2017 23:43:04 +0200
Source: upx-ucl
Binary: upx-ucl
Architecture: source amd64
Version: 3.94-3
Distribution: unstable
Urgency: medium
Maintainer: Robert Luberda 
Changed-By: Robert Luberda 
Description:
 upx-ucl- efficient live-compressor for executables
Closes: 871633 871647
Changes:
 upx-ucl (3.94-3) unstable; urgency=medium
 .
   * Note in README.source that upx uses upstream-provided LZMA library
 because lzma-dev package does not provide all the files necessary
 to build upx (closes: #871647).
   * Apply patch from Helmut Grohne to fix cross-compiling (closes: #871633):
 + let debhelper choose the correct CC;
 + fix build/host confusion;
 + ask dpkg for host endianness rather than maintaining a list.
   * Standards-Version: 4.1.0.
Checksums-Sha1:
 7a954d9cbba4316d84884b70f00f727f891df722 1866 upx-ucl_3.94-3.dsc
 d5574f9a82ec7ba1171c575a602858308613be51 14152 upx-ucl_3.94-3.debian.tar.xz
 862a6fe781eb8d91abda96abb49efb7902e171e4 1228788 
upx-ucl-dbgsym_3.94-3_amd64.deb
 ec3bf9f6803e5984b1964b60de7c4ffb32c7c3f0 5664 upx-ucl_3.94-3_amd64.buildinfo
 4cc936861f2289d6fe0259b672a232d02c0e9149 380928 upx-ucl_3.94-3_amd64.deb
Checksums-Sha256:
 9200806ebf485be9afeef99372c73050a9e1931b7db5041baba26755fc6c0c94 1866 
upx-ucl_3.94-3.dsc
 6ec43721a2789db6e1ac80b5dec5eeac83a31919eb9ddc0e3d8ccb7aee50faa6 14152 
upx-ucl_3.94-3.debian.tar.xz
 f6a6ad0f10fe39cd71fed21168f45021790085cf6953b9f63efe68b573633e79 1228788 
upx-ucl-dbgsym_3.94-3_amd64.deb
 fccc6ff3cd1f688c0afa7419b6fb920dbf4e255de441ace4ed1174e7e31f80fe 5664 
upx-ucl_3.94-3_amd64.buildinfo
 3555287f85edec76828dc5c9650ccb056973409607ff67d3ac5996e47f058ae1 380928 
upx-ucl_3.94-3_amd64.deb
Files:
 845f8201213385844fe11d180736a94e 1866 utils optional upx-ucl_3.94-3.dsc
 b3760178b320a7e9001c460a9da86d4d 14152 utils optional 
upx-ucl_3.94-3.debian.tar.xz
 8217bfbdba69e0273e6a6375e656a57a 1228788 debug extra 
upx-ucl-dbgsym_3.94-3_amd64.deb
 3fb8095638f5ca6174480221c691ef63 5664 utils optional 
upx-ucl_3.94-3_amd64.buildinfo
 4be2f84f97edc1df0eba66e5fc922675 380928 utils optional upx-ucl_3.94-3_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEENeh2+rTTcy6TtNI3Yx3nVTvor9QFAlmp1cIACgkQYx3nVTvo
r9SeSRAAlJkNyVupFddYWSCyjxzQSV4MDmXx+Sv7wlj+ga77TRxZmxz7VUupa7zg
jUacvi8J+Kpgw2qMFVm7FLEtQ30rksQciBiZyTaXkUAC7QXLkTEMacVT/rWDctFq
0D3jDJQW/bcCCIjOz2FUJVNKUS1Iwli9qGhK/tmhBUZsioJbGOIRgD2FctgKKD/5
LiZ+UpSKZLmn9WaXlbcgIIMRLnsQOKxQP2CoKpUaQ9GjhiyYSPyBpn81s8HdMKNz
DW0hjJH3otwQGMigCen4Riz981cEjvPcjdS0g905oHpRJAgRM0IEfhU46EM2usU9
1cp2urXPL+22SHssaEDmKtk9MHpQMZOvbYi4zcVasETvLkdYiw0rSBecqrlJ7f+t
djktRfhg32ZyQ9v1wtDsDveaY9Q6vLSVmKm1YaG/Qj7pZJKP3MWL94V3p6/XymiA
biqTSEG/s8ZYiOOd26Ue6Wa719/8CcftVjEsWayw9PwTauL8SV7bKAvMK9bI+UM0
I+8fo6ug/EfzieIL81/5ix9ISTsgBaHZNFnc+FBCUTp0WbjOP5b/3WhUyDiO1vSo
9jzjAs+PAtTiazSvSsE9LPnMYJ8eCSZVFh0EgWnTY69hvOlwuznx3zb3cPaiZ3mI
1Ajtym19mfRzi90x9NHntVFH04Yl6j3SSWyL802MqMZf8ewIY2U=
=08Ii
-END PGP SIGNATURE--

Bug#872544: dbusada: Please update for gnat-7

[Gianfranco Costamagna]

hello!

welcome back :)


dcut ssh-upload cancel -f dbusada_0.4.0-0.1_amd64.changes
Uploading commands file to ssh.upload.debian.org (incoming: 
/srv/upload.debian.org/UploadQueue/)
SCP is deprecated. Please consider upgrading to SFTP.
Uploading locutus-1504304589.commands to ssh-upload


please don't make the patches on the BTS useless/lost if possible :D

G.


Il Venerdì 1 Settembre 2017 16:30, Reto Buerki  ha scritto:



Hi,


On 09/01/2017 01:41 PM, Gianfranco Costamagna wrote:

> since we got no answer, and this is blocking the gnat transition (one of the 
> last blockers), I think

> we should bump severity and go ahead even without a maintainer answer (please 
> followup, there is still

> time to address the issue without having to NMU the package).

> 

> the following attached tarballs are part of the package uploaded in unstable.

> 

> I'm also attaching the debdiff and the filtered debdiff for "debian" 
> directory.

> 

> Changes since the patch queue above are:

> - one patch from Ubuntu, fixing the wl-asneeded linking order

> - std-version is 4.1.0

> - changelog updated.

> 

> Feel free to reschedule, defer, cancel if you think the packaging has issues.


Please cancel this upload, the updated dbusada package is almost ready

for upload. Sorry for the delay, but I was on holidays last week.


Regards,

- reto

Bug#784487: marked as done ([ktorrent] Qt4's WebKit removal)

[Debian Bug Tracking System]

Your message dated Fri, 01 Sep 2017 21:52:33 +
with message-id 
and subject line Bug#784487: fixed in ktorrent 5.1.0-1
has caused the Debian Bug report #784487,
regarding [ktorrent] Qt4's WebKit removal
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.)


-- 
784487: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784487
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ktorrent
Version: 4.3.1-2
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4webkit-removal

Dear Debian KDE Extras Team ,

As you might know we the Qt/KDE team are preparing to remove Qt4's WebKit
as announced in [announce].

[announce] 


Basically we are about to get the latest Qt4 point release and upstream is
migrating from WebKit to Bing in the Qt5 series, so we won't have much upstream
support for maintaining Qt4's WebKit.

In order to make this move, all packages directly or indirectly depending on
the Qt4's WebKit library have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5
port of your application
- if there are no activities regarding porting, investigate whether there are
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian
archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4. In
order to ease the transition time we have provided Wheezy backports for Qt5.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE
team at debian-qt-...@lists.debian.org

Ana,
on behalf of the Qt4 maintainers
--- End Message ---
--- Begin Message ---
Source: ktorrent
Source-Version: 5.1.0-1

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

Debian distribution maintenance software
pp.
Pino Toscano  (supplier of updated ktorrent package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 01 Sep 2017 23:22:02 +0200
Source: ktorrent
Binary: ktorrent ktorrent-data
Architecture: source
Version: 5.1.0-1
Distribution: experimental
Urgency: medium
Maintainer: Debian KDE Extras Team 
Changed-By: Pino Toscano 
Description:
 ktorrent   - BitTorrent client based on the KDE platform
 ktorrent-data - KTorrent data and other architecture independent files
Closes: 504271 763902 767218 778813 784487 821180 832547 837216 859250
Changes:
 ktorrent (5.1.0-1) experimental; urgency=medium
 .
   * Team upload.
   * New upstream release: (Closes: #821180)
 - the plugin system of Frameworks does not use sycoca anymore
   (Closes: #504271)
 - fixes a download order bug in queue (Closes: #763902)
 - the ipfilter plugin updates correctly from compressed files
   (Closes: #767218) (LP: #1207589)
 - switches from Qt4 (using QtWebKit) to Frameworks (Closes: #784487)
 - the switch to KF5 makes the scripting plugin work again, as krosspython
   was already switched to KF5 (Closes: #832547)
 - the search line edit is reset when closing it (Closes: #859250)
   * Update the build dependencies following the port to Frameworks:
 - remove libqt4-dev, kdelibs5-dev, libphonon-dev, kdepimlibs5-dev, and
   libqtwebkit-dev
 - add extra-cmake-modules, qtbase5-dev, qtscript5-dev, libphonon4qt5-dev,
   libphonon4qt5experimental-dev, libkf5archive-dev, libkf5completion-dev,
  

Processed: Re: preload fails due to missing preload.state file

[Debian Bug Tracking System]

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

> severity 861937 serious
Bug #861937 [preload] preload fails due to missing preload.state file
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#853495: marked as done (libktorrent: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Fri, 01 Sep 2017 21:00:10 +
with message-id 
and subject line Bug#853495: fixed in libktorrent 2.1-1
has caused the Debian Bug report #853495,
regarding libktorrent: 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.)


-- 
853495: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853495
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libktorrent
Version: 1.3.1-5
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/libktorrent_1.3.1-5_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

[...]
+#MISSING: 1.3.1-5# 
(optional=templinst)_ZNSt8_Rb_treeIjjSt9_IdentityIjESt4lessIjESaIjEE16_M_insert_uniqueERKj@Base
 1.3.0
+ 
_ZNSt8_Rb_treeIjjSt9_IdentityIjESt4lessIjESaIjEE16_M_insert_uniqueIRKjEESt4pairISt17_Rb_tree_iteratorIjEbEOT_@Base
 1.3.1-5
  
(optional=templinst)_ZNSt8_Rb_treeIjjSt9_IdentityIjESt4lessIjESaIjEE8_M_eraseEPSt13_Rb_tree_nodeIjE@Base
 1.3.0
  _ZTIN2bt10BValueNodeE@Base 1.3.0
  _ZTIN2bt10BufferPoolE@Base 1.3.0
@@ -2527,9 +2536,9 @@
  _ZTIN3utp9UTPServer7PrivateE@Base 1.3.0
  _ZTIN3utp9UTPServerE@Base 1.3.0
  _ZTIN3utp9UTPSocketE@Base 1.3.0
- (optional=internal)_ZTIN5boost16exception_detail10clone_baseE@Base 1.3.1
- 
(optional=internal)_ZTIN5boost16exception_detail19error_info_injectorISt12length_errorEE@Base
 1.3.1
- _ZTIN5boost9exceptionE@Base 1.3.0
+#MISSING: 1.3.1-5# 
(optional=internal)_ZTIN5boost16exception_detail10clone_baseE@Base 1.3.1
+#MISSING: 1.3.1-5# 
(optional=internal)_ZTIN5boost16exception_detail19error_info_injectorISt12length_errorEE@Base
 1.3.1
+#MISSING: 1.3.1-5# _ZTIN5boost9exceptionE@Base 1.3.0
  _ZTSN2bt10BValueNodeE@Base 1.3.0
  _ZTSN2bt10BufferPoolE@Base 1.3.0
  _ZTSN2bt10DownloaderE@Base 1.3.0
@@ -2675,9 +2684,9 @@
  _ZTSN3utp9UTPServer7PrivateE@Base 1.3.0
  _ZTSN3utp9UTPServerE@Base 1.3.0
  _ZTSN3utp9UTPSocketE@Base 1.3.0
- (optional=internal)_ZTSN5boost16exception_detail10clone_baseE@Base 1.3.1
- 
(optional=internal)_ZTSN5boost16exception_detail19error_info_injectorISt12length_errorEE@Base
 1.3.1
- _ZTSN5boost9exceptionE@Base 1.3.0
+#MISSING: 1.3.1-5# 
(optional=internal)_ZTSN5boost16exception_detail10clone_baseE@Base 1.3.1
+#MISSING: 1.3.1-5# 
(optional=internal)_ZTSN5boost16exception_detail19error_info_injectorISt12length_errorEE@Base
 1.3.1
+#MISSING: 1.3.1-5# _ZTSN5boost9exceptionE@Base 1.3.0
  _ZTVN2bt10BValueNodeE@Base 1.3.0
  _ZTVN2bt10BufferPoolE@Base 1.3.0
  _ZTVN2bt10DownloaderE@Base 1.3.0
@@ -2812,10 +2821,10 @@
  _ZTVN3utp9UTPServer7PrivateE@Base 1.3.0
  _ZTVN3utp9UTPServerE@Base 1.3.0
  _ZTVN3utp9UTPSocketE@Base 1.3.0
- (optional=internal)_ZTVN5boost16exception_detail10clone_baseE@Base 1.3.1
- 
(optional=internal)_ZTVN5boost16exception_detail19error_info_injectorISt12length_errorEE@Base
 1.3.1
- _ZTVN5boost9exceptionE@Base 1.3.0
- (c++|optional=internal)"non-virtual thunk to 
boost::exception_detail::error_info_injector::~error_info_injector()@Base"
 1.3.1
+#MISSING: 1.3.1-5# 
(optional=internal)_ZTVN5boost16exception_detail10clone_baseE@Base 1.3.1
+#MISSING: 1.3.1-5# 
(optional=internal)_ZTVN5boost16exception_detail19error_info_injectorISt12length_errorEE@Base
 1.3.1
+#MISSING: 1.3.1-5# _ZTVN5boost9exceptionE@Base 1.3.0
+#MISSING: 1.3.1-5# (c++|optional=internal)"non-virtual thunk to 
boost::exception_detail::error_info_injector::~error_info_injector()@Base"
 1.3.1
  (c++)"non-virtual thunk to 
bt::ChunkDownload::getStats(bt::ChunkDownloadInterface::Stats&)@Base" 1.3.0
  (c++)"non-virtual th

Bug#874009: rkt FTBFS: cannot find package "github.com/aws/aws-sdk-go/private/signer/v4"

[Adrian Bunk]

Source: rkt
Version: 1.21.0+dfsg-1
Severity: serious

Some recent change in unstable makes rkt FTBFS:

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

...
/usr/bin/make -C _build/src/github.com/coreos/rkt manpages 
GOPATH="/build/1st/rkt-1.21.0+dfsg"/_build/src2
make[2]: Entering directory 
'/build/1st/rkt-1.21.0+dfsg/_build/src/github.com/coreos/rkt'
mkdir -p dist/manpages/
ls 
/build/1st/rkt-1.21.0+dfsg/_build/src/github.com/coreos/rkt/build-rkt-1.21.0/gopath/src/github.com/coreos/rkt/rkt/*.go
 | \
grep -vE '_test.go|main.go|_gen.go|_stub.go' | \
GO15VENDOREXPERIMENT=1 GOARCH="amd64" CGO_ENABLED=1 CC="gcc" CXX="g++" 
GOPATH="/build/1st/rkt-1.21.0+dfsg/_build/src2" GOARCH=amd64 CC= xargs "go" run 
/build/1st/rkt-1.21.0+dfsg/_build/src/github.com/coreos/rkt/build-rkt-1.21.0/gopath/src/github.com/coreos/rkt/rkt/manpages_gen.go
../../../../src2/src/github.com/coreos/rkt/rkt/config/auth.go:25:2: cannot find 
package "github.com/aws/aws-sdk-go/private/signer/v4" in any of:

/build/1st/rkt-1.21.0+dfsg/_build/src2/src/github.com/coreos/rkt/vendor/github.com/aws/aws-sdk-go/private/signer/v4
 (vendor tree)
/usr/lib/go-1.8/src/github.com/aws/aws-sdk-go/private/signer/v4 (from 
$GOROOT)

/build/1st/rkt-1.21.0+dfsg/_build/src2/src/github.com/aws/aws-sdk-go/private/signer/v4
 (from $GOPATH)
rkt/rkt.mk:37: recipe for target 'manpages' failed
make[2]: *** [manpages] Error 123
make[2]: Leaving directory 
'/build/1st/rkt-1.21.0+dfsg/_build/src/github.com/coreos/rkt'
debian/rules:45: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2

Bug#873978: sendmail-base: Please check for /usr/share/sendmail/dynamic before sourcing it

[Sebastian Andrzej Siewior]

Package: sendmail-base
Version: 8.15.2-8
Severity: serious

I had sendmail installed. Then I removed it including sendmail-base. I
used "apt-get remove" instead of "purge" and this did not end well. The
log was quickly filled with this:

|Sep  1 21:28:02 debbuildd dhclient[3221]: DHCPREQUEST of 172.123.10.83 on eth0 
to 255.255.255.255 port 67
|Sep  1 21:28:02 debbuildd dhclient[3221]: DHCPOFFER of 172.123.10.83 from 
172.123.10.1
|Sep  1 21:28:03 debbuildd dhclient[3221]: DHCPACK of 172.123.10.83 from 
172.123.10.1
|Sep  1 21:28:03 debbuildd dhclient[3221]: DHCPDECLINE on eth0 to 
255.255.255.255 port 67
|Sep  1 21:28:03 debbuildd dhclient[3221]: DHCPDISCOVER on eth0 to 
255.255.255.255 port 67 interval 5
|Sep  1 21:28:03 debbuildd dhclient[3221]: DHCPREQUEST of 172.123.10.83 on eth0 
to 255.255.255.255 port 67
|Sep  1 21:28:03 debbuildd dhclient[3221]: DHCPOFFER of 172.123.10.83 from 
172.123.10.1
|Sep  1 21:28:03 debbuildd dhclient[3221]: DHCPACK of 172.123.10.83 from 
172.123.10.1
|Sep  1 21:28:03 debbuildd dhclient[3221]: DHCPDECLINE on eth0 to 
255.255.255.255 port 67
 
The reason for the DHCPCELINE was:
|/sbin/dhclient-script: 28: . :Can't open /usr/share/sendmail/dynamic

Which could have been caused by
|/etc/network/if-up.d/sendmail:. /usr/share/sendmail/dynamic;
|/etc/network/if-post-down.d/sendmail:. /usr/share/sendmail/dynamic;
|/etc/network/if-down.d/sendmail:. /usr/share/sendmail/dynamic;
|/etc/dhcp/dhclient-exit-hooks.d/sendmail:. /usr/share/sendmail/dynamic;
|/etc/ppp/ip-up.d/sendmail:. /usr/share/sendmail/dynamic;
|/etc/ppp/ip-down.d/sendmail:. /usr/share/sendmail/dynamic;
|/etc/resolvconf/update-libc.d/sendmail:. /usr/share/sendmail/dynamic;

but in my case it was /etc/dhcp/dhclient-exit-hooks.d/sendmail.

Please either remove those files on remove or test for
"/usr/share/sendmail/dynamic" before the script sources the file.

This was a headless box so it took while to notice…

Sebastian

Bug#784510: marked as done ([psi-plus] Qt4's WebKit removal)

[Debian Bug Tracking System]

Your message dated Fri, 01 Sep 2017 18:51:05 +
with message-id 
and subject line Bug#784510: fixed in psi-plus 1.2.40-1
has caused the Debian Bug report #784510,
regarding [psi-plus] Qt4's WebKit removal
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.)


-- 
784510: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784510
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: psi-plus
Version: 0.16.330-1
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4webkit-removal

Dear Boris Pek ,

As you might know we the Qt/KDE team are preparing to remove Qt4's WebKit
as announced in [announce].

[announce] 


Basically we are about to get the latest Qt4 point release and upstream is
migrating from WebKit to Bing in the Qt5 series, so we won't have much upstream
support for maintaining Qt4's WebKit.

In order to make this move, all packages directly or indirectly depending on
the Qt4's WebKit library have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5
port of your application
- if there are no activities regarding porting, investigate whether there are
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian
archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4. In
order to ease the transition time we have provided Wheezy backports for Qt5.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE
team at debian-qt-...@lists.debian.org

Ana,
on behalf of the Qt4 maintainers
--- End Message ---
--- Begin Message ---
Source: psi-plus
Source-Version: 1.2.40-1

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

Debian distribution maintenance software
pp.
Boris Pek  (supplier of updated psi-plus package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 01 Sep 2017 21:27:10 +0300
Source: psi-plus
Binary: psi-plus psi-plus-webkit psi-plus-common psi-plus-plugins 
psi-plus-skins psi-plus-sounds
Architecture: source
Version: 1.2.40-1
Distribution: unstable
Urgency: medium
Maintainer: Boris Pek 
Changed-By: Boris Pek 
Description:
 psi-plus   - Qt-based XMPP/Jabber client (basic version)
 psi-plus-common - common files for Psi+
 psi-plus-plugins - plugins for Psi+
 psi-plus-skins - skins for Psi+
 psi-plus-sounds - sound files for Psi+
 psi-plus-webkit - Qt-based XMPP/Jabber client (WebKit version)
Closes: 717350 759335 784510 789472 799967
Changes:
 psi-plus (1.2.40-1) unstable; urgency=medium
 .
   * New upstream release:
 - fixed crash in automatic color choosing algorithm for messages from users
   with nick "_" in group chats (Closes: #799967)
 - fixed re-establishing connection to XMPP server after changing of network
   settings or enabling laptop after sleep (LP: #906870)
 - fixed frequent crashes after enabling laptop after sleep (LP: #955415)
 - fixed rare crash in case when user tries to disconnect from server during
   ongoing connection (LP: #919726)
 - added few client icons into program sources (LP: #1304842)
   * Bump Standards-Version to 4.1.0 (was 3.9.5).
   * Common changes in the package:
 - change build system from qconf to cmake
 - use hunspell instead of aspell for spell check
 - build package with Q

Bug#868570: marked as done (python-klein: Fails to upgrade: "async def leaf(request): SyntaxError: invalid syntax")

[Debian Bug Tracking System]

Your message dated Fri, 01 Sep 2017 18:50:27 +
with message-id 
and subject line Bug#868570: fixed in klein 17.2.0-2
has caused the Debian Bug report #868570,
regarding python-klein: Fails to upgrade: "async def leaf(request): 
SyntaxError: invalid syntax"
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.)


-- 
868570: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868570
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-klein
Version: 17.2.0-1
Severity: serious

Upgrading python-klein from 16.12.0-1 to 17.2.0-1 fails for me as
follows:

[…]
Setting up python-klein (17.2.0-1) ...
  File "/usr/lib/python2.7/dist-packages/klein/test/py3_test_resource.py", line 
26
async def leaf(request):
^
SyntaxError: invalid syntax

dpkg: error processing package python-klein (--configure):
 subprocess installed post-installation script returned error exit status 101
[…]

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (600, 'testing'), (500, 'unstable-debug'), 
(500, 'buildd-unstable'), (110, 'experimental'), (1, 'experimental-debug'), (1, 
'buildd-experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.11.0-trunk-amd64 (SMP w/8 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages python-klein depends on:
ii  python   2.7.13-2
ii  python-incremental   16.10.1-3
ii  python-six   1.10.0-4
ii  python-twisted-core  16.6.0-2
ii  python-werkzeug  0.12.2+dfsg1-2

python-klein recommends no packages.

python-klein suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: klein
Source-Version: 17.2.0-2

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

Debian distribution maintenance software
pp.
Iain R. Learmonth  (supplier of updated klein package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 01 Sep 2017 14:43:52 +0100
Source: klein
Binary: python-klein python3-klein
Architecture: source all
Version: 17.2.0-2
Distribution: unstable
Urgency: medium
Maintainer: Iain R. Learmonth 
Changed-By: Iain R. Learmonth 
Description:
 python-klein - Python micro-framework for developing web services - Python 2.x
 python3-klein - Python micro-framework for developing web services - Python 3.x
Closes: 868570
Changes:
 klein (17.2.0-2) unstable; urgency=medium
 .
   * Removes Python 3 tests from Python 2 package (Closes: #868570)
Checksums-Sha1:
 dcd957ea0da20ec86248508d505762070041a2a5 1746 klein_17.2.0-2.dsc
 8dec265b838d386712cb7eb5e1f4404b026f8df8 2312 klein_17.2.0-2.debian.tar.xz
 ab8f68caf52b55433d2bf581423c0a47961652fd 7279 klein_17.2.0-2_amd64.buildinfo
 43e9b21fa82dd56ad1cc4681e89e44d5042d6c40 22144 python-klein_17.2.0-2_all.deb
 e5b59da15440ccc53ee0025f6037ac0c375f0bfd 21750 python3-klein_17.2.0-2_all.deb
Checksums-Sha256:
 8f5ad2e2f03fbdf1f8cb24ae79f5d7e82098b839090b6d92ec413c7d9d8ac435 1746 
klein_17.2.0-2.dsc
 99bfd0386642f16eaf505ff81ea5c7797f6568db68ecefae42a3145ad96a8cf1 2312 
klein_17.2.0-2.debian.tar.xz
 fdffe1234a829a7b662307b9882bfb680011bbb9a04e72df4821c5723e0f33ac 7279 
klein_17.2.0-2_amd64.buildinfo
 0980cd254573eb40ccf5c678e0e42bd7802b7713b56998339b3264f7b7e196a7 22144 
python-klein_17.2.0-2_all.deb
 67a1483e4dcc4da12cef8a9446fa18be6b19eec3e1bbe3fa416485f0b7b44534 21750 
python3-klein_17.2.0-2_all.deb
Files:
 7618b77cbc13b44e165008b37a28828f 1746 python optional klein_17.2.0-2.dsc
 41cb73ad70271a4b2fc70901e3e68471 2312 python optional 
klein_17.2.0-2.debian.tar.xz
 ff21eca2b6dc117809c4b471c76b2af6 7279 python optional 
klein_17.2.0-2_amd64.buildinfo
 d053d0280637e7afcd07a3146c30ad1b 22144 python optional 
python-klein_17.2.0-2_all.deb
 cbd9f762a832bc16142b17ae6e392075 21750 python optional 
python3-klein_17.2.0-2_all.deb

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEfGEElJRPyB2mSFaW0hedW4oe0BEFAlmpqQUACgkQ0hedW4oe
0BESSgf9HOiPqYmL84BI3O

Bug#869549: marked as done (libgpiv3-dev is not installable)

[Debian Bug Tracking System]

Your message dated Fri, 01 Sep 2017 18:50:42 +
with message-id 
and subject line Bug#869549: fixed in libgpiv 0.6.1-7
has caused the Debian Bug report #869549,
regarding libgpiv3-dev is not installable
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.)


-- 
869549: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869549
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgpiv3-dev
Version: 0.6.1-6
Severity: serious
Control: affects -1 src:pygpiv

libgpiv3-dev depends on both libgpiv-mpi3 and libgpiv3,
but they now conflict with each other.
--- End Message ---
--- Begin Message ---
Source: libgpiv
Source-Version: 0.6.1-7

We believe that the bug you reported is fixed in the latest version of
libgpiv, 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.
Steve Langasek  (supplier of updated libgpiv 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: Fri, 01 Sep 2017 18:18:20 +
Source: libgpiv
Binary: libgpiv3-common libgpiv3 libgpiv3-dev libgpiv3-doc libgpiv-mpi3
Architecture: source amd64 all
Version: 0.6.1-7
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Steve Langasek 
Description:
 libgpiv-mpi3 - library for Particle Image Velocimetry (PIV) - MPI version
 libgpiv3   - library for Particle Image Velocimetry (PIV)
 libgpiv3-common - library for Particle Image Velocimetry (PIV) - common files
 libgpiv3-dev - library for Particle Image Velocimetry (PIV) - development files
 libgpiv3-doc - library for Particle Image Velocimetry (PIV) - documentation
Closes: 869549
Changes:
 libgpiv (0.6.1-7) unstable; urgency=medium
 .
   * Fix libgpiv3-dev to depend on either of the conflicting implementations,
 not both.  Closes: #869549.
Checksums-Sha1:
 53be3b96d06d0b550652eeed5ec8bda8468f9877 2353 libgpiv_0.6.1-7.dsc
 d5a65919577c197c8d0c175957a6f8fed836663c 13848 libgpiv_0.6.1-7.debian.tar.xz
 4bd900c428d9a887e51f827d70dd69284be0a050 224478 
libgpiv-mpi3-dbgsym_0.6.1-7_amd64.deb
 da7a2968738b546cce7a1b561731b005e58112b1 85648 libgpiv-mpi3_0.6.1-7_amd64.deb
 0556740732aaa3a9b70fec71203fd5c7162c15f8 9102 libgpiv3-common_0.6.1-7_amd64.deb
 1a3e4ab0cb7ad43d72e4c186da6eea36fef40768 224468 
libgpiv3-dbgsym_0.6.1-7_amd64.deb
 005224218baccec5c807e76751369ab2e201c95f 125504 libgpiv3-dev_0.6.1-7_amd64.deb
 03135f428cad117b8f9d610317a1d28787dee90d 233248 libgpiv3-doc_0.6.1-7_all.deb
 032d6fd0646088f9ebe9c764a4e25cb7d5bb71bf 85662 libgpiv3_0.6.1-7_amd64.deb
 4c1bc0e4d697c3eca6327b567526aa4acb7595f3 9336 libgpiv_0.6.1-7_amd64.buildinfo
Checksums-Sha256:
 634e2eb821b08db46b53797a3fe878a6acdf740a38dd4bf986bfa5f8efe6f1d0 2353 
libgpiv_0.6.1-7.dsc
 e077d5aef7eb85d4ca3dc462c36616f9dd8be683454dadde6ae61a8d474c8cca 13848 
libgpiv_0.6.1-7.debian.tar.xz
 2b530b06a4a6ea3c61d145af418451f89135a2413765ccda0702fae46d66371d 224478 
libgpiv-mpi3-dbgsym_0.6.1-7_amd64.deb
 f71c391e91aca386781d312ffec9119e80bdcf322952c54435a5474e6c3484cd 85648 
libgpiv-mpi3_0.6.1-7_amd64.deb
 d258a411dbbfe377062df9c8af5a53f9c830a8e0869ad349fe34c41a83ddad68 9102 
libgpiv3-common_0.6.1-7_amd64.deb
 def01dce5fae53c370468606676b5137e17beaa6a6038276e6a777e6ffa10267 224468 
libgpiv3-dbgsym_0.6.1-7_amd64.deb
 36f463e2986d659e0b45782fd84ff1c5550ca7b4577edf5e607fe807fbc0dbd1 125504 
libgpiv3-dev_0.6.1-7_amd64.deb
 c6819336ff7d194f886f562847418a5aff7ccc3c482bcaaa2bb3d647b29df2b4 233248 
libgpiv3-doc_0.6.1-7_all.deb
 de2b62ede3703871d4d97ca090750d7b9fffe1caa4378a87c388b27feac20cbc 85662 
libgpiv3_0.6.1-7_amd64.deb
 489c82e8efa5c00355bc9ba4ad2754ececc0a3f3514cb7ec5c73d77b501f4aa2 9336 
libgpiv_0.6.1-7_amd64.buildinfo
Files:
 09e5e62e29016a827f571b0d8e5889c2 2353 science optional libgpiv_0.6.1-7.dsc
 0f34df1155d6a900ae071247d471c407 13848 science optional 
libgpiv_0.6.1-7.debian.tar.xz
 2284438084bfa904dc8776d0e8708b95 224478 debug extra 
libgpiv-mpi3-dbgsym_0.6.1-7_amd64.deb
 a3e8db7a589be4872dce6c87edcef29c 85648 libs optional 
libgpiv-mpi3_0.6.1-7_amd64.deb
 3db89762948e9f6e588cdf10e76723f1 9102 libs optional 
libgpiv3-common_0.6.1-7_amd64.deb
 5f3362d860b66b4679e3471e7acf6

Processed: Re: Bug#873962: sweethome3d: Random crash when opening/manipulating a file

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #873962 [sweethome3d] sweethome3d: Random crash when opening/manipulating a 
file
Severity set to 'important' from 'grave'

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

Bug#873962: sweethome3d: Random crash when opening/manipulating a file

[Markus Koschany]

Control: severity -1 important

Am 01.09.2017 um 17:19 schrieb Ludovic Lebègue:
> Package: sweethome3d
> Version: 5.4+dfsg-2
> Severity: grave
> Tags: upstream
> Justification: causes non-serious data loss
> 
> Hi,
> 
> On Debian testing sweethome3D now crashes randomly when opening or 
> manipulating
> a file

Hello,

thanks for reporting. We have to narrow down the issue first before we
assume severity grave which basically means that the program is
unusable. Your stacktrace also indicates that sweethome3d is only
affected by the bug and the real issue is in OpenJDK 8 or the underlying
graphics stack.

Could you provide more information how you trigger the crash please?
What file do you use? Please install openjdk-8-dbg so that we can get a
meaningful backtrace of the crash.

When I just search for the string
"Java_sun_java2d_opengl_OGLRenderQueue_flushBuffer" I can also find
numerous bug reports related to OpenJDK.

Markus




signature.asc
Description: OpenPGP digital signature

Bug#853687: trinityrnaseq: ftbfs with GCC-7

[Gert Wollny]

Am Freitag, den 01.09.2017, 15:16 +0200 schrieb Andreas Tille:
> Hi,
> 
> 
> I admit I have no idea why this and other header files are not found.

In  Chrysalis/Makefile it is only tested up until gcc version 6 to set
the include path, for 7 no additional include path is set. 

I've pushed the update gcc6 patch. 

Best, 
Gert 

Bug#867376: Processed: Re: Bug#867376 closed by Alexander GQ Gerasiov (Bug#867376: fixed in uncrustify 0.65+git20170831+dfsg1-1)

[Julien Cristau]

On 09/01/2017 12:57 AM, Alexander Gerasiov wrote:
> Hello Julien,
> 
> On Thu, 31 Aug 2017 22:15:04 +
> ow...@bugs.debian.org (Debian Bug Tracking System) wrote:
> 
>> This bug was not a request for packaging a new upstream version, so
>> this changelog entry isn't appropriate.
> Could you please explain your point?
> 
> There was several bugs in upstream code which leads to incorrect
> behavior on some architectures.
> We have fixed them in current upstream code, and current upstream
> version was uploaded into archive. This really fixes #867376, you can
> see this on https://buildd.debian.org/status/package.php?p=uncrustify
> 
What I mean is that when closing bugs in your changelog entry, it should
actually describe what fixes the bug.  So "New upstream release (closes:
#nnn)" implies that #nnn was about packaging a new upstream release.
"Fix vanilla flavor to not taste like chocolate (closes: #mmm)" implies
that #mmm is about something being wrong with the vanilla flavor of ice
cream.

See also
https://www.debian.org/doc/manuals/developers-reference/ch06.en.html#bpp-changelog-do

Cheers,
Julien

Bug#873962: sweethome3d: Random crash when opening/manipulating a file

[Ludovic Lebègue]

Package: sweethome3d
Version: 5.4+dfsg-2
Severity: grave
Tags: upstream
Justification: causes non-serious data loss

Hi,

On Debian testing sweethome3D now crashes randomly when opening or manipulating
a file

Launched from command line the crash reads this :

ludovic@leonardo ~ % /usr/lib/jvm/java-8-openjdk-amd64/bin/java
-Djava.library.path=/usr/lib/jni
-Dcom.eteks.sweethome3d.applicationFolders=/home/ludo/.eteks/sweethome3d:/usr/share/sweethome3d
-Dcom.eteks.sweethome3d.j3d.checkOffScreenSupport=false
-Dsun.java2d.opengl=true -classpath
/usr/share/java/j3dcore.jar:/usr/share/java/j3dutils.jar:/usr/share/java/vecmath.jar:/usr/share/java/batik.jar:/usr/share/java/sunflow.jar:/usr/share/java/itext.jar:/usr/share/java/janino.jar:/usr/share/java/freehep-
util.jar:/usr/share/java/freehep-io.jar:/usr/share/java/freehep-
xml.jar:/usr/share/java/freehep-graphics2d.jar:/usr/share/java/freehep-
graphicsio.jar:/usr/share/java/freehep-graphicsio-
svg.jar:/usr/share/sweethome3d/sweethome3d.jar:/usr/share/icedtea-web/netx.jar
com.eteks.sweethome3d.SweetHome3D -open
Java 3D: implicit antialiasing enabled
Gtk-Message: Failed to load module "canberra-gtk-module"
*** Error in `/usr/lib/jvm/java-8-openjdk-amd64/bin/java': double free or
corruption (fasttop): 0x7f40882d7df0 ***
=== Backtrace: =
/lib/x86_64-linux-gnu/libc.so.6(+0x70bfb)[0x7f411f11cbfb]
/lib/x86_64-linux-gnu/libc.so.6(+0x76fc6)[0x7f411f122fc6]
/lib/x86_64-linux-gnu/libc.so.6(+0x7780e)[0x7f411f12380e]
/usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so(+0x472b0c)[0x7f40ea07cb0c]
/usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so(+0x472d57)[0x7f40ea07cd57]
/usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so(+0x473073)[0x7f40ea07d073]
/usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so(+0x33031c)[0x7f40e9f3a31c]
/usr/lib/x86_64-linux-gnu/libGL.so.1(+0x49e13)[0x7f40f064ee13]
/usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so(+0x32f215)[0x7f40e9f39215]
/usr/lib/jvm/java-8-openjdk-
amd64/jre/lib/amd64/libawt_xawt.so(Java_sun_java2d_opengl_OGLRenderQueue_flushBuffer+0xd01)[0x7f40f1c636e1]
[0x7f4109a4fbaa]
=== Memory map: 
a2c0-af68 rw-p  00:00 0
af68-e0f0 ---p  00:00 0
e0f0-f420 rw-p  00:00 0
f420-1 ---p  00:00 0
1-1003e rw-p  00:00 0
1003e-14000 ---p  00:00 0
556b9ee24000-556b9ee25000 r-xp  08:31 787340
/usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java
556b9f024000-556b9f025000 r--p  08:31 787340
/usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java
556b9f025000-556b9f026000 rw-p 1000 08:31 787340
/usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java
556b9f44f000-556b9f47 rw-p  00:00 0  [heap]
7f3fe5dfe000-7f3fe61fe000 rw-s 129cb4000 00:06 1491
/dev/dri/card1
7f3fe61fe000-7f3fe65fe000 rw-s 1298b4000 00:06 1491
/dev/dri/card1
7f3fe65fe000-7f3fe69fe000 rw-s 1294b4000 00:06 1491
/dev/dri/card1
7f3fe69fe000-7f3fe6dfe000 rw-s 1290b4000 00:06 1491
/dev/dri/card1
7f3fe6dfe000-7f3fe71fe000 rw-s 128cb4000 00:06 1491
/dev/dri/card1
7f3fe71fe000-7f3fe75fe000 rw-s 1288b4000 00:06 1491
/dev/dri/card1
7f3fe75fe000-7f3fe79fe000 rw-s 1284b4000 00:06 1491
/dev/dri/card1
7f3fe79fe000-7f3fe7dfe000 rw-s 1280b4000 00:06 1491
/dev/dri/card1
7f3fe7dfe000-7f3fe81fe000 rw-s 127cb4000 00:06 1491
/dev/dri/card1
7f3fe81fe000-7f3fe85fe000 rw-s 1278b4000 00:06 1491
/dev/dri/card1
7f3fe85fe000-7f3fe89fe000 rw-s 1274b4000 00:06 1491
/dev/dri/card1
7f3fe89fe000-7f3fe8dfe000 rw-s 1270b4000 00:06 1491
/dev/dri/card1
7f3fe8dfe000-7f3fe91fe000 rw-s 126cb4000 00:06 1491
/dev/dri/card1
7f3fe91fe000-7f3fe95fe000 rw-s 1268b4000 00:06 1491
/dev/dri/card1
7f3fe95fe000-7f3fe99fe000 rw-s 1264b4000 00:06 1491
/dev/dri/card1
7f3fe99fe000-7f3fe9dfe000 rw-s 1260b4000 00:06 1491
/dev/dri/card1
7f3fe9dfe000-7f3fea1fe000 rw-s 125cb4000 00:06 1491
/dev/dri/card1
7f3fea1fe000-7f3fea5fe000 rw-s 1258b4000 00:06 1491
/dev/dri/card1
7f3fea5fe000-7f3fea9fe000 rw-s 1254b4000 00:06 1491
/dev/dri/card1
7f3fea9fe000-7f3feadfe000 rw-s 1250b4000 00:06 1491
/dev/dri/card1
7f3feadfe000-7f3feb1fe000 rw-s 124cb4000 00:06 1491
/dev/dri/card1
7f3feb1fe000-7f3feb5fe000 rw-s 1248b4000 00:06 1491
/dev/dri/card1
7f3feb5fe000-7f3feb9fe000 rw-s 1244b4000 00:06 1491
/dev/dri/card1
7f3feb9fe000-7f3febdfe000 rw-s 1192ac000 00:06 1491
/dev/dri/card1
7f3febdfe000-7f3febe01000 ---p  00:00 0
7f3febe01000-7f3febeff000 rw-p  00:00 0
7f3febeff000-7f3febf02000 ---p  00:00 0
7f3febf02000-7f3fec00 rw-p  00:00 0
7f3fec00-7f3fec023000 rw-p  00:00 0
7f3fec023000-7f3ff000 ---p  00:00 0
7f3ff000-7f3ff400 rw-s  00:05 524292
/SYSV (deleted)
7f3ff400-7f3ff4023000 rw-p  00:00 0
7f3ff4023000-7f3ff800 ---p  00:00 0
7f3ff800-7f3ff8021000 rw-p  00:00 0
7f3ff8021000-7f3ffc00 ---p  00:00 0
7f3ffc00-7f3ffc021000 rw-p  00:00 0
7f3ffc021000-7f40 ---p  00:00 0
7f40-7f4000

Bug#853672: svxlink: diff for NMU version 15.11-2.1

[Felix Lechner]

Adrian,

Thank you for doing this!

Felix


On Fri, Sep 1, 2017 at 6:20 AM, Adrian Bunk  wrote:

> Control: tags 853672 + pending
>
> Dear maintainer,
>
> I've prepared an NMU for svxlink (versioned as 15.11-2.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
>
>

Bug#872595: closed by Norbert Preining (Bug#872595: fixed in calibre 3.7.0+dfsg-1)

[duck]

Control: -1 reopen


Quack,

Upstream ported the patch which fixes this one-off security problem, 
very well. Unfortunately this bug report is not about it, even if it was 
an example of how harmful having a copy of the code is.


So it seems you don't get me right and I would encourage you to read the 
Debian Policy section 4.13 about this problem. Calibre has no good 
reason to borrow code from a maintained and packaged library. This 
library is lightweight and does not drag any other dependency, so 
upstream should not be shy about it.


I'm adding the security team so they don't miss this problem and how 
this package (all versions) is affected by the libmspack security issues 
(part of).


Regards.
\_o<

--
Marc Dequènes

Bug#872544: dbusada: Please update for gnat-7

[Reto Buerki]

Hi,

On 09/01/2017 01:41 PM, Gianfranco Costamagna wrote:
> since we got no answer, and this is blocking the gnat transition (one of the 
> last blockers), I think
> we should bump severity and go ahead even without a maintainer answer (please 
> followup, there is still
> time to address the issue without having to NMU the package).
> 
> the following attached tarballs are part of the package uploaded in unstable.
> 
> I'm also attaching the debdiff and the filtered debdiff for "debian" 
> directory.
> 
> Changes since the patch queue above are:
> - one patch from Ubuntu, fixing the wl-asneeded linking order
> - std-version is 4.1.0
> - changelog updated.
> 
> Feel free to reschedule, defer, cancel if you think the packaging has issues.

Please cancel this upload, the updated dbusada package is almost ready
for upload. Sorry for the delay, but I was on holidays last week.

Regards,
- reto



signature.asc
Description: OpenPGP digital signature

Processed: Re: hope this triggers the buster migration for torbrowser-launcher

[Debian Bug Tracking System]

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

> fixed 868280 torbrowser-launcher/0.2.7-3
Bug #868280 [torbrowser-launcher] torbrowser-launcher: after update 
torbrowser-launcher doesn't work, the binary is not in its place.
Marked as fixed in versions torbrowser-launcher/0.2.7-3.
> fixed 864733 torbrowser-launcher/0.2.7-3
Bug #864733 [torbrowser-launcher] Error: "Download error: Download Error: 404 
Not Found", Debian stable
Marked as fixed in versions torbrowser-launcher/0.2.7-3.
>
End of message, stopping processing here.

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

Processed: Re: hope this triggers the buster migration for torbrowser-launcher

[Debian Bug Tracking System]

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

> notfound 868280 torbrowser-launcher/0.2.7-3
Bug #868280 [torbrowser-launcher] torbrowser-launcher: after update 
torbrowser-launcher doesn't work, the binary is not in its place.
Ignoring request to alter found versions of bug #868280 to the same values 
previously set
> notfound 864733 torbrowser-launcher/0.2.7-3
Bug #864733 [torbrowser-launcher] Error: "Download error: Download Error: 404 
Not Found", Debian stable
Ignoring request to alter found versions of bug #864733 to the same values 
previously set
>
End of message, stopping processing here.

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

Bug#873878: [gluster-packaging] Fwd: Bug#873878: glusterfs-client: mount.glusterfs needs bash as /bin/sh

[Michael Lundkvist]

On 09/01/2017 01:25 PM, Patrick Matthäi wrote:


Am 01.09.2017 um 11:40 schrieb Niels de Vos:

On Fri, Sep 01, 2017 at 09:36:16AM +0200, Patrick Matthäi wrote:

Hi,

how should it be fixed for glusterfs now? Better shell code without
bashishm or do you want /bin/bash as shebang?

Do you have a preference? I do not know how much work is it is to
rewrite the mount.glusterfs script to remove all the Bashisms. At least
in the Debian builds you may want to patch it to /bin/bash for the time
being.


I would prefer a patch, so that it works without bash. Luckily the bug
reporter just wrote a patch :)
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873878#10



To be very clear, I've only tested this by manually modifying 
/sbin/mount.glusterfs in the same way. I've not even tried building it.


Also, this code seems related to the new sub-directory mounts that came 
in 3.12 and I'm not using that.


But at least it takes the package from unusable to fully functional for 
me. :)


/Micke

Bug#853554: marked as done (mongo-cxx-driver-legacy: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Fri, 01 Sep 2017 13:52:37 +
with message-id 
and subject line Bug#853554: fixed in mongo-cxx-driver-legacy 1.1.2-6
has caused the Debian Bug report #853554,
regarding mongo-cxx-driver-legacy: 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.)


-- 
853554: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853554
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:mongo-cxx-driver-legacy
Version: 1.1.2-5
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/mongo-cxx-driver-legacy_1.1.2-5_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

[...]
[   OK ] TimeFormatting.DateAsISO8601UTCStream (0 ms)
[ RUN  ] TimeFormatting.DateAsISO8601LocalStream
[   OK ] TimeFormatting.DateAsISO8601LocalStream (0 ms)
[ RUN  ] TimeFormatting.DateAsCtimeStream
[   OK ] TimeFormatting.DateAsCtimeStream (0 ms)
[--] 7 tests from TimeFormatting (0 ms total)

[--] 4 tests from TimeParsing
[ RUN  ] TimeParsing.DateAsISO8601UTC
src/mongo/util/time_support_test.cpp:140: Failure
  Expected: swull.getValue()
  Which is: -211
To be equal to: 34401906789ULL
  Which is: 34401906789
[  FAILED  ] TimeParsing.DateAsISO8601UTC (0 ms)
[ RUN  ] TimeParsing.DateAsISO8601Local
src/mongo/util/time_support_test.cpp:189: Failure
  Expected: swull.getValue()
  Which is: -18660211
To be equal to: 34401906789ULL
  Which is: 34401906789
[  FAILED  ] TimeParsing.DateAsISO8601Local (0 ms)
[ RUN  ] TimeParsing.InvalidDates
[   OK ] TimeParsing.InvalidDates (0 ms)
[ RUN  ] TimeParsing.LeapYears
src/mongo/util/time_support_test.cpp:380: Failure
  Expected: swull.getValue()
  Which is: -1000
To be equal to: 6816960ULL
  Which is: 6816960
[  FAILED  ] TimeParsing.LeapYears (0 ms)
[--] 4 tests from TimeParsing (0 ms total)

[--] Global test environment tear-down
[==] 11 tests from 2 test cases ran. (0 ms total)
[  PASSED  ] 8 tests.
[  FAILED  ] 3 tests, listed below:
[  FAILED  ] TimeParsing.DateAsISO8601UTC
[  FAILED  ] TimeParsing.DateAsISO8601Local
[  FAILED  ] TimeParsing.LeapYears

 3 FAILED TESTS
scons: *** [run-util/time_support_test] Error 1
scons: building terminated because of errors.
debian/rules:40: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 2
make[1]: Leaving directory '/<>'
debian/rules:9: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
--- End Message ---
--- Begin Message ---
Source: mongo-cxx-driver-legacy
Source-Version: 1.1.2-6

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

Debian distribution maintenance software
pp.
Apollon Oikonomopoulos  (supplier of updated 
mongo-cxx-driver-legacy 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
Da

Processed: tagging 873928

[Debian Bug Tracking System]

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

> tags 873928 + sid buster
Bug #873928 {Done: Wookey } [src:caveconverter] 
caveconverter: please Build-Depend on rename
Ignoring request to alter tags of bug #873928 to the same tags previously set
> thanks
Stopping processing here.

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

Processed: hope this triggers the buster migration for torbrowser-launcher

[Debian Bug Tracking System]

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

> notfound 868280 0.2.7-3
Bug #868280 [torbrowser-launcher] torbrowser-launcher: after update 
torbrowser-launcher doesn't work, the binary is not in its place.
Ignoring request to alter found versions of bug #868280 to the same values 
previously set
> notfound 864733 0.2.7-3
Bug #864733 [torbrowser-launcher] Error: "Download error: Download Error: 404 
Not Found", Debian stable
Ignoring request to alter found versions of bug #864733 to the same values 
previously set
> tag 861744 -sid -buster
Bug #861744 [torbrowser-launcher] torbrowser-launcher: Should not be part of 
Stretch
Removed tag(s) sid.
Bug #861744 [torbrowser-launcher] torbrowser-launcher: Should not be part of 
Stretch
Removed tag(s) buster.
>
End of message, stopping processing here.

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

Bug#853368: dbf2mysql: diff for NMU version 1.14a-5.1

[Adrian Bunk]

Control: tags 853368 + pending

Dear maintainer,

I've prepared an NMU for dbf2mysql (versioned as 1.14a-5.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 dbf2mysql-1.14a/debian/changelog dbf2mysql-1.14a/debian/changelog
--- dbf2mysql-1.14a/debian/changelog	2016-12-13 00:30:47.0 +0200
+++ dbf2mysql-1.14a/debian/changelog	2017-09-01 16:20:46.0 +0300
@@ -1,3 +1,10 @@
+dbf2mysql (1.14a-5.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS with gcc 7. (Closes: #853368)
+
+ -- Adrian Bunk   Fri, 01 Sep 2017 16:20:46 +0300
+
 dbf2mysql (1.14a-5) unstable; urgency=medium
 
   * Moved to new libmysql-dev b-d.
diff -Nru dbf2mysql-1.14a/debian/patches/35_gcc-7.patch dbf2mysql-1.14a/debian/patches/35_gcc-7.patch
--- dbf2mysql-1.14a/debian/patches/35_gcc-7.patch	1970-01-01 02:00:00.0 +0200
+++ dbf2mysql-1.14a/debian/patches/35_gcc-7.patch	2017-08-17 20:28:30.0 +0300
@@ -0,0 +1,55 @@
+Description: Make strtoupper/strtolower static inline
+ This seems to have been intended,
+ and the static makes gcc 7 happy.
+Author: Adrian Bunk 
+Bug-Debian: https://bugs.debian.org/853368
+
+--- dbf2mysql-1.14a.orig/dbf2mysql.c
 dbf2mysql-1.14a/dbf2mysql.c
+@@ -41,21 +41,19 @@ char	*convert = NULL;
+ 
+ void do_onlyfields (char *flist, dbhead *dbh);
+ void do_substitute(char *subarg, dbhead *dbh);
+-inline void strtoupper(char *string);
+-inline void strtolower(char *string);
+ void do_create(MYSQL *, char*, dbhead*);
+ void do_inserts(MYSQL *, char*, dbhead*);
+ int check_table(MYSQL *, char*);
+ void usage(void);
+ 
+-inline void strtoupper(char *string) {
++static inline void strtoupper(char *string) {
+ 	while(*string != '\0') {
+ 		*string = toupper(*string);
+ 		string++;
+ 	}
+ }
+ 
+-inline void strtolower(char *string) {
++static inline void strtolower(char *string) {
+ 	while(*string != '\0') {
+ 		*string = tolower(*string);
+ 		string++;
+--- dbf2mysql-1.14a.orig/mysql2dbf.c
 dbf2mysql-1.14a/mysql2dbf.c
+@@ -21,18 +21,16 @@ char	*table = NULL;
+ char*pass = NULL;
+ char*user = NULL;
+ 
+-inline void strtoupper(char *string);
+-inline void strtolower(char *string);
+ void usage(void);
+ 
+-inline void strtoupper(char *string) {
++static inline void strtoupper(char *string) {
+ while(*string != '\0') {
+ *string = toupper(*string);
+ 		string++;
+ }
+ }
+ 
+-inline void strtolower(char *string) {
++static inline void strtolower(char *string) {
+ while(*string != '\0') {
+ *string = tolower(*string);
+ 		string++;
diff -Nru dbf2mysql-1.14a/debian/patches/series dbf2mysql-1.14a/debian/patches/series
--- dbf2mysql-1.14a/debian/patches/series	2016-03-06 16:32:58.0 +0200
+++ dbf2mysql-1.14a/debian/patches/series	2017-09-01 16:20:46.0 +0300
@@ -4,3 +4,4 @@
 20-u-char.patch
 25-mysql-real-connect.patch
 30-makefile
+35_gcc-7.patch

Processed: dbf2mysql: diff for NMU version 1.14a-5.1

[Debian Bug Tracking System]

Processing control commands:

> tags 853368 + pending
Bug #853368 [src:dbf2mysql] dbf2mysql: ftbfs with GCC-7
Added tag(s) pending.

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

Bug#811036: marked as done (wireshark-qt: aborts immediately)

[Debian Bug Tracking System]

Your message dated Fri, 1 Sep 2017 16:21:47 +0300
with message-id <20170901132147.6lw3n6226ry23...@mitya57.me>
and subject line Re: Bug#860839: vlc fails to start due to missing QT platform 
plugin xcb
has caused the Debian Bug report #809989,
regarding wireshark-qt: aborts immediately
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.)


-- 
809989: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809989
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wireshark-qt
Version: 2.0.0+g9a73b82-1
Severity: grave

Dear Maintainer,

I tried starting wireshark from the comman-line and it immediately
aborted.  Like so:

  $ wireshark
  This application failed to start because it could not find or load the Qt 
platform plugin "xcb".

  Available platform plugins are: linuxfb, minimal, minimalegl, offscreen.

  Reinstalling the application may fix this problem.
  Aborted

I had expected it to start like it used to do.  I don't recall when I
last used it.  I keep my system up-to-date with unattended-upgrades and
my logs indicate wireshark-qt was installed on 2015-12-01 with the
upgrade of wireshark from 1.12.8+g5b6e543-2 to 2.0.0+g9a73b82-1.  I do
remember being surprised at the changed look-and-feel of wireshark, so I
am pretty sure that I have run wireshark-qt successfully in the past.

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

Kernel: Linux 4.3.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages wireshark-qt depends on:
ii  libc62.21-6
ii  libgcc1  1:5.3.1-5
ii  libglib2.0-0 2.46.2-3
ii  libnl-3-200  3.2.26-1
ii  libnl-genl-3-200 3.2.26-1
ii  libnl-route-3-2003.2.26-1
ii  libpcap0.8   1.7.4-2
ii  libqt5core5a 5.5.1+dfsg-12
ii  libqt5gui5   5.5.1+dfsg-12
ii  libqt5printsupport5  5.5.1+dfsg-12
ii  libqt5widgets5   5.5.1+dfsg-12
ii  libsbc1  1.3-1
ii  libstdc++6   5.3.1-5
ii  libwireshark62.0.0+g9a73b82-1
ii  libwiretap5  2.0.0+g9a73b82-1
ii  libwsutil6   2.0.0+g9a73b82-1
ii  wireshark-common 2.0.0+g9a73b82-1
ii  xdg-utils1.1.1-1
ii  zlib1g   1:1.2.8.dfsg-2+b1

wireshark-qt recommends no packages.

wireshark-qt suggests no packages.

-- no debconf information

-- 
Olaf Meeuwissen, LPIC-2   FLOSS Engineer -- EPSON AVASYS CORPORATION
   Free Software Foundation Associate Member since 2004-01-27
Support Free Software  https://my.fsf.org/donate
Support the Free Software Foundation https://my.fsf.org/join
--- End Message ---
--- Begin Message ---
On Thu, Apr 20, 2017 at 10:18:42PM +0200, Sebastian Ramacher wrote:
> Control: reassign -1 src:qtbase-opensource-src 5.5.1+dfsg-13
> Control: forcemerge -1 809989

This had an unwanted effect of reopening bug 809989. Closing it again,
as the problem has been resolved long time ago.

--
Dmitry Shachnev


signature.asc
Description: PGP signature
--- End Message ---

Bug#809176: marked as done (Merge platforms plugins into libqt5gui5)

[Debian Bug Tracking System]

Your message dated Fri, 1 Sep 2017 16:21:47 +0300
with message-id <20170901132147.6lw3n6226ry23...@mitya57.me>
and subject line Re: Bug#860839: vlc fails to start due to missing QT platform 
plugin xcb
has caused the Debian Bug report #809989,
regarding Merge platforms plugins into libqt5gui5
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.)


-- 
809989: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809989
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: vlc
Version: 2.2.1-5+b1
Severity: normal

Hi! Sebastian Ramacher told me that vlc is a X11-only app. In other words,
even if it's built against Qt5 it depends upon X11 itself (Qt5 apps can run
without X11).

If that's the case then it should depend upon libqt5xcbqpa5, which is the
pluging used by Qt5 to use X11.

This is the case of a non-automatic dependency (ie, not catched by our
Debian tools) like QML stuff.

Kinds regards, Lisandro.


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

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

Versions of packages vlc depends on:
ii  fonts-freefont-ttf  20120503-4
ii  libaa1  1.4p5-44
ii  libavcodec-ffmpeg-extra56   7:2.8.4-1
ii  libavutil-ffmpeg54  7:2.8.4-1
ii  libc6   2.21-4
ii  libcaca00.99.beta19-2+b1
ii  libcairo2   1.14.4-1
ii  libegl1-mesa [libegl1-x11]  11.0.7-1
ii  libfreerdp-client1.11.1.0~git20140921.1.440916e+dfsg1-5+b1
ii  libfreerdp-core1.1  1.1.0~git20140921.1.440916e+dfsg1-5+b1
ii  libfreerdp-gdi1.1   1.1.0~git20140921.1.440916e+dfsg1-5+b1
ii  libfreetype62.6.1-0.1
ii  libfribidi0 0.19.7-1
ii  libgcc1 1:5.3.1-4
ii  libgl1-mesa-glx [libgl1]11.0.7-1
ii  libgles1-mesa [libgles1]11.0.7-1
ii  libgles2-mesa [libgles2]11.0.7-1
ii  libglib2.0-02.46.2-1
ii  libpulse0   7.1-2
ii  libqt5core5a5.5.1+dfsg-9
ii  libqt5gui5  5.5.1+dfsg-9
ii  libqt5widgets5  5.5.1+dfsg-9
ii  libqt5x11extras55.5.1-3
ii  librsvg2-2  2.40.12-1
ii  libsdl-image1.2 1.2.12-5+b5
ii  libsdl1.2debian 1.2.15-12
ii  libstdc++6  5.3.1-4
ii  libva-drm1  1.6.2-1
ii  libva-x11-1 1.6.2-1
ii  libva1  1.6.2-1
ii  libvlccore8 2.2.1-5+b1
ii  libvncclient1   0.9.10+dfsg-3
ii  libx11-62:1.6.3-1
ii  libxcb-composite0   1.11.1-1
ii  libxcb-keysyms1 0.4.0-1
ii  libxcb-randr0   1.11.1-1
ii  libxcb-shm0 1.11.1-1
ii  libxcb-xv0  1.11.1-1
ii  libxcb1 1.11.1-1
ii  libxext62:1.3.3-1
ii  libxi6  2:1.7.5-1
ii  libxinerama12:1.1.3-1+b1
ii  libxpm4 1:3.5.11-1+b1
ii  vlc-nox 2.2.1-5+b1
ii  zlib1g  1:1.2.8.dfsg-2+b1

Versions of packages vlc recommends:
ii  vlc-plugin-notify  2.2.1-5+b1
ii  vlc-plugin-samba   2.2.1-5+b1
ii  xdg-utils  1.1.1-1

vlc suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
On Thu, Apr 20, 2017 at 10:18:42PM +0200, Sebastian Ramacher wrote:
> Control: reassign -1 src:qtbase-opensource-src 5.5.1+dfsg-13
> Control: forcemerge -1 809989

This had an unwanted effect of reopening bug 809989. Closing it again,
as the problem has been resolved long time ago.

--
Dmitry Shachnev


signature.asc
Description: PGP signature
--- End Message ---

Bug#809989: marked as done (vlc crashes at startup because it could not find or load the Qt platform plugin "xcb")

[Debian Bug Tracking System]

Your message dated Fri, 1 Sep 2017 16:21:47 +0300
with message-id <20170901132147.6lw3n6226ry23...@mitya57.me>
and subject line Re: Bug#860839: vlc fails to start due to missing QT platform 
plugin xcb
has caused the Debian Bug report #809989,
regarding vlc crashes at startup because it could not find or load the Qt 
platform plugin "xcb"
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.)


-- 
809989: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809989
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: vlc
Version: 2.2.1-5+b1
Severity: important

Dear Maintainer,

I upgraded vlc to latest version in Debian sid. When I try to start it, I get
the message:

>>> vlc
VLC media player 2.2.1 Terry Pratchett (Weatherwax) (revision 
2.2.1-0-ga425c42)
[0131c388] core libvlc: Running vlc with the default interface. 
Use 'cvlc' to use vlc without interface.
This application failed to start because it could not find or load the 
Qt platform plugin "xcb".

Available platform plugins are: linuxfb, minimal, minimalegl, offscreen.

Reinstalling the application may fix this problem.

I tried to 'aptitude reinstall vlc', but the above output stayed the same.
Below you'll find the output of 'vlc -vvv':


>>> vlc -vvv
VLC media player 2.2.1 Terry Pratchett (Weatherwax) (revision 2.2.1-0-ga425c42)
[01036388] core libvlc debug: VLC media player - 2.2.1 Terry Pratchett 
(Weatherwax)
[01036388] core libvlc debug: Copyright © 1996-2015 the VideoLAN team
[01036388] core libvlc debug: revision 2.2.1-0-ga425c42
[01036388] core libvlc debug: configured with ./configure  
'--includedir=${prefix}/include' '--mandir=${prefix}/share/man' 
'--infodir=${prefix}/share/info' '--localstatedir=/var' 
'--libdir=${prefix}/lib/x86_64-linux-gnu' 
'--libexecdir=${prefix}/lib/x86_64-linux-gnu' '--disable-dependency-tracking' 
'--build=x86_64-linux-gnu' 'CPPFLAGS=-D_FORTIFY_SOURCE=2' 'LDFLAGS=-Wl,-z,relro 
-Wl,--as-needed' '--config-cache' '--disable-maintainer-mode' 
'--disable-silent-rules' '--disable-update-check' '--enable-fast-install' 
'--prefix=/usr' '--docdir=/usr/share/doc/vlc-nox' '--libdir=/usr/lib' 
'--sysconfdir=/etc' '--with-binary-version=5+b1' '--enable-a52' '--enable-aa' 
'--enable-bluray' '--enable-bonjour' '--enable-caca' '--enable-chromaprint' 
'--enable-dbus' '--enable-dca' '--enable-directfb' '--enable-dvbpsi' 
'--enable-dvdnav' '--enable-faad' '--enable-flac' '--enable-fluidsynth' 
'--enable-freerdp' '--enable-freetype' '--enable-fribidi' '--enable-gles1' 
'--enable-gles2' '--enable-gnutls' '--enable-jack' '--enable-kate' 
'--enable-libass' '--enable-libmpeg2' '--enable-libxml2' '--enable-lirc' 
'--enable-live555' '--enable-mad' '--enable-mkv' '--enable-mod' '--enable-mpc' 
'--enable-mtp' '--enable-mux_ogg' '--enable-ncurses' '--enable-notify' 
'--enable-ogg' '--enable-opus' '--enable-pulse' '--enable-qt' 
'--enable-realrtsp' '--enable-samplerate' '--enable-schroedinger' 
'--enable-sdl' '--enable-sdl-image' '--enable-sftp' '--enable-shine' 
'--enable-shout' '--enable-skins2' '--enable-speex' '--enable-svg' 
'--enable-svgdec' '--enable-taglib' '--enable-theora' '--enable-twolame' 
'--enable-upnp' '--enable-vcdx' '--enable-vdpau' '--enable-vnc' 
'--enable-vorbis' '--enable-x264' '--enable-x265' '--enable-zvbi' 
'--with-kde-solid=/usr/share/kde4/apps/solid/actions/' '--disable-decklink' 
'--disable-dxva2' '--disable-fdkaac' '--disable-gnomevfs' '--disable-goom' 
'--disable-libtar' '--disable-mfx' '--disable-opencv' '--disable-projectm' 
'--disable-sndio' '--disable-telx' '--disable-vpx' '--disable-vsxu' 
'--disable-wasapi' '--enable-alsa' '--enable-atmo' '--enable-dc1394' 
'--enable-dv1394' '--enable-linsys' '--enable-omxil' '--enable-udev' 
'--enable-v4l2' '--enable-libva' '--enable-vcd' '--enable-smbclient' 
'--disable-oss' '--enable-crystalhd' '--enable-mmx' '--enable-sse' 
'--disable-neon' '--disable-altivec' 'CFLAGS=-g -O2 -fstack-protector-strong 
-Wformat -Werror=format-security' 'CXXFLAGS=-g -O2 -fstack-protector-strong 
-Wformat -Werror=format-security' 'build_alias=x86_64-linux-gnu' 'OBJCFLAGS=-g 
-O2 -fstack-protector-strong -Wformat -Werror=format-security'
[01036388] core libvlc debug: searching plug-in modules
[01036388] core libvlc debug: loading plugins cache file 
/usr/lib/vlc/plugins/plugins.dat
[01036388] core libvlc warning: This doesn't look like a valid plugins 
cache
[01036388] core libvlc debug: recursively browsing 
`/usr/lib/vlc/plugins'
[01036388] core libv

Bug#864439: Disable bowtie for mips64el

[Andreas Tille]

Hi,

do we have any better idea than disabling bowtie for mips64el architecture?

Kind regards

   Andreas.

-- 
http://fam-tille.de

Bug#810253: marked as done (vlc requires libqt5xcbqpa5 but does not declare dependency on it)

[Debian Bug Tracking System]

Your message dated Fri, 1 Sep 2017 16:21:47 +0300
with message-id <20170901132147.6lw3n6226ry23...@mitya57.me>
and subject line Re: Bug#860839: vlc fails to start due to missing QT platform 
plugin xcb
has caused the Debian Bug report #809989,
regarding vlc requires libqt5xcbqpa5 but does not declare dependency on it
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.)


-- 
809989: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809989
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: vlc
Version: 2.2.1-5+b1
Severity: normal

Dear Maintainer,

 When starting vlc on my debian testing system, I received the
following note:

(Error message start)

VLC media player 2.2.1 Terry Pratchett (Weatherwax) (revision 2.2.1-0-
ga425c42)
[01bd4158] core libvlc: Running vlc with the default interface.
Use 'cvlc' to use vlc without interface.
This application failed to start because it could not find or load the
Qt platform plugin "xcb".

Available platform plugins are: linuxfb, minimal, minimalegl,
offscreen.

Reinstalling the application may fix this problem.

(End of error Message)


I tried to apt-get install --reinstall vlc or even apt-get purge vlc
but the problem persisted. The error code after the crash is 137.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

 I installed package libqt5xcbqpa5. vlc does not seem to declare a
dependency on this package, however. Please consider adding a
dependency on this package.

   * What was the outcome of this action?

 Problem solved.


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

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

Versions of packages vlc depends on:
ii  fonts-freefont-ttf  20120503-4
ii  libaa1  1.4p5-44
ii  libavcodec-ffmpeg56 7:2.8.4-1+b1
ii  libavutil-ffmpeg54  7:2.8.4-1+b1
ii  libc6   2.21-6
ii  libcaca00.99.beta19-2+b1
ii  libcairo2   1.14.4-1
ii  libegl1-mesa [libegl1-x11]  11.0.8-1
ii  libfreerdp-client1.11.1.0~git20140921.1.440916e+dfsg1-5+b1
ii  libfreerdp-core1.1  1.1.0~git20140921.1.440916e+dfsg1-5+b1
ii  libfreerdp-gdi1.1   1.1.0~git20140921.1.440916e+dfsg1-5+b1
ii  libfreetype62.6.1-0.1
ii  libfribidi0 0.19.7-1
ii  libgcc1 1:5.3.1-5
ii  libgl1-mesa-glx [libgl1]11.0.8-1
ii  libgles1-mesa [libgles1]11.0.8-1
ii  libgles2-mesa [libgles2]11.0.8-1
ii  libglib2.0-02.46.2-3
ii  libpulse0   7.1-2
ii  libqt5core5a5.5.1+dfsg-10
ii  libqt5gui5  5.5.1+dfsg-10
ii  libqt5widgets5  5.5.1+dfsg-10
ii  libqt5x11extras55.5.1-3
ii  librsvg2-2  2.40.11-2
ii  libsdl-image1.2 1.2.12-5+b5
ii  libsdl1.2debian 1.2.15-12
ii  libstdc++6  5.3.1-5
ii  libva-drm1  1.6.2-1
ii  libva-x11-1 1.6.2-1
ii  libva1  1.6.2-1
ii  libvlccore8 2.2.1-5+b1
ii  libvncclient1   0.9.10+dfsg-3
ii  libx11-62:1.6.3-1
ii  libxcb-composite0   1.10-3+b1
ii  libxcb-keysyms1 0.4.0-1
ii  libxcb-randr0   1.10-3+b1
ii  libxcb-shm0 1.10-3+b1
ii  libxcb-xv0  1.10-3+b1
ii  libxcb1 1.10-3+b1
ii  libxext62:1.3.3-1
ii  libxi6  2:1.7.5-1
ii  libxinerama12:1.1.3-1+b1
ii  libxpm4 1:3.5.11-1+b1
ii  vlc-nox 2.2.1-5+b1
ii  zlib1g  1:1.2.8.dfsg-2+b1

Versions of packages vlc recommends:
ii  vlc-plugin-notify  2.2.1-5+b1
ii  vlc-plugin-samba   2.2.1-5+b1
ii  xdg-utils  1.1.1-1

vlc suggests no packages.

Versions of packages vlc-nox depends on:
ii  liba52-0.7.4   0.7.4-18
ii  libasound2 1.0.29-1
ii  libass50.13.1-1
ii  libavahi-client3   0.6.32~rc+dfsg-1
ii  libavahi-common3   0.6.32~rc+dfsg-1
ii  libavc1394-0   0.5.4-2
ii  libavcodec-ffmpeg567:2.8.4-1+b1
ii  libavformat-ffmpeg56   7:2.8.4-1+b1
ii  libavutil-ffmpeg54 7:2.8.4-1+b1
ii  libbasicusageenvironment0  2014.01.13-1
ii  libbluray1   

Processed: svxlink: diff for NMU version 15.11-2.1

[Debian Bug Tracking System]

Processing control commands:

> tags 853672 + pending
Bug #853672 [src:svxlink] svxlink: ftbfs with GCC-7
Added tag(s) pending.

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

Bug#853672: svxlink: diff for NMU version 15.11-2.1

[Adrian Bunk]

Control: tags 853672 + pending

Dear maintainer,

I've prepared an NMU for svxlink (versioned as 15.11-2.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 svxlink-15.11/debian/changelog svxlink-15.11/debian/changelog
--- svxlink-15.11/debian/changelog	2016-12-10 02:45:49.0 +0200
+++ svxlink-15.11/debian/changelog	2017-09-01 16:15:22.0 +0300
@@ -1,3 +1,10 @@
+svxlink (15.11-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add upstream patch to fix FTBFS with gcc 7. (Closes: #853672)
+
+ -- Adrian Bunk   Fri, 01 Sep 2017 16:15:22 +0300
+
 svxlink (15.11-2) unstable; urgency=medium
 
   * Bugfix release
diff -Nru svxlink-15.11/debian/patches/0001-Fix-compilation-problem-in-Async-AudioDeviceAlsa.patch svxlink-15.11/debian/patches/0001-Fix-compilation-problem-in-Async-AudioDeviceAlsa.patch
--- svxlink-15.11/debian/patches/0001-Fix-compilation-problem-in-Async-AudioDeviceAlsa.patch	1970-01-01 02:00:00.0 +0200
+++ svxlink-15.11/debian/patches/0001-Fix-compilation-problem-in-Async-AudioDeviceAlsa.patch	2017-08-17 18:05:06.0 +0300
@@ -0,0 +1,26 @@
+From 611cc5cc134f710f94fc8987375259bd8af34604 Mon Sep 17 00:00:00 2001
+From: Tobias Blomberg 
+Date: Mon, 19 Jun 2017 22:04:20 +0200
+Subject: Fix compilation problem in Async::AudioDeviceAlsa
+
+- On newer compilers the compilation would fail on ambiguous call to abs
+---
+ src/async/audio/AsyncAudioDeviceAlsa.cpp | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/src/async/audio/AsyncAudioDeviceAlsa.cpp b/src/async/audio/AsyncAudioDeviceAlsa.cpp
+index 17d255e8..15d760d5 100644
+--- a/src/async/audio/AsyncAudioDeviceAlsa.cpp
 b/src/async/audio/AsyncAudioDeviceAlsa.cpp
+@@ -548,7 +548,7 @@ bool AudioDeviceAlsa::initParams(snd_pcm_t *pcm_handle)
+ return false;
+   }
+ 
+-  if (::abs(real_rate - sample_rate) > 100)
++  if (::abs(static_cast(real_rate) - sample_rate) > 100)
+   {
+ cerr << "*** ERROR: The sample rate could not be set to "
+  << sample_rate << "Hz for ALSA device \"" << dev_name << "\". "
+-- 
+2.11.0
+
diff -Nru svxlink-15.11/debian/patches/series svxlink-15.11/debian/patches/series
--- svxlink-15.11/debian/patches/series	2016-01-13 20:50:43.0 +0200
+++ svxlink-15.11/debian/patches/series	2017-08-17 18:06:19.0 +0300
@@ -10,3 +10,4 @@
 enable-static-libs.patch
 use-default-compile-flags.patch
 enable-verbose-output.patch
+0001-Fix-compilation-problem-in-Async-AudioDeviceAlsa.patch

Bug#853687: trinityrnaseq: ftbfs with GCC-7

[Andreas Tille]

Hi,

I tried to track down this gcc-7 error.  I think the issue is somewhere
here:

...
g++  -W -Wall -Wno-unused -Wno-deprecated -ansi -pedantic -Wno-long-long 
-fno-nonansi-builtins -Wctor-dtor-privacy -Wsign-promo -Woverloaded-virtual 
-Wendif-labels  -O3  -ggdb3 -   DMAKE_DATE='"Fri Aug  5 19:21:49 UTC 
2016"' -DMAKE_OS_RELEASE='"4.5.0-2-amd64"' -DMAKE_RELEASE='"3.0"' 
-DNEW_MAKEFILE -imacros system/BigFileDefines.h -pthread  -ftemplate-depth-30 
-fno-   strict-aliasing -mieee-fp   -fopenmp  -Wdate-time 
-D_FORTIFY_SOURCE=2  -c ./analysis/DNAVector.cc -o obj/analysis/DNAVector.o
./aligns/KmerAlignCore.cc:6:10: fatal error: aligns/KmerAlignCore.h: No such 
file or directory
 #include "aligns/KmerAlignCore.h"
  ^~~~
compilation terminated.
Makefile:473: recipe for target 'aligns/KmerAlignCore.o' failed
make[2]: *** [aligns/KmerAlignCore.o] Error 1
...

I admit I have no idea why this and other header files are not found.

Could somebody have a look please?

Kind regards

 Andreas.

-- 
http://fam-tille.de

Processed: Re: Bug#873921: python3.5_3.5.4-3 breaks borgbackup: undefined symbol: PyFPE_jbuf

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 src:python3.5
Bug #873921 [borgbackup] python3.5_3.5.4-3 breaks borgbackup: undefined symbol: 
PyFPE_jbuf
Bug reassigned from package 'borgbackup' to 'src:python3.5'.
No longer marked as found in versions borgbackup/1.0.11-3.
Ignoring request to alter fixed versions of bug #873921 to the same values 
previously set
> found -1 3.5.4-3
Bug #873921 [src:python3.5] python3.5_3.5.4-3 breaks borgbackup: undefined 
symbol: PyFPE_jbuf
Marked as found in versions python3.5/3.5.4-3.
> notfound -1 3.5.4-2
Bug #873921 [src:python3.5] python3.5_3.5.4-3 breaks borgbackup: undefined 
symbol: PyFPE_jbuf
Ignoring request to alter found versions of bug #873921 to the same values 
previously set

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

Bug#873921: python3.5_3.5.4-3 breaks borgbackup: undefined symbol: PyFPE_jbuf

[Gianfranco Costamagna]

control: reassign -1 src:python3.5
control: found -1 3.5.4-3
control: notfound -1 3.5.4-2

control: affects -1 src:borgbackup


Hello, I don't know why this should be a borgbackup issue.

If they changed ABI, they have to track the transition


G.

Il Venerdì 1 Settembre 2017 10:51, Sven Hartge  ha scritto:



Package: borgbackup

Version: 1.0.11-3

Severity: grave


Hi!


I am reporting this bug against borgbackup, because I am not sure if the

bug is in python3.5 or borgbackup just needs to be binNMUd. Please

reassign as you see fit.


The upload of python3.5 (3.5.4-3) disables the fpectl extension and

breaks borgbackup:


$ borg

Traceback (most recent call last):

  File "/usr/bin/borg", line 11, in 

load_entry_point('borgbackup==1.0.11', 'console_scripts', 'borg')()

  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 564, in 
load_entry_point

return get_distribution(dist).load_entry_point(group, name)

  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2662, 
in load_entry_point

return ep.load()

  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2316, 
in load

return self.resolve()

  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2322, 
in resolve

module = __import__(self.module_name, fromlist=['__name__'], level=0)

  File "/usr/lib/python3/dist-packages/borg/archiver.py", line 22, in 

from .helpers import Error, location_validator, archivename_validator, 
format_line, format_time, format_file_size, \

  File "/usr/lib/python3/dist-packages/borg/helpers.py", line 35, in 

from . import crypto

ImportError: 
/usr/lib/python3/dist-packages/borg/crypto.cpython-35m-i386-linux-gnu.so: 
undefined symbol: PyFPE_jbuf


Grüße,

Sven.


-- System Information:

Debian Release: buster/sid

  APT prefers unstable-debug

  APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 
'unstable'), (500, 'testing'), (200, 'experimental'), (1, 'experimental-debug')

Architecture: i386 (x86_64)

Foreign Architectures: amd64


Kernel: Linux 4.9.0-3-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 borgbackup depends on:

ii  fuse   2.9.7-1

ii  libacl12.2.52-3+b1

ii  libc6  2.24-17

ii  liblz4-1   0.0~r131-2+b1

pn  libssl1.1  

ii  python33.5.3-3

ii  python3-llfuse 1.2+dfsg-1+b1

ii  python3-msgpack0.4.8-1+b1

ii  python3-pkg-resources  36.2.7-2


borgbackup recommends no packages.


Versions of packages borgbackup suggests:

pn  borgbackup-doc  


-- debconf-show failed

Bug#873713: marked as done (node-foreground-child FTBFS: test failures)

[Debian Bug Tracking System]

Your message dated Fri, 01 Sep 2017 12:49:42 +
with message-id 
and subject line Bug#873713: fixed in node-foreground-child 1.5.6-3
has caused the Debian Bug report #873713,
regarding node-foreground-child 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.)


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

Source: node-foreground-child
Version: 1.5.6-1
Severity: serious

Hi Maintainer

Node-foreground-child FTBFS in unstable:

https://tests.reproducible-builds.org/debian/history/node-foreground-child.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-foreground-child.html

...
test/immortal-child.js

  1) should match pattern provided

  38 passing (11s)
  1 failing

  1) test/immortal-child.js should match pattern provided:
 Error: should match pattern provided
  at ChildProcess. (test/immortal-child.js:37:7)

debian/rules:12: recipe for target 'override_dh_auto_test' failed

Regards
Graham
--- End Message ---
--- Begin Message ---
Source: node-foreground-child
Source-Version: 1.5.6-3

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

Debian distribution maintenance software
pp.
Bastien Roucariès  (supplier of updated node-foreground-child 
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: Fri, 01 Sep 2017 14:19:37 +0200
Source: node-foreground-child
Binary: node-foreground-child
Architecture: source
Version: 1.5.6-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Bastien Roucariès 
Description:
 node-foreground-child - helper running a child process as a foreground process
Closes: 873713
Changes:
 node-foreground-child (1.5.6-3) unstable; urgency=medium
 .
   * Increase delay in test hopefully fixing FTBFS: "test failures",
 thanks to Graham Inggs (Closes: #873713).
Checksums-Sha1:
 552c8409dee8cbcf7db7c2ba1de2683a7b52bcc6 2234 node-foreground-child_1.5.6-3.dsc
 2a475e3492b34e81e1c4361b1f8548d07b715268 3388 
node-foreground-child_1.5.6-3.debian.tar.xz
 2b84de9a16a6b497c93732e409545946d4b1a270 6416 
node-foreground-child_1.5.6-3_source.buildinfo
Checksums-Sha256:
 2ac9a939dbb72b1747efdc572350334d48717d9d82658f9d3e61490833b9ca57 2234 
node-foreground-child_1.5.6-3.dsc
 9e69fc977740547574dca688b21c4ab2a10f54e28c81fbef807348aac765f05c 3388 
node-foreground-child_1.5.6-3.debian.tar.xz
 21177377523503504eaffe55eb64b4f7fb0eea0d4f1290c37bf6a7f92d480eb2 6416 
node-foreground-child_1.5.6-3_source.buildinfo
Files:
 5849642915195b43b25b49d03a65eb64 2234 web optional 
node-foreground-child_1.5.6-3.dsc
 cf1ac042fc48006dab81b729a6dab83f 3388 web optional 
node-foreground-child_1.5.6-3.debian.tar.xz
 047f9793b688275e660597893ff3bb5f 6416 web optional 
node-foreground-child_1.5.6-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEXQGHuUCiRbrXsPVqADoaLapBCF8FAlmpUbYACgkQADoaLapB
CF+zpA//UY5U/vht9nlYQE1gL2qNB3cibT4YNZeBSbgSjF8gPuz7Zns30Sf0GpAY
xp98Iie8YSzC3Vz55QiQAbNSV+kCJ9ebNJd2SbiihQDqXzc1I5AZXTAquo2+Zgb7
pM2WVG6N1k6K9yX4KGTtUes2ykwpucApbX98yolwKBXFh9s+hDa4bNpTVdnre/Y6
fWPC8Oang7X6gwZmvbJgCXQ7mD+js/22XEi6xgsRkITZ87C2Hcg2sojN69Kgkniw
I5kbR4yzYSvTqOSQ7Mi16DTaqrZFlkX0+qqT2/0zedh0TaVNqeoRZo9xFl9gowcD
3NbvLDFm37svFXdomelOS8kqVLp915ayLA2BO7lOSIr/nXeyrdPN+pIAe55Uf61M
okhnz7Uy2rF8ht0qVpyobrg4zmUT6hrjpKceuBoCYhO2X2DNYW7vhjRvEjAXi/la
1NX81U2fEVGGtxZL+nApl+CIodH2SvhEAiVvmchmMsauJ9Ba6p3khgU02sZyR5bR
7y5Q1uGHSoCSI8elav6kbk9MhqgMxnFwnCYvhKpIeYEjgX85RF4kTsWs1dpFbrmi
+qwA/imx6PtBhQW/B5/NZvMHS7VvkdU39M1Rge2PiTUkGltRL4SRFYi+eWRfQ+en
DA0yxWUzBnTMpkkkEeBdKTkq36WuT9mxSc/8EWmAxI3G40WVsZM=
=uRzh
-END PGP SIGNATURE End Message ---

Bug#873928: marked as done (caveconverter: please Build-Depend on rename)

[Debian Bug Tracking System]

Your message dated Fri, 1 Sep 2017 12:32:45 +0100
with message-id <20170901113245.gk19...@mail.wookware.org>
and subject line Re: Bug#873928: caveconverter: please Build-Depend on rename
has caused the Debian Bug report #873928,
regarding caveconverter: please Build-Depend on rename
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.)


-- 
873928: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873928
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: caveconverter
Version: 0~20170114-1
Severity: serious
Justification: FTBFS with impending change
User: debian-p...@lists.debian.org
Usertags: rename-deprecation

As announced last year[1] and as advised by deprecation messages,
rename(1) will be removed from the perl package after the stretch
release, and this is now imminent.

Your package FTBFS with perl from experimental as a result. Please
add a Build-Depends: rename to your package, and all will be well
again:

#change to unix command name in examples files
sed --in-place -e 's/java -jar CaveConverter.jar/caveconverter/' 
debian//caveconverter/usr/share/doc/caveconverter/examples/*.bat
rename 's/\.bat$//' 
debian//caveconverter/usr/share/doc/caveconverter/examples/*.bat
/bin/sh: 1: rename: not found

Let me know if you would prefer an NMU to get this trivial change made.

Cheers,
Dominic.

[1] 
--- End Message ---
--- Begin Message ---
On 2017-09-01 10:53 +0100, Dominic Hargreaves wrote:
> As announced last year[1] and as advised by deprecation messages,
> rename(1) will be removed from the perl package after the stretch
> release, and this is now imminent.
> 
> Your package FTBFS with perl from experimental as a result. Please
> add a Build-Depends: rename to your package, and all will be well
> again:

OK, a fixed -2 just uploaded.

Wookey
-- 
Principal hats:  Linaro, Debian, Wookware, ARM
http://wookware.org/


signature.asc
Description: Digital signature
--- End Message ---

Bug#873508: sparse test failures on ppc32le (and other not so common archs)

[Christopher Li]

On Fri, Sep 1, 2017 at 3:02 AM, Josh Triplett  wrote:
>> First of all. It is not very trivial to teach sparse about the architecture
>> stuff. To my mind, we need to move all the cgcc logic into sparse.
>
> Related to that: while it would mean we couldn't necessarily just rely
> entirely on GCC's definitions for a target platform, I think in an ideal
> world we could have a sparse binary that understood *all* target
> platforms at once, such that you could ask Sparse on x86_64 to "compile"

Yes, that is what I want to have. It is list as one of the project in
project idea document as well. I have  a related question. How do we
test the different architecture handling without actually run sparse
on different platform? I am thinking maybe using gcc cross platform
compiler and compare some macro against the sparse one.

> as though targeting any arbitrary architecture. That would also have the
> major advantage of making it easy to run the Sparse testsuite for
> *every* target architecture without needing compilers for every such
> architecture.

Another way to fix the test suite for now would be let testsuite
specify using cgcc instead of sparse directly, for the test source
that needs it. That will buy us some time. Fixing sparse properly
in the long term obvious would be better.

Chris

Bug#873508: sparse test failures on ppc32le (and other not so common archs)

[Christopher Li]

On Fri, Sep 1, 2017 at 3:46 AM, Uwe Kleine-König  wrote:
\>
> Nearly right. I'm responsible for the sparse Debian package and the
> problem at hand is https://bugs.debian.org/873508. This bug report has
> "Severity: serious" wihch might eventually result in the removal of
> sparse from the Debian archive.
>
> @anarcat: Given that cgcc seems to work, would you agree to apply the
> following patch to horst:
>
> diff --git a/Makefile b/Makefile
> index 4f924fa..d563652 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -110,7 +110,7 @@ $(NAME): $(OBJS)
>  $(OBJS): .buildflags
>
>  check:
> -   sparse $(CFLAGS) *.[ch]
> +   cgcc -no-compile $(CFLAGS) *.[ch]

You patch definitely works.
I think it is the better way to fix it.
Sparse "selfcheck" target was doing the same thing.
It is using "cgcc -no-compile" already.

I suggest in your patch you can do some thing
similar to "selfcheck" target:

CHECKER = cgcc -no-compile

 $(CHECKER) $(CFLAGS) *.[ch]

Later when we update sparse to handle architecture
properly. We can just invoke make with "CHECKER="
to test.


> and downgrade the bug to "important"? That would be a compromise that
> buys us a bit of time.

Agree.

>
> This only solves a part of the problem because the bug report is about
> sparse itself, not it's llvm part.

I agree with that too.

Chris

Bug#872595: marked as done (calibre: please use system libmspack instead of embedded copy)

[Debian Bug Tracking System]

Your message dated Fri, 01 Sep 2017 11:49:59 +
with message-id 
and subject line Bug#872595: fixed in calibre 3.7.0+dfsg-1
has caused the Debian Bug report #872595,
regarding calibre: please use system libmspack instead of embedded copy
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.)


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

Source: calibre
Version: 3.4.0+dfsg-1
Severity: grave
Tags: security upstream
X-Debbugs-CC: t...@security.debian.org


Quack,

Sorry for the bad news, but Calibre embed a very old version of 
libmspack to build a plugin: /usr/lib/calibre/calibre/plugins/lzx.so


Unfortunately, this library had a few security issues over time, and 
recently:

  https://security-tracker.debian.org/tracker/source-package/libmspack

So this means Calibre is affected (all versions is Debian) by these two 
security bugs and probably other older ones. The proper solution would 
be to use the libmspack library which has been fixed with all the fixes 
backported to stable and oldstable.


It is defined in 'setup/extensions.json' but I have no idea how to make 
it use the system library so I have no patch to suggest.


Btw it seems 'src/calibre/utils/' contains a lot of borrowed code which 
might lead to security problems too, so I would suggest to have a look 
and work things out with upstream to at least have build flags to use 
system libraries when available.


Regards.

--
Marc Dequènes
--- End Message ---
--- Begin Message ---
Source: calibre
Source-Version: 3.7.0+dfsg-1

We believe that the bug you reported is fixed in the latest version of
calibre, 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.
Norbert Preining  (supplier of updated calibre package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 30 Aug 2017 20:40:23 +0900
Source: calibre
Binary: calibre calibre-bin
Architecture: source amd64 all
Version: 3.7.0+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Miriam Ruiz 
Changed-By: Norbert Preining 
Description:
 calibre- e-book converter and library management
 calibre-bin - e-book converter and library management
Closes: 872595
Changes:
 calibre (3.7.0+dfsg-1) unstable; urgency=medium
 .
   [ Martin Pitt ]
   * Whitespace fixes
 .
   [ Norbert Preining ]
   * New upstream version 3.7.0+dfsg
   * Rework .pyc generation using pycompile in postinst/postrm
 code copied from dh_python generated debhelper snippets.
   * do not delete _ui.py files in clean action
   * update list of installed files
   * add source override for wrong lintian check
   * add python-html5-parser to deps
   * bump standards version, no changes necessary
   * cherrypick upstream fix for mspack security issues (Closes: #872595)
Checksums-Sha1:
 5c717980606c2719b02deda328978dc97ef8cbc8 2447 calibre_3.7.0+dfsg-1.dsc
 1e3221a7cc1b2ed6045eeecffbffbaf1a9335aae 35995564 
calibre_3.7.0+dfsg.orig.tar.xz
 5054a77ab93afd82153a1ba70b0b92445f50cb40 52976 
calibre_3.7.0+dfsg-1.debian.tar.xz
 af575b173da54d51404c5912c799066e1f866bd7 943170 
calibre-bin-dbgsym_3.7.0+dfsg-1_amd64.deb
 b7ec885e121fd7b32e89a841e3089e5114191ea7 410016 
calibre-bin_3.7.0+dfsg-1_amd64.deb
 8e061ccb5d529df2b653aacd90c6ba49bb2b1775 22909424 calibre_3.7.0+dfsg-1_all.deb
 af8330e10162a681a2664e063fbb5e5a5292beda 16634 
calibre_3.7.0+dfsg-1_amd64.buildinfo
Checksums-Sha256:
 0d379919aff038568e5883f9428935d8758a5a6478c5fc400f3de141bea8ea6d 2447 
calibre_3.7.0+dfsg-1.dsc
 e8a9534bdc71a9537f4a6d24b2df760dd4a1099479f8e5a65aaad974eed9b297 35995564 
calibre_3.7.0+dfsg.orig.tar.xz
 72f6957e35cb7db5bf7647aeb0633009c6ab781ee7a02a62101f0423c85199bc 52976 
calibre_3.7.0+dfsg-1.debian.tar.xz
 2b3bf5006282e47a2327420bd49559b253c67f430a93a79571b3780e7743 943170 
calibre-bin-dbgsym_3.7.0+dfsg-1_amd64.deb
 a8047b7a6cc5944b997367ceee6f18ac8a17b90220810ddb30b755b7d8621648 410016 
calibre-bin_3.7.0+dfsg-1_amd64.deb
 76dad9afd03b082de5ab55437592e1601e49bb4f31c373065477b8bd8aa2cb99 22909424 
calibre_3.7.0+dfsg-1_all.deb
 92f5e4614105

Processed: dbusada: Please update for gnat-7

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #872544 [src:dbusada] dbusada: Please update for gnat-7
Severity set to 'serious' from 'normal'

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

Bug#873508: sparse test failures on ppc32le (and other not so common archs)

[Antoine Beaupré]

On 2017-09-01 09:46:44, Uwe Kleine-König wrote:
> Hello,
>
> On Thu, Aug 31, 2017 at 11:43:53PM +0100, Ramsay Jones wrote:
>> On 31/08/17 21:55, Uwe Kleine-König wrote:
>> > On Wed, Aug 30, 2017 at 08:11:49PM -0400, Christopher Li wrote:
>> >> That is very much like on x86_64 missing define "#weak_define __x86_64__ 
>> >> 1"
>> >>
>> >> Does cgcc work for you? In the future we do want to move the archetecture
>> >> related define from cgcc into sparse by itself. For now you can set
>> >> "sparse" as "cgcc -no-compile"
>> > 
>> > Yes that works. So to address the Debian bug I can do:
>> > 
>> >  - move sparse to /usr/lib
>> >  - teach cgcc about the move of sparse
>> >  - make /usr/bin/sparse call cgcc -no-compile "$@"
>> 
>> Hmm, I don't think that would be a good idea ...
>> 
>> > or is it easier to teach sparse about the architecture stuff?
>> 
>> I now understand (I think!) that you are building a sparse
>> package (presumably a .deb) and you are concerned that sparse
>> does not pass it's own testsuite on those platforms.
>
> Nearly right. I'm responsible for the sparse Debian package and the
> problem at hand is https://bugs.debian.org/873508. This bug report has
> "Severity: serious" wihch might eventually result in the removal of
> sparse from the Debian archive.
>
> @anarcat: Given that cgcc seems to work, would you agree to apply the
> following patch to horst:
>
> diff --git a/Makefile b/Makefile
> index 4f924fa..d563652 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -110,7 +110,7 @@ $(NAME): $(OBJS)
>  $(OBJS): .buildflags
>  
>  check:
> - sparse $(CFLAGS) *.[ch]
> + cgcc -no-compile $(CFLAGS) *.[ch]
>  
>  clean:
>   -rm -f *.o radiotap/*.o *~
>
> and downgrade the bug to "important"? That would be a compromise that
> buys us a bit of time.

Well right now I have simply disabled the checks for those broken
architectures, so sparse isn't as affected anymore.

Frankly, I don't quite know what to do with this - but I'd be happy to
happly that patch to sparse if it fixes the issue better.

A.

-- 
Those who would give up essential Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety.
- Benjamin Franklin, 1755

Bug#873878: [gluster-packaging] Fwd: Bug#873878: glusterfs-client: mount.glusterfs needs bash as /bin/sh

[Patrick Matthäi]

Am 01.09.2017 um 11:40 schrieb Niels de Vos:
> On Fri, Sep 01, 2017 at 09:36:16AM +0200, Patrick Matthäi wrote:
>> Hi,
>>
>> how should it be fixed for glusterfs now? Better shell code without
>> bashishm or do you want /bin/bash as shebang?
> Do you have a preference? I do not know how much work is it is to
> rewrite the mount.glusterfs script to remove all the Bashisms. At least
> in the Debian builds you may want to patch it to /bin/bash for the time
> being.

I would prefer a patch, so that it works without bash. Luckily the bug
reporter just wrote a patch :)
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873878#10

If you would merge it, I also would add it to the repository. I have
attached two other patches for 3.12.x, too.

>
> Opinions welcome :) Thanks,
> Niels
>
>>
>>
>>  Weitergeleitete Nachricht 
>> Betreff: Bug#873878: glusterfs-client: mount.glusterfs needs bash as
>> /bin/sh
>> Weitersenden-Datum:  Thu, 31 Aug 2017 20:21:01 +
>> Weitersenden-Von:Michael Lundkvist 
>> Weitersenden-An: debian-bugs-d...@lists.debian.org
>> Weitersenden-CC: Patrick Matthäi 
>> Datum:   Thu, 31 Aug 2017 21:46:18 +0200
>> Von: Michael Lundkvist 
>> Antwort an:  Michael Lundkvist ,
>> 873...@bugs.debian.org
>> An:  Debian Bug Tracking System 
>>
>>
>>
>> Package: glusterfs-client
>> Version: 3.12.0-1
>> Severity: serious
>> Tags: upstream
>> Justification: Policy 10.4
>>
>> Version 3.12 of Glusterfs adds code in /sbin/mount.glusterfs that depends on 
>> bash.
>>
>> With dash as /bin/sh, I get the following error message when trying to mount 
>> a glusterfs volume:
>>> /sbin/mount.glusterfs: 667: /sbin/mount.glusterfs: Bad substitution
>> Line 667 is:
>> 667 [ ${volume_str:0:1} = '/' ] && {
>>
>> Modifying mount.glusterfs to use /bin/bash makes it possible to mount again.
>>
>> /Micke
>>
>>
>> -- System Information:
>> Debian Release: buster/sid
>>   APT prefers unstable
>>   APT policy: (500, 'unstable')
>> Architecture: amd64 (x86_64)
>>
>> Kernel: Linux 4.12.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:en (charmap=UTF-8)
>> Shell: /bin/sh linked to /bin/dash
>> Init: systemd (via /run/systemd/system)
>>
>> Versions of packages glusterfs-client depends on:
>> ii  fuse  2.9.7-1
>> ii  glusterfs-common  3.12.0-1
>> ii  libc6 2.24-17
>> ii  libssl1.1 1.1.0f-5
>> ii  python2.7.13-2
>>
>> glusterfs-client recommends no packages.
>>
>> glusterfs-client suggests no packages.
>>
>> -- no debconf information
>>
>> ___
>> packaging mailing list
>> packag...@gluster.org
>> http://lists.gluster.org/mailman/listinfo/packaging

-- 
/*
Mit freundlichem Gruß / With kind regards,
 Patrick Matthäi
 GNU/Linux Debian Developer

  Blog: http://www.linux-dev.org/
E-Mail: pmatth...@debian.org
patr...@linux-dev.org
*/

# Fix syntax error in shell script.

diff -Naur 
glusterfs-3.11.1.orig/extras/hook-scripts/create/post/S10selinux-label-brick.sh 
glusterfs-3.11.1/extras/hook-scripts/create/post/S10selinux-label-brick.sh
--- 
glusterfs-3.11.1.orig/extras/hook-scripts/create/post/S10selinux-label-brick.sh 
2017-06-27 17:25:12.237136825 +0200
+++ glusterfs-3.11.1/extras/hook-scripts/create/post/S10selinux-label-brick.sh  
2017-07-03 16:21:05.113301642 +0200
@@ -43,7 +43,7 @@
 do
 # Add a file context for each brick path and associate with the
 # glusterd_brick_t SELinux type.
-semanage fcontext --add -t glusterd_brick_t -r s0 $b(/.*)?
+semanage fcontext --add -t glusterd_brick_t -r s0 $b
 
 # Set the labels on the new brick path.
 restorecon -R $b
# Fix new spelling errors.

diff -Naur glusterfs-3.12.0.orig/xlators/mgmt/glusterd/src/glusterd-geo-rep.c 
glusterfs-3.12.0/xlators/mgmt/glusterd/src/glusterd-geo-rep.c
--- glusterfs-3.12.0.orig/xlators/mgmt/glusterd/src/glusterd-geo-rep.c  
2017-08-30 14:46:33.875359178 +0200
+++ glusterfs-3.12.0/xlators/mgmt/glusterd/src/glusterd-geo-rep.c   
2017-08-31 10:43:14.228479030 +0200
@@ -3615,7 +3615,7 @@
 "geo-replication start failed",
 strerror (errno));
 snprintf (errmsg, sizeof(errmsg),
-  "fuse unvailable");
+  "fuse unavailable");
 ret = -1;
 goto out;
 }
diff -Naur 
glusterfs-3.12.0.orig/xlators/mgmt/glusterd/src/glusterd-volume-set.c 
glusterfs-3.12.0/xlators/mgmt/glusterd/src/glusterd-volume-set.c
--- glusterfs-3.12.0.orig/xlators/mgmt/glusterd/src/glusterd-volume-set.c   
2017-08-30 14:46:33.901359256 +0200
+++ glusterfs-3.12.0/xlators/mgmt/glusterd/src/glusterd-volume-s

Processed: Not a problem in stretch

[Debian Bug Tracking System]

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

> tags 873928 buster sid
Bug #873928 [src:caveconverter] caveconverter: please Build-Depend on rename
Added tag(s) sid and buster.
> thanks
Stopping processing here.

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

Bug#871514: gcc-7: miscompiles stack spills on mips64el

[James Cowgill]

Control: tags -1 patch

Hi,

On 23/08/17 17:42, James Cowgill wrote:
> This bug is very closely related to an earlier GCC bootstrap failure on
> mips64el: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78660
> In comment 17 Matthew sent a patch and applying it also fixes this bug.
> However, he tells me it has some other issues and isn't suitable to be
> applied (which is presumably why it was reverted).

Matthew has now had a better look at the bug and has posted a patch to
fix it which is a tweaked version of the patch above:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81803#c9

I've done some testing, and it seems to solve all the known package
failures (at least the ones on my list) caused by this bug and I haven't
noticed any failures with it. I also tested it on armhf and it causes no
regressions there (this was one of the issues with the earlier patch).

So I think the attached debdiff should be applied to gcc-7. Currently
the patch is applied everywhere, but if you want you could limit it to
mips64el.

Thanks,
James
diff -u gcc-7-7.2.0/debian/rules.patch gcc-7-7.2.0/debian/rules.patch
--- gcc-7-7.2.0/debian/rules.patch
+++ gcc-7-7.2.0/debian/rules.patch
@@ -72,6 +72,7 @@
gcc-fuse-ld-lld \
libgo-s390x-default-isa \
pr81829 \
+   gcc-mips64-stack-spilling \
 
 
 #  $(if $(filter yes, $(DEB_CROSS)),,gcc-print-file-name) \
only in patch2:
unchanged:
--- gcc-7-7.2.0.orig/debian/patches/gcc-mips64-stack-spilling.diff
+++ gcc-7-7.2.0/debian/patches/gcc-mips64-stack-spilling.diff
@@ -0,0 +1,16 @@
+--- a/src/gcc/lra-constraints.c
 b/src/gcc/lra-constraints.c
+@@ -4235,7 +4235,12 @@ curr_insn_transform (bool check_only_p)
+ && (goal_alt[i] == NO_REGS
+ || (simplify_subreg_regno
+ (ira_class_hard_regs[goal_alt[i]][0],
+- GET_MODE (reg), byte, mode) >= 0)
++ GET_MODE (reg), byte, mode) >= 0
++|| (type != OP_IN
++&& GET_MODE_PRECISION (mode)
++< GET_MODE_PRECISION (GET_MODE (reg))
++&& GET_MODE_SIZE (GET_MODE (reg)) <= UNITS_PER_WORD
++&& WORD_REGISTER_OPERATIONS))
+   {
+ /* An OP_INOUT is required when reloading a subreg of a
+mode wider than a word to ensure that data beyond the


signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#871514: gcc-7: miscompiles stack spills on mips64el

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #871514 [gcc-7] gcc-7: miscompiles stack spills on mips64el
Bug #871538 [gcc-7] gcc-7: miscompiles stack spills on mips64el
Bug #872438 [gcc-7] gcc-7: miscompiles stack spills on mips64el
Bug #872987 [gcc-7] gcc-7: miscompiles stack spills on mips64el
Added tag(s) patch.
Added tag(s) patch.
Added tag(s) patch.
Added tag(s) patch.

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

Bug#873792: marked as done (qjackctl will not start at all)

[Debian Bug Tracking System]

Your message dated Fri, 1 Sep 2017 12:38:56 +0200
with message-id <20170901103856.nayms5vpp2dzt...@ramacher.at>
and subject line Re: Bug#873792: qjackctl will not start at all
has caused the Debian Bug report #873792,
regarding qjackctl will not start at all
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.)


-- 
873792: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873792
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: qjackctl
Version: 0.4.5-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

   * What led up to the situation?
   I use jackd to facilitate realtime audio according to my limits.conf
   for some software called Pianoteq. In the last update, I tried to run
   qjackctl and received the following error:

   qjackctl: symbol lookup error:
   /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5: undefined symbol:
   FT_Property_Set

   I am unable to start qjackctl

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

   I do not think I intentionally installed any extra packages that stops 
qjackctl from launching properly.

   * What was the outcome of this action?
   qjackctl does not launch

   * What outcome did you expect instead?
   qjackctl launches normally

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

Kernel: Linux 4.12.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 qjackctl depends on:
ii  jackd 5
ii  libasound21.1.3-5
ii  libc6 2.24-14
ii  libgcc1   1:7.2.0-1
ii  libjack-jackd2-0 [libjack-0.125]  1.9.10+20150825git1ed50c92~dfsg-5
ii  libqt5core5a  5.9.1+dfsg-9
ii  libqt5dbus5   5.9.1+dfsg-9
ii  libqt5gui55.9.1+dfsg-9
ii  libqt5widgets55.9.1+dfsg-9
ii  libqt5x11extras5  5.9.1-2+b1
ii  libqt5xml55.9.1+dfsg-9
ii  libstdc++67.2.0-1
ii  libx11-6  2:1.6.4-3

qjackctl recommends no packages.

Versions of packages qjackctl suggests:
ii  pulseaudio-utils  10.0-2

-- no debconf information
--- End Message ---
--- Begin Message ---
On 2017-09-01 03:38:28, Ed Peguillan III wrote:
> My mail client replied to the wrong address, my apologies.
> 
> After performing
> $ sudo mv /usr/lib/x86_64-linux-gnu/freetype-infinality/liblibfreetype.so.6
> ~
> 
> qjackctl and virtualbox seem to start and work normally.
> 
> It's too bad that I can't use infinality fonts anymore, my screen is back to
> looking terrible.
> 
> Thank you for your help! This bug can be closed.

Thanks, closing.
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature
--- End Message ---

Processed: gcc-7: miscompiles stack spills on mips64el

[Debian Bug Tracking System]

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

> affects 871514 src:telegram-desktop
Bug #871514 [gcc-7] gcc-7: miscompiles stack spills on mips64el
Bug #871538 [gcc-7] gcc-7: miscompiles stack spills on mips64el
Bug #872438 [gcc-7] gcc-7: miscompiles stack spills on mips64el
Bug #872987 [gcc-7] gcc-7: miscompiles stack spills on mips64el
Added indication that 871514 affects src:telegram-desktop
Added indication that 871538 affects src:telegram-desktop
Added indication that 872438 affects src:telegram-desktop
Added indication that 872987 affects src:telegram-desktop
> thanks
Stopping processing here.

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

Bug#873557: mbedtls: CVE-2017-14032: authentication bypass

[James Cowgill]

Hi,

On 30/08/17 20:48, Salvatore Bonaccorso wrote:
> Control: retitle mbedtls: CVE-2017-14032: authentication bypass
> 
> Hi
> 
> On Tue, Aug 29, 2017 at 12:09:30AM +0100, James Cowgill wrote:
>> Source: mbedtls
>> Version: 2.1.2-1
>> Severity: grave
>> Tags: security
>>
>> Hi,
>>
>> The following security advisory was published for mbedtls:
>> https://tls.mbed.org/tech-updates/security-advisories/mbedtls-security-advisory-2017-02
> 
> MITRE has assigned CVE-2017-14032 for this issue.

Does the attached patch look OK for stretch? I did a bit of testing with
it and it seems to fix the issue for me.

Thanks,
James
diff -Nru mbedtls-2.4.2/debian/changelog mbedtls-2.4.2/debian/changelog
--- mbedtls-2.4.2/debian/changelog  2017-03-14 10:54:33.0 +
+++ mbedtls-2.4.2/debian/changelog  2017-09-01 09:29:59.0 +0100
@@ -1,3 +1,12 @@
+mbedtls (2.4.2-1+deb9u1) stretch-security; urgency=high
+
+  * Fix CVE-2017-14032:
+If optional authentication is configured, allows remote attackers to
+bypass peer authentication via an X.509 certificate chain with many
+intermediates. (Closes: #873557)
+
+ -- James Cowgill   Fri, 01 Sep 2017 09:29:59 +0100
+
 mbedtls (2.4.2-1) unstable; urgency=high
 
   * New upstream version.
diff -Nru mbedtls-2.4.2/debian/patches/CVE-2017-14032.patch 
mbedtls-2.4.2/debian/patches/CVE-2017-14032.patch
--- mbedtls-2.4.2/debian/patches/CVE-2017-14032.patch   1970-01-01 
01:00:00.0 +0100
+++ mbedtls-2.4.2/debian/patches/CVE-2017-14032.patch   2017-09-01 
09:29:59.0 +0100
@@ -0,0 +1,149 @@
+Description: Fix CVE-2017-14032: authentication bypass
+ If a malicious peer supplies an X.509 certificate chain that has more
+ than MBEDTLS_X509_MAX_INTERMEDIATE_CA intermediates (which by default is
+ 8), it could bypass authentication of the certificates, when the
+ authentication mode was set to 'optional' eg.
+ MBEDTLS_SSL_VERIFY_OPTIONAL. The issue could be triggered remotely by
+ both the client and server sides.
+ .
+ Fix by backporting two patches from the upstream 2.6 branch:
+  d15795acd507 = Improve behaviour on fatal errors
+  31458a18788b = Only return VERIFY_FAILED from a single point
+Author: Manuel Pégourié-Gonnard 
+Origin: backport, 
https://github.com/ARMmbed/mbedtls/commit/d15795acd5074e0b44e71f7ede8bdfe1b48591fc
+Origin: backport, 
https://github.com/ARMmbed/mbedtls/commit/31458a18788b0cf0b722acda9bb2f2fe13a3fb32
+Bug-Debian: https://bugs.debian.org/873557
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+
+--- a/library/x509_crt.c
 b/library/x509_crt.c
+@@ -2055,8 +2055,8 @@ static int x509_crt_verify_child(
+ /* path_cnt is 0 for the first intermediate CA */
+ if( 1 + path_cnt > MBEDTLS_X509_MAX_INTERMEDIATE_CA )
+ {
+-*flags |= MBEDTLS_X509_BADCERT_NOT_TRUSTED;
+-return( MBEDTLS_ERR_X509_CERT_VERIFY_FAILED );
++/* return immediately as the goal is to avoid unbounded recursion */
++return( MBEDTLS_ERR_X509_FATAL_ERROR );
+ }
+ 
+ if( mbedtls_x509_time_is_past( &child->valid_to ) )
+@@ -2200,11 +2200,14 @@ int mbedtls_x509_crt_verify_with_profile
+ mbedtls_x509_sequence *cur = NULL;
+ mbedtls_pk_type_t pk_type;
+ 
+-if( profile == NULL )
+-return( MBEDTLS_ERR_X509_BAD_INPUT_DATA );
+-
+ *flags = 0;
+ 
++if( profile == NULL )
++{
++ret = MBEDTLS_ERR_X509_BAD_INPUT_DATA;
++goto exit;
++}
++
+ if( cn != NULL )
+ {
+ name = &crt->subject;
+@@ -2278,7 +2281,7 @@ int mbedtls_x509_crt_verify_with_profile
+ ret = x509_crt_verify_top( crt, parent, ca_crl, profile,
+pathlen, selfsigned, flags, f_vrfy, p_vrfy 
);
+ if( ret != 0 )
+-return( ret );
++goto exit;
+ }
+ else
+ {
+@@ -2293,17 +2296,28 @@ int mbedtls_x509_crt_verify_with_profile
+ ret = x509_crt_verify_child( crt, parent, trust_ca, ca_crl, 
profile,
+  pathlen, selfsigned, flags, f_vrfy, 
p_vrfy );
+ if( ret != 0 )
+-return( ret );
++goto exit;
+ }
+ else
+ {
+ ret = x509_crt_verify_top( crt, trust_ca, ca_crl, profile,
+pathlen, selfsigned, flags, f_vrfy, 
p_vrfy );
+ if( ret != 0 )
+-return( ret );
++goto exit;
+ }
+ }
+ 
++exit:
++/* prevent misuse of the vrfy callback */
++if( ret == MBEDTLS_ERR_X509_CERT_VERIFY_FAILED )
++ret = MBEDTLS_ERR_X509_FATAL_ERROR;
++
++if( ret != 0 )
++{
++*flags = (uint32_t) -1;
++return( ret );
++}
++
+ if( *flags != 0 )
+ return( MBEDTLS_ERR_X509_CERT_VERIFY_FAILED );
+ 
+--- a/include/mbedtls/error.h
 b/include/mbedtls/error.h
+@@ -71,7 +71,7 @@
+  * Name  ID  Nr of Errors
+  * PEM   1   9
+  * PKCS#12   1   4 (Started from top)
+- * 

Bug#873928: caveconverter: please Build-Depend on rename

[Dominic Hargreaves]

Source: caveconverter
Version: 0~20170114-1
Severity: serious
Justification: FTBFS with impending change
User: debian-p...@lists.debian.org
Usertags: rename-deprecation

As announced last year[1] and as advised by deprecation messages,
rename(1) will be removed from the perl package after the stretch
release, and this is now imminent.

Your package FTBFS with perl from experimental as a result. Please
add a Build-Depends: rename to your package, and all will be well
again:

#change to unix command name in examples files
sed --in-place -e 's/java -jar CaveConverter.jar/caveconverter/' 
debian//caveconverter/usr/share/doc/caveconverter/examples/*.bat
rename 's/\.bat$//' 
debian//caveconverter/usr/share/doc/caveconverter/examples/*.bat
/bin/sh: 1: rename: not found

Let me know if you would prefer an NMU to get this trivial change made.

Cheers,
Dominic.

[1] 

Bug#873925: nfs-ganesha FTBFS with libntirpc-dev 1.5.3-1

[Adrian Bunk]

Source: nfs-ganesha
Version: 2.4.5-2
Severity: serious

https://buildd.debian.org/status/package.php?p=nfs-ganesha&suite=sid

...
make -f log/CMakeFiles/log.dir/build.make log/CMakeFiles/log.dir/build
make[4]: Entering directory '/<>/src/obj-x86_64-linux-gnu'
[  1%] Building C object log/CMakeFiles/log.dir/display.c.o
cd /<>/src/obj-x86_64-linux-gnu/log && /usr/bin/cc -D__USE_GNU 
-I/usr/include/glusterfs -I/usr/include/uuid 
-I/<>/src/obj-x86_64-linux-gnu/include 
-I/<>/src/include -I/<>/src/include/os/linux 
-I/include -I/usr/include/ntirpc -I/usr/include/dbus-1.0 
-I/usr/lib/x86_64-linux-gnu/dbus-1.0/include  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -D_LARGEFILE64_SOURCE 
-D_FILE_OFFSET_BITS=64 -O2 -g -DNDEBUG   -D _GNU_SOURCE -o 
CMakeFiles/log.dir/display.c.o   -c /<>/src/log/display.c
[  1%] Building C object log/CMakeFiles/log.dir/log_functions.c.o
cd /<>/src/obj-x86_64-linux-gnu/log && /usr/bin/cc -D__USE_GNU 
-I/usr/include/glusterfs -I/usr/include/uuid 
-I/<>/src/obj-x86_64-linux-gnu/include 
-I/<>/src/include -I/<>/src/include/os/linux 
-I/include -I/usr/include/ntirpc -I/usr/include/dbus-1.0 
-I/usr/lib/x86_64-linux-gnu/dbus-1.0/include  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -D_LARGEFILE64_SOURCE 
-D_FILE_OFFSET_BITS=64 -O2 -g -DNDEBUG   -D _GNU_SOURCE -o 
CMakeFiles/log.dir/log_functions.c.o   -c 
/<>/src/log/log_functions.c
In file included from /<>/src/log/log_functions.c:49:0:
/<>/src/include/gsh_rpc.h:27:10: fatal error: rpc/rpc_dplx.h: No 
such file or directory
 #include 
  ^~~~
compilation terminated.
log/CMakeFiles/log.dir/build.make:89: recipe for target 
'log/CMakeFiles/log.dir/log_functions.c.o' failed
make[4]: *** [log/CMakeFiles/log.dir/log_functions.c.o] Error 1

Bug#873791: Bug#873915: python2.7: fpectl removal breaks cython

[Axel Beckert]

Ole Streicher wrote:
> On 01.09.2017 09:51, Matthias Klose wrote:
> > Control: severity -1 important
> 
> IMO it is RC, isn't it?

I'd even say "critical" instead of the previous "serious" since it
breaks unrelated packages like apt and aptitude. (But the "unrelated"
is discussable so I didn't raise the severity from serious.)

IMHO this issue (since there are breaks in the python packages) now
should be filed again against python-numpy and what else is affected.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Bug#870686: marked as done (libglvnd: not ready for buster, yet)

[Debian Bug Tracking System]

Your message dated Fri, 01 Sep 2017 09:24:27 +
with message-id 
and subject line Bug#870686: fixed in libglvnd 0.2.999+git20170802-3
has caused the Debian Bug report #870686,
regarding libglvnd: not ready for buster, yet
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.)


-- 
870686: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870686
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libglvnd
Version: 0.2.999+git20170802-2
Severity: serious

Since the mesa packaging hasn't switched to glvnd, yet, there are file
conflicts between several packages from src:mesa and src:libglvnd.
So let's keep libglvnd out of testing until this transition progresses.


Andreas
--- End Message ---
--- Begin Message ---
Source: libglvnd
Source-Version: 0.2.999+git20170802-3

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

Debian distribution maintenance software
pp.
Timo Aaltonen  (supplier of updated libglvnd package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 01 Sep 2017 11:15:04 +0300
Source: libglvnd
Binary: libglvnd-dev libglvnd-core-dev libglvnd0 libegl1 libgles2 libgl1 
libglx0 libopengl0
Architecture: source
Version: 0.2.999+git20170802-3
Distribution: unstable
Urgency: medium
Maintainer: Debian X Strike Force 
Changed-By: Timo Aaltonen 
Description:
 libegl1- Vendor neutral GL dispatch library -- EGL support
 libgl1 - Vendor neutral GL dispatch library -- legacy GL support
 libgles2   - Vendor neutral GL dispatch library -- GLES support
 libglvnd-core-dev - Vendor neutral GL dispatch library -- core development 
files
 libglvnd-dev - Vendor neutral GL dispatch library -- development files
 libglvnd0  - Vendor neutral GL dispatch library
 libglx0- Vendor neutral GL dispatch library -- GLX support
 libopengl0 - Vendor neutral GL dispatch library -- OpenGL support
Closes: 870686
Changes:
 libglvnd (0.2.999+git20170802-3) unstable; urgency=medium
 .
   [ Timo Aaltonen ]
   * control: Add Breaks/Replaces to match mesa upload which enabled
 GLVND. (Closes: #870686)
   * control: Add back depends on default libegl/libglx vendor.
 .
   [ Andreas Beckmann ]
   * libgl1: Add Breaks against glx-diversions (<< 0.8) which did not divert
 libGL.so.1.0.0.
   * libglvnd0: Add Breaks+Replaces: libgldispatch0-nvidia which also shipped
 libGLdispatch.so.0.
Checksums-Sha1:
 aaef85f27bf64af547fb7d54016b2cefcbec5fa6 2386 
libglvnd_0.2.999+git20170802-3.dsc
 46936b0cfa6f47af1db0fcb3ddd887b9302c2a76 22555 
libglvnd_0.2.999+git20170802-3.diff.gz
Checksums-Sha256:
 fb09441888514cdb2c3a2e793139812e08061e54779ade6a94d427de8247cc60 2386 
libglvnd_0.2.999+git20170802-3.dsc
 8b16254f76507a0b5bbdbc76e9f1135c41d8286680698f49e068d89a07117c67 22555 
libglvnd_0.2.999+git20170802-3.diff.gz
Files:
 39e6904bf0f0c0f6e3f16b10bfd6 2386 libs extra 
libglvnd_0.2.999+git20170802-3.dsc
 eab570f87e6e6005212ef151ea6bc52a 22555 libs extra 
libglvnd_0.2.999+git20170802-3.diff.gz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJZqReWAAoJEMtwMWWoiYTcqBoP/AtDtD/5xaJ3SCCtE3HPRboP
MOZJlEMV/DP9TWOzzmxvZZfipA34/X0LFQ635feCle3zxLIhbLgAwOeYuCVBK3py
Vv5JuRYNvXc0QGuZ07oduM9I76VzT6CE6bWmerWYGn/+27xVOio6Lsb91GMokVrN
smfH0Hl23jOwrBsx9i4/SiJ5pOO8Ga7bf4Ac4g7YjBJNdTLIrWVl7mOC2CRAK1WS
DY1Iw2R8C2xAB4owc6UWloXFva3WzFllSdo/kv/AhlRHo+8ZqI053HLoxnYIVSKY
M35Wo0aWNTqrH9yL3VVXInKGVriVBnp0lvPONpu2hKCqOsFxWa0hcjA2ym1RN3vL
mKKXIo+oAUzmiVpkxFTq2ywjPIMiOQ9ppK/6cyaAsl+0OPNb2lzO96LjBXWsp8X8
Yv7yInJ9ZQi1W7uU3AF27Xb8nYChFNqnQVfEFM2G0xSwmxZlSqDKofkGjC3DMqIg
oSEUVid40LcKkPHGwJksu1HNe1uymybNB33zxORpYfrYMK5b2OlhobfykJsasUvH
O4W/329rqpOyKwNO0HG2YcRCelzlqM9qDfOZW9UwkQUanu0NxkUxm+lC0Qm86ExY
HMnokbvuN+tpttVpXljaz2WIp9SopdqkzzvZnXBCTKmRf4fqINHqxdB5J4+XBO7c
reB4x4ICgm15O5n02NOs
=hkfy
-END PGP SIGNATURE End Message ---

Bug#873912: marked as done (coffeescript: Error: Cannot find module '../../package.json')

[Debian Bug Tracking System]

Your message dated Fri, 01 Sep 2017 09:21:02 +
with message-id 
and subject line Bug#873912: fixed in coffeescript 1.12.7~dfsg-2
has caused the Debian Bug report #873912,
regarding coffeescript: Error: Cannot find module '../../package.json'
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.)


-- 
873912: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873912
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: coffeescript
Version: 1.12.7~dfsg-1
Severity: serious

Most (all?) packages build-depending on coffeescript
FTBFS with 1.12.7~dfsg-1, example:

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

...
   debian/rules override_dh_auto_build
make[1]: Entering directory '/build/1st/camo-2.3.0+dfsg'
rake --trace build
** Invoke build (first_time)
** Invoke server.js (first_time)
** Invoke server.coffee (first_time, not_needed)
** Execute server.js
coffee -c -o . server.coffee
module.js:471
throw err;
^

Error: Cannot find module '../../package.json'
at Function.Module._resolveFilename (module.js:469:15)
at Function.Module._load (module.js:417:25)
at Module.require (module.js:497:17)
at require (internal/module.js:20:19)
at Object. 
(/usr/lib/coffee-script/lib/coffee-script/coffee-script.js:20:17)
at Object. 
(/usr/lib/coffee-script/lib/coffee-script/coffee-script.js:426:4)
at Module._compile (module.js:570:32)
at Object.Module._extensions..js (module.js:579:10)
at Module.load (module.js:487:32)
at tryModuleLoad (module.js:446:12)
rake aborted!
Command failed with status (1): [coffee -c -o . server.coffee...]
/usr/lib/ruby/vendor_ruby/rake/file_utils.rb:66:in `block in 
create_shell_runner'
/usr/lib/ruby/vendor_ruby/rake/file_utils.rb:56:in `sh'
/build/1st/camo-2.3.0+dfsg/Rakefile:2:in `block in '
/usr/lib/ruby/vendor_ruby/rake/task.rb:250:in `block in execute'
/usr/lib/ruby/vendor_ruby/rake/task.rb:250:in `each'
/usr/lib/ruby/vendor_ruby/rake/task.rb:250:in `execute'
/usr/lib/ruby/vendor_ruby/rake/task.rb:194:in `block in invoke_with_call_chain'
/usr/lib/ruby/2.3.0/monitor.rb:214:in `mon_synchronize'
/usr/lib/ruby/vendor_ruby/rake/task.rb:187:in `invoke_with_call_chain'
/usr/lib/ruby/vendor_ruby/rake/task.rb:216:in `block in invoke_prerequisites'
/usr/lib/ruby/vendor_ruby/rake/task.rb:214:in `each'
/usr/lib/ruby/vendor_ruby/rake/task.rb:214:in `invoke_prerequisites'
/usr/lib/ruby/vendor_ruby/rake/task.rb:193:in `block in invoke_with_call_chain'
/usr/lib/ruby/2.3.0/monitor.rb:214:in `mon_synchronize'
/usr/lib/ruby/vendor_ruby/rake/task.rb:187:in `invoke_with_call_chain'
/usr/lib/ruby/vendor_ruby/rake/task.rb:180:in `invoke'
/usr/lib/ruby/vendor_ruby/rake/application.rb:152:in `invoke_task'
/usr/lib/ruby/vendor_ruby/rake/application.rb:108:in `block (2 levels) in 
top_level'
/usr/lib/ruby/vendor_ruby/rake/application.rb:108:in `each'
/usr/lib/ruby/vendor_ruby/rake/application.rb:108:in `block in top_level'
/usr/lib/ruby/vendor_ruby/rake/application.rb:117:in `run_with_threads'
/usr/lib/ruby/vendor_ruby/rake/application.rb:102:in `top_level'
/usr/lib/ruby/vendor_ruby/rake/application.rb:80:in `block in run'
/usr/lib/ruby/vendor_ruby/rake/application.rb:178:in 
`standard_exception_handling'
/usr/lib/ruby/vendor_ruby/rake/application.rb:77:in `run'
/usr/bin/rake:27:in `'
Tasks: TOP => build => server.js
debian/rules:30: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 1
--- End Message ---
--- Begin Message ---
Source: coffeescript
Source-Version: 1.12.7~dfsg-2

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated coffeescript 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: Fri, 01 Sep 2017 10:57:20 +0200
Source: coffeescript
Binary: coffeescript libjs-coffeescript coffeescript-doc
Architecture: source all
Version: 1.12.7~dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainer

Bug#873791: [python-numpy] Undefined symbols on several architectures

[Adrian Bunk]

On Fri, Sep 01, 2017 at 11:18:00AM +0300, Adrian Bunk wrote:
> On Thu, Aug 31, 2017 at 12:48:53PM +0200, Matthias Klose wrote:
> > On 31.08.2017 12:35, Adrian Bunk wrote:
> > > Control: reassign -1 python2.7 2.7.14~rc1-1
> > > Control: retitle -1 python2.7: fpectl extension removal broke the ABI for 
> > > C extensions
> > > Control: affects -1 python-numpy
> > > 
> > > On Thu, Aug 31, 2017 at 11:34:55AM +0200, Michał Klichowicz wrote:
> > >> Got that error on amd64, too.
> > >>
> > >> This started today, after the upgrading python2.7 packages to 2.7.14~rc1
> > >> in sid. Downgrading back to buster's 2.7.13-2 solves the problem.
> > > 
> > > I got the same error with Cython:
> > > 
> > > ImportError: 
> > > /usr/lib/python2.7/dist-packages/Cython/Compiler/Code.x86_64-linux-gnu.so:
> > >  undefined symbol: PyFPE_jbuf.  You should look at http://www.cython.org"; 
> > > 
> > > It seems the following change in 2.7.14~rc1-1 broke the ABI:
> > >   * Stop building the fpectl extension.
> > 
> > yes, that's intended. I'll add a break.  Are there other known packages 
> > besides
> > python-numpy?
> 
> As written above, Cython is the one where I ran into this issue.

And based on #873921, borgbackup.

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

Bug#873792: qjackctl will not start at all

[Ed Peguillan III]

My mail client replied to the wrong address, my apologies.

After performing
$ sudo mv 
/usr/lib/x86_64-linux-gnu/freetype-infinality/liblibfreetype.so.6 ~


qjackctl and virtualbox seem to start and work normally.

It's too bad that I can't use infinality fonts anymore, my screen is 
back to looking terrible.


Thank you for your help! This bug can be closed.

Ed

On Thu, 31 Aug 2017 23:46:16 +0200 Sebastian Ramacher 
 wrote:

> Re-adding the bug to CC.
>
> On 2017-08-31 16:02:13, Ed Peguillan III wrote:
> > Sure.
> >
> > |$ ldd -r /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5||
> > || linux-vdso.so.1 (0x7ffd883f3000)||
> > || libxcb-xinerama.so.0 => 
/usr/lib/x86_64-linux-gnu/libxcb-xinerama.so.0

> > (0x7f6ec82f9000)||
> > || libglib-2.0.so.0 => /lib/x86_64-linux-gnu/libglib-2.0.so.0
> > (0x7f6ec7fe4000)||
> > || libfontconfig.so.1 => /usr/lib/x86_64-linux-gnu/libfontconfig.so.1
> > (0x7f6ec7da)||
> > || libfreetype.so.6 =>
> > /usr/lib/x86_64-linux-gnu/freetype-infinality/libfreetype.so.6
>
> And that's the issue. Please remove it and try again.
>
> Cheers
>
> > (0x7f6ec7aef000)||
> > || libQt5Gui.so.5 => /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
> > (0x7f6ec7388000)||
> > || libQt5DBus.so.5 => /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
> > (0x7f6ec70fe000)||
> > || libQt5Core.so.5 => /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
> > (0x7f6ec69b5000)||
> > || libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
> > (0x7f6ec6798000)||
> > || libX11.so.6 => /usr/lib/x86_64-linux-gnu/libX11.so.6
> > (0x7f6ec6458000)||
> > || libX11-xcb.so.1 => /usr/lib/x86_64-linux-gnu/libX11-xcb.so.1
> > (0x7f6ec6256000)||
> > || libXi.so.6 => /usr/lib/x86_64-linux-gnu/libXi.so.6
> > (0x7f6ec6046000)||
> > || libSM.so.6 => /usr/lib/x86_64-linux-gnu/libSM.so.6
> > (0x7f6ec5e3e000)||
> > || libICE.so.6 => /usr/lib/x86_64-linux-gnu/libICE.so.6
> > (0x7f6ec5c21000)||
> > || libxcb-xkb.so.1 => /usr/lib/x86_64-linux-gnu/libxcb-xkb.so.1
> > (0x7f6ec5a05000)||
> > || libxcb-render-util.so.0 =>
> > /usr/lib/x86_64-linux-gnu/libxcb-render-util.so.0 
(0x7f6ec5801000)||

> > || libxcb-render.so.0 => /usr/lib/x86_64-linux-gnu/libxcb-render.so.0
> > (0x7f6ec55f3000)||
> > || libxcb-sync.so.1 => /usr/lib/x86_64-linux-gnu/libxcb-sync.so.1
> > (0x7f6ec53ec000)||
> > || libxcb-xfixes.so.0 => /usr/lib/x86_64-linux-gnu/libxcb-xfixes.so.0
> > (0x7f6ec51e4000)||
> > || libxcb-randr.so.0 => /usr/lib/x86_64-linux-gnu/libxcb-randr.so.0
> > (0x7f6ec4fd4000)||
> > || libxcb-image.so.0 => /usr/lib/x86_64-linux-gnu/libxcb-image.so.0
> > (0x7f6ec4dcf000)||
> > || libxcb-shm.so.0 => /usr/lib/x86_64-linux-gnu/libxcb-shm.so.0
> > (0x7f6ec4bcb000)||
> > || libxcb-keysyms.so.1 => /usr/lib/x86_64-linux-gnu/libxcb-keysyms.so.1
> > (0x7f6ec49c8000)||
> > || libxcb-icccm.so.4 => /usr/lib/x86_64-linux-gnu/libxcb-icccm.so.4
> > (0x7f6ec47c3000)||
> > || libxcb.so.1 => /usr/lib/x86_64-linux-gnu/libxcb.so.1

Bug#873791: Bug#873915: python2.7: fpectl removal breaks cython

[Ole Streicher]

Hi Mathias,

On 01.09.2017 09:51, Matthias Klose wrote:
> Control: severity -1 important

IMO it is RC, isn't it?

> yes, please check the archive for uploads before you file issues.
Which one do you mean?

Currently (from the tracker): Python 2.7 is still 2.7.14~rc1-2, and
Python 3.6 is still 3.6.2-3, both from yesterday, and both don't break
Cython. Cython also did not get an binNMU yet.

To me, this looks as it is still unresolved on both Python 2 and 3. I
just didn't want to create another issue since you do probably both in
the same step anyway.

Best regards

Ole

Bug#873921: python3.5_3.5.4-3 breaks borgbackup: undefined symbol: PyFPE_jbuf

[Sven Hartge]

Package: borgbackup
Version: 1.0.11-3
Severity: grave

Hi!

I am reporting this bug against borgbackup, because I am not sure if the
bug is in python3.5 or borgbackup just needs to be binNMUd. Please
reassign as you see fit.

The upload of python3.5 (3.5.4-3) disables the fpectl extension and
breaks borgbackup:

$ borg
Traceback (most recent call last):
  File "/usr/bin/borg", line 11, in 
load_entry_point('borgbackup==1.0.11', 'console_scripts', 'borg')()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 564, in 
load_entry_point
return get_distribution(dist).load_entry_point(group, name)
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2662, 
in load_entry_point
return ep.load()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2316, 
in load
return self.resolve()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2322, 
in resolve
module = __import__(self.module_name, fromlist=['__name__'], level=0)
  File "/usr/lib/python3/dist-packages/borg/archiver.py", line 22, in 
from .helpers import Error, location_validator, archivename_validator, 
format_line, format_time, format_file_size, \
  File "/usr/lib/python3/dist-packages/borg/helpers.py", line 35, in 
from . import crypto
ImportError: 
/usr/lib/python3/dist-packages/borg/crypto.cpython-35m-i386-linux-gnu.so: 
undefined symbol: PyFPE_jbuf

Grüße,
Sven.

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

Kernel: Linux 4.9.0-3-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 borgbackup depends on:
ii  fuse   2.9.7-1
ii  libacl12.2.52-3+b1
ii  libc6  2.24-17
ii  liblz4-1   0.0~r131-2+b1
pn  libssl1.1  
ii  python33.5.3-3
ii  python3-llfuse 1.2+dfsg-1+b1
ii  python3-msgpack0.4.8-1+b1
ii  python3-pkg-resources  36.2.7-2

borgbackup recommends no packages.

Versions of packages borgbackup suggests:
pn  borgbackup-doc  

-- debconf-show failed

Processed: fixed 867376 in 0.65+git20170831+dfsg1-1

[Debian Bug Tracking System]

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

> fixed 867376 0.65+git20170831+dfsg1-1
Bug #867376 [src:uncrustify] uncrustify: fills up buildd disk space
Marked as fixed in versions uncrustify/0.65+git20170831+dfsg1-1.
> thanks
Stopping processing here.

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

Bug#873878: Acknowledgement (glusterfs-client: mount.glusterfs needs bash as /bin/sh)

[Michael Lundkvist]

Here is a quick and dirty patch. I manually applied the same change to 
/sbin/mount.glusterfs and got it working with dash again.


No real testing done...

/Micke
diff --git a/xlators/mount/fuse/utils/mount.glusterfs.in b/xlators/mount/fuse/utils/mount.glusterfs.in
index 216d03c41..51792c479 100755
--- a/xlators/mount/fuse/utils/mount.glusterfs.in
+++ b/xlators/mount/fuse/utils/mount.glusterfs.in
@@ -673,8 +673,9 @@ main ()
 [ -n "$volume_str" ] && {
 volume_id=$volume_str
 volume_str_temp=$volume_str
-[ ${volume_str:0:1} = '/' ] && {
-volume_str_temp=${volume_str:1}
+	first_char=$(echo "$volume_str" | cut -c 1)
+[ ${first_char} = '/' ] && {
+volume_str_temp=$(echo "$volume_str" | cut -c 2-)
 }
 [ $(echo $volume_str_temp | grep -c "/") -eq 1 ] && {
 volume_id=$(echo "$volume_str_temp" | cut -f1 -d '/');

Bug#870599: Re; upload ansible version with Depends: python-jinja2 < 2.9

[Jack Henschel]

Thanks for fixing this, greatly appreciated!

Greetings
Jack



signature.asc
Description: OpenPGP digital signature

Bug#873791: [python-numpy] Undefined symbols on several architectures

[Adrian Bunk]

On Thu, Aug 31, 2017 at 12:48:53PM +0200, Matthias Klose wrote:
> On 31.08.2017 12:35, Adrian Bunk wrote:
> > Control: reassign -1 python2.7 2.7.14~rc1-1
> > Control: retitle -1 python2.7: fpectl extension removal broke the ABI for C 
> > extensions
> > Control: affects -1 python-numpy
> > 
> > On Thu, Aug 31, 2017 at 11:34:55AM +0200, Michał Klichowicz wrote:
> >> Got that error on amd64, too.
> >>
> >> This started today, after the upgrading python2.7 packages to 2.7.14~rc1
> >> in sid. Downgrading back to buster's 2.7.13-2 solves the problem.
> > 
> > I got the same error with Cython:
> > 
> > ImportError: 
> > /usr/lib/python2.7/dist-packages/Cython/Compiler/Code.x86_64-linux-gnu.so: 
> > undefined symbol: PyFPE_jbuf.  You should look at http://www.cython.org"; 
> > 
> > It seems the following change in 2.7.14~rc1-1 broke the ABI:
> >   * Stop building the fpectl extension.
> 
> yes, that's intended. I'll add a break.  Are there other known packages 
> besides
> python-numpy?

As written above, Cython is the one where I ran into this issue.

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

Bug#873918: charmtimetracker: Missing binary dependency on libqt5sql5-sqlite

[Chris Lamb]

Package: charmtimetracker
Version: 1.11.4-1
Severity: grave
Tags: patch
Justification: Renders package unusable

Hi,

charmtimetracker appears to be missing a binary dependency on
libqt5sql5-sqlite. Installing libqt5sql5-sqlite manually moves
past this.

  $ charmtimetracker
  QSqlDatabase: QSQLITE driver not loaded
  QSqlDatabase: available drivers: 

Screenshot of UI error:

  https://i.imgur.com/1RLOZ4L.jpg


Patch attached.



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

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

Versions of packages charmtimetracker depends on:
ii  libc62.24-17
ii  libgcc1  1:7.2.0-1
ii  libqt5core5a 5.9.1+dfsg-9
ii  libqt5dbus5  5.9.1+dfsg-9
ii  libqt5gui5   5.9.1+dfsg-9
ii  libqt5keychain1  0.7.0-3
ii  libqt5network5   5.9.1+dfsg-9
ii  libqt5printsupport5  5.9.1+dfsg-9
ii  libqt5script55.9.1+dfsg-2
ii  libqt5sql5   5.9.1+dfsg-9
ii  libqt5widgets5   5.9.1+dfsg-9
ii  libqt5xml5   5.9.1+dfsg-9
ii  libstdc++6   7.2.0-1
ii  libxcb-screensaver0  1.12-1
ii  libxcb1  1.12-1

charmtimetracker recommends no packages.

charmtimetracker suggests no packages.

-- no debconf information


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
diff --git a/debian/control b/debian/control
index 32ff76f..ebdba87 100644
--- a/debian/control
+++ b/debian/control
@@ -20,7 +20,7 @@ Vcs-Browser: 
https://anonscm.debian.org/cgit/pkg-kde/kde-extras/charmtimetracker
 
 Package: charmtimetracker
 Architecture: any
-Depends: ${misc:Depends}, ${shlibs:Depends}
+Depends: ${misc:Depends}, ${shlibs:Depends}, libqt5sql5-sqlite
 Description: Cross-Platform Time Tracker
  It is built around two major ideas - tasks and events.
  Tasks are the things time is spend on, repeatedly. Tasks

Bug#873508: sparse test failures on ppc32le (and other not so common archs)

[Uwe Kleine-König]

On Fri, Sep 01, 2017 at 12:02:12AM -0700, Josh Triplett wrote:
> On Thu, Aug 31, 2017 at 08:47:55PM -0400, Christopher Li wrote:
> > On Thu, Aug 31, 2017 at 4:55 PM, Uwe Kleine-König  Yes
> > that works. So to address the Debian bug I can do:
> > >
> > >  - move sparse to /usr/lib
> > >  - teach cgcc about the move of sparse
> > >  - make /usr/bin/sparse call cgcc -no-compile "$@"
> > 
> > I don't like that. It means the user can't invoke sparse directly.
> > 
> > >
> > > or is it easier to teach sparse about the architecture stuff?
> > 
> > First of all. It is not very trivial to teach sparse about the architecture
> > stuff. To my mind, we need to move all the cgcc logic into sparse.
> 
> Related to that: while it would mean we couldn't necessarily just rely
> entirely on GCC's definitions for a target platform, I think in an ideal
> world we could have a sparse binary that understood *all* target
> platforms at once, such that you could ask Sparse on x86_64 to "compile"
> as though targeting any arbitrary architecture. That would also have the
> major advantage of making it easy to run the Sparse testsuite for
> *every* target architecture without needing compilers for every such
> architecture.

You'd need the target arch's system headers though. But still it would
be great. In a first attempt something like:

#ifdef __powerpc__
add_pre_buffer("#weak_define __powerpc__ " __powerpc__ "\n");
#ifdef _CALL_ELF
add_pre_buffer("#weak_define _CALL_ELF " _CALL_ELF "\n");
#endif
#endif

would be helpful already.

Best regards
Uwe


signature.asc
Description: PGP signature

Bug#873915: python2.7: fpectl removal breaks cython

[Matthias Klose]

Control: severity -1 important

On 01.09.2017 09:32, Ole Streicher wrote:
> Package: python2.7
> Version: 2.7.14~rc1-2
> Severity: serious
> Affects: cython
> 
> Like #873791, Cython is also affected. This causes an FTBFS for
> python-numpy:
> 
> https://buildd.debian.org/status/logs.php?pkg=python-numpy&ver=1%3A1.12.1-3.1
> 
> The same problem probably happens with  python3.6 3.6.2-3.

yes, please check the archive for uploads before you file issues.

Processed: Re: Bug#873915: python2.7: fpectl removal breaks cython

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #873915 [python2.7] python2.7: fpectl removal breaks cython
Severity set to 'important' from 'serious'

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

Bug#873508: sparse test failures on ppc32le (and other not so common archs)

[Uwe Kleine-König]

Hello,

On Thu, Aug 31, 2017 at 11:43:53PM +0100, Ramsay Jones wrote:
> On 31/08/17 21:55, Uwe Kleine-König wrote:
> > On Wed, Aug 30, 2017 at 08:11:49PM -0400, Christopher Li wrote:
> >> That is very much like on x86_64 missing define "#weak_define __x86_64__ 1"
> >>
> >> Does cgcc work for you? In the future we do want to move the archetecture
> >> related define from cgcc into sparse by itself. For now you can set
> >> "sparse" as "cgcc -no-compile"
> > 
> > Yes that works. So to address the Debian bug I can do:
> > 
> >  - move sparse to /usr/lib
> >  - teach cgcc about the move of sparse
> >  - make /usr/bin/sparse call cgcc -no-compile "$@"
> 
> Hmm, I don't think that would be a good idea ...
> 
> > or is it easier to teach sparse about the architecture stuff?
> 
> I now understand (I think!) that you are building a sparse
> package (presumably a .deb) and you are concerned that sparse
> does not pass it's own testsuite on those platforms.

Nearly right. I'm responsible for the sparse Debian package and the
problem at hand is https://bugs.debian.org/873508. This bug report has
"Severity: serious" wihch might eventually result in the removal of
sparse from the Debian archive.

@anarcat: Given that cgcc seems to work, would you agree to apply the
following patch to horst:

diff --git a/Makefile b/Makefile
index 4f924fa..d563652 100644
--- a/Makefile
+++ b/Makefile
@@ -110,7 +110,7 @@ $(NAME): $(OBJS)
 $(OBJS): .buildflags
 
 check:
-   sparse $(CFLAGS) *.[ch]
+   cgcc -no-compile $(CFLAGS) *.[ch]
 
 clean:
-rm -f *.o radiotap/*.o *~

and downgrade the bug to "important"? That would be a compromise that
buys us a bit of time.
 
> As I said before, the additional failures you are seeing are
> in the 'llvm backend' code (which, as far as I know, only passes
> on x86_64 Linux), and in my opinion the llvm-backend programs should
> not be installed. (The Makefile will build them automatically if
> you have llvm installed, likewise for c2xml/libxml and test-inspect/gtk).

Currently the sparse package contains /usr/include/sparse/, c2xml, cgcc,
sparse, sparse-llvm, sparsec and a separate package sparse-test-inspect
includes test-inspect. (That's how I inherited the package some time
ago.)
 
> [I would like to see build variable(s) to allow the user to suppress
> the build (or installation) of the other 'non-primary' sparse programs.]
> 
> Anyway, if you were to un-install llvm, sparse-llvm etc., would not
> be built, and the tests would not be run ... ;-)
> 
> Christopher, as the project maintainer, has the joy of making these
> kinds of decisions! :-D

This only solves a part of the problem because the bug report is about
sparse itself, not it's llvm part.

Best regards
Uwe


signature.asc
Description: PGP signature

Bug#853568: [Debian-med-packaging] Bug#853568: No idea how to fix abs arguments in nanopolish

[Gert Wollny]

Am Donnerstag, den 31.08.2017, 21:00 -0700 schrieb Walter Landry:
> Andreas Tille  wrote:
> > Hi,
> > 
> > to fix bug #853568 I tried a patch (gcc-7.patch) to fix abs()
> > arguments
> > in nanopolish[1] but I have no idea how to deal with this:
> > 
> > ...
> > g++ -o src/hmm/nanopolish_pore_model_set.o -c -g -O2 -fdebug-
> > prefix-map=/build/nanopolish-0.5.0=. -fstack-protector-strong
> > -Wformat -Werror=format-security -g -O3 -std=c++11 -fopenmp -Wdate-
> > t
> > src/common/nanopolish_variant.cpp: In function
> > 'std::vector extract_variants(const string&, const
> > string&)':
> > src/common/nanopolish_variant.cpp:32:69: error: call of overloaded
> > 'abs(std::__cxx11::basic_string::size_type)' is ambiguous
> >  size_t difference = std::abs(reference.size() -
> > haplotype.size());
> 
> The result of subtracting two size_t's is still a size_t, which is
> unsigned.  So you need to cast it to a signed type.  The correct type
> is ptrdiff_t.
> 
>   http://en.cppreference.com/w/cpp/types/ptrdiff_t
> 
> The line then becomes
> 
>   size_t difference =
> std::abs(static_cast(reference.size() -
> haplotype.size()));

Casting the difference may result in undefined behavior. Consider the
case 

   reference.size() == 1
   haplotype.size() == 2 

then 

   reference.size() - haplotype.size() 

will be 0x (on 32 bit), and how this is casted to a signed type
is implementation dependent (i.e. it is not guaranteed that this simply
wraps to -1, it may also raise a trap because of integer overflow). 

It would be better to avoid the cast altogether by doing something like

   size_t difference = reference.size() > haplotype.size() ? 
   reference.size() - haplotype.size() : 
   haplotype.size() - reference.size(); 


or cast both values before doing the subtraction.

Best, 
Gert 

Bug#873915: python2.7: fpectl removal breaks cython

[Ole Streicher]

Package: python2.7
Version: 2.7.14~rc1-2
Severity: serious
Affects: cython

Like #873791, Cython is also affected. This causes an FTBFS for
python-numpy:

https://buildd.debian.org/status/logs.php?pkg=python-numpy&ver=1%3A1.12.1-3.1

The same problem probably happens with  python3.6 3.6.2-3.

Best

Ole

Processed: tagging 853495

[Debian Bug Tracking System]

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

> tags 853495 + pending
Bug #853495 [src:libktorrent] libktorrent: ftbfs with GCC-7
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#873508: sparse test failures on ppc32le (and other not so common archs)

[Josh Triplett]

On Thu, Aug 31, 2017 at 08:47:55PM -0400, Christopher Li wrote:
> On Thu, Aug 31, 2017 at 4:55 PM, Uwe Kleine-König  Yes
> that works. So to address the Debian bug I can do:
> >
> >  - move sparse to /usr/lib
> >  - teach cgcc about the move of sparse
> >  - make /usr/bin/sparse call cgcc -no-compile "$@"
> 
> I don't like that. It means the user can't invoke sparse directly.
> 
> >
> > or is it easier to teach sparse about the architecture stuff?
> 
> First of all. It is not very trivial to teach sparse about the architecture
> stuff. To my mind, we need to move all the cgcc logic into sparse.

Related to that: while it would mean we couldn't necessarily just rely
entirely on GCC's definitions for a target platform, I think in an ideal
world we could have a sparse binary that understood *all* target
platforms at once, such that you could ask Sparse on x86_64 to "compile"
as though targeting any arbitrary architecture. That would also have the
major advantage of making it easy to run the Sparse testsuite for
*every* target architecture without needing compilers for every such
architecture.

Bug#873832:

[Arturo Borrero Gonzalez]

Control: tags -1 pending

Thanks, I did the change and is now pending:

https://anonscm.debian.org/cgit/pkg-suricata/pkg-suricata.git/commit/?id=93ee9030a53a45c800ad5879c4e7c754c1dc1331

Processed:

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #873832 [src:suricata] suricata: missing libluajit-5.1-dev build dependency 
on mipsel
Added tag(s) pending.

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