Bug#907538: marked as done (audit: FTBFS: /usr/bin/ld: lookup_test.o: file not recognized: file truncated)
Your message dated Fri, 31 Aug 2018 05:48:56 + with message-id and subject line Bug#907538: fixed in audit 1:2.8.4-2 has caused the Debian Bug report #907538, regarding audit: FTBFS: /usr/bin/ld: lookup_test.o: file not recognized: file truncated to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 907538: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907538 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: audit Version: 1:2.8.4-1 Severity: serious The latest upload of audit FTBFS on various architectures. It looks like a test program is built twice in parallel and make stumbles upon that[1]: , | make[5]: Entering directory '/<>/debian/build/auparse/test' | gcc -DHAVE_CONFIG_H -I. -I../../../../auparse/test -I../.. -I../../../../auparse -I../../../../lib -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o auparse_test.o ../../../../auparse/test/auparse_test.c | ../../../../auparse/test/auparselol_test.c: In function 'main': | ../../../../auparse/test/auparselol_test.c:219:46: warning: format '%lu' expects argument of type 'long unsigned int', but argument 4 has type 'unsigned int' [-Wformat=] | "%s: No memory to allocate %lu bytes\n", | ~~^ | %u | argv[0], sizeof(int)); | ~~~ | /bin/bash ../../libtool --tag=CC --mode=link gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -static -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -o auparselol_test auparselol_test.o ../../auparse/libauparse.la ../../lib/libaudit.la | libtool: link: gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z -Wl,relro -Wl,-z -Wl,now -Wl,--as-needed -o auparselol_test auparselol_test.o ../../auparse/.libs/libauparse.a /<>/debian/build/lib/.libs/libaudit.a ../../lib/.libs/libaudit.a -lcap-ng | /bin/bash ../../libtool --tag=CC --mode=link gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -static -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -o auparse_test auparse_test.o ../../auparse/libauparse.la ../../lib/libaudit.la | gcc -DHAVE_CONFIG_H -I. -I../../../../auparse/test -I../.. -I../../../../auparse -I../../../../lib -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o auparselol_test.o ../../../../auparse/test/auparselol_test.c | gcc -DHAVE_CONFIG_H -I. -I../../../../auparse/test -I../.. -I../../../../auparse -I../../../../lib -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o lookup_test.o ../../../../auparse/test/lookup_test.c | make[5]: Nothing to be done for '../../../../auparse/test/auparse_test.py'. | ../../../../auparse/test/auparselol_test.c: In function 'main': | ../../../../auparse/test/auparselol_test.c:219:46: warning: format '%lu' expects argument of type 'long unsigned int', but argument 4 has type 'unsigned int' [-Wformat=] | "%s: No memory to allocate %lu bytes\n", | ~~^ | %u | argv[0], sizeof(int)); | ~~~ | libtool: link: gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z -Wl,relro -Wl,-z -Wl,now -Wl,--as-needed -o auparse_test auparse_test.o ../../auparse/.libs/libauparse.a /<>/debian/build/lib/.libs/libaudit.a ../../lib/.libs/libaudit.a -lcap-ng | /bin/bash ../../libtool --tag=CC --mode=link gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -static -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -o auparse_test auparse_test.o ../../auparse/libauparse.la ../../lib/libaudit.la | /bin/bash ../../libtool --tag=CC --mode=link gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -static -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -o auparselol_test auparselol_test.o ../../auparse/libauparse.la ../../lib/libaudit.la | libtool: link: gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z -Wl,relro -Wl,-z -Wl,now -Wl,--as-needed -o auparselol_test auparselol_test.o
Bug#906380: libtool: FTBFS in buster/sid
Dear Juhani Numminen, Could you upload the built libtool binary somewhere so I could install it and see if the issue goes away ? Thank you. I'll share my findings on the bug itself. -- Regards, Shirish Agarwal शिरीष अग्रवाल My quotes in this email licensed under CC 3.0 http://creativecommons.org/licenses/by-nc/3.0/ http://flossexperiences.wordpress.com EB80 462B 08E1 A0DE A73A 2C2F 9F3D C7A4 E1C4 D2D8
Processed: forcibly merging 905913 905838
Processing commands for cont...@bugs.debian.org: > # The latter caused by an incorrect sponsor upload into unstable as explained > in the former > forcemerge 905913 905838 Bug #905913 [src:sane-backends] sane-backends: Don't install into testing Bug #905838 [src:sane-backends] sane-backends: please, do not confuse the user by having "experimental" in the package version in unstable Severity set to 'serious' from 'normal' 902557 was blocked by: 904740 901082 895959 904737 897790 902556 901085 902674 900832 905913 904914 904735 904727 899021 900232 629405 897724 902771 862678 902557 was not blocking any bugs. Added blocking bug(s) of 902557: 905838 Merged 905838 905913 > thanks Stopping processing here. Please contact me if you need assistance. -- 902557: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902557 905838: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905838 905913: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905913 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#869585: (No Subject)
I understand Debian Stable = frozen packages, but is this really not something that can just be fixed in stable? It's pretty severe.
Bug#907493: ghostscript breaks cups autopkgtest: test times out
Quoting Paul Gevers (2018-08-29 20:24:49) > Control: tags -1 moreinfo > > Hi, > > On 29-08-18 20:20, Jonas Smedegaard wrote: > > Thanks - that is indeed helpful, but provides only the _cups_ commands. > > > > Inside those are some Ghostscript command (and some data) which I would > > need to check if/what fails with Ghostscript. > > Both of them are "ELF 64-bit LSB shared object" so it would help if the > cups maintainers could help here. Do the freshly released experimental Ghostscript release help anything? - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#906997: lua-sec: FTBFS with OpenSSL 1.1.1: test failure
On Thu 2018-08-30 15:38:50 -0400, Daniel Kahn Gillmor wrote: > On Thu 2018-08-30 15:25:49 -0400, Daniel Kahn Gillmor wrote: >> the NMU uses the attached patches, which i'll push to salsa as well >> shortly. > > The changes are available on salsa at > https://salsa.debian.org/lua-team/lua-sec/merge_requests/1. > > They also merge in upstream's git history, which should make it easier > to cherry-pick from upstream in the future. I've just updated debian/patches/0010-*.patch to cover the transition from sha1 to sha256 as well. I made that 0.6-4.2 and uploaded it as an NMU. the current version of that patch is attached below, and i've updated the merge request on salsa. Regards, --dkg From: Daniel Kahn Gillmor Date: Thu, 30 Aug 2018 14:53:01 -0400 Subject: use 2048-bit RSA keys and sha256 instead of 1024-bit RSA and sha1 According to Kurt Roeckx in https://bugs.debian.org/906997, the test suite is failing when built against libssl 1.1.1 because we require at least 2048-bit keys. We also move from sha1 to sha256, as we're updating our cryptographic primitives. --- samples/certs/clientA.bat | 4 ++-- samples/certs/clientA.cnf | 4 ++-- samples/certs/clientA.sh | 4 ++-- samples/certs/clientB.bat | 4 ++-- samples/certs/clientB.cnf | 4 ++-- samples/certs/clientB.sh | 4 ++-- samples/certs/rootA.bat| 4 ++-- samples/certs/rootA.cnf| 4 ++-- samples/certs/rootA.sh | 4 ++-- samples/certs/rootB.bat| 4 ++-- samples/certs/rootB.cnf| 4 ++-- samples/certs/rootB.sh | 4 ++-- samples/certs/serverA.bat | 4 ++-- samples/certs/serverA.cnf | 4 ++-- samples/certs/serverA.sh | 4 ++-- samples/certs/serverB.bat | 4 ++-- samples/certs/serverB.cnf | 4 ++-- samples/certs/serverB.sh | 4 ++-- samples/dhparam/params.sh | 2 +- samples/dhparam/server.lua | 4 ++-- 20 files changed, 39 insertions(+), 39 deletions(-) diff --git a/samples/certs/clientA.bat b/samples/certs/clientA.bat index 112cdef..f70a832 100644 --- a/samples/certs/clientA.bat +++ b/samples/certs/clientA.bat @@ -1,8 +1,8 @@ rem #!/bin/sh -openssl req -newkey rsa:1024 -sha1 -keyout clientAkey.pem -out clientAreq.pem -nodes -config ./clientA.cnf -days 365 -batch +openssl req -newkey rsa:2048 -sha256 -keyout clientAkey.pem -out clientAreq.pem -nodes -config ./clientA.cnf -days 365 -batch -openssl x509 -req -in clientAreq.pem -sha1 -extfile ./clientA.cnf -extensions usr_cert -CA rootA.pem -CAkey rootAkey.pem -CAcreateserial -out clientAcert.pem -days 365 +openssl x509 -req -in clientAreq.pem -sha256 -extfile ./clientA.cnf -extensions usr_cert -CA rootA.pem -CAkey rootAkey.pem -CAcreateserial -out clientAcert.pem -days 365 copy clientAcert.pem + rootA.pem clientA.pem diff --git a/samples/certs/clientA.cnf b/samples/certs/clientA.cnf index f938d90..d88219c 100644 --- a/samples/certs/clientA.cnf +++ b/samples/certs/clientA.cnf @@ -67,7 +67,7 @@ cert_opt = ca_default # Certificate field options default_days = 365 # how long to certify for default_crl_days= 30 # how long before next CRL -default_md = sha1 # which md to use. +default_md = sha256 # which md to use. preserve = no # keep passed DN ordering # A few difference way of specifying how similar the request should look @@ -98,7 +98,7 @@ emailAddress = optional [ req ] -default_bits = 1024 +default_bits = 2048 default_keyfile = privkey.pem distinguished_name = req_distinguished_name attributes = req_attributes diff --git a/samples/certs/clientA.sh b/samples/certs/clientA.sh index 0350ede..118e186 100755 --- a/samples/certs/clientA.sh +++ b/samples/certs/clientA.sh @@ -1,9 +1,9 @@ #!/bin/sh -openssl req -newkey rsa:1024 -sha1 -keyout clientAkey.pem -out clientAreq.pem \ +openssl req -newkey rsa:2048 -sha256 -keyout clientAkey.pem -out clientAreq.pem \ -nodes -config ./clientA.cnf -days 365 -batch -openssl x509 -req -in clientAreq.pem -sha1 -extfile ./clientA.cnf \ +openssl x509 -req -in clientAreq.pem -sha256 -extfile ./clientA.cnf \ -extensions usr_cert -CA rootA.pem -CAkey rootAkey.pem -CAcreateserial \ -out clientAcert.pem -days 365 diff --git a/samples/certs/clientB.bat b/samples/certs/clientB.bat index 9f341f6..ded7537 100644 --- a/samples/certs/clientB.bat +++ b/samples/certs/clientB.bat @@ -1,8 +1,8 @@ rem #!/bin/sh -openssl req -newkey rsa:1024 -sha1 -keyout clientBkey.pem -out clientBreq.pem -nodes -config ./clientB.cnf -days 365 -batch +openssl req -newkey rsa:2048 -sha256 -keyout clientBkey.pem -out clientBreq.pem -nodes -config ./clientB.cnf -days 365 -batch -openssl x509 -req -in clientBreq.pem -sha1 -extfile ./clientB.cnf -extensions usr_cert -CA rootB.pem -CAkey rootBkey.pem -CAcreateserial -out clientBcert.pem -days 365 +openssl x509 -req -in clientBreq.pem -sha256 -extfile ./clientB.cnf -extensions usr_cert -CA rootB.pem -CAkey rootBkey.pem -CAcreateserial -out clientBcert.pem -days 365 copy clientBcert.pem +
Bug#907663: subdownloader depends on python-kaa-metadata
Package: subdownloader Version: 2.0.18-2.1 Severity: serious Tags: fixed-upstream Control: block -1 by 892751 subdownloader is the last reverse dependency of python-kaa-metadata which has already been removed from testing. Upstream version 2.0.19 supports pymediainfo as fallback.
Processed: subdownloader depends on python-kaa-metadata
Processing control commands: > block -1 by 892751 Bug #907663 [subdownloader] subdownloader depends on python-kaa-metadata 907663 was not blocked by any bugs. 907663 was not blocking any bugs. Added blocking bug(s) of 907663: 892751 -- 907663: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907663 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#887868: marked as done (libgnomecanvas FTBFS with gtk-doc-tools 1.27-1)
Your message dated Thu, 30 Aug 2018 21:24:04 + with message-id and subject line Bug#887868: fixed in libgnomecanvas 2.30.3-4 has caused the Debian Bug report #887868, regarding libgnomecanvas FTBFS with gtk-doc-tools 1.27-1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 887868: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887868 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libgnomecanvas Version: 2.30.3-3 Severity: serious Tags: buster sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libgnomecanvas.html ... Making all in reference make[4]: Entering directory '/build/1st/libgnomecanvas-2.30.3/docs/reference' gtk-doc: Scanning header files gtk-doc: Building XML ./libgnomecanvas.args:7: warning: Property GnomeCanvasBpath:bpath has no documentation. ./libgnomecanvas.args:17: warning: Property GnomeCanvasClipgroup:path has no documentation. ./libgnomecanvas.args:27: warning: Property GnomeCanvasClipgroup:wind has no documentation. ./libgnomecanvas.args:47: warning: Property GnomeCanvas:focused-item has no documentation. ./libgnomecanvas.args:77: warning: Property GnomeCanvasItem:parent has no documentation. ./libgnomecanvas.args:87: warning: Property GnomeCanvasLine:arrow-shape-a has no documentation. ./libgnomecanvas.args:97: warning: Property GnomeCanvasLine:arrow-shape-b has no documentation. ./libgnomecanvas.args:107: warning: Property GnomeCanvasLine:arrow-shape-c has no documentation. ./libgnomecanvas.args:117: warning: Property GnomeCanvasLine:cap-style has no documentation. ./libgnomecanvas.args:127: warning: Property GnomeCanvasLine:fill-color has no documentation. ./libgnomecanvas.args:137: warning: Property GnomeCanvasLine:fill-color-gdk has no documentation. ./libgnomecanvas.args:147: warning: Property GnomeCanvasLine:fill-color-rgba has no documentation. ./libgnomecanvas.args:157: warning: Property GnomeCanvasLine:fill-stipple has no documentation. ./libgnomecanvas.args:167: warning: Property GnomeCanvasLine:first-arrowhead has no documentation. ./libgnomecanvas.args:177: warning: Property GnomeCanvasLine:join-style has no documentation. ./libgnomecanvas.args:187: warning: Property GnomeCanvasLine:last-arrowhead has no documentation. ./libgnomecanvas.args:197: warning: Property GnomeCanvasLine:line-style has no documentation. ./libgnomecanvas.args:207: warning: Property GnomeCanvasLine:points has no documentation. ./libgnomecanvas.args:217: warning: Property GnomeCanvasLine:smooth has no documentation. ./libgnomecanvas.args:227: warning: Property GnomeCanvasLine:spline-steps has no documentation. ./libgnomecanvas.args:237: warning: Property GnomeCanvasLine:width-pixels has no documentation. ./libgnomecanvas.args:247: warning: Property GnomeCanvasLine:width-units has no documentation. ./libgnomecanvas.args:257: warning: Property GnomeCanvasPixbuf:anchor has no documentation. ./libgnomecanvas.args:267: warning: Property GnomeCanvasPixbuf:height has no documentation. ./libgnomecanvas.args:277: warning: Property GnomeCanvasPixbuf:height-in-pixels has no documentation. ./libgnomecanvas.args:287: warning: Property GnomeCanvasPixbuf:height-set has no documentation. ./libgnomecanvas.args:297: warning: Property GnomeCanvasPixbuf:pixbuf has no documentation. ./libgnomecanvas.args:307: warning: Property GnomeCanvasPixbuf:width has no documentation. ./libgnomecanvas.args:317: warning: Property GnomeCanvasPixbuf:width-in-pixels has no documentation. ./libgnomecanvas.args:327: warning: Property GnomeCanvasPixbuf:width-set has no documentation. ./libgnomecanvas.args:337: warning: Property GnomeCanvasPixbuf:x has no documentation. ./libgnomecanvas.args:347: warning: Property GnomeCanvasPixbuf:x-in-pixels has no documentation. ./libgnomecanvas.args:357: warning: Property GnomeCanvasPixbuf:y has no documentation. ./libgnomecanvas.args:367: warning: Property GnomeCanvasPixbuf:y-in-pixels has no documentation. ./libgnomecanvas.args:377: warning: Property GnomeCanvasPolygon:points has no documentation. ./libgnomecanvas.args:387: warning: Property GnomeCanvasRE:x1 has no documentation. ./libgnomecanvas.args:397: warning: Property GnomeCanvasRE:x2 has no documentation. ./libgnomecanvas.args:407: warning: Property GnomeCanvasRE:y1 has no documentation. ./libgnomecanvas.args:417: warning: Property GnomeCanvasRE:y2 has no documentation. ./libgnomecanvas.args:627: warning: Property GnomeCanvasShape:cap-style has no documentation. ./libgnomecanvas.args:637: warning: Property GnomeCanvasShape:dash has no documentation.
Bug#886063: marked as done (libgnomecanvas: Don't release with Buster)
Your message dated Thu, 30 Aug 2018 21:24:04 + with message-id and subject line Bug#886063: fixed in libgnomecanvas 2.30.3-4 has caused the Debian Bug report #886063, regarding libgnomecanvas: Don't release with Buster 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.) -- 886063: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886063 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libgnomecanvas Version: 2.30.3-3 Severity: serious User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs libgnomecanvas Tags: sid buster As announced [1], we do not intend to release Debian 10 "Buster" with the old libgnome (and related) libraries. libgnomecanvas is one of these unmaintained libraries. [1] https://lists.debian.org/debian-devel/2017/10/msg00299.html On behalf of the Debian GNOME team, Jeremy Bicha --- End Message --- --- Begin Message --- Source: libgnomecanvas Source-Version: 2.30.3-4 We believe that the bug you reported is fixed in the latest version of libgnomecanvas, 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 886...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Adrian Bunk (supplier of updated libgnomecanvas 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: Thu, 30 Aug 2018 23:19:52 +0300 Source: libgnomecanvas Binary: libgnomecanvas2-0 libgnomecanvas2-dev libgnomecanvas2-common libgnomecanvas2-doc Architecture: source Version: 2.30.3-4 Distribution: unstable Urgency: low Maintainer: Adrian Bunk Changed-By: Adrian Bunk Description: libgnomecanvas2-0 - powerful object-oriented display engine - runtime files libgnomecanvas2-common - powerful object-oriented display engine - common files libgnomecanvas2-dev - powerful object-oriented display engine - development files libgnomecanvas2-doc - powerful object-oriented display engine - documentation files Closes: 753621 829811 873351 886063 887868 895247 Changes: libgnomecanvas (2.30.3-4) unstable; urgency=low . * New maintainer. (Closes: #873351, #886063, #895247) * Add fix from Jason Duerstock for FTBFS with gtk-doc-tools 1.27. (Closes: #887868) * Add memory leak fix for gnome-canvas.c:paint(). (Closes: #753621) * Stop using the deprecated GNOME_COMPILE_WARNINGS. (Closes: #829811) * Move all packages to Section: oldlibs. * Update the package descriptions for the deprecated status. Checksums-Sha1: 3e8072ef3fbb63d976ae2e4ff248f827e7e0a06e 2237 libgnomecanvas_2.30.3-4.dsc 98faad5bfbbc41d3c07da8d041f1179446e219d9 7080 libgnomecanvas_2.30.3-4.debian.tar.xz Checksums-Sha256: 987b228da0d71b72463d9f912a6bd1e1cbaba1dda38ab4d89e7fe6b91a756dd1 2237 libgnomecanvas_2.30.3-4.dsc bcc56cc4b6dd601ba27036c537a55eed9d9a5b2b038c898eafea6468522e5250 7080 libgnomecanvas_2.30.3-4.debian.tar.xz Files: 99dd9733c861aadd5e3272605d3c9d30 2237 oldlibs optional libgnomecanvas_2.30.3-4.dsc 8e20972f714746af37e39223ba393e6e 7080 oldlibs optional libgnomecanvas_2.30.3-4.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAluIWikACgkQiNJCh6LY mLFPtRAAgsnbmNCWLQSpDM4A2aXIzSvDFGiWCJBTKPuCBRq2PtbLHJ+UoxzLI/vv mX/ybMn4IDTLZl+wIvt93n74g9sTwMh/hlViU3Kpsrc7k48yP8SRArjLon1FARG/ HPeiQ545p78dUiIaq8D1+Sq7FAMkbO9SYO5yhALe0ZagKmP7DpjnEpKQkNomOUhs 4ezquhvqcqXw1c6m+wH/IaTDddn/+S5vdTfBnuUAxpGlXa/VMstWZSsQfwGVbZsq /Ag2lyV7xN+rU7Vood8Af3eMIyNTqk6zago4zmdiM8y+3owvLcSAVyCvFLD4pq4j pOogIlARhQ2wHf+NtGMW4mJ5TXwCfoydGS+lyCb8MKYeTJ+z0urmgZygp8zdFfeK ofhuq/wPsNEgi6oxqGdILxQO9jkuWvPY4ifl6y3FnDAuntxAVnwJUJBfk1JK7x9U fCm9OkCfaQ4ywWsWVo+xjthBWHh3dHKq4YEuD1ikP8lvbLU5Ghl1zP8P5Uiol3Nl ggpg0XZoIPwHqXDhBGf/GrQuL2Tv2T6KXsbbcsbx4UqZ8/hqM4iCsCEVXjFzo9Pa p8MCCQlz8aJz2T4ONJFq0TemST13FIcMJFYPs9qnXB9Xs9+J7lHHj83ggKXGbZAq YhLmTDUdqLzBON+Y3vFszZF5cEqIx09ROn5y5lh9j4RZOlfqU2c= =jTdl -END PGP SIGNATURE End Message ---
Bug#907662: python-tvrage: useless after TVRage.com shut down?
Package: python-tvrage Version: 0.4.1-1 Severity: grave http://www.tvrage.com/ TVRage.com website has shut down (2005-2015)
Bug#906568: marked as done (samba-dsdb-modules not installable)
Your message dated Fri, 31 Aug 2018 00:11:53 +0300 with message-id <20180830211152.GP3214@localhost> and subject line Fixed in 2:4.8.5+dfsg-1 has caused the Debian Bug report #906562, regarding samba-dsdb-modules not installable to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 906562: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906562 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: samba Version: 2:4.8.4+dfsg-1 Severity: grave Justification: renders package unusable # apt install samba-dsdb-modules Reading package lists... Done Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: samba-dsdb-modules : Depends: libldb1 (< 2:1.3.6~) but 2:1.4.0+really1.3.5-2 is to be installed E: Unable to correct problems, you have held broken packages. -- Package-specific info: * /etc/samba/smb.conf not present * /var/lib/samba/dhcp.conf not present -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.14.60-toy-lxtec-amd64 (SMP w/8 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages samba depends on: ii adduser 3.117 ii dpkg 1.19.0.5+b1 ii libattr1 1:2.4.47-2+b2 ii libbsd0 0.9.1-1 ii libc6 2.27-5 ii libldb1 2:1.4.0+really1.3.5-2 ii libpam-modules1.1.8-3.8 ii libpam-runtime1.1.8-3.8 ii libpopt0 1.16-11 ii libpython2.7 2.7.15-3 ii libtalloc22.1.14-1 ii libtdb1 1.3.15-4 ii libtevent00.9.36-2 ii lsb-base 9.20170808 ii procps2:3.3.15-2 ii python2.7.15-3 ii python-dnspython 1.15.0-1 ii python-samba 2:4.8.4+dfsg-1 ii python2.7 2.7.15-3 ii samba-common 2:4.8.4+dfsg-1 ii samba-common-bin 2:4.8.4+dfsg-1 ii samba-libs2:4.8.4+dfsg-1 ii tdb-tools 1.3.15-4 Versions of packages samba recommends: ii attr1:2.4.47-2+b2 ii logrotate 3.11.0-0.1 pn samba-dsdb-modules ii samba-vfs-modules 2:4.8.4+dfsg-1 Versions of packages samba suggests: ii bind9 1:9.11.4+dfsg-4 ii bind9utils 1:9.11.4+dfsg-4 pn ctdb ii ldb-tools 2:1.4.0+really1.3.5-2 ii ntp1:4.2.8p12+dfsg-1 ii smbldap-tools 0.9.9-1 pn ufw ii winbind2:4.8.4+dfsg-1 -- no debconf information --- End Message --- --- Begin Message --- Version: 2:4.8.5+dfsg-1 samba (2:4.8.5+dfsg-1) unstable; urgency=medium ... - Bump ldb Build-depends to 2:1.4.0+really1.3.6 ... -- Mathieu Parent Thu, 30 Aug 2018 19:32:24 +0200 cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed--- End Message ---
Bug#906562: marked as done (samba-dsdb-modules not installable)
Your message dated Fri, 31 Aug 2018 00:11:53 +0300
with message-id <20180830211152.GP3214@localhost>
and subject line Fixed in 2:4.8.5+dfsg-1
has caused the Debian Bug report #906562,
regarding samba-dsdb-modules not installable
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
906562: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906562
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: samba
Version: 2:4.8.4+dfsg-1
Severity: grave
Justification: renders package unusable
# apt install samba-dsdb-modules
Reading package lists... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
samba-dsdb-modules : Depends: libldb1 (< 2:1.3.6~) but 2:1.4.0+really1.3.5-2 is
to be installed
E: Unable to correct problems, you have held broken packages.
-- Package-specific info:
* /etc/samba/smb.conf present, and attached
* /var/lib/samba/dhcp.conf not present
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (990, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.14.60-toy-lxtec-amd64 (SMP w/8 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8),
LANGUAGE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages samba depends on:
ii adduser 3.117
ii dpkg 1.19.0.5+b1
ii libattr1 1:2.4.47-2+b2
ii libbsd0 0.9.1-1
ii libc6 2.27-5
ii libldb1 2:1.4.0+really1.3.5-2
ii libpam-modules1.1.8-3.8
ii libpam-runtime1.1.8-3.8
ii libpopt0 1.16-11
ii libpython2.7 2.7.15-3
ii libtalloc22.1.14-1
ii libtdb1 1.3.15-4
ii libtevent00.9.36-2
ii lsb-base 9.20170808
ii procps2:3.3.15-2
ii python2.7.15-3
ii python-dnspython 1.15.0-1
ii python-samba 2:4.8.4+dfsg-1
ii python2.7 2.7.15-3
ii samba-common 2:4.8.4+dfsg-1
ii samba-common-bin 2:4.8.4+dfsg-1
ii samba-libs2:4.8.4+dfsg-1
ii tdb-tools 1.3.15-4
Versions of packages samba recommends:
ii attr1:2.4.47-2+b2
ii logrotate 3.11.0-0.1
pn samba-dsdb-modules
ii samba-vfs-modules 2:4.8.4+dfsg-1
Versions of packages samba suggests:
ii bind9 1:9.11.4+dfsg-4
ii bind9utils 1:9.11.4+dfsg-4
pn ctdb
ii ldb-tools 2:1.4.0+really1.3.5-2
ii ntp1:4.2.8p12+dfsg-1
ii smbldap-tools 0.9.9-1
pn ufw
ii winbind2:4.8.4+dfsg-1
-- no debconf information
# Global parameters
[global]
workgroup = LXTEC
realm = HOME.LXTEC.NET
netbios name = TOY
server role = active directory domain controller
#server role = standalone server
server services = s3fs, rpc, nbt, wrepl, ldap, cldap, kdc, drepl,
winbind, ntp_signd, kcc, dnsupdate
#server services = s3fs, rpc, nbt, wrepl, kdc, drepl, winbind,
ntp_signd, kcc, dnsupdate
idmap_ldb:use rfc2307 = yes
interfaces = 192.168.200.1
Debugging/Accounting
# This tells Samba to use a separate log file for each machine
# that connects
log file = /var/log/samba/log.toy
# log level = 3
# Cap the size of the individual log files (in KiB).
max log size = 1000
# If you want Samba to only log through syslog then set the following
# parameter to 'yes'.
# syslog only = no
# We want Samba to log a minimum amount of information to syslog. Everything
# should go to /var/log/samba/log.{smbd,nmbd} instead. If you want to log
# through syslog you should set the following parameter to something higher.
# syslog = 0
# Do something sensible when Samba crashes: mail the admin a backtrace
panic action = /usr/share/samba/panic-action %d
# This parameter determines if nmbd(8) advertises itself as a time server to
Windows clients.
time server = yes
printing = bsd
printcap name = /dev/null
#nsupdate command = nsupdate
[netlogon]
comment = Logon scripts for Users
#path = /var/lib/samba/sysvol/home.lxtec.de/scripts
path = /samba/logon
read only = No
[sysvol]
path = /var/lib/samba/sysvol
read only = No
[home]
comment = Unix Home
path = /home/users
read only = No
Processed: Mark packages that FTBFS as affected
Processing commands for cont...@bugs.debian.org: > affects 907466 src:firefox src:firefox-esr src:ldm src:libisocodes src:gspell Bug #907466 [iso-codes] Package doesn't ship xml files anymore Added indication that 907466 affects src:firefox, src:firefox-esr, src:ldm, src:libisocodes, and src:gspell > block 907612 by 907466 Bug #907612 [src:firefox] firefox: FTBFS with iso-codes 4.0-1: No such file or directory: '/usr/share/xml/iso-codes/iso_639_3.xml' 907612 was not blocked by any bugs. 907612 was not blocking any bugs. Added blocking bug(s) of 907612: 907466 > block 907611 by 907466 Bug #907611 [src:firefox-esr] firefox-esr: FTBFS with iso-codes 4.0-1: No such file or directory: '/usr/share/xml/iso-codes/iso_639_3.xml' 907611 was not blocked by any bugs. 907611 was not blocking any bugs. Added blocking bug(s) of 907611: 907466 > thanks Stopping processing here. Please contact me if you need assistance. -- 907466: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907466 907611: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907611 907612: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907612 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#907466: Package doesn't ship xml files anymore
On 8/30/18 22:35, Dr. Tobias Quathamer wrote: > I would like to go through this list of packages and try to spot the > actual usage of the XML files. If there are only a few packages which > need to be fixed, it might still be doable before the freeze. From a > quick glance, there are a few false positives included. This is very well possible/likely, that this list contains false positives. But I also might have missed affected packages. My attempt to find affected packages was done knowing virtually nothing about the iso-codes package. I guess you have a better idea, how to find affected reverse dependencies. Aside from trying codesearch.debian.net, checking for package (build)-depending on iso-codes might also be an idea. Regards, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#907466: Package doesn't ship xml files anymore
Am 30.08.2018 um 22:43 schrieb Michael Biebl: > Hi Tobias > > On 8/30/18 22:35, Dr. Tobias Quathamer wrote: >> thanks for your investigation. I've deprecated those XML files more than >> two years ago and thought that this time might suffice to switch over to >> the JSON files. > > From past experience, unless you actively file bug reports, don't expect > packages to migrate on their own. Right. :-) >> I would like to go through this list of packages and try to spot the >> actual usage of the XML files. If there are only a few packages which >> need to be fixed, it might still be doable before the freeze. From a >> quick glance, there are a few false positives included. So maybe it's >> not that bad after all. > > Filing bug reports against affected packages and user-tagging them might > be a good idea. This will help with tracking the progress of this > transition. Yes, that was my plan. That will take a few days, however, because I'd like to quickly look into the sources of those packages and try to determine if they actually rely on the XML files. Regards, Tobias signature.asc Description: OpenPGP digital signature
Bug#907466: Package doesn't ship xml files anymore
Hi Tobias On 8/30/18 22:35, Dr. Tobias Quathamer wrote: > thanks for your investigation. I've deprecated those XML files more than > two years ago and thought that this time might suffice to switch over to > the JSON files. From past experience, unless you actively file bug reports, don't expect packages to migrate on their own. > I would like to go through this list of packages and try to spot the > actual usage of the XML files. If there are only a few packages which > need to be fixed, it might still be doable before the freeze. From a > quick glance, there are a few false positives included. So maybe it's > not that bad after all. Filing bug reports against affected packages and user-tagging them might be a good idea. This will help with tracking the progress of this transition. > If however most of the packages in your list have problems now, I'll > re-add the XML files with the next upload of iso-codes. Maybe another > try to remove them after the next Debian release ... I fear unless you actively file bug reports against those packages, the situation will not automatically be better in buster+1. Regards, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#907466: Package doesn't ship xml files anymore
Am 30.08.2018 um 14:47 schrieb Michael Biebl: > On Wed, 29 Aug 2018 15:49:43 +0200 Michael Biebl wrote: > >> Possibly affected: >> https://codesearch.debian.net/search?q=iso-codes.*xml > > The list might be even longer: > https://codesearch.debian.net/search?q=iso_.*%5C.xml [...]> > Given that, what do you think about rolling back the changes in > iso-codes for now e.g. by re-adding the xml files to 4.0 or re-uploading > 3.79? Hi, thanks for your investigation. I've deprecated those XML files more than two years ago and thought that this time might suffice to switch over to the JSON files. Maybe this is not true, after all. :-( I would like to go through this list of packages and try to spot the actual usage of the XML files. If there are only a few packages which need to be fixed, it might still be doable before the freeze. From a quick glance, there are a few false positives included. So maybe it's not that bad after all. If however most of the packages in your list have problems now, I'll re-add the XML files with the next upload of iso-codes. Maybe another try to remove them after the next Debian release ... Regards, Tobias signature.asc Description: OpenPGP digital signature
Bug#906997: marked as done (lua-sec FTBFS with OpenSSL 1.1.1: test failure)
Your message dated Thu, 30 Aug 2018 20:35:24 + with message-id and subject line Bug#906997: fixed in lua-sec 0.6-4.1 has caused the Debian Bug report #906997, regarding lua-sec FTBFS with OpenSSL 1.1.1: test failure 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.) -- 906997: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906997 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: lua-sec Version: 0.6-4 Severity: serious Tags: ftbfs dh_auto_test: Compatibility levels before 9 are deprecated (level 8 in use) make --no-print-directory -f /usr/share/dh-lua/make/dh-lua.Makefile.multiple test Making target test for debian/lua5.1.dh-lua.conf # tests Copying src/https.lua src/ssl.lua src/options.lua in /build/1st/lua-sec-0.6/5.1-sec for test ** lua dynamic (5.1) * Test: cd samples/certs/ && sh rootA.sh && sh clientA.sh && sh serverA.sh && cd ../.. && @@LUA@@ test.lua && rm -f samples/certs/*.pem samples/certs/*.srl Ignoring -days; not generating a certificate Can't load /nonexistent/first-build/.rnd into RNG 140323139330240:error:2406F079:random number generator:RAND_load_file:Cannot open file:../crypto/rand/randfile.c:88:Filename=/nonexistent/first-build/.rnd Generating a 1024 bit RSA private key ...+ .+ writing new private key to 'rootAkey.pem' - Signature ok subject=C = BR, ST = Espirito Santo, L = Santo Antonio do Canaa, O = Santo Tonico Ltda, OU = Department of Computer Science, CN = Root A Getting Private key subject=C = BR, ST = Espirito Santo, L = Santo Antonio do Canaa, O = Santo Tonico Ltda, OU = Department of Computer Science, CN = Root A issuer=C = BR, ST = Espirito Santo, L = Santo Antonio do Canaa, O = Santo Tonico Ltda, OU = Department of Computer Science, CN = Root A Ignoring -days; not generating a certificate Can't load /nonexistent/first-build/.rnd into RNG 140211621429696:error:2406F079:random number generator:RAND_load_file:Cannot open file:../crypto/rand/randfile.c:88:Filename=/nonexistent/first-build/.rnd Generating a 1024 bit RSA private key + + writing new private key to 'clientAkey.pem' - Signature ok subject=C = BR, ST = Espirito Santo, L = Santo Antonio do Canaa, O = Sao Tonico Ltda, OU = Department of Computer Science, CN = Client A Getting CA Private Key subject=C = BR, ST = Espirito Santo, L = Santo Antonio do Canaa, O = Sao Tonico Ltda, OU = Department of Computer Science, CN = Client A issuer=C = BR, ST = Espirito Santo, L = Santo Antonio do Canaa, O = Santo Tonico Ltda, OU = Department of Computer Science, CN = Root A Ignoring -days; not generating a certificate Can't load /nonexistent/first-build/.rnd into RNG 139660593205696:error:2406F079:random number generator:RAND_load_file:Cannot open file:../crypto/rand/randfile.c:88:Filename=/nonexistent/first-build/.rnd Generating a 1024 bit RSA private key ..+ + writing new private key to 'serverAkey.pem' - Signature ok subject=C = BR, ST = Espirito Santo, L = Santo Antonio do Canaa, O = Sao Tonico Ltda, OU = Department of Computer Science, CN = Server A Getting CA Private Key subject=C = BR, ST = Espirito Santo, L = Santo Antonio do Canaa, O = Sao Tonico Ltda, OU = Department of Computer Science, CN = Server A issuer=C = BR, ST = Espirito Santo, L = Santo Antonio do Canaa, O = Santo Tonico Ltda, OU = Department of Computer Science, CN = Root A + cd samples/oneshot/ + sleep 1 + lua server.lua lua: server.lua:19: error loading certificate (ee key too small) stack traceback: [C]: in function 'assert' server.lua:19: in main chunk [C]: ? + ret=0 + lua client.lua lua: client.lua:22: Broken pipe stack traceback: [C]: in function 'assert' client.lua:22: in main chunk [C]: ? + ret=1 + kill -9 %1 test.sh: 12: kill: No such process + true + exit 1 make[2]: *** [/usr/share/dh-lua/make/dh-lua.Makefile.single:307: test-lua-dynamic-real] Error 1 --- End Message --- --- Begin Message --- Source: lua-sec Source-Version: 0.6-4.1 We believe that the bug you reported is fixed in the latest version of lua-sec, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 906...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Daniel Kahn Gillmor (supplier of updated
Bug#903868: marked as done (heat: FTBFS in buster/sid (dh_installman: Cannot find "doc/build/man/heat-api.1"))
Your message dated Thu, 30 Aug 2018 20:34:53 + with message-id and subject line Bug#903868: fixed in heat 1:11.0.0-1 has caused the Debian Bug report #903868, regarding heat: FTBFS in buster/sid (dh_installman: Cannot find "doc/build/man/heat-api.1") to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 903868: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903868 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:heat Version: 1:10.0.0-3 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep pyversions: missing X(S)-Python-Version in control file, fall back to debian/pyversions pyversions: missing debian/pyversions file, fall back to supported versions py3versions: no X-Python3-Version in control file, using supported versions dh build-indep --buildsystem=python_distutils --with python3,sphinxdoc,systemd dh_update_autotools_config -i -O--buildsystem=python_distutils dh_autoreconf -i -O--buildsystem=python_distutils dh_auto_configure -i -O--buildsystem=python_distutils dh_auto_configure: Please use the third-party "pybuild" build system instead of python-distutils dh_auto_configure: This feature will be removed in compat 12. debian/rules override_dh_auto_build make[1]: Entering directory '/<>' pyversions: missing X(S)-Python-Version in control file, fall back to debian/pyversions pyversions: missing debian/pyversions file, fall back to supported versions [... snipped ...] writing output... [ 92%] template_guide/hot_guide writing output... [ 93%] template_guide/hot_spec writing output... [ 94%] template_guide/index writing output... [ 95%] template_guide/openstack writing output... [ 96%] template_guide/software_deployment writing output... [ 97%] template_guide/unsupported writing output... [ 98%] templates/cfn/WordPress_Single_Instance writing output... [ 99%] templates/hot/hello_world writing output... [100%] templates/index /<>/doc/source/admin/auth-model.rst:74: WARNING: unknown document: identity-management WARNING: Cannot get gitsha from git repository. /<>/doc/source/admin/stack-domain-users.rst:120: WARNING: unknown document: identity-management /<>/doc/source/template_guide/environment.rst:55: WARNING: unknown option: -e /<>/doc/source/template_guide/environment.rst:58: WARNING: unknown option: --parameter /<>/doc/source/template_guide/environment.rst:62: WARNING: unknown option: --parameter generating indices... genindex writing additional pages... search copying static files... done copying extra files... done dumping search index in English (code: en) ... done dumping object inventory... done build succeeded, 59 warnings. The HTML pages are in debian/heat-doc/usr/share/doc/heat-doc/html. dh_sphinxdoc dh_sphinxdoc: ignoring unknown JavaScript code: debian/heat-doc/usr/share/doc/heat-doc/html/_static/js/bootstrap.min.js dh_sphinxdoc: ignoring unknown JavaScript code: debian/heat-doc/usr/share/doc/heat-doc/html/_static/js/docs.js dh_sphinxdoc: ignoring unknown JavaScript code: debian/heat-doc/usr/share/doc/heat-doc/html/_static/js/navigation.js dh_sphinxdoc: ignoring unknown JavaScript code: debian/heat-doc/usr/share/doc/heat-doc/html/_static/js/webui-popover.js make[1]: Leaving directory '/<>' debian/rules override_dh_installchangelogs make[1]: Entering directory '/<>' pyversions: missing X(S)-Python-Version in control file, fall back to debian/pyversions pyversions: missing debian/pyversions file, fall back to supported versions py3versions: no X-Python3-Version in control file, using supported versions if [ -e /<>/debian/CHANGELOG ] ; then \ dh_installchangelogs /<>/debian/CHANGELOG ; \ else \ dh_installchangelogs ; \ fi make[1]: Leaving directory '/<>' dh_installman -i -O--buildsystem=python_distutils dh_installman: Cannot find (any matches for) "doc/build/man/heat-api.1" (tried in .) dh_installman: Aborting due to earlier error debian/rules:6: recipe for target 'binary-indep' failed make: *** [binary-indep] Error 25 dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess returned exit status 2 The build was made with "dpkg-buildpackage -A" in my autobuilder. Most probably, it also fails here in reproducible builds: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/heat.html [ Note: There has been a recent change in debhelper
Bug#897214: Fixed in 6.1.7-1
On Mon, Apr 30, 2018 at 02:56:00PM +0200, Christoph Martin wrote: > seafile-6.1.7-1 is still stuck in NEW queue. > > Am 30.04.2018 um 10:24 schrieb Moritz Schlarb: > > Control: fixed -1 seafile-cli/6.1.7-1 > > Control: tags -1 + fixed pending > > > > This will be resolved as soon as src:seafile/6.1.7-1 finally migrates... > > Given 6.1.8-1 is in buster, and there is additionally a bpo9 of this version, I think this bug can be closed, no? Cheers, Nicholas signature.asc Description: PGP signature
Processed: tagging 907655
Processing commands for cont...@bugs.debian.org: > tags 907655 + buster sid Bug #907655 [xserver-xorg-video-mga] xserver-xorg-video-mga: X don't start with the latest package version Added tag(s) buster and sid. > thanks Stopping processing here. Please contact me if you need assistance. -- 907655: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907655 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#905586: lxc: diff for NMU version 1:2.0.9-6.1
Control: tags 905586 + pending
Dear maintainer,
I've prepared an NMU for lxc (versioned as 1:2.0.9-6.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer. Note that the two patches while adressing the
issue, still would allow test for existence of files, but this was
afaics not adressed explicitly.
Regards,
Salvatore
diff -Nru lxc-2.0.9/debian/changelog lxc-2.0.9/debian/changelog
--- lxc-2.0.9/debian/changelog 2018-01-27 15:44:36.0 +0100
+++ lxc-2.0.9/debian/changelog 2018-08-29 15:22:46.0 +0200
@@ -1,3 +1,11 @@
+lxc (1:2.0.9-6.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * utils: add LXC_PROC_PID_FD_LEN
+ * CVE 2018-6556: verify netns fd in lxc-user-nic (Closes: #905586)
+
+ -- Salvatore Bonaccorso Wed, 29 Aug 2018 15:22:46 +0200
+
lxc (1:2.0.9-6) unstable; urgency=medium
* 0004-debian-Use-iproute2-instead-of-iproute.patch: fix creation of
diff -Nru lxc-2.0.9/debian/patches/0005-utils-add-LXC_PROC_PID_FD_LEN_stable-2.0.patch lxc-2.0.9/debian/patches/0005-utils-add-LXC_PROC_PID_FD_LEN_stable-2.0.patch
--- lxc-2.0.9/debian/patches/0005-utils-add-LXC_PROC_PID_FD_LEN_stable-2.0.patch 1970-01-01 01:00:00.0 +0100
+++ lxc-2.0.9/debian/patches/0005-utils-add-LXC_PROC_PID_FD_LEN_stable-2.0.patch 2018-08-29 15:22:46.0 +0200
@@ -0,0 +1,35 @@
+From f96f5f3c1341e73ee51c8b49bef4ba571c562d8c Mon Sep 17 00:00:00 2001
+From: Christian Brauner
+Date: Fri, 4 May 2018 11:59:11 +0200
+Subject: [PATCH] utils: add LXC_PROC_PID_FD_LEN
+
+Signed-off-by: Christian Brauner
+---
+ src/lxc/utils.h | 11 +++
+ 1 file changed, 11 insertions(+)
+
+diff --git a/src/lxc/utils.h b/src/lxc/utils.h
+index a2bad89db..e4d8519db 100644
+--- a/src/lxc/utils.h
b/src/lxc/utils.h
+@@ -99,6 +99,17 @@
+ #define LXC_NUMSTRLEN64 21
+ #define LXC_LINELEN 4096
+ #define LXC_IDMAPLEN 4096
++/* /proc/ =6
++ *+
++ * = LXC_NUMSTRLEN64
++ *+
++ * /fd/ =4
++ *+
++ * = LXC_NUMSTRLEN64
++ *+
++ * \0 =1
++ */
++#define LXC_PROC_PID_FD_LEN (6 + LXC_NUMSTRLEN64 + 4 + LXC_NUMSTRLEN64 + 1)
+
+ /* returns 1 on success, 0 if there were any failures */
+ extern int lxc_rmdir_onedev(char *path, const char *exclude);
+--
+2.17.1
+
diff -Nru lxc-2.0.9/debian/patches/0006-stable-2.0-lxc-user-nic-verify-file-descriptor.patch lxc-2.0.9/debian/patches/0006-stable-2.0-lxc-user-nic-verify-file-descriptor.patch
--- lxc-2.0.9/debian/patches/0006-stable-2.0-lxc-user-nic-verify-file-descriptor.patch 1970-01-01 01:00:00.0 +0100
+++ lxc-2.0.9/debian/patches/0006-stable-2.0-lxc-user-nic-verify-file-descriptor.patch 2018-08-29 15:22:46.0 +0200
@@ -0,0 +1,101 @@
+From d183654ec1a2cd1149bdb92601ccb7246bddb14e Mon Sep 17 00:00:00 2001
+From: Christian Brauner
+Date: Wed, 25 Jul 2018 19:56:54 +0200
+Subject: [PATCH] CVE 2018-6556: verify netns fd in lxc-user-nic
+
+Signed-off-by: Christian Brauner
+---
+ src/lxc/lxc_user_nic.c | 35 ---
+ src/lxc/utils.c| 12
+ src/lxc/utils.h| 5 +
+ 3 files changed, 49 insertions(+), 3 deletions(-)
+
+--- a/src/lxc/lxc_user_nic.c
b/src/lxc/lxc_user_nic.c
+@@ -1124,12 +1124,41 @@ int main(int argc, char *argv[])
+ exit(EXIT_FAILURE);
+ }
+ } else if (request == LXC_USERNIC_DELETE) {
+- netns_fd = open(args.pid, O_RDONLY);
++ char opath[LXC_PROC_PID_FD_LEN];
++
++ /* Open the path with O_PATH which will not trigger an actual
++ * open(). Don't report an errno to the caller to not leak
++ * information whether the path exists or not.
++ * When stracing setuid is stripped so this is not a concern
++ * either.
++ */
++ netns_fd = open(args.pid, O_PATH | O_CLOEXEC);
+ if (netns_fd < 0) {
+- usernic_error("Could not open \"%s\": %s\n", args.pid,
+- strerror(errno));
++ usernic_error("Failed to open \"%s\"\n", args.pid);
++ exit(EXIT_FAILURE);
++ }
++
++ if (!fhas_fs_type(netns_fd, NSFS_MAGIC)) {
++ usernic_error("Path \"%s\" does not refer to a network namespace path\n", args.pid);
++ close(netns_fd);
++ exit(EXIT_FAILURE);
++ }
++
++ ret = snprintf(opath, sizeof(opath), "/proc/self/fd/%d", netns_fd);
++ if (ret < 0 || (size_t)ret >= sizeof(opath)) {
++ close(netns_fd);
++ exit(EXIT_FAILURE);
++ }
++
++ /* Now get an fd that we can use in setns() calls. */
++ ret = open(opath, O_RDONLY | O_CLOEXEC);
++ if (ret < 0) {
++ usernic_error("Failed to open \"%s\": %s\n", args.pid, strerror(errno));
++ close(netns_fd);
+ exit(EXIT_FAILURE);
+ }
++ close(netns_fd);
++ netns_fd = ret;
+ }
+
+ if (!create_db_dir(LXC_USERNIC_DB)) {
+--- a/src/lxc/utils.c
b/src/lxc/utils.c
+@@ -2377,6 +2377,18 @@ bool has_fs_type(const char *path, fs_ty
+ return has_type;
+ }
+
++bool fhas_fs_type(int fd, fs_type_magic magic_val)
++{
++ int ret;
++ struct statfs sb;
++
++ ret = fstatfs(fd, );
++ if (ret < 0)
++
Processed: lxc: diff for NMU version 1:2.0.9-6.1
Processing control commands: > tags 905586 + pending Bug #905586 [src:lxc] lxc: CVE-2018-6556: lxc-user-nic allows unprivileged users to open arbitrary files Added tag(s) pending. -- 905586: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905586 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#906997: lua-sec: FTBFS with OpenSSL 1.1.1: test failure
On Thu 2018-08-30 15:25:49 -0400, Daniel Kahn Gillmor wrote: > the NMU uses the attached patches, which i'll push to salsa as well > shortly. The changes are available on salsa at https://salsa.debian.org/lua-team/lua-sec/merge_requests/1. They also merge in upstream's git history, which should make it easier to cherry-pick from upstream in the future. Enrico, if you'd like, i can also provide patches to do other modernization and minor cleanup of the package, i can convert the git repo to DEP-14, and to potentially to merge upstream version 0.7. let me know if you want that. --dkg signature.asc Description: PGP signature
Bug#906997: lua-sec: FTBFS with OpenSSL 1.1.1: test failure
On Sat 2018-08-25 20:10:36 +0200, Kurt Roeckx wrote: > The problem is: >> Generating a 1024 bit RSA private key > > Which then later results in: >> lua: server.lua:19: error loading certificate (ee key too small) > > We've changed the default in Debian to require 2048 bit keys. thanks for the pointer! I've just uploaded an NMU for this, and i've taken the opportunity to to a bit of simple packaging cleanup to reduce the number of pedantic lintian warnings a bit at least, and to point to the latest upstream repository as well. the NMU uses the attached patches, which i'll push to salsa as well shortly. --dkg From c442b9a28ba78241d4da5f051529e1d87141b00b Mon Sep 17 00:00:00 2001 From: Daniel Kahn Gillmor Date: Thu, 30 Aug 2018 14:46:25 -0400 Subject: [PATCH 1/7] point Vcs-* to salsa --- debian/control | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/debian/control b/debian/control index 4bc9c45..bffd2b1 100644 --- a/debian/control +++ b/debian/control @@ -10,8 +10,8 @@ Build-Depends: debhelper (>= 8.1.3), openssl Standards-Version: 3.9.6 Homepage: https://github.com/brunoos/luasec -Vcs-Git: git://git.debian.org/git/pkg-lua/lua-sec.git -Vcs-Browser: http://git.debian.org/?p=pkg-lua/lua-sec.git +Vcs-Git: https://salsa.debian.org/lua-team/lua-sec.git +Vcs-Browser: https://salsa.debian.org/lua-team/lua-sec Package: lua-sec Architecture: any -- 2.18.0 From 16d8759e90ac04afddd7dd5c7ee86fdb530cf0d1 Mon Sep 17 00:00:00 2001 From: Daniel Kahn Gillmor Date: Thu, 30 Aug 2018 14:54:49 -0400 Subject: [PATCH 2/7] use 2048-bit keys in test suite (Closes: #906997) --- debian/patches/0010-use-2048-bit-keys.patch | 279 debian/patches/series | 1 + 2 files changed, 280 insertions(+) create mode 100644 debian/patches/0010-use-2048-bit-keys.patch diff --git a/debian/patches/0010-use-2048-bit-keys.patch b/debian/patches/0010-use-2048-bit-keys.patch new file mode 100644 index 000..7e99e7c --- /dev/null +++ b/debian/patches/0010-use-2048-bit-keys.patch @@ -0,0 +1,279 @@ +From: Daniel Kahn Gillmor +Date: Thu, 30 Aug 2018 14:53:01 -0400 +Subject: use 2048-bit keys + +According to Kurt Roeckx in https://bugs.debian.org/906997, the test +suite is failing when built against libssl 1.1.1 because we require at +least 2048-bit keys. + +this should address that issue. +--- + samples/certs/clientA.bat | 2 +- + samples/certs/clientA.cnf | 2 +- + samples/certs/clientA.sh | 2 +- + samples/certs/clientB.bat | 2 +- + samples/certs/clientB.cnf | 2 +- + samples/certs/clientB.sh | 2 +- + samples/certs/rootA.bat| 2 +- + samples/certs/rootA.cnf| 2 +- + samples/certs/rootA.sh | 2 +- + samples/certs/rootB.bat| 2 +- + samples/certs/rootB.cnf| 2 +- + samples/certs/rootB.sh | 2 +- + samples/certs/serverA.bat | 2 +- + samples/certs/serverA.cnf | 2 +- + samples/certs/serverA.sh | 2 +- + samples/certs/serverB.bat | 2 +- + samples/certs/serverB.cnf | 2 +- + samples/certs/serverB.sh | 2 +- + samples/dhparam/params.sh | 2 +- + samples/dhparam/server.lua | 4 ++-- + 20 files changed, 21 insertions(+), 21 deletions(-) + +diff --git a/samples/certs/clientA.bat b/samples/certs/clientA.bat +index 112cdef..ddde0e4 100644 +--- a/samples/certs/clientA.bat b/samples/certs/clientA.bat +@@ -1,6 +1,6 @@ + rem #!/bin/sh + +-openssl req -newkey rsa:1024 -sha1 -keyout clientAkey.pem -out clientAreq.pem -nodes -config ./clientA.cnf -days 365 -batch ++openssl req -newkey rsa:2048 -sha1 -keyout clientAkey.pem -out clientAreq.pem -nodes -config ./clientA.cnf -days 365 -batch + + openssl x509 -req -in clientAreq.pem -sha1 -extfile ./clientA.cnf -extensions usr_cert -CA rootA.pem -CAkey rootAkey.pem -CAcreateserial -out clientAcert.pem -days 365 + +diff --git a/samples/certs/clientA.cnf b/samples/certs/clientA.cnf +index f938d90..3c6a6fe 100644 +--- a/samples/certs/clientA.cnf b/samples/certs/clientA.cnf +@@ -98,7 +98,7 @@ emailAddress = optional + + + [ req ] +-default_bits = 1024 ++default_bits = 2048 + default_keyfile = privkey.pem + distinguished_name = req_distinguished_name + attributes = req_attributes +diff --git a/samples/certs/clientA.sh b/samples/certs/clientA.sh +index 0350ede..363230b 100755 +--- a/samples/certs/clientA.sh b/samples/certs/clientA.sh +@@ -1,6 +1,6 @@ + #!/bin/sh + +-openssl req -newkey rsa:1024 -sha1 -keyout clientAkey.pem -out clientAreq.pem \ ++openssl req -newkey rsa:2048 -sha1 -keyout clientAkey.pem -out clientAreq.pem \ + -nodes -config ./clientA.cnf -days 365 -batch + + openssl x509 -req -in clientAreq.pem -sha1 -extfile ./clientA.cnf \ +diff --git a/samples/certs/clientB.bat b/samples/certs/clientB.bat +index 9f341f6..1da9677 100644 +--- a/samples/certs/clientB.bat b/samples/certs/clientB.bat +@@ -1,6 +1,6 @@ + rem #!/bin/sh + +-openssl req -newkey rsa:1024 -sha1 -keyout clientBkey.pem
Bug#907655: xserver-xorg-video-mga: X don't start with the latest package version
Package: xserver-xorg-video-mga Version: 1:1.6.5-1 Severity: grave Justification: renders package unusable Dear Maintainer, upgrading the system to the latest version don't let X to start: screen black with a cursor not blinking at the upper left corner. Ctrl-Alt-Fx don't works. Magic keys work. Restarting the system in recovery mode and accessing as root I was able to install previous version of xserver-xorg-video-mga and server-xorg-core: # dpkg -i xserver-xorg-video-mga_1%3a1.6.5-1_i386.deb xserver-xorg- core_2%3a1.19.6-1_i386.deb this fix the problem. using the command $ grep --binary-files=text wdm /var/log/syslog in a successful start I see the following: Aug 30 20:12:52 debian-eeepc wdm: X.Org X Server 1.19.6 Aug 30 20:12:52 debian-eeepc wdm: Release Date: 2017-12-20 Aug 30 20:12:53 debian-eeepc wdm: X Protocol Version 11, Revision 0 Aug 30 20:12:53 debian-eeepc wdm: Build Operating System: Linux 4.9.0-5-amd64 i686 Debian Aug 30 20:12:53 debian-eeepc wdm: Current Operating System: Linux debian-eeepc 4.17.0-3-686-pae #1 SMP Debian 4.17.17-1 (2018-08-18) i686 Aug 30 20:12:53 debian-eeepc wdm: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.17.0-3-686-pae root=UUID=0a5125b0-7623-41ad-9924-f86564311fe3 ro quiet Aug 30 20:12:53 debian-eeepc wdm: Build Date: 26 January 2018 05:11:03PM Aug 30 20:12:53 debian-eeepc wdm: xorg-server 2:1.19.6-1 (https://www.debian.org/support) Aug 30 20:12:53 debian-eeepc wdm: Current version of pixman: 0.34.0 Aug 30 20:12:53 debian-eeepc wdm: #011Before reporting problems, check http://wiki.x.org Aug 30 20:12:53 debian-eeepc wdm: #011to make sure that you have the latest version. Aug 30 20:12:53 debian-eeepc wdm: Markers: (--) probed, (**) from config file, (==) default setting, Aug 30 20:12:53 debian-eeepc wdm: #011(++) from command line, (!!) notice, (II) informational, Aug 30 20:12:53 debian-eeepc wdm: #011(WW) warning, (EE) error, (NI) not implemented, (??) unknown. Aug 30 20:12:53 debian-eeepc wdm: (==) Log file: "/var/log/Xorg.0.log", Time: Thu Aug 30 20:12:52 2018 Aug 30 20:12:53 debian-eeepc wdm: (==) Using system config directory "/usr/share/X11/xorg.conf.d" Aug 30 20:12:54 debian-eeepc wdm: (EE) fbdev: module ABI major version (24) doesn't match the server's version (23) Aug 30 20:12:54 debian-eeepc wdm: (EE) vesa: module ABI major version (24) doesn't match the server's version (23) Aug 30 20:12:54 debian-eeepc wdm: pci id for fd 14: 8086:8108, driver (null) Aug 30 20:12:58 debian-eeepc wdm: EGL_MESA_drm_image required. Aug 30 20:13:02 debian-eeepc wdm: Cannot open config file. Using builtin defaults Aug 30 20:16:55 debian-eeepc wdm[705]: geometry: 530x240+-2147483648+-2147483648 Note: the EE is because I have installed all 24 except mga and core in an unsuccessful start I see the following: Aug 30 18:41:52 debian-eeepc wdm: X.Org X Server 1.20.1 Aug 30 18:41:52 debian-eeepc wdm: X Protocol Version 11, Revision 0 Aug 30 18:41:52 debian-eeepc wdm: Build Operating System: Linux 4.9.0-7-amd64 i686 Debian Aug 30 18:41:52 debian-eeepc wdm: Current Operating System: Linux debian-eeepc 4.17.0-3-686-pae #1 SMP Debian 4.17.17-1 (2018-08-18) i686 Aug 30 18:41:52 debian-eeepc wdm: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.17.0-3-686-pae root=UUID=0a5125b0-7623-41ad-9924-f86564311fe3 ro quiet Aug 30 18:41:52 debian-eeepc wdm: Build Date: 17 August 2018 08:05:00PM Aug 30 18:41:52 debian-eeepc wdm: xorg-server 2:1.20.1-1 (https://www.debian.org/support) Aug 30 18:41:52 debian-eeepc wdm: Current version of pixman: 0.34.0 Aug 30 18:41:52 debian-eeepc wdm: #011Before reporting problems, check http://wiki.x.org Aug 30 18:41:52 debian-eeepc wdm: #011to make sure that you have the latest version. Aug 30 18:41:52 debian-eeepc wdm: Markers: (--) probed, (**) from config file, (==) default setting, Aug 30 18:41:52 debian-eeepc wdm: #011(++) from command line, (!!) notice, (II) informational, Aug 30 18:41:52 debian-eeepc wdm: #011(WW) warning, (EE) error, (NI) not implemented, (??) unknown. Aug 30 18:41:52 debian-eeepc wdm: (==) Log file: "/var/log/Xorg.0.log", Time: Thu Aug 30 18:41:52 2018 Aug 30 18:41:52 debian-eeepc wdm: (==) Using system config directory "/usr/share/X11/xorg.conf.d" Aug 30 18:41:52 debian-eeepc wdm: pci id for fd 14: 8086:8108, driver (null) Aug 30 18:41:53 debian-eeepc wdm: (EE) Aug 30 18:41:53 debian-eeepc wdm: (EE) Backtrace: Aug 30 18:41:53 debian-eeepc wdm: server unexpectedly died Aug 30 18:42:08 debian-eeepc wdm: Server for display :0 can't be started, session disabled Let me know if you need more info. Ciao Davide -- Package-specific info: X server symlink status: lrwxrwxrwx 1 root root 13 Dec 5 2009 /etc/X11/X -> /usr/bin/Xorg -rwxr-xr-x 1 root root 274 Jan 18 2018 /usr/bin/Xorg VGA-compatible devices on PCI bus: -- 00:02.0 VGA compatible controller [0300]: Intel Corporation System Controller Hub (SCH Poulsbo) Graphics Controller [8086:8108] (rev
Bug#902468: marked as done (golang-github-mwitkow-go-conntrack: FTBFS in buster/sid (failing tests))
Your message dated Thu, 30 Aug 2018 18:03:58 + with message-id and subject line Bug#902468: fixed in golang-github-mwitkow-go-conntrack 0.0~git20161129.cc309e4-3 has caused the Debian Bug report #902468, regarding golang-github-mwitkow-go-conntrack: FTBFS in buster/sid (failing tests) 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.) -- 902468: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902468 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:golang-github-mwitkow-go-conntrack Version: 0.0~git20161129.cc309e4-2 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster with "dpkg-buildpackage -A" but it failed: [...] debian/rules build-indep dh build-indep --buildsystem=golang --with=golang dh_update_autotools_config -i -O--buildsystem=golang dh_autoreconf -i -O--buildsystem=golang dh_auto_configure -i -O--buildsystem=golang dh_auto_configure: "github.com/mwitkow/go-conntrack" is already installed. Please check for circular dependencies. dh_auto_build -i -O--buildsystem=golang cd obj-x86_64-linux-gnu && go install -gcflags=\"-trimpath=/<>/golang-github-mwitkow-go-conntrack-0.0\~git20161129.cc309e4/obj-x86_64-linux-gnu/src\" -asmflags=\"-trimpath=/<>/golang-github-mwitkow-go-conntrack-0.0\~git20161129.cc309e4/obj-x86_64-linux-gnu/src\" -v -p 1 github.com/mwitkow/go-conntrack github.com/mwitkow/go-conntrack/connhelpers github.com/beorn7/perks/quantile github.com/golang/protobuf/proto github.com/prometheus/client_model/go github.com/matttproud/golang_protobuf_extensions/pbutil github.com/prometheus/common/internal/bitbucket.org/ww/goautoneg github.com/prometheus/common/model github.com/prometheus/common/expfmt github.com/prometheus/procfs/internal/util github.com/prometheus/procfs/nfs github.com/prometheus/procfs/xfs github.com/prometheus/procfs github.com/prometheus/client_golang/prometheus golang.org/x/net/internal/timeseries golang.org/x/net/trace github.com/mwitkow/go-conntrack github.com/mwitkow/go-conntrack/connhelpers dh_auto_test -i -O--buildsystem=golang cd obj-x86_64-linux-gnu && go test -vet=off -v -p 1 github.com/mwitkow/go-conntrack github.com/mwitkow/go-conntrack/connhelpers === RUN TestDialerWrapper === RUN TestDialerWrapper/TestDialerMetricsAreNotPreregisteredWithMonitoringOff === RUN TestDialerWrapper/TestDialerMetricsArePreregistered === RUN TestDialerWrapper/TestDialerRefusedFailure === RUN TestDialerWrapper/TestDialerResolutionFailure === RUN TestDialerWrapper/TestDialerUnderNormalConnection === RUN TestDialerWrapper/TestDialerWithContextName --- PASS: TestDialerWrapper (0.12s) --- PASS: TestDialerWrapper/TestDialerMetricsAreNotPreregisteredWithMonitoringOff (0.01s) --- PASS: TestDialerWrapper/TestDialerMetricsArePreregistered (0.02s) --- PASS: TestDialerWrapper/TestDialerRefusedFailure (0.01s) --- PASS: TestDialerWrapper/TestDialerResolutionFailure (0.04s) --- PASS: TestDialerWrapper/TestDialerUnderNormalConnection (0.02s) --- PASS: TestDialerWrapper/TestDialerWithContextName (0.01s) dialer_test.go:186: stopped http.Server at: 127.0.0.1:46241 === RUN TestListenerTestSuite === RUN TestListenerTestSuite/TestDialerTracingCapturedInPage === RUN TestListenerTestSuite/TestMonitoringNormalConns === RUN TestListenerTestSuite/TestTracingNormalComms === RUN TestListenerTestSuite/TestTrackingMetricsPreregistered --- FAIL: TestListenerTestSuite (0.05s) --- PASS: TestListenerTestSuite/TestDialerTracingCapturedInPage (0.01s) --- FAIL: TestListenerTestSuite/TestMonitoringNormalConns (0.01s) listener_test.go:81: Error Trace:listener_test.go:81 Error: Not equal: expected: 2 actual : 1 Test: TestListenerTestSuite/TestMonitoringNormalConns Messages: the closed conn counter must be incremented after connection was closed --- PASS: TestListenerTestSuite/TestTracingNormalComms (0.01s) --- PASS: TestListenerTestSuite/TestTrackingMetricsPreregistered (0.01s) listener_test.go:97: stopped http.Server at: 127.0.0.1:41893 FAIL FAILgithub.com/mwitkow/go-conntrack 0.180s ? github.com/mwitkow/go-conntrack/connhelpers [no test files] dh_auto_test: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 1
Bug#907267: openmpi: liggghts build on i386 times out
Latest build of liggghts on i386 against openmpi 3.1.2-1 timed out. https://buildd.debian.org/status/fetch.php?pkg=liggghts=i386=3.7.0%2Brepack1-1.1=1535641058=0
Processed: Bug #902468 in golang-github-mwitkow-go-conntrack marked as pending
Processing control commands: > tag -1 pending Bug #902468 [src:golang-github-mwitkow-go-conntrack] golang-github-mwitkow-go-conntrack: FTBFS in buster/sid (failing tests) Added tag(s) pending. -- 902468: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902468 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#902468: Bug #902468 in golang-github-mwitkow-go-conntrack marked as pending
Control: tag -1 pending Hello, Bug #902468 in golang-github-mwitkow-go-conntrack 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/go-team/packages/golang-github-mwitkow-go-conntrack/commit/518a0fe897096e24e63989c84d3571d9cc68885f Fix flaky test. Closes: #902468 (this message was generated automatically) -- Greetings https://bugs.debian.org/902468
Processed: notfound 905913 in 1.0.25-4.1
Processing commands for cont...@bugs.debian.org: > notfound 905913 1.0.25-4.1 Bug #905913 [src:sane-backends] sane-backends: Don't install into testing No longer marked as found in versions sane-backends/1.0.25-4.1. > thanks Stopping processing here. Please contact me if you need assistance. -- 905913: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905913 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: [bts-link] source package tweepy
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package tweepy > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #904648 (http://bugs.debian.org/904648) > # Bug title: python3-tweepy: fails to install with Python 3.7 > # * https://github.com/tweepy/tweepy/issues/1017 > # * remote status changed: (?) -> closed > # * closed upstream > tags 904648 + fixed-upstream Bug #904648 [python3-tweepy] python3-tweepy: fails to install with Python 3.7 Added tag(s) fixed-upstream. > usertags 904648 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 904648: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904648 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#902468: Info
It took me a while to reproduce, as it seems to only happen with high CPU contention. I will see if I can fix the bug, or disable it otherwise. -- Martín Ferrari (Tincho)
Bug#907553: marked as done (libminc: wrong cmake installation path)
Your message dated Thu, 30 Aug 2018 17:21:28 + with message-id and subject line Bug#907553: fixed in libminc 2.4.03-2 has caused the Debian Bug report #907553, regarding libminc: wrong cmake installation path to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 907553: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907553 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libminc Version: 2.4.03-1 Affects -1 src:minc-tools Severity: serious as said here: https://salsa.debian.org/med-team/libminc/commit/96b470374ae407cd2886dcea79a5543be9e44876 minc-tools now FTBFS this commit seems to have regressed libminc installation, from /usr/lib//cmake/LIBMINC/ to /usr/lib//cmake/ and now minc-tools is failing to find the cmake file, and FTBFS https://buildd.debian.org/status/fetch.php?pkg=minc-tools=amd64=2.3.00%2Bdfsg-2%2Bb1=1535535100=0 doing a mv /usr/lib//cmake/*.cmake /usr/lib//cmake/LIBMINC/ "fixes" the build G. --- End Message --- --- Begin Message --- Source: libminc Source-Version: 2.4.03-2 We believe that the bug you reported is fixed in the latest version of libminc, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 907...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gert Wollny (supplier of updated libminc 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: Thu, 30 Aug 2018 18:44:55 +0200 Source: libminc Binary: libminc2-5.2.0 libminc-dev Architecture: source Version: 2.4.03-2 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Gert Wollny Description: libminc-dev - MNI medical image format development environment libminc2-5.2.0 - MNI medical image format library Closes: 907553 Changes: libminc (2.4.03-2) unstable; urgency=medium . * Team upload * d/: Install cmake file in the correct location Closes: #907553 (locutusofborg) Checksums-Sha1: e4e5616ff860b9b34698560071be60cad99df459 2083 libminc_2.4.03-2.dsc fc7313935bef8e5c81449b43aadbb1e51841ea90 8804 libminc_2.4.03-2.debian.tar.xz ad88375b76577ef113f22f5fc10544b3ddd12a8e 7842 libminc_2.4.03-2_source.buildinfo Checksums-Sha256: 202a8e1f56210c1e4090731fb5db57e472398a82dc756dce8c0464921d630ed9 2083 libminc_2.4.03-2.dsc 102723640c5941f91d29eeb0e083ae228a3d8439c9343cd0d5b3acd0d139c7b1 8804 libminc_2.4.03-2.debian.tar.xz 2379cc41ae9b82aa6403f27e882f4035a825e9190103a7d1b736644a4484ed07 7842 libminc_2.4.03-2_source.buildinfo Files: 44bf9278b53e72dbcd0c977d6894e44a 2083 science optional libminc_2.4.03-2.dsc 179c9a6143d7939555de3379b50e3d3f 8804 science optional libminc_2.4.03-2.debian.tar.xz 7278390d1b9ca4050c904472615576e8 7842 science optional libminc_2.4.03-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEELtRZww6NuKjZPKd6l/LU/KCfME4FAluIIVgACgkQl/LU/KCf ME54RBAAhU4JpGYXk8URaB4eaPfmbhQv9Z+847+DUBc2/g4XmMMMOHRILUHooFJC lPcogx7fll/In0udKqAI6jnhN9XC2HSVDYOu347YrmTuGneiWg/eISO+OYm84RU2 4CNWpTE+gTlebGIvehpJpEvxUkzkp2ee2QCeO8C2IKzxlovjgHzx7wyIbNBlu/If fLKecUc2kcjLXtqIGkmwNzjC/uv4qcljvcwxUPltMWYElsbsq5qM8+I3HF+XVZQx VhlotD2ORRgzY/VRhn8WJcslIemrNkLIpbI972tfqaLmExhgWHEbIjbcnPM8SNTH Oc31SZMgCG5kI8D+bGAHWqYwpJc41feUpD2qgZa1vpE9ojX8J1RhcaCNbVHnOUT8 XrSi65CTqn6wd0CKo/d906Cjm66tSRR/ugILiXgsDZCGcORo3Csea521B+/Qn4G4 S6YCe3XWo3EE7q9pj9gNM0Fw9Yg7iHxR7Q5CBzKZBZjS+QXD/GpOux0niOj9nIrc iUtO2VqRJaC/Fy2AS/FHsSueFIcPf08HheaXE5jEKPUuoOkgthPgxqgRBXmNZzpU p7wVZpRX87tekpSuf9rZCJUZTUxkaYzLkX+OyawQN8fR5e8UiZPxPoUDpnspRLhR 09cMIzj1YVyPCtYQhh/CLeb/bnTPVCyhZ3aXNDrBxFB5w7zT4N4= =mDNY -END PGP SIGNATURE End Message ---
Bug#885751: teg: Port to GooCanvas / GTK+ 3 / GSettings
Am 30.08.2018 um 01:53 schrieb Yavor Doganov: > tags 885751 + patch > thanks > > Attached are patches that should fix this bug completely (removing all > dependencies on old libraries that are scheduled for removal), plus > the following issues of non-RC severity: [...] Yavor, thank you very much again for your work on porting games to newer libraries. I will take a look at the patch tomorrow and if I don't find anything serious, I'm going to upload it. Regards, Markus signature.asc Description: OpenPGP digital signature
Bug#906976: marked as done (FTBFS in buster)
Your message dated Thu, 30 Aug 2018 16:34:52 +
with message-id
and subject line Bug#906976: fixed in mitmproxy 4.0.4-4
has caused the Debian Bug report #906976,
regarding FTBFS in buster
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.)
--
906976: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906976
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:mitmproxy
Version: 4.0.4-3
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-indep
cat: debian/mitmproxy.manpages: No such file or directory
dh build-indep --with python3 --buildsystem=pybuild
dh_update_autotools_config -i -O--buildsystem=pybuild
dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:217: python3.6 setup.py config
running config
dh_auto_build -i -O--buildsystem=pybuild
I: pybuild base:217: /usr/bin/python3 setup.py build
running build
running build_py
creating /<>/.pybuild/cpython3_3.6_mitmproxy/build/mitmproxy
copying mitmproxy/connections.py ->
/<>/.pybuild/cpython3_3.6_mitmproxy/build/mitmproxy
copying mitmproxy/websocket.py ->
/<>/.pybuild/cpython3_3.6_mitmproxy/build/mitmproxy
[... snipped ...]
[1mdef test_verification_w_confdir(self, tdata):[0m
[1mself.options.update([0m
[1mssl_insecure=False,[0m
[1mssl_verify_upstream_trusted_confdir=tdata.path([0m
[1m"mitmproxy/data/servercert/"[0m
[1m),[0m
[1mssl_verify_upstream_trusted_ca=None,[0m
[1m)[0m
[1m> assert self._request().status_code == 242[0m
[1m[31mE assert 502 == 242[0m
[1m[31mE+ where 502 = Response(502 Bad Gateway, text/html,
307b).status_code[0m
[1m[31mE+where Response(502 Bad Gateway, text/html, 307b) =
>()[0m
[1m[31mE+ where > =
._request[0m
[1m[31mtest/mitmproxy/proxy/test_server.py[0m:320: AssertionError
[31m[1m_
TestHTTPSUpstreamServerVerificationWTrustedCert.test_verification_w_pemfile
__[0m
self =
tdata =
[1mdef test_verification_w_pemfile(self, tdata):[0m
[1mself.options.update([0m
[1mssl_insecure=False,[0m
[1mssl_verify_upstream_trusted_confdir=None,[0m
[1mssl_verify_upstream_trusted_ca=tdata.path([0m
[1m"mitmproxy/data/servercert/trusted-root.pem"[0m
[1m),[0m
[1m)[0m
[1m> assert self._request().status_code == 242[0m
[1m[31mE assert 502 == 242[0m
[1m[31mE+ where 502 = Response(502 Bad Gateway, text/html,
307b).status_code[0m
[1m[31mE+where Response(502 Bad Gateway, text/html, 307b) =
>()[0m
[1m[31mE+ where > =
._request[0m
[1m[31mtest/mitmproxy/proxy/test_server.py[0m:330: AssertionError
[33m=== warnings summary
===[0m
.pybuild/cpython3_3.6_mitmproxy/build/test/mitmproxy/tools/console/test_master.py::TestMaster::()::test_basic
/usr/lib/python3/dist-packages/_pytest/python.py:195: RuntimeWarning:
coroutine 'TestMaster.test_basic' was never awaited
testfunction(**testargs)
-- Docs: http://doc.pytest.org/en/latest/warnings.html
[31m[1m== 5 failed, 805 passed, 545 deselected, 1 warnings in 43.08
seconds ===[0m
E: pybuild pybuild:338: test: plugin distutils failed with: exit code=1: cd
/<>/.pybuild/cpython3_3.6_mitmproxy/build; python3.6 -m pytest
"-k-TestHARDump -k-TestScripts -k-test_mitmweb -k-test_mitmdump"
dh_auto_test: pybuild --test --test-pytest -i python{version} -p 3.6 returned
exit code 13
make: *** [debian/rules:11: build-indep] Error 25
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit
status 2
The build was made with "dpkg-buildpackage -A" in my autobuilder.
Most probably, it also fails here in reproducible builds:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/mitmproxy.html
where you can get a full build log if you need it.
If this is really a bug in one of the build-depends, please use reassign and
affects,
so that this is still visible in the BTS web page for this package.
Thanks.
--- End Message ---
--- Begin Message ---
Source: mitmproxy
Source-Version: 4.0.4-4
We believe that the bug you reported is fixed in the latest version of
mitmproxy, which is due to be installed in the Debian FTP
Processed: closing 865633
Processing commands for cont...@bugs.debian.org: > close 865633 Bug #865633 [src:spice-gtk] can't drag windows or click "Activities" in GNOME 3 guest Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 865633: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865633 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#906348: marked as done (django-prometheus: FTBFS in buster/sid (failing tests))
Your message dated Thu, 30 Aug 2018 16:03:59 +
with message-id
and subject line Bug#906348: fixed in django-prometheus 1.0.15-2
has caused the Debian Bug report #906348,
regarding django-prometheus: FTBFS in buster/sid (failing tests)
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.)
--
906348: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906348
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:django-prometheus
Version: 1.0.15-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 python2,python3 --buildsystem=pybuild
dh_update_autotools_config -i -O--buildsystem=pybuild
dh_autoreconf -i -O--buildsystem=pybuild
dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:217: python2.7 setup.py config
running config
I: pybuild base:217: python3.6 setup.py config
running config
dh_auto_build -i -O--buildsystem=pybuild
I: pybuild base:217: /usr/bin/python setup.py build
running build
running build_py
creating
/<>/.pybuild/cpython2_2.7_django-prometheus/build/django_prometheus
[... snipped ...]
dh_auto_test -i -O--buildsystem=pybuild
I: pybuild base:217: python2.7 setup.py test
running test
running egg_info
creating django_prometheus.egg-info
writing requirements to django_prometheus.egg-info/requires.txt
writing django_prometheus.egg-info/PKG-INFO
writing top-level names to django_prometheus.egg-info/top_level.txt
writing dependency_links to django_prometheus.egg-info/dependency_links.txt
writing manifest file 'django_prometheus.egg-info/SOURCES.txt'
reading manifest file 'django_prometheus.egg-info/SOURCES.txt'
writing manifest file 'django_prometheus.egg-info/SOURCES.txt'
running build_ext
Traceback (most recent call last):
File "setup.py", line 42, in
"License :: OSI Approved :: Apache Software License",
File "/usr/lib/python2.7/dist-packages/setuptools/__init__.py", line 129, in
setup
return distutils.core.setup(**attrs)
File "/usr/lib/python2.7/distutils/core.py", line 151, in setup
dist.run_commands()
File "/usr/lib/python2.7/distutils/dist.py", line 953, in run_commands
self.run_command(cmd)
File "/usr/lib/python2.7/distutils/dist.py", line 972, in run_command
cmd_obj.run()
File "/usr/lib/python2.7/dist-packages/setuptools/command/test.py", line 226,
in run
self.run_tests()
File "/usr/lib/python2.7/dist-packages/setuptools/command/test.py", line 248,
in run_tests
exit=False,
File "/usr/lib/python2.7/unittest/main.py", line 94, in __init__
self.parseArgs(argv)
File "/usr/lib/python2.7/unittest/main.py", line 149, in parseArgs
self.createTests()
File "/usr/lib/python2.7/unittest/main.py", line 158, in createTests
self.module)
File "/usr/lib/python2.7/unittest/loader.py", line 130, in loadTestsFromNames
suites = [self.loadTestsFromName(name, module) for name in names]
File "/usr/lib/python2.7/unittest/loader.py", line 103, in loadTestsFromName
return self.loadTestsFromModule(obj)
File "/usr/lib/python2.7/dist-packages/setuptools/command/test.py", line 52,
in loadTestsFromModule
tests.append(self.loadTestsFromName(submodule))
File "/usr/lib/python2.7/unittest/loader.py", line 100, in loadTestsFromName
parent, obj = obj, getattr(obj, part)
AttributeError: 'module' object has no attribute 'test_exports'
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-indep] Error 25
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit
status 2
The build was made with "dpkg-buildpackage -A" in my autobuilder.
Most probably, it also fails here in reproducible builds:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/django-prometheus.html
where you can get a full build log if you need it.
If this is really a bug in one of the build-depends, please use reassign and
affects,
so that this is still visible in the BTS web page for this package.
Thanks.
--- End Message ---
--- Begin Message ---
Source: django-prometheus
Source-Version: 1.0.15-2
We believe that the bug you reported is fixed in the latest version of
django-prometheus, which is due to be installed in the Debian FTP archive.
A summary of the changes
Processed: Bug #906348 in django-prometheus marked as pending
Processing control commands: > tag -1 pending Bug #906348 [src:django-prometheus] django-prometheus: FTBFS in buster/sid (failing tests) Added tag(s) pending. -- 906348: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906348 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#906348: Bug #906348 in django-prometheus marked as pending
Control: tag -1 pending Hello, Bug #906348 in django-prometheus 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/python-team/modules/django-prometheus/commit/af549eab8af36a0b07ab9555c61e9d99a89bae32 Add missing build-deps. Closes: #906348 (this message was generated automatically) -- Greetings https://bugs.debian.org/906348
Bug#905913: sane-backends: Don't install into testing
Package: libsane Version: 1.0.25-4.1 Followup-For: Bug #905913 The upload of 1.0.27-1~experimental6 makes libsane currently uninstallable on sid. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (900, 'unstable'), (800, 'experimental'), (500, 'unstable-debug') Architecture: amd64 (x86_64) Kernel: Linux 4.17.0-3-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libsane depends on: ii acl2.2.52-3+b1 ii adduser3.117 ii libavahi-client3 0.7-4 ii libavahi-common3 0.7-4 ii libc6 2.27-5 ii libgphoto2-6 2.5.19-1 ii libgphoto2-port12 2.5.19-1 ii libieee1284-3 0.2.11-13 ii libjpeg62-turbo1:1.5.2-2+b1 ii libsane-common 1.0.25-4.1 ii libtiff5 4.0.9-6 ii libusb-1.0-0 2:1.0.22-2 ii udev 239-7 Versions of packages libsane recommends: pn libsane-extras pn sane-utils Versions of packages libsane suggests: pn avahi-daemon pn hplip
Bug#906380: libtool: FTBFS in buster/sid
at bottom :-
On 30/08/2018, Juhani Numminen wrote:
> Control: tags -1 patch
>
> shirish शिरीष kirjoitti 30.08.2018 klo 07:51:> I, and I guess others would
> welcome a test build if it helps to see
>> if the issue is resolved. See how to apply patch [1] and see if you
>> can do the same thing -
>>
>> 1.
>> https://unix.stackexchange.com/questions/324680/how-to-apply-a-patch-in-a-debian-package
>>
>> Look forward to seeing a new deb package and trying it out to see if
>> it fixes the issue. Can't compile any packages due to the libtool
>> issues :(
>
> I applied the patch and the build is successful. The tests pass. You can
> find the commands I used in the end of this message.
>
> While I can already apply a patch in a Debian package, I appreciate you
> sharing the instructions :)
>
> Regards,
> Juhani
>
> --
> dget -x
> http://deb.debian.org/debian/pool/main/libt/libtool/libtool_2.4.6-2.1.dsc
> wget
> https://src.fedoraproject.org/rpms/libtool/raw/master/f/libtool-2.4.6-am-1.16-test.patch
> cd libtool-2.4.6
> quilt import ../libtool-2.4.6-am-1.16-test.patch
> dch
> dpkg-buildpackage -S -d -us -uc
> sudo cowbuilder --build ../libtool_2.4.6-2.1+local1.dsc
>
Wish I could help but cannot even install dget i.e. devscripts due to
the libtool and other bugs :(
$ sudo aptitude install devscripts -y
The following NEW packages will be installed:
debhelper{a} devscripts dh-autoreconf{a} dh-strip-nondeterminism{a}
equivs{a} libltdl-dev{a} libtool{a}
libyaml-libyaml-perl{a} lintian{a}
0 packages upgraded, 9 newly installed, 0 to remove and 0 not upgraded.
Need to get 2,115 kB/3,887 kB of archives. After unpacking 10.5 MB will be used.
Get: 1 http://cdn-fastly.deb.debian.org/debian buster/main amd64
devscripts amd64 2.18.3 [984 kB]
Get: 2 http://cdn-fastly.deb.debian.org/debian buster/main amd64
lintian all 2.5.98 [1,131 kB]
Fetched 2,115 kB in 24s (89.5 kB/s)
Retrieving bug reports... Done
Parsing Found/Fixed information... Done
grave bugs of libltdl-dev (→ 2.4.6-2.1)
b1 - #905841 - libltdl-dev: dependency on specific automake version
Merged with: 906394 906395 906423 906501 906507
grave bugs of libyaml-libyaml-perl (→ 0.72+repack-1)
b2 - #862373 - libyaml-libyaml-perl: Unconditionally instantiates
objects from yaml data
grave bugs of devscripts (→ 2.18.3)
b3 - #902409 - devscripts: CVE-2018-13043 - grep-excuses uses
YAML::Syck in a unsafe way
Summary:
devscripts(1 bug), libltdl-dev(1 bug), libyaml-libyaml-perl(1 bug)
Are you sure you want to install/upgrade the above packages? [Y/n/?/...] n
**
** Exiting with an error in order to stop the installation. **
**
E: Sub-process /usr/sbin/apt-listbugs apt returned an error code (10)
E: Failure running script /usr/sbin/apt-listbugs apt
$ apt-file list devscripts | grep dget
devscripts: /usr/bin/dget
devscripts: /usr/share/bash-completion/completions/dget
devscripts: /usr/share/man/de/man1/dget.1.gz
devscripts: /usr/share/man/fr/man1/dget.1.gz
devscripts: /usr/share/man/man1/dget.1.gz
Btw, thank you for sharing the updated instructions, have bookmarked it :)
--
Regards,
Shirish Agarwal शिरीष अग्रवाल
My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A 2C2F 9F3D C7A4 E1C4 D2D8
Bug#906361: marked as done (golang-github-smira-go-ftp-protocol: FTBFS in buster/sid (failing tests))
Your message dated Thu, 30 Aug 2018 14:34:31 + with message-id and subject line Bug#906361: fixed in golang-github-smira-go-ftp-protocol 0.0~git20140829.066b75c-2 has caused the Debian Bug report #906361, regarding golang-github-smira-go-ftp-protocol: FTBFS in buster/sid (failing tests) 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.) -- 906361: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906361 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:golang-github-smira-go-ftp-protocol Version: 0.0~git20140829.066b75c-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=golang --with=golang dh_update_autotools_config -i -O--buildsystem=golang dh_autoreconf -i -O--buildsystem=golang dh_auto_configure -i -O--buildsystem=golang dh_auto_build -i -O--buildsystem=golang cd obj-x86_64-linux-gnu && go install -gcflags=\"-trimpath=/<>/golang-github-smira-go-ftp-protocol-0.0\~git20140829.066b75c/obj-x86_64-linux-gnu/src\" -asmflags=\"-trimpath=/<>/golang-github-smira-go-ftp-protocol-0.0\~git20140829.066b75c/obj-x86_64-linux-gnu/src\" -v -p 1 github.com/smira/go-ftp-protocol/protocol github.com/jlaffaye/ftp github.com/smira/go-ftp-protocol/protocol dh_auto_test -i -O--buildsystem=golang cd obj-x86_64-linux-gnu && go test -vet=off -v -p 1 github.com/smira/go-ftp-protocol/protocol === RUN TestProtocol --- PASS: TestProtocol (2.51s) === RUN TestConcurrent --- FAIL: TestConcurrent (8.72s) protocol_test.go:67: Get ftp://ftp.ru.debian.org/debian/README: EOF FAIL FAILgithub.com/smira/go-ftp-protocol/protocol 11.231s dh_auto_test: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 1 github.com/smira/go-ftp-protocol/protocol returned exit code 1 make: *** [debian/rules:4: build-indep] Error 1 dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit status 2 The build was made with "dpkg-buildpackage -A" in my autobuilder. Most probably, it also fails here in reproducible builds: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-github-smira-go-ftp-protocol.html where you can get a full build log if you need it. If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks. --- End Message --- --- Begin Message --- Source: golang-github-smira-go-ftp-protocol Source-Version: 0.0~git20140829.066b75c-2 We believe that the bug you reported is fixed in the latest version of golang-github-smira-go-ftp-protocol, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 906...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alexandre Viau (supplier of updated golang-github-smira-go-ftp-protocol 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: Thu, 30 Aug 2018 09:58:24 -0400 Source: golang-github-smira-go-ftp-protocol Binary: golang-github-smira-go-ftp-protocol-dev Architecture: source Version: 0.0~git20140829.066b75c-2 Distribution: unstable Urgency: medium Maintainer: Debian Go Packaging Team Changed-By: Alexandre Viau Description: golang-github-smira-go-ftp-protocol-dev - plugin for http.Transport with support for ftp:// protocol Closes: 906361 Changes: golang-github-smira-go-ftp-protocol (0.0~git20140829.066b75c-2) unstable; urgency=medium . * Skip tests as they require an internet connection. (Closes: #906361) Checksums-Sha1: 9fc537fcacfaf2ff049a7a1c8929c6abdb73f489 2482 golang-github-smira-go-ftp-protocol_0.0~git20140829.066b75c-2.dsc f2b59bc369072522dc3a8a1c8fc7a364b97f901e 2608 golang-github-smira-go-ftp-protocol_0.0~git20140829.066b75c-2.debian.tar.xz c257c3b2d1315701aa9795ce4dae58ed31edf1d4 6163 golang-github-smira-go-ftp-protocol_0.0~git20140829.066b75c-2_source.buildinfo Checksums-Sha256:
Bug#907496: libcurlpp0: Always fails with "No URL set!"
Hi, I'd like to report that I'm not seeing this error. When I compile and run the program from Ted's mail, I just get some HTML from example.org in stdout as expected. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.17.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE=fi_FI.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libcurlpp0 depends on: ii libc6 2.27-5 ii libcurl47.61.0-1 ii libgcc1 1:8.2.0-4 ii libstdc++6 8.2.0-4 libcurlpp0 recommends no packages. libcurlpp0 suggests no packages. -- no debconf information
Bug#906380: libtool: FTBFS in buster/sid
Control: tags -1 patch shirish शिरीष kirjoitti 30.08.2018 klo 07:51:> I, and I guess others would welcome a test build if it helps to see > if the issue is resolved. See how to apply patch [1] and see if you > can do the same thing - > > 1. > https://unix.stackexchange.com/questions/324680/how-to-apply-a-patch-in-a-debian-package > > Look forward to seeing a new deb package and trying it out to see if > it fixes the issue. Can't compile any packages due to the libtool > issues :( I applied the patch and the build is successful. The tests pass. You can find the commands I used in the end of this message. While I can already apply a patch in a Debian package, I appreciate you sharing the instructions :) Regards, Juhani -- dget -x http://deb.debian.org/debian/pool/main/libt/libtool/libtool_2.4.6-2.1.dsc wget https://src.fedoraproject.org/rpms/libtool/raw/master/f/libtool-2.4.6-am-1.16-test.patch cd libtool-2.4.6 quilt import ../libtool-2.4.6-am-1.16-test.patch dch dpkg-buildpackage -S -d -us -uc sudo cowbuilder --build ../libtool_2.4.6-2.1+local1.dsc
Processed: Re: Bug#906380: libtool: FTBFS in buster/sid
Processing control commands: > tags -1 patch Bug #906380 [src:libtool] libtool: FTBFS in buster/sid Added tag(s) patch. -- 906380: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906380 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#907637: bonding with virtio NICs does not work any more
Package: src:linux Version: 4.9.110-3+deb9u4 Severity: critical Hi, For network testing reasons I run several KVM VMs with up to now four virtio NICs, where only one NIC is connected and the others are marked as "link_down" in the KVM configuration. In the guest the NICs are configured as bonding device with lacp. Up to linux-image-4.9.0-6-amd64 this worked without issues. Starting with linux-image-4.9.0-7-amd64 the kernel now reports after booting: Aug 27 12:01:39 test-gate-1 kernel: [ 22.881163] bond0: link status up for interface ens18, enabling it in 0 ms Aug 27 12:01:39 test-gate-1 kernel: [ 22.882881] bond0: failed to get link speed/duplex for ens18 Aug 27 12:01:39 test-gate-1 kernel: [ 22.985209] bond0: link status up for interface ens18, enabling it in 0 ms Aug 27 12:01:39 test-gate-1 kernel: [ 22.986998] bond0: failed to get link speed/duplex for ens18 Aug 27 12:01:39 test-gate-1 kernel: [ 23.089250] bond0: link status up for interface ens18, enabling it in 0 ms Aug 27 12:01:39 test-gate-1 kernel: [ 23.091765] bond0: failed to get link speed/duplex for ens18 Aug 27 12:01:40 test-gate-1 kernel: [ 23.193170] bond0: link status up for interface ens18, enabling it in 0 ms Aug 27 12:01:40 test-gate-1 kernel: [ 23.195772] bond0: failed to get link speed/duplex for ens18 ethtool also shows unknown speed and duplex for the virtio interfaces. This seems to not have been an issue before linux-4.9.0-7. Switching the virtual NICs from virtio to vmxnet3 solves the issue, ethtool also reports speed and duplex mode. I do not know if this is a KVM issue or a kernel issue, but as the older kernel image works it looks more like a kernel issue to me. -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: QEMU product_name: Standard PC (i440FX + PIIX, 1996) product_version: pc-i440fx-2.11 chassis_vendor: QEMU chassis_version: pc-i440fx-2.11 bios_vendor: SeaBIOS bios_version: rel-1.11.0-0-g63451fca13-prebuilt.qemu-project.org ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC [Natoma] [8086:1237] (rev 02) Subsystem: Red Hat, Inc Qemu virtual machine [1af4:1100] Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- BAR=0 offset= size= Capabilities: [70] Vendor Specific Information: VirtIO: Notify BAR=4 offset=3000 size=1000 multiplier=0004 Capabilities: [60] Vendor Specific Information: VirtIO: DeviceCfg BAR=4 offset=2000 size=1000 Capabilities: [50] Vendor Specific Information: VirtIO: ISR BAR=4 offset=1000 size=1000 Capabilities: [40] Vendor Specific Information: VirtIO: CommonCfg BAR=4 offset= size=1000 Kernel driver in use: virtio-pci Kernel modules: virtio_pci 00:05.0 SCSI storage controller [0100]: Red Hat, Inc Virtio SCSI [1af4:1004] Subsystem: Red Hat, Inc Virtio SCSI [1af4:0008] Physical Slot: 5 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- BAR=0 offset= size= Capabilities: [70] Vendor Specific Information: VirtIO: Notify BAR=4 offset=3000 size=1000 multiplier=0004 Capabilities: [60] Vendor Specific Information: VirtIO: DeviceCfg BAR=4 offset=2000 size=1000 Capabilities: [50] Vendor Specific Information: VirtIO: ISR BAR=4 offset=1000 size=1000 Capabilities: [40] Vendor Specific Information: VirtIO: CommonCfg BAR=4 offset= size=1000 Kernel driver in use: virtio-pci Kernel modules: virtio_pci 00:08.0 Communication controller [0780]: Red Hat, Inc Virtio console [1af4:1003] Subsystem: Red Hat, Inc Virtio console [1af4:0003] Physical Slot: 8 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- BAR=0 offset= size= Capabilities: [70] Vendor Specific Information: VirtIO: Notify BAR=4 offset=3000 size=1000 multiplier=0004 Capabilities: [60] Vendor Specific Information: VirtIO: DeviceCfg BAR=4 offset=2000 size=1000 Capabilities: [50] Vendor Specific Information: VirtIO: ISR BAR=4 offset=1000 size=1000 Capabilities: [40] Vendor Specific Information: VirtIO: CommonCfg
Processed: tagging 905109, tagging 899525, tagging 907316, tagging 906117, found 906714 in 5.4.1+dfsg4-3
Processing commands for cont...@bugs.debian.org:
> tags 905109 + sid buster
Bug #905109 {Done: Jonathan Carter }
[gnome-shell-extension-pixelsaver] gnome-shell-extension-pixelsaver:
global.screen is not available in GNOME Shell 3.29
Ignoring request to alter tags of bug #905109 to the same tags previously set
> tags 899525 + sid buster
Bug #899525 [src:gigolo] gigolo: Invalid maintainer address
pkg-xfce-de...@lists.alioth.debian.org
Added tag(s) sid and buster.
> tags 907316 + sid buster
Bug #907316 [src:tomboy] tomboy: Is tomboy still being maintained?
Added tag(s) sid and buster.
> tags 906117 + experimental
Bug #906117 [openjdk-7-jre-headless] openjdk-7-jre-headless: FTBFS in Debian
Experimental
Added tag(s) experimental.
> found 906714 5.4.1+dfsg4-3
Bug #906714 [paraview] paraview: FTBFS in Sid
Marked as found in versions paraview/5.4.1+dfsg4-3.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
899525: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899525
905109: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905109
906117: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906117
906714: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906714
907316: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907316
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#907466: Package doesn't ship xml files anymore
On Wed, 29 Aug 2018 15:49:43 +0200 Michael Biebl wrote: > Possibly affected: > https://codesearch.debian.net/search?q=iso-codes.*xml The list might be even longer: https://codesearch.debian.net/search?q=iso_.*%5C.xml apper calibre choose-mirror cinnamon-control-center django-countries empathy epiphany-browser evolution fcitx fcitx-configtool firefox firefox-esr gaupol geary gimagereader gimp gnome-desktop3 gnome-software gnuradio gspell gst-plugins-base1.0 gtkpod gtkspell3 gtranslator hexchat ibus iso-codes java-gnome kaffeine ldm libgda5 libgweather libisocodes liblingua-translit-perl lintian localechooser lxdm mkvtoolnix mozjs24 mozjs52 network-manager-applet ocrfeeder onboard openjfx oz performous plasma-desktop pluma python-apt qtdeclarative-opensource-src qtspell quodlibet ros-catkin ruby-libxml software-properties sound-juicer subtitleeditor thunderbird trilinos workrave Given that, what do you think about rolling back the changes in iso-codes for now e.g. by re-adding the xml files to 4.0 or re-uploading 3.79? -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#897764: marked as done (guymager: ftbfs with GCC-8)
Your message dated Thu, 30 Aug 2018 12:34:16 + with message-id and subject line Bug#897764: fixed in guymager 0.8.8-2 has caused the Debian Bug report #897764, regarding guymager: ftbfs with GCC-8 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.) -- 897764: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897764 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:guymager Version: 0.8.7-1 Severity: normal Tags: sid buster User: debian-...@lists.debian.org Usertags: ftbfs-gcc-8 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-8/g++-8, but succeeds to build with gcc-7/g++-7. The severity of this report will be raised before the buster release. The full build log can be found at: http://aws-logs.debian.net/2018/05/01/gcc8/guymager_0.8.7-1_unstable_gcc8.log.gz The last lines of the build log are at the end of this report. To build with GCC 8, either set CC=gcc-8 CXX=g++-8 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-8/porting_to.html [...] Now at patch desktop_integration dh_testdir qmake -qt5 DEFINES+="SPLASH_DIR=\'\\\"/usr/share/guymager\\\"\' LANGUAGE_DIR=\'\\\"/usr/share/guymager\\\"\' LANGUAGE_DIR_QT=\'\\\"/usr/share/qt5/translations\\\"\'" Info: creating stash file /<>/.qmake.stash touch configure-stamp make[1]: Leaving directory '/<>' debian/rules override_dh_auto_build make[1]: Entering directory '/<>' dh_testdir /usr/bin/make make[2]: Entering directory '/<>' g++ -c -pipe -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -ggdb -O3 -Wall -W -fmessage-length=0 -fno-strict-aliasing -D_REENTRANT -fPIC -DSPLASH_DIR='"/usr/share/guymager"' -DLANGUAGE_DIR='"/usr/share/guymager"' -DLANGUAGE_DIR_QT='"/usr/share/qt5/translations"' -DQT_NO_DEBUG -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_DBUS_LIB -DQT_CORE_LIB -I. -isystem /usr/include/libguytools2 -isystem /usr/include/x86_64-linux-gnu/qt5 -isystem /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem /usr/include/x86_64-linux-gnu/qt5/QtDBus -isystem /usr/include/x86_64-linux-gnu/qt5/QtCore -Imoc -isystem /usr/include/libdrm -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o aaff.o aaff.cpp g++ -c -pipe -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -ggdb -O3 -Wall -W -fmessage-length=0 -fno-strict-aliasing -D_REENTRANT -fPIC -DSPLASH_DIR='"/usr/share/guymager"' -DLANGUAGE_DIR='"/usr/share/guymager"' -DLANGUAGE_DIR_QT='"/usr/share/qt5/translations"' -DQT_NO_DEBUG -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_DBUS_LIB -DQT_CORE_LIB -I. -isystem /usr/include/libguytools2 -isystem /usr/include/x86_64-linux-gnu/qt5 -isystem /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem /usr/include/x86_64-linux-gnu/qt5/QtDBus -isystem /usr/include/x86_64-linux-gnu/qt5/QtCore -Imoc -isystem /usr/include/libdrm -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o aewf.o aewf.cpp g++ -c -pipe -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -ggdb -O3 -Wall -W -fmessage-length=0 -fno-strict-aliasing -D_REENTRANT -fPIC -DSPLASH_DIR='"/usr/share/guymager"' -DLANGUAGE_DIR='"/usr/share/guymager"' -DLANGUAGE_DIR_QT='"/usr/share/qt5/translations"' -DQT_NO_DEBUG -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_DBUS_LIB -DQT_CORE_LIB -I. -isystem /usr/include/libguytools2 -isystem /usr/include/x86_64-linux-gnu/qt5 -isystem /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem /usr/include/x86_64-linux-gnu/qt5/QtDBus -isystem /usr/include/x86_64-linux-gnu/qt5/QtCore -Imoc -isystem /usr/include/libdrm -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o config.o config.cpp g++ -c -pipe -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -ggdb -O3 -Wall -W -fmessage-length=0 -fno-strict-aliasing -D_REENTRANT -fPIC
Bug#907171: prometheus FTBFS:
On Thu, 2018-08-30 at 13:23 +0100, Martín Ferrari wrote: > > Unless the tests are run in their own network namespace (which provides > > some guarantees over what else might be bound to a port, I can't seem > > to find logs which would confirm or deny if a netns was in use here > > though) probably the test needs to use a random port or otherwise be > > tollerant of 9090 not being available. > Right, but this can't be done without root, and buildds do not give root. I don't think that applies to the "needs to use a random port or otherwise be tollerant of 9090 not being available" which was the main thrust of my comment. > > Maybe there is (or should be) an autopkgtest flag to request a clean > > netns be used? > > This discussion is about a FTBFS bug, not about the CI system. ALso, > that would not solve the issue, as it is autopkgtest installing (and > therefore starting) prometheus. So the issue is a parallel (but unrelated) autopkgtest run on the same host interfering with builds which are happening at the same time? (I had thought the autopkgtest was part of the build hence → FTBFS, seems I was misunderstanding then, sorry for the noise on that front) Ian.
Bug#903121: (no subject)
I did not encounter this bug or any other related problem on my system. System type: Desktop PC Gfx: Nvidia GTX 10170 CPU: AMD Ryzen 2700 Kernel: 4.17.0-3-amd64 #1 SMP Debian 4.17.17-1 (2018-08-18) x86_64 GNU/Linux Nvidia Driver: nvidia-graphics-drivers 390.77-1 Even the problem described in https://lists.debian.org/debian-user/2018/07/msg00059.html is solved. Maybe its only Laptop related. The bug reporter should give an update if the issue still exists.
Processed: Re: Bug#891087: beautifulsoup has been replaced by bs4
Processing control commands: > severity -1 serious Bug #891087 [src:beautifulsoup] beautifulsoup has been replaced by bs4 Severity set to 'serious' from 'important' -- 891087: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891087 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#907171: prometheus FTBFS:
Ian, On 30/08/18 09:51, Ian Campbell wrote: > Does `nc -l -p 9090` repro the test failure perhaps? yes, of course. > Unless the tests are run in their own network namespace (which provides > some guarantees over what else might be bound to a port, I can't seem > to find logs which would confirm or deny if a netns was in use here > though) probably the test needs to use a random port or otherwise be > tollerant of 9090 not being available. Right, but this can't be done without root, and buildds do not give root. > Maybe there is (or should be) an autopkgtest flag to request a clean > netns be used? This discussion is about a FTBFS bug, not about the CI system. ALso, that would not solve the issue, as it is autopkgtest installing (and therefore starting) prometheus. -- Martín Ferrari (Tincho)
Bug#907559: marked as done (cgview: Does not start)
Your message dated Thu, 30 Aug 2018 12:18:56 + with message-id and subject line Bug#907559: fixed in cgview 0.0.20100111-4 has caused the Debian Bug report #907559, regarding cgview: Does not start 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.) -- 907559: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907559 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: cgview Severity: grave Justification: renders package unusable Hi, cgview in sid/testing does not start while the same code base in stable works perfectly. It just dies with: $ cgview Error: Unable to initialize main class ca.ualberta.stothard.cgview.CgviewIO Caused by: java.lang.NoClassDefFoundError: org/apache/batik/util/XMLConstants Olivier Sallou suspected that the issue could be caused by the version of Batik which is 1.8 in stable and 1.10 in testing/sid. I've checked both source code and JARs for instance like $ grep -wl XMLConstants /usr/share/java/batik* /usr/share/java/batik-all-1.10.jar /usr/share/java/batik-all.jar /usr/share/java/batik-constants-1.10.jar /usr/share/java/batik-constants.jar /usr/share/java/batik.jar /usr/share/java/batik-libs.jar on a machine (testing) where it fails and where cgview works (stable): $ $ grep -wl XMLConstants /usr/share/java/batik* /usr/share/java/batik-1.8.jar /usr/share/java/batik-all-1.8.jar /usr/share/java/batik-all.jar /usr/share/java/batik.jar /usr/share/java/batik-libs-1.8.jar /usr/share/java/batik-libs.jar /usr/share/java/batik-util-1.8.jar /usr/share/java/batik-util.jar The only interesting difference is that on stable (batik-1.8) the symbol is inside /usr/share/java/batik-util.jar while it is not any more in batik 1.10. The tricky thing is that the string XMLConstants itself is not part of the cgview source code so simply changing util in something else that can be found is not possible and may be the bug is simply in one of the dependencies and not in cgview itself. That's why I take the freedom to add Debian Java list in CC of this bug report. Kind regards Andreas. -- System Information: Debian Release: 9.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-6-amd64 (SMP w/1 CPU core) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages cgview depends on: pn default-jre | java8-runtime pn jarwrapper pn libbatik-java pn libcommons-lang-java pn libjargs-java pn libxerces2-java cgview recommends no packages. cgview suggests no packages. --- End Message --- --- Begin Message --- Source: cgview Source-Version: 0.0.20100111-4 We believe that the bug you reported is fixed in the latest version of cgview, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 907...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated cgview 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: Thu, 30 Aug 2018 13:57:12 +0200 Source: cgview Binary: cgview Architecture: source Version: 0.0.20100111-4 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Description: cgview - Circular Genome Viewer Closes: 907559 Changes: cgview (0.0.20100111-4) unstable; urgency=medium . * Add batik-constants.jar to CLASSPATH (Thanks for the hint to Emmanuel Bourg) Closes: #907559 * debhelper 11 * Point Vcs fields to salsa.debian.org * Standards-Version: 4.2.1 Checksums-Sha1: 0d50c9a9b9c4adfcc7cdb2c6b62c1c2238cc48c6 2063 cgview_0.0.20100111-4.dsc 57eb7881e7d4320e8cf372f2162aacf9636c24af 7816 cgview_0.0.20100111-4.debian.tar.xz Checksums-Sha256: 5c6a64522b6984bee1d648e143d4be8debfd929de3ba7f6c88c01c2ea71b5fd7 2063 cgview_0.0.20100111-4.dsc efa75aca02ea2e99256157fc40158e522cecf2bbfe4fc015005a4a1fc8b69821 7816 cgview_0.0.20100111-4.debian.tar.xz Files:
Bug#890024: npapi-vlc: upcoming Firefox ESR dropping support for NPAPI
I agree that it's time to have the package npapi-vlc removed from unstable. Let's proceed with the RM bug.
Bug#894618: marked as done (diaspora-installer: Don't depend on old openssl)
Your message dated Thu, 30 Aug 2018 12:03:55 + with message-id and subject line Bug#894618: fixed in diaspora-installer 0.7.4.0+nmu1 has caused the Debian Bug report #894618, regarding diaspora-installer: Don't depend on old openssl 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.) -- 894618: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894618 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: diaspora-installer Version: 0.7.4.0 Severity: serious Please depend on libssl-dev instead of libssl1.0-dev for the openssl transition. Thanks, Jeremy Bicha --- End Message --- --- Begin Message --- Source: diaspora-installer Source-Version: 0.7.4.0+nmu1 We believe that the bug you reported is fixed in the latest version of diaspora-installer, 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 894...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gianfranco Costamagna (supplier of updated diaspora-installer 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: Thu, 30 Aug 2018 10:59:22 +0200 Source: diaspora-installer Binary: diaspora-installer diaspora-installer-mysql diaspora-common Architecture: source Version: 0.7.4.0+nmu1 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers Changed-By: Gianfranco Costamagna Description: diaspora-common - distributed social networking service - common files diaspora-installer - distributed social networking service - installer diaspora-installer-mysql - distributed social networking service - installer (with MySQL) Closes: 894618 Changes: diaspora-installer (0.7.4.0+nmu1) unstable; urgency=medium . * Non-maintainer upload. * Switch to libssl 1.1 (Closes: #894618) Checksums-Sha1: 945c43171cc4adeb7f537481230049f751ecafcc 2014 diaspora-installer_0.7.4.0+nmu1.dsc d34d6d1695034e0f171820a72e073c1420f3748e 39528 diaspora-installer_0.7.4.0+nmu1.tar.xz d1f85514159d6c1f19c33064f5582887fc2dc1af 7280 diaspora-installer_0.7.4.0+nmu1_source.buildinfo Checksums-Sha256: bbaf6aed9c127917dd32381ddc93f82ff1ab77db2e5ea7f4dbeda609a54072ed 2014 diaspora-installer_0.7.4.0+nmu1.dsc 5420c47eaec91f0047eb94d84f95d6608b8e8c5655318a7c50b458af390e7ce9 39528 diaspora-installer_0.7.4.0+nmu1.tar.xz c211bda1d12f2406d76f14baecf78f68dbca2a51d16c5dd13725f0ab90abb119 7280 diaspora-installer_0.7.4.0+nmu1_source.buildinfo Files: 2617bf2e18b2ab8875a117dc90cae48f 2014 net optional diaspora-installer_0.7.4.0+nmu1.dsc fba305e97e43651fa0acdb808f44eca9 39528 net optional diaspora-installer_0.7.4.0+nmu1.tar.xz bb38eaa4bc2908eaf724b883e4421388 7280 net optional diaspora-installer_0.7.4.0+nmu1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEkpeKbhleSSGCX3/w808JdE6fXdkFAluH3IQACgkQ808JdE6f Xdki5w//T22cwGVRK2OUB8tnYRT3kFcK/qMPUj/f+hC7BfYG5+KEnllqyGDUVRds 2kCSCxs3+pg/Ql4lnfJ/MTPQyRjpCj3qwRs6H37T4MbMSL2SBTtVha5uXt+GL9RA Pq1NfA3oFRNuMrACF3h6u6AlsYOjrLF1euN/dnFqUtZiqfh3q+Tay4NPxLUeM15o Kw7+f+y2HpAM9C4GCrKC+QvDJOLzyWwp/Mzl6qcg9/saUqWvT2HZ9ttwNCIxjO8Z 4crgz5RUEMsUk8QHPJYg63FamJm/dcFjU5knkb5z2xU3a18/82Cw1C4DI1sJlmlg 5J2wATXCXXHgK7/an5Pyv5t9wB8RlGM6A1udPhIoHYxReLxrSxOkvvecISiiwmCN 1GlYMaLIUQ6C+dLLzGW30Tl4I7dK/efLEmOmyiWM99WqLscOXgMsDsJdjO5/uJoj XVDZuqyz71j66JEU7C4m2zcgQZkkL++puLCR6NHUzfVDOayEV+Il0jZV/zzEhjAP nKzUbIqi0d6OAATYWrpekkxeXoURJqgZtvMmjgarGOwk5HhKO3YJMeUsEbOQAymt eeLWY3q9JWVJrPTiTW7Z8+twq/z8pDnknODJMbVNrnwtMkXhvPUjYUTSRbBJrsdY hh0BUMNvD266rctoyzs5jPZLU5H/g5e0paGJQ4k2cPuiJtvbagU= =Eicy -END PGP SIGNATURE End Message ---
Bug#907559: Do you have any clue? [andr...@an3as.eu: cgview.jar does not find class from batik-util]
On Thu, Aug 30, 2018 at 10:00:52AM +0200, Emmanuel Bourg wrote: > On 29/08/2018 17:16, Markus Koschany wrote: > > https://mvnrepository.com/artifact/org.apache.xmlgraphics/batik-constants > > Technically batik-constants is not a new project but a new Maven module > of the batik project. It seems we already build it [1]. Maybe it's just > a matter of updating the classpath in the manifests? Thanks a lot - that's it. Kind regards Andreas. -- http://fam-tille.de
Bug#905112: marked as done (gnome-shell-extension-workspaces-to-dock: global.screen is not available in GNOME Shell 3.29)
Your message dated Thu, 30 Aug 2018 11:49:12 + with message-id and subject line Bug#905112: fixed in gnome-shell-extension-workspaces-to-dock 47-1 has caused the Debian Bug report #905112, regarding gnome-shell-extension-workspaces-to-dock: global.screen is not available in GNOME Shell 3.29 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.) -- 905112: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905112 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gnome-shell-extension-workspaces-to-dock Version: 45-1 Severity: important Tags: upstream experimental User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: shell-3.30 According to codesearch.debian.net, this extension uses the MetaScreen via global.screen. MetaScreen no longer exists in GNOME 3.29, which is starting to become available in experimental. This extension will need code changes to use the MetaDisplay (global.display), MetaWorkspaceManager (global.workspace_manager), MetaMonitorManager (Meta.MonitorManager.get()) or MetaX11Display (global.display.get_x11_display()). Because GNOME 3.29/3.30 is not a stable release yet and is not in Debian unstable yet, you'll probably need to condition on the GNOME Shell version. smcv --- End Message --- --- Begin Message --- Source: gnome-shell-extension-workspaces-to-dock Source-Version: 47-1 We believe that the bug you reported is fixed in the latest version of gnome-shell-extension-workspaces-to-dock, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 905...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonathan Carter (supplier of updated gnome-shell-extension-workspaces-to-dock 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: Thu, 30 Aug 2018 13:08:05 +0200 Source: gnome-shell-extension-workspaces-to-dock Binary: gnome-shell-extension-workspaces-to-dock Architecture: source all Version: 47-1 Distribution: unstable Urgency: medium Maintainer: Debian GNOME Maintainers Changed-By: Jonathan Carter Description: gnome-shell-extension-workspaces-to-dock - additional options for GNOME workspace switcher Closes: 905112 Changes: gnome-shell-extension-workspaces-to-dock (47-1) unstable; urgency=medium . * New upstream release (Closes: #905112) * Update standards version to 4.2.1 * Set Debian GNOME Maintainers as maintainer * Set self as uploader * Move project to salsa.debian.net service Checksums-Sha1: 3d3db173b01101574252061f5347c54fb1eb295b 2329 gnome-shell-extension-workspaces-to-dock_47-1.dsc c80fbecfaa6e4aa88cbf236589c1d5eb21969e16 5293202 gnome-shell-extension-workspaces-to-dock_47.orig.tar.gz 214937ca32b7eb9c959a3e1d332b1cb684c4e281 2004 gnome-shell-extension-workspaces-to-dock_47-1.debian.tar.xz 86927955473fbefc56669b962c93b3b7a7e4a3ac 93576 gnome-shell-extension-workspaces-to-dock_47-1_all.deb 541b659e1098dd55a4f8bbdfa36add644fad729b 5857 gnome-shell-extension-workspaces-to-dock_47-1_amd64.buildinfo Checksums-Sha256: 9661f3c9905e7d73d25b87fe680c904b2cff134133bb629992e524762c0bfd6d 2329 gnome-shell-extension-workspaces-to-dock_47-1.dsc c882648c2aca87f940cf24f561b13b9b31524ee6cb00e367287fff5ce42bf2e9 5293202 gnome-shell-extension-workspaces-to-dock_47.orig.tar.gz 97d17b217058412bd4dba23efcf28fbc4b8bfb8ae6e88d0e702c2c18358ea489 2004 gnome-shell-extension-workspaces-to-dock_47-1.debian.tar.xz 5bd62df4a0fee5e7a35add8a379cc6648805a93de66af493153dc76c978d1cb7 93576 gnome-shell-extension-workspaces-to-dock_47-1_all.deb 224a635a877e8a95b7a65aad56b209832a01daf229efffe6c9168a73031de6a4 5857 gnome-shell-extension-workspaces-to-dock_47-1_amd64.buildinfo Files: ca334298c843a1b58dbe95f23dff2fb8 2329 gnome optional gnome-shell-extension-workspaces-to-dock_47-1.dsc a54e2f06e88719d082a91f63ad03b43c 5293202 gnome optional gnome-shell-extension-workspaces-to-dock_47.orig.tar.gz c8d6b078fe040bd99f907b1fde60695f 2004 gnome optional gnome-shell-extension-workspaces-to-dock_47-1.debian.tar.xz becb1f6a3889502a555d75cdec97fb60 93576 gnome optional gnome-shell-extension-workspaces-to-dock_47-1_all.deb d180dafa523466d825479291993af366 5857
Processed: Bug #897764 in guymager marked as pending
Processing control commands: > tag -1 pending Bug #897764 [src:guymager] guymager: ftbfs with GCC-8 Added tag(s) pending. -- 897764: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897764 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#897764: Bug #897764 in guymager marked as pending
Control: tag -1 pending Hello, Bug #897764 in guymager 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/pkg-security-team/guymager/commit/7ffc3b5c291b26bc50b573a3aac69788616b2853 Include patch to fix ftbfs with GCC-8 Closes: #897764 Thanks: Hilko Bengen for a preliminary patch + Guy for the changes that should be part of the upcoming 0.8.9 guymager version (this message was generated automatically) -- Greetings https://bugs.debian.org/897764
Bug#905418: openmpi: elpa builds hang on multiple architectures
Hi Alastair On 30/08/2018 13:07, Alastair McKinstry wrote: Can you redo tests with openmpi 3.1.2 ? Thanks for the new upload. I'm redoing the tests on elpa, ligghts and arpack. I'll update the bugs in due course. I think this new release fixes the hang issues, i've done some tests on armhf that went ok Here's hoping! Regards Graham
Bug#905418: openmpi: elpa builds hang on multiple architectures
Hi Graham Can you redo tests with openmpi 3.1.2 ? I think this new release fixes the hang issues, i've done some tests on armhf that went ok regards Alastair On 27/08/2018 20:48, Graham Inggs wrote: Hi Alastair Elpa seems to be another package with builds timing out. Confirmed on reproducible builders for i386 [1] and armhf [2]. Regards Graham [1] https://tests.reproducible-builds.org/debian/history/i386/elpa.html [2] https://tests.reproducible-builds.org/debian/history/armhf/elpa.html -- Alastair McKinstry, , , https://diaspora.sceal.ie/u/amckinstry Commander Vimes didn’t like the phrase “The innocent have nothing to fear,” believing the innocent had everything to fear, mostly from the guilty but in the longer term even more from those who say things like “The innocent have nothing to fear.” - T. Pratchett, Snuff
Bug#905109: marked as done (gnome-shell-extension-pixelsaver: global.screen is not available in GNOME Shell 3.29)
Your message dated Thu, 30 Aug 2018 11:04:16 + with message-id and subject line Bug#905109: fixed in gnome-shell-extension-pixelsaver 1.10+git20180804-d97c6e4-1 has caused the Debian Bug report #905109, regarding gnome-shell-extension-pixelsaver: global.screen is not available in GNOME Shell 3.29 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.) -- 905109: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905109 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gnome-shell-extension-pixelsaver Version: 1.10+git20161217-49f47bf-1 Severity: important Tags: upstream experimental User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: shell-3.30 According to codesearch.debian.net, this extension uses the MetaScreen via global.screen. MetaScreen no longer exists in GNOME 3.29, which is starting to become available in experimental. This extension will need code changes to use the MetaDisplay (global.display), MetaWorkspaceManager (global.workspace_manager), MetaMonitorManager (Meta.MonitorManager.get()) or MetaX11Display (global.display.get_x11_display()). Because GNOME 3.29/3.30 is not a stable release yet and is not in Debian unstable yet, you'll probably need to condition on the GNOME Shell version. smcv --- End Message --- --- Begin Message --- Source: gnome-shell-extension-pixelsaver Source-Version: 1.10+git20180804-d97c6e4-1 We believe that the bug you reported is fixed in the latest version of gnome-shell-extension-pixelsaver, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 905...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonathan Carter (supplier of updated gnome-shell-extension-pixelsaver 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: Thu, 30 Aug 2018 12:13:43 +0200 Source: gnome-shell-extension-pixelsaver Binary: gnome-shell-extension-pixelsaver Architecture: source all Version: 1.10+git20180804-d97c6e4-1 Distribution: unstable Urgency: medium Maintainer: Debian GNOME Maintainers Changed-By: Jonathan Carter Description: gnome-shell-extension-pixelsaver - pixel saver extension for GNOME shell Closes: 905109 Changes: gnome-shell-extension-pixelsaver (1.10+git20180804-d97c6e4-1) unstable; urgency=medium . * New upstream snapshot (Closes: #905109) * Update standards version to 4.1.2 * Update compat to level 11 * Drop versioned depend on gnome-shell * Move git repository to salsa.debian.net service * Set maintainer to Debian GNOME Maintainers * Set myself as uploader and update e-mail address Checksums-Sha1: dd10fe3967658f91e254413cca65ef4373d7a984 2365 gnome-shell-extension-pixelsaver_1.10+git20180804-d97c6e4-1.dsc 4599fbb724732380458e23ae1cf57a4d16619d3e 170033 gnome-shell-extension-pixelsaver_1.10+git20180804-d97c6e4.orig.tar.gz d8093b3335372a1d39e45e3ab7f1333be8c18066 9364 gnome-shell-extension-pixelsaver_1.10+git20180804-d97c6e4-1.debian.tar.xz d646a1b4a29e390c2b39fb00ab42328d150dcd4d 111876 gnome-shell-extension-pixelsaver_1.10+git20180804-d97c6e4-1_all.deb fa9532227830a25ef694c9a242f03d8c3ac3abd1 5903 gnome-shell-extension-pixelsaver_1.10+git20180804-d97c6e4-1_amd64.buildinfo Checksums-Sha256: 1e2c54f81665a87889180973c6786bcf87f19893a465a08f45d84567d704118c 2365 gnome-shell-extension-pixelsaver_1.10+git20180804-d97c6e4-1.dsc 83f3bc16ce2bb40d4f6a6cd16da20f1f16e9eea5838d50d78951b4e8fda35310 170033 gnome-shell-extension-pixelsaver_1.10+git20180804-d97c6e4.orig.tar.gz aa7f5156016b91481506c108816f10c455cf4db4b774186911ddef054b3841d3 9364 gnome-shell-extension-pixelsaver_1.10+git20180804-d97c6e4-1.debian.tar.xz 6448ab863636c79a4873018fa69530232d250c06b45a15d630def0558d1356d2 111876 gnome-shell-extension-pixelsaver_1.10+git20180804-d97c6e4-1_all.deb f074bd2ce187298a9aca299d6ed4d83e24b8b8c7613218ea96bf9815a107bbb6 5903 gnome-shell-extension-pixelsaver_1.10+git20180804-d97c6e4-1_amd64.buildinfo Files: 3583d5c7cee2a448fbe0930403d3200a 2365 gnome optional gnome-shell-extension-pixelsaver_1.10+git20180804-d97c6e4-1.dsc a3ac65625ab20fe023c9c7e15f923ea6 170033 gnome optional
Bug#907616: budgie-desktop: needs modification for Mutter 3.30
On Thu, 30 Aug 2018 at 09:34:09 +0100, David Mohammed wrote: > Not clear here. Should I submit an upload to experimental? Yes please. smcv
Processed: diaspora-installer: diff for NMU version 0.7.4.0+nmu1
Processing control commands: > tags 894618 + patch Bug #894618 [src:diaspora-installer] diaspora-installer: Don't depend on old openssl Added tag(s) patch. > tags 894618 + pending Bug #894618 [src:diaspora-installer] diaspora-installer: Don't depend on old openssl Added tag(s) pending. -- 894618: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894618 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#894618: diaspora-installer: diff for NMU version 0.7.4.0+nmu1
Control: tags 894618 + patch Control: tags 894618 + pending Dear maintainer, I've prepared an NMU for diaspora-installer (versioned as 0.7.4.0+nmu1) and uploaded it to unstable. Regards. diff -Nru diaspora-installer-0.7.4.0/debian/changelog diaspora-installer-0.7.4.0+nmu1/debian/changelog --- diaspora-installer-0.7.4.0/debian/changelog 2018-03-27 08:41:03.0 +0200 +++ diaspora-installer-0.7.4.0+nmu1/debian/changelog 2018-08-30 10:59:22.0 +0200 @@ -1,3 +1,10 @@ +diaspora-installer (0.7.4.0+nmu1) unstable; urgency=medium + + * Non-maintainer upload. + * Switch to libssl 1.1 (Closes: #894618) + + -- Gianfranco Costamagna Thu, 30 Aug 2018 10:59:22 +0200 + diaspora-installer (0.7.4.0) unstable; urgency=medium [ Joseph Nuthalapati ] diff -Nru diaspora-installer-0.7.4.0/debian/control diaspora-installer-0.7.4.0+nmu1/debian/control --- diaspora-installer-0.7.4.0/debian/control 2018-03-27 08:41:03.0 +0200 +++ diaspora-installer-0.7.4.0+nmu1/debian/control 2018-08-30 10:59:20.0 +0200 @@ -23,7 +23,7 @@ libcurl4-openssl-dev, libmagickwand-dev, libpq-dev, - libssl1.0-dev, + libssl-dev, libxml2-dev, libxslt-dev, libffi-dev,
Bug#905334: marked as done (ffindex: missing build dependency on cmake)
Your message dated Thu, 30 Aug 2018 12:51:08 +0200 with message-id <20180830105108.dwo5dtww7h3zk...@an3as.eu> and subject line Re: Bug#905334: ffindex : autopkgtest regression: Segmentation fault has caused the Debian Bug report #905334, regarding ffindex: missing build dependency on 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.) -- 905334: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905334 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ffindex Version: 0.9.9.7+soedinglab+git20180802-1 X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), Since the upload of version 0.9.9.7+soedinglab+git20180802-1 the autopkgtest of your package started to fail. I have copied the output below. Could you please investigate? Currently this failure is contributing to delaying migration to testing with 13 days. You probably want to raise the severity of this bug if the segfault doesn't only happen in some corner-case of the test. Paul https://ci.debian.net/data/autopkgtest/unstable/amd64/f/ffindex/757862/log.gz autopkgtest [01:45:16]: test run-unit-test: [--- + ffindex_build -s ./test.data ./test.ffindex ./data ./data2 + ffindex_get ./test.data ./test.ffindex a b foo + tee ./test.out a bb fooo fooo + ffindex_modify -u ./test.ffindex b /tmp/autopkgtest-lxc.vvrqco0v/downtmp/build.ZBE/src/debian/tests/run-unit-test: line 21: 897 Segmentation fault ffindex_modify -u ./test.ffindex b autopkgtest [01:45:16]: test run-unit-test: ---] signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Hi Adrian, On Thu, Aug 30, 2018 at 12:54:03PM +0300, Adrian Bunk wrote: > Control: clone -1 -2 > Control: retitle -1 ffindex: missing build dependency on cmake You are so terribly fast. Could you please confirm that you are a human beeing and no bot watching BTS. ;-) Since I did the upload fixing the issue before I realised that you have split the bug I'm hereby closing the cmake build issue one. Thanks a lot for all your work Andreas. -- http://fam-tille.de--- End Message ---
Bug#902241: Bug #902241 in python-proliantutils marked as pending
Control: tag -1 pending Hello, Bug #902241 in python-proliantutils 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/openstack-team/libs/python-proliantutils/commit/f16b17cc8f6facd72ae21247e840e56df18df00c * Uploading to unstable: - Fixes FTBFS (Closes: #902241). (this message was generated automatically) -- Greetings https://bugs.debian.org/902241
Processed: Bug #902241 in python-proliantutils marked as pending
Processing control commands: > tag -1 pending Bug #902241 [src:python-proliantutils] python-proliantutils: FTBFS in stretch (AssertionError: IloConnectionError not raised) Added tag(s) pending. -- 902241: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902241 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#905334: ffindex : autopkgtest regression: Segmentation fault
Control: clone -1 -2 Control: retitle -1 ffindex: missing build dependency on cmake Control: retitle -2 ffindex: ffindex_modify segfaults during autopkgtest On Thu, Aug 30, 2018 at 10:12:23AM +0200, Paul Gevers wrote: > Control: retitle -1 ffindex: FTBFS everywhere and amd64 binary segfaults > Control: tags -1 ftbfs > Control: severity -1 serious > > On Fri, 3 Aug 2018 10:37:39 +0200 Paul Gevers wrote: > > Since the upload of version 0.9.9.7+soedinglab+git20180802-1 the > > autopkgtest of your package started to fail. I have copied the output below. > > Apart from this, the package fails to build on the Debian build > infrastructure, so the uploaded amd64 binary was probably build in a > less optimal environment: > https://buildd.debian.org/status/package.php?p=ffindex=unstable > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ffindex.html These two seem unrelated, the FTBFS is a missing build dependency. I'm splitting this into two bugs for the likely unrelated problems. > Paul 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: Re: Bug#905334: ffindex : autopkgtest regression: Segmentation fault
Processing control commands: > clone -1 -2 Bug #905334 [src:ffindex] ffindex: FTBFS everywhere and amd64 binary segfaults Bug 905334 cloned as bug 907624 > retitle -1 ffindex: missing build dependency on cmake Bug #905334 [src:ffindex] ffindex: FTBFS everywhere and amd64 binary segfaults Changed Bug title to 'ffindex: missing build dependency on cmake' from 'ffindex: FTBFS everywhere and amd64 binary segfaults'. > retitle -2 ffindex: ffindex_modify segfaults during autopkgtest Bug #907624 [src:ffindex] ffindex: FTBFS everywhere and amd64 binary segfaults Changed Bug title to 'ffindex: ffindex_modify segfaults during autopkgtest' from 'ffindex: FTBFS everywhere and amd64 binary segfaults'. -- 905334: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905334 907624: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907624 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 905109
Processing commands for cont...@bugs.debian.org: > tags 905109 + buster sid Bug #905109 [gnome-shell-extension-pixelsaver] gnome-shell-extension-pixelsaver: global.screen is not available in GNOME Shell 3.29 Added tag(s) buster and sid. > thanks Stopping processing here. Please contact me if you need assistance. -- 905109: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905109 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#905472: marked as done (libtextwrap FTBFS: cannot find -ltextwrap)
Your message dated Thu, 30 Aug 2018 09:34:28 + with message-id and subject line Bug#905472: fixed in libtextwrap 0.1-14.2 has caused the Debian Bug report #905472, regarding libtextwrap FTBFS: cannot find -ltextwrap 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.) -- 905472: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905472 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libtextwrap Version: 0.1-14.1 Severity: serious Tags: ftbfs User: helm...@debian.org Usertags: rebootstrap libtextwrap fails to build from source on amd64 in unstable. A build log ends with: | touch configure-stamp | dh_testdir | /usr/bin/make | make[1]: Entering directory '/<>' | /usr/bin/make all-am | make[2]: Entering directory '/<>' | gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -MT dotextwrap.o -MD -MP -MF .deps/dotextwrap.Tpo -c -o dotextwrap.o dotextwrap.c | mv -f .deps/dotextwrap.Tpo .deps/dotextwrap.Po | /bin/bash ./libtool --tag=CC --mode=link gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro -o dotextwrap dotextwrap.o -ltextwrap | libtool: link: gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z -Wl,relro -o dotextwrap dotextwrap.o -ltextwrap | /usr/bin/ld: cannot find -ltextwrap | collect2: error: ld returned 1 exit status | make[2]: *** [Makefile:515: dotextwrap] Error 1 | make[2]: Leaving directory '/<>' | make[1]: *** [Makefile:373: all] Error 2 | make[1]: Leaving directory '/<>' | make: *** [debian/rules:56: build-stamp] Error 2 | dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 This looks very strange and more of a breakage of makefile dependencies. It didn't even try building -ltextwrap and links it already. The issue is reproducible without parallelism. I haven't seen it until "recently" though since meson and then pcre3 have fucked up bootstrap qa lately, "recently" means like two weeks here though reproducible builds didn't encounter the issue (yet?). The make-dfsg upload looks a bit suspicious, so I'm Ccing Ben here. I hope that someone can make sense of this, or at least reproduce it. Helmut --- End Message --- --- Begin Message --- Source: libtextwrap Source-Version: 0.1-14.2 We believe that the bug you reported is fixed in the latest version of libtextwrap, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 905...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Adrian Bunk (supplier of updated libtextwrap package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 15 Aug 2018 11:34:42 +0300 Source: libtextwrap Binary: libtextwrap-dev libtextwrap1 libtextwrap1-udeb Architecture: source Version: 0.1-14.2 Distribution: unstable Urgency: medium Maintainer: Anibal Monsalve Salazar Changed-By: Adrian Bunk Description: libtextwrap-dev - text-wrapping library with i18n - development files libtextwrap1 - text-wrapping library with i18n - runtime libtextwrap1-udeb - text-wrapping library with i18n - runtime udeb (udeb) Closes: 905472 Changes: libtextwrap (0.1-14.2) unstable; urgency=medium . * Non-maintainer upload. * Makefile.am: Fix dependency bug exposed by automake 1.16, thanks to Helmut Grohne. (Closes: #905472) Checksums-Sha1: 5672168dde62425e4ddf67de74b863e04ab466de 1918 libtextwrap_0.1-14.2.dsc 42e116d46b6f52d467b781ad844ad6e8f18a1785 5932 libtextwrap_0.1-14.2.debian.tar.xz Checksums-Sha256: 206412c9724b96c8c5695657b01638c949a022e269ec154f23df99c0bada6f06 1918 libtextwrap_0.1-14.2.dsc 51c47a0cd4b89bd97986d23ec32dbbad2aba5977d61cf4e562e5ec7b7532bbfc 5932 libtextwrap_0.1-14.2.debian.tar.xz Files: fae1ad01ff838565ac923c331e03ac2c 1918 libs important libtextwrap_0.1-14.2.dsc 50ef269a7abf00fac98859d4e59eb4ba 5932 libs important libtextwrap_0.1-14.2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAltz5hQACgkQiNJCh6LY
Processed: reassign 907576 to wnpp, forcibly merging 691685 907576, reassign 907596 to grub-efi-arm ...
Processing commands for cont...@bugs.debian.org:
> reassign 907576 wnpp
Bug #907576 [dream --a software digital radio mondiale (drm) receiver (rfp]
ITP: dream --A Software Digital Radio Mondiale (DRM) receiver (RFP 691685)
Warning: Unknown package 'dream'
Warning: Unknown package '--a'
Warning: Unknown package 'software'
Warning: Unknown package 'digital'
Warning: Unknown package 'mondiale'
Warning: Unknown package 'drm'
Warning: Unknown package 'receiver'
Warning: Unknown package 'rfp'
Bug reassigned from package 'dream --a software digital radio mondiale (drm)
receiver (rfp' to 'wnpp'.
Ignoring request to alter found versions of bug #907576 to the same values
previously set
Ignoring request to alter fixed versions of bug #907576 to the same values
previously set
> forcemerge 691685 907576
Bug #691685 [wnpp] RFP: dream -- A software Digital Radio Mondiale (DRM)
receiver
Bug #907576 [wnpp] ITP: dream --A Software Digital Radio Mondiale (DRM)
receiver (RFP 691685)
Severity set to 'wishlist' from 'normal'
Merged 691685 907576
> reassign 907596 grub-efi-arm 2.02+dfsg1-6
Bug #907596 [grub-arm-efi] grub-arm-efi fails to boot kernel
Warning: Unknown package 'grub-arm-efi'
Bug reassigned from package 'grub-arm-efi' to 'grub-efi-arm'.
No longer marked as found in versions 2.02+dfsg1-6.
Ignoring request to alter fixed versions of bug #907596 to the same values
previously set
Bug #907596 [grub-efi-arm] grub-arm-efi fails to boot kernel
Marked as found in versions grub2/2.02+dfsg1-6.
> notfound 895657 0.91-1
Bug #895657 {Done: Juhani Numminen } [gcompris-qt]
gcompris-qt: Icons missing
No longer marked as found in versions gcompris-qt/0.91-1.
> notfixed 907197 1:60.0-2
Bug #907197 {Done: Carsten Schoenert } [thunderbird]
thunderbird 60 - although thunderbird-l10n-it is installed, the language is
always English
No longer marked as fixed in versions 1:60.0-2.
> reassign 907248 libpmix2 3.0.1-1
Bug #907248 {Done: Alastair McKinstry }
[libopenmpi3,libpmix2] libopenmpi3, libpmix2: both ship libpmix.so.2 without
suitable conflicts / replaces
Bug reassigned from package 'libopenmpi3,libpmix2' to 'libpmix2'.
No longer marked as found in versions libpmix2/3.0.1-1 and
libopenmpi3/3.1.1.real-7.
No longer marked as fixed in versions pmix/3.0.1-2.
Bug #907248 {Done: Alastair McKinstry } [libpmix2]
libopenmpi3, libpmix2: both ship libpmix.so.2 without suitable conflicts /
replaces
Marked as found in versions pmix/3.0.1-1.
> fixed 907248 3.0.1-2
Bug #907248 {Done: Alastair McKinstry } [libpmix2]
libopenmpi3, libpmix2: both ship libpmix.so.2 without suitable conflicts /
replaces
Marked as fixed in versions pmix/3.0.1-2.
> reassign 906051 init-system-helpers 1.52
Bug #906051 {Done: Felipe Sateler } [src:puppet,
src:init-system-helpers] init-system-helpers breaks puppet autopkgtest: puppet
service not running
Bug reassigned from package 'src:puppet, src:init-system-helpers' to
'init-system-helpers'.
Ignoring request to alter found versions of bug #906051 to the same values
previously set
No longer marked as fixed in versions init-system-helpers/1.54.
Bug #906051 {Done: Felipe Sateler } [init-system-helpers]
init-system-helpers breaks puppet autopkgtest: puppet service not running
Marked as found in versions init-system-helpers/1.52.
> fixed 906051 1.54
Bug #906051 {Done: Felipe Sateler } [init-system-helpers]
init-system-helpers breaks puppet autopkgtest: puppet service not running
Marked as fixed in versions init-system-helpers/1.54.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
691685: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691685
895657: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895657
906051: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906051
907197: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907197
907248: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907248
907576: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907576
907596: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907596
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#907171: prometheus FTBFS:
On Mon, 2018-08-27 at 19:18 +0100, Martín Ferrari wrote: > On 27/08/18 17:08, Adrian Bunk wrote: > > > How often did you try? > > > > I would say the probability to hit is somewhere around 50%: > > https://tests.reproducible-builds.org/debian/history/prometheus.html > > I just tried 20 builds, while using desktop applications that put some > extra strain on tHE CPU, and none failed.. Port 9090 isn't reserved or privileged at all afaik so it's not out of the question that some other random outgoing socket connection might be using it as a source port (or listening on it) at any given point, whether it is prom running on the host or something else. Does `nc -l -p 9090` repro the test failure perhaps? Unless the tests are run in their own network namespace (which provides some guarantees over what else might be bound to a port, I can't seem to find logs which would confirm or deny if a netns was in use here though) probably the test needs to use a random port or otherwise be tollerant of 9090 not being available. Maybe there is (or should be) an autopkgtest flag to request a clean netns be used? Ian.
Processed: Re: Bug#895723: librsvg: FTBFS on powerpc arches
Processing control commands: > severity -1 serious Bug #895723 [src:librsvg] librsvg: FTBFS on powerpc arches Severity set to 'serious' from 'important' > tags -1 + ftbfs Bug #895723 [src:librsvg] librsvg: FTBFS on powerpc arches Added tag(s) ftbfs. -- 895723: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895723 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#907616: budgie-desktop: needs modification for Mutter 3.30
Simon Not clear here. Should I submit an upload to experimental? If so I will do that asap David On Thu, 30 Aug 2018, 09:21 Simon McVittie, wrote: > Source: budgie-desktop > Version: 10.4+git20171031.10.g9f71bb8-1.2 > Severity: serious > Justification: https://bugs.debian.org/906015 > > The version of budgie-desktop in testing/unstable is not compatible with > mutter 3.29.x/3.30, which is required by the corresponding GNOME Shell > version. These are currently in experimental, but should be uploaded to > unstable soon. > > The version in Ubuntu 'cosmic' appears to have already been patched to > be compatible with GNOME 3.30. > > smcv >
Processed: block 906015 with 907616
Processing commands for cont...@bugs.debian.org: > block 906015 with 907616 Bug #906015 [release.debian.org] transition: mutter 3.30, gnome-shell 3.30 906015 was blocked by: 905114 905110 905107 905106 905112 905113 905109 906015 was not blocking any bugs. Added blocking bug(s) of 906015: 907616 > thanks Stopping processing here. Please contact me if you need assistance. -- 906015: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906015 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#907618: hddemux FTBFS
Source: hddemux Version: 0.4-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=hddemux=sid ... cleaning up --- cleaning up working directory /tmp/tmp.bu60TW2ktI ./testsuite: line 50: 6762 Terminated systemd-socket-activate -l "$ip:8853" --fdname=tls /usr/sbin/kresd -c "$d/kresd.conf" "$d" 2> "$d/kresd.err" ./testsuite: line 50: 6764 Terminated systemd-socket-activate -l "$ip:2000" -E=HTTP_TARGET="$ip:8853" -E DNS_TARGET="$ip:8853" "$hddemux" 2> "$d/hddemux.err" make[1]: *** [Makefile:13: check] Error 1
Bug#907617: cylc binary-any FTBFS
Source: cylc Version: 7.7.2-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=cylc=sid ... debian/rules override_dh_fixperms make[1]: Entering directory '/<>' # Delete after install. Use packages instead. for p in Pyro cherrypy markupsafe jinja2 ; do \ rm -rf debian/python-cylc/usr/lib/python2.7/dist-packages/$p ; \ done chmod +x debian/cylc/usr/share/bash-completion/completions/cylc-bash-completion chmod: cannot access 'debian/cylc/usr/share/bash-completion/completions/cylc-bash-completion': No such file or directory make[1]: *** [debian/rules:37: override_dh_fixperms] Error 1
Bug#907616: budgie-desktop: needs modification for Mutter 3.30
Source: budgie-desktop Version: 10.4+git20171031.10.g9f71bb8-1.2 Severity: serious Justification: https://bugs.debian.org/906015 The version of budgie-desktop in testing/unstable is not compatible with mutter 3.29.x/3.30, which is required by the corresponding GNOME Shell version. These are currently in experimental, but should be uploaded to unstable soon. The version in Ubuntu 'cosmic' appears to have already been patched to be compatible with GNOME 3.30. smcv
Processed: limit source to libnet-ssleay-perl, tagging 895959
Processing commands for cont...@bugs.debian.org: > limit source libnet-ssleay-perl Limiting to bugs with field 'source' containing at least one of 'libnet-ssleay-perl' Limit currently set to 'source':'libnet-ssleay-perl' > tags 895959 + pending Bug #895959 [libnet-ssleay-perl] libnet-ssleay-perl: FTBFS with openssl 1.1.1 in exp Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 895959: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895959 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: ffindex : autopkgtest regression: Segmentation fault
Processing control commands: > retitle -1 ffindex: FTBFS everywhere and amd64 binary segfaults Bug #905334 [src:ffindex] ffindex : autopkgtest regression: Segmentation fault Changed Bug title to 'ffindex: FTBFS everywhere and amd64 binary segfaults' from 'ffindex : autopkgtest regression: Segmentation fault'. > tags -1 ftbfs Bug #905334 [src:ffindex] ffindex: FTBFS everywhere and amd64 binary segfaults Added tag(s) ftbfs. > severity -1 serious Bug #905334 [src:ffindex] ffindex: FTBFS everywhere and amd64 binary segfaults Severity set to 'serious' from 'normal' -- 905334: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905334 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#905114: gnome-shell-extension-multi-monitors: global.screen is not available in GNOME Shell 3.29
Processing control commands: > forwarded -1 https://github.com/spin83/multi-monitors-add-on/issues/70 Bug #905114 [gnome-shell-extension-multi-monitors] gnome-shell-extension-multi-monitors: global.screen is not available in GNOME Shell 3.29 Set Bug forwarded-to-address to 'https://github.com/spin83/multi-monitors-add-on/issues/70'. > severity -1 serious Bug #905114 [gnome-shell-extension-multi-monitors] gnome-shell-extension-multi-monitors: global.screen is not available in GNOME Shell 3.29 Severity set to 'serious' from 'important' > tags -1 - experimental Bug #905114 [gnome-shell-extension-multi-monitors] gnome-shell-extension-multi-monitors: global.screen is not available in GNOME Shell 3.29 Removed tag(s) experimental. -- 905114: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905114 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#905113: gnome-shell-extension-taskbar: global.screen is not available in GNOME Shell 3.29
Processing control commands: > forwarded -1 https://github.com/zpydr/gnome-shell-extension-taskbar/issues/197 Bug #905113 [gnome-shell-extension-taskbar] gnome-shell-extension-taskbar: global.screen is not available in GNOME Shell 3.29 Set Bug forwarded-to-address to 'https://github.com/zpydr/gnome-shell-extension-taskbar/issues/197'. > tags -1 - experimental Bug #905113 [gnome-shell-extension-taskbar] gnome-shell-extension-taskbar: global.screen is not available in GNOME Shell 3.29 Removed tag(s) experimental. > severity -1 serious Bug #905113 [gnome-shell-extension-taskbar] gnome-shell-extension-taskbar: global.screen is not available in GNOME Shell 3.29 Severity set to 'serious' from 'important' -- 905113: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905113 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#905110: gnome-shell-extension-dash-to-panel: global.screen is not available in GNOME Shell 3.29
Processing control commands: > tags -1 = patch fixed-upstream Bug #905110 [gnome-shell-extension-dash-to-panel] gnome-shell-extension-dash-to-panel: global.screen is not available in GNOME Shell 3.29 Added tag(s) patch and fixed-upstream; removed tag(s) upstream and experimental. > severity -1 serious Bug #905110 [gnome-shell-extension-dash-to-panel] gnome-shell-extension-dash-to-panel: global.screen is not available in GNOME Shell 3.29 Severity set to 'serious' from 'important' -- 905110: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905110 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#905112: gnome-shell-extension-workspaces-to-dock: global.screen is not available in GNOME Shell 3.29
Processing control commands: > tags -1 = fixed-upstream Bug #905112 [gnome-shell-extension-workspaces-to-dock] gnome-shell-extension-workspaces-to-dock: global.screen is not available in GNOME Shell 3.29 Added tag(s) fixed-upstream; removed tag(s) upstream and experimental. > severity -1 serious Bug #905112 [gnome-shell-extension-workspaces-to-dock] gnome-shell-extension-workspaces-to-dock: global.screen is not available in GNOME Shell 3.29 Severity set to 'serious' from 'important' -- 905112: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905112 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#905109: gnome-shell-extension-pixelsaver: global.screen is not available in GNOME Shell 3.29
Processing control commands: > severity -1 serious Bug #905109 [gnome-shell-extension-pixelsaver] gnome-shell-extension-pixelsaver: global.screen is not available in GNOME Shell 3.29 Severity set to 'serious' from 'important' > tags -1 = patch fixed-upstream Bug #905109 [gnome-shell-extension-pixelsaver] gnome-shell-extension-pixelsaver: global.screen is not available in GNOME Shell 3.29 Added tag(s) fixed-upstream and patch; removed tag(s) upstream and experimental. > forwarded -1 https://github.com/deadalnix/pixel-saver/pull/174 Bug #905109 [gnome-shell-extension-pixelsaver] gnome-shell-extension-pixelsaver: global.screen is not available in GNOME Shell 3.29 Set Bug forwarded-to-address to 'https://github.com/deadalnix/pixel-saver/pull/174'. -- 905109: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905109 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#905107: gnome-shell-extension-pomodoro: global.screen is not available in GNOME Shell 3.29
Processing control commands: > severity -1 serious Bug #905107 [gnome-shell-pomodoro] gnome-shell-extension-pomodoro: global.screen is not available in GNOME Shell 3.29 Severity set to 'serious' from 'important' > tags -1 - experimental Bug #905107 [gnome-shell-pomodoro] gnome-shell-extension-pomodoro: global.screen is not available in GNOME Shell 3.29 Removed tag(s) experimental. -- 905107: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905107 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 905107 is forwarded to https://github.com/codito/gnome-pomodoro/issues/365
Processing commands for cont...@bugs.debian.org: > forwarded 905107 https://github.com/codito/gnome-pomodoro/issues/365 Bug #905107 [gnome-shell-pomodoro] gnome-shell-extension-pomodoro: global.screen is not available in GNOME Shell 3.29 Set Bug forwarded-to-address to 'https://github.com/codito/gnome-pomodoro/issues/365'. > thanks Stopping processing here. Please contact me if you need assistance. -- 905107: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905107 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Only waiting for another RM
Processing commands for cont...@bugs.debian.org: > unblock 904275 by 907239 Bug #904275 [ftp.debian.org] RM: llvm-toolchain-5.0 -- ROM; Trying to limit the number of llvm versions in Debian 904275 was blocked by: 904278 907239 904276 904277 904279 904275 was not blocking any bugs. Removed blocking bug(s) of 904275: 907239 > block 904275 by 907520 Bug #904275 [ftp.debian.org] RM: llvm-toolchain-5.0 -- ROM; Trying to limit the number of llvm versions in Debian 904275 was blocked by: 904277 904276 904279 904278 904275 was not blocking any bugs. Added blocking bug(s) of 904275: 907520 > thanks Stopping processing here. Please contact me if you need assistance. -- 904275: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904275 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#907612: firefox: FTBFS with iso-codes 4.0-1: No such file or directory: '/usr/share/xml/iso-codes/iso_639_3.xml'
Package: src:firefox
Version: 61.0.1-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Hi,
Same as firefox-esr, firefox fails to build in current sid with iso-codes
4.0-1. The failing part is:
--
debian/rules debian/control TESTDIR=
make[2]: Entering directory '/<>'
python -B debian/l10n/gen ach af an ar as ast az be bg bn-BD bn-IN br bs ca cak
cs cy da de dsb el en-GB en-ZA eo es-AR es-CL es-ES es-MX et eu fa ff fi fr fy-N
L ga-IE gd gl gn gu-IN he hi-IN hr hsb hu hy-AM ia id is it ja ka kab kk km kn k
o lij lt lv mai mk ml mr ms my nb-NO ne-NP nl nn-NO oc or pa-IN pl pt-BR pt-PT r
m ro ru si sk sl son sq sr sv-SE ta te th tr uk ur uz vi xh zh-CN zh-TW > debian
/l10n/browser-l10n.control
Traceback (most recent call last):
File "debian/l10n/gen", line 34, in
parser.parse('/usr/share/xml/iso-codes/iso_639_3.xml')
File "/usr/lib/python2.7/xml/sax/expatreader.py", line 105, in parse
source = saxutils.prepare_input_source(source)
File "/usr/lib/python2.7/xml/sax/saxutils.py", line 349, in prepare_input_sour
ce
f = urllib.urlopen(source.getSystemId())
File "/usr/lib/python2.7/urllib.py", line 87, in urlopen
return opener.open(url)
File "/usr/lib/python2.7/urllib.py", line 213, in open
return getattr(self, name)(url)
File "/usr/lib/python2.7/urllib.py", line 469, in open_file
return self.open_local_file(url)
File "/usr/lib/python2.7/urllib.py", line 483, in open_local_file
raise IOError(e.errno, e.strerror, e.filename)
IOError: [Errno 2] No such file or directory: '/usr/share/xml/iso-codes/iso_639_
3.xml'
make[2]: *** [debian/rules:148: debian/l10n/browser-l10n.control] Error 1
make[2]: Leaving directory '/<>'
make[1]: *** [debian/rules:255: override_dh_auto_clean] Error 2
--
Фром iso-codes changelog:
* New upstream version 4.0
- This new release does no longer include the XML data files.
Please use the JSON data files from now on.
Full build log attached. Reproducible builds also fail in sid:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/firefox.html
-- dam
firefox_amd64-2018-08-30T05:48:51Z.build.xz
Description: application/xz
Bug#906404: Bug #906404 in python-os-vif marked as pending
Control: tag -1 pending Hello, Bug #906404 in python-os-vif 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/openstack-team/libs/python-os-vif/commit/87feb9ebc0ca0148a1ee2706761c5ee67d385528 * Uploading to unstable: - Fixes FTBFS (Closes: #906404). (this message was generated automatically) -- Greetings https://bugs.debian.org/906404
Bug#892784: Bug #892784 in zaqar marked as pending
Control: tag -1 pending Hello, Bug #892784 in zaqar 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/openstack-team/services/zaqar/commit/f95ef304b0673418b378c7e9cd34f6f4d4a2383f * Uploading to unstable: - Fixes FTBFS (Closes: #892784). (this message was generated automatically) -- Greetings https://bugs.debian.org/892784
Processed: Bug #892784 in zaqar marked as pending
Processing control commands: > tag -1 pending Bug #892784 [src:zaqar] zaqar FTBFS: test failures Added tag(s) pending. -- 892784: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892784 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#900159: Bug #900159 in python-glanceclient marked as pending
Control: tag -1 pending Hello, Bug #900159 in python-glanceclient 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/openstack-team/clients/python-glanceclient/commit/7122ebea145387ec9ac7f9ae4fcd24fdef0b8b1c * Uploading to unstable: - Fixes FTBFS (Closes: #900159). (this message was generated automatically) -- Greetings https://bugs.debian.org/900159
Processed: Bug #906404 in python-os-vif marked as pending
Processing control commands: > tag -1 pending Bug #906404 [src:python-os-vif] python-os-vif: FTBFS in buster/sid (Could not import extension openstackdocstheme) Added tag(s) pending. -- 906404: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906404 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug #900159 in python-glanceclient marked as pending
Processing control commands: > tag -1 pending Bug #900159 [src:python-glanceclient] python-glanceclient: FTBFS against openssl 1.1.1 Added tag(s) pending. -- 900159: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900159 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
