Bug#946752: [Pkg-opencl-devel] Bug#946752: intel-opencl-icd: Depends on libigdgmm5, which no longer exists
On 2019-12-15 10:53, Rebecca N. Palmer wrote: Package: intel-opencl-icd Version: 19.29.13530-1 Severity: serious Justification: makes package uninstallable This package's debian/control hardcodes a dependency on libigdgmm5. As this library has changed soname to libigdgmm11, this makes it uninstallable. Neo runtime 19.29.13530 was tested/released with gmmlib 19.2.3 containing so version=9. See: https://github.com/intel/compute-runtime/releases/tag/19.29.13530 The first compute-runtime with gmmlib containing so version=11 was 19.39.14278 See: https://github.com/intel/compute-runtime/releases/tag/19.39.14278 -- jacek
Bug#946734: [Pkg-rust-maintainers] Bug#946734: rust-addr2line Build-Depends on librust-fallible-iterator-0.1+default-dev which isn't available
On 12/14/19 10:49 PM, Paul Gevers wrote:
> Source: rust-addr2line
> Version: 0.7.0-1
> Severity: serious
> Tags: ftbfs
>
> Dear maintainers,
>
> Your package was never build on a buildd, and was rescheduled 117 days
> ago. Since then, the status is BD-Uninstallable. Can you please make sure that
> we can actually build packages in Debian?
Hi Paul,
Thank you for your report.
We already have a new version of addr2line prepared, but it is still
waiting for rust-gimli to pass the NEW queue.
In my experience, the packages have been able to build in the past, but
became un-buildable due to the update of a dependency (in this case
rust-fallible-iterator).
I prepared an update of a set of packages, namely
rust-{object,fallible-iterator,gimli,addr2line,backtrace} with
consistent versions. However, the upload of rust-gimli landed in the NEW
queue due to having an additional bin package. The details on the
problems we currently have with that can be found in #945542. The whole
situation seems stuck and is somewhere between discouraging and
demotivating for the whole debian-rust team atm.
> Please check https://release.debian.org/transitions/html/rust.html, there is
> at
> least one more packages like this one: rust-nitrokey-test. Can/should I
> reschedule all the red packages or will that fail anyways?
I take a look at this page at regular intervals, that was one of the
incentives to start working on the set of packages as described above.
Can't say for the other packages though. It is well possible that they
are in a similar situation.
Wolfgang.
Processed: Re: Bug#945931: haskell-crypto: Removal notice: broken and unmaintained
Processing control commands: > affects -1 - ganeti Bug #945931 [src:haskell-crypto] haskell-crypto: Removal notice: broken and unmaintained Removed indication that 945931 affects ganeti -- 945931: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945931 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#945931: haskell-crypto: Removal notice: broken and unmaintained
Control: affects -1 - ganeti Hey, On 13:04 Sun 01 Dec , Ilias Tsitsimpis wrote: > Source: haskell-crypto > Version: 4.2.5.1-9 > Severity: grave > Justification: renders package unusable > > This package is no longer maintained (last upstream upload in 2012). It > is also broken with GHC 8.6.4 and unlikely to ever be fixed (see [1]). > > I intend to remove this package once ganeti has been updated to use > cryptonite instead (see [2]). Ganeti has been ported[3] to cryptonite, you can safely remove haskell-crypto. Thanks for keeping the Haskell ecosystem in Debian healthy :) [3] https://salsa.debian.org/ganeti-team/ganeti/commit/8f8a95bea4661153380a75908038768b0af50594 Cheers, Apollon
Bug#944940: marked as done (python-ethtool: needs an explicit build dependency on dh-python)
Your message dated Mon, 16 Dec 2019 07:49:18 + with message-id and subject line Bug#944940: fixed in python-ethtool 0.14-2 has caused the Debian Bug report #944940, regarding python-ethtool: needs an explicit 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.) -- 944940: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944940 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-ethtool Version: 0.14-1 Severity: serious Tags: sid bullseye python3-all and python3-dev now dropped the dependency on dh-python: [ Piotr Ożarowski ] * Remove dh-python dependency from python3-all and python3-dev packages. Packages should build depend on dh-python or dh-sequence-python3 instead. Please add an explicit build dependency on dh-python. --- End Message --- --- Begin Message --- Source: python-ethtool Source-Version: 0.14-2 We believe that the bug you reported is fixed in the latest version of python-ethtool, 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 944...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stewart Ferguson (supplier of updated python-ethtool package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 16 Dec 2019 07:26:54 + Source: python-ethtool Architecture: source Version: 0.14-2 Distribution: unstable Urgency: medium Maintainer: Stewart Ferguson Changed-By: Stewart Ferguson Closes: 944940 Changes: python-ethtool (0.14-2) unstable; urgency=medium . [ Ondřej Nový ] * Use debhelper-compat instead of debian/compat. . [ Stewart Ferguson ] * Adding build-dep on dh-python (Closes: #944940) * Changing build system to pybuild * Bumping compat * Bumping Standards-Version to 4.4.1 Checksums-Sha1: 795921e5c2069bdd2c22d6726b454aedab00e8c5 2264 python-ethtool_0.14-2.dsc 8a89d8c386712219e0d4775db5d9d5786f7de024 4572 python-ethtool_0.14-2.debian.tar.xz Checksums-Sha256: 57137bc7bf2fe99ee88a5579a0f98577aca0e41972ac46fda8822ece2363ee35 2264 python-ethtool_0.14-2.dsc 07670980683eeb1f738f4cc1a499bbea9657923c7e3bd99c88a60b6d5e60f323 4572 python-ethtool_0.14-2.debian.tar.xz Files: 0cea4f1b06160b1b03e3586f0d6131f2 2264 python optional python-ethtool_0.14-2.dsc 368f3d8bbfb7312f4ddf7079b348feb4 4572 python optional python-ethtool_0.14-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEJeP/LX9Gnb59DU5Qr8/sjmac4cIFAl33MrkACgkQr8/sjmac 4cJX7BAAgLLfFjTJYm6xEsCPePbvozSWqziEBB8Q6jCG+5WZ25+wP7QaQ9ENfzMK c8uGHWtu9leYVKfkVQ6xaYOBzrnweGbMuTbCdsJS9izVcnl+ldm8UxvHXHH9NtjL zqbIY4/CaIukTiX8gRMUHDPa30meE/wN/RfXMrpWyhNOM/hv6RzvLoI1bdwS2mof sUY90rgyerRMNjjAgnf5jFPvRB+8xr2AstX5qQtR1+gkUevS4k5lg1X7aBKkaMrc CXkfnwhNjif7sv2lTUVRh2VDjj8+LuyDXGAC1Kam+T64fhCXoWUd6HiQcx24T6Xw hYKoP8ZQJyaM5RG+NdjHoIXEYQ+DpYZnKvF3rtsGoF53J0RqLNRIX49vvKYo1XpW PeKVc50xsQzPfOEa9AP378CHY7xZPq7r8Bg19nXKmp8uIQmbzn1YCKhV0lp/go7W n/+Yjm8LIaz2m3Ls1esecmXwCOGWWSrLHSOM2BLgAC5zNQ/JLWhyknThr9SStUz2 TKC5Z7EUt73RArDOMbNONIxEQKGPq0t0p1wq9Z59YYUS/XZJ918TbNN3o7N0VwEG J8H5T2lSeWc8KDYgHiPehhutaqSzxrWC8wqzoHyGOo6zJ4SR9/tPtZBu2qYDEj60 PnCFQ+zfJZF6eVBSKk0o2haS/VKv67bHXT0r5XQpbuJJjrz62Fc= =A6Tz -END PGP SIGNATURE End Message ---
Bug#946800: marked as done (python3-pbcommand: missing Breaks+Replaces: python-pbcommand (<< 1.1.1+git20191122.ec024c3))
Your message dated Mon, 16 Dec 2019 07:34:16 + with message-id and subject line Bug#946800: fixed in python-pbcommand 1.1.1+git20191122.ec024c3-2 has caused the Debian Bug report #946800, regarding python3-pbcommand: missing Breaks+Replaces: python-pbcommand (<< 1.1.1+git20191122.ec024c3) 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.) -- 946800: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946800 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-pbcommand Version: 1.1.1+git20191122.ec024c3-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...): Selecting previously unselected package python3-pbcommand. Preparing to unpack .../16-python3-pbcommand_1.1.1+git20191122.ec024c3-1_all.deb ... Unpacking python3-pbcommand (1.1.1+git20191122.ec024c3-1) ... dpkg: error processing archive /tmp/apt-dpkg-install-vOkgKo/16-python3-pbcommand_1.1.1+git20191122.ec024c3-1_all.deb (--unpack): trying to overwrite '/usr/share/man/man1/pbservice.1.gz', which is also in package python-pbcommand 1.1.1-1 Errors were encountered while processing: /tmp/apt-dpkg-install-vOkgKo/16-python3-pbcommand_1.1.1+git20191122.ec024c3-1_all.deb cheers, Andreas python-pbcommand=1.1.1-1_python3-pbcommand=1.1.1+git20191122.ec024c3-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: python-pbcommand Source-Version: 1.1.1+git20191122.ec024c3-2 We believe that the bug you reported is fixed in the latest version of python-pbcommand, 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 946...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated python-pbcommand package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 16 Dec 2019 07:46:37 +0100 Source: python-pbcommand Binary: python3-pbcommand Architecture: source Version: 1.1.1+git20191122.ec024c3-2 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Description: python3-pbcommand - common command-line interface for Pacific Biosciences analysis mo Closes: 946800 Changes: python-pbcommand (1.1.1+git20191122.ec024c3-2) unstable; urgency=medium . * Breaks+Provides+Replaces: python-pbcommand Closes: #946800 Checksums-Sha1: acf9afa036656077fb319982b0448f0610ef3a72 2537 python-pbcommand_1.1.1+git20191122.ec024c3-2.dsc 6c3b43deb6c5da6fb6434ad9da93a8a1fd42f856 5068 python-pbcommand_1.1.1+git20191122.ec024c3-2.debian.tar.xz Checksums-Sha256: f929f36968d1c288a29e4db865c5d8c4d213c7bbfccbe84a6f08aea74b23f91d 2537 python-pbcommand_1.1.1+git20191122.ec024c3-2.dsc 6faa02a7169cc7a2fa894191813126cecba76d51145c050d5b09c26bb0ccaf36 5068 python-pbcommand_1.1.1+git20191122.ec024c3-2.debian.tar.xz Files: 96c64d60ceb326d8a295eec76fd84158 2537 python optional python-pbcommand_1.1.1+git20191122.ec024c3-2.dsc 7822d340318529620ee97ba367474cdd 5068 python optional python-pbcommand_1.1.1+git20191122.ec024c3-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl33LwYRHHRpbGxlQGRl Ymlhbi5vcmcACgkQV4oElNHGRtGz+A/+IcLa1qZXl7s5PasbC5SSMquSgh5w2qLz i0pF2Nyxb4uKU/eCBs9jnVa9UCmFUdqtDZVb8Zo+wGsHX274P1h4Z9t+SF/KPLUc oiRedRc8JcRIowmhpJLwB7ML3pQ4y92zKu/N0jAv+snZc3uleRh2qFWPjjDaTuc5 YcNg9ix9VwshDsRoIZxbzB+0bbzuv1U7LrPPq5ts2ea2l7vUGIz1v7mQOBb4Ckqw Yh19hqrRboKj+ZOAcgKUarVNBPQP+asLqOkc7qfraK7VSPQkcmgCZFHPcftxguXA fhzQgym6soaRPabF56bGlTxGlxqhUZe501+fDo87mTRVuXzMcmcCfhwmUUYX7TZf 8REmc5ZYP+G0E7xKesBBQd0hDzt+UA0u9GGTj90kIW7KnLzs0E3nEYarTY/NlVs6 199M+E29WBb1bRp0baWr7/WVCMoqJoFtzs05aI95Zw5OgbFzCgEkFAWDAqOlu1U6 iYTBDj7OlJEGkgjhEPAP7ezMmuqn5GmDvSxELk6lLWQQjbYiZRFCEV+KdFxAuKHt inJyB1Ro+HamBMxe/MlDlUtyuzouq2e9+pT+H/PSi5u3/WALyTW07s9otTsB1X2l w92DL5AU8T7N
Bug#945920: Chrome bug
Hi! I'm using an up-to-date test system, but chromium is 79.0.3945.79 from sid. The crash/close error also occurred to me. Workaround for me: chrome: // flags "Override software rendering list" change to "enable". Since then the error has not occurred ... -- PP
Bug#941527: Bug #941527: marked as pending in matplotlib
On Sunday, December 15, 2019 4:03:10 PM EST Sandro Tosi wrote: > On Sun, Dec 15, 2019 at 3:48 PM Scott Kitterman wrote: > > > > > https://salsa.debian.org/python-team/modules/matplotlib/commit/b343a > > > > > 4fcf > > > > > 363853002b509d022dde143691f099a > > > > > > > > > > > > > > > > > > > > drop Qt4 from depends; Closes: #941527 > > > > > > > > > > > > > > > > > > When are you going to upload this? matplotlib is currently the last > > > > thing > > > > holding PyQt4 in testing. > > > > > > that's part a new upstream release i was preparing, while doing so, i > > > noticed mpl doc requires a new package, which is prepared and it's > > > waiting in NEW; i'll ping the FTP Masters and see if they can speed it > > > up > > > > I don't see it in New or the archive? What's the status on this? > > Sorry Scott, i was probably not clear: it's not matplotlib in NEW but > sphinx-copybutton, which is a new build-depends of mpl -- can you hav > ea look at that package? thanks! It's marked for accept now. Scott K signature.asc Description: This is a digitally signed message part.
Bug#936840: marked as done (lhapdf: Python2 removal in sid/bullseye)
Your message dated Mon, 16 Dec 2019 06:15:46 + with message-id and subject line Bug#932052: Removed package(s) from unstable has caused the Debian Bug report #936840, regarding lhapdf: 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.) -- 936840: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936840 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:lhapdf Version: 5.9.1-6 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:lhapdf 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: 5.9.1-6+rm Dear submitter, as the package lhapdf has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/932052 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#937473: marked as done (pylucene: Python2 removal in sid/bullseye)
Your message dated Mon, 16 Dec 2019 06:16:16 + with message-id and subject line Bug#944755: Removed package(s) from unstable has caused the Debian Bug report #937473, regarding pylucene: 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.) -- 937473: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937473 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:pylucene Version: 4.10.1+dfsg-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:pylucene 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: 4.10.1+dfsg-2+rm Dear submitter, as the package pylucene has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/944755 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#943202: marked as done (olsrd: Python2 removal in sid/bullseye)
Your message dated Mon, 16 Dec 2019 06:17:07 + with message-id and subject line Bug#946790: Removed package(s) from unstable has caused the Debian Bug report #943202, regarding olsrd: 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.) -- 943202: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943202 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: olsrd Version: 0.6.6.2-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 (the specific reason can be found searching this source package in https://people.debian.org/~morph/mass-bug-py2removal_take2.txt ). 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 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.6.6.2-1+rm Dear submitter, as the package olsrd has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/946790 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#896299: marked as done (python-lucene: lucene fails to import)
Your message dated Mon, 16 Dec 2019 06:16:16 +
with message-id
and subject line Bug#944755: Removed package(s) from unstable
has caused the Debian Bug report #896299,
regarding python-lucene: lucene fails to import
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.)
--
896299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896299
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-lucene
Version: 4.10.1+dfsg-2
Severity: serious
User: helm...@debian.org
Usertags: python-import
After installing python-lucene importing the module lucene
into a python interpreter fails with the following error:
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python2.7/dist-packages/lucene/__init__.py", line 2, in
import os, _lucene
ImportError: libjava.so: cannot open shared object file: No such file or
directory
The vast majority of import failures is attributed to missing dependencies.
Often times that manifests as an ImportError or ModuleNotFoundError.
Typically, dependencies should be inserted by dh-python via ${python:Depends}
or ${python3:Depends}. Thus a missing dependency can be caused by incomplete
install_requires in setup.py. Sometimes a missing dependency of a dependency
is the cause, in such cases this bug should be reassigned.
Helmut
--- End Message ---
--- Begin Message ---
Version: 4.10.1+dfsg-2+rm
Dear submitter,
as the package pylucene has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/944755
The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.
Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.
Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#871366: marked as done (pylucene: FTBFS: Makefile:265: recipe for target 'lucene-java-4.10.x/lucene/expressions/lib/asm-5.2.jar' failed)
Your message dated Mon, 16 Dec 2019 06:16:16 +
with message-id
and subject line Bug#944755: Removed package(s) from unstable
has caused the Debian Bug report #871366,
regarding pylucene: FTBFS: Makefile:265: recipe for target
'lucene-java-4.10.x/lucene/expressions/lib/asm-5.2.jar' failed
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.)
--
871366: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871366
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pylucene
Version: 4.10.1+dfsg-2
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170807 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
> make[2]: Entering directory '/<>/pylucene-4.10.1+dfsg'
> mkdir -p lucene-java-4.10.x/lucene
> mkdir -p lucene-java-4.10.x/lucene/build/core
> rm -f lucene-java-4.10.x/lucene/build/core/lucene-core-4.10.x.jar
> find /usr/share/maven-repo -name `basename
> lucene-java-4.10.x/lucene/build/core/lucene-core-4.10.x.jar` -exec ln -s {}
> lucene-java-4.10.x/lucene/build/core/lucene-core-4.10.x.jar \;
> test -e lucene-java-4.10.x/lucene/build/core/lucene-core-4.10.x.jar
> mkdir -p lucene-java-4.10.x/lucene/build/analysis/common
> rm -f
> lucene-java-4.10.x/lucene/build/analysis/common/lucene-analyzers-common-4.10.x.jar
> find /usr/share/maven-repo -name `basename
> lucene-java-4.10.x/lucene/build/analysis/common/lucene-analyzers-common-4.10.x.jar`
> -exec ln -s {}
> lucene-java-4.10.x/lucene/build/analysis/common/lucene-analyzers-common-4.10.x.jar
> \;
> test -e
> lucene-java-4.10.x/lucene/build/analysis/common/lucene-analyzers-common-4.10.x.jar
> mkdir -p lucene-java-4.10.x/lucene/build/memory
> rm -f lucene-java-4.10.x/lucene/build/memory/lucene-memory-4.10.x.jar
> find /usr/share/maven-repo -name `basename
> lucene-java-4.10.x/lucene/build/memory/lucene-memory-4.10.x.jar` -exec ln -s
> {} lucene-java-4.10.x/lucene/build/memory/lucene-memory-4.10.x.jar \;
> test -e lucene-java-4.10.x/lucene/build/memory/lucene-memory-4.10.x.jar
> mkdir -p lucene-java-4.10.x/lucene/build/highlighter
> rm -f
> lucene-java-4.10.x/lucene/build/highlighter/lucene-highlighter-4.10.x.jar
> find /usr/share/maven-repo -name `basename
> lucene-java-4.10.x/lucene/build/highlighter/lucene-highlighter-4.10.x.jar`
> -exec ln -s {}
> lucene-java-4.10.x/lucene/build/highlighter/lucene-highlighter-4.10.x.jar \;
> test -e
> lucene-java-4.10.x/lucene/build/highlighter/lucene-highlighter-4.10.x.jar
> mkdir -p lucene-java-4.10.x/lucene/build/queryparser
> rm -f
> lucene-java-4.10.x/lucene/build/queryparser/lucene-queryparser-4.10.x.jar
> find /usr/share/maven-repo -name `basename
> lucene-java-4.10.x/lucene/build/queryparser/lucene-queryparser-4.10.x.jar`
> -exec ln -s {}
> lucene-java-4.10.x/lucene/build/queryparser/lucene-queryparser-4.10.x.jar \;
> test -e
> lucene-java-4.10.x/lucene/build/queryparser/lucene-queryparser-4.10.x.jar
> ant -propertyfile /<>/pylucene-4.10.1+dfsg/debian/ant.properties -f
> extensions.xml -Dlucene.dir=lucene-java-4.10.x
> Buildfile: /<>/pylucene-4.10.1+dfsg/extensions.xml
>
> compile:
> [mkdir] Created dir: /<>/pylucene-4.10.1+dfsg/build/classes
> [javac] /<>/pylucene-4.10.1+dfsg/extensions.xml:19: warning:
> 'includeantruntime' was not set, defaulting to build.sysclasspath=last; set
> to false for repeatable builds
> [javac] Compiling 35 source files to
> /<>/pylucene-4.10.1+dfsg/build/classes
> [javac] warning: [options] bootstrap class path not set in conjunction
> with -source 1.5
> [javac] warning: [options] source value 1.5 is obsolete and will be
> removed in a future release
> [javac] warning: [options] target value 1.5 is obsolete and will be
> removed in a future release
> [javac] warning: [options] To suppress warnings about obsolete options,
> use -Xlint:-options.
> [javac] Note: Some input files use or override a deprecated API.
> [javac] Note: Recompile with -Xlint:deprecation for details.
> [javac] Note:
> /<>/pylucene-4.10.1+dfsg/java/org/apache/pylucene/search/PythonFieldComparator.java
> uses unchecked or unsafe operations.
> [javac] Note: Recompile with -Xlint:unchecked for details.
> [javac] 4 warnings
>
> jar:
> [mkdir] Created dir: /<>/pylucene-4.10.1+dfsg/build/jar
> [jar] Building jar:
> /<>/pylucene-4.10.1+dfsg/build/jar/extensions.jar
>
> BUILD SUCCESSFUL
> Total time: 0 seconds
> mkdir -p lucene-java-4.10.x/lucene/build/queries
> rm -f lucene-java-4.
Bug#897779: marked as done (lhapdf: ftbfs with GCC-8)
Your message dated Mon, 16 Dec 2019 06:15:46 + with message-id and subject line Bug#932052: Removed package(s) from unstable has caused the Debian Bug report #897779, regarding lhapdf: ftbfs with GCC-8 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 897779: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897779 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:lhapdf Version: 5.9.1-6 Severity: normal Tags: sid buster User: debian-...@lists.debian.org Usertags: ftbfs-gcc-8 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-8/g++-8, but succeeds to build with gcc-7/g++-7. The severity of this report will be raised before the buster release. The full build log can be found at: http://aws-logs.debian.net/2018/05/01/gcc8/lhapdf_5.9.1-6_unstable_gcc8.log.gz The last lines of the build log are at the end of this report. To build with GCC 8, either set CC=gcc-8 CXX=g++-8 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-8/porting_to.html [...] CALL AFPOLIN(AS,AF,N,S,AANS,DY) 1 Error: Actual argument contains too few elements for dummy argument 'xa' (3/10) at (1) wrapacfgpg.f:628:19: CALL AFPOLIN(AS,AF,N,S,AANS,DY) 1 Error: Actual argument contains too few elements for dummy argument 'xa' (3/10) at (1) make[2]: *** [Makefile:701: wrapacfgpg.lo] Error 1 make[2]: Leaving directory '/<>/src' make[2]: *** Waiting for unfinished jobs make[2]: Entering directory '/<>/src' /bin/bash ../libtool--mode=compile gfortran -ffree-form -I. -I. -D_FORTIFY_SOURCE=2 -fstack-protector --param=ssp-buffer-size=4 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -ffree-form -c -o wraplacg.lo wraplacg.f libtool: compile: gfortran -ffree-form -I. -I. -D_FORTIFY_SOURCE=2 -fstack-protector --param=ssp-buffer-size=4 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -ffree-form -c wraplacg.f -fPIC -o .libs/wraplacg.o libtool: compile: gfortran -ffree-form -I. -I. -D_FORTIFY_SOURCE=2 -fstack-protector --param=ssp-buffer-size=4 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -ffree-form -c wraplacg.f -o wraplacg.o >/dev/null 2>&1 make[2]: Leaving directory '/<>/src' make[2]: Entering directory '/<>/src' /bin/bash ../libtool--mode=compile gfortran -ffree-form -I. -I. -D_FORTIFY_SOURCE=2 -fstack-protector --param=ssp-buffer-size=4 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -ffree-form -c -o wrapgrvg.lo wrapgrvg.f libtool: compile: gfortran -ffree-form -I. -I. -D_FORTIFY_SOURCE=2 -fstack-protector --param=ssp-buffer-size=4 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -ffree-form -c wrapgrvg.f -fPIC -o .libs/wrapgrvg.o libtool: compile: gfortran -ffree-form -I. -I. -D_FORTIFY_SOURCE=2 -fstack-protector --param=ssp-buffer-size=4 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -ffree-form -c wrapgrvg.f -o wrapgrvg.o >/dev/null 2>&1 make[2]: Leaving directory '/<>/src' make[2]: Entering directory '/<>/src' /bin/bash ../libtool--mode=compile gfortran -ffree-form -I. -I. -D_FORTIFY_SOURCE=2 -fstack-protector --param=ssp-buffer-size=4 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -ffree-form -c -o wrapgsg96.lo wrapgsg96.f libtool: compile: gfortran -ffree-form -I. -I. -D_FORTIFY_SOURCE=2 -fstack-protector --param=ssp-buffer-size=4 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -ffree-form -c wrapgsg96.f -fPIC -o .libs/wrapgsg96.o libtool: compile: gfortran -ffree-form -I. -I. -D_FORTIFY_SOURCE=2 -fstack-protector --param=ssp-buffer-size=4 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -ffree-form -c wrapgsg96.f -o wrapgsg96.o >/dev/null 2>&1 make[2]: Leaving directory '/<>/src' make[2]: Entering directory '/<>/src' /bin/bash ../libtool--mode=compile gfortran -ffree-form -I. -I. -D_FORTIFY_SOURCE=2 -fstack-protector --param=ssp-buffer-size=4 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -ffree-form
Bug#946353: marked as done (tran: Conflict for [ა] in mtavruli>latin, it resolves to [a] and [a])
Your message dated Mon, 16 Dec 2019 05:04:27 + with message-id and subject line Bug#946353: fixed in tran 5-1 has caused the Debian Bug report #946353, regarding tran: Conflict for [ა] in mtavruli>latin, it resolves to [a] and [a] 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.) -- 946353: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946353 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: tran Version: 4-1 Severity: grave tran no longer works in unstable: $ echo foo | tran Conflict for [ა] in mtavruli>latin, it resolves to [a] and [a] -- System Information: Architecture: i386 -- Jakub Wilk --- End Message --- --- Begin Message --- Source: tran Source-Version: 5-1 We believe that the bug you reported is fixed in the latest version of tran, 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 946...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Adam Borowski (supplier of updated tran package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 16 Dec 2019 05:41:47 +0100 Source: tran Architecture: source Version: 5-1 Distribution: unstable Urgency: medium Maintainer: Adam Borowski Changed-By: Adam Borowski Closes: 946353 Changes: tran (5-1) unstable; urgency=medium . * New upstream release. + Handles mkhedruli uppercasing to mtavruli in new Unicode. (closes: #946353) Checksums-Sha1: 3dc35b583256b18a6d0345e0d8db2bab612a7e21 1789 tran_5-1.dsc 91f4c6f2e42724d1ceaab326309df93a2f6579cf 17701 tran_5.orig.tar.gz edf1d25a393fadda82a5ec89e3f183e02aae04f3 2444 tran_5-1.debian.tar.xz 62c66dddb9d59847744b33a8bfe8c8ff20cbbba1 5743 tran_5-1_source.buildinfo Checksums-Sha256: 691c5258f2c3f172743748345d652b19989be9e9161f53682d5ba736471c9cdf 1789 tran_5-1.dsc 0cc4db3f7611a83e8fcf0223eb8ef151252c18e8311a931653286010c8589897 17701 tran_5.orig.tar.gz f8e2eb6e48053e8bb2f9b85db4279b196cdee229ef85c1f81c4817546f1763e9 2444 tran_5-1.debian.tar.xz a957430eaeb78a0e0845fe676a4f671ad1b368a172a3e4d55d3c1cd0919fcdb7 5743 tran_5-1_source.buildinfo Files: 25da98484a52d87821864667ec0224e7 1789 text optional tran_5-1.dsc 9626c63cafffbf5289a2d12a1ecc8658 17701 text optional tran_5.orig.tar.gz b5a7b5b5296f10abe28d780502f39de7 2444 text optional tran_5-1.debian.tar.xz a03c90bc38c59a64f446d9d04c8f1b7a 5743 text optional tran_5-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEkjZVexcMh/iCHArDweDZLphvfH4FAl33C/wUHGtpbG9ieXRl QGFuZ2JhbmQucGwACgkQweDZLphvfH4W9xAAtC5LCpvNbta1nlbosJcybXvb4H5K oILoHKbI1cRwcHmttPNtRkwmQadJfx3eZ5JxIrcQdueOH5Zg44ekygzxSAOsc0R7 jmpCO2vn+xheobkXgESMZfTI4pmP6luols8/1oTRbnEUEDD3YHYEL31rznT8QYzi d1vTJSix7BVDqQwJL4OEROfDx9yFsqN0sT48HNeYc0m3/sWoYQCnzu7hy8QU9+7c XCZ/FJQANKvqmWQBzfGj5HjeLjHgJCBiFQCsTS2sjLNvGHmTB7yCK26uA8s+LIDc iqRxs5y1VTwvV4A+oazNf/Isx2z6ujlYpLWAwWZctwyZcTKdsQ5Qmk0BE0XMe7w5 aVN+PT1jWXhnu8+hneojvmqjanY6JxP8ha41TwTa/KkK9DdfqZUV1hfkVE0vMDns R1dI40pDkFBdSsVzFlVllUvYxEMASwIimEG6q6yuTxpoRepoGeNUTRs9CaSZgvEL TtIr1Vv42kEj43NI5g9vmmyHbzN3w1cSEroQ/rSs6fAZwDp1VxkpwnA9pJdYbWt7 2gP5fuOmwzdoRev3PEj+qb6UZchupvwpVj+4buLhveZFxOn3/tuxcZR6hboKKLw0 aGZhfGNCwaxeFUIasfyKnKC9X21e0yyyZjLNQ6TpA1uagGrHNxGfsGwKFXuotS+n Bgr1xz4B02EUJIw= =D6zq -END PGP SIGNATURE End Message ---
Bug#907489: Fixing sambamba 0.8.6
Am So., 15. Dez. 2019 um 10:16 Uhr schrieb Pjotr Prins : > [...] > > Therefore, the way of least resistance was to just use Meson for > > building, as that does everything we need in Debian. Both BioD and > > Sambamba build well with Meson. > > That is great. We can add the meson builds in the repos. That's something I forgot in my last mail: I didn't create PRs, because Meson support was upstream once but was removed. Also because it's understandable if upstream projects want to reduce the amount of ways a software can be built. As it happens though, I have already created (by accident) build definitions that work for the current upstream code of BioD/Sambamba. I've created PRs for those now. Having this upstream would obviously be great, and if there are issues with it, I can help. (The definitions are really straightforward to use though) See https://github.com/biod/BioD/pull/54 and https://github.com/biod/sambamba/pull/419 Integration with CI is possible, but your Travis YAML will become a bit bigger ^^ > > I applied a few tweaks to the packages, that haven't been there > > before: BioD is now built as a shared as well as a static library, so > > applications can choose between the two. That's pretty common in > > Debian, and as a sideeffect this also guarantees that things are > > rebuilt properly when a transition happens. The Sambamba package will > > now prefer statically linking BioD if possible (so BioD is statically > > linked by default now in Debian). > > Additionally both packages now apply the optimization flags upstream > > has set for releases (-O3, no bounds checks, etc.). Combined, these > > two changes should make the Debian builds comparably fast to the > > upstream builds, but I haven't tested that yet. > > > There are also two brand new remaining issues: Apparently, for some > > reason, SONAME isn't set correctly for BioD, producing a Lintian error > > - not sure what happens there, and which component is to blame for > > that (Meson or LDC, most likely). Also, Sambamba doesn't *actually* > > build yet: > > ``` > > roup -L=-rpath > > -L=/usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu:/usr/lib/x86_64-linux-gnu > > slicereader.d:71: error: undefined reference to 'cram_to_bam' > > collect2: error: ld returned 1 exit status > > ``` > > The cram_to_bam is private in htslib, so it shouldn't be used by other > > applications. Not sure whether htslib or Sambamba needs to be changed > > here, I simply worked around this issue for testing, and when this is > > resolved, Sambamba builds & works. > > Sambamba ships with an old version of htslib that is patched for that > function call. I plan to drop CRAM support and htslib. No one I know > uses the CRAM functionality in sambamba. It certainly wasn't needed for the tests :-D I don't think we should silently comment that out from the Debian builds though... > > Unfortunately I briefly forgot that this issue existed, so I already > > uploaded the new sambamba package with this issue still present (I > > remembered literally the moment the upload finished), so its builds > > will fail. This is probably something for Andreas to look into :-) > > > > Anyway, I hope this is helpful to you and the resulting binaries are > > performant :-) > > Thanks Matthias! If the last issues can be fixed, this may just be in time for the next Ubuntu LTS release, which is probably something that you'll want ;-) Currently, BioD fails to build on x86: https://buildd.debian.org/status/fetch.php?pkg=libbiod&arch=i386&ver=0.2.3%2Bgit20191120.b8eecef-1&stamp=1576379323&raw=0 This issue looks trivial to me, it's probably a matter of using size_t instead of plain ints. There's of course also the question of whether we need to support x86 with this package, but in any case, this FTBFS will block the package in unstable until it has either been removed from i386 or the build failure has been fixed. The good news is that the package builds on arm64 now though - yay? ^^ Sambamba is only failing on missing cram_to_bam, so once that's fixed, it should be good to go as well. Cheers, Matthias -- I welcome VSRE emails. See http://vsre.info/
Bug#942737: libapache2-mod-gnutls: mod_gnutls consumes 100% cpu
Dear Maintainer, tried to reconstruct the given backtrace with debug symbols in a gdb session and came to following, maybe it could be of some help. (Still a proper backtrace with dbgsym packages installed would be better.) Kind regards, Bernhard Reconstructed: #0 0x7f78b4cfb92f in gnutls_assert_val_int at ../../lib/errors.h:139 from libgnutls.so.30 #1 0x7f78b4cfdf7c in _gnutls_recv_int at ../../lib/record.c:1773 from libgnutls.so.30 in gnutls_record_recv at ../../lib/record.c:2281 #2 0x7f78b4e90f38 in gnutls_io_input_read at gnutls_io.c:246 from mod_gnutls.so #3 0x7f78b4e91ad2 in gnutls_io_input_getline at gnutls_io.c:342 from mod_gnutls.so in mgs_filter_input at gnutls_io.c:595 in ap_get_brigade at util_filter.c:553 #4 0x55c220cd08e1 in ap_rgetline_core at protocol.c:246 #5 0x55c220cd336c in read_request_line at protocol.c:682 in ap_read_request at protocol.c:1322 #6 0x55c220cfe7a8 in ap_process_http_sync_connection at http_core.c:192 #7 0x55c220cf38b0 in ap_run_process_connection at connection.c:42 in ap_process_connection at connection.c:219 #8 0x7f78b3bd23df in child_main at prefork.c:615 from mod_mpm_prefork.so #9 0x7f78b3bd26d4 in make_child at prefork.c:717 from mod_mpm_prefork.so #10 0x7f78b3bd272f in startup_children at prefork.c:735 from mod_mpm_prefork.so #11 0x7f78b3bd32f3 in prefork_run at prefork.c:897 from mod_mpm_prefork.so #12 0x55c220ccc67e in ap_run_mpm at mpm_common.c:94 #13 0x55c220cc4f57 in main at main.c:819
Processed: severity of 941633 is important
Processing commands for cont...@bugs.debian.org: > severity 941633 important Bug #941633 [synfigstudio] synfigstudio crashes on almost every operation Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 941633: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941633 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#944426: Still not able to update
Hi! The problem is still there for lazarus-src-2.0_2.0.6+dfsg-3_all.deb. It was actually also there for 2.0.6+dfsg-2 as well as 2.0.6+dfsg-1. The only thing which helps is forcing it, but it gives a huge load of warnings: # dpkg -i --force-all /var/cache/apt/archives/lazarus-src-2.0_2.0.6+dfsg-3_all.deb (Reading database ... 528262 files and directories currently installed.) Preparing to unpack .../lazarus-src-2.0_2.0.6+dfsg-3_all.deb ... Unpacking lazarus-src-2.0 (2.0.6+dfsg-3) over (2.0.6+dfsg-2) ... dpkg: warning: overriding problem because --force enabled: dpkg: warning: trying to overwrite '/usr/lib/lazarus/2.0.6/components/IdeInspector/ideinspector.lpk', which is also in package lcl-units-2.0 2.0.6+dfsg-3 dpkg: warning: overriding problem because --force enabled: dpkg: warning: trying to overwrite '/usr/lib/lazarus/2.0.6/components/IdeLazLogger/idelazlogger.lpk', which is also in package lcl-units-2.0 2.0.6+dfsg-3 dpkg: warning: overriding problem because --force enabled: dpkg: warning: trying to overwrite '/usr/lib/lazarus/2.0.6/components/PascalScript/Source/pascalscript.lpk', which is also in package lcl-units-2.0 2.0.6+dfsg-3 dpkg: warning: overriding problem because --force enabled: dpkg: warning: trying to overwrite '/usr/lib/lazarus/2.0.6/components/PascalScript/Source/pascalscriptfcl.lpk', which is also in package lcl-units-2.0 2.0.6+dfsg-3 dpkg: warning: overriding problem because --force enabled: dpkg: warning: trying to overwrite '/usr/lib/lazarus/2.0.6/components/aarre/src/aarrebase.lpk', which is also in package lcl-units-2.0 2.0.6+dfsg-3 dpkg: warning: overriding problem because --force enabled: dpkg: warning: trying to overwrite '/usr/lib/lazarus/2.0.6/components/activex/LazActiveX.lpk', which is also in package lcl-units-2.0 2.0.6+dfsg-3 dpkg: warning: overriding problem because --force enabled: dpkg: warning: trying to overwrite '/usr/lib/lazarus/2.0.6/components/aggpas/lazarus/aggpaslcl.lpk', which is also in package lcl-units-2.0 2.0.6+dfsg-3 dpkg: warning: overriding problem because --force enabled: dpkg: warning: trying to overwrite '/usr/lib/lazarus/2.0.6/components/anchordocking/anchordocking.lpk', which is also in package lcl-units-2.0 2.0.6+dfsg-3 dpkg: warning: overriding problem because --force enabled: dpkg: warning: trying to overwrite '/usr/lib/lazarus/2.0.6/components/anchordocking/design/anchordockingdsgn.lpk', which is also in package lcl-units-2.0 2.0.6+dfsg-3 dpkg: warning: overriding problem because --force enabled: dpkg: warning: trying to overwrite '/usr/lib/lazarus/2.0.6/components/cairocanvas/cairocanvas_pkg.lpk', which is also in package lcl-units-2.0 2.0.6+dfsg-3 dpkg: warning: overriding problem because --force enabled: dpkg: warning: trying to overwrite '/usr/lib/lazarus/2.0.6/components/chmhelp/packages/help/lhelpcontrolpkg.lpk', which is also in package lcl-units-2.0 2.0.6+dfsg-3 dpkg: warning: overriding problem because --force enabled: dpkg: warning: trying to overwrite '/usr/lib/lazarus/2.0.6/components/chmhelp/packages/idehelp/chmhelppkg.lpk', which is also in package lcl-units-2.0 2.0.6+dfsg-3 dpkg: warning: overriding problem because --force enabled: dpkg: warning: trying to overwrite '/usr/lib/lazarus/2.0.6/components/codetools/codetools.lpk', which is also in package lcl-units-2.0 2.0.6+dfsg-3 dpkg: warning: overriding problem because --force enabled: dpkg: warning: trying to overwrite '/usr/lib/lazarus/2.0.6/components/codetools/ide/cody.lpk', which is also in package lcl-units-2.0 2.0.6+dfsg-3 dpkg: warning: overriding problem because --force enabled: dpkg: warning: trying to overwrite '/usr/lib/lazarus/2.0.6/components/compilers/c/lazc.lpk', which is also in package lcl-units-2.0 2.0.6+dfsg-3 dpkg: warning: overriding problem because --force enabled: dpkg: warning: trying to overwrite '/usr/lib/lazarus/2.0.6/components/customdrawn/customdrawn.lpk', which is also in package lcl-units-2.0 2.0.6+dfsg-3 dpkg: warning: overriding problem because --force enabled: dpkg: warning: trying to overwrite '/usr/lib/lazarus/2.0.6/components/customform/demo/appforms.lpk', which is also in package lcl-units-2.0 2.0.6+dfsg-3 dpkg: warning: overriding problem because --force enabled: dpkg: warning: trying to overwrite '/usr/lib/lazarus/2.0.6/components/customform/lazcustforms.lpk', which is also in package lcl-units-2.0 2.0.6+dfsg-3 dpkg: warning: overriding problem because --force enabled: dpkg: warning: trying to overwrite '/usr/lib/lazarus/2.0.6/components/daemon/lazdaemon.lpk', which is also in package lcl-units-2.0 2.0.6+dfsg-3 dpkg: warning: overriding problem because --force enabled: dpkg: warning: trying to overwrite '/usr/lib/lazarus/2.0.6/components/datadict/lazdatadict.lpk', which is also in package lcl-units-2.0 2.0.6+dfsg-3 dpkg: warning: overriding problem because --force enabled: dpkg: warning: trying to overwrite '/usr/lib/lazarus/2.0.6/components/datetimectrls/datetimectrls.lpk', which is also in pack
Bug#946802: python3-minieigen: missing Breaks+Replaces: python-minieigen
Package: python3-minieigen Version: 0.50.3+dfsg1-10 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 .../python3-minieigen_0.50.3+dfsg1-10_amd64.deb ... Unpacking python3-minieigen (0.50.3+dfsg1-10) ... dpkg: error processing archive /var/cache/apt/archives/python3-minieigen_0.50.3+dfsg1-10_amd64.deb (--unpack): trying to overwrite '/usr/share/doc-base/python-minieigen', which is also in package python-minieigen 0.50.3+dfsg1-9 Errors were encountered while processing: /var/cache/apt/archives/python3-minieigen_0.50.3+dfsg1-10_amd64.deb cheers, Andreas python-minieigen=0.50.3+dfsg1-9_python3-minieigen=0.50.3+dfsg1-10.log.gz Description: application/gzip
Bug#946800: python3-pbcommand: missing Breaks+Replaces: python-pbcommand (<< 1.1.1+git20191122.ec024c3)
Package: python3-pbcommand Version: 1.1.1+git20191122.ec024c3-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...): Selecting previously unselected package python3-pbcommand. Preparing to unpack .../16-python3-pbcommand_1.1.1+git20191122.ec024c3-1_all.deb ... Unpacking python3-pbcommand (1.1.1+git20191122.ec024c3-1) ... dpkg: error processing archive /tmp/apt-dpkg-install-vOkgKo/16-python3-pbcommand_1.1.1+git20191122.ec024c3-1_all.deb (--unpack): trying to overwrite '/usr/share/man/man1/pbservice.1.gz', which is also in package python-pbcommand 1.1.1-1 Errors were encountered while processing: /tmp/apt-dpkg-install-vOkgKo/16-python3-pbcommand_1.1.1+git20191122.ec024c3-1_all.deb cheers, Andreas python-pbcommand=1.1.1-1_python3-pbcommand=1.1.1+git20191122.ec024c3-1.log.gz Description: application/gzip
Bug#939401: marked as done (nvidia-driver-libs-nonglvnd: Xorg crashing when running with nonglvnd libraries)
Your message dated Sun, 15 Dec 2019 22:30:13 + with message-id and subject line Bug#939401: fixed in nvidia-graphics-drivers 430.64-4 has caused the Debian Bug report #939401, regarding nvidia-driver-libs-nonglvnd: Xorg crashing when running with nonglvnd libraries 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.) -- 939401: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939401 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: nvidia-driver Version: 430.40-2 Severity: grave Justification: renders package unusable Dear Maintainer, * What led up to the situation? I upgraded the nvidia-driver package (version 418) to the newer version 430.40-2 * What was the outcome of this action? Every time I boot my computer with the NVIDIA driver version 430 installed, I end up in an infinite loop between the tty and Xorg starting and instantly crashing. Switching ttys does not seem to work. * What exactly did you do (or not do) that was effective (or ineffective)? I tried rebooting with an older kernel to reinstall the driver, which did not work. I also tried unplugging my second monitor and deleting the xorg.conf file. This didn't help either. I have resorted to using the legacy 390 driver for now. * What outcome did you expect instead? I expected my system to boot normally after the upgrade. I use a GTX 1050 Ti with a dual-monitor setup, one monitor using DVI and one using HDMI. The Xorg log can be found here: https://paste.debian.net/1098761/ -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.2.0-2-amd64 (SMP w/6 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=en_US (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages nvidia-driver depends on: pn nvidia-alternative pn nvidia-driver-bin pn nvidia-driver-libs | nvidia-driver-libs-nonglvnd ii nvidia-installer-cleanup 20151021+9 pn nvidia-kernel-dkms | nvidia-kernel-430.40 ii nvidia-legacy-check 430.40-2 ii nvidia-support20151021+9 pn nvidia-vdpau-driver pn xserver-xorg-video-nvidia Versions of packages nvidia-driver recommends: pn libnvidia-cfg1 ii nvidia-persistenced 418.56-1 pn nvidia-settings Versions of packages nvidia-driver suggests: pn nvidia-kernel-dkms | nvidia-kernel-source --- End Message --- --- Begin Message --- Source: nvidia-graphics-drivers Source-Version: 430.64-4 We believe that the bug you reported is fixed in the latest version of nvidia-graphics-drivers, 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 939...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Beckmann (supplier of updated nvidia-graphics-drivers package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 15 Dec 2019 22:39:11 +0100 Source: nvidia-graphics-drivers Architecture: source Version: 430.64-4 Distribution: unstable Urgency: medium Maintainer: Debian NVIDIA Maintainers Changed-By: Andreas Beckmann Closes: 939401 Changes: nvidia-graphics-drivers (430.64-4) unstable; urgency=medium . * Do not build most non-GLVND packages (435.17-1). (Closes: #939401) Checksums-Sha1: 7aacc2cfb5c12bc1306eaeaa725a3f9142886e30 6274 nvidia-graphics-drivers_430.64-4.dsc 783d9d91055cd9b6602cd4487f305856763ee790 189632 nvidia-graphics-drivers_430.64-4.debian.tar.xz 2f1dd605255640a3ca6f46b4de062ce7922c79ec 7860 nvidia-graphics-drivers_430.64-4_source.buildinfo Checksums-Sha256: 5ab4a8ed53138056e009cfe9087a60cc20b7fc2ac1890a83f3a35e04a5fc48e3 6274 nvidia-graphics-drivers_430.64-4.dsc 183266fc403d112b851dee720
Bug#939489: marked as done (nvidia-driver-libs-nonglvnd: Xorg crashing when running with nonglvnd libraries)
Your message dated Sun, 15 Dec 2019 22:30:13 + with message-id and subject line Bug#939401: fixed in nvidia-graphics-drivers 430.64-4 has caused the Debian Bug report #939401, regarding nvidia-driver-libs-nonglvnd: Xorg crashing when running with nonglvnd libraries 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.) -- 939401: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939401 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: bumblebee-nvidia Version: 3.2.1-20 Severity: grave I upgrade my debian just now. The nvidia-driver and other nvidia packages were upgraded to 430.40-2. Then I found that bumblebee fails to disable discrete graphics card. We can not run opengl software with command "optirun", and when I run "lspci -nn | grep VGA", I got the message: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3e94] 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP107GLM [Quadro P2000 Mobile] [10de:1cba] (rev al) It seem that the nvidia video card can not be disabled. My laptop is Thinkpad P1. How do I resolve this error? Thank you very much! Best regards, Gulfstream -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.2.0-2-amd64 (SMP w/12 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8), LANGUAGE=zh_CN.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages bumblebee-nvidia depends on: ii bumblebee3.2.1-20 ii glx-alternative-nvidia 1.0.0 ii nvidia-driver430.40-2 ii nvidia-kernel-dkms 430.40-2 ii nvidia-legacy-390xx-kernel-dkms 390.129-1 bumblebee-nvidia recommends no packages. bumblebee-nvidia suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: nvidia-graphics-drivers Source-Version: 430.64-4 We believe that the bug you reported is fixed in the latest version of nvidia-graphics-drivers, 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 939...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Beckmann (supplier of updated nvidia-graphics-drivers package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 15 Dec 2019 22:39:11 +0100 Source: nvidia-graphics-drivers Architecture: source Version: 430.64-4 Distribution: unstable Urgency: medium Maintainer: Debian NVIDIA Maintainers Changed-By: Andreas Beckmann Closes: 939401 Changes: nvidia-graphics-drivers (430.64-4) unstable; urgency=medium . * Do not build most non-GLVND packages (435.17-1). (Closes: #939401) Checksums-Sha1: 7aacc2cfb5c12bc1306eaeaa725a3f9142886e30 6274 nvidia-graphics-drivers_430.64-4.dsc 783d9d91055cd9b6602cd4487f305856763ee790 189632 nvidia-graphics-drivers_430.64-4.debian.tar.xz 2f1dd605255640a3ca6f46b4de062ce7922c79ec 7860 nvidia-graphics-drivers_430.64-4_source.buildinfo Checksums-Sha256: 5ab4a8ed53138056e009cfe9087a60cc20b7fc2ac1890a83f3a35e04a5fc48e3 6274 nvidia-graphics-drivers_430.64-4.dsc 183266fc403d112b851dee7208434dff07d42958ea0b7877cd9cbad5e26f80fe 189632 nvidia-graphics-drivers_430.64-4.debian.tar.xz 8d4a71f136a6435e49333a162e7f799eb31c048ffdc77e85e20125260803e103 7860 nvidia-graphics-drivers_430.64-4_source.buildinfo Files: 3911bdd6cd27c302d284afd57179f6f1 6274 non-free/libs optional nvidia-graphics-drivers_430.64-4.dsc 7ae6d51c82c7e627767053e487002a2f 189632 non-free/libs optional nvidia-graphics-drivers_430.64-4.debian.tar.xz 845ddd81360fe393d88644af26b285ba 7860 non-free/libs optional nvidia-graphics-drivers_430.64-4_source.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAl32qW0QHGFuYmVAZGVi aWFuLm9yZwAKCRBfsz+TWentCPMyD/48ArEndS9GtlukPjMiQkYkiCCwmqgWNljg n1K+g60dxjnW4kDM64hbobSubK+9ZEVtFrG0QpyZ1cAOT105+1bpjJ4MRb7nwr8m KSj6q2/z9tVZlntjGq0dNHQheDRz3
Bug#939643: marked as done (nvidia-driver-libs-nonglvnd: Xorg crashing when running with nonglvnd libraries)
Your message dated Sun, 15 Dec 2019 22:30:13 + with message-id and subject line Bug#939401: fixed in nvidia-graphics-drivers 430.64-4 has caused the Debian Bug report #939401, regarding nvidia-driver-libs-nonglvnd: Xorg crashing when running with nonglvnd libraries 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.) -- 939401: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939401 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: bumblebee Version: 3.2.1-20 Severity: normal Hi, bumblebee stops working when I install nvidia drivers version 430.40-2. Everything is fine, instead, with previous version 418.88-1. The bug manifests itself as: $ optirun glxgears [162424.750419] [ERROR]Cannot access secondary GPU - error: [XORG] (EE) NVIDIA(GPU-0): Failed to initialize the NVIDIA GPU at PCI:1:0:0. Please [162424.750441] [ERROR]Aborting because fallback start is disabled. Syslog has: > Sep 7 11:05:11 amalgama bumblebeed[20985]: [163003.002983] [WARN][XORG] (WW) > NVIDIA(0): Unable to get display device for DPI computation. > Sep 7 11:05:11 amalgama bumblebeed[20985]: [163003.003001] [WARN][XORG] (WW) > NVIDIA(0): Option "NoLogo" is not used > Sep 7 11:05:11 amalgama bumblebeed[20985]: [163003.003011] [ERROR][XORG] (EE) > Sep 7 11:05:11 amalgama bumblebeed[20985]: [163003.003015] [ERROR][XORG] > (EE) Backtrace: > Sep 7 11:05:11 amalgama bumblebeed[20985]: [163003.003019] [ERROR][XORG] > (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x562bef9812c9] > Sep 7 11:05:11 amalgama bumblebeed[20985]: [163003.003022] [ERROR][XORG] > (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x50) > [0x7fb671c2677f] > Sep 7 11:05:11 amalgama bumblebeed[20985]: [163003.003026] [ERROR][XORG] > (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (memcpy+0x1f) [0x7fb671af303f] > Sep 7 11:05:11 amalgama bumblebeed[20985]: [163003.003029] [ERROR][XORG] > (EE) 3: /usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.430.40 > (_nv043glcore+0x27ff39) [0x7fb670713339] > Sep 7 11:05:11 amalgama bumblebeed[20985]: [163003.003032] [ERROR][XORG] > (EE) 4: /usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.430.40 > (_nv043glcore+0x28009d) [0x7fb67071365d] > Sep 7 11:05:11 amalgama bumblebeed[20985]: [163003.003036] [ERROR][XORG] > (EE) 5: /usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.430.40 > (_nv015glcore+0x49bb8) [0x7fb6701c5ba8] > Sep 7 11:05:11 amalgama bumblebeed[20985]: [163003.003039] [ERROR][XORG] > (EE) unw_get_proc_name failed: no unwind info found [-10] > Sep 7 11:05:11 amalgama bumblebeed[20985]: [163003.003042] [ERROR][XORG] > (EE) 6: /usr/lib/nvidia/nvidia/libglxserver_nvidia.so (?+0x0) [0x7fb66e15cd32] > Sep 7 11:05:11 amalgama bumblebeed[20985]: [163003.003045] [ERROR][XORG] (EE) > Sep 7 11:05:11 amalgama bumblebeed[20985]: [163003.003049] [ERROR][XORG] > (EE) Segmentation fault at address 0x7fb66e256000 > Sep 7 11:05:11 amalgama bumblebeed[20985]: [163003.003053] [ERROR][XORG] (EE) > Sep 7 11:05:11 amalgama bumblebeed[20985]: [163003.003057] [ERROR][XORG] > (EE) Caught signal 11 (Segmentation fault). Server aborting > Sep 7 11:05:11 amalgama bumblebeed[20985]: [163003.003062] [ERROR][XORG] (EE) > Sep 7 11:05:11 amalgama bumblebeed[20985]: [163003.003067] [ERROR][XORG] (EE) > Sep 7 11:05:11 amalgama bumblebeed[20985]: [163003.003074] [ERROR][XORG] > (EE) Please also check the log file at "/var/log/Xorg.8.log" for additional > information. > Sep 7 11:05:11 amalgama bumblebeed[20985]: [163003.003083] [ERROR][XORG] (EE) > Sep 7 11:05:11 amalgama bumblebeed[20985]: [163003.029955] [ERROR][XORG] > (EE) Server terminated with error (1). Closing log file. > Sep 7 11:05:11 amalgama bumblebeed[20985]: [163003.029971] [ERROR]X did not > start properly The Xorg.log file does not seem to have any additional relevant information, but I am attaching it in case it helps. This thread[1] seems to be related to the same problem, and it seems to have a workaround, but I could not understand how to apply it. [1] https://github.com/Bumblebee-Project/Bumblebee/issues/153 Thanks, Giovanni. --- System information. --- Architecture: Kernel: Linux 4.19.0-5-amd64 Debian Release: bullseye/sid 500 xenial updates.signal.org 500 unstable-debug debug.mirrors.debian.org 500 unstabledeb.debian.org 500 testing deb.debian.org 500 stable repo.skype.com 500 stable dl.google.com 1 experimentaldeb.debian.org --- Package information. --- Depends (Version) | Installed =-+- bbs
Bug#943923: marked as done (python-apptools: please stop build-depending on python-pandas)
Your message dated Sun, 15 Dec 2019 22:00:04 +
with message-id
and subject line Bug#943923: fixed in python-apptools 4.4.0-4
has caused the Debian Bug report #943923,
regarding python-apptools: please stop build-depending on python-pandas
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.)
--
943923: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943923
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-apptools
Version: 4.4.0-3
Control: block 937296 by -1
Control: tags -1 patch
pandas upstream dropped Python 2 support in 0.25 (before adding Python
3.8 support). As further discussed in #937296, the Debian package
python-pandas is currently part of a big tangle of circular
(build-)dependencies, but can be cut out of that tangle by removing the
build-dependencies from python-apptools and matplotlib2.
Hence, please apply the attached patch to drop the python-pandas build
dependency and allow the test suite to be run without it.
diff -Nru python-apptools-4.4.0/debian/changelog
python-apptools-4.4.0/debian/changelog
--- python-apptools-4.4.0/debian/changelog 2019-03-05 20:26:46.0
+
+++ python-apptools-4.4.0/debian/changelog 2019-10-31 21:42:13.0
+
@@ -1,3 +1,10 @@
+python-apptools (4.4.0-4) UNRELEASED; urgency=medium
+
+ * Stop build-depending on python-pandas,
+and fix resulting test issues.
+
+ -- Rebecca N. Palmer Thu, 31 Oct 2019 21:42:13
+
+
python-apptools (4.4.0-3) unstable; urgency=medium
* Fixing broken links in python-apptools-doc
diff -Nru python-apptools-4.4.0/debian/control
python-apptools-4.4.0/debian/control
--- python-apptools-4.4.0/debian/control2019-03-05 20:26:46.0
+
+++ python-apptools-4.4.0/debian/control2019-10-31 21:33:48.0
+
@@ -11,7 +11,6 @@
python-setuptools,
python-traits,
python-tables,
- python-pandas,
python-nose,
python-configobj,
python3-all,
diff -Nru python-apptools-4.4.0/debian/patches/series
python-apptools-4.4.0/debian/patches/series
--- python-apptools-4.4.0/debian/patches/series 2019-03-05 20:26:46.0
+
+++ python-apptools-4.4.0/debian/patches/series 2019-10-31 21:42:13.0
+
@@ -4,3 +4,4 @@
dont_delete_tmp
skip_test_file_properties
man_page_section
+test_without_pandas
diff -Nru python-apptools-4.4.0/debian/patches/test_without_pandas
python-apptools-4.4.0/debian/patches/test_without_pandas
--- python-apptools-4.4.0/debian/patches/test_without_pandas1970-01-01
01:00:00.0 +0100
+++ python-apptools-4.4.0/debian/patches/test_without_pandas2019-10-31
21:42:13.0 +
@@ -0,0 +1,52 @@
+Description: Allow importing H5TableNode without pandas
+
+Needed to run the test suite without python-pandas.
+
+Author: Rebecca N. Palmer
+Bug-Debian: https://bugs.debian.org/
+Forwarded: no
+
+--- python-apptools-4.4.0.orig/apptools/io/h5/table_node.py
python-apptools-4.4.0/apptools/io/h5/table_node.py
+@@ -1,5 +1,8 @@
+ import numpy as np
+-from pandas import DataFrame
++try:
++from pandas import DataFrame
++except ImportError:
++DataFrame = None
+ from tables.table import Table as PyTablesTable
+
+
+@@ -116,6 +119,8 @@ class H5TableNode(object):
+ XXX: This does not work if the table contains a multidimensional
column
+ """
+ # Slicing rows gives a numpy struct array, which DataFrame
understands.
++if DataFrame is None:
++raise ImportError("to_dataframe requires pandas, which was not
found")
+ return DataFrame(self.ix[:])
+
+
#--
+--- python-apptools-4.4.0.orig/apptools/io/h5/tests/test_table_node.py
python-apptools-4.4.0/apptools/io/h5/tests/test_table_node.py
+@@ -1,6 +1,10 @@
+ import numpy as np
+ from numpy.testing import assert_allclose
+-from pandas import DataFrame
++from numpy.testing.decorators import skipif
++try:
++from pandas import DataFrame
++except ImportError:
++DataFrame = None
+
+ from ..table_node import H5TableNode
+ from .utils import temp_h5_file
+@@ -46,7 +50,7 @@ def test_keys():
+ h5table = H5TableNode.add_to_h5file(h5, NODE, description)
+ assert set(h5table.keys()) == keys
+
+-
++@skipif(DataFrame == None, "requires pandas")
+ def test_to_dataframe():
+ description = [('a', np.float64)]
+ with temp_h5_file() as h5:
--- End Message ---
--- Begin Message ---
Source: python-apptools
Source-Version: 4.4.0-4
We believe that the bug you reported is fixed in the latest version of
Bug#936585: gbirthday: Python2 removal in sid/bullseye
On Tue, Oct 22, 2019 at 10:04:35PM +0200, Jérôme wrote: > Hi. > > Last gbirthday maintainer speaking. > > The gbirthday package is more or less dead upstream, unless someone > volunteers to take it over. Hi Rolf, are you planning to port it yourself or switch to the mentioned qt port? Otherwise we should remove it from the archive. Cheers, Moritz
Bug#885468: bumping severity of pygtk bugs
On Sun, Oct 06, 2019 at 05:09:30PM -0400, Jeremy Bicha wrote: > Control: severity -1 serious > Control: tags -1 -buster > > > As part of the Python2 removal, it is our intent that pygtk will be removed > from Testing before the release of Debian 11 > "Bullseye". Therefore, I am bumping the severity of this bug to Serious to > ensure that there is plenty of warning before > the Debian 11 release and to make the eventual removal of pygtk as smooth as > possible. The latest pycha 0.8.1 (while ported to Python 3) still uses pygtk2 and there are no reverse deps in the archive, shall we remove it? Cheers, Moritz
Bug#946787: policyd-spf-fs: FTBFS in sid/experimental: undefined reference to many SPF_* symbols
Source: policyd-spf-fs Version: 0+svn27-1 Severity: serious Tags: ftbfs Justification: fails to build from source At some point after the release of buster policyd-spf-fs started to FTBFS: debian/rules build dh_testdir /usr/bin/make LIBS=-lspf2 make[1]: Entering directory '/build/policyd-spf-fs-0+svn27' gcc -g -O2 -Wall -DHAVE_GETOPT_LONG_ONLY -I /usr/include/spf2 -c -o policyd-spf-fs.o policyd-spf-fs.c policyd-spf-fs.c: In function 'main': policyd-spf-fs.c:405:11: warning: variable 'opt_keep_comments' set but not used [-Wunused-but-set-variable] 405 | int opt_keep_comments = 0; | ^ gcc -g -O2 -Wall -DHAVE_GETOPT_LONG_ONLY -lspf2 policyd-spf-fs.o -o policyd-spf-fs /usr/bin/ld: policyd-spf-fs.o: in function `response_print_errors': /build/policyd-spf-fs-0+svn27/policyd-spf-fs.c:226: undefined reference to `SPF_response_message' /usr/bin/ld: /build/policyd-spf-fs-0+svn27/policyd-spf-fs.c:227: undefined reference to `SPF_error_message' /usr/bin/ld: /build/policyd-spf-fs-0+svn27/policyd-spf-fs.c:231: undefined reference to `SPF_error_errorp' /usr/bin/ld: /build/policyd-spf-fs-0+svn27/policyd-spf-fs.c:228: undefined reference to `SPF_error_errorp' /usr/bin/ld: /build/policyd-spf-fs-0+svn27/policyd-spf-fs.c:225: undefined reference to `SPF_response_messages' /usr/bin/ld: /build/policyd-spf-fs-0+svn27/policyd-spf-fs.c:222: undefined reference to `SPF_strerror' /usr/bin/ld: policyd-spf-fs.o: in function `response_print': /build/policyd-spf-fs-0+svn27/policyd-spf-fs.c:252: undefined reference to `SPF_response_result' /usr/bin/ld: /build/policyd-spf-fs-0+svn27/policyd-spf-fs.c:252: undefined reference to `SPF_strresult' /usr/bin/ld: /build/policyd-spf-fs-0+svn27/policyd-spf-fs.c:254: undefined reference to `SPF_response_reason' /usr/bin/ld: /build/policyd-spf-fs-0+svn27/policyd-spf-fs.c:254: undefined reference to `SPF_strreason' /usr/bin/ld: /build/policyd-spf-fs-0+svn27/policyd-spf-fs.c:256: undefined reference to `SPF_response_errcode' /usr/bin/ld: /build/policyd-spf-fs-0+svn27/policyd-spf-fs.c:256: undefined reference to `SPF_strerror' /usr/bin/ld: /build/policyd-spf-fs-0+svn27/policyd-spf-fs.c:258: undefined reference to `SPF_response_errcode' /usr/bin/ld: policyd-spf-fs.o: in function `main': /build/policyd-spf-fs-0+svn27/policyd-spf-fs.c:435: undefined reference to `SPF_error_syslog' /usr/bin/ld: /build/policyd-spf-fs-0+svn27/policyd-spf-fs.c:435: undefined reference to `SPF_error_handler' /usr/bin/ld: /build/policyd-spf-fs-0+svn27/policyd-spf-fs.c:436: undefined reference to `SPF_warning_syslog' /usr/bin/ld: /build/policyd-spf-fs-0+svn27/policyd-spf-fs.c:436: undefined reference to `SPF_warning_handler' /usr/bin/ld: /build/policyd-spf-fs-0+svn27/policyd-spf-fs.c:437: undefined reference to `SPF_info_syslog' /usr/bin/ld: /build/policyd-spf-fs-0+svn27/policyd-spf-fs.c:437: undefined reference to `SPF_info_handler' /usr/bin/ld: /build/policyd-spf-fs-0+svn27/policyd-spf-fs.c:438: undefined reference to `SPF_debug_syslog' /usr/bin/ld: /build/policyd-spf-fs-0+svn27/policyd-spf-fs.c:438: undefined reference to `SPF_debug_handler' /usr/bin/ld: /build/policyd-spf-fs-0+svn27/policyd-spf-fs.c:722: undefined reference to `SPF_response_free' /usr/bin/ld: /build/policyd-spf-fs-0+svn27/policyd-spf-fs.c:723: undefined reference to `SPF_request_free' /usr/bin/ld: /build/policyd-spf-fs-0+svn27/policyd-spf-fs.c:724: undefined reference to `SPF_server_free' /usr/bin/ld: /build/policyd-spf-fs-0+svn27/policyd-spf-fs.c:505: undefined reference to `SPF_get_lib_version' /usr/bin/ld: /build/policyd-spf-fs-0+svn27/policyd-spf-fs.c:554: undefined reference to `SPF_server_new' /usr/bin/ld: /build/policyd-spf-fs-0+svn27/policyd-spf-fs.c:557: undefined reference to `SPF_server_set_rec_dom' /usr/bin/ld: /build/policyd-spf-fs-0+svn27/policyd-spf-fs.c:564: undefined reference to `SPF_server_set_localpolicy' /usr/bin/ld: /build/policyd-spf-fs-0+svn27/policyd-spf-fs.c:570: undefined reference to `SPF_response_free' /usr/bin/ld: /build/policyd-spf-fs-0+svn27/policyd-spf-fs.c:578: undefined reference to `SPF_server_set_explanation' /usr/bin/ld: /build/policyd-spf-fs-0+svn27/policyd-spf-fs.c:584: undefined reference to `SPF_response_free' /usr/bin/ld: /build/policyd-spf-fs-0+svn27/policyd-spf-fs.c:621: undefined reference to `SPF_request_set_helo_dom' /usr/bin/ld: /build/policyd-spf-fs-0+svn27/policyd-spf-fs.c:628: undefined reference to `SPF_request_set_env_from' /usr/bin/ld: /build/policyd-spf-fs-0+svn27/policyd-spf-fs.c:636: undefined reference to `SPF_request_query_mailfrom' /usr/bin/ld: /build/policyd-spf-fs-0+svn27/policyd-spf-fs.c:649: undefined reference to `SPF_response_result' /usr/bin/ld: /build/policyd-spf-fs-0+svn27/policyd-spf-fs.c:649: undefined reference to `SPF_strresult' /usr/bin/ld: /build/policyd-spf-fs-0+svn27/policyd-spf-fs.c:689: undefined reference to `SPF_request_query_fallback' /usr/bin/ld: /build/policyd-spf-fs-0+svn27/policyd-spf-fs.c:70
Processed: Bug#943923 marked as pending in python-apptools
Processing control commands: > tag -1 pending Bug #943923 [python-apptools] python-apptools: please stop build-depending on python-pandas Added tag(s) pending. -- 943923: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943923 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#943923: marked as pending in python-apptools
Control: tag -1 pending Hello, Bug #943923 in python-apptools 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-apptools/commit/b54e1ab4016c39399efa159d2af9829db840b342 Drop python2 support; Closes: #943923, #937577, #935202 (this message was generated automatically) -- Greetings https://bugs.debian.org/943923
Bug#941527: Bug #941527: marked as pending in matplotlib
On Sun, Dec 15, 2019 at 3:48 PM Scott Kitterman wrote: > > > > > https://salsa.debian.org/python-team/modules/matplotlib/commit/b343a4fcf > > > > 363853002b509d022dde143691f099a > > > > > > > > > > > > drop Qt4 from depends; Closes: #941527 > > > > > > > > > > When are you going to upload this? matplotlib is currently the last thing > > > holding PyQt4 in testing. > > > > that's part a new upstream release i was preparing, while doing so, i > > noticed mpl doc requires a new package, which is prepared and it's > > waiting in NEW; i'll ping the FTP Masters and see if they can speed it > > up > > I don't see it in New or the archive? What's the status on this? Sorry Scott, i was probably not clear: it's not matplotlib in NEW but sphinx-copybutton, which is a new build-depends of mpl -- can you hav ea look at that package? thanks! > > Scott K -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi Twitter: https://twitter.com/sandrotosi
Bug#938562: marked as done (sshfp: Python2 removal in sid/bullseye)
Your message dated Sun, 15 Dec 2019 20:47:27 + with message-id and subject line Bug#945802: Removed package(s) from unstable has caused the Debian Bug report #938562, regarding sshfp: 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.) -- 938562: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938562 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:sshfp Version: 1.2.2-6 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:sshfp 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: 1.2.2-6+rm Dear submitter, as the package sshfp has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/945802 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#945802: marked as done (RM: sshfp -- RoQA; python2 only; no upstream release in 8+ years; low popcon; leaf package)
Your message dated Sun, 15 Dec 2019 20:47:22 + with message-id and subject line Bug#945802: Removed package(s) from unstable has caused the Debian Bug report #945802, regarding RM: sshfp -- RoQA; python2 only; no upstream release in 8+ years; low popcon; leaf package to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 945802: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945802 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sshfp Severity: serious Hello, i believe sshfp should be removed: * it's python2-only * no upstream release in 8+ years * it's a leaf package. If i dont hear back in 7 days with a good reason to keep tis pacakge, i'll file for its removal. Regards, Sandro -- System Information: Debian Release: 10.0 APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages sshfp depends on: ii libpython2.7-stdlib [python-argparse] 2.7.16-2 ii openssh-client 1:7.9p1-10 ii python 2.7.16-1 pn python-dnspython pn python-ipcalc pn python-ldns sshfp recommends no packages. sshfp suggests no packages. --- End Message --- --- Begin Message --- We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: sshfp |1.2.2-6 | source, all --- Reason --- RoQA; python2 only; no upstream release in 8+ years; low popcon; leaf package -- Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. Packages are usually not removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. The release team can force a removal from testing if it is really needed, please contact them if this should be the case. We try to close bugs which have been reported against this package automatically. But please check all old bugs, if they were closed correctly or should have been re-assigned to another package. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 945...@bugs.debian.org. The full log for this bug can be viewed at https://bugs.debian.org/945802 This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#934976: marked as done (defendguin-data: Bill Gates images used, questionable copyright status)
Your message dated Sun, 15 Dec 2019 20:48:15 + with message-id and subject line Bug#946736: Removed package(s) from unstable has caused the Debian Bug report #934976, regarding defendguin-data: Bill Gates images used, questionable copyright status 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.) -- 934976: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934976 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: defendguin-data Version: 0.0.12-7 Severity: serious Tags: upstream Justification: Policy 2.3 Dear Maintainer, defendguin-data uses real-life photographs of Bill Gates (from the 70s, I believe) in the defendguin/images/evilbill directory. I doubt those are released under a free license. The audio files in the defendguin/sounds directory are also suspicious, they sound like they have been sampled from sources whose copyright status isn't clear. For this reason, I think these files should not be distributed by Debian. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- no debconf information --- End Message --- --- Begin Message --- Version: 0.0.12-7+rm Dear submitter, as the package defendguin has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/946736 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#941527: Bug #941527: marked as pending in matplotlib
> > > https://salsa.debian.org/python-team/modules/matplotlib/commit/b343a4fcf > > > 363853002b509d022dde143691f099a > > > > > > > > > drop Qt4 from depends; Closes: #941527 > > > > > > > When are you going to upload this? matplotlib is currently the last thing > > holding PyQt4 in testing. > > that's part a new upstream release i was preparing, while doing so, i > noticed mpl doc requires a new package, which is prepared and it's > waiting in NEW; i'll ping the FTP Masters and see if they can speed it > up I don't see it in New or the archive? What's the status on this? Scott K signature.asc Description: This is a digitally signed message part.
Bug#946741: marked as done (librime: Version 1.5.3 ships broken pkg-config file)
Your message dated Sun, 15 Dec 2019 20:39:30 +
with message-id
and subject line Bug#946741: fixed in librime 1.5.3+dfsg1-3
has caused the Debian Bug report #946741,
regarding librime: Version 1.5.3 ships broken pkg-config file
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.)
--
946741: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946741
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: librime
Severity: grave
Version: 1.5.3+dfsg1-1
Currently the pkg-config file for librime is broken for includes dir and
libdir (not absolute path, the ${prefix} is missing). This needs to be fixed.
--
Thanks,
Boyuan Yang
signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: librime
Source-Version: 1.5.3+dfsg1-3
We believe that the bug you reported is fixed in the latest version of
librime, 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 946...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Boyuan Yang (supplier of updated librime package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 15 Dec 2019 13:15:08 -0500
Source: librime
Architecture: source
Version: 1.5.3+dfsg1-3
Distribution: unstable
Urgency: high
Maintainer: Debian Input Method Team
Changed-By: Boyuan Yang
Closes: 946741
Changes:
librime (1.5.3+dfsg1-3) unstable; urgency=high
.
* debian/patches/0010: Add patch for CMakeLists.txt to properly
generate pkgconfig file with absolute path. (Closes: #946741)
Checksums-Sha1:
9c5f4a24b5b0c61865bb4cd642dc7540478074b7 2533 librime_1.5.3+dfsg1-3.dsc
160eea12f328ef2aec51eee8b8a52b74904d9d44 15244
librime_1.5.3+dfsg1-3.debian.tar.xz
fe9b31692e40528d2d7da5c84eee20158caf82d0 9500
librime_1.5.3+dfsg1-3_amd64.buildinfo
Checksums-Sha256:
69b4f698e37d7734c4bd8f4c73b77f2f07ff5f1b4075c6594fbc02a7f3aa1045 2533
librime_1.5.3+dfsg1-3.dsc
291ec4c9f348486872d7569cdcef85473e03d3d3fd7c06ade9b528e1cc30b735 15244
librime_1.5.3+dfsg1-3.debian.tar.xz
09752eb864bc11b99c0fcf851d909b6fc379266bbe197d3383e9bab7429c5a84 9500
librime_1.5.3+dfsg1-3_amd64.buildinfo
Files:
a0e02b64dc6b4797932474ca20696f30 2533 libs optional librime_1.5.3+dfsg1-3.dsc
f1d45a70378a83fa9083f63eca7f7002 15244 libs optional
librime_1.5.3+dfsg1-3.debian.tar.xz
7d9b85cde3450c72cbc64e3f73d015f9 9500 libs optional
librime_1.5.3+dfsg1-3_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAl32i4kACgkQwpPntGGC
Ws4HnA/9G2UxKWiSZ1Jzyq0x/zQknYtC2KHkfywCg2zWBGcNotZFxndRfu6zmagy
uXXTs61xkxJkNRwg79OOiIRaK1uG1dJzCD45kDl7S5wUsdplH0lAuI0Fdqh/SVvh
esAtuYR7bVyFkZhD4YcnLmUx8xWcsQdALjEOTWULkzKdQfX4wXlvTbuwr7Z3oaSZ
VjhLJkpC0DML6kDvPLg+yWxd5smYSqGqD2N3yZIzU/gdm2XwRM3bQzdW+rP5DvdZ
owB9kmgM7kDxXeGsTeyiiJyfDnXm+kTO/Ey2OIi6kDA1Je8hgiS63B8G0kkZUIoE
VGMZCSnTDomQ55yOPTcnnS/0gaQyUwFQC/9M7qURHS2v41AqGk4sG8Ls0FnF4H4P
arV3YO4eq40DILfnJDW3Fl3QVoug4wjMaisEDeLpUuX6ta3qD2LNUHHz2qCpL2Wb
5xbqxTUopQfehZqncSDnaHtdKT4ub7GHQDCrZWNt8NxodBSQ4VhDY4hus3L1MS7b
Bxqz5FRgoRrghVFyv3uGlCOR4A7V4508vOnxch0jPSulDy1vK+J12TxsPPyzMbua
GAS0wsfMzgCWoI9b+iqjLHqFxp9Zi19w0E1Yqsb+qdmlNAm0YfCQC9rJaSjoIjfa
Ie2odW2WOdPXREHh9Y+DPkWxrcCt0hHPAa3bchZAuBZfD+lwLNU=
=Qkah
-END PGP SIGNATURE End Message ---
Bug#885358: marked as done (nut-monitor: Depends on unmaintained pygtk)
Your message dated Sun, 15 Dec 2019 20:40:57 + with message-id and subject line Bug#885358: fixed in nut 2.7.4-11 has caused the Debian Bug report #885358, regarding nut-monitor: Depends on unmaintained pygtk 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.) -- 885358: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885358 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: nut-monitor Version: 2.7.4-5.1 Severity: important User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs pygtk Tags: sid buster X-Debbugs-CC: bi...@debian.org pygtk is unmaintained upstream. It has not had a release since GNOME 3 was released in 2011. The way forward is to port your app to use GObject Introspection bindings (and gtk3). For more information on GObject Introspection see [1] and [2]. Please try to do this before the Buster release as we're going to try to remove pygtk this cycle. If you have any question don't hesitate to ask. [1] https://wiki.gnome.org/Projects/GObjectIntrospection [2] https://wiki.gnome.org/Projects/PyGObject On behalf of the Debian GNOME team, Jeremy Bicha --- End Message --- --- Begin Message --- Source: nut Source-Version: 2.7.4-11 We believe that the bug you reported is fixed in the latest version of nut, 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 885...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Laurent Bigonville (supplier of updated nut package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 15 Dec 2019 21:22:13 +0100 Source: nut Architecture: source Version: 2.7.4-11 Distribution: unstable Urgency: medium Maintainer: Arnaud Quette Changed-By: Laurent Bigonville Closes: 885358 937169 Changes: nut (2.7.4-11) unstable; urgency=medium . * Remove python(2) binding and disable nut-monitor package for now as it depends on unmaintained pygtk (Closes: #885358, #937169) * debian/control: Add support for the Build-Profile * debian/patches/0013-fix-doc-build.patch: Fix the documentation build with asciidoc >= 0.9 * Disable python3-nut package for now as it's broken with python3 Checksums-Sha1: b72cdae1c206fba21f830a7fd4b32d57eae7807e 2919 nut_2.7.4-11.dsc 387ea169d607707cd59626485e8fa56ef0ca2757 76432 nut_2.7.4-11.debian.tar.xz 980bbde8e9fbdb8419ec26c4bf3c59d13373a665 6105 nut_2.7.4-11_source.buildinfo Checksums-Sha256: 91a4d42caf1b38cc857c37e5532c3b31e7e40ce9927626b9a686b1c179ac66b1 2919 nut_2.7.4-11.dsc 923d36e8b05c586df09b160626f7322c640915dda0f1bc82db02e17b63964bcd 76432 nut_2.7.4-11.debian.tar.xz bcdaae49d41e2415ed0095fbac73524617fccd03c34e832d4bcdf39a2aead49b 6105 nut_2.7.4-11_source.buildinfo Files: 9add389d7e63c026e54b21aa05461c5f 2919 admin optional nut_2.7.4-11.dsc 8ea130830dd800666165c5d361879908 76432 admin optional nut_2.7.4-11.debian.tar.xz dfbabb797d0e8afa0ddf50ef431b2906 6105 admin optional nut_2.7.4-11_source.buildinfo -BEGIN PGP SIGNATURE- iQFFBAEBCAAvFiEEmRrdqQAhuF2x31DwH8WJHrqwQ9UFAl32lhURHGJpZ29uQGRl Ymlhbi5vcmcACgkQH8WJHrqwQ9VGCwf+KMNjXCVUcWyrZWzyB+YT8X0GWBfHiKa9 +dMleVksX/bmJ+fzZWuSmh0NqlRgcT92Kj+DZ29r7iDyLxQho6o6QFWBnXer6vq5 30mQuIBfOEh9n27hfeEBISYnmKtHfXZ3JZxpeyocRZvVlYS162twfzHNdJX3my// 6KP1hdyJ2pk7yUpGY4iI+Y0+0ZjKMAInhHtowzV1/FgIohtNDUbtQHNvR/BArI0J w3xaZFshzpH11HaGpFYpCOn0uL2JoF0oRU8hl5X4oz2V0tWYMyVyD6JCHX1hp3Ag ot4eVBHNqO1PD1c8CBbdsvQLC5hUQHE5d5kf7Bi8byXvTnxyHduKtw== =yV+p -END PGP SIGNATURE End Message ---
Bug#937169: marked as done (nut: Python2 removal in sid/bullseye)
Your message dated Sun, 15 Dec 2019 20:40:57 + with message-id and subject line Bug#937169: fixed in nut 2.7.4-11 has caused the Debian Bug report #937169, regarding nut: 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.) -- 937169: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937169 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:nut Version: 2.7.4-10 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:nut 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: nut Source-Version: 2.7.4-11 We believe that the bug you reported is fixed in the latest version of nut, 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. Laurent Bigonville (supplier of updated nut package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 15 Dec 2019 21:22:13 +0100 Source: nut Architecture: source Version: 2.7.4-11 Distribution: unstable Urgency: medium Maintainer: Arnaud Quette Changed-By: Laurent Bigonville Closes: 885358 937169 Changes: nut (2.7.4-11) unstable; urgency=medium . * Remove python(2) binding and disable nut-monitor package for now as it depends on unmaintained pygtk (Closes: #885358, #937169) * debian/control: Add support for the Build-Profile * debian/patches/0013-fix-doc-build.patch: Fix the documentation build with asciidoc >= 0.9 * Disable python3-nut package for now as it's broken with python3 Checksums-Sha1: b72cdae1c206fba21f830a7fd4b32d57eae7807e 2919 nut_2.7.4-11.dsc 387ea169d607707cd59626485e8fa56ef0ca2757 76432 nut_2.7.4-11.debian.tar.xz 980bbde8e9fbdb8419ec26c4bf3c59d13373a665 6105 nut_2.7.4-11_source.buildinfo Checksums-Sha256: 91a4d42caf1b38cc857c37e5532c3b31e7e40ce9927626b9a686b1c179ac66b1 2919 nut_2.7.4-11.dsc 923d36e8b05c586df09b160626f7322c640915dda0f1bc
Bug#946732: [Python-modules-team] Bug#946732: python-django-braces: autopkgtest failure: No module named 'django_braces'
Hi Emmanuel, On 15-12-2019 17:01, Emmanuel Arias wrote: > I've just push to salsa the fix. I add the > `debian/tests/pkg-python/import-name` file > but locally the error is still happening. With which version of autodep8? Are you running on buster? I guess we should backport all of autopep8 and autopkgtest. Paul signature.asc Description: OpenPGP digital signature
Bug#945981: marked as done (pathspider build-depends on cruft package.)
Your message dated Sun, 15 Dec 2019 19:08:19 + with message-id and subject line Bug#945981: fixed in pathspider 2.0.1-2.1 has caused the Debian Bug report #945981, regarding pathspider build-depends on cruft package. to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 945981: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945981 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: pathspider Version: 2.0.1-2 Severity: serious Pathspider build-depends on pylint3, which is no longer built by the pylint source package. Please consider changing your build-dependency to pylint (>= 2.2.2-2). I have not done a test build in this case, because your package already has a FTBFS bug. --- End Message --- --- Begin Message --- Source: pathspider Source-Version: 2.0.1-2.1 We believe that the bug you reported is fixed in the latest version of pathspider, 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 945...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gianfranco Costamagna (supplier of updated pathspider package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 10 Dec 2019 18:49:55 +0100 Source: pathspider Binary: pathspider Architecture: source Version: 2.0.1-2.1 Distribution: unstable Urgency: medium Maintainer: Internet Measurement Packaging Team Changed-By: Gianfranco Costamagna Description: pathspider - Internet path transparency measurement tool Closes: 945981 Changes: pathspider (2.0.1-2.1) unstable; urgency=medium . * Non-maintainer upload. * Switch pylint3 dependency to pylint, the former is a cruft package (Closes: #945981) * Disable test_plugin_evilbit.py and test_plugin_udpzero.py by adding them to debian/clean target. NOTE: I'm not closing the RC bug, because the fix needs to be addressed anyway, this upload is meant to remove pylint2 cruft package. Checksums-Sha1: 1970c2575b3b472e58d4072b18594b22c29da19f 2180 pathspider_2.0.1-2.1.dsc 1bf09ea802f792e20a1280a8515e1194c53b115c 3824 pathspider_2.0.1-2.1.debian.tar.xz efd49e88f66b6acab007b18a9f512883a519c707 10811 pathspider_2.0.1-2.1_source.buildinfo Checksums-Sha256: 261ab33274ed2fb4276cf37d826985c2229a38693005df282a8d1bd3ca18dacc 2180 pathspider_2.0.1-2.1.dsc 83bf2a2d491050f757945e02371b71fcc4aa728cfa3baa0a488d92d65e04a82f 3824 pathspider_2.0.1-2.1.debian.tar.xz 44212b2776b2739cc45465e91fc7dcc4db3dd7671090265d881ede0c752f27f5 10811 pathspider_2.0.1-2.1_source.buildinfo Files: 4c0468022690337442cde19f18edee53 2180 net optional pathspider_2.0.1-2.1.dsc 8ea0fa30e72cf387614edc06a97506ca 3824 net optional pathspider_2.0.1-2.1.debian.tar.xz d957445eaf479827718e74a1a4206862 10811 net optional pathspider_2.0.1-2.1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEkpeKbhleSSGCX3/w808JdE6fXdkFAl3v3yIACgkQ808JdE6f XdmZow//TK7xkiAmjU7OYwXclbOao9DcULQWd9BWf022qX97QkbGMYOhsFkHqiSt lGrabSVr703MrklmYInbsd4wHg7GnBe5NUxOcGBrB4hlwCJLdG11x60RIXu+konC 3qZ/DqzJtheix25/nwgsKwraj9SjK4NdP+vQSQJwhvXGcqPwIBGd2RD0b8MUEwT3 JRY6ZTIp60ze81d8o6TUptQtXzW+nJAoiQgEM+tUB7RXjti18Ga3G0wAFS0dqkQb nSdjSc+81//1Qvk5CguIouq6gpfoW8VMCYtmu3xpKU7viYhsePXloYLNwZhdoqXl lPAvtReXisr4TvPZK+P6a0LtTMkLS5I58cylsELCqRV/8vORDsZYHvL+8GGDu7iC QKkKWBDZ1MNqn5wxyQnbazEZFwhfPH2aaywDpLBMT+W9Z1m/rgJJD1JRu8sbRoaE d5ypnhMHrBOZkBUldLa+ahPr0tHiskKAkuhZtW0jKx4olEttXoNMK48GoFGngP/a hZgUy08EWlCJB/PFluUpOXjnU2MpY94VriGhY02mwXzmwh1BM7zzu+7sW5DK7uG9 ytHYP20Eg7U5onKV7IyhmTAx+dsHurTXtILqBB2UGhIAYsqC1uiPlDGoeeShtlBZ j0Nt3gL4OXqq6Xc0kNgLiGJqkd1GBeZoPWuvz14x+OinLWE9XhU= =4LDg -END PGP SIGNATURE End Message ---
Bug#940463: fixed in falkon 3.1.0+dfsg1-4
Control: reopen -1 Control: tags -1 unreproducible moreinfo Control: severity -1 normal If 3.1.0+dfsg1-4 doesn't have any changes from 3.1.0+dfsg1-3, why was it uploaded? That uses additional mirror space and rebuilds all of the packages. It also marks the bug as fixed in 3.1.0+dfsg1-4. Instead, if a bug isn't being fixed by a new upload, send the reason you're closing it to 940463-done@b.d.o with a Version: header reflecting if a version does have a fix. > As my last e-mail tells, I "Checked that falkon-3.1.0+dfsg1-3 does not > crash", which can be considered as being unable to reproduce the bug. Bugs shouldn't be closed solely for being unreproducible. Instead, add the tags and contact the submitter. I see you might've been desperate to get Falkon back into testing since the upload was the same day it was removed. Bugs serious, grave, and critical cause removal, so I've downgraded the bug to normal. > I got no reply from Xeno Idaltu , so I believe > that either he is not using falkon again, or he installed falkon's new > package and found the bug fixed. Did you reply to him separately from the bug report? The log doesn't show anyone reaching out to him. Additionally, I'm curious about this changelog entry > falkon (3.1.0+dfsg1-5) unstable; urgency=medium > * removed the dependency on libgnome-keyring-dev, since this package > is no longer part of Debian. Together with the upstream version > change, this ... Closes: #943769 since #943769 doesn't appear to be related to GNOME Keyring. I am also seeking to know why 3.1.0+dfsg1-3 has a +dfsg1-3 since the prior uploads were 3.0 and didn't have the +dfsg1. I haven't been able to find the reason for the change documented. I haven't been able to reproduce the bug. However, I hope my suggestions are helpful for you and that I'll be able to help Falcon in this way. Sincerely, John Scott signature.asc Description: This is a digitally signed message part.
Processed: Bug#940463: fixed in falkon 3.1.0+dfsg1-4
Processing control commands:
> reopen -1
Bug #940463 {Done: Georges Khaznadar } [falkon] falkon:
Falkon crashes and even freezes entire desktop.
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions falkon/3.1.0+dfsg1-4.
> tags -1 unreproducible moreinfo
Bug #940463 [falkon] falkon: Falkon crashes and even freezes entire desktop.
Added tag(s) moreinfo and unreproducible.
> severity -1 normal
Bug #940463 [falkon] falkon: Falkon crashes and even freezes entire desktop.
Severity set to 'normal' from 'critical'
--
940463: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940463
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#946529: marked as done (lua-nvim: FTBFS: test timeout)
Your message dated Sun, 15 Dec 2019 17:22:32 + with message-id and subject line Bug#946529: fixed in lua-nvim 0.2.1-1-1 has caused the Debian Bug report #946529, regarding lua-nvim: FTBFS: test timeout 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.) -- 946529: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946529 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: lua-nvim Version: 0.2.0-1-2 Severity: serious Tags: ftbfs sid bullseye Justification: fails to build from source (but built successfully in the past) lua-nvim currently fails to build in unstable: |dh_auto_test -O--buildsystem=lua | make --no-print-directory -f /usr/share/dh-lua/make/dh-lua.Makefile.multiple test | | Making target test for debian/lua5.1.dh-lua.conf | # tests | Copying nvim/socket_stream.lua nvim/msgpack_rpc_stream.lua nvim/session.lua nvim/tcp_stream.lua nvim/child_process_stream.lua nvim/stdio_stream.lua in /<>/5.1-nvim for test | ** lua dynamic custom (5.1) ** | [==] Running tests from scanned files. | [--] Global test environment setup. | [--] Running tests from test/session_spec.lua | [ RUN ] test/session_spec.lua @ 35: Session using ChidProcessStream can make requests to nvim | [ OK ] test/session_spec.lua @ 35: Session using ChidProcessStream can make requests to nvim (6.66 ms) | [ RUN ] test/session_spec.lua @ 40: Session using ChidProcessStream can get api metadata | [ OK ] test/session_spec.lua @ 40: Session using ChidProcessStream can get api metadata (7.37 ms) | [ RUN ] test/session_spec.lua @ 50: Session using ChidProcessStream can receive messages from nvim | [ OK ] test/session_spec.lua @ 50: Session using ChidProcessStream can receive messages from nvim (6.73 ms) | [ RUN ] test/session_spec.lua @ 58: Session using ChidProcessStream can receive requests from nvim | E: Build killed with signal TERM after 150 minutes of inactivity | It also fails on the build farm run by the reproducible builds effort: https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/lua-nvim_0.2.0-1-2.rbuild.log.gz Cheers -- Sebastian Ramacher --- End Message --- --- Begin Message --- Source: lua-nvim Source-Version: 0.2.1-1-1 We believe that the bug you reported is fixed in the latest version of lua-nvim, 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 946...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. James McCoy (supplier of updated lua-nvim package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 15 Dec 2019 11:33:25 -0500 Source: lua-nvim Architecture: source Version: 0.2.1-1-1 Distribution: unstable Urgency: medium Maintainer: Jason Pleau Changed-By: James McCoy Closes: 946529 Changes: lua-nvim (0.2.1-1-1) unstable; urgency=medium . * New upstream release + Fix 'can receive requests from nvim' test (Closes: #946529) * Provide the module for Lua 5.3 Checksums-Sha1: d750a31261a67ac88a532bab68d519e0a84cd9bc 2244 lua-nvim_0.2.1-1-1.dsc 36b4726ebeca59b20771b7c5fbf5734f37937870 13563 lua-nvim_0.2.1-1.orig.tar.gz 719176b19d21fe2086d3342e380d72a55780c6d5 2688 lua-nvim_0.2.1-1-1.debian.tar.xz 89ba492d5701d879dd38290a678fa3ad652ec816 7551 lua-nvim_0.2.1-1-1_amd64.buildinfo Checksums-Sha256: 6da972b3b445e144002edc6b62eb163bc759fdb54b4408489f1e462e0e17e94f 2244 lua-nvim_0.2.1-1-1.dsc 86f8e9eba074e227025b0a09d0fcd1605abb5603971e9c45cb1efc6e8039ebfb 13563 lua-nvim_0.2.1-1.orig.tar.gz 09f89d07e54cb5a096d5aaeefd8ffeccbe9ce0ac70a68b0f9ba8383a535f1521 2688 lua-nvim_0.2.1-1-1.debian.tar.xz c76e40e53185092a49e62e11bf9219ea0ed01e41b94dd73d1d9784427e184c7f 7551 lua-nvim_0.2.1-1-1_amd64.buildinfo Files: 7dd22946ff671047a40fe82c16aff6a2 2244 interpreters optional lua-nvim_0.2.1-1-1.dsc 4a361bdfdaf6af9a7d7d19f66ee4cf89 13563 interpreters optional lua-nvim_0.2.1-1.orig.tar.gz f35fe0e6374d6e8f336a19506d53bdbc 2688 interpreters optional lua-nvim_0.2.1-1-1.debian.tar.xz 669b87efe62ca99a80c635d296c1dafb 7551 interpre
Bug#937145: nitime: Python2 removal in sid/bullseye
A Python3 version of this package, also updated to the latest release, is available at https://github.com/yarikoptic/nitime/pull/1 for sponsorship Thanks
Bug#946771: librdf-doap-perl: autopkgtest failure
Source: librdf-doap-perl Version: 0.104-1 Severity: serious Justification: no testing migration with autopkgtest failure -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 librdf-doap-perl 0.104-1 has enabled autopkgtest-pkg-perl. Unfortunately they fail: https://ci.debian.net/packages/libr/librdf-doap-perl/unstable/amd64/ https://ci.debian.net/data/autopkgtest/unstable/amd64/libr/librdf-doap-perl/3669776/log.gz The failure is in the third test, syntax.t: # Subtest: all modules in librdf-doap-perl pass the syntax check 1..22 ok 1 - /usr/bin/perl -wc /usr/share/perl5/RDF/DOAP/Change/Addition.pm exited successfully ok 2 - /usr/bin/perl -wc /usr/share/perl5/RDF/DOAP/Change/BackCompat.pm exited successfully # Undefined subroutine &RDF::Trine::NIL_GRAPH called at /usr/share/perl5/RDF/Trine/Node/Resource.pm line 78. # Compilation failed in require at /usr/share/perl5/Module/Runtime.pm line 314. # Compilation failed in require at /usr/share/perl5/RDF/DOAP/Change/Bugfix.pm line 9. # BEGIN failed--compilation aborted at /usr/share/perl5/RDF/DOAP/Change/Bugfix.pm line 9. not ok 3 - /usr/bin/perl -wc /usr/share/perl5/RDF/DOAP/Change/Bugfix.pm exited successfully ok 4 - /usr/bin/perl -wc /usr/share/perl5/RDF/DOAP/Change/Documentation.pm exited successfully ok 5 - /usr/bin/perl -wc /usr/share/perl5/RDF/DOAP/Change/Packaging.pm exited successfully ok 6 - /usr/bin/perl -wc /usr/share/perl5/RDF/DOAP/Change/Regression.pm exited successfully ok 7 - /usr/bin/perl -wc /usr/share/perl5/RDF/DOAP/Change/Removal.pm exited successfully ok 8 - /usr/bin/perl -wc /usr/share/perl5/RDF/DOAP/Change/SecurityFix.pm exited successfully ok 9 - /usr/bin/perl -wc /usr/share/perl5/RDF/DOAP/Change/SecurityRegression.pm exited successfully ok 10 - /usr/bin/perl -wc /usr/share/perl5/RDF/DOAP/Change/Tests.pm exited successfully ok 11 - /usr/bin/perl -wc /usr/share/perl5/RDF/DOAP/Change/Update.pm exited successfully # Undefined subroutine &RDF::Trine::NIL_GRAPH called at /usr/share/perl5/RDF/Trine/Node/Resource.pm line 78. # Compilation failed in require at /usr/share/perl5/Module/Runtime.pm line 314. # Compilation failed in require at /usr/share/perl5/RDF/DOAP/Change.pm line 9. # BEGIN failed--compilation aborted at /usr/share/perl5/RDF/DOAP/Change.pm line 9. not ok 12 - /usr/bin/perl -wc /usr/share/perl5/RDF/DOAP/Change.pm exited successfully # Undefined subroutine &RDF::Trine::NIL_GRAPH called at /usr/share/perl5/RDF/Trine/Node/Resource.pm line 78. # Compilation failed in require at /usr/share/perl5/Module/Runtime.pm line 314. # Compilation failed in require at /usr/share/perl5/RDF/DOAP/Change.pm line 9. # BEGIN failed--compilation aborted at /usr/share/perl5/RDF/DOAP/Change.pm line 9. # Compilation failed in require at /usr/share/perl5/RDF/DOAP/ChangeSet.pm line 10. # BEGIN failed--compilation aborted at /usr/share/perl5/RDF/DOAP/ChangeSet.pm line 10. not ok 13 - /usr/bin/perl -wc /usr/share/perl5/RDF/DOAP/ChangeSet.pm exited successfully ok 14 - /usr/bin/perl -wc /usr/share/perl5/RDF/DOAP/Issue.pm exited successfully ok 15 - /usr/bin/perl -wc /usr/share/perl5/RDF/DOAP/Person.pm exited successfully # Undefined subroutine &RDF::Trine::NIL_GRAPH called at /usr/share/perl5/RDF/Trine/Node/Resource.pm line 78. # Compilation failed in require at /usr/share/perl5/Module/Runtime.pm line 314. # Compilation failed in require at /usr/share/perl5/RDF/DOAP/Project.pm line 9. # BEGIN failed--compilation aborted at /usr/share/perl5/RDF/DOAP/Project.pm line 9. not ok 16 - /usr/bin/perl -wc /usr/share/perl5/RDF/DOAP/Project.pm exited successfully ok 17 - /usr/bin/perl -wc /usr/share/perl5/RDF/DOAP/Repository.pm exited successfully ok 18 - /usr/bin/perl -wc /usr/share/perl5/RDF/DOAP/Resource.pm exited successfully ok 19 - /usr/bin/perl -wc /usr/share/perl5/RDF/DOAP/Types.pm exited successfully ok 20 - /usr/bin/perl -wc /usr/share/perl5/RDF/DOAP/Utils.pm exited successfully # Undefined subroutine &RDF::Trine::NIL_GRAPH called at /usr/share/perl5/RDF/Trine/Node/Resource.pm line 78. # Compilation failed in require at /usr/share/perl5/Module/Runtime.pm line 314. # Compilation failed in require at /usr/share/perl5/RDF/DOAP/Change.pm line 9. # BEGIN failed--compilation aborted at /usr/share/perl5/RDF/DOAP/Change.pm line 9. # Compilation failed in require at /usr/share/perl5/RDF/DOAP/ChangeSet.pm line 10. # BEGIN failed--compilation aborted at /usr/share/perl5/RDF/DOAP/ChangeSet.pm line 10. # Compilation failed in require at /usr/share/perl5/RDF/DOAP/Version.pm line 9. # BEGIN failed--compilation aborted at /usr/share/perl5/RDF/DOAP/Version.pm line 9. not ok 21 - /usr/bin/perl -wc /usr/share/perl5/RDF/DOAP/Version.pm exited successfully ok 22 - /usr/bin/perl -wc /usr/share/perl5/RDF/DOAP.pm exited successfully not ok 4 - all modu
Bug#946732: [Python-modules-team] Bug#946732: python-django-braces: autopkgtest failure: No module named 'django_braces'
Hello Paul, I've just push to salsa the fix. I add the `debian/tests/pkg-python/import-name` file but locally the error is still happening. Anyone could review it please? Thanks! Cheers, Arias Emmanuel @eamanu http://eamanu.com El sáb., 14 de dic. de 2019 a la(s) 18:03, Paul Gevers (elb...@debian.org) escribió: > > Source: python-django-braces > Version: 1.13.0-1 > Severity: serious > X-Debbugs-CC: debian...@lists.debian.org > User: debian...@lists.debian.org > Usertags: regression > > Dear maintainers, > > With a recent upload of python-django-braces you added an autopkgtest to > your package, great. However, it fails. I copied some of the output at > the bottom of this report. The layout of your package doesn't seem to be > working with autodep8 out of the box. However, autodep8 recently grew > support [1] for modules named differently than the package name suggest. > Please follow the documentation. > > 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://salsa.debian.org/ci-team/autodep8/commit/f05b0babe551ac512a3543758d21ec329ec0e58d > [2] https://qa.debian.org/excuses.php?package=python-django-braces > > https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-django-braces/3483366/log.gz > autopkgtest [15:23:51]: test autodep8-python3: set -e ; for py in > $(py3versions -r 2>/dev/null) ; do cd "$AUTOPKGTEST_TMP" ; echo "Testing > with $py:" ; $py -c "import django_braces; print(django_braces)" ; done > autopkgtest [15:23:51]: test autodep8-python3: [--- > Testing with python3.7: > Traceback (most recent call last): > File "", line 1, in > ModuleNotFoundError: No module named 'django_braces' > autopkgtest [15:23:52]: test autodep8-python3: ---] > > > ___ > Python-modules-team mailing list > python-modules-t...@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team
Bug#945920: Chromium randomly crashes in the latest version.
Package: chromium Version: 79.0.3945.79-1 Followup-For: Bug #945920 Dear Maintainer, I'm experiencing the same random crashes after upgrading from 78.0.3904.108-1 to 79.0.3945.79-1 Backtrace attached. Regards -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.3.0-3-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages chromium depends on: ii chromium-common79.0.3945.79-1 ii libasound2 1.1.9-1 ii libatk-bridge2.0-0 2.34.1-2 ii libatk1.0-02.34.1-1 ii libatomic1 9.2.1-21 ii libatspi2.0-0 2.34.0-3 ii libavcodec-extra58 [libavcodec58] 7:4.2.1-2 ii libavformat58 7:4.2.1-2 ii libavutil567:4.2.1-2 ii libc6 2.29-6 ii libcairo-gobject2 1.16.0-4 ii libcairo2 1.16.0-4 ii libcups2 2.3.0-7 ii libdbus-1-31.12.16-2 ii libdrm22.4.100-4 ii libevent-2.1-7 2.1.11-stable-1 ii libexpat1 2.2.9-1 ii libflac8 1.3.3-1 ii libfontconfig1 2.13.1-2+b1 ii libfreetype6 2.10.1-2 ii libgcc11:9.2.1-21 ii libgdk-pixbuf2.0-0 2.40.0+dfsg-1 ii libglib2.0-0 2.62.3-2 ii libgtk-3-0 3.24.13-1 ii libharfbuzz0b 2.6.4-1 ii libicu63 63.2-2 ii libjpeg62-turbo1:1.5.2-2+b1 ii libjsoncpp11.7.4-3+b1 ii liblcms2-2 2.9-4 ii libminizip11.1-8+b1 ii libnspr4 2:4.23-1 ii libnss32:3.47.1-1 ii libopenjp2-7 2.3.1-1 ii libopus0 1.3-1+b1 ii libpango-1.0-0 1.42.4-7 ii libpangocairo-1.0-01.42.4-7 ii libpci31:3.6.2-6 ii libpng16-161.6.37-1 ii libpulse0 13.0-3 ii libre2-5 20191101+dfsg-1 ii libsnappy1v5 1.1.7-2 ii libstdc++6 9.2.1-21 ii libva2 2.5.0-2 ii libvpx61.8.1-2 ii libwebp6 0.6.1-2+b1 ii libwebpdemux2 0.6.1-2+b1 ii libwebpmux30.6.1-2+b1 ii libx11-6 2:1.6.8-1 ii libx11-xcb12:1.6.8-1 ii libxcb11.13.1-2 ii libxcomposite1 1:0.4.4-2 ii libxcursor11:1.2.0-2 ii libxdamage11:1.1.5-1 ii libxext6 2:1.3.3-1+b2 ii libxfixes3 1:5.0.3-1 ii libxi6 2:1.7.9-1 ii libxml22.9.4+dfsg1-8 ii libxrandr2 2:1.5.1-1 ii libxrender11:0.9.10-1 ii libxslt1.1 1.1.32-2.2 ii libxss11:1.2.3-1 ii libxtst6 2:1.2.3-1 ii zlib1g 1:1.2.11.dfsg-1+b1 Versions of packages chromium recommends: ii chromium-sandbox 79.0.3945.79-1 Versions of packages chromium suggests: pn chromium-driver pn chromium-l10n pn chromium-shell Versions of packages chromium-common depends on: ii x11-utils 7.7+4 ii xdg-utils 1.1.3-1 Versions of packages chromium-common recommends: ii chromium-sandbox 79.0.3945.79-1 ii dunst [notification-daemon] 1.4.1-1 ii fonts-liberation 1:1.07.4-10 ii libgl1-mesa-dri 19.2.6-1 ii libu2f-udev 1.1.10-1 ii notification-daemon 3.20.0-4 ii system-config-printer1.5.12-1 ii upower 0.99.11-1 Versions of packages chromium-sandbox depends on: ii libatomic1 9.2.1-21 ii libc6 2.29-6 ii libgcc1 1:9.2.1-21 ii libstdc++6 9.2.1-21 -- no debconf information #0 0x5a77cee7 in memory_instrumentation::MemoryInstrumentation::RequestGlobalDump(std::vector, std::allocator >, std::allocator, std::allocator > > > const&, base::OnceCallback >)>) () #1 0x58f8ddb0 in ProcessMemoryMetric
Bug#946769: Please remove dependency on fontypython (RC buggy, marked for removal)
Package: open-font-design-toolkit Severity: serious open-font-design-toolkit depends on fontypython which is marked as removal due to RC buggy and not maintained anymore by upstream and upstream has no plan to port it to Python3 as of now. Please remove dependency on fontypython, so it can be removed from Debian. Thanks! -- Kartik Mistry | IRC: kart_ https://kartikm.wordpress.com signature.asc Description: PGP signature
Bug#940463: fixed in falkon 3.1.0+dfsg1-4
Dear John, thank you for your interest in Bug#940463. I got no reply from Xeno Idaltu , so I believe that either he is not using falkon again, or he installed falkon's new package and found the bug fixed. His only e-mail states that he made a fresh install, and gives version numbers for the distribution and dependencies. Sorry, I had no time to reproduce the same installation. As my last e-mail tells, I "Checked that falkon-3.1.0+dfsg1-3 does not crash", which can be considered as being unable to reproduce the bug. The issue seems to be fixed between two upstream releases (falkon 3.0 and falkon 3.1). John, if you want to help about packaging falkon for Debian, you are most welcome. By the way, were you able to reproduce the crash? Best regards, Georges. John Scott a écrit : > On Wed, 16 Oct 2019 10:00:15 + Georges Khaznadar > wrote: > > Source: falkon > > Source-Version: 3.1.0+dfsg1-4 > > > > We believe that the bug you reported is fixed in the latest version of > > falkon, which is due to be installed in the Debian FTP archive. > > > > A summary of the changes between this version and the previous one is > > attached. > > > > Changes: > > falkon (3.1.0+dfsg1-4) unstable; urgency=medium > > . > >* Checked that falkon-3.1.0+dfsg1-3 does not crash. > > Closes: #940463 > > Did a change to Falkon fix the issue, or is 3.1.0+dfsg-1-4 the same as > 3.1.0+dfsg-1-3? Was the submitter's issue resolved or were you unable to > reproduce the crash? -- Georges KHAZNADAR et Jocelyne FOURNIER 22 rue des mouettes, 59240 Dunkerque France. Téléphone +33 (0)3 28 29 17 70 signature.asc Description: PGP signature
Bug#938327: Upstream references
FWIW Upstream is working on Python 3 support here: https://github.com/rabbitvcs/rabbitvcs/issues/279 signature.asc Description: PGP signature
Bug#936454: No longer depends on python-fastimport
severity 936454 normal thanks Resetting this to normal. As of 0.19.14-1 (uploaded at the same time as the python-fastimport removal), Dulwich has stopped build-depending on python-fastimport.
Processed: No longer depends on python-fastimport
Processing commands for cont...@bugs.debian.org: > severity 936454 normal Bug #936454 [src:dulwich] dulwich: Python2 removal in sid/bullseye Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 936454: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936454 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: UICommon.so: cannot open shared object file
Processing control commands: > fixed -1 6.1.0-dfsg-2 Bug #946749 [virtualbox] UICommon.so: cannot open shared object file There is no source info for the package 'virtualbox' at version '6.1.0-dfsg-2' with architecture '' Unable to make a source version for version '6.1.0-dfsg-2' Marked as fixed in versions 6.1.0-dfsg-2. > close -1 Bug #946749 [virtualbox] UICommon.so: cannot open shared object file Marked Bug as done -- 946749: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946749 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#946749: UICommon.so: cannot open shared object file
control: fixed -1 6.1.0-dfsg-2 control: close -1 On Sun, 15 Dec 2019 09:55:08 +0100 Mattia Monga wrote: > Package: virtualbox > Version: 6.1.0-dfsg-1 > Severity: grave > Justification: renders package unusable > > The file UICommon.so is missing > > Complete error message: > > /usr/lib/virtualbox/VirtualBox: error while loading shared libraries: > UICommon.so: cannot open shared object file: No such file or directory > > -- System Information: > Debian Release: bullseye/sid > APT prefers unstable > APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, > 'experimental') > Architecture: amd64 (x86_64) > Foreign Architectures: i386, armhf > > Kernel: Linux 5.3.15 (SMP w/8 CPU cores; PREEMPT) > Kernel taint flags: TAINT_OOT_MODULE > Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), > LANGUAGE=it_IT.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /usr/bin/dash > Init: systemd (via /run/systemd/system) > > Versions of packages virtualbox depends on: > ii adduser 3.118 > ii iproute2 5.4.0-1 > ii libc6 2.29-6 > ii libcurl3-gnutls 7.67.0-2 > ii libdevmapper1.02.12:1.02.155-3 > ii libgcc1 1:9.2.1-21 > ii libgl11.1.0-1+b1 > ii libgsoap-2.8.91 2.8.91-2 > ii libopus0 1.3-1+b1 > ii libpng16-16 1.6.37-1 > ii libpython3.7 3.7.5-2 > ii libsdl1.2debian 1.2.15+dfsg2-5 > ii libssl1.1 1.1.1d-2 > ii libstdc++69.2.1-21 > ii libvncserver1 0.9.12+dfsg-4 > ii libvpx6 1.8.1-2 > ii libx11-6 2:1.6.8-1 > ii libxcursor1 1:1.2.0-2 > ii libxml2 2.9.4+dfsg1-8 > ii libxt61:1.1.5-1+b3 > ii procps2:3.3.15-2+b1 > ii python3 3.7.5-3 > ii python3.7 3.7.5-2 > ii virtualbox-dkms [virtualbox-modules] 6.1.0-dfsg-1 > ii zlib1g1:1.2.11.dfsg-1+b1 > > Versions of packages virtualbox recommends: > ii libqt5core5a5.12.5+dfsg-2 > ii libqt5gui5 5.12.5+dfsg-2 > ii libqt5opengl5 5.12.5+dfsg-2 > ii libqt5widgets5 5.12.5+dfsg-2 > ii libxcb1 1.13.1-2 > ii libxext62:1.3.3-1+b2 > ii libxmu6 2:1.1.2-2+b3 > ii virtualbox-qt 6.1.0-dfsg-1
Bug#946760: python-pattern: needs a source-only upload.
Package: python-pattern Version: 2.6+git20180818-1 Severity: serious The release team have decreed that non-buildd binaries can no longer migrate to testing, plase make a source-only upload so your package can migrate.
Bug#943600: marked as done (lazarus autopkgtest intermittedly fails due to EAccessViolation: Access violation)
Your message dated Sun, 15 Dec 2019 12:05:03 + with message-id and subject line Bug#943600: fixed in lazarus 2.0.6+dfsg-3 has caused the Debian Bug report #943600, regarding lazarus autopkgtest intermittedly fails due to EAccessViolation: Access violation 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.) -- 943600: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943600 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: lazarus Version: 2.0.2+dfsg-7 Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: flaky Dear all, Version 2.0.2+dfsg-7 of lazarus has failed already at least three times on the ci.d.n infrastructure. The error is always a logged EAccessViolation, except the stack isn't always the same length. So far the offset between the two lowest items is the same. Paul https://ci.debian.net/data/autopkgtest/testing/amd64/l/lazarus/3271190/log.gz An unhandled exception occurred at $: EAccessViolation: Access violation $ $55EFE24EAB67 $55EFE24EBDC1 https://ci.debian.net/data/autopkgtest/unstable/amd64/l/lazarus/3250811/log.gz An unhandled exception occurred at $: EAccessViolation: Access violation $ $557D05069B67 $557D0506ADC1 https://ci.debian.net/data/autopkgtest/unstable/amd64/l/lazarus/3250711/log.gz EAccessViolation: Access violation $563EC38CCBF3 $563EC3D9ABC5 $563EC3D9EB67 $563EC3D9FDC1 - -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'testing-debug') Architecture: amd64 (x86_64) Kernel: Linux 5.2.0-3-amd64 (SMP w/2 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: lazarus Source-Version: 2.0.6+dfsg-3 We believe that the bug you reported is fixed in the latest version of lazarus, 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 943...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Abou Al Montacir (supplier of updated lazarus package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 15 Dec 2019 12:16:47 +0100 Source: lazarus Architecture: source Version: 2.0.6+dfsg-3 Distribution: unstable Urgency: medium Maintainer: Pascal Packaging Team Changed-By: Abou Al Montacir Closes: 943600 Changes: lazarus (2.0.6+dfsg-3) unstable; urgency=medium . * Limit number of processor within LPK build test to avoid crash. (Closes: Bug#943600) Checksums-Sha1: da46b4da1e4f6eb912b1caf9e3306a8e4d1536cc 2990 lazarus_2.0.6+dfsg-3.dsc 100c01d9560460e90cf3b147aceb109231584ee4 71208 lazarus_2.0.6+dfsg-3.debian.tar.xz 592baeef874594fb870ea37c19044d6c27a129e8 19690 lazarus_2.0.6+dfsg-3_amd64.buildinfo Checksums-Sha256: bb5ece05de3a66ed00fab18efe82098e25e88e50d3d9a17a9fcee4a8e59c273b 2990 lazarus_2.0.6+dfsg-3.dsc 0f5b6983845ca8a54748c4a2502c1f2fe091e8955b8db0d25f29bd03e6e83fd8 71208 lazarus_2.0.6+dfsg-3.debian.tar.xz 396f84b834a805d31b7e37d88b57672a2db5ea64bde05800c8d964f7eab84644 19690 lazarus_2.0.6+dfsg-3_amd64.buildinfo Files: 5448b6846e75e18b81654c96e5fbdc16 2990 devel optional lazarus_2.0.6+dfsg-3.dsc 21d8be4c29e990a24723160742fd952d 71208 devel optional lazarus_2.0.6+dfsg-3.debian.tar.xz 94cb715a38e11a247560466f6bf36bc7 19690 devel optional lazarus_2.0.6+dfsg-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iI0EAREKADUWIQS69sZENhB4UNQicQazJVxtVYeNjAUCXfYddxccYWJvdS5hbG1v bnRhY2lyQHNmci5mcgAKCRCzJVxtVYeNjEVGAQCk1q6VL9mU2+qQJ1PM3pnZrM9m GNuzjzojeWjR7IyRmQD+OGUNnNjPO7inXX4I20Ev0N2k9E6CUBwJZqbfvIBB1Gg= =gFw7 -END PGP SIGNATURE End Message ---
Bug#945687: marked as done (kraft: Python2 removal in sid/bullseye)
Your message dated Sun, 15 Dec 2019 10:04:08 + with message-id and subject line Bug#945687: fixed in kraft 0.90-1 has caused the Debian Bug report #945687, regarding kraft: 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.) -- 945687: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945687 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: kraft Version: 0.82-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 (the specific reason can be found searching this source package in https://people.debian.org/~morph/mass-bug-py2removal_take3.txt ). 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 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: kraft Source-Version: 0.90-1 We believe that the bug you reported is fixed in the latest version of kraft, 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 945...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Pino Toscano (supplier of updated kraft package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 15 Dec 2019 10:37:17 +0100 Source: kraft Architecture: source Version: 0.90-1 Distribution: unstable Urgency: medium Maintainer: Debian KDE Extras Team Changed-By: Pino Toscano Closes: 935190 945687 Changes: kraft (0.90-1) unstable; urgency=medium . * Team upload. * New upstream release. * Add the configuration for the CI on salsa. * Update the build dependencies according to the upstream build system: - remove libkf5coreaddons-dev, libkf5widgetsaddons-dev, and libkf5xmlgui-dev - add libkf5config-dev - explicitly add gettext * The new unit tests do not seem to work with an uninstalled kraft, so do not invoke dh_auto_test. * Bump Standards-Version to 4.4.1, no changes required. * Bump the debhelper compatibility to 12: - switch the debhelper build dependency to debhelper-compat 12 - remove debian/compat * Drop the man page, as it is mostly obsolete. * Switch the erml2pdf.py invocation to Python 3: (Closes: #945687, #935190) - replace the python-reportlab, python-six, and python-pypdf2 dependencies with python3-reportlab, python3-six, and python3-pypdf2 - ex
Bug#946752: intel-opencl-icd: Depends on libigdgmm5, which no longer exists
Package: intel-opencl-icd
Version: 19.29.13530-1
Severity: serious
Justification: makes package uninstallable
This package's debian/control hardcodes a dependency on libigdgmm5. As
this library has changed soname to libigdgmm11, this makes it uninstallable.
Changing the dependency may well work, but I haven't tested this.
${shlibs:Depends} is meant to automatically track this, but since the
Depends _also_ has that and it doesn't produce a dependency on both
versions, it may not work for this package.
Processed: tagging 945687, tagging 935190
Processing commands for cont...@bugs.debian.org: > tags 945687 + pending Bug #945687 [src:kraft] kraft: Python2 removal in sid/bullseye Added tag(s) pending. > tags 935190 + pending Bug #935190 [src:kraft] python-pypdf2 removal Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 935190: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935190 945687: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945687 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#907489: Fixing sambamba 0.8.6
On Sun, Dec 15, 2019 at 03:15:59AM +0100, Matthias Klumpp wrote: > The LDC transition went really well this time, I don't think it has > ever been this smooth! No regressions this time, hurray! Indeed! > I had a bit of time to look into the sambamba/biod packages today, and > fixing them was actually really easy. Originally, I wanted to just > make use of the upstream-provided Makefiles, but unfortunately it was > really annoying to make them produce a proper static and dynamic > library, and then I would still have had the problem of installing all > pieces to the right locations and to write a pkg-config file. > Therefore, the way of least resistance was to just use Meson for > building, as that does everything we need in Debian. Both BioD and > Sambamba build well with Meson. That is great. We can add the meson builds in the repos. > I applied a few tweaks to the packages, that haven't been there > before: BioD is now built as a shared as well as a static library, so > applications can choose between the two. That's pretty common in > Debian, and as a sideeffect this also guarantees that things are > rebuilt properly when a transition happens. The Sambamba package will > now prefer statically linking BioD if possible (so BioD is statically > linked by default now in Debian). > Additionally both packages now apply the optimization flags upstream > has set for releases (-O3, no bounds checks, etc.). Combined, these > two changes should make the Debian builds comparably fast to the > upstream builds, but I haven't tested that yet. > There are also two brand new remaining issues: Apparently, for some > reason, SONAME isn't set correctly for BioD, producing a Lintian error > - not sure what happens there, and which component is to blame for > that (Meson or LDC, most likely). Also, Sambamba doesn't *actually* > build yet: > ``` > roup -L=-rpath > -L=/usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu:/usr/lib/x86_64-linux-gnu > slicereader.d:71: error: undefined reference to 'cram_to_bam' > collect2: error: ld returned 1 exit status > ``` > The cram_to_bam is private in htslib, so it shouldn't be used by other > applications. Not sure whether htslib or Sambamba needs to be changed > here, I simply worked around this issue for testing, and when this is > resolved, Sambamba builds & works. Sambamba ships with an old version of htslib that is patched for that function call. I plan to drop CRAM support and htslib. No one I know uses the CRAM functionality in sambamba. > Unfortunately I briefly forgot that this issue existed, so I already > uploaded the new sambamba package with this issue still present (I > remembered literally the moment the upload finished), so its builds > will fail. This is probably something for Andreas to look into :-) > > Anyway, I hope this is helpful to you and the resulting binaries are > performant :-) Thanks Matthias! Pj.
Bug#907489: Bug#938431: Fixing sambamba 0.8.6
On Sun, Dec 15, 2019 at 3:18 AM Matthias Klumpp wrote: > Am Do., 28. Nov. 2019 um 16:37 Uhr schrieb Pjotr Prins < > pjotr2...@thebird.nl>: > > > > When 1.18 arrives I think it is a good time to get sambamba and biod > > in Debian again. > > They always were in Debian, just not in a release because the packages > were broken ^^ > The LDC transition went really well this time, I don't think it has > ever been this smooth! No regressions this time, hurray! > Huzzah, indeed! > There are also two brand new remaining issues: Apparently, for some > reason, SONAME isn't set correctly for BioD, producing a Lintian error > - not sure what happens there, and which component is to blame for > that (Meson or LDC, most likely). Also, Sambamba doesn't *actually* > build yet: > ``` > roup -L=-rpath > -L=/usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu:/usr/lib/x86_64-linux-gnu > slicereader.d:71: error: undefined reference to 'cram_to_bam' > collect2: error: ld returned 1 exit status > ``` > The cram_to_bam is private in htslib, so it shouldn't be used by other > applications. Not sure whether htslib or Sambamba needs to be changed > here, I simply worked around this issue for testing, and when this is > resolved, Sambamba builds & works. > You'll be wanting libhts-private-dev, but libhts is broken in unstable right now; sorry! -- Michael R. Crusoe
Bug#946749: UICommon.so: cannot open shared object file
Package: virtualbox Version: 6.1.0-dfsg-1 Severity: grave Justification: renders package unusable The file UICommon.so is missing Complete error message: /usr/lib/virtualbox/VirtualBox: error while loading shared libraries: UICommon.so: cannot open shared object file: No such file or directory -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf Kernel: Linux 5.3.15 (SMP w/8 CPU cores; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages virtualbox depends on: ii adduser 3.118 ii iproute2 5.4.0-1 ii libc6 2.29-6 ii libcurl3-gnutls 7.67.0-2 ii libdevmapper1.02.12:1.02.155-3 ii libgcc1 1:9.2.1-21 ii libgl11.1.0-1+b1 ii libgsoap-2.8.91 2.8.91-2 ii libopus0 1.3-1+b1 ii libpng16-16 1.6.37-1 ii libpython3.7 3.7.5-2 ii libsdl1.2debian 1.2.15+dfsg2-5 ii libssl1.1 1.1.1d-2 ii libstdc++69.2.1-21 ii libvncserver1 0.9.12+dfsg-4 ii libvpx6 1.8.1-2 ii libx11-6 2:1.6.8-1 ii libxcursor1 1:1.2.0-2 ii libxml2 2.9.4+dfsg1-8 ii libxt61:1.1.5-1+b3 ii procps2:3.3.15-2+b1 ii python3 3.7.5-3 ii python3.7 3.7.5-2 ii virtualbox-dkms [virtualbox-modules] 6.1.0-dfsg-1 ii zlib1g1:1.2.11.dfsg-1+b1 Versions of packages virtualbox recommends: ii libqt5core5a5.12.5+dfsg-2 ii libqt5gui5 5.12.5+dfsg-2 ii libqt5opengl5 5.12.5+dfsg-2 ii libqt5widgets5 5.12.5+dfsg-2 ii libxcb1 1.13.1-2 ii libxext62:1.3.3-1+b2 ii libxmu6 2:1.1.2-2+b3 ii virtualbox-qt 6.1.0-dfsg-1 Versions of packages virtualbox suggests: ii vde22.3.2+r586-2.2+b1 ii virtualbox-guest-additions-iso 6.0.10-1 -- no debconf information
Bug#891233: marked as done (kamoso: segmentation fault in kamoso in Debian 9 stable. Application crashes while starting.)
Your message dated Sun, 15 Dec 2019 09:07:56 +0100 with message-id <6f1cbfbc-f3e7-4c8f-bedf-cff076040...@debian.org> and subject line Marking as closed has caused the Debian Bug report #891233, regarding kamoso: segmentation fault in kamoso in Debian 9 stable. Application crashes while starting. 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.) -- 891233: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891233 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: kamoso Version: 3.2.1-1 Severity: normal Hello Thanks for packaging kamoso. I've just installed it for the first time in my laptop using Debian 9 stable, and cannot make it run. When I start it from a terminal I get this message: $ kamoso Playing device changed "/dev/video0" Cannot initialize model with data QJsonObject() . missing: QJsonValue(string, "urls") new gamma 119 new gamma 120 file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls/Slider.qml:204:5: QML RangeModel: Binding loop detected for property "value" New saturation 100 New contrast 100 org.kde.kcoreaddons: doesn't know "" Segmentation fault The application seems to open a window but quickly crashes, in less than a second from my commandline. I've tried to launch it from the KDE Plasma menu as well, but nothing happens (I mean, it also crashes). Although the package is unusable, I've set severity to normal because I don't know if this affects any system or only a particular configuration. Best regards -- System Information: Debian Release: 9.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-5-amd64 (SMP w/4 CPU cores) Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages kamoso depends on: ii gstreamer1.0-plugins-good 1.10.4-1 ii gstreamer1.0-x 1.10.4-1 ii kio 5.28.0-2 ii libc6 2.24-11+deb9u1 ii libgcc1 1:6.3.0-18+deb9u1 ii libkf5configcore5 5.28.0-2 ii libkf5configgui55.28.0-2 ii libkf5coreaddons5 5.28.0-2 ii libkf5declarative5 5.28.0-1 ii libkf5i18n5 5.28.0-2 ii libkf5kiocore5 5.28.0-2 ii libkf5kiowidgets5 5.28.0-2 ii libqt5core5a5.7.1+dfsg-3+b1 ii libqt5glib-2.0-01.2.0-4 ii libqt5gstreamer-1.0-0 1.2.0-4 ii libqt5gstreamerquick-1.0-0 1.2.0-4 ii libqt5gui5 5.7.1+dfsg-3+b1 ii libqt5qml5 5.7.1-2+b2 ii libqt5quick55.7.1-2+b2 ii libqt5widgets5 5.7.1+dfsg-3+b1 ii libstdc++6 7.2.0-16 ii libudev1232-25+deb9u1 ii qml-module-org-kde-purpose 1.1-4 kamoso recommends no packages. kamoso suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- --- End Message ---
