Processed: found 918443 in 2.9.11~20110321-13
Processing commands for cont...@bugs.debian.org: > found 918443 2.9.11~20110321-13 Bug #918443 [src:sl-modem] sl-modem: ftbfs on i386: undefined reference to `minor' Marked as found in versions sl-modem/2.9.11~20110321-13. > thanks Stopping processing here. Please contact me if you need assistance. -- 918443: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918443 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#917788: libmedc11: Overwrites a file from libmedc1v5
On Sat, Jan 05, 2019 at 11:10:52PM +0100, Mattia Rizzolo wrote: > On Sat, Jan 05, 2019 at 09:53:13PM +0100, Gilles Filippini wrote: >... > > > Incidentally, I think that would also cover the just openend #918372, > > > as with a Conflicts the libgmsh3 package from testing woudln't be > > > installable, so it would force an upgrade to the version in unstable, > > > making the test pass. > > > > Here I'm not sure. I think the problem is that libmed1v5 and libmedc1v5 > > from the broken med-fichier 4.0.0+repack-1 are still present into > > unstable. Is there a way to have them removed? > > He also said this. > However, I think that -generally, at least- the presence of cruft > packages in the archive should not be an excuse, and upgrades like the > one debci is trying to emulate should just work. >... The problem is not the presence of a cruft package in general. The problem is that there was one completely broken version of a package, that was fixed by removing/renaming this package. debci is trying to install a known-broken cruft package that will never migrate to testing (due to it being cruft). The actual bug is that debci considers such cruft packages still part of the source package, so the upgrade that is actually tested for gmsh is to the known-broken old med-fichier 4.0.0+repack-1. > regards, > Mattia Rizzolo 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
Processed: closing 918026
Processing commands for cont...@bugs.debian.org: > close 918026 Bug #918026 [ruby-sinatra-contrib] ruby-sinatra-contrib: uninstallable; depends on versions not present in the archive Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 918026: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918026 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: fixed 918026 in 2.0.5-2
Processing commands for cont...@bugs.debian.org: > fixed 918026 2.0.5-2 Bug #918026 [ruby-sinatra-contrib] ruby-sinatra-contrib: uninstallable; depends on versions not present in the archive Marked as fixed in versions ruby-sinatra/2.0.5-2. > thanks Stopping processing here. Please contact me if you need assistance. -- 918026: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918026 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#916020: marked as done (smp-utils FTBFS with glibc 2.28)
Your message dated Sun, 06 Jan 2019 07:19:29 +
with message-id
and subject line Bug#916020: fixed in smp-utils 0.98-2
has caused the Debian Bug report #916020,
regarding smp-utils 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.)
--
916020: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916020
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: smp-utils
Version: 0.98-1
Severity: serious
Tags: ftbfs buster sid
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/smp-utils.html
...
smp_lin_bsg.c: In function 'open_lin_bsg_device':
smp_lin_bsg.c:230:21: warning: implicit declaration of function 'makedev'
[-Wimplicit-function-declaration]
makedev(maj, min));
^~~
...
smp_mptctl_io.c: In function 'chk_mpt_device':
smp_mptctl_io.c:66:52: warning: implicit declaration of function 'major'
[-Wimplicit-function-declaration]
if ((S_ISCHR(st.st_mode)) && (MPT_DEV_MAJOR == major(st.st_rdev))) {
^
smp_mptctl_io.c:67:31: warning: implicit declaration of function 'minor'; did
you mean 'mknod'? [-Wimplicit-function-declaration]
if ((MPT_DEV_MINOR == minor(st.st_rdev)) ||
^
...
smp_aac_io.c: In function 'chk_aac_device':
smp_aac_io.c:90:35: warning: implicit declaration of function 'makedev'
[-Wimplicit-function-declaration]
if(mknod(dev_name,S_IFCHR,makedev(aacDevMjr,aacDevMnr))) {
^~~
smp_aac_io.c:101:53: warning: implicit declaration of function 'major'
[-Wimplicit-function-declaration]
if ((S_ISCHR(st.st_mode)) && (aacDevMjr ==(int) major(st.st_rdev))) {
^
smp_aac_io.c:102:33: warning: implicit declaration of function 'minor'; did you
mean 'mknod'? [-Wimplicit-function-declaration]
if ((aacDevMnr == (int) minor(st.st_rdev)))
...
gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -I ../include
-D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -Wall -W -g -O2
-ffile-prefix-map=/build/1st/smp-utils-0.98=. -fstack-protector-strong -Wformat
-Werror=format-security -c -o smp_conf_general.o smp_conf_general.c
/bin/bash ../libtool --tag=CC --mode=link gcc -I ../include
-D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -Wall -W -g -O2
-ffile-prefix-map=/build/1st/smp-utils-0.98=. -fstack-protector-strong -Wformat
-Werror=format-security -Wl,-z,relro -Wl,-z,now -o smp_conf_general
smp_conf_general.o ../lib/libsmputils1.la
libtool: link: gcc -I ../include -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64
-Wall -W -g -O2 -ffile-prefix-map=/build/1st/smp-utils-0.98=.
-fstack-protector-strong -Wformat -Werror=format-security -Wl,-z -Wl,relro
-Wl,-z -Wl,now -o .libs/smp_conf_general smp_conf_general.o
../lib/.libs/libsmputils1.so
/usr/bin/ld: ../lib/.libs/libsmputils1.so: undefined reference to `minor'
/usr/bin/ld: ../lib/.libs/libsmputils1.so: undefined reference to `major'
/usr/bin/ld: ../lib/.libs/libsmputils1.so: undefined reference to `makedev'
collect2: error: ld returned 1 exit status
make[3]: *** [Makefile:564: smp_conf_general] Error 1
--- End Message ---
--- Begin Message ---
Source: smp-utils
Source-Version: 0.98-2
We believe that the bug you reported is fixed in the latest version of
smp-utils, 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 916...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Ritesh Raj Sarraf (supplier of updated smp-utils 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 12:35:38 +0530
Source: smp-utils
Binary: smp-utils
Architecture: source amd64
Version: 0.98-2
Distribution: unstable
Urgency: medium
Maintainer: Ritesh Raj Sarraf
Changed-By: Ritesh Raj Sarraf
Description:
smp-utils - SAS Expander (SMP) utilities for SAS/SATA disk arrays
Closes: 916020
Changes:
smp-utils (0.98-2) unstable; urgency=medium
.
* Switch repository to Salsa
* Add patch to fix build failure for implicit function declaration
(Closes: #916020)
*
Bug#917562: marked as done (umd breaks node-caniuse-lite build, provide cjs)
Your message dated Sun, 06 Jan 2019 07:04:20 + with message-id and subject line Bug#917562: fixed in node-ramda 0.26.1+dfsg-2 has caused the Debian Bug report #917562, regarding umd breaks node-caniuse-lite build, provide cjs 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.) -- 917562: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917562 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: node-caniuse-lite version: 1.0.3915+dfsg-1 severity: grave Justification: Makes it unusable Control: block 837463 by -1 Control: tag -1 help When trying to build autoprefixer.js which build depends on node-caniuse-lite, I got this error and upon inspection I found data/features directory is missing. ERROR in /usr/lib/nodejs/caniuse-lite/data/features.js Module not found: Error: Can't resolve './features/aac' in '/usr/lib/nodejs/caniuse-lite/data' @ /usr/lib/nodejs/caniuse-lite/data/features.js 1:22-47 @ /usr/lib/nodejs/caniuse-lite/dist/unpacker/features.js @ /usr/lib/nodejs/caniuse-lite/dist/unpacker/index.js @ /usr/lib/nodejs/autoprefixer/lib/autoprefixer.js I was not able to figure out why this is not working now. Need help. signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: node-ramda Source-Version: 0.26.1+dfsg-2 We believe that the bug you reported is fixed in the latest version of node-ramda, 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. Pirate Praveen (supplier of updated node-ramda 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, 06 Jan 2019 12:14:44 +0530 Source: node-ramda Binary: node-ramda Architecture: source Version: 0.26.1+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Pirate Praveen Description: node-ramda - practical functional library for JavaScript programmers Closes: 917562 Changes: node-ramda (0.26.1+dfsg-2) unstable; urgency=medium . * Team upload . [ Sruthi Chandran ] * Bump debhelper compatibility level to 11 . [ Pirate Praveen ] * Drop umd and build cjs (Closes: #917562) * Embed babel-plugin-annotate-pure-calls module (build dependency) * Bump Standards-Version to 4.3.0 (no changes needed) Checksums-Sha1: 7829f7ab7c32c7dac270cbdfd3b74c25808926bf 2010 node-ramda_0.26.1+dfsg-2.dsc 369af8b7caf4c357673f8303af9c592fae9a798f 4664 node-ramda_0.26.1+dfsg-2.debian.tar.xz 8fde814262eefc2a73812fb5fd36c20929a5111e 7979 node-ramda_0.26.1+dfsg-2_source.buildinfo Checksums-Sha256: 50ec20ccc94dacea5c4a195e312c6395ed6bbf2462631e1d63b5f43723050b0f 2010 node-ramda_0.26.1+dfsg-2.dsc 1d7d8c137036b4cc89d05876d3873625f9acee347845663a4645e2a6d0ab6d31 4664 node-ramda_0.26.1+dfsg-2.debian.tar.xz 6bf72ff8e900b73d1890d912b88ad636584d21e7f9f681f08f6684d5cfa4863b 7979 node-ramda_0.26.1+dfsg-2_source.buildinfo Files: 0322edcbaf32ea48edd04454905bb1ac 2010 javascript optional node-ramda_0.26.1+dfsg-2.dsc 240a8bd388b8d0f18f4b0f4b62973398 4664 javascript optional node-ramda_0.26.1+dfsg-2.debian.tar.xz 76a5d359fce00771c7b16336b5836c32 7979 javascript optional node-ramda_0.26.1+dfsg-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEKnl0ri/BUtd4Z9pKzh+cZ0USwioFAlwxp1wACgkQzh+cZ0US wirgow/+OC2Z5UuE8lxP3l9f6EvW7Ut3blH7+t6ELR55MzYvWgPwlKHFiXxuy5rW y8yaB7z4P81A1DQajFEcfoG5wU+Ho5s/mmFFI+svOiK602gSbv1+A0ppmBSOmJH4 KSYpClSEXqce4XwgOoZDO6RrwM3Y4Z8LzcLaVjmtOwDNVGRUKhbpotpWasIzodWh xuMTul1El4uel+ke27PkzUA1ynZihZceykP1SaDGPgNxMrgymerAiGvr6EWxXFSt HqujeIdXSgiHPdm5ngJvVaqZVtS2GV6WW0Jn8hdajDQ5O7+Cgip32rrwBsRncAz6 +jf+54Upq+zaYhCOGWQz7r3JQvnCMwZzZPkdOAFgyn08zfVskw3Wn/SiqHG8co1i HSBKO3cwsK5EL1R11w0PxTrgL8ZVlyF1a9P9SBrVRcOYc8OBGH9JYoyAONGQWD0D hNS+IX7ukNfJsNjMKt/A0ZSXwU21Pk77XCYgu9FefiOYU3Z3wkgCFGn3FoTRhCYu vIsqvYkrssbw3flHY3yomaI5rufxp4eLMfVdbG1syB2/FZXA0WDsmGyJFTQbCmxN yGE80K1P63qoIV67YQ+mE8Hv/J+ciw+CgtOuXBU+i9I8UCXZFMtSOUdW2kUxY/7B asiyTzYCGcpbWK4GhltwK4W4o47OIS1rGfrRh8HHa+xv52YB6nA= =04Fc -END PGP SIGNATURE End Message ---
Processed: severity of 918316 is important
Processing commands for cont...@bugs.debian.org: > severity 918316 important Bug #918316 [src:nocache] nocache: FTBFS in sid Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 918316: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918316 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: affects 917562
Processing commands for cont...@bugs.debian.org: > affects 917562 node-caniuse-lite Bug #917562 [node-ramda] data/features directory is missing in node-caniuse-lite Added indication that 917562 affects node-caniuse-lite > thanks Stopping processing here. Please contact me if you need assistance. -- 917562: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917562 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 917562 to node-ramda
Processing commands for cont...@bugs.debian.org: > reassign 917562 node-ramda Bug #917562 [node-caniuse-lite] data/features directory is missing in node-caniuse-lite Bug reassigned from package 'node-caniuse-lite' to 'node-ramda'. No longer marked as found in versions node-caniuse-lite/1.0.3915+dfsg-1. Ignoring request to alter fixed versions of bug #917562 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 917562: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917562 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: retitle 917562 to umd breaks node-caniuse-lite build, provide cjs
Processing commands for cont...@bugs.debian.org: > retitle 917562 umd breaks node-caniuse-lite build, provide cjs Bug #917562 [node-ramda] data/features directory is missing in node-caniuse-lite Changed Bug title to 'umd breaks node-caniuse-lite build, provide cjs' from 'data/features directory is missing in node-caniuse-lite'. > thanks Stopping processing here. Please contact me if you need assistance. -- 917562: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917562 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#918447: pelican: fails to build: wrong dependency?
Source: pelican Version: 3.7.1+dfsg-2 Severity: serious Tags: ftbfs X-Debbugs-CC: stapp...@debian.org pelican fails to build. I notice that a dependency on python3-feedparser was added, but pelican appears to be a Python2 package. Build log https://launchpad.net/ubuntu/+source/pelican/3.7.1+dfsg-2/+build/16238504 Thanks, Jeremy Bicha
Bug#918088: Acknowledgement (autofs-ldap: automount dies with SIGABRT after libkrb5-3 upgrade - "(k5_mutex_lock: Assertion `r == 0' failed.)")
On Fri, 4 Jan 2019 19:24:52 -0500 Greg Hudson wrote: > krb5_mcc_start_seq_get() is in the traceback, so the memory cache change > is a clear candidate for the bug. I can't find anything wrong with the > code, though. From the stack trace, there appears to be a memory ccache > on the list with an invalid mutex, but I don't see any way of getting > into that state. I found the bug. krb5_mcc_ptcursor_next() is not increasing the refcount on the caches it yields. The per-type cursor is also subject to badness if what would have been the next cache is destroyed before it is yielded, either by a separate thread or by a single thread doing cache destroy operations in the midst of the iteration. My plan is to backport commit 49bb627fed70c5258c151c5135ac3d95ed1ee55d from the master branch and issue new 1.15.x and 1.16.x releases. Apologies for the release branch regression; in hindsight I should have decided that commit 146dadec8fe7ccc4149eb2e3f577cc320aee6efb was too big to backport.
Bug#918445: libgccjit-9-doc: missing Conflicts: libgccjit-8-doc
Package: libgccjit-9-doc Version: 9-20190103-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts libgccjit-9-doc needs to conflict with libgccjit-8-doc like it does with the older ones. Andreas libgccjit-8-doc=8.2.0-13_libgccjit-9-doc=9-20190103-1.log.gz Description: application/gzip
Processed: found 866122 in 4.9.130-2, found 866122 in 4.19.13-1, found 866122 in 4.20-1~exp1
Processing commands for cont...@bugs.debian.org: > found 866122 4.9.130-2 Bug #866122 [src:linux] FP register corruption on ppc64el with lock elision Bug #866371 [src:linux] FP register corruption on ppc64el with lock elision Marked as found in versions linux/4.9.130-2. Marked as found in versions linux/4.9.130-2. > found 866122 4.19.13-1 Bug #866122 [src:linux] FP register corruption on ppc64el with lock elision Bug #866371 [src:linux] FP register corruption on ppc64el with lock elision Marked as found in versions linux/4.19.13-1. Marked as found in versions linux/4.19.13-1. > found 866122 4.20-1~exp1 Bug #866122 [src:linux] FP register corruption on ppc64el with lock elision Bug #866371 [src:linux] FP register corruption on ppc64el with lock elision Marked as found in versions linux/4.20-1~exp1. Marked as found in versions linux/4.20-1~exp1. > thanks Stopping processing here. Please contact me if you need assistance. -- 866122: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866122 866371: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866371 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#917990: closed by Ole Streicher (Bug#917990: fixed in plplot 5.14.0+dfsg-2)
Control: found -1 5.14.0+dfsg-2 On 2019-01-02 14:24, Debian Bug Tracking System wrote: > This is an automatic notification regarding your Bug report > which was filed against the libplplotada1-dev package: > > #917990: libplplotada1-dev: fails to upgrade from 'testing' - trying to > overwrite /usr/lib/x86_64-linux-gnu/ada/adalib/plplotada/plplot_auxiliary.ali > > It has been closed by Ole Streicher . The Breaks+Replaces against libplplot-ada-dev are incorrectly versioned, that needs to be (<< 5.14) Andreas
Processed: Re: Bug#917990 closed by Ole Streicher (Bug#917990: fixed in plplot 5.14.0+dfsg-2)
Processing control commands:
> found -1 5.14.0+dfsg-2
Bug #917990 {Done: Ole Streicher } [libplplotada1-dev]
libplplotada1-dev: fails to upgrade from 'testing' - trying to overwrite
/usr/lib/x86_64-linux-gnu/ada/adalib/plplotada/plplot_auxiliary.ali
Marked as found in versions plplot/5.14.0+dfsg-2; no longer marked as fixed in
versions plplot/5.14.0+dfsg-2 and reopened.
--
917990: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917990
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#918398: marked as done (wml: missing dependencies on libio-all-perl and liblist-moreutils-perl)
Your message dated Sun, 06 Jan 2019 03:20:39 + with message-id and subject line Bug#918398: fixed in wml 2.12.0~ds1-4 has caused the Debian Bug report #918398, regarding wml: missing dependencies on libio-all-perl and liblist-moreutils-perl 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.) -- 918398: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918398 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wml Version: 2.12.0~ds1-3 Severity: serious Control: affects -1 src:doc-debian https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/doc-debian.html ... wml -i bug-pkgreport-opts.inc -q bug-log-access.wml >bug-log-access.html Can't locate IO/All.pm in @INC (you may need to install the IO::All module) (@INC contains: /usr/share/wml /usr/lib/x86_64-linux-gnu/wml /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.28.1 /usr/local/share/perl/5.28.1 /usr/lib/x86_64-linux-gnu/perl5/5.28 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.28 /usr/share/perl/5.28 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base .) at /usr/share/wml/TheWML/CmdLine/IO.pm line 6. BEGIN failed--compilation aborted at /usr/share/wml/TheWML/CmdLine/IO.pm line 6. Compilation failed in require at /usr/share/wml/TheWML/CmdLine/Base.pm line 6. BEGIN failed--compilation aborted at /usr/share/wml/TheWML/CmdLine/Base.pm line 6. Compilation failed in require at /usr/share/perl/5.28/parent.pm line 16. BEGIN failed--compilation aborted at /usr/share/wml/TheWML/Frontends/Wml/Runner.pm line 18. Compilation failed in require at /usr/bin/wml line 45. BEGIN failed--compilation aborted at /usr/bin/wml line 45. make[1]: *** [Makefile:40: bug-log-access.html] Error 2 --- End Message --- --- Begin Message --- Source: wml Source-Version: 2.12.0~ds1-4 We believe that the bug you reported is fixed in the latest version of wml, 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 918...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Axel Beckert (supplier of updated wml 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, 06 Jan 2019 03:49:04 +0100 Source: wml Binary: wml Architecture: source all Version: 2.12.0~ds1-4 Distribution: unstable Urgency: medium Maintainer: Axel Beckert Changed-By: Axel Beckert Description: wml- off-line HTML generation toolkit Closes: 918398 Changes: wml (2.12.0~ds1-4) unstable; urgency=medium . * Add missing dependencies on libio-all-perl and liblist-moreutils-perl. (Closes: #918398) Thanks Adrian Bunk! * Drop all *-dev build-dependencies. No more needed since actually the switch to "Architecture: all". * Drop "" from all build-dependencies for which CMake checks. * Add all (test-suite-related) build-dependencies which are checked by CMake, namely libbit-vector-perl and liblist-moreutils-perl (not yet, see https://github.com/thewml/website-meta-language/pull/23). * override_dh_auto_test: For now, check both, DEB_BUILD_OPTIONS and DEB_BUILD_PROFILES, see https://lists.debian.org/debian-devel/2019/01/msg00039.html ff. Checksums-Sha1: a0a66f2a230c251df5d5e352ff1bb62da60e4dfc 2357 wml_2.12.0~ds1-4.dsc d5a0fb204b42757658a196da5da0fcd5b905a07a 30100 wml_2.12.0~ds1-4.debian.tar.xz e8b99dd3c5f6033046ab78763c07a550b55e48d3 468864 wml_2.12.0~ds1-4_all.deb d73866b17b95da127adaf1d1d1fe8ef76b211a6a 10159 wml_2.12.0~ds1-4_amd64.buildinfo Checksums-Sha256: 0254b77c637e1e27e108b5bd5a13d9b87b2f68948c787c78217940e7b414fe39 2357 wml_2.12.0~ds1-4.dsc 9b510c8f7d93b9904dcb7ea38ddad126e0d051add7b01e5975ba99d1ceb4 30100 wml_2.12.0~ds1-4.debian.tar.xz 778659a3bb46287780bc9850a37b7dd8aafae089c3af7fdc0d6c157874b948ef 468864 wml_2.12.0~ds1-4_all.deb ea648e16217e6e404eced4eef4d1d1c3a939dd9bbd3981fbd2a6e6266767c775 10159 wml_2.12.0~ds1-4_amd64.buildinfo Files: 3c2a8d3e6722d0107c405ca03c4c8d5b 2357 web optional wml_2.12.0~ds1-4.dsc c5a008517f810b2b853e96878639de31 30100 web optional wml_2.12.0~ds1-4.debian.tar.xz 11141e5aca0ec4c0e3d2e33c291c318f 468864 web optional wml_2.12.0~ds1-4_all.deb 1d9557df79c44bb1273dcc53cf3d6dd0 10159 web
Processed (with 1 error): Re: dpkg: warning: unable to delete old directory '/usr/lib/python3.6/
Processing control commands: > forcemerge -1 918098 Bug #918182 [python3-lib2to3] dpkg: warning: unable to delete old directory '/usr/lib/python3.6/ Unable to merge bugs because: package of #918098 is 'src:python3-stdlib-extensions' not 'python3-lib2to3' Failed to forcibly merge 918182: Did not alter merged bugs. -- 918098: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918098 918182: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918182 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#918443: sl-modem: ftbfs on i386: undefined reference to `minor'
Source: sl-modem Version: 2.9.11~20110321-14 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Hi, sl-modem FTBFS on i386 (but succeeds on amd64): [...] gcc -m32 -o slmodemd modem_main.o modem_cmdline.o modem.o modem_datafile.o modem_at.o modem_timer.o modem_pack.o modem_ec.o modem_comp.o modem_param.o modem_debug.o homolog_data.o dp_sinus.o dp_dummy.o dsplibs.o sysdep_common.o -Wl,-z,relro -lasound /usr/bin/ld: modem_main.o: in function `mdm_device_setup': ./modem/modem_main.c:642: undefined reference to `minor' collect2: error: ld returned 1 exit status make[3]: *** [Makefile:48: slmodemd] Error 1 Full log attached. Check https://bugs.debian.org/908160 for the solution of the same issue in another package. Andreas sl-modem_2.9.11~20110321-14.log.gz Description: application/gzip
Bug#918440: marked as done (jabref: FTBFS (Could not resolve all files for configuration ':antlr4'))
Your message dated Sun, 06 Jan 2019 02:46:19 + with message-id and subject line Bug#918440: fixed in jabref 3.8.2+ds-11 has caused the Debian Bug report #918440, regarding jabref: FTBFS (Could not resolve all files for configuration ':antlr4') 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.) -- 918440: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918440 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:jabref Version: 3.8.2+ds-10 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep dh build-indep --buildsystem=gradle dh_update_autotools_config -i -O--buildsystem=gradle dh_autoreconf -i -O--buildsystem=gradle dh_auto_configure -i -O--buildsystem=gradle dh_auto_build -i -O--buildsystem=gradle mkdir -p .gradle/init.d cp /usr/share/gradle-debian-helper/init.gradle .gradle/init.d/ gradle --info --console plain --offline --stacktrace --no-daemon --refresh-dependencies --gradle-user-home .gradle -Duser.home=. -Duser.name=debian -Ddebian.package=jabref -Dfile.encoding=UTF-8 jar Initialized native services in: /<>/jabref-3.8.2+ds/.gradle/native To honour the JVM settings for this build a new JVM will be forked. Please consider using the daemon: https://docs.gradle.org/4.4.1/userguide/gradle_daemon.html. Starting process 'Gradle build daemon'. Working directory: /<>/jabref-3.8.2+ds/.gradle/daemon/4.4.1 Command: /usr/lib/jvm/java-11-openjdk-amd64/bin/java -Xbootclasspath/a:/usr/share/java/gradle-helper-hook.jar:/usr/share/java/maven-repo-helper.jar -Dfile.encoding=UTF-8 -Duser.country=US -Duser.language=en -Duser.variant -cp /usr/share/gradle/lib/gradle-launcher-4.4.1.jar org.gradle.launcher.daemon.bootstrap.GradleDaemon 4.4.1 Successfully started process 'Gradle build daemon' An attempt to start the daemon took 1.216 secs. [... snipped ...] at org.gradle.launcher.daemon.server.DaemonStateCoordinator$1.run(DaemonStateCoordinator.java:295) at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:63) at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:46) at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:55) Caused by: org.gradle.internal.resolve.ModuleVersionNotFoundException: Could not find com.ibm.icu:icu4j:debian. Searched in the following locations: file:/usr/share/maven-repo/com/ibm/icu/icu4j/debian/icu4j-debian.pom file:/usr/share/maven-repo/com/ibm/icu/icu4j/debian/icu4j-debian.jar Required by: project : > org.antlr:antlr4:debian at org.gradle.internal.resolve.result.DefaultBuildableComponentResolveResult.notFound(DefaultBuildableComponentResolveResult.java:38) at org.gradle.api.internal.artifacts.ivyservice.ivyresolve.RepositoryChainComponentMetaDataResolver.resolveModule(RepositoryChainComponentMetaDataResolver.java:108) at org.gradle.api.internal.artifacts.ivyservice.ivyresolve.RepositoryChainComponentMetaDataResolver.resolve(RepositoryChainComponentMetaDataResolver.java:63) at org.gradle.api.internal.artifacts.ivyservice.resolveengine.ComponentResolversChain$ComponentMetaDataResolverChain.resolve(ComponentResolversChain.java:93) at org.gradle.api.internal.artifacts.ivyservice.clientmodule.ClientModuleResolver.resolve(ClientModuleResolver.java:48) at org.gradle.api.internal.artifacts.ivyservice.resolveengine.graph.builder.ComponentState.resolve(ComponentState.java:157) at org.gradle.api.internal.artifacts.ivyservice.resolveengine.graph.builder.ComponentState.getMetaData(ComponentState.java:168) at org.gradle.api.internal.artifacts.ivyservice.resolveengine.graph.builder.EdgeState.calculateTargetConfigurations(EdgeState.java:134) at org.gradle.api.internal.artifacts.ivyservice.resolveengine.graph.builder.EdgeState.attachToTargetConfigurations(EdgeState.java:105) at org.gradle.api.internal.artifacts.ivyservice.resolveengine.graph.builder.DependencyGraphBuilder.attachToTargetRevisionsSerially(DependencyGraphBuilder.java:239) at org.gradle.api.internal.artifacts.ivyservice.resolveengine.graph.builder.DependencyGraphBuilder.resolveEdges(DependencyGraphBuilder.java:229) at
Processed: Bug #918440 in jabref marked as pending
Processing control commands: > tag -1 pending Bug #918440 [src:jabref] jabref: FTBFS (Could not resolve all files for configuration ':antlr4') Added tag(s) pending. -- 918440: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918440 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#918440: Bug #918440 in jabref marked as pending
Control: tag -1 pending Hello, Bug #918440 in jabref 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/java-team/jabref/commit/fd1d50cec53f3125fd5a47414702329f221f9715 Add build dependency on libicu4j-java. Closes: #918440 Thanks: Santiago Vila for the bug report. (this message was generated automatically) -- Greetings https://bugs.debian.org/918440
Bug#914357: Cannot reproduce this problem
Santiago Vila writes: > On Sun, Jan 06, 2019 at 12:16:21AM +0800, Yanhao Mo wrote: > >> I cannnot reproduce this problem in my pbuilder environment. >> Could you please help reverify if this problem still exists? > > Note: I reported this because it failed for me once and I saw that it also > failed in reproducible-builds. > > I've now triggered a rebuild on reproducible-builds in all architectures. > > In a while you can see the results here: > > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/hotspot.html > > If all of them build ok, you should probably ask for a retry here: > > https://buildd.debian.org/status/package.php?p=hotspot > > If not, we will see what can we do. > > Thanks. Hmm, the reproducible building is still failed. And I still cannot reproduce the error. Accordding to the error message: > XPASS : TestKallsyms::testProc() 'kallsyms.parseMapping(path)' returned TRUE > unexpectedly. () > Loc: > [/<>/hotspot-1.1.0+git20180816/3rdparty/perfparser/tests/auto/kallsyms/tst_kallsyms.cpp(138)] > QDEBUG : TestKallsyms::testParseErrors() "Mapping is empty." > QDEBUG : TestKallsyms::testParseErrors() "Invalid address: this" > QDEBUG : TestKallsyms::testParseErrors() "No such file or directory" I guess that because the build environments used by tests.reproducible-builds.org dosen't have a normal /proc/kallsyms file. Or maybe it doesn't have such file at all. Could you please help verify that? Very appreciated. And if what I'm guessing is true for the /proc/kallsyms file. Then what operations am I excepted to take? Should I just disable the specific testcase?
Bug#918329: apriltag ftbfs on release architectures
Control: reassign -1 src:apriltag Control: tags -1 + moreinfo thanks please attach the preprocessed source, it's incomplete as a GCC report. On 05.01.19 19:59, Adrian Bunk wrote: > Control: reassign -1 gcc-8 > Control: affects -1 src:apriltag > > On Sat, Jan 05, 2019 at 08:44:32AM +0100, Matthias Klose wrote: >> Package: src:apriltag >> Version: 0.10.0-1 >> Severity: serious >> Tags: sid buster >> >> apriltag ftbfs on release architectures, where it built before. Looks like >> the >> build system is exaggerating optimization flags, using -O4 nonsense. > > -O4 is treated as -O3, so that is harmless. > > The actual bug is in gcc, and also present with -O2. > > Compiling a not too complicated C file that assigns different buildtime > integer constants to all 65k members of an array is not very fast on amd64 > (this is Coffee Lake at 4.7 GHz): > > $ time gcc -c -O2 tagCircle49h12.c > > real0m51.891s > user0m51.775s > sys 0m0.116s > $ > > > But gcc speed on some architectures like ppc64el or arm64 is really pathetic: > > (sid_ppc64el-dchroot)bunk@plummer:~/build/apriltag-0.10.0$ time gcc -c -O2 > tagCircle49h12.c > > real150m38.971s > user149m18.332s > sys 0m57.941s > (sid_ppc64el-dchroot)bunk@plummer:~/build/apriltag-0.10.0$ > > (sid_arm64-dchroot)bunk@amdahl:~/build/apriltag-0.10.0$ time gcc -c -O2 > tagCircle49h12.c > > real216m20.266s > user215m47.712s > sys 0m2.172s > (sid_arm64-dchroot)bunk@amdahl:~/build/apriltag-0.10.0$ > > > cu > Adrian >
Processed: Re: Bug#918329: apriltag ftbfs on release architectures
Processing control commands: > reassign -1 src:apriltag Bug #918329 [gcc-8] apriltag ftbfs on release architectures Bug reassigned from package 'gcc-8' to 'src:apriltag'. Ignoring request to alter found versions of bug #918329 to the same values previously set Ignoring request to alter fixed versions of bug #918329 to the same values previously set > tags -1 + moreinfo Bug #918329 [src:apriltag] apriltag ftbfs on release architectures Added tag(s) moreinfo. -- 918329: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918329 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Still needs to be fixed in buster/sid, reopening to avoid duplicate reports
Processing commands for cont...@bugs.debian.org:
> reopen 884155
Bug #884155 {Done: Pirate Praveen } [src:node-object-path]
FTBFS with chai 4.1.2 in experimental
Bug #917757 {Done: Pirate Praveen } [src:node-object-path]
node-object-path: FTBFS: tests failed
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions node-object-path/0.11.4-1.
No longer marked as fixed in versions node-object-path/0.11.4-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
884155: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884155
917757: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917757
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#918441: node-websocket: FTBFS (ld: cannot find -lnode)
Package: src:node-websocket Version: 1.0.23-3.1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep dh build-indep --with nodejs dh_update_autotools_config -i dh_auto_configure -i debian/rules override_dh_auto_build-indep make[1]: Entering directory '/<>' dh_auto_build make -j1 make[2]: Entering directory '/<>' node-gyp configure build gyp info it worked if it ends with ok gyp info using node-gyp@3.8.0 gyp info using node@8.11.2 | linux | x64 gyp info spawn /usr/bin/python2 [... snipped ...] ^~~ ../src/bufferutil.cc:104:7: note: here case 2: *((unsigned char*)to+1) = *((unsigned char*)from+1) ^ *((unsigned char*)mask+1); ^~~~ ../src/bufferutil.cc:104:39: warning: this statement may fall through [-Wimplicit-fallthrough=] case 2: *((unsigned char*)to+1) = *((unsigned char*)from+1) ^ *((unsigned char*)mask+1); ^~~ ../src/bufferutil.cc:105:7: note: here case 1: *((unsigned char*)to ) = *((unsigned char*)from ) ^ *((unsigned char*)mask); ^~~~ ../src/bufferutil.cc: In static member function 'static Nan::NAN_METHOD_RETURN_TYPE BufferUtil::Unmask(Nan::NAN_METHOD_ARGS_TYPE)': ../src/bufferutil.cc:78:41: warning: this statement may fall through [-Wimplicit-fallthrough=] case 3: *((unsigned char*)from+2) = *((unsigned char*)from+2) ^ ((unsigned char*)mask)[2]; ~~^~~ ../src/bufferutil.cc:79:7: note: here case 2: *((unsigned char*)from+1) = *((unsigned char*)from+1) ^ ((unsigned char*)mask)[1]; ^~~~ ../src/bufferutil.cc:79:41: warning: this statement may fall through [-Wimplicit-fallthrough=] case 2: *((unsigned char*)from+1) = *((unsigned char*)from+1) ^ ((unsigned char*)mask)[1]; ~~^~~ ../src/bufferutil.cc:80:7: note: here case 1: *((unsigned char*)from ) = *((unsigned char*)from ) ^ ((unsigned char*)mask)[0]; ^~~~ SOLINK_MODULE(target) Release/obj.target/bufferutil.node /usr/bin/ld: cannot find -lnode collect2: error: ld returned 1 exit status make[3]: *** [bufferutil.target.mk:131: Release/obj.target/bufferutil.node] Error 1 make[3]: Leaving directory '/<>/build' gyp ERR! build error gyp ERR! stack Error: `make` failed with exit code: 2 gyp ERR! stack at ChildProcess.onExit (/usr/share/node-gyp/lib/build.js:262:23) gyp ERR! stack at emitTwo (events.js:126:13) gyp ERR! stack at ChildProcess.emit (events.js:214:7) gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:198:12) gyp ERR! System Linux 4.9.0-8-amd64 gyp ERR! command "/usr/bin/node" "/usr/bin/node-gyp" "configure" "build" gyp ERR! cwd /<> gyp ERR! node -v v8.11.2 gyp ERR! node-gyp -v v3.8.0 gyp ERR! not ok make[2]: *** [Makefile:2: all] Error 1 make[2]: Leaving directory '/<>' dh_auto_build: make -j1 returned exit code 2 make[1]: *** [debian/rules:44: override_dh_auto_build-indep] Error 2 make[1]: Leaving directory '/<>' make: *** [debian/rules:14: 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" but it also fails here: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-websocket.html where you can get a full build log if you need it. If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks.
Bug#884155: Still needs to be fixed in buster/sid, reopening to avoid duplicate reports
reopen 884155 thanks
Bug#918440: jabref: FTBFS (Could not resolve all files for configuration ':antlr4')
Package: src:jabref Version: 3.8.2+ds-10 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep dh build-indep --buildsystem=gradle dh_update_autotools_config -i -O--buildsystem=gradle dh_autoreconf -i -O--buildsystem=gradle dh_auto_configure -i -O--buildsystem=gradle dh_auto_build -i -O--buildsystem=gradle mkdir -p .gradle/init.d cp /usr/share/gradle-debian-helper/init.gradle .gradle/init.d/ gradle --info --console plain --offline --stacktrace --no-daemon --refresh-dependencies --gradle-user-home .gradle -Duser.home=. -Duser.name=debian -Ddebian.package=jabref -Dfile.encoding=UTF-8 jar Initialized native services in: /<>/jabref-3.8.2+ds/.gradle/native To honour the JVM settings for this build a new JVM will be forked. Please consider using the daemon: https://docs.gradle.org/4.4.1/userguide/gradle_daemon.html. Starting process 'Gradle build daemon'. Working directory: /<>/jabref-3.8.2+ds/.gradle/daemon/4.4.1 Command: /usr/lib/jvm/java-11-openjdk-amd64/bin/java -Xbootclasspath/a:/usr/share/java/gradle-helper-hook.jar:/usr/share/java/maven-repo-helper.jar -Dfile.encoding=UTF-8 -Duser.country=US -Duser.language=en -Duser.variant -cp /usr/share/gradle/lib/gradle-launcher-4.4.1.jar org.gradle.launcher.daemon.bootstrap.GradleDaemon 4.4.1 Successfully started process 'Gradle build daemon' An attempt to start the daemon took 1.216 secs. [... snipped ...] at org.gradle.launcher.daemon.server.DaemonStateCoordinator$1.run(DaemonStateCoordinator.java:295) at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:63) at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:46) at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:55) Caused by: org.gradle.internal.resolve.ModuleVersionNotFoundException: Could not find com.ibm.icu:icu4j:debian. Searched in the following locations: file:/usr/share/maven-repo/com/ibm/icu/icu4j/debian/icu4j-debian.pom file:/usr/share/maven-repo/com/ibm/icu/icu4j/debian/icu4j-debian.jar Required by: project : > org.antlr:antlr4:debian at org.gradle.internal.resolve.result.DefaultBuildableComponentResolveResult.notFound(DefaultBuildableComponentResolveResult.java:38) at org.gradle.api.internal.artifacts.ivyservice.ivyresolve.RepositoryChainComponentMetaDataResolver.resolveModule(RepositoryChainComponentMetaDataResolver.java:108) at org.gradle.api.internal.artifacts.ivyservice.ivyresolve.RepositoryChainComponentMetaDataResolver.resolve(RepositoryChainComponentMetaDataResolver.java:63) at org.gradle.api.internal.artifacts.ivyservice.resolveengine.ComponentResolversChain$ComponentMetaDataResolverChain.resolve(ComponentResolversChain.java:93) at org.gradle.api.internal.artifacts.ivyservice.clientmodule.ClientModuleResolver.resolve(ClientModuleResolver.java:48) at org.gradle.api.internal.artifacts.ivyservice.resolveengine.graph.builder.ComponentState.resolve(ComponentState.java:157) at org.gradle.api.internal.artifacts.ivyservice.resolveengine.graph.builder.ComponentState.getMetaData(ComponentState.java:168) at org.gradle.api.internal.artifacts.ivyservice.resolveengine.graph.builder.EdgeState.calculateTargetConfigurations(EdgeState.java:134) at org.gradle.api.internal.artifacts.ivyservice.resolveengine.graph.builder.EdgeState.attachToTargetConfigurations(EdgeState.java:105) at org.gradle.api.internal.artifacts.ivyservice.resolveengine.graph.builder.DependencyGraphBuilder.attachToTargetRevisionsSerially(DependencyGraphBuilder.java:239) at org.gradle.api.internal.artifacts.ivyservice.resolveengine.graph.builder.DependencyGraphBuilder.resolveEdges(DependencyGraphBuilder.java:229) at org.gradle.api.internal.artifacts.ivyservice.resolveengine.graph.builder.DependencyGraphBuilder.traverseGraph(DependencyGraphBuilder.java:143) at org.gradle.api.internal.artifacts.ivyservice.resolveengine.graph.builder.DependencyGraphBuilder.resolve(DependencyGraphBuilder.java:109) at org.gradle.api.internal.artifacts.ivyservice.resolveengine.DefaultArtifactDependencyResolver.resolve(DefaultArtifactDependencyResolver.java:90) at org.gradle.api.internal.artifacts.ivyservice.DefaultConfigurationResolver.resolveGraph(DefaultConfigurationResolver.java:146) at org.gradle.api.internal.artifacts.ivyservice.ShortCircuitEmptyConfigurationResolver.resolveGraph(ShortCircuitEmptyConfigurationResolver.java:73) at org.gradle.api.internal.artifacts.ivyservice.ErrorHandlingConfigurationResolver.resolveGraph(ErrorHandlingConfigurationResolver.java:66) at
Bug#918442: perl6-readline: FTBFS (Operation "cmp": no method found)
Package: src:perl6-readline Version: 0.1.4-3 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep dh build-indep --with perl6 dh_update_autotools_config -i dh_autoreconf -i dh_perl6_test -i /usr/bin/prove6 -l t/01-load.t .. ok t/02-base.t .. ok All tests successful. Files=2, Tests=18, 41 wallclock secs Result: PASS create-stamp debian/debhelper-build-stamp fakeroot debian/rules binary-indep dh binary-indep --with perl6 dh_testroot -i dh_prep -i dh_install -i dh_perl6_depsfile -i Operation "cmp": no method found, left argument in overloaded package Debian::Dependency, right argument in overloaded package Debian::Dependency at /usr/bin/dh_perl6_depsfile line 39. make: *** [debian/rules:4: binary-indep] Error 25 dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess returned exit status 2 The build was made in my autobuilder with "dpkg-buildpackage -A" but it also fails here: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/perl6-readline.html where you can get a full build log if you need it. If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks.
Bug#918439: cockpit: FTBFS (failing tests)
Package: src:cockpit Version: 184-1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep dh build-indep dh_update_autotools_config -i dh_autoreconf -i debian/rules override_dh_auto_configure make[1]: Entering directory '/<>' set -ex; if [ -d debian/git-patches ]; then \ git init; \ git config user.email "unu...@example.com"; git config user.name "Unused"; \ git config core.autocrlf false; git config core.safecrlf false && git config gc.auto 0; \ git add -f . && git commit -a -q -m "Base" && git tag -a initial --message="initial"; \ git am --whitespace=nowarn debian/git-patches/*.patch; \ touch -r $(git diff --name-only initial..HEAD) .git; \ fi [... snipped ...] # ./tools/tap-driver --test-name dist/kubernetes/scripts/test-volumes.html --log-file dist/kubernetes/scripts/test-volumes.log --trs-file dist/kubernetes/scripts/test-volumes.trs --color-tests no --enable-hard-errors yes --expect-failure no -- /usr/bin/python3 ./test/common/tap-cdp --strip=./ -- ./test-server ./dist/kubernetes/scripts/test-volumes.html 1..0 # skip web browser not found SKIP: dist/machines/test-machines = # ./tools/tap-driver --test-name dist/machines/test-machines.html --log-file dist/machines/test-machines.log --trs-file dist/machines/test-machines.trs --color-tests no --enable-hard-errors yes --expect-failure no -- /usr/bin/python3 ./test/common/tap-cdp --strip=./ -- ./test-server ./dist/machines/test-machines.html 1..0 # skip web browser not found SKIP: dist/networkmanager/test-utils # ./tools/tap-driver --test-name dist/networkmanager/test-utils.html --log-file dist/networkmanager/test-utils.log --trs-file dist/networkmanager/test-utils.trs --color-tests no --enable-hard-errors yes --expect-failure no -- /usr/bin/python3 ./test/common/tap-cdp --strip=./ -- ./test-server ./dist/networkmanager/test-utils.html 1..0 # skip web browser not found SKIP: dist/storaged/test-util = # ./tools/tap-driver --test-name dist/storaged/test-util.html --log-file dist/storaged/test-util.log --trs-file dist/storaged/test-util.trs --color-tests no --enable-hard-errors yes --expect-failure no -- /usr/bin/python3 ./test/common/tap-cdp --strip=./ -- ./test-server ./dist/storaged/test-util.html 1..0 # skip web browser not found Testsuite summary for Cockpit 184 # TOTAL: 882 # PASS: 806 # SKIP: 45 # XFAIL: 0 # FAIL: 31 # XPASS: 0 # ERROR: 0 See ./test-suite.log Please report to de...@lists.cockpit-project.org make[4]: *** [Makefile:8135: test-suite.log] Error 1 make[4]: Leaving directory '/<>' make[3]: *** [Makefile:8243: check-TESTS] Error 2 make[3]: Leaving directory '/<>' make[2]: *** [Makefile:8805: check-am] Error 2 make[2]: Leaving directory '/<>' make[1]: *** [Makefile:8807: check] Error 2 make[1]: Leaving directory '/<>' dh_auto_test: make -j1 check VERBOSE=1 returned exit code 2 make: *** [debian/rules:18: 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" but it also fails here: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/cockpit.html where you can get a full build log if you need it. If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks.
Bug#918437: ring-clojure: FTBFS randomly due to filesystem ordering
Package: src:ring-clojure Version: 1.6.2-1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep dh build-indep --with javahelper --with maven_repo_helper dh_update_autotools_config -i dh_autoreconf -i jh_linkjars -i debian/rules override_jh_build make[1]: Entering directory '/<>' jar cf ring-core.jar -C ring-core/src . jar cf ring-servlet.jar -C ring-servlet/src . jar cf ring-jetty-adapter.jar -C ring-jetty-adapter/src . make[1]: Leaving directory '/<>' debian/rules override_dh_auto_test make[1]: Entering directory '/<>' find ring-core/test -name '*.clj' | \ xargs --verbose clojure -cp ring-core.jar:/usr/share/java/clojure.jar:/usr/share/java/tools.reader.jar:/usr/share/java/ring-codec.jar:/usr/share/java/commons-io.jar:/usr/share/java/commons-fileupload.jar:/usr/share/java/clj-time.jar:/usr/share/java/crypto-random.jar:/usr/share/java/crypto-equality.jar clojure -cp ring-core.jar:/usr/share/java/clojure.jar:/usr/share/java/tools.reader.jar:/usr/share/java/ring-codec.jar:/usr/share/java/commons-io.jar:/usr/share/java/commons-fileupload.jar:/usr/share/java/clj-time.jar:/usr/share/java/crypto-random.jar:/usr/share/java/crypto-equality.jar ring-core/test/ring/middleware/multipart_params/test/request_context.clj ring-core/test/ring/middleware/multipart_params/test/temp_file.clj ring-core/test/ring/middleware/multipart_params/test/byte_array.clj ring-core/test/ring/middleware/session/test/memory.clj ring-core/test/ring/middleware/session/test/cookie.clj ring-core/test/ring/middleware/test/session.clj ring-core/test/ring/middleware/test/flash.clj ring-core/test/ring/middleware/test/keyword_params.clj ring-core/test/ring/middleware/test/multipart_params.clj ring-core/test/ring/middleware/test/file_info.clj ring-core/test/ring/middleware/test/nested_params.clj ring-core/test/ring/middleware/test/params.clj ring-core/test/ring/middleware/test/ file.clj ring-core/test/ring/middleware/test/head.clj ring-core/test/ring/middleware/test/content_type.clj ring-core/test/ring/middleware/test/resource.clj ring-core/test/ring/middleware/test/cookies.clj ring-core/test/ring/middleware/test/not_modified.clj ring-core/test/ring/util/test/time.clj ring-core/test/ring/util/test/mime_type.clj ring-core/test/ring/util/test/io.clj ring-core/test/ring/util/test/request.clj ring-core/test/ring/util/test/response.clj ring-core/test/ring/core/test/protocols.clj Exception in thread "main" java.lang.NoClassDefFoundError: javax/servlet/http/HttpServletRequest, compiling:(ring/middleware/multipart_params.clj:54:20) at clojure.lang.Compiler.analyzeSeq(Compiler.java:7010) at clojure.lang.Compiler.analyze(Compiler.java:6773) at clojure.lang.Compiler.analyzeSeq(Compiler.java:6991) at clojure.lang.Compiler.analyze(Compiler.java:6773) at clojure.lang.Compiler.analyze(Compiler.java:6729) at clojure.lang.Compiler$BodyExpr$Parser.parse(Compiler.java:6102) at clojure.lang.Compiler$LetExpr$Parser.parse(Compiler.java:6420) at clojure.lang.Compiler.analyzeSeq(Compiler.java:7003) at clojure.lang.Compiler.analyze(Compiler.java:6773) at clojure.lang.Compiler.analyzeSeq(Compiler.java:6991) at clojure.lang.Compiler.analyze(Compiler.java:6773) at clojure.lang.Compiler.analyzeSeq(Compiler.java:6991) at clojure.lang.Compiler.analyze(Compiler.java:6773) at clojure.lang.Compiler.analyze(Compiler.java:6729) at clojure.lang.Compiler$IfExpr$Parser.parse(Compiler.java:2822) at clojure.lang.Compiler.analyzeSeq(Compiler.java:7003) at clojure.lang.Compiler.analyze(Compiler.java:6773) at clojure.lang.Compiler.access$300(Compiler.java:38) at clojure.lang.Compiler$LetExpr$Parser.parse(Compiler.java:6368) at clojure.lang.Compiler.analyzeSeq(Compiler.java:7003) at clojure.lang.Compiler.analyze(Compiler.java:6773) at clojure.lang.Compiler.analyzeSeq(Compiler.java:6991) at clojure.lang.Compiler.analyze(Compiler.java:6773) at clojure.lang.Compiler.analyze(Compiler.java:6729) at clojure.lang.Compiler$BodyExpr$Parser.parse(Compiler.java:6104) at clojure.lang.Compiler$FnMethod.parse(Compiler.java:5460) at clojure.lang.Compiler$FnExpr.parse(Compiler.java:4022) at clojure.lang.Compiler.analyzeSeq(Compiler.java:7001) at clojure.lang.Compiler.analyze(Compiler.java:6773) at clojure.lang.Compiler.analyzeSeq(Compiler.java:6991) at clojure.lang.Compiler.analyze(Compiler.java:6773) at clojure.lang.Compiler.access$300(Compiler.java:38) at clojure.lang.Compiler$DefExpr$Parser.parse(Compiler.java:596) at clojure.lang.Compiler.analyzeSeq(Compiler.java:7003) at
Bug#917788: libmedc11: Overwrites a file from libmedc1v5
On Sat, Jan 05, 2019 at 09:53:13PM +0100, Gilles Filippini wrote: > > > In this special case, you probably need to add > > > Breaks+Replaces: libmed1v5 (>= 4) > > > respectively > > > Breaks+Replaces: libmedc1v5 (>= 4) > > > since the versions before 4 should not have any file conflicts. > > > > Actually, I think Breaks+Replaces is wrong here. > > > > Breaks+Replaces allow for silent replacing of the old package, but here > > you need to forcefully remove it, which is what you'd use Conflicts for. > > As a data point, that what we usually use when renaming packages during > > ABI breaks like what has been done for #916881. > > I agree that Conflicts suits better regarding the need to forcibly > remove libmed1v5 / libmedc1v5 (= 4.0.0+repack-1). Apparently bunk disagrees with me and mentioned on IRC that it should be fine, and also: > > Incidentally, I think that would also cover the just openend #918372, > > as with a Conflicts the libgmsh3 package from testing woudln't be > > installable, so it would force an upgrade to the version in unstable, > > making the test pass. > > Here I'm not sure. I think the problem is that libmed1v5 and libmedc1v5 > from the broken med-fichier 4.0.0+repack-1 are still present into > unstable. Is there a way to have them removed? He also said this. However, I think that -generally, at least- the presence of cruft packages in the archive should not be an excuse, and upgrades like the one debci is trying to emulate should just work. Anyway, please consider holding on any upload, I'll try to do a few update tests locally tomorrow afternoon (CET). (bunk, anbe: feel free to chime in here) -- 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#918434: golint: FTBFS (failing tests)
Package: src:golint Version: 0.0+git20161013.3390df4-2 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-arch dh build-arch --buildsystem=golang --with=golang dh_update_autotools_config -a -O--buildsystem=golang dh_auto_configure -a -O--buildsystem=golang dh_auto_build -a -O--buildsystem=golang cd obj-x86_64-linux-gnu && go install -gcflags=all=\"-trimpath=/<>/golint-0.0\+git20161013.3390df4/obj-x86_64-linux-gnu/src\" -asmflags=all=\"-trimpath=/<>/golint-0.0\+git20161013.3390df4/obj-x86_64-linux-gnu/src\" -v -p 1 github.com/golang/lint github.com/golang/lint/golint errors internal/cpu internal/bytealg internal/race runtime/internal/atomic runtime/internal/sys runtime sync/atomic [... snipped ...] go/parser text/tabwriter go/printer container/heap encoding/binary math/rand math/big go/constant go/types bufio path regexp/syntax regexp net/url text/template/parse text/template go/doc log context os/exec go/build text/scanner golang.org/x/tools/go/gcimporter15 github.com/golang/lint flag github.com/golang/lint/golint dh_auto_test -a -O--buildsystem=golang cd obj-x86_64-linux-gnu && go test -vet=off -v -p 1 github.com/golang/lint github.com/golang/lint/golint === RUN TestAll --- FAIL: TestAll (0.04s) lint_test.go:94: Lint failed at errorf.go:29; /should replace.*t\.Error\(fmt\.Sprintf\(\.\.\.\)\).*t\.Errorf\(\.\.\.\)/ did not match lint_test.go:94: Lint failed at time.go:11; /Msec.*\*time.Duration/ did not match lint_test.go:94: Lint failed at time.go:13; /Secs.*time.Duration/ did not match lint_test.go:94: Lint failed at var-decl.go:18; /should.*\*http\.ServeMux.*inferred/ did not match lint_test.go:94: Lint failed at var-decl.go:74; /should omit.*io\.Writer/ did not match === RUN TestLine --- PASS: TestLine (0.00s) === RUN TestLintName --- PASS: TestLintName (0.00s) === RUN TestExportedType --- PASS: TestExportedType (0.00s) FAIL FAILgithub.com/golang/lint 0.043s ? github.com/golang/lint/golint [no test files] dh_auto_test: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 1 github.com/golang/lint github.com/golang/lint/golint returned exit code 1 make: *** [debian/rules:4: build-arch] Error 1 dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit status 2 The build was made in my autobuilder with "dpkg-buildpackage -B" but it also fails here: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golint.html where you can get a full build log if you need it. If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks.
Bug#918436: node-groove: FTBFS (ld: cannot find -lnode)
Package: src:node-groove
Version: 2.5.0-4
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-arch
dh build-arch --with nodejs
dh_update_autotools_config -a
debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
node-gyp configure build
gyp info it worked if it ends with ok
gyp info using node-gyp@3.8.0
gyp info using node@8.11.2 | linux | x64
gyp info spawn /usr/bin/python2
gyp info spawn args [ '/usr/share/node-gyp/gyp/gyp_main.py',
gyp info spawn args 'binding.gyp',
gyp info spawn args '-f',
gyp info spawn args 'make',
[... snipped ...]
../src/encoder.cc:339:39: warning: 'void node::FatalException(const
v8::TryCatch&)' is deprecated: Use FatalException(isolate, ...)
[-Wdeprecated-declarations]
node::FatalException(try_catch);
^
In file included from /usr/include/nodejs/src/node_buffer.h:25,
from ../src/encoder.cc:1:
/usr/include/nodejs/src/node.h:338:29: note: declared here
inline void FatalException(const v8::TryCatch& try_catch) {
^~
/usr/include/nodejs/src/node.h:87:42: note: in definition of macro
'NODE_DEPRECATED'
__attribute__((deprecated(message))) declarator
^~
../src/encoder.cc: In static member function 'static
Nan::NAN_METHOD_RETURN_TYPE GNEncoder::Detach(Nan::NAN_METHOD_ARGS_TYPE)':
../src/encoder.cc:367:31: warning: cast between incompatible function types
from 'void (*)(uv_work_t*)' {aka 'void (*)(uv_work_s*)'} to 'uv_after_work_cb'
{aka 'void (*)(uv_work_s*, int)'} [-Wcast-function-type]
(uv_after_work_cb)DetachAfter);
^~~
In file included from /usr/include/nodejs/src/node.h:63,
from /usr/include/nodejs/src/node_buffer.h:25,
from ../src/encoder.cc:1:
/usr/include/nodejs/deps/v8/include/v8.h: In instantiation of 'void
v8::PersistentBase::SetWeak(P*, typename v8::WeakCallbackInfo::Callback,
v8::WeakCallbackType) [with P = node::ObjectWrap; T = v8::Object; typename
v8::WeakCallbackInfo::Callback = void (*)(const
v8::WeakCallbackInfo&)]':
/usr/include/nodejs/src/node_object_wrap.h:85:78: required from here
/usr/include/nodejs/deps/v8/include/v8.h:9253:16: warning: cast between
incompatible function types from
'v8::WeakCallbackInfo::Callback' {aka 'void (*)(const
v8::WeakCallbackInfo&)'} to 'Callback' {aka 'void (*)(const
v8::WeakCallbackInfo&)'} [-Wcast-function-type]
reinterpret_cast(callback), type);
^~~~
/usr/include/nodejs/deps/v8/include/v8.h: In instantiation of 'void
v8::PersistentBase::SetWeak(P*, typename v8::WeakCallbackInfo::Callback,
v8::WeakCallbackType) [with P = Nan::ObjectWrap; T = v8::Object; typename
v8::WeakCallbackInfo::Callback = void (*)(const
v8::WeakCallbackInfo&)]':
/usr/include/nan_object_wrap.h:66:61: required from here
/usr/include/nodejs/deps/v8/include/v8.h:9253:16: warning: cast between
incompatible function types from
'v8::WeakCallbackInfo::Callback' {aka 'void (*)(const
v8::WeakCallbackInfo&)'} to 'Callback' {aka 'void (*)(const
v8::WeakCallbackInfo&)'} [-Wcast-function-type]
SOLINK_MODULE(target) Release/obj.target/groove.node
/usr/bin/ld: cannot find -lnode
collect2: error: ld returned 1 exit status
make[2]: *** [groove.target.mk:141: Release/obj.target/groove.node] Error 1
make[2]: Leaving directory '/<>/build'
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack at ChildProcess.onExit
(/usr/share/node-gyp/lib/build.js:262:23)
gyp ERR! stack at emitTwo (events.js:126:13)
gyp ERR! stack at ChildProcess.emit (events.js:214:7)
gyp ERR! stack at Process.ChildProcess._handle.onexit
(internal/child_process.js:198:12)
gyp ERR! System Linux 4.9.0-8-amd64
gyp ERR! command "/usr/bin/node" "/usr/bin/node-gyp" "configure" "build"
gyp ERR! cwd /<>
gyp ERR! node -v v8.11.2
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok
make[1]: *** [debian/rules:14: override_dh_auto_build] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:11: build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit
status 2
The build was made in my autobuilder with "dpkg-buildpackage -B"
but it also fails here:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-groove.html
where you can get a full build log if you need it.
If this is really a bug in one of the build-depends, please use reassign and
affects,
so that this is still visible in the BTS web page for this package.
Thanks.
Bug#918435: libgit-raw-perl: FTBFS (failing tests)
Package: src:libgit-raw-perl Version: 0.79-5 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-arch dh build-arch dh_update_autotools_config -a dh_autoreconf -a dh_auto_configure -a perl -I. Makefile.PL INSTALLDIRS=vendor "OPTIMIZE=-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" "LD=x86_64-linux-gnu-gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro" SSH2 support enabled SSL support disabled CURL support disabled Threads support enabled Checking if your kit is complete... Warning: the following files are missing in your kit: deps/libgit2/appveyor.yml deps/libgit2/AUTHORS [... snipped ...] ok 36 ok 37 ok 38 - An object of class 'Git::Raw::Rebase::Operation' isa 'Git::Raw::Rebase::Operation' ok 39 ok 40 ok 41 ok 42 ok 43 ok 44 ok 45 ok 46 ok 47 - An object of class 'Git::Raw::Rebase' isa 'Git::Raw::Rebase' ok 48 ok 49 ok 50 - An object of class 'Git::Raw::Index' isa 'Git::Raw::Index' 1..50 ok t/98-internal.t . ok 1 ok 2 ok 3 ok 4 1..4 ok t/99-cleanup.t .. ok 1 ok 2 ok 3 1..3 ok t/author-pod-coverage.t . skipped: these tests are for testing by the author t/author-pod-syntax.t ... skipped: these tests are for testing by the author t/release-check-manifest.t .. skipped: these tests are for release candidate testing Test Summary Report --- t/33-worktree.t (Wstat: 512 Tests: 11 Failed: 0) Non-zero exit status: 2 Parse errors: No plan found in TAP output Files=40, Tests=1667, 12 wallclock secs ( 0.48 usr 0.12 sys + 9.16 cusr 2.34 csys = 12.10 CPU) Result: FAIL Failed 1/40 test programs. 0/1667 subtests failed. make[1]: *** [Makefile:1290: test_dynamic] Error 255 make[1]: Leaving directory '/<>' dh_auto_test: make -j1 test TEST_VERBOSE=1 returned exit code 2 make: *** [debian/rules:4: build-arch] Error 2 dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit status 2 The build was made in my autobuilder with "dpkg-buildpackage -B" but it also fails here: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libgit-raw-perl.html where you can get a full build log if you need it. If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks.
Bug#906398: marked as done (projectreactor: FTBFS in buster/sid)
Your message dated Sun, 06 Jan 2019 00:04:17 + with message-id and subject line Bug#906398: fixed in jarjar 1.4+svn142-9 has caused the Debian Bug report #906398, regarding projectreactor: FTBFS in buster/sid to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 906398: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906398 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:projectreactor Version: 2.0.8-1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep dh build-indep --buildsystem=gradle --with maven_repo_helper dh_update_autotools_config -i -O--buildsystem=gradle dh_auto_configure -i -O--buildsystem=gradle debian/rules override_dh_auto_build make[1]: Entering directory '/<>' dh_auto_build -- :reactor-core:install :reactor-net:install :reactor-bus:install :reactor-stream:install -x javadoc mkdir -p .gradle/init.d cp /usr/share/gradle-debian-helper/init.gradle .gradle/init.d/ gradle --info --console plain --offline --stacktrace --no-daemon --refresh-dependencies --gradle-user-home .gradle -Duser.home=. -Duser.name=debian -Ddebian.package=projectreactor -Dfile.encoding=UTF-8 :reactor-core:install :reactor-net:install :reactor-bus:install :reactor-stream:install -x javadoc Initialized native services in: /<>/.gradle/native WARNING: An illegal reflective access operation has occurred WARNING: Illegal reflective access by org.gradle.internal.reflect.JavaMethod (file:/usr/share/gradle/lib/gradle-base-services-3.4.1.jar) to method java.lang.ClassLoader.getPackages() WARNING: Please consider reporting this to the maintainers of org.gradle.internal.reflect.JavaMethod [... snipped ...] at org.gradle.launcher.daemon.server.exec.ForwardClientInput.execute(ForwardClientInput.java:72) at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:120) at org.gradle.launcher.daemon.server.exec.LogAndCheckHealth.execute(LogAndCheckHealth.java:50) at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:120) at org.gradle.launcher.daemon.server.exec.LogToClient.doBuild(LogToClient.java:60) at org.gradle.launcher.daemon.server.exec.BuildCommandOnly.execute(BuildCommandOnly.java:36) at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:120) at org.gradle.launcher.daemon.server.exec.EstablishBuildEnvironment.doBuild(EstablishBuildEnvironment.java:72) at org.gradle.launcher.daemon.server.exec.BuildCommandOnly.execute(BuildCommandOnly.java:36) at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:120) at org.gradle.launcher.daemon.server.exec.StartBuildOrRespondWithBusy$1.run(StartBuildOrRespondWithBusy.java:50) at org.gradle.launcher.daemon.server.DaemonStateCoordinator$1.run(DaemonStateCoordinator.java:297) at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:63) at org.gradle.internal.concurrent.StoppableExecutorImpl$1.run(StoppableExecutorImpl.java:46) Caused by: org.gradle.api.internal.tasks.compile.CompilationFailedException: Compilation failed; see the compiler error output for details. at org.gradle.api.internal.tasks.compile.JdkJavaCompiler.execute(JdkJavaCompiler.java:48) at org.gradle.api.internal.tasks.compile.JdkJavaCompiler.execute(JdkJavaCompiler.java:33) at org.gradle.api.internal.tasks.compile.NormalizingJavaCompiler.delegateAndHandleErrors(NormalizingJavaCompiler.java:99) at org.gradle.api.internal.tasks.compile.NormalizingJavaCompiler.execute(NormalizingJavaCompiler.java:52) at org.gradle.api.internal.tasks.compile.NormalizingJavaCompiler.execute(NormalizingJavaCompiler.java:37) at org.gradle.api.internal.tasks.compile.CleaningJavaCompilerSupport.execute(CleaningJavaCompilerSupport.java:35) at org.gradle.api.internal.tasks.compile.CleaningJavaCompilerSupport.execute(CleaningJavaCompilerSupport.java:25) at org.gradle.api.tasks.compile.JavaCompile.performCompilation(JavaCompile.java:209) at org.gradle.api.tasks.compile.JavaCompile.compile(JavaCompile.java:190) at org.gradle.api.tasks.compile.JavaCompile.compile(JavaCompile.java:135)
Bug#914357: Cannot reproduce this problem
On Sun, Jan 06, 2019 at 12:16:21AM +0800, Yanhao Mo wrote: > I cannnot reproduce this problem in my pbuilder environment. > Could you please help reverify if this problem still exists? Note: I reported this because it failed for me once and I saw that it also failed in reproducible-builds. I've now triggered a rebuild on reproducible-builds in all architectures. In a while you can see the results here: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/hotspot.html If all of them build ok, you should probably ask for a retry here: https://buildd.debian.org/status/package.php?p=hotspot If not, we will see what can we do. Thanks.
Bug#916060: tuxmath: Starts and immediately closes
This patch fixes issue with deprecated rsvg_handle_get_desc now return
NULL value.
Tuxmath now runs fine for me.
diff -Nru t4kcommon-0.1.1/debian/changelog t4kcommon-0.1.1/debian/changelog
--- t4kcommon-0.1.1/debian/changelog 2018-05-31 22:16:05.0 +1000
+++ t4kcommon-0.1.1/debian/changelog 2019-01-05 23:19:03.0 +1100
@@ -1,3 +1,10 @@
+t4kcommon (0.1.1-4.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix loading each frame from SVG sprites (Closes: #916060)
+
+ -- Chris Donoghue Sat, 05 Jan 2019 23:19:03 +1100
+
t4kcommon (0.1.1-4) unstable; urgency=medium
* d/control:
diff -Nru t4kcommon-0.1.1/debian/patches/loadsvgsprite_numframe_load t4kcommon-0.1.1/debian/patches/loadsvgsprite_numframe_load
--- t4kcommon-0.1.1/debian/patches/loadsvgsprite_numframe_load 1970-01-01 10:00:00.0 +1000
+++ t4kcommon-0.1.1/debian/patches/loadsvgsprite_numframe_load 2019-01-05 23:19:03.0 +1100
@@ -0,0 +1,32 @@
+Description: fix loading each frame from SVG sprites
+ rsvg_handle_get_desc returns null so next sscanf segfaults. Use instead iterating
+ up from zero for id frame%d
+Author: cdono...@gmail.com
+Origin: other
+Forwarded: no
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/src/t4k_loaders.c
b/src/t4k_loaders.c
+@@ -213,14 +213,13 @@
+ new_sprite = malloc(sizeof(sprite));
+ new_sprite->default_img = render_svg_from_handle(file_handle, width, height, "#default");
+
+- /* get number of frames from description */
+- sscanf(rsvg_handle_get_desc(file_handle), "%d", _sprite->num_frames);
+- DEBUGMSG(debug_loaders, "load_svg_sprite(): loading %d frames\n", new_sprite->num_frames);
+-
+- for(i = 0; i < new_sprite->num_frames; i++)
+- {
+-sprintf(lay_name, "#frame%d", i);
+-new_sprite->frame[i] = render_svg_from_handle(file_handle, width, height, lay_name);
++ /* get number of frames directly. End when #frame doesn't exist */
++ new_sprite->num_frames = 0;
++ while(1) {
++sprintf(lay_name, "#frame%d", new_sprite->num_frames);
++if ( ! (rsvg_handle_has_sub(file_handle, lay_name)) ) break;
++new_sprite->frame[new_sprite->num_frames] = render_svg_from_handle(file_handle, width, height, lay_name);
++new_sprite->num_frames++;
+ }
+
+ g_object_unref(file_handle);
diff -Nru t4kcommon-0.1.1/debian/patches/series t4kcommon-0.1.1/debian/patches/series
--- t4kcommon-0.1.1/debian/patches/series 2018-05-31 22:14:02.0 +1000
+++ t4kcommon-0.1.1/debian/patches/series 2019-01-05 23:05:28.0 +1100
@@ -1 +1,2 @@
libpng16.patch
+loadsvgsprite_numframe_load
Bug#906398: Bug #906398 in jarjar marked as pending
Control: tag -1 pending Hello, Bug #906398 in jarjar 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/java-team/jarjar/commit/ccaf9a36d3997189b62e9a40467d8c7808ef0f5f Depend on libasm-java instead of libasm4-java (Closes: #906398) (this message was generated automatically) -- Greetings https://bugs.debian.org/906398
Processed: Bug #906398 in jarjar marked as pending
Processing control commands: > tag -1 pending Bug #906398 [libjarjar-java] projectreactor: FTBFS in buster/sid Added tag(s) pending. -- 906398: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906398 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#906398: projectreactor: FTBFS in buster/sid
Processing control commands: > reassign -1 libjarjar-java Bug #906398 [src:projectreactor] projectreactor: FTBFS in buster/sid Bug reassigned from package 'src:projectreactor' to 'libjarjar-java'. No longer marked as found in versions projectreactor/2.0.8-1. Ignoring request to alter fixed versions of bug #906398 to the same values previously set > affects -1 src:projectreactor Bug #906398 [libjarjar-java] projectreactor: FTBFS in buster/sid Added indication that 906398 affects src:projectreactor -- 906398: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906398 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#906398: projectreactor: FTBFS in buster/sid
Control: reassign -1 libjarjar-java Control: affects -1 src:projectreactor This is an issue with the jarjar Ant task that no longer works but I fail to understand exactly why. The classes in the disruptor jar should be relocated to reactor.jarjar.com.lmax.disruptor but it doesn't happen and this leads to compilation errors. It looks like the error was triggered by the upload of disruptor/3.4.2-1, projectreactor builds fine with the version 3.3.11-1. Rebuilding jarjar with ASM 7 instead of 5 fixes the issue. I guess something specific to Java 9+ was introduced when building disruptor 3.4.2-1 and it derailed the jarjar processing. Emmanuel Bourg
Bug#918426: jupyter-notebook FTBFS: AttributeError in examples/Notebook/Connecting with the Qt Console.ipynb
Source: jupyter-notebook Version: 5.4.1-1 Severity: serious Tags: ftbfs Some recent change in unstable makes jupyter-notebook FTBFS: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/jupyter-notebook.html ... updating environment: 32 added, 0 changed, 0 removed reading sources... [ 3%] changelog reading sources... [ 6%] comms reading sources... [ 9%] config_overview reading sources... [ 12%] contributing reading sources... [ 15%] development_faq reading sources... [ 18%] development_release reading sources... [ 21%] examples/Notebook/Connecting with the Qt Console Notebook error: AttributeError in examples/Notebook/Connecting with the Qt Console.ipynb: 'NoneType' object has no attribute 'argv' make[1]: *** [debian/rules:124: override_dh_auto_build] Error 2
Bug#901952: anyone want to craft a patch?
tags 901952 +help thanks I question whether this bug is really release-critical, since the only cases of it I've heard about so far are the two instances pointed to in this bug log where pristine-tar is being used across distributions and versions... I've not seen the behavior in any of my own packaging work. However, if someone wants to work out a way to patch current tar such that it mimics the old behavior when necessary to unpack an older tarball without breaking anything else, I'd be happy to merge such a patch. I mean something like what was done to fix #897653. Bdale
Bug#918424: node-end-of-stream FTBFS with nodejs 10.15.0
Source: node-end-of-stream Version: 1.4.0-1 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-end-of-stream.html ... debian/rules override_dh_auto_test make[1]: Entering directory '/build/1st/node-end-of-stream-1.4.0' nodejs test.js assert.js:350 throw err; ^ AssertionError [ERR_ASSERTION]: The expression evaluated to a falsy value: assert(!!err) at WriteStream. (/build/1st/node-end-of-stream-1.4.0/test.js:12:2) at WriteStream.f (/usr/lib/nodejs/once.js:25:25) at WriteStream.onfinish (/build/1st/node-end-of-stream-1.4.0/index.js:30:27) at WriteStream.emit (events.js:182:13) at finishMaybe (_stream_writable.js:641:14) at stream._final (_stream_writable.js:619:5) at WriteStream._final (internal/fs/streams.js:264:3) at callFinal (_stream_writable.js:612:10) at process._tickCallback (internal/process/next_tick.js:63:19) at Function.Module.runMain (internal/modules/cjs/loader.js:745:11) make[1]: *** [debian/rules:13: override_dh_auto_test] Error 1
Bug#918423: node-builtin-modules FTBFS with nodejs 10.15.0
Source: node-builtin-modules Version: 2.0.0-1 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-builtin-modules.html ... 0 passing (68ms) 1 failing 1) test: AssertionError [ERR_ASSERTION]: Got unwanted exception. Actual message: "Cannot find module 'config'" at Context. (test.js:8:9) at callFn (/usr/lib/nodejs/mocha/lib/runnable.js:354:21) at Test.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:346:7) at Runner.runTest (/usr/lib/nodejs/mocha/lib/runner.js:442:10) at /usr/lib/nodejs/mocha/lib/runner.js:560:12 at next (/usr/lib/nodejs/mocha/lib/runner.js:356:14) at /usr/lib/nodejs/mocha/lib/runner.js:366:7 at next (/usr/lib/nodejs/mocha/lib/runner.js:290:14) at Immediate._onImmediate (/usr/lib/nodejs/mocha/lib/runner.js:334:5) make[1]: *** [debian/rules:13: override_dh_auto_test] Error 1
Bug#918422: node-livescript FTBFS with nodejs 10.15.0
Source: node-livescript
Version: 1.5.0+dfsg-4
Severity: serious
Tags: ftbfs
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-livescript.html
...
dh_auto_test
make -j1 test
make[1]: Entering directory '/build/1st/node-livescript-1.5.0+dfsg'
/usr/bin/lsc --output lib --bare --compile "src/ast.ls"
/usr/bin/lsc --output lib --bare --compile "src/browser.ls"
/usr/bin/lsc --output lib --bare --compile "src/command.ls"
/usr/bin/lsc --output lib --bare --compile "src/grammar.ls"
/usr/bin/lsc --output lib --bare --compile "src/index.ls"
/usr/bin/lsc --output lib --bare --compile "src/lang-ls.ls"
/usr/bin/lsc --output lib --bare --compile "src/lexer.ls"
/usr/bin/lsc --output lib --bare --compile "src/mode-ls.ls"
/usr/bin/lsc --output lib --bare --compile "src/node.ls"
/usr/bin/lsc --output lib --bare --compile "src/options.ls"
/usr/bin/lsc --output lib --bare --compile "src/util.ls"
./scripts/build-parser > lib/parser.js
./scripts/test
test/accessor.ls
test/assignment.ls
[0;31mInput A expected to strictly equal input B:
+ expected - actual
- 0
+ -0
[0;31mat test/assignment.ls:389:1[0m
: [{}]), d = e[0];
eq(a, o.a);
eq(b, 'b');
eq(c, 'c');
eq(d, e[0]);
o = {};
eq(1, o[0] = -~o[0]);
eq(false, o = !o);
[0;1meq(0, o = -o);[0m
eq(1, o += !o);
eq(true, o = !!o);
helloWorld = 2;
eq(helloWorld, 2);
a = 2;
b = 3;
aB = 99;
eq(1, a - 1);
test/chaining.ls
test/cli.ls
test/comment.ls
test/compilation.ls
test/cs-classes.ls
test/declaration.ls
test/existence.ls
test/function.ls
test/heredoc.ls
test/if.ls
test/label.ls
test/lib.ls
test/literal.ls
test/loop.ls
test/null.ls
test/oo.ls
test/operator.ls
test/regex.ls
test/splat.ls
test/string.ls
test/switch.ls
test/try.ls
[0;31mfailed 1 and passed 1935 tests in 3.02 seconds[0m
make[1]: *** [Makefile:52: test] Error 1
Bug#918420: node-jison-lex FTBFS with nodejs 10.15.0
Source: node-jison-lex Version: 0.3.4-2 Severity: serious Tags: ftbfs buster sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-jison-lex.html ... test more() [35m⚡ SyntaxError: Unexpected token ( at new RegExpLexer (/build/1st/node-jison-lex-0.3.4/regexp-lexer.js:124:22) at exports.test more() (/build/1st/node-jison-lex-0.3.4/tests/regexplexer.js:322:17) at test (/usr/lib/nodejs/test/test.js:29:20) at next (/usr/lib/nodejs/test/test.js:69:7) at Object.end (/usr/lib/nodejs/test/test.js:25:7) at test (/usr/lib/nodejs/test/test.js:41:28) at next (/usr/lib/nodejs/test/test.js:69:7) at Object.end (/usr/lib/nodejs/test/test.js:25:7) at test (/usr/lib/nodejs/test/test.js:41:28) at next (/usr/lib/nodejs/test/test.js:69:7)[39m ... test generator with more complex lexer [35m⚡ SyntaxError: Unexpected token ( at new RegExpLexer (/build/1st/node-jison-lex-0.3.4/regexp-lexer.js:124:22) at exports.test generator with more complex lexer (/build/1st/node-jison-lex-0.3.4/tests/regexplexer.js:413:18) at test (/usr/lib/nodejs/test/test.js:29:20) at next (/usr/lib/nodejs/test/test.js:69:7) at Object.end (/usr/lib/nodejs/test/test.js:25:7) at test (/usr/lib/nodejs/test/test.js:41:28) at next (/usr/lib/nodejs/test/test.js:69:7) at Object.end (/usr/lib/nodejs/test/test.js:25:7) at test (/usr/lib/nodejs/test/test.js:41:28) at next (/usr/lib/nodejs/test/test.js:69:7)[39m ... Passed:40 Failed:0 Errors:2 make[1]: *** [debian/rules:13: override_dh_auto_test] Error 1
Bug#918421: node-prelude-ls FTBFS with nodejs 10.15.0
Source: node-prelude-ls Version: 1.1.2+dfsg-2 Severity: serious Tags: ftbfs buster sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-prelude-ls.html ... 437 passing (337ms) 2 failing 1) negate zero: AssertionError [ERR_ASSERTION]: Input A expected to strictly equal input B: + expected - actual - 0 + -0 + expected - actual -0 +-0 at Context. (test/Num.ls:35:12) at callFn (/usr/lib/nodejs/mocha/lib/runnable.js:354:21) at Test.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:346:7) at Runner.runTest (/usr/lib/nodejs/mocha/lib/runner.js:442:10) at /usr/lib/nodejs/mocha/lib/runner.js:560:12 at next (/usr/lib/nodejs/mocha/lib/runner.js:356:14) at /usr/lib/nodejs/mocha/lib/runner.js:366:7 at next (/usr/lib/nodejs/mocha/lib/runner.js:290:14) at Immediate._onImmediate (/usr/lib/nodejs/mocha/lib/runner.js:334:5) 2) ceiling negative number: AssertionError [ERR_ASSERTION]: Input A expected to strictly equal input B: + expected - actual - 0 + -0 + expected - actual -0 +-0 at Context. (test/Num.ls:236:12) at callFn (/usr/lib/nodejs/mocha/lib/runnable.js:354:21) at Test.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:346:7) at Runner.runTest (/usr/lib/nodejs/mocha/lib/runner.js:442:10) at /usr/lib/nodejs/mocha/lib/runner.js:560:12 at next (/usr/lib/nodejs/mocha/lib/runner.js:356:14) at /usr/lib/nodejs/mocha/lib/runner.js:366:7 at next (/usr/lib/nodejs/mocha/lib/runner.js:290:14) at Immediate._onImmediate (/usr/lib/nodejs/mocha/lib/runner.js:334:5) make[1]: *** [Makefile:40: test] Error 2
Processed: anyone want to craft a patch?
Processing commands for cont...@bugs.debian.org: > tags 901952 +help Bug #901952 [tar] xdelta: expected from file (/tmp/pristine-tar.SljdkfANnj/recreatetarball) of length 7557120 bytes Added tag(s) help. > thanks Stopping processing here. Please contact me if you need assistance. -- 901952: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901952 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#918419: runit: binary-all FTBFS
Source: runit Version: 2.1.2-21 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=runit=all=2.1.2-21=1546690634=0 ... dh_compress for x in changelog.gz buildinfo_amd64.gz ; do \ ln -sf ../runit/$x debian/runit-init/usr/share/doc/runit-init/$x ;\ done ln: failed to create symbolic link 'debian/runit-init/usr/share/doc/runit-init/changelog.gz': No such file or directory ln: failed to create symbolic link 'debian/runit-init/usr/share/doc/runit-init/buildinfo_amd64.gz': No such file or directory make[1]: *** [debian/rules:49: override_dh_compress] Error 1 This can be reproduced with dpkg-buildpackage -A
Bug#918418: django-prometheus FTBFS: test failures
Source: django-prometheus
Version: 1.0.15-2
Severity: serious
Tags: ftbfs
Some recent change in unstable makes django-prometheus FTBFS:
https://tests.reproducible-builds.org/debian/history/django-prometheus.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/django-prometheus.html
...
==
ERROR: testAssertMetricEquals
(django_prometheus.tests.test_testutils.PrometheusTestCaseMixinTest)
Tests assertMetricEquals.
--
Traceback (most recent call last):
File
"/build/1st/django-prometheus-1.0.15/django_prometheus/tests/test_testutils.py",
line 69, in testAssertMetricEquals
self.t.assertMetricEquals(42, 'some_gauge', registry=self.registry)
File "/build/1st/django-prometheus-1.0.15/django_prometheus/testutils.py",
line 102, in assertMetricEquals
value = self.getMetric(metric_name, registry=registry, **labels)
File "/build/1st/django-prometheus-1.0.15/django_prometheus/testutils.py",
line 55, in getMetric
metric_name, registry.collect(), **labels)
File "/build/1st/django-prometheus-1.0.15/django_prometheus/testutils.py",
line 48, in getMetricFromFrozenRegistry
for n, l, value in metric.samples:
ValueError: too many values to unpack
==
ERROR: testGetMetricVector
(django_prometheus.tests.test_testutils.PrometheusTestCaseMixinTest)
Tests getMetricVector.
--
Traceback (most recent call last):
File
"/build/1st/django-prometheus-1.0.15/django_prometheus/tests/test_testutils.py",
line 53, in testGetMetricVector
'some_nonexistent_gauge', registry=self.registry)
File "/build/1st/django-prometheus-1.0.15/django_prometheus/testutils.py",
line 77, in getMetricVector
metric_name, registry.collect())
File "/build/1st/django-prometheus-1.0.15/django_prometheus/testutils.py",
line 61, in getMetricVectorFromFrozenRegistry
for n, l, value in metric.samples:
ValueError: too many values to unpack
==
ERROR: testGetMetrics
(django_prometheus.tests.test_testutils.PrometheusTestCaseMixinTest)
Tests getMetric.
--
Traceback (most recent call last):
File
"/build/1st/django-prometheus-1.0.15/django_prometheus/tests/test_testutils.py",
line 41, in testGetMetrics
'some_gauge', registry=self.registry))
File "/build/1st/django-prometheus-1.0.15/django_prometheus/testutils.py",
line 55, in getMetric
metric_name, registry.collect(), **labels)
File "/build/1st/django-prometheus-1.0.15/django_prometheus/testutils.py",
line 48, in getMetricFromFrozenRegistry
for n, l, value in metric.samples:
ValueError: too many values to unpack
==
ERROR: testRegistrySaving
(django_prometheus.tests.test_testutils.PrometheusTestCaseMixinTest)
Tests saveRegistry and frozen registries operations.
--
Traceback (most recent call last):
File
"/build/1st/django-prometheus-1.0.15/django_prometheus/tests/test_testutils.py",
line 103, in testRegistrySaving
'some_gauge', frozen_registry))
File "/build/1st/django-prometheus-1.0.15/django_prometheus/testutils.py",
line 48, in getMetricFromFrozenRegistry
for n, l, value in metric.samples:
ValueError: too many values to unpack
--
Ran 6 tests in 0.006s
FAILED (errors=4)
Test failed:
error: Test failed:
E: pybuild pybuild:338: test: plugin distutils failed with: exit code=1:
python2.7 setup.py test
dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13
make: *** [debian/rules:8: build] Error 25
Bug#918417: golang-golang-x-exp FTBFS with Go 1.11
Source: golang-golang-x-exp Version: 0.0~git20181112.a3060d4-1 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-golang-x-exp.html ... === RUN TestSpec --- FAIL: TestSpec (0.00s) ebnflint_test.go:14: /usr/lib/go-1.11/doc/go_spec.html:413:20: expected "term", found RawString `\` (and 43 more errors) ...
Bug#918230: python-django: CVE-2019-3498: Content spoofing possibility in the default 404 page
Hi Chris, Thanks for working on the update. [disclaimer: not a full review, but something jumped on while i was reading the debdiff] On Sat, Jan 05, 2019 at 09:39:38PM +0100, Chris Lamb wrote: > Hi Moritz, > > > > This also affects stable from my reading of the code. Shall I > > > prepare an upload to stretch-security? > [..] > > Please do. > > debdiff attached, awaiting t...@security.debian.org ACK to upload. > > > Best wishes, > > -- > ,''`. > : :' : Chris Lamb > `. `'` la...@debian.org / chris-lamb.co.uk >`- > diff --git a/debian/changelog b/debian/changelog > index b1c56f7c5..d6472a04e 100644 > --- a/debian/changelog > +++ b/debian/changelog > @@ -1,3 +1,10 @@ > +python-django (1:1.10.7-2+deb9u4) stretch-security; urgency=high > + > + * CVE-2019-3498: Fix a content spoofing vulnerability in the default > +404 page. (Closes: #918230) > + > + -- Chris Lamb Sat, 05 Jan 2019 21:36:27 +0100 > + > python-django (1:1.10.7-2+deb9u3) stretch; urgency=medium > >* Default to supporting Spatialite >= 4.2. (Closes: #910240) > diff --git a/debian/patches/0017-CVE-2019-3498.patch > b/debian/patches/0017-CVE-2019-3498.patch > new file mode 100644 > index 0..ea647e964 > --- /dev/null > +++ b/debian/patches/0017-CVE-2019-3498.patch > @@ -0,0 +1,401 @@ > +From: Tom Hacohen > +Date: Fri, 4 Jan 2019 02:21:55 + > +Subject: Fixed #30070, > + CVE-2019-3498 -- Fixed content spoofing possiblity in the default 404 page. > + > +Co-Authored-By: Tim Graham > +Backport of 1ecc0a395be721e987e8e9fdfadde952b6dee1c7 from master. > +--- > + ...0006-Default-to-supporting-Spatialite-4.2.patch | 4 +-- > + debian/patches/0013-CVE-2018-7536.patch| 6 ++-- > + debian/patches/0015-CVE-2018-14574.patch | 2 +- > + .../patches/02_disable-sources-in-sphinxdoc.diff | 5 ++-- > + .../06_use_debian_geoip_database_as_default.diff | 3 +- > + debian/patches/fix-migration-fake-initial-1.patch | 20 ++ > + debian/patches/fix-migration-fake-initial-2.patch | 32 > -- > + .../fix-test-middleware-classes-headers.patch | 7 ++--- > + debian/patches/series | 1 + > + django/views/defaults.py | 8 -- > + tests/handlers/tests.py| 12 +--- > + 11 files changed, 65 insertions(+), 35 deletions(-) With the 0017-CVE-2019-3498.patch patch there is something strange. While it touches correctly the files django/views/defaults.py and the tests, it touches and modifies files in debian/*, other patches and series file. Can you recheck what went wrong here? Were you able to test resulting packages under stretch on production systems or any other tests which were performed? Regards, Salvatore
Bug#918416: golang-github-microcosm-cc-bluemonday FTBFS with Go 1.11
Source: golang-github-microcosm-cc-bluemonday Version: 0.0~git20161202.0.e797637-1.1 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-github-microcosm-cc-bluemonday.html ... === RUN TestUGCPolicy --- FAIL: TestUGCPolicy (0.00s) policies_test.go:194: test 4 failed; input : http://example.org/; rel="nofollow">Hello, Worldhttps://example.org/#!; rel="nofollow">! output : http://example.org/; rel="nofollow">Hello, Worldhttps://example.org/#!; rel="nofollow">! expected: http://example.org/; rel="nofollow">Hello, Worldhttps://example.org/#%21; rel="nofollow">! policies_test.go:194: test 5 failed; input : Hello, Worldhttps://example.org/#!; rel="nofollow">! output : Hello, Worldhttps://example.org/#!; rel="nofollow">! expected: Hello, Worldhttps://example.org/#%21; rel="nofollow">! ...
Bug#918415: golang-golang-x-tools FTBFS with Go 1.11
Source: golang-golang-x-tools
Version: 1:0.0~git20180501.d3e4ceb5+ds-1
Severity: serious
Tags: ftbfs
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-golang-x-tools.html
...
=== RUN TestGuru
testdata/src/softerrs/main.go:8:6: i declared but not used
--- FAIL: TestGuru (115.50s)
guru_test.go:301: Guru tests for testdata/src/referrers/main.go failed:
exit status 1.
--- testdata/src/referrers/main.golden 2019-01-03 12:48:16.976984149
-1200
+++ testdata/src/referrers/main.got 2019-01-03 12:50:41.761147882
-1200
@@ -56,5 +56,5 @@
@referrers ref-type-U
references to type U int
-open nosuchfile.y: no such file or directory (+ 1 more refs in this
file)
+open testdata/src/referrers/nosuchfile.y: no such file or directory (+
1 more refs in this file)
...
=== RUN TestImportTestdata
--- FAIL: TestImportTestdata (1.15s)
gcimporter_test.go:93: testPath(./testdata/exports): reading export data:
testdata/exports.o: cannot import, possibly version skew (unknown export format
version -1 ("i\x00\x83")) - reinstall package
=== RUN TestVersionHandling
--- PASS: TestVersionHandling (0.00s)
=== RUN TestImportStdLib
--- FAIL: TestImportStdLib (0.02s)
gcimporter_test.go:93: testPath(archive/tar): reading export data:
/usr/lib/go-1.11/pkg/linux_amd64/archive/tar.a: cannot import, possibly version
skew (unknown export format version -1
("i\x00\x8c\x16\xc1/!$GOROOT/src/archive/tar/common.go\x00\bTypeflag\x04Name\bLinkname\x04Size\x04Mode\x03Uid\x03Gid\x05Uname\x05Gname\aModTime\x04Time\x04time"))
- reinstall package
gcimporter_test.go:93: testPath(archive/zip): reading export data:
/usr/lib/go-1.11/pkg/linux_amd64/archive/zip.a: cannot import, possibly version
skew (unknown export format version -1
("i\x00\xe0$\xb9E!$GOROOT/src/archive/zip/reader.go\x00\x01r\bReaderAt\x02io\x04File\aComment\rdecompressors\fDecompressor\x04init\x01z\x06Reader\x04size\x14RegisterDecompressor\x06method\x05dcomp\fdecompressor\aesc:0x1\x01f\x02os\x05Close\x02rc"))
- reinstall package
gcimporter_test.go:110: testing time used up
gcimporter_test.go:240: tested 0 imports
=== RUN TestImportedTypes
--- FAIL: TestImportedTypes (0.09s)
gcimporter_test.go:275: reading export data:
/usr/lib/go-1.11/pkg/linux_amd64/math.a: cannot import, possibly version skew
(unknown export format version -1
("i\x00\xcf\x0e\x98\x1d\x17$GOROOT/src/math/abs.go\x01x\x00\x0fFloat64frombits\vFloat64bits\x19$GOROOT/src/math/acosh.go\x18$GOROOT/src/math/asin.go\x19$GOROOT/src/math/asinh.go\x18$GOROOT/src/math/atan.go\x19$GOROOT/src/math/atan2.go\x01y\x19$GOROOT/src/math/atanh.go\x18$GOROOT/src/math/bits.go\x04sign\x04v·3\x01f\x02is\x19$GOROOT/src/math/const.go\x18$GOROOT/src/math/cbrt.go\x1c$GOROOT/src/math/copysign.go\x17$GOROOT/src/math/dim.go\x04v·4\x17$GOROOT/src/math/erf.go\x1a$GOROOT/src/math/erfinv.go\x17$GOROOT/src/math/exp.go\x19$GOROOT/src/math/expm1.go\x19$GOROOT/src/math/floor.go\abits·3\x04e·4\x19$GOROOT/src/math/frexp.go\x04frac\x03exp\x19$GOROOT/src/math/gamma.go\x19$GOROOT/src/math/hypot.go\x01p\x01q\x16$GOROOT/src/math/j0.go\x16$GOROOT/src/math/j1.go\x16$GOROOT/src/math/jn.go\x01n\x19$GOROOT/src/math/ldexp.go\x1a$GOROOT/src/math/lgamma.go\x06lgamma\x17$GOROOT/src/math/log.go\x19$GOROOT/src/math/log10.go\x19$GOROOT/src/math/log1p.go\x18$GOROOT/src/math/logb.go\x17$GOROOT/src/math/mod.go\x18$GOROOT/src/math/modf.go\x03int\x1d$GOROOT/src/math/nextafter.go\x01r\x17$GOROOT/src/math/pow.go\x19$GOROOT/src/math/pow10.go\rpow10postab32\bpow10tab\rpow10negtab32\x03Inf\x1d$GOROOT/src/math/remainder.go\x1b$GOROOT/src/math/signbit.go\x17$GOROOT/src/math/sin.go\x1a$GOROOT/src/math/sincos.go\x03sin\x03cos\x18$GOROOT/src/math/sinh.go\x18$GOROOT/src/math/sqrt.go\x17$GOROOT/src/math/tan.go\x18$GOROOT/src/math/tanh.go\x1a$GOROOT/src/math/unsafe.go\x01b\x0f\x04math\x03Abs\x04Acos\x05Acosh\x04Asin\x05Asinh\x04Atan\x05Atan2\x05Atanh\x04Cbrt\x04Ceil\bCopysign\x03Cos\x04Cosh\x03Dim\x01E\x03Erf\x04Erfc\aErfcinv\x06Erfinv\x03Exp\x04Exp2\x05Expm1\vFloat32bits\x0fFloat32frombits\x05Floor\x05Frexp\x05Gamma\x05Hypot\x05Ilogb\x05IsInf\x05IsNaN\x02J0\x02J1\x02Jn\x05Ldexp\x06Lgamma\x04Ln10\x03Ln2\x03Log\x05Log10\x06Log10E\x05Log1p\x04Log2\x05Log2E\x04Logb\x03Max"))
- reinstall package
gcimporter_test.go:275: reading export data:
/usr/lib/go-1.11/pkg/linux_amd64/io.a: cannot import, possibly version skew
(unknown export format version -1
("i\x00\xb8\t\x9d\x12\x14$GOROOT/src/io/io.go\x00\x04Read\x01p\x01n\x03err\x05Write\x05Close\x04Seek\x06offset\x06whence\x06Reader\x06Writer\x06Closer\x06Seeker\bReadFrom\x01r\aWriteTo\x01w\x06ReadAt\x03off\aWriteAt\bReadByte"))
- reinstall package
gcimporter_test.go:275: reading export data:
/usr/lib/go-1.11/pkg/linux_amd64/math.a: cannot import, possibly version skew
(unknown export format version -1
Bug#918414: golang-github-jacobsa-ogletest FTBFS with Go 1.11
Source: golang-github-jacobsa-ogletest Version: 0.0~git20150610-8 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-github-jacobsa-ogletest.html ... === RUN TestGoldenFiles --- FAIL: TestGoldenFiles (24.28s) integration_test.go:261: Output for test case panicking doesn't match golden file. FAIL FAILgithub.com/jacobsa/ogletest 24.287s ...
Bug#918413: golang-github-aws-aws-sdk-go FTBFS with Go 1.11
Source: golang-github-aws-aws-sdk-go Version: 1.12.79+dfsg-1 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-github-aws-aws-sdk-go.html ... === RUN TestIsSerializationErrorRetryable --- FAIL: TestIsSerializationErrorRetryable (0.00s) request_test.go:548: Case 4: Expected true, but received false ... === RUN TestSerializationErrConnectionReset --- FAIL: TestSerializationErrConnectionReset (0.00s) request_test.go:686: Expected '6', but received 1 ... === RUN ExampleCookieSigner_Sign --- FAIL: ExampleCookieSigner_Sign (0.06s) got: Cookies: CloudFront-Policy: eyJTdGF0ZW1lbnQiOlt7IlJlc291cmNlIjoiaHR0cDovL2V4YW1wbGUuY29tL3NvbWVwYXRoLyoiLCJDb25kaXRpb24iOnsiRGF0ZUxlc3NUaGFuIjp7IkFXUzpFcG9jaFRpbWUiOjEyNTc4OTU4MDB9fX1dfQ__, , , false CloudFront-Signature: XWGDN6T8J3QRTZjX8mxZtYS3QwjT2jX7KS7QMNjzAV0MEZprJYYoEdQd8kVTqk-Yo~HDNq1oyT9UB8xUqOqZPtjdidQ5ETRHkBOq1ohUFMhXlHyz-k~iAodqE0AkB6~ErXQPcc3~CcnGuFTConfAf3m2L6DfRpdOHmV7o9r1gQo_, , , false CloudFront-Key-Pair-Id: keyID, , , false want: Cookies: CloudFront-Policy: eyJTdGF0ZW1lbnQiOlt7IlJlc291cmNlIjoiaHR0cDovL2V4YW1wbGUuY29tL3NvbWVwYXRoLyoiLCJDb25kaXRpb24iOnsiRGF0ZUxlc3NUaGFuIjp7IkFXUzpFcG9jaFRpbWUiOjEyNTc4OTU4MDB9fX1dfQ__, , , false CloudFront-Signature: o~jvj~CFkvGZB~yYED3elicKZag-CRijy8yD2E5yF1s7VNV7kNeQWC7MDtEcBQ8-eh7Xgjh0wMPQdAVdh09gBObd-hXDpKUyh8YKxogj~oloV~8KOvqE5xzWiKcqjdfJjmT5iEqIui~H1ExYjyKjgir79npmlyYkaJS5s62EQa8_, , , false CloudFront-Key-Pair-Id: keyID, , , false ...
Processed: bug 900156 is forwarded to https://github.com/puma/puma/issues/1609
Processing commands for cont...@bugs.debian.org: > forwarded 900156 https://github.com/puma/puma/issues/1609 Bug #900156 [src:puma] puma: FTBFS against openssl 1.1.1 Bug #907022 [src:puma] puma: autopkgtest times out after update of openssl Set Bug forwarded-to-address to 'https://github.com/puma/puma/issues/1609'. Set Bug forwarded-to-address to 'https://github.com/puma/puma/issues/1609'. > thanks Stopping processing here. Please contact me if you need assistance. -- 900156: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900156 907022: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907022 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#918088: Acknowledgement (autofs-ldap: automount dies withSIGABRT after libkrb5-3 upgrade - "(k5_mutex_lock: Assertion `r == 0'failed.)")
>Unfortunately the latter. > >Manu Alén has expressed interest in adopting autofs, >and might be interested in helping out in addition >to the help already provided by Andreas - added to Cc. Yes, I can support autofs. I’m testing other packages but I think I have a bit of free time to do the needful with autofs package. Please do not hesitate to request me for any test to do with this package. Thanks BR Manu From: Adrian Bunk Sent: Saturday, January 5, 2019 21:58 To: Sam Hartman Cc: Andreas Maus; 918...@bugs.debian.org; Russ Allbery; Benjamin Kaduk; Manu Alén Subject: Re: Bug#918088: Acknowledgement (autofs-ldap: automount dies withSIGABRT after libkrb5-3 upgrade - "(k5_mutex_lock: Assertion `r == 0'failed.)") On Fri, Jan 04, 2019 at 09:00:01PM -0500, Sam Hartman wrote: > > "Adrian" == Adrian Bunk writes: > > latest upgrade of libkrb5-3 (1.16.1-1 -> 1.16.2-1) > >> automount starts but dies immediately after accessing a > >> automounter point. > >> > >> Automount is configured to authenticate via GSSAPI using system > >> keytab. After the GSSAPI authentication succeeded, any access to > >> a configure automount entry causes automount to die with an > >> assertion failure (followed by an abort()): > > Adrian> Thanks for your report. > > Adrian> I'm moving this bug report to libkrb5-3 since this is the > Adrian> change that triggered your regression for assessment whether > Adrian> the bug is there. > > Adrian, I'm guessing you're looking at this with your QA hat on? > How well do you understand autofs? Any chance you could help put > together a repo? >... Unfortunately the latter. Manu Alén has expressed interest in adopting autofs, and might be interested in helping out in addition to the help already provided by Andreas - added to Cc. > --Sam cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed
Bug#917788: libmedc11: Overwrites a file from libmedc1v5
On Sat, 5 Jan 2019 21:53:13 +0100 Gilles Filippini wrote: > On Sat, 5 Jan 2019 17:23:11 +0100 Mattia Rizzolo wrote: > > Control: reopen -1 > > > > On Wed, Jan 02, 2019 at 12:45:08AM +0100, Andreas Beckmann wrote: > > > On Sun, 30 Dec 2018 09:21:03 -0600 Kurt Kremitzki > > > wrote: > > > > I was just about to open a bug on this same issue. It's actually present > > > > in both libmed11 and libmedc11. Instead of Conflicts, they both need > > > > Breaks + Replaces, see Policy 7.6 [1] or #906110 [2] for a similar > > > > > > In this special case, you probably need to add > > > Breaks+Replaces: libmed1v5 (>= 4) > > > respectively > > > Breaks+Replaces: libmedc1v5 (>= 4) > > > since the versions before 4 should not have any file conflicts. > > > > Actually, I think Breaks+Replaces is wrong here. > > > > Breaks+Replaces allow for silent replacing of the old package, but here > > you need to forcefully remove it, which is what you'd use Conflicts for. > > As a data point, that what we usually use when renaming packages during > > ABI breaks like what has been done for #916881. > > I agree that Conflicts suits better regarding the need to forcibly > remove libmed1v5 / libmedc1v5 (= 4.0.0+repack-1). > > > Incidentally, I think that would also cover the just openend #918372, > > as with a Conflicts the libgmsh3 package from testing woudln't be > > installable, so it would force an upgrade to the version in unstable, > > making the test pass. > > Here I'm not sure. I think the problem is that libmed1v5 and libmedc1v5 > from the broken med-fichier 4.0.0+repack-1 are still present into > unstable. Is there a way to have them removed? Oh, looking at cruft-report [1] I see that syrthes-tools still dépends on libmedc1v5, preventing the removal : * source package med-fichier version 4.0.0+repack-6 no longer builds binary package(s): libmed1v5 libmedc1v5 on amd64,arm64,armel,armhf,hurd-i386,i386,mips,mips64el,mipsel,ppc64el,s390x - suggested command: dak rm -m "[auto-cruft] NBS (no longer built by med-fichier)" -s unstable -a amd64,arm64,armel,armhf,hurd-i386,i386,mips,mips64el,mipsel,ppc64el,s390x -p -R -b libmed1v5 libmedc1v5 - broken Depends: syrthes: syrthes-tools [amd64 arm64 armel armhf hurd-i386 i386 mips mips64el mipsel ppc64el] [1] http://ftp-master.debian.org/cruft-report-daily.txt I'm going to fix that. Thanks, _g.
Bug#917303: Request for help with MariaDB 10.3 / libdbd-mysql-perl packaging
On Fri, 04 Jan 2019 16:07:19 +0100, p...@cpan.org wrote: > Or... how many packages depends on libdbd-mysql-perl? > Cannot be they migrated to libdbd-mariadb-perl? Maybe the packages could be migrated (although I'm a bit skeptical that we would be able to catch all issues) but libdbd-mysql-perl is also widely used in third-party code and projects written by users. Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- NP: Bruce Springsteen: Jungleland signature.asc Description: Digital Signature
Bug#914638: marked as done (ambdec FTBFS: freetype-config not found)
Your message dated Sat, 05 Jan 2019 21:04:22 + with message-id and subject line Bug#914638: fixed in ambdec 0.7.1-1 has caused the Debian Bug report #914638, regarding ambdec FTBFS: freetype-config 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.) -- 914638: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914638 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ambdec Version: 0.5.1-5 Severity: serious Tags: ftbfs ambdec fails to build from source, because it uses freetype-config, which got removed from Debian. Please use pkg-config instead. Helmut --- End Message --- --- Begin Message --- Source: ambdec Source-Version: 0.7.1-1 We believe that the bug you reported is fixed in the latest version of ambdec, 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 914...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastian Ramacher (supplier of updated ambdec 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: Sat, 05 Jan 2019 21:33:13 +0100 Source: ambdec Binary: ambdec Architecture: source Version: 0.7.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Sebastian Ramacher Description: ambdec - Ambisonic decoder for first and second order Closes: 914638 Changes: ambdec (0.7.1-1) unstable; urgency=medium . * Team upload. * New upstream release. - Use pkgconf to detect freetype. (Closes: #914638) * debian/patches: Refresh patches. * debian/control: Bump Standards-Version. * debian/: - Use pkg-config where possible. - Bump debhelper compat to 12. Checksums-Sha1: 7547b874c342861ac3d588c6f40916b7f2a11214 2025 ambdec_0.7.1-1.dsc 6ee719e2d164fb3c2af2cfcadeabd16bf5f78cd8 54074 ambdec_0.7.1.orig.tar.bz2 bdc3c2dfbab7019185a6c552fdb121885041fece 4856 ambdec_0.7.1-1.debian.tar.xz Checksums-Sha256: 7b20270c865ce39e3052bc8695669a2d09cc07e20323a6108b0cd2a6ac70f70f 2025 ambdec_0.7.1-1.dsc 8ad266355a2108a9116e7b6d6c08f7c17b8ee852e1a3850b43bb5802924fe354 54074 ambdec_0.7.1.orig.tar.bz2 ca62d166d6fe4ddc6797ff43a18d3f9593758413a4af5d5594b10b3f29d64737 4856 ambdec_0.7.1-1.debian.tar.xz Files: 8d705a7645c4a48bea169d73e717eb99 2025 sound optional ambdec_0.7.1-1.dsc a91a331eb87cec25219c0dd73646dc90 54074 sound optional ambdec_0.7.1.orig.tar.bz2 48966fba3123e6692daddf008262 4856 sound optional ambdec_0.7.1-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE94y6B4F7sUmhHTOQafL8UW6nGZMFAlwxFLsACgkQafL8UW6n GZPkexAAm6PSepkmVdA3pzlAcvXeD9KamS6bh6U4NPzOI4ClaULimgFbMr4HMqoy Bvw3DA7pzZ1EeUA9+eXW8f8AHhmW1YX8d4g6ASDX8+zjwaccyemSPqE6nYwKdFdE tUuc7iSRe2mQIo+cht/gOD+4Eqi3WHrX21QxWlM0zuyd1QE55y+L+MC5IuagmRjf OX4D3ksD/UbECfBw+gtdrxmFSoOiHMrTAYxldhGj9GHqTIVjmyj11KC6hVdsWivz 6KJzEup55qhL4Y4Der03B4jjWsjp+CCZQEihN5TKad0fCAHGRKYn1Qne/RKOMHTd +MBPMfsdes83wMxgGRStKnPiXyuNT0whCam4gK6da3lZdA6nrnUwiUkRRbTJsTfz a92IeYiYHR1SCwt9cafJejrOkQCi8y4VXFfG9qbKRie3NGZzWv4+jk+kTtkwpMMm XoIOYbOTdDDIoJcPhhOz18zsyGp8vjwjaEUG1RxuixOSRLr7xoKRwh6W/lsGoCRD xZ2jq9YdBiBmYl7gg4BSNdezUnQ7CPZYgUwL7xAP5bUb01mFQ1jykMzGQXPBBHy7 ncsjk+dxw3j62Lbkz9bB5UgByV4tPVqhJ7DTO5rSTkSABcb9ZPjOoVF0dcAUXA8a KjJhwv6zSkvitSrvrQ8TbLBJe0Wlmsg7JpwgF/KER9TR0BYgPmI= =aqwM -END PGP SIGNATURE End Message ---
Bug#917303: Request for help with MariaDB 10.3 / libdbd-mysql-perl packaging
On Sat, 05 Jan 2019 13:33:01 +0200, Otto Kekäläinen wrote: > Since this is holding back mariadb-10.3 from entering Debian Testing, > and the transition freeze will start on Jan 14th, could you consider > uploading an intermediate version with autopkgtest disabled or skipped > in some way so that this test passes? Disabling the failing tests during autopkgtests wouldn't help, as they fail in the same way during build. And disabling them during build seems wrong to me as they are the result of an actual bug. Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- NP: Rolling Stones: Sweetblack signature.asc Description: Digital Signature
Processed: your mail
Processing commands for cont...@bugs.debian.org: > tags 918407 upstream Bug #918407 [src:golang-github-twstrike-otr3] golang-github-twstrike-otr3 FTBFS with Go 1.11 Added tag(s) upstream. > forwarded 918407 https://github.com/coyim/otr3/issues/55 Bug #918407 [src:golang-github-twstrike-otr3] golang-github-twstrike-otr3 FTBFS with Go 1.11 Set Bug forwarded-to-address to 'https://github.com/coyim/otr3/issues/55'. > thanks Stopping processing here. Please contact me if you need assistance. -- 918407: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918407 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#918088: Acknowledgement (autofs-ldap: automount dies with SIGABRT after libkrb5-3 upgrade - "(k5_mutex_lock: Assertion `r == 0' failed.)")
On Fri, Jan 04, 2019 at 09:00:01PM -0500, Sam Hartman wrote: > > "Adrian" == Adrian Bunk writes: > > latest upgrade of libkrb5-3 (1.16.1-1 -> 1.16.2-1) > >> automount starts but dies immediately after accessing a > >> automounter point. > >> > >> Automount is configured to authenticate via GSSAPI using system > >> keytab. After the GSSAPI authentication succeeded, any access to > >> a configure automount entry causes automount to die with an > >> assertion failure (followed by an abort()): > > Adrian> Thanks for your report. > > Adrian> I'm moving this bug report to libkrb5-3 since this is the > Adrian> change that triggered your regression for assessment whether > Adrian> the bug is there. > > Adrian, I'm guessing you're looking at this with your QA hat on? > How well do you understand autofs? Any chance you could help put > together a repo? >... Unfortunately the latter. Manu Alén has expressed interest in adopting autofs, and might be interested in helping out in addition to the help already provided by Andreas - added to Cc. > --Sam cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed
Bug#917788: libmedc11: Overwrites a file from libmedc1v5
On Sat, 5 Jan 2019 17:23:11 +0100 Mattia Rizzolo wrote: > Control: reopen -1 > > On Wed, Jan 02, 2019 at 12:45:08AM +0100, Andreas Beckmann wrote: > > On Sun, 30 Dec 2018 09:21:03 -0600 Kurt Kremitzki wrote: > > > I was just about to open a bug on this same issue. It's actually present > > > in both libmed11 and libmedc11. Instead of Conflicts, they both need > > > Breaks + Replaces, see Policy 7.6 [1] or #906110 [2] for a similar > > > > In this special case, you probably need to add > > Breaks+Replaces: libmed1v5 (>= 4) > > respectively > > Breaks+Replaces: libmedc1v5 (>= 4) > > since the versions before 4 should not have any file conflicts. > > Actually, I think Breaks+Replaces is wrong here. > > Breaks+Replaces allow for silent replacing of the old package, but here > you need to forcefully remove it, which is what you'd use Conflicts for. > As a data point, that what we usually use when renaming packages during > ABI breaks like what has been done for #916881. I agree that Conflicts suits better regarding the need to forcibly remove libmed1v5 / libmedc1v5 (= 4.0.0+repack-1). > Incidentally, I think that would also cover the just openend #918372, > as with a Conflicts the libgmsh3 package from testing woudln't be > installable, so it would force an upgrade to the version in unstable, > making the test pass. Here I'm not sure. I think the problem is that libmed1v5 and libmedc1v5 from the broken med-fichier 4.0.0+repack-1 are still present into unstable. Is there a way to have them removed? Thanks, _g. signature.asc Description: OpenPGP digital signature
Bug#918411: node-timed-out FTBFS with nodejs 10.15.0
Source: node-timed-out Version: 4.0.1-2 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-timed-out.html ... debian/rules override_dh_auto_test make[1]: Entering directory '/build/1st/node-timed-out-4.0.1' mocha -R spec when connection is established ✓ should emit ESOCKETTIMEDOUT (no data) (243ms) ✓ should emit ESOCKETTIMEDOUT (only first chunk of body) (314ms) ✓ should be able to only apply connect timeout ✓ should be able to only apply socket timeout (56ms) ✓ should not add event handlers twice for the same socket ✓ should set socket timeout if socket is already connected (203ms) 1) should clear socket timeout for keep-alive sockets 6 passing (1s) 1 failing 1) when connection is established should clear socket timeout for keep-alive sockets: Uncaught AssertionError [ERR_ASSERTION]: undefined == 100 at Socket. (test.js:231:12) at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1103:10) make[1]: *** [debian/rules:14: override_dh_auto_test] Error 1
Processed: your mail
Processing commands for cont...@bugs.debian.org: > forwarded 916807 https://github.com/haskell/haskell-mode/issues/1630 Bug #916807 [src:haskell-mode] haskell-mode: FTBFS with Emacs 26.1: tests fail Set Bug forwarded-to-address to 'https://github.com/haskell/haskell-mode/issues/1630'. > thanks Stopping processing here. Please contact me if you need assistance. -- 916807: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916807 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#918409: node-merge-descriptors FTBFS with nodejs 10.15.0
Source: node-merge-descriptors Version: 1.0.1-1 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-merge-descriptors.html ... debian/rules override_dh_auto_test make[1]: Entering directory '/build/1st/node-merge-descriptors-1.0.1' mocha --reporter spec --bail --check-leaks test/ merge(dest, src) arguments dest 1) should be required 0 passing (52ms) 1 failing 1) merge(dest, src) arguments dest should be required: TypeError [ERR_AMBIGUOUS_ARGUMENT]: The "error/message" argument is ambiguous. The error message "argument dest is required" is identical to the message. at expectsError (assert.js:629:15) at Function.throws (assert.js:690:3) at Context. (test/merge.js:19:16) at callFn (/usr/lib/nodejs/mocha/lib/runnable.js:354:21) at Test.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:346:7) at Runner.runTest (/usr/lib/nodejs/mocha/lib/runner.js:442:10) at /usr/lib/nodejs/mocha/lib/runner.js:560:12 at next (/usr/lib/nodejs/mocha/lib/runner.js:356:14) at /usr/lib/nodejs/mocha/lib/runner.js:366:7 at next (/usr/lib/nodejs/mocha/lib/runner.js:290:14) at Immediate._onImmediate (/usr/lib/nodejs/mocha/lib/runner.js:334:5) make[1]: *** [debian/rules:13: override_dh_auto_test] Error 1
Bug#916807: (no subject)
I've ran tests against the source code from upstream's repository and
got even more failures:
Ran 532 tests, 523 results as expected, 7 unexpected, 2 skipped (2019-01-06
01:42:08+0500)
122 expected failures
7 unexpected results:
FAILED haskell-cabal-compute-checksum-1
FAILED haskell-cabal-compute-next-prev-section-1
FAILED haskell-cabal-enum-targets-1
FAILED haskell-cabal-enum-targets-2
FAILED haskell-cabal-get-field-1
FAILED haskell-process-type-test-1
FAILED haskell-process-type-test-2
2 skipped results:
SKIPPED haskell-indent-in-comment-1
SKIPPED haskell-indentation-altj-comment
Please, find the check-ert log attached.
Regards,
Lev
===File /home/dogsleg/tmp/haskell-mode/check-ert.log
$ emacs --version
GNU Emacs 26.1
Copyright (C) 2018 Free Software Foundation, Inc.
GNU Emacs comes with ABSOLUTELY NO WARRANTY.
You may redistribute copies of GNU Emacs
under the terms of the GNU General Public License.
For more information about these matters, see the file named COPYING.
$ LANG=C.UTF-8 make check-ert
EMACS check-ert
Running 532 tests (2019-01-06 01:40:45+0500)
passed1/532 backward-sexp
passed2/532 bos-270
passed3/532 commented-out-import-parse
Process is not running, so running directly.
passed4/532 do-cabal-no-process
passed5/532 empty-buffer
passed6/532 file-structure
passed7/532 fill-comment-1
failed8/532 fill-comment-10
passed9/532 fill-comment-11
passed 10/532 fill-comment-12
passed 11/532 fill-comment-2
passed 12/532 fill-comment-3
passed 13/532 fill-comment-4
passed 14/532 fill-comment-5
passed 15/532 fill-comment-6
passed 16/532 fill-comment-7
failed 17/532 fill-comment-8
failed 18/532 fill-comment-9
passed 19/532 fill-comment-haddock-1
passed 20/532 fill-comment-haddock-2
passed 21/532 forward-sexp-function-1
passed 22/532 forward-sexp-function-2
passed 23/532 full-import-parse
Could not…
passed 24/532 goto-first-error-after
Could not…
passed 25/532 goto-first-error-before
Could not…
passed 26/532 goto-first-error-between
No further notes from Haskell compiler.
passed 27/532 goto-next-error-after
Could not…
passed 28/532 goto-next-error-before
Could not…
passed 29/532 goto-next-error-between
Could not…
passed 30/532 goto-prev-error-after
No further notes from Haskell compiler.
passed 31/532 goto-prev-error-before
Could not…
passed 32/532 goto-prev-error-between
passed 33/532 haskell-backward-sexp
passed 34/532 haskell-c2hs-alignof-hook
passed 35/532 haskell-c2hs-basic-import-hook
passed 36/532 haskell-c2hs-class-hook
passed 37/532 haskell-c2hs-const-hook
failed 38/532 haskell-c2hs-enum-define-hook
failed 39/532 haskell-c2hs-enum-hook
passed 40/532 haskell-c2hs-full-context-hook
passed 41/532 haskell-c2hs-full-pointer-hook
passed 42/532 haskell-c2hs-get-hook
passed 43/532 haskell-c2hs-nongnu-hook
passed 44/532 haskell-c2hs-offsetof-hook
passed 45/532 haskell-c2hs-pointer-hook-1
passed 46/532 haskell-c2hs-pointer-hook-2
passed 47/532 haskell-c2hs-pure-call-hook
passed 48/532 haskell-c2hs-pure-fun-hook
passed 49/532 haskell-c2hs-qualified-import-hook
passed 50/532 haskell-c2hs-set-hook
passed 51/532 haskell-c2hs-sizeof-hook
passed 52/532 haskell-c2hs-type-hook
passed 53/532 haskell-c2hs-typedef-hook
passed 54/532 haskell-c2hs-unsafe-call-hook
passed 55/532 haskell-c2hs-unsafe-fun-hook
failed 56/532 haskell-cabal-add-dependency-01
passed 57/532 haskell-cabal-add-dependency-02
passed 58/532 haskell-cabal-add-dependency-03
passed 59/532 haskell-cabal-add-dependency-04
Test haskell-cabal-compute-checksum-1 backtrace:
file-name-directory(nil)
(let ((scriptDir (file-name-directory (or (symbol-file 'haskell-caba
(closure (t) nil (let ((scriptDir (file-name-directory (or (symbol-f
ert--run-test-internal(#s(ert--test-execution-info :test #s(ert-test
ert-run-test(#s(ert-test :name haskell-cabal-compute-checksum-1 :doc
ert-run-or-rerun-test(#s(ert--stats :selector t :tests [#s(ert-test
ert-run-tests(t #f(compiled-function (event-type event-args) #
ert-run-tests-batch(nil)
ert-run-tests-batch-and-exit()
command-line-1(("--eval" "(add-to-list 'load-path (expand-file-name
command-line()
normal-top-level()
Test haskell-cabal-compute-checksum-1 condition:
(wrong-type-argument stringp nil)
FAILED 60/532 haskell-cabal-compute-checksum-1
Test haskell-cabal-compute-next-prev-section-1 backtrace:
file-name-directory(nil)
(let ((scriptDir (file-name-directory (or (symbol-file 'haskell-caba
(closure (t) nil (let ((scriptDir (file-name-directory (or (symbol-f
ert--run-test-internal(#s(ert--test-execution-info :test #s(ert-test
ert-run-test(#s(ert-test :name
Bug#918407: golang-github-twstrike-otr3 FTBFS with Go 1.11
Source: golang-github-twstrike-otr3
Version: 0.0~git20161015.0.744856d-2
Severity: serious
Tags: ftbfs
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-github-twstrike-otr3.html
...
=== RUN Test_revealSigMessage
--- FAIL: Test_revealSigMessage (0.00s)
helpers_test.go:13: Expected:
{s:"EOF"}
to equal:
helpers_test.go:69: Expected:
[]byte(nil)
to equal:
[]byte{0x0, 0x0, 0x0, 0x10, 0xab, 0xcd, 0xab, 0xcd, 0xab, 0xcd, 0xab,
0xcd, 0xab, 0xcd, 0xab, 0xcd, 0xab, 0xcd, 0xab, 0xcd, 0x0, 0x0, 0x1, 0xd2,
0xdd, 0xa2, 0xd4, 0xef, 0x36, 0x57, 0x11, 0xc1, 0x72, 0xda, 0xd9, 0x28, 0x4,
0xb2, 0x1, 0xfc, 0xd2, 0xfd, 0xd6, 0x44, 0x45, 0x68, 0xeb, 0xf0, 0x84, 0x40,
0x19, 0xfb, 0x65, 0xca, 0x4f, 0x5f, 0x57, 0x3, 0x19, 0x36, 0xf9, 0xa3, 0x39,
0xe0, 0x8b, 0xfd, 0x44, 0x10, 0x90, 0x5a, 0xb8, 0x6c, 0x5d, 0x6f, 0x73, 0xe6,
0xc9, 0x4d, 0xe6, 0xa2, 0x7, 0xf3, 0x73, 0xbe, 0xff, 0x3f, 0x76, 0x76, 0xfa,
0xee, 0x7b, 0x1d, 0x3b, 0xe2, 0x1e, 0x63, 0xf, 0xe4, 0x2e, 0x95, 0xdb, 0x9d,
0x4a, 0xc5, 0x59, 0x25, 0x2b, 0xff, 0x53, 0x4, 0x81, 0x30, 0x1b, 0x59, 0xe,
0x21, 0x63, 0xb9, 0x9b, 0xde, 0x8a, 0xa1, 0xb0, 0x74, 0x48, 0xbf, 0x72, 0x52,
0x58, 0x8e, 0x31, 0x7b, 0xb, 0xa2, 0xfc, 0x52, 0xf8, 0x5a, 0x72, 0xa9, 0x21,
0xba, 0x75, 0x77, 0x85, 0xb9, 0x49, 0xe5, 0xe6, 0x82, 0x34, 0x1d, 0x98, 0x80,
0xa, 0xa1, 0x80, 0xaa, 0xb, 0xd0, 0x1f, 0x51, 0x18, 0xd, 0x48, 0x26, 0xe, 0x43,
0x58, 0xff, 0xae, 0x72, 0xa9, 0x7f, 0x65, 0x2f, 0x2, 0xeb, 0x6a, 0xe3, 0xbc,
0x6a, 0x25, 0xa3, 0x17, 0xd0, 0xca, 0x5e, 0xd0, 0x16, 0x4a, 0x99, 0x22, 0x40,
0xba, 0xac, 0x8e, 0x4, 0x3f, 0x84, 0x83, 0x32, 0xd2, 0x2c, 0x10, 0xa4, 0x6d,
0x12, 0xc7, 0x45, 0xdc, 0x7b, 0x1b, 0xe, 0xe3, 0x7f, 0xd1, 0x46, 0x14, 0xd4,
0xb6, 0x9d, 0x50, 0xb, 0x8c, 0xe5, 0x62, 0x4, 0xe, 0x3a, 0x4b, 0xfd, 0xd1, 0x7,
0x4e, 0x23, 0x12, 0xd3, 0xe3, 0xe4, 0xc6, 0x8b, 0xd1, 0x5d, 0x70, 0x16, 0x68,
0x55, 0xd8, 0x14, 0x1f, 0x69, 0x5b, 0x21, 0xc9, 0x8c, 0x60, 0x55, 0xa5, 0xed,
0xb9, 0xa2, 0x33, 0x92, 0x5c, 0xf4, 0x92, 0x21, 0x83, 0x42, 0x45, 0xb, 0x80,
0x6e, 0x58, 0xb3, 0xa8, 0x21, 0xe5, 0xd1, 0xd2, 0xb9, 0xc6, 0xb9, 0xcb, 0xcb,
0xa2, 0x63, 0x90, 0x8d, 0x71, 0x90, 0xa3, 0x42, 0x8a, 0xce, 0x92, 0x57, 0x2c,
0x6, 0x4a, 0x32, 0x8f, 0x86, 0xfa, 0x5b, 0x8a, 0xd2, 0xa9, 0xc7, 0x6d, 0x5b,
0x9d, 0xca, 0xea, 0xe5, 0x32, 0x7f, 0x54, 0x5b, 0x97, 0x37, 0x95, 0xf7, 0xc6,
0x55, 0x24, 0x81, 0x41, 0xc2, 0xf8, 0x2d, 0xb0, 0xa2, 0x4, 0x5e, 0x95, 0xc1,
0x93, 0x6b, 0x72, 0x6d, 0x64, 0x74, 0xf5, 0x2, 0x83, 0x28, 0x9e, 0x92, 0xab,
0x5c, 0x72, 0x97, 0x8, 0x1a, 0x54, 0xb9, 0xe7, 0xf, 0xce, 0x87, 0x60, 0x35,
0x6, 0xde, 0xdd, 0x67, 0x34, 0xba, 0xb3, 0xc1, 0x56, 0x7e, 0xe4, 0x83, 0xcd,
0x4b, 0xcb, 0xe, 0x66, 0x9d, 0x9d, 0x97, 0x86, 0x6c, 0xa2, 0x74, 0xf1, 0x78,
0x84, 0x1d, 0xaf, 0xc2, 0xac, 0xfd, 0xcd, 0x10, 0xcb, 0xe, 0x2d, 0x7, 0xdb,
0x24, 0x4f, 0xf4, 0xb1, 0xd2, 0x3a, 0xfe, 0x25, 0x38, 0x31, 0xf1, 0x42, 0x8,
0x3d, 0x91, 0x2a, 0x71, 0x64, 0xa3, 0x42, 0x5f, 0x82, 0xc9, 0x56, 0x75, 0x29,
0x8c, 0xf3, 0xc5, 0xeb, 0x3e, 0x9, 0x6b, 0xbc, 0x95, 0xe4, 0x4e, 0xcf, 0xfa,
0xfb, 0xb5, 0x85, 0x73, 0x87, 0x23, 0xc0, 0xad, 0xbe, 0x11, 0xf1, 0x6c, 0x31,
0x1a, 0x6c, 0xdd, 0xde, 0x63, 0xb, 0x9c, 0x30, 0x47, 0x17, 0xce, 0x5b, 0x9,
0x24, 0x7d, 0x48, 0x2f, 0x32, 0x70, 0x9e, 0xa7, 0x1c, 0xed, 0x16, 0xba, 0x93,
0xa, 0x55, 0x4f, 0x99, 0x49, 0xc1, 0xac, 0xbe, 0xcf, 0x8e, 0x6e, 0x5e, 0xf6,
0x3a, 0x4e, 0x8d, 0x6a, 0xa2, 0xcf, 0xb1, 0xc5, 0xfe, 0x18, 0x31, 0x49, 0x88,
0x62, 0xf6, 0x9d}
...
=== RUN Test_processRevealSig
--- FAIL: Test_processRevealSig (0.00s)
helpers_test.go:13: Expected:
otr3.OtrError{msg:"corrupt reveal signature message", conflict:false}
to equal:
helpers_test.go:13: Expected:
0x0
to equal:
0x1
...
=== RUN Test_generateSigKeyEncryptedSignature
--- FAIL: Test_generateSigKeyEncryptedSignature (0.00s)
helpers_test.go:13: Expected:
{s:"EOF"}
to equal:
helpers_test.go:69: Expected:
[]byte(nil)
to equal:
[]byte{0x0, 0x0, 0x1, 0xd2, 0xb4, 0xf6, 0xac, 0x65, 0xc, 0xc1, 0xd2,
0x8f, 0x61, 0xa3, 0xb9, 0xbd, 0xf3, 0xcd, 0x60, 0xe2, 0xd1, 0xea, 0x55, 0xd4,
0xc5, 0x6e, 0x9f, 0x95, 0x4e, 0xb2, 0x2e, 0x10, 0x76, 0x48, 0x61, 0xfb, 0x40,
0xd6, 0x99, 0x17, 0xf5, 0xc4, 0x24, 0x9f, 0xa7, 0x1, 0xf3, 0xc0, 0x4f, 0xae,
0x94, 0x49, 0xcd, 0x13, 0xa5, 0x5, 0x48, 0x61, 0xf9, 0x5f, 0xbc, 0x57, 0x75,
0xfc, 0x3c, 0xfd, 0x93, 0x1c, 0xf5, 0xcc, 0x1a, 0x89, 0xea, 0xc8, 0x2e, 0x72,
0x9, 0xb6, 0x7, 0xc4, 0xfb, 0xf1, 0x8d, 0xf9, 0x45, 0xe2, 0x3b, 0xd0, 0xe9,
0x13, 0x65, 0xfc, 0xc6, 0xc5, 0xda, 0xc0, 0x72, 0x70, 0x3d, 0xd8, 0xe2, 0x28,
0x73, 0x72, 0x10, 0x7f, 0x6a, 0x2c, 0xbb, 0x91, 0x39, 0xf5, 0xe8, 0x21, 0x8,
0xd4, 0xcb, 0xcc, 0x1c, 0x6c, 0xdf, 0xcc, 0x77, 0x20, 0x14, 0x13, 0x6e, 0x75,
0x63, 0x38, 0x74, 0x5e, 0x22, 0x10, 0xd4, 0x2c, 0x6e, 0x3e, 0xc4, 0xe9, 0xcf,
0x87, 0xfa, 0x8e, 0xbd, 0x81, 0x90, 0xe0, 0xf, 0x3a, 0x54, 0xbe, 0xc8,
Bug#918230: python-django: CVE-2019-3498: Content spoofing possibility in the default 404 page
Hi Moritz,
> > This also affects stable from my reading of the code. Shall I
> > prepare an upload to stretch-security?
[..]
> Please do.
debdiff attached, awaiting t...@security.debian.org ACK to upload.
Best wishes,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
diff --git a/debian/changelog b/debian/changelog
index b1c56f7c5..d6472a04e 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+python-django (1:1.10.7-2+deb9u4) stretch-security; urgency=high
+
+ * CVE-2019-3498: Fix a content spoofing vulnerability in the default
+404 page. (Closes: #918230)
+
+ -- Chris Lamb Sat, 05 Jan 2019 21:36:27 +0100
+
python-django (1:1.10.7-2+deb9u3) stretch; urgency=medium
* Default to supporting Spatialite >= 4.2. (Closes: #910240)
diff --git a/debian/patches/0017-CVE-2019-3498.patch
b/debian/patches/0017-CVE-2019-3498.patch
new file mode 100644
index 0..ea647e964
--- /dev/null
+++ b/debian/patches/0017-CVE-2019-3498.patch
@@ -0,0 +1,401 @@
+From: Tom Hacohen
+Date: Fri, 4 Jan 2019 02:21:55 +
+Subject: Fixed #30070,
+ CVE-2019-3498 -- Fixed content spoofing possiblity in the default 404 page.
+
+Co-Authored-By: Tim Graham
+Backport of 1ecc0a395be721e987e8e9fdfadde952b6dee1c7 from master.
+---
+ ...0006-Default-to-supporting-Spatialite-4.2.patch | 4 +--
+ debian/patches/0013-CVE-2018-7536.patch| 6 ++--
+ debian/patches/0015-CVE-2018-14574.patch | 2 +-
+ .../patches/02_disable-sources-in-sphinxdoc.diff | 5 ++--
+ .../06_use_debian_geoip_database_as_default.diff | 3 +-
+ debian/patches/fix-migration-fake-initial-1.patch | 20 ++
+ debian/patches/fix-migration-fake-initial-2.patch | 32 --
+ .../fix-test-middleware-classes-headers.patch | 7 ++---
+ debian/patches/series | 1 +
+ django/views/defaults.py | 8 --
+ tests/handlers/tests.py| 12 +---
+ 11 files changed, 65 insertions(+), 35 deletions(-)
+
+diff --git a/debian/patches/0006-Default-to-supporting-Spatialite-4.2.patch
b/debian/patches/0006-Default-to-supporting-Spatialite-4.2.patch
+index 6c92929..41e6f79 100644
+--- a/debian/patches/0006-Default-to-supporting-Spatialite-4.2.patch
b/debian/patches/0006-Default-to-supporting-Spatialite-4.2.patch
+@@ -14,10 +14,10 @@ See, for example:
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+ diff --git a/django/contrib/gis/db/backends/spatialite/base.py
b/django/contrib/gis/db/backends/spatialite/base.py
+-index 1f03868..6d0d631 100644
++index 44514a8..a26270b 100644
+ --- a/django/contrib/gis/db/backends/spatialite/base.py
+ +++ b/django/contrib/gis/db/backends/spatialite/base.py
+-@@ -35,7 +35,7 @@ class DatabaseWrapper(SQLiteDatabaseWrapper):
++@@ -30,7 +30,7 @@ class DatabaseWrapper(SQLiteDatabaseWrapper):
+ # cannot be found by `ctypes.util.find_library`), then it may be set
+ # manually in the settings via the `SPATIALITE_LIBRARY_PATH` setting.
+ self.spatialite_lib = getattr(settings, 'SPATIALITE_LIBRARY_PATH',
+diff --git a/debian/patches/0013-CVE-2018-7536.patch
b/debian/patches/0013-CVE-2018-7536.patch
+index 5b1be8f..e54ae4f 100644
+--- a/debian/patches/0013-CVE-2018-7536.patch
b/debian/patches/0013-CVE-2018-7536.patch
+@@ -5,8 +5,8 @@ Subject: Fix CVE-2018-7536 -- DOS in urlize
+ This is a security fix.
+ ---
+ django/utils/html.py | 33 +
+- tests/utils_tests/test_html.py | 9 +
+- 2 files changed, 30 insertions(+), 12 deletions(-)
++ tests/utils_tests/test_html.py | 8
++ 2 files changed, 29 insertions(+), 12 deletions(-)
+
+ diff --git a/django/utils/html.py b/django/utils/html.py
+ index a5cb56e..5a9f735 100644
+@@ -81,7 +81,7 @@ index a5cb56e..5a9f735 100644
+ try:
+ domain = domain.encode('idna').decode('ascii')
+ diff --git a/tests/utils_tests/test_html.py b/tests/utils_tests/test_html.py
+-index 20de851..9f76d48 100644
++index 20de851..8b683c1 100644
+ --- a/tests/utils_tests/test_html.py
+ +++ b/tests/utils_tests/test_html.py
+ @@ -231,3 +231,11 @@ class TestUtilsHtml(SimpleTestCase):
+diff --git a/debian/patches/0015-CVE-2018-14574.patch
b/debian/patches/0015-CVE-2018-14574.patch
+index c8bf439..2996c0a 100644
+--- a/debian/patches/0015-CVE-2018-14574.patch
b/debian/patches/0015-CVE-2018-14574.patch
+@@ -27,7 +27,7 @@ Backported by Chris Lamb from:
+ 6 files changed, 49 insertions(+), 4 deletions(-)
+
+ diff --git a/django/middleware/common.py b/django/middleware/common.py
+-index 4cec6f0..4ac5e01 100644
++index 4cec6f0..ca35bd4 100644
+ --- a/django/middleware/common.py
+ +++ b/django/middleware/common.py
+ @@ -9,6 +9,7 @@ from django.urls import is_valid_path
+diff --git a/debian/patches/02_disable-sources-in-sphinxdoc.diff
b/debian/patches/02_disable-sources-in-sphinxdoc.diff
Bug#918408: node-sqlite3 FTBFS with nodejs 10.15.0
Source: node-sqlite3
Version: 3.1.8+ds1-2
Severity: serious
Tags: ftbfs buster sid
Control: close -1 4.0.2+ds1-1
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-sqlite3.html
...
../src/database.cc: In static member function 'static
Nan::NAN_METHOD_RETURN_TYPE
node_sqlite3::Database::New(Nan::NAN_METHOD_ARGS_TYPE)':
../src/database.cc:133:18: error: 'class v8::Object' has no member named
'ForceSet'
info.This()->ForceSet(Nan::New("filename").ToLocalChecked(),
info[0].As(), ReadOnly);
^~~~
../src/database.cc:134:18: error: 'class v8::Object' has no member named
'ForceSet'
info.This()->ForceSet(Nan::New("mode").ToLocalChecked(), Nan::New(mode),
ReadOnly);
^~~~
...
The package in experimental seems to be fixed.
Processed: node-sqlite3 FTBFS with nodejs 10.15.0
Processing control commands: > close -1 4.0.2+ds1-1 Bug #918408 [src:node-sqlite3] node-sqlite3 FTBFS with nodejs 10.15.0 Marked as fixed in versions node-sqlite3/4.0.2+ds1-1. Bug #918408 [src:node-sqlite3] node-sqlite3 FTBFS with nodejs 10.15.0 Marked Bug as done -- 918408: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918408 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#918083: marked as done (cutesdr FTCBFS: does not pass cross flags to cmake)
Your message dated Sat, 05 Jan 2019 20:40:23 + with message-id and subject line Bug#918083: fixed in cutesdr 1.20-3 has caused the Debian Bug report #918083, regarding cutesdr FTCBFS: does not pass cross flags to cmake 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.) -- 918083: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918083 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cutesdr Version: 1.20-2 Severity: serious Justification: policy 4.6 Tags: patch User: helm...@debian.org Usertags: rebootstrap cutesdr fails to cross build from source, because its builds two cmake projects (one via dh_auto_foo and then the siqs directory explicitly in override_dh_auto_install) and the latter invocation lacks cross flags. The easiest way of fixing that is using dh_auto_configure. Doing so is sufficient to make cutesdr cross buildable. Please consider applying the attached patch. I also noticed that cutesdr chains build commands with ";". Doing so is prohibited by Debian policy section 4.6, thus satisfying serious severity. My patch fixes this issue as well. Please lower the severity of this bug if you fix the policy violation independently, but I think it would be least effort to simply use the patch thus filing only one bug. Helmut diff --minimal -Nru cutesdr-1.20/debian/changelog cutesdr-1.20/debian/changelog --- cutesdr-1.20/debian/changelog 2018-08-29 06:18:15.0 +0200 +++ cutesdr-1.20/debian/changelog 2019-01-02 22:07:05.0 +0100 @@ -1,3 +1,11 @@ +cutesdr (1.20-2.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix FTCBFS: Let dh_auto_configure pass cross flags to cmake. (Closes: #-1) + * Propagate errors from cmake (policy 4.6). + + -- Helmut Grohne Wed, 02 Jan 2019 22:07:05 +0100 + cutesdr (1.20-2) unstable; urgency=medium * update to svn r75, builds with qt5.11. (Closes:#907226) diff --minimal -Nru cutesdr-1.20/debian/rules cutesdr-1.20/debian/rules --- cutesdr-1.20/debian/rules 2018-05-23 05:01:12.0 +0200 +++ cutesdr-1.20/debian/rules 2019-01-02 22:07:05.0 +0100 @@ -8,7 +8,8 @@ override_dh_auto_install: dh_auto_install mkdir siqsbuild - (cd siqsbuild ; cmake ../siqs ; make) + dh_auto_configure --builddirectory=siqsbuild --sourcedirectory=siqs + dh_auto_build --builddirectory=siqsbuild cp siqsbuild/siqs_ftdi debian/cutesdr/usr/bin/siqs_ftdi rm -rf siqsbuild cp CuteSdr debian/cutesdr/usr/bin/CuteSdr --- End Message --- --- Begin Message --- Source: cutesdr Source-Version: 1.20-3 We believe that the bug you reported is fixed in the latest version of cutesdr, 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 918...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. A. Maitland Bottoms (supplier of updated cutesdr package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 05 Jan 2019 14:35:40 -0500 Source: cutesdr Binary: cutesdr Architecture: source Version: 1.20-3 Distribution: unstable Urgency: medium Maintainer: A. Maitland Bottoms Changed-By: A. Maitland Bottoms Description: cutesdr- simple demodulation and spectrum display program Closes: 918083 Changes: cutesdr (1.20-3) unstable; urgency=medium . * Fix FTCBFS: Let dh_auto_configure pass cross flags to cmake. (Closes: #918083) * Propagate errors from cmake (policy 4.6). Thanks Helmut! Checksums-Sha1: 1adf851f71c3d86dbe1f058ca0b1079c4ebfc9d4 2144 cutesdr_1.20-3.dsc 965f5c49ec908facbd4bc066823b392e8cf2ecb5 27224 cutesdr_1.20-3.debian.tar.xz 98b105ce726c3a8d979aa7a85b41a7b0db0a5ed8 13218 cutesdr_1.20-3_amd64.buildinfo Checksums-Sha256: f0ec72ffd5a1b47abbc280c05bd14c18073b2300f3ba73ac63f23694c3a27e1c 2144 cutesdr_1.20-3.dsc f9514045d3706781aea75666a81767a78603de7fb3595d69f8d5d758ea9fffea 27224 cutesdr_1.20-3.debian.tar.xz 2aa4e5c6bc529c127f60d611962c90aad66aab4dc1b5b58c3f6765e2b5eec5fb 13218 cutesdr_1.20-3_amd64.buildinfo Files: 23654e9d07919347e23515ce363addfe 2144 hamradio optional cutesdr_1.20-3.dsc d336ac0d62fa63c2ce4d412fe1a5bec9 27224 hamradio optional
Processed: ruby-rails-i18n FTBFS with rails 5.2.0
Processing control commands: > close -1 5.1.2-1 Bug #918406 [src:ruby-rails-i18n] ruby-rails-i18n FTBFS with rails 5.2.0 Marked as fixed in versions ruby-rails-i18n/5.1.2-1. Bug #918406 [src:ruby-rails-i18n] ruby-rails-i18n FTBFS with rails 5.2.0 Marked Bug as done -- 918406: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918406 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#918340: pylint-django build depends on python3-factory-boy that is currently not in buster
Hi Adrian, Thanks for the report. I was hoping to get a quick answer from https://github.com/FactoryBoy/factory_boy/issues/552 to push the new version of factory-boy without patching but I'll probably try to update the package and add the patch for python 3.7 that has been already merged so that the FTBS is fixed. I'll probably do that tomorrow if Brian is ok with it. Thanks, Joseph
Bug#918406: ruby-rails-i18n FTBFS with rails 5.2.0
Source: ruby-rails-i18n Version: 4.0.9-1 Severity: serious Tags: ftbfs Control: close -1 5.1.2-1 https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ruby-rails-i18n.html ... /usr/lib/ruby/2.5.0/rubygems/dependency.rb:312:in `to_specs': Could not find 'railties' (~> 4.0) - did find: [railties-5.2.0] (Gem::MissingSpecVersionError) ... The package in experimental seems to be fixed.
Bug#910318: factory-boy: do you mind if I upload the new version and fix the FTBS?
Hi Brian, One of my packages needs factory-boy to be able to run properly (see #918340). Do you mind if I upload the latest version of factory-boy and add the subset of the relevant patch that fixes the compatibility with python 3.7? (the part about factory/utils.py in https://github.com/FactoryBoy/factory_boy/commit/97f48597d241aca598783f7bcaed34bf7b133343) I can work on it asap if you don't mind me taking care of it. Thanks for your help, Joseph
Processed: tagging 918398
Processing commands for cont...@bugs.debian.org: > tags 918398 + pending Bug #918398 [wml] wml: missing dependencies on libio-all-perl and liblist-moreutils-perl Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 918398: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918398 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#907518: [RFC] Disable TLSv1.0 by default, but allow enabling it
On Tue, Dec 04, 2018 at 01:00:08PM +0100, Andrej Shadura wrote: > In the Debian bug reports #907518 and #911297 (see below), people complained > that OpenSSL 1.1.1 disables TLSv1.0 and some other insecure settings by > default, but some older networks may still require their support: > wpa_supplicant[523]: OpenSSL: pending error: error:140C618E:SSL > routines:SSL_use_certificate:ca md too weak > Some of those issues can be overrided by adding > openssl_ciphers=DEFAULT@SECLEVEL=1 > to the wpa config, but e.g. Kurt Roeckx complained that the minimum TLS > version is still 1.2: > > ssl_choose_client_version:version too low > > Unlike ciphers, that cannot be overridden in the wpa config, since > tls_disable_tlsv1_0 only allows disabling TLS versions, not enabling > them back if the default version is too high. I intend to apply > the patch below to wpa in Debian, which will enable switching TLSv1.0 > back if necessary by adding tls_disable_tlsv1_0=0 to the config. tls_disable_tlv1_0=0 in wpa_supplicant has actually been defined to enable TLSv1.0. However, the implementation handled that only within wpa_supplicant itself and not in a manner that would be able to override this systemwide default in OpenSSL parameters. It looks like the safest approach is to allow this explicit enabling to be used in configuration to do that override so that distributions are free to do whatever systemwide enforcement they want to expose to their users to try to enforce security while the users have an option of overriding that if there is no way of fixing the issue at the other end of the exchange. The following hostap.git commit does this: https://w1.fi/cgit/hostap/commit/?id=cc9c4feccc5588137f66c40a4a6729476556853e And as an example, the following network profile parameters would undo the Debian systemwide restrictions: phase1="tls_disable_tlsv1_0=0 tls_disable_tlsv1_1=0" openssl_ciphers="DEFAULT@SECLEVEL=1" -- Jouni MalinenPGP id EFC895FA
Processed: tagging 918398
Processing commands for cont...@bugs.debian.org: > tags 918398 + confirmed Bug #918398 [wml] wml: missing dependencies on libio-all-perl and liblist-moreutils-perl Added tag(s) confirmed. > thanks Stopping processing here. Please contact me if you need assistance. -- 918398: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918398 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 918404
Processing commands for cont...@bugs.debian.org: > tags 918404 + buster sid Bug #918404 [src:node-temporary] node-temporary FTBFS with nodejs 10.15.0 Added tag(s) buster and sid. > thanks Stopping processing here. Please contact me if you need assistance. -- 918404: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918404 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#918405: ruby-simple-navigation FTBFS with rails 5.2.0
Source: ruby-simple-navigation
Version: 4.0.3-1
Severity: serious
Tags: ftbfs buster sid
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ruby-simple-navigation.html
...
Failures:
1) SimpleNavigation::Renderer::Breadcrumbs#render sets the right html id on
the rendered 'div' tag
Failure/Error: let(:output) { HTML::Document.new(raw_output).root }
NameError:
uninitialized constant SimpleNavigation::Renderer::HTML
# ./spec/simple_navigation/renderer/breadcrumbs_spec.rb:8:in `block (2
levels) in '
# ./spec/simple_navigation/renderer/breadcrumbs_spec.rb:20:in `block (3
levels) in '
2) SimpleNavigation::Renderer::Breadcrumbs#render renders a 'div' tag for the
navigation
Failure/Error: let(:output) { HTML::Document.new(raw_output).root }
NameError:
uninitialized constant SimpleNavigation::Renderer::HTML
# ./spec/simple_navigation/renderer/breadcrumbs_spec.rb:8:in `block (2
levels) in '
# ./spec/simple_navigation/renderer/breadcrumbs_spec.rb:16:in `block (3
levels) in '
3) SimpleNavigation::Renderer::Breadcrumbs#render sets the right html classes
on the rendered 'div' tag
Failure/Error: let(:output) { HTML::Document.new(raw_output).root }
NameError:
uninitialized constant SimpleNavigation::Renderer::HTML
# ./spec/simple_navigation/renderer/breadcrumbs_spec.rb:8:in `block (2
levels) in '
# ./spec/simple_navigation/renderer/breadcrumbs_spec.rb:24:in `block (3
levels) in '
4) SimpleNavigation::Renderer::Breadcrumbs#render when a sub navigation item
is selected renders all items as links
Failure/Error: let(:output) { HTML::Document.new(raw_output).root }
NameError:
uninitialized constant SimpleNavigation::Renderer::HTML
# ./spec/simple_navigation/renderer/breadcrumbs_spec.rb:8:in `block (2
levels) in '
# ./spec/simple_navigation/renderer/breadcrumbs_spec.rb:100:in `block (4
levels) in '
5) SimpleNavigation::Renderer::Breadcrumbs#render when a sub navigation item
is selected when the :static_leaf option is true renders the items as links
Failure/Error: let(:output) { HTML::Document.new(raw_output).root }
NameError:
uninitialized constant SimpleNavigation::Renderer::HTML
# ./spec/simple_navigation/renderer/breadcrumbs_spec.rb:8:in `block (2
levels) in '
# ./spec/simple_navigation/renderer/breadcrumbs_spec.rb:107:in `block (5
levels) in '
6) SimpleNavigation::Renderer::Breadcrumbs#render when a sub navigation item
is selected when the :static_leaf option is true renders the last item as
simple text
Failure/Error: let(:output) { HTML::Document.new(raw_output).root }
NameError:
uninitialized constant SimpleNavigation::Renderer::HTML
# ./spec/simple_navigation/renderer/breadcrumbs_spec.rb:8:in `block (2
levels) in '
# ./spec/simple_navigation/renderer/breadcrumbs_spec.rb:111:in `block (5
levels) in '
7) SimpleNavigation::Renderer::Breadcrumbs#render when no item is selected
doesn't render any 'a' tag in the 'div' tag
Failure/Error: let(:output) { HTML::Document.new(raw_output).root }
NameError:
uninitialized constant SimpleNavigation::Renderer::HTML
# ./spec/simple_navigation/renderer/breadcrumbs_spec.rb:8:in `block (2
levels) in '
# ./spec/simple_navigation/renderer/breadcrumbs_spec.rb:29:in `block (4
levels) in '
8) SimpleNavigation::Renderer::Breadcrumbs#render when an item is selected
remders the 'a' tag without any html id
Failure/Error: let(:output) { HTML::Document.new(raw_output).root }
NameError:
uninitialized constant SimpleNavigation::Renderer::HTML
# ./spec/simple_navigation/renderer/breadcrumbs_spec.rb:8:in `block (2
levels) in '
# ./spec/simple_navigation/renderer/breadcrumbs_spec.rb:41:in `block (4
levels) in '
9) SimpleNavigation::Renderer::Breadcrumbs#render when an item is selected
renders the selected 'a' tag
Failure/Error: let(:output) { HTML::Document.new(raw_output).root }
NameError:
uninitialized constant SimpleNavigation::Renderer::HTML
# ./spec/simple_navigation/renderer/breadcrumbs_spec.rb:8:in `block (2
levels) in '
# ./spec/simple_navigation/renderer/breadcrumbs_spec.rb:37:in `block (4
levels) in '
10) SimpleNavigation::Renderer::Breadcrumbs#render when an item is selected
renders the 'a' tag without any html class
Failure/Error: let(:output) { HTML::Document.new(raw_output).root }
NameError:
uninitialized constant SimpleNavigation::Renderer::HTML
# ./spec/simple_navigation/renderer/breadcrumbs_spec.rb:8:in `block (2
levels) in '
# ./spec/simple_navigation/renderer/breadcrumbs_spec.rb:45:in `block (4
levels) in '
11) SimpleNavigation::Renderer::Breadcrumbs#render when an item is selected
and the :allow_classes_and_ids option is true renders the 'a' tag with the
selected class
Failure/Error: let(:output) {
Bug#918404: node-temporary FTBFS with nodejs 10.15.0
Source: node-temporary Version: 0.0.8-2 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-temporary.html ... 15 passing (290ms) 5 failing 1) Tempdir rmdir should remove the directory: TypeError [ERR_INVALID_CALLBACK]: Callback must be a function at makeCallback (fs.js:137:11) at Object.rmdir (fs.js:667:14) at Function.invoke (/usr/lib/nodejs/sinon/lib/sinon/spy.js:172:59) at Object.proxy [as rmdir] (eval at createProxy (/usr/lib/nodejs/sinon/lib/sinon/spy.js:77:17), :1:37) at Dir.rmdir (lib/dir.js:44:12) at Context. (test/dir.test.js:29:11) at callFn (/usr/lib/nodejs/mocha/lib/runnable.js:354:21) at Test.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:346:7) at Runner.runTest (/usr/lib/nodejs/mocha/lib/runner.js:442:10) at /usr/lib/nodejs/mocha/lib/runner.js:560:12 at next (/usr/lib/nodejs/mocha/lib/runner.js:356:14) at /usr/lib/nodejs/mocha/lib/runner.js:366:7 at next (/usr/lib/nodejs/mocha/lib/runner.js:290:14) at Immediate._onImmediate (/usr/lib/nodejs/mocha/lib/runner.js:334:5) 2) Tempfile readFile should call fs.readfile: TypeError [ERR_INVALID_CALLBACK]: Callback must be a function at maybeCallback (fs.js:129:9) at Object.readFile (fs.js:278:14) at Function.invoke (/usr/lib/nodejs/sinon/lib/sinon/spy.js:172:59) at Object.proxy [as readFile] (eval at createProxy (/usr/lib/nodejs/sinon/lib/sinon/spy.js:77:17), :1:39) at File.readFile (lib/file.js:44:15) at Context. (test/file.test.js:29:11) at callFn (/usr/lib/nodejs/mocha/lib/runnable.js:354:21) at Test.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:346:7) at Runner.runTest (/usr/lib/nodejs/mocha/lib/runner.js:442:10) at /usr/lib/nodejs/mocha/lib/runner.js:560:12 at next (/usr/lib/nodejs/mocha/lib/runner.js:356:14) at /usr/lib/nodejs/mocha/lib/runner.js:366:7 at next (/usr/lib/nodejs/mocha/lib/runner.js:290:14) at Immediate._onImmediate (/usr/lib/nodejs/mocha/lib/runner.js:334:5) 3) Tempfile writeFile should call fs.readfile: TypeError [ERR_INVALID_CALLBACK]: Callback must be a function at maybeCallback (fs.js:129:9) at Object.writeFile (fs.js:1159:14) at Function.invoke (/usr/lib/nodejs/sinon/lib/sinon/spy.js:172:59) at Object.proxy [as writeFile] (eval at createProxy (/usr/lib/nodejs/sinon/lib/sinon/spy.js:77:17), :1:41) at File.writeFile (lib/file.js:58:16) at Context. (test/file.test.js:49:11) at callFn (/usr/lib/nodejs/mocha/lib/runnable.js:354:21) at Test.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:346:7) at Runner.runTest (/usr/lib/nodejs/mocha/lib/runner.js:442:10) at /usr/lib/nodejs/mocha/lib/runner.js:560:12 at next (/usr/lib/nodejs/mocha/lib/runner.js:356:14) at /usr/lib/nodejs/mocha/lib/runner.js:366:7 at next (/usr/lib/nodejs/mocha/lib/runner.js:290:14) at Immediate._onImmediate (/usr/lib/nodejs/mocha/lib/runner.js:334:5) 4) Tempfile close should call fs.close: TypeError [ERR_INVALID_CALLBACK]: Callback must be a function at makeCallback (fs.js:137:11) at Object.close (fs.js:395:20) at Function.invoke (/usr/lib/nodejs/sinon/lib/sinon/spy.js:172:59) at Object.proxy [as close] (eval at createProxy (/usr/lib/nodejs/sinon/lib/sinon/spy.js:77:17), :1:37) at File.close (lib/file.js:86:12) at Context. (test/file.test.js:91:11) at callFn (/usr/lib/nodejs/mocha/lib/runnable.js:354:21) at Test.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:346:7) at Runner.runTest (/usr/lib/nodejs/mocha/lib/runner.js:442:10) at /usr/lib/nodejs/mocha/lib/runner.js:560:12 at next (/usr/lib/nodejs/mocha/lib/runner.js:356:14) at /usr/lib/nodejs/mocha/lib/runner.js:366:7 at next (/usr/lib/nodejs/mocha/lib/runner.js:290:14) at Immediate._onImmediate (/usr/lib/nodejs/mocha/lib/runner.js:334:5) 5) Tempfile unlink should call fs.unlink: TypeError [ERR_INVALID_CALLBACK]: Callback must be a function at makeCallback (fs.js:137:11) at Object.unlink (fs.js:939:14) at Function.invoke (/usr/lib/nodejs/sinon/lib/sinon/spy.js:172:59) at Object.proxy [as unlink] (eval at createProxy (/usr/lib/nodejs/sinon/lib/sinon/spy.js:77:17), :1:37) at File.unlink (lib/file.js:100:13) at Context. (test/file.test.js:112:11) at callFn (/usr/lib/nodejs/mocha/lib/runnable.js:354:21) at Test.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:346:7) at Runner.runTest (/usr/lib/nodejs/mocha/lib/runner.js:442:10) at /usr/lib/nodejs/mocha/lib/runner.js:560:12 at next (/usr/lib/nodejs/mocha/lib/runner.js:356:14) at /usr/lib/nodejs/mocha/lib/runner.js:366:7 at next
Bug#918398: wml: missing dependencies on libio-all-perl and liblist-moreutils-perl
Hi Adrian, Adrian Bunk wrote: > Can't locate IO/All.pm in @INC (you may need to install the IO::All module) > (@INC contains: /usr/share/wml /usr/lib/x86_64-linux-gnu/wml /etc/perl > /usr/local/lib/x86_64-linux-gnu/perl/5.28.1 /usr/local/share/perl/5.28.1 > /usr/lib/x86_64-linux-gnu/perl5/5.28 /usr/share/perl5 > /usr/lib/x86_64-linux-gnu/perl/5.28 /usr/share/perl/5.28 > /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base .) at > /usr/share/wml/TheWML/CmdLine/IO.pm line 6. Thanks for the bug report! Will prepare an upload directly after this mail. Regards, Axel -- ,''`. | Axel Beckert , https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
Bug#918403: ruby-rack-pjax FTBFS with ruby-rack 2.0.6-2
Source: ruby-rack-pjax
Version: 0.7.0-2
Severity: serious
Tags: ftbfs buster sid
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ruby-rack-pjax.html
...
┌──┐
│ Run tests for ruby2.5 from debian/ruby-tests.rake│
└──┘
RUBYLIB=/build/1st/ruby-rack-pjax-0.7.0/debian/ruby-rack-pjax/usr/lib/ruby/vendor_ruby:.
GEM_PATH=debian/ruby-rack-pjax/usr/share/rubygems-integration/all:/var/lib/gems/2.5.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all
ruby2.5 -S rake -f debian/ruby-tests.rake
/usr/bin/ruby2.5 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb
FFF
Failures:
1) Rack::Pjax a pjaxified app, upon receiving a pjax-request should return
the title-tag in the body
Failure/Error: {'Content-Type' => 'text/plain', 'Content-Length' =>
Rack::Utils.bytesize(body).to_s},
NoMethodError:
undefined method `bytesize' for Rack::Utils:Module
# ./spec/rack/pjax_spec.rb:14:in `block in generate_app'
# ./lib/rack/pjax.rb:12:in `call'
# ./spec/rack/pjax_spec.rb:28:in `block (3 levels) in '
2) Rack::Pjax a pjaxified app, upon receiving a pjax-request should return
the inner-html of the pjax-container in the body
Failure/Error: {'Content-Type' => 'text/plain', 'Content-Length' =>
Rack::Utils.bytesize(body).to_s},
NoMethodError:
undefined method `bytesize' for Rack::Utils:Module
# ./spec/rack/pjax_spec.rb:14:in `block in generate_app'
# ./lib/rack/pjax.rb:12:in `call'
# ./spec/rack/pjax_spec.rb:35:in `block (3 levels) in '
3) Rack::Pjax a pjaxified app, upon receiving a pjax-request should return
the inner-html of the custom pjax-container in the body
Failure/Error: {'Content-Type' => 'text/plain', 'Content-Length' =>
Rack::Utils.bytesize(body).to_s},
NoMethodError:
undefined method `bytesize' for Rack::Utils:Module
# ./spec/rack/pjax_spec.rb:14:in `block in generate_app'
# ./lib/rack/pjax.rb:12:in `call'
# ./spec/rack/pjax_spec.rb:42:in `block (3 levels) in '
4) Rack::Pjax a pjaxified app, upon receiving a pjax-request should handle
self closing tags with HTML5 elements
Failure/Error: {'Content-Type' => 'text/plain', 'Content-Length' =>
Rack::Utils.bytesize(body).to_s},
NoMethodError:
undefined method `bytesize' for Rack::Utils:Module
# ./spec/rack/pjax_spec.rb:14:in `block in generate_app'
# ./lib/rack/pjax.rb:12:in `call'
# ./spec/rack/pjax_spec.rb:49:in `block (3 levels) in '
5) Rack::Pjax a pjaxified app, upon receiving a pjax-request should handle
nesting of elements inside anchor tags
Failure/Error: {'Content-Type' => 'text/plain', 'Content-Length' =>
Rack::Utils.bytesize(body).to_s},
NoMethodError:
undefined method `bytesize' for Rack::Utils:Module
# ./spec/rack/pjax_spec.rb:14:in `block in generate_app'
# ./lib/rack/pjax.rb:12:in `call'
# ./spec/rack/pjax_spec.rb:57:in `block (3 levels) in '
6) Rack::Pjax a pjaxified app, upon receiving a pjax-request should handle
html5 br tags correctly
Failure/Error: {'Content-Type' => 'text/plain', 'Content-Length' =>
Rack::Utils.bytesize(body).to_s},
NoMethodError:
undefined method `bytesize' for Rack::Utils:Module
# ./spec/rack/pjax_spec.rb:14:in `block in generate_app'
# ./lib/rack/pjax.rb:12:in `call'
# ./spec/rack/pjax_spec.rb:65:in `block (3 levels) in '
7) Rack::Pjax a pjaxified app, upon receiving a pjax-request should return
the correct Content Length
Failure/Error: {'Content-Type' => 'text/plain', 'Content-Length' =>
Rack::Utils.bytesize(body).to_s},
NoMethodError:
undefined method `bytesize' for Rack::Utils:Module
# ./spec/rack/pjax_spec.rb:14:in `block in generate_app'
# ./lib/rack/pjax.rb:12:in `call'
# ./spec/rack/pjax_spec.rb:71:in `block (3 levels) in '
8) Rack::Pjax a pjaxified app, upon receiving a pjax-request should return
the original body when there's no pjax-container
Failure/Error: {'Content-Type' => 'text/plain', 'Content-Length' =>
Rack::Utils.bytesize(body).to_s},
NoMethodError:
undefined method `bytesize' for Rack::Utils:Module
# ./spec/rack/pjax_spec.rb:14:in `block in generate_app'
# ./lib/rack/pjax.rb:12:in `call'
# ./spec/rack/pjax_spec.rb:78:in `block (3 levels) in '
9) Rack::Pjax a pjaxified app, upon receiving a pjax-request should preserve
whitespaces of the original body
Failure/Error: {'Content-Type' => 'text/plain', 'Content-Length' =>
Rack::Utils.bytesize(body).to_s},
NoMethodError:
undefined method `bytesize' for Rack::Utils:Module
# ./spec/rack/pjax_spec.rb:14:in `block in generate_app'
# ./lib/rack/pjax.rb:12:in `call'
#
Bug#918402: open-build-service FTBFS with rails 5.2.0
Source: open-build-service Version: 2.7.4-3 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/open-build-service.html ... /usr/lib/ruby/vendor_ruby/bundler/resolver.rb:289:in `block in verify_gemfile_dependencies_are_found!': Could not find gem 'rails (~> 4.2.2)' in any of the gem sources listed in your Gemfile. (Bundler::GemNotFound) ...
Processed: python-pygments must depend on python3-pygments (or a new package for pygmentize)
Processing control commands: > affects -1 src:ruby-albino src:ask Bug #918401 [python-pygments] python-pygments must depend on python3-pygments (or a new package for pygmentize) Added indication that 918401 affects src:ruby-albino and src:ask -- 918401: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918401 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#918401: python-pygments must depend on python3-pygments (or a new package for pygmentize)
Package: python-pygments Version: 2.3.1+dfsg-1 Severity: serious Control: affects -1 src:ruby-albino src:ask Programs like pygmentize should be in an own package, not part of some module package. In any case python-pygments must depend on whatever package ships pygmentize now, examples for the breakage this will fix: https://ci.debian.net/data/autopkgtest/testing/amd64/r/ruby-albino/1643948/log.gz https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ask.html
Processed: Re: More info
Processing control commands: > tag -1 moreinfo Bug #918322 [initramfs-tools] 4.19.0-1-amd64 kernel fails to boot with "Gave up waiting for root file system device" Added tag(s) moreinfo. -- 918322: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918322 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#918322: More info
Control: tag -1 moreinfo On Sat, 5 Jan 2019 02:22:33 + Jakub Sokołowski wrote: > Seems like I failed to add additional info: > > Picture of error: https://mega.nz/#!LehDlKbB!x_pFGX3wlq-Kgo6v5jUC6ydbqTQ4R43bft7mAC6j_ms > > This seems to be realted to initrd since when I ran update-initramfs on an older kernel that one started showing the same symptoms as the new one. But initramfs-tools has not been updated for some months. Do you have udev version 240-1 installed? Ben. -- Ben Hutchings Absolutum obsoletum. (If it works, it's out of date.) - Stafford Beer signature.asc Description: This is a digitally signed message part
Processed: severity of 918322 is important
Processing commands for cont...@bugs.debian.org: > severity 918322 important Bug #918322 [initramfs-tools] 4.19.0-1-amd64 kernel fails to boot with "Gave up waiting for root file system device" Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 918322: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918322 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#918398: wml: missing dependencies on libio-all-perl and liblist-moreutils-perl
Package: wml Version: 2.12.0~ds1-3 Severity: serious Control: affects -1 src:doc-debian https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/doc-debian.html ... wml -i bug-pkgreport-opts.inc -q bug-log-access.wml >bug-log-access.html Can't locate IO/All.pm in @INC (you may need to install the IO::All module) (@INC contains: /usr/share/wml /usr/lib/x86_64-linux-gnu/wml /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.28.1 /usr/local/share/perl/5.28.1 /usr/lib/x86_64-linux-gnu/perl5/5.28 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.28 /usr/share/perl/5.28 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base .) at /usr/share/wml/TheWML/CmdLine/IO.pm line 6. BEGIN failed--compilation aborted at /usr/share/wml/TheWML/CmdLine/IO.pm line 6. Compilation failed in require at /usr/share/wml/TheWML/CmdLine/Base.pm line 6. BEGIN failed--compilation aborted at /usr/share/wml/TheWML/CmdLine/Base.pm line 6. Compilation failed in require at /usr/share/perl/5.28/parent.pm line 16. BEGIN failed--compilation aborted at /usr/share/wml/TheWML/Frontends/Wml/Runner.pm line 18. Compilation failed in require at /usr/bin/wml line 45. BEGIN failed--compilation aborted at /usr/bin/wml line 45. make[1]: *** [Makefile:40: bug-log-access.html] Error 2
Processed: wml: missing dependencies on libio-all-perl and liblist-moreutils-perl
Processing control commands: > affects -1 src:doc-debian Bug #918398 [wml] wml: missing dependencies on libio-all-perl and liblist-moreutils-perl Added indication that 918398 affects src:doc-debian -- 918398: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918398 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#918396: golang-github-glendc-gopher-json FTBFS with Go 1.11
Source: golang-github-glendc-gopher-json Version: 0.1.0+git20170414.0.dc47430-4 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-github-glendc-gopher-json.html ... dh_auto_test -O--buildsystem=golang cd obj-x86_64-linux-gnu && go test -vet=off -v -p 16 github.com/glendc/gopher-json === RUN TestSimple --- FAIL: TestSimple (0.00s) json_test.go:59: cannot encode recursively nested tables to JSON stack traceback: [G]: in function 'encode' :45: in main chunk [G]: ? === RUN TestCustomRequire --- PASS: TestCustomRequire (0.00s) FAIL FAILgithub.com/glendc/gopher-json 0.007s dh_auto_test: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 16 github.com/glendc/gopher-json returned exit code 1 make: *** [debian/rules:4: build] Error 1
Bug#918395: thumbor FTBFS: test failure in test_redeye_applied
Package: src:thumbor Version: 6.5.1-3 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Hi! I've been doing a full rebuild of the Debian archive, building all source packages targeting armel and armhf using arm64 hardware. We are planning in future to move all of our 32-bit armel/armhf builds to using arm64 machines, so this rebuild is to identify packages that might have problems with this configuration. I've found that thumbor exhibits test failures as armhf on aem64, but the problem is generic. I can see that it also shows the same failure in sid at the moment for amd64: == ERROR: test_redeye_applied (tests.filters.test_redeye.RedEyeFilterTestCase) -- Traceback (most recent call last): File "/work/stemci01/debian/build/thumbor/thumbor-6.5.1/.pybuild/cpython2_2.7_thumbor/build/tests/filters/test_redeye.py", line 43, in test_redeye_applied config_context File "/work/stemci01/debian/build/thumbor/thumbor-6.5.1/.pybuild/cpython2_2.7_thumbor/build/tests/base.py", line 279, in get_filtered fltr.run(dummy_callback) File "thumbor/filters/__init__.py", line 202, in run results.append(self.runnable_method(*self.params)) File "thumbor/filters/__init__.py", line 23, in wrapper return fn(self, *args2) File "thumbor/filters/redeye.py", line 38, in red_eye image.setflags(write=1) ValueError: cannot set WRITEABLE flag to True of this array >> begin captured logging << PIL.PngImagePlugin: DEBUG: STREAM 'IHDR' 16 13 PIL.PngImagePlugin: DEBUG: STREAM 'IDAT' 41 358237 PIL.PngImagePlugin: DEBUG: STREAM 'IHDR' 16 13 PIL.PngImagePlugin: DEBUG: STREAM 'IDAT' 41 65536 PIL.PngImagePlugin: DEBUG: STREAM 'IHDR' 16 13 PIL.PngImagePlugin: DEBUG: STREAM 'IDAT' 41 358944 - >> end captured logging << - Full log for armhf online at: https://www.einval.com/debian/arm/rebuild-logs/armhf/FAIL/thumbor_6.5.1-3_armhf.log -- System Information: Debian Release: 9.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-debug'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-8-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)
Processed: reassign 918386 to src:vm, forcibly merging 916875 918386
Processing commands for cont...@bugs.debian.org: > reassign 918386 src:vm Bug #918386 [vm] emacs-gtk: Emacs-gtk insall fail - install script from vm package failed - buster Bug reassigned from package 'vm' to 'src:vm'. Ignoring request to alter found versions of bug #918386 to the same values previously set Ignoring request to alter fixed versions of bug #918386 to the same values previously set > forcemerge 916875 918386 Bug #916875 [src:vm] vm: FTBFS with Emacs 26.1: Variable name missing after Bug #918386 [src:vm] emacs-gtk: Emacs-gtk insall fail - install script from vm package failed - buster Marked as found in versions vm/8.2.0b-4. Added tag(s) ftbfs and patch. Merged 916875 918386 > thanks Stopping processing here. Please contact me if you need assistance. -- 916875: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916875 918386: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918386 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
