Bug#895381: Severity
* micah anderson [2019-01-20 21:03:53 +0100]: > I'm not disputing this bug exists, I'm just trying to determine why it > is you set the severity to "Serious". As you are probably aware, this > severity indicates that this is a sever violation of Debian policy > (violates a "must" or "required" directive), or in the package > maintainer's opinion, makes the package unsuitable for release. Oh. In the package maintainer's opinion. I had missed that part; my apologies. No, I don't claim a policy violation on this one and of course I'll defer to the package maintainer's assessment. I do find the bug scary, though, due to the possibility of silent corruption, and have been running a privately patched version of the package for that reason.
Processed: yapf: Python 2 removal breaks build dependencies of other packages
Processing control commands: > affects -1 src:forensic-artifacts src:backblaze-b2 Bug #919974 [src:yapf] yapf: Python 2 removal breaks build dependencies of other packages Added indication that 919974 affects src:forensic-artifacts and src:backblaze-b2 -- 919974: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919974 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#919974: yapf: Python 2 removal breaks build dependencies of other packages
Source: yapf Version: 0.25.0-1 Severity: serious Control: affects -1 src:forensic-artifacts src:backblaze-b2 yapf (0.25.0-1) unstable; urgency=medium ... [ Ana C. Custura ] * debian/control: - updates standards version to 4.3.0 - bumps debhelper version to 12 - removes support for end-of-life Python 2 * debian/compat: - bumps debhelper vesion to 12 * debian/rules: - removes support for end-of-life Python 2 -- Ana Custura Sun, 06 Jan 2019 22:15:35 + Python 2 might become end-of-life next year, but Debian buster does fully (security) support Python 2 in buster until the EOL of buster mid-2022. Note that most of the software in a stable Debian release is no longer upstream supported during the lifetime of a Debian release. Does yapf upstream support 0.25 until mid-2022? Chances are yapf 0.25 might be as unsupported as Python 2.7 in 2022. This is only a problem when not-backportable security fixes are expected. The unnecessary removal of Python 2 support in yapf did break the build dependencies of other packages in buster.
Bug#905415: marked as done (libnode-dev: broken symlinks: /usr/include/nodejs/deps/uv/include/{uv,uv.h} -> ../../../../{uv,uv.h})
Your message dated Mon, 21 Jan 2019 07:51:39 +
with message-id
and subject line Bug#905415: fixed in nodejs 10.15.0~dfsg-9
has caused the Debian Bug report #905415,
regarding libnode-dev: broken symlinks:
/usr/include/nodejs/deps/uv/include/{uv,uv.h} -> ../../../../{uv,uv.h}
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.)
--
905415: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905415
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libnode64-dev
Version: 10.4.0~dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package ships (or creates)
a broken symlink.
>From the attached log (scroll to the bottom...):
0m32.4s ERROR: FAIL: Broken symlinks:
/usr/include/nodejs/deps/uv/include/uv.h -> ../../../../uv.h
/usr/include/nodejs/deps/uv/include/uv-version.h -> ../../../../uv-version.h
/usr/include/nodejs/deps/uv/include/uv-unix.h -> ../../../../uv-unix.h
/usr/include/nodejs/deps/uv/include/uv-threadpool.h ->
../../../../uv-threadpool.h
/usr/include/nodejs/deps/uv/include/uv-linux.h -> ../../../../uv-linux.h
/usr/include/nodejs/deps/uv/include/uv-errno.h -> ../../../../uv-errno.h
Is libnode64-dev missing a Depends: libuv1-dev ?
cheers,
Andreas
libnode64-dev_10.4.0~dfsg-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: nodejs
Source-Version: 10.15.0~dfsg-9
We believe that the bug you reported is fixed in the latest version of
nodejs, 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 905...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Jérémy Lal (supplier of updated nodejs package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 21 Jan 2019 08:33:36 +0100
Source: nodejs
Binary: nodejs-dev libnode-dev nodejs libnode64 nodejs-doc
Architecture: source
Version: 10.15.0~dfsg-9
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers
Changed-By: Jérémy Lal
Description:
libnode-dev - evented I/O for V8 javascript (development files)
libnode64 - evented I/O for V8 javascript - runtime library
nodejs - evented I/O for V8 javascript - runtime executable
nodejs-dev - evented I/O for V8 javascript (debhelper files)
nodejs-doc - API documentation for Node.js, the javascript platform
Closes: 905415
Changes:
nodejs (10.15.0~dfsg-9) unstable; urgency=medium
.
* M-A: foreign on nodejs-doc
* libnode-dev depends libuv1-dev (Closes: #905415)
Checksums-Sha1:
dd5b1b07de4a298354ca0ebdeab6b160e7e459d0 3188 nodejs_10.15.0~dfsg-9.dsc
07d8c0d80427fab6d6548a5f71144884ffd54ac1 94420
nodejs_10.15.0~dfsg-9.debian.tar.xz
922e0c429de41fc6256a2791e202c8138c4fdf62 7760
nodejs_10.15.0~dfsg-9_source.buildinfo
Checksums-Sha256:
28e20415a90df6fb19faba7ad02f57f67b5b83893f8a44b37ae2d8949b06009d 3188
nodejs_10.15.0~dfsg-9.dsc
00bb6ef3d1a81e31bcaca5a39b9ccd58dcce66ca3082c6943822e92b74a6ac5c 94420
nodejs_10.15.0~dfsg-9.debian.tar.xz
1516cb030f0d54da95178bc98f0d67261e2638db1324aadb8ce95b2a815e37f3 7760
nodejs_10.15.0~dfsg-9_source.buildinfo
Files:
2ca7d3261168ccdf8cd17959648e8d33 3188 javascript optional
nodejs_10.15.0~dfsg-9.dsc
aecd75d789dd974e91fc9364e0546680 94420 javascript optional
nodejs_10.15.0~dfsg-9.debian.tar.xz
3440a024a069687125fe8ad40f8bfd5e 7760 javascript optional
nodejs_10.15.0~dfsg-9_source.buildinfo
-BEGIN PGP SIGNATURE-
iQJGBAEBCgAwFiEEA8Tnq7iA9SQwbkgVZhHAXt0583QFAlxFdgcSHGthcG91ZXJA
bWVsaXgub3JnAAoJEGYRwF7dOfN0NOwQAItwDfHwjLIdfA+UvJ+kCRHPSs66rFDM
NlIUUGXkuxGfBvkBC3mUJY6AQOJlLxMd8u1lyO1qOZzq77F6muZXgMIFEXYiQddJ
tfJf4k6wXCKuxKASpYQ3Hyy/sTehJJTzMNTKmyZRYO6Cf1LhKsQcd5WFW9MXQWA/
+ZPLTAtFTUfS8S6UTtl+NeMa1MZ2IGuQ5w4C+2xYtd14gxKZ5AIA8fCyTwYnfbab
P/uiQpD7QoQhQiIDK8Q3rytLRoPVtlwIDn/YgAfXZ0CBdbwU7ynu6bmcEb6DaHea
DRLXztTKOiwwIdVS3wH8TxGFchSBNRXQyFWb8RGLcpCYGq1/Fq8qzY5CoAQaJXVO
WAMUH/tgnbdzkwjhJXd9mETlCcm4mh9XvyBhV6DVTodyJ36YZ1BVHaHGgLkbHrN8
SNAYE0Is6cD8Oa580IU9hAQF5aSHPNlvKya6X+bTmSqG2Pz8B+SP5oXF8SFXJARo
LVq5kBgKk7Y8LqEd0v8JAwAAQaEFRG0ubWuFzUV5bNjL6+tF+wXtPPuucnAM+tgX
Bug#919823: marked as done (harp: FTBFS in sid (ERROR: CODA library and/or header file not found))
Your message dated Mon, 21 Jan 2019 07:34:48 +
with message-id
and subject line Bug#919823: fixed in harp 1.5+data-2
has caused the Debian Bug report #919823,
regarding harp: FTBFS in sid (ERROR: CODA library and/or header file not found)
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.)
--
919823: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919823
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:harp
Version: 1.5+data-1
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in sid but it failed:
[...]
debian/rules build-arch
dh build-arch --with python3
dh_update_autotools_config -a
dh_autoreconf -a
find ! -ipath "./debian/*" -a ! \( -path '*/.git/*' -o -path '*/.hg/*'
-o -path '*/.bzr/*' -o -path '*/.svn/*' -o -path '*/CVS/*' \) -a -type f -exec
md5sum {} + -o -type l -printf "symlink %p
" > debian/autoreconf.before
grep -q ^XDT_ configure.ac
autoreconf -f -i
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, '.'.
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'
[... snipped ...]
checking for floor... yes
checking for pread... yes
checking for stat... yes
checking for memmove... yes
checking for bcopy... yes
checking for strerror... yes
checking for strdup... yes
checking for strcasecmp... yes
checking for strncasecmp... yes
checking for vsnprintf... yes
checking build IDL interface... no
checking build MATLAB interface... no
checking use HDF4... yes
checking for compress in -lz... yes
checking for jpeg_start_compress in -ljpeg... yes
checking for SZ_encoder_enabled in -lsz... yes
checking hdf.h usability... yes
checking hdf.h presence... yes
checking for hdf.h... yes
checking netcdf.h usability... yes
checking netcdf.h presence... yes
checking for netcdf.h... yes
checking mfhdf.h usability... yes
checking mfhdf.h presence... yes
checking for mfhdf.h... yes
checking for Hopen in -ldfalt... yes
checking for SDstart in -lmfhdfalt... yes
checking for HDF4 installation... yes
checking coda.h usability... yes
checking coda.h presence... yes
checking for coda.h... yes
checking for coda_init in -lcoda... no
checking for CODA installation... no
configure: error:
ERROR: CODA library and/or header file not found.
Try setting the CODA_LIB and CODA_INCLUDE environment variables to the
location of your CODA library and include file.
make[1]: *** [debian/rules:19: override_dh_auto_configure] Error 1
make[1]: Leaving directory '/<>/harp-1.5+data'
make: *** [debian/rules:7: build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit
status 2
(The above is just how the build ends and not necessarily the most relevant
part)
The build was made in my autobuilder with "dpkg-buildpackage -B"
and it also fails here with plain "dpkg-buildpackage":
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/harp.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: harp
Source-Version: 1.5+data-2
We believe that the bug you reported is fixed in the latest version of
harp, 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 919...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Alastair McKinstry (supplier of updated harp package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 20 Jan 2019 13:50:49 +
Source: harp
Binary: harp libharp9 libharp-dev python3-harp
Architecture: source
Bug#916317: Working on bug
Attempting to find solution, also asked on debian-python for some assistance.
Bug#919973: netdata: fails to install: useradd: group netdata exists - if you want to add this user to that group, use -g.
Package: netdata Version: 1.12.0~rc3-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): Selecting previously unselected package netdata. (Reading database ... (Reading database ... 5667 files and directories currently installed.) Preparing to unpack .../netdata_1.12.0~rc3-1_amd64.deb ... Unpacking netdata (1.12.0~rc3-1) ... Setting up netdata (1.12.0~rc3-1) ... useradd: group netdata exists - if you want to add this user to that group, use -g. dpkg: error processing package netdata (--configure): installed netdata package post-installation script subprocess returned error exit status 9 Errors were encountered while processing: netdata cheers, Andreas netdata_1.12.0~rc3-1.log.gz Description: application/gzip
Bug#919971: node-rollup-pluginutils: autopkgtestsuite failure
Package: node-rollup-pluginutils
Version: 2.3.3-2
Severity: serious
Tags: patch
Hello, looks like the latest upload fails its autopkgtestsuite, since
some days/weeks.
See e.g.:
https://ci.debian.net/data/autopkgtest/unstable/amd64/n/node-rollup-pluginutils/1618356/log.gz
(Reading database ... 22971 files and directories currently installed.)
Removing autopkgtest-satdep (0) ...
autopkgtest [07:49:14]: test upstreamtestsuite: [---
find test/ -name '*.js' -and -not -name 'createFilter.test.js' -exec mocha {} \;
internal/modules/cjs/loader.js:583
throw err;
^
Error: Cannot find module '..'
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:581:15)
at Function.Module._load (internal/modules/cjs/loader.js:507:25)
at Module.require (internal/modules/cjs/loader.js:637:17)
at require (internal/modules/cjs/helpers.js:22:18)
at Object.
(/tmp/autopkgtest-lxc.nqmg3_9p/downtmp/build.9cL/src/test/addExtension.test.js:2:22)
at Module._compile (internal/modules/cjs/loader.js:689:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:700:10)
at Module.load (internal/modules/cjs/loader.js:599:32)
at tryModuleLoad (internal/modules/cjs/loader.js:538:12)
at Function.Module._load (internal/modules/cjs/loader.js:530:3)
at Module.require (internal/modules/cjs/loader.js:637:17)
at require (internal/modules/cjs/helpers.js:22:18)
at /usr/lib/nodejs/mocha/lib/mocha.js:231:27
at Array.forEach ()
at Mocha.loadFiles (/usr/lib/nodejs/mocha/lib/mocha.js:228:14)
at Mocha.run (/usr/lib/nodejs/mocha/lib/mocha.js:536:10)
at Object. (/usr/lib/nodejs/mocha/bin/_mocha:573:18)
at Module._compile (internal/modules/cjs/loader.js:689:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:700:10)
at Module.load (internal/modules/cjs/loader.js:599:32)
at tryModuleLoad (internal/modules/cjs/loader.js:538:12)
at Function.Module._load (internal/modules/cjs/loader.js:530:3)
at Function.Module.runMain (internal/modules/cjs/loader.js:742:12)
at startup (internal/bootstrap/node.js:283:19)
at bootstrapNodeJSCore (internal/bootstrap/node.js:743:3)
internal/modules/cjs/loader.js:583
throw err;
^
I'm not sure which is the best approach to fix this issue, but at least
this approach works:
--- node-rollup-pluginutils-2.3.3/debian/tests/upstreamtestsuite 2018-12-31
02:23:05.0 +0100
+++ node-rollup-pluginutils-2.3.3/debian/tests/upstreamtestsuite 2019-01-20
22:46:52.0 +0100
@@ -1,2 +1,7 @@
#!/bin/sh
-make -f debian/rules test_package
+sed -i test/dataToEsm.test.js -e "s/( '..' )/('rollup-pluginutils')/g"
+sed -i test/attachScopes.test.js -e "s/( '..' )/('rollup-pluginutils')/g"
+sed -i test/addExtension.test.js -e "s/( '..' )/('rollup-pluginutils')/g"
+sed -i test/makeLegalIdentifier.test.js -e "s/( '..'
)/('rollup-pluginutils')/g"
+sed -i test/createFilter.test.js -e "s/( '..' )/('rollup-pluginutils')/g"
+make -f debian/rules test_package
This is something that basically reverts commit
b33024e405af90183a6e6a65ab3163f177932e5e
Thanks for having a look,
Gianfranco
Processed: affects 919968
Processing commands for cont...@bugs.debian.org: > affects 919968 > src:libparanamer-java,src:libreoffice,src:java-string-similarity,src:libgoogle-gson-java,src:libxml-security-java,src:antlr4,src:jnr-posix,src:localizer,src:jackson-databind, Bug #919968 [openjdk-11-jdk-headless] libreoffice: binary-all FTBFS Added indication that 919968 affects src:libparanamer-java, src:libreoffice, src:java-string-similarity, src:libgoogle-gson-java, src:libxml-security-java, src:antlr4, src:jnr-posix, src:localizer, and src:jackson-databind > thanks Stopping processing here. Please contact me if you need assistance. -- 919968: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919968 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#919968: libreoffice: binary-all FTBFS
reassign 919968 openjdk-11-jdk-headless merge 919883 919968 thanks Hi, On Mon, Jan 21, 2019 at 08:28:16AM +0200, Adrian Bunk wrote: > ... > [build BIN] ucbhelper > S=/<> && I=$S/instdir && W=$S/workdir && mkdir -p > $W/Module/nonl10n/ && touch $W/Module/nonl10n/ucbhelper > javadoc: error - The code being documented uses modules but the packages > defined in http://java.sun.com/j2se/1.5/docs/api/ are in the unnamed module. > make[2]: *** [/<>/odk/CustomTarget_javadoc.mk:34: > /<>/workdir/CustomTarget/odk/docs/java/ref/javadoc_log.txt] > Error 1 See http://bugs.debian.org/919883. Regards, Rene
Processed (with 1 error): affects 919968, merging 919883 919968
Processing commands for cont...@bugs.debian.org: > affects 919968 > src:libparanamer-java,src:libreoffice,src:java-string-similarity,src:libgoogle-gson-java,src:libxml-security-java,src:antlr4,src:jnr-posix,src:localizer,src:jackson-databind Bug #919968 [openjdk-11-jdk-headless] libreoffice: binary-all FTBFS Ignoring request to set affects of bug 919968 to the same value previously set > merge 919883 919968 Bug #919883 [openjdk-11-jdk-headless] libreoffice arch all FTBFS, javadoc: error - The code being documented uses modules but the packages defined in http://java.sun.com/j2se/1.5/docs/api/ are in the unnamed module. Bug #919798 [openjdk-11-jdk-headless] antlr4: FTBFS (Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar) Bug #919800 [openjdk-11-jdk-headless] jackson-databind: FTBFS (Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar) Bug #919801 [openjdk-11-jdk-headless] libgoogle-gson-java: FTBFS (Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar) Bug #919874 [openjdk-11-jdk-headless] bsaf: FTBFS (Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar) Bug #919875 [openjdk-11-jdk-headless] commons-csv: FTBFS (Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar= Bug #919876 [openjdk-11-jdk-headless] java-string-similarity: FTBFS (Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar) Bug #919878 [openjdk-11-jdk-headless] servlet-api: FTBFS (Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar) Bug #919895 [openjdk-11-jdk-headless] openjdk-11-jdk-headless: Regression: Breaks a bunch of packages using javadoc Unable to merge bugs because: affects of #919876 is 'src:libgoogle-gson-java,src:java-string-similarity,src:libparanamer-java,src:libreoffice,src:jnr-posix,src:antlr4,src:libxml-security-java,src:jackson-databind,src:localizer,src:commons-csv,src:weupnp,src:servlet-api,src:bsaf,src:dirgra' not 'src:libparanamer-java,src:libreoffice,src:java-string-similarity,src:libgoogle-gson-java,src:libxml-security-java,src:antlr4,src:jnr-posix,src:localizer,src:jackson-databind,src:dirgra,src:bsaf,src:servlet-api,src:weupnp,src:commons-csv' affects of #919801 is 'src:localizer,src:jackson-databind,src:dirgra,src:bsaf,src:servlet-api,src:weupnp,src:commons-csv,src:libreoffice,src:libparanamer-java,src:java-string-similarity,src:libgoogle-gson-java,src:libxml-security-java,src:antlr4,src:jnr-posix' not 'src:libparanamer-java,src:libreoffice,src:java-string-similarity,src:libgoogle-gson-java,src:libxml-security-java,src:antlr4,src:jnr-posix,src:localizer,src:jackson-databind,src:dirgra,src:bsaf,src:servlet-api,src:weupnp,src:commons-csv' affects of #919968 is 'src:java-string-similarity,src:libxml-security-java,src:libreoffice,src:jackson-databind,src:localizer,src:libgoogle-gson-java,src:libparanamer-java,src:jnr-posix,src:antlr4' not 'src:libparanamer-java,src:libreoffice,src:java-string-similarity,src:libgoogle-gson-java,src:libxml-security-java,src:antlr4,src:jnr-posix,src:localizer,src:jackson-databind,src:dirgra,src:bsaf,src:servlet-api,src:weupnp,src:commons-csv' affects of #919895 is 'src:jackson-databind,src:localizer,src:commons-csv,src:weupnp,src:servlet-api,src:bsaf,src:dirgra,src:libgoogle-gson-java,src:java-string-similarity,src:libparanamer-java,src:libreoffice,src:jnr-posix,src:antlr4,src:libxml-security-java' not 'src:libparanamer-java,src:libreoffice,src:java-string-similarity,src:libgoogle-gson-java,src:libxml-security-java,src:antlr4,src:jnr-posix,src:localizer,src:jackson-databind,src:dirgra,src:bsaf,src:servlet-api,src:weupnp,src:commons-csv' affects of #919874 is 'src:servlet-api,src:commons-csv,src:weupnp,src:dirgra,src:bsaf,src:localizer,src:jackson-databind,src:antlr4,src:jnr-posix,src:libxml-security-java,src:libgoogle-gson-java,src:libparanamer-java,src:libreoffice,src:java-string-similarity' not 'src:libparanamer-java,src:libreoffice,src:java-string-similarity,src:libgoogle-gson-java,src:libxml-security-java,src:antlr4,src:jnr-posix,src:localizer,src:jackson-databind,src:dirgra,src:bsaf,src:servlet-api,src:weupnp,src:commons-csv' affects of #919798 is 'src:java-string-similarity,src:libreoffice,src:libparanamer-java,src:libgoogle-gson-java,src:libxml-security-java,src:jnr-posix,src:antlr4,src:jackson-databind,src:localizer,src:bsaf,src:dirgra,src:weupnp,src:commons-csv,src:servlet-api' not 'src:libparanamer-java,src:libreoffice,src:java-string-similarity,src:libgoogle-gson-java,src:libxml-security-java,src:antlr4,src:jnr-posix,src:localizer,src:jackson-databind,src:dirgra,src:bsaf,src:servlet-api,src:weupnp,src:commons-csv' affects of #919878 is
Processed (with 1 error): affects 919968, merging 19883 919968
Processing commands for cont...@bugs.debian.org: > affects 919968 > src:libparanamer-java,src:libreoffice,src:java-string-similarity,src:libgoogle-gson-java,src:libxml-security-java,src:antlr4,src:jnr-posix,src:localizer,src:jackson-databind Bug #919968 [openjdk-11-jdk-headless] libreoffice: binary-all FTBFS Ignoring request to set affects of bug 919968 to the same value previously set > merge 19883 919968 Failed to merge 19883: Not altering archived bugs; see unarchive. > thanks Stopping processing here. Please contact me if you need assistance. -- 919968: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919968 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 1 error): Re: Bug#919968: libreoffice: binary-all FTBFS
Processing commands for cont...@bugs.debian.org: > reassign 919968 openjdk-11-jdk-headless Bug #919968 [src:libreoffice] libreoffice: binary-all FTBFS Bug reassigned from package 'src:libreoffice' to 'openjdk-11-jdk-headless'. No longer marked as found in versions libreoffice/1:6.1.5~rc1-1. Ignoring request to alter fixed versions of bug #919968 to the same values previously set > merge 919883 919968 Bug #919883 [openjdk-11-jdk-headless] libreoffice arch all FTBFS, javadoc: error - The code being documented uses modules but the packages defined in http://java.sun.com/j2se/1.5/docs/api/ are in the unnamed module. Bug #919798 [openjdk-11-jdk-headless] antlr4: FTBFS (Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar) Bug #919800 [openjdk-11-jdk-headless] jackson-databind: FTBFS (Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar) Bug #919801 [openjdk-11-jdk-headless] libgoogle-gson-java: FTBFS (Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar) Bug #919874 [openjdk-11-jdk-headless] bsaf: FTBFS (Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar) Bug #919875 [openjdk-11-jdk-headless] commons-csv: FTBFS (Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar= Bug #919876 [openjdk-11-jdk-headless] java-string-similarity: FTBFS (Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar) Bug #919878 [openjdk-11-jdk-headless] servlet-api: FTBFS (Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar) Bug #919895 [openjdk-11-jdk-headless] openjdk-11-jdk-headless: Regression: Breaks a bunch of packages using javadoc Unable to merge bugs because: affects of #919800 is 'src:libxml-security-java,src:jnr-posix,src:antlr4,src:java-string-similarity,src:libparanamer-java,src:libreoffice,src:libgoogle-gson-java,src:bsaf,src:dirgra,src:weupnp,src:commons-csv,src:servlet-api,src:jackson-databind,src:localizer' not 'src:libparanamer-java,src:libreoffice,src:java-string-similarity,src:libgoogle-gson-java,src:libxml-security-java,src:antlr4,src:jnr-posix,src:localizer,src:jackson-databind,src:dirgra,src:bsaf,src:servlet-api,src:weupnp,src:commons-csv' affects of #919874 is 'src:servlet-api,src:commons-csv,src:weupnp,src:dirgra,src:bsaf,src:localizer,src:jackson-databind,src:antlr4,src:jnr-posix,src:libxml-security-java,src:libgoogle-gson-java,src:libparanamer-java,src:libreoffice,src:java-string-similarity' not 'src:libparanamer-java,src:libreoffice,src:java-string-similarity,src:libgoogle-gson-java,src:libxml-security-java,src:antlr4,src:jnr-posix,src:localizer,src:jackson-databind,src:dirgra,src:bsaf,src:servlet-api,src:weupnp,src:commons-csv' affects of #919895 is 'src:jackson-databind,src:localizer,src:commons-csv,src:weupnp,src:servlet-api,src:bsaf,src:dirgra,src:libgoogle-gson-java,src:java-string-similarity,src:libparanamer-java,src:libreoffice,src:jnr-posix,src:antlr4,src:libxml-security-java' not 'src:libparanamer-java,src:libreoffice,src:java-string-similarity,src:libgoogle-gson-java,src:libxml-security-java,src:antlr4,src:jnr-posix,src:localizer,src:jackson-databind,src:dirgra,src:bsaf,src:servlet-api,src:weupnp,src:commons-csv' affects of #919878 is 'src:bsaf,src:dirgra,src:weupnp,src:commons-csv,src:servlet-api,src:jackson-databind,src:localizer,src:libxml-security-java,src:jnr-posix,src:antlr4,src:java-string-similarity,src:libparanamer-java,src:libreoffice,src:libgoogle-gson-java' not 'src:libparanamer-java,src:libreoffice,src:java-string-similarity,src:libgoogle-gson-java,src:libxml-security-java,src:antlr4,src:jnr-posix,src:localizer,src:jackson-databind,src:dirgra,src:bsaf,src:servlet-api,src:weupnp,src:commons-csv' affects of #919875 is 'src:jackson-databind,src:localizer,src:commons-csv,src:weupnp,src:servlet-api,src:bsaf,src:dirgra,src:libgoogle-gson-java,src:java-string-similarity,src:libreoffice,src:libparanamer-java,src:jnr-posix,src:antlr4,src:libxml-security-java' not 'src:libparanamer-java,src:libreoffice,src:java-string-similarity,src:libgoogle-gson-java,src:libxml-security-java,src:antlr4,src:jnr-posix,src:localizer,src:jackson-databind,src:dirgra,src:bsaf,src:servlet-api,src:weupnp,src:commons-csv' affects of #919876 is 'src:libgoogle-gson-java,src:java-string-similarity,src:libparanamer-java,src:libreoffice,src:jnr-posix,src:antlr4,src:libxml-security-java,src:jackson-databind,src:localizer,src:commons-csv,src:weupnp,src:servlet-api,src:bsaf,src:dirgra' not 'src:libparanamer-java,src:libreoffice,src:java-string-similarity,src:libgoogle-gson-java,src:libxml-security-java,src:antlr4,src:jnr-posix,src:localizer,src:jackson-databind,src:dirgra,src:bsaf,src:servlet-api,src:weupnp,src:commons-csv' affects of #919801 is
Processed: severity of 919962 is serious
Processing commands for cont...@bugs.debian.org: > severity 919962 serious Bug #919962 [goaccess] Errors caused by not installing Recommend packages Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 919962: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919962 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#919968: libreoffice: binary-all FTBFS
Source: libreoffice Version: 1:6.1.5~rc1-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=libreoffice=all=1%3A6.1.5~rc1-1=1547977527=0 ... [build BIN] ucbhelper S=/<> && I=$S/instdir && W=$S/workdir && mkdir -p $W/Module/nonl10n/ && touch $W/Module/nonl10n/ucbhelper javadoc: error - The code being documented uses modules but the packages defined in http://java.sun.com/j2se/1.5/docs/api/ are in the unnamed module. make[2]: *** [/<>/odk/CustomTarget_javadoc.mk:34: /<>/workdir/CustomTarget/odk/docs/java/ref/javadoc_log.txt] Error 1
Bug#919967: ndcube FTBFS: There is a programable error in your configuration file:
Source: ndcube
Version: 1.0.1-2
Severity: serious
Tags: ftbfs
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ndcube.html
...
Running Sphinx v1.7.9
/usr/lib/python3/dist-packages/astropy_helpers/sphinx/conf.py:5: UserWarning:
Note that astropy_helpers.sphinx.conf is deprecated - use sphinx_astropy.conf
instead
warnings.warn("Note that astropy_helpers.sphinx.conf is deprecated - use
sphinx_astropy.conf instead")
Configuration error:
There is a programable error in your configuration file:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/sphinx/config.py", line 161, in __init__
execfile_(filename, config)
File "/usr/lib/python3/dist-packages/sphinx/util/pycompat.py", line 150, in
execfile_
exec_(code, _globals)
File "conf.py", line 143, in
extensions.remove('astropy_helpers.extern.numpydoc')
ValueError: list.remove(x): x not in list
make[1]: *** [debian/rules:18: override_dh_auto_build] Error 2
Bug#919966: akregator: symbol lookup error: /usr/lib/x86_64-linux-gnu/libKF5NewStuff.so.5: undefined symbol: _ZN7KNSCore6Engine15signalErrorCodeERKNS_9ErrorCodeERK7QStringRK8QVariant
Package: akregator Version: 4:18.08.1-1 Severity: grave Justification: renders package unusable akregator doesn't start anymore. It exits with the following error message: akregator: symbol lookup error: /usr/lib/x86_64-linux-gnu/libKF5NewStuff.so.5: undefined symbol: _ZN7KNSCore6Engine15signalErrorCodeERKNS_9ErrorCodeERK7QStringRK8QVariant -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_CA.utf8, LC_CTYPE=fr_CA.utf8 (charmap=UTF-8), LANGUAGE=fr_CA.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages akregator depends on: ii kinit5.54.0-1 ii kio 5.51.0-1 ii libc62.28-5 ii libgcc1 1:8.2.0-14 ii libkf5codecs55.51.0-1 ii libkf5completion55.51.0-1 ii libkf5configcore55.51.0-1 ii libkf5configgui5 5.51.0-1 ii libkf5configwidgets5 5.51.0-1 ii libkf5coreaddons55.51.0-1 ii libkf5crash5 5.51.0-1 ii libkf5grantleetheme-plugins 18.08.1-1 ii libkf5grantleetheme5 18.08.1-1 ii libkf5i18n5 5.51.0-1 ii libkf5iconthemes55.51.0-1 ii libkf5jobwidgets55.51.0-1 ii libkf5kcmutils5 5.51.0-1 ii libkf5kiocore5 5.54.1-1 ii libkf5kiogui55.54.1-1 ii libkf5kiowidgets55.54.1-1 ii libkf5kontactinterface5 18.08.1-1 ii libkf5libkdepim-plugins 4:18.08.1-1 ii libkf5libkdepim5 4:18.08.1-1 ii libkf5messageviewer5abi1 4:18.08.1-1 ii libkf5mimetreeparser5abi14:18.08.1-1 ii libkf5notifications5 5.51.0-1 ii libkf5notifyconfig5 5.54.0-1 ii libkf5parts5 5.54.0-1 ii libkf5pimcommon5abi2 4:18.08.1-1 ii libkf5pimtextedit5abi2 18.08.1-1 ii libkf5service-bin5.51.0-1 ii libkf5service5 5.51.0-1 ii libkf5syndication5abi1 18.08.1-1 ii libkf5textwidgets5 5.51.0-1 ii libkf5webengineviewer5abi1 4:18.08.1-1 ii libkf5widgetsaddons5 5.51.0-1 ii libkf5xmlgui55.51.0-1 ii libqt5core5a 5.11.2+dfsg-7 ii libqt5dbus5 5.11.2+dfsg-7 ii libqt5gui5 5.11.2+dfsg-7 ii libqt5network5 5.11.2+dfsg-7 ii libqt5printsupport5 5.11.2+dfsg-7 ii libqt5webenginewidgets5 5.11.2+dfsg-2+b1 ii libqt5widgets5 5.11.2+dfsg-7 ii libqt5xml5 5.11.2+dfsg-7 ii libstdc++6 8.2.0-14 akregator recommends no packages. akregator suggests no packages. -- no debconf information
Bug#880393: nmuing cyrus-sasl2
Hi Ondřej, On Sun, Jan 20, 2019 at 10:01:04PM +0100, OndÅ?ej Surý wrote: > No harm doing was intended. I simply missed the NMU. > > If you can point me to the direction of the patches you prepared I will try > to care of it before soft freeze. In good NMU practise, I sent the combined patch to the very bug you are replying to. You can find it at: https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=880393;filename=cyrus-sasl2_2.1.27~101-g0780600%2Bdfsg-3.2.debdiff;msg=24 May I suggest subscribing to the cyrus-sasl2 package for not missing important communication? That's very easy to do these days using https://tracker.debian.org/. Once logged in, you have a "subscribe" button in the top right corner. It would be good if you could include those changes before the soft freeze indeed. Thank you for following up. Helmut
Processed: tagging 919965
Processing commands for cont...@bugs.debian.org: > tags 919965 + buster sid Bug #919965 [unyaffs] unyaffs: Non-working maintainer address Added tag(s) buster and sid. > thanks Stopping processing here. Please contact me if you need assistance. -- 919965: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919965 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: found 919965 in 0.9.6-1
Processing commands for cont...@bugs.debian.org: > found 919965 0.9.6-1 Bug #919965 [unyaffs] unyaffs: Non-working maintainer address Marked as found in versions unyaffs/0.9.6-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 919965: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919965 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#919717: marked as done (biosig4c++ FTBFS on 32bit: symbol differences)
Your message dated Mon, 21 Jan 2019 06:59:44 +0200 with message-id <20190121045944.GN32397@localhost> and subject line Fixed in 1.9.3-2 has caused the Debian Bug report #919717, regarding biosig4c++ FTBFS on 32bit: symbol differences 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.) -- 919717: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919717 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: biosig4c++ Version: 1.9.3-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=biosig4c%2B%2B=sid ... dh_makeshlibs dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see diff output below dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libbiosig2/DEBIAN/symbols doesn't match completely debian/libbiosig2.symbols --- debian/libbiosig2.symbols (libbiosig2_1.9.3-1_i386) +++ dpkg-gensymbolsvMyQ0c 2019-01-18 13:32:03.817439748 + @@ -670,11 +670,11 @@ (c++)"TiXmlPrinter::VisitExit(TiXmlDocument const&)@Base" 1.3.6 (c++)"TiXmlPrinter::VisitExit(TiXmlElement const&)@Base" 1.3.6 (c++)"TiXmlPrinter::~TiXmlPrinter()@Base" 1.3.6 - (c++)"TiXmlString::append(char const*, unsigned long)@Base" 1.3.6 - (c++)"TiXmlString::assign(char const*, unsigned long)@Base" 1.3.6 +#MISSING: 1.9.3-1# (c++)"TiXmlString::append(char const*, unsigned long)@Base" 1.3.6 +#MISSING: 1.9.3-1# (c++)"TiXmlString::assign(char const*, unsigned long)@Base" 1.3.6 (c++)"TiXmlString::npos@Base" 1.3.6 (c++)"TiXmlString::nullrep_@Base" 1.3.6 - (c++)"TiXmlString::reserve(unsigned long)@Base" 1.3.6 +#MISSING: 1.9.3-1# (c++)"TiXmlString::reserve(unsigned long)@Base" 1.3.6 (c++)"TiXmlText::Accept(TiXmlVisitor*) const@Base" 1.3.6 (c++)"TiXmlText::Blank() const@Base" 1.3.6 (c++)"TiXmlText::Clone() const@Base" 1.3.6 @@ -713,6 +713,10 @@ UnitsOfMeasurementCode_free@Base 1.3.6 UnitsOfMeasurementCode_print@Base 1.3.6 VERBOSE_LEVEL@Base 1.3.6 + _Z8mymallocj@Base 1.9.3-1 + _ZN11TiXmlString6appendEPKcj@Base 1.9.3-1 + _ZN11TiXmlString6assignEPKcj@Base 1.9.3-1 + _ZN11TiXmlString7reserveEj@Base 1.9.3-1 _ZN12TiXmlComment8StreamInEPSiPNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base 1.9.3 _ZN12TiXmlElement12SetAttributeERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES7_@Base 1.9.3 _ZN12TiXmlElement12SetAttributeERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEi@Base 1.9.3 @@ -1138,7 +1142,7 @@ makeTree@Base 1.3.6 mfer_swap8b@Base 1.3.6 month_string2int@Base 1.9.3 - (c++)"mymalloc(unsigned long)@Base" 1.3.6 +#MISSING: 1.9.3-1# (c++)"mymalloc(unsigned long)@Base" 1.3.6 newNode@Base 1.3.6 (c++)"operator+(TiXmlString const&, TiXmlString const&)@Base" 1.3.6 (c++)"operator+(TiXmlString const&, char const*)@Base" 1.3.6 dh_makeshlibs: failing due to earlier errors make[1]: *** [debian/rules:76: override_dh_makeshlibs] Error 2 --- End Message --- --- Begin Message --- Version: 1.9.3-2 biosig4c++ (1.9.3-2) unstable; urgency=medium ... * Provide symbols file only for architectures where it can be used unchanged ... -- Andreas Tille Sun, 20 Jan 2019 22:09:35 +0100 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--- End Message ---
Bug#919965: unyaffs: Non-working maintainer address
Package: unyaffs Version: 0.9.7-0.1 Severity: serious Justification: Policy 3.3 A working maintainer address is required: A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: matthew.fisc...@ubuntu.com host mx.canonical.com [91.189.95.10] SMTP error from remote mail server after RCPT TO:: 550 5.1.1 : Recipient address rejected: User unknown in virtual alias table Date: Sun, 06 Jan 2019 23:30:37 +0200 Source: unyaffs Binary: unyaffs Architecture: source Version: 0.9.7-0.1 Distribution: unstable Urgency: medium Maintainer: Matthew Fischer Changed-By: Adrian Bunk Scott K
Processed (with 1 error): your mail
Processing commands for cont...@bugs.debian.org: > merge 917756 918201 918625 Bug #917756 [src:astropy-healpix] astropy-healpix: FTBFS: tests failed Unable to merge bugs because: severity of #918625 is 'normal' not 'serious' affects of #918625 is 'src:python-numpy' not '' severity of #918201 is 'normal' not 'serious' blocks of #918201 is '917323' not '' Failed to merge 917756: Did not alter merged bugs. > End of message, stopping processing here. Please contact me if you need assistance. -- 917756: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917756 918201: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918201 918625: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918625 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#880393: nmuing cyrus-sasl2
Hello, I extracted Helmut's changes for this issue from the debdiff he posted in an earlier message, and proposed a merge request on salsa. https://salsa.debian.org/debian/cyrus-sasl2/merge_requests/3 as a git-format-patch(1) patch: https://salsa.debian.org/debian/cyrus-sasl2/merge_requests/3.patch I have built it and verified that the Depends line and library dependencies are corrected, and that it is installable. I have not actually tested the module's functionality. I agree with Helmut that this looks suitable for a stretch update. I would be willing to drive that process if the maintainers agree but lack time.
Bug#919907: ntopng FTBFS with ndpi 2.6
Thank you for bug report. I am going to upload ntopng 3.8 soon and it will fix the build against the latest ndpi. Ludovico On Sun, Jan 20, 2019 at 8:36 AM Adrian Bunk wrote: > Source: ntopng > Version: 2.4+dfsg1-4 > Severity: serious > Tags: ftbfs > > > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ntopng.html > > ... > g++ -g -Wall -I/build/1st/ntopng-3.2+dfsg1 > -I/build/1st/ntopng-3.2+dfsg1/include -I/usr/local/include > -D_FILE_OFFSET_BITS=64 -I/usr/include/hiredis -I/usr/include/hiredis > -I/build/1st/ntopng-3.2+dfsg1/third-party/mongoose -I/usr/include/json-c > -I/usr/include/ndpi/libndpi > -I/build/1st/ntopng-3.2+dfsg1/third-party/LuaJIT-2.1.0-beta3/src -isystem > /usr/include/mit-krb5 -I/usr/include/pgm-5.2 > -I/usr/lib/x86_64-linux-gnu/pgm-5.2/include -I/usr/include/mariadb > -I/usr/include/mariadb/mysql -Wdate-time -D_FORTIFY_SOURCE=2 > -I/build/1st/ntopng-3.2+dfsg1 -I/build/1st/ntopng-3.2+dfsg1/include > -I/usr/local/include > -I/build/1st/ntopng-3.2+dfsg1/third-party/http-client-c/src/ > -I/usr/include/openssl -DDATA_DIR='"/usr/share"' > -I/build/1st/ntopng-3.2+dfsg1/third-party/libgeohash > -I/build/1st/ntopng-3.2+dfsg1/third-party/patricia -g -O2 > -ffile-prefix-map=/build/1st/ntopng-3.2+dfsg1=. -fstack-protector-strong > -Wformat -Werror=format-security -c src/AlertCounter.cpp -o > src/AlertCounter.o > In file included from src/AlertCounter.cpp:22: > /build/1st/ntopng-3.2+dfsg1/include/ntop_includes.h:107:10: fatal error: > ndpi_main.h: No such file or directory > #include "ndpi_main.h" > ^ > compilation terminated. > make[2]: *** [Makefile:153: src/AlertCounter.o] Error 1 >
Bug#919349: marked as done (pyvo: Please remove python-astropy-helpers build dependency)
Your message dated Mon, 21 Jan 2019 00:20:48 + with message-id and subject line Bug#919349: fixed in pyvo 0.9.2-2 has caused the Debian Bug report #919349, regarding pyvo: Please remove python-astropy-helpers build dependency 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.) -- 919349: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919349 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pyvo Version: 0.9.2-1 Severity: serious Dear maintainer, python-astropy-helpers (the Python 2 package) is going away soon. Therefore, please remove it as build dependency from pyvo. I is probably anyway unused and just forgotten to remove, right? Cheers Ole --- End Message --- --- Begin Message --- Source: pyvo Source-Version: 0.9.2-2 We believe that the bug you reported is fixed in the latest version of pyvo, 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 919...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Josue Ortega (supplier of updated pyvo package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 20 Jan 2019 17:45:38 -0600 Source: pyvo Binary: python3-pyvo Architecture: source all Version: 0.9.2-2 Distribution: unstable Urgency: medium Maintainer: Debian Astronomy Maintainers Changed-By: Josue Ortega Description: python3-pyvo - Python 3 library for data services of the Virtual observatory (VO Closes: 919349 Changes: pyvo (0.9.2-2) unstable; urgency=medium . * Remove python-astropy-helpers. (Closes: #919349) * Add patch to include version file generated at build time, otherwise package import does not work. Checksums-Sha1: 6729d8c19a07358fcedbf65438954cddecf63f21 2158 pyvo_0.9.2-2.dsc cd5d7b460ea2bbeda24911011dbc4ce2ac6ec8fb 6436 pyvo_0.9.2-2.debian.tar.xz eac65b3362f465cc8dbfc86e8452e900c98b2de9 1286380 python3-pyvo_0.9.2-2_all.deb 9deb1fb2c253cc6072760107ad4042b648dde9c9 8949 pyvo_0.9.2-2_amd64.buildinfo Checksums-Sha256: ff62274837e52d5993add5608002303ffca21260155e08b752517ef41d43b301 2158 pyvo_0.9.2-2.dsc a6acbeacc2ea81e3d0a70087ec6354d92b51d8710957c3d7c5e64e2fd03fa08f 6436 pyvo_0.9.2-2.debian.tar.xz 640cce4214bc6c24eb13729f9cbc764247325c9d41cc350578087592d848f7a2 1286380 python3-pyvo_0.9.2-2_all.deb 2633db7de30eee588e8e6d147c75676a85c592f4d045bdb4f75fc3efb58f6e91 8949 pyvo_0.9.2-2_amd64.buildinfo Files: 24d698af8635466e4a1ed54e21e0c0b8 2158 python optional pyvo_0.9.2-2.dsc afc6a803b316b914fa5fd7a6c4c33c02 6436 python optional pyvo_0.9.2-2.debian.tar.xz 7a542e7525e8ed3c774e793180113b4c 1286380 python optional python3-pyvo_0.9.2-2_all.deb eee255b94ae2d87bd04340a7c79e6a24 8949 python optional pyvo_0.9.2-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCAAvFiEEdzOzKNJ5X1viMlrdAVCdXKtK/T8FAlxFDGgRHGpvc3VlQGRl Ymlhbi5vcmcACgkQAVCdXKtK/T+DrRAAn91guONLohHOu0474/qzcQvC30AqWHwI 7Qz2vYHmp8YNz4Jx1tcu73+s5/sbnew5FpiqucbRK4cWPAC3MX/17aaBRTpfjv0t CjfEjJTi6vo8iBNFUul2qUa0TMJf60ECRdkg1Xg8eEkFHgS19vYTYi9a4QjXUFPu skFGDiYnCVHFHlqJ30BJciSbbQyQzr7PSzuJOLIhWWHTl7U9ryhQxwr3hE2/fwOl JgN0CZ5k8/Gq0j3VFk0TE+frlJmbo38WhC3DAC5RJaYwCaVN3DSdGtXWkj+bSAw8 es7aSR9TQKxPjhFMx1qBKshwceyDccFQOckb+2veL/FiUiI4KwMYpeCLyT+mt9yy NBK5P9gxJSrYT6su9+mm2tV46LnNxZJ5LX/Plqiy8xcieMp6quLePd9ofLde/BpB ls2EuZd8p3f8zVVqWi+qzMUQAY2QU0gqlHgB36AO04inmX9fhsR8R/kuQofeNHe/ LIFQz/9WkoBmD2Sb1jHQAwjXVL2AzRZ+3gRrsxysxv1cwFk2oSQDJBfOZ5ryBoyH HDhLyESwMQwIJgkdJuYzE9d58ttvXxZqQmb1sNb5o8j3/c5zpk6lb0mIJ4watfRc CgPFzZN5MfavZ1UAqznw9kfg8VOkHXtiy1DTEIpbAItnEqL3MYHzHwqNepojNZbG CbfXNwjibow= =k+Vx -END PGP SIGNATURE End Message ---
Processed: More affects
Processing commands for cont...@bugs.debian.org: > affects 919895 src:dirgra Bug #919895 [openjdk-11-jdk-headless] openjdk-11-jdk-headless: Regression: Breaks a bunch of packages using javadoc Bug #919798 [openjdk-11-jdk-headless] antlr4: FTBFS (Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar) Bug #919800 [openjdk-11-jdk-headless] jackson-databind: FTBFS (Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar) Bug #919801 [openjdk-11-jdk-headless] libgoogle-gson-java: FTBFS (Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar) Bug #919874 [openjdk-11-jdk-headless] bsaf: FTBFS (Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar) Bug #919875 [openjdk-11-jdk-headless] commons-csv: FTBFS (Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar= Bug #919876 [openjdk-11-jdk-headless] java-string-similarity: FTBFS (Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar) Bug #919878 [openjdk-11-jdk-headless] servlet-api: FTBFS (Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar) Bug #919883 [openjdk-11-jdk-headless] libreoffice arch all FTBFS, javadoc: error - The code being documented uses modules but the packages defined in http://java.sun.com/j2se/1.5/docs/api/ are in the unnamed module. Added indication that 919895 affects src:dirgra Added indication that 919798 affects src:dirgra Added indication that 919800 affects src:dirgra Added indication that 919801 affects src:dirgra Added indication that 919874 affects src:dirgra Added indication that 919875 affects src:dirgra Added indication that 919876 affects src:dirgra Added indication that 919878 affects src:dirgra Added indication that 919883 affects src:dirgra > affects 919895 src:jnr-posix Bug #919895 [openjdk-11-jdk-headless] openjdk-11-jdk-headless: Regression: Breaks a bunch of packages using javadoc Bug #919798 [openjdk-11-jdk-headless] antlr4: FTBFS (Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar) Bug #919800 [openjdk-11-jdk-headless] jackson-databind: FTBFS (Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar) Bug #919801 [openjdk-11-jdk-headless] libgoogle-gson-java: FTBFS (Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar) Bug #919874 [openjdk-11-jdk-headless] bsaf: FTBFS (Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar) Bug #919875 [openjdk-11-jdk-headless] commons-csv: FTBFS (Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar= Bug #919876 [openjdk-11-jdk-headless] java-string-similarity: FTBFS (Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar) Bug #919878 [openjdk-11-jdk-headless] servlet-api: FTBFS (Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar) Bug #919883 [openjdk-11-jdk-headless] libreoffice arch all FTBFS, javadoc: error - The code being documented uses modules but the packages defined in http://java.sun.com/j2se/1.5/docs/api/ are in the unnamed module. Added indication that 919895 affects src:jnr-posix Added indication that 919798 affects src:jnr-posix Added indication that 919800 affects src:jnr-posix Added indication that 919801 affects src:jnr-posix Added indication that 919874 affects src:jnr-posix Added indication that 919875 affects src:jnr-posix Added indication that 919876 affects src:jnr-posix Added indication that 919878 affects src:jnr-posix Added indication that 919883 affects src:jnr-posix > affects 919895 src:libparanamer-java Bug #919895 [openjdk-11-jdk-headless] openjdk-11-jdk-headless: Regression: Breaks a bunch of packages using javadoc Bug #919798 [openjdk-11-jdk-headless] antlr4: FTBFS (Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar) Bug #919800 [openjdk-11-jdk-headless] jackson-databind: FTBFS (Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar) Bug #919801 [openjdk-11-jdk-headless] libgoogle-gson-java: FTBFS (Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar) Bug #919874 [openjdk-11-jdk-headless] bsaf: FTBFS (Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar) Bug #919875 [openjdk-11-jdk-headless] commons-csv: FTBFS (Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar= Bug #919876 [openjdk-11-jdk-headless] java-string-similarity: FTBFS (Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar) Bug #919878 [openjdk-11-jdk-headless] servlet-api: FTBFS (Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar) Bug #919883 [openjdk-11-jdk-headless] libreoffice arch all FTBFS, javadoc: error - The code being documented uses modules but the packages defined in http://java.sun.com/j2se/1.5/docs/api/ are in the unnamed module.
Processed: Lmms fix uploaded
Processing commands for cont...@bugs.debian.org: > tag 891756 + pending Bug #891756 [lmms] lmms: demote Dependency on "calf-ladspa" to "Recommends" Added tag(s) pending. > tag 897806 + pending Bug #897806 [src:lmms] lmms: ftbfs with GCC-8 Added tag(s) pending. > tag 918242 + pending Bug #918242 [src:lmms] ITS: lmms Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 891756: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891756 897806: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897806 918242: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918242 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#897806: Lmms fix uploaded
tag 891756 + pending tag 897806 + pending tag 918242 + pending thanks I have uploaded a fix. It is unfortunately waiting for my new signing sub-key to be rolled into the Debian Keyring. Regards, Ross signature.asc Description: OpenPGP digital signature
Bug#919857: marked as done (klibc crashes on hppa)
Your message dated Sun, 20 Jan 2019 23:05:43 + with message-id and subject line Bug#919855: fixed in klibc 2.0.5-2 has caused the Debian Bug report #919855, regarding klibc crashes on hppa 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.) -- 919855: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919855 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: klibc Version: 2.0.5-1 Severity: critical The new klibc package (2.0.5-1) leads to crashes and an unbootable system. Version 2.0.4-15 was working ok. Output is as shown below. I haven't had time yet to analyze what exactly is wrong in the new version. Any idea what to test or where to look would be good. Helge Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... done. [ 58.612345] 117 (fstype): Uhuuh, elf segment at 0001 requested but the memory is mapped already Segmentation fault [ 58.746281] 121 (fstype): Uhuuh, elf segment at 0001 requested but the memory is mapped already Segmentation fault [ 58.799789] 124 (fstype): Uhuuh, elf segment at 0001 requested but the memory is mapped already Segmentation fault Begin: Will now check root file system ... fsck from util-linux 2.33.1 [/sbin/fsck.ext4 (1) -- /dev/sdb3] fsck.ext4 -a -C0 /dev/sdb3 ROOT300: clean, 139523/17039360 files, 15570025/68157440 blocks done. [ 59.841124] EXT4-fs (sdb3): mounted filesystem with ordered data mode. Opts: (null) done. Begin: Running /scripts/local-bottom ... done. Begin: Running /scripts/init-bottom ... [ 60.171403] 138 (nuke): Uhuuh, elf segment at 0001 requested but the memory is mapped already Segmentation fault done. [ 60.228447] 140 (run-init): Uhuuh, elf segment at 0001 requested but the memory is mapped already Segmentation fault Target filesystem doesn't have requested /sbin/init. [ 60.243239] 141 (run-init): Uhuuh, elf segment at 0001 requested but the memory is mapped already Segmentation fault [ 60.257792] 142 (run-init): Uhuuh, elf segment at 0001 requested but the memory is mapped already Segmentation fault [ 60.272482] 143 (run-init): Uhuuh, elf segment at 0001 requested but the memory is mapped already Segmentation fault [ 60.287150] 144 (run-init): Uhuuh, elf segment at 0001 requested but the memory is mapped already Segmentation fault [ 60.301670] 145 (run-init): Uhuuh, elf segment at 0001 requested but the memory is mapped already Segmentation fault chvt: can't open console --- End Message --- --- Begin Message --- Source: klibc Source-Version: 2.0.5-2 We believe that the bug you reported is fixed in the latest version of klibc, 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 919...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ben Hutchings (supplier of updated klibc package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 20 Jan 2019 22:49:25 + Source: klibc Binary: libklibc-dev libklibc klibc-utils Architecture: source Version: 2.0.5-2 Distribution: unstable Urgency: medium Maintainer: maximilian attems Changed-By: Ben Hutchings Description: klibc-utils - small utilities built with klibc for early boot libklibc - minimal libc subset for use with initramfs libklibc-dev - kernel headers used during the build of klibc Closes: 919855 Changes: klibc (2.0.5-2) unstable; urgency=medium . * Drop redundant patch "Include the multiarch include directory in klcc's path" * Drop "Fix klibc Debian specific build trouble" and introduce links in debian/rules * Fix up debug symbol support: - Use -Ttext-segment to link shared library on all arches (Closes: #919855) - Drop "kbuild: Enable build IDs" - Kbuild: Add option to install unstripped binaries - Kbuild: Enable full debug information - Set CONFIG_DEBUG_INFO instead of overriding
Bug#919855: marked as done (s390x executables crash)
Your message dated Sun, 20 Jan 2019 23:05:43 + with message-id and subject line Bug#919855: fixed in klibc 2.0.5-2 has caused the Debian Bug report #919855, regarding s390x executables crash 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.) -- 919855: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919855 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: klibc Version: 2.0.5-1 Severity: serious While investigating some test failures on klibc upstream, I found that the new Debian version crashes on s390x. It looks like this is due to an address collision between the build ID in the shared library and the code in the executables. The addition of build IDs is not (yet) part of an upstream release. Ben. -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Source: klibc Source-Version: 2.0.5-2 We believe that the bug you reported is fixed in the latest version of klibc, 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 919...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ben Hutchings (supplier of updated klibc package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 20 Jan 2019 22:49:25 + Source: klibc Binary: libklibc-dev libklibc klibc-utils Architecture: source Version: 2.0.5-2 Distribution: unstable Urgency: medium Maintainer: maximilian attems Changed-By: Ben Hutchings Description: klibc-utils - small utilities built with klibc for early boot libklibc - minimal libc subset for use with initramfs libklibc-dev - kernel headers used during the build of klibc Closes: 919855 Changes: klibc (2.0.5-2) unstable; urgency=medium . * Drop redundant patch "Include the multiarch include directory in klcc's path" * Drop "Fix klibc Debian specific build trouble" and introduce links in debian/rules * Fix up debug symbol support: - Use -Ttext-segment to link shared library on all arches (Closes: #919855) - Drop "kbuild: Enable build IDs" - Kbuild: Add option to install unstripped binaries - Kbuild: Enable full debug information - Set CONFIG_DEBUG_INFO instead of overriding STRIP Checksums-Sha1: e04129f6bc10cd88947737b20d87e717dfcf 2036 klibc_2.0.5-2.dsc 986fcbc312bf4a5b90e21c31ede7e4349ac5f4cc 21452 klibc_2.0.5-2.debian.tar.xz e6549740baee74fc4383afa7bbab695620e55cc8 6049 klibc_2.0.5-2_source.buildinfo Checksums-Sha256: 6397f5c5ee42a6cfa62e9ad5e64c0e16cf3f01853588ab26539c247837be2313 2036 klibc_2.0.5-2.dsc 69439f71169124f14a4c5073d45be1a5061c4aa76d41661ffbfb7eab146263fa 21452 klibc_2.0.5-2.debian.tar.xz ceae138a5a020a07191b5eca9bf792846196aebd7096dd21f8f875e181dc985f 6049 klibc_2.0.5-2_source.buildinfo Files: 4597821877d31c2fc3e4a0b024340c24 2036 libs optional klibc_2.0.5-2.dsc b3df9b9fb478cbc7339aa4ed8655eedc 21452 libs optional klibc_2.0.5-2.debian.tar.xz 05aecf98afecaa715e0328d9466885dc 6049 libs optional klibc_2.0.5-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEErCspvTSmr92z9o8157/I7JWGEQkFAlxE/IcACgkQ57/I7JWG EQkS9g//TsaqQqmiPdDanhUKBrv/3maEqAWscXf3m+1LjMN0kVrgU6N4/QpNXJaO ptsHhqZx+f/Jo5e9cJV4vFdneF28PfqE2dwOFHfISnalREJ/INWgDEac2mraMT+W Fyokrsq3JOrJnfSwM5h4isiu4SMb6+t8iVoZo76GJFKTxaY2iHMbGqvaGZP1tXqk VcfHxGeObZQ2o1n+MzObNjOoEdd0f3IOJ+iVmHog4FxMjsFbLDYCWHYmndDne2N+ rxfvD6sxagC65mzcCP/cNARDX/0l/8IAEmarsuQTJ6rZziggtFYXoBuSpOHYAecF /t3M3ki3P1CE8zn8GHCrmhyACw7bN/Q4rABCaLhqltC+An0iq2OfzGNkyx+hW0eG DK+FvkkzLCDGVk1A/kGuHrHq8NZH+AJRLgsmu0KVeeF3HYazrC/S+lrj0l+PgB+q izBVoiXb7bOnFV1LuUN1OdYY9ZX3LL+NQqkfd4CBzue+FrYO2/SzAfOagKlYJyg8 J9gX7S1SKx1YChaQ3tPJ1puWi1vNzCPE6gk5tVAYqcVUsvhVKsWamNd7uNIf2oLu
Processed: reassign 919857 to src:klibc, forcibly merging 919855 919857
Processing commands for cont...@bugs.debian.org: > reassign 919857 src:klibc Bug #919857 [klibc] klibc crashes on hppa Bug reassigned from package 'klibc' to 'src:klibc'. No longer marked as found in versions 2.0.5-1. Ignoring request to alter fixed versions of bug #919857 to the same values previously set > forcemerge 919855 919857 Bug #919855 [src:klibc] s390x executables crash Bug #919857 [src:klibc] klibc crashes on hppa Severity set to 'grave' from 'important' Marked as found in versions klibc/2.0.5-1. Merged 919855 919857 > thanks Stopping processing here. Please contact me if you need assistance. -- 919855: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919855 919857: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919857 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 1 error): Re: Bug#919857: 2.0.5-1 crashes
Processing control commands: > forcemerge 919855 919857 Bug #919855 [src:klibc] s390x executables crash Unable to merge bugs because: package of #919857 is 'klibc' not 'src:klibc' Failed to forcibly merge 919855: Did not alter merged bugs. -- 919855: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919855 919857: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919857 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#919855: Bug#919857: 2.0.5-1 crashes
Control: forcemerge 919855 919857 On Sun, Jan 20, 2019 at 02:22:38PM +, Thorsten Glaser wrote: > Ben Hutchings dixit: > > >the new Debian version crashes on s390x. It looks like this is due to > >an address collision between the build ID in the shared library and > >the code in the executables. > > > Helge Deller dixit: > > >[ 58.612345] 117 (fstype): Uhuuh, elf segment at 0001 > >requested but the memory is mapped already > > > Are these two maybe related? Pretty sure it's the same, given we have it on sparc64 too: > [9.765691] 426 (fstype): Uhuuh, elf segment at 0010 requested > but the memory is mapped already > Segmentation fault > [9.777174] aes_sparc64: sparc64 aes opcodes not available. (second line included to convince you I haven't just copied the error :P) James
Processed (with 1 error): Re: Bug#919857: 2.0.5-1 crashes
Processing control commands: > forcemerge 919855 919857 Bug #919855 [src:klibc] s390x executables crash Unable to merge bugs because: package of #919857 is 'klibc' not 'src:klibc' Failed to forcibly merge 919855: Did not alter merged bugs. -- 919855: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919855 919857: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919857 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#919827: marked as done (asterisk-espeak: FTBFS (Externally compiled modules must declare AST_MODULE_SELF_SYM))
Your message dated Sun, 20 Jan 2019 22:49:14 + with message-id and subject line Bug#919827: fixed in asterisk-espeak 5.0~1-2 has caused the Debian Bug report #919827, regarding asterisk-espeak: FTBFS (Externally compiled modules must declare AST_MODULE_SELF_SYM) 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.) -- 919827: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919827 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:asterisk-espeak Version: 5.0~1-1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules binary-arch test -x debian/rules dh_testroot dh_prep dh_installdirs -A mkdir -p "." /usr/bin/make -C . CFLAGS="-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -pipe -fPIC -Wall -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -D_REENTRANT -D_GNU_SOURCE" CXXFLAGS="-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security" CPPFLAGS="-Wdate-time -D_FORTIFY_SOURCE=2" LDFLAGS="-Wl,-z,relro" make[1]: Entering directory '/<>' gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -pipe -fPIC -Wall -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -D_REENTRANT -D_GNU_SOURCE -g -O2 -c -o app_espeak.o app_espeak.c In file included from app_espeak.c:34: /usr/include/asterisk.h:232:2: error: #error "Externally compiled modules must declare AST_MODULE_SELF_SYM." #error "Externally compiled modules must declare AST_MODULE_SELF_SYM." ^ In file included from app_espeak.c:43: app_espeak.c: In function 'load_module': app_espeak.c:414:9: error: 'AST_MODULE_SELF' undeclared (first use in this function); did you mean 'AST_MODULE_INFO'? return ast_register_application(app, espeak_exec, synopsis, descrip) ? ^~~~ app_espeak.c:414:9: note: each undeclared identifier is reported only once for each function it appears in app_espeak.c:416:1: warning: control reaches end of non-void function [-Wreturn-type] } ^ make[1]: *** [Makefile:36: app_espeak.o] Error 1 make[1]: Leaving directory '/<>' make: *** [/usr/share/cdbs/1/class/makefile.mk:77: debian/stamp-makefile-build] Error 2 dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit status 2 (The above is just how the build ends and not necessarily the most relevant part) The build was made in my autobuilder with "dpkg-buildpackage -B" and it also fails here: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/asterisk-espeak.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: asterisk-espeak Source-Version: 5.0~1-2 We believe that the bug you reported is fixed in the latest version of asterisk-espeak, 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 919...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bernhard Schmidt (supplier of updated asterisk-espeak package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 20 Jan 2019 23:24:04 +0100 Source: asterisk-espeak Binary: asterisk-espeak Architecture: source Version: 5.0~1-2 Distribution: unstable Urgency: medium Maintainer: Debian VoIP Team Changed-By: Bernhard Schmidt Description: asterisk-espeak - eSpeak module for Asterisk Closes: 919827 Changes: asterisk-espeak (5.0~1-2) unstable; urgency=medium . * Team upload . [ Jonas Smedegaard ] * Update copyright info: Fix source URLs. . [ Bernhard Schmidt ] * Readd AST_MODULE_SELF_SYM upstream CFLAG (Closes: #919827) Checksums-Sha1: 04f0f6bfd65eafc41d4a6d8f08e005c5d2b5d78d 2078 asterisk-espeak_5.0~1-2.dsc 80d759e87a5d8ffd48788c8e0812cdcbc6c1073d 5512
Bug#919738: marked as done (asterisk-flite: FTBFS (Externally compiled modules must declare AST_MODULE_SELF_SYM))
Your message dated Sun, 20 Jan 2019 22:34:25 + with message-id and subject line Bug#919738: fixed in asterisk-flite 3.0-3 has caused the Debian Bug report #919738, regarding asterisk-flite: FTBFS (Externally compiled modules must declare AST_MODULE_SELF_SYM) 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.) -- 919738: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919738 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:asterisk-flite Version: 3.0-2 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules binary-arch test -x debian/rules dh_testroot dh_prep dh_installdirs -A mkdir -p "." /usr/bin/make -C . CFLAGS="-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -pipe -fPIC -Wall -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -D_REENTRANT -D_GNU_SOURCE" CXXFLAGS="-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security" CPPFLAGS="-Wdate-time -D_FORTIFY_SOURCE=2" LDFLAGS="-Wl,-z,relro" make[1]: Entering directory '/<>' awk: cannot open /etc/asterisk/asterisk.conf (No such file or directory) gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -pipe -fPIC -Wall -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -D_REENTRANT -D_GNU_SOURCE -g -O2 -c -o app_flite.o app_flite.c In file included from app_flite.c:34: /usr/include/asterisk.h:232:2: error: #error "Externally compiled modules must declare AST_MODULE_SELF_SYM." #error "Externally compiled modules must declare AST_MODULE_SELF_SYM." ^ In file included from app_flite.c:43: app_flite.c: In function 'load_module': app_flite.c:283:9: error: 'AST_MODULE_SELF' undeclared (first use in this function); did you mean 'AST_MODULE_INFO'? return ast_register_application(app, flite_exec, synopsis, descrip) ? ^~~~ app_flite.c:283:9: note: each undeclared identifier is reported only once for each function it appears in app_flite.c:285:1: warning: control reaches end of non-void function [-Wreturn-type] } ^ make[1]: *** [Makefile:36: app_flite.o] Error 1 make[1]: Leaving directory '/<>' make: *** [/usr/share/cdbs/1/class/makefile.mk:77: debian/stamp-makefile-build] Error 2 dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit status 2 The build was made in my autobuilder with "dpkg-buildpackage -B" and it also fails here: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/asterisk-flite.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: asterisk-flite Source-Version: 3.0-3 We believe that the bug you reported is fixed in the latest version of asterisk-flite, 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 919...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bernhard Schmidt (supplier of updated asterisk-flite package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 20 Jan 2019 23:03:43 +0100 Source: asterisk-flite Binary: asterisk-flite Architecture: source Version: 3.0-3 Distribution: unstable Urgency: medium Maintainer: Debian VoIP Team Changed-By: Bernhard Schmidt Description: asterisk-flite - flite module for Asterisk Closes: 919738 Changes: asterisk-flite (3.0-3) unstable; urgency=medium . * Team upload . [ Jonas Smedegaard ] * Update copyright info: Fix source URLs. . [ Bernhard Schmidt ] * Add missing upstream CFLAG (Closes: #919738) Checksums-Sha1: 57a358c9f8f1cb787dbf1a27382fbd9fdaea0e4d 2016 asterisk-flite_3.0-3.dsc 3bff95aa405aed904b6f477fb276f87a28453a63 5312 asterisk-flite_3.0-3.debian.tar.xz
Bug#915997: marked as done (unyaffs FTBFS with glibc 2.28)
Your message dated Sun, 20 Jan 2019 22:36:18 + with message-id and subject line Bug#915997: fixed in unyaffs 0.9.7-0.1 has caused the Debian Bug report #915997, regarding unyaffs FTBFS with glibc 2.28 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.) -- 915997: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915997 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: unyaffs Version: 0.9.6-1 Severity: serious Tags: ftbfs buster sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/unyaffs.html ... make V=1 -j1 make[2]: Entering directory '/build/1st/unyaffs-0.9.6' cc -D_FORTIFY_SOURCE=2 -O2 -Wall -Wl,-z,relro unyaffs.c -o unyaffs unyaffs.c: In function 'prt_node': unyaffs.c:360:15: warning: implicit declaration of function 'major' [-Wimplicit-function-declaration] major(oh->yst_rdev), ^ unyaffs.c:361:15: warning: implicit declaration of function 'minor'; did you mean 'mknod'? [-Wimplicit-function-declaration] minor(oh->yst_rdev)); ^ mknod /usr/bin/ld: /tmp/ccmn6g0d.o: in function `process_chunk': unyaffs.c:(.text+0x12cf): undefined reference to `minor' /usr/bin/ld: unyaffs.c:(.text+0x12e1): undefined reference to `major' /usr/bin/ld: unyaffs.c:(.text+0x1330): undefined reference to `minor' /usr/bin/ld: unyaffs.c:(.text+0x1342): undefined reference to `major' collect2: error: ld returned 1 exit status make[2]: *** [Makefile:4: unyaffs] Error 1 --- End Message --- --- Begin Message --- Source: unyaffs Source-Version: 0.9.7-0.1 We believe that the bug you reported is fixed in the latest version of unyaffs, 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 915...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Adrian Bunk (supplier of updated unyaffs 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, 06 Jan 2019 23:30:37 +0200 Source: unyaffs Binary: unyaffs Architecture: source Version: 0.9.7-0.1 Distribution: unstable Urgency: medium Maintainer: Matthew Fischer Changed-By: Adrian Bunk Description: unyaffs- Extracts files from a YAFFS2 filesystem image Closes: 805593 915997 916117 Changes: unyaffs (0.9.7-0.1) unstable; urgency=medium . * Non-maintainer upload. * New upstream release. - Fixes FTBFS with glibc 2.28. (Closes: #915997) * Build with default CFLAGS for non-empty -dbgsym. * Use the upstream manpage. (Closes: #805593) * Remove incorrect Vcs-Git and Vcs-Browser fields. (Closes: #916117) * Priority: extra -> optional Checksums-Sha1: 48f495469a329d80d2a8fe9c29968bb08ad5450a 1717 unyaffs_0.9.7-0.1.dsc 8c12965639f21693f51e3d959a637f9a9b605c5b 15795 unyaffs_0.9.7.orig.tar.gz f54fd2214734a5c85b5615f28b8ec7bec159f1ee 1692 unyaffs_0.9.7-0.1.debian.tar.xz Checksums-Sha256: 85947184b844a1fb738e65d170579fd55961e96c47079155e98a0b0ad687592c 1717 unyaffs_0.9.7-0.1.dsc 099ee9e51046b83fe8555d7a6284f6fe4fbae96be91404f770443d8129bd8775 15795 unyaffs_0.9.7.orig.tar.gz d30e33723d44e67dd91d40c124680b5da9c842e8e3f18dda4541f83b511502db 1692 unyaffs_0.9.7-0.1.debian.tar.xz Files: 329b8ff7badbcbcc69510b7b143e 1717 devel optional unyaffs_0.9.7-0.1.dsc 87fe594d2bc95b73e198d385c87c7b0c 15795 devel optional unyaffs_0.9.7.orig.tar.gz e5383e5646f3b4ed87a0fb219fa559bb 1692 devel optional unyaffs_0.9.7-0.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAlwydgkACgkQiNJCh6LY mLGtRxAAluGl+S9X9gYMm/cAg91w8aPLkG9iygaMZ9adXFKWtSU9GZQ5M2HWxU8D ykX4vgmJivitH/VbE9ugYJW8FrCbl1SPJfiAOhWtmTg1nrl1Y3ivXb8U+or/33lh H+NvkPFbmPQz0iyBXQOzruuWqNl44xuQsJEKrIVIzwpkeQev2o9vEozWujrgluRy 3jKtX2iDXdHqw7mvALTpDWNVWHX62zoKr4Jg0TAq1vgWuOaBP/NQqO3ZjT0O7ZbJ pTv2XmXucULpTh1g3lmnyPll/Ok9sRv8+oeg3Ursknu31HSMZXvCiRTUJc/WQ4S4 v/vBtIrRsHX5VRxvoOQVL2srqklE1SnGAEjTcU1ucR1m0Fw5RUe+FxF9DF4Qnmbe v6yDzeEtSIEmD+Cf+mWWjpx+DB8At/4kKK/GSeoVxbcj1zME8xa5nZA1JKaXCzMt OCpF5R3eHIlcmW8cewrBlm4kUVxGPddWtMc7tTbArEkkl5bd02rn23skUfBzI15N Sq13MVZtqxP1A69lnkmK4rdZF4+L9kj41kmFDwuCmN8+VsBNJFV30gY3+hKLQ9Qq XG3f3GZDSapD3lDNvdpgQqjuljfqoGT8pKotSux7zLPa269rUgBOkQDaD8mZhMBN
Processed: bug 919828 is forwarded to https://github.com/traud/asterisk-opus/issues/15
Processing commands for cont...@bugs.debian.org: > forwarded 919828 https://github.com/traud/asterisk-opus/issues/15 Bug #919828 [src:asterisk-opus] asterisk-opus: FTBFS (Externally compiled modules must declare AST_MODULE_SELF_SYM) Set Bug forwarded-to-address to 'https://github.com/traud/asterisk-opus/issues/15'. > thanks Stopping processing here. Please contact me if you need assistance. -- 919828: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919828 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: not ftbfs anymore since 1.2.0-1 (test disable)
Processing control commands: > tag -1 -ftbfs Bug #912249 [src:ruby-file-tail] ruby-file-tail FTBFS: test_tail_change2(FileTailTest) fails Removed tag(s) ftbfs. > retitle -1 test_tail_change2(FileTailTest) fails Bug #912249 [src:ruby-file-tail] ruby-file-tail FTBFS: test_tail_change2(FileTailTest) fails Changed Bug title to 'test_tail_change2(FileTailTest) fails' from 'ruby-file-tail FTBFS: test_tail_change2(FileTailTest) fails'. > severity -1 normal Bug #912249 [src:ruby-file-tail] test_tail_change2(FileTailTest) fails Severity set to 'normal' from 'serious' -- 912249: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912249 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#912249: not ftbfs anymore since 1.2.0-1 (test disable)
Control: tag -1 -ftbfs Control: retitle -1 test_tail_change2(FileTailTest) fails Control: severity -1 normal Hi, This test is now disabled in the test suite (build and autopkgtest). I am therefore downgrading the severity of the bug and removing the ftbfs tag, but leave the bug open, waiting for a true fix. Cheers, Cédric signature.asc Description: PGP signature
Bug#916468: Conflict over /usr/bin/dune
Paul Gevers writes ("Re: Conflict over /usr/bin/dune"):
> For all those that haven't followed along in the bug report, the bug got
> reassigned to whitedune. I'm not sure if I agree with the reassignment,
> but an NMU by me is hanging in DELAYED/7 to fix the conflict in
> whitedune. If people object, I'll delay it more to discuss.
I see that, apparently, this was done by NMUing whitedune to remove
the symlink and using Conflicts/Replaces in ocaml dune so that it can
still provide /usr/bin/dune.
I think that is completely opposite to the consensus in this thread
and also opposite to Debian policy.
Under the circumstances I felt I wouldn't be listened to if I simply
petitioned the maintainers of what is now src:dune again, so I have
escalated this to the TC. See #919951.
Ian.
--
Ian JacksonThese opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.
Processed: /usrr/bin/dune and `dune' binary package should refer to dune-common
Processing control commands: > block -1 by 919951 Bug #919953 [dune] /usrr/bin/dune and `dune' binary package should refer to dune-common 919953 was not blocked by any bugs. 919953 was not blocking any bugs. Added blocking bug(s) of 919953: 919951 -- 919953: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919953 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#919953: /usrr/bin/dune and `dune' binary package should refer to dune-common
Package: dune Version: 1.6.2-2 Severity: serious Control: block -1 by 919951 According to Debian policy file conflicts should be resolved by no-one using the conflicting name. This applies to /usr/bin/dune. Additionally, the only referent of `dune' that anyone has heard of (eg, wikipedia) is a C++ library which we have in Debian as `src:dune-commmon', `libdune*-dev', etc. It is evident from actions taken in response to #916468 that the you (the maintainers of what is current `src:dune') do not agree. Instead, it seems to me that you ahead and took the name despite a fairly clear consensus in debian-devel that you shouldn't. I don't think you should have done that. I am escalating this to the Technical Commitee in another bug. In the meantime this bug needs to be open to keep this out of testing. Sorry, Ian. -- Ian JacksonThese opinions are my own. If I emailed you from an address @fyvzl.net or @evade.org.uk, that is a private address which bypasses my fierce spamfilter.
Bug#916702: freezegun FTBFS: test failures
Package: src:freezegun Followup-For: Bug #916702 I locally created a version based on the more recent 0.3.11 upstream version, with the same Debian files (plus an extra changelog entry, of course), and ``dpkg-buildpackage -A`` seemed to successfully build, pass the tests and package everything. So probably using the latest upstream would fix the issue. Thanks! -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: arm64, armhf, i386 Kernel: Linux 4.19.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=ca_ES.UTF-8, LC_CTYPE=ca_ES.UTF-8 (charmap=UTF-8), LANGUAGE=ca:es (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#919375: marked as done (monitoring-plugins: FTBFS with mariadb-10.3: check_mysql.c:61:24: error: 'MYSQL_PORT' undeclared)
Your message dated Sun, 20 Jan 2019 21:37:20 + with message-id and subject line Bug#919375: fixed in monitoring-plugins 2.2-5 has caused the Debian Bug report #919375, regarding monitoring-plugins: FTBFS with mariadb-10.3: check_mysql.c:61:24: error: 'MYSQL_PORT' undeclared 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.) -- 919375: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919375 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: monitoring-plugins Version: 2.2-4 Severity: serious Justification: fails to build from source (but built successfully in the past) Hi, monitoring-plugins FTBFS with mariadb-10.3 in sid: i686-linux-gnu-gcc -DLOCALEDIR=\"/usr/share/locale\" -DHAVE_CONFIG_H -I. -I.. -I.. -I../lib -I../gl -I../intl -I/usr/include/ldap -I/usr/include/postgresql -I/usr/include -I/usr/include/mariadb -I/usr/include/ma riadb/mysql -Wdate-time -D_FORTIFY_SOURCE=2 -DNP_VERSION='"2.2"' -I/usr/include/mariadb -I/usr/include/mariadb/mysql -g -O2 -fdebug-prefix-map=/build/monitoring-plugins-2.2=. -fstack-protector-strong -Wformat -We rror=format-security -Wall -Wl,-z,now -MT check_mysql-check_mysql.o -MD -MP -MF .deps/check_mysql-check_mysql.Tpo -c -o check_mysql-check_mysql.o `test -f 'check_mysql.c' || echo './'`check_mysql.c check_mysql.c:61:24: error: 'MYSQL_PORT' undeclared here (not in a function); did you mean 'MYSQL_STMT'? unsigned int db_port = MYSQL_PORT; ^~ MYSQL_STMT make[3]: *** [Makefile:1869: check_mysql-check_mysql.o] Error 1 Cheers, Andreas monitoring-plugins_2.2-4.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: monitoring-plugins Source-Version: 2.2-5 We believe that the bug you reported is fixed in the latest version of monitoring-plugins, 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 919...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jan Wagner (supplier of updated monitoring-plugins package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 20 Jan 2019 19:40:25 +0100 Source: monitoring-plugins Binary: monitoring-plugins monitoring-plugins-common monitoring-plugins-basic monitoring-plugins-standard Architecture: source i386 all Version: 2.2-5 Distribution: unstable Urgency: medium Maintainer: Debian Nagios Maintainer Group Changed-By: Jan Wagner Description: monitoring-plugins - Plugins for nagios compatible monitoring systems (metapackage) monitoring-plugins-basic - Plugins for nagios compatible monitoring systems (basic) monitoring-plugins-common - Common files for plugins for nagios compatible monitoring monitoring-plugins-standard - Plugins for nagios compatible monitoring systems (standard) Closes: 879084 905318 907484 914092 919375 Changes: monitoring-plugins (2.2-5) unstable; urgency=medium . [ Bas Couwenberg ] * [890cd8c] Bump Standards-Version to 4.1.5, no changes. * [59073f6] Bump Standards-Version to 4.2.0, no changes. * [e07a06c] Bump Standards-Version to 4.2.1, no changes. . [ Jan Wagner ] * [40b9004] travis-ci: Use xenial image * [56443b1] d/control: Add Provides for 'old' nagios-plugins . [ Bas Couwenberg ] * [c70710f] Apply path by Andreas Henriksson to fix usrmerge issue. (closes: #914092) * [377eec3] Bump Standards-Version to 4.3.0, no changes. . [ Jan Wagner ] * [73f2273] Add d/p/14_mariad to fix FTBFS with MariaDB 10.3. (Closes: #919375) * [4f75b28] Add d/p/15_check_smtp_initialize to fix check_smtp with custom commands and SSL * [61315ee] d/rules: Configure with sudo (Closes: 905318) * [d8a134e] d/control: Add sudo to Recommends * [1fe1cd2] Symlink /usr/lib/nagios/plugins/utils.* to /usr/lib/icinga/ (Closes: #879084, #907484) Checksums-Sha1: e5a69a2b76194fd88bc371998bd25b314e782d86 2535 monitoring-plugins_2.2-5.dsc 782ee59ed5be6136337cce32f48875fe8efba118 1590008 monitoring-plugins_2.2.orig.tar.gz a3b50468d81d3c6855b85228be6b13d6a4cb9f3b 41624 monitoring-plugins_2.2-5.debian.tar.xz 984b79f340729caac4aec2e9ff803c1bd1928b3e 1590168
Processed: mark 891297 as patched
Processing commands for cont...@bugs.debian.org: > tag 891297 patch Bug #891297 [src:gnome-keyring] gnome-keyring: Incomplete debian/copyright? Ignoring request to alter tags of bug #891297 to the same tags previously set > End of message, stopping processing here. Please contact me if you need assistance. -- 891297: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891297 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: mark 891297 as patched
Processing commands for cont...@bugs.debian.org: > tag 891297 patch Bug #891297 [src:gnome-keyring] gnome-keyring: Incomplete debian/copyright? Added tag(s) patch. > End of message, stopping processing here. Please contact me if you need assistance. -- 891297: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891297 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#917055: marked as done (blktool FTBFS with glibc 2.28)
Your message dated Sun, 20 Jan 2019 21:35:16 +
with message-id
and subject line Bug#917055: fixed in blktool 4-7.1
has caused the Debian Bug report #917055,
regarding blktool FTBFS with glibc 2.28
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.)
--
917055: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917055
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: blktool
Version: 4-7
Severity: serious
Tags: ftbfs buster sid
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/blktool.html
...
blktool.c: In function 'detect_dev_class':
blktool.c:295:10: warning: implicit declaration of function 'major'
[-Wimplicit-function-declaration]
switch (major(st_rdev)) {
^
...
gcc -Wall -g -O2 -ffile-prefix-map=/build/1st/blktool-4=.
-fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro -o
blktool blktool.o ata.o scsi.o util.o -lglib-2.0
/usr/bin/ld: blktool.o: in function `detect_dev_class':
./blktool.c:295: undefined reference to `major'
collect2: error: ld returned 1 exit status
make[2]: *** [Makefile:254: blktool] Error 1
--- End Message ---
--- Begin Message ---
Source: blktool
Source-Version: 4-7.1
We believe that the bug you reported is fixed in the latest version of
blktool, 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 917...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Adrian Bunk (supplier of updated blktool package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 11 Jan 2019 20:35:44 +0200
Source: blktool
Binary: blktool
Architecture: source
Version: 4-7.1
Distribution: unstable
Urgency: medium
Maintainer: Azat Khuzhin
Changed-By: Adrian Bunk
Description:
blktool- tune low-level block device parameters
Closes: 636500 917055
Changes:
blktool (4-7.1) unstable; urgency=medium
.
* Non-maintainer upload.
* Fix FTBFS with glibc 2.28. (Closes: #917055)
* Package description improvement from Aputsiaq Janussen.
(Closes: #636500)
Checksums-Sha1:
f67104a68d8cdeb41cde6f9435b086ccbae8d270 1846 blktool_4-7.1.dsc
f519a6e4357a84ba0681fb7bcd95fc73e86d4255 4288 blktool_4-7.1.debian.tar.xz
Checksums-Sha256:
2245298ee795cbe7bb708f19d5b9227aed7c80ade5594cccf37727667e4f6d54 1846
blktool_4-7.1.dsc
b7ea643b5b4ca6e660581a21eeced40bb39755d0f363af348209391caa6d3ebc 4288
blktool_4-7.1.debian.tar.xz
Files:
9d43267adc7b12843f1ea2db1ea66d43 1846 admin optional blktool_4-7.1.dsc
6d9f1d436bfa225910ed215e322d9da7 4288 admin optional
blktool_4-7.1.debian.tar.xz
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAlw441gACgkQiNJCh6LY
mLFcXhAAm08CXnzAW2ZsQw5jo8qRS30GIyZYqmY+tTL3IKScrfBffK6oVFWt6aPL
kuXQsXwn8JFM4oew2FmVIr5w1FrJI7rjN9gxxBQ3XMYL2lBN63QL6nLlAYgtYOvV
dt9mjR51Q1+az1o8y3orW4482V69XBvTHS1wFU+DQtRb2pT5lRufBv57xCbbAtCW
0zo1TTDJHjk2Vg0axoa1e9JV/qg4w/BLTtcQt/VgWHuNIyBqSCE+yuMiosIdGiw9
FQyHFGzSGxkQnYuNvoEKvMZE+QUv/+o+Bp9qQ3y3fTkMRLn6cCZcbqJoCTjfRjqf
ojrUheZ5durOMpe5FQgbopj9dI6K/IrhAIX439wMmLU6mJq+ZDa/vTHTJCK0DfYS
YDlQ/orysomTw9aEls7Bio7hNCjFYiowmg3lLEJpe2mDhqDXJmrd13OlHal/T2cu
vdVWmDnlYF1IquRywOWqFFrlvRFXiYs1JUHxvT0bKbkmvbeMKVRr2b1WZXak7VM0
TYKlKnxrmVv8GjjfJdV7Yoq4U47aABkkEhNYr4+fxlbMMrALdLxgXCUkSBjnaQjC
QzD3pUTY6eR4IO4EHe+QFnuqc/KkrA/6zw6Ufhtd2z0mbze/pWZAyoUU36INuZZp
+HHAaXLNhfujZKYcNdjdofx9vlpy72EK9p0IOP3KO57UMrx1T+k=
=yle0
-END PGP SIGNATURE End Message ---
Bug#891297: gnome-keyring: Incomplete debian/copyright?
Hello from the Montreal BSP! I created a Merge Request on Salsa to fix this bug [1]. If there is a problem with that patch, don't hesitate to ping me and I'll be glad to fix it. Cheers! [1] https://salsa.debian.org/gnome-team/gnome-keyring/merge_requests/1 -- ,''`. : :' : Louis-Philippe Véronneau `. `'` po...@debian.org / veronneau.org `- signature.asc Description: OpenPGP digital signature
Processed: Re: Bug#919915: grub2-common: fails to upgrade from 'stretch-backports' - trying to overwrite /etc/kernel/postinst.d/zz-update-grub from grub-cloud-amd64 0.0.4~bpo9+1
Processing control commands: > notfound -1 0.4.4~bpo9+1 Bug #919915 [grub-cloud-amd64] grub2-common: fails to upgrade from 'stretch-backports' - trying to overwrite /etc/kernel/postinst.d/zz-update-grub from grub-cloud-amd64 0.0.4~bpo9+1 There is no source info for the package 'grub-cloud-amd64' at version '0.4.4~bpo9+1' with architecture '' Unable to make a source version for version '0.4.4~bpo9+1' No longer marked as found in versions 0.4.4~bpo9+1. > found -1 0.0.4~bpo9+1 Bug #919915 [grub-cloud-amd64] grub2-common: fails to upgrade from 'stretch-backports' - trying to overwrite /etc/kernel/postinst.d/zz-update-grub from grub-cloud-amd64 0.0.4~bpo9+1 Marked as found in versions grub-cloud/0.0.4~bpo9+1. > fixed -1 0.0.4 Bug #919915 [grub-cloud-amd64] grub2-common: fails to upgrade from 'stretch-backports' - trying to overwrite /etc/kernel/postinst.d/zz-update-grub from grub-cloud-amd64 0.0.4~bpo9+1 Marked as fixed in versions grub-cloud/0.0.4. > severity -1 important Bug #919915 [grub-cloud-amd64] grub2-common: fails to upgrade from 'stretch-backports' - trying to overwrite /etc/kernel/postinst.d/zz-update-grub from grub-cloud-amd64 0.0.4~bpo9+1 Severity set to 'important' from 'serious' > tags -1 wontfix Bug #919915 [grub-cloud-amd64] grub2-common: fails to upgrade from 'stretch-backports' - trying to overwrite /etc/kernel/postinst.d/zz-update-grub from grub-cloud-amd64 0.0.4~bpo9+1 Added tag(s) wontfix. -- 919915: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919915 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#919915: grub2-common: fails to upgrade from 'stretch-backports' - trying to overwrite /etc/kernel/postinst.d/zz-update-grub from grub-cloud-amd64 0.0.4~bpo9+1
Control: notfound -1 0.4.4~bpo9+1 Control: found -1 0.0.4~bpo9+1 Control: fixed -1 0.0.4 Control: severity -1 important Control: tags -1 wontfix On Sun, Jan 20, 2019 at 05:46:27PM +, Colin Watson wrote: > It isn't me who needs the policy lecture here - this is grub2-common's > configuration file, and the version of grub-cloud-amd64 in > stretch-backports seems to have decided that it's OK to overwrite it > unilaterally. This is not OK. Bastian, if you need the update-grub > snippets to be modified for some reason, then you need to coordinate > with us to get the change into grub2-common rather than just shipping > your own version. This is the state pre-#910959, so grub2-common does not yet include the file. This means all binary packages that install grub need to ship them separately, that's what grub-cloud-amd64 does. > I'm happy to add Breaks/Replaces, but first the version of > grub-cloud-amd64 in stretch-backports needs to be fixed to stop > hijacking grub2-common's conffiles. After that has been done, I would > be happy to add Breaks/Replaces on grub-cloud-amd64 (<< fixed-version). There is not way to define Breaks/Replaces relations that only match on the package variant in backports. Maybe I'll try to add a dependency grub2-common (<= fixed-#910959). Otherwise it's going to be ignored. Regards, Bastian -- Most legends have their basis in facts. -- Kirk, "And The Children Shall Lead", stardate 5029.5
Bug#919029: grub-pc forgets installation device
> On Sat, Jan 12, 2019 at 02:11:25PM +0100, Vincent Lefevre wrote: > I'm not at all sure that I agree. The configuration in question exists > in order to tell the postinst which devices it should run grub-install > on. If the device does not exist, it obviously isn't possible to run > grub-install on it. Just to be very specific. The dialogue is shown without any change to installed drives or partitions. The problem is that grub-pc simply forgets where it is installed. Best regards Heinrich
Bug#880393: nmuing cyrus-sasl2
No harm doing was intended. I simply missed the NMU. If you can point me to the direction of the patches you prepared I will try to care of it before soft freeze. Ondrej -- Ondřej Surý > On 25 Dec 2018, at 11:58, Helmut Grohne wrote: > > Hi Ryan, > >> On Mon, Dec 24, 2018 at 03:48:19PM -0800, Ryan Tandy wrote: >> I don't see any conversation about it in the bugs, but that NMU doesn't seem >> to have happened, was there a reason? > > The NMU went to delayed, but then Ondřej Surý did a maintainer upload > without including the fixes nor explaining why they shouldn't be used. > Since his (MU) version was higher than my (NMU) version, my upload was > rejected once it departed from delayed. Therefore this bug still affects > unstable despite having a solution. I'm unsure on how to best deal with > this non-communication and figured that I'd simply give up. > > I'd appreciate if someone else could handle this. At least I dissected > the cause and provided a simple and backportable solution. Could you > move this forward? > > Also given the simplicity of the fix, adding it to a stretch point > release would make a lot of sense. > > Helmut
Processed: user debian...@lists.debian.org, usertagging 909313, found 909313 in 31.0.0-1
Processing commands for cont...@bugs.debian.org:
> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was a...@debian.org).
> usertags 909313 piuparts
There were no usertags set.
Usertags are now: piuparts.
> found 909313 31.0.0-1
Bug #909313 {Done: Carsten Schoenert }
[xul-ext-sogo-connector] [xul-ext-sogo-connector] Not compatible with
thunderbird 60 (New version exists)
Marked as found in versions sogo-connector/31.0.0-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
909313: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909313
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: severity of 919919 is important
Processing commands for cont...@bugs.debian.org: > severity 919919 important Bug #919919 [src:linux] frequent lockups requiring power off Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 919919: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919919 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 918418 is forwarded to https://github.com/korfuri/django-prometheus/issues/83
Processing commands for cont...@bugs.debian.org: > forwarded 918418 https://github.com/korfuri/django-prometheus/issues/83 Bug #918418 [src:django-prometheus] django-prometheus FTBFS: test failures Set Bug forwarded-to-address to 'https://github.com/korfuri/django-prometheus/issues/83'. > thanks Stopping processing here. Please contact me if you need assistance. -- 918418: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918418 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#895381: Severity
Hello Sergio, I'm reviewing bugs that are currently release critical at our local bug squashing party, and I stumbled on yours. I'm not disputing this bug exists, I'm just trying to determine why it is you set the severity to "Serious". As you are probably aware, this severity indicates that this is a sever violation of Debian policy (violates a "must" or "required" directive), or in the package maintainer's opinion, makes the package unsuitable for release. Can you specify what part of debian policy this issue makes this bug severity "Serious"? Thanks! -- micah
Bug#892340: Status of upload?
Hello Marc, I'm checking up on RC bugs, because we are working on a Bug Squashing Party here. Back in November, you were saying you were going to combine this fix with a bump of upstream's version: > I was planning to combine this with an update from upstream. I'm wondering if you are planning on doing this soon? If you aren't, maybe we could upload the package with the fix? -- micah
Bug#919855: s390x executables crash
Control: severity -1 grave On Sun, 2019-01-20 at 06:39 +, Ben Hutchings wrote: > Source: klibc > Version: 2.0.5-1 > Severity: serious > > While investigating some test failures on klibc upstream, I found that > the new Debian version crashes on s390x. It looks like this is due to > an address collision between the build ID in the shared library and > the code in the executables. The addition of build IDs is not (yet) > part of an upstream release. In fact all architectures except mips and x86 seem to be broken. Ben. -- Ben Hutchings You can't have everything. Where would you put it? signature.asc Description: This is a digitally signed message part
Processed: Re: s390x executables crash
Processing control commands: > severity -1 grave Bug #919855 [src:klibc] s390x executables crash Severity set to 'grave' from 'serious' -- 919855: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919855 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#919255: [Pkg-electronics-devel] Bug#918533: gnucap-python: diff for NMU version 0.0.2-1.1
On Sun, Jan 20, 2019 at 07:33:44PM +0100, Mattia Rizzolo wrote: > Then if you don't mind I'd still keep my NMU as it is and let it enter > unstable. The only thing is that you'd find yourself to integrate it > into your own tree. no worries. will merge it. thanks felix
Bug#919255: marked as done (gnucap-python: please stop build-depending on python3.6)
Your message dated Sun, 20 Jan 2019 19:04:27 + with message-id and subject line Bug#919255: fixed in gnucap-python 0.0.2-1.1 has caused the Debian Bug report #919255, regarding gnucap-python: please stop build-depending on python3.6 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.) -- 919255: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919255 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gnucap-python Version: 0.0.2-1 Severity: serious Control: block 916817 by -1 Deaer maintainer, We would like to remove python3.6 from buster, so please drop the build-depends on gnucap-python. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: gnucap-python Source-Version: 0.0.2-1.1 We believe that the bug you reported is fixed in the latest version of gnucap-python, 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 919...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mattia Rizzolo (supplier of updated gnucap-python package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 20 Jan 2019 13:38:13 +0100 Source: gnucap-python Binary: gnucap-python python-gnucap python3-gnucap Architecture: source Version: 0.0.2-1.1 Distribution: unstable Urgency: medium Maintainer: Debian Electronics Team Changed-By: Mattia Rizzolo Description: gnucap-python - GNU Circuit Analysis package, Python command plugin python-gnucap - Python 2 bindings for the GNU Circuit Analysis Package python3-gnucap - Python 3 bindings for the GNU Circuit Analysis Package Closes: 918533 919255 Changes: gnucap-python (0.0.2-1.1) unstable; urgency=medium . * Non-maintainer upload. * Build-Depend on python3-all-dev instead of python3.6-dev and python3.7-dev; also stop mentioning those versions in d/rules. Closes: #919255 * Drop ancient XS-Python-Version. * Set Rules-Requires-Root:no. * Apply patch from Chris Lamb to make the build reproducible. Closes: #918533 Checksums-Sha1: a1b2c48ca9c6c14739cbc83f88afe66ec0214bcb 2339 gnucap-python_0.0.2-1.1.dsc 64435c53583e0dff16a53add1bec16bc334cf67c 8008 gnucap-python_0.0.2-1.1.debian.tar.xz c0757556e48da37576321a9752ae0847037ff643 8483 gnucap-python_0.0.2-1.1_amd64.buildinfo Checksums-Sha256: bb302b0f8bc86b7d0ca56b24838ff723df68830df9c438f0fcdf22cc2ad76ee0 2339 gnucap-python_0.0.2-1.1.dsc 41231454b22087a4f12c662182f8815470a71e48a6bfc71378fbf90408eab515 8008 gnucap-python_0.0.2-1.1.debian.tar.xz 8f4ffeb5a80afda1f9f684207d3d68daadaa8ab33022121bd88878e498629b69 8483 gnucap-python_0.0.2-1.1_amd64.buildinfo Files: 6eea63f48ce859dde56544a0cbc103a1 2339 electronics optional gnucap-python_0.0.2-1.1.dsc c5807d0f64f13d88e00c0b32e7ac1dad 8008 electronics optional gnucap-python_0.0.2-1.1.debian.tar.xz d135367b1bb68dff19d2bce5f2c9aedf 8483 electronics optional gnucap-python_0.0.2-1.1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEi3hoeGwz5cZMTQpICBa54Yx2K60FAlxEb5sACgkQCBa54Yx2 K60nHg/9HFzQv3bk8iVGCRz2lXnG0opMrIzR00aikjNwzfD6Ur4zZiqX77dl15RD l9AojiknKGwvaRGdKF7AIEwYrZjB6TV7CM3MWNchZZA79mHFA40G9UT0dKpvVw01 JX7O2fCuN2lBBi2zYxCsYoH/H4JxQ7kLLPUeIXVWtgVzJwjtIIK6b2G/lqEznwfN sPmHzvnnyTtEa0LmJ1L/VMfaSXxKya3nF0mtSnDkpynI3jQbsZ6ECCcvX4yXGJL8 lWRjKCfdTGxE2ps6vFUl9dCrZhSiD7XLu4iBXfcX5sAZV7LazdsAenPf8MMFzhcA bn+Aoj/pJcfwdLb7Df43fd/Ufazu5syfnU91gMWARkUcuP728B90IAA8SJKb+YQ3 ScvahA0eq16gulHfDAjqVrM6Q4dNaWyWq5cEXV9vCs8U/rag1MFG2hrU2r4e3Dgq BoK+zAPoiLmxYy8yeWk596hdRKkaBEHaLrRZ8bboi/UXxRL44lpfYHKv09eQWA1Z td+fN6ZypPfN7JQpU8X4EQo8GDaF+UYO/Tuq0Cwcz3zLk+wG2zdkU5wPXyPKJ0cE DDXn7sdi3oXqtau7/mN0ntMfwOPv7yfbv9QQWaM6DF+I8GFliyRe9UKfkHJx7gzz vTuD3zlFlJiw0ZQ95zcDxRMCUnj9EZ9aI4kTrJFzkZQ4H2LZYhk= =8H70 -END PGP SIGNATURE End Message ---
Bug#919255: [Pkg-electronics-devel] Bug#918533: gnucap-python: diff for NMU version 0.0.2-1.1
On Sun, Jan 20, 2019 at 07:36:57PM +0100, Felix Salfelder wrote: > On Sun, Jan 20, 2019 at 07:33:44PM +0100, Mattia Rizzolo wrote: > > Then if you don't mind I'd still keep my NMU as it is and let it enter > > unstable. The only thing is that you'd find yourself to integrate it > > into your own tree. > > no worries. will merge it. ACK, so I rescheduled the NMU to go in now. Thank you! /me looks forward for his other NMU for libkolabxml to also go in… -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature
Processed: canceled NMUs are not pending
Processing commands for cont...@bugs.debian.org: > tag 792851 - pending Bug #792851 [src:cyrus-sasl2] FTCBFS: confuses build arch and host arch compiler Removed tag(s) pending. > tag 880393 - pending Bug #880393 [libsasl2-modules-gssapi-heimdal] libsasl2-modules-gssapi-heimdal seems built against MIT Removed tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 792851: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792851 880393: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880393 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#880393: canceled NMUs are not pending
tag 792851 - pending tag 880393 - pending thanks Since Helmut's NMU was canceled as described in #880393, I am removing the "pending" tag from these two bugs.
Bug#919255: [Pkg-electronics-devel] Bug#918533: gnucap-python: diff for NMU version 0.0.2-1.1
On Sun, Jan 20, 2019 at 05:03:27PM +0100, Felix Salfelder wrote: > On Sun, Jan 20, 2019 at 04:34:28PM +0100, Mattia Rizzolo wrote: > > If it's only about sponsoring I'm happy to help, but I don't really want > > to play with symbols at this time… > > my preferred solution will be to accept the dpkg-shlibdeps warnings, as > described in the manual. it will be more tricky to silence them. I also usually just ignore those myself… > > With this and onther package being the only last blockers for the > > removal of python3.6 I'm somewhat pressured to continue, unless you can > > give me a shorter ETA. Also, I'm happy to rework my work. > > I essetially agree with your changes. the ETA is subject to > review & sponsoring. Then if you don't mind I'd still keep my NMU as it is and let it enter unstable. The only thing is that you'd find yourself to integrate it into your own tree. > > * you are build-depending on python3-dev, instead of python3-all-dev, > > is that wanted? As I went for the letter in my NMU. > > looks reasonable. i simply did not know about it. python3-all-dev depends on all the supported python3 versions, which means that until 2 months ago it would have pulled in both 3.6 and 3.7. Instead, python3-dev only pulls in the default version. > > Also, while working on gnucap-python, I had the feeling that those > > out2.7 and out3.6 directories were pre-built stuff that shouldn't be in > > out* contains the expected output for testing, which varies across > python versions. it actually shouldn't, and it does not between 3.7 and > 3.6. perhaps out2 and out3 will be sufficient. work in progress, > possibly ready in 0.0.3. Oh, then my change that is removing them is not right. mhh well, since the tests are disabled anyway I'll leave it there, but indeed it requires some changes. Sorry I didn't understand what that thing was. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature
Bug#919909: marked as done (libconfig-model-backend-yaml-perl: fails to upgrade from 'stretch' - trying to overwrite /usr/share/man/man3/Config::Model::Backend::Yaml.3pm.gz)
Your message dated Sun, 20 Jan 2019 18:21:35 + with message-id and subject line Bug#919909: fixed in libconfig-model-backend-yaml-perl 2.133-2 has caused the Debian Bug report #919909, regarding libconfig-model-backend-yaml-perl: fails to upgrade from 'stretch' - trying to overwrite /usr/share/man/man3/Config::Model::Backend::Yaml.3pm.gz to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 919909: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919909 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libconfig-model-backend-yaml-perl Version: 2.133-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: affects -1 + libconfig-model-perl Hi, during a test with piuparts I noticed your package fails to upgrade from 'stretch'. It installed fine in 'stretch', then the upgrade to 'buster' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Selecting previously unselected package libconfig-model-backend-yaml-perl. Preparing to unpack .../047-libconfig-model-backend-yaml-perl_2.133-1_all.deb ... Unpacking libconfig-model-backend-yaml-perl (2.133-1) ... dpkg: error processing archive /tmp/apt-dpkg-install-T8rg5D/047-libconfig-model-backend-yaml-perl_2.133-1_all.deb (--unpack): trying to overwrite '/usr/share/man/man3/Config::Model::Backend::Yaml.3pm.gz', which is also in package libconfig-model-perl 2.097-2 cheers, Andreas libconfig-model-perl_2.133-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: libconfig-model-backend-yaml-perl Source-Version: 2.133-2 We believe that the bug you reported is fixed in the latest version of libconfig-model-backend-yaml-perl, 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 919...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. gregor herrmann (supplier of updated libconfig-model-backend-yaml-perl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 20 Jan 2019 19:07:57 CET Source: libconfig-model-backend-yaml-perl Binary: libconfig-model-backend-yaml-perl Architecture: source Version: 2.133-2 Distribution: unstable Urgency: medium Maintainer: Debian Perl Group Changed-By: gregor herrmann Description: libconfig-model-backend-yaml-perl - Read and write config as a YAML data structure Closes: 919909 Changes: libconfig-model-backend-yaml-perl (2.133-2) unstable; urgency=medium . * Team upload. * Add Breaks+Replaces on old libconfig-model-perl which still contained the YAML backend. Thanks to Andreas Beckmann for the bug report. (Closes: #919909) * Don't install t/README.md. * Update debian/upstream/metadata. Checksums-Sha256: 6b078bca0d9dd38d0bc8c5dac7be26c3b767d9e98bc778b96d102e02a895e5e6 2624 libconfig-model-backend-yaml-perl_2.133-2.dsc c5e65b3430c0a592dcc97c3c3d33652d700e895f80ebe6cd7830ed4756d85464 1928 libconfig-model-backend-yaml-perl_2.133-2.debian.tar.xz ad293b316af24e443c2ea4e4f66933d54bee67fcbdb1ee1c8acb19111f8e0f80 6941 libconfig-model-backend-yaml-perl_2.133-2_sourceonly.buildinfo Checksums-Sha1: 5754f8c38d91c235eb8aee0bb828a67524247cc1 2624 libconfig-model-backend-yaml-perl_2.133-2.dsc 86de3ae9794a7e8d93190238fa024416821f6126 1928 libconfig-model-backend-yaml-perl_2.133-2.debian.tar.xz d13019e10341c2d0e7a6c0615be9ffdf4b04d6bc 6941 libconfig-model-backend-yaml-perl_2.133-2_sourceonly.buildinfo Files: b621acdf5009580a54fb7c06044591f6 2624 perl optional libconfig-model-backend-yaml-perl_2.133-2.dsc 1667b208409a8f7ba0dee59295dbf74a 1928 perl optional libconfig-model-backend-yaml-perl_2.133-2.debian.tar.xz 29af4196c654092dda6c26b80fe27c15 6941 - - libconfig-model-backend-yaml-perl_2.133-2_sourceonly.buildinfo -BEGIN PGP SIGNATURE- iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAlxEuP1fFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
Bug#919922: Does not start anymore, existing file /var/log/atop/atop_20190120 has incompatible header
Package: atop
Version: 2.4.0-1
Severity: grave
Hello!
After the update tpo 2.4.0-1 atop does not start anymore for me.
TL;DR:
existing file /var/log/atop/atop_20190120 has incompatible header
(created by version 2.3 - current version 2.4)
Here the whole debugging session:
server:~# systemctl start atop; systemctl status atop; sleep 2; systemctl
status atop
● atop.service - Atop advanced performance monitor
Loaded: loaded (/lib/systemd/system/atop.service; enabled; vendor preset:
enabled)
Active: active (running) since Sun 2019-01-20 19:08:50 CET; 11ms ago
Docs: man:atop(1)
Main PID: 550488 (atop.daily)
Tasks: 5 (limit: 4691)
Memory: 1.5M
CGroup: /system.slice/atop.service
├─550488 /bin/bash /usr/share/atop/atop.daily
├─550491 ps -p 547913
└─550492 grep atop$
● atop.service - Atop advanced performance monitor
Loaded: loaded (/lib/systemd/system/atop.service; enabled; vendor preset:
enabled)
Active: failed (Result: exit-code) since Sun 2019-01-20 19:08:50 CET; 1s ago
Docs: man:atop(1)
Process: 550488 ExecStart=/usr/share/atop/atop.daily (code=exited, status=7)
Main PID: 550488 (code=exited, status=7)
As one can see, the unit starts /usr/share/atop/atop.daily but no daemon
remains at the end.
Even when running the shell script directly, nothing happens:
server:~# ps auwwwx | grep [a]top; rm /run/atop.pid; bash -x
/usr/share/atop/atop.daily; sleep 5; ps auwwwx | grep [a]top
user 547330 0.2 0.8 51748 33624 pts/2S+ 19:06 0:00
/usr/bin/python3 /usr/bin/reportbug atop
user 549910 0.0 0.0 2512 508 pts/2S+ 19:07 0:00 sh -c vim -c
:6 '/tmp/user/1000/reportbug-atop-20190120-547330-uof401oa'
user 549911 0.1 0.1 12340 7324 pts/2S+ 19:07 0:00 vim -c :6
/tmp/user/1000/reportbug-atop-20190120-547330-uof401oa
+ LOGOPTS=-R
+ LOGINTERVAL=600
+ LOGGENERATIONS=28
+ DEFAULTSFILE=/etc/default/atop
+ '[' -e /etc/default/atop ']'
+ . /etc/default/atop
+ case "$LOGGENERATIONS" in
++ date +%Y%m%d
+ CURDAY=20190120
+ LOGPATH=/var/log/atop
+ BINPATH=/usr/bin
+ PIDFILE=/run/atop.pid
+ '[' -e /run/atop.pid ']'
+ sleep 3
+ echo 555663
+ exec /usr/bin/atop -R -w /var/log/atop/atop_20190120 600
+ find /var/log/atop -name 'atop_*' -mtime +28 -exec rm '{}' ';'
user 547330 0.2 0.8 51748 33624 pts/2S+ 19:06 0:00
/usr/bin/python3 /usr/bin/reportbug atop
user 549910 0.0 0.0 2512 508 pts/2S+ 19:07 0:00 sh -c vim -c
:6 '/tmp/user/1000/reportbug-atop-20190120-547330-uof401oa'
user 549911 0.1 0.1 12340 7324 pts/2S+ 19:07 0:00 vim -c :6
/tmp/user/1000/reportbug-atop-20190120-547330-uof401oa
(You can see the open reportbug where I type this in right now.)
Running atop directly shows the problem:
server:~# /usr/bin/atop -R -w /var/log/atop/atop_20190120 600
existing file /var/log/atop/atop_20190120 has incompatible header
(created by version 2.3 - current version 2.4)
Deleting all files in /var/log/atop/ makes it work again.
Side not: the error message does *not* appear in the journal nor the syslog.
Grüße,
Sven.
-- System Information:
Debian Release: buster/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500,
'unstable'), (500, 'testing'), (200, 'experimental'), (1, 'experimental-debug')
Architecture: i386 (x86_64)
Foreign Architectures: amd64
Kernel: Linux 4.19.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8),
LANGUAGE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages atop depends on:
ii libc62.28-5
ii libncurses6 6.1+20181013-1
ii libtinfo66.1+20181013-1
ii lsb-base 10.2018112800
ii zlib1g 1:1.2.11.dfsg-1
Versions of packages atop recommends:
ii cron [cron-daemon] 3.0pl1-130
atop suggests no packages.
-- debconf-show failed
Processed: Bug #919909 in libconfig-model-backend-yaml-perl marked as pending
Processing control commands: > tag -1 pending Bug #919909 [libconfig-model-backend-yaml-perl] libconfig-model-backend-yaml-perl: fails to upgrade from 'stretch' - trying to overwrite /usr/share/man/man3/Config::Model::Backend::Yaml.3pm.gz Added tag(s) pending. -- 919909: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919909 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#919899: marked as done (libppl-{c4,swi}: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE)
Your message dated Sun, 20 Jan 2019 18:05:24 +
with message-id
and subject line Bug#919899: fixed in ppl 1:1.2-7
has caused the Debian Bug report #919899,
regarding libppl-{c4,swi}: unhandled symlink to directory conversion:
/usr/share/doc/PACKAGE
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.)
--
919899: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919899
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libppl-c4,libppl-swi
Version: 1:1.2-5
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old version of the package shipped a
symlink but that was later replaced by a real (and non-empty)
directory. This kind of overwriting another package's files cannot be
detected by dpkg.
This was observed on the following upgrade paths:
stretch -> sid
For /usr/share/doc/PACKAGE this may not be problematic as long as both
packages are installed, ship byte-for-byte identical files and are
upgraded in lockstep. But once one of the involved packages gets
removed, the other one will lose its documentation files, too,
including the copyright file, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#copyright-information
For other overwritten locations anything interesting may happen.
Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#details-of-unpack-phase-of-installation-or-upgrade
It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.maintscript.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.
>From the attached log (scroll to the bottom...):
0m26.3s ERROR: FAIL: silently overwrites files via directory symlinks:
/usr/share/doc/libppl-c4/changelog.Debian.gz (libppl-c4:amd64) !=
/usr/share/doc/libppl14/changelog.Debian.gz (libppl14:amd64)
/usr/share/doc/libppl-c4 -> libppl14
/usr/share/doc/libppl-c4/changelog.gz (libppl-c4:amd64) !=
/usr/share/doc/libppl14/changelog.gz (libppl14:amd64)
/usr/share/doc/libppl-c4 -> libppl14
/usr/share/doc/libppl-c4/copyright (libppl-c4:amd64) !=
/usr/share/doc/libppl14/copyright (libppl14:amd64)
/usr/share/doc/libppl-c4 -> libppl14
0m39.7s ERROR: FAIL: silently overwrites files via directory symlinks:
/usr/share/doc/libppl-swi/changelog.Debian.gz (libppl-swi:amd64) !=
/usr/share/doc/libppl14/changelog.Debian.gz (libppl14:amd64)
/usr/share/doc/libppl-swi -> libppl14
/usr/share/doc/libppl-swi/changelog.gz (libppl-swi:amd64) !=
/usr/share/doc/libppl14/changelog.gz (libppl14:amd64)
/usr/share/doc/libppl-swi -> libppl14
/usr/share/doc/libppl-swi/copyright (libppl-swi:amd64) !=
/usr/share/doc/libppl14/copyright (libppl14:amd64)
/usr/share/doc/libppl-swi -> libppl14
cheers,
Andreas
libppl-c4_1:1.2-5.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: ppl
Source-Version: 1:1.2-7
We believe that the bug you reported is fixed in the latest version of
ppl, 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 919...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
James Clarke (supplier of updated ppl package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 20 Jan 2019 16:48:25 +
Source: ppl
Binary: libppl14 libppl-dev ppl-dev libppl-c4 libppl-doc libppl-swi
Architecture: source
Version: 1:1.2-7
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team
Changed-By: James Clarke
Description:
libppl-c4 - Parma Polyhedra Library (C interface)
libppl-dev - Parma Polyhedra Library (development)
libppl-doc - Parma Polyhedra Library: Documentation
libppl-swi - Parma Polyhedra Library (SWI Prolog interface)
Bug#919909: Bug #919909 in libconfig-model-backend-yaml-perl marked as pending
Control: tag -1 pending Hello, Bug #919909 in libconfig-model-backend-yaml-perl reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/perl-team/modules/packages/libconfig-model-backend-yaml-perl/commit/9cf9ad397b069eeb14b77036072925d593144520 Add Breaks+Replaces on old libconfig-model-perl which still contained the YAML backend. Closes: #919909 Thanks: Andreas Beckmann for the bug report. (this message was generated automatically) -- Greetings https://bugs.debian.org/919909
Processed: Bug #783346: patch for booting Jessie domU with wheezy dom0
Processing commands for cont...@bugs.debian.org: > reassign 783346 src:xen 4.1.4-3+deb7u4 Bug #783346 [xen-utils-4.1] patch for booting Jessie domU with wheezy dom0 Bug reassigned from package 'xen-utils-4.1' to 'src:xen'. No longer marked as found in versions xen/4.1.4-3+deb7u4. Ignoring request to alter fixed versions of bug #783346 to the same values previously set Bug #783346 [src:xen] patch for booting Jessie domU with wheezy dom0 Marked as found in versions xen/4.1.4-3+deb7u4. > severity 783346 normal Bug #783346 [src:xen] patch for booting Jessie domU with wheezy dom0 Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 783346: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783346 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 919882 is normal
Processing commands for cont...@bugs.debian.org: > severity 919882 normal Bug #919882 [firefox-esr] firefox-esr: linker options under investigation for 32-bit builds Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 919882: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919882 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#783346: Bug #783346: patch for booting Jessie domU with wheezy dom0
reassign 783346 src:xen 4.1.4-3+deb7u4 severity 783346 normal thanks Hi Daniel, This is about the bug report that you filed before about pygrub in the Debian bug tracker against the Xen packages. Your bug report was targeted at a Xen package in a Debian distribution older than the current stable (Stretch), and I'm trying to clean up our open bug report list a bit. In the bug history, I see that already was suggested to use the grub2 based way of booting the virtual machines instead of pygrub. This is still recommended. Addtionally, the grub-xen-* packages in Debian Buster will now also be able to boot a Xen domU using the new PVH virtualization mode, if you use the Debian Linux 4.19 kernel package inside. Am I right to understand that we can close this bug report now? >8 Please note that unless there's a response within a month from now, we will close the bug report. If you discover this message later, and this case is important to you, then you can try unarchiving the bug and replying to it, or reach out to the maintainers email list at pkg-xen-devel at lists.alioth.debian.org (no subscription required) and post a message. Thanks, Hans van Kranenburg
Bug#912592: Xen stuck at boot "device-mapper: ioctl: …"
severity 912592 normal tags 912592 + moreinfo thanks Hi zer0 divide, Thanks for your report. I have never used the combination of Xen dom0 and cryptsetup myself. Did you already find out what the cause of this issue is? It sounds a bit like a problem with your initramfs. Or, can you explain why you think the problem is caused by a defect in Xen? If not, can you show more debug logging? Good luck, Hans van Kranenburg
Processed: Xen stuck at boot "device-mapper: ioctl: …"
Processing commands for cont...@bugs.debian.org: > severity 912592 normal Bug #912592 [src:xen] Xen stuck at boot "device-mapper: ioctl: …" Severity set to 'normal' from 'critical' > tags 912592 + moreinfo Bug #912592 [src:xen] Xen stuck at boot "device-mapper: ioctl: …" Added tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 912592: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912592 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#919915: grub2-common: fails to upgrade from 'stretch-backports' - trying to overwrite /etc/kernel/postinst.d/zz-update-grub from grub-cloud-amd64 0.0.4~bpo9+1
Control: reassign -1 grub-cloud-amd64 0.4.4~bpo9+1 Control: affects -1 grub2-common On Sun, Jan 20, 2019 at 06:03:36PM +0100, Andreas Beckmann wrote: > during a test with piuparts I noticed your package fails to upgrade from > 'stretch'. > It installed fine in 'stretch', then the upgrade to 'buster' fails > because it tries to overwrite other packages files without declaring a > Breaks+Replaces relation. > > See policy 7.6 at > https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces > > >From the attached log (scroll to the bottom...): > > Unpacking grub2-common (2.02+dfsg1-10) over (2.02~beta3-5+deb9u1) ... > dpkg: error processing archive > /tmp/apt-dpkg-install-lSZYhO/12-grub2-common_2.02+dfsg1-10_amd64.deb > (--unpack): >trying to overwrite '/etc/kernel/postinst.d/zz-update-grub', which is also > in package grub-cloud-amd64 0.0.4~bpo9+1 > dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) > > Interestingly I could only trigger this error so far on a > stretch->stetch-backports->buster > upgrade path. Dependencies seem to be tight enough to prevent this within > buster itself. It isn't me who needs the policy lecture here - this is grub2-common's configuration file, and the version of grub-cloud-amd64 in stretch-backports seems to have decided that it's OK to overwrite it unilaterally. This is not OK. Bastian, if you need the update-grub snippets to be modified for some reason, then you need to coordinate with us to get the change into grub2-common rather than just shipping your own version. I'm happy to add Breaks/Replaces, but first the version of grub-cloud-amd64 in stretch-backports needs to be fixed to stop hijacking grub2-common's conffiles. After that has been done, I would be happy to add Breaks/Replaces on grub-cloud-amd64 (<< fixed-version). -- Colin Watson [cjwat...@debian.org]
Processed: severity of 919774 is serious
Processing commands for cont...@bugs.debian.org: > severity 919774 serious Bug #919774 [meld] add dependency on python3-gi-cairo Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 919774: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919774 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#919915: grub2-common: fails to upgrade from 'stretch-backports' - trying to overwrite /etc/kernel/postinst.d/zz-update-grub from grub-cloud-amd64 0.0.4~bpo9+1
Processing control commands: > reassign -1 grub-cloud-amd64 0.4.4~bpo9+1 Bug #919915 [grub2-common] grub2-common: fails to upgrade from 'stretch-backports' - trying to overwrite /etc/kernel/postinst.d/zz-update-grub from grub-cloud-amd64 0.0.4~bpo9+1 Bug reassigned from package 'grub2-common' to 'grub-cloud-amd64'. No longer marked as found in versions grub2/2.02+dfsg1-10. Ignoring request to alter fixed versions of bug #919915 to the same values previously set Bug #919915 [grub-cloud-amd64] grub2-common: fails to upgrade from 'stretch-backports' - trying to overwrite /etc/kernel/postinst.d/zz-update-grub from grub-cloud-amd64 0.0.4~bpo9+1 There is no source info for the package 'grub-cloud-amd64' at version '0.4.4~bpo9+1' with architecture '' Unable to make a source version for version '0.4.4~bpo9+1' Marked as found in versions 0.4.4~bpo9+1. > affects -1 grub2-common Bug #919915 [grub-cloud-amd64] grub2-common: fails to upgrade from 'stretch-backports' - trying to overwrite /etc/kernel/postinst.d/zz-update-grub from grub-cloud-amd64 0.0.4~bpo9+1 Added indication that 919915 affects grub2-common -- 919915: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919915 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#919919: frequent lockups requiring power off
Package: src:linux Version: 4.19.12-1 Severity: grave Tags: upstream Hello, I experience lockups about every few minutes to hours of my laptop which I guess are kernel bugs. At least, the machine is fairly new, and hardware diagnostics turned up nothing. The system has a standard /boot and an LUKS+LVM container, containing the rest of it (/, swap, and some unused space). The root partition (/) is formatted as BTRFS. In the logs, I find things like this: Jan 13 02:42:51 laptop-t kernel: [112014.623614] (NULL device *): firmware: direct-loading firmware iwlwifi-9260-th-b0-jf-b0-38.ucode Jan 13 11:15:37 laptop-t kernel: [112014.623725] Freezing user space processes ... (elapsed 0.001 seconds) done. Jan 13 11:15:37 laptop-t kernel: [112014.625213] OOM killer disabled. Jan 13 11:15:37 laptop-t kernel: [112014.625213] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. Jan 13 11:15:37 laptop-t kernel: [112014.626318] Suspending console(s) (use no_console_suspend to debug) Jan 13 11:15:37 laptop-t kernel: [112014.627028] wlp59s0: deauthenticating from c0:3e:0f:ac:54:8d by local choice (Reason: 3=DEAUTH_LEAVING) Jan 13 11:15:37 laptop-t kernel: [112227.801000] watchdog: BUG: soft lockup - CPU#11 stuck for 192s! [swapper/11:0] Jan 13 11:15:37 laptop-t kernel: [112227.801002] Modules linked in: iptable_nat iptable_filter ctr ccm ipt_MASQUERADE nf_conntrack_netlink xfrm_user xfrm_algo cmac nft_chain_nat_ipv4 devlink xt_addrtype br_netfilter bridge stp ifb sch_fq_codel snd_hda_codec_hdmi overlay snd_hda_codec_realtek snd_hda_codec_generic nft_chain_route_ipv6 nf_log_ipv6 nft_chain_route_ipv4 xt_connmark nf_log_ipv4 nf_log_common nft_limit nft_counter xt_helper xt_LOG xt_limit xt_conntrack xt_tcpudp nft_compat nf_conntrack_sip nf_conntrack_ftp nf_conntrack_irc nf_conntrack_pptp nf_conntrack_proto_gre ip6_tables appletalk psnap llc ax25 bnep fuse arc4 nf_tables nfnetlink openvswitch nsh nf_nat_ipv6 nf_nat_ipv4 nf_conncount nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 dell_rbtn binfmt_misc nls_ascii nls_cp437 vfat fat ext4 mbcache jbd2 fscrypto ecb intel_rapl Jan 13 11:15:37 laptop-t kernel: [112227.801073] x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel dell_laptop dell_wmi kvm iwlmvm irqbypass dell_smbios mac80211 nouveau snd_hda_intel i915 btusb snd_hda_codec btrtl btbcm uvcvideo btintel snd_hda_core videobuf2_vmalloc wmi_bmof snd_hwdep videobuf2_memops videobuf2_v4l2 bluetooth snd_pcm mxm_wmi videobuf2_common efi_pstore snd_timer intel_cstate iwlwifi dell_wmi_descriptor ttm dcdbas intel_uncore drbg dell_smm_hwmon videodev snd drm_kms_helper ansi_cprng iTCO_wdt cfg80211 media serio_raw intel_rapl_perf pcspkr hid_multitouch efivars soundcore iTCO_vendor_support rtsx_pci_sdmmc rtsx_pci_ms mei_me ecdh_generic mmc_core drm evdev mei rfkill crc16 memstick joydev ucsi_acpi typec_ucsi idma64 processor_thermal_device i2c_algo_bit typec intel_soc_dts_iosf intel_pch_thermal battery int3403_thermal Jan 13 11:15:37 laptop-t kernel: [112227.801144] int340x_thermal_zone wmi video dell_smo8800 int3400_thermal intel_hid pcc_cpufreq acpi_thermal_rel sparse_keymap acpi_pad ac button parport_pc ppdev lp parport efivarfs ip_tables x_tables autofs4 btrfs xor zstd_decompress zstd_compress xxhash raid6_pq libcrc32c crc32c_generic algif_skcipher af_alg dm_crypt dm_mod wacom usbhid hid_generic crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel pcbc ahci xhci_pci libahci aesni_intel xhci_hcd libata aes_x86_64 crypto_simd psmouse cryptd usbcore nvme glue_helper scsi_mod i2c_i801 nvme_core rtsx_pci i2c_hid intel_lpss_pci hid intel_lpss usb_common thermal [last unloaded: ebtables] Jan 13 11:15:37 laptop-t kernel: [112227.801210] CPU: 11 PID: 0 Comm: swapper/11 Tainted: G L4.19.0-1-amd64 #1 Debian 4.19.12-1 Jan 13 11:15:37 laptop-t kernel: [112227.801211] Hardware name: Dell Inc. Precision 5530/0FP2W2, BIOS 1.6.0 11/02/2018 Jan 13 11:15:37 laptop-t kernel: [112227.801218] RIP: 0010:do_idle+0x267/0x280 Jan 13 11:15:37 laptop-t kernel: [112227.801222] Code: 12 4e 00 e9 d0 fe ff ff 48 89 df e8 f3 57 04 00 e9 1f ff ff ff 0f 0b fb 66 0f 1f 44 00 00 e9 d3 fe ff ff fb 66 0f 1f 44 00 00 a9 fe ff ff e8 1f fe 05 00 eb b0 e8 08 c3 fc ff 0f 1f 84 00 00 Jan 13 11:15:37 laptop-t kernel: [112227.801224] RSP: 0018:b81583253ed8 EFLAGS: 0202 ORIG_RAX: ff13 Jan 13 11:15:37 laptop-t kernel: [112227.801228] RAX: 0008 RBX: 000b RCX: Jan 13 11:15:37 laptop-t kernel: [112227.801230] RDX: 0011 RSI: 99ed1c4ea240 RDI: fff86eefda25 Jan 13 11:15:37 laptop-t kernel: [112227.801232] RBP: 91b2c820 R08: 0002 R09: 000214c0 Jan 13 11:15:37 laptop-t kernel: [112227.801234] R10: 0001287fb6384ab9 R11: 0fc5 R12: 99ed1c4ea100 Jan 13 11:15:37 laptop-t kernel: [112227.801235] R13: 91ab64c0 R14: R15: Jan 13
Processed: xen-hypervisor-4.8-amd64: After upgrade to stretch all Windows VM crash on boot or hang on boot
Processing commands for cont...@bugs.debian.org: > severity 882806 normal Bug #882806 [src:xen] xen-hypervisor-4.8-amd64: After upgrade to stretch all Windows VM crash on boot or hang on boot Severity set to 'normal' from 'critical' > tags 882806 + moreinfo Bug #882806 [src:xen] xen-hypervisor-4.8-amd64: After upgrade to stretch all Windows VM crash on boot or hang on boot Added tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 882806: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882806 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#919918: scikit-learn FTBFS on armel/armhf/arm64/ppc64el/s390x: test failures
Source: scikit-learn Version: 0.20.1+dfsg-3 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=scikit-learn=sid There are several, potentially unrelated, test failures on various architectures.
Bug#882806: xen-hypervisor-4.8-amd64: After upgrade to stretch all Windows VM crash on boot or hang on boot
severity 882806 normal tags 882806 + moreinfo thanks Hi Dan, Thanks for your report. There's a small team of Debian package maintainers, and a huge amount of different things you can do with Xen. While Xen allows running Windows guests, the Debian maintainers do not have much experience with that, and moreover, do not have the means to help reproducing the errors you see. I hope you have found out more about your issue in the meantime. If so, please let us know. The upstream Xen documentation and wiki has information about debugging guest startup and collecting information. You could also try your luck on the upstream xen-users mailing list [0]. However, this would also require more detailed information instead of only "It doesn't work"-style information in order to enable others to help you. Good luck, Hans van Kranenburg [0] https://lists.xenproject.org/mailman/listinfo/xen-users
Bug#919902: marked as done (exim4-config: fails to upgrade from 'stretch': option "hosts_try_dane" unknown)
Your message dated Sun, 20 Jan 2019 17:19:45 + with message-id and subject line Bug#919902: fixed in exim4 4.92~RC4-3 has caused the Debian Bug report #919902, regarding exim4-config: fails to upgrade from 'stretch': option "hosts_try_dane" unknown 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.) -- 919902: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919902 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: exim4-config Version: 4.92~RC4-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: affects -1 + exim4-daemon-light Hi, during a test with piuparts I noticed your package fails to upgrade from 'stretch'. It installed fine in 'stretch', then the upgrade to 'buster' fails. >From the attached log (scroll to the bottom...): Setting up exim4-config (4.92~RC4-2) ... Installing new version of config file /etc/exim4/conf.d/acl/30_exim4-config_check_rcpt ... Installing new version of config file /etc/exim4/conf.d/acl/40_exim4-config_check_data ... Installing new version of config file /etc/exim4/conf.d/main/01_exim4-config_listmacrosdefs ... Installing new version of config file /etc/exim4/conf.d/main/02_exim4-config_options ... Installing new version of config file /etc/exim4/conf.d/router/200_exim4-config_primary ... Installing new version of config file /etc/exim4/conf.d/transport/30_exim4-config_remote_smtp ... Installing new version of config file /etc/exim4/conf.d/transport/30_exim4-config_remote_smtp_smarthost ... Installing new version of config file /etc/exim4/exim4.conf.template ... 2019-01-18 08:14:02 Exim configuration error in line 833 of /var/lib/exim4/config.autogenerated.tmp: option "hosts_try_dane" unknown Invalid new configfile /var/lib/exim4/config.autogenerated.tmp, not installing /var/lib/exim4/config.autogenerated.tmp to /var/lib/exim4/config.autogenerated dpkg: error processing package exim4-config (--configure): subprocess installed post-installation script returned error exit status 1 cheers, Andreas exim4-daemon-light_4.92~RC4-2.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: exim4 Source-Version: 4.92~RC4-3 We believe that the bug you reported is fixed in the latest version of exim4, 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 919...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Metzler (supplier of updated exim4 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 20 Jan 2019 17:52:39 +0100 Source: exim4 Binary: exim4-base exim4-config exim4-daemon-light exim4 exim4-daemon-heavy eximon4 exim4-dev Architecture: source Version: 4.92~RC4-3 Distribution: unstable Urgency: medium Maintainer: Exim4 Maintainers Changed-By: Andreas Metzler Closes: 919902 Description: exim4-base - support files for all Exim MTA (v4) packages exim4-config - configuration for the Exim MTA (v4) exim4-daemon-heavy - Exim MTA (v4) daemon with extended features, including exiscan-ac exim4-daemon-light - lightweight Exim MTA (v4) daemon exim4-dev - header files for the Exim MTA (v4) packages exim4 - metapackage to ease Exim MTA (v4) installation eximon4- monitor application for the Exim MTA (v4) (X11 interface) Changes: exim4 (4.92~RC4-3) unstable; urgency=medium . * Refresh debian/upstream/signing-key.asc from https://downloads.exim.org/Exim-Maintainers-Keyring.asc. * Drop outdated pointers to alioth package homepage from README.Debian. * Update exim4-config Breaks to enforce upgrade to daemon binary package with DANE support. Closes: #919902 * [lintian] Minimize upstream/signing-key.asc. Checksums-Sha1: 85b75bac8e96f7e9485aeb9d13d0e9c57407f761 2863 exim4_4.92~RC4-3.dsc cbf2fb2ca06210339aca55d128373a158c3c1fde 452864 exim4_4.92~RC4-3.debian.tar.xz Checksums-Sha256: 30642ca3f0c4e66730fba424550fc22b513a5bab9d6100ada10a5222bccb5069 2863 exim4_4.92~RC4-3.dsc d8aa4b974707e9cbf4d7881e5dd095eb4e1a4bffc893a311c350db7255a2655d 452864 exim4_4.92~RC4-3.debian.tar.xz Files: 58666fd8e16dbe80d71dd74362d59fb2 2863
Processed: yui-compressor: insufficient java dependency in jessie
Processing control commands: > affects -1 + libjs-protoaculous Bug #919917 [yui-compressor] yui-compressor: insufficient java dependency in jessie Added indication that 919917 affects libjs-protoaculous > found -1 libjs-protoaculous/5 Bug #919917 [yui-compressor] yui-compressor: insufficient java dependency in jessie The source libjs-protoaculous and version 5 do not appear to match any binary packages Marked as found in versions libjs-protoaculous/5. -- 919917: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919917 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#919917: yui-compressor: insufficient java dependency in jessie
Package: yui-compressor Version: 2.4.7-2 Severity: serious Tags: jessie User: debian...@lists.debian.org Usertags: piuparts Control: affects -1 + libjs-protoaculous Control: found -1 libjs-protoaculous/5 Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): Setting up default-jre-headless (2:1.7-52) ... Setting up yui-compressor (2.4.7-2) ... Setting up libjs-protoaculous (5) ... [warning] /usr/bin/yui-compressor: No java runtime was found [warning] /usr/bin/yui-compressor: No JAVA_CMD set for run_java, falling back to JAVA_CMD = java readlink: missing operand Try 'readlink --help' for more information. /usr/bin/yui-compressor: 304: exec: java: not found dpkg: error processing package libjs-protoaculous (--configure): subprocess installed post-installation script returned error exit status 127 Processing triggers for ca-certificates (20141019+deb8u3) ... Updating certificates in /etc/ssl/certs... 0 added, 0 removed; done. Running hooks in /etc/ca-certificates/update.d done. done. Setting up openjdk-7-jre-headless:amd64 (7u181-2.6.14-1~deb8u1) ... update-alternatives: using /usr/lib/jvm/java-7-openjdk-amd64/jre/bin/rmid to provide /usr/bin/rmid (rmid) in auto mode update-alternatives: using /usr/lib/jvm/java-7-openjdk-amd64/jre/bin/java to provide /usr/bin/java (java) in auto mode update-alternatives: using /usr/lib/jvm/java-7-openjdk-amd64/jre/bin/keytool to provide /usr/bin/keytool (keytool) in auto mode update-alternatives: using /usr/lib/jvm/java-7-openjdk-amd64/jre/bin/pack200 to provide /usr/bin/pack200 (pack200) in auto mode update-alternatives: using /usr/lib/jvm/java-7-openjdk-amd64/jre/bin/rmiregistry to provide /usr/bin/rmiregistry (rmiregistry) in auto mode update-alternatives: using /usr/lib/jvm/java-7-openjdk-amd64/jre/bin/unpack200 to provide /usr/bin/unpack200 (unpack200) in auto mode update-alternatives: using /usr/lib/jvm/java-7-openjdk-amd64/jre/bin/orbd to provide /usr/bin/orbd (orbd) in auto mode update-alternatives: using /usr/lib/jvm/java-7-openjdk-amd64/jre/bin/servertool to provide /usr/bin/servertool (servertool) in auto mode update-alternatives: using /usr/lib/jvm/java-7-openjdk-amd64/jre/bin/tnameserv to provide /usr/bin/tnameserv (tnameserv) in auto mode update-alternatives: using /usr/lib/jvm/java-7-openjdk-amd64/jre/lib/jexec to provide /usr/bin/jexec (jexec) in auto mode Processing triggers for libc-bin (2.19-18+deb8u10) ... Processing triggers for systemd (215-17+deb8u7) ... Errors were encountered while processing: libjs-protoaculous cheers, Andreas libjs-protoaculous_5.log.gz Description: application/gzip
Bug#919915: grub2-common: fails to upgrade from 'stretch-backports' - trying to overwrite /etc/kernel/postinst.d/zz-update-grub from grub-cloud-amd64 0.0.4~bpo9+1
Package: grub2-common Version: 2.02+dfsg1-10 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: affects -1 + grub-cloud-amd64 Hi, during a test with piuparts I noticed your package fails to upgrade from 'stretch'. It installed fine in 'stretch', then the upgrade to 'buster' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Unpacking grub2-common (2.02+dfsg1-10) over (2.02~beta3-5+deb9u1) ... dpkg: error processing archive /tmp/apt-dpkg-install-lSZYhO/12-grub2-common_2.02+dfsg1-10_amd64.deb (--unpack): trying to overwrite '/etc/kernel/postinst.d/zz-update-grub', which is also in package grub-cloud-amd64 0.0.4~bpo9+1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Interestingly I could only trigger this error so far on a stretch->stetch-backports->buster upgrade path. Dependencies seem to be tight enough to prevent this within buster itself. cheers, Andreas grub-cloud-amd64_0.0.4.log.gz Description: application/gzip
Processed: grub2-common: fails to upgrade from 'stretch-backports' - trying to overwrite /etc/kernel/postinst.d/zz-update-grub from grub-cloud-amd64 0.0.4~bpo9+1
Processing control commands: > affects -1 + grub-cloud-amd64 Bug #919915 [grub2-common] grub2-common: fails to upgrade from 'stretch-backports' - trying to overwrite /etc/kernel/postinst.d/zz-update-grub from grub-cloud-amd64 0.0.4~bpo9+1 Added indication that 919915 affects grub-cloud-amd64 -- 919915: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919915 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#919914: gnome-tweaks now equates "don't suspend on lid close" with "don't lock on lid close" (security issue)
Package: gnome-tweaks Version: 3.30.2-1 Severity: grave Tags: security Recently, disabling the setting "Suspend when laptop lid is closed" seems to have started preventing *any* action on lid close, including locking the screen; disabling that setting adds a startup file to run /usr/lib/gnome-tweak-tool/gnome-tweak-tool-lid-inhibitor, which inhibits *any* action on the lid switch. This is a security issue. I disable suspend on lid close, but I *always* need the screen to lock when I close the lid. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gnome-tweaks depends on: ii gir1.2-glib-2.01.58.3-2 ii gir1.2-gnomedesktop-3.03.30.2-4 ii gir1.2-gtk-3.0 3.24.3-1 ii gir1.2-notify-0.7 0.7.7-4 ii gir1.2-pango-1.0 1.42.4-6 ii gir1.2-soup-2.42.64.2-2 ii gnome-settings-daemon 3.30.2-1 ii gnome-shell-common 3.30.2-1 ii gsettings-desktop-schemas 3.28.1-1 ii mutter-common 3.30.2-4 ii python33.7.2-1 ii python3-gi 3.30.4-1 gnome-tweaks recommends no packages. gnome-tweaks suggests no packages. -- no debconf information
Bug#919912: knxd: FTBFS in sid (dh_install: missing files)
Package: src:knxd
Version: 0.14.29-1
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in sid but it failed:
[...]
debian/rules build-arch
dh build-arch
dh_update_autotools_config -a
dh_autoreconf -a
find ! -ipath "./debian/*" -a ! \( -path '*/.git/*' -o -path '*/.hg/*'
-o -path '*/.bzr/*' -o -path '*/.svn/*' -o -path '*/CVS/*' \) -a -type f -exec
md5sum {} + -o -type l -printf "symlink %p
" > debian/autoreconf.before
grep -q ^XDT_ configure.ac
autoreconf -f -i
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'
[... snipped ...]
make[5]: Nothing to be done for 'install-exec-am'.
make[5]: Leaving directory '/<>/src/examples'
make[4]: Leaving directory '/<>/src/examples'
make[4]: Entering directory '/<>/src'
make[5]: Entering directory '/<>/src'
make[5]: Nothing to be done for 'install-exec-am'.
make[5]: Nothing to be done for 'install-data-am'.
make[5]: Leaving directory '/<>/src'
make[4]: Leaving directory '/<>/src'
make[3]: Leaving directory '/<>/src'
Making install in systemd
make[3]: Entering directory '/<>/systemd'
make[4]: Entering directory '/<>/systemd'
/bin/mkdir -p '/<>/debian/tmp/etc'
/usr/bin/install -c -m 644 knxd.conf '/<>/debian/tmp/etc'
/bin/mkdir -p '/<>/debian/tmp/usr/lib/systemd/system/'
/usr/bin/install -c -m 644 knxd.service knxd.socket
'/<>/debian/tmp/usr/lib/systemd/system/'
/bin/mkdir -p '/<>/debian/tmp/usr/lib/sysusers.d/'
/usr/bin/install -c -m 644 sysusers.d/knxd.conf
'/<>/debian/tmp/usr/lib/sysusers.d/'
make[4]: Leaving directory '/<>/systemd'
make[3]: Leaving directory '/<>/systemd'
make[2]: Leaving directory '/<>'
make[1]: Leaving directory '/<>'
debian/rules override_dh_install
make[1]: Entering directory '/<>'
cp debian/knxd.install.in debian/knxd.install
grep -qs 'HAVE_SYSTEMD_TRUE.*#' config.status || cat
debian/knxd.install.systemd >> debian/knxd.install
test -e systemd/knxd.socket && cp systemd/knxd.socket debian/knxd.socket
test -e systemd/knxd.service && cp systemd/knxd.service debian/knxd.service
dh_install
dh_install: Cannot find (any matches for) "/lib/*" (tried in ., debian/tmp)
dh_install: knxd missing files: /lib/*
install -d debian/knxd//usr/bin
cp --reflink=auto -a debian/tmp/usr/bin/knxd debian/knxd//usr/bin/
install -d debian/knxd//usr/lib
cp --reflink=auto -a debian/tmp/usr/lib/knxd_args debian/knxd//usr/lib/
dh_install: missing files, aborting
install -d debian/.debhelper/generated/knxd
install -d debian/.debhelper/generated/knxd-tools
install -d debian/.debhelper/generated/knxd-dev
make[1]: *** [debian/rules:27: override_dh_install] Error 25
make[1]: Leaving directory '/<>'
make: *** [debian/rules:14: binary-arch] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-arch subprocess returned
exit status 2
The build was made in my autobuilder with "dpkg-buildpackage -B" on amd64
and it also fails here:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/knxd.html
(at least on arm64 at the time of writing this) and also here:
https://buildd.debian.org/status/package.php?p=knxd
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#917493: Bug #917493 in fenix marked as pending
Control: tag -1 pending Hello, Bug #917493 in fenix reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/games-team/fenix/commit/dd9057c3f20c60483cdb8aae27f0679cd5c176da Do not compile anything when building only architecture-independent packages. Closes: #917493 Reported by:Santiago Vila (this message was generated automatically) -- Greetings https://bugs.debian.org/917493
Processed: Bug #917493 in fenix marked as pending
Processing control commands: > tag -1 pending Bug #917493 [src:fenix] fenix: FTBFS when built with dpkg-buildpackage -A Added tag(s) pending. -- 917493: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917493 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: libconfig-model-backend-yaml-perl: fails to upgrade from 'stretch' - trying to overwrite /usr/share/man/man3/Config::Model::Backend::Yaml.3pm.gz
Processing control commands: > affects -1 + libconfig-model-perl Bug #919909 [libconfig-model-backend-yaml-perl] libconfig-model-backend-yaml-perl: fails to upgrade from 'stretch' - trying to overwrite /usr/share/man/man3/Config::Model::Backend::Yaml.3pm.gz Added indication that 919909 affects libconfig-model-perl -- 919909: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919909 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#919909: libconfig-model-backend-yaml-perl: fails to upgrade from 'stretch' - trying to overwrite /usr/share/man/man3/Config::Model::Backend::Yaml.3pm.gz
Package: libconfig-model-backend-yaml-perl Version: 2.133-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: affects -1 + libconfig-model-perl Hi, during a test with piuparts I noticed your package fails to upgrade from 'stretch'. It installed fine in 'stretch', then the upgrade to 'buster' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Selecting previously unselected package libconfig-model-backend-yaml-perl. Preparing to unpack .../047-libconfig-model-backend-yaml-perl_2.133-1_all.deb ... Unpacking libconfig-model-backend-yaml-perl (2.133-1) ... dpkg: error processing archive /tmp/apt-dpkg-install-T8rg5D/047-libconfig-model-backend-yaml-perl_2.133-1_all.deb (--unpack): trying to overwrite '/usr/share/man/man3/Config::Model::Backend::Yaml.3pm.gz', which is also in package libconfig-model-perl 2.097-2 cheers, Andreas libconfig-model-perl_2.133-1.log.gz Description: application/gzip
Bug#919907: ntopng FTBFS with ndpi 2.6
Source: ntopng Version: 2.4+dfsg1-4 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ntopng.html ... g++ -g -Wall -I/build/1st/ntopng-3.2+dfsg1 -I/build/1st/ntopng-3.2+dfsg1/include -I/usr/local/include -D_FILE_OFFSET_BITS=64 -I/usr/include/hiredis -I/usr/include/hiredis -I/build/1st/ntopng-3.2+dfsg1/third-party/mongoose -I/usr/include/json-c -I/usr/include/ndpi/libndpi -I/build/1st/ntopng-3.2+dfsg1/third-party/LuaJIT-2.1.0-beta3/src -isystem /usr/include/mit-krb5 -I/usr/include/pgm-5.2 -I/usr/lib/x86_64-linux-gnu/pgm-5.2/include -I/usr/include/mariadb -I/usr/include/mariadb/mysql -Wdate-time -D_FORTIFY_SOURCE=2 -I/build/1st/ntopng-3.2+dfsg1 -I/build/1st/ntopng-3.2+dfsg1/include -I/usr/local/include -I/build/1st/ntopng-3.2+dfsg1/third-party/http-client-c/src/ -I/usr/include/openssl -DDATA_DIR='"/usr/share"' -I/build/1st/ntopng-3.2+dfsg1/third-party/libgeohash -I/build/1st/ntopng-3.2+dfsg1/third-party/patricia -g -O2 -ffile-prefix-map=/build/1st/ntopng-3.2+dfsg1=. -fstack-protector-strong -Wformat -Werror=format-security -c src/AlertCounter.cpp -o src/AlertCounter.o In file included from src/AlertCounter.cpp:22: /build/1st/ntopng-3.2+dfsg1/include/ntop_includes.h:107:10: fatal error: ndpi_main.h: No such file or directory #include "ndpi_main.h" ^ compilation terminated. make[2]: *** [Makefile:153: src/AlertCounter.o] Error 1
Bug#919905: node-istanbul: FTBFS in sid
Package: src:node-istanbul Version: 0.4.5+ds-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 dh_autoreconf -i debian/rules override_dh_auto_build make[1]: Entering directory '/<>/node-istanbul-0.4.5+ds' mkdir -p lib/assets/vendor test -f /usr/share/javascript/prettify/prettify.js make[1]: *** [debian/rules:15: override_dh_auto_build] Error 1 make[1]: Leaving directory '/<>/node-istanbul-0.4.5+ds' 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 "dpkg-buildpackage -A" and it also fails here: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-istanbul.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.
Processed: Claiming bug 891297
Processing commands for cont...@bugs.debian.org: > owner 891297 po...@debian.org Bug #891297 [src:gnome-keyring] gnome-keyring: Incomplete debian/copyright? Owner recorded as po...@debian.org. > user debian-rele...@lists.debian.org Setting user to debian-rele...@lists.debian.org (was po...@debian.org). > usertags 891297 + bsp-2019-01-ca-montreal There were no usertags set. Usertags are now: bsp-2019-01-ca-montreal. > End of message, stopping processing here. Please contact me if you need assistance. -- 891297: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891297 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 919877
Processing commands for cont...@bugs.debian.org: > tags 919877 + buster sid Bug #919877 [src:ruby-sprite-factory] ruby-sprite-factory: FTBFS (failing test) Added tag(s) sid and buster. > thanks Stopping processing here. Please contact me if you need assistance. -- 919877: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919877 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#919902: exim4-config: fails to upgrade from 'stretch': option "hosts_try_dane" unknown
Package: exim4-config Version: 4.92~RC4-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: affects -1 + exim4-daemon-light Hi, during a test with piuparts I noticed your package fails to upgrade from 'stretch'. It installed fine in 'stretch', then the upgrade to 'buster' fails. >From the attached log (scroll to the bottom...): Setting up exim4-config (4.92~RC4-2) ... Installing new version of config file /etc/exim4/conf.d/acl/30_exim4-config_check_rcpt ... Installing new version of config file /etc/exim4/conf.d/acl/40_exim4-config_check_data ... Installing new version of config file /etc/exim4/conf.d/main/01_exim4-config_listmacrosdefs ... Installing new version of config file /etc/exim4/conf.d/main/02_exim4-config_options ... Installing new version of config file /etc/exim4/conf.d/router/200_exim4-config_primary ... Installing new version of config file /etc/exim4/conf.d/transport/30_exim4-config_remote_smtp ... Installing new version of config file /etc/exim4/conf.d/transport/30_exim4-config_remote_smtp_smarthost ... Installing new version of config file /etc/exim4/exim4.conf.template ... 2019-01-18 08:14:02 Exim configuration error in line 833 of /var/lib/exim4/config.autogenerated.tmp: option "hosts_try_dane" unknown Invalid new configfile /var/lib/exim4/config.autogenerated.tmp, not installing /var/lib/exim4/config.autogenerated.tmp to /var/lib/exim4/config.autogenerated dpkg: error processing package exim4-config (--configure): subprocess installed post-installation script returned error exit status 1 cheers, Andreas exim4-daemon-light_4.92~RC4-2.log.gz Description: application/gzip
