Processed: fixed 941041 in 1.9.0-2+deb10u1
Processing commands for cont...@bugs.debian.org: > fixed 941041 1.9.0-2+deb10u1 Bug #941041 [unbound] unbound: FTBFS with nettle 3.5.1, accesses ECC curves directly Marked as fixed in versions unbound/1.9.0-2+deb10u1. > thanks Stopping processing here. Please contact me if you need assistance. -- 941041: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941041 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: fixed 941041 in 1.9.4-1
Processing commands for cont...@bugs.debian.org: > fixed 941041 1.9.4-1 Bug #941041 [unbound] unbound: FTBFS with nettle 3.5.1, accesses ECC curves directly Ignoring request to alter fixed versions of bug #941041 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 941041: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941041 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#922569: marked as done (FTBFS against opencv 4.0.1 (exp))
Your message dated Thu, 17 Oct 2019 05:04:29 + with message-id and subject line Bug#922569: fixed in caffe 1.0.0+git20180821.99bd997-3 has caused the Debian Bug report #922569, regarding FTBFS against opencv 4.0.1 (exp) 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.) -- 922569: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922569 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: caffe Version: 1.0.0+git20180821.99bd997-2 Severity: important Opencv4 breaks caffe due to API change. --- End Message --- --- Begin Message --- Source: caffe Source-Version: 1.0.0+git20180821.99bd997-3 We believe that the bug you reported is fixed in the latest version of caffe, 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 922...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mo Zhou (supplier of updated caffe 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, 17 Oct 2019 12:35:06 +0800 Source: caffe Architecture: source Version: 1.0.0+git20180821.99bd997-3 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Mo Zhou Closes: 922569 Changes: caffe (1.0.0+git20180821.99bd997-3) unstable; urgency=medium . * Cherry-pick PR#6693 to fix FTBFS against OpenCV4. (Closes: #922569) * Bump debhelper compat level to 12. * Bump Standards-Version to 4.4.0 (no change). * Add not-installed to silent dh-missing. Checksums-Sha1: cee9d6e7e233b36ebe7335fac1ea2f392b3e7459 3106 caffe_1.0.0+git20180821.99bd997-3.dsc 70628b6fe36f12fc8476125010823e25f0b4ae9d 15376 caffe_1.0.0+git20180821.99bd997-3.debian.tar.xz f87857c17ad41d64f20f25699e6b7b8d6c8f5ba2 18656 caffe_1.0.0+git20180821.99bd997-3_source.buildinfo Checksums-Sha256: 72fdf0e1e8561bc8e98f265bd59fe9404b0a2a43961135d59070d5ecd033d038 3106 caffe_1.0.0+git20180821.99bd997-3.dsc cbe7d0fbd92fca0451285038d589751bdce712cad87701652b8f5f7bb209b208 15376 caffe_1.0.0+git20180821.99bd997-3.debian.tar.xz 6f4e8bcc3a629f5e186695412d7a2ae7ae96dc40586ae3d6763d61a84a8fc664 18656 caffe_1.0.0+git20180821.99bd997-3_source.buildinfo Files: 8079a22d2533924e3e9dd5df36164e3d 3106 science optional caffe_1.0.0+git20180821.99bd997-3.dsc 91e50bea1702d135929a1f8f75d5490e 15376 science optional caffe_1.0.0+git20180821.99bd997-3.debian.tar.xz 7775cb31c2adc1502cd4cca39d87f3b9 18656 science optional caffe_1.0.0+git20180821.99bd997-3_source.buildinfo -BEGIN PGP SIGNATURE- iQJJBAEBCgAzFiEEY4vHXsHlxYkGfjXeYmRes19oaooFAl2n8MkVHGNkbHVtaW5h dGVAZ21haWwuY29tAAoJEGJkXrNfaGqKejwP/32W0UCdw14eRhJtM//dTEGeTO00 gckFJOkIGQYjkOY7E/SZ3e6KSbORG93rxETZZUUHTvWBQu5DSX7dIRNHK2h9Le+B NGeWwEym6l5bVthyv0t4/+yW/Zp7HYo5idpSXd44NXBP5kmh3dS7pFMf4TRZKoZI I1ML3aQ+oNfQu7CTkRaPyhXm4n4rHTzSKRXA6WKtipCGeQwjyD/yOaQGTrHsDu/Y SNH0J1zQsVUQ/+7/pVjuu+8oiX2b7dIjzBmQHY1LOqLZnIPluGgoLinrT2hODCIp Yv/Tql+8FMJgzvxLsVLrczs8+mhK+3WOfdlaNFkA4YZSFuQO1mAfIIuzuPz3UQAO kpz2VM1eeJgq1Zg+M5EzyZ+HpZQBjbxX04pr+Enm/unwyf4L/bzpd+m/uCSEIcjn vtWf3cFsB+ZrDnyMrC6dnWsMwECBq4ABPNHaWyzDUi7tIN8pk3de7SYIHfHtNQ6k kvAR1VQ/YkDH5SCB5bhES0oNCn0rHDaQzLYTRFblhJgZbXjYvSwkDe0uvoNGgjhb MZK87PGwjw8ZVU0VpLVPGmhVfeyna/9BIHK1AwyE/4EdrcCJ2e5QFdC07MUnQJKU MwXzMTq3yBuJQyF2pD5FHDWsoTzvsrUUBAlCx6+KB5pdfqGDYFNzkrHv+XFEafBO 0dYzZCxftSn+lSf7 =iuoI -END PGP SIGNATURE End Message ---
Bug#942113: marked as done (3depict: FTBFS on PPC64EL - POWERPC macro not always defined)
Your message dated Thu, 17 Oct 2019 04:19:05 + with message-id and subject line Bug#942113: fixed in 3depict 0.0.22-1.1 has caused the Debian Bug report #942113, regarding 3depict: FTBFS on PPC64EL - POWERPC macro not always defined 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.) -- 942113: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942113 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: 3depict Version 0.0.22-1 Severity: normal The error when compiling on ppc64el: g++ -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/freetype2 -I/usr/include/libpng16 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security --std=gnu++11 -I/usr/lib/powerpc64le-linux-gnu/wx/include/gtk3-unicode-3.0 -I/usr/include/wx-3.0 -D_FILE_OFFSET_BITS=64 -DWXUSINGDLL -D__WXGTK__ -I/usr/include -I/usr/include/libxml2 -L/lib -fopenmp -D_GLIBCXX_PARALLEL -pipe -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security --std=gnu++11 -c -o backend/3Depict-viscontrol.o `test -f 'backend/viscontrol.cpp' || echo './'`backend/viscontrol.cpp In file included from /usr/include/qhull/qhull_a.h:28, from backend/filters/algorithms/spatial.cpp:29: /usr/include/qhull/libqhull.h:46:30: error: operator '&&' has no right operand 46 | #if __MWERKS__ && __POWERPC__ | ^ is due to the fact that __POWERPC__ macro is not defined by default on g++ A see a couple of solutions I have tested , - define __POWERPC__ before including qhull_a.h - or have the included library qhull_a.h using __powerpc__ instead of __POWERPC__ --- End Message --- --- Begin Message --- Source: 3depict Source-Version: 0.0.22-1.1 We believe that the bug you reported is fixed in the latest version of 3depict, 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 942...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Olly Betts (supplier of updated 3depict 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, 17 Oct 2019 16:44:15 +1300 Source: 3depict Architecture: source Version: 0.0.22-1.1 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Olly Betts Closes: 942113 Changes: 3depict (0.0.22-1.1) unstable; urgency=medium . * Non-maintainer upload. * Fix FTBFS on ppc64el, new patch: undefine-__POWERPC__.patch (Closes: #942113) Checksums-Sha1: 0349c64226c136f84ffba6d722306cbc63f0c12c 2117 3depict_0.0.22-1.1.dsc 261e54adee062694d553c609ed0968c3231e2606 14484 3depict_0.0.22-1.1.debian.tar.xz a7058e6732560cf04b5dd23e9866153b996b84f5 15016 3depict_0.0.22-1.1_amd64.buildinfo Checksums-Sha256: 648af6a5a0c9baee1040f51154db3420e9160c6365853cbc2ffe0e2e8c2effbc 2117 3depict_0.0.22-1.1.dsc f4b2dc9f7bb012c4d95e70f1ec1681859a48991ccbf4f2e3a010632fb1fb9dbf 14484 3depict_0.0.22-1.1.debian.tar.xz 46136d78f3f0fcbb7f9aca4e254d19b8caeb3e6baf7a96a0c111546e323d1cf1 15016 3depict_0.0.22-1.1_amd64.buildinfo Files: d33c5d76cb1e834953f1d750ca8f9774 2117 science optional 3depict_0.0.22-1.1.dsc 4cc6235bba71a10836d4aff989d4e06c 14484 science optional 3depict_0.0.22-1.1.debian.tar.xz ea397dfe8bfab5ed5dc9e1beece32f1b 15016 science optional 3depict_0.0.22-1.1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEECOJAD/f+j+3jrLUoGBR7BzutKwcFAl2n5mcACgkQGBR7Bzut KwfU4xAAk3WF56PjMxOzoE8K82kD61HPmmWBBgph0CgP1CwoaPyk3ZbOQ7lFfBvK BppmUf1ephTryeYAu2mwjIgdUO145o7Z/IN75mxtYligzMXWsZgMIJacJJzIMizC tX3UJG2wl9m89AzDKm7lrr+Xx4drGwrM5r4U0G+yJaP1xuZNbz/krlgxjS3JMYRk 6a4SUAPH6q5vlng1sy4g3WeLMvKgfFQuDOp0oGgUtXZNQifgU6XUOMWfqwfRgaQw YcCqWP61AMxgKwsI6WAWUemfcr/YB9QbtFQjuoGGva4kbqIjTAzA9NjCa25eBj5h 1n5s/tuMqibaPi1vIwK3NJt+3Tdx903bG2sKiF1R2hvHMVNQVP55/J4Ls4SxiTLk QLbhI8hcAqx+XSuvtiEtzWupPh+D9vxLCAP/zHlN7TJ/LNb96MHMebjWLblu/1Ga MlaskI5qBab1uLgtlzreJmBN7EUzhvKJe7BU3SBELA/xXIaPhrat8r8LCJrV1GxN +mGy9JRamprmoJTBe9nkomaQ4ZqPm184kOeI6dA3YIDUxekMh4gRc91cbrf42TQs P+6wbtJudvlW/0J/3RRifpwgeXvPGXU5EEVpXge3n8VuB4su25YfBWJa54Xa7iaJ CM2NMFR6SxzHG/ymyiDU6054SMky4eZXOmGWwe/NAmu1KZU6tU8= =67c
Processed: Re: Bug#942113: 3depict: FTBFS on PPC64EL - POWERPC macro not always defined
Processing control commands: > tags -1 + pending Bug #942113 [3depict] 3depict: FTBFS on PPC64EL - POWERPC macro not always defined Added tag(s) pending. -- 942113: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942113 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#942113: 3depict: FTBFS on PPC64EL - POWERPC macro not always defined
Control: tags -1 + pending On Thu, Oct 17, 2019 at 04:12:35PM +1300, Olly Betts wrote: > And why does this only cause an error on one architecture? I downloaded > and compared the headers in the amd64 and ppc64el libqhull-dev packages > and they're identical. If neither __MWERKS__ nor __POWERPC__ are > defined on ppc64el then the same situation should exist on amd64. If > __POWERPC__ *is* defined on ppc64el that could be a difference - I can't > connect to the ppc64el porterbox to check though. Aha! wxWidgets "helpfully" defines __POWERPC__ for us on ppc64el, but to an empty value. Then 3depict has a workaround to define it to 1 if it is defined, because that empty value breaks Qhull. This bug has been open 7 days without a maintainer response now, so I'm going to NMU a patch to undefine __POWERPC__ instead, which seems a better solution since Qhull won't expect GCC to define it anyway. Cheers, Olly
Bug#942113: 3depict: FTBFS on PPC64EL - POWERPC macro not always defined
On Wed, Oct 16, 2019 at 11:30:47AM +0200, Thierry fa...@linux.ibm.com wrote: > I've personally always used __powerpc__ . > Here is my reference, very useful for all arch related defines : > https://wiki.debian.org/ArchitectureSpecificsMemo That page documents what's defined by GCC on Debian, but this check is for the metroworks compiler, so to fix this properly the question is really what that compiler defines on powerpc platforms. But looking more closely, I think this probably should be a defined-ness check: #if defined __MWERKS__ && defined __POWERPC__ But also, I see this code is in a header from a different package (libqhull-dev) so it seems this is really a bug in that. I would reassign, but I'm wondering if I'm missing something here - qhull was last uploaded in 2017 and ten other packages build-depend on libqhull-dev, so why aren't they all FTBFS on ppc64el too? $ reverse-depends -b libqhull-dev Reverse-Build-Depends = * 3depict * gdal * getfem++ * gnudatalanguage * meshlab * octave * pcl * plplot * pymca * ros-geometric-shapes * saga And why does this only cause an error on one architecture? I downloaded and compared the headers in the amd64 and ppc64el libqhull-dev packages and they're identical. If neither __MWERKS__ nor __POWERPC__ are defined on ppc64el then the same situation should exist on amd64. If __POWERPC__ *is* defined on ppc64el that could be a difference - I can't connect to the ppc64el porterbox to check though. But testing this on amd64 I get no error anyway: #if __MWERKS__ && __amd64__ Cheers, Olly
Bug#932529: (no subject)
Hi, I uploaded a NMU to 5-day/delay queue. Feel free to cancel this upload if needed. Thanks. Regards, Thiago Andrade diff -Nru fbcat-0.3/debian/changelog fbcat-0.3/debian/changelog --- fbcat-0.3/debian/changelog 2012-05-13 18:02:07.0 -0300 +++ fbcat-0.3/debian/changelog 2019-10-16 22:37:54.0 -0300 @@ -1,3 +1,22 @@ +fbcat (0.3-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * Using new DH level format. Consequently: + - debian/compat: removed. + - debian/control: changed from 'debhelper 7' to 'debhelper-compat 12' in + Build-Depends field. + * debian/control: + - bumped Standards-Version to 4.4.1. + - updated the homepage field. Thanks to Jakub Wilk + (Closes: #783970) + * debian/rules: replaced a deprecated option (--until and --remaining) + to use an override_dh_auto_build. Thanks to + Niels Thykier (Closes: #932529) + * debian/watch: full updated. Thanks to Jakub Wilk + (Closes: #749865) + + -- Thiago Andrade Marques Wed, 16 Oct 2019 22:37:54 -0300 + fbcat (0.3-1) unstable; urgency=low * New upstream version diff -Nru fbcat-0.3/debian/compat fbcat-0.3/debian/compat --- fbcat-0.3/debian/compat 2012-05-13 17:43:40.0 -0300 +++ fbcat-0.3/debian/compat 1969-12-31 21:00:00.0 -0300 @@ -1 +0,0 @@ -7 diff -Nru fbcat-0.3/debian/control fbcat-0.3/debian/control --- fbcat-0.3/debian/control 2012-05-13 18:01:01.0 -0300 +++ fbcat-0.3/debian/control 2019-10-16 22:37:54.0 -0300 @@ -3,11 +3,11 @@ Priority: extra Maintainer: Piotr Lewandowski Uploaders: Luca Bruno -Build-Depends: debhelper (>= 7), docbook-xml (>= 4.5), docbook-xsl, xsltproc, libxml2-utils, linux-libc-dev, dpkg-dev (>= 1.16.1~) -Standards-Version: 3.9.3 +Build-Depends: debhelper-compat (= 12), docbook-xml (>= 4.5), docbook-xsl, xsltproc, libxml2-utils, linux-libc-dev, dpkg-dev (>= 1.16.1~) +Standards-Version: 4.4.1 Vcs-Browser: http://git.debian.org/?p=collab-maint/fbcat.git Vcs-Git: git://git.debian.org/collab-maint/fbcat.git -Homepage: http://fbcat.googlecode.com/ +Homepage: https://jwilk.net/software/fbcat Package: fbcat Architecture: any diff -Nru fbcat-0.3/debian/rules fbcat-0.3/debian/rules --- fbcat-0.3/debian/rules 2012-05-13 18:01:01.0 -0300 +++ fbcat-0.3/debian/rules 2019-10-16 22:37:54.0 -0300 @@ -4,9 +4,9 @@ include /usr/share/dpkg/buildflags.mk build build-arch: - dh build --until dh_auto_build +override_dh_auto_build: + dh_auto_build $(MAKE) -C doc - dh build --remaining %: dh $@ diff -Nru fbcat-0.3/debian/watch fbcat-0.3/debian/watch --- fbcat-0.3/debian/watch 2012-05-13 17:43:40.0 -0300 +++ fbcat-0.3/debian/watch 2019-10-16 22:37:54.0 -0300 @@ -1,5 +1,2 @@ -version=3 -opts=\ -downloadurlmangle=s|.*[?]name=(.*?)&.*|http://fbcat.googlecode.com/files/$1|,\ -filenamemangle=s|[^/]+[?]name=(.*?)&.*|$1| \ -http://code.google.com/p/fbcat/downloads/detail[?]name=fbcat-([0-9.]+).tar.gz&.* +version=4 +https://github.com/jwilk/fbcat/releases .*/archive/v?(\d\S+)\.tar\.(?:bz2|gz|xz) -- ... ⢀⣴⠾⠻⢶⣦⠀ Thiago Andrade Marques ⣾⠁⢰⠒⠀⣿⡁ GPG: 4096R/F8CDB08B ⢿⡄⠘⠷⠚⠋⠀ GPG Fingerprint: 1D38 EE3C 624F 955C E1FA 3C85 5A30 3591 F8CD B08B ⠈⠳⣄ Cel: 19 98181-1156
Processed: control
Processing commands for cont...@bugs.debian.org:
> severity 922566 serious
Bug #922566 [src:actiona] FTBFS against opencv 4.0.1 (exp)
Severity set to 'serious' from 'important'
> severity 922569 serious
Bug #922569 [src:caffe] FTBFS against opencv 4.0.1 (exp)
Severity set to 'serious' from 'important'
> severity 922570 serious
Bug #922570 [src:caffe-contrib] FTBFS against opencv 4.0.1 (exp)
Severity set to 'serious' from 'important'
> severity 922573 serious
Bug #922573 [src:darknet] FTBFS against opencv 4.0.1 (exp)
Severity set to 'serious' from 'important'
> severity 922574 serious
Bug #922574 [src:digikam] FTBFS against opencv 4.0.1 (exp)
Severity set to 'serious' from 'important'
> severity 922578 serious
Bug #922578 [src:eviacam] FTBFS against opencv 4.0.1 (exp)
Severity set to 'serious' from 'important'
> severity 922579 serious
Bug #922579 [src:freeture] FTBFS against opencv 4.0.1 (exp)
Severity set to 'serious' from 'important'
> severity 922582 serious
Bug #922582 [src:gmic] FTBFS against opencv 4.0.1 (exp)
Severity set to 'serious' from 'important'
> severity 922583 serious
Bug #922583 [src:gst-plugins-bad1.0] FTBFS against opencv 4.0.1 (exp)
Severity set to 'serious' from 'important'
> severity 922584 serious
Bug #922584 [src:limereg] FTBFS against opencv 4.0.1 (exp)
Severity set to 'serious' from 'important'
> severity 922585 serious
Bug #922585 [src:mldemos] FTBFS against opencv 4.0.1 (exp)
Severity set to 'serious' from 'important'
> severity 922586 serious
Bug #922586 [src:mrpt] FTBFS against opencv 4.0.1 (exp)
Severity set to 'serious' from 'important'
> severity 922587 serious
Bug #922587 [src:node-opencv] FTBFS against opencv 4.0.1 (exp)
Severity set to 'serious' from 'important'
> severity 922588 serious
Bug #922588 [src:openalpr] FTBFS against opencv 4.0.1 (exp)
Severity set to 'serious' from 'important'
> severity 922589 serious
Bug #922589 [src:opencfu] FTBFS against opencv 4.0.1 (exp)
Severity set to 'serious' from 'important'
> severity 922590 serious
Bug #922590 [src:php-facedetect] FTBFS against opencv 4.0.1 (exp)
Severity set to 'serious' from 'important'
> severity 922591 serious
Bug #922591 [src:ros-opencv-apps] FTBFS against opencv 4.0.1 (exp)
Severity set to 'serious' from 'important'
> severity 922592 serious
Bug #922592 [src:ros-vision-opencv] FTBFS against opencv 4.0.1 (exp)
Severity set to 'serious' from 'important'
> severity 922593 serious
Bug #922593 {Done: Bas Couwenberg } [src:saga] FTBFS
against opencv 4.0.1 (exp)
Severity set to 'serious' from 'important'
> severity 922595 serious
Bug #922595 [src:sdaps] FTBFS due to PDF compilation failure (against Opencv
4.0.1)
Severity set to 'serious' from 'important'
> severity 922596 serious
Bug #922596 [src:siril] FTBFS against opencv 4.0.1 (exp)
Severity set to 'serious' from 'important'
> severity 922597 serious
Bug #922597 {Done: Debian FTP Masters }
[src:sitplus] FTBFS against opencv 4.0.1 (exp)
Severity set to 'serious' from 'important'
> severity 922600 serious
Bug #922600 [src:visp] FTBFS against opencv 4.0.1 (exp)
Severity set to 'serious' from 'important'
> severity 915708 serious
Bug #915708 [src:eviacam] eviacam FTBFS against opencv 3.4.4 in experimental
Severity set to 'serious' from 'important'
> severity 915711 serious
Bug #915711 [src:mldemos] mldemos FTBFS against opencv 3.4.4 in experimental
Severity set to 'serious' from 'important'
> severity 915712 serious
Bug #915712 [src:php-facedetect] php-facedetect FTBFS against opencv 3.4.4 in
experimental
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
915708: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915708
915711: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915711
915712: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915712
922566: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922566
922569: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922569
922570: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922570
922573: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922573
922574: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922574
922578: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922578
922579: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922579
922582: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922582
922583: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922583
922584: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922584
922585: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922585
922586: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922586
922587: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922587
922588: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922588
922589: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922589
922590: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922590
922591: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922591
922592: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
Bug#937162: nototools: Python2 removal in sid/bullseye
On Wed, Oct 16, 2019 at 7:45 PM peter green wrote: > So it seems that to fix this the following steps are needed. Yes, I'm keeping an eye on this package & the Noto Emoji font. It was a mistake for fonttools to drop its Python2 package as early as it did before important reverse dependencies had stopped using it. But that's happening frequently in Debian now and it's a bit too late to complain about it now. Jeremy
Bug#942481: unclutter-startup: fails to configure on installation
Hi Axel, thanks for the immediate check and fix, very much appreciated. > Why are you using bash here? The script has a "#!/bin/sh" shebang line No special reason but simply habit ;-) Best Norbert -- PREINING Norbert http://www.preining.info Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
Bug#942459: wordpress: WordPress 5.2.4 Security Release
I can get the CVEs. I can also backport the patches into stable along with the previous set. Curiously, there were 6 patchsets and 6 security bugs. But not all of them match up. For example, two patchsets fix one bug and another patchset fixes a directory traversal which isn't mentioned at all. I'll be using this [1] to fix stable or its version equivalent. - Craig 1: https://github.com/WordPress/WordPress/commit/2fc33ef47d3a4d48f03ef79d4aacf420da51bb54
Bug#942481: marked as done (unclutter-startup: fails to configure on installation)
Your message dated Thu, 17 Oct 2019 03:22:23 +0200
with message-id <2019101701.hzdws42vv6ohb...@sym.noone.org>
and subject line Re: Bug#942481: unclutter-startup: fails to configure on
installation
has caused the Debian Bug report #942481,
regarding unclutter-startup: fails to configure on installation
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.)
--
942481: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942481
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: unclutter-startup
Version: 8-22
Severity: serious
Hi,
I am not sure whether this is the failure of unclutter-startup or
debconf, so please reassign if necessary.
unclutter-startup cannot --configure properly and always terminates with
post-installation script subprocess returned error exit status 10
The postinstall script is indeed trivial and it somehow hangs in the
debconf code:
$ bash -x /var/lib/dpkg/info/unclutter-startup.postinst configure
+ set -e
+ . /usr/share/debconf/confmodule
++ '[' '!' '' ']'
++ PERL_DL_NONLAZY=1
++ export PERL_DL_NONLAZY
++ '[' '' ']'
++ exec /usr/share/debconf/frontend
/var/lib/dpkg/info/unclutter-startup.postinst configure
I am not really sure why debconf frontend fails, though ...
Best
Norbert
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.3.6 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
unclutter-startup depends on no packages.
unclutter-startup recommends no packages.
Versions of packages unclutter-startup suggests:
ii unclutter-xfixes 1.5-2
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 8-23
Hi,
Norbert Preining wrote:
> unclutter-startup cannot --configure properly and always terminates with
> post-installation script subprocess returned error exit status 10
This is fixed in the just uploaded 8-23, but I forgot the "Closes:" in
the changelog. I just added that retroactively, but I still need to
close this bug report manually.
Here's the full changelog entry as it will appear with the next (8-24)
upload:
unclutter (8-23) experimental; urgency=low
* Move debian/unclutter.{config,template} to unclutter-startup, too.
+ Update debian/po/{POTFILES.in,templates.pot} accordingly.
+ Closes: #942481
* Declare compliance with Debian Policy 4.4.1. (No changes
needed.)
-- Axel Beckert Thu, 17 Oct 2019 03:12:53 +0200
Regards, Axel
--
,''`. | Axel Beckert , https://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5
`-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
signature.asc
Description: PGP signature
--- End Message ---
Processed: Re: Bug#942481: unclutter-startup: fails to configure on installation
Processing control commands: > tag -1 confirmed pending Bug #942481 [unclutter-startup] unclutter-startup: fails to configure on installation Added tag(s) pending and confirmed. -- 942481: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942481 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#942481: unclutter-startup: fails to configure on installation
Control: tag -1 confirmed pending
Hi Norbert,
Norbert Preining wrote:
> I am not sure whether this is the failure of unclutter-startup or
> debconf, so please reassign if necessary.
Thanks for the bug report! I can reproduce this in a clean pbuilder
sid + experimental chroot.
It seems as if I have forgotten to move
/var/lib/dpkg/info/unclutter.{config,template} to
/var/lib/dpkg/info/unclutter-startup.{config,template}, too. At least
it no more fails if I do that.
Will upload a fixed version to Debian Experimental again, soon.
One remark:
> $ bash -x /var/lib/dpkg/info/unclutter-startup.postinst configure
Why are you using bash here? The script has a "#!/bin/sh" shebang line
and your /bin/sh is a dash, not a bash:
> Shell: /bin/sh linked to /bin/dash
And bash and dash behave slightly different, especially when it comes
to when they spawn subshells (or don't).
Regards, Axel
--
,''`. | Axel Beckert , https://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5
`-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
Bug#942481: unclutter-startup: fails to configure on installation
Package: unclutter-startup Version: 8-22 Severity: serious Hi, I am not sure whether this is the failure of unclutter-startup or debconf, so please reassign if necessary. unclutter-startup cannot --configure properly and always terminates with post-installation script subprocess returned error exit status 10 The postinstall script is indeed trivial and it somehow hangs in the debconf code: $ bash -x /var/lib/dpkg/info/unclutter-startup.postinst configure + set -e + . /usr/share/debconf/confmodule ++ '[' '!' '' ']' ++ PERL_DL_NONLAZY=1 ++ export PERL_DL_NONLAZY ++ '[' '' ']' ++ exec /usr/share/debconf/frontend /var/lib/dpkg/info/unclutter-startup.postinst configure I am not really sure why debconf frontend fails, though ... Best Norbert -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.3.6 (SMP w/8 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) unclutter-startup depends on no packages. unclutter-startup recommends no packages. Versions of packages unclutter-startup suggests: ii unclutter-xfixes 1.5-2 -- no debconf information
Processed: re: routes: Python2 removal in sid/bullseye
Processing commands for cont...@bugs.debian.org: > severity 938407 serious Bug #938407 [src:routes] routes: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > block 938816 by 938407 Bug #938816 [src:webtest] webtest: Python2 removal in sid/bullseye 938816 was blocked by: 938015 938816 was blocking: 936196 Added blocking bug(s) of 938816: 938407 > thanks Stopping processing here. Please contact me if you need assistance. -- 938407: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938407 938816: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938816 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: re: python-pecan: Python2 removal in sid/bullseye
Processing commands for cont...@bugs.debian.org: > severity 938015 serious Bug #938015 [src:python-pecan] python-pecan: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > block 938816 by 938015 Bug #938816 [src:webtest] webtest: Python2 removal in sid/bullseye 938816 was not blocked by any bugs. 938816 was blocking: 936196 Added blocking bug(s) of 938816: 938015 > thanks Stopping processing here. Please contact me if you need assistance. -- 938015: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938015 938816: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938816 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#935669: assaultcube-data (1.2.0.2.1-3) in enabled autobuilding
Hi, The assaultcube-data (1.2.0.2.1-3) package includes "XS-Autobuild: yes" in the header portion of "debian/control"[1] and the disclaimer compliance with the licenses contained in "debian/copyright"[2] where It's okay to create the software automatically across multiple architectures and distribute it. [1] https://sources.debian.org/src/assaultcube-data/1.2.0.2.1-3/debian/control [2] https://sources.debian.org/src/assaultcube-data/1.2.0.2.1-3/debian/copyright If so, could you approve this package or do I need to target something else? Thanks! -- ⢀⣴⠾⠻⢶⣦⠀ Carlos Donizete Froes [a.k.a coringao] ⣾⠁⢠⠒⠀⣿⡁ Debian Wiki: https://wiki.debian.org/coringao ⢿⡄⠘⠷⠚⠋⠀ GPG: 4096R/B638B780 ⠈⠳⣄⠀⠀⠀ 2157 630B D441 A775 BEFF D35F FA63 ADA6 B638 B780 signature.asc Description: This is a digitally signed message part
Processed: re: grokmirror: Python2 removal in sid/bullseye
Processing commands for cont...@bugs.debian.org: > severity 936665 serious Bug #936665 [src:grokmirror] grokmirror: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 936665: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936665 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#937162: nototools: Python2 removal in sid/bullseye
Hi. As I posted earlier nototools build-depends on python-fonttools which is no longer built by the fonttools source package. Since this package turned out not to be eligable for autoremoval I decided to take a slightly deeper look. nototools builds a single binary package, python-nototools which has two reverse build-dependencies: fonts-noto-color-emoji and fonts-roboto-slab , both of those are considered "key packages" due to their popcon score. Some googling reveals that upstream has just accepted a python3 pull-request for nototools. https://github.com/googlefonts/nototools/pull/488/commits So it seems that to fix this the following steps are needed. 1. Apply the upstream fix for python 3 support. 2. Add a python3-nototools package 3. Adapt fonts-noto-color-emoji and fonts-roboto-slab to use python3-nototools instead of python-nototools. 4. Drop the python-nototools package.
Bug#875075: [openscenegraph] Future Qt4 removal from Buster
Hi, Em sáb, 12 de out de 2019 às 13:23, Sebastiaan Couwenberg escreveu: > > I suggest to first update src:openscenegraph to 3.6. > > Once that's in unstable file bugreports for the src:openscenegraph-3.4 > rdeps to have them migrate to 3.6. I uploaded the new version on Alberto's behalf, initially to experimental. Hoping that it doesn't take too long to pass NEW and that everything goes well, but then the move to unstable can be immediate. Cheers. -- Manuel A. Fernandez Montecelo
Bug#942478: A little more info
Greetings: If you'd like a pcap file showing the client side of this bug, just holler. The big picture of it in action is at: https://www.artsackett.com/apt_fail.png The wireshark window is showing apt's nausea -- in the whole .pcap file there's the usual drop scenario: three requests thirty seconds apart, each with scads of TCP retransmits and then FIN/ACK. -- Art Sackett http://www.artsackett.com/
Bug#942478: apt User-Agent causes mirrors to drop connections
Package: apt Version: 1.8.2 Severity: grave Justification: renders package unusable Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Attempting to install Debian10.1/AMD64 and/or updating/upgrading existing installations. * What exactly did you do (or not do) that was effective (or ineffective)? apt update * What was the outcome of this action? ERR:1 stable InRelease Connection failed [IP:] * What outcome did you expect instead? The usual 'apt update' response. What works around it: I added file /etc/apt/apt.sources.d/99useragent and configured it to send the same User-Agent string as my Firefox web browser. I've six machines that suffered this, and all respond well to the workaround. *** End of the template - remove these template lines *** -- Package-specific info: -- (no /etc/apt/preferences present) -- -- (no /etc/apt/preferences.d/* present) -- -- /etc/apt/sources.list -- deb http://ftp.us.debian.org/debian/ stable main non-free contrib deb-src http://ftp.us.debian.org/debian/ stable main non-free contrib deb http://security.debian.org/debian-security buster/updates main contrib non-free deb-src http://security.debian.org/debian-security buster/updates main contrib non-free # buster-updates deb http://ftp.us.debian.org/debian/ buster-updates main contrib non-free deb-src http://ftp.us.debian.org/debian/ buster-updates main contrib non-free # Debian multimedia #deb http://www.deb-multimedia.org stable main non-free # Backports deb http://ftp.debian.org/debian/ buster-backports main contrib non-free -- (/etc/apt/sources.list.d/google-chrome.list present, but not submitted) -- -- (/etc/apt/sources.list.d/virtualbox.list present, but not submitted) -- -- (/etc/apt/sources.list.d/x2go.list present, but not submitted) -- -- System Information: Debian Release: 10.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-6-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE 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) LSM: AppArmor: enabled Versions of packages apt depends on: ii adduser 3.118 ii debian-archive-keyring 2019.1 ii gpgv2.2.12-1+deb10u1 ii libapt-pkg5.0 1.8.2 ii libc6 2.28-10 ii libgcc1 1:8.3.0-6 ii libgnutls30 3.6.7-4 ii libseccomp2 2.3.3-4 ii libstdc++6 8.3.0-6 Versions of packages apt recommends: ii ca-certificates 20190110 Versions of packages apt suggests: pn apt-doc ii aptitude0.8.11-7 ii dpkg-dev1.19.7 ii gnupg 2.2.12-1+deb10u1 ii gnupg2 2.2.12-1+deb10u1 ii powermgmt-base 1.34 ii synaptic0.84.6 -- no debconf information
Bug#942229: llvm-toolchain-9: Fails to compile on i386
> > http://debomatic-i386.debian.net/distribution#unstable/llvm-toolchain-9/9-2/buildlog > > can't reproduce on a clean sbuild environmen, neither on builders. > > Please make sure you have all the build-deps installed, and share > something more wrt build log and environment. > > G. I did kind of kick myself for being too quick with hitting send, my apologies. I have a 32 bit Buster chroot to build the i386 packages for my Buster 64 bit machine because some i386 build-dep packages don't like living together in 64 bit. (I'm trying to get Mesa, Wine, vulkan, non-free firmware and kernel to the latest versions possible and backporting seemed like a good idea when I started. LLVM is needed by Mesa 19.x.) I do it like this (https://wiki.debian.org/SimpleBackportCreation) and use the chroot to compile unmodified Debian Bullseye/Sid packages from their Debian sources. LLVM-9 built fine (took hours though) on AMD64 and other packages built fine in the chroot. Build-deps are installed. I don't know where to log for log files so your help would be appreciated. I looked in a lot of directories but nothing really stood out to my untrained eye. Thanks, Matthew ETA Humble apologies for accidentally replying to your personal email. This is attempt number 2. It's been a while since I used Linux or Evolution. Hopefully I got this right...
Bug#871933: marked as done (xsynth-dssi: no Gui for plugin after loading)
Your message dated Wed, 16 Oct 2019 22:35:17 + with message-id and subject line Bug#871933: fixed in xsynth-dssi 0.9.4-4 has caused the Debian Bug report #871933, regarding xsynth-dssi: no Gui for plugin after loading 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.) -- 871933: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871933 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: xsynth-dssi Version: 0.9.4-3 Severity: important Dear Maintainer, I cannot get a GUI after loading plugin in muse or qtractor. package: xsynth-dssi (0.9.4-2) was working. Package: xsynth-dssi (0.9.4-3) is not working. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.11.6-lowlatency (SMP w/8 CPU cores; PREEMPT) 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 xsynth-dssi depends on: ii libatk1.0-0 2.24.0-1 ii libc62.24-12 ii libcairo21.14.10-1 ii libfontconfig1 2.12.3-0.2 ii libfreetype6 2.8-0.2 ii libgdk-pixbuf2.0-0 2.36.5-2 ii libglib2.0-0 2.53.4-3 ii libgtk2.0-0 2.24.31-2 ii liblo7 0.28-5+b2 ii libpango-1.0-0 1.40.6-1 ii libpangocairo-1.0-0 1.40.6-1 ii libpangoft2-1.0-01.40.6-1 xsynth-dssi recommends no packages. xsynth-dssi suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: xsynth-dssi Source-Version: 0.9.4-4 We believe that the bug you reported is fixed in the latest version of xsynth-dssi, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 871...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastian Ramacher (supplier of updated xsynth-dssi 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, 17 Oct 2019 00:18:46 +0200 Source: xsynth-dssi Architecture: source Version: 0.9.4-4 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Sebastian Ramacher Closes: 871933 Changes: xsynth-dssi (0.9.4-4) unstable; urgency=medium . [ Ondřej Nový ] * Team upload. * d/control: Set Vcs-* to salsa.debian.org * d/changelog: Remove trailing whitespaces . [ Felipe Sateler ] * Change maintainer address to debian-multime...@lists.debian.org . [ Ondřej Nový ] * d/watch: Use https protocol . [ Sebastian Ramacher ] * debian/: Bump debhelper compat to 12 * debian/control: - Bump Standards-Version - Set RRR: no * debian/patches: - Do not check for GTK 1 - Fix GtkKnob type handling (Closes: #871933) Checksums-Sha1: 89b2941d288879656c7f5de6170d0296cd402ae6 2054 xsynth-dssi_0.9.4-4.dsc 663cd5e627d132b19c88b2adf94baede66ff13f9 4296 xsynth-dssi_0.9.4-4.debian.tar.xz Checksums-Sha256: 85f7f1ee15c2481758c4e6bae1cfc3ced764356d7a8824b5f08c6b83caba8895 2054 xsynth-dssi_0.9.4-4.dsc c4b3dbbb2930b51cbe4739c063336fd1fd894a2c110547b649ec700d1430fa40 4296 xsynth-dssi_0.9.4-4.debian.tar.xz Files: 3853d265e09ffe6e247fa4a68929ee91 2054 sound optional xsynth-dssi_0.9.4-4.dsc 09efddae7fcb47e381c0f2cec801ad6e 4296 sound optional xsynth-dssi_0.9.4-4.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE94y6B4F7sUmhHTOQafL8UW6nGZMFAl2nl4YACgkQafL8UW6n GZMw9A/6AzWJnEMNzZgW54VgKtGxYlJWxpeInkMP77EwgkqKja59O7j7FEbrER3u 3zu0hfLU9piLluE8O1zqYbsH9/d3ipPZBeGIyCnKYalx8qnngzlZt3Ivwt41dJyO wot1aG9u/MqcxFBL9F2JvknHsUZ86xtpmgpd1nucCmiCTztTBAgs9L8sOgbcACSz U7sakdTyo5NehtakLP4WpV3ZEzR3UnWyrZITdaUPnwbRPa5Ly0z82K+eegHgKZcd agOcJ6vmIpIDBXxPHiui4eb3DexUnJle8fnQGaUMjwhfO+2T/UprYUvvBSCQpJ0B 7LRWiNeC3CDcsfep+f6JODy7g7sk6u5HnWIINgpXi6XqbRNhPC0itArlnkai9BGl wEgdepxWXf0paGK/mG0DtY16oQCRvwqys1ybHHWk++GhN8YTMiPDie9JvfDtckxm NgXoWKvxILkGAXSWbzuQ+3QRKwbJ91pwRf3kGEZs/LbWOSDltJaC7bXXozAlb5Jh lMCNEoei1wxnq2qhXi3rVsRUX8l2GcAUscYHrpJ99PCKc/Ld+IDjoAkVvN1dmrih nq9i5AJTSrJYs5LeAE4JcUwAYBQo5NZtN8LvNglp7JCLLnB26kWyrksQQnCdhFF/ uojn7w4sGwR
Bug#942442: Fwd: Bug#942442: libgnatvsn ftbfs in 9.2.1-10
> libgnatvsn ftbfs in 9.2.1-10 Sorry for the mess. After a successful build, it seems that I have incorrectly played the autoreconf/quilt refresh/scp/git commit music. A build currently tests the following fix. --- a/debian/patches/ada-libgnatvsn.diff +++ b/debian/patches/ada-libgnatvsn.diff @@ -437,7 +437,7 @@ } --- /dev/null +++ b/src/libgnatvsn/Makefile.in -@@ -0,0 +1,899 @@ +@@ -0,0 +1,938 @@ +# Makefile.in generated by automake 1.16.1 from Makefile.am. +# @configure_input@ +
Bug#941960: marked as done (gnome-shell-extension-log-out-button: fails to load under gnome-shell 3.34: TypeError: System._actionsItem is undefined)
Your message dated Wed, 16 Oct 2019 22:19:30 + with message-id and subject line Bug#941960: fixed in gnome-shell-extension-log-out-button 1.0.8-1 has caused the Debian Bug report #941960, regarding gnome-shell-extension-log-out-button: fails to load under gnome-shell 3.34: TypeError: System._actionsItem is undefined 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.) -- 941960: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941960 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gnome-shell-extension-log-out-button Version: 1.0.7-1 Severity: serious When using gnome-shell 3.34 GNOME Tweaks indicates the log-out-button extension fails to load on login. I was able to get this error from the Looking Glass thing for debugging GNOME shell: TypeError: System._actionsItem is undefined -- System Information: Debian Release: bullseye/sid APT prefers testing-debug APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.2.0-3-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8), LANGUAGE=en_AU:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gnome-shell-extension-log-out-button depends on: ii gnome-shell 3.34.0-2 gnome-shell-extension-log-out-button recommends no packages. gnome-shell-extension-log-out-button suggests no packages. -- no debconf information -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part --- End Message --- --- Begin Message --- Source: gnome-shell-extension-log-out-button Source-Version: 1.0.8-1 We believe that the bug you reported is fixed in the latest version of gnome-shell-extension-log-out-button, 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 941...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Kyle Robbertze (supplier of updated gnome-shell-extension-log-out-button 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, 16 Oct 2019 23:46:24 +0200 Source: gnome-shell-extension-log-out-button Architecture: source Version: 1.0.8-1 Distribution: unstable Urgency: medium Maintainer: Kyle Robbertze Changed-By: Kyle Robbertze Closes: 941960 Changes: gnome-shell-extension-log-out-button (1.0.8-1) unstable; urgency=medium . * Update watch file * New upstream version 1.0.8 (Closes: #941960) * Update maintainer email * Bump Standards-Version to 4.4.1 (no change) * Bump copyright years * Use debhelper-compat * Move git repo to debian group Checksums-Sha1: 3ee4937c5d90459a3624a74bfc09e22b822c4a11 2239 gnome-shell-extension-log-out-button_1.0.8-1.dsc 7e0301822b07854c38438ef83d621fec64ae853c 15819 gnome-shell-extension-log-out-button_1.0.8.orig.tar.gz dd44aeb9d5b05cf96e0562705ab423cbd6154cdb 2580 gnome-shell-extension-log-out-button_1.0.8-1.debian.tar.xz cbe8dd8f13deeff567a07e8eac94a12c019fe222 5767 gnome-shell-extension-log-out-button_1.0.8-1_amd64.buildinfo Checksums-Sha256: ed40460df27ff05c0431b635f8d2daa05803a8b18864b4b28188e4a85b91e61f 2239 gnome-shell-extension-log-out-button_1.0.8-1.dsc 9b4512b83d464539121dd17f66f12dcdde30bd19e8bbbcfc1c155302693169ff 15819 gnome-shell-extension-log-out-button_1.0.8.orig.tar.gz 90ea190de22820256fa57d7d00770153a8ec0f567dd0a0c4eed874c4632db021 2580 gnome-shell-extension-log-out-button_1.0.8-1.debian.tar.xz 3a1224cbca44a377adbd699fa0bdb5fb9c337c0df9f12daf0255ef9ff47e6409 5767 gnome-shell-extension-log-out-button_1.0.8-1_amd64.buildinfo Files: ee347e770475dfe40c35d5bf71c56311 2239 gnome optional gnome-shell-extension-log-out-button_1.0.8-1.dsc d49927a76751a17b36ac5424b9989b5e 15819 gnome optional gnome-shell-extension-log-out-button_1.0.8.orig.tar.gz ca16456340ecc145f96da2aab3e3ce38 2580 gnome optional gnome-shell-e
Bug#942315: tcpdump: Version in oldoldstable is higher than oldstable and stable
On Wed, Oct 16, 2019 at 9:48 PM Salvatore Bonaccorso wrote: > Ideally given the issues are denial of service issues, this would have > been okay via a point release. But we discussed this coincidentally in > the team concluding we could as well release it via security. But we > were thinking of postponing it a bit yet to see if some bug > reports/regression reports did appear after the unstable version was > exposed. Ah, okay. 4.9.3~git20190901-1 included significant packaging changes to drop root privileges by default, is that appropriate for an upload via security? (If so, it is my preferred avenue to reach stable users, as point releases aren't very frequent.) > Can you prepare updates for buster-security and stretch-security? I don't have much free time these days but I will try to get this done over the week-end. Thanks.
Bug#942468: Fix url
Sorry, the correct URL to the edit history of core/loki/Visitor.h is https://gitlab.kitware.com/xdmf/xdmf/commits/master/core/loki/Visitor.h -- Jonas Lippuner, PhD Scientist Computational Physics and Methods, CCS-2 Center for Theoretical Astrophysics Los Alamos National Laboratory jlippu...@lanl.gov 505-667-1646 http://jonaslippuner.com
Bug#942468: libxdmf-dev: Incompatible libloki header
Package: libxdmf-dev Version: 3.0+git20160803-5+b1 Severity: grave Justification: renders package unusable Dear Maintainer, Starting in version 3.0+git20190531-1 of this package, the libloki header were removed and the dependency on libloki-dev was introduced. Unfortunately, libxdmf has modified the core/loki/Visitor.h header file from the original libloki code (see https://gitlab.kitware.com/xdmf/xdmf/blob/master/core/loki/Visitor.h). The original header file from the libloki-dev package is incompatible with the libxdmf code, which means that no application can be built with libxdmf-dev version 3.0+git20190531-1. Removing the libloki and libloki-dev packages and downgrading to libxdmf-dev version 3.0+git20160803-5 fixes the issue, since that resotres the libloki headers shipped with libxdmf. I recommend removing the libloki-dev depencency and mark it as conflicting again (which it is), and shipping the libloki headers with the libxdmf-dev package (as does the xdmf code at https://gitlab.kitware.com/xdmf/xdmf). Thanks for mainting this package! Best, Jonas -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.2.0-3-amd64 (SMP w/48 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libxdmf-dev depends on: ii libgzstream-dev 1.5+dfsg-4 ii libxdmf3 3.0+git20160803-5+b1 libxdmf-dev recommends no packages. libxdmf-dev suggests no packages. -- no debconf information
Bug#942463: jss: CVE-2019-14823
Source: jss Version: 4.6.1-3 Severity: grave Tags: security upstream Forwarded: https://github.com/dogtagpki/jss/pull/284 Hi, The following vulnerability was published for jss. CVE-2019-14823[0]: | A flaw was found in the "Leaf and Chain" OCSP policy implementation in | JSS' CryptoManager versions after 4.4.6, 4.5.3, 4.6.0, where it | implicitly trusted the root certificate of a certificate chain. | Applications using this policy may not properly verify the chain and | could be vulnerable to attacks such as Man in the Middle. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2019-14823 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14823 [1] https://github.com/dogtagpki/jss/pull/284 [2] https://github.com/dogtagpki/jss/commit/be37ff4738b4696d529a13b6ed33c7ac56d97ba4 Please adjust the affected versions in the BTS as needed. Regards, Salvatore
Bug#942322: marked as done (sudo: CVE-2019-14287: Potential bypass of Runas user restrictions)
Your message dated Wed, 16 Oct 2019 19:50:40 + with message-id and subject line Bug#942322: fixed in sudo 1.8.27-1.1 has caused the Debian Bug report #942322, regarding sudo: CVE-2019-14287: Potential bypass of Runas user restrictions 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.) -- 942322: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942322 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sudo Version: 1.8.27-1 Severity: grave Tags: security upstream Justification: user security hole Control: found -1 1.8.19p1-2.1 Control: fixed -1 1.8.19p1-2.1+deb9u1 Control: fixed -1 1.8.27-1+deb10u1 Hi, The following vulnerability was published for sudo. CVE-2019-14287[0]: Potential bypass of Runas user restrictions If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2019-14287 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14287 [1] https://www.sudo.ws/alerts/minus_1_uid.html Please adjust the affected versions in the BTS as needed. It will be fixed in a DSA for stretch- and buster-security. Regards, Salvatore --- End Message --- --- Begin Message --- Source: sudo Source-Version: 1.8.27-1.1 We believe that the bug you reported is fixed in the latest version of sudo, 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 942...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Salvatore Bonaccorso (supplier of updated sudo package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 14 Oct 2019 21:10:58 +0200 Source: sudo Architecture: source Version: 1.8.27-1.1 Distribution: unstable Urgency: high Maintainer: Bdale Garbee Changed-By: Salvatore Bonaccorso Closes: 942322 Changes: sudo (1.8.27-1.1) unstable; urgency=high . * Non-maintainer upload. * Treat an ID of -1 as invalid since that means "no change" (CVE-2019-14287) (Closes: #942322) * Fix test failure in plugins/sudoers/regress/testsudoers/test5.sh Checksums-Sha1: 7d929c2ac7bedd34a8ed1d60cb7367aef3125f5f 2106 sudo_1.8.27-1.1.dsc 4546c1696e01b9af17f6dd0694d8e58bd81814b2 25672 sudo_1.8.27-1.1.debian.tar.xz Checksums-Sha256: 29541e25ae299b6b2d8ccf0babee15a63b00ff53cba9b061e66bc545962efb53 2106 sudo_1.8.27-1.1.dsc 33ad443bb02db64d7c00cb52148650f94061320ac21870dc8c20c385b055c775 25672 sudo_1.8.27-1.1.debian.tar.xz Files: a794eae33c67379347b2dea93a654891 2106 admin optional sudo_1.8.27-1.1.dsc 000bedfd4cbfa42334be85cc45ed9f00 25672 admin optional sudo_1.8.27-1.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAl2kynpfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2 NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk ZWJpYW4ub3JnAAoJEAVMuPMTQ89EmdEP/jeiSU6L21LWhRSibBIBpayeE8nExp3l 8i5VQL/W+JNOxyBVhL4TKOf5khcSFr1zqUhS7zIYzwF+/Pgo0O67VT3i7O+X51Ig bDz+U0bBkLlXWrmnh4zIRH8XwYdNZJyB483iFcLHAq6xvJLeqql60vecpqu83yEL SyK7Mt9jlwbtPtX8K3n9PY3Dw2sMS1W3IUxrLAb4ves87oFEKvu4+AWogcmEYusE qAm18Fr9zkKdmnYI5mmrbF7Y1fu6ycnMFeXTZRfQFQDvgX5jGddLrTWEpPYsGfe/ yBhZRD28FIeeuSJ1BhXVeKNR4T0upaN+XEIQtQX62SickFUzXCYgQxsifClUw+mT z2XdCgiOcgUiKearsPt1yjciyKWnEeYkG75YCJPU5Nyo3lvkpZwBbZiT7X7RnxK6 16TJR1QniRFz+ZHK2pJpKJFmAqlsSEXgK6yq0rEd+HrWVMuVdpb5IWcLMMvuVBJL nbiphQaSuhVdjnnB1IQnuvn4O2D6zCHyR1hNVfNP+ysde1vEJKbNu5kgY5lo3kRt Mx90yiV/WeRib0ouj4K8PwMBsMH/2SJDNLMO2aKvJm2gOMEmhYG4j4XqlB0pqqPm xXfyjoudMDaB4+Y6jv0DNSctIy/6x8BlPnnCbmJvXyMSn2TnrXr0gwnJpGLzZUuj BgAPljnOfdYG =WDqI -END PGP SIGNATURE End Message ---
Bug#942315: tcpdump: Version in oldoldstable is higher than oldstable and stable
Hi Romain, On Wed, Oct 16, 2019 at 08:30:44PM +0200, Romain Francoise wrote: > Hi Guillem, > > On Mon, Oct 14, 2019 at 3:45 PM Guillem Jover wrote: > > With the latest upload to oldoldstable-security, the versions in > > oldstable and stable are now lower. This means that upgrades will > > not take effect for this package, which will be left built against > > libraries and packaging from oldoldstable. > > Yes, the jessie-lts team kinda jumped the gun here. I think the best > way forward is to request approval for a buster-pu update of tcpdump > to 4.9.3 as well... > > Salvatore, any thoughts? Ideally given the issues are denial of service issues, this would have been okay via a point release. But we discussed this coincidentally in the team concluding we could as well release it via security. But we were thinking of postponing it a bit yet to see if some bug reports/regression reports did appear after the unstable version was exposed. Can you prepare updates for buster-security and stretch-security? If you have preference for the point release road though, we can followup there. Reards, Salvatore
Bug#941432: [pkg-uWSGI-devel] Bug#941432: Bug#941432: Bug#941432: Bug#941432: Bug#941432: Bug#941432: uwsgi-core: Dependency libmatheval is getting out of bullseye
[sent again with ASCII-only header, to not upset Debian mailservers] Quoting Alexandre Rossi (2019-10-16 20:06:46) > > >Do you require some assistance regarding a new upload of uwsgi? I'm > > >eager to dedicate some time to it if you can't do so. :) > > > > I have a patch but I have not been able to test it yet because the py2 > > removal makes the package FTBS... I'm close to fix it though. I'll post an > > update here by wednesday. > > The patch I want to test is here: > https://sml.zincube.net/~niol/repositories.git/uwsgi/commit/?id=5e0246cc5d27ea2ccd29e938ceb24913431da364 > > Unfortunately it does not build (which is not related to the patch): > > plugins/gevent/../python/uwsgi_python.h:2:10: fatal error: Python.h: No > such file or directory > > If I try to remove even more py2, I'm stuck with: > > *** uWSGI building and linking plugin plugins/asyncio_python3 *** > Error: unable to find directory 'plugins/asyncio_python3' > > Which means I've messed up debian/rules because it should try to build > plugins/asyncio and not plugins/asyncio_python3 . I need to find more time > to understand how this works with plugins flavours, stems, etc. I also > did not find yet some kind of cdbs debug mode (like DH_VERBOSE=1). What happened to "It should be as simple as not building the matheval plugin"? Please do *NOT* upload a custom fork of uwsgi-converted-to-Python3!!! If you want to help convert uwsgi to Python3, then please work directly upstream on that. This Debian package should *not* become a fork of the upstream project. - 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#942459: wordpress: WordPress 5.2.4 Security Release
Source: wordpress Version: 5.2.3+dfsg1-1 Severity: grave Tags: security upstream Justification: user security hole Hi Craig, See https://wordpress.org/news/2019/10/wordpress-5-2-4-security-release/ As in previous rounds, could you please requests the CVEs as neededfor the found issues? Regards, Salvatore
Bug#942315: tcpdump: Version in oldoldstable is higher than oldstable and stable
Hello, Am 16.10.19 um 20:30 schrieb Romain Francoise: > Hi Guillem, > > On Mon, Oct 14, 2019 at 3:45 PM Guillem Jover wrote: >> With the latest upload to oldoldstable-security, the versions in >> oldstable and stable are now lower. This means that upgrades will >> not take effect for this package, which will be left built against >> libraries and packaging from oldoldstable. > > Yes, the jessie-lts team kinda jumped the gun here. I think the best > way forward is to request approval for a buster-pu update of tcpdump > to 4.9.3 as well... > > Salvatore, any thoughts? > > Thanks. I was assuming that Romain prepared the updates for stable again, so the corresponding backports will be 4.9.3-1~deb9u1 and 4.9.3-1~deb10u1 respectively exactly as it was done last time with the backport of 4.9.2. Regards, Markus signature.asc Description: OpenPGP digital signature
Bug#942315: tcpdump: Version in oldoldstable is higher than oldstable and stable
Hi Guillem, On Mon, Oct 14, 2019 at 3:45 PM Guillem Jover wrote: > With the latest upload to oldoldstable-security, the versions in > oldstable and stable are now lower. This means that upgrades will > not take effect for this package, which will be left built against > libraries and packaging from oldoldstable. Yes, the jessie-lts team kinda jumped the gun here. I think the best way forward is to request approval for a buster-pu update of tcpdump to 4.9.3 as well... Salvatore, any thoughts? Thanks.
Bug#941890: marked as done (python-clang-7: missing dependency on libclang-7-dev)
Your message dated Wed, 16 Oct 2019 18:09:24 + with message-id and subject line Bug#941890: fixed in llvm-toolchain-9 1:9-3 has caused the Debian Bug report #941890, regarding python-clang-7: missing dependency on libclang-7-dev to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 941890: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941890 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python-clang-7 Version: 1:7.0.1-8 Severity: serious Justification: missing dependency After installing python-clang-7, it is unusable as is: | $ python | ... | >>> import clang.cindex | >>> clang.cindex.Index.create() | Traceback (most recent call last): | File "", line 1, in | File "/usr/lib/python2.7/dist-packages/clang/cindex.py", line 2672, in create | return Index(conf.lib.clang_createIndex(excludeDecls, 0)) | File "/usr/lib/python2.7/dist-packages/clang/cindex.py", line 198, in __get__ | value = self.wrapped(instance) | File "/usr/lib/python2.7/dist-packages/clang/cindex.py", line 4115, in lib | lib = self.get_cindex_library() | File "/usr/lib/python2.7/dist-packages/clang/cindex.py", line 4146, in get_cindex_library | raise LibclangError(msg) | clang.cindex.LibclangError: libclang-7.so: cannot open shared object file: No such file or directory. To provide a path to libclang use Config.set_library_path() or Config.set_library_file(). | >>> It fails to find libclang-7.so, which is shipped in libclang-7-dev. After installing that package, creating the index works. Helmut --- End Message --- --- Begin Message --- Source: llvm-toolchain-9 Source-Version: 1:9-3 We believe that the bug you reported is fixed in the latest version of llvm-toolchain-9, 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 941...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sylvestre Ledru (supplier of updated llvm-toolchain-9 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: Mon, 07 Oct 2019 09:47:10 +0200 Source: llvm-toolchain-9 Architecture: source Version: 1:9-3 Distribution: unstable Urgency: medium Maintainer: LLVM Packaging Team Changed-By: Sylvestre Ledru Closes: 941890 Changes: llvm-toolchain-9 (1:9-3) unstable; urgency=medium . * python-clang-9: missing dependency on libclang-9-dev (Closes: #941890) * Enable Z3 solver (llvm & clang) to improve the quality of the static analysis results * Do not fail the test suite on the -lclang-cpp failing I think I need to create a libclang-cpp-dev package to unblock it (but dunno why it works locally) Checksums-Sha1: cbde26a91b5e4518c395275785e6196fd37afbae 8593 llvm-toolchain-9_9-3.dsc 54f8fe9ca6104f189d52a1ad6ef60b3603b80016 110480 llvm-toolchain-9_9-3.debian.tar.xz 59372f737aab8975df533a4568a06408bba314aa 25106 llvm-toolchain-9_9-3_amd64.buildinfo Checksums-Sha256: 1ff9487bf4e186defa1a029c9581377e71faebe0d49da1125b09c0e7ef7c47c0 8593 llvm-toolchain-9_9-3.dsc 76c061a79993ad31a8de6b8007bc10fe941a5986394d44e338e4029f106d1a95 110480 llvm-toolchain-9_9-3.debian.tar.xz a65b8c2d333bdbbd411594ae97b2e8202c5946eb8f1c934faf157cc2a9814d7c 25106 llvm-toolchain-9_9-3_amd64.buildinfo Files: 04905bd3efc336eeac130d234dd4a0df 8593 devel optional llvm-toolchain-9_9-3.dsc f416269ed9c6788c1389fc2174013790 110480 devel optional llvm-toolchain-9_9-3.debian.tar.xz f9f9a0846a10080a7c462da4fd2ab716 25106 devel optional llvm-toolchain-9_9-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEtg21mU05vsTRqVzPfmUo2nUvG+EFAl2nV0UACgkQfmUo2nUv G+Hffw/7B1v8S4ViZgjxMjc9sIzmNVRG2yFrgpp5JpNQHDe/sc1wPcb8aJM+a9OF 7Z/FmvX/ejIP6874AIitWFkm11xZnkmFP/kOMmWMq+kZjxHAoAhz2tmpvVXTVN/4 HGZNvO+v18Tcn/EC+XjM4ec55uQt0EZwzoxZVZiqByFPq8ydLZwULV1XnQCIbchH eThK63fqci8A0Izc4+rEdcP1GVEwvTUOAKahRPrrUKnRKv0yFI32li6pyJlDJWUh 1T7IsjwhQt10BqStDQN1c8iMI3EXorZhBe0X69C7BWHRkIvR8wWWZOfHwZ6vyZy9 VrnVTVvVInTHChOYe24em4WsEisRMzzW/KVAvNJrQ9KhMaxd0qEYwORJKiG9xLE3 gKkkRtchsRAAL7cCN0F/vFqcyd3TCB+RtiotKyVCxQn8UjjlLi5/9RQOeJ+RLLvz P2e2rst6GwePN65ThrP1dc+dDvtynn4fNiOwjtmkkH8utAGC3xT0xtdBAkJOsyMg WiwUP4wrQfo26K0YJg2tzajV9hU6HT+N7PsnRy8ZhR1iZlDMiul
Bug#941432: [pkg-uWSGI-devel] Bug#941432: Bug#941432: Bug#941432: Bug#941432: Bug#941432: Bug#941432: uwsgi-core: Dependency libmatheval is getting out of bullseye
Hi, > >Do you require some assistance regarding a new upload of uwsgi? I'm > >eager to dedicate some time to it if you can't do so. :) > > I have a patch but I have not been able to test it yet because the py2 > removal makes the package FTBS... I'm close to fix it though. I'll post an > update here by wednesday. The patch I want to test is here: https://sml.zincube.net/~niol/repositories.git/uwsgi/commit/?id=5e0246cc5d27ea2ccd29e938ceb24913431da364 Unfortunately it does not build (which is not related to the patch): plugins/gevent/../python/uwsgi_python.h:2:10: fatal error: Python.h: No such file or directory If I try to remove even more py2, I'm stuck with: *** uWSGI building and linking plugin plugins/asyncio_python3 *** Error: unable to find directory 'plugins/asyncio_python3' Which means I've messed up debian/rules because it should try to build plugins/asyncio and not plugins/asyncio_python3 . I need to find more time to understand how this works with plugins flavours, stems, etc. I also did not find yet some kind of cdbs debug mode (like DH_VERBOSE=1). Thanks, Alex
Bug#934491: libelogind0: failing to switch from systemd to sysvinit-core/elogind results in libsystemd.so.0 disappearing
Simon, On Tue, Aug 27, 2019 at 05:46:32PM +0100, Mark Hindley wrote: > Simon, > > I think I have finally got to the bottom of this. As you suspected it is apt's > invocation of dpkg. See #935910. This is now resolved in apt version 1.8.4 which is in both sid and bullseye. I can no longer reproduce the breakage that you reported. Are you satisfied that this bug can be closed? Thanks. Mark
Bug#942418: libmutter-5-0: Blank screen after upgrading to bullseye, caused by failing wayland
Hi, I can reproduce this issue: Oct 16 18:00:46 localhost gnome-session[1169]: gnome-session-binary[1169]: WARNING: Falling back to non-systemd startup procedure due to error: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.systemd1 was not provided by any .service files Oct 16 18:00:46 localhost org.gnome.Shell.desktop[1177]: pci id for fd 11: 80ee:beef, driver (null) *Oct 16 18:00:47 localhost gnome-shell[1177]: Failed to initialize accelerated iGPU/dGPU framebuffer sharing: Do not want to use software renderer (llvmpipe (LLVM 9.0, 256 bits)), falling back to CPU copy pathOct 16 18:00:48 localhost org.gnome.Shell.desktop[1177]: can't load /usr/lib/x86_64-linux-gnu/spa/support/libspa-support.so: /usr/lib/x86_64-linux-gnu/spa/support/libspa-support.so: cannot open shared object file: No such file or directoryOct 16 18:00:48 localhost org.gnome.Shell.desktop[1177]: glamor: 'wl_drm' not supportedOct 16 18:00:48 localhost org.gnome.Shell.desktop[1177]: Missing Wayland requirements for glamor GBM backendOct 16 18:00:48 localhost org.gnome.Shell.desktop[1177]: Failed to initialize glamor, falling back to sw* Oct 16 18:00:48 localhost /usr/lib/gdm3/gdm-wayland-session[1165]: dbus-daemon[1167]: [session uid=117 pid=1167] Activating service name='org.a11y.Bus' requested by ':1.3' (uid=117 pid=1177 comm="/usr/bin/gnome-shell ") Oct 16 18:00:48 localhost /usr/lib/gdm3/gdm-wayland-session[1165]: dbus-daemon[1167]: [session uid=117 pid=1167] Successfully activated service 'org.a11y.Bus' Oct 16 18:00:49 localhost gnome-shell[1177]: Failed to launch ibus-daemon: Failed to execute child process “ibus-daemon” (No such file or directory) Oct 16 18:00:49 localhost /usr/lib/gdm3/gdm-wayland-session[1165]: dbus-daemon[1167]: [session uid=117 pid=1167] Activating service name='org.freedesktop.impl.portal.PermissionStore' requested by ':1.2' (uid=117 pid=1177 comm="/usr/bin/gnome-shell ") Oct 16 18:00:49 localhost /usr/lib/gdm3/gdm-wayland-session[1165]: dbus-daemon[1167]: [session uid=117 pid=1167] Successfully activated service 'org.freedesktop.impl.portal.PermissionStore' Oct 16 18:00:50 localhost gnome-shell[1177]: Failed to launch ibus-daemon: Failed to execute child process “ibus-daemon” (No such file or directory) Oct 16 18:00:50 localhost gnome-shell[1177]: Failed to get PolKit permission: Polkit.Error: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Action org.freedesktop.bolt.enroll is not registered Oct 16 18:00:50 localhost gnome-shell[1177]: Getting invalid resource scale property Oct 16 18:00:50 localhost gnome-shell[1177]: Could not issue 'StartUnit' systemd call Oct 16 18:00:50 localhost gnome-shell[1177]: Error checking authorization for action id org.freedesktop.bolt.enroll: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Action org.freedesktop.bolt.enroll is not registered Oct 16 18:00:50 localhost gnome-shell[1177]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation gdm shows a grey screen with mouse. thanks, regards, Pedro
Bug#942456: python-flask-marshmallow - Incomplete debian/copyright
Source: python-flask-marshmallow Version: 0.10.1-1 Severity: serious Justication: Policy §12.5 X-Debbugs-CC: ftpmas...@debian.org, guptautkarsh2...@gmail.com, python-modules-t...@lists.alioth.debian.org I just accepted python-flask-marshmallow from NEW. docs/_themes/flask/static/flasky.css_t lists as license: | * :copyright: Copyright 2010 by Armin Ronacher. | * :license: Flask Design License, see LICENSE for details. This license is not listed in debian/copyright. Bastian -- Death, when unnecessary, is a tragic thing. -- Flint, "Requiem for Methuselah", stardate 5843.7
Bug#935562: marked as done (Missing dependency on 'google-auth-httplib2>=0.0.3')
Your message dated Wed, 16 Oct 2019 17:06:09 + with message-id and subject line Bug#935562: fixed in python-googleapi 1.7.11-3 has caused the Debian Bug report #935562, regarding Missing dependency on 'google-auth-httplib2>=0.0.3' 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.) -- 935562: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935562 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: goobook Version: 3.3-1 Severity: grave Justification: renders package unusable Dear Maintainer, Running goobook results in a traceback: Traceback (most recent call last): File "/usr/bin/goobook", line 6, in from pkg_resources import load_entry_point File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3250, in @_call_aside File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3234, in _call_aside f(*args, **kwargs) File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3263, in _initialize_master_working_set working_set = WorkingSet._build_master() File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 583, in _build_master ws.require(__requires__) File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 900, in require needed = self.resolve(parse_requirements(requirements)) File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 786, in resolve raise DistributionNotFound(req, requirers) pkg_resources.DistributionNotFound: The 'google-auth-httplib2>=0.0.3' distribution was not found and is required by google-api-python-client -- The correct dependencies are installed, and it seems like the versions are correct, so I'm not sure why the exception is being raised. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.2.0-2-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_USER, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to C.UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to C.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages goobook depends on: ii python3 3.7.3-1 ii python3-googleapi 1.7.11-2 ii python3-oauth2client 4.1.2-4 ii python3-simplejson3.16.0-2 goobook recommends no packages. goobook suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: python-googleapi Source-Version: 1.7.11-3 We believe that the bug you reported is fixed in the latest version of python-googleapi, 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 935...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Laszlo Boszormenyi (GCS) (supplier of updated python-googleapi 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: Wed, 16 Oct 2019 16:13:14 + Source: python-googleapi Architecture: source Version: 1.7.11-3 Distribution: unstable Urgency: medium Maintainer: Laszlo Boszormenyi (GCS) Changed-By: Laszlo Boszormenyi (GCS) Closes: 935562 Changes: python-googleapi (1.7.11-3) unstable; urgency=medium . * Add google-auth-httplib2 dependency (closes: #935562). Checksums-Sha1: d910b26f7dedc4bdb2ccffba5164eba6fec42426 2111 python-googleapi_1.7.11-3.dsc d4da878ee62e4b7b3f32732e423146b43ed78267 3692 python-googleapi_1.7.11-3.debian.tar.xz Checksums-Sha256: f7071fa56f1533fda4bf34d757ab7cdbcdbf97a94fa959b7fa8f9d9cb2e68dbe 2111 python-googleapi_1.7.11-3.dsc 4afbb4b654c3a76bbaa732a530e9d3fdeb32f3b2e9cbb859bf2cc75a7f2b36c9 3692 python-googleapi_1.7.11-3.debian.tar.xz Files: 65d6249ac7c1bd4f07b1d93c47567fcb 2111 python optional python-googleapi_1.7.11-3.dsc d4de868ae6265edf0572a7aeb9211d9f 3692 python optional python-googleapi_1.7.11-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEfYh9yLp7u6e4NeO63OMQ54ZMyL8FAl2nS0gACgkQ3OMQ54ZM yL92DQ/+JhIFXer0rGd8uD/SPZh
Bug#942279: marked as done (golang-github-hashicorp-go-retryablehttp breaks golang-github-circonus-labs-circonus-gometrics autopkgtest)
Your message dated Wed, 16 Oct 2019 16:34:54 + with message-id and subject line Bug#942279: fixed in golang-github-circonus-labs-circonus-gometrics 2.3.1-1 has caused the Debian Bug report #942279, regarding golang-github-hashicorp-go-retryablehttp breaks golang-github-circonus-labs-circonus-gometrics autopkgtest 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.) -- 942279: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942279 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: golang-github-hashicorp-go-retryablehttp, golang-github-circonus-labs-circonus-gometrics Control: found -1 golang-github-hashicorp-go-retryablehttp/0.6.2-1 Control: found -1 golang-github-circonus-labs-circonus-gometrics/2.0.0-1 Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainers, With a recent upload of golang-github-hashicorp-go-retryablehttp the autopkgtest of golang-github-circonus-labs-circonus-gometrics fails in testing when that autopkgtest is run with the binary packages of golang-github-hashicorp-go-retryablehttp from unstable. It passes when run with only packages from testing. In tabular form: pass fail golang-github-hashicorp-go-retryablehttpfrom testing 0.6.2-1 golang-github-circonus-labs-circonus-gometrics from testing 2.0.0-1 all others from testing from testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of golang-github-hashicorp-go-retryablehttp to testing [1]. Due to the nature of this issue, I filed this bug report against both packages. Can you please investigate the situation and reassign the bug to the right package? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=golang-github-hashicorp-go-retryablehttp https://ci.debian.net/data/autopkgtest/testing/amd64/g/golang-github-circonus-labs-circonus-gometrics/3160364/log.gz # github.com/circonus-labs/circonus-gometrics src/github.com/circonus-labs/circonus-gometrics/submit.go:133:24: cannot use func literal (type func(*log.Logger, *http.Request, int)) as type retryablehttp.RequestLogHook in assignment dh_auto_build: cd obj-x86_64-linux-gnu && go install -gcflags=all=\"-trimpath=/tmp/autopkgtest-lxc.ikh1z671/downtmp/autopkgtest_tmp/obj-x86_64-linux-gnu/src\" -asmflags=all=\"-trimpath=/tmp/autopkgtest-lxc.ikh1z671/downtmp/autopkgtest_tmp/obj-x86_64-linux-gnu/src\" -v -p 2 github.com/circonus-labs/circonus-gometrics github.com/circonus-labs/circonus-gometrics/api github.com/circonus-labs/circonus-gometrics/api/config github.com/circonus-labs/circonus-gometrics/checkmgr returned exit code 2 make: *** [debian/rules:4: build] Error 255 signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: golang-github-circonus-labs-circonus-gometrics Source-Version: 2.3.1-1 We believe that the bug you reported is fixed in the latest version of golang-github-circonus-labs-circonus-gometrics, 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 942...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dmitry Smirnov (supplier of updated golang-github-circonus-labs-circonus-gometrics 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, 17 Oct 2019 03:12:05 +1100 Source: golang-github-circonus-labs-circonus-gometrics Architecture: source Version: 2.3.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Go Packaging Team Changed-By: Dmitry Smirnov Closes: 942279 Changes: golang-github-circonus-labs-circonus-gometrics (2.3.1-1) unstable; urgency=medium . * New upstream release (Closes: #942279). * Standards-Version: 4.4.1. * DH & compat to version 12. * (Build-)Depends: + golang-github-tv42-httpunix-dev = golang-github-hashicorp-go-retryablehttp-dev (>= 0.6.2
Bug#942279: [pkg-go] Bug#942279: golang-github-hashicorp-go-retryablehttp breaks golang-github-circonus-labs-circonus-gometrics autopkgtest
On Monday, 14 October 2019 6:40:17 AM AEDT Paul Gevers wrote: > With a recent upload of golang-github-hashicorp-go-retryablehttp the > autopkgtest of golang-github-circonus-labs-circonus-gometrics fails in > testing when that autopkgtest is run with the binary packages of > golang-github-hashicorp-go-retryablehttp from unstable. It passes when > run with only packages from testing. In tabular form: > pass fail > golang-github-hashicorp-go-retryablehttpfrom testing 0.6.2-1 > golang-github-circonus-labs-circonus-gometrics from testing 2.0.0-1 Thanks. Sometimes I wish we could postpone that kind of bug reports as they are unavoidable during transitions. I've noticed the problem when "golang-github-hashicorp-go-retryablehttp" did not migrate and I had changes ready for upload but held by pending NEW package. Fix is already on its way. -- All the best, Dmitry Smirnov --- In a war of ideas it is people who get killed. -- Stanisław Jerzy Lec signature.asc Description: This is a digitally signed message part.
Processed: tagging 942279
Processing commands for cont...@bugs.debian.org: > tags 942279 + pending Bug #942279 [src:golang-github-hashicorp-go-retryablehttp, src:golang-github-circonus-labs-circonus-gometrics] golang-github-hashicorp-go-retryablehttp breaks golang-github-circonus-labs-circonus-gometrics autopkgtest Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 942279: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942279 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: notfound 942279 in golang-github-hashicorp-go-retryablehttp/0.6.2-1
Processing commands for cont...@bugs.debian.org: > notfound 942279 golang-github-hashicorp-go-retryablehttp/0.6.2-1 Bug #942279 [src:golang-github-hashicorp-go-retryablehttp, src:golang-github-circonus-labs-circonus-gometrics] golang-github-hashicorp-go-retryablehttp breaks golang-github-circonus-labs-circonus-gometrics autopkgtest No longer marked as found in versions golang-github-hashicorp-go-retryablehttp/0.6.2-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 942279: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942279 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: found 942279 in golang-github-circonus-labs-circonus-gometrics/2.0.0-1
Processing commands for cont...@bugs.debian.org: > found 942279 golang-github-circonus-labs-circonus-gometrics/2.0.0-1 Bug #942279 [src:golang-github-hashicorp-go-retryablehttp, src:golang-github-circonus-labs-circonus-gometrics] golang-github-hashicorp-go-retryablehttp breaks golang-github-circonus-labs-circonus-gometrics autopkgtest Marked as found in versions golang-github-circonus-labs-circonus-gometrics/2.0.0-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 942279: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942279 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: notfound 942279 in golang-github-circonus-labs-circonus-gometrics/2.0.0-1
Processing commands for cont...@bugs.debian.org: > notfound 942279 golang-github-circonus-labs-circonus-gometrics/2.0.0-1 Bug #942279 [src:golang-github-hashicorp-go-retryablehttp, src:golang-github-circonus-labs-circonus-gometrics] golang-github-hashicorp-go-retryablehttp breaks golang-github-circonus-labs-circonus-gometrics autopkgtest No longer marked as found in versions golang-github-circonus-labs-circonus-gometrics/2.0.0-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 942279: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942279 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: mark pending
Processing commands for cont...@bugs.debian.org: > tags 934716 + fixed pending Bug #934716 [src:cross-toolchain-base-mipsen] binutils patch applied, package now ftbfs Added tag(s) fixed and pending. > tags 941057 + fixed pending Bug #941057 [src:cross-toolchain-base-mipsen] c-t-b-mipsen tries to build targets which are not configured for this package Added tag(s) pending and fixed. > thanks Stopping processing here. Please contact me if you need assistance. -- 934716: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934716 941057: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941057 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#935752: marked as done (gcc-9-cross-mipsen: FTBFS (/usr/bin/python: bad interpreter: No such file or directory))
Your message dated Wed, 16 Oct 2019 22:53:54 +0800 with message-id and subject line Re: gcc-9-cross-mipsen: FTBFS (/usr/bin/python: bad interpreter: No such file or directory) has caused the Debian Bug report #935752, regarding gcc-9-cross-mipsen: FTBFS (/usr/bin/python: bad interpreter: No such file or directory) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 935752: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935752 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:gcc-9-cross-mipsen Version: 1+c1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in sid but it failed: [...] debian/rules build-indep gcc: 9.2.1-3 / 9.1.0-10cross1 old gcc version: 9.1.0-10 / 1 new gcc version: 9.2.1-3cross1 START stamp-dir/init-gcc mkdir -p gcc set -ex; \ cd gcc ; \ ln -sf /usr/src/gcc-9/gcc-9.2.0-dfsg.tar.xz gcc-9.2.0-dfsg.tar.xz ;\ cp -a /usr/src/gcc-9/debian/ . ; \ if [ -n "$(grep -v '^\#' /<>/debian/patches/gcc-9/series)" ]; then \ QUILT_PATCHES=/<>/debian/patches/gcc-9 quilt push --quiltrc /dev/null -a ; \ fi [ ... ] if [ xinfo = xinfo ]; then \ rm -f doc/gfc-internals.info-*; \ makeinfo --split-size=500 --split-size=500 -I ../../src/gcc/doc/include -I ../../src/gcc/fortran \ -o doc/gfc-internals.info ../../src/gcc/fortran/gfc-internals.texi; \ else true; fi ../../src/gcc/fortran/gfc-internals.texi: warning: document without nodes mkdir -p gm2/images if [ -f ../../src/gcc/gm2/images/gnu.eps ] ; then \ cp ../../src/gcc/gm2/images/gnu.eps /<>/gcc/build/gcc/gm2/images/gnu.eps ; \ else \ pngtopnm ../../src/gcc/gm2/images/gnupng | pnmtops -noturn > /<>/gcc/build/gcc/gm2/images/gnu.eps ; \ fi bash ../../src/gcc/gm2/tools-src/makeSystem -fpim \ ../../src/gcc/gm2/gm2-libs/SYSTEM.def \ ../../src/gcc/gm2/gm2-libs/SYSTEM.mod \ -I../../src/gcc/gm2/gm2-libs \ "/<>/gcc/build/./gcc/xgm2 -B/<>/gcc/build/./gcc/" /<>/gcc/build/gcc/gm2/gm2-libs/SYSTEM.def ../../src/gcc/gm2/tools-src/def2texi.py -b/<>/gcc/build/gcc/gm2 -f/<>/gcc/build/gcc/gm2/gm2-libs/SYSTEM.def > /<>/gcc/build/gcc/gm2/SYSTEM-pim.texi /bin/bash: ../../src/gcc/gm2/tools-src/def2texi.py: /usr/bin/python: bad interpreter: No such file or directory make[5]: *** [../../src/gcc/gm2/Make-lang.in:247: gm2/SYSTEM-pim.texi] Error 126 make[5]: Leaving directory '/<>/gcc/build/gcc' make[4]: *** [Makefile:4368: all-gcc] Error 2 make[4]: Leaving directory '/<>/gcc/build' make[3]: *** [Makefile:970: all] Error 2 make[3]: Leaving directory '/<>/gcc/build' T Thu, 22 Aug 2019 13:25:38 + [ ... ] make[2]: *** [debian/rules2:1230: stamps/05-build-stamp] Error 1 make[2]: Leaving directory '/<>/gcc' make[1]: *** [debian/rules:40: build] Error 2 make[1]: Leaving directory '/<>/gcc' dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 make: *** [debian/rules:410: stamp-dir/build-gcc.mips64] Error 2 dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit status 2 The build was made in my autobuilder with "dpkg-buildpackage -A". I guess it will happen 100% of the time when built in a clean chroot. 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 --- On Sun, 25 Aug 2019 20:33:56 + Santiago Vila wrote: > Package: src:gcc-9-cross-mipsen > Version: 1+c1 > Severity: serious > Tags: ftbfs This bug has been fixed by version 2+c1 > > Dear maintainer: > > I tried to build this package in sid but it failed: > > > [...] > debian/rules build-indep > gcc: 9.2.1-3 / 9.1.0-10cross1 > > old gcc version: 9.1.0-10 / 1 > > new gcc version: 9.2.1-3cross1 > START stamp-dir/init-gcc > mkdir -p gcc > set -ex; \ > cd gcc ; \ > ln -sf /usr/src/gcc-9/gcc-9.2.0-dfsg.tar.xz gcc-9.2.0-dfsg.tar.xz ;\ > cp -a /usr/src/gcc-9/debian/ . ; \ > if [ -n "$(grep -v '^\#' /<>/debian/patches/gcc-9/series)" ]; > then \ > QUILT_PATCHES=/<>/debian/patches/gcc-9 quilt push --quiltrc > /dev/null -a ; \ > fi > > [ ... ] > > if [ xinfo = xinfo ]; then \ > rm -f doc/gfc-internals.info-*; \ > makeinfo --split-size=500 --split-size=500 -I > ../../src/gcc/doc/include -I ../../src/gc
Processed: tagging 942442
Processing commands for cont...@bugs.debian.org: > tags 942442 + ftbfs Bug #942442 [src:gcc-9] libgnatvsn ftbfs in 9.2.1-10 Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 942442: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942442 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#942364: [patch] perl6-* (vendored) packages out of the reach of perl6 path
On Wed, 16 Oct 2019 04:19:58 -0700, Mo Zhou wrote: > 2019.07.1-7 in experimental should be able to address all the remaining > issues. If the upgrading process didn't automatically trigger the > reinstallation of vendored modules (fixed in master branch), the manual > invokation of rakudo-helper.pl -R should be able to address the > problems. Sounds good. > Could you please verify it? :-) I'm probably not in the best position to test, as I've "transitioned" the directories yesterday already and the modules manually. But upgrading to -7 looks good: Setting up rakudo (2019.07.1-7) ... rakudo-helper.pl: Reinstalling all perl6 modules ... (1/3) reinstall: perl6-readline (2/3) reinstall: perl6-zef (3/3) reinstall: perl6-tap-harness and I see no errors when running `zef' or `perl6 -MReadline'. Ideally someone would try to update directly from -4 in unstable to -7 … Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- signature.asc Description: Digital Signature
Bug#938962: [PATCH] um: Add back support for extra userspace libraries
PCAP and VDE network transports require linking with userspace
libraries. The current build system has no means of passing these
as arguments.
This patch adds a script to expand the library list for linking
for these transports as well as any future driver that needs to
rely on additional libraries on the userspace side.
Signed-off-by: Anton Ivanov
---
arch/um/scripts/extra-libs.sh | 10 ++
scripts/link-vmlinux.sh | 4 +++-
2 files changed, 13 insertions(+), 1 deletion(-)
create mode 100644 arch/um/scripts/extra-libs.sh
diff --git a/arch/um/scripts/extra-libs.sh b/arch/um/scripts/extra-libs.sh
new file mode 100644
index ..0592485e0675
--- /dev/null
+++ b/arch/um/scripts/extra-libs.sh
@@ -0,0 +1,10 @@
+#!/bin/sh
+
+# This file should be included from link-vmlinux, not executed!!!
+
+if [ "${CONFIG_UML_NET_VDE}" = "y" ] ; then
+ UML_EXTRA_LIBS="$UML_EXTRA_LIBS -lvde -lvdeplug"
+fi
+if [ "${CONFIG_UML_NET_PCAP}" = "y" ] ; then
+ UML_EXTRA_LIBS="$UML_EXTRA_LIBS -lpcap"
+fi
diff --git a/scripts/link-vmlinux.sh b/scripts/link-vmlinux.sh
index 06495379fcd8..15f9e5096da0 100755
--- a/scripts/link-vmlinux.sh
+++ b/scripts/link-vmlinux.sh
@@ -90,11 +90,13 @@ vmlinux_link()
-Wl,--end-group \
${@}"
+ . arch/um/scripts/extra-libs.sh
+
${CC} ${CFLAGS_vmlinux} \
-o ${output}\
-Wl,-T,${lds} \
${objects} \
- -lutil -lrt -lpthread
+ -lutil -lrt -lpthread ${UML_EXTRA_LIBS}
rm -f linux
fi
}
--
2.20.1
Bug#942443: mysql-5.7: Security fixes from the October 2019 CPU
Source: mysql-5.7 Version: 5.7.26-1 Severity: grave Tags: security upstream Justification: user security hole Hi See https://www.oracle.com/technetwork/security-advisory/cpuoct2019-5072832.html#AppendixMSQL for a list of CVEs affecting src:mysql-5.7. Regards, Salvatore
Bug#942442: libgnatvsn ftbfs in 9.2.1-10
Package: src:gcc-9 Version: 9.2.1-10 Severity: serious Tags: sid bullseye libgnatvsn ftbfs in 9.2.1-10 [...] make[5]: *** No rule to make target 'alloc.lo', needed by 'libgnatvsn.la'. Stop. make[5]: *** Waiting for unfinished jobs
Bug#942364: [patch] perl6-* (vendored) packages out of the reach of perl6 path
Hi 2019.07.1-7 in experimental should be able to address all the remaining issues. If the upgrading process didn't automatically trigger the reinstallation of vendored modules (fixed in master branch), the manual invokation of rakudo-helper.pl -R should be able to address the problems. Could you please verify it? :-) On 2019-10-15 16:44, gregor herrmann wrote: > On Tue, 15 Oct 2019 02:17:24 -0700, Mo Zhou wrote: > >> Could you please double check the -6 revision? If it looks good, >> I'll continue and upload it to unstable and close this bug. > > After upgrading rakudo from 2019.07.1-4 to 2019.07.1-6: > > % zef > ===SORRY!=== > Could not find Zef::CLI at line 3 in: > inst#/home/gregoa/.perl6 > inst#/usr/share/perl6/site > inst#/usr/share/perl6/vendor > inst#/usr/share/perl6/core > ap# > nqp# > perl5# > > (i.e. same as before) > > /usr/lib/perl6 doesn't exist anymore; /usr/share/perl6 has lots of > stuff with zef: > > /usr/share/perl6/debian-sources/perl6-zef > /usr/share/perl6/debian-sources/perl6-zef/resources > /usr/share/perl6/debian-sources/perl6-zef/resources/scripts > /usr/share/perl6/debian-sources/perl6-zef/resources/scripts/perl5tar.pl > /usr/share/perl6/debian-sources/perl6-zef/resources/scripts/win32http.ps1 > /usr/share/perl6/debian-sources/perl6-zef/resources/scripts/win32unzip.ps1 > /usr/share/perl6/debian-sources/perl6-zef/resources/config.json > /usr/share/perl6/debian-sources/perl6-zef/lib > /usr/share/perl6/debian-sources/perl6-zef/lib/Zef > /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Extract.pm6 > /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Repository > /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Repository/LocalCache.pm6 > /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Repository/Ecosystems.pm6 > /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Repository/MetaCPAN.pm6 > /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Utils > /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Utils/URI.pm6 > /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Utils/FileSystem.pm6 > /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Utils/SystemInfo.pm6 > /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Utils/SystemQuery.pm6 > /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Config.pm6 > /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Repository.pm6 > /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Install.pm6 > /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Fetch.pm6 > /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/CLI.pm6 > /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Client.pm6 > /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Report.pm6 > /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Service > /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Service/InstallPM6.pm6 > /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Service/P6CReporter.pm6 > /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Service/FetchPath.pm6 > /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Service/Shell > /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Service/Shell/git.pm6 > /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Service/Shell/prove.pm6 > /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Service/Shell/PowerShell > /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Service/Shell/PowerShell/download.pm6 > /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Service/Shell/PowerShell/unzip.pm6 > /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Service/Shell/LegacyBuild.pm6 > /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Service/Shell/curl.pm6 > /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Service/Shell/tar.pm6 > /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Service/Shell/p5tar.pm6 > /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Service/Shell/PowerShell.pm6 > /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Service/Shell/wget.pm6 > /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Service/Shell/DistributionBuilder.pm6 > /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Service/Shell/unzip.pm6 > /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Service/Shell/Test.pm6 > /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Service/TAP.pm6 > /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Distribution > /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Distribution/DependencySpecification.pm6 > /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Distribution/Local.pm6 > /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Identity.pm6 > /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Test.pm6 > /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Build.pm6 > /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Distribution.pm6 > /usr/share/perl6/debian-sources/perl6-zef/lib/Zef.pm6 > /usr/share/perl6/debian-sources/perl6-zef/lib/.precomp > /usr/share/perl6/debian-sources/perl6-zef/lib/.precomp/.lock > /usr/share/perl6/debian-sources/perl6-zef/lib/.precomp/1994AC47AA915F09C497C113636DA8687C32F278 > /usr/share/perl6/debian-sources/perl6-zef/
Bug#942404: discosnp: flaky autopkgtest: discoRes_k_31_c_auto_D_100_P_1_b_0_coherent.fa: No such file or directory
Just did a test on sid up-to-date, and tests were fine. Will be difficult to forward upstream with bug occuring "sometimes" and not really reproducible. On 10/15/19 9:35 PM, Paul Gevers wrote: > Source: discosnp > Version: 2.3.0-2 > Severity: serious > Tags: sid bullseye > X-Debbugs-CC: debian...@lists.debian.org > User: debian...@lists.debian.org > Usertags: flaky > > Dear maintainer(s), > > With a recent upload of python-defaults to unstable, the autopkgtest of > discosnp failed in testing when that autopkgtest was run with the binary > packages of python-defaults from unstable. However, as we check for > regression, the reference was retried and failed as well, without > further changes. I looked into the history of your autopkgtest and it > fails very often. > > Because the unstable-to-testing migration software now blocks on > regressions in testing, flaky tests, i.e. tests that flip between > passing and failing without changes to the list of installed packages, > are causing people unrelated to your package to spend time on these > tests. Please either fix the test to be more robust, or or use the > "flaky" restriction for the offending test until a solution has been found. > > I copied the output at the bottom of this report. All the failing tests > that I inspected look like it. > > I'll have the migration software ignore the results of your autopkgtest > until this bug is fixed. > > Paul > > https://ci.debian.net/data/autopkgtest/unstable/amd64/d/discosnp/3153055/log.gz > > autopkgtest [08:02:13]: test run-unit-test: [--- > use read set: fof.txt > Running discoSnp++ 2.3.X, in directory /usr with following parameters: >read_sets=fof.txt >prefix=discoRes_k_31_c_auto >c=auto >C=2147483647 >k=31 >b=0 >d=1 >D=100 >starting date=Mon Oct 14 08:02:14 UTC 2019 > > > GRAPH CREATION ### > > /usr/bin/dbgh5 -in > fof.txt_discoRes_k_31_c_auto_D_100_P_1_b_0_removemeplease -out > discoRes_k_31_c_auto -kmer-size 31 -abundance-min auto -abundance-max > 2147483647 -solidity-kind one -verbose 1 -skip-bcalm -skip-bglue -no-mphf > > [DSK: counting kmers ] 0% elapsed: 0 min 0 > sec remaining: 0 min 0 sec cpu: -1.0 % mem: [ 14, 14, > 36] MB > [DSK: Pass 1/1, Step 1: partitioning ] 0% elapsed: 0 min 0 > sec remaining: 0 min 0 sec cpu: -1.0 % mem: [ 46, 46, > 46] MB > EXCEPTION: Pool allocation failed for 128 bytes (kmers alloc), > mainbuffer is null?. Current usage is 144 and capacity is 5242881056 > Pool allocation failed for 1288 bytes (kmers alloc), mainbuffer is > null?. Current usage is 1448 and capacity is 5242881056 > > there was a problem with graph construction > diff: discoRes_k_31_c_auto_D_100_P_1_b_0_coherent.fa: No such file or > directory > *** Test: FAILURE on diff .fa > autopkgtest [08:02:15]: test run-unit-test: ---] > > > ___ > Debian-med-packaging mailing list > debian-med-packag...@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-med-packaging -- Olivier Sallou Univ Rennes, Inria, CNRS, IRISA Irisa, Campus de Beaulieu F-35042 RENNES - FRANCE Tel: 02.99.84.71.95 gpg key id: 4096R/326D8438 (keyring.debian.org) Key fingerprint = 5FB4 6F83 D3B9 5204 6335 D26D 78DC 68DB 326D 8438 signature.asc Description: OpenPGP digital signature
Processed: tagging 942270
Processing commands for cont...@bugs.debian.org: > tags 942270 + pending confirmed Bug #942270 [src:tasksel] task-spanish depends on removed manpages-es Added tag(s) pending and confirmed. > thanks Stopping processing here. Please contact me if you need assistance. -- 942270: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942270 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: libmutter-5-0: Blank screen after upgrading to bullseye, caused by failing wayland
Processing commands for cont...@bugs.debian.org: > found 942418 3.34.0-4 Bug #942418 [libmutter-5-0] libmutter-5-0: Blank screen after upgrading to bullseye, caused by failing wayland Marked as found in versions mutter/3.34.0-4. > End of message, stopping processing here. Please contact me if you need assistance. -- 942418: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942418 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: found 942165 in 2.1.6-1, found 942165 in 2.3.10.2-1
Processing commands for cont...@bugs.debian.org:
> found 942165 2.1.6-1
Bug #942165 {Done: Moritz Schlarb }
[libapache2-mod-auth-openidc] CVE-2019-14857
Marked as found in versions libapache2-mod-auth-openidc/2.1.6-1.
> found 942165 2.3.10.2-1
Bug #942165 {Done: Moritz Schlarb }
[libapache2-mod-auth-openidc] CVE-2019-14857
Marked as found in versions libapache2-mod-auth-openidc/2.3.10.2-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
942165: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942165
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#940463: marked as done (falkon: Falkon crashes and even freezes entire desktop.)
Your message dated Wed, 16 Oct 2019 10:00:15 + with message-id and subject line Bug#940463: fixed in falkon 3.1.0+dfsg1-4 has caused the Debian Bug report #940463, regarding falkon: Falkon crashes and even freezes entire desktop. 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.) -- 940463: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940463 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: falkon Version: 3.0.0-3 Severity: critical Tags: upstream Justification: breaks the whole system Dear Maintainer, After a fresh install, I tried to run Falkon with no success. It crashes on start. Sometimes it actually starts but when it does, If I click the default bookmark, titled Falkon Wiki, it crashes and/or freezes the entire desktop. Falkon actually froze the entire desktop twice. I could't even use a TTY Terminal. -- System Information: Debian Release: 10.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-6-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 /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages falkon depends on: ii libc62.28-10 ii libgcc1 1:8.3.0-6 ii libkf5wallet-bin 5.54.0-1 ii libkf5wallet55.54.0-1 ii libqt5core5a 5.11.3+dfsg1-1 ii libqt5dbus5 5.11.3+dfsg1-1 ii libqt5gui5 5.11.3+dfsg1-1 ii libqt5network5 5.11.3+dfsg1-1 ii libqt5positioning5 5.11.3+dfsg-2 ii libqt5printsupport5 5.11.3+dfsg1-1 ii libqt5qml5 5.11.3-4 ii libqt5quick5 5.11.3-4 ii libqt5quickwidgets5 5.11.3-4 ii libqt5sql5 5.11.3+dfsg1-1 ii libqt5sql5-sqlite5.11.3+dfsg1-1 ii libqt5webchannel55.11.3-2 ii libqt5webenginecore5 5.11.3+dfsg-2+b1 ii libqt5webenginewidgets5 5.11.3+dfsg-2+b1 ii libqt5widgets5 5.11.3+dfsg1-1 ii libqt5x11extras5 5.11.3-2 ii libssl1.11.1.1c-1 ii libstdc++6 8.3.0-6 ii libxcb1 1.13.1-2 falkon recommends no packages. falkon suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: falkon Source-Version: 3.1.0+dfsg1-4 We believe that the bug you reported is fixed in the latest version of falkon, 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 940...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Georges Khaznadar (supplier of updated falkon 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: Tue, 17 Sep 2019 16:28:23 +0200 Source: falkon Binary: falkon falkon-dbgsym falkon-plugin-wallet falkon-plugin-wallet-dbgsym qupzilla qupzilla-plugin-kwallet Architecture: source amd64 Version: 3.1.0+dfsg1-4 Distribution: unstable Urgency: medium Maintainer: Georges Khaznadar Changed-By: Georges Khaznadar Description: falkon - lightweight web browser based on Qt WebEngine falkon-plugin-wallet - adds password management to Falkon qupzilla - transitional package for qupzilla qupzilla-plugin-kwallet - transitional package for qupzilla-plugin-kwallet Closes: 940463 Changes: falkon (3.1.0+dfsg1-4) unstable; urgency=medium . * Checked that falkon-3.1.0+dfsg1-3 does not crash. Closes: #940463 Checksums-Sha1: d31d25188fc0db2004a6ae19c68616541ceb2364 2642 falkon_3.1.0+dfsg1-4.dsc a32dba4d34edc8d3fe5efe3445aab53d7f9b91cd 187868 falkon_3.1.0+dfsg1-4.debian.tar.xz 2769dc49ee42aa75b8db022fc95165c01688487a 48339768 falkon-dbgsym_3.1.0+dfsg1-4_amd64.deb 471fb1c7313bfa4c790a9d677dcae71b09ff0495 570312 falkon-plugin-wallet-dbgsym_3.1.0+dfsg1-4_amd64.deb 7171a9d21a782fbb8fd1021b1c30e63463167a2d 41120 falkon-plugin-wallet_3.1.0+dfsg1-4_amd64.deb 951042af5d5eee33749e12a0a3aa9bb09a3c5b9b 25412 falkon_3.1.0+dfsg1-4_amd64.buildinfo 0e40b10a1f4cccf80491257e13d95c1626b85ed9 2477228 falkon_3.1.0+dfsg1-4_amd64.deb 7352419cd810c483fa6e0b9f39b34c7776f1a7
Bug#942287: marked as done (python3-exif: package name should be python3-exifread)
Your message dated Wed, 16 Oct 2019 10:00:31 + with message-id and subject line Bug#942287: fixed in python-exif 2.2.0-4 has caused the Debian Bug report #942287, regarding python3-exif: package name should be python3-exifread 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.) -- 942287: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942287 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-exif Version: 2.2.0-3 Severity: serious Hello, since this package installs a module called `exifread` the binary package name should be python3-exifread not python3-exif. Since it violates the policy, severity is set to serious. Regards, Sandro -- System Information: Debian Release: 10.0 APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3-exif depends on: ii python3 3.7.3-1 python3-exif recommends no packages. python3-exif suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: python-exif Source-Version: 2.2.0-4 We believe that the bug you reported is fixed in the latest version of python-exif, 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 942...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. TANIGUCHI Takaki (supplier of updated python-exif 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: Mon, 14 Oct 2019 23:50:34 +0900 Source: python-exif Binary: python3-exif python3-exifread Architecture: source all Version: 2.2.0-4 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team Changed-By: TANIGUCHI Takaki Description: python3-exif - Transition package for python3-exifread python3-exifread - Python library to extract Exif data from TIFF and JPEG files Closes: 942287 Changes: python-exif (2.2.0-4) unstable; urgency=medium . * Rename binary package (Closes: #942287) Checksums-Sha1: e3a001eb927f0eaf49bf4c8429fb40698927e8fd 2142 python-exif_2.2.0-4.dsc 30bb3032930dc9db152e22d148656308c9878f5f 2992 python-exif_2.2.0-4.debian.tar.xz ed9e4a3e74e6c2ce1d9b56f190fe4f22d8f1d64f 7256 python-exif_2.2.0-4_amd64.buildinfo bba68ec11d5690494b03014156711329e0c2ca85 8092 python3-exif_2.2.0-4_all.deb e1dd45e717de820b41a0134652b1ce13af14c3d6 32884 python3-exifread_2.2.0-4_all.deb Checksums-Sha256: da1d3a6cd9dfca0028ab65e4775c1151b1499efebb59fada4e3a7a157ad419c9 2142 python-exif_2.2.0-4.dsc 1fb2f232bdba3bd46ef1a1cee45508ad83470504944f2b8a0b4125ee6493659b 2992 python-exif_2.2.0-4.debian.tar.xz 0b0bd1c164a3054dc9ec2a683fa5bc574e05daca0d887a26e0dada4a07eb6742 7256 python-exif_2.2.0-4_amd64.buildinfo 9de34ea54d232f059ce0ca0a29c01bb37a92b267d9edfad77e358054771e4f6b 8092 python3-exif_2.2.0-4_all.deb 82f795118128f3db89462148c551ec86a3424d6ee898df11d01e5aae10e3e845 32884 python3-exifread_2.2.0-4_all.deb Files: 10206f6453c2d4392d93373708993ea8 2142 python optional python-exif_2.2.0-4.dsc 6d4cc8ac81ecd86969ffd5e644fd5f9d 2992 python optional python-exif_2.2.0-4.debian.tar.xz 765738cf1fba81e752e7424d56210fb0 7256 python optional python-exif_2.2.0-4_amd64.buildinfo 7f7789ebc26ac5a95714ba668682b3dd 8092 oldlibs optional python3-exif_2.2.0-4_all.deb 5946cb97a9d8b41c538e3c6b779a2972 32884 python optional python3-exifread_2.2.0-4_all.deb -BEGIN PGP SIGNATURE- iQJGBAEBCAAwFiEE0kq/0SfNJVahPGx5zBSfbCil4lcFAl2kjv0SHHRha2FraUBk ZWJpYW4ub3JnAAoJEMwUn2wopeJXBaMP/2+CRgwHLNp99V6isQJUsE9mvgiLtvna Ko5YMXjm/V/quic2fyJ/Nian1Y2nhXKHN31ezwOAOOG0VKSLINuDhsKeuoSgZfb+ LSa20SpT44ru9EfVbRmhe7BOiUx4AebebbpidteF8To5bVvGKf1htVaG68pgBN6H 2j5r/DPe+lECqYu9yHlm79JGIZ2WzYAtPBtCbh9VsJdcDex4cG5AouUIGMjOfb0Z bU1Pk1QNfAZoKO/48a7Pqejh7MNm9uOszlRHkG6L2kjKyhR
Bug#942165: CVE-2019-14857
Same for stretch: https://salsa.debian.org/debian/libapache2-mod-auth-openidc/commit/e0b3eac21212b12562721ab3c903c4f24eef9e8f On 16.10.19 11:19, Moritz Schlarb wrote: > Hi everyone, > > I have prepared a backport of the patches for the version packaged in > Buster: > https://salsa.debian.org/debian/libapache2-mod-auth-openidc/commit/17e31b94a71ef02d1417bee6b0ef7b7379b40375 > > If you deem necessary and sufficient, please release as a security > update or otherwise I'll try to get it in in proposed-updates. > > Regards, > Moritz (another one) > > On 11.10.19 10:14, Moritz Muehlenhoff wrote: >> Package: libapache2-mod-auth-openidc >> Severity: grave >> Tags: security >> >> Please see: >> https://groups.google.com/forum/#!topic/mod_auth_openidc/boy1Ba3Gdk4 >> >> https://github.com/zmartzone/mod_auth_openidc/commit/5c15dfb08106c2451c2c44ce7ace6813c216ba75 >> https://github.com/zmartzone/mod_auth_openidc/commit/ce37080c6aea30aabae8b4a9b4eea7808445cc8e >> https://github.com/zmartzone/mod_auth_openidc/pull/451 >> >> Cheers, >> Moritz >> >> > -- Moritz Schlarb Unix-Gruppe | Systembetreuung Zentrum für Datenverarbeitung Johannes Gutenberg-Universität Mainz Raum 01-331 - Tel. +49 6131 39-29441 OpenPGP Fingerprint: DF01 2247 BFC6 5501 AFF2 8445 0C24 B841 C7DD BAAF signature.asc Description: OpenPGP digital signature
Processed: Re: Bug#936270: calibre: Python2 removal in sid/bullseye
Processing commands for cont...@bugs.debian.org: > severity 936270 important Bug #936270 [src:calibre] calibre: Python2 removal in sid/bullseye Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 936270: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936270 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#936270: calibre: Python2 removal in sid/bullseye
severity 936270 important thanks Hi Stuart, hi Thomas, @Thomas, thanks for reintroducing python-cherrypy3! On Mon, 14 Oct 2019, Stuart Prescott wrote: > bullseye would currently fail because there would be no Python 2 module for > cherrypy3 available. > > While python-cherrypy3 should not yet have been dropped, the reality is that > it has been. This bug is RC just like any other bug about depending on Since the package has been introduced again, I am adjusting the severity accordingly. If you are of different opinion, please adjust again. Thanks Norbert -- PREINING Norbert http://www.preining.info Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
Bug#942113: 3depict: FTBFS on PPC64EL - POWERPC macro not always defined
Hello I've personally always used __powerpc__ . Here is my reference, very useful for all arch related defines : https://wiki.debian.org/ArchitectureSpecificsMemo Cheers Thierry I've Cc:-ed tille as his was the most recent upload. Let me know if you'd like me to NMU with a s/__POWERPC__/__powerpc__/. Cheers, Olly
Bug#942165: CVE-2019-14857
Hi everyone, I have prepared a backport of the patches for the version packaged in Buster: https://salsa.debian.org/debian/libapache2-mod-auth-openidc/commit/17e31b94a71ef02d1417bee6b0ef7b7379b40375 If you deem necessary and sufficient, please release as a security update or otherwise I'll try to get it in in proposed-updates. Regards, Moritz (another one) On 11.10.19 10:14, Moritz Muehlenhoff wrote: > Package: libapache2-mod-auth-openidc > Severity: grave > Tags: security > > Please see: > https://groups.google.com/forum/#!topic/mod_auth_openidc/boy1Ba3Gdk4 > > https://github.com/zmartzone/mod_auth_openidc/commit/5c15dfb08106c2451c2c44ce7ace6813c216ba75 > https://github.com/zmartzone/mod_auth_openidc/commit/ce37080c6aea30aabae8b4a9b4eea7808445cc8e > https://github.com/zmartzone/mod_auth_openidc/pull/451 > > Cheers, > Moritz > > -- Moritz Schlarb Unix-Gruppe | Systembetreuung Zentrum für Datenverarbeitung Johannes Gutenberg-Universität Mainz Raum 01-331 - Tel. +49 6131 39-29441 OpenPGP Fingerprint: DF01 2247 BFC6 5501 AFF2 8445 0C24 B841 C7DD BAAF signature.asc Description: OpenPGP digital signature
Bug#938962: [PATCH] um: Fix pcap and vde driver builds
On 16/10/2019 08:53, Anton Ivanov wrote:
Signed-off-by: Anton Ivanov
---
arch/um/drivers/Makefile | 8
scripts/link-vmlinux.sh | 2 +-
2 files changed, 9 insertions(+), 1 deletion(-)
diff --git a/arch/um/drivers/Makefile b/arch/um/drivers/Makefile
index 693319839f69..34355057ec85 100644
--- a/arch/um/drivers/Makefile
+++ b/arch/um/drivers/Makefile
@@ -24,6 +24,14 @@ LDFLAGS_vde.o := -r $(shell $(CC) $(CFLAGS)
-print-file-name=libvdeplug.a)
targets := pcap_kern.o pcap_user.o vde_kern.o vde_user.o
+ifeq ($(CONFIG_UML_NET_PCAP),y)
+ export UML_EXTRA_LIBS += -lpcap
+endif
+ifeq ($(CONFIG_UML_NET_VDE),y)
+ export UML_EXTRA_LIBS += -lvde -lvdeplug
+endif
+
+
$(obj)/pcap.o: $(obj)/pcap_kern.o $(obj)/pcap_user.o
$(LD) -r -dp -o $@ $^ $(ld_flags)
diff --git a/scripts/link-vmlinux.sh b/scripts/link-vmlinux.sh
index 915775eb2921..d3e6a6cdfc13 100755
--- a/scripts/link-vmlinux.sh
+++ b/scripts/link-vmlinux.sh
@@ -86,7 +86,7 @@ vmlinux_link()
${CC} ${CFLAGS_vmlinux} -o ${2} \
-Wl,-T,${lds} \
${objects} \
- -lutil -lrt -lpthread
+ -lutil -lrt -lpthread ${UML_EXTRA_LIBS}
rm -f linux
fi
}
This will not work as advertised unfortunately - I have to write out the
libs list somewhere and load it again in the link script instead of
passing it as an environment variable.
A fixed patch will follow shortly.
--
Anton R. Ivanov
Cambridgegreys Limited. Registered in England. Company Number 10273661
https://www.cambridgegreys.com/
Bug#942165: marked as done (CVE-2019-14857)
Your message dated Wed, 16 Oct 2019 08:38:39 + with message-id and subject line Bug#942165: fixed in libapache2-mod-auth-openidc 2.4.0.3-1 has caused the Debian Bug report #942165, regarding CVE-2019-14857 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.) -- 942165: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942165 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libapache2-mod-auth-openidc Severity: grave Tags: security Please see: https://groups.google.com/forum/#!topic/mod_auth_openidc/boy1Ba3Gdk4 https://github.com/zmartzone/mod_auth_openidc/commit/5c15dfb08106c2451c2c44ce7ace6813c216ba75 https://github.com/zmartzone/mod_auth_openidc/commit/ce37080c6aea30aabae8b4a9b4eea7808445cc8e https://github.com/zmartzone/mod_auth_openidc/pull/451 Cheers, Moritz --- End Message --- --- Begin Message --- Source: libapache2-mod-auth-openidc Source-Version: 2.4.0.3-1 We believe that the bug you reported is fixed in the latest version of libapache2-mod-auth-openidc, 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 942...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Moritz Schlarb (supplier of updated libapache2-mod-auth-openidc 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, 16 Oct 2019 10:13:44 +0200 Source: libapache2-mod-auth-openidc Architecture: source Version: 2.4.0.3-1 Distribution: unstable Urgency: high Maintainer: Moritz Schlarb Changed-By: Moritz Schlarb Closes: 942165 Changes: libapache2-mod-auth-openidc (2.4.0.3-1) unstable; urgency=high . * Update watch file to use Github tag archives * New upstream version 2.4.0.3 (Closes: #942165) Checksums-Sha1: fca106f98d34b3e9f16eb42e4df519b0b153184e 2525 libapache2-mod-auth-openidc_2.4.0.3-1.dsc d8df9aa4e085b7d230ada7a3ef8328c2b49830af 237869 libapache2-mod-auth-openidc_2.4.0.3.orig.tar.gz 5a3f79b68769cdb0327063ee40b727d0ec5f5d80 5044 libapache2-mod-auth-openidc_2.4.0.3-1.debian.tar.xz 904037fc4ae4d117e63953ce2ebcbef06a1ffa5f 7565 libapache2-mod-auth-openidc_2.4.0.3-1_amd64.buildinfo Checksums-Sha256: 2c439c8408a6e13a2a2efc318f51be0f3fcd9e5b85278e76d2841f6011c8bb67 2525 libapache2-mod-auth-openidc_2.4.0.3-1.dsc 65dadbc19c4d5837b1cb52e080c7404d6435ddf66298ad8693ad2ed0ad4d1fbd 237869 libapache2-mod-auth-openidc_2.4.0.3.orig.tar.gz 819c5fb1b52be5d3a60090cac1d879ed5f3d54a90fc494243b80009c25710951 5044 libapache2-mod-auth-openidc_2.4.0.3-1.debian.tar.xz b4c6ee709dc684d72fd0ca45aef4ea80dd89c94dae4901733382b00b6ce0ad50 7565 libapache2-mod-auth-openidc_2.4.0.3-1_amd64.buildinfo Files: 8ba702880e8063b73ce7a07f169c2cb1 2525 httpd optional libapache2-mod-auth-openidc_2.4.0.3-1.dsc 8929b6c8fea069bd445125b8e3113807 237869 httpd optional libapache2-mod-auth-openidc_2.4.0.3.orig.tar.gz 9cc5745aac8fe58160bd9f73eecdf376 5044 httpd optional libapache2-mod-auth-openidc_2.4.0.3-1.debian.tar.xz 27955009cbd36c9e5b2d78ca0d772c8c 7565 httpd optional libapache2-mod-auth-openidc_2.4.0.3-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJKBAEBCgA0FiEE3wEiR7/GVQGv8oRFDCS4Qcfduq8FAl2m0t4WHHNjaGxhcmJt QHVuaS1tYWluei5kZQAKCRAMJLhBx926r9uwD/4lPSBC/kPInALrSNdZB6BLKBW2 xItsM2xm2mZurTEOwab7i405Q9dZi8JBK5Sm35pJG8efFAD0463AvzXZFkEZfySK 5P+m3LhiLLccZ3Z+R3RIUKOJoneyMC3TKe8QfRoyxrNnVMc9bZBkgVpMXdqYcFRr O2bvrAvaibD7JAanzMrNq9Tk3DsJRPSP8czZWlEico9zvFLOrmQwWY+KTOU8NtfT IWEt5+hGfnIj4HaZpiW4dQU50sfxW/S25RFBjvji1/MQ1sT9hKob5Z5og9PtDmN4 Y4JegJHlprNnnovswwwWhq4VhWJntkuc+M5KtL18422wCzjj5cTnPp/HGIgUkrS7 62NaJ+WSyqJvrS3QtMWgPI7M8x4HSXIS7EHkTadHuNgCFPGkoBql3cz3YSWoN0dG ZMM90X9Eu57tU+IVjhOMNxsO/sCB365O0Dzp215cAEHoU1/xz08mZYgITLTMiLwR UHxxgiRzpb+teiNm5hV1JE8lAC7wGZhWpCBxYsjR0OeHp0MouKMT2tkDFZug+D8S zjbWb7KiPAihfQ34pflZE30cPjjlkXZNjCgWSMT/EwOYWmu4Nl0FCZ8ksi7X0M3b EVTyk25Wir+4u84iM+oUI+Zd8EV9MnDYak55Hto7FhqbwRYMMW+J2g759w/O9kDn ZPeB7PsDisyNc7u6/w== =NwOt -END PGP SIGNATURE End Message ---
Bug#938962: [PATCH] um: Fix pcap and vde driver builds
Signed-off-by: Anton Ivanov
---
arch/um/drivers/Makefile | 8
scripts/link-vmlinux.sh | 2 +-
2 files changed, 9 insertions(+), 1 deletion(-)
diff --git a/arch/um/drivers/Makefile b/arch/um/drivers/Makefile
index 693319839f69..34355057ec85 100644
--- a/arch/um/drivers/Makefile
+++ b/arch/um/drivers/Makefile
@@ -24,6 +24,14 @@ LDFLAGS_vde.o := -r $(shell $(CC) $(CFLAGS)
-print-file-name=libvdeplug.a)
targets := pcap_kern.o pcap_user.o vde_kern.o vde_user.o
+ifeq ($(CONFIG_UML_NET_PCAP),y)
+ export UML_EXTRA_LIBS += -lpcap
+endif
+ifeq ($(CONFIG_UML_NET_VDE),y)
+ export UML_EXTRA_LIBS += -lvde -lvdeplug
+endif
+
+
$(obj)/pcap.o: $(obj)/pcap_kern.o $(obj)/pcap_user.o
$(LD) -r -dp -o $@ $^ $(ld_flags)
diff --git a/scripts/link-vmlinux.sh b/scripts/link-vmlinux.sh
index 915775eb2921..d3e6a6cdfc13 100755
--- a/scripts/link-vmlinux.sh
+++ b/scripts/link-vmlinux.sh
@@ -86,7 +86,7 @@ vmlinux_link()
${CC} ${CFLAGS_vmlinux} -o ${2} \
-Wl,-T,${lds} \
${objects} \
- -lutil -lrt -lpthread
+ -lutil -lrt -lpthread ${UML_EXTRA_LIBS}
rm -f linux
fi
}
--
2.20.1
Bug#938962: Build fix for VDE and PCAP drivers
Hi all, A patch to fix the build for these follows. I will stick to my original suggestion - pcap should be obsoleted in favour of vector raw + BPF firmware load. The latter will work on interfaces where gso/gro is enabled. The original pcap will fail on that due to the 1500 bytes size limit in the legacy net code. I had to dig the root cause here and figure out what is going on while working on an AF_XDP transport as that had the same problem - it needed to pass -lbpf -lelf -lz which could not be passed under the current build system. A.
Processed: forwarded dwz issue
Processing commands for cont...@bugs.debian.org: > forwarded 942193 https://sourceware.org/bugzilla/show_bug.cgi?id=25109 Bug #942193 [dwz] dwz: dh_dwz freecad build regression: write_die: Assertion `value && refdcu->cu_kind != CU_ALT' failed. Set Bug forwarded-to-address to 'https://sourceware.org/bugzilla/show_bug.cgi?id=25109'. > thanks Stopping processing here. Please contact me if you need assistance. -- 942193: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942193 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
