Bug#955535: httping: diff for NMU version 2.5-5.1
Control: tags 955535 + patch Control: tags 955535 + pending Dear maintainer, I've prepared an NMU for httping (versioned as 2.5-5.1) and uploaded it to DELAYED/14. Please feel free to tell me if I should cancel it. cu Adrian diff -Nru httping-2.5/debian/changelog httping-2.5/debian/changelog --- httping-2.5/debian/changelog 2018-11-20 12:32:29.0 +0200 +++ httping-2.5/debian/changelog 2020-05-08 09:30:50.0 +0300 @@ -1,3 +1,11 @@ +httping (2.5-5.1) unstable; urgency=low + + * Non-maintainer upload. + * Add needs-internet restrictions to autopkgtest. (Closes: #955535) + * Remove unnecessary test depends. + + -- Adrian Bunk Fri, 08 May 2020 09:30:50 +0300 + httping (2.5-5) unstable; urgency=medium * debian/tests/control: update the depends for ci.debian.net diff -Nru httping-2.5/debian/tests/control httping-2.5/debian/tests/control --- httping-2.5/debian/tests/control 2018-11-20 12:32:29.0 +0200 +++ httping-2.5/debian/tests/control 2020-05-08 09:30:50.0 +0300 @@ -3,10 +3,10 @@ Restrictions: allow-stderr Test-Command: httping -c 2 https://debian.org -Depends: @, openssl -Restrictions: allow-stderr +Depends: @ +Restrictions: allow-stderr, needs-internet Test-Command: httping -F -c 4 http://google.com -Depends: @, @builddeps@ -Restrictions: allow-stderr +Depends: @ +Restrictions: allow-stderr, needs-internet
Processed: httping: diff for NMU version 2.5-5.1
Processing control commands: > tags 955535 + patch Bug #955535 [src:httping] httping: flaky autopkgtest: PING google.com:80 Added tag(s) patch. > tags 955535 + pending Bug #955535 [src:httping] httping: flaky autopkgtest: PING google.com:80 Added tag(s) pending. -- 955535: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955535 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 936153
Processing commands for cont...@bugs.debian.org: > tags 936153 + fixed-upstream Bug #936153 [src:aseba-plugin-blockly] aseba-plugin-blockly: Python2 removal in sid/bullseye Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 936153: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936153 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 938036
Processing commands for cont...@bugs.debian.org: > tags 938036 + fixed-upstream Bug #938036 [src:python-pmw] python-pmw: Python2 removal in sid/bullseye Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 938036: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938036 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#959946: marked as done (grace: fails to start: failed request: 12 (X_ConfigureWindow))
Your message dated Fri, 08 May 2020 13:12:01 +0800 with message-id <0ea239623b45aed21f226ed98d544...@debian.org> and subject line Re: Bug#959946: grace: fails to start: failed request: 12 (X_ConfigureWindow) has caused the Debian Bug report #959946, regarding grace: fails to start: failed request: 12 (X_ConfigureWindow) 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.) -- 959946: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959946 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: grace Version: 1:5.1.25-8 Severity: grave Justification: renders package unusable On a clean installation, grace fails to launch: $ xmgrace X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 12 (X_ConfigureWindow) Value in failed request: 0x0 Serial number of failed request: 2821 Current serial number in output stream: 2822 This happens both with the latest official build from the archive and with a fresh local rebuild. backtrace from gdb adds a reference to libthread_db.so: Starting program: /usr/bin/xmgrace [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". X Error of failed request: BadValue (integer parameter out of range for operation) -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.5.0-2-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_WARN Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages grace depends on: ii fontconfig2.13.1-4 ii gsfonts 1:8.11+urwcyr1.0.7~pre44-4.4 ii libc6 2.30-7 ii libfftw3-double3 3.3.8-2 ii libjpeg62-turbo 1:1.5.2-2+b1 ii libnetcdf18 1:4.7.4-1 ii libpng16-16 1.6.37-2 ii libx11-6 2:1.6.9-2+b1 ii libxbae4m 4.60.4-7+b11 ii libxm42.3.8-2 ii libxmhtml1.1 1.1.10-3 ii libxmu6 2:1.1.2-2+b3 ii libxpm4 1:3.5.12-1 ii libxt61:1.1.5-1+b3 ii xterm 356-1 Versions of packages grace recommends: ii xfonts-100dpi 1:1.0.4+nmu1 ii xfonts-75dpi 1:1.0.4+nmu1 Versions of packages grace suggests: ii gconf2 3.2.6-6 ii ghostscript 9.52~dfsg-1 pn texlive-extra-utils -- no debconf information --- End Message --- --- Begin Message --- On 2020-05-08 04:38, Nicholas Breen wrote: I cannot reproduce this on any of three systems. If you have a residual /etc/X11/app-defaults/XMgrace, can you try removing it? It's a fresh installation, there's no /etc/X11/app-defaults/XMgrace Can you generate a log with xtrace? Hmm, actually xtrace isn't working either...time for a reboot. ... After the reboot, xmgrace is now launching fine. Still don't know what the problem was, but it's gone now, so I'll close this bug. Strangely, xtrace is still not working: $ xtrace xmgrace No display name to create specified, trying :9 Error parsing xauth list data: less than three things in a line! Says it can't find a display, even though DISPLAY is defined. I suspect it might be a problem with Wayland, which is now used by default in fresh installations with Gnome. Anyway, xmgrace is now working. Can worry about xtrace elsewhere. Thanks for checking for the bug. Drew--- End Message ---
Bug#959454: marked as done (dvbtune: Build-Depends on obsolete package linux-kernel-headers)
Your message dated Fri, 08 May 2020 03:34:31 + with message-id and subject line Bug#959454: fixed in dvbtune 0.5.ds-2 has caused the Debian Bug report #959454, regarding dvbtune: Build-Depends on obsolete package linux-kernel-headers 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.) -- 959454: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959454 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:dvbtune Version: 0.5.ds-1.1 Severity: serious linux-kernel-headers was removed from unstable in 2007 (I think). It is now effectively a virtual package provided by linux-libc-dev, but it's not a documented virtual package name and I would like to stop providing it. Please change the dependency to linux-libc-dev. Ben. -- Ben Hutchings The first rule of tautology club is the first rule of tautology club. signature.asc Description: This is a digitally signed message part --- End Message --- --- Begin Message --- Source: dvbtune Source-Version: 0.5.ds-2 Done: Sudip Mukherjee We believe that the bug you reported is fixed in the latest version of dvbtune, 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 959...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sudip Mukherjee (supplier of updated dvbtune 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: Tue, 05 May 2020 13:19:59 +0100 Source: dvbtune Architecture: source Version: 0.5.ds-2 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Sudip Mukherjee Closes: 883578 959454 Changes: dvbtune (0.5.ds-2) unstable; urgency=medium . * QA upload. . [ Sudip Mukherjee ] * Orphan the package. (See: #839969) * Remove dependency on linux-kernel-headers. (Closes: #959454) * Update Standards-Version to 4.5.0 * Use debhelper-commit. - Update to compat version 13. * Mark Vcs to salsa. * Build with debug symbols. * Remove whitespace from changelog. . [ Helmut Grohne ] * Fix FTCBFS: Let dh_auto_build pass cross tools to make. (Closes: #883578) Checksums-Sha1: 531cc98430a4550017aed0a480fb442e619ef267 1861 dvbtune_0.5.ds-2.dsc 781631b2af453b3159169608464ec0a6e820cb61 11856 dvbtune_0.5.ds-2.debian.tar.xz 3a170325e8bb02afcc46b342bf62c8b3fa0f5bb4 5439 dvbtune_0.5.ds-2_source.buildinfo Checksums-Sha256: f5f553d1aad8cb6b0bb0880fa759a3a1c51dd931e8b723adbba06dc3bd0026b7 1861 dvbtune_0.5.ds-2.dsc cc320915a41f235df6677519fc480750c6153bbc4b0f4f9fd98ab5978afdcea6 11856 dvbtune_0.5.ds-2.debian.tar.xz 2e1aad24c0bd6e2ebeee93712e1ade219c4f0dcd44e67bbb8b41c05c483ed7e6 5439 dvbtune_0.5.ds-2_source.buildinfo Files: 2b01cf3fbe4df5fb364469f23a7be618 1861 utils optional dvbtune_0.5.ds-2.dsc 6609e862793288d21a99eda92fe6849d 11856 utils optional dvbtune_0.5.ds-2.debian.tar.xz 0f5b5496a8c6ee136184040967a87f5c 5439 utils optional dvbtune_0.5.ds-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAl60yiwACgkQweDZLphv fH47/xAA6ZGsdDjcNe7IbvMdplCxndKIcP1z+l/yeqXhDSF0+kWTaj5leSClLved hIOiEKSKi8selhiTIqZaE/Qr/X7kfMv7aRJGUqnA7nn2ihmDTjTc9vMVLCHWuYly 60DPi/JDHbYv7jiYqaaGu8u51CbcP4RP+IFIfQTIbEu4rjqFR9VPCFPi3JPiddd3 fPly4Q3ApeSb/Sys92JxWj7MDF18AHsra1b1PxGKZ9IJ4Y3Z6RBs/BabeHrGIMH3 NHLp6Vd4y74kVWq5wxS4BxmMxIZlR7OpVBzOeoX1ZXpEsYByf3Y2BNxw5eRQYHz2 6rT6HOWamq+PmJ3DkR3+xhNkL5z8+zQLBi/3HynYRRGKVy0LbPCKIqwUF7JxjUWg lHvD5ElwlZGW4iM8pLLNCagHsrsZv68N+4FsSQTYfxjNVXru/jWUv6WzszxFG9Ip nBrpkoW6Z55QtXty6Oh4ZMBkMqXetYSjrYUu+s3tcBKZdh5Em+J9VX4I6i6+sgOH hiMw17GhCo2jR1dhFTFXfzax+JtmQ/V1fipNqarFbTOPtY3Y2xsz5Kix7Gq0H4R4 v4o7z0aa5KC2o3oHDRhpkZJ6OZpuaHMFSsZ2lKrEySdIrX5s8qUr4+z3NHVQzHRO KeSVNrrNLPXvlxZ0vjYeprrtAR8JmsYkD3M4lMW1ngK9opmWi+4= =jJkC -END PGP SIGNATURE End Message ---
Bug#959889: marked as done (python3-sphinx-gallery: AttributeError: 'URLError' object has no attribute 'url')
Your message dated Fri, 08 May 2020 02:45:12 + with message-id and subject line Bug#959889: fixed in sphinx-gallery 0.6.2-1 has caused the Debian Bug report #959889, regarding python3-sphinx-gallery: AttributeError: 'URLError' object has no attribute 'url' 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.) -- 959889: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959889 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sphinx-gallery Version: 0.5.0 Severity: serious Tags: affects -1 src:astropy Dear maintainer, when I try to use sphinx-gallery to build the new astropy package, I get the following error from sphinx-gallery: Exception occurred: File "/usr/lib/python3/dist-packages/sphinx_gallery/docs_resolv.py", line 260, in _handle_http_url_error msg, e.url, extra, e.msg) AttributeError: 'URLError' object has no attribute 'url' The reason seems to be that urllib.error.URLError indeed has no such attribute (anymore?) on Python 3.8 This seem fixed upstream and could probvably be solved by uploading a new version. Best regards Ole --- End Message --- --- Begin Message --- Source: sphinx-gallery Source-Version: 0.6.2-1 Done: Sandro Tosi We believe that the bug you reported is fixed in the latest version of sphinx-gallery, 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 959...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sandro Tosi (supplier of updated sphinx-gallery 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, 07 May 2020 22:00:07 -0400 Source: sphinx-gallery Architecture: source Version: 0.6.2-1 Distribution: unstable Urgency: medium Maintainer: Sandro Tosi Changed-By: Sandro Tosi Closes: 959889 Changes: sphinx-gallery (0.6.2-1) unstable; urgency=medium . * New upstream release; Closes: #959889 * debian/patches/* - refresh, update patches * debian/rules - make rules look like more a dh + pybuild file * run unittest at build time Checksums-Sha1: 71f521e98d0edd8fa381161ac735d214fca31e4c 2572 sphinx-gallery_0.6.2-1.dsc 6d789c66d5ad5827f77852aa2d382add3e18d9ca 375856 sphinx-gallery_0.6.2.orig.tar.xz 3f2d39207f480b4d9568da0c241dacb32cc521eb 4688 sphinx-gallery_0.6.2-1.debian.tar.xz 82ca0ccae5c6350502de6f0f450f7b501791f6a1 10703 sphinx-gallery_0.6.2-1_source.buildinfo Checksums-Sha256: 2002e0d27c42f35fe741594bd537a62d77d7ea6c9796545fc9aa084c23862b7b 2572 sphinx-gallery_0.6.2-1.dsc f64c2439b45e5fe34950719ccc195f1cd8bb2a76e6b18d6f54a06fa03046ac69 375856 sphinx-gallery_0.6.2.orig.tar.xz 943d9abc89749c1af356bd350baea3e7c0a7c8140c352cc1cd3fa1fdd1b107a7 4688 sphinx-gallery_0.6.2-1.debian.tar.xz 32b08a21d7f31a223a34967e7838498bba3c5ba247634bfc60b75c61d06554ef 10703 sphinx-gallery_0.6.2-1_source.buildinfo Files: 69a31f8d2b423cc27c2608c1cbca8eef 2572 python optional sphinx-gallery_0.6.2-1.dsc e9861fc2d020809c9fbc46b162840f01 375856 python optional sphinx-gallery_0.6.2.orig.tar.xz ccda97031f4af30ee8beae40095cee01 4688 python optional sphinx-gallery_0.6.2-1.debian.tar.xz af31d3d200023a19846326d2289a1370 10703 python optional sphinx-gallery_0.6.2-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEufrTGSrz5KUwnZ05h588mTgBqU8FAl60vVMACgkQh588mTgB qU9w6hAAoFwoXO6ytdQ9sHAy2gVHFoADLUO4kp0L0Xu3yG5fv+AZSDdToqkztsyY 84HrUvswsmLdn5nfuRw2DKv8FN/PWL5mL50E/W1X/EPBhymw3tKdlNi0HamKz9L2 4Q6WPnq/pg0pEWXIF1UdS3dt6Hh7bpd9oc+9nLIwE4K/iXqGjhzUMl125pQijj/m h0Te2VihjTIUKcFRnml1SVeGnxXdE7N5R3mifs41Ei69pZwPe84n0A3Ke54X//w7 4MgVGCxits+MSYsQzPOYy3x7LINsUduf8p9190+SOyL7up4/x1CFYxhbiEUiumtb sUkrybMuQf8KsOqGl3TYCvcGCU5ip7Ou8MihRCbCQLfgnMcDgLLlrsSIN8tbkhUU yJnspKhITwbUfEsVoTCEknZVQ9UDkkLH2w2kswGEjvq5KIT/MgfzBwuPXpCwwySJ EHsBMPZ5JYhmt5H3Zfr0W+JmofNHe85CrQjLxaYMTtqSFZgHGQY9QSgSf4/6Rgh7 JWsqMdaxWc92czbzbIf0HfPHv07XL2KQ838JWKgIfdMspXaO6zq7EG3+yV9h+XYg 9z/dAlRdsMSBG8l8VOWycNRihfGXOofgAm+LiDwBAtzE7ByMJFw+4nySlTjuxgyb 7QC3QBo/wHVDnKuzrQf7YpvLiX1GPAwsXtsp0GhuQsMEMJglOck= =GkJa -END PGP SIGNATURE End Message ---
Bug#959889: marked as pending in sphinx-gallery
Control: tag -1 pending Hello, Bug #959889 in sphinx-gallery reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/modules/sphinx-gallery/-/commit/d47222006f9cf5ae5be60264492ed87164c03931 New upstream release; Closes: #959889 (this message was generated automatically) -- Greetings https://bugs.debian.org/959889
Processed: Bug#959889 marked as pending in sphinx-gallery
Processing control commands: > tag -1 pending Bug #959889 [sphinx-gallery] python3-sphinx-gallery: AttributeError: 'URLError' object has no attribute 'url' Added tag(s) pending. -- 959889: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959889 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#959994: codeville: Consider removing this package
Source: codeville Severity: serious Version: 0.8.0-2.1 Tags: sid bullseye X-Debbugs-CC: jamu...@debian.org Dear Debian codeville maintainer, It seems that package codevilla has a dead upstream since at least 2014. It is a discontinued VCS thus it doesn't make any sense to keep it in Debian archive. Besides, this software is now affected by python2 removal. As a result, I am proposing to have this package removed from Debian. I will submit a removal request to FTP Masters 7 days later (after May 14, 2020). If you have any thoughts, please let me know *immediately*. -- Best Regards, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#938605: marked as done (svgtune: Python2 removal in sid/bullseye)
Your message dated Thu, 07 May 2020 20:35:40 -0400 with message-id <2f3cd2e49538cb07173ea26410453f0b6894be7a.ca...@debian.org> and subject line Re: svgtune: Python2 removal in sid/bullseye has caused the Debian Bug report #938605, regarding svgtune: Python2 removal in sid/bullseye 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.) -- 938605: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938605 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:svgtune Version: 0.2.0-2 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:svgtune If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Version: 0.3.0-1 It seems that the new version has made it compatible with Python3. -- Regards, Boyuan Yang On Fri, 30 Aug 2019 07:54:44 + Matthias Klose wrote: > Package: src:svgtune > Version: 0.2.0-2 > Severity: normal > Tags: sid bullseye > User: debian-pyt...@lists.debian.org > Usertags: py2removal > > Python2 becomes end-of-live upstream, and Debian aims to remove > Python2 from the distribution, as discussed in > https://lists.debian.org/debian-python/2019/07/msg00080.html > > Your package either build-depends, depends on Python2, or uses Python2 > in the autopkg tests. Please stop using Python2, and fix this issue > by one of the following actions. > > - Convert your Package to Python3. This is the preferred option. In > case you are providing a Python module foo, please consider dropping > the python-foo package, and only build a python3-foo package. Please > don't drop Python2 modules, which still have reverse dependencies, > just document them. > > This is the preferred option. > > - If the package is dead upstream, cannot be converted or maintained > in Debian, it should be removed from the distribution. If the > package still has reverse dependencies, raise the severity to > "serious" and document the reverse dependencies with the BTS affects > command. If the package has no reverse dependencies, confirm that > the package can be removed, reassign this issue to ftp.debian.org, > make sure that the bug priority is set to normal and retitle the > issue to "RM: PKG -- removal triggered by the Python2 removal". > > - If the package has still many users (popcon >= 300), or is needed to > build another package which cannot be removed, document that by >
Bug#933439: amule: Please rebuild against wxWidgets GTK 3 package
> Does the crash you referenced here require connecting to file sharing > networks to reproduce? hard to say, as it crashed early on in the start up process (and also because i dont really remember because several months have passed). Clearly there's always a "risk" when using a file sharing software that it connects to the network. that being said, there's no _legal_ issue is you dont have anything in download/upload: even if amule connects to the enkey/kademlia networks it has nothing so share or download, so that's just an empty client with no implications for the IP address it connected to. Regards, -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi Twitter: https://twitter.com/sandrotosi
Bug#947720: sollya ftbfs with libfplll6
Hi, I tried to build this and did not get any failure. +--+ | Summary | +--+ Build Architecture: amd64 Build Type: full Build-Space: 163104 Build-Time: 388 Distribution: unstable Host Architecture: amd64 Install-Time: 244 Job: sollya Machine Architecture: amd64 Package: sollya Package-Time: 636 Source-Version: 7.0+ds-3 Space: 163104 Status: successful Version: 7.0+ds-3 The test has also passed: Building check029.sh PASS: check029.sh Building check030.sh PASS: check030.sh Building check031.sh PASS: check031.sh Building timecheck.sh PASS: timecheck.sh Testsuite summary for sollya 7.0 # TOTAL: 32 # PASS: 32 # SKIP: 0 # XFAIL: 0 # FAIL: 0 # XPASS: 0 # ERROR: 0 Can you please retest and confirm. -- Regards Sudip
Processed: Bug#937762 marked as pending in python-flexmock
Processing control commands: > tag -1 pending Bug #937762 [src:python-flexmock] python-flexmock: Python2 removal in sid/bullseye Added tag(s) pending. -- 937762: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937762 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#937762: marked as pending in python-flexmock
Control: tag -1 pending Hello, Bug #937762 in python-flexmock reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/modules/python-flexmock/-/commit/f30fa4d00bb6b725fb9323d9ece16f25f1e99369 Drop python 2 binary package, no longer used in Debian. (Closes: #937762) (this message was generated automatically) -- Greetings https://bugs.debian.org/937762
Bug#937762: marked as done (python-flexmock: Python2 removal in sid/bullseye)
Your message dated Thu, 07 May 2020 22:34:27 + with message-id and subject line Bug#937762: fixed in python-flexmock 0.10.4-3 has caused the Debian Bug report #937762, regarding python-flexmock: Python2 removal in sid/bullseye 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.) -- 937762: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937762 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-flexmock Version: 0.10.4-1 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:python-flexmock If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: python-flexmock Source-Version: 0.10.4-3 Done: Stefano Rivera We believe that the bug you reported is fixed in the latest version of python-flexmock, 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 937...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stefano Rivera (supplier of updated python-flexmock 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, 07 May 2020 15:17:06 -0700 Source: python-flexmock Architecture: source Version: 0.10.4-3 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team Changed-By: Stefano Rivera Closes: 937762 Changes: python-flexmock (0.10.4-3) unstable; urgency=medium . * Drop python 2 binary package, no longer used in Debian. (Closes: #937762) * Bump Standards-Version to 4.5.0, no changes needed. Checksums-Sha1: f0f8c808a2e905e5f1d31a560bd49812024c805e 1577 python-flexmock_0.10.4-3.dsc 8c23e2fc70e201a9dfdb0e82b932259daba195cb 3344 python-flexmock_0.10.4-3.debian.tar.xz 79dcc08a0fc84e68566057b424da7de97bdedef8 5949 python-flexmock_0.10.4-3_source.buildinfo Checksums-Sha256: b274d048c7c2ad7ffcd7f6d5c3afec7250d442a6f1afb18ae063e70d1f89e4fb 1577 python-flexmock_0.10.4-3.dsc 917bff2d6f65d9ec81374c47766d49c2e3c1f74eeb570557659c26f3a7a9010f 3344 python-flexmock_0.
Bug#959981: Trademark concerns with Chef/Cinc package included in Debian and Ubuntu
I think removing it from Debian is the safe way to go currently. If you want assistance with how we build Cinc and how it could be adapted for Debian let me know. Also if there are any changes we can make on our end to make it easier. Thanks- On Thu, May 7, 2020 at 2:14 PM Antonio Terceiro wrote: > On Thu, May 07, 2020 at 03:32:10PM -0400, benny Vasquez wrote: > > Thanks, Lance! > > > > As he laid out, this packaged shipped as-is is a pretty serious violation > > of our trademarks, and we'd like to see it addressed as soon as humanly > > possible. > > > > On Thu, May 7, 2020 at 2:40 PM Lance Albertson wrote: > > > > > All, > > > > > > I'm a member of the Cinc Project [1] which rebuilds and rebrands > various > > > Chef projects to comply with Chef Trademark Policy [2]. We have worked > > > closely with Chef to ensure Cinc Client complies with this policy. > > > > > > A member of our community notified us today that it appears that Ubuntu > > > [3] and Debian [4] are both including a package called "chef" which > seems > > > to pull in the Cinc source code but doesn't fully comply with the Chef > > > Trademark Policy. We are concerned that this use of the Cinc Client in > the > > > manner it's currently presented will create an issue for us and you in > the > > > future unless this gets resolved quickly. > > > > > > Specifically, we are concerned with the following: > > > > > > 1. The package name should be cinc and not chef as Chef is trademarked > and > > > also causes users to think they are installing Chef when they are > > > installing Cinc > > > 2. The package should have proper attributions to include the Cinc > Project > > > including pointing any issues related to the package to our issue > page, and > > > not Chef > > > 2. Running "chef-client" (or other similar commands) does not tell the > > > user that it's actually using Cinc Client as our package does properly > > > 3. All of the trademark renaming we did in our Cinc Client distribution > > > seems to have been removed and retains all of the Chef related paths > (i.e. > > > /etc/chef when it should be /etc/cinc). This will cause confusion for > users > > > who are expecting Cinc. > > > > > > We would like to work with the Debian/Ubuntu maintainers to ensure > you're > > > following compliance and also ensuring our distribution works well on > > > Debian/Ubuntu. However we also want to ensure you don't get into any > legal > > > trouble with Chef. I am sure most of these changes weren't done > > > intentionally and was a mistake. > > > > > > Feel free to reach out to us via the #community-distros channel on the > > > Chef Community Slack, or you can reach me directly via IRC on Freenode > as > > > "Ramereth". I've also cc'd Benny Vasquez who is a community manager at > > > Chef who can answer any questions relating to this and provide any > > > additional feedback. > > > > > > Thanks! > > > > > > [1] https://cinc.sh/ > > > [2] https://www.chef.io/trademark-policy/ > > > [3] https://packages.ubuntu.com/focal/chef > > > [4] https://packages.debian.org/sid/chef > > I am inclined to just remove chef from Debian as a way of fixing this. > > Maybe I will package cinc from scratch. That would be easier if there > were proper source releases. > -- Lance Albertson Director Oregon State University | Open Source Lab
Processed: affects astropy
Processing commands for cont...@bugs.debian.org: > affects 959889 src:astropy Bug #959889 [sphinx-gallery] python3-sphinx-gallery: AttributeError: 'URLError' object has no attribute 'url' Added indication that 959889 affects src:astropy > thanks Stopping processing here. Please contact me if you need assistance. -- 959889: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959889 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#953751: marked as done (drf-extensions: autopkgtest failure: No module named 'djangorestframework_extensions')
Your message dated Thu, 07 May 2020 21:34:00 + with message-id and subject line Bug#953751: fixed in drf-extensions 0.6.0-2 has caused the Debian Bug report #953751, regarding drf-extensions: autopkgtest failure: No module named 'djangorestframework_extensions' 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.) -- 953751: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953751 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: drf-extensions Version: 0.6.0-1 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: fails-always Dear maintainers, With a recent upload of drf-extensions you added an autopkgtest, great. However, it fails. I copied some of the output at the bottom of this report. You're using autodep8 to trigger the test, but it seems your package naming and Python module name aren't aligned for autodep8. autodep8 recently acquired a new feature that enables you to tell autode8 what the real module name is that should be tested [1]. Currently this regression is blocking the migration to testing [2]. Can you please investigate the situation and fix it? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://manpages.debian.org/unstable/autodep8/autodep8.1.en.html#PYTHON_PACKAGES [2] https://qa.debian.org/excuses.php?package=drf-extensions https://ci.debian.net/data/autopkgtest/testing/amd64/d/drf-extensions/4365527/log.gz [1] https://manpages.debian.org/unstable/autodep8/autodep8.1.en.html#PYTHON_PACKAGES autopkgtest [03:10:46]: test autodep8-python3: set -e ; for py in $(py3versions -r 2>/dev/null) ; do cd "$AUTOPKGTEST_TMP" ; echo "Testing with $py:" ; $py -c "import djangorestframework_extensions; print(djangorestframework_extensions)" ; done autopkgtest [03:10:46]: test autodep8-python3: [--- Testing with python3.8: Traceback (most recent call last): File "", line 1, in ModuleNotFoundError: No module named 'djangorestframework_extensions' autopkgtest [03:10:46]: test autodep8-python3: ---] signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: drf-extensions Source-Version: 0.6.0-2 Done: Antonio Terceiro We believe that the bug you reported is fixed in the latest version of drf-extensions, 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 953...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Antonio Terceiro (supplier of updated drf-extensions 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, 07 May 2020 18:11:39 -0300 Source: drf-extensions Architecture: source Version: 0.6.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team Changed-By: Antonio Terceiro Closes: 953751 Changes: drf-extensions (0.6.0-2) unstable; urgency=medium . * Team upload * autopkgtest: run the actual test suite (Closes: #953751) Checksums-Sha1: d5c064bd0d870cedb4eaf08b897f6d6e3d7e809c 2474 drf-extensions_0.6.0-2.dsc cb937af449f34e3db0db5f822a738b6c2ee2c7c8 3452 drf-extensions_0.6.0-2.debian.tar.xz Checksums-Sha256: f453e8de9af1c708b6d617b2f86c90d9c58d45fee742df3f8f9bc1971d987501 2474 drf-extensions_0.6.0-2.dsc b57504045eb0d5f91d3c36b5527ea335be630e1eba0290fcb592e63a876e3747 3452 drf-extensions_0.6.0-2.debian.tar.xz Files: 387429b4ee23f71c3dd1ab728308f2b9 2474 python optional drf-extensions_0.6.0-2.dsc f96e2f7b293894595d9d2ff464501419 3452 python optional drf-extensions_0.6.0-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQJIBAEBCAAyFiEEst7mYDbECCn80PEM/A2xu81GC94FAl60eocUHHRlcmNlaXJv QGRlYmlhbi5vcmcACgkQ/A2xu81GC96d/BAAmo17J6SLSHHP3OJR5ST0uLsuqNAE VYb/USpzTW+Epwz3+xHuxVtg6cu41Ka/6paKi9MKAuSWrHXuxh340tfi/iho7OJa cPYvrWITCa5j4ZERDcVTqQDn4CBIfbRUFesxHOYB2hYA8LrgsFPy1aGr+25jgs7D sZmHNrAuq8h/8Us1f9aVHexZGHYTmIGeGz0mC+oOFPuuIPXS7+VsWp++2XYIyV9i /+JHhJDB0guJZVeQDwY3E3p11cMVCK7PFoKgqLBQTPDYQuXV7V/TEN4ctitazBqr YA1pB6r91lxDrOPlDVHbtnxpFVoOL0nZRaAiAjyoCI7r3lJkuxsWJs18YKxd0cGN 1/n+JYmTWk0XhLYTdCTeQBC
Bug#958313: marked as done (libnitrokey: FTBFS: symbol changes)
Your message dated Thu, 07 May 2020 21:06:47 + with message-id and subject line Bug#958313: fixed in libnitrokey 3.5-2 has caused the Debian Bug report #958313, regarding libnitrokey: FTBFS: symbol changes 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.) -- 958313: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958313 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- package: src:libnitrokey version: 3.4.1-4 severity: serious tags: ftbfs Hi, A binnmu of libnitrokey on mipsel (to bring the versions in sync for multiarch) failed: https://buildd.debian.org/status/package.php?p=libnitrokey Note that only mipsel was rebuilt (because the binNMU version was lower), so it's possible that this issue isn't limited to mipsel. Cheers, Ivo --- End Message --- --- Begin Message --- Source: libnitrokey Source-Version: 3.5-2 Done: Scott Kitterman We believe that the bug you reported is fixed in the latest version of libnitrokey, 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 958...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Scott Kitterman (supplier of updated libnitrokey 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, 07 May 2020 15:43:59 -0400 Source: libnitrokey Architecture: source Version: 3.5-2 Distribution: unstable Urgency: medium Maintainer: Scott Kitterman Changed-By: Scott Kitterman Closes: 958313 Changes: libnitrokey (3.5-2) unstable; urgency=medium . * Upload to unstable * Update symbols files from experimental build logs (Closes: #958313) * Switch to debhelper-compat and update to compat 12 * Update standards-version to 4.5.0 without further change Checksums-Sha1: ffdd43fcd818a882c56b3c50a69c55310923a804 2066 libnitrokey_3.5-2.dsc fc3a9424d74f59bf97c89994b637e40fdc1eaf59 94356 libnitrokey_3.5.orig.tar.gz 53957cf9ba97b16237c55bf5cb7aca8ea6f44baf 10500 libnitrokey_3.5-2.debian.tar.xz 498e9a6e569cc2ba50cb139bdbda85dd33e37fff 6941 libnitrokey_3.5-2_source.buildinfo Checksums-Sha256: dade13f309434c823c0579c0d72f2c3e35e79234b75068cf0d2ff64604bc7415 2066 libnitrokey_3.5-2.dsc d836f2f20c5b24088542da445893ef0a04834dca7dd8eef020e793de0601bb5a 94356 libnitrokey_3.5.orig.tar.gz f3638d9fc34c0b37bab53c2316ea6c149b1c7c9064b954282b643ef7da64a138 10500 libnitrokey_3.5-2.debian.tar.xz dd2022e8a4c8c437f8860ec8aa02700317e9e3e725c509fbe0d2c2e31a871e5b 6941 libnitrokey_3.5-2_source.buildinfo Files: 9371af7c642520eda3b12740fe839eb2 2066 libs optional libnitrokey_3.5-2.dsc 0b76c501f8e7b5d55505591ba81379be 94356 libs optional libnitrokey_3.5.orig.tar.gz 7d0335c620842ae4fc7aa05898727f6f 10500 libs optional libnitrokey_3.5-2.debian.tar.xz 0156910c5e97dd3f71a57707c2fb6298 6941 libs optional libnitrokey_3.5-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE53Kb/76FQA/u7iOxeNfe+5rVmvEFAl60bS4ACgkQeNfe+5rV mvEbOw//agzDBg+c0giKIgy4CpgtyCRivIGU/XuTQNz5Lyd4xSbVUapJamqtummy HVB+jpSvNoyeHE2Cf9zeoEjX8nph4uJWXr5fV0bKuaCzzxVV2Tgav+q51zXM2Cpu UquE9Of2P35mkvqznUZWzrKy9Q5oDXp6qwOyk0HRu7ywhZBdWz5jp6/+zsKm6bOm zjy7g6YF01Ukn1BEiq9pajeTupmQKZSliJ8feGRobAJk9uLNYc8HHCYC35Y0hzNu b3eSkJJsPTyVkjzrYPmqu6Mg0dVinQucH2eXvQ7Atzuggp7azJ5z3OMYsMcDv/cH apVM2yA4zgMfdu4AeSthwbmUBCviCzKHB23QRNwBgGvJComb2tP+i3x5EQIG36P9 AlSeTsD0Qi7C6M2CG0LWkKW+NbgNhD1LDjQbUKrZSP2fpTmWf0kn/NpO8vtf41V2 dz5Jy38Mgd7D5F3rXfY3t7a3K/3b6dOhDrO1HTLU3OGTYE/W6qXl6N/SDN/GbTwr MsEBrwQOjdEMX58BKyaupZJ49OOZ5hGJdZK5uEL9/awOq1QlZinGkv9Y5QIGIsLZ R5Jg6dOlN8PiC6hjsnWrxHk0vCU3yCDL4KFXljdhNseXXlL1HI8GxxtP8rwBUqKo CJT8K3muVPVHsE/Ifh5uiMTJk7421owfDD6DshSIPBGi36HiL7E= =pA/0 -END PGP SIGNATURE End Message ---
Bug#959961: marked as done (Prefix not properly set?)
Your message dated Thu, 07 May 2020 21:07:15 + with message-id and subject line Bug#959961: fixed in virt-p2v 1.42.0-2 has caused the Debian Bug report #959961, regarding Prefix not properly set? 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.) -- 959961: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959961 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: virt-p2v Version: 1.42.0-1 Severity: grave Hi, When running virt-p2v-make-disk or virt-p2v-make-kiwi, I get the folowing errors: # virt-p2v-make-disk -o plop virt-p2v-make-disk: cannot find /lib/x86_64-linux-gnu/virt-p2v/virt-p2v.xz # virt-p2v-make-kiwi /usr/bin/virt-p2v-make-kiwi: cannot find dependencies file (/share/virt-p2v/dependencies.suse) The files are installed under /usr/lib/x86_64-linux-gnu/virt-p2v/virt-p2v.xz and /usr/share/virt-p2v/dependencies.suse. Looks like the prefix is not properly set Kind regards, Laurent Bigonville -- System Information: Debian Release: bullseye/sid 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 5.5.0-2-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy --- End Message --- --- Begin Message --- Source: virt-p2v Source-Version: 1.42.0-2 Done: Hilko Bengen We believe that the bug you reported is fixed in the latest version of virt-p2v, 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 959...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Hilko Bengen (supplier of updated virt-p2v 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, 07 May 2020 22:22:59 +0200 Source: virt-p2v Architecture: source Version: 1.42.0-2 Distribution: unstable Urgency: medium Maintainer: Hilko Bengen Changed-By: Hilko Bengen Closes: 959961 959962 Changes: virt-p2v (1.42.0-2) unstable; urgency=medium . * Change debian/watch url from https to http * Add patch to fix prefix (Closes: #959961) * Fix dependencies (Closes: #959962) Checksums-Sha1: 47bc659989d3dd30714b5ed29db70615b29eb625 1963 virt-p2v_1.42.0-2.dsc f9dfa6cd81ee2a676bb9d67799ebb2f91f201cae 2216 virt-p2v_1.42.0-2.debian.tar.xz 1261b7090c92d7c16a74c69771f77dc5d3fa6a52 6019 virt-p2v_1.42.0-2_source.buildinfo Checksums-Sha256: ccafcc864aa1680598c9cb80d4992cbba961b055820f8aef4042c83f554a64b8 1963 virt-p2v_1.42.0-2.dsc 99a42baffaac915ed92c578cce75649b94f60514520150dd29c1137e87b8850e 2216 virt-p2v_1.42.0-2.debian.tar.xz 4e488974217f49d6dcbd706821f11bf2f05d1b7c8b17ea55bdb4689c3bd69e9e 6019 virt-p2v_1.42.0-2_source.buildinfo Files: 14084973598a75a87eec94e9979b4b03 1963 admin optional virt-p2v_1.42.0-2.dsc 4844930022cbe6e169306b3c7390c994 2216 admin optional virt-p2v_1.42.0-2.debian.tar.xz 829485133cd35cf1312d4665e7057e03 6019 admin optional virt-p2v_1.42.0-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCAAwFiEErnMQVUQqHZbPTUx4dbcQY1whOn4FAl60cTQSHGJlbmdlbkBk ZWJpYW4ub3JnAAoJEHW3EGNcITp+SKsP/0W1+2RfepPOf86TKNayNh2hlmWmpmS8 aZtdQiA4uXN6rza4uF3bTsysIVHoRG7w9rA6obPIORemp3ljcj/FYSvNvnNkleiF nAQC9Q8iG5uuNruDgFTtD3mwlKiQYZwtymo4vaQ569U8/MOdDpO9YShjgcLjFgGj e+1gwstv0/L/zdQdEtfHqHV+VFbXbMIhAoYo2DaYf/Zk+r55NiiALSObhhyUSO2p JGXCgPPdXHKI4NPtRZVzz9zxwmIqUyme9/o906lZJ5ixGy6MZAXITvmQcqjkzHyV 2sR1JVZsCq4xbH6gSzFzVDaIZhhKo55j1cF+TdJO2NJ8e5oNHYbfH6kGdGJNnFdX gE3qZv033Eg8G1LT0+Kj/p++1iXwzmVWri8MiP0l7gqY7plkdAxnyjWqZ1VjEzOd t3wqypjFJsxuCbba7rCRjX3t+9t4XHa4QjlOIJkA5o+UEHQ4z3PO+T7y/H/wz8MT 2+CbT5mily/OzM+dBX01lUYZfls0MkrQ2eDHJKb46uesKVvrKaVCHH7Q10FsQkAR WtKfLcaWOcDyCkt/7d0QX1YMHSNWgUKoHrTqGtirfjebhiUOvdoawgrXiqz/ZVMf Xfw6QFLu5vXBUlsXMXzZ/qDTvmpvS/Eyk/asfYIRkmY/gY+8Byxu74zO7UifDt+q nmanh5jbdkTd =48JQ -END PGP SIGNATURE End Message ---
Bug#959962: marked as done (Missing dependencies?)
Your message dated Thu, 07 May 2020 21:07:15 + with message-id and subject line Bug#959962: fixed in virt-p2v 1.42.0-2 has caused the Debian Bug report #959962, regarding Missing dependencies? 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.) -- 959962: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959962 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: virt-p2v Version: 1.42.0-1 Severity: serious Hello, virt-p2v has no dependencies defined, but quickly looking which external tools it's using it should IMVHO at least requires the following dependencies: xz-utils for xzcat binutils for strip libguestfs-tools for virt-builder It's also using bash and gzip but these are essentials and should probably not be added to the dependencies. Kind regards, Laurent Bigonville -- System Information: Debian Release: bullseye/sid 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 5.5.0-2-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy --- End Message --- --- Begin Message --- Source: virt-p2v Source-Version: 1.42.0-2 Done: Hilko Bengen We believe that the bug you reported is fixed in the latest version of virt-p2v, 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 959...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Hilko Bengen (supplier of updated virt-p2v 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, 07 May 2020 22:22:59 +0200 Source: virt-p2v Architecture: source Version: 1.42.0-2 Distribution: unstable Urgency: medium Maintainer: Hilko Bengen Changed-By: Hilko Bengen Closes: 959961 959962 Changes: virt-p2v (1.42.0-2) unstable; urgency=medium . * Change debian/watch url from https to http * Add patch to fix prefix (Closes: #959961) * Fix dependencies (Closes: #959962) Checksums-Sha1: 47bc659989d3dd30714b5ed29db70615b29eb625 1963 virt-p2v_1.42.0-2.dsc f9dfa6cd81ee2a676bb9d67799ebb2f91f201cae 2216 virt-p2v_1.42.0-2.debian.tar.xz 1261b7090c92d7c16a74c69771f77dc5d3fa6a52 6019 virt-p2v_1.42.0-2_source.buildinfo Checksums-Sha256: ccafcc864aa1680598c9cb80d4992cbba961b055820f8aef4042c83f554a64b8 1963 virt-p2v_1.42.0-2.dsc 99a42baffaac915ed92c578cce75649b94f60514520150dd29c1137e87b8850e 2216 virt-p2v_1.42.0-2.debian.tar.xz 4e488974217f49d6dcbd706821f11bf2f05d1b7c8b17ea55bdb4689c3bd69e9e 6019 virt-p2v_1.42.0-2_source.buildinfo Files: 14084973598a75a87eec94e9979b4b03 1963 admin optional virt-p2v_1.42.0-2.dsc 4844930022cbe6e169306b3c7390c994 2216 admin optional virt-p2v_1.42.0-2.debian.tar.xz 829485133cd35cf1312d4665e7057e03 6019 admin optional virt-p2v_1.42.0-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCAAwFiEErnMQVUQqHZbPTUx4dbcQY1whOn4FAl60cTQSHGJlbmdlbkBk ZWJpYW4ub3JnAAoJEHW3EGNcITp+SKsP/0W1+2RfepPOf86TKNayNh2hlmWmpmS8 aZtdQiA4uXN6rza4uF3bTsysIVHoRG7w9rA6obPIORemp3ljcj/FYSvNvnNkleiF nAQC9Q8iG5uuNruDgFTtD3mwlKiQYZwtymo4vaQ569U8/MOdDpO9YShjgcLjFgGj e+1gwstv0/L/zdQdEtfHqHV+VFbXbMIhAoYo2DaYf/Zk+r55NiiALSObhhyUSO2p JGXCgPPdXHKI4NPtRZVzz9zxwmIqUyme9/o906lZJ5ixGy6MZAXITvmQcqjkzHyV 2sR1JVZsCq4xbH6gSzFzVDaIZhhKo55j1cF+TdJO2NJ8e5oNHYbfH6kGdGJNnFdX gE3qZv033Eg8G1LT0+Kj/p++1iXwzmVWri8MiP0l7gqY7plkdAxnyjWqZ1VjEzOd t3wqypjFJsxuCbba7rCRjX3t+9t4XHa4QjlOIJkA5o+UEHQ4z3PO+T7y/H/wz8MT 2+CbT5mily/OzM+dBX01lUYZfls0MkrQ2eDHJKb46uesKVvrKaVCHH7Q10FsQkAR WtKfLcaWOcDyCkt/7d0QX1YMHSNWgUKoHrTqGtirfjebhiUOvdoawgrXiqz/ZVMf Xfw6QFLu5vXBUlsXMXzZ/qDTvmpvS/Eyk/asfYIRkmY/gY+8Byxu74zO7UifDt+q nmanh5jbdkTd =48JQ -END PGP SIGNATURE End Message ---
Processed: [bts-link] source package cmake
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package cmake > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #959064 (http://bugs.debian.org/959064) > # Bug title: cmake breaks on -isystem > # * https://gitlab.kitware.com/cmake/cmake/-/issues/20652 > # * remote status changed: opened -> closed > # * closed upstream > tags 959064 + fixed-upstream Bug #959064 [cmake] cmake breaks on -isystem Bug #959960 [cmake] ignition-transport: FTBFS in sid Added tag(s) fixed-upstream. Added tag(s) fixed-upstream. > usertags 959064 - status-opened Usertags were: status-opened. Usertags are now: . > usertags 959064 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 959064: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959064 959960: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959960 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: [bts-link] source package src:dask
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:dask > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #959136 (http://bugs.debian.org/959136) > # Bug title: numpy breaks dask autopkgtest: E assert 10 == 11 > # * https://github.com/dask/dask/issues/6139 > # * remote status changed: open -> closed > # * closed upstream > tags 959136 + fixed-upstream Bug #959136 [src:dask] numpy breaks dask autopkgtest: E assert 10 == 11 Added tag(s) fixed-upstream. > usertags 959136 - status-open Usertags were: status-open. Usertags are now: . > usertags 959136 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 959136: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959136 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#959946: grace: fails to start: failed request: 12 (X_ConfigureWindow)
On Thu, May 07, 2020 at 06:52:58PM +0800, Drew Parsons wrote: > On a clean installation, grace fails to launch: > > $ xmgrace > X Error of failed request: BadValue (integer parameter out of range for > operation) > Major opcode of failed request: 12 (X_ConfigureWindow) > Value in failed request: 0x0 > Serial number of failed request: 2821 > Current serial number in output stream: 2822 Hello Drew, I cannot reproduce this on any of three systems. If you have a residual /etc/X11/app-defaults/XMgrace, can you try removing it? Can you generate a log with xtrace? -- Nicholas Breen nbr...@debian.org
Bug#889748: diagnostics FTBFS: FAIL: stacktrace
Hi, I tried to build it and did not get any failure. Build Architecture: amd64 Build Type: full Build-Space: 352384 Build-Time: 172 Distribution: unstable Host Architecture: amd64 Install-Time: 37 Job: diagnostics Machine Architecture: amd64 Package: diagnostics Package-Time: 213 Source-Version: 0.3.3-12 Space: 352384 Status: successful Version: 0.3.3-12 And this is the stacktrace test that failed before: /usr/bin/make check-TESTS make[11]: Entering directory '/<>/diagnostics/extensions/stacktrace' make[12]: Entering directory '/<>/diagnostics/extensions/stacktrace' PASS: stacktrace Testsuite summary for diagnostics 0.3.3 # TOTAL: 1 # PASS: 1 # SKIP: 0 # XFAIL: 0 # FAIL: 0 # XPASS: 0 # ERROR: 0 Can you please retest this and confirm.. -- Regards Sudip
Bug#959981: Trademark concerns with Chef/Cinc package included in Debian and Ubuntu
On Thu, May 07, 2020 at 03:32:10PM -0400, benny Vasquez wrote: > Thanks, Lance! > > As he laid out, this packaged shipped as-is is a pretty serious violation > of our trademarks, and we'd like to see it addressed as soon as humanly > possible. > > On Thu, May 7, 2020 at 2:40 PM Lance Albertson wrote: > > > All, > > > > I'm a member of the Cinc Project [1] which rebuilds and rebrands various > > Chef projects to comply with Chef Trademark Policy [2]. We have worked > > closely with Chef to ensure Cinc Client complies with this policy. > > > > A member of our community notified us today that it appears that Ubuntu > > [3] and Debian [4] are both including a package called "chef" which seems > > to pull in the Cinc source code but doesn't fully comply with the Chef > > Trademark Policy. We are concerned that this use of the Cinc Client in the > > manner it's currently presented will create an issue for us and you in the > > future unless this gets resolved quickly. > > > > Specifically, we are concerned with the following: > > > > 1. The package name should be cinc and not chef as Chef is trademarked and > > also causes users to think they are installing Chef when they are > > installing Cinc > > 2. The package should have proper attributions to include the Cinc Project > > including pointing any issues related to the package to our issue page, and > > not Chef > > 2. Running "chef-client" (or other similar commands) does not tell the > > user that it's actually using Cinc Client as our package does properly > > 3. All of the trademark renaming we did in our Cinc Client distribution > > seems to have been removed and retains all of the Chef related paths (i.e. > > /etc/chef when it should be /etc/cinc). This will cause confusion for users > > who are expecting Cinc. > > > > We would like to work with the Debian/Ubuntu maintainers to ensure you're > > following compliance and also ensuring our distribution works well on > > Debian/Ubuntu. However we also want to ensure you don't get into any legal > > trouble with Chef. I am sure most of these changes weren't done > > intentionally and was a mistake. > > > > Feel free to reach out to us via the #community-distros channel on the > > Chef Community Slack, or you can reach me directly via IRC on Freenode as > > "Ramereth". I've also cc'd Benny Vasquez who is a community manager at > > Chef who can answer any questions relating to this and provide any > > additional feedback. > > > > Thanks! > > > > [1] https://cinc.sh/ > > [2] https://www.chef.io/trademark-policy/ > > [3] https://packages.ubuntu.com/focal/chef > > [4] https://packages.debian.org/sid/chef I am inclined to just remove chef from Debian as a way of fixing this. Maybe I will package cinc from scratch. That would be easier if there were proper source releases. signature.asc Description: PGP signature
Processed: closing 959684
Processing commands for cont...@bugs.debian.org: > close 959684 2016.11.2+ds-1+deb9u4 Bug #959684 [src:salt] salt: CVE-2020-11651 and CVE-2020-11652 The source 'salt' and version '2016.11.2+ds-1+deb9u4' do not appear to match any binary packages Marked as fixed in versions salt/2016.11.2+ds-1+deb9u4. Bug #959684 [src:salt] salt: CVE-2020-11651 and CVE-2020-11652 Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 959684: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959684 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: blah
Processing commands for cont...@bugs.debian.org: > forwarded 951888 https://github.com/enthought/enable/issues/360 Bug #951888 [src:python-enable] python-enable FTBFS with swig 4.0.1 Set Bug forwarded-to-address to 'https://github.com/enthought/enable/issues/360'. > End of message, stopping processing here. Please contact me if you need assistance. -- 951888: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951888 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#959684: closing 959684
close 959684 2016.11.2+ds-1+deb9u4 thanks
Bug#959981: Trademark issues with Chef/Cinc package included in Debian
Package: chef Version: 15.8.25.3.gcf41df6a2-6 Severity: serious X-Debbugs-CC: la...@osuosl.org, maintain...@cinc.sh, be...@chef.io - Forwarded message from Lance Albertson - Date: Thu, 7 May 2020 11:40:38 -0700 From: Lance Albertson To: pkg-ruby-extras-maintain...@lists.alioth.debian.org, terce...@debian.org, ubuntu-m...@lists.ubuntu.com Cc: maintain...@cinc.sh, be...@chef.io Subject: Trademark concerns with Chef/Cinc package included in Debian and Ubuntu X-Spam-Level: X-Spam-Status: No, score=0.5 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,HTML_MESSAGE,SPF_SOFTFAIL,URIBL_BLOCKED,URIBL_SBL, URIBL_SBL_A autolearn=no autolearn_force=no version=3.4.2 Message-ID: All, I'm a member of the Cinc Project [1] which rebuilds and rebrands various Chef projects to comply with Chef Trademark Policy [2]. We have worked closely with Chef to ensure Cinc Client complies with this policy. A member of our community notified us today that it appears that Ubuntu [3] and Debian [4] are both including a package called "chef" which seems to pull in the Cinc source code but doesn't fully comply with the Chef Trademark Policy. We are concerned that this use of the Cinc Client in the manner it's currently presented will create an issue for us and you in the future unless this gets resolved quickly. Specifically, we are concerned with the following: 1. The package name should be cinc and not chef as Chef is trademarked and also causes users to think they are installing Chef when they are installing Cinc 2. The package should have proper attributions to include the Cinc Project including pointing any issues related to the package to our issue page, and not Chef 2. Running "chef-client" (or other similar commands) does not tell the user that it's actually using Cinc Client as our package does properly 3. All of the trademark renaming we did in our Cinc Client distribution seems to have been removed and retains all of the Chef related paths (i.e. /etc/chef when it should be /etc/cinc). This will cause confusion for users who are expecting Cinc. We would like to work with the Debian/Ubuntu maintainers to ensure you're following compliance and also ensuring our distribution works well on Debian/Ubuntu. However we also want to ensure you don't get into any legal trouble with Chef. I am sure most of these changes weren't done intentionally and was a mistake. Feel free to reach out to us via the #community-distros channel on the Chef Community Slack, or you can reach me directly via IRC on Freenode as "Ramereth". I've also cc'd Benny Vasquez who is a community manager at Chef who can answer any questions relating to this and provide any additional feedback. Thanks! [1] https://cinc.sh/ [2] https://www.chef.io/trademark-policy/ [3] https://packages.ubuntu.com/focal/chef [4] https://packages.debian.org/sid/chef -- Lance Albertson Director Oregon State University | Open Source Lab - End forwarded message - signature.asc Description: PGP signature
Bug#937769: [Python-modules-team] Bug#938756: Bug#937769: getting python-linecache2/python-traceback2 fixes into testing (FAO traceback2, funcsigs nipype and numba maintainers).
On Thursday, May 7, 2020 2:00:58 PM EDT peter green wrote: > I got a failure too when I cloned that branch and tried to build it, but > once I added in the changes from the previous NMU it built fine. I would > push that addition back to the branch but i'm not currently a member of the > python modules team, I requested to join but no response yet. That part is fixed (waiting to join the team). Scott K signature.asc Description: This is a digitally signed message part.
Processed: reassign 959960 to cmake, forcibly merging 959064 959960
Processing commands for cont...@bugs.debian.org: > reassign 959960 cmake Bug #959960 [src:ignition-transport] ignition-transport: FTBFS in sid Bug reassigned from package 'src:ignition-transport' to 'cmake'. No longer marked as found in versions ignition-transport/8.0.0+dfsg-3. Ignoring request to alter fixed versions of bug #959960 to the same values previously set > forcemerge 959064 959960 Bug #959064 [cmake] cmake breaks on -isystem Bug #959960 [cmake] ignition-transport: FTBFS in sid Set Bug forwarded-to-address to 'https://gitlab.kitware.com/cmake/cmake/-/issues/20652'. Added indication that 959960 affects ignition-transport Marked as found in versions cmake/3.16.3-2. Merged 959064 959960 > thanks Stopping processing here. Please contact me if you need assistance. -- 959064: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959064 959960: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959960 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#937769: getting python-linecache2/python-traceback2 fixes into testing (FAO traceback2, funcsigs nipype and numba maintainers).
On 21/04/2020 22:20, Thomas Goirand wrote:
Python 2 has never been removed from this
package. Though instead, we shall remove this source package entirely
from Debian.
# Broken Depends:
nipype: python-nipype
pytest: pypy-pytest
python-logfury: python3-logfury
python-oslo.utils: python3-oslo.utils
# Broken Build-Depends:
beaker: python3-funcsigs
kombu: python3-funcsigs
nipype: python-funcsigs
pagure: python3-funcsigs
pytest: pypy-funcsigs
python-oslo.log: python3-funcsigs
python-oslo.utils: python3-funcsigs (>= 0.4)
ripe-atlas-cousteau: python3-funcsigs
You can remove all of the python-oslo* from the list. The versions in
Experimental, which are the next version of OpenStack, are fixed. In 2
weeks of time, I'll upload all what I staged in Experimental to Sid
(maybe 150 packages?) and that's going to fix it all.
For the others, probably I should start filling bugs...
While I understand you would like to get rid of the python-funcsigs source
package completely, would you be ok with a NMU (debdiff attached) so we can get
the packages in testing back into a consistent state without waiting for all
the rdeps of funcsigs?
So, if I'm following correctly, what you seem to propose, is to remove
Python 2 from unittest2. If that's the case, then I agree with such a
plan. I just didn't dare to do it yet.
Though in fact, I already worked on that, but stopped, also because
unittest2 FTBFS when I try building it on my laptop. So I've pushed it
in its normal Git repo [1] under a py2-removal branch. If anyone has
some time available to look at it, that'd be nice (I currently don't...).
I got a failure too when I cloned that branch and tried to build it, but once I
added in the changes from the previous NMU it built fine. I would push that
addition back to the branch but i'm not currently a member of the python
modules team, I requested to join but no response yet.
I also prepped a NMU for numba and posted a debdiff to the bug report
diff -Nru python-funcsigs-1.0.2/debian/changelog
python-funcsigs-1.0.2/debian/changelog
--- python-funcsigs-1.0.2/debian/changelog 2018-02-27 12:49:28.0
+
+++ python-funcsigs-1.0.2/debian/changelog 2020-04-30 21:43:30.0
+
@@ -1,3 +1,12 @@
+python-funcsigs (1.0.2-4.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Drop python 2 support.
+ * Switch to pybuild, the old build system doesn't like building python3
+only packages.
+
+ -- Peter Michael Green Thu, 30 Apr 2020 21:43:30 +
+
python-funcsigs (1.0.2-4) unstable; urgency=medium
* Team upload.
diff -Nru python-funcsigs-1.0.2/debian/control
python-funcsigs-1.0.2/debian/control
--- python-funcsigs-1.0.2/debian/control2018-02-27 12:49:28.0
+
+++ python-funcsigs-1.0.2/debian/control2020-04-30 21:43:20.0
+
@@ -9,13 +9,10 @@
dh-python,
pypy,
pypy-setuptools (>= 17.1),
- python-all,
- python-setuptools (>= 17.1),
python3-all,
python3-setuptools (>= 17.1),
python3-sphinx,
Build-Depends-Indep:
- python-unittest2 (>= 1.1.0),
python3-unittest2 (>= 1.1.0),
Standards-Version: 4.1.3
Vcs-Browser: https://salsa.debian.org/openstack-team/python/python-funcsigs
@@ -37,20 +34,6 @@
.
This package contains the PyPy module.
-Package: python-funcsigs
-Architecture: all
-Depends:
- ${misc:Depends},
- ${python:Depends},
-Suggests:
- python-funcsigs-doc,
-Description: function signatures from PEP362 - Python 2.7
- funcsigs is a backport of the PEP 362 function signature features from Python
- 3.3's inspect module. The backport is compatible with Python 2.6, 2.7 as well
- as 3.2 and up.
- .
- This package contains the Python 2.7 module.
-
Package: python-funcsigs-doc
Section: doc
Architecture: all
diff -Nru python-funcsigs-1.0.2/debian/rules python-funcsigs-1.0.2/debian/rules
--- python-funcsigs-1.0.2/debian/rules 2018-02-27 12:43:35.0 +
+++ python-funcsigs-1.0.2/debian/rules 2020-04-30 21:43:30.0 +
@@ -1,19 +1,14 @@
#!/usr/bin/make -f
-PYTHONS:=$(shell pyversions -vr)
PYTHON3S:=$(shell py3versions -vr)
UPSTREAM_GIT := https://github.com/testing-cabal/funcsigs.git
-include /usr/share/openstack-pkg-tools/pkgos.make
%:
- dh $@ --buildsystem=python_distutils --with
python2,python3,pypy,sphinxdoc
+ dh $@ --buildsystem=pybuild --with python3,pypy,sphinxdoc
override_dh_auto_install:
- set -e ; for pyvers in $(PYTHONS); do \
- python$$pyvers setup.py install --install-layout=deb \
- --root $(CURDIR)/debian/python-funcsigs; \
- done
set -e ; for pyvers in $(PYTHON3S); do \
python$$pyvers setup.py install --install-layout=deb \
--root $(CURDIR)/debian/python3-funcsigs; \
@@ -24,7 +19,7 @@
override_dh_auto_test:
ifeq (,$(findstring nocheck, $(DEB_BUILD_OPTIONS)))
- set -e ; for pyvers in $(PYTHONS) $(PYTHON3S); do \
+ set -e ; for pyvers in $(PYTHON3S); do \
Bug#959828: systemctl: `Provides: systemd`, but doesn't provide what systemd does
On Thu, May 07, 2020 at 09:48:34PM +1000, Dmitry Smirnov wrote: > On Thursday, 7 May 2020 7:04:17 PM AEST Julien Cristau wrote: > > This use of Provides is not acceptable. The systemctl package does not > > in any way provide the same functionality / interfaces as the systemd > > package, and as such it does not get to pretend that it does and cause > > problems to other packages. > > I have to challenge that. "systemctl" provides enough functionality to > replace "systemd" inside application containers. Therefore there are > situations where "Provides: systemd" is justified. > That's not what "Provides" means though. What you're saying is "systemctl provides a subset of the systemd package's functionality". That's not good enough. Provides is much stronger than "there are cases where this might be enough", and there's more to systemd than systemctl. Also, per policy §3.6, virtual packages outside the defined agreed-upon names should only be used "amongst a cooperating group of packages". It seems clear to me this is neither of those cases. You're welcome to try and convince either the systemd maintainers to split some of the functionality to separate binary packages, or the php-fpm maintainer to forgo using functionality that is only available in systemd, but abusing package relationships the way you're doing now is just not on. Cheers, Julien
Bug#959973: pgcli: does not work due to prompt_toolkit incompatibility
Package: pgcli
Version: 2.2.0-4
Severity: grave
Justification: renders package unusable
```
borisov@glossy:~ $ pgcli
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 584, in
_build_master
ws.require(__requires__)
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 901, in
require
needed = self.resolve(parse_requirements(requirements))
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 792, in
resolve
raise VersionConflict(dist, req).with_context(dependent_req)
pkg_resources.ContextualVersionConflict: (prompt-toolkit 3.0.5
(/usr/lib/python3/dist-packages),
Requirement.parse('prompt_toolkit<3.0.0,>=2.0.6'), {'pgcli'})
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/bin/pgcli", line 6, in
from pkg_resources import load_entry_point
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3259,
in
def _initialize_master_working_set():
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3242,
in _call_aside
f(*args, **kwargs)
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3271,
in _initialize_master_working_set
working_set = WorkingSet._build_master()
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 586, in
_build_master
return cls._build_from_requirements(__requires__)
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 599, in
_build_from_requirements
dists = ws.resolve(reqs, Environment())
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 787, in
resolve
raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'prompt_toolkit<3.0.0,>=2.0.6'
distribution was not found and is required by pgcli
```
```
borisov@glossy:~ $ sudo aptitude install python3-prompt-toolkit
[sudo] password for borisov:
python3-prompt-toolkit is already installed at the requested version (3.0.5-2)
python3-prompt-toolkit is already installed at the requested version (3.0.5-2)
No packages will be installed, upgraded, or removed.
0 packages upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
Need to get 0 B of archives. After unpacking 0 B will be used.
```
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.6.0-1-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages pgcli depends on:
ii python3 3.8.2-3
ii python3-click 7.0-3
ii python3-configobj 5.0.6-4
ii python3-humanize2.3.0-1
ii python3-pgspecial 1.9.0-2
ii python3-pkg-resources 46.1.3-1
ii python3-prompt-toolkit 3.0.5-2
ii python3-psycopg22.8.5-1
ii python3-pygments2.3.1+dfsg-3
ii python3-setproctitle1.1.10-1+b4
ii python3-sqlparse0.3.1-1
ii python3-tabulate0.8.2-1.1
ii python3-terminaltables 3.1.0-3
pgcli recommends no packages.
pgcli suggests no packages.
-- no debconf information
Processed: Re: Bug#959937: tomcat9: update to tomcat9:amd64 9.0.31-1~deb10u1 breaks application
Processing control commands: > severity -1 normal Bug #959937 [tomcat9] tomcat9: update to tomcat9:amd64 9.0.31-1~deb10u1 breaks application Severity set to 'normal' from 'grave' -- 959937: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959937 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#959937: tomcat9: update to tomcat9:amd64 9.0.31-1~deb10u1 breaks application
Control: severity -1 normal Am 07.05.20 um 17:58 schrieb Michael Meier: [...] > The application doesn't use ajp. > > The sense of using unattended-upgrades and debian stable (no breaking > changes on updates) is not to read each security announcement in before. > > I'm not working in an area, where anybody would (be able to) pay for that. It is not feasible to detect any possible incompatibility beforehand because it heavily depends on the apps in use. Debian stable updates work 99% of the time without major issues but there will never be a 100% success rate because some problems are unrelated or simply not under Debian control. Setting up a test server before deploying updates to a production environment is the way to go here. >> If that does not solve your problem, then we need more information about >> your setup and configuration to debug the problem but note that we ship >> the latest upstream version basically unmodified, so this would be most >> likely an upstream bug. > > I could trace it back to the zk library used: > > https://bz.apache.org/bugzilla/show_bug.cgi?id=64097 > > https://tracker.zkoss.org/browse/ZK-4510 > > That seems to be a really really weird bug. If I understand it > correctly, it's the fault of zk, but I'm not 100% sure. > > Anyway, as it seems if I manage to update the project to the new zk > major version, it's supposed to work again. Ok, as I previously thought, it is an upstream bug but not in Tomcat itself but in el-api. Updating the zk library for your app might resolve the issue. I wonder if we need to upgrade src:el-api in Debian too. I think it is best when Emmanuel Bourg chimes in here. Regards, Markus signature.asc Description: OpenPGP digital signature
Bug#958414: Latest equivs version 2.3.0 breaks mk-build-deps
Hi Axel,
Quoting Axel Beckert (2020-05-07 15:45:12)
> > bisection finished successfully
> > last good timestamp: 2020-04-19 06:52:31.476563+02:00
> > first bad timestamp: 2020-04-19 10:35:09.156250+02:00
> > only one package differs: equivs is the culprit
> Yeah, but we know that already. I still haven't understood what exactly
> causes this issue.
sorry, me writing this was not supposed to come across as "I think that you are
wrong, so here is further evidence that I'm right". Instead, all I knew was
what was written by Otto and (same as myself) Otto wasn't sure whether this was
a bug in equivs or something else. So what I wanted to say was "this problem
indeed only started happening once the new equivs version got uploaded".
> If it's similar as with mk-ci-build-deps above, this is likely a bug in
> mk-build-deps then, just triggered by equivs.
Again, I don't want to be confrontational here. I don't understand as much
about equivs as you do. But what I tested is completely independent from
mk-build-deps. What I tried was running:
equivs-build /usr/share/doc/equivs/examples/webserver.ctl
And I got the same error as Otto ("Unmet build dependencies:
build-essential:native") -- even when I tried with all the other control files
in the examples directory. So if the bug is indeed not in equivs, then there
must be a bug in the control files?
Sorry if I came across as confrontational -- that was not my intention. Please
ignore this mail in case I still didn't manage to make sense.
Thanks!
cheers, josch
signature.asc
Description: signature
Bug#959937: tomcat9: update to tomcat9:amd64 9.0.31-1~deb10u1 breaks application
On 07.05.20 06:31, Markus Koschany wrote:
Am 07.05.20 um 10:04 schrieb Michael Meier:
Package: tomcat9
Version: 9.0.16-4
Severity: grave
Justification: renders package unusable
I've just been called out of bed.
As it seems unattended-upgrades upgraded on a debian buster server
from:9.0.16-4 to 9.0.31-1~deb10u1
One of the installed webapps throws following error when trying to use it:
[https-openssl-nio-8443-exec-13] ERROR org.zkoss.zk.ui.metainfo.Property -
Failed to assign [value=${i18n:rt('Benutzername')}] to
Unable to find ExpressionFactory of type: # Licensed to the Apache Software
Foundation (ASF) under one or more
Downgrading to 9.0.16-4 solves the issue.
Have you read the changelog or the Debian security announcement before
upgrading Tomcat 9 ? Does your application require the AJP protocol to
work? Then you probably need to slightly change your Tomcat
configuration. For more information please also refer to the official
documentation at
https://tomcat.apache.org/tomcat-9.0-doc/config/ajp.html
The application doesn't use ajp.
The sense of using unattended-upgrades and debian stable (no breaking
changes on updates) is not to read each security announcement in before.
I'm not working in an area, where anybody would (be able to) pay for that.
If that does not solve your problem, then we need more information about
your setup and configuration to debug the problem but note that we ship
the latest upstream version basically unmodified, so this would be most
likely an upstream bug.
I could trace it back to the zk library used:
https://bz.apache.org/bugzilla/show_bug.cgi?id=64097
https://tracker.zkoss.org/browse/ZK-4510
That seems to be a really really weird bug. If I understand it
correctly, it's the fault of zk, but I'm not 100% sure.
Anyway, as it seems if I manage to update the project to the new zk
major version, it's supposed to work again.
Processed (with 1 error): forcibly merging 959064 959960
Processing commands for cont...@bugs.debian.org: > forcemerge 959064 959960 Bug #959064 [cmake] cmake breaks on -isystem Unable to merge bugs because: package of #959960 is 'src:ignition-transport' not 'cmake' Failed to forcibly merge 959064: Did not alter merged bugs. > thanks Stopping processing here. Please contact me if you need assistance. -- 959064: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959064 959960: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959960 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 1 error): merging 959064 959960
Processing commands for cont...@bugs.debian.org: > merge 959064 959960 Bug #959064 [cmake] cmake breaks on -isystem Unable to merge bugs because: forwarded of #959960 is '' not 'https://gitlab.kitware.com/cmake/cmake/-/issues/20652' affects of #959960 is '' not 'ignition-transport' package of #959960 is 'src:ignition-transport' not 'cmake' Failed to merge 959064: Did not alter merged bugs. > thanks Stopping processing here. Please contact me if you need assistance. -- 959064: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959064 959960: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959960 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: py2removal bugs severity updates - 2020-05-07 15:35:09.790170+00:00
Processing commands for cont...@bugs.debian.org: > # This is an automated script, part of the effort for the removal of Python 2 > from bullseye > # * https://wiki.debian.org/Python/2Removal > # * http://sandrotosi.me/debian/py2removal/index.html > # See https://lists.debian.org/debian-devel-announce/2019/11/msg0.html > # and https://lists.debian.org/debian-python/2019/12/msg00076.html > # and https://lists.debian.org/debian-python/2020/03/msg00087.html > # mail threads for more details on this severity update > # python-flexmock is a module and has 0 external rdeps or not in testing > severity 937762 serious Bug #937762 [src:python-flexmock] python-flexmock: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > # php-sabre-dav is an application, has low popcon (455 <= 1000), and has 0 > external rdeps or not in testing > severity 943210 serious Bug #943210 [src:php-sabredav] php-sabredav: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > # python-pysam is a module and has 0 external rdeps or not in testing > severity 938092 serious Bug #938092 [src:python-pysam] python-pysam: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > # python-setproctitle is a module and has 0 external rdeps or not in testing > severity 938166 serious Bug #938166 [src:python-setproctitle] python-setproctitle: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > End of message, stopping processing here. Please contact me if you need assistance. -- 937762: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937762 938092: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938092 938166: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938166 943210: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943210 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#959828: systemctl: `Provides: systemd`, but doesn't provide what systemd does
I can see both php-fpm and systemctl maintainers have good reasons to do what they did. So taking one step back, does it make sense to dpkg-divert /usr/bin/systemctl?
Bug#959684: [cveh...@saltstack.com] Action Required: SaltStack CVE Follow-Up Patch
Hi Salvatore and others, * Salvatore Bonaccorso [2020-05-06 13:09 +0200]: > Hi Elimar, > > On Wed, May 06, 2020 at 10:36:42AM +0200, Elimar Riesebieter wrote: > > Hi all, > > > > please notice the attached note from saltstack! I assume this is not > > integrated into DSA 4676-1, isn't it? > > Yes this is right, those parts were missing. > > Do you have possibility to test updated salt packages for stretch? we fired up your kindly provided deb9u4 packages and run the verification script http://em.saltstack.com/F1sH900oN0P0M17U000Qhf7 with the following result: CVE-2020-11651 - OK CVE-2020-11652 - OK Thanks for cooperation Elimar -- Never make anything simple and efficient when a way can be found to make it complex and wonderful ;-)
Bug#959189: marked as done (bbswitch-dkms: fails to build for kernel 5.6.7)
Your message dated Thu, 07 May 2020 14:33:51 +
with message-id
and subject line Bug#959189: fixed in bbswitch 0.8-9
has caused the Debian Bug report #959189,
regarding bbswitch-dkms: fails to build for kernel 5.6.7
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.)
--
959189: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959189
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bbswitch-dkms
Version: 0.8-8
Severity: important
Dear Maintainer,
with the recent release on sid of the new linux kernel 5.6.7, I stumbled on
a problem with the bbswitch module, which fails to build with the following
error message:
make[1]: ingresso nella directory "/usr/src/linux-source-5.6.7.1"
CC [M] /var/lib/dkms/bbswitch/0.8/build/bbswitch.o
/var/lib/dkms/bbswitch/0.8/build/bbswitch.c: In function ‘bbswitch_init’:
/var/lib/dkms/bbswitch/0.8/build/bbswitch.c:460:63: error: passing argument 4
of ‘proc_create’ from incompatible pointer type
[-Werror=incompatible-pointer-types]
460 | acpi_entry = proc_create("bbswitch", 0664, acpi_root_dir,
&bbswitch_fops);
|
^~
| |
| struct
file_operations *
In file included from ./include/acpi/acpi_bus.h:83,
from ./include/linux/acpi.h:32,
from /var/lib/dkms/bbswitch/0.8/build/bbswitch.c:32:
./include/linux/proc_fs.h:64:24: note: expected ‘const struct proc_ops *’ but
argument is of type ‘struct file_operations *’
64 | struct proc_dir_entry *proc_create(const char *name, umode_t mode,
struct proc_dir_entry *parent, const struct proc_ops *proc_ops);
|^~~
Apparently some structures changed in the new kernel, making it incompatible
with bbswitch.
Of course, it still builds and works on 5.5.x and older kernels, but still,
since 5.6.x is now the default on sid I think this should be tagged important.
Thanks in advance, best regards
Giacomo Mulas
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (401, 'unstable'), (10, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.5.17-jak (SMP w/4 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8) (ignored: LC_ALL
set to it_IT.utf8), LANGUAGE=it_IT,en_EN (charmap=UTF-8) (ignored: LC_ALL set
to it_IT.utf8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages bbswitch-dkms depends on:
ii dkms 2.8.1-5
bbswitch-dkms recommends no packages.
Versions of packages bbswitch-dkms suggests:
ii bumblebee 3.2.1-22
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: bbswitch
Source-Version: 0.8-9
Done: Andreas Beckmann
We believe that the bug you reported is fixed in the latest version of
bbswitch, 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 959...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Beckmann (supplier of updated bbswitch 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, 07 May 2020 15:59:02 +0200
Source: bbswitch
Architecture: source
Version: 0.8-9
Distribution: unstable
Urgency: medium
Maintainer: Debian NVIDIA Maintainers
Changed-By: Andreas Beckmann
Closes: 842964 959189
Changes:
bbswitch (0.8-9) unstable; urgency=medium
.
* Add proposed upstream patch for Linux 5.6 support. (Closes: #959189)
* Run clean target against the kernel version used for building.
* Switch to debhelper-compat (= 13).
* Update Standards version to 4.5.0, no changes required.
* Declare Testsuite: autopkgtest-pkg-dkms.
* Restrict to architectures with the nvidia binary driver. (Closes: #842964)
* Add upstream metadata URLs.
* Add myself to Uploaders.
Checksums-Sha1:
87e262e82338da4ec05974ad686c5d876f7f2680 2253 bbswitch_0.8-9.dsc
Bug#959962: Missing dependencies?
Package: virt-p2v Version: 1.42.0-1 Severity: serious Hello, virt-p2v has no dependencies defined, but quickly looking which external tools it's using it should IMVHO at least requires the following dependencies: xz-utils for xzcat binutils for strip libguestfs-tools for virt-builder It's also using bash and gzip but these are essentials and should probably not be added to the dependencies. Kind regards, Laurent Bigonville -- System Information: Debian Release: bullseye/sid 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 5.5.0-2-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy
Bug#959961: Prefix not properly set?
Package: virt-p2v Version: 1.42.0-1 Severity: grave Hi, When running virt-p2v-make-disk or virt-p2v-make-kiwi, I get the folowing errors: # virt-p2v-make-disk -o plop virt-p2v-make-disk: cannot find /lib/x86_64-linux-gnu/virt-p2v/virt-p2v.xz # virt-p2v-make-kiwi /usr/bin/virt-p2v-make-kiwi: cannot find dependencies file (/share/virt-p2v/dependencies.suse) The files are installed under /usr/lib/x86_64-linux-gnu/virt-p2v/virt-p2v.xz and /usr/share/virt-p2v/dependencies.suse. Looks like the prefix is not properly set Kind regards, Laurent Bigonville -- System Information: Debian Release: bullseye/sid 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 5.5.0-2-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy
Bug#958414: Latest equivs version 2.3.0 breaks mk-build-deps
Hi Josch, thanks for bringing this to my attention. It seems as if I have overseen Otto's bug report wen it came in two weeks ago. (Sorry, Otto.) Johannes Schauer wrote: > Otto Kekäläinen wrote: > > I am pretty sure this is related to the recent equivs 2.3.0 release, > > but I have not figured out the details yet. Some things have changed slightly in equivs and might need adaptions in scripts using them where they make assumptions never guaranteed and now no more true, like that only a .deb file is produced. E.g. now it also produces .changes and .buildinfo files, see e.g. https://salsa.debian.org/salsa-ci-team/pipeline/-/issues/154 > bisection finished successfully > last good timestamp: 2020-04-19 06:52:31.476563+02:00 > first bad timestamp: 2020-04-19 10:35:09.156250+02:00 > only one package differs: equivs is the culprit Yeah, but we know that already. I still haven't understood what exactly causes this issue. If it's similar as with mk-ci-build-deps above, this is likely a bug in mk-build-deps then, just triggered by equivs. > Notice that the test-command executes equivs-build with one of the provided > examples (webserver.ctl), so the problem is not mk-build-deps specific. Ok, will have a look at this closer. > I wrote an autopkgtest which also demonstrates the problem: > > https://salsa.debian.org/perl-team/modules/packages/equivs/-/merge_requests/5 Will likely merge it once I've understood the cause of issue. Thanks for the test! 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#933439: amule: Please rebuild against wxWidgets GTK 3 package
On Wed, 6 May 2020, Sandro Tosi wrote: Any update on moving amule to use libwxgtk3.0-gtk3-dev? amule is one of the last couple of packages keeping the gtk2 wx package in unstable (as cruft). We keep getting bug reports about those cruft packages periodically. Sadly no: upstream hasnt ported amule to WX GTK3 and it doesnt look like it's gonna happen anytime soon (help with the port is of course welcome, probably better to sync upstream if someone wants to lend a hand) so feel free to ask FTP Masters to force the decruft Does the crash you referenced here require connecting to file sharing networks to reproduce? Scott
Bug#959364: marked as done (acpi-call-dkms: fails to build on kernel 5.6)
Your message dated Thu, 07 May 2020 13:18:30 +
with message-id
and subject line Bug#959729: fixed in acpi-call 1.1.0-6
has caused the Debian Bug report #959729,
regarding acpi-call-dkms: fails to build on kernel 5.6
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
959729: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959729
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: acpi-call-dkms
Version: 1.1.0-5
Severity: serious
Tags: patch ftbfs
Justification: fails to build from source
Dear Maintainer,
Building modules for kernel 5.6.0-1-amd64 fails with
error: passing argument 4 of ‘proc_create’ from incompatible pointer type
[...]
expected ‘const struct proc_ops *’ but argument is of type ‘struct
file_operations *’
This seems to be due to a kernel change from earlier this year:
https://github.com/torvalds/linux/commit/97a32539b9568bb653683349e5a76d02ff3c3e2c
It can be naively be fixed by applying the changes suggested in that commit,
in acpi_call.c:321 changing :
static struct file_operations proc_acpi_operations = {
.owner= THIS_MODULE,
.read = acpi_proc_read,
.write= acpi_proc_write,
};
to
static struct proc_ops proc_acpi_operations={
.proc_read = acpi_proc_read,
.proc_write = acpi_proc_write,
};
Which seems to fix the build for 5.6. It probably breaks it for kernels older
than 5.6,
so it would need some conditionals.
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (900, 'testing'), (500, 'stable-updates'), (500,
'oldstable-updates'), (500, 'stable'), (500, 'oldstable'), (50,
'experimental'), (50, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.6.0-1-amd64 (SMP w/2 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8),
LANGUAGE=en_IE:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages acpi-call-dkms depends on:
ii dkms 2.8.1-5
acpi-call-dkms recommends no packages.
acpi-call-dkms suggests no packages.
-- no debconf information
-- debsums errors found:
debsums: changed file /usr/src/acpi-call-1.1.0/acpi_call.c (from acpi-call-dkms
package)
--- End Message ---
--- Begin Message ---
Source: acpi-call
Source-Version: 1.1.0-6
Done: =?utf-8?q?Rapha=C3=ABl_Halimi?=
We believe that the bug you reported is fixed in the latest version of
acpi-call, 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 959...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Raphaël Halimi (supplier of updated acpi-call
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, 07 May 2020 14:58:58 +0200
Source: acpi-call
Architecture: source
Version: 1.1.0-6
Distribution: unstable
Urgency: medium
Maintainer: Raphaël Halimi
Changed-By: Raphaël Halimi
Closes: 959364 959729
Changes:
acpi-call (1.1.0-6) unstable; urgency=medium
.
* [ce9dd75] Fix patches order (#3 was applied first)
* [01a2d16] Add patch to fix build on Linux 5.6.
Thanks to Nikita Knutov for the patch, Thomas Koch and Gard Spreemann for
pointing me to the patch (Closes: #959364, #959729)
* [6ca6f81] Bump Standards-Version to 4.5.0
* [f14a922] Bump debhelper compat to 12
* [93b030a] Silence lintian about spelling error (false positive)
Checksums-Sha1:
735929db994e1d1a0bb17376ec98c3665be16bf6 2007 acpi-call_1.1.0-6.dsc
dd0e307a6e51e180840f06e94e5abf34618ba657 4384 acpi-call_1.1.0-6.debian.tar.xz
7ed13adedd7f5eb45f91d6e5dde744498e7ccd4a 6157 acpi-call_1.1.0-6_amd64.buildinfo
Checksums-Sha256:
53c2acba82b70095667297d8ee53f85b6064faf20a60c6dd76f6cacbe44d22e8 2007
acpi-call_1.1.0-6.dsc
087cc98902f2e7412876b08a6447f129a6836a3751794cb25acb54fd8ca2489e 4384
acpi-call_1.1.0-6.debian.tar.xz
6ed9542dfb8b1fc8a8507155c7d82a1467b5d1c6c70f518b18d7b6345dbf8e20 6157
acpi-call_1.1.0-6_amd64.buildinfo
Files:
69d1aee29507e5635d9869bfe8a87421 2007 kernel optional acpi-call_1.1.0-6.dsc
e2813dacbc87d4ae73b136d4ef9728e4 4384
Bug#959729: marked as done (Build error with kernel 5.6)
Your message dated Thu, 07 May 2020 13:18:30 +
with message-id
and subject line Bug#959729: fixed in acpi-call 1.1.0-6
has caused the Debian Bug report #959729,
regarding Build error with kernel 5.6
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
959729: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959729
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: acpi-call-dkms
Version: 1.1.0-5
Hi Raphael,
make.log says:
--
DKMS make.log for acpi-call-1.1.0 for kernel 5.6.0-1-amd64 (x86_64)
Mo 4. Mai 17:42:51 CEST 2020
make: Entering directory '/usr/src/linux-headers-5.6.0-1-amd64'
AR /var/lib/dkms/acpi-call/1.1.0/build/built-in.a
CC [M] /var/lib/dkms/acpi-call/1.1.0/build/acpi_call.o
/var/lib/dkms/acpi-call/1.1.0/build/acpi_call.c: In function
‘init_acpi_call’:
/var/lib/dkms/acpi-call/1.1.0/build/acpi_call.c:356:53: error: passing
argument 4 of ‘proc_create’ from incompatible pointer type
[-Werror=incompatible-pointer-types]
356 |
&proc_acpi_operations);
|
^
| |
| struct
file_operations *
In file included from /var/lib/dkms/acpi-call/1.1.0/build/acpi_call.c:6:
/usr/src/linux-headers-5.6.0-1-common/include/linux/proc_fs.h:64:24:
note: expected ‘const struct proc_ops *’ but argument is of type ‘struct
file_operations *’
64 | struct proc_dir_entry *proc_create(const char *name, umode_t
mode, struct proc_dir_entry *parent, const struct proc_ops *proc_ops);
|^~~
cc1: some warnings being treated as errors
make[2]: ***
[/usr/src/linux-headers-5.6.0-1-common/scripts/Makefile.build:273:
/var/lib/dkms/acpi-call/1.1.0/build/acpi_call.o] Error 1
make[1]: *** [/usr/src/linux-headers-5.6.0-1-common/Makefile:1696:
/var/lib/dkms/acpi-call/1.1.0/build] Error 2
make: *** [/usr/src/linux-headers-5.6.0-1-common/Makefile:180: sub-make]
Error 2
make: Leaving directory '/usr/src/linux-headers-5.6.0-1-amd64'
--
Patch is attached. For good measure it is also backwards compatible with
kernels < 5.6.
--
Freundliche Grüße / Kind regards,
Thomas Koch
--- acpi_call.c-orig 2020-05-04 13:25:32.691890015 +0200
+++ acpi_call.c 2020-05-04 13:30:48.732403548 +0200
@@ -317,11 +317,18 @@
return ret;
}
+#if LINUX_VERSION_CODE >= KERNEL_VERSION(5, 6, 0)
+static struct proc_ops proc_acpi_operations = {
+.proc_read = acpi_proc_read,
+.proc_write = acpi_proc_write,
+};
+#else
static struct file_operations proc_acpi_operations = {
.owner= THIS_MODULE,
.read = acpi_proc_read,
.write= acpi_proc_write,
};
+#endif
#else
static int acpi_proc_read(char *page, char **start, off_t off,
DKMS make.log for acpi-call-1.1.0 for kernel 5.6.0-1-amd64 (x86_64)
Mo 4. Mai 17:42:51 CEST 2020
make: Entering directory '/usr/src/linux-headers-5.6.0-1-amd64'
AR /var/lib/dkms/acpi-call/1.1.0/build/built-in.a
CC [M] /var/lib/dkms/acpi-call/1.1.0/build/acpi_call.o
/var/lib/dkms/acpi-call/1.1.0/build/acpi_call.c: In function ‘init_acpi_call’:
/var/lib/dkms/acpi-call/1.1.0/build/acpi_call.c:356:53: error: passing argument 4 of ‘proc_create’ from incompatible pointer type [-Werror=incompatible-pointer-types]
356 | &proc_acpi_operations);
| ^
| |
| struct file_operations *
In file included from /var/lib/dkms/acpi-call/1.1.0/build/acpi_call.c:6:
/usr/src/linux-headers-5.6.0-1-common/include/linux/proc_fs.h:64:24: note: expected ‘const struct proc_ops *’ but argument is of type ‘struct file_operations *’
64 | struct proc_dir_entry *proc_create(const char *name, umode_t mode, struct proc_dir_entry *parent, const struct proc_ops *proc_ops);
|^~~
cc1: some warnings being treated as errors
make[2]: *** [/usr/src/linux-headers-5.6.0-1-common/scripts/Makefile.build:273: /var/lib/dkms/acpi-call/1.1.0/build/acpi_call.o] Error 1
make[1]: *** [/usr/src/linux-headers-5.6.0-1-common/Makefile:1696: /var/lib/dkms/acpi-call/1.1.0/build] Error 2
make: *** [/usr/src/linux-headers-5.6.0-1-common/Makefile:180: sub-make] Error 2
make: Leaving directory '/usr/src/linux-headers-5.6.0-
Bug#959729: marked as done (Build error with kernel 5.6)
Your message dated Thu, 07 May 2020 13:18:30 +
with message-id
and subject line Bug#959364: fixed in acpi-call 1.1.0-6
has caused the Debian Bug report #959364,
regarding Build error with kernel 5.6
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
959364: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959364
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: acpi-call-dkms
Version: 1.1.0-5
Hi Raphael,
make.log says:
--
DKMS make.log for acpi-call-1.1.0 for kernel 5.6.0-1-amd64 (x86_64)
Mo 4. Mai 17:42:51 CEST 2020
make: Entering directory '/usr/src/linux-headers-5.6.0-1-amd64'
AR /var/lib/dkms/acpi-call/1.1.0/build/built-in.a
CC [M] /var/lib/dkms/acpi-call/1.1.0/build/acpi_call.o
/var/lib/dkms/acpi-call/1.1.0/build/acpi_call.c: In function
‘init_acpi_call’:
/var/lib/dkms/acpi-call/1.1.0/build/acpi_call.c:356:53: error: passing
argument 4 of ‘proc_create’ from incompatible pointer type
[-Werror=incompatible-pointer-types]
356 |
&proc_acpi_operations);
|
^
| |
| struct
file_operations *
In file included from /var/lib/dkms/acpi-call/1.1.0/build/acpi_call.c:6:
/usr/src/linux-headers-5.6.0-1-common/include/linux/proc_fs.h:64:24:
note: expected ‘const struct proc_ops *’ but argument is of type ‘struct
file_operations *’
64 | struct proc_dir_entry *proc_create(const char *name, umode_t
mode, struct proc_dir_entry *parent, const struct proc_ops *proc_ops);
|^~~
cc1: some warnings being treated as errors
make[2]: ***
[/usr/src/linux-headers-5.6.0-1-common/scripts/Makefile.build:273:
/var/lib/dkms/acpi-call/1.1.0/build/acpi_call.o] Error 1
make[1]: *** [/usr/src/linux-headers-5.6.0-1-common/Makefile:1696:
/var/lib/dkms/acpi-call/1.1.0/build] Error 2
make: *** [/usr/src/linux-headers-5.6.0-1-common/Makefile:180: sub-make]
Error 2
make: Leaving directory '/usr/src/linux-headers-5.6.0-1-amd64'
--
Patch is attached. For good measure it is also backwards compatible with
kernels < 5.6.
--
Freundliche Grüße / Kind regards,
Thomas Koch
--- acpi_call.c-orig 2020-05-04 13:25:32.691890015 +0200
+++ acpi_call.c 2020-05-04 13:30:48.732403548 +0200
@@ -317,11 +317,18 @@
return ret;
}
+#if LINUX_VERSION_CODE >= KERNEL_VERSION(5, 6, 0)
+static struct proc_ops proc_acpi_operations = {
+.proc_read = acpi_proc_read,
+.proc_write = acpi_proc_write,
+};
+#else
static struct file_operations proc_acpi_operations = {
.owner= THIS_MODULE,
.read = acpi_proc_read,
.write= acpi_proc_write,
};
+#endif
#else
static int acpi_proc_read(char *page, char **start, off_t off,
DKMS make.log for acpi-call-1.1.0 for kernel 5.6.0-1-amd64 (x86_64)
Mo 4. Mai 17:42:51 CEST 2020
make: Entering directory '/usr/src/linux-headers-5.6.0-1-amd64'
AR /var/lib/dkms/acpi-call/1.1.0/build/built-in.a
CC [M] /var/lib/dkms/acpi-call/1.1.0/build/acpi_call.o
/var/lib/dkms/acpi-call/1.1.0/build/acpi_call.c: In function ‘init_acpi_call’:
/var/lib/dkms/acpi-call/1.1.0/build/acpi_call.c:356:53: error: passing argument 4 of ‘proc_create’ from incompatible pointer type [-Werror=incompatible-pointer-types]
356 | &proc_acpi_operations);
| ^
| |
| struct file_operations *
In file included from /var/lib/dkms/acpi-call/1.1.0/build/acpi_call.c:6:
/usr/src/linux-headers-5.6.0-1-common/include/linux/proc_fs.h:64:24: note: expected ‘const struct proc_ops *’ but argument is of type ‘struct file_operations *’
64 | struct proc_dir_entry *proc_create(const char *name, umode_t mode, struct proc_dir_entry *parent, const struct proc_ops *proc_ops);
|^~~
cc1: some warnings being treated as errors
make[2]: *** [/usr/src/linux-headers-5.6.0-1-common/scripts/Makefile.build:273: /var/lib/dkms/acpi-call/1.1.0/build/acpi_call.o] Error 1
make[1]: *** [/usr/src/linux-headers-5.6.0-1-common/Makefile:1696: /var/lib/dkms/acpi-call/1.1.0/build] Error 2
make: *** [/usr/src/linux-headers-5.6.0-1-common/Makefile:180: sub-make] Error 2
make: Leaving directory '/usr/src/linux-headers-5.6.0-
Bug#959364: marked as done (acpi-call-dkms: fails to build on kernel 5.6)
Your message dated Thu, 07 May 2020 13:18:30 +
with message-id
and subject line Bug#959364: fixed in acpi-call 1.1.0-6
has caused the Debian Bug report #959364,
regarding acpi-call-dkms: fails to build on kernel 5.6
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
959364: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959364
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: acpi-call-dkms
Version: 1.1.0-5
Severity: serious
Tags: patch ftbfs
Justification: fails to build from source
Dear Maintainer,
Building modules for kernel 5.6.0-1-amd64 fails with
error: passing argument 4 of ‘proc_create’ from incompatible pointer type
[...]
expected ‘const struct proc_ops *’ but argument is of type ‘struct
file_operations *’
This seems to be due to a kernel change from earlier this year:
https://github.com/torvalds/linux/commit/97a32539b9568bb653683349e5a76d02ff3c3e2c
It can be naively be fixed by applying the changes suggested in that commit,
in acpi_call.c:321 changing :
static struct file_operations proc_acpi_operations = {
.owner= THIS_MODULE,
.read = acpi_proc_read,
.write= acpi_proc_write,
};
to
static struct proc_ops proc_acpi_operations={
.proc_read = acpi_proc_read,
.proc_write = acpi_proc_write,
};
Which seems to fix the build for 5.6. It probably breaks it for kernels older
than 5.6,
so it would need some conditionals.
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (900, 'testing'), (500, 'stable-updates'), (500,
'oldstable-updates'), (500, 'stable'), (500, 'oldstable'), (50,
'experimental'), (50, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.6.0-1-amd64 (SMP w/2 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8),
LANGUAGE=en_IE:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages acpi-call-dkms depends on:
ii dkms 2.8.1-5
acpi-call-dkms recommends no packages.
acpi-call-dkms suggests no packages.
-- no debconf information
-- debsums errors found:
debsums: changed file /usr/src/acpi-call-1.1.0/acpi_call.c (from acpi-call-dkms
package)
--- End Message ---
--- Begin Message ---
Source: acpi-call
Source-Version: 1.1.0-6
Done: =?utf-8?q?Rapha=C3=ABl_Halimi?=
We believe that the bug you reported is fixed in the latest version of
acpi-call, 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 959...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Raphaël Halimi (supplier of updated acpi-call
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, 07 May 2020 14:58:58 +0200
Source: acpi-call
Architecture: source
Version: 1.1.0-6
Distribution: unstable
Urgency: medium
Maintainer: Raphaël Halimi
Changed-By: Raphaël Halimi
Closes: 959364 959729
Changes:
acpi-call (1.1.0-6) unstable; urgency=medium
.
* [ce9dd75] Fix patches order (#3 was applied first)
* [01a2d16] Add patch to fix build on Linux 5.6.
Thanks to Nikita Knutov for the patch, Thomas Koch and Gard Spreemann for
pointing me to the patch (Closes: #959364, #959729)
* [6ca6f81] Bump Standards-Version to 4.5.0
* [f14a922] Bump debhelper compat to 12
* [93b030a] Silence lintian about spelling error (false positive)
Checksums-Sha1:
735929db994e1d1a0bb17376ec98c3665be16bf6 2007 acpi-call_1.1.0-6.dsc
dd0e307a6e51e180840f06e94e5abf34618ba657 4384 acpi-call_1.1.0-6.debian.tar.xz
7ed13adedd7f5eb45f91d6e5dde744498e7ccd4a 6157 acpi-call_1.1.0-6_amd64.buildinfo
Checksums-Sha256:
53c2acba82b70095667297d8ee53f85b6064faf20a60c6dd76f6cacbe44d22e8 2007
acpi-call_1.1.0-6.dsc
087cc98902f2e7412876b08a6447f129a6836a3751794cb25acb54fd8ca2489e 4384
acpi-call_1.1.0-6.debian.tar.xz
6ed9542dfb8b1fc8a8507155c7d82a1467b5d1c6c70f518b18d7b6345dbf8e20 6157
acpi-call_1.1.0-6_amd64.buildinfo
Files:
69d1aee29507e5635d9869bfe8a87421 2007 kernel optional acpi-call_1.1.0-6.dsc
e2813dacbc87d4ae73b136d4ef9728e4 4384
Bug#959684: salt: CVE-2020-11652: [cveh...@saltstack.com] Action Required: SaltStack CVE Follow-Up Patch
Hi Salvatore, On Thu, 07 May 2020 at 08:18:34 +0200, Salvatore Bonaccorso wrote: > I would like to get some testing feedback on the stretch packages, if > you have such instance > https://people.debian.org/~carnil/tmp/salt/stretch/ contains testing > packages. Unfortunately I don't, would have been able to help with Buster (you were faster though ;-)) but I currently don't have a running stretch instance and won't find time to deploy one before the week-end. Cheers, -- Guilhem. signature.asc Description: PGP signature
Processed: Re: Latest equivs version 2.3.0 breaks mk-build-deps
Processing control commands: > severity -1 grave Bug #958414 [equivs] Latest equivs version 2.3.0 breaks mk-build-deps Severity set to 'grave' from 'normal' -- 958414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958414 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#959684: [External] Bug#959684: salt: CVE-2020-11652: [cveh...@saltstack.com] Action Required: SaltStack CVE Follow-Up Patch
Hi Graham, On Thu, May 07, 2020 at 11:25:00AM +0100, Graham Clinch wrote: > Hi, > > > I would like to get some testing feedback on the stretch packages, if > > you have such instance > > https://people.debian.org/~carnil/tmp/salt/stretch/ contains testing > > packages. > > These packages look good to me. > > I updated two stretch instances from 2016.11.2+ds-1+deb9u3 to > 2016.11.2+ds-1+deb9u4, for the following packages: > > salt-api, salt-common, salt-master, salt-minion. > > There were no errors during the update, and minions at various releases > (including 9u2, 9u3 and 9u4) connect to the salt master as expected. > > Additionally a test tool reports the deb9u4 master as not vulnerable (it > reported the deb9u3 master as vulnerable to 'read_token'). Thanks for testing those, much appreciated. I will send out the followup advisory with the fixed packages later today. Regards, Salvatore
Bug#959955: libsis-jhdf5-jni: ships /usr/lib/jni/libjhdf5.so already provided by libjhdf5-jni
Package: libsis-jhdf5-jni Version: 19.04.0+dfsg-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../libsis-jhdf5-jni_19.04.0+dfsg-1_amd64.deb ... Unpacking libsis-jhdf5-jni (19.04.0+dfsg-1) ... dpkg: error processing archive /var/cache/apt/archives/libsis-jhdf5-jni_19.04.0+dfsg-1_amd64.deb (--unpack): trying to overwrite '/usr/lib/jni/libjhdf5.so', which is also in package libjhdf5-jni 2.11.0+dfsg-4 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/libsis-jhdf5-jni_19.04.0+dfsg-1_amd64.deb cheers, Andreas libjhdf5-jni=2.11.0+dfsg-4_libsis-jhdf5-jni=19.04.0+dfsg-1.log.gz Description: application/gzip
Bug#959954: pyte: accesses internet during build?
Source: pyte Version: 0.8.0-1 Severity: serious Hello, in Ubuntu the network is more strictly disabled, and the package FTBFS I'm not sure if this is a change in sphinx or the new release dh_auto_build I: pybuild base:217: /usr/bin/python3 setup.py build running build running build_py creating /<>/.pybuild/cpython3_3.8/build/pyte copying pyte/compat.py -> /<>/.pybuild/cpython3_3.8/build/pyte copying pyte/graphics.py -> /<>/.pybuild/cpython3_3.8/build/pyte copying pyte/control.py -> /<>/.pybuild/cpython3_3.8/build/pyte copying pyte/__main__.py -> /<>/.pybuild/cpython3_3.8/build/pyte copying pyte/__init__.py -> /<>/.pybuild/cpython3_3.8/build/pyte copying pyte/charsets.py -> /<>/.pybuild/cpython3_3.8/build/pyte copying pyte/escape.py -> /<>/.pybuild/cpython3_3.8/build/pyte copying pyte/modes.py -> /<>/.pybuild/cpython3_3.8/build/pyte copying pyte/streams.py -> /<>/.pybuild/cpython3_3.8/build/pyte copying pyte/screens.py -> /<>/.pybuild/cpython3_3.8/build/pyte python3 -m sphinx -b html -d docs/build/doctrees docs docs/build/html Running Sphinx v2.4.3 Configuration error: There is a programmable error in your configuration file: Traceback (most recent call last): File "/usr/lib/python3.8/urllib/request.py", line 1326, in do_open h.request(req.get_method(), req.selector, req.data, headers, File "/usr/lib/python3.8/http/client.py", line 1240, in request self._send_request(method, url, body, headers, encode_chunked) File "/usr/lib/python3.8/http/client.py", line 1286, in _send_request self.endheaders(body, encode_chunked=encode_chunked) File "/usr/lib/python3.8/http/client.py", line 1235, in endheaders self._send_output(message_body, encode_chunked=encode_chunked) File "/usr/lib/python3.8/http/client.py", line 1006, in _send_output self.send(msg) File "/usr/lib/python3.8/http/client.py", line 946, in send self.connect() File "/usr/lib/python3.8/http/client.py", line 1402, in connect super().connect() File "/usr/lib/python3.8/http/client.py", line 917, in connect self.sock = self._create_connection( File "/usr/lib/python3.8/socket.py", line 787, in create_connection for res in getaddrinfo(host, port, 0, SOCK_STREAM): File "/usr/lib/python3.8/socket.py", line 918, in getaddrinfo for res in _socket.getaddrinfo(host, port, family, type, proto, flags): socket.gaierror: [Errno -2] Name or service not known During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/sphinx/config.py", line 348, in eval_config_file execfile_(filename, namespace) File "/usr/lib/python3/dist-packages/sphinx/util/pycompat.py", line 81, in execfile_ exec(code, _globals) File "/<>/docs/conf.py", line 106, in tag = resolve_tag() File "/<>/docs/conf.py", line 99, in resolve_tag urlopen(linkcode_base_url + release) File "/usr/lib/python3.8/urllib/request.py", line 222, in urlopen return opener.open(url, data, timeout) File "/usr/lib/python3.8/urllib/request.py", line 525, in open response = self._open(req, data) File "/usr/lib/python3.8/urllib/request.py", line 542, in _open result = self._call_chain(self.handle_open, protocol, protocol + File "/usr/lib/python3.8/urllib/request.py", line 502, in _call_chain result = func(*args) File "/usr/lib/python3.8/urllib/request.py", line 1369, in https_open return self.do_open(http.client.HTTPSConnection, req, File "/usr/lib/python3.8/urllib/request.py", line 1329, in do_open raise URLError(err) urllib.error.URLError: make[1]: *** [debian/rules:11: override_dh_auto_build] Error 2 make[1]: Leaving directory '/<>' make: *** [debian/rules:7: binary] Error 2 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 Build finished at 20200507-1159 looking at the diff of the new version, my guess is to blame the new resolve_tag function +linkcode_base_url = "https://github.com/selectel/pyte/tree/"; + +def resolve_tag(): +from urllib.request import urlopen +from urllib.error import HTTPError +try: +urlopen(linkcode_base_url + release) +except HTTPError: +return "master" +else: +return release + + +tag = resolve_tag() G.
Processed: Lower severity
Processing control commands: > severity -1 important Bug #956324 [clustalo] "clustalo: Bus error on mipsel" Severity set to 'important' from 'serious' -- 956324: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956324 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Lower severity
Processing control commands:
> severity -1 important
Bug #956828 {Done: Paul Gevers } [src:bedtools]
src:bedtools: fails to migrate to testing for too long: FTBFS on several archs
Severity set to 'important' from 'serious'
--
956828: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956828
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#956324: Lower severity
Control: severity -1 important The builds for the failed architectures are requested for removal. So the bug is set to severity important to move on with architectures that are used in practical applications without creating noise in form of lots of testing removal warnings of rdepends. Kind regards Andreas.
Bug#959828: systemctl: `Provides: systemd`, but doesn't provide what systemd does
On Thursday, 7 May 2020 7:04:17 PM AEST Julien Cristau wrote: > This use of Provides is not acceptable. The systemctl package does not > in any way provide the same functionality / interfaces as the systemd > package, and as such it does not get to pretend that it does and cause > problems to other packages. I have to challenge that. "systemctl" provides enough functionality to replace "systemd" inside application containers. Therefore there are situations where "Provides: systemd" is justified. Just like "runit" and "supervisor", "systemctl" is a niche package intended to be used in application containers. It makes little sense to install it to "normal" (default) systemd-managed system and attempt to do so would warn admin by prompt to uninstall "systemd". What is the problem with that? "systemctl" can be useful on SysV managed systems to start/stop services without SysV init scripts. These days Debian usability inside application containers should be our strategic goal that became much closer thanks to "systemctl" package. It is OK that we have have established "systemd" hegemony. But systemd is not an answer to everything and I feel that "systemctl" is being penalised for honest attempt to provide a semi-compatible "systemctl" interface. Obviously unlike "runit" and "supervisor", "systemctl" can not be installed side-by-side with "systemd" as that would be much worse than "Provides: systemd". Is there are any other options? > Please stop severity ping-pong on this. Not until I get an answer that make sense. -- Best wishes, Dmitry Smirnov. --- It is a fine thing to be honest, but it is also very important to be right. -- Winston Churchill signature.asc Description: This is a digitally signed message part.
Bug#959942: src:caffe: missing (unversioned) Breaks+Replaces: libcaffe-cpu1/libcaffe-cpu-dev/caffe-tools-cpu/python3-caffe-cpu
Followup-For: Bug #959942 Control: retitle -1 src:caffe: missing (unversioned) Breaks+Replaces: libcaffe-cpu1/libcaffe-cpu-dev/caffe-tools-cpu/python3-caffe-cpu I overlooked another occurrence in python3-caffe: Preparing to unpack .../libcaffe1_1.0.0+git20180821.99bd997-6_amd64.deb ... Unpacking libcaffe1:amd64 (1.0.0+git20180821.99bd997-6) ... dpkg: error processing archive /var/cache/apt/archives/libcaffe1_1.0.0+git20180821.99bd997-6_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libcaffe.so.1.0.0', which is also in package libcaffe-cpu1:amd64 1.0.0+git20180821.99bd997-5+b5 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Preparing to unpack .../python3-caffe_1.0.0+git20180821.99bd997-6_amd64.deb ... Unpacking python3-caffe (1.0.0+git20180821.99bd997-6) ... dpkg: error processing archive /var/cache/apt/archives/python3-caffe_1.0.0+git20180821.99bd997-6_amd64.deb (--unpack): trying to overwrite '/usr/lib/python3/dist-packages/caffe/__init__.py', which is also in package python3-caffe-cpu 1.0.0+git20180821.99bd997-5+b5 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/libcaffe1_1.0.0+git20180821.99bd997-6_amd64.deb /var/cache/apt/archives/python3-caffe_1.0.0+git20180821.99bd997-6_amd64.deb Andreas
Processed: Re: src:caffe: missing (unversioned) Breaks+Replaces: libcaffe-cpu1/libcaffe-cpu-dev/caffe-tools-cpu/python3-caffe-cpu
Processing control commands: > retitle -1 src:caffe: missing (unversioned) Breaks+Replaces: > libcaffe-cpu1/libcaffe-cpu-dev/caffe-tools-cpu/python3-caffe-cpu Bug #959942 [src:caffe] src:caffe: missing (unversioned) Breaks+Replaces: libcaffe-cpu1/libcaffe-cpu-dev/caffe-tools-cpu Changed Bug title to 'src:caffe: missing (unversioned) Breaks+Replaces: libcaffe-cpu1/libcaffe-cpu-dev/caffe-tools-cpu/python3-caffe-cpu' from 'src:caffe: missing (unversioned) Breaks+Replaces: libcaffe-cpu1/libcaffe-cpu-dev/caffe-tools-cpu'. -- 959942: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959942 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#959684: [External] Bug#959684: salt: CVE-2020-11652: [cveh...@saltstack.com] Action Required: SaltStack CVE Follow-Up Patch
Hi, I would like to get some testing feedback on the stretch packages, if you have such instance https://people.debian.org/~carnil/tmp/salt/stretch/ contains testing packages. These packages look good to me. I updated two stretch instances from 2016.11.2+ds-1+deb9u3 to 2016.11.2+ds-1+deb9u4, for the following packages: salt-api, salt-common, salt-master, salt-minion. There were no errors during the update, and minions at various releases (including 9u2, 9u3 and 9u4) connect to the salt master as expected. Additionally a test tool reports the deb9u4 master as not vulnerable (it reported the deb9u3 master as vulnerable to 'read_token'). Graham
Bug#959937: tomcat9: update to tomcat9:amd64 9.0.31-1~deb10u1 breaks application
Am 07.05.20 um 10:04 schrieb Michael Meier:
> Package: tomcat9
> Version: 9.0.16-4
> Severity: grave
> Justification: renders package unusable
>
> I've just been called out of bed.
> As it seems unattended-upgrades upgraded on a debian buster server
> from:9.0.16-4 to 9.0.31-1~deb10u1
> One of the installed webapps throws following error when trying to use it:
>
> [https-openssl-nio-8443-exec-13] ERROR org.zkoss.zk.ui.metainfo.Property -
> Failed to assign [value=${i18n:rt('Benutzername')}] to
> Unable to find ExpressionFactory of type: # Licensed to the Apache Software
> Foundation (ASF) under one or more
>
> Downgrading to 9.0.16-4 solves the issue.
Have you read the changelog or the Debian security announcement before
upgrading Tomcat 9 ? Does your application require the AJP protocol to
work? Then you probably need to slightly change your Tomcat
configuration. For more information please also refer to the official
documentation at
https://tomcat.apache.org/tomcat-9.0-doc/config/ajp.html
If that does not solve your problem, then we need more information about
your setup and configuration to debug the problem but note that we ship
the latest upstream version basically unmodified, so this would be most
likely an upstream bug.
Regards,
Markus Koschany
signature.asc
Description: OpenPGP digital signature
Processed: Re: Bug#959940: hdmf FTBFS with h5py 2.10.0
Processing control commands: > tags -1 upstream Bug #959940 [src:hdmf] hdmf FTBFS with h5py 2.10.0 Added tag(s) upstream. > forwarded -1 https://github.com/hdmf-dev/hdmf/issues/343 Bug #959940 [src:hdmf] hdmf FTBFS with h5py 2.10.0 Set Bug forwarded-to-address to 'https://github.com/hdmf-dev/hdmf/issues/343'. -- 959940: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959940 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#959940: hdmf FTBFS with h5py 2.10.0
Control: tags -1 upstream Control: forwarded -1 https://github.com/hdmf-dev/hdmf/issues/343
Bug#959947: python-m2crypto-doc: missing Breaks+Replaces: m2crypto-doc (<< 0.35.2-2)
Package: python-m2crypto-doc Version: 0.35.2-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../python-m2crypto-doc_0.35.2-2_all.deb ... Unpacking python-m2crypto-doc (0.35.2-2) ... dpkg: error processing archive /var/cache/apt/archives/python-m2crypto-doc_0.35.2-2_all.deb (--unpack): trying to overwrite '/usr/share/doc-base/m2crypto-documentation', which is also in package m2crypto-doc 0.31.0-9 Errors were encountered while processing: /var/cache/apt/archives/python-m2crypto-doc_0.35.2-2_all.deb cheers, Andreas m2crypto-doc=0.31.0-9_python-m2crypto-doc=0.35.2-2.log.gz Description: application/gzip
Bug#959946: grace: fails to start: failed request: 12 (X_ConfigureWindow)
Package: grace Version: 1:5.1.25-8 Severity: grave Justification: renders package unusable On a clean installation, grace fails to launch: $ xmgrace X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 12 (X_ConfigureWindow) Value in failed request: 0x0 Serial number of failed request: 2821 Current serial number in output stream: 2822 This happens both with the latest official build from the archive and with a fresh local rebuild. backtrace from gdb adds a reference to libthread_db.so: Starting program: /usr/bin/xmgrace [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". X Error of failed request: BadValue (integer parameter out of range for operation) -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.5.0-2-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_WARN Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages grace depends on: ii fontconfig2.13.1-4 ii gsfonts 1:8.11+urwcyr1.0.7~pre44-4.4 ii libc6 2.30-7 ii libfftw3-double3 3.3.8-2 ii libjpeg62-turbo 1:1.5.2-2+b1 ii libnetcdf18 1:4.7.4-1 ii libpng16-16 1.6.37-2 ii libx11-6 2:1.6.9-2+b1 ii libxbae4m 4.60.4-7+b11 ii libxm42.3.8-2 ii libxmhtml1.1 1.1.10-3 ii libxmu6 2:1.1.2-2+b3 ii libxpm4 1:3.5.12-1 ii libxt61:1.1.5-1+b3 ii xterm 356-1 Versions of packages grace recommends: ii xfonts-100dpi 1:1.0.4+nmu1 ii xfonts-75dpi 1:1.0.4+nmu1 Versions of packages grace suggests: ii gconf2 3.2.6-6 ii ghostscript 9.52~dfsg-1 pn texlive-extra-utils -- no debconf information
Bug#959861: marked as done (virt-p2v: missing epoch in Conflicts)
Your message dated Thu, 07 May 2020 10:34:16 + with message-id and subject line Bug#959861: fixed in virt-p2v 1.42.0-1 has caused the Debian Bug report #959861, regarding virt-p2v: missing epoch in Conflicts 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.) -- 959861: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959861 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: virt-p2v Version: 1.42-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'stable'. It installed fine in 'stable', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces This test intentionally skipped 'testing' to find file overwrite problems before packages migrate from 'unstable' to 'testing'. >From the attached log (scroll to the bottom...): Preparing to unpack .../virt-p2v_1.42-2_amd64.deb ... Unpacking virt-p2v (1.42-2) ... dpkg: error processing archive /var/cache/apt/archives/virt-p2v_1.42-2_amd64.deb (--unpack): trying to overwrite '/usr/bin/virt-p2v-make-disk', which is also in package libguestfs-tools 1:1.40.2-2 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/virt-p2v_1.42-2_amd64.deb Instead of Conflicts, Breaks+Replaces: libguestfs-tools (<< 1:1.42) should be sufficient (and will make it easier for apt). cheers, Andreas --- End Message --- --- Begin Message --- Source: virt-p2v Source-Version: 1.42.0-1 Done: Hilko Bengen We believe that the bug you reported is fixed in the latest version of virt-p2v, 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 959...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Hilko Bengen (supplier of updated virt-p2v 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, 07 May 2020 12:21:50 +0200 Source: virt-p2v Architecture: source Version: 1.42.0-1 Distribution: unstable Urgency: medium Maintainer: Hilko Bengen Changed-By: Hilko Bengen Closes: 959861 Changes: virt-p2v (1.42.0-1) unstable; urgency=medium . * Don't run gnulib tests * Fix versioned Conflicts (Closes: #959861) Checksums-Sha1: 2ede30e3f41bbfc93f7882f5d693b780507a411e 1938 virt-p2v_1.42.0-1.dsc 68f3c5ef858b8dc7e98e9a46289e43aaf7d52f47 885675 virt-p2v_1.42.0.orig.tar.gz bef6c5fdf219eaae83a9ee719f638d66564e33f7 1852 virt-p2v_1.42.0-1.debian.tar.xz 76cc8eb8fc6b1efffe7551258b0c75c23f4bca04 14546 virt-p2v_1.42.0-1_source.buildinfo Checksums-Sha256: 9156f1616893cbcd0ae6c2fd6643d520a12fe18d52954906bbb129b125142aee 1938 virt-p2v_1.42.0-1.dsc b1164bde6658646f11e8ff0da36fe5acbedde3445cc8424110c08fc144564e20 885675 virt-p2v_1.42.0.orig.tar.gz ccfe8826419c48cc31ee552b457600f408bc809919a198cde53c6ef578cd531f 1852 virt-p2v_1.42.0-1.debian.tar.xz 5751f703e94d03bf89366a0c3bec09f4acc93421a4a3860deab781eb59f67364 14546 virt-p2v_1.42.0-1_source.buildinfo Files: 92613e7407573eaf3a183caf4c52b407 1938 admin optional virt-p2v_1.42.0-1.dsc 648b08bfd1c35edbc755df7040141774 885675 admin optional virt-p2v_1.42.0.orig.tar.gz f6dc565879895008d2721fe5712fbe69 1852 admin optional virt-p2v_1.42.0-1.debian.tar.xz 72529e5b095b7ddd70a8d0a9bcf66ad2 14546 admin optional virt-p2v_1.42.0-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEErnMQVUQqHZbPTUx4dbcQY1whOn4FAl6z4ZwACgkQdbcQY1wh On5oxBAAjAuz+xGdNehZoMd3j3KDNRIaYgICjWEtSt3oBkWSWbSI8AqNvIvhX9X8 FwJs1j+5mnuv9e7alK43wRvRIobZ62250mvhMcpEJmkFlL81Z6q7piYONF5gZ94o H9ntL7KzFq/OIolJeg2ActA/jtAB4FYLZEUDKUfwB9Nr6w4PR0ZFE4qMLh0gxM0E NNDbo4W4ze8Gw88gZXHoCJNNGl4HEJs1yTx1ubbh5keE+GIV6VyQjUJM4+3NS232 S8q3VJiVNGyN4UGGmt6vLN2x4mqY2rgxmPaRh8AmUxKP3lyJQ5j4IUCtqUgrfYiJ jW23glpkhW+KadkwZaoAiBdC6nAeuzqqdqCqj52zni/1U0/3O7UdTHeWeh5eXTvR atzzYaR5k98v72jqwWvTuiMgFYrgfiiptZKsvwR9py0NFfv/KDIPbIexjfMY7QDI valzKhqmu3tuhJNorU84ycJH4uLcnnXdgeYDKnXLobKVTgGsS8D0+8KMqmBP5
Bug#953235: vtkplotter: autopkgtest arm64 failure: No module named 'vtkIOFFMPEGPython'
On Thu, May 07, 2020 at 10:28:33AM +0200, Paul Gevers wrote: >... > On 07-05-2020 10:07, Adrian Bunk wrote: > > This is a toolchain problem affecting many packages: > > https://sourceware.org/bugzilla/show_bug.cgi?id=25051 > > Do you have any rough estimate how many? >... Other bugs I can quickly find are #930039 and #945878. AFAIR I have seen maintainers adding workarounds for arm64+ppc64el FTBFS caused by this bug that did not have bugs in the BTS. #951704 looks like a similar but unrelated problem with jemalloc. > Is there any way to predict which packages are effected, Anything loading a plugin that is directly or indirectly linked with libgomp might or might not have this problem. Python C extensions are the most frequent ones. Heavy usage of Python code with C extensions tends to be in the more scientific areas of the archive, I'd guess many of these packages have no users at all on ppc64el or arm64 who would report bugs (Raspbian is armhf). python3-vtkplotter -> python3-vtk7 -> libvtk -> FFmpeg libraries -> libsoxr -> libgomp > or to detect which packages are effected? "import vtk" works, but "import vtkplotter" blows up when importing vtk. This is similar to the two different OpenSSL versions in stretch, where module load order might determine whether Apache segfaults or starts. >... > > Is there a non-manual way to express that the autopkgtest must not run > > on arm64 and powerpc64el? > > There is currently not even a manual way except for marking the test as > skippable and exitting with error code 77 on unsupported architectures. > Mind you, I don't think toolchain issues should be marked at the package > level (but maybe you didn't mean that). vtkplotter: flagged for removal in 6.3 days The big hammer would be to remove the autopkgtest... > If we can detect this failure > mode (and similar ones in the future) we can of course generate hints > based on this heuristics and have the failures ignored until the > toolchain issues are fixed. A failing arm64 or ppc64el autopkgtest log containing the string "libgomp.so.1: cannot allocate memory in static TLS block" is this bug. > Paul cu Adrian
Bug#959602: gtkmm3.0: FTBFS: gtk-demo/demowindow.cc:54:1: error: ‘demo_columns’ function uses ‘auto’ type specifier without trailing return type
control: tags -1 patch Changing stdc++11 to stdc++14 fixed the build failure --- gtkmm3.0-3.24.2/debian/patches/series 1970-01-01 00:00:00.0 + +++ gtkmm3.0-3.24.2/debian/patches/series 2020-05-07 10:03:05.0 + @@ -0,0 +1 @@ +stdc++14.patch diff -Nru gtkmm3.0-3.24.2/debian/patches/stdc++14.patch gtkmm3.0-3.24.2/debian/patches/stdc++14.patch --- gtkmm3.0-3.24.2/debian/patches/stdc++14.patch 1970-01-01 00:00:00.0 + +++ gtkmm3.0-3.24.2/debian/patches/stdc++14.patch 2020-05-07 10:03:05.0 + @@ -0,0 +1,16 @@ +Description: + * Use std=c++14 for build, to fix a build failure on i386 +Author: Gianfranco Costamagna +Last-Update: 2020-05-07 + +--- gtkmm3.0-3.24.2.orig/configure.ac gtkmm3.0-3.24.2/configure.ac +@@ -45,7 +45,7 @@ MM_CONFIG_DOCTOOL_DIR([docs]) + AC_SUBST([LIBGTKMM_SO_VERSION], [2:0:1]) + + AC_PROG_CXX +-MM_AX_CXX_COMPILE_STDCXX([11], [noext],[mandatory]) ++MM_AX_CXX_COMPILE_STDCXX([14], [noext],[mandatory]) + + AC_DISABLE_STATIC + LT_INIT([win32-dll]) On Sun, 3 May 2020 14:37:53 +0200 Lucas Nussbaum wrote: > Source: gtkmm3.0 > Version: 3.24.2-1 > Severity: serious > Justification: FTBFS on amd64 > Tags: bullseye sid ftbfs > Usertags: ftbfs-20200501 ftbfs-bullseye > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. > > Relevant part (hopefully): > > g++ -std=c++11 -DHAVE_CONFIG_H -I.. -I../gdk -I../gtk -pthread -pthread > > -I/usr/include/atkmm-1.6 -I/usr/include/giomm-2.4 > > -I/usr/lib/x86_64-linux-gnu/giomm-2.4/include -I/usr/include/pangomm-1.4 > > -I/usr/lib/x86_64-linux-gnu/pangomm-1.4/include -I/usr/include/glibmm-2.4 > > -I/usr/lib/x86_64-linux-gnu/glibmm-2.4/include -I/usr/include/cairomm-1.0 > > -I/usr/lib/x86_64-linux-gnu/cairomm-1.0/include -I/usr/include/sigc++-2.0 > > -I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include > > -I/usr/include/gtk-3.0/unix-print -I/usr/include/gtk-3.0 > > -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 > > -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include > > -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0 -I/usr/include/cairo > > -I/usr/include/pango-1.0 -I/usr/include/fribidi -I/usr/include/harfbuzz > > -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 > > -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 > > -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libmount -I/usr/include/blkid > > -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include > > -DDEMOCODEDIR=\"""\" -Wdate-time -D_FORTIFY_SOURCE=2 -Wall > > -DGLIBMM_DISABLE_DEPRECATED -DGIOMM_DISABLE_DEPRECATED > > -DGTKMM_DISABLE_DEPRECATED -DGDKMM_DISABLE_DEPRECATED -g -O2 > > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > > -Werror=format-security -c -o gtk-demo/gtkmm_demo-example_appwindow.o `test > > -f 'gtk-demo/example_appwindow.cc' || echo > > './'`gtk-demo/example_appwindow.cc > > gtk-demo/demowindow.cc:54:1: error: ‘demo_columns’ function uses ‘auto’ > > type specifier without trailing return type > >54 | const auto& demo_columns() > > | ^ > > gtk-demo/demowindow.cc:54:1: note: deduced return type only available with > > ‘-std=c++14’ or ‘-std=gnu++14’ > > make[4]: *** [Makefile:733: gtk-demo/gtkmm_demo-demowindow.o] Error 1 > > The full build log is available from: >http://qa-logs.debian.net/2020/05/01/gtkmm3.0_3.24.2-1_unstable.log > > A list of current common problems and possible solutions is available at > http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! > > About the archive rebuild: The rebuild was done on EC2 VM instances from > Amazon Web Services, using a clean, minimal and up-to-date chroot. Every > failed build was retried once to eliminate random failures. > >
Processed: Re: gtkmm3.0: FTBFS: gtk-demo/demowindow.cc:54:1: error: ‘demo_columns’ function uses ‘auto’ type specifier without trailing return type
Processing control commands: > tags -1 patch Bug #959602 [src:gtkmm3.0] gtkmm3.0: FTBFS: gtk-demo/demowindow.cc:54:1: error: ‘demo_columns’ function uses ‘auto’ type specifier without trailing return type Added tag(s) patch. -- 959602: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959602 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#959828: systemctl: `Provides: systemd`, but doesn't provide what systemd does
On Thursday, 7 May 2020 7:04:17 PM AEST Julien Cristau wrote: > This use of Provides is not acceptable. The systemctl package does not > in any way provide the same functionality / interfaces as the systemd > package, and as such it does not get to pretend that it does and cause > problems to other packages. Would you care to define criteria regarding what level of "pretend" would be acceptable?? I'm interested in reasoning, not your authority. You have provided no reasoning whatsoever. Did you even look at the package to say "does not in any way provide the same functionality / interfaces as the systemd" when it clearly implements a "systemctl" interface?? On what ground do you make this judgement? Or perhaps what are your concerns? I recommend to point your energy and attention to #959174. Thanks. -- Regards, Dmitry Smirnov. --- For a creative writer possession of the 'truth' is less important than emotional sincerity. -- George Orwell signature.asc Description: This is a digitally signed message part.
Bug#959942: src:caffe: missing (unversioned) Breaks+Replaces: libcaffe-cpu1/libcaffe-cpu-dev/caffe-tools-cpu
Source: caffe Version: 1.0.0+git20180821.99bd997-6 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Unpacking libcaffe1:amd64 (1.0.0+git20180821.99bd997-6) ... dpkg: error processing archive /var/cache/apt/archives/libcaffe1_1.0.0+git20180821.99bd997-6_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libcaffe.so.1.0.0', which is also in package libcaffe-cpu1:amd64 1.0.0+git20180821.99bd997-5+b5 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Preparing to unpack .../libcaffe-dev_1.0.0+git20180821.99bd997-6_amd64.deb ... Unpacking libcaffe-dev:amd64 (1.0.0+git20180821.99bd997-6) ... dpkg: error processing archive /var/cache/apt/archives/libcaffe-dev_1.0.0+git20180821.99bd997-6_amd64.deb (--unpack): trying to overwrite '/usr/include/caffe/blob.hpp', which is also in package libcaffe-cpu-dev:amd64 1.0.0+git20180821.99bd997-5+b5 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/libcaffe1_1.0.0+git20180821.99bd997-6_amd64.deb /var/cache/apt/archives/libcaffe-dev_1.0.0+git20180821.99bd997-6_amd64.deb Preparing to unpack .../libcaffe1_1.0.0+git20180821.99bd997-6_amd64.deb ... Unpacking libcaffe1:amd64 (1.0.0+git20180821.99bd997-6) ... dpkg: error processing archive /var/cache/apt/archives/libcaffe1_1.0.0+git20180821.99bd997-6_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libcaffe.so.1.0.0', which is also in package libcaffe-cpu1:amd64 1.0.0+git20180821.99bd997-5+b5 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Preparing to unpack .../caffe_1.0.0+git20180821.99bd997-6_amd64.deb ... Unpacking caffe (1.0.0+git20180821.99bd997-6) ... dpkg: error processing archive /var/cache/apt/archives/caffe_1.0.0+git20180821.99bd997-6_amd64.deb (--unpack): trying to overwrite '/usr/bin/caffe', which is also in package caffe-tools-cpu 1.0.0+git20180821.99bd997-5+b5 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/libcaffe1_1.0.0+git20180821.99bd997-6_amd64.deb /var/cache/apt/archives/caffe_1.0.0+git20180821.99bd997-6_amd64.deb Since the packages have been renamed in experimental without providing transitional packages, the B+R can be unversioned. Would a transitional package for caffe-tools-cpu be useful? Then use versioning (<< 1.0.0+git20180821.99bd997-6). (A Provides will not help upgrades to switch to the new name, a real package is needed in that case.) cheers, Andreas libcaffe-cpu1=1.0.0+git20180821.99bd997-5+b5_libcaffe1=1.0.0+git20180821.99bd997-6.log.gz Description: application/gzip
Processed: found 959937 in 9.0.31-1~deb10u1, notfound 959937 in 9.0.16-4
Processing commands for cont...@bugs.debian.org: > # reporter says stable version is fine > found 959937 9.0.31-1~deb10u1 Bug #959937 [tomcat9] tomcat9: update to tomcat9:amd64 9.0.31-1~deb10u1 breaks application Marked as found in versions tomcat9/9.0.31-1~deb10u1. > notfound 959937 9.0.16-4 Bug #959937 [tomcat9] tomcat9: update to tomcat9:amd64 9.0.31-1~deb10u1 breaks application No longer marked as found in versions tomcat9/9.0.16-4. > thanks Stopping processing here. Please contact me if you need assistance. -- 959937: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959937 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#959828: requires support on systemd side
The real culprit here, is that pkg:systemd provides many many distinct interfaces, without letting any consumers say _which_ interfaces they want. Thus, all of this would be solved if systemd declared Provides:systemctl and relevant consumers depended on that. Same with systemd-revolvd, tmpfiles, etc. Meow! -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ in the beginning was the boot and root floppies and they were good. ⢿⡄⠘⠷⠚⠋⠀ -- on #linux-sunxi ⠈⠳⣄
Bug#959828: systemctl: `Provides: systemd`, but doesn't provide what systemd does
On Thursday, 7 May 2020 6:58:49 PM AEST Ansgar wrote: > So all packages that want systemd-tmpfiles need "Depends: systemd" and > "Conflicts: systemctl" now? (Same for anything else provided by systemd, > but not systemctl.) You are over-reacting. "systemctl" is a niche package that is used only under a very specific requirements. I might consider making a quick shell implementation of `systemd-tmpfiles` but without upstream support that won't be enough. > That's what would be required thanks to the changes in systemctl now > because you have some disagreement with the php maintainer. That disagreement led me to think that "Provides: systemd" would be useful in other similar situations. Why would you not apply pressure to maintainer of PHP-FPM instead of me? > Note that in particular "php7.4-fpm" would need that Conflicts now... Of course not. > > No, it is broken because of the bug in SysV init script which explicitly > > calls `systemd-tmpfiles` binary hence _requires_ systemd facility. > > That is not a bug, even if you might not like the init script doing > that. You don't want to call it a bug? OK, then let's call it sloppy design, misuse of systemd facility and problematic mixing of init systems functionality. Don't you see how it cause this and few other bugs? > Please read https://www.debian.org/vote/2019/vote_002. Vote have nothing to do with poor technical decisions. This is not a debate against systemd and I was never against it. Please stop trying to portray me as anti-systemd activist. > Also accusations of "systemd zealotry" and such poisons debates with > toxic arguments. I would appreciate if you could stop doing that. OK, I may have spoke a bit too emotionally but Ondřej was un-provokingly and unexpectedly rude to me first. I do express strong disapproval and disagreement with his decision to leverage `systemd-tmpfiles` for php-fpm SysV init script. Maybe he would listen to you if you wish to convey this message with grace of your eloquence, lack of which you are blaming on me. -- All the best, Dmitry Smirnov. --- Good luck happens when preparedness meets opportunity. signature.asc Description: This is a digitally signed message part.
Bug#959758: marked as done (theano: FTBFS with pegjs 0.10)
Your message dated Thu, 07 May 2020 09:35:06 + with message-id and subject line Bug#959758: fixed in theano 1.0.4+dfsg-3 has caused the Debian Bug report #959758, regarding theano: FTBFS with pegjs 0.10 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.) -- 959758: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959758 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-theano Version: 1.0.4+dfsg-2 Severity: serious #graphlib-dot.js make -C debian/missing-source/graphlib-dot --always-make dist make[2]: Entering directory '/build/theano-1.0.4+dfsg/debian/missing-source/graphlib-dot' pegjs -e 'module.exports' src/dot-grammar.pegjs lib/dot-grammar.js Can't use the -e/--export-var option with the "commonjs" module format. make[2]: *** [Makefile:33: lib/dot-grammar.js] Error 1 --- End Message --- --- Begin Message --- Source: theano Source-Version: 1.0.4+dfsg-3 Done: rebecca_pal...@zoho.com (Rebecca N. Palmer) We believe that the bug you reported is fixed in the latest version of theano, 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 959...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Rebecca N. Palmer (supplier of updated theano 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, 06 May 2020 22:59:23 +0100 Source: theano Architecture: source Version: 1.0.4+dfsg-3 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Rebecca N. Palmer Closes: 959758 Changes: theano (1.0.4+dfsg-3) unstable; urgency=medium . * Use packaged (but still build-time copied) dagre* and graphlib. * Embedded graphlib-dot: update, verbose build, run tests, fix build with pegjs 0.10 (Closes: #959758). Checksums-Sha1: 1fc3f6b9ae194ea57f952749d4d997d76f74b234 2787 theano_1.0.4+dfsg-3.dsc 6d0a0c5cd50b19edb16c68a311300019d100 68328 theano_1.0.4+dfsg-3.debian.tar.xz 2844a947149d2a51592bd3c4d7c3528bbd1cad00 5653 theano_1.0.4+dfsg-3_source.buildinfo Checksums-Sha256: fbff96c84132593f44192f4996a808db664d02cb95e34e6fa37317de2f894fb8 2787 theano_1.0.4+dfsg-3.dsc 5867a27115cc8582bedbfa9b1351086ba582ba50a6545bcbadd0d7fb6f03f11a 68328 theano_1.0.4+dfsg-3.debian.tar.xz bcf53f9fabb7f797fbc15864382d41f0295ee64b0efdf6d4e2e7196e9302f8ff 5653 theano_1.0.4+dfsg-3_source.buildinfo Files: 449594addb2e0df3187fdae6f7a26454 2787 science optional theano_1.0.4+dfsg-3.dsc ad98813e83367a22e737c0e748075208 68328 science optional theano_1.0.4+dfsg-3.debian.tar.xz d47292dd4cb67ac047147f45741a55d0 5653 science optional theano_1.0.4+dfsg-3_source.buildinfo -BEGIN PGP SIGNATURE- iQJMBAEBCgA2FiEEZ8sxEAXE7b4yF1MI3uUNDVZ+omYFAl6zz1wYHHJlYmVjY2Ff cGFsbWVyQHpvaG8uY29tAAoJEN7lDQ1WfqJmEIsQAKIZXHgslYJ3ngNwmLZcwJjx 67iD8hjBl4IQ+RcqZAI7Pa7EO8xbum4fTJJEB958O+9ZKQl92ZT+qQIncUjE44F9 N/7FFYWHJuvL7zPgO9DdW9qsRGlqCQ77cP35CsuFspQkwejZuJ6XDWD+vsw27fKZ c8IhvxOHBGzAZ+0rMEATYwMPfTq8TzuB61YgEYKPtHbRk92NlhcTdxDG0RT/C+Iw GOa2TsMswf7wbQi0L3ZHaXrpRoJaECIYChX4nC4QwtGNX4HDO5ahsRwNvNbiF2N3 c562LoeZtU9vlPt8yNVOdQt7SyjJJosMKdYpByE+s0JCCiC/AK89qLkemE12GS/d CKIYdXvgMPurE90zCDf8szugUYeIVVtiCQ92Y0fz6cXbcWZw6iYHKPrjR01fpk5b XGM8OFLt05R7MO1imQOclMm6eSE8+71JiujVOd/05wrh5yVTnhlj5e47jOfRFeul dhaL8PVpzU+vn4sGgSEnhyoqMK2GwJEhNc7yBOICoxtWpBxe6O+GiGMqug8WlQ/i ff6cmQ3uHlx4wL/E4p0Wpwxr0ps84tP/mzZpox3YCJMoMIPvoCxAbpAP+hw4oe/J MzGmRzENxLTp6anD1hNHMMwNfhMeZl7F4NRM2mMDenBNMlLZ2WvMZVIMhBuAJk7x dDZHuJT2kLkprtmOlWbt =Nn2e -END PGP SIGNATURE End Message ---
Bug#958531: marked as done (pandas: broken by NaT/isnan changes in numpy 1.18)
Your message dated Thu, 07 May 2020 09:33:46 + with message-id and subject line Bug#958531: fixed in pandas 0.25.3+dfsg2-1 has caused the Debian Bug report #958531, regarding pandas: broken by NaT/isnan changes in numpy 1.18 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.) -- 958531: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958531 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-pandas Version: 0.25.3+dfsg-9 Severity: serious Tags: fixed-upstream patch numpy 1.18 includes two behaviour changes that affect pandas, causing a CI fail / presumed FTBFS. Both are fixed in pandas 1.0 (in experimental, but moving that to unstable causes other issues, see #950430). - NaT sorts to the end rather than the beginning This causes an actual behaviour change for Index (but not values) sorting, not just broken tests. Fix: https://github.com/pandas-dev/pandas/commit/f85502531806df4f3c0233edffe9460f3ee26031#diff-26a6d2ca7adfca586aabbb1c9dd8bf36 - np.isinf/isnan no longer raise on datetime/timedelta data type Breaks tests that assert they raise. Fix: https://github.com/pandas-dev/pandas/commit/0c0adfbc291fc1b1e9afad592f5275e783ffd0b0#diff-af2644300e4b344f0c048fe3adde10e0 --- End Message --- --- Begin Message --- Source: pandas Source-Version: 0.25.3+dfsg2-1 Done: rebecca_pal...@zoho.com (Rebecca N. Palmer) We believe that the bug you reported is fixed in the latest version of pandas, 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 958...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Rebecca N. Palmer (supplier of updated pandas 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, 06 May 2020 12:18:23 +0100 Source: pandas Architecture: source Version: 0.25.3+dfsg2-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Team Changed-By: Rebecca N. Palmer Closes: 956021 958531 Changes: pandas (0.25.3+dfsg2-1) unstable; urgency=medium . * Remove inconveniently licensed (CC-BY-SA) snippets. * Fix (harmless) SyntaxWarning on install. (Closes: #956021) * Fix NaT sort order and test failures with numpy 1.18. (Closes: #958531) Checksums-Sha1: 01c551569607a83fca1b83ddd2013a5f17b7c897 4004 pandas_0.25.3+dfsg2-1.dsc 033932bd17bb1fb005fc9538fa593ad537deda40 5406572 pandas_0.25.3+dfsg2.orig.tar.xz 5acf86d9b29efe218837dfac7813fb9c1ebae498 71664 pandas_0.25.3+dfsg2-1.debian.tar.xz fb95e701270a5134f30eafd15b08c9e5b709d34d 5996 pandas_0.25.3+dfsg2-1_source.buildinfo Checksums-Sha256: 6eef83a56466ad77eda8e4681ca698ba836d98a6d1f2eaa0b176b36653de097c 4004 pandas_0.25.3+dfsg2-1.dsc f646bde445e4ddf2c56ca90e11013fad3e0dc25cee9d2a51ac00eeb60b12e1dc 5406572 pandas_0.25.3+dfsg2.orig.tar.xz de62a1ba61ec808385b83160a9b4e2415f98a76d28cc2bbd5362f17df8d32d3d 71664 pandas_0.25.3+dfsg2-1.debian.tar.xz 56c46d7adf6ad225c2338ed544df3b88c2f93537e5c432ec73a54fc2eb45 5996 pandas_0.25.3+dfsg2-1_source.buildinfo Files: 8a7e8c12bc4359e977dcc6c2dc2ecf92 4004 python optional pandas_0.25.3+dfsg2-1.dsc 17d6c4d929b71289a7f8f33cef639953 5406572 python optional pandas_0.25.3+dfsg2.orig.tar.xz 033bc844da957c75282df12c0310c1f6 71664 python optional pandas_0.25.3+dfsg2-1.debian.tar.xz 5351a03d0ac9bf53ee00211e58ace15f 5996 python optional pandas_0.25.3+dfsg2-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJMBAEBCgA2FiEEZ8sxEAXE7b4yF1MI3uUNDVZ+omYFAl6zz1IYHHJlYmVjY2Ff cGFsbWVyQHpvaG8uY29tAAoJEN7lDQ1WfqJmV+4QALKwYJSTcQp6QzH0+XU5YHrS 9xySoTCBU7qnyguuoevFlYFU+Q1OJ9ViTpyKzk0sGEGlTwEuX+5ylkluOPP7wKsi WuuNXa7EDi+/1BsPoSff1ExARTJqlOSxSWdhcnHPfkWrMrQ4fFJoJzYoNJExq14U 0y9pQNSDXwXdLR/VijYqseei1ElN0n+z9C/A+qvhnp1xfxbRI85pL4YMA9kdwloR behXcK67mJ3vJMK6z1uSFBwkwI76HTsHRzmjcVEC2WsjTZ3l+ub1VHeMBFpBDFZ9 SCNqSjK1lYR1RJwSn9QCr5dTW923y8Fcrv+oCAdPqOKwuGB0IbTsZT5PraM7h0ZD hi0fDW+QgEpPt5uOgVOH46a7uWkKK/Dgz6UzBV2DecXCQNarGGVjI64cEs1KFd1Z oKgidIcs+tI38F4HQkAA0PZ+MDtfgLoLHbHvyy+lHwqAaApxrhd1l59KQRsFn8X+ tdWkadTeTaJNosPgEN3LyTlyfE+LE5jUOLyVpa+cI8stfhCPDy6ecpAxvSzXfg9u A7sR9kHbiuQpJz+eu7J6qGhcKObfV3NmUYGkIne7a2+VcKX0L1px+X40JdvNElwi RdRxWVF/tzp9zeO/078W+sMSe3rIHo6L9+eejdnCcj4YIfqICyv0
Processed: hdmf FTBFS with h5py 2.10.0
Processing control commands: > affects -1 src:pynwb Bug #959940 [src:hdmf] hdmf FTBFS with h5py 2.10.0 Added indication that 959940 affects src:pynwb -- 959940: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959940 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#959940: hdmf FTBFS with h5py 2.10.0
Source: hdmf
Version: 1.5.4-1
Severity: serious
Tags: ftbfs
Control: affects -1 src:pynwb
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/hdmf.html
...
==
ERROR: test_dynamic_container_constructor_name_default_name
(tests.unit.build_tests.test_io_map.TestDynamicContainer)
--
Traceback (most recent call last):
File
"/build/1st/hdmf-1.5.4/.pybuild/cpython3_3.8_hdmf/build/tests/unit/build_tests/test_io_map.py",
line 313, in test_dynamic_container_constructor_name_default_name
with self.assertWarns(Warning):
File "/usr/lib/python3.8/unittest/case.py", line 255, in __enter__
if getattr(v, '__warningregistry__', None):
File
"/usr/lib/python3/dist-packages/h5py/_debian_h5py_serial/h5py_warnings.py",
line 36, in __getattr__
return getattr(self._mod, attr)
File
"/usr/lib/python3/dist-packages/h5py/_debian_h5py_serial/h5py_warnings.py",
line 35, in __getattr__
self._mod = self._import()
File
"/usr/lib/python3/dist-packages/h5py/_debian_h5py_serial/h5py_warnings.py",
line 39, in _import
return import_module(self._mod)
File "/usr/lib/python3.8/importlib/__init__.py", line 118, in import_module
if name.startswith('.'):
File
"/usr/lib/python3/dist-packages/h5py/_debian_h5py_serial/h5py_warnings.py",
line 35, in __getattr__
self._mod = self._import()
File
"/usr/lib/python3/dist-packages/h5py/_debian_h5py_serial/h5py_warnings.py",
line 39, in _import
return import_module(self._mod)
File "/usr/lib/python3.8/importlib/__init__.py", line 118, in import_module
if name.startswith('.'):
...
File
"/usr/lib/python3/dist-packages/h5py/_debian_h5py_serial/h5py_warnings.py",
line 35, in __getattr__
self._mod = self._import()
File
"/usr/lib/python3/dist-packages/h5py/_debian_h5py_serial/h5py_warnings.py",
line 39, in _import
return import_module(self._mod)
File "/usr/lib/python3.8/importlib/__init__.py", line 118, in import_module
if name.startswith('.'):
File
"/usr/lib/python3/dist-packages/h5py/_debian_h5py_serial/h5py_warnings.py",
line 35, in __getattr__
self._mod = self._import()
RecursionError: maximum recursion depth exceeded
--
Ran 464 tests in 3.412s
FAILED (errors=8)
E: pybuild pybuild:352: test: plugin distutils failed with: exit code=1: cd
/build/1st/hdmf-1.5.4/.pybuild/cpython3_3.8_hdmf/build; python3.8 -m unittest
discover -v
dh_auto_test: error: pybuild --test -i python{version} -p 3.8 returned exit
code 13
make: *** [debian/rules:7: build] Error 25
Processed: Re: Bug#959828: systemctl: `Provides: systemd`, but doesn't provide what systemd does
Processing control commands: > severity -1 serious Bug #959828 [systemctl] systemctl: `Provides: systemd`, but doesn't provide what systemd does Severity set to 'serious' from 'normal' -- 959828: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959828 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#953235: vtkplotter: autopkgtest arm64 failure: No module named 'vtkIOFFMPEGPython'
Dear Adrian, On 07-05-2020 10:07, Adrian Bunk wrote: > This is a toolchain problem affecting many packages: > https://sourceware.org/bugzilla/show_bug.cgi?id=25051 Do you have any rough estimate how many? Is there any way to predict which packages are effected, or to detect which packages are effected? > There is nothing a binary-all python module can do to fix > architecture-specific toolchain bugs. Ack. > Is there a non-manual way to express that the autopkgtest must not run > on arm64 and powerpc64el? There is currently not even a manual way except for marking the test as skippable and exitting with error code 77 on unsupported architectures. Mind you, I don't think toolchain issues should be marked at the package level (but maybe you didn't mean that). If we can detect this failure mode (and similar ones in the future) we can of course generate hints based on this heuristics and have the failures ignored until the toolchain issues are fixed. Paul signature.asc Description: OpenPGP digital signature
Bug#953235: vtkplotter: autopkgtest arm64 failure: No module named 'vtkIOFFMPEGPython'
On Fri, Mar 06, 2020 at 10:57:20AM +0100, Paul Gevers wrote: >... > However, it fails on arm64. I copied some of the output at the bottom of > this report. > > Currently this regression is blocking the migration to testing [1]. Can > you please investigate the situation and fix it? >... > https://ci.debian.net/data/autopkgtest/testing/amd64/v/vtkplotter/4281870/log.gz > > autopkgtest [12:57:24]: test python3: [--- > Processing test_actors.py script.. > Traceback (most recent call last): > File "/usr/lib/python3/dist-packages/vtk/vtkIOFFMPEG.py", line 5, in > > from .vtkIOFFMPEGPython import * > ImportError: /lib/aarch64-linux-gnu/libgomp.so.1: cannot allocate memory > in static TLS block >... This is a toolchain problem affecting many packages: https://sourceware.org/bugzilla/show_bug.cgi?id=25051 There is nothing a binary-all python module can do to fix architecture-specific toolchain bugs. Is there a non-manual way to express that the autopkgtest must not run on arm64 and powerpc64el? cu Adrian
Bug#959937: tomcat9: update to tomcat9:amd64 9.0.31-1~deb10u1 breaks application
Package: tomcat9
Version: 9.0.16-4
Severity: grave
Justification: renders package unusable
I've just been called out of bed.
As it seems unattended-upgrades upgraded on a debian buster server
from:9.0.16-4 to 9.0.31-1~deb10u1
One of the installed webapps throws following error when trying to use it:
[https-openssl-nio-8443-exec-13] ERROR org.zkoss.zk.ui.metainfo.Property -
Failed to assign [value=${i18n:rt('Benutzername')}] to
Unable to find ExpressionFactory of type: # Licensed to the Apache Software
Foundation (ASF) under one or more
Downgrading to 9.0.16-4 solves the issue.
-- System Information:
Debian Release: 10.3
APT prefers stable
APT policy: (990, 'stable'), (500, 'stable-updates'), (400, 'testing'), (300,
'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.5.0-2-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_USER, TAINT_WARN, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages tomcat9 depends on:
ii lsb-base10.2019051400
ii systemd 245.5-2~bpo10+1
ii tomcat9-common 9.0.16-4
ii ucf 3.0038+nmu1
Versions of packages tomcat9 recommends:
pn libtcnative-1
Versions of packages tomcat9 suggests:
pn tomcat9-admin
pn tomcat9-docs
pn tomcat9-examples
pn tomcat9-user
-- no debconf information
Processed: block on pagure
Processing commands for cont...@bugs.debian.org: > block 937769 by 959934 Bug #937769 [src:python-funcsigs] python-funcsigs: Python2 removal in sid/bullseye 937769 was blocked by: 937926 937144 937558 943135 937769 was blocking: 937695 938168 938756 Added blocking bug(s) of 937769: 959934 > End of message, stopping processing here. Please contact me if you need assistance. -- 937769: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937769 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#956828: This bug creates noise (Was: bedtools: fails to migrate to testing for too long: FTBFS on several archs)
Hi Michael, this bug continuously creates noise on the testing removal front. I'd really love to ask for removal the failing arches for the moment. What do you think? Kind regards Andreas. -- http://fam-tille.de
Bug#956828: This bug creates noise (Was: bedtools: fails to migrate to testing for too long: FTBFS on several archs)
That's fine by me -- Michael R. Crusoe On Thu, May 7, 2020, 09:53 Andreas Tille wrote: > Hi Michael, > > this bug continuously creates noise on the testing removal front. I'd > really love to ask for removal the failing arches for the moment. > > What do you think? > > Kind regards > > Andreas. > > -- > http://fam-tille.de >
Bug#950066: marked as done (python-asyncssh: missing build dependency on dh-python)
Your message dated Thu, 07 May 2020 07:48:33 + with message-id and subject line Bug#950066: fixed in python-asyncssh 1.12.2-2 has caused the Debian Bug report #950066, regarding python-asyncssh: missing build dependency on dh-python 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.) -- 950066: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950066 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-asyncssh Version: 1.12.2-1 Severity: serious Tags: ftbfs bullseye sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-asyncssh.html ... fakeroot debian/rules clean dh clean --with python3,sphinxdoc --buildsystem pybuild dh: error: unable to load addon python3: Can't locate Debian/Debhelper/Sequence/python3.pm in @INC (you may need to install the Debian::Debhelper::Sequence::python3 module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.30.0 /usr/local/share/perl/5.30.0 /usr/lib/x86_64-linux-gnu/perl5/5.30 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.30 /usr/share/perl/5.30 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at (eval 10) line 1. BEGIN failed--compilation aborted at (eval 10) line 1. make: *** [debian/rules:7: clean] Error 25 --- End Message --- --- Begin Message --- Source: python-asyncssh Source-Version: 1.12.2-2 Done: Gordon Ball We believe that the bug you reported is fixed in the latest version of python-asyncssh, 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 950...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gordon Ball (supplier of updated python-asyncssh 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, 07 May 2020 07:00:36 + Source: python-asyncssh Architecture: source Version: 1.12.2-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team Changed-By: Gordon Ball Closes: 950066 Changes: python-asyncssh (1.12.2-2) unstable; urgency=medium . [ Ondřej Nový ] * Use debhelper-compat instead of debian/compat. . [ Debian Janitor ] * Bump debhelper from old 9 to 12. * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository, Repository-Browse. * Add missing build dependency on dh-python (Closes: #950066). Checksums-Sha1: 21102aa06a2f8a8593c782dd44ef300b6fbbd1d0 2299 python-asyncssh_1.12.2-2.dsc de5dd6d5622f737d82fcac3862f4c0ade0327851 7844 python-asyncssh_1.12.2-2.debian.tar.xz 1a199c2d87be9a47f394fc0598dd5a561f151495 8154 python-asyncssh_1.12.2-2_amd64.buildinfo Checksums-Sha256: 18ed4020e5256bf252294274d8b4d9e3fd482db31ffc3e62e91064cdbb8f27ad 2299 python-asyncssh_1.12.2-2.dsc 9ba688567ed960e61ce980944c8dbc352879fb05bf7b06e9b8799c0f6fe9cb20 7844 python-asyncssh_1.12.2-2.debian.tar.xz 4007f58cdfe750e3b0cf77982db8b8cb656f94937a822ca22dc2e49445479be6 8154 python-asyncssh_1.12.2-2_amd64.buildinfo Files: 12a7f116039b475071741d466ff27b95 2299 python optional python-asyncssh_1.12.2-2.dsc 5f27e0bfaf6da4237c160e5b1b3a4060 7844 python optional python-asyncssh_1.12.2-2.debian.tar.xz a880dffd18aacfe39d25a8fb7206e223 8154 python optional python-asyncssh_1.12.2-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE6PwpXIa418BJ+Xuno12v+60p6N4FAl6zufEACgkQo12v+60p 6N69Gg//TxL+LXjRBdRbwGSRB3QboRVt5COCxhorv+YifVvdHwv2dtpZb7pnqTHq GLRqanI73udIDUM/0myHYUerb+FS7cOMJqSJj9cgj8aR7Jpzf4rPdkcb9M/cmuh3 xSC2l1SvsRXwGEGwZl84tAe+06v6zOUP3Ye6y8AtshffMiTFKl1vOBwvbogw8eyv AM8uEDe0fLkxXrRJw/1ZkTLQmormlBM7kmphtmERpTPAvPj5tBSCaLuR8FQPBs1+ GNLhLhlBoxRC3EM2yTHcHP89MX577uTuczlkii5/4imMs2ceXTpn4ndAoeEzRe5y r4nPZ/2ic56NhRgYBf8wphOf30I1FxZ7JjAkmY/kFhpJeQtGoC3DsnmxcX5bmdxS tq5b8ersVrvbmTUeRXkZhK//GXOn6rFO3xDDh62NPjLA46rTdsOa79EhpyjSVsUv srbjAyM578WQ7qa/4ibs7ibQrFAyYRbbu2jxSUpZfsMRrD4sASyuURmCrj0zH/Gf mcHRhZzGFktDycER24HaBgEB2YFJLhvPxrP7lC+GrPnwSeKEHAnDgHiV6TuX8XtX elFNuAXDluu/Br6An0lGV8YS+fT29NMWnn/bxPgFVmG+bMbESTGSkjhq2ZKuC8b6 dOuPh2k5XLOfp8336x0AX+f5cDxgamEG0hG1L2OPfYO9wVGR88k= =Wofx -END PGP SIGNATURE End Message ---
Processed: Merge duplicates
Processing commands for cont...@bugs.debian.org: > reassign 959556 libyaml-cpp0.6 Bug #959556 [src:olive-editor] olive-editor: FTBFS: ld: /usr/lib/libOpenColorIO.so: undefined reference to `YAML::detail::node_data::empty_scalar[abi:cxx11]' Bug reassigned from package 'src:olive-editor' to 'libyaml-cpp0.6'. No longer marked as found in versions olive-editor/20200210-1. Ignoring request to alter fixed versions of bug #959556 to the same values previously set > reassign 959657 libyaml-cpp0.6 Bug #959657 [olive-editor] olive-editor: Does not start: symbol lookup error Bug reassigned from package 'olive-editor' to 'libyaml-cpp0.6'. No longer marked as found in versions olive-editor/20200210-1. Ignoring request to alter fixed versions of bug #959657 to the same values previously set > forcemerge 959201 959556 959657 Bug #959201 [libyaml-cpp0.6] jami-daemon: dring does not start due to a symbol lookup error Bug #959586 [libyaml-cpp0.6] openimageio: FTBFS: ld: /usr/lib/libOpenColorIO.so.1: undefined reference to `YAML::detail::node_data::empty_scalar[abi:cxx11]' Bug #959657 [libyaml-cpp0.6] olive-editor: Does not start: symbol lookup error Set Bug forwarded-to-address to 'https://github.com/jbeder/yaml-cpp/issues/789'. Added indication that 959657 affects jami-daemon,src:openimageio,libopencolorio1v5 Marked as found in versions yaml-cpp/0.6.3-1. Added tag(s) upstream, ftbfs, sid, confirmed, and bullseye. Bug #959586 [libyaml-cpp0.6] openimageio: FTBFS: ld: /usr/lib/libOpenColorIO.so.1: undefined reference to `YAML::detail::node_data::empty_scalar[abi:cxx11]' Removed indication that 959586 affects jami-daemon, src:openimageio, and libopencolorio1v5 Added indication that 959586 affects jami-daemon,src:openimageio,libopencolorio1v5 Removed indication that 959201 affects libopencolorio1v5, src:openimageio, and jami-daemon Added indication that 959201 affects jami-daemon,src:openimageio,libopencolorio1v5 Bug #959556 [libyaml-cpp0.6] olive-editor: FTBFS: ld: /usr/lib/libOpenColorIO.so: undefined reference to `YAML::detail::node_data::empty_scalar[abi:cxx11]' Set Bug forwarded-to-address to 'https://github.com/jbeder/yaml-cpp/issues/789'. Severity set to 'grave' from 'serious' Added indication that 959556 affects jami-daemon,src:openimageio,libopencolorio1v5 Marked as found in versions yaml-cpp/0.6.3-1. Added tag(s) upstream and confirmed. Merged 959201 959556 959586 959657 > affects 959201 olive-editor src:olive-editor Bug #959201 [libyaml-cpp0.6] jami-daemon: dring does not start due to a symbol lookup error Bug #959556 [libyaml-cpp0.6] olive-editor: FTBFS: ld: /usr/lib/libOpenColorIO.so: undefined reference to `YAML::detail::node_data::empty_scalar[abi:cxx11]' Bug #959586 [libyaml-cpp0.6] openimageio: FTBFS: ld: /usr/lib/libOpenColorIO.so.1: undefined reference to `YAML::detail::node_data::empty_scalar[abi:cxx11]' Bug #959657 [libyaml-cpp0.6] olive-editor: Does not start: symbol lookup error Added indication that 959201 affects olive-editor and src:olive-editor Added indication that 959556 affects olive-editor and src:olive-editor Added indication that 959586 affects olive-editor and src:olive-editor Added indication that 959657 affects olive-editor and src:olive-editor > thanks Stopping processing here. Please contact me if you need assistance. -- 959201: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959201 959556: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959556 959586: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959586 959657: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959657 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#937769: logfury
I just uploaded python-logfury dropping the funcsigs dependency, so that's one step closer.
