Bug#907026: cups-filters: filter failed on Ricoh MP 3554 SP after upgrading to 1.21.0-1

[Ben Caradoc-Davies]

Also affects Brother MFC-L2740DW with Generic PCL 6/PCL XL Printer 
Foomatic/pxlcolor from foomatic-db-compressed-ppds 20180604-1. Confirmed 
fixed by downgrading cups-browsed, cups-filters, 
cups-filters-core-drivers, libcupsfilters1, and libfontembed1 to 1.20.4-1.


Kind regards,

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

Bug#907370: TypeError: object of type 'int' has no len()

[Antoine Beaupre]

Package: python3-sh
Version: 1.11-1
Severity: grave

I found a regression in the python3-sh package. I have yet to find
exactly what is going on, but it looks to me like something changed in
Python 3.6 that broke the sh module in some way:

$ lwn get -o blog/2017-12-13-kubecon-overview.mdwn 
https://lwn.net/Articles/741301/
Exception in thread Thread-1:
Traceback (most recent call last):
  File "/usr/lib/python3.6/threading.py", line 916, in _bootstrap_inner
self.run()
  File "/usr/lib/python3.6/threading.py", line 864, in run
self._target(*self._args, **self._kwargs)
  File "/usr/lib/python3/dist-packages/sh.py", line 1453, in input_thread
done = stdin.write()
  File "/usr/lib/python3/dist-packages/sh.py", line 1799, in write
self.log.debug("got chunk size %d: %r", len(proc_chunk),
TypeError: object of type 'int' has no len()

The source for the `lwn` command is here:

https://gitlab.com/anarcat/lwn/blob/master/lwn.py

It's totally unclear to me, from the backtrace, from *where* exactly
sh is being called, so I am having a hard time writing a
reproducer... But I am *guessing* it's this call:

result = sh.pandoc(filter_args, _in=content)

But really, I have no frigging clue.

Any brilliant idea of what could possibly be going on here? This used
to work fine in Debian stretch (which has the same version of
python3-sh, so probably no change there).

My best guess so far is something changed in some standard library,
but I really have no idea...

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

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

Versions of packages python3-sh depends on:
ii  python3  3.6.5-3

python3-sh recommends no packages.

python3-sh suggests no packages.

-- debconf-show failed

Bug#906362: marked as done (gr-radar: FTBFS in buster/sid (build hangs))

[Debian Bug Tracking System]

Your message dated Mon, 27 Aug 2018 02:35:10 +
with message-id 
and subject line Bug#906362: fixed in gr-radar 0.0.0.20180308-1
has caused the Debian Bug report #906362,
regarding gr-radar: FTBFS in buster/sid (build hangs)
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.)


-- 
906362: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906362
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gr-radar
Version: 0.0.0.20161018-3
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_update_autotools_config -i
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure -- -DLIB_SUFFIX=/x86_64-linux-gnu 
-DCMAKE_BUILD_TYPE="RelWithDebInfo"
cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None 
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var 
-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON "-GUnix Makefiles" 
-DLIB_SUFFIX=/x86_64-linux-gnu -DCMAKE_BUILD_TYPE=RelWithDebInfo ..
-- The CXX compiler identification is GNU 8.2.0
-- The C compiler identification is GNU 8.2.0
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features

[... snipped ...]

/usr/bin/cmake -E cmake_progress_start 
/<>/obj-x86_64-linux-gnu/CMakeFiles 0
make[1]: Leaving directory '/<>/obj-x86_64-linux-gnu'
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
mkdir debian/test
mkdir debian/test/.gnuradio
if [ amd64 != hurd-i386 ]; then HOME=/<>/debian/test dh_auto_test 
-- CTEST_TEST_TIMEOUT=60 ; fi
cd obj-x86_64-linux-gnu && make -j1 test CTEST_TEST_TIMEOUT=60 
ARGS\+=-j1
make[2]: Entering directory '/<>/obj-x86_64-linux-gnu'
Running tests...
/usr/bin/ctest --force-new-ctest-process -j1
Test project /<>/obj-x86_64-linux-gnu
  Start  1: test_radar
 1/27 Test  #1: test_radar ..   Passed0.02 sec
  Start  2: qa_signal_generator_cw_c
 2/27 Test  #2: qa_signal_generator_cw_c    Passed0.27 sec
  Start  3: qa_signal_generator_fmcw_c
 3/27 Test  #3: qa_signal_generator_fmcw_c ..   Passed0.20 sec
  Start  4: qa_split_cc
 4/27 Test  #4: qa_split_cc .   Passed0.20 sec
  Start  5: qa_os_cfar_c
 5/27 Test  #5: qa_os_cfar_c    Passed1.24 sec
  Start  6: qa_ts_fft_cc
 6/27 Test  #6: qa_ts_fft_cc    Passed0.68 sec
  Start  7: qa_estimator_cw
 7/27 Test  #7: qa_estimator_cw .   Passed0.70 sec
  Start  8: qa_static_target_simulator_cc
 8/27 Test  #8: qa_static_target_simulator_cc ...   Passed0.34 sec
  Start  9: qa_signal_generator_fsk_c
 9/27 Test  #9: qa_signal_generator_fsk_c ...   Passed0.21 sec
  Start 10: qa_split_fsk_cc
10/27 Test #10: qa_split_fsk_cc .   Passed0.20 sec
  Start 11: qa_estimator_fsk
11/27 Test #11: qa_estimator_fsk    Passed0.71 sec
  Start 12: qa_usrp_echotimer_cc
12/27 Test #12: qa_usrp_echotimer_cc    Passed0.20 sec
  Start 13: qa_estimator_fmcw
13/27 Test #13: qa_estimator_fmcw ...***Failed0.22 sec
Traceback (most recent call last):
  File "/<>/python/qa_estimator_fmcw.py", line 27, in 
from matplotlib import pyplot as plt
ImportError: No module named matplotlib

  Start 14: qa_signal_generator_sync_pulse_c
14/27 Test #14: qa_signal_generator_sync_pulse_c    Passed0.20 sec
  Start 15: qa_estimator_sync_pulse_c
E: Build killed with signal TERM after 60 minutes of inactivity


The build was made with "dpkg-buildpackage -A" in my autobuilder.
Most probably, it also fails here in reproducible builds:

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

where you can get a full build log if you need it.

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

Thanks.
--- End Message ---
--- Begin Message ---
Source: gr-radar
Source-Version: 

Processed: tagging 906761, bug 906761 is forwarded to https://github.com/LibreCAD/LibreCAD/commit/6c392e9

[Debian Bug Tracking System]

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

> tags 906761 + fixed-upstream
Bug #906761 [src:librecad] librecad: FTBFS in buster/sid (invalid use of 
incomplete type 'class QActionGroup')
Added tag(s) fixed-upstream.
> forwarded 906761 https://github.com/LibreCAD/LibreCAD/commit/6c392e9
Bug #906761 [src:librecad] librecad: FTBFS in buster/sid (invalid use of 
incomplete type 'class QActionGroup')
Set Bug forwarded-to-address to 
'https://github.com/LibreCAD/LibreCAD/commit/6c392e9'.
> thanks
Stopping processing here.

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

Processed: bug 906651 is forwarded to https://github.com/KDE/cantor/commit/db8c792, tagging 906651

[Debian Bug Tracking System]

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

> forwarded 906651 https://github.com/KDE/cantor/commit/db8c792
Bug #906651 [src:cantor] cantor: FTBFS in buster/sid (invalid use of incomplete 
type 'class QStyle')
Set Bug forwarded-to-address to 'https://github.com/KDE/cantor/commit/db8c792'.
> tags 906651 + patch fixed-upstream
Bug #906651 [src:cantor] cantor: FTBFS in buster/sid (invalid use of incomplete 
type 'class QStyle')
Added tag(s) patch and fixed-upstream.
> thanks
Stopping processing here.

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

Processed: bug 906659 is forwarded to https://github.com/keepassxreboot/keepassxc/issues/2048, tagging 906659

[Debian Bug Tracking System]

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

> forwarded 906659 https://github.com/keepassxreboot/keepassxc/issues/2048
Bug #906659 [src:keepassxc] keepassxc: FTBFS in buster/sid (invalid use of 
incomplete type ‘class QButtonGroup’)
Set Bug forwarded-to-address to 
'https://github.com/keepassxreboot/keepassxc/issues/2048'.
> tags 906659 + patch
Bug #906659 [src:keepassxc] keepassxc: FTBFS in buster/sid (invalid use of 
incomplete type ‘class QButtonGroup’)
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#907362: fwbuilder-dbg is empty

[Adrian Bunk]

Package: fwbuilder-dbg
Version: 5.3.7-2
Severity: grave

Both fwbuilder-dbgsym (with proper contents)
and an empty fwbuilder-dbg exist:

$ dpkg -L fwbuilder-dbg
/.
/usr
/usr/share
/usr/share/doc
/usr/share/doc/fwbuilder-dbg
/usr/share/doc/fwbuilder-dbg/changelog.Debian.gz
/usr/share/doc/fwbuilder-dbg/changelog.gz
/usr/share/doc/fwbuilder-dbg/copyright
$


Please drop the empty fwbuilder-dbg.

Processed: Re: linpsk: FTBFS: invalid use of incomplete type 'class QButtonGroup'

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #906253 [src:linpsk] linpsk: FTBFS: invalid use of incomplete type 'class 
QButtonGroup'
Added tag(s) patch.

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

Bug#906253: linpsk: FTBFS: invalid use of incomplete type 'class QButtonGroup'

[Reiner Herrmann]

Control: tags -1 + patch

Hi,

the attached patch fixes the FTBFS by including the missing header for
the class QButtonGroup.

Regards,
  Reiner
diff -Nru linpsk-1.3.5/debian/patches/qt5.11.patch linpsk-1.3.5/debian/patches/qt5.11.patch
--- linpsk-1.3.5/debian/patches/qt5.11.patch	1970-01-01 01:00:00.0 +0100
+++ linpsk-1.3.5/debian/patches/qt5.11.patch	2018-08-27 01:20:29.0 +0200
@@ -0,0 +1,13 @@
+Author: Reiner Herrmann 
+Description: Include missing header for QButtonGroup
+
+--- a/gui/modemenu.cpp
 b/gui/modemenu.cpp
+@@ -23,6 +23,7 @@
+ #include "parameter.h"
+ #include "crxchannel.h"
+ 
++#include 
+ 
+ extern Parameter settings;
+ 
diff -Nru linpsk-1.3.5/debian/patches/series linpsk-1.3.5/debian/patches/series
--- linpsk-1.3.5/debian/patches/series	2017-07-18 18:24:41.0 +0200
+++ linpsk-1.3.5/debian/patches/series	2018-08-27 01:18:31.0 +0200
@@ -1,3 +1,4 @@
 we_have_hamlib.patch
 typo.patch
 ftbfs-clang.patch
+qt5.11.patch


signature.asc
Description: PGP signature

Bug#906492: marked as done (mosh: FTBFS in buster/sid ('%s' directive output may be truncated))

[Debian Bug Tracking System]

Your message dated Mon, 27 Aug 2018 00:53:53 +0200
with message-id <20180826225353.z7uayh7bfpbcl...@reiner-h.de>
and subject line Re: mosh: FTBFS in buster/sid ('%s' directive output may be 
truncated)
has caused the Debian Bug report #906492,
regarding mosh: FTBFS in buster/sid ('%s' directive output may be truncated)
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.)


-- 
906492: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906492
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:mosh
Version: 1.3.2-2
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-arch
dh build-arch --parallel --with autoreconf
   dh_update_autotools_config -a -O--parallel
   dh_autoreconf -a -O--parallel
configure.ac:21: installing './ar-lib'
configure.ac:13: installing './compile'
configure.ac:6: installing './install-sh'
configure.ac:6: installing './missing'
src/crypto/Makefile.am: installing './depcomp'
parallel-tests: installing './test-driver'
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure -- \
--disable-silent-rules \

[... snipped ...]

make[4]: Entering directory '/<>/src/statesync'
c++ -DHAVE_CONFIG_H -I. -I../..  -I./../util -I./../terminal -I../protobufs 
-pthread -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Werror -Wextra -pedantic 
-Wno-long-long -Weffc++ -Wmissing-declarations -fno-strict-overflow 
-D_FORTIFY_SOURCE=2 -fstack-protector-all -Wstack-protector --param 
ssp-buffer-size=1 -fPIE -fno-default-inline -pipe -g -O2 
-fdebug-prefix-map=/<>=. -Wformat -Werror=format-security -c -o 
completeterminal.o completeterminal.cc
c++ -DHAVE_CONFIG_H -I. -I../..  -I./../util -I./../terminal -I../protobufs 
-pthread -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Werror -Wextra -pedantic 
-Wno-long-long -Weffc++ -Wmissing-declarations -fno-strict-overflow 
-D_FORTIFY_SOURCE=2 -fstack-protector-all -Wstack-protector --param 
ssp-buffer-size=1 -fPIE -fno-default-inline -pipe -g -O2 
-fdebug-prefix-map=/<>=. -Wformat -Werror=format-security -c -o 
user.o user.cc
rm -f libmoshstatesync.a
ar cru libmoshstatesync.a completeterminal.o user.o 
ar: `u' modifier ignored since `D' is the default (see `U')
ranlib libmoshstatesync.a
make[4]: Leaving directory '/<>/src/statesync'
Making all in frontend
make[4]: Entering directory '/<>/src/frontend'
c++ -DHAVE_CONFIG_H -I. -I../..  -I./../statesync -I./../terminal 
-I./../network -I./../crypto -I../protobufs -I./../util -D_DEFAULT_SOURCE 
-D_XOPEN_SOURCE=600 -pthread  -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Werror 
-Wextra -pedantic -Wno-long-long -Weffc++ -Wmissing-declarations 
-fno-strict-overflow -D_FORTIFY_SOURCE=2 -fstack-protector-all 
-Wstack-protector --param ssp-buffer-size=1 -fPIE -fno-default-inline -pipe -g 
-O2 -fdebug-prefix-map=/<>=. -Wformat -Werror=format-security -c 
-o mosh-client.o mosh-client.cc
c++ -DHAVE_CONFIG_H -I. -I../..  -I./../statesync -I./../terminal 
-I./../network -I./../crypto -I../protobufs -I./../util -D_DEFAULT_SOURCE 
-D_XOPEN_SOURCE=600 -pthread  -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Werror 
-Wextra -pedantic -Wno-long-long -Weffc++ -Wmissing-declarations 
-fno-strict-overflow -D_FORTIFY_SOURCE=2 -fstack-protector-all 
-Wstack-protector --param ssp-buffer-size=1 -fPIE -fno-default-inline -pipe -g 
-O2 -fdebug-prefix-map=/<>=. -Wformat -Werror=format-security -c 
-o stmclient.o stmclient.cc
c++ -DHAVE_CONFIG_H -I. -I../..  -I./../statesync -I./../terminal 
-I./../network -I./../crypto -I../protobufs -I./../util -D_DEFAULT_SOURCE 
-D_XOPEN_SOURCE=600 -pthread  -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Werror 
-Wextra -pedantic -Wno-long-long -Weffc++ -Wmissing-declarations 
-fno-strict-overflow -D_FORTIFY_SOURCE=2 -fstack-protector-all 
-Wstack-protector --param ssp-buffer-size=1 -fPIE -fno-default-inline -pipe -g 
-O2 -fdebug-prefix-map=/<>=. -Wformat -Werror=format-security -c 
-o terminaloverlay.o terminaloverlay.cc
c++ -Wall -Werror -Wextra -pedantic -Wno-long-long -Weffc++ 
-Wmissing-declarations -fno-strict-overflow -D_FORTIFY_SOURCE=2 
-fstack-protector-all -Wstack-protector --param ssp-buffer-size=1 -fPIE 
-fno-default-inline -pipe -g -O2 -fdebug-prefix-map=/<>=. -Wformat 
-Werror=format-security -pie -Wl,-z,relro -Wl,-z,now -Wl,-z,relro -o 
mosh-client mosh-client.o stmclient.o terminaloverlay.o 
../crypto/libmoshcrypto.a ../network/libmoshnetwork.a 
../statesync/libmoshstatesync.a ../terminal/libmoshterminal.a 

Bug#906367: marked as done (jabref: FTBFS in buster/sid)

[Debian Bug Tracking System]

Your message dated Sun, 26 Aug 2018 22:20:24 +
with message-id 
and subject line Bug#906367: fixed in jabref 3.8.2+ds-7
has caused the Debian Bug report #906367,
regarding jabref: FTBFS in buster/sid
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.)


-- 
906367: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906367
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:jabref
Version: 3.8.2+ds-6
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep --buildsystem=gradle
   dh_update_autotools_config -i -O--buildsystem=gradle
   dh_autoreconf -i -O--buildsystem=gradle
   dh_auto_configure -i -O--buildsystem=gradle
   dh_auto_build -i -O--buildsystem=gradle
mkdir -p .gradle/init.d
cp /usr/share/gradle-debian-helper/init.gradle .gradle/init.d/
gradle --info --console plain --offline --stacktrace --no-daemon 
--refresh-dependencies --gradle-user-home .gradle -Duser.home=. 
-Duser.name=debian -Ddebian.package=jabref -Dfile.encoding=UTF-8 jar
Initialized native services in: /<>/jabref-3.8.2+ds/.gradle/native
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.gradle.internal.reflect.JavaMethod 
(file:/usr/share/gradle/lib/gradle-base-services-3.4.1.jar) to method 
java.lang.ClassLoader.getPackages()
WARNING: Please consider reporting this to the maintainers of 
org.gradle.internal.reflect.JavaMethod
WARNING: Use --illegal-access=warn to enable warnings of further illegal 
reflective access operations

[... snipped ...]

Searched in the following locations:

file:/usr/share/maven-repo/org/glassfish/javax.json/debian/javax.json-debian.pom

file:/usr/share/maven-repo/org/glassfish/javax.json/debian/javax.json-debian.jar
Required by:
project : > org.antlr:antlr4:debian
at 
org.gradle.internal.resolve.result.DefaultBuildableComponentResolveResult.notFound(DefaultBuildableComponentResolveResult.java:38)
at 
org.gradle.api.internal.artifacts.ivyservice.ivyresolve.RepositoryChainComponentMetaDataResolver.resolveModule(RepositoryChainComponentMetaDataResolver.java:88)
at 
org.gradle.api.internal.artifacts.ivyservice.ivyresolve.RepositoryChainComponentMetaDataResolver.resolve(RepositoryChainComponentMetaDataResolver.java:59)
at 
org.gradle.api.internal.artifacts.ivyservice.resolveengine.ComponentResolversChain$ComponentMetaDataResolverChain.resolve(ComponentResolversChain.java:85)
at 
org.gradle.api.internal.artifacts.ivyservice.clientmodule.ClientModuleResolver.resolve(ClientModuleResolver.java:45)
at 
org.gradle.api.internal.artifacts.ivyservice.resolveengine.graph.DependencyGraphBuilder$ModuleVersionResolveState.resolve(DependencyGraphBuilder.java:642)
at 
org.gradle.api.internal.artifacts.ivyservice.resolveengine.graph.DependencyGraphBuilder$ModuleVersionResolveState.getMetaData(DependencyGraphBuilder.java:653)
at 
org.gradle.api.internal.artifacts.ivyservice.resolveengine.graph.DependencyGraphBuilder$DependencyEdge.calculateTargetConfigurations(DependencyGraphBuilder.java:291)
at 
org.gradle.api.internal.artifacts.ivyservice.resolveengine.graph.DependencyGraphBuilder$DependencyEdge.attachToTargetConfigurations(DependencyGraphBuilder.java:264)
at 
org.gradle.api.internal.artifacts.ivyservice.resolveengine.graph.DependencyGraphBuilder.traverseGraph(DependencyGraphBuilder.java:161)
at 
org.gradle.api.internal.artifacts.ivyservice.resolveengine.graph.DependencyGraphBuilder.resolve(DependencyGraphBuilder.java:98)
at 
org.gradle.api.internal.artifacts.ivyservice.resolveengine.DefaultArtifactDependencyResolver.resolve(DefaultArtifactDependencyResolver.java:88)
at 
org.gradle.api.internal.artifacts.ivyservice.CacheLockingArtifactDependencyResolver$1.run(CacheLockingArtifactDependencyResolver.java:43)
at org.gradle.internal.Factories$1.create(Factories.java:25)
at 
org.gradle.cache.internal.DefaultCacheAccess.useCache(DefaultCacheAccess.java:190)
at 
org.gradle.cache.internal.DefaultCacheAccess.useCache(DefaultCacheAccess.java:172)
at 
org.gradle.cache.internal.DefaultPersistentDirectoryStore.useCache(DefaultPersistentDirectoryStore.java:136)
at 
org.gradle.cache.internal.DefaultCacheFactory$ReferenceTrackingCache.useCache(DefaultCacheFactory.java:199)
at 

Bug#906385: marked as done (ms-gsl: FTBFS in buster/sid (error: catching polymorphic type 'struct gsl::fail_fast' by value))

[Debian Bug Tracking System]

Your message dated Sun, 26 Aug 2018 22:20:36 +
with message-id 
and subject line Bug#906385: fixed in ms-gsl 1.0.0-2
has caused the Debian Bug report #906385,
regarding ms-gsl: FTBFS in buster/sid (error: catching polymorphic type 'struct 
gsl::fail_fast' by value)
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.)


-- 
906385: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906385
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ms-gsl
Version: 1.0.0-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules binary-indep
dh binary-indep
   dh_update_autotools_config -i
   dh_autoreconf -i
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure -- -DCMAKE_DISABLE_FIND_PACKAGE_Git=ON
cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None 
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var 
-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
"-GUnix Makefiles" -DCMAKE_DISABLE_FIND_PACKAGE_Git=ON ..
-- The CXX compiler identification is GNU 8.2.0
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features

[... snipped ...]

^
/<>/tests/multi_span_tests.cpp:1108:32: error: catching 
polymorphic type 'struct gsl::fail_fast' by value [-Werror=catch-value=]
 CHECK_THROWS_AS(av[0][-1], fail_fast);
^
/<>/tests/multi_span_tests.cpp:1109:36: error: catching 
polymorphic type 'struct gsl::fail_fast' by value [-Werror=catch-value=]
 CHECK_THROWS_AS((av[{0, -1}]), fail_fast);
^
/<>/tests/multi_span_tests.cpp: In function 'void 
C_A_T_C_HT_E_S_T52()':
/<>/tests/multi_span_tests.cpp:1247:38: error: catching 
polymorphic type 'struct gsl::fail_fast' by value [-Werror=catch-value=]
 CHECK_THROWS_AS(empty_av[0], fail_fast);
  ^
/<>/tests/multi_span_tests.cpp:1248:46: error: catching 
polymorphic type 'struct gsl::fail_fast' by value [-Werror=catch-value=]
 CHECK_THROWS_AS(empty_av.begin()[0], fail_fast);
  ^
/<>/tests/multi_span_tests.cpp:1249:47: error: catching 
polymorphic type 'struct gsl::fail_fast' by value [-Werror=catch-value=]
 CHECK_THROWS_AS(empty_av.cbegin()[0], fail_fast);
   ^
/<>/tests/multi_span_tests.cpp:1259:38: error: catching 
polymorphic type 'struct gsl::fail_fast' by value [-Werror=catch-value=]
 CHECK_THROWS_AS(empty_av[0], fail_fast);
  ^
/<>/tests/multi_span_tests.cpp:1260:46: error: catching 
polymorphic type 'struct gsl::fail_fast' by value [-Werror=catch-value=]
 CHECK_THROWS_AS(empty_av.begin()[0], fail_fast);
  ^
/<>/tests/multi_span_tests.cpp:1261:47: error: catching 
polymorphic type 'struct gsl::fail_fast' by value [-Werror=catch-value=]
 CHECK_THROWS_AS(empty_av.cbegin()[0], fail_fast);
   ^
/<>/tests/multi_span_tests.cpp: In function 'void 
C_A_T_C_HT_E_S_T64()':
/<>/tests/multi_span_tests.cpp:1546:36: error: catching 
polymorphic type 'struct gsl::fail_fast' by value [-Werror=catch-value=]
 CHECK_THROWS_AS(av1[10][3][4], fail_fast);
^
/<>/tests/multi_span_tests.cpp: In function 'void 
C_A_T_C_HT_E_S_T66()':
/<>/tests/multi_span_tests.cpp:1637:30: error: catching 
polymorphic type 'struct gsl::fail_fast' by value [-Werror=catch-value=]
 CHECK_THROWS_AS(f(), fail_fast);
  ^
/<>/tests/multi_span_tests.cpp:1646:26: error: catching 
polymorphic type 'struct gsl::fail_fast' by value [-Werror=catch-value=]
 CHECK_THROWS_AS(f(), fail_fast);
  ^
cc1plus: all warnings being treated as errors
make[3]: *** [tests/CMakeFiles/multi_span_tests.dir/build.make:66: 
tests/CMakeFiles/multi_span_tests.dir/multi_span_tests.cpp.o] Error 1
make[3]: Leaving 

Bug#907358: ncbi-vdb: fix broken library on i386

[Steve Langasek]

Package: ncbi-vdb
Version: 2.9.1-1+dfsg-1
Severity: grave
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu cosmic ubuntu-patch

Dear Andreas,

The libncbi-vdb2 library is broken on i386, because while it has managed to
build, it has unresolvable references:

$ ldd -d -r /usr/lib/i386-linux-gnu/libncbi-vdb.so.2
linux-gate.so.1 (0xf7f0d000)
libmbedx509.so.0 => /usr/lib/i386-linux-gnu/libmbedx509.so.0 
(0xf7a33000)
libmbedtls.so.10 => /usr/lib/i386-linux-gnu/libmbedtls.so.10 
(0xf7a03000)
libmbedcrypto.so.1 => /usr/lib/i386-linux-gnu/libmbedcrypto.so.1 
(0xf7999000)
libz.so.1 => /lib/i386-linux-gnu/libz.so.1 (0xf797a000)
libbz2.so.1.0 => /lib/i386-linux-gnu/libbz2.so.1.0 (0xf7968000)
libdl.so.2 => /lib/i386-linux-gnu/libdl.so.2 (0xf7963000)
libpthread.so.0 => /lib/i386-linux-gnu/libpthread.so.0 (0xf7944000)
libxml2.so.2 => /usr/lib/i386-linux-gnu/libxml2.so.2 (0xf7757000)
libm.so.6 => /lib/i386-linux-gnu/libm.so.6 (0xf7655000)
libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xf7479000)
/lib/ld-linux.so.2 (0xf7f0f000)
libicuuc.so.60 => /usr/lib/i386-linux-gnu/libicuuc.so.60 (0xf72b8000)
liblzma.so.5 => /lib/i386-linux-gnu/liblzma.so.5 (0xf728c000)
libicudata.so.60 => /usr/lib/i386-linux-gnu/libicudata.so.60 
(0xf58e2000)
libstdc++.so.6 => /usr/lib/i386-linux-gnu/libstdc++.so.6 (0xf575b000)
libgcc_s.so.1 => /lib/i386-linux-gnu/libgcc_s.so.1 (0xf573d000)
undefined symbol: uint64_msbit  (/usr/lib/i386-linux-gnu/libncbi-vdb.so.2)
$

This is because there is no implementation of uint64_msbit for the gcc/i386
target.

However, there doesn't appear to be anything about the gcc/x86_64
implementation which is 64-bit-specific, so attached is a patch that fixes
this bug by simply copying the x86_64 implementation to the i386 file.

This problem was discovered because it caused a build failure for sra-sdk on
i386 in Ubuntu when trying to link against the library at build time.  The
same build failure appears to exist in Debian.

It would also be perfectly reasonable to drop i386 as a supported
architecture for ncbi-vdb if you prefer; but I suggest you then make sure to
actually do this, rather than shipping a broken library package on i386.

Also, this broken library package would have been detectable at build time
if you were building with -Wl,-z,defs in LDFLAGS, as that would have
prevented ever generating a shared library with missing symbols.  That's a
good idea to do anyway, but in particular it would mean that if you didn't
want to support i386 anymore, you could just add this to build flags and not
have to worry about changing the architecture list explicitly.

Cheers,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru ncbi-vdb-2.9.1-1+dfsg/debian/patches/i386-uint64_msbit.patch 
ncbi-vdb-2.9.1-1+dfsg/debian/patches/i386-uint64_msbit.patch
--- ncbi-vdb-2.9.1-1+dfsg/debian/patches/i386-uint64_msbit.patch
1969-12-31 16:00:00.0 -0800
+++ ncbi-vdb-2.9.1-1+dfsg/debian/patches/i386-uint64_msbit.patch
2018-08-26 14:57:18.0 -0700
@@ -0,0 +1,25 @@
+Description: add missing implementation of uint64_msbit for i386
+ Without this definition, we get a "successful" library build with undefined
+ symbols on i386.  We can use the same implementation of this function as on
+ x86_64.
+Author: Steve Langasek 
+Last-Modified: 2018-08-26
+
+Index: ncbi-vdb-2.9.1-1+dfsg/interfaces/cc/gcc/i386/arch-impl.h
+===
+--- ncbi-vdb-2.9.1-1+dfsg.orig/interfaces/cc/gcc/i386/arch-impl.h
 ncbi-vdb-2.9.1-1+dfsg/interfaces/cc/gcc/i386/arch-impl.h
+@@ -127,6 +127,13 @@ int32_t uint32_msbit ( uint32_t self )
+ return rtn;
+ }
+ 
++static __inline__
++int32_t uint64_msbit ( uint64_t self )
++{
++if (self==0) return -1;
++return 63 - __builtin_clzll ( self );
++}
++
+ typedef struct int128_t int128_t;
+ struct int128_t
+ {
diff -Nru ncbi-vdb-2.9.1-1+dfsg/debian/patches/series 
ncbi-vdb-2.9.1-1+dfsg/debian/patches/series
--- ncbi-vdb-2.9.1-1+dfsg/debian/patches/series 2018-06-27 20:41:16.0 
-0700
+++ ncbi-vdb-2.9.1-1+dfsg/debian/patches/series 2018-08-26 14:58:11.0 
-0700
@@ -9,3 +9,4 @@
 add_-msse2.patch
 use_debian_packaged_libmbedx.patch
 mbedtls_ssl_init.patch
+i386-uint64_msbit.patch

Bug#907359: minify-maven-plugin: FTBFS in buster/sid (Could not resolve dependencies for project com.samaxes.maven:minify-maven-plugin:maven-plugin:1.7.4)

[Santiago Vila]

Package: src:minify-maven-plugin
Version: 1.7.4-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep --buildsystem=maven
   dh_update_autotools_config -i -O--buildsystem=maven
   dh_autoreconf -i -O--buildsystem=maven
   dh_auto_configure -i -O--buildsystem=maven
mh_patchpoms -plibminify-maven-plugin-java --debian-build 
--keep-pom-version --maven-repo=/<>/debian/maven-repo
   dh_auto_build -i -O--buildsystem=maven
/usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.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 --batch-mode package 
-DskipTests -Dnotimestamp=true -Dlocale=en_US
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by 
com.google.inject.internal.cglib.core.$ReflectUtils$1 
(file:/usr/share/maven/lib/guice.jar) to method 
java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain)
WARNING: Please consider reporting this to the maintainers of 
com.google.inject.internal.cglib.core.$ReflectUtils$1
WARNING: Use --illegal-access=warn to enable warnings of further illegal 
reflective access operations
WARNING: All illegal access operations will be denied in a future release
[INFO] Scanning for projects...
[INFO] 
[INFO] ---< com.samaxes.maven:minify-maven-plugin >
[INFO] Building Minify Maven Plugin 1.7.4
[INFO] [ maven-plugin ]
[WARNING] The POM for org.json:json:jar:debian is missing, no dependency 
information available
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 0.469 s
[INFO] Finished at: 2018-08-26T12:24:35Z
[INFO] 
[ERROR] Failed to execute goal on project minify-maven-plugin: Could not 
resolve dependencies for project 
com.samaxes.maven:minify-maven-plugin:maven-plugin:1.7.4: Cannot access central 
(https://repo.maven.apache.org/maven2) in offline mode and the artifact 
org.json:json:jar:debian has not been downloaded from it before. -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
dh_auto_build: /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.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 --batch-mode package 
-DskipTests -Dnotimestamp=true -Dlocale=en_US returned exit code 1
make: *** [debian/rules:4: build-indep] Error 1
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


The build was made in my autobuilder with "dpkg-buildpackage -A"
but it also fails here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/minify-maven-plugin.html

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

Thanks.

Bug#859719: sslscan: Please migrate to openssl1.1 in Buster

[Marvin Stark]

Hi Sebastian,

I'll orphan the package and I think it should be removed.

See bug=905862.

Feel free to adopt the package :)


On 06/14/2018 11:36 PM, Sebastian Andrzej Siewior wrote:
> Marvin, do you have any plans here? Upstream made it clear that they
> won't support openssl 1.1.0+ and I doubt that an embedded copy of the
> ssl library will work here (not saying it won't, it is not my
> decision).
>
> Sebastian
>

-- 
 .""`. Marvin Stark 
: :"  :Homepage: www.der-marv.de
`. `"`
  `-  Debian - when you have better things to do than fix a system 




signature.asc
Description: OpenPGP digital signature

Bug#899792: marked as done (libpyzy: Invalid maintainer address pkg-ime-de...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Sun, 26 Aug 2018 21:21:13 +
with message-id 
and subject line Bug#899792: fixed in libpyzy 1.0.1-6
has caused the Debian Bug report #899792,
regarding libpyzy: Invalid maintainer address 
pkg-ime-de...@lists.alioth.debian.org
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.)


-- 
899792: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899792
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libpyzy
Version: 1.0.1-5
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of libpyzy,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package libpyzy since the list address
pkg-ime-de...@lists.alioth.debian.org used in the Maintainer: field was
not transferred to the alioth-lists service that provides a
continuation for the lists in the @lists.alioth.debian.org domain.

Addresses that were not migrated have been disabled some time  ago. As
a result your package is now in violation of a "must" in the Debian
policy (3.3, working email address), making it unfit for release.

Please fix this before long. Among other reasons, keep in mind bug
reports and important notifications about your package might not reach
you.

Your options:

* Upload another version with a new maintainer address of your choice,

* Migrate the list to the new system. This is still possible,
  please appoint a Debian developer as a list owner first, then
  contact the alioth lists migration team 
  and provide all the necessary information.

  More information about the new service can be found here:
  

* More options, even if imperfect, can be found at
  


The first option is probably suitable only if the address was used just
in a small number of packages since this requires an upload for each of
them. To our knowledge, the usage count of
pkg-ime-de...@lists.alioth.debian.org is 68.

The second option is available for a limited time only, by end of
May 2018 the most. So if you're interested in going this way, start the
process as soon as possible.

Note, as mails to the maintainer address will not get through, this
bugreport is Cc'ed (X-Debbugs-CC:) to all uploaders of the package.

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: libpyzy
Source-Version: 1.0.1-6

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

Debian distribution maintenance software
pp.
Boyuan Yang <073p...@gmail.com> (supplier of updated libpyzy package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 26 Aug 2018 16:47:11 -0400
Source: libpyzy
Binary: libpyzy-1.0-0v5 libpyzy-dev
Architecture: source
Version: 1.0.1-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Input Method Team 
Changed-By: Boyuan Yang <073p...@gmail.com>
Description:
 libpyzy-1.0-0v5 - Chinese PinYin and Bopomofo conversion library
 libpyzy-dev - Development files of libpyzy
Closes: 899792
Changes:
 libpyzy (1.0.1-6) unstable; urgency=medium
 .
   * Team upload.
   * Apply "wrap-and-sort -abst".
   * debian/control:
 + Use debian-input-method mailing list in Maintainer field (Closes: 
#899792)
 + Update YunQiang Su's email address and use the @debian.org one.
 + Bump debhelper compat to v11.
 + Standards-Version to 4.2.1.
 + Remove unnesessary build-dependency dh-autoreconf.
 + Use git repo on Salsa platform for Vcs fields.
   * debian/rules: Modernize rules file and get rid of dpkg-parsechangelog
 invocation.
   * debian/copyright: Use secure uri.
Checksums-Sha1:
 8b73920f12e0100e45a20ae1eb062deacf4a1d09 2359 libpyzy_1.0.1-6.dsc
 20d048f4f42df1c6028c90bd07d39933729b25d0 4820 libpyzy_1.0.1-6.debian.tar.xz
 661ffeea7c6094874b91cc08e9c2e05e5dcd3a44 7235 libpyzy_1.0.1-6_amd64.buildinfo
Checksums-Sha256:
 

Bug#906556: marked as done (python-admesh: FTBFS in buster/sid)

[Debian Bug Tracking System]

Your message dated Sun, 26 Aug 2018 21:05:36 +
with message-id 
and subject line Bug#906556: fixed in python-admesh 0.98.9-1
has caused the Debian Bug report #906556,
regarding python-admesh: FTBFS in buster/sid
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.)


-- 
906556: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906556
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-admesh
Version: 0.98.8-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-arch
dh build-arch --with python2,python3 --buildsystem=pybuild
   dh_update_autotools_config -a -O--buildsystem=pybuild
   dh_autoreconf -a -O--buildsystem=pybuild
   dh_auto_configure -a -O--buildsystem=pybuild
I: pybuild base:217: python2.7 setup.py config 
running config
I: pybuild base:217: python3.6 setup.py config 
running config
   dh_auto_build -a -O--buildsystem=pybuild
I: pybuild base:217: /usr/bin/python setup.py build 
running build
running build_ext
generating cadmesh.pxd and admesh.pyx

[... snipped ...]

  File "/usr/lib/python2.7/dist-packages/Cython/Distutils/old_build_ext.py", 
line 193, in build_extensions
ext.sources = self.cython_sources(ext.sources, ext)
  File "/usr/lib/python2.7/dist-packages/Cython/Distutils/old_build_ext.py", 
line 346, in cython_sources
full_module_name=module_name)
  File "/usr/lib/python2.7/dist-packages/Cython/Compiler/Main.py", line 700, in 
compile
return compile_single(source, options, full_module_name)
  File "/usr/lib/python2.7/dist-packages/Cython/Compiler/Main.py", line 649, in 
compile_single
return run_pipeline(source, options, full_module_name)
  File "/usr/lib/python2.7/dist-packages/Cython/Compiler/Main.py", line 499, in 
run_pipeline
err, enddata = Pipeline.run_pipeline(pipeline, source)
  File "/usr/lib/python2.7/dist-packages/Cython/Compiler/Pipeline.py", line 
354, in run_pipeline
data = run(phase, data)
  File "/usr/lib/python2.7/dist-packages/Cython/Compiler/Pipeline.py", line 
334, in run
return phase(data)
  File "/usr/lib/python2.7/dist-packages/Cython/Compiler/Pipeline.py", line 52, 
in generate_pyx_code_stage
module_node.process_implementation(options, result)
  File "/usr/lib/python2.7/dist-packages/Cython/Compiler/ModuleNode.py", line 
142, in process_implementation
self.generate_c_code(env, options, result)
  File "/usr/lib/python2.7/dist-packages/Cython/Compiler/ModuleNode.py", line 
378, in generate_c_code
self.body.generate_function_definitions(env, code)
  File "/usr/lib/python2.7/dist-packages/Cython/Compiler/Nodes.py", line 438, 
in generate_function_definitions
stat.generate_function_definitions(env, code)
  File "/usr/lib/python2.7/dist-packages/Cython/Compiler/Nodes.py", line 9244, 
in generate_function_definitions
self.node.generate_function_definitions(env, code)
  File "/usr/lib/python2.7/dist-packages/Cython/Compiler/Nodes.py", line 1976, 
in generate_function_definitions
self.generate_function_body(env, code)
  File "/usr/lib/python2.7/dist-packages/Cython/Compiler/Nodes.py", line 1738, 
in generate_function_body
self.body.generate_execution_code(code)
  File "/usr/lib/python2.7/dist-packages/Cython/Compiler/Nodes.py", line 444, 
in generate_execution_code
stat.generate_execution_code(code)
  File "/usr/lib/python2.7/dist-packages/Cython/Compiler/Nodes.py", line 5102, 
in generate_execution_code
self.generate_rhs_evaluation_code(code)
  File "/usr/lib/python2.7/dist-packages/Cython/Compiler/Nodes.py", line 5389, 
in generate_rhs_evaluation_code
self.rhs.generate_evaluation_code(code)
  File "/usr/lib/python2.7/dist-packages/Cython/Compiler/ExprNodes.py", line 
720, in generate_evaluation_code
self.generate_result_code(code)
  File "/usr/lib/python2.7/dist-packages/Cython/Compiler/ExprNodes.py", line 
13137, in generate_result_code
self.arg.py_result(), self.result(), self.pos, code, 
from_py_function=from_py_function))
  File "/usr/lib/python2.7/dist-packages/Cython/Compiler/PyrexTypes.py", line 
514, in from_py_call_code
error_condition or self.error_condition(result_code)
  File "/usr/lib/python2.7/dist-packages/Cython/Compiler/PyrexTypes.py", line 
2483, in from_py_call_code
assert not error_condition, '%s: %s' % (error_pos, error_condition)
AssertionError: (, 30, 19): 
(__pyx_t_12 == ((char *)NULL)) && PyErr_Occurred()
E: pybuild pybuild:338: build: plugin distutils failed with: exit 

Bug#898804: marked as done (myproxy: FTBFS against openssl 1.1.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Aug 2018 20:42:33 +
with message-id 
and subject line Bug#898804: fixed in myproxy 6.1.30-2
has caused the Debian Bug report #898804,
regarding myproxy: FTBFS against openssl 1.1.1
to be marked as done.

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

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


-- 
898804: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898804
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: myproxy
Version: 6.1.28-2
Severity: important
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: openssl-1.1.1

The new openssl 1.1.1 is currently in experimental [0]. This package
failed to build against this new package [1] while it built fine against
the openssl version currently in unstable [2].
Could you please have a look?

|The Error
|Problem with server credentials. GSS Major Status: General failure GSS Minor 
Status Error Chain: globus_gsi_gssapi: Error with GSI credential 
globus_gsi_gssapi: Error with gss credential handle globus_gsi_gssapi: Error 
with openssl: Couldn't set the certificate to be used for the SSL context 
OpenSSL Error: ../ssl/ssl_rsa.c:310: in library: SSL routines, function 
SSL_CTX_use_certificate: ca md too weak  
|FAIL myproxy-test-wrapper (exit status: 1)

is due to:
1.1.1~~pre6-1 changelog):
|   * Increase default security level from 1 to 2. This moves from the 80 bit
| security level to the 112 bit securit level and will require 2048 bit RSA
| and DHE keys.

[0] https://lists.debian.org/msgid-search/20180501211400.ga21...@roeckx.be
[1] 
https://breakpoint.cc/openssl-rebuild/2018-05-03-rebuild-openssl1.1.1-pre6/attempted/myproxy_6.1.28-2_amd64-2018-05-01T20%3A28%3A31Z
[2] 
https://breakpoint.cc/openssl-rebuild/2018-05-03-rebuild-openssl1.1.1-pre6/successful/myproxy_6.1.28-2_amd64-2018-05-02T18%3A46%3A02Z

Sebastian
--- End Message ---
--- Begin Message ---
Source: myproxy
Source-Version: 6.1.30-2

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

Debian distribution maintenance software
pp.
Mattias Ellert  (supplier of updated myproxy 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 26 Aug 2018 15:37:18 +0200
Source: myproxy
Binary: myproxy libmyproxy6 libmyproxy-voms libmyproxy-dev myproxy-server 
myproxy-admin libmyproxy-doc
Architecture: source amd64 all
Version: 6.1.30-2
Distribution: unstable
Urgency: medium
Maintainer: Mattias Ellert 
Changed-By: Mattias Ellert 
Description:
 libmyproxy-dev - Credential Management Service Development
 libmyproxy-doc - Credential Management Service Documentation
 libmyproxy-voms - Credential Management Service VOMS Library
 libmyproxy6 - Credential Management Service Library
 myproxy- Credential Management Service Client
 myproxy-admin - Credential Management Service Administration Tools
 myproxy-server - Credential Management Service Server
Closes: 898804
Changes:
 myproxy (6.1.30-2) unstable; urgency=medium
 .
   * Use 2048 bit CA key for myproxy tests (Closes: #898804)
Checksums-Sha1:
 816cd31db5bd120618a5d158dbb728b312cdd5b1 2659 myproxy_6.1.30-2.dsc
 1c4e7fb7299f344cad2bd7838dafa7630685c754  myproxy_6.1.30-2.debian.tar.xz
 2bec89768c473ebd176fe3cebc3b9b771845388c 16056 
libmyproxy-dev_6.1.30-2_amd64.deb
 35afec61b8d0c12d27a8cecfb1ac8dbf6070e46e 26524 libmyproxy-doc_6.1.30-2_all.deb
 19d07f6cf0cb7ff043090d1a169e6246cd7de4de 35716 
libmyproxy-voms-dbgsym_6.1.30-2_amd64.deb
 70fb9b39f14b546245cba099ad86a1e3b4433bf2 12892 
libmyproxy-voms_6.1.30-2_amd64.deb
 b2b2b6e3805f4862238d347e31cb3d0daf779f59 347076 
libmyproxy6-dbgsym_6.1.30-2_amd64.deb
 73b2db34a62c3e48c15acf88c2e14ca8dc20e8ef 96868 libmyproxy6_6.1.30-2_amd64.deb
 9827a23e86132e0a4e10e51b48ae99aedcc475d8 44100 
myproxy-admin-dbgsym_6.1.30-2_amd64.deb
 f42948cd359c784fe3d333986fe8f6f7cc2770aa 44248 myproxy-admin_6.1.30-2_amd64.deb
 88bfdd20a21f6a0bf2279542877688f8929c3180 124928 
myproxy-dbgsym_6.1.30-2_amd64.deb
 46414f6e1cd1229d0889304e00fd641d9cd64d81 53800 
myproxy-server-dbgsym_6.1.30-2_amd64.deb
 a6e5aebe805f207fab07602b79ed28868209616e 45796 

Processed: tagging 907332

[Debian Bug Tracking System]

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

> tags 907332 + upstream
Bug #907332 [ghostscript] ghostscript has a new code execution issue, even when 
used with -dSAFER
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Bug#907348: dateutils FTBFS on 32bit: test failures

[Adrian Bunk]

Source: dateutils
Version: 0.4.4-1
Severity: serious
Tags: ftbfs

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

...
FAIL: dtcore-conv
=

  VALUES DIFFER 1341100836 v 1341100833
  VALUES DIFFER 1341100837 v 1341100835
FAIL dtcore-conv (exit status: 1)

FAIL: dtconv.024


$ dconv '2012-03-01 00:00:00' -z TAI
--- "expected output  5b88a553" 2018-08-26 16:07:27.682809364 +
+++ "actual output  5b88a553"   2018-08-26 16:07:27.682809364 +
@@ -1 +1 @@
-2012-03-01T00:00:34
+2012-03-01T00:00:37
$? 1
FAIL dtconv.024.clit (exit status: 1)

FAIL: dtconv.026


$ dconv '2012-03-01 00:00:00' -z GPS
--- "expected output  5b881603" 2018-08-26 16:07:27.702809312 +
+++ "actual output  5b881603"   2018-08-26 16:07:27.702809312 +
@@ -1 +1 @@
-2012-03-01T00:00:15
+2012-03-01T00:00:18
$? 1
FAIL dtconv.026.clit (exit status: 1)

FAIL: dtconv.027


$ dconv '2012-03-01 00:00:00' --from-zone TAI
--- "expected output  5b8820a2" 2018-08-26 16:07:27.714809281 +
+++ "actual output  5b8820a2"   2018-08-26 16:07:27.714809281 +
@@ -1 +1 @@
-2012-02-29T23:59:26
+2012-02-29T23:59:23
$? 1
FAIL dtconv.027.clit (exit status: 1)

FAIL: dtconv.029


$ dconv '2012-03-01 00:00:00' --from-zone GPS
--- "expected output  5b899088" 2018-08-26 16:07:27.734809230 +
+++ "actual output  5b899088"   2018-08-26 16:07:27.734809230 +
@@ -1 +1 @@
-2012-02-29T23:59:45
+2012-02-29T23:59:42
$? 1
FAIL dtconv.029.clit (exit status: 1)

FAIL: dtconv.030


$ dconv '1970-01-01 00:00:00' -z TAI
--- "expected output  5b89b895" 2018-08-26 16:07:27.746809199 +
+++ "actual output  5b89b895"   2018-08-26 16:07:27.746809199 +
@@ -1 +1 @@
-1970-01-01T00:00:10
+1970-01-01T00:00:37
$? 1
FAIL dtconv.030.clit (exit status: 1)

FAIL: dtconv.031


$ dconv '1972-01-01 00:00:00' -z TAI
--- "expected output  5b89402a" 2018-08-26 16:07:27.754809178 +
+++ "actual output  5b89402a"   2018-08-26 16:07:27.754809178 +
@@ -1 +1 @@
-1972-01-01T00:00:10
+1972-01-01T00:00:37
$? 1
FAIL dtconv.031.clit (exit status: 1)

FAIL: dtconv.032


$ dconv '1972-01-01 00:00:01' -z TAI
--- "expected output  5b8967c5" 2018-08-26 16:07:27.766809147 +
+++ "actual output  5b8967c5"   2018-08-26 16:07:27.766809147 +
@@ -1 +1 @@
-1972-01-01T00:00:11
+1972-01-01T00:00:38
$? 1
FAIL dtconv.032.clit (exit status: 1)

FAIL: dtadd.030
===

$ dadd '2012-06-30 23:59:30' 30rs
--- "expected output  5b8a5636" 2018-08-26 16:07:35.554789033 +
+++ "actual output  5b8a5636"   2018-08-26 16:07:35.554789033 +
@@ -1 +1 @@
-2012-06-30T23:59:60
+2012-07-01T00:00:00
$? 1
FAIL dtadd.030.clit (exit status: 1)

FAIL: dtadd.031
===

$ dadd '2012-06-30 23:59:30' 31rs
--- "expected output  5b8a7e58" 2018-08-26 16:07:35.566789002 +
+++ "actual output  5b8a7e58"   2018-08-26 16:07:35.566789002 +
@@ -1 +1 @@
-2012-07-01T00:00:00
+2012-07-01T00:00:01
$? 1
FAIL dtadd.031.clit (exit status: 1)

FAIL: dtadd.034
===

$ dadd '2012-07-01 00:00:05' -6rs
--- "expected output  5b8bf7d2" 2018-08-26 16:07:35.598788920 +
+++ "actual output  5b8bf7d2"   2018-08-26 16:07:35.598788920 +
@@ -1 +1 @@
-2012-06-30T23:59:60
+2012-06-30T23:59:59
$? 1
FAIL dtadd.034.clit (exit status: 1)

FAIL: dtadd.035
===

$ dadd '2012-07-01 00:00:05' -7rs
--- "expected output  5b8b9fe9" 2018-08-26 16:07:35.606788899 +
+++ "actual output  5b8b9fe9"   2018-08-26 16:07:35.606788899 +
@@ -1 +1 @@
-2012-06-30T23:59:59
+2012-06-30T23:59:58
$? 1
FAIL dtadd.035.clit (exit status: 1)

FAIL: dtdiff.019


$ ddiff '2012-06-30 23:59:00' '2012-07-01 00:00:00' -f '%rSs'
--- "expected output  5b86f62a" 2018-08-26 16:07:36.270787184 +
+++ "actual output  5b86f62a"   2018-08-26 16:07:36.270787184 +
@@ -1 +1 @@
-61s
+60s
$? 1
FAIL dtdiff.019.clit (exit status: 1)

FAIL: dtdiff.021


$ ddiff '2012-06-30 23:59:00' '2012-07-01 00:00:00' -f '%rT'
--- "expected output  5b86a6e9" 2018-08-26 16:07:36.290787133 +
+++ "actual output  5b86a6e9"   2018-08-26 16:07:36.290787133 +
@@ -1 +1 @@
-61s
+60s
$? 1
FAIL dtdiff.021.clit (exit status: 1)


Testsuite summary for dateutils 0.4.4

# TOTAL: 853
# PASS:  839
# SKIP:  0
# XFAIL: 0
# FAIL:  14
# XPASS: 0
# ERROR: 0

See test/test-suite.log
Please report to https://github.com/hroptatyr/dateutils/issues

make[6]: *** [Makefile:1227: test-suite.log] Error 1

Processed: tagging 907332, found 907332 in 9.20~dfsg-1

[Debian Bug Tracking System]

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

> tags 907332 - stretch
Bug #907332 [ghostscript] ghostscript has a new code execution issue, even when 
used with -dSAFER
Removed tag(s) stretch.
> found 907332 9.20~dfsg-1
Bug #907332 [ghostscript] ghostscript has a new code execution issue, even when 
used with -dSAFER
Marked as found in versions ghostscript/9.20~dfsg-1.
> thanks
Stopping processing here.

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

Bug#907332: ghostscript has a new code execution issue, even when used with -dSAFER

[Salvatore Bonaccorso]

Hi,

On Sun, Aug 26, 2018 at 06:08:58PM +0100, Nicolas Braud-Santoni wrote:
> Tavis Ormandy disclosed a new ghoscript security issue, leading directly to 
> code
> execution:  http://openwall.com/lists/oss-security/2018/08/21/2

There are actually several issues, see the whole thread. For now since
you filled this bug will track all those with this bug entry. Proper
evaluation though is still pending (and Moritz is taking care of
strech, adding this note to dsa-needed file ("needs some research on
issues found by Tavis").

See

https://www.kb.cert.org/vuls/id/332928

the current set of fixes:

http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=b575e1ec
http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=8e9ce501
http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=241d9111
http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=c432131c
http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=e01e77a3
http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=0edd3d6c
http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=a054156d
http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=0d390118
http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=c3476dde
http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=b326a716
http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=78911a01
http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=5516c614

Regards,
Salvatore

Bug#898803: marked as done (globus-gssapi-gsi: FTBFS against openssl 1.1.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Aug 2018 19:50:13 +
with message-id 
and subject line Bug#898803: fixed in globus-gssapi-gsi 13.8-2
has caused the Debian Bug report #898803,
regarding globus-gssapi-gsi: FTBFS against openssl 1.1.1
to be marked as done.

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

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


-- 
898803: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898803
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: globus-gssapi-gsi
Version: 13.5-1
Severity: important
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: openssl-1.1.1

The new openssl 1.1.1 is currently in experimental [0]. This package
failed to build against this new package [1] while it built fine against
the openssl version currently in unstable [2].
Could you please have a look?

I suspect the failure due to a too small key in the testsuite
1.1.1~~pre6-1 changelog):
|   * Increase default security level from 1 to 2. This moves from the 80 bit
| security level to the 112 bit securit level and will require 2048 bit RSA
| and DHE keys.

[0] https://lists.debian.org/msgid-search/20180501211400.ga21...@roeckx.be
[1] 
https://breakpoint.cc/openssl-rebuild/2018-05-03-rebuild-openssl1.1.1-pre6/attempted/globus-gssapi-gsi_13.5-1_amd64-2018-05-01T20%3A05%3A40Z
[2] 
https://breakpoint.cc/openssl-rebuild/2018-05-03-rebuild-openssl1.1.1-pre6/successful/globus-gssapi-gsi_13.5-1_amd64-2018-05-02T18%3A43%3A41Z

Sebastian
--- End Message ---
--- Begin Message ---
Source: globus-gssapi-gsi
Source-Version: 13.8-2

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

Debian distribution maintenance software
pp.
Mattias Ellert  (supplier of updated 
globus-gssapi-gsi package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 26 Aug 2018 12:58:59 +0200
Source: globus-gssapi-gsi
Binary: libglobus-gssapi-gsi4 libglobus-gssapi-gsi-dev libglobus-gssapi-gsi-doc
Architecture: source amd64 all
Version: 13.8-2
Distribution: unstable
Urgency: medium
Maintainer: Mattias Ellert 
Changed-By: Mattias Ellert 
Description:
 libglobus-gssapi-gsi-dev - Globus Toolkit - GSSAPI library Development Files
 libglobus-gssapi-gsi-doc - Globus Toolkit - GSSAPI library Documentation Files
 libglobus-gssapi-gsi4 - Globus Toolkit - GSSAPI library
Closes: 898803
Changes:
 globus-gssapi-gsi (13.8-2) unstable; urgency=medium
 .
   * Use 2048 bit RSA key for tests (Closes: #898803)
   * Avoid TLS 1.3 - needs porting (Closes: #898803)
Checksums-Sha1:
 34b93c2946f2c34c3b77289a530b4be8f5882722 2452 globus-gssapi-gsi_13.8-2.dsc
 784d1b33999f7eee9667ae686832786831fc508d 6744 
globus-gssapi-gsi_13.8-2.debian.tar.xz
 ccd2ea454a16ecd67c12410b7f049f70dbb31efd 8829 
globus-gssapi-gsi_13.8-2_amd64.buildinfo
 b7bfab3b7feced56e09433dcd947cdac3ff22423 12164 
libglobus-gssapi-gsi-dev_13.8-2_amd64.deb
 587ce3e919909dd0418e197fb6c26145b9128f57 262112 
libglobus-gssapi-gsi-doc_13.8-2_all.deb
 511d76993c52782ac51b98a1b1587a5544306b74 250732 
libglobus-gssapi-gsi4-dbgsym_13.8-2_amd64.deb
 e6c9951b7a942b6c37bd7c0d57e0973874563cbe 57600 
libglobus-gssapi-gsi4_13.8-2_amd64.deb
Checksums-Sha256:
 cace549bfca6face29af82100f16915c926cb143f9b09a4998ec88adfb2a3265 2452 
globus-gssapi-gsi_13.8-2.dsc
 46ab68cd6a7f6b9aa64af4c33419e4a411b3291810a20a305a2655e1a5b6b2b5 6744 
globus-gssapi-gsi_13.8-2.debian.tar.xz
 723b2194e32afabcc5353f47aec84798ad6d61c6e4390830b7602b32d1acd360 8829 
globus-gssapi-gsi_13.8-2_amd64.buildinfo
 88370de81b14e9e89d19649cea6cd609202d8a6473e48bf3587def84ebaa640b 12164 
libglobus-gssapi-gsi-dev_13.8-2_amd64.deb
 fb3c66430ac1a70375f6e67371dcc38a692732b00bd0df8fa028bf9d43cace52 262112 
libglobus-gssapi-gsi-doc_13.8-2_all.deb
 183789c6412e89f67abf2902dfdc741536903cfc9ab67ea6287a0da62a8730a7 250732 
libglobus-gssapi-gsi4-dbgsym_13.8-2_amd64.deb
 0ce71120b854c7ebd0a55932ff66d7c008b229c671feffcca74434afd2fd03c2 57600 
libglobus-gssapi-gsi4_13.8-2_amd64.deb
Files:
 057a8d478ecbf1e8d50c3cd32df9a34c 2452 net optional globus-gssapi-gsi_13.8-2.dsc
 b830562cb0581ad7879f83c92364e6a3 6744 net optional 

Processed: tagging 907332

[Debian Bug Tracking System]

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

> tags 907332 - sid buster
Bug #907332 [ghostscript] ghostscript has a new code execution issue, even when 
used with -dSAFER
Removed tag(s) sid and buster.
> thanks
Stopping processing here.

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

Bug#907346: slic3r FTBFS on big endian: #error "admesh works correctly on little endian machines only!"

[Adrian Bunk]

Source: slic3r
Version: 1.3.0+dfsg1-1
Severity: serious
Tags: ftbfs

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

...
In file included from src/libslic3r/TriangleMesh.hpp:5:0,
 from src/libslic3r/Model.hpp:9,
 from src/libslic3r/Print.hpp:14,
 from src/libslic3r/GCode.hpp:11,
 from src/libslic3r/GCode/SpiralVase.hpp:5,
 from src/libslic3r/GCode/SpiralVase.cpp:1:
src/admesh/stl.h:32:2: error: #error "admesh works correctly on little endian 
machines only!"
 #error "admesh works correctly on little endian machines only!"
  ^


This looks similar to the fixed #869638 in slic3r-prusa.

Bug#898801: marked as done (globus-gass-copy: FTBFS against openssl 1.1.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Aug 2018 19:34:38 +
with message-id 
and subject line Bug#898801: fixed in globus-gass-copy 9.28-2
has caused the Debian Bug report #898801,
regarding globus-gass-copy: FTBFS against openssl 1.1.1
to be marked as done.

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

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


-- 
898801: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898801
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: globus-gass-copy
Version: 9.28-1
Severity: important
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: openssl-1.1.1

The new openssl 1.1.1 is currently in experimental [0]. This package
failed to build against this new package [1] while it built fine against
the openssl version currently in unstable [2].
Could you please have a look?
The Error 
|# 530-OpenSSL Error: ../ssl/ssl_rsa.c:310: in library: SSL routines, function 
SSL_CTX_use_certificate: ee key too small

is due to:
1.1.1~~pre6-1 changelog):
|   * Increase default security level from 1 to 2. This moves from the 80 bit
| security level to the 112 bit securit level and will require 2048 bit RSA
| and DHE keys.

[0] https://lists.debian.org/msgid-search/20180501211400.ga21...@roeckx.be
[1] 
https://breakpoint.cc/openssl-rebuild/2018-05-03-rebuild-openssl1.1.1-pre6/attempted/globus-gass-copy_9.28-1_amd64-2018-05-01T20%3A03%3A39Z
[2] 
https://breakpoint.cc/openssl-rebuild/2018-05-03-rebuild-openssl1.1.1-pre6/successful/globus-gass-copy_9.28-1_amd64-2018-05-02T18%3A43%3A39Z

Sebastian
--- End Message ---
--- Begin Message ---
Source: globus-gass-copy
Source-Version: 9.28-2

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

Debian distribution maintenance software
pp.
Mattias Ellert  (supplier of updated 
globus-gass-copy package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 26 Aug 2018 07:34:14 +0200
Source: globus-gass-copy
Binary: libglobus-gass-copy2 globus-gass-copy-progs libglobus-gass-copy-dev 
libglobus-gass-copy-doc
Architecture: source amd64 all
Version: 9.28-2
Distribution: unstable
Urgency: medium
Maintainer: Mattias Ellert 
Changed-By: Mattias Ellert 
Description:
 globus-gass-copy-progs - Globus Toolkit - Globus Gass Copy Programs
 libglobus-gass-copy-dev - Globus Toolkit - Globus Gass Copy Development Files
 libglobus-gass-copy-doc - Globus Toolkit - Globus Gass Copy Documentation Files
 libglobus-gass-copy2 - Globus Toolkit - Globus Gass Copy
Closes: 898801
Changes:
 globus-gass-copy (9.28-2) unstable; urgency=medium
 .
   * Use 2048 bit RSA key for tests (Closes: #898801)
   * Move VCS to salsa.debian.org
Checksums-Sha1:
 e82d96603efdc1abfe1e70385ae764ac6858a314 2557 globus-gass-copy_9.28-2.dsc
 42403f0631ae3fe1bc75282673faaf6e171d4d5d 5124 
globus-gass-copy_9.28-2.debian.tar.xz
 d51bc0ca8bd8de3bbbca4c26780e29b7ae3edd5e 73984 
globus-gass-copy-progs-dbgsym_9.28-2_amd64.deb
 a0fbe459d709c30a9bf1cebcec14b5b5a16d83de 38556 
globus-gass-copy-progs_9.28-2_amd64.deb
 181412b9217158eeac647c1ecfe846fab6e3d8d6 10794 
globus-gass-copy_9.28-2_amd64.buildinfo
 d4d7587e5e65ce97bf7c51465097805a8e426da0 9800 
libglobus-gass-copy-dev_9.28-2_amd64.deb
 2332a6247a046ff46b36f490a453859df1a90aa7 153160 
libglobus-gass-copy-doc_9.28-2_all.deb
 eaf224f2fcf39747ce8f120dfc489c7a1f05b7e8 77248 
libglobus-gass-copy2-dbgsym_9.28-2_amd64.deb
 422eabbceea5722477d7fb06e131dc5a3dc43a01 27964 
libglobus-gass-copy2_9.28-2_amd64.deb
Checksums-Sha256:
 3ecc83119a51fc945700eed44a5c10340f709e2633269bed4568889a7df897a9 2557 
globus-gass-copy_9.28-2.dsc
 2876ce6c0da0e7b4728967ad8d5f74b70b48a865fdd77746d44b0842309bcb8b 5124 
globus-gass-copy_9.28-2.debian.tar.xz
 b5ed5791a585fdc2995dd31d54ee3ace545b85d039ebdd785612aac6d83b2e2a 73984 
globus-gass-copy-progs-dbgsym_9.28-2_amd64.deb
 6d8514addb3215a891a2cbb1fd3a336034645ccc9184d67de481d992b33e17a9 38556 
globus-gass-copy-progs_9.28-2_amd64.deb
 72a20ae63ecc49411c79365c75867fbe9220d2c3a5a32d20dbbb730e09869785 10794 
globus-gass-copy_9.28-2_amd64.buildinfo
 

Bug#898802: marked as done (globus-gram-job-manager: FTBFS against openssl 1.1.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Aug 2018 19:35:02 +
with message-id 
and subject line Bug#898802: fixed in globus-gram-job-manager 14.36-3
has caused the Debian Bug report #898802,
regarding globus-gram-job-manager: FTBFS against openssl 1.1.1
to be marked as done.

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

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


-- 
898802: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898802
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: globus-gram-job-manager
Version: 14.36-2
Severity: important
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: openssl-1.1.1

The new openssl 1.1.1 is currently in experimental [0]. This package
failed to build against this new package [1] while it built fine against
the openssl version currently in unstable [2].
Could you please have a look?

I suspect a too small key in the testsuite 1.1.1~~pre6-1 changelog):
|   * Increase default security level from 1 to 2. This moves from the 80 bit
| security level to the 112 bit securit level and will require 2048 bit RSA
| and DHE keys.

[0] https://lists.debian.org/msgid-search/20180501211400.ga21...@roeckx.be
[1] 
https://breakpoint.cc/openssl-rebuild/2018-05-03-rebuild-openssl1.1.1-pre6/attempted/globus-gram-job-manager_14.36-2_amd64-2018-05-01T20%3A03%3A44Z
[2] 
https://breakpoint.cc/openssl-rebuild/2018-05-03-rebuild-openssl1.1.1-pre6/successful/globus-gram-job-manager_14.36-2_amd64-2018-05-02T18%3A43%3A40Z

Sebastian
--- End Message ---
--- Begin Message ---
Source: globus-gram-job-manager
Source-Version: 14.36-3

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

Debian distribution maintenance software
pp.
Mattias Ellert  (supplier of updated 
globus-gram-job-manager package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 26 Aug 2018 11:03:52 +0200
Source: globus-gram-job-manager
Binary: globus-gram-job-manager globus-seg-job-manager
Architecture: source amd64
Version: 14.36-3
Distribution: unstable
Urgency: medium
Maintainer: Mattias Ellert 
Changed-By: Mattias Ellert 
Description:
 globus-gram-job-manager - Globus Toolkit - GRAM Jobmanager
 globus-seg-job-manager - Globus Toolkit - Scheduler Event Generator Job Manager
Closes: 898802
Changes:
 globus-gram-job-manager (14.36-3) unstable; urgency=medium
 .
   * Use 2048 bit RSA key for tests (Closes: #898802)
   * Move VCS to salsa.debian.org
Checksums-Sha1:
 6f34c1983b9af5d6550cd9e76a1c69611d5fd754 3024 
globus-gram-job-manager_14.36-3.dsc
 9ab369afc206d392a636265b2bc2a56b5073e050 6068 
globus-gram-job-manager_14.36-3.debian.tar.xz
 d6bf81529b46692c8c4c7e21c2beff672550ed10 737200 
globus-gram-job-manager-dbgsym_14.36-3_amd64.deb
 60491a34c99912f1250685656ab010e2c324d4d5 10267 
globus-gram-job-manager_14.36-3_amd64.buildinfo
 3fc6ad4b2e2a3b2e1182a522f7def6a0a272425a 149200 
globus-gram-job-manager_14.36-3_amd64.deb
 966af9c5abe56849fadedf52d350af82bd970251 17776 
globus-seg-job-manager-dbgsym_14.36-3_amd64.deb
 682bd59bf2f808f4a588b76b256332a3ded5dd71 10468 
globus-seg-job-manager_14.36-3_amd64.deb
Checksums-Sha256:
 d943dd2776e22aff04fc4ba53fda847ccd9b1296e640787f0643b3813aaecb5c 3024 
globus-gram-job-manager_14.36-3.dsc
 3f68afb6547ff8707cde336c5e2e587ece30358b7b772190cac64a515f5babb9 6068 
globus-gram-job-manager_14.36-3.debian.tar.xz
 f08b06c189bca3ebdc3aa6483b49dce734931abd8e385061446d754241cf21b5 737200 
globus-gram-job-manager-dbgsym_14.36-3_amd64.deb
 939cbe0ed8f1c4df9fb4ffd7d7850ca12383ce4b52cbb83439762bf911242c5f 10267 
globus-gram-job-manager_14.36-3_amd64.buildinfo
 c26210bd556d64aad5589167582bd8621b78fdb66266d3db81a197fb0d829dde 149200 
globus-gram-job-manager_14.36-3_amd64.deb
 165ca2559875b36a6577117718235a48611c52f2a1ae7ffeefc1404be23638ac 17776 
globus-seg-job-manager-dbgsym_14.36-3_amd64.deb
 d58824dcffdefe56a75225db5b927904e15bcd3d84a4e07f3311971ce5493c7b 10468 
globus-seg-job-manager_14.36-3_amd64.deb
Files:
 f6e9a98a659d3a95ed7269142c948683 3024 net optional 
globus-gram-job-manager_14.36-3.dsc
 54916ee73514d878017fc1b10783d7c6 6068 net optional 

Bug#907210: marked as done (libfastahack: ftbfs on some architectures (symbols))

[Debian Bug Tracking System]

Your message dated Sun, 26 Aug 2018 19:35:36 +
with message-id 
and subject line Bug#907210: fixed in libfastahack 
0.0+git20160702.bbc645f+dfsg-4
has caused the Debian Bug report #907210,
regarding libfastahack: ftbfs on some architectures (symbols)
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.)


-- 
907210: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907210
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: libfastahack
version: 0.0+git20160702.bbc645f+dfsg-2
severity: serious

Hi,

The latest upload of libfastahack FTBFS on a number of architectures (it seems
to be related to the symbols):

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

Cheers,

Ivo
--- End Message ---
--- Begin Message ---
Source: libfastahack
Source-Version: 0.0+git20160702.bbc645f+dfsg-4

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated libfastahack package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 26 Aug 2018 21:15:36 +0200
Source: libfastahack
Binary: libfastahack0 libfastahack-dev fastahack
Architecture: source
Version: 0.0+git20160702.bbc645f+dfsg-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 fastahack  - utility for indexing and sequence extraction from FASTA files
 libfastahack-dev - library for indexing and sequence extraction from FASTA 
files (de
 libfastahack0 - library for indexing and sequence extraction from FASTA files 
(li
Closes: 907210
Changes:
 libfastahack (0.0+git20160702.bbc645f+dfsg-4) unstable; urgency=medium
 .
   * Fix symbols file for mips64el and ppc64el
 Closes: #907210
Checksums-Sha1:
 381013423a978bafb84880e7eec777b912f38b76 2273 
libfastahack_0.0+git20160702.bbc645f+dfsg-4.dsc
 ae30a3ca3678d8f2ca6c6bf7f3547d0f278c2d9e 6012 
libfastahack_0.0+git20160702.bbc645f+dfsg-4.debian.tar.xz
Checksums-Sha256:
 38fc34ab50f9ea7f127ff185a7da5c6ef0ee9c3a2743aa8d467ae43001950606 2273 
libfastahack_0.0+git20160702.bbc645f+dfsg-4.dsc
 8e9497e456d88946a600289328103b07f6580800e4465226412d31e5f0289c8c 6012 
libfastahack_0.0+git20160702.bbc645f+dfsg-4.debian.tar.xz
Files:
 e878e0edafda35a69e4ddae36a135496 2273 science optional 
libfastahack_0.0+git20160702.bbc645f+dfsg-4.dsc
 1b7ca342f4accf0b531d5668da3706f3 6012 science optional 
libfastahack_0.0+git20160702.bbc645f+dfsg-4.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAluC/YIRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtEmww//Wmj7nCJxAFgQPrRpM5mKbz6MT8Hiedj9
R70UmjW9/uOv1UrIxCuVW8U4oZEw5f4hvl2FiKcAHFEAuTGeSk7Qvf7XLKxW+e5Z
C/cb/cjNTghqXQrd4EOgKrY8kVhZlPs3pkFOuj1Q1VqtucmreS5HSXyH4kEGVfdQ
MqdK+S2bar0uvUJsV73JlddHLzLWPWHZWkjt7TdLxkE1GhlX2T2RCZea9DBVNtJV
hmueYc9vG1/EaIxW7oVVEn9vYYOOxdAot1BKcPFyl8fmgAbvid4RhAYFhWWcMlzf
4rbEpMs3uJJJeBdKxkaq77XZSjS7uun8kRXMUPb2fe7ekHNNjckVNZHtvvUnxVOU
KpmiW5mN8F0kYo4o22piZYxAkZYlk0T7AxWa5zwzCLcZHXz16FXazG/s27PKCLt1
89agYsXNfG2VxwwbKzHGN/q2MDpAllL+gfkc3Zd65tFjuh7xyAPg09yS8doEWqS8
FKIh5PQJZgQ+Yc/FmjLt8NECtML1VyTJBIbRxDcHsp8sMBbFvuOOyuNgYmPeGWFK
MCQ4WEv8Rvbqbjq7wN0CggkLGVgnzzYL8M0ebEd9aw+29X7aXDEzMjKmhnPy11Te
2jFZ2vlIG0bST2AHM24SllwmqagUHd/7RcqttuP60Mft19bjwumvV9igjOrCXsIX
K7pbPD2arNs=
=sl+Z
-END PGP SIGNATURE End Message ---

Bug#897652: marked as done (globus-ftp-client: FTBFS against openssl 1.1.1)

[Debian Bug Tracking System]

Your message dated Sun, 26 Aug 2018 19:34:11 +
with message-id 
and subject line Bug#897652: fixed in globus-ftp-client 8.36-3
has caused the Debian Bug report #897652,
regarding globus-ftp-client: FTBFS against openssl 1.1.1
to be marked as done.

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

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


-- 
897652: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897652
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: globus-ftp-client
Version: 8.36-2
Severity: important
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: openssl-1.1.1

The new openssl 1.1.1 is currently in experimental [0]. This package
failed to build against this new package [1] while it built fine against
the openssl version currently in unstable [2].
Could you please have a look?

The problem is the 1024bit RSA key in the testsuite due to (1.1.1~~pre6-1
changelog):
|   * Increase default security level from 1 to 2. This moves from the 80 bit
| security level to the 112 bit securit level and will require 2048 bit RSA
| and DHE keys.

The key can be upgraded via
sed s@1024@2048 -i test/Makefile.am

[0] https://lists.debian.org/msgid-search/20180501211400.ga21...@roeckx.be
[1] 
https://breakpoint.cc/openssl-rebuild/2018-05-03-rebuild-openssl1.1.1-pre6/attempted/globus-ftp-client_8.36-2_amd64-2018-05-01T22%3A33%3A50Z
[2] 
https://breakpoint.cc/openssl-rebuild/2018-05-03-rebuild-openssl1.1.1-pre6/successful/globus-ftp-client_8.36-2_amd64-2018-05-02T18%3A43%3A38Z

Sebastian
--- End Message ---
--- Begin Message ---
Source: globus-ftp-client
Source-Version: 8.36-3

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

Debian distribution maintenance software
pp.
Mattias Ellert  (supplier of updated 
globus-ftp-client package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 26 Aug 2018 08:27:20 +0200
Source: globus-ftp-client
Binary: libglobus-ftp-client2 libglobus-ftp-client-dev libglobus-ftp-client-doc
Architecture: source amd64 all
Version: 8.36-3
Distribution: unstable
Urgency: medium
Maintainer: Mattias Ellert 
Changed-By: Mattias Ellert 
Description:
 libglobus-ftp-client-dev - Globus Toolkit - GridFTP Client Library Development 
Files
 libglobus-ftp-client-doc - Globus Toolkit - GridFTP Client Library 
Documentation Files
 libglobus-ftp-client2 - Globus Toolkit - GridFTP Client Library
Closes: 897652
Changes:
 globus-ftp-client (8.36-3) unstable; urgency=medium
 .
   * Use 2048 bit RSA key for tests (Closes: #897652)
   * Move VCS to salsa.debian.org
Checksums-Sha1:
 99447fb6b2f12a7bc416df37932a70b91a4db4d9 2494 globus-ftp-client_8.36-3.dsc
 6db3d54eab6b74a19ce2c76a34f6c4b1765f9784 5400 
globus-ftp-client_8.36-3.debian.tar.xz
 7fd55b68f7d3c72f79d94029e6c6e0688a364bed 10039 
globus-ftp-client_8.36-3_amd64.buildinfo
 ec1e2248f00cb5465a102a8ec0e0a7ff82436ac4 19192 
libglobus-ftp-client-dev_8.36-3_amd64.deb
 1ab13a251c36c82b051a594fba1c41e17477a241 907920 
libglobus-ftp-client-doc_8.36-3_all.deb
 eec0f73feda98f95b261ecdd18b38d3f18175071 336316 
libglobus-ftp-client2-dbgsym_8.36-3_amd64.deb
 6435769af3aa5aef21e1a39d47ac33acb0e83306 86204 
libglobus-ftp-client2_8.36-3_amd64.deb
Checksums-Sha256:
 bef369ae911e03d39e4858e0ec9092b181cccda63ab57790a4f8ee28943a33eb 2494 
globus-ftp-client_8.36-3.dsc
 120a03f5ec9850f9430992f31272cbcfba05cd1020adeddbef4d9c749ca65830 5400 
globus-ftp-client_8.36-3.debian.tar.xz
 9003c6edae354993a6150f72d62f4886eb0356f2d4e601ba0d22f721bf2899a7 10039 
globus-ftp-client_8.36-3_amd64.buildinfo
 528eee7049dfcac9a7ae24b218176e5cf8dbed4639548e0a0872b9cb3b42e1ef 19192 
libglobus-ftp-client-dev_8.36-3_amd64.deb
 df02570c5dcd59290777296a557fac5c3560a83917159d077438c7cfb5a59f55 907920 
libglobus-ftp-client-doc_8.36-3_all.deb
 34893106d1a7935bde23a408185fbf0e7897161908a0ba9f0263115850237890 336316 
libglobus-ftp-client2-dbgsym_8.36-3_amd64.deb
 30715b6538039f368d8f35bd17a1a852db9690abe56552f6122e4c8e742e8c4c 86204 
libglobus-ftp-client2_8.36-3_amd64.deb
Files:
 25efaee3b460266ae7ec364c53ec4ec9 2494 net optional 

Bug#907042: opam 1.2.0 is deprecated (jessie)

[Ben Hutchings]

On Sun, 2018-08-26 at 16:40 +0100, Nicolas Braud-Santoni wrote:
> Dear LTS contributors,
> 
> I'm a co-maintainer of opam, the OCaml-specific dependencies manager, which
> is currently broken in olstable: the version in Jessie is 1.2.0 and does
> not support the current opam repository format[0], meaning that users
> cannot install new OPAM packages, get updates, ... (see #907042)
> 
> I would like to propose an update in Jessie to 1.2.2, the same version as
> in Stretch, and Ben suggested that I ask here to check nobody would be
> opposed to it, and to get advise on the process to follow.
> 
> Please note that upstream is planning a change to a new repository format
> (as part of releasing 2.0.0, which is currently in NEW) [1], but they plan
> to keep a branch of the repository in 1.2 format, and accept important
> updates there, so opam 1.2 will keep working for users of stable and LTS.

This seems OK in principle, but:

* Looking at the upstream CHANGES file, there seem to be quite large
non-bugfix changes between 1.2.0 and 1.2.2.  Are they definitely
backward-compatible?

* The Build-Depends for the version in stretch are not satisfiable in
jessie (specifically libdose3-ocaml-dev (>= 4.0.1-2~), libcmdliner-
ocaml-dev (>= 0.9.7~), ibjsonm-ocaml-dev).  It looks like you will need
to revert several of the packaging changes.

Ben.
 
-- 
Ben Hutchings
Klipstein's 4th Law of Prototyping and Production:
   A fail-safe circuit will destroy others.



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

Bug#907227: equalx: FTBFS with Qt 5.11

[Juhani Numminen]

Control: tags -1 patch
Control: forwarded -1 https://bugs.launchpad.net/equalx/+bug/1789117

Dear maintainer,

I have a one-line patch for this and I've sent it upstream as well.

Regards,
Juhani

Processed: qtbase-opensource-src breaks purpose autopkgtest possibly due to new openssl

[Debian Bug Tracking System]

Processing control commands:

> block 907015 by -1
Bug #907015 [src:openssl] openssl version 1.1.1 breaks multiple reverse 
dependencies; versioned Breaks needed
907015 was blocked by: 900161 900156 900154 907033 906981 900158 900153 900982 
900159 907022 898802 907055 898807 900157 897643 895959 906997 898804 898800 
907219 897658 898805 900160 907135 900152 907049 898801 891625 907031 891665 
906955 907079 907339 897651 898803 907118 907215 907028 897652 907216 907168
907015 was not blocking any bugs.
Added blocking bug(s) of 907015: 907340

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

Processed: Re: equalx: FTBFS with Qt 5.11

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #907227 [src:equalx] equalx: FTBFS with Qt 5.11
Added tag(s) patch.
> forwarded -1 https://bugs.launchpad.net/equalx/+bug/1789117
Bug #907227 [src:equalx] equalx: FTBFS with Qt 5.11
Set Bug forwarded-to-address to 
'https://bugs.launchpad.net/equalx/+bug/1789117'.

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

Bug#907210: fixed in libfastahack 0.0+git20160702.bbc645f+dfsg-3

[Ivo De Decker]

Control: reopen -1

Hi Andreas,

On Sat, Aug 25, 2018 at 04:04:19PM +, Andreas Tille wrote:
> Subject: Bug#907210: fixed in libfastahack 0.0+git20160702.bbc645f+dfsg-3
> 
> Source: libfastahack
> Source-Version: 0.0+git20160702.bbc645f+dfsg-3

It seems libfastahack still FTBFS on mips64el and ppc64el.

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

Cheers,

Ivo

Processed: Re: Bug#907210: fixed in libfastahack 0.0+git20160702.bbc645f+dfsg-3

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #907210 {Done: Andreas Tille } [libfastahack] 
libfastahack: ftbfs on some architectures (symbols)
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 
libfastahack/0.0+git20160702.bbc645f+dfsg-3.

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

Processed: qtbase-opensource-src breaks kdeconnect autopkgtest possibly due to new openssl

[Debian Bug Tracking System]

Processing control commands:

> block 907015 by -1
Bug #907015 [src:openssl] openssl version 1.1.1 breaks multiple reverse 
dependencies; versioned Breaks needed
907015 was blocked by: 900154 906981 898800 907219 898804 898805 900156 897643 
897651 898807 898802 906997 907215 898801 900982 895959 907135 907049 907031 
906955 907079 907033 900153 900160 900158 907118 907028 898803 907022 907216 
897658 907055 907168 891625 900152 900161 897652 891665 900159 900157
907015 was not blocking any bugs.
Added blocking bug(s) of 907015: 907339

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

Bug#906534: marked as done (emacs25-nox: too lax dependency on emacs-nox)

[Debian Bug Tracking System]

Your message dated Sun, 26 Aug 2018 18:04:16 +
with message-id 
and subject line Bug#906534: fixed in emacs 1:25.2+1-11
has caused the Debian Bug report #906534,
regarding emacs25-nox: too lax dependency on emacs-nox
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.)


-- 
906534: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906534
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: emacs-nox
Version: 47.0
Severity: grave
Tags: a11y
Justification: renders package unusable

Dear Maintainer,

I installed emacs-nox package in 2018-07-16. Then packages emacs, emacs25-nox,
emacs-nox were installed.

I execute 'apt-get update && apt-get upgrade' in 2018-08-16. Then
package emacs and emacs25-nox were upgraded, but emacs-nox had been kept
back.

At the time, emacs binary disappeared and I could not use emacs.

I executed 'apt-get install emacs-nox' to upgrade emacs-nox manually and
/usr/bin/emacs-nox is installed. (So I can use emacs now.)

Thanks,
Shin Yoshida

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

Kernel: Linux 4.9.0-6-amd64 (SMP w/2 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 /usr/bin/dash
Init: unable to detect

Versions of packages emacs-nox depends on:
ii  emacs25-nox  1:25.2+1-10

emacs-nox recommends no packages.

emacs-nox suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: emacs
Source-Version: 1:25.2+1-11

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

Debian distribution maintenance software
pp.
Rob Browning  (supplier of updated emacs package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 26 Aug 2018 11:49:09 -0500
Source: emacs
Binary: emacs emacs-lucid emacs-lucid-dbg emacs-nox emacs-nox-dbg emacs-gtk 
emacs-gtk-dbg emacs-bin-common emacs-common emacs-el emacs23 emacs23-lucid 
emacs23-nox emacs24 emacs24-lucid emacs24-nox emacs25 emacs25-lucid emacs25-nox
Architecture: source
Version: 1:25.2+1-11
Distribution: unstable
Urgency: medium
Maintainer: Rob Browning 
Changed-By: Rob Browning 
Description:
 emacs  - GNU Emacs editor (metapackage)
 emacs-bin-common - GNU Emacs editor's shared, architecture dependent files
 emacs-common - GNU Emacs editor's shared, architecture independent 
infrastructur
 emacs-el   - GNU Emacs LISP (.el) files
 emacs-gtk  - GNU Emacs editor (with GTK+ GUI support)
 emacs-gtk-dbg - Debugging symbols for emacs-gtk
 emacs-lucid - GNU Emacs editor (with Lucid GUI support)
 emacs-lucid-dbg - Debugging symbols for emacs-lucid
 emacs-nox  - GNU Emacs editor (without GUI support)
 emacs-nox-dbg - Debugging symbols for emacs-nox
 emacs23- GNU Emacs transitional package to emacs-gtk
 emacs23-lucid - GNU Emacs transitional package to emacs-lucid
 emacs23-nox - GNU Emacs transitional package to emacs-nox
 emacs24- GNU Emacs transitional package to emacs-gtk
 emacs24-lucid - GNU Emacs transitional package to emacs-lucid
 emacs24-nox - GNU Emacs transitional package to emacs-nox
 emacs25- GNU Emacs transitional package to emacs-gtk
 emacs25-lucid - GNU Emacs transitional package to emacs-lucid
 emacs25-nox - GNU Emacs transitional package to emacs-nox
Closes: 883434 906534
Changes:
 emacs (1:25.2+1-11) unstable; urgency=medium
 .
   * Add (>= 1:25) restriction to emacs metapackage dependencies.
 Without this it was possible to end up with two empty metapackages
 installed instead of the expected metapackage and actual package.
 Thanks to Shin Yoshida for reporting the problem and Sven Joachim
 for noting the solution. (Closes: 906534)
 .
   * Don't unexpectedly modify the byte order mark.  Add
 0014-Emacs-should-no-longer-unexpectedly-alter-the-byte-o.patch to
 fix the problem.  Thanks to Vincent Lefevre for reporting the
 problem and Eli Zaretskii for the patch. (Closes: 883434)
Checksums-Sha1:
 

Bug#883434: marked as done (emacs25: Silent file corruption on file with BOM: BOM gets removed)

[Debian Bug Tracking System]

Your message dated Sun, 26 Aug 2018 18:04:16 +
with message-id 
and subject line Bug#883434: fixed in emacs 1:25.2+1-11
has caused the Debian Bug report #883434,
regarding emacs25: Silent file corruption on file with BOM: BOM gets removed
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.)


-- 
883434: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883434
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: emacs25
Version: 25.2+1-6
Severity: grave
Justification: causes non-serious data loss

Under some conditions, when saving a file with a BOM, the BOM
*silently* gets removed, which is a major change (some applications,
such as Firefox, are BOM-sensitive, so that this bug breaks things
without knowing the cause).

To reproduce the bug:

0. Uncompress the attached file (I used compression to make sure that
   it doesn't get corrupted by the mail system): unxz a.html.xz

1. cp a.html b.html

2. emacs -Q b.html

3. Type M-: (set-buffer-modified-p t) to mark the buffer as modified
   (so that one can save it).

4. Save the file with C-x C-s.

5. Quit with C-x C-c.

6. cmp a.html b.html

This gives:

a.html b.html differ: char 1, line 1

$ hd a.html | head -n 1
  ef bb bf 3c 21 44 4f 43  54 59 50 45 20 68 74 6d  |...

a.html.xz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: emacs
Source-Version: 1:25.2+1-11

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

Debian distribution maintenance software
pp.
Rob Browning  (supplier of updated emacs package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 26 Aug 2018 11:49:09 -0500
Source: emacs
Binary: emacs emacs-lucid emacs-lucid-dbg emacs-nox emacs-nox-dbg emacs-gtk 
emacs-gtk-dbg emacs-bin-common emacs-common emacs-el emacs23 emacs23-lucid 
emacs23-nox emacs24 emacs24-lucid emacs24-nox emacs25 emacs25-lucid emacs25-nox
Architecture: source
Version: 1:25.2+1-11
Distribution: unstable
Urgency: medium
Maintainer: Rob Browning 
Changed-By: Rob Browning 
Description:
 emacs  - GNU Emacs editor (metapackage)
 emacs-bin-common - GNU Emacs editor's shared, architecture dependent files
 emacs-common - GNU Emacs editor's shared, architecture independent 
infrastructur
 emacs-el   - GNU Emacs LISP (.el) files
 emacs-gtk  - GNU Emacs editor (with GTK+ GUI support)
 emacs-gtk-dbg - Debugging symbols for emacs-gtk
 emacs-lucid - GNU Emacs editor (with Lucid GUI support)
 emacs-lucid-dbg - Debugging symbols for emacs-lucid
 emacs-nox  - GNU Emacs editor (without GUI support)
 emacs-nox-dbg - Debugging symbols for emacs-nox
 emacs23- GNU Emacs transitional package to emacs-gtk
 emacs23-lucid - GNU Emacs transitional package to emacs-lucid
 emacs23-nox - GNU Emacs transitional package to emacs-nox
 emacs24- GNU Emacs transitional package to emacs-gtk
 emacs24-lucid - GNU Emacs transitional package to emacs-lucid
 emacs24-nox - GNU Emacs transitional package to emacs-nox
 emacs25- GNU Emacs transitional package to emacs-gtk
 emacs25-lucid - GNU Emacs transitional package to emacs-lucid
 emacs25-nox - GNU Emacs transitional package to emacs-nox
Closes: 883434 906534
Changes:
 emacs (1:25.2+1-11) unstable; urgency=medium
 .
   * Add (>= 1:25) restriction to emacs metapackage dependencies.
 Without this it was possible to end up with two empty metapackages
 installed instead of the expected metapackage and actual package.
 Thanks to Shin Yoshida for reporting the problem and Sven Joachim
 for noting the solution. (Closes: 906534)
 .
   * Don't unexpectedly modify the byte order mark.  Add
 0014-Emacs-should-no-longer-unexpectedly-alter-the-byte-o.patch to
 fix the problem.  Thanks to Vincent Lefevre for reporting the
 problem and Eli Zaretskii for the patch. (Closes: 883434)
Checksums-Sha1:
 523a022fa1003aadb4e8b49766300d9eb7627062 3344 emacs_25.2+1-11.dsc
 9dabcd86e6392301a2dbfbc090301ee7f37495a1 55060 emacs_25.2+1-11.debian.tar.xz
 a2bd8a2765a86abf043d035b418185ace3062162 21770 

Bug#907335: patsy FTBFS with Python 3.7 as supported version

[Adrian Bunk]

Source: patsy
Version: 0.4.1+git34-ga5b54c2-1
Severity: serious
Tags: buster sid ftbfs

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

...
==
FAIL: patsy.test_build.test_DesignInfo_subset
--
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
  File 
"/build/1st/patsy-0.4.1+git34-ga5b54c2/debian/tmp/usr/lib/python3/dist-packages/patsy/test_build.py",
 line 700, in test_DesignInfo_subset
t("~ 0 + x + y + z", ["x", "y", "z"], slice(None))
  File 
"/build/1st/patsy-0.4.1+git34-ga5b54c2/debian/tmp/usr/lib/python3/dist-packages/patsy/test_build.py",
 line 690, in t
sub_design_info = all_builder.subset(which_terms)
  File 
"/build/1st/patsy-0.4.1+git34-ga5b54c2/debian/tmp/usr/lib/python3/dist-packages/patsy/design_info.py",
 line 630, in subset
desc = ModelDesc.from_formula(which_terms)
  File 
"/build/1st/patsy-0.4.1+git34-ga5b54c2/debian/tmp/usr/lib/python3/dist-packages/patsy/desc.py",
 line 164, in from_formula
tree = parse_formula(tree_or_string)
  File 
"/build/1st/patsy-0.4.1+git34-ga5b54c2/debian/tmp/usr/lib/python3/dist-packages/patsy/parse_formula.py",
 line 148, in parse_formula
_atomic_token_types)
  File 
"/build/1st/patsy-0.4.1+git34-ga5b54c2/debian/tmp/usr/lib/python3/dist-packages/patsy/infix_parser.py",
 line 210, in infix_parse
for token in token_source:
  File 
"/build/1st/patsy-0.4.1+git34-ga5b54c2/debian/tmp/usr/lib/python3/dist-packages/patsy/parse_formula.py",
 line 94, in _tokenize_formula
yield _read_python_expr(it, end_tokens)
  File 
"/build/1st/patsy-0.4.1+git34-ga5b54c2/debian/tmp/usr/lib/python3/dist-packages/patsy/parse_formula.py",
 line 44, in _read_python_expr
for pytype, token_string, origin in it:
  File 
"/build/1st/patsy-0.4.1+git34-ga5b54c2/debian/tmp/usr/lib/python3/dist-packages/patsy/util.py",
 line 332, in next
return six.advance_iterator(self._it)
  File 
"/build/1st/patsy-0.4.1+git34-ga5b54c2/debian/tmp/usr/lib/python3/dist-packages/patsy/tokens.py",
 line 35, in python_tokenize
assert pytype not in (tokenize.NL, tokenize.NEWLINE)
AssertionError

==
FAIL: patsy.test_highlevel.test_formula_likes
--
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
  File 
"/build/1st/patsy-0.4.1+git34-ga5b54c2/debian/tmp/usr/lib/python3/dist-packages/patsy/test_highlevel.py",
 line 255, in test_formula_likes
[[1], [2]], ["y"])
  File 
"/build/1st/patsy-0.4.1+git34-ga5b54c2/debian/tmp/usr/lib/python3/dist-packages/patsy/test_highlevel.py",
 line 87, in t
builders = incr_dbuilders(formula_like, data_iter_maker, depth)
  File 
"/build/1st/patsy-0.4.1+git34-ga5b54c2/debian/tmp/usr/lib/python3/dist-packages/patsy/highlevel.py",
 line 130, in incr_dbuilders
NA_action)
  File 
"/build/1st/patsy-0.4.1+git34-ga5b54c2/debian/tmp/usr/lib/python3/dist-packages/patsy/highlevel.py",
 line 62, in _try_incr_builders
formula_like = ModelDesc.from_formula(formula_like)
  File 
"/build/1st/patsy-0.4.1+git34-ga5b54c2/debian/tmp/usr/lib/python3/dist-packages/patsy/desc.py",
 line 164, in from_formula
tree = parse_formula(tree_or_string)
  File 
"/build/1st/patsy-0.4.1+git34-ga5b54c2/debian/tmp/usr/lib/python3/dist-packages/patsy/parse_formula.py",
 line 148, in parse_formula
_atomic_token_types)
  File 
"/build/1st/patsy-0.4.1+git34-ga5b54c2/debian/tmp/usr/lib/python3/dist-packages/patsy/infix_parser.py",
 line 210, in infix_parse
for token in token_source:
  File 
"/build/1st/patsy-0.4.1+git34-ga5b54c2/debian/tmp/usr/lib/python3/dist-packages/patsy/parse_formula.py",
 line 94, in _tokenize_formula
yield _read_python_expr(it, end_tokens)
  File 
"/build/1st/patsy-0.4.1+git34-ga5b54c2/debian/tmp/usr/lib/python3/dist-packages/patsy/parse_formula.py",
 line 44, in _read_python_expr
for pytype, token_string, origin in it:
  File 
"/build/1st/patsy-0.4.1+git34-ga5b54c2/debian/tmp/usr/lib/python3/dist-packages/patsy/util.py",
 line 332, in next
return six.advance_iterator(self._it)
  File 
"/build/1st/patsy-0.4.1+git34-ga5b54c2/debian/tmp/usr/lib/python3/dist-packages/patsy/tokens.py",
 line 35, in python_tokenize
assert pytype not in (tokenize.NL, tokenize.NEWLINE)
AssertionError

==
FAIL: patsy.test_highlevel.test_return_pandas
--
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
  File 

Bug#907332: ghostscript has a new code execution issue, even when used with -dSAFER

[Nicolas Braud-Santoni]

On Sun, Aug 26, 2018 at 06:08:58PM +0100, Nicolas Braud-Santoni wrote:
> 
> I'm attaching the relevant files.

Oops, forgot the attachments.


exploit.ps
Description: PostScript document


signature.asc
Description: PGP signature

Processed: retitling to hopefully more relevant error messages

[Debian Bug Tracking System]

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

> retitle 906624 kexi: FTBFS in buster/sid (invalid use of incomplete type 
> 'class QAction')
Bug #906624 [src:kexi] kexi: FTBFS in buster/sid (no type named 'type' in 
'struct std::enable_if')
Changed Bug title to 'kexi: FTBFS in buster/sid (invalid use of incomplete type 
'class QAction')' from 'kexi: FTBFS in buster/sid (no type named 'type' in 
'struct std::enable_if')'.
> retitle 906969 cb2bib: FTBFS in buster/sid (invalid use of incomplete type 
> 'class QAction')
Bug #906969 [src:cb2bib] cb2bib: FTBFS in buster/sid (no type named 'Object')
Changed Bug title to 'cb2bib: FTBFS in buster/sid (invalid use of incomplete 
type 'class QAction')' from 'cb2bib: FTBFS in buster/sid (no type named 
'Object')'.
> retitle 907155 calligraplan: FTBFS in buster/sid (invalid use of incomplete 
> type 'class QButtonGroup')
Bug #907155 [src:calligraplan] calligraplan: FTBFS in buster/sid (no type named 
'Object' in 'struct QtPrivate::FunctionPointer')
Changed Bug title to 'calligraplan: FTBFS in buster/sid (invalid use of 
incomplete type 'class QButtonGroup')' from 'calligraplan: FTBFS in buster/sid 
(no type named 'Object' in 'struct QtPrivate::FunctionPointer')'.
> retitle 907151 skydns: FTBFS in buster/sid (too many arguments in call to 
> activation.PacketConns)
Bug #907151 [src:skydns] skydns: FTBFS in buster/sid (no type named 'type' in 
'struct std::enable_if')
Changed Bug title to 'skydns: FTBFS in buster/sid (too many arguments in call 
to activation.PacketConns)' from 'skydns: FTBFS in buster/sid (no type named 
'type' in 'struct std::enable_if')'.
> stop
Stopping processing here.

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

Processed: Re: Bug#907332: ghostscript has a new code execution issue, even when used with -dSAFER

[Debian Bug Tracking System]

Processing control commands:

> tag -1 stretch
Bug #907332 [ghostscript] ghostscript has a new code execution issue, even when 
used with -dSAFER
Added tag(s) stretch.

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

Bug#907332: ghostscript has a new code execution issue, even when used with -dSAFER

[Stefano Rivera]

Control: tag -1 stretch

> I was able to reproduce the issue on my system:

Reproduced on stretch too.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Bug#907332: ghostscript has a new code execution issue, even when used with -dSAFER

[Nicolas Braud-Santoni]

Package: ghostscript
Version: 9.22~dfsg-2.1
Severity: grave
Tags: security buster sid
Justification: user security hole

Hi,

Tavis Ormandy disclosed a new ghoscript security issue, leading directly to code
execution:  http://openwall.com/lists/oss-security/2018/08/21/2

I don't think this is [CVE-2018-11645], as it's supposedly fixed in buster, and
I was able to reproduce the issue on my system:

> $ gs -q -sDEVICE=ppmraw -dSAFER -sOutputFile=/dev/null < exploit.ps
> GS>GS>GS>GS>GS<1>uid=1000(nicoo) gid=1000(nicoo) 
> groups=1000(nicoo),4(adm),5(tty),20(dialout),27(sudo),44(video),46(plugdev),104(input),113(sbuild),115(wireshark)
> 
> $ convert exploit.jpg exploit.gif:(
> uid=1000(nicoo) gid=1000(nicoo) 
> groups=1000(nicoo),4(adm),5(tty),20(dialout),27(sudo),44(video),46(plugdev),104(input),113(sbuild),115(wireshark)
> convert-im6.q16: FailedToExecuteCommand `'gs' -sstdout=%stderr -dQUIET 
> -dSAFER -dBATCH -dNOPAUSE -dNOPROMPT -dMaxBitmap=5 -dAlignToPixels=0 
> -dGridFitTT=2 '-sDEVICE=pngalpha' -dTextAlphaBits=4 -dGraphicsAlphaBits=4 
> '-r72x72' -g612x792  '-sOutputFile=/tmp/magick-955WzJ4UvxhLwQT%d' 
> '-f/tmp/magick-95505j-kbelxXGs' '-f/tmp/magick-955IqsJtzVIPtx1' -c showpage' 
> (-1) @ error/delegate.c/ExternalDelegateCommand/462.
> convert-im6.q16: no images defined `exploit.gif' @ 
> error/convert.c/ConvertImageCommand/3258.
> 
> $ apt-cache policy ghostscript 
> ghostscript:
>   Installed: 9.22~dfsg-2.1
>   Candidate: 9.22~dfsg-2.1
>   Version table:
>  *** 9.22~dfsg-2.1 990
> 990 http://localhost:3142/debian buster/main amd64 Packages
> 500 http://localhost:3142/debian sid/main amd64 Packages
> 100 /var/lib/dpkg/status


I'm attaching the relevant files.


Best,

  nicoo


[CVE-2018-11645]: https://security-tracker.debian.org/tracker/CVE-2018-11645


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

Kernel: Linux 4.17.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set 
to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages ghostscript depends on:
ii  debconf [debconf-2.0]  1.5.69
ii  libc6  2.27-5
ii  libgs9 9.22~dfsg-2.1

Versions of packages ghostscript recommends:
ii  gsfonts  1:8.11+urwcyr1.0.7~pre44-4.4

Versions of packages ghostscript suggests:
pn  ghostscript-x  

-- no debconf information

Processed: retitling

[Debian Bug Tracking System]

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

> retitle 906979 tagua: FTBFS in buster/sid (invalid use of incomplete type 
> 'class QAction')
Bug #906979 [src:tagua] tagua: FTBFS in buster/sid (no type named 'Object' in 
'struct QtPrivate::FunctionPointer')
Changed Bug title to 'tagua: FTBFS in buster/sid (invalid use of incomplete 
type 'class QAction')' from 'tagua: FTBFS in buster/sid (no type named 'Object' 
in 'struct QtPrivate::FunctionPointer')'.
> stop
Stopping processing here.

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

Processed: Re: openrpt: FTBFS in buster/sid (no type named 'Object' in 'struct QtPrivate::FunctionPointer')

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 openrpt: FTBFS in buster/sid (invalid use of incomplete type 
> 'class QButtonGroup')
Bug #906661 [src:openrpt] openrpt: FTBFS in buster/sid (no type named 'Object' 
in 'struct QtPrivate::FunctionPointer')
Changed Bug title to 'openrpt: FTBFS in buster/sid (invalid use of incomplete 
type 'class QButtonGroup')' from 'openrpt: FTBFS in buster/sid (no type named 
'Object' in 'struct QtPrivate::FunctionPointer')'.
> tags -1 fixed-upstream
Bug #906661 [src:openrpt] openrpt: FTBFS in buster/sid (invalid use of 
incomplete type 'class QButtonGroup')
Added tag(s) fixed-upstream.
> forwarded -1 https://github.com/xtuple/openrpt/pull/96
Bug #906661 [src:openrpt] openrpt: FTBFS in buster/sid (invalid use of 
incomplete type 'class QButtonGroup')
Set Bug forwarded-to-address to 'https://github.com/xtuple/openrpt/pull/96'.

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

Bug#906661: openrpt: FTBFS in buster/sid (no type named 'Object' in 'struct QtPrivate::FunctionPointer')

[Juhani Numminen]

Control: retitle -1 openrpt: FTBFS in buster/sid (invalid use of incomplete 
type 'class QButtonGroup')
Control: tags -1 fixed-upstream
Control: forwarded -1 https://github.com/xtuple/openrpt/pull/96

Hello,
In the build log at reproducible builds, these are first errors to appear:

reportparameter.cpp: In constructor 'ReportParameter::ReportParameter(QWidget*, 
Qt::WindowFlags)':
reportparameter.cpp:32:55: error: invalid use of incomplete type 'class 
QButtonGroup'
 QButtonGroup * buttonGroup = new QButtonGroup(this);
   ^
In file included from 
/usr/include/x86_64-linux-gnu/qt5/QtWidgets/qcheckbox.h:44,
 from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/QCheckBox:1,
 from tmp/ui_reportparameter.h:34,
 from reportparameter.h:26,
 from reportparameter.cpp:21:
/usr/include/x86_64-linux-gnu/qt5/QtWidgets/qabstractbutton.h:53:7: note: 
forward declaration of 'class QButtonGroup'
 class QButtonGroup;
   ^~~~
reportparameter.cpp:33:16: error: invalid use of incomplete type 'class 
QButtonGroup'
 buttonGroup->addButton(_staticList, 0);
^~
In file included from 
/usr/include/x86_64-linux-gnu/qt5/QtWidgets/qcheckbox.h:44,
 from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/QCheckBox:1,
 from tmp/ui_reportparameter.h:34,
 from reportparameter.h:26,
 from reportparameter.cpp:21:
/usr/include/x86_64-linux-gnu/qt5/QtWidgets/qabstractbutton.h:53:7: note: 
forward declaration of 'class QButtonGroup'
 class QButtonGroup;
   ^~~~
reportparameter.cpp:34:16: error: invalid use of incomplete type 'class 
QButtonGroup'
 buttonGroup->addButton(_dynamicList, 1);
^~
In file included from 
/usr/include/x86_64-linux-gnu/qt5/QtWidgets/qcheckbox.h:44,
 from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/QCheckBox:1,
 from tmp/ui_reportparameter.h:34,
 from reportparameter.h:26,
 from reportparameter.cpp:21:
/usr/include/x86_64-linux-gnu/qt5/QtWidgets/qabstractbutton.h:53:7: note: 
forward declaration of 'class QButtonGroup'
 class QButtonGroup;
   ^~~~


Cheers,
Juhani

Processed: pyside2: diff for NMU version 5.11.0-3.1

[Debian Bug Tracking System]

Processing control commands:

> tags 906168 + patch
Bug #906168 [src:pyside2] pyside2 build depends on 
libclang-4.0-dev/llvm-4.0-dev which is scheduled for removal
Warning: Unknown package 'src:pyside2'
Added tag(s) patch.
Warning: Unknown package 'src:pyside2'
> tags 906168 + pending
Bug #906168 [src:pyside2] pyside2 build depends on 
libclang-4.0-dev/llvm-4.0-dev which is scheduled for removal
Warning: Unknown package 'src:pyside2'
Added tag(s) pending.
Warning: Unknown package 'src:pyside2'

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

Bug#906168: pyside2: diff for NMU version 5.11.0-3.1

[Adrian Bunk]

Control: tags 906168 + patch
Control: tags 906168 + pending

Dear maintainer,

I've prepared an NMU for pyside2 (versioned as 5.11.0-3.1) and uploaded 
it to DELAYED/11. 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 pyside2-5.11.0/debian/changelog pyside2-5.11.0/debian/changelog
--- pyside2-5.11.0/debian/changelog	2018-07-31 22:33:04.0 +0300
+++ pyside2-5.11.0/debian/changelog	2018-08-25 11:50:28.0 +0300
@@ -1,3 +1,13 @@
+pyside2 (5.11.0-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Use the default LLVM/Clang. (Closes: #906168)
+  * Add upstream fix for FTBFS on armel/armhf.
+  * Fix debian/libpyside2-5.11.install for triplets that are
+not *-linux-gnu.
+
+ -- Adrian Bunk   Sat, 25 Aug 2018 11:50:28 +0300
+
 pyside2 (5.11.0-3) unstable; urgency=medium
 
   * More fixes for builds building only arch any or only arch all.
diff -Nru pyside2-5.11.0/debian/control pyside2-5.11.0/debian/control
--- pyside2-5.11.0/debian/control	2018-07-31 22:33:04.0 +0300
+++ pyside2-5.11.0/debian/control	2018-08-25 11:50:28.0 +0300
@@ -9,7 +9,7 @@
debhelper (>= 11),
dh-exec,
dh-python,
-   libclang-4.0-dev,
+   libclang-dev,
libqt5charts5-dev,
libqt5opengl5-dev,
libqt5sensors5-dev,
@@ -22,7 +22,7 @@
libqt5xmlpatterns5-dev,
libxml2-dev,
libxslt1-dev,
-   llvm-4.0-dev,
+   llvm-dev,
pyqt5-dev (>=5.6),
python-all-dev,
python-setuptools,
diff -Nru pyside2-5.11.0/debian/libpyside2-5.11.install pyside2-5.11.0/debian/libpyside2-5.11.install
--- pyside2-5.11.0/debian/libpyside2-5.11.install	2018-07-31 22:33:04.0 +0300
+++ pyside2-5.11.0/debian/libpyside2-5.11.install	2018-08-25 11:50:28.0 +0300
@@ -1,5 +1,5 @@
 #!/usr/bin/dh-exec
-pyside2_install/py*-relwithdebinfo/lib/libpyside2-python2.7.*-linux-gnu.so.* usr/lib/${DEB_HOST_MULTIARCH}/
+pyside2_install/py*-relwithdebinfo/lib/libpyside2-python2.7.${DEB_HOST_MULTIARCH}.so.* usr/lib/${DEB_HOST_MULTIARCH}/
 pyside2_install/py2*-relwithdebinfo/lib/python2.7/site-packages/PySide2/_git_pyside_version.py usr/lib/python2.7/dist-packages/PySide2
 pyside2_install/py2*-relwithdebinfo/lib/python2.7/site-packages/PySide2/__init__.py usr/lib/python2.7/dist-packages/PySide2
 pyside2_install/py2*-relwithdebinfo/lib/python2.7/site-packages/PySide2/_config.py usr/lib/python2.7/dist-packages/PySide2
diff -Nru pyside2-5.11.0/debian/patches/0001-PySide2-QtGui-Fix-build-of-Debian-armel-armh-OpenGL-.patch pyside2-5.11.0/debian/patches/0001-PySide2-QtGui-Fix-build-of-Debian-armel-armh-OpenGL-.patch
--- pyside2-5.11.0/debian/patches/0001-PySide2-QtGui-Fix-build-of-Debian-armel-armh-OpenGL-.patch	1970-01-01 02:00:00.0 +0200
+++ pyside2-5.11.0/debian/patches/0001-PySide2-QtGui-Fix-build-of-Debian-armel-armh-OpenGL-.patch	2018-08-25 11:50:28.0 +0300
@@ -0,0 +1,65 @@
+From 83b42ca06c834ad07985397764ebe2d7a58234ce Mon Sep 17 00:00:00 2001
+From: Friedemann Kleint 
+Date: Wed, 1 Aug 2018 09:09:08 +0200
+Subject: PySide2/QtGui: Fix build of Debian/armel,armh (OpenGL ES 2)
+
+Add optional class checks to QtGui and use them for
+QOpenGLTimeMonitor and QOpenGLTimerQuery.
+
+Task-number: PYSIDE-764
+Change-Id: Ib33ec1d64c40f53aa31059e4ca9422707636375d
+Reviewed-by: Christian Tismer 
+---
+ sources/pyside2/PySide2/QtGui/CMakeLists.txt | 15 +++
+ 1 file changed, 11 insertions(+), 4 deletions(-)
+
+diff --git a/sources/pyside2/PySide2/QtGui/CMakeLists.txt b/sources/pyside2/PySide2/QtGui/CMakeLists.txt
+index bee58bde..1fe743c0 100644
+--- a/sources/pyside2/PySide2/QtGui/CMakeLists.txt
 b/sources/pyside2/PySide2/QtGui/CMakeLists.txt
+@@ -2,6 +2,12 @@ project(QtGui)
+ 
+ qt5_wrap_cpp(QPYTEXTOBJECT_MOC "${pyside2_SOURCE_DIR}/qpytextobject.h")
+ 
++set(QtGui_OPTIONAL_SRC)
++set(QtGui_DROPPED_ENTRIES)
++
++check_qt_class(QtGui QOpenGLTimeMonitor QtGui_OPTIONAL_SRC QtGui_DROPPED_ENTRIES)
++check_qt_class(QtGui QOpenGLTimerQuery  QtGui_OPTIONAL_SRC QtGui_DROPPED_ENTRIES)
++
+ set(QtGui_SRC
+ ${QtGui_GEN_DIR}/qabstractopenglfunctions_wrapper.cpp
+ ${QtGui_GEN_DIR}/qabstracttextdocumentlayout_paintcontext_wrapper.cpp
+@@ -96,8 +102,6 @@ ${QtGui_GEN_DIR}/qopenglpixeltransferoptions_wrapper.cpp
+ ${QtGui_GEN_DIR}/qopenglshaderprogram_wrapper.cpp
+ ${QtGui_GEN_DIR}/qopengltexture_wrapper.cpp
+ ${QtGui_GEN_DIR}/qopengltextureblitter_wrapper.cpp
+-${QtGui_GEN_DIR}/qopengltimemonitor_wrapper.cpp
+-${QtGui_GEN_DIR}/qopengltimerquery_wrapper.cpp
+ ${QtGui_GEN_DIR}/qopenglversionprofile_wrapper.cpp
+ 

Bug#907042: opam 1.2.0 is deprecated (jessie)

[Holger Levsen]

hi nicoo,

thanks to your work on opam! I'm much looking forward to opam 2! :)

On Sun, Aug 26, 2018 at 04:40:50PM +0100, Nicolas Braud-Santoni wrote:
> I'm a co-maintainer of opam, the OCaml-specific dependencies manager, which
> is currently broken in olstable: the version in Jessie is 1.2.0 and does
> not support the current opam repository format[0], meaning that users
> cannot install new OPAM packages, get updates, ... (see #907042)
> 
> I would like to propose an update in Jessie to 1.2.2, the same version as
> in Stretch, and Ben suggested that I ask here to check nobody would be
> opposed to it, and to get advise on the process to follow.
 
sounds good to me.

> [0]: https://opam.ocaml.org/blog/deprecating-opam-1-2-0/


-- 
cheers,
Holger

---
holger@(debian|reproducible-builds).org


signature.asc
Description: PGP signature

Processed: merging

[Debian Bug Tracking System]

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

> forcemerge 906433 906554
Bug #906433 [src:icecast2] icecast2: FTBFS: aclocal-1.15: not found
Bug #906554 [src:icecast2] icecast2: FTBFS in buster/sid (aclocal-1.15: not 
found)
Merged 906433 906554
> stop
Stopping processing here.

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

Processed: forwarded, fixed-upstream

[Debian Bug Tracking System]

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

> forwarded 906606 https://github.com/Jehan/mypaint-brushes/issues/5
Bug #906606 [src:mypaint-brushes] mypaint-brushes: FTBFS in buster/sid 
(automake-1.13: not found)
Warning: Unknown package 'src:mypaint-brushes'
Set Bug forwarded-to-address to 
'https://github.com/Jehan/mypaint-brushes/issues/5'.
Warning: Unknown package 'src:mypaint-brushes'
> tags 906606 fixed-upstream
Bug #906606 [src:mypaint-brushes] mypaint-brushes: FTBFS in buster/sid 
(automake-1.13: not found)
Warning: Unknown package 'src:mypaint-brushes'
Added tag(s) fixed-upstream.
Warning: Unknown package 'src:mypaint-brushes'
> stop
Stopping processing here.

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

Bug#907306: marked as done (configure: error: gdk-pixbuf-query-loaders not found in path)

[Debian Bug Tracking System]

Your message dated Sun, 26 Aug 2018 16:20:22 +
with message-id 
and subject line Bug#907306: fixed in librsvg 2.40.20-3
has caused the Debian Bug report #907306,
regarding configure: error: gdk-pixbuf-query-loaders not found in path
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.)


-- 
907306: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907306
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:librsvg
Version: 2.40.20-2
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep --with gnome,gir
   dh_update_autotools_config -i
   debian/rules override_dh_autoreconf
make[1]: Entering directory '/<>'
dh_autoreconf --as-needed
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'

[... snipped ...]

mkdir_p='$(MKDIR_P)'
oldincludedir='/usr/include'
pdfdir='${docdir}'
prefix='/usr'
program_transform_name='s,x,x,'
psdir='${docdir}'
runstatedir='/run'
sbindir='${exec_prefix}/sbin'
sharedstatedir='${prefix}/com'
sysconfdir='/etc'
target_alias=''

## --- ##
## confdefs.h. ##
## --- ##

/* confdefs.h */
#define PACKAGE_NAME "RSVG"
#define PACKAGE_TARNAME "librsvg"
#define PACKAGE_VERSION "2.40.20"
#define PACKAGE_STRING "RSVG 2.40.20"
#define PACKAGE_BUGREPORT 
"https://bugzilla.gnome.org/enter_bug.cgi?product=librsvg;
#define PACKAGE_URL ""
#define PACKAGE "librsvg"
#define VERSION "2.40.20"
#define STDC_HEADERS 1
#define HAVE_SYS_TYPES_H 1
#define HAVE_SYS_STAT_H 1
#define HAVE_STDLIB_H 1
#define HAVE_STRING_H 1
#define HAVE_MEMORY_H 1
#define HAVE_STRINGS_H 1
#define HAVE_INTTYPES_H 1
#define HAVE_STDINT_H 1
#define HAVE_UNISTD_H 1
#define HAVE_DLFCN_H 1
#define LT_OBJDIR ".libs/"
#define HAVE_STRTOK_R 1

configure: exit 1
dh_auto_configure: ./configure --build=x86_64-linux-gnu --prefix=/usr 
--includedir=\${prefix}/include --mandir=\${prefix}/share/man 
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-silent-rules --libdir=\${prefix}/lib/x86_64-linux-gnu 
--libexecdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run 
--disable-maintainer-mode --disable-dependency-tracking --enable-pixbuf-loader 
--enable-introspection --enable-vala --enable-gtk-doc returned exit code 1
make[1]: *** [debian/rules:14: override_dh_auto_configure] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:8: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


The build was made in my autobuilder with either "dpkg-buildpackage -A"
(if the package allows it) or "dpkg-buildpackage -B" (if it does not).

Most probably, it also fails here in reproducible builds:

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

where you can get a full build log if you need it.

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

Thanks.
--- End Message ---
--- Begin Message ---
Source: librsvg
Source-Version: 2.40.20-3

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

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated librsvg package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 26 Aug 2018 16:34:42 +0100
Source: librsvg
Binary: librsvg2-dev librsvg2-2 librsvg2-common librsvg2-doc librsvg2-bin 
gir1.2-rsvg-2.0
Architecture: source
Version: 2.40.20-3
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME 

Bug#907328: ktorrent: FTBFS with Qt 5.11

[Santiago Vila]

Package: src:ktorrent
Version: 5.1.0-3
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep --with kf5
   dh_update_autotools_config -i
   dh_autoreconf -i
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure -Skf5 -- -DWITH_SYSTEM_GEOIP:BOOL=ON \
   -DBUILD_TESTING=OFF
cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None 
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var 
-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
"-GUnix Makefiles" -DCMAKE_BUILD_TYPE=Debian -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DKDE_INSTALL_USE_QT_SYS_PATHS=ON -DWITH_SYSTEM_GEOIP:BOOL=ON 
-DBUILD_TESTING=OFF ..
-- The C compiler identification is GNU 8.2.0
-- The CXX compiler identification is GNU 8.2.0

[... snipped ...]

[ 32%] Building CXX object 
plugins/search/CMakeFiles/ktorrent_search.dir/searchprefpage.cpp.o
cd /<>/obj-x86_64-linux-gnu/plugins/search && /usr/bin/c++  
-DKCOREADDONS_LIB -DQT_CONCURRENT_LIB -DQT_CORE_LIB -DQT_DBUS_LIB -DQT_GUI_LIB 
-DQT_NETWORK_LIB -DQT_NO_CAST_FROM_ASCII -DQT_NO_CAST_FROM_BYTEARRAY 
-DQT_NO_CAST_TO_ASCII -DQT_NO_CAST_TO_BYTEARRAY -DQT_NO_DEBUG 
-DQT_NO_URL_CAST_FROM_STRING -DQT_STRICT_ITERATORS -DQT_USE_FAST_OPERATOR_PLUS 
-DQT_USE_QSTRINGBUILDER -DQT_WEBKITWIDGETS_LIB -DQT_WEBKIT_LIB -DQT_WIDGETS_LIB 
-DQT_XML_LIB -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -Dktorrent_search_EXPORTS 
-I/<>/obj-x86_64-linux-gnu/plugins/search 
-I/<>/plugins/search 
-I/<>/obj-x86_64-linux-gnu/plugins/search/ktorrent_search_autogen/include
 -I/<>/libktcore -I/<>/obj-x86_64-linux-gnu/libktcore 
-I/<>/obj-x86_64-linux-gnu -isystem /usr/include/KF5/KConfigCore 
-isystem /usr/include/KF5 -isystem /usr/include/x86_64-linux-gnu/qt5 -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtCore -isystem /usr/lib/x86_64-linu
 x-gnu/qt5/mkspecs/linux-g++ -isystem /usr/include/KF5/KCoreAddons -isystem 
/usr/include/KF5/KI18n -isystem /usr/include/KF5/KCMUtils -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
/usr/include/KF5/KConfigWidgets -isystem /usr/include/KF5/KCodecs -isystem 
/usr/include/KF5/KWidgetsAddons -isystem /usr/include/KF5/KConfigGui -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtXml -isystem /usr/include/KF5/KAuth 
-isystem /usr/include/KF5/KService -isystem /usr/include/KF5/KParts -isystem 
/usr/include/KF5/KIOWidgets -isystem /usr/include/KF5/KIOCore -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtConcurrent -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtDBus -isystem /usr/include/KF5/KJobWidgets 
-isystem /usr/include/KF5/KCompletion -isystem /usr/include/KF5/KXmlGui 
-isystem /usr/include/KF5/KTextWidgets -isystem /usr/include/KF5/SonnetUi 
-isystem /usr/include/KF5/Solid -isystem /usr/
 include/KF5/libktorrent -isystem /usr/include/KF5/KArchive -isystem 
/usr/include/KF5/KCrash -isystem /usr/include/x86_64-linux-gnu -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtWebKitWidgets -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtWebKit -isystem 
/usr/include/KF5/KIconThemes -isystem /usr/include/KF5/KNotifications -isystem 
/usr/include/KF5/KDEWebKit  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -std=c++0x -fno-operator-names -Wall -Wextra -Wcast-align 
-Wchar-subscripts -Wformat-security -Wno-long-long -Wpointer-arith -Wundef 
-Wnon-virtual-dtor -Woverloaded-virtual -Werror=return-type -Wvla -Wdate-time 
-fexceptions -fPIC -fvisibility=hidden -fvisibility-inlines-hidden   -fPIC 
-std=gnu++11 -o CMakeFiles/ktorrent_search.dir/searchprefpage.cpp.o -c 
/<>/plugins/search/searchprefpage.cpp
/<>/plugins/search/searchprefpage.cpp: In constructor 
'kt::SearchPrefPage::SearchPrefPage(kt::SearchPlugin*, kt::SearchEngineList*, 
QWidget*)':
/<>/plugins/search/searchprefpage.cpp:72:49: error: invalid use of 
incomplete type 'class QButtonGroup'
 QButtonGroup* bg = new QButtonGroup(this);
 ^
In file included from 
/usr/include/x86_64-linux-gnu/qt5/QtWidgets/qcheckbox.h:44,
 from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/QCheckBox:1,
 from 
/<>/obj-x86_64-linux-gnu/plugins/search/ui_searchpref.h:16,
 from /<>/plugins/search/searchprefpage.h:27,
 from /<>/plugins/search/searchprefpage.cpp:22:
/usr/include/x86_64-linux-gnu/qt5/QtWidgets/qabstractbutton.h:53:7: note: 
forward declaration of 'class QButtonGroup'
 class QButtonGroup;
   ^~~~
/<>/plugins/search/searchprefpage.cpp:73:11: error: invalid use of 
incomplete type 'class 

Bug#907308: Bug depends on glibc version

[Daniel Lange]

as discussed with jwilk on irc:

This bug depends on the (g)libc version:

* stock Stretch is unaffected (libc6-2.24-11+deb9u3)
* Stretch with glibc from unstable (libc6-2.27-5) is affected
* stock Ubuntu 18.04.1 (libc6-2.27-3ubuntu1) is affected

Bug#907042: opam 1.2.0 is deprecated (jessie)

[Nicolas Braud-Santoni]

Dear LTS contributors,

I'm a co-maintainer of opam, the OCaml-specific dependencies manager, which
is currently broken in olstable: the version in Jessie is 1.2.0 and does
not support the current opam repository format[0], meaning that users
cannot install new OPAM packages, get updates, ... (see #907042)

I would like to propose an update in Jessie to 1.2.2, the same version as
in Stretch, and Ben suggested that I ask here to check nobody would be
opposed to it, and to get advise on the process to follow.

Please note that upstream is planning a change to a new repository format
(as part of releasing 2.0.0, which is currently in NEW) [1], but they plan
to keep a branch of the repository in 1.2 format, and accept important
updates there, so opam 1.2 will keep working for users of stable and LTS.


Best,

  nicoo


[0]: https://opam.ocaml.org/blog/deprecating-opam-1-2-0/
[1]: http://opam.ocaml.org/blog/opam-2-0-0-repo-upgrade-roadmap/


signature.asc
Description: PGP signature

Bug#904854: marked as done (gemma ftbfs in unstable (test failures and libquadmath not available on all architectures))

[Debian Bug Tracking System]

Your message dated Sun, 26 Aug 2018 15:34:38 +
with message-id 
and subject line Bug#904854: fixed in gemma 0.97+dfsg-4
has caused the Debian Bug report #904854,
regarding gemma ftbfs in unstable (test failures and libquadmath not available 
on all architectures)
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.)


-- 
904854: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904854
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gemma
Version: 0.97+dfsg-3
Severity: serious
Tags: sid buster

gemma ftbfs in unstable (test failures and libquadmath not available on all
architectures).  Please check the availability of libquadmath before explicitly
linking with libquadmath.

on amd64:

Ran 12 tests.

FAILED (failures=11)
tail -n 1 test.log | grep -q OK
make[1]: *** [Makefile:175: slow-check] Error 1
make[1]: Leaving directory '/<>/gemma-0.97+dfsg'
dh_auto_test: make -j4 check returned exit code 2
make: *** [debian/rules:18: build-arch] Error 2
--- End Message ---
--- Begin Message ---
Source: gemma
Source-Version: 0.97+dfsg-4

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated gemma package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 26 Aug 2018 17:00:21 +0200
Source: gemma
Binary: gemma gemma-doc
Architecture: source
Version: 0.97+dfsg-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 gemma  - Genome-wide Efficient Mixed Model Association
 gemma-doc  - Example folder for GEMMA
Closes: 902153 904854
Changes:
 gemma (0.97+dfsg-4) unstable; urgency=medium
 .
   * Team upload.
   * Don't link with libquadmath (Thanks for the patch to Adrian Bunk
 )
 Closes: #902153
   * No parallel test
 Closes: #904854
   * Fix installation of docs
   * debhelper 11
   * Standards-Version: 4.2.0
Checksums-Sha1:
 63b6d0b81016648f341a86efc7b8225aa46c3870 2097 gemma_0.97+dfsg-4.dsc
 b6270d70b063bb6701f92f8e98d7393d60aa6679 5152 gemma_0.97+dfsg-4.debian.tar.xz
Checksums-Sha256:
 31409c55ab96e11bb8faa9f9dcfa51a8e342842fdd17ce3fe8a0a0bf0ea3a0a5 2097 
gemma_0.97+dfsg-4.dsc
 ce2e3cb84cfc17df201721d8c0bfb5da4a684a466e5a7be71a266e14b2ee21f3 5152 
gemma_0.97+dfsg-4.debian.tar.xz
Files:
 6b51dd8aa7792f47eac88af6d286ea3b 2097 science optional gemma_0.97+dfsg-4.dsc
 f4fef645937ab8ac26f0484606f2318c 5152 science optional 
gemma_0.97+dfsg-4.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAluCw3wRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtGNJw/+MLl+AdkqKV17YtOaOEJYlm/VljnUf/Z/
PxB04g08fxqk+f5f+zPF534YEOqW1NiXZvC9hbGDjJ3tRJQ+U92rPWOK6+aEoZkF
IqrzYInQw3cwrB6PQrx3pRfc+JEYqLOMGWooxWYza67Hav0Szsg7rF3vwBvrAKCo
sUoA8pyIEGF7AqRtnw9LRcoPuRjR8wSbWeni0UbbJRv/d5gcF9wMgt60JJYh2bPR
Rc4VQvxCF1cAj4pYaPZhvBpCEfCt7+Ub02Vtfq5eT563bmgz92O4mYOoAjIfaDtT
yWKH/J3V8Fr1h4M4pJJ//Us6xBPs9/5DP4XBzwJq7gt5c0DKOdGZeLXIv+u+WxDN
iYIPf8ZVTp+ACUeLshj4Nt80/twVB8SDG2Bcj3UCkFFWBp45wA5LZ6oEa0sy4c6V
vhStSZ1MmtDrVI6GjFK3sTG21kEzC1h+ZlxMM9j0Lx7/q1sLES5aYn3uycG3CHno
V9f/bTf1OwOga88+KlfWN8mbrw85uvW6x/aLKCS53Z9MT/+7puB6DNJZyZCEhfsl
RLY0t3RcMLotVtWDzqWiJQ0RPJ+9LYtemomgqFjMcVTJT7VunRTN6nTBAFfXStrs
ww6fTlricCIWLOOIYZor3qmeSX+tM03NUqDVSWv3BEypMj0LVIN3zlOckUtYhz1O
PtpfBLrajbQ=
=1a6b
-END PGP SIGNATURE End Message ---

Bug#907007: marked as done (kmer FTBFS on arm64: recompile with -fPIC)

[Debian Bug Tracking System]

Your message dated Sun, 26 Aug 2018 15:34:50 +
with message-id 
and subject line Bug#907007: fixed in kmer 0~20150903+r2013-5
has caused the Debian Bug report #907007,
regarding kmer FTBFS on arm64: recompile with -fPIC
to be marked as done.

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

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


-- 
907007: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907007
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kmer
Version: 0~20150903+r2013-3
Severity: serious
Tags: patch ftbfs buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/buster/arm64/kmer.html
https://buildd.debian.org/status/fetch.php?pkg=kmer=arm64=0~20150903%2Br2013-4=1533471604=0

...
rm -f seatac/filter-heavychains.so && g++ -Wl,-z,relro -Wl,-z,now -shared  -o 
seatac/filter-heavychains.so seatac/filter-heavychains.o seatac/heavychains.o 
-pthread -ldl -lm
/usr/bin/ld: seatac/heavychains.o: relocation R_AARCH64_ADR_PREL_PG_HI21 
against symbol `_Z8x_comparPKvS0_' which may bind externally can not be used 
when making a shared object; recompile with -fPIC
/usr/bin/ld: seatac/heavychains.o: in function `StrandPair::process()':
./seatac/heavychains.H:410:(.text+0x8f0): dangerous relocation: unsupported 
relocation
/usr/bin/ld: seatac/heavychains.o: relocation R_AARCH64_ADR_PREL_PG_HI21 
against symbol `_Z8y_comparPKvS0_' which may bind externally can not be used 
when making a shared object; recompile with -fPIC
/usr/bin/ld: ./seatac/heavychains.H:410:(.text+0xd14): dangerous relocation: 
unsupported relocation
/usr/bin/ld: seatac/heavychains.o: relocation R_AARCH64_ADR_PREL_PG_HI21 
against symbol `_Z8y_comparPKvS0_' which may bind externally can not be used 
when making a shared object; recompile with -fPIC
/usr/bin/ld: ./seatac/heavychains.H:406:(.text+0x1224): dangerous relocation: 
unsupported relocation
/usr/bin/ld: seatac/heavychains.o: relocation R_AARCH64_ADR_PREL_PG_HI21 
against symbol `_Z8y_comparPKvS0_' which may bind externally can not be used 
when making a shared object; recompile with -fPIC
/usr/bin/ld: ./seatac/heavychains.H:410:(.text+0x26c0): dangerous relocation: 
unsupported relocation
/usr/bin/ld: seatac/heavychains.o: relocation R_AARCH64_ADR_PREL_PG_HI21 
against symbol `_Z8y_comparPKvS0_' which may bind externally can not be used 
when making a shared object; recompile with -fPIC
/usr/bin/ld: seatac/heavychains.o: in function 
`DPTree::sort_nodes(DPTree::kd_node)':
./seatac/heavychains.H:410:(.text._ZN6DPTree10sort_nodesENS_7kd_nodeE[_ZN6DPTree10sort_nodesENS_7kd_nodeE]+0x40):
 dangerous relocation: unsupported relocation
/usr/bin/ld: seatac/heavychains.o: relocation R_AARCH64_ADR_PREL_PG_HI21 
against symbol `_Z8x_comparPKvS0_' which may bind externally can not be used 
when making a shared object; recompile with -fPIC
/usr/bin/ld: 
./seatac/heavychains.H:410:(.text._ZN6DPTree10sort_nodesENS_7kd_nodeE[_ZN6DPTree10sort_nodesENS_7kd_nodeE]+0x44):
 dangerous relocation: unsupported relocation
collect2: error: ld returned 1 exit status
make[2]: *** [Make.rules:180: seatac/filter-heavychains.so] Error 1


Fix is attached.
Description: Use the same compile flags in all Linux builds, and include -fPIC
 atac .so were built without -fPIC on !amd64/ia64.
Author: Adrian Bunk 

--- kmer-0~20150903+r2013.orig/configure.sh
+++ kmer-0~20150903+r2013/configure.sh
@@ -57,12 +57,12 @@ if [ "x$target" = "x" ] ; then
   ;;
 Linux)
   target="Linux-i686$opts"
-  if [ `uname -m` = "x86_64" ] ; then
-target="Linux-amd64$opts"
-  fi
-  if [ `uname -m` = "ia64" ] ; then
-target="Linux-ia64$opts"
-  fi
+  #if [ `uname -m` = "x86_64" ] ; then
+  #  target="Linux-amd64$opts"
+  #fi
+  #if [ `uname -m` = "ia64" ] ; then
+  #  target="Linux-ia64$opts"
+  #fi
   ;;
 SunOS)
   target="solaris$opts"
@@ -221,11 +221,11 @@ EOF
 #  Linux, optimized
 CC:= $CC
 SHLIB_FLAGS   := -shared
-CFLAGS_COMPILE:= -D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE -D_REENTRANT 
-O3 -D_THREAD_SAFE -pthread -fmessage-length=0 -Wall -Wno-char-subscripts 
-funroll-loops -fexpensive-optimizations -finline-functions -fomit-frame-pointer
+CFLAGS_COMPILE:= -fPIC -D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE 
-D_REENTRANT -O3 -D_THREAD_SAFE -pthread -fmessage-length=0 -Wall 
-Wno-char-subscripts -funroll-loops -fexpensive-optimizations 
-finline-functions -fomit-frame-pointer
 CLDFLAGS  := -L/usr/local/lib
 CLIBS := -pthread -ldl
 CXX   := $CXX
-CXXFLAGS_COMPILE  := -D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE -D_REENTRANT 
-O3 

Bug#907267: openmpi: liggghts build on i386 times out

[Adrian Bunk]

On Sat, Aug 25, 2018 at 07:35:48PM +0200, Graham Inggs wrote:
> Source: openmpi
> Version: 3.1.1.real-6
> Severity: serious
> 
> Hi Alastair
> 
> The last two builds of liggghts on i386 [1] against openmpi
> 3.1.1.real-6 and 3.1.1.real-7 have timed out.

I do not know how reliable this is, but there is a pacakge
mpi-testsuite in unstable that has test hangs on all
32bit release architectures:
https://buildd.debian.org/status/package.php?p=mpi-testsuite

> Regards
> Graham
>...

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#902524: marked as done (xemacs21: FTBFS in buster/sid (does not work with recent debhelper))

[Debian Bug Tracking System]

Your message dated Sun, 26 Aug 2018 14:50:07 +
with message-id 
and subject line Bug#902524: fixed in xemacs21 21.4.24-6
has caused the Debian Bug report #902524,
regarding xemacs21: FTBFS in buster/sid (does not work with recent debhelper)
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.)


-- 
902524: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902524
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:xemacs21
Version: 21.4.24-5
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
chmod +x debian/makevarfile
debian/makevarfile "debian/var_file.pl" \
"MAJVERSION" "21" \
"VERSION" "21.4.24" \
"SUBNAME" "" \
"CONF_NAME" "x86_64-linux-gnu" \
"ARCH" "x86_64" \
"HTML_FILE_LOC" "debian/html" \
"TMP_FILE_LOC" "debian/tmp" \
"PREFIX" "usr" \
"TOPDIR" "/<>" \
"SUPPORT_BINS" "b2m etags gnuclient gnuattach gnudoit rcs-checkin ellcc"

[... snipped ...]

dh_md5sums -pxemacs21 -P/<>/debian/build/xemacs21
dh_builddeb -pxemacs21 -P/<>/debian/build/xemacs21
dpkg-deb: building package 'xemacs21' in '../xemacs21_21.4.24-5_all.deb'.
dh_testroot
dh_installdirs -pxemacs21-supportel 
-P/<>/debian/build/xemacs21-supportel
dh_installdirs: Compatibility levels before 9 are deprecated (level 5 in use)
dh_movefiles -pxemacs21-supportel 
-P/<>/debian/build/xemacs21-supportel
sh debian/move-el-files debian/tmp/usr/share/xemacs-21.4.24/lisp 
/<>/debian/build/xemacs21-supportel/usr/share/xemacs-21.4.24/lisp
End directory given ( 
/<>/debian/build/xemacs21-supportel/usr/share/xemacs-21.4.24/lisp 
) is not there... making it.
gzip -9nfr 
/<>/debian/build/xemacs21-supportel/usr/share/xemacs-21.4.24 || 
exit 0
( mkdir -p /<>/debian/build/xemacs21-supportel/usr/share/doc ; cd 
/<>/debian/build/xemacs21-supportel/usr/share/doc ; ln -sf 
xemacs21-support xemacs21-supportel )
dh_fixperms -pxemacs21-supportel 
-P/<>/debian/build/xemacs21-supportel
dh_installdeb -pxemacs21-supportel 
-P/<>/debian/build/xemacs21-supportel
dh_installdeb: Compatibility levels before 9 are deprecated (level 5 in use)
dh_shlibdeps -pxemacs21-supportel 
-P/<>/debian/build/xemacs21-supportel
dh_shlibdeps: Compatibility levels before 9 are deprecated (level 5 in use)
dh_gencontrol -pxemacs21-supportel 
-P/<>/debian/build/xemacs21-supportel
dh_makeshlibs -pxemacs21-supportel 
-P/<>/debian/build/xemacs21-supportel
dh_md5sums -pxemacs21-supportel 
-P/<>/debian/build/xemacs21-supportel
dh_builddeb -pxemacs21-supportel 
-P/<>/debian/build/xemacs21-supportel
dpkg-deb: building package 'xemacs21-supportel' in 
'../xemacs21-supportel_21.4.24-5_all.deb'.
dh_testroot
dh_installdirs -pxemacs21-support 
-P/<>/debian/build/xemacs21-support
dh_installdirs: Compatibility levels before 9 are deprecated (level 5 in use)
dh_movefiles -pxemacs21-support -P/<>/debian/build/xemacs21-support
dh_movefiles: Compatibility levels before 9 are deprecated (level 5 in use)
mkdir -p /<>/debian/build/xemacs21-support/usr/lib/xemacs-21.4.24
cp 
/<>/debian/build/xemacs21-support/usr/share/xemacs-21.4.24/etc/xemacs-icon*.*
 /<>/debian/build/xemacs21-support/usr/share/icons
cp debian/00debian.el 
/<>/debian/build/xemacs21-support/etc/xemacs21/site-start.d/
cp debian/site-start.el 
/<>/debian/build/xemacs21-support/usr/share/xemacs21/site-packages/lisp
cp debian/debian-rundir.el 
/<>/debian/build/xemacs21-support/usr/share/xemacs21/site-packages/lisp
rm -f 
/<>/debian/build/xemacs21-support/usr/share/info/xemacs21/dir*
( cd /<>/debian/build/xemacs21-support ; find . -name .cvsignore | 
xargs rm -f )
rm 
/<>/debian/build/xemacs21-support/usr/share/xemacs-21.4.24/etc/check_cygwin_setup.sh
dh_installdocs --package=xemacs21-support 
-P/<>/debian/build/xemacs21-support
dh_installdocs: Compatibility levels before 9 are deprecated (level 5 in use)
dh_installchangelogs -pxemacs21-support 
-P/<>/debian/build/xemacs21-support
dh_installchangelogs: Compatibility levels before 9 are deprecated (level 5 in 
use)
mv 
/<>/debian/build/xemacs21-support/usr/share/doc/xemacs21-support/ChangeLog
 
/<>/debian/build/xemacs21-support/usr/share/doc/xemacs21-support/changelog
mv: cannot stat 
'/<>/debian/build/xemacs21-support/usr/share/doc/xemacs21-support/ChangeLog':
 No such file or directory
debian/PackagesMakefile:68: recipe for target 'xemacs21-support' failed
make[1]: *** [xemacs21-support] Error 1
make[1]: Leaving directory '/<>'
debian/rules:123: recipe for 

Bug#899548: marked as done (ibus-table: Invalid maintainer address pkg-ime-de...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Sun, 26 Aug 2018 14:42:24 +
with message-id 
and subject line Bug#899548: fixed in ibus-table 1.9.20-1
has caused the Debian Bug report #899548,
regarding ibus-table: Invalid maintainer address 
pkg-ime-de...@lists.alioth.debian.org
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.)


-- 
899548: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899548
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ibus-table
Version: 1.9.14-3
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of ibus-table,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package ibus-table since the list address
pkg-ime-de...@lists.alioth.debian.org used in the Maintainer: field was
not transferred to the alioth-lists service that provides a
continuation for the lists in the @lists.alioth.debian.org domain.

Addresses that were not migrated have been disabled some time  ago. As
a result your package is now in violation of a "must" in the Debian
policy (3.3, working email address), making it unfit for release.

Please fix this before long. Among other reasons, keep in mind bug
reports and important notifications about your package might not reach
you.

Your options:

* Upload another version with a new maintainer address of your choice,

* Migrate the list to the new system. This is still possible,
  please appoint a Debian developer as a list owner first, then
  contact the alioth lists migration team 
  and provide all the necessary information.

  More information about the new service can be found here:
  

* More options, even if imperfect, can be found at
  


The first option is probably suitable only if the address was used just
in a small number of packages since this requires an upload for each of
them. To our knowledge, the usage count of
pkg-ime-de...@lists.alioth.debian.org is 68.

The second option is available for a limited time only, by end of
May 2018 the most. So if you're interested in going this way, start the
process as soon as possible.

Note, as mails to the maintainer address will not get through, this
bugreport is Cc'ed (X-Debbugs-CC:) to all uploaders of the package.

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ibus-table
Source-Version: 1.9.20-1

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

Debian distribution maintenance software
pp.
Boyuan Yang <073p...@gmail.com> (supplier of updated ibus-table package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 26 Aug 2018 09:32:31 -0400
Source: ibus-table
Binary: ibus-table
Architecture: source
Version: 1.9.20-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Input Method Team 
Changed-By: Boyuan Yang <073p...@gmail.com>
Description:
 ibus-table - table engine for IBus
Closes: 899548 906264
Changes:
 ibus-table (1.9.20-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream version 1.9.20 (Closes: #906264).
   * debian/control:
 + Use debian-input-method mailing list for maintainer field.
   (Closes: #899548)
 + Use Salsa platform for Vcs fields.
 + Apply "wrap-and-sort -abst".
 + Bump debhelper compat to v11.
 + Bump Standards-Version to 4.2.1.
 - Remove explicit dependency to dh-autoreconf since new debhelper
   will pull it in automatically.
   * debian/rules:
 + Don't explicitly use dh --with autoreconf, not needed anymore.
 + Enable full hardening.
   * debian/patches: Drop patch 0002, merged upstream.
   * debian/changelog: Remove trailing spaces.
Checksums-Sha1:
 631ef67565fa70b58480560eb245b5a99faeb5f4 2051 ibus-table_1.9.20-1.dsc
 33ab80525f7aeff2007ca2f7d95624d933c927e0 469172 ibus-table_1.9.20.orig.tar.gz
 f7983ae40acc98ab95f3f8d1d50c45a448e33826 4644 

Bug#903338: marked as done (opencryptoki: FTBFS in buster/sid (dh_installdocs: Cannot find "README"))

[Debian Bug Tracking System]

Your message dated Sun, 26 Aug 2018 14:43:12 +
with message-id 
and subject line Bug#903338: fixed in opencryptoki 3.8.1+dfsg-3.1
has caused the Debian Bug report #903338,
regarding opencryptoki: FTBFS in buster/sid (dh_installdocs: Cannot find 
"README")
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.)


-- 
903338: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903338
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:opencryptoki
Version: 3.8.1+dfsg-3
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-arch
dh build-arch
   dh_update_autotools_config -a
   dh_autoreconf -a
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
configure.ac:11: installing './compile'
configure.ac:5: installing './config.guess'

[... snipped ...]

 /bin/mkdir -p 
'/<>/opencryptoki-3.8.1+dfsg/debian/tmp/lib/systemd/system'
 /usr/bin/install -c -m 644 pkcsslotd.service tmpfiles.conf 
'/<>/opencryptoki-3.8.1+dfsg/debian/tmp/lib/systemd/system'
make  install-data-hook
make[5]: Entering directory '/<>/opencryptoki-3.8.1+dfsg/misc'
mkdir -p /<>/opencryptoki-3.8.1+dfsg/debian/tmp/usr/lib/tmpfiles.d
cp tmpfiles.conf 
/<>/opencryptoki-3.8.1+dfsg/debian/tmp/usr/lib/tmpfiles.d/opencryptoki.conf
/bin/chmod 0644 
/<>/opencryptoki-3.8.1+dfsg/debian/tmp/usr/lib/tmpfiles.d/opencryptoki.conf
rm -f 
/<>/opencryptoki-3.8.1+dfsg/debian/tmp/usr/lib/systemd/system/tmpfiles.conf
make[5]: Leaving directory '/<>/opencryptoki-3.8.1+dfsg/misc'
make[4]: Leaving directory '/<>/opencryptoki-3.8.1+dfsg/misc'
make[3]: Leaving directory '/<>/opencryptoki-3.8.1+dfsg/misc'
make[3]: Entering directory '/<>/opencryptoki-3.8.1+dfsg'
make[4]: Entering directory '/<>/opencryptoki-3.8.1+dfsg'
make[4]: Nothing to be done for 'install-exec-am'.
make[4]: Nothing to be done for 'install-data-am'.
make[4]: Leaving directory '/<>/opencryptoki-3.8.1+dfsg'
make[3]: Leaving directory '/<>/opencryptoki-3.8.1+dfsg'
make[2]: Leaving directory '/<>/opencryptoki-3.8.1+dfsg'
# create links to .so-files in usr/lib
( cd debian/tmp/usr/lib/x86_64-linux-gnu && \
 for FILE in ./opencryptoki/*.so.* ./opencryptoki/stdll/*.so.*; \
 do \
ln -s $FILE ; \
 done \
)
# Remove broken symlinks in /usr/lib/pkcs11/
cd debian/tmp/usr/lib/x86_64-linux-gnu/pkcs11 && rm -f \
libopencryptoki.so PKCS11_API.so
# Removing useless files
rm -rf debian/tmp/etc/ld.so.conf.d
rm -rf debian/tmp/etc/init.d
rm -f debian/tmp/usr/include/Makefile*
rm -f debian/tmp/usr/include/*/Makefile*
rm -f debian/tmp/usr/lib/x86_64-linux-gnu/opencryptoki/*.la \
debian/tmp/usr/lib/x86_64-linux-gnu/opencryptoki/stdll/*.la
rm -f debian/tmp/lib/systemd/system/tmpfiles.conf
make[1]: Leaving directory '/<>/opencryptoki-3.8.1+dfsg'
   debian/rules override_dh_install
make[1]: Entering directory '/<>/opencryptoki-3.8.1+dfsg'
dh_install --fail-missing  --sourcedir=debian/tmp
dh_install: Please use dh_missing --list-missing/--fail-missing instead
dh_install: This feature will be removed in compat 12.
make[1]: Leaving directory '/<>/opencryptoki-3.8.1+dfsg'
   dh_installdocs -a
dh_installdocs: Cannot find (any matches for) "README" (tried in .)

debian/rules:8: recipe for target 'binary-arch' failed
make: *** [binary-arch] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-arch subprocess returned 
exit status 2


The build was made with "dpkg-buildpackage -B" in my autobuilder.
Most probably, it also fails here in reproducible builds:

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

[ Note: There has been a recent change in debhelper behaviour, the current
  behaviour is the intended one. See Bug #903133 for details ].

Thanks.
--- End Message ---
--- Begin Message ---
Source: opencryptoki
Source-Version: 3.8.1+dfsg-3.1

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

Bug#903343: marked as done (voikko-fi: FTBFS in buster/sid (dh_installdocs: Cannot find "README"))

[Debian Bug Tracking System]

Your message dated Sun, 26 Aug 2018 14:43:43 +
with message-id 
and subject line Bug#903343: fixed in voikko-fi 2.2-1.1
has caused the Debian Bug report #903343,
regarding voikko-fi: FTBFS in buster/sid (dh_installdocs: Cannot find "README")
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.)


-- 
903343: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903343
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:voikko-fi
Version: 2.2-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-arch
dh build-arch --fail-missing
   dh_update_autotools_config -a -O--fail-missing
   dh_auto_configure -a -O--fail-missing
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
/usr/bin/make vvfst EXTRA_LEX=vocabulary/erikoisalat/linux-distributions.lex
make[2]: Entering directory '/<>'
python3 vvfst/generate_taivutuskaavat.py   --destdir=vvfst
python3 vvfst/generate_lex.py  --destdir=vvfst
##
touch vvfst/joukahainen.lexc.stamp
python3 vvfst/filter_lexc.py vvfst/all.lexc   vvfst/root.lexc 
vvfst/taivutuskaavat.lexc vvfst/joukahainen-ee.lexc vvfst/joukahainen-em.lexc 
vvfst/joukahainen-ep.lexc vvfst/joukahainen-es.lexc vvfst/joukahainen-h.lexc 
vvfst/joukahainen-l.lexc vvfst/joukahainen-n.lexc vvfst/joukahainen-nl.lexc 
vvfst/joukahainen-t.lexc vvfst/joukahainen-p.lexc vvfst/joukahainen-a.lexc 
vvfst/joukahainen-s.lexc vvfst/joukahainen-c.lexc vvfst/suomi.lexc 
vvfst/olla-ei.lexc vvfst/poikkeavat.lexc vvfst/lukusanat.lexc 
vvfst/asemosanat.lexc vvfst/seikkasanat.lexc vvfst/suhdesanat.lexc
sed -e "s,VVFST_BUILDDIR,vvfst," < vvfst/main.foma.in > vvfst/main.foma

[... snipped ...]

7.5 MB. 429607 states, 490840 arcs, Cyclic.
Writing AT file: vvfst/all.att
! grep ']]' vvfst/all.att
cat vvfst/all.att | sort -n | voikkovfstc -o vvfst/mor.vfst
Symbols: 288
Transitions: 490840
Final states: 1
Overflow cells: 1
python3 vvfst/autocorrect_to_lexc.py vocabulary/autocorrect/fi.xml 
vvfst/autocorrect.lexc
sed -e "s,VVFST_BUILDDIR,vvfst," < vvfst/autocorrect.foma.in > 
vvfst/autocorrect.foma
foma -f vvfst/autocorrect.foma 2>&1 | grep -v "defined but not used"
Root...Building lexicon...
228
Determinizing...
Minimizing...
Done!
22.8 kB. 1188 states, 1411 arcs, 227 paths.
defined Lexicon: 22.8 kB. 1188 states, 1411 arcs, 227 paths.
variable flag-is-epsilon = ON
22.8 kB. 1188 states, 1411 arcs, 227 paths.
22.8 kB. 1188 states, 1411 arcs, 227 paths.
Writing AT file: vvfst/autocorrect.att
cat vvfst/autocorrect.att | sort -n | voikkovfstc -o vvfst/autocorr.vfst
Symbols: 22
Transitions: 1411
Final states: 1
Overflow cells: 0
sed -e "s/SM_VOIKKO_VARIANT/standard/; s/SM_VOIKKO_DESCRIPTION/suomi 
(perussanasto)/; s/SM_VERSION/2.2/; s/SM_PATCHINFO//; 
s/SM_BUILDCONFIG/GENLEX_OPTS= 
EXTRA_LEX=vocabulary\\/erikoisalat\\/linux-distributions.lex/; 
s/SM_BUILDDATE/Fri, 08 Sep 2017 13:05:40 +/" < vvfst/index.txt.in > 
vvfst/index.txt
make[2]: Leaving directory '/<>'
make[1]: Leaving directory '/<>'
   dh_auto_test -a -O--fail-missing
 fakeroot debian/rules binary-arch
dh binary-arch --fail-missing
   dh_testroot -a -O--fail-missing
   dh_prep -a -O--fail-missing
   debian/rules override_dh_auto_install
make[1]: Entering directory '/<>'
/usr/bin/make vvfst-install 
DESTDIR=/<>/debian/voikko-fi/usr/lib/voikko
make[2]: Entering directory '/<>'
install -m 755 -d 
/<>/debian/voikko-fi/usr/lib/voikko/5/mor-standard
install -m 644 vvfst/index.txt vvfst/mor.vfst vvfst/autocorr.vfst 
/<>/debian/voikko-fi/usr/lib/voikko/5/mor-standard
make[2]: Leaving directory '/<>'
make[1]: Leaving directory '/<>'
   dh_installdocs -a -O--fail-missing
dh_installdocs: Cannot find (any matches for) "README" (tried in .)

debian/rules:7: recipe for target 'binary-arch' failed
make: *** [binary-arch] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-arch subprocess returned 
exit status 2


The build was made with "dpkg-buildpackage -B" in my autobuilder.
Most probably, it also fails here in reproducible builds:

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

[ Note: There has been a recent change in debhelper behaviour, the current
  behaviour is the intended one. See Bug #903133 for details ].

Thanks.
--- End Message ---
--- Begin Message ---
Source: voikko-fi
Source-Version: 2.2-1.1

We believe that the bug you 

Bug#897551: marked as done (usbview: FTBFS: convert-im6.q16: unable to open file `/tmp/magick-20115vbmutCN0nGsV': No such file or directory @ error/constitute.c/ReadImage/544.)

[Debian Bug Tracking System]

Your message dated Sun, 26 Aug 2018 14:27:26 +0100
with message-id <20180826132726.gc2...@sirena.org.uk>
and subject line Fixed a while ago
has caused the Debian Bug report #897551,
regarding usbview: FTBFS: convert-im6.q16: unable to open file 
`/tmp/magick-20115vbmutCN0nGsV': No such file or directory @ 
error/constitute.c/ReadImage/544.
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.)


-- 
897551: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897551
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: usbview
Version: 2.0-21-g6fe2f4f-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20180502 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[2]: Entering directory '/<>'
> convert -geometry $(basename $(dirname $(dirname 
> hicolor/64x64/apps/usbview_icon.xpm))) usbview_icon.svg 
> hicolor/64x64/apps/usbview_icon.xpm
> convert-im6.q16: delegate failed `'rsvg-convert' -o '%o' '%i'' @ 
> error/delegate.c/InvokeDelegate/1919.
> convert-im6.q16: unable to open file `/tmp/magick-20115vbmutCN0nGsV': No such 
> file or directory @ error/constitute.c/ReadImage/544.
> convert-im6.q16: no images defined `hicolor/64x64/apps/usbview_icon.xpm' @ 
> error/convert.c/ConvertImageCommand/3258.
> make[2]: *** [Makefile:964: hicolor/64x64/apps/usbview_icon.xpm] Error 1

The full build log is available from:
   http://aws-logs.debian.net/2018/05/02/usbview_2.0-21-g6fe2f4f-1_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
An upload a while ago fixed this, for some reason only one of the bugs
listed in the changelog got closed.


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

Bug#907306: configure: error: gdk-pixbuf-query-loaders not found in path

[Simon McVittie]

On Sun, 26 Aug 2018 at 14:20:14 +0200, Michael Biebl wrote:
> On 8/26/18 12:50, Simon McVittie wrote:
> > Looking at librsvg, it seems we might be able to reinstate
> > gdk-pixbuf-query-loaders in libgdk-pixbuf2.0-dev but rename it to
> > $(DEB_HOST_ARCH)-gdk-pixbuf-query-loaders, and then change librsvg to
> > use AC_CHECK_TOOL instead of AC_PATH_PROGS; or install
> > gdk-pixbuf-query-loaders in /usr/lib/$(DEB_HOST_MULTIARCH) instead of
> > /usr/bin, then add that to PATH when building librsvg. That would mean
> > we can't cross-compile librsvg on a build machine that can't run host
> > binaries, but we'd still be able to cross-compile other gdk-pixbuf users.
> 
> Why exactly so we need gdk-pixbuf-query-loaders?
> Looking at
> https://salsa.debian.org/gnome-team/librsvg/blob/debian/master/gdk-pixbuf-loader/Makefile.am
> 
> it seems we require it for two cases:
> a/ It's used in the rsvg-loader test
> b/ It's called during make install
> 
> b/ is handled by triggers in Debian and already conditionalized by DESTDIR
> 
> So maybe an alternative could be to simply skip building the rsvg-loader
> test.

I think I have a patch that works for (a) without modifying gdk-pixbuf:
we already install gdk-pixbuf-query-loaders in
/usr/lib/$(DEB_HOST_MULTIARCH)/gdk-pixbuf-2.0, so I just need to set
GDK_PIXBUF_QUERYLOADERS. Testing now.

smcv

Bug#907322: jekyll: Requires internet access to build

[Jeremy Bicha]

Source: jekyll
Version: 3.8.3+dfsg-2
Severity: serious
X-Debbugs-CC: prav...@debian.org

jekyll fails to build from source if the build environment does not
have Internet access.

This can be seen in Debian's reproducible builds and Ubuntu's builders.

I am filing this as serious because it is a violation of Debian Policy
§ 4.9 which says "no required targets may attempt network access".

By the way, there is a recently added patch,
0004_skip_test_autopkgtest.patch, that is not listed in
debian/patches/series. I enabled it in my local testing, but it didn't
fix the build failure.

Build logs
===
https://launchpad.net/ubuntu/+source/jekyll/3.8.3+dfsg-2/+build/15298887

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/jekyll.html
(see test history and rbuild)

Build log excerpt


RUBYLIB=/build/1st/jekyll-3.8.3+dfsg/debian/jekyll/usr/lib/ruby/vendor_ruby:.
GEM_PATH=debian/jekyll/usr/share/rubygems-integration/all:/var/lib/gems/2.5.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all
ruby2.5 -S rake -f debian/ruby-tests.rake
/usr/bin/ruby2.5 -w -I"lib:lib:test"
"/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb"
"test/test_ansi.rb" "test/test_cleaner.rb" "test/test_coffeescript.rb"
"test/test_collections.rb" "test/test_command.rb"
"test/test_commands_serve.rb" "test/test_commands_serve_servlet.rb"
"test/test_configuration.rb" "test/test_data_reader.rb"
"test/test_doctor_command.rb" "test/test_document.rb"
"test/test_drop.rb" "test/test_entry_filter.rb" "test/test_excerpt.rb"
"test/test_excerpt_drop.rb" "test/test_filters.rb"
"test/test_front_matter_defaults.rb" "test/test_generated_site.rb"
"test/test_kramdown.rb" "test/test_layout_reader.rb"
"test/test_liquid_extensions.rb" "test/test_liquid_renderer.rb"
"test/test_log_adapter.rb" "test/test_page.rb"
"test/test_page_without_a_file.rb" "test/test_path_sanitization.rb"
"test/test_rdiscount.rb" "test/test_redcarpet.rb"
"test/test_regenerator.rb" "test/test_related_posts.rb"
"test/test_sass.rb" "test/test_site_drop.rb"
"test/test_static_file.rb" "test/test_url.rb" "test/test_utils.rb"
# -
# SPECS AND TESTS ARE RUNNING WITH WARNINGS OFF.
# SEE: https://github.com/Shopify/liquid/issues/730
# SEE: https://github.com/jekyll/jekyll/issues/4719
# -

# Running tests with run options --seed 6667:

F

Finished tests in 298.388558s, 2.2018 tests/s, 3.6865 assertions/s.


Failure:
Minitest::Result#test_: Utils::Internet.connected? should return true
if there's internet.
[/build/1st/jekyll-3.8.3+dfsg/test/test_utils.rb:420]
Minitest::Assertion: Expected false to be truthy.

657 tests, 1100 assertions, 1 failures, 0 errors, 0 skips
Coverage report generated for Unit Tests to
/build/1st/jekyll-3.8.3+dfsg/coverage. 3257 / 3815 LOC (85.37%)
covered.
rake aborted!
Command failed with status (1): [ruby -w -I"lib:lib:test"
"/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb"
"test/test_ansi.rb" "test/test_cleaner.rb" "test/test_coffeescript.rb"
"test/test_collections.rb" "test/test_command.rb"
"test/test_commands_serve.rb" "test/test_commands_serve_servlet.rb"
"test/test_configuration.rb" "test/test_data_reader.rb"
"test/test_doctor_command.rb" "test/test_document.rb"
"test/test_drop.rb" "test/test_entry_filter.rb" "test/test_excerpt.rb"
"test/test_excerpt_drop.rb" "test/test_filters.rb"
"test/test_front_matter_defaults.rb" "test/test_generated_site.rb"
"test/test_kramdown.rb" "test/test_layout_reader.rb"
"test/test_liquid_extensions.rb" "test/test_liquid_renderer.rb"
"test/test_log_adapter.rb" "test/test_page.rb"
"test/test_page_without_a_file.rb" "test/test_path_sanitization.rb"
"test/test_rdiscount.rb" "test/test_redcarpet.rb"
"test/test_regenerator.rb" "test/test_related_posts.rb"
"test/test_sass.rb" "test/test_site_drop.rb"
"test/test_static_file.rb" "test/test_url.rb" "test/test_utils.rb" ]

Tasks: TOP => default => test
(See full trace by running task with --trace)
ERROR: Test "ruby2.5" failed. Exiting.


Thanks,
Jeremy Bicha

Bug#880765: marked as done (cvsgraph build depends on removed libgd2*-dev provides)

[Debian Bug Tracking System]

Your message dated Sun, 26 Aug 2018 13:33:58 +
with message-id 
and subject line Bug#880765: fixed in cvsgraph 1.7.0-5
has caused the Debian Bug report #880765,
regarding cvsgraph build depends on removed libgd2*-dev provides
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.)


-- 
880765: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880765
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cvsgraph
Version: 1.7.0-4
Severity: serious
Tags: buster sid

The following packages have unmet dependencies:
 builddeps:cvsgraph : Depends: libgd2-noxpm-dev but it is not installable or
   libgd2-xpm-dev but it is not installable


Please change the build dependency to libgd-dev.
--- End Message ---
--- Begin Message ---
Source: cvsgraph
Source-Version: 1.7.0-5

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

Debian distribution maintenance software
pp.
Mark Brown  (supplier of updated cvsgraph package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 26 Aug 2018 14:11:15 +0100
Source: cvsgraph
Binary: cvsgraph
Architecture: source amd64
Version: 1.7.0-5
Distribution: unstable
Urgency: low
Maintainer: Mark Brown 
Changed-By: Mark Brown 
Description:
 cvsgraph   - Create a tree of revisions/branches from a CVS/RCS file
Closes: 880765
Changes:
 cvsgraph (1.7.0-5) unstable; urgency=low
 .
   * Change libgd build dependency to libgd-dev (closes: #880765).
Checksums-Sha1:
 897e27a84ea27784916161e31d33d957d577ebb0 1426 cvsgraph_1.7.0-5.dsc
 585191a3da24160bd5ebc7d7b191ea5176eda4fd 8896 cvsgraph_1.7.0-5.debian.tar.xz
 a519163ada52c4988ae89fe4a744bebf79b7a246 116144 
cvsgraph-dbgsym_1.7.0-5_amd64.deb
 2cb1446027e1912a2001c6886282fe402f7d970d 7052 cvsgraph_1.7.0-5_amd64.buildinfo
 c2d90f01ada47cb5f34d29aaba2e4ddb47dd5187 80268 cvsgraph_1.7.0-5_amd64.deb
Checksums-Sha256:
 12f884b9a8d36ac611ed033630a70cdc6bb6c00ab79c085d67459597e78d511c 1426 
cvsgraph_1.7.0-5.dsc
 1aa00413093a4f101284e4026693abb7dad3c827fe898f92266dc91f45812c96 8896 
cvsgraph_1.7.0-5.debian.tar.xz
 4b37bb779312c977b5dec6e0439f30b17c73f1c3b2f6dbb8759a95bcae99a1dd 116144 
cvsgraph-dbgsym_1.7.0-5_amd64.deb
 1a48e487590aba8fbc9cb1b3868f01bd12915194c1c79da52b76a5d3d047aa6a 7052 
cvsgraph_1.7.0-5_amd64.buildinfo
 8cd6e1f3297ef3c68e29863a786a4ca71d39a9232ede0bc28cf209a5b82e5e4b 80268 
cvsgraph_1.7.0-5_amd64.deb
Files:
 590117ecdc89c589ecb0dde3807859f4 1426 devel optional cvsgraph_1.7.0-5.dsc
 e509b7ddcfa577b3adbb428cd0565746 8896 devel optional 
cvsgraph_1.7.0-5.debian.tar.xz
 4e99c6e30bdd1ad8ba52ae0557af2ad4 116144 debug optional 
cvsgraph-dbgsym_1.7.0-5_amd64.deb
 ce35c1a0e50b3234ac02cf1709cacf9e 7052 devel optional 
cvsgraph_1.7.0-5_amd64.buildinfo
 8374ae827c021337281b048f9d999a1b 80268 devel optional 
cvsgraph_1.7.0-5_amd64.deb

-BEGIN PGP SIGNATURE-

iQFHBAEBCgAxFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAluCqD4THGJyb29uaWVA
ZGViaWFuLm9yZwAKCRAk1otyXVSH0E5uB/0ZRTE4uQm8g2rn3x9PXfw/op9HeNGX
ThNmcsNWRV1Zm60haH/V1p25ZsLRmj2UNUwXzWeEIUoZ/+3wVtgPAJFQYV3P3c5a
khRhMxzXsW4dfT1qXxCF/jgQN2iZi13LrwwqmnWF5Mx/gGkCXtwisMbjKgCFuu5E
ytATsZm3o07XjT9SsY3e8PjFnf7Kl7QKlQrLG7fBC87iVw8JlIQRhk6SOW3hWHuJ
Iq8zosTXI/McGGhsg9fQT01NbhIz927vTTrI/+ijRDaehCW1W9iwexi0WKqwd6qz
uS491K9i23UERAoc01f9b5ZPnBvZZdK69corMOPGfYkKJMzE2oIMYfbf
=VDZN
-END PGP SIGNATURE End Message ---

Bug#906618: marked as done (libthread-pool builds with -march=native)

[Debian Bug Tracking System]

Your message dated Sun, 26 Aug 2018 13:19:26 +
with message-id 
and subject line Bug#906618: fixed in libthread-pool 1.0.0-2
has caused the Debian Bug report #906618,
regarding libthread-pool builds with -march=native
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.)


-- 
906618: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906618
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libthread-pool
Version: 1.0.0-1
Severity: serious

-march=native must not be used since the resulting code will only run
on machines compatible with whatever buildd built the package.
--- End Message ---
--- Begin Message ---
Source: libthread-pool
Source-Version: 1.0.0-2

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated libthread-pool package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 26 Aug 2018 14:56:11 +0200
Source: libthread-pool
Binary: libthread-pool0 libthread-pool-dev
Architecture: source
Version: 1.0.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 libthread-pool-dev - C++ thread pool library (devel)
 libthread-pool0 - C++ thread pool library
Closes: 906618
Changes:
 libthread-pool (1.0.0-2) unstable; urgency=medium
 .
   * Do not build with -march=native
 Closes: #906618
   * Standards-Version: 4.2.0
Checksums-Sha1:
 3bce7fe1926557236238154fd578fab843b4aa83 2106 libthread-pool_1.0.0-2.dsc
 e0f1ff5c1573d9352573a4892714ce690280f6c8 3180 
libthread-pool_1.0.0-2.debian.tar.xz
Checksums-Sha256:
 4dc273b9b080331b309bf978deffb02ece33951959494ce0ddda8b6b72b5f55f 2106 
libthread-pool_1.0.0-2.dsc
 8d0da22b84491a5125646712194bf28d75a3e33d04092bf2ab4b668c21eeb514 3180 
libthread-pool_1.0.0-2.debian.tar.xz
Files:
 a6243040c1142ee7a3e51ea811e02cd5 2106 science optional 
libthread-pool_1.0.0-2.dsc
 b309bf4f8d61009bdaf098e8bf605b99 3180 science optional 
libthread-pool_1.0.0-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAluCpAARHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtEBSw//USoW5G2J+uoGEXHMz/lHdFSvR+bjRZuq
JTSlAVZCJoM7udwPNZ4hBgtjD4N+m2Bt+bF2d1brHFUTL6qHkI1Sh8EiDC0P3wAv
PzAabtb+P4PQdZFnaKVXoM5D4zVai2MbQC2aUKzRWigoMx7jH8LvtIf2NhIIRmOQ
4wtPcUNMXoQwVEYB6rhG5il42qfU4LlDUx/0TpbNuel4elvry3LQnOdf2LfI6/I3
gD1GAWwZcvlbPJqFNv3IrCUde1Rjbmx2YgzSVK3tm/SJ3KoX2mrLaR9ikSH3PyNU
+HzpB3yDvqnajG8a9bNSPRlN68+lfi3CjDN2aAPRwEolOiuU/1kcAwOV3xS3Pcbr
0goUbhokv9Lp8chxczepQBtmIeNIBnO6aivZWp8WZxO8CyeXRj+KJ5ZSUjrVVDEI
50XVjDKS76EMgATB0VNh32+3Cb/KXbs+ABs2DcIb35YcK9ir/JyGqp1Vrz50nKZ+
gac6gnVx4IIhogYuVr8uaVSwu/OUw7PMBkrKIlLpCQuUHLrQornByIsa7MQzJ5Yw
JDk/bTn84AUAlqts4JCqf06dkwANB5aQa4ENUCWmvc/iu8etkMtFZn7ruo5cXh5w
cSmgJViXiGyxgsEZ9r+TqJm3C/Fmfsu0O1Eh5gbHNRwIz5AvK2tFMk8rc/jSzEHT
bl9sNaf8tPU=
=ZONy
-END PGP SIGNATURE End Message ---

Bug#907306: configure: error: gdk-pixbuf-query-loaders not found in path

[Michael Biebl]

On 8/26/18 12:50, Simon McVittie wrote:
> Looking at librsvg, it seems we might be able to reinstate
> gdk-pixbuf-query-loaders in libgdk-pixbuf2.0-dev but rename it to
> $(DEB_HOST_ARCH)-gdk-pixbuf-query-loaders, and then change librsvg to
> use AC_CHECK_TOOL instead of AC_PATH_PROGS; or install
> gdk-pixbuf-query-loaders in /usr/lib/$(DEB_HOST_MULTIARCH) instead of
> /usr/bin, then add that to PATH when building librsvg. That would mean
> we can't cross-compile librsvg on a build machine that can't run host
> binaries, but we'd still be able to cross-compile other gdk-pixbuf users.

Why exactly so we need gdk-pixbuf-query-loaders?
Looking at
https://salsa.debian.org/gnome-team/librsvg/blob/debian/master/gdk-pixbuf-loader/Makefile.am

it seems we require it for two cases:
a/ It's used in the rsvg-loader test
b/ It's called during make install

b/ is handled by triggers in Debian and already conditionalized by DESTDIR

So maybe an alternative could be to simply skip building the rsvg-loader
test.

-- 
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#907316: tomboy: Is tomboy still being maintained?

[Tobias Frost]

Package: src:tomboy
Severity: serious

Dear maintaines for tomboy,

We've received concerns about tomboy being not properly maintained by a
user of this package. It seems to that the package is indeed not being
maintained properly, as of this writing is is RC buggy with 3 RC-bugs,
the repo has not been migrated to salsa and upstream has released
several (5+) new versions, the latest over an year ago.

It would be great if you could update the package and then close this
bug. Otherwise, I will re-evalute in 3 months and if there is no answer
to this bug, I will orphan this package on behalf of the MIA team.

Thanks for your contributions to Debian!

-- 
tobi (for the MIA team)

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

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

Processed: These two bugs are really the same

[Debian Bug Tracking System]

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

> retitle 830739 mpi-testsuite: FTBFS randomly because Makefile errors are not 
> trapped properly
Bug #830739 [src:mpi-testsuite] mpi-testsuite: FTBFS on non-Linux: 
'override_dh_auto_configure' failed
Changed Bug title to 'mpi-testsuite: FTBFS randomly because Makefile errors are 
not trapped properly' from 'mpi-testsuite: FTBFS on non-Linux: 
'override_dh_auto_configure' failed'.
> retitle 907158 mpi-testsuite: FTBFS randomly because Makefile errors are not 
> trapped properly
Bug #907158 [src:mpi-testsuite] mpi-testsuite: FTBFS in buster/sid (ln: failed 
to create symbolic link)
Changed Bug title to 'mpi-testsuite: FTBFS randomly because Makefile errors are 
not trapped properly' from 'mpi-testsuite: FTBFS in buster/sid (ln: failed to 
create symbolic link)'.
> forcemerge 830739 907158
Bug #830739 [src:mpi-testsuite] mpi-testsuite: FTBFS randomly because Makefile 
errors are not trapped properly
Bug #830739 [src:mpi-testsuite] mpi-testsuite: FTBFS randomly because Makefile 
errors are not trapped properly
Added tag(s) ftbfs.
Bug #907158 [src:mpi-testsuite] mpi-testsuite: FTBFS randomly because Makefile 
errors are not trapped properly
Merged 830739 907158
> severity 830739 serious
Bug #830739 [src:mpi-testsuite] mpi-testsuite: FTBFS randomly because Makefile 
errors are not trapped properly
Bug #907158 [src:mpi-testsuite] mpi-testsuite: FTBFS randomly because Makefile 
errors are not trapped properly
Severity set to 'serious' from 'important'
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: Re: cups-filters: filter failed on Ricoh MP 3554 SP after upgrading to 1.21.0-1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 +upstream fixed-upstream
Bug #907026 [cups-filters] cups-filters: filter failed on Ricoh MP 3554 SP 
after upgrading to 1.21.0-1
Added tag(s) fixed-upstream and upstream.

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

Bug#907026: cups-filters: filter failed on Ricoh MP 3554 SP after upgrading to 1.21.0-1

[Wenbin Lv]

Package: cups-filters
Version: 1.21.0-1
Followup-For: Bug #907026
Control: tags -1 +upstream fixed-upstream

You are welcome, and thank you Till Kamppeter for the fix.

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

Kernel: Linux 4.17.0-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=zh_CN.utf8, LC_CTYPE=zh_CN.utf8 (charmap=UTF-8), LANGUAGE=zh_CN:zh 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages cups-filters depends on:
ii  bc 1.07.1-2+b1
ii  cups-filters-core-drivers  1.21.0-1
ii  ghostscript9.22~dfsg-2.1
ii  libc6  2.27-5
ii  libcups2   2.2.8-5
ii  libcupsfilters11.21.0-1
ii  libcupsimage2  2.2.8-5
ii  libfontconfig1 2.13.0-5
ii  libfontembed1  1.21.0-1
ii  libgcc11:8.2.0-4
ii  libqpdf21  8.2.1-1
ii  libstdc++6 8.2.0-4
ii  poppler-utils  0.63.0-2

Versions of packages cups-filters recommends:
ii  colord   1.3.3-2
ii  imagemagick  8:6.9.10.8+dfsg-1
ii  imagemagick-6.q16 [imagemagick]  8:6.9.10.8+dfsg-1
ii  liblouisutdml-bin2.7.0-2+b3

Versions of packages cups-filters suggests:
pn  antiword   
pn  docx2txt   
ii  foomatic-db-compressed-ppds [foomatic-db]  20180604-1

-- no debconf information

Bug#904459: netdata: modifies conffiles (policy 10.7.3): /etc/netdata/health_alarm_notify.conf

[Daniel Baumann]

retitle 904459 modifies conffiles (health_alarm_notify.conf)
tag 904459 - moreinfo
tag 904459 + pending
thanks

Hi Andreas,

thanks you for your patience and sorry for the delay (there was
debconf+vacation). I've got it mostly sorted out, doing some more tests
and then uploading in the next couple of days.

Regards,
Daniel

Processed: Re: netdata: modifies conffiles (policy 10.7.3): /etc/netdata/health_alarm_notify.conf

[Debian Bug Tracking System]

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

> retitle 904459 modifies conffiles (health_alarm_notify.conf)
Bug #904459 [netdata] netdata: modifies conffiles (policy 10.7.3): 
/etc/netdata/health_alarm_notify.conf
Changed Bug title to 'modifies conffiles (health_alarm_notify.conf)' from 
'netdata: modifies conffiles (policy 10.7.3): 
/etc/netdata/health_alarm_notify.conf'.
> tag 904459 - moreinfo
Bug #904459 [netdata] modifies conffiles (health_alarm_notify.conf)
Removed tag(s) moreinfo.
> tag 904459 + pending
Bug #904459 [netdata] modifies conffiles (health_alarm_notify.conf)
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#905913: Don't install into testing

[Cody Brownstein]

Hello Jörg,

Niko Tyni wrote:
> On Sat, Aug 11, 2018 at 05:09:15PM +0200, Jörg Frings-Fürst wrote:
> > don't install 1.0.27-1~experimental6 into testing.
> 
> Hi, could you please elaborate a bit on the plan for this?  The current
> state in sid is going to clash with other transitions.
> 
> It looks like 1.0.27-1~experimental6 entered sid accidentally, do you
> intend to revert that or go ahead with the transition?

I also am curious to know what the plan for this is.

Currently, the `gnome` package cannot be installed. See below. I am sure
(many) other packages are affected as well.

$ apt-get -o Debug::pkgProblemResolver=yes --dry-run install gnome
NOTE: This is only a simulation!
  apt-get needs root privileges for real execution.
  Keep also in mind that locking is deactivated,
  so don't depend on the relevance to the real current situation!
Reading package lists...
Building dependency tree...
Reading state information...
Starting pkgProblemResolver with broken count: 2
Starting 2 pkgProblemResolver with broken count: 2
Investigating (0) colord:amd64 < none -> 1.3.3-2 @rc uN Ib >
Broken colord:amd64 Depends on libsane:amd64 < none | 1.0.25-4.1 @un uH > (>= 
1.0.24)
  Considering libsane:amd64 0 as a solution to colord:amd64 36
  Holding Back colord:amd64 rather than change libsane:amd64
Investigating (0) gnome-control-center:amd64 < none -> 1:3.28.2-1 @un uN Ib >
Broken gnome-control-center:amd64 Depends on colord:amd64 < none | 1.3.3-2 @rc 
uH > (>= 0.1.30)
  Considering colord:amd64 36 as a solution to gnome-control-center:amd64 12
  Holding Back gnome-control-center:amd64 rather than change colord:amd64
Investigating (0) gnome-core:amd64 < none -> 1:3.22+9 @un uN Ib >
Broken gnome-core:amd64 Depends on gnome-control-center:amd64 < none | 
1:3.28.2-1 @un uH > (>= 1:3.22)
  Considering gnome-control-center:amd64 12 as a solution to gnome-core:amd64 0
  Holding Back gnome-core:amd64 rather than change gnome-control-center:amd64
Investigating (0) gnome-color-manager:amd64 < none -> 3.28.0-1 @un uN Ib >
Broken gnome-color-manager:amd64 Depends on colord:amd64 < none | 1.3.3-2 @rc 
uH > (>= 1.3.1)
  Considering colord:amd64 36 as a solution to gnome-color-manager:amd64 0
  Holding Back gnome-color-manager:amd64 rather than change colord:amd64
Investigating (0) simple-scan:amd64 < none -> 3.28.1-1 @un uN Ib >
Broken simple-scan:amd64 Depends on libsane:amd64 < none | 1.0.25-4.1 @un uH > 
(>= 1.0.24)
  Considering libsane:amd64 0 as a solution to simple-scan:amd64 0
  Holding Back simple-scan:amd64 rather than change libsane:amd64
Investigating (1) gnome:amd64 < none -> 1:3.22+9 @un puN Ib >
Broken gnome:amd64 Depends on gnome-core:amd64 < none | 1:3.22+9 @un uH > (= 
1:3.22+9)
  Considering gnome-core:amd64 0 as a solution to gnome:amd64 
Reinst Failed early because of libsane-common:amd64
Reinst Failed because of libsane:amd64
Reinst Failed because of colord:amd64
Reinst Failed because of gnome-control-center:amd64
Broken gnome:amd64 Depends on gnome-color-manager:amd64 < none | 3.28.0-1 @un 
uH > (>= 3.22)
  Considering gnome-color-manager:amd64 0 as a solution to gnome:amd64 
Reinst Failed because of colord:amd64
Broken gnome:amd64 Depends on simple-scan:amd64 < none | 3.28.1-1 @un uH >
  Considering simple-scan:amd64 0 as a solution to gnome:amd64 
Reinst Failed because of libsane:amd64
Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 gnome : Depends: gnome-core (= 1:3.22+9) but it is not going to be installed
 Depends: gnome-color-manager (>= 3.22) but it is not going to be 
installed
 Depends: simple-scan but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

Processed: Re: Bug#907306: configure: error: gdk-pixbuf-query-loaders not found in path

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 configure: error: gdk-pixbuf-query-loaders not found in path
Bug #907306 [src:librsvg] librsvg: FTBFS in buster/sid (configure fails)
Changed Bug title to 'configure: error: gdk-pixbuf-query-loaders not found in 
path' from 'librsvg: FTBFS in buster/sid (configure fails)'.

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

Bug#907306: configure: error: gdk-pixbuf-query-loaders not found in path

[Simon McVittie]

Control: retitle -1 configure: error: gdk-pixbuf-query-loaders not found in path

On Sun, 26 Aug 2018 at 09:07:44 +, Santiago Vila wrote:
> [...]
>  debian/rules build-indep
> dh build-indep --with gnome,gir
>dh_update_autotools_config -i
>debian/rules override_dh_autoreconf
> make[1]: Entering directory '/<>'
> dh_autoreconf --as-needed
> libtoolize: putting auxiliary files in '.'.
> libtoolize: copying file './ltmain.sh'
> libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
> libtoolize: copying file 'm4/libtool.m4'
> libtoolize: copying file 'm4/ltoptions.m4'
> libtoolize: copying file 'm4/ltsugar.m4'
> libtoolize: copying file 'm4/ltversion.m4'
> libtoolize: copying file 'm4/lt~obsolete.m4'
> 
> [... snipped ...]
> 
> mkdir_p='$(MKDIR_P)'
> oldincludedir='/usr/include'
> pdfdir='${docdir}'
> prefix='/usr'
> program_transform_name='s,x,x,'
> psdir='${docdir}'
> runstatedir='/run'
[...]
> configure: exit 1
> dh_auto_configure: ./configure --build=x86_64-linux-gnu --prefix=/usr 
> --includedir=\${prefix}/include --mandir=\${prefix}/share/man 
> --infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
> --disable-silent-rules --libdir=\${prefix}/lib/x86_64-linux-gnu 
> --libexecdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run 
> --disable-maintainer-mode --disable-dependency-tracking 
> --enable-pixbuf-loader --enable-introspection --enable-vala --enable-gtk-doc 
> returned exit code 1
> make[1]: *** [debian/rules:14: override_dh_auto_configure] Error 2
> make[1]: Leaving directory '/<>'
> make: *** [debian/rules:8: build-indep] Error 2
> dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
> status 2

Unfortunately you removed the interesting part of this log. If you
are routinely reporting FTBFS in Autotools packages, please attach the
whole log, or quote the part of configure's output just before it starts
dumping config.log and the part of config.log just before it starts
dumping cache variables. Those are the actual failure.

Luckily, this package also FTBFS on reproducible-builds, so I was able
to find the interesting parts of the log:

8<
...
checking for gio-2.0 gio-unix-2.0 gdk-pixbuf-2.0 cairo pangocairo... yes
checking for strtok_r... yes
checking for gtk+-3.0 >= 3.10.0... yes
checking whether to build the GDK-Pixbuf SVG loader... yes
checking for gdk-pixbuf-2.0 >= 2.20... yes
checking for gdk-pixbuf-query-loaders... no
checking for gdk-pixbuf-query-loaders-64... no
checking for gdk-pixbuf-query-loaders-32... no
configure: error: gdk-pixbuf-query-loaders not found in path   <--HERE
tail -v -n \+0 config.log
==> config.log <==
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
...
8<

and

8<
...
configure:14630: checking for gdk-pixbuf-2.0 >= 2.20
configure:14637: $PKG_CONFIG --exists --print-errors "gdk-pixbuf-2.0 >= 
$GDK_PIXBUF_REQUIRED"
configure:14640: $? = 0
configure:14654: $PKG_CONFIG --exists --print-errors "gdk-pixbuf-2.0 >= 
$GDK_PIXBUF_REQUIRED"
configure:14657: $? = 0
configure:14715: result: yes
configure:14724: checking for gdk-pixbuf-query-loaders   }
configure:14757: result: no  }
configure:14724: checking for gdk-pixbuf-query-loaders-64}
configure:14757: result: no  } <--HERE
configure:14724: checking for gdk-pixbuf-query-loaders-32}
configure:14757: result: no  }
configure:14768: error: gdk-pixbuf-query-loaders not found in path   }

##  ##
## Cache variables. ##
##  ##

ac_cv_build=x86_64-pc-linux-gnu
ac_cv_c_bigendian=no
ac_cv_c_compiler_gnu=yes
ac_cv_env_CC_set=
...
8<

This looks like fallout from gdk-pixbuf (2.36.12-2) which removed
gdk-pixbuf-query-loaders in order to make libgdk-pixbuf2.0-dev Multi-Arch:
same. I used codesearch.debian.net to try to find packages that depended
on gdk-pixbuf-query-loaders and did not find any, but I must have missed
this one.

I don't see a way for gdk-pixbuf-query-loaders to be in PATH
while allowing cross-compilation to use libgdk-pixbuf2.0-dev:
gdk-pixbuf-query-loaders queries the available loaders for its own
architecture, but when cross-compiling on a build architecture for a
host architecture, the build machine can't necessarily run the host
architecture's gdk-pixbuf-query-loaders. It also can't be in a
Multi-Arch: foreign package because its output is architecture-specific.

Looking at librsvg, it seems we might be able to reinstate
gdk-pixbuf-query-loaders in libgdk-pixbuf2.0-dev but rename it to
$(DEB_HOST_ARCH)-gdk-pixbuf-query-loaders, and then change librsvg to
use AC_CHECK_TOOL instead of AC_PATH_PROGS; or install
gdk-pixbuf-query-loaders in /usr/lib/$(DEB_HOST_MULTIARCH) instead of
/usr/bin, then add that to PATH when building librsvg. That would mean
we 

Processed: Re: Processed (with 1 error): your mail

[Debian Bug Tracking System]

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

> block 906385 by 907250
Bug #906385 [src:ms-gsl] ms-gsl: FTBFS in buster/sid (error: catching 
polymorphic type 'struct gsl::fail_fast' by value)
906385 was not blocked by any bugs.
906385 was not blocking any bugs.
Added blocking bug(s) of 906385: 907250
>
End of message, stopping processing here.

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

Bug#906959: sketch FTBFS arch-only: dh_installman: Cannot find (any matches for) "sketch.1" (tried in .)

[David Bremner]

Helmut Grohne  writes:

> Source: sketch
> Version: 1:0.3.7-6
> Severity: serious
> Tags: ftbfs
> User: helm...@debian.org
> Usertags: rebootstrap
>
> sketch fails to build from source in unstable on amd64 when performing
> an arch-only build. A log ends with:
>
> | dh_installman: Cannot find (any matches for) "sketch.1" (tried in .)
>
> It didn't fail there. Sounds plausible, no?
>

Hi Helmut;

The underlying cause is fix for #871322. It's easy enough to change to
something like

ifneq ($(filter sketch-doc,$(shell dh_listpackages)),)
cd Doc && perl make.pl linux examples
endif
ifneq ($(filter sketch,$(shell dh_listpackages)),)
$(XP) -o sketch.1 $(DB2MAN)  debian/sketch-man.xml
endif

The trickier issue is "sketch.info". It is build by the above "perl
make.pl" call, but currrently is in the sketch binary packgage. I'm not
sure if it's better to move to the -doc package, or add a redundant call
to makeinfo.

d

Bug#906505: qlandkartegt: FTBFS in buster/sid (unable to find string literal operator)

[Sebastiaan Couwenberg]

On 8/26/18 11:02 AM, Stuart Prescott wrote:
> On Sunday, 26 August 2018 10:29:43 AEST Sebastiaan Couwenberg wrote:
>> On 8/26/18 10:17 AM, Stuart Prescott wrote:
>> No one in the Debian GIS team is willing to maintain this EOL package
>> any longer, qmapshack is were we invest our effort.
>
> Please file a WNPP bug that orphans qlandkarte. That signals to others
> that
> they can (and should) take over maintenance of the package.
>
> §5.9.4 of the Developers Reference covers the case where the existing
> maintainers are unwilling to maintain a package any longer:
>
> https://www.debian.org/doc/manuals/developers-reference/ch05.en.html#orp
> ha
> ning

 No, EOL software should be removed. The QA team is not the place for EOL
 and broken packages.

 The removal of qlandkartegt was a long time coming, since it's been
 superseded by qmapshack in Debian and upstream, this issue was just the
 trigger.
>>>
>>> If you really believe that, the correct course of action is an RM bug.
>>> wontfix on an RC bug still isn't right.
>>
>> If you really cared, you would have checked and seen that one already
>> exists.
> 
> My apologies, I had actually checked, but missed it.
> 
>>> More generally, though, there is plenty of software that is Debian without
>>> an active upstream but with active maintainers keeping it alive. Dead
>>> upstream's aren't a problem for Debian; it's dead upstreams coupled with
>>> inactive maintainers. It's fine for you to decide that you don't want to
>>> be that maintainer, but it's not your call to stand in the way of others
>>> who do want to do this work.
>>
>> I am the only active maintainer of this package, it *is* my call to tell
>> others that I will not fix this issue because the software is EOL.
> 
> Except that is absolutely not what I said.
> 
> You get to make calls about your time, that's fine. You don't get to say that 
> other maintainers aren't allowed to maintain this package but that is what 
> you're doing.

Sigh. You're quite hopeless. I never said that other maintainers aren't
allowed to maintain this package.

Your hypothetical maintainers willing to maintain this package haven't
joined the GIS team or offered to take over the package.

Still lots of talk and no action.

>> People that want to fix this package know what to do, get involved in
>> upstream development and take over maintenance of the package.
>>
>> I care more about the quality of Debian than to keep broken packages
>> that have no future in Debian.
>>
>> So far no one has stepped up to revive QLandkarteGT upstream
>> development, it just a lot of empty talk and no action.
> 
> My point is that no-one knows that it needs action because there is no RFH, 
> RFA or O bug.

There is no need to help, nor adoption, the package will be removed
because upstream development stopped in favour of qmapshack. Hence the
RM bug to remove the package. We kept it in Debian as long as it was
still somewhat functioning, but the it was never fully functional since
the switch to Qt5.

The only action required is for FTP masters to remove this package, that
will resolve this bugreport. In the mean time the wontfix tag indicates
that this bug will not be fixed by the maintainer.

>> Stop talking out of your ass, and get off it to revive upstream
>> development if you really care about the future of this package.
> 
> *sigh* That's completely out of line. 
> 
> You can't complain that others aren't doing work when they don't know that 
> the 
> work is required and where you are actively blocking that work.
> 
> * Today was the first I knew that you weren't planning to continue to 
> maintain 
> it. I follow O/RFA/RFH bugs in packages I use for *precisely* this sort of 
> situation where help is needed. There is no bug filed and my mind-reading kit 
> was yet to pick up your request for assistance.

Again, there is no need to assistance, there is need for upstream
development.

You should add RM bugs to your list of things to follow.

> * The lack of O/RFA bug means that to do anything here, I must first hijack 
> the package. That's not how we normally do things. Your course of action 
> means 
> that even though I *am* considering taking this package on, I am required to 
> act in a way that is not normally acceptable in Debian.

Sigh, again. There is no need to hijack, the package is team maintained,
joining the team is also an option. But the package doesn't lack
maintainers, it lacks upstream development.

> You're also asking me to suddenly take on this code base with a whole 2 hours 
> notice. Please don't be surprised that I've not yet agreed to do so or that 
> generating so much stop energy discourages people from doing so.

Your energy is better spend elsewhere, like getting familiar with
qmapshack so you can let go of your emotional attachment to qlandkartegt.

Kind Regards,

Bas

Bug#907308: latrace: every program "killed by signal 11"

[Jakub Wilk]

Package: latrace
Version: 0.5.11-1+b2
Severity: grave

latrace seems to be completely broken:

  $ latrace true
  
  true finished - killed by signal 11



-- System Information:
Architecture: i386

Versions of packages latrace depends on:
ii  libc6  2.27-5

--
Jakub Wilk

Bug#907306: librsvg: FTBFS in buster/sid (configure fails)

[Sven Joachim]

On 2018-08-26 09:07 +, Santiago Vila wrote:

> Package: src:librsvg
> Version: 2.40.20-2
> Severity: serious
> Tags: ftbfs
>
> Dear maintainer:
>
> I tried to build this package in buster but it failed:
> [...]
> Most probably, it also fails here in reproducible builds:
>
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/librsvg.html
>
> where you can get a full build log if you need it.

The relevant lines from that build log are these:

,
| checking for gdk-pixbuf-query-loaders... no
| checking for gdk-pixbuf-query-loaders-64... no
| checking for gdk-pixbuf-query-loaders-32... no
| configure: error: gdk-pixbuf-query-loaders not found in path
`

This is due to the following change in gdk-pixbuf:

,
| gdk-pixbuf (2.36.12-2) unstable; urgency=medium
| 
|   [ Simon McVittie ]
|   * Update versioned Breaks/Replaces
|   * Remove /usr/bin/gdk-pixbuf-query-loaders symlink from -dev package.
| It has architecture-dependent output and breaks Multi-Arch: same
| co-installability. Debian packages do not seem to rely on this tool
| being in PATH.
| 
|  -- Simon McVittie   Tue, 21 Aug 2018 15:15:42 +0100
`

Apparently the statement "Debian packages do not seem to rely on this tool
being in PATH" was a bit too optimistic.

Cheers,
   Sven

Bug#907026: cups-filters: filter failed on Ricoh MP 3554 SP after upgrading to 1.21.0-1

[Till Kamppeter]

Wenbin Lv, thank you very much for testing.

I have released version 1.21.1 with the fix. It will soon appear in Debian.

   Till

Bug#906595: marked as done (clevis: FTBFS when built with dpkg-buildpackage -A)

[Debian Bug Tracking System]

Your message dated Sun, 26 Aug 2018 09:18:50 +
with message-id 
and subject line Bug#906595: fixed in clevis 10-2
has caused the Debian Bug report #906595,
regarding clevis: FTBFS when built with dpkg-buildpackage -A
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.)


-- 
906595: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906595
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:clevis
Version: 10-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A" but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_update_autotools_config -i
   dh_autoreconf -i
   dh_auto_configure -i
./configure --build=x86_64-linux-gnu --prefix=/usr 
--includedir=\${prefix}/include --mandir=\${prefix}/share/man 
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-silent-rules --libdir=\${prefix}/lib/x86_64-linux-gnu 
--libexecdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run 
--disable-maintainer-mode --disable-dependency-tracking
configure: WARNING: unrecognized options: --disable-maintainer-mode
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking target system type... x86_64-pc-linux-gnu
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 

[... snipped ...]

make[3]: Leaving directory '/<>/src/systemd'
Making install in udisks2
make[3]: Entering directory '/<>/src/udisks2'
make[4]: Entering directory '/<>/src/udisks2'
 /bin/mkdir -p '/<>/debian/tmp/usr/lib/x86_64-linux-gnu'
  /usr/bin/install -c clevis-luks-udisks2 
'/<>/debian/tmp/usr/lib/x86_64-linux-gnu'
 /bin/mkdir -p '/<>/debian/tmp/etc/xdg/autostart'
 /usr/bin/install -c -m 644 clevis-luks-udisks2.desktop 
'/<>/debian/tmp/etc/xdg/autostart'
make[4]: Leaving directory '/<>/src/udisks2'
make[3]: Leaving directory '/<>/src/udisks2'
Making install in .
make[3]: Entering directory '/<>/src'
make[4]: Entering directory '/<>/src'
 /bin/mkdir -p '/<>/debian/tmp/usr/bin'
  /usr/bin/install -c clevis-encrypt-sss clevis-decrypt-sss 
'/<>/debian/tmp/usr/bin'
 /bin/mkdir -p '/<>/debian/tmp/usr/bin'
 /usr/bin/install -c clevis-encrypt-http clevis-encrypt-tang 
clevis-decrypt-http clevis-decrypt-tang clevis-bind-luks clevis-luks-unlock 
clevis-luks-bind clevis-luks-unbind clevis-decrypt clevis 
'/<>/debian/tmp/usr/bin'
make[4]: Nothing to be done for 'install-data-am'.
make[4]: Leaving directory '/<>/src'
make[3]: Leaving directory '/<>/src'
make[2]: Leaving directory '/<>/src'
Making install in tests
make[2]: Entering directory '/<>/tests'
make[3]: Entering directory '/<>/tests'
make[3]: Nothing to be done for 'install-exec-am'.
make[3]: Nothing to be done for 'install-data-am'.
make[3]: Leaving directory '/<>/tests'
make[2]: Leaving directory '/<>/tests'
make[1]: Leaving directory '/<>'
   dh_install -i
   dh_installdocs -i
   dh_installchangelogs -i
   dh_installman -i
   dh_perl -i
   dh_link -i
   dh_strip_nondeterminism -i
   dh_compress -i
   debian/rules override_dh_fixperms
make[1]: Entering directory '/<>'
dh_fixperms
chmod u+s \
debian/clevis-udisks2/usr/lib/*/clevis-luks-udisks2
chmod: cannot access 'debian/clevis-udisks2/usr/lib/*/clevis-luks-udisks2': No 
such file or directory
make[1]: *** [debian/rules:15: override_dh_fixperms] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:8: binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


Hint: Try splitting override_dh_fixperms into override_dh_fixperms-arch
and override_dh_fixperms-indep.

Note: If possible, consider uploading in source-only form (dpkg-buildpackage 
-S).
That way this kind of bugs would never propagate to testing and also we would 
get
official build logs for the arch:all autobuilder here:

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

Thanks.
--- End Message ---
--- Begin Message ---
Source: clevis
Source-Version: 10-2

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

Bug#907306: librsvg: FTBFS in buster/sid (configure fails)

[Santiago Vila]

Package: src:librsvg
Version: 2.40.20-2
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep --with gnome,gir
   dh_update_autotools_config -i
   debian/rules override_dh_autoreconf
make[1]: Entering directory '/<>'
dh_autoreconf --as-needed
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'

[... snipped ...]

mkdir_p='$(MKDIR_P)'
oldincludedir='/usr/include'
pdfdir='${docdir}'
prefix='/usr'
program_transform_name='s,x,x,'
psdir='${docdir}'
runstatedir='/run'
sbindir='${exec_prefix}/sbin'
sharedstatedir='${prefix}/com'
sysconfdir='/etc'
target_alias=''

## --- ##
## confdefs.h. ##
## --- ##

/* confdefs.h */
#define PACKAGE_NAME "RSVG"
#define PACKAGE_TARNAME "librsvg"
#define PACKAGE_VERSION "2.40.20"
#define PACKAGE_STRING "RSVG 2.40.20"
#define PACKAGE_BUGREPORT 
"https://bugzilla.gnome.org/enter_bug.cgi?product=librsvg;
#define PACKAGE_URL ""
#define PACKAGE "librsvg"
#define VERSION "2.40.20"
#define STDC_HEADERS 1
#define HAVE_SYS_TYPES_H 1
#define HAVE_SYS_STAT_H 1
#define HAVE_STDLIB_H 1
#define HAVE_STRING_H 1
#define HAVE_MEMORY_H 1
#define HAVE_STRINGS_H 1
#define HAVE_INTTYPES_H 1
#define HAVE_STDINT_H 1
#define HAVE_UNISTD_H 1
#define HAVE_DLFCN_H 1
#define LT_OBJDIR ".libs/"
#define HAVE_STRTOK_R 1

configure: exit 1
dh_auto_configure: ./configure --build=x86_64-linux-gnu --prefix=/usr 
--includedir=\${prefix}/include --mandir=\${prefix}/share/man 
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-silent-rules --libdir=\${prefix}/lib/x86_64-linux-gnu 
--libexecdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run 
--disable-maintainer-mode --disable-dependency-tracking --enable-pixbuf-loader 
--enable-introspection --enable-vala --enable-gtk-doc returned exit code 1
make[1]: *** [debian/rules:14: override_dh_auto_configure] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:8: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


The build was made in my autobuilder with either "dpkg-buildpackage -A"
(if the package allows it) or "dpkg-buildpackage -B" (if it does not).

Most probably, it also fails here in reproducible builds:

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

where you can get a full build log if you need it.

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

Thanks.

Bug#907305: hhvm: FTBFS in buster/sid (failing tests)

[Santiago Vila]

Package: src:hhvm
Version: 3.24.7+dfsg-2
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
/test/run -m jit quick
Running 1167 tests in 1 threads (0 in serial)
.
FAILED: /<>/hhvm-3.24.7+dfsg/hphp/test/quick/FPassC-2.php
011+ Core dumped: Segmentation fault

012+ Stack trace in /tmp/stacktrace.25634.log

013+ Segmentation fault


That's from my autobuilder, but a similar error happens here:

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

where you can get a full build log if you need it.

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

Thanks.

Bug#906505: qlandkartegt: FTBFS in buster/sid (unable to find string literal operator)

[Stuart Prescott]

Hi Sebastiaan,

On Sunday, 26 August 2018 10:29:43 AEST Sebastiaan Couwenberg wrote:
> On 8/26/18 10:17 AM, Stuart Prescott wrote:
>  No one in the Debian GIS team is willing to maintain this EOL package
>  any longer, qmapshack is were we invest our effort.
> >>> 
> >>> Please file a WNPP bug that orphans qlandkarte. That signals to others
> >>> that
> >>> they can (and should) take over maintenance of the package.
> >>> 
> >>> §5.9.4 of the Developers Reference covers the case where the existing
> >>> maintainers are unwilling to maintain a package any longer:
> >>> 
> >>> https://www.debian.org/doc/manuals/developers-reference/ch05.en.html#orp
> >>> ha
> >>> ning
> >> 
> >> No, EOL software should be removed. The QA team is not the place for EOL
> >> and broken packages.
> >> 
> >> The removal of qlandkartegt was a long time coming, since it's been
> >> superseded by qmapshack in Debian and upstream, this issue was just the
> >> trigger.
> > 
> > If you really believe that, the correct course of action is an RM bug.
> > wontfix on an RC bug still isn't right.
> 
> If you really cared, you would have checked and seen that one already
> exists.

My apologies, I had actually checked, but missed it.

> > More generally, though, there is plenty of software that is Debian without
> > an active upstream but with active maintainers keeping it alive. Dead
> > upstream's aren't a problem for Debian; it's dead upstreams coupled with
> > inactive maintainers. It's fine for you to decide that you don't want to
> > be that maintainer, but it's not your call to stand in the way of others
> > who do want to do this work.
> 
> I am the only active maintainer of this package, it *is* my call to tell
> others that I will not fix this issue because the software is EOL.

Except that is absolutely not what I said.

You get to make calls about your time, that's fine. You don't get to say that 
other maintainers aren't allowed to maintain this package but that is what 
you're doing.

> People that want to fix this package know what to do, get involved in
> upstream development and take over maintenance of the package.
> 
> I care more about the quality of Debian than to keep broken packages
> that have no future in Debian.
> 
> So far no one has stepped up to revive QLandkarteGT upstream
> development, it just a lot of empty talk and no action.

My point is that no-one knows that it needs action because there is no RFH, 
RFA or O bug.

> Stop talking out of your ass, and get off it to revive upstream
> development if you really care about the future of this package.

*sigh* That's completely out of line. 

You can't complain that others aren't doing work when they don't know that the 
work is required and where you are actively blocking that work.

* Today was the first I knew that you weren't planning to continue to maintain 
it. I follow O/RFA/RFH bugs in packages I use for *precisely* this sort of 
situation where help is needed. There is no bug filed and my mind-reading kit 
was yet to pick up your request for assistance.

* The lack of O/RFA bug means that to do anything here, I must first hijack 
the package. That's not how we normally do things. Your course of action means 
that even though I *am* considering taking this package on, I am required to 
act in a way that is not normally acceptable in Debian.

You're also asking me to suddenly take on this code base with a whole 2 hours 
notice. Please don't be surprised that I've not yet agreed to do so or that 
generating so much stop energy discourages people from doing so.

Stuart


-- 
Stuart Prescotthttp://www.nanonanonano.net/   stu...@nanonanonano.net
Debian Developer   http://www.debian.org/ stu...@debian.org
GPG fingerprint90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7

Bug#906505: qlandkartegt: FTBFS in buster/sid (unable to find string literal operator)

[Sebastiaan Couwenberg]

On 8/26/18 10:17 AM, Stuart Prescott wrote:
 No one in the Debian GIS team is willing to maintain this EOL package
 any longer, qmapshack is were we invest our effort.
>>>
>>> Please file a WNPP bug that orphans qlandkarte. That signals to others
>>> that
>>> they can (and should) take over maintenance of the package.
>>>
>>> §5.9.4 of the Developers Reference covers the case where the existing
>>> maintainers are unwilling to maintain a package any longer:
>>>
>>> https://www.debian.org/doc/manuals/developers-reference/ch05.en.html#orpha
>>> ning
>> No, EOL software should be removed. The QA team is not the place for EOL
>> and broken packages.
>>
>> The removal of qlandkartegt was a long time coming, since it's been
>> superseded by qmapshack in Debian and upstream, this issue was just the
>> trigger.
> 
> If you really believe that, the correct course of action is an RM bug. 
> wontfix 
> on an RC bug still isn't right.

If you really cared, you would have checked and seen that one already
exists.

> More generally, though, there is plenty of software that is Debian without an 
> active upstream but with active maintainers keeping it alive. Dead upstream's 
> aren't a problem for Debian; it's dead upstreams coupled with inactive 
> maintainers. It's fine for you to decide that you don't want to be that 
> maintainer, but it's not your call to stand in the way of others who do want 
> to do this work.

I am the only active maintainer of this package, it *is* my call to tell
others that I will not fix this issue because the software is EOL.

People that want to fix this package know what to do, get involved in
upstream development and take over maintenance of the package.

I care more about the quality of Debian than to keep broken packages
that have no future in Debian.

So far no one has stepped up to revive QLandkarteGT upstream
development, it just a lot of empty talk and no action.

Stop talking out of your ass, and get off it to revive upstream
development if you really care about the future of this package.

Kind Regards,

Bas

Bug#905913: libsane1: My apt program shows broke packages

[Vinicius Couto]

Package: libsane1
Version: 1.0.27-1~experimental6
Followup-For: Bug #905913

Dear Maintainer,

For 2 weeks, apt program shows broke compatibility with libsane:

Os pacotes a seguir possuem dependências não satisfeitas:
 libsane1 : Quebra: libsane (< 1.0.27-1) but 1.0.25-4.1 is installed
 libsane : Depende: libsane-common (= 1.0.25-4.1) but 1.0.27-1~experimental6 is 
to be installed
As seguintes ações resolverão estas dependências:

 Manter os pacotes a seguir em suas versões atuais:
1) libsane-common [1.0.25-4.1 (now, unstable)] 
2) libsane1 [Não Instalado]
3) sane-utils [1.0.25-4.1 (now)]

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

Kernel: Linux 4.17.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), 
LANGUAGE=pt_BR:pt:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libsane1 depends on:
ii  acl2.2.52-3+b1
ii  adduser3.117
ii  libavahi-client3   0.7-4
ii  libavahi-common3   0.7-4
ii  libc6  2.27-5
ii  libgphoto2-6   2.5.19-1
ii  libgphoto2-port12  2.5.19-1
ii  libieee1284-3  0.2.11-13
ii  libjpeg62-turbo1:1.5.2-2+b1
ii  libsane-common 1.0.25-4.1
ii  libsnmp30  5.7.3+dfsg-3
ii  libssl1.1  1.1.1~~pre9-1
ii  libtiff5   4.0.9-6
ii  libusb-1.0-0   2:1.0.22-2
ii  udev   239-7

Versions of packages libsane1 recommends:
ii  sane-utils  1.0.25-4.1

Versions of packages libsane1 suggests:
ii  avahi-daemon  0.7-4
ii  hplip 3.17.10+repack0-5

Bug#906505: qlandkartegt: FTBFS in buster/sid (unable to find string literal operator)

[Stuart Prescott]

> >> No one in the Debian GIS team is willing to maintain this EOL package
> >> any longer, qmapshack is were we invest our effort.
> > 
> > Please file a WNPP bug that orphans qlandkarte. That signals to others
> > that
> > they can (and should) take over maintenance of the package.
> > 
> > §5.9.4 of the Developers Reference covers the case where the existing
> > maintainers are unwilling to maintain a package any longer:
> > 
> > https://www.debian.org/doc/manuals/developers-reference/ch05.en.html#orpha
> > ning
> No, EOL software should be removed. The QA team is not the place for EOL
> and broken packages.
>
> The removal of qlandkartegt was a long time coming, since it's been
> superseded by qmapshack in Debian and upstream, this issue was just the
> trigger.

If you really believe that, the correct course of action is an RM bug. wontfix 
on an RC bug still isn't right.

More generally, though, there is plenty of software that is Debian without an 
active upstream but with active maintainers keeping it alive. Dead upstream's 
aren't a problem for Debian; it's dead upstreams coupled with inactive 
maintainers. It's fine for you to decide that you don't want to be that 
maintainer, but it's not your call to stand in the way of others who do want 
to do this work.

Cheers
Stuart

-- 
Stuart Prescotthttp://www.nanonanonano.net/   stu...@nanonanonano.net
Debian Developer   http://www.debian.org/ stu...@debian.org
GPG fingerprint90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7

Bug#906505: qlandkartegt: FTBFS in buster/sid (unable to find string literal operator)

[Sebastiaan Couwenberg]

On 8/26/18 8:50 AM, Stuart Prescott wrote:
> On Saturday, 25 August 2018 23:05:51 AEST Sebastiaan Couwenberg wrote:
>> On 8/25/18 7:45 PM, Christoph Biedl wrote:
>>> Christoph, who'd like to have a usable qlandkartegt in Debian - how is
>>> QMapShack supposed to be a replacement?
>> Upstream stopped developing QLGT and switches his attention to QMS.
>>
>> You will have to take over maintenance of qlandkartegt if you want to
>> keep it in Debian, but the package and upstream development. As long as
>> there is no one actively working on QLGT upstream the fate of the
>> package is sealed.
>>
>> No one in the Debian GIS team is willing to maintain this EOL package
>> any longer, qmapshack is were we invest our effort.
> 
> Please file a WNPP bug that orphans qlandkarte. That signals to others that 
> they can (and should) take over maintenance of the package. 
> 
> §5.9.4 of the Developers Reference covers the case where the existing 
> maintainers are unwilling to maintain a package any longer:
> 
> https://www.debian.org/doc/manuals/developers-reference/ch05.en.html#orphaning

No, EOL software should be removed. The QA team is not the place for EOL
and broken packages.

The removal of qlandkartegt was a long time coming, since it's been
superseded by qmapshack in Debian and upstream, this issue was just the
trigger.

If you want a usable qlandkartegt in Debian, you first need to revive
upstream development, after which the package can be revived.

Kind Regards,

Bas

Bug#906505: qlandkartegt: FTBFS in buster/sid (unable to find string literal operator)

[Stuart Prescott]

On Saturday, 25 August 2018 23:05:51 AEST Sebastiaan Couwenberg wrote:
> Control: tags -1 wontfix
> 
> On 8/25/18 7:45 PM, Christoph Biedl wrote:
> > Christoph, who'd like to have a usable qlandkartegt in Debian - how is
> > QMapShack supposed to be a replacement?
> Upstream stopped developing QLGT and switches his attention to QMS.
> 
> You will have to take over maintenance of qlandkartegt if you want to
> keep it in Debian, but the package and upstream development. As long as
> there is no one actively working on QLGT upstream the fate of the
> package is sealed.
> 
> No one in the Debian GIS team is willing to maintain this EOL package
> any longer, qmapshack is were we invest our effort.

Please file a WNPP bug that orphans qlandkarte. That signals to others that 
they can (and should) take over maintenance of the package. 

§5.9.4 of the Developers Reference covers the case where the existing 
maintainers are unwilling to maintain a package any longer:

https://www.debian.org/doc/manuals/developers-reference/ch05.en.html#orphaning

Thanks
Stuart

-- 
Stuart Prescotthttp://www.nanonanonano.net/   stu...@nanonanonano.net
Debian Developer   http://www.debian.org/ stu...@debian.org
GPG fingerprint90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7

Bug#907298: CVE-2018-15869

[Moritz Muehlenhoff]

Package: awscli
Severity: grave
Tags: security

Please see http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-15869

Cheers,
Moritz