Bug#1033170: marked as done (libitext-rups-java: Does not work at all)
Your message dated Wed, 29 Mar 2023 03:48:59 + with message-id and subject line Bug#1033170: fixed in libitext-java 2.1.7-14 has caused the Debian Bug report #1033170, regarding libitext-rups-java: Does not work at all 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.) -- 1033170: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033170 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libitext-rups-java Version: 2.1.7-13 Severity: grave Justification: renders package unusable X-Debbugs-Cc: jorge.moral...@gmail.com Dear Maintainer, The package does not work at all. Based on the following Ubuntu bug report it appears the version packaged is too old to work: https://bugs.launchpad.net/ubuntu/+source/libitext-java/+bug/802021 -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (800, 'testing'), (500, 'testing-security'), (50, 'experimental'), (50, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-6-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libitext-rups-java depends on: ii libitext-java 2.1.7-13 libitext-rups-java recommends no packages. libitext-rups-java suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: libitext-java Source-Version: 2.1.7-14 Done: tony mancill We believe that the bug you reported is fixed in the latest version of libitext-java, 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 1033...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. tony mancill (supplier of updated libitext-java package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 22 Mar 2023 19:59:21 -0700 Source: libitext-java Architecture: source Version: 2.1.7-14 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers Changed-By: tony mancill Closes: 1033170 Changes: libitext-java (2.1.7-14) unstable; urgency=medium . * Team upload. * Remove libitext-rups-java binary package (Closes: #1033170) Checksums-Sha1: ba0ff85bd80700b6933d2c6280018c1015a9e470 2257 libitext-java_2.1.7-14.dsc 368b50d5f6584083329dc356c9171a4240e6bf8a 42900 libitext-java_2.1.7-14.debian.tar.xz 91cfee7da8e951fc1b93a4ed733c700db7c0c961 12507 libitext-java_2.1.7-14_amd64.buildinfo Checksums-Sha256: c6bd9b65d7fa007fc61283164d00eed2275875802d22e034295c68ef87018dd4 2257 libitext-java_2.1.7-14.dsc 533ab941b1956d2cf228b6ba6f646bba7b8740f30f41101443ec880a833dcc21 42900 libitext-java_2.1.7-14.debian.tar.xz d45952749d9246965864624faee78ac9f18440fb21f5eb8a00d55dd698d2315e 12507 libitext-java_2.1.7-14_amd64.buildinfo Files: 93aa22d71acd8c0cf2dd91ed73337d87 2257 java optional libitext-java_2.1.7-14.dsc fa3c9b059bfb32a4f645fb95d8f4774d 42900 java optional libitext-java_2.1.7-14.debian.tar.xz 53bb4a282a387a4d713b82026acbd10a 12507 java optional libitext-java_2.1.7-14_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEE5Qr9Va3SequXFjqLIdIFiZdLPpYFAmQjsCgUHHRtYW5jaWxs QGRlYmlhbi5vcmcACgkQIdIFiZdLPpZo3A/9Fn8P4ik0wgOxznc3r6+VB+LGXXCm CpIOHEvSvyISnkX8XHT+TTpzDYSj4DyChDSuI6w4hgC39XSkBDr1opgLK8cDF+QH cdeMzQ7v6E5pWyXJYzYFvuDVyBowkgd3snpdbSsa/WSg1OZUhRHR+IqHFIykPKgx VeM4Sg/a9dUzY63i+AZLdf4nBt3LWJVq0WwSBo015s2PkCfO5E4Q7LCXS51RU5gc y4Acta4MD3d48qyTogZnsaVqpVVXmLDQHeZuqyoBi68vMaf4MgwkYwwGeJFddATw jnxsoxvvmFb1DOU6oouRGWlP8cjAZwSx0cVhNKFzf+ClvwPNQZidfEHJvnddMRJt dODvdFWGbA63DbbYSfb16+3GG9gStvL5ASxW/M8Cu+qigDw6JibR+5JeLkVaeI9V JRqr2Pd8e7yBa4OAuaGP0UbNY/kdLuSLl0rXnNr5Uk/FwFWwW9rPokQMAKhdIUz2 QkUWaLyXFyIqdd/hfilzvvnjn8AEt2/1iyI8yl3EmH+CobyUAM1e5DJi4tei5XgD zz07Q6gNbMGXAYuwyaQezScvcAdYohMS89QXYtzzY/0s/YfqQUYR8qgpVqD13IYA sc2NEJIUqe81VUgVhzV/twTe7+IrJi4x0Dbwqlq+2eTs+arJ7em6FbQvOdpzmzQC MXvY3R34G89vyFA= =Gywr -END PGP SIGNATURE End Message ---
Bug#1033170: libitext-rups-java: Does not work at all
Processed: Bug#1033170 marked as pending in libitext-java
Processing control commands: > tag -1 pending Bug #1033170 [libitext-rups-java] libitext-rups-java: Does not work at all Added tag(s) pending. -- 1033170: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033170 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1033170: marked as pending in libitext-java
Control: tag -1 pending Hello, Bug #1033170 in libitext-java reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/java-team/libitext-java/-/commit/f67a1b8530b8a46f99ef56d89e8f0a148698cae8 Remove libitext-rups-java binary package (Closes: #1033170) (this message was generated automatically) -- Greetings https://bugs.debian.org/1033170
Bug#1033530: marked as done (auto-apt-proxy: autopkgtest regression: squid-deb-proxy not available in testing)
Your message dated Wed, 29 Mar 2023 01:03:56 + with message-id and subject line Bug#1033530: fixed in auto-apt-proxy 14.1 has caused the Debian Bug report #1033530, regarding auto-apt-proxy: autopkgtest regression: squid-deb-proxy not available in testing 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.) -- 1033530: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033530 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: auto-apt-proxy Version: 14 Severity: serious Tags: bookworm-ignore User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), Your package has an autopkgtest, great. However, one of the tests depends on squid-deb-proxy which was removed from testing on 2022-10-19 and hence your test fails in testing (and it's in principle too late to fix squid-deb-proxy in bookworm). [Release Team hat on] Because of the timing of this bug (during the hard freeze) and because it doesn't seem to indicate functionality failure of this package, I have marked it as bookworm-ignore. However, if done reasonably soon, we'll unblock an upload fixing this issue. Paul OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: auto-apt-proxy Source-Version: 14.1 Done: Antonio Terceiro We believe that the bug you reported is fixed in the latest version of auto-apt-proxy, 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 1033...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Antonio Terceiro (supplier of updated auto-apt-proxy 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, 28 Mar 2023 21:56:37 -0300 Source: auto-apt-proxy Architecture: source Version: 14.1 Distribution: unstable Urgency: medium Maintainer: Antonio Terceiro Changed-By: Antonio Terceiro Closes: 1033530 Changes: auto-apt-proxy (14.1) unstable; urgency=medium . * autopkgtest: drop test for squid-deb-proxy (Closes: #1033530) Checksums-Sha1: 4c3f86fdcec57b93c7d85af88b2fc3bbdbf9da37 1765 auto-apt-proxy_14.1.dsc 631103ababc9d5590aa84baf06d6c4c96e11746c 18668 auto-apt-proxy_14.1.tar.xz cab4ddc25d3b0d90397a7a65af227906471b6b7a 6628 auto-apt-proxy_14.1_source.buildinfo Checksums-Sha256: 7389fad9a6cf3109901bec89cf54b41f499383b3347035b5ef635b48a2904014 1765 auto-apt-proxy_14.1.dsc 090f1d928f2a0a36fd59aeba9365ae682b851efb3e04f0281fdb60188f2cd175 18668 auto-apt-proxy_14.1.tar.xz 8d1dcdc0507740de8cbf5948b383dc44a95aa35ea5e679c01dc2d7358159eefa 6628 auto-apt-proxy_14.1_source.buildinfo Files: 28f1173f5d575bdeae15153275ada776 1765 net optional auto-apt-proxy_14.1.dsc c03effd0c7bccfb8fe08431fb3fd8e00 18668 net optional auto-apt-proxy_14.1.tar.xz 5690361fcfd1deb057b50021c4f9519c 6628 net optional auto-apt-proxy_14.1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEst7mYDbECCn80PEM/A2xu81GC94FAmQjjM4ACgkQ/A2xu81G C97dYxAA40HPP8NxtXBVC+YKgyzA9/uDt2iKZlecmDlCkh4IOsITUhHG71CdNQdk tzr+v2tHoo1BCC3Rom+JvjB8ix/EsHB8E3V3iyyURIIYS2G4Fx1Ah6hbE2RZ3L/n 3XTFOuTvm+4xVO5Nt+/d37juutpQ2pXAjw+1DvJ9X52aQz5ccxDx3I+67ymV/p/O +1qDYM2nxVy+8196vwTz8hEa2crHxFfx+nmoR5H+aOEFmrqLYpe89o/rrcITV6Ld kBCGH+G7swXGct0CEQv9G8FcyD2NdPEgrPi2ir2eMgiJLbBFXTh3UuN0aHxlid2n S5u4Cua4sCO4iw+tt23DUI/wVAfrbpbTjXgEEZd3BuVCwQHTtOy2NraNRyfeWmEP wD+c6QhsAXsLluiePEITr/9j3pW1/g9sOpUlwDXe341MxTLRVR/UD0GdqS0NrKVU Qg7xWEoaOpNTV1QSKIR6AyCL0prKE+9EyGalPTSKE7zIBB+Vk7YVwmsNLW4ajs+o TOt0xK+/rMcg3ulce28PYcTypqAoWX8bcpDGq74zv4TUznri+sxvhjFzz9ws4csR ODEZEF1hZ/o2uSNntlJtqpR6Yk8y78HUACh0LjojjG5g1ocVSG3czd/ukyW18G66 sCHMCgxigf1g1fvrgrO8ICevucodItsvyC+3Y0LXiq5KCRjJT0o= =PWAm -END PGP SIGNATURE End Message ---
Processed: your mail
Processing commands for cont...@bugs.debian.org: > affects 1032930 src:pynest2d Bug #1032930 [src:libnest2d] pynest2d: FTBFS with cmake 3.25: Libnest2D could not be found because dependency clipper could not be found. Added indication that 1032930 affects src:pynest2d > outlook 1032930 fix committed, waiting for release Outlook recorded from message bug 1032930 message > thanks Stopping processing here. Please contact me if you need assistance. -- 1032930: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032930 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 2 errors): your mail
Processing commands for cont...@bugs.debian.org:
> reassign 1032930 src:libnest2d 5.0.0-1
Bug #1032930 [src:pynest2d] pynest2d: FTBFS with cmake 3.25: Libnest2D could
not be found because dependency clipper could not be found.
Bug reassigned from package 'src:pynest2d' to 'src:libnest2d'.
No longer marked as found in versions pynest2d/5.0.0-1.
Ignoring request to alter fixed versions of bug #1032930 to the same values
previously set
Bug #1032930 [src:libnest2d] pynest2d: FTBFS with cmake 3.25: Libnest2D could
not be found because dependency clipper could not be found.
Marked as found in versions libnest2d/5.0.0-1.
> affects -1 src:pynest2d
Failed to mark -1 as affecting package(s): The 'bug' parameter ("-1") to
Debbugs::Control::affects did not pass regex check
.
> outlook -1 fix committed, waiting for release
Failed to give -1 a outlook: The 'bug' parameter ("-1") to
Debbugs::Control::_summary did not pass regex check
.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1032930: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032930
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed (with 1 error): Re: Bug#1030600: redis breaks python-fakeredis autopkgtest: Connection refused
Processing commands for cont...@bugs.debian.org: > reassign 1030600 src:redis 5:7.0.8-2 Bug #1030600 [src:redis, src:python-fakeredis] redis breaks python-fakeredis autopkgtest: Connection refused Bug reassigned from package 'src:redis, src:python-fakeredis' to 'src:redis'. No longer marked as found in versions python-fakeredis/1.9.0-0.1 and redis/5:7.0.8-2. Ignoring request to alter fixed versions of bug #1030600 to the same values previously set Bug #1030600 [src:redis] redis breaks python-fakeredis autopkgtest: Connection refused Marked as found in versions redis/5:7.0.8-2. > affects 1030600 src:python-fakeredis Bug #1030600 [src:redis] redis breaks python-fakeredis autopkgtest: Connection refused Added indication that 1030600 affects src:python-fakeredis > fixed 1030600 5:7.0.10-1 Bug #1030600 [src:redis] redis breaks python-fakeredis autopkgtest: Connection refused Marked as fixed in versions redis/5:7.0.10-1. > done 1030600 Unknown command or malformed arguments to command. > thanks Stopping processing here. Please contact me if you need assistance. -- 1030600: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030600 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1030600: redis breaks python-fakeredis autopkgtest: Connection refused
reassign 1030600 src:redis 5:7.0.8-2 affects 1030600 src:python-fakeredis fixed 1030600 5:7.0.10-1 done 1030600 thanks On Mon, Feb 06, 2023 at 10:46:52AM -0800, Chris Lamb wrote: Paul Gevers wrote: With a recent upload of redis the autopkgtest of python-fakeredis fails in testing when that autopkgtest is run with the binary packages of redis from unstable. It passes when run with only packages from testing. Just had a stab at this. Unfortunately, I tried updating the python-fakeredis package to the latest upstream version (hey, it worked before!), but I believe I get the same errors. Some thoughts: * I wonder if this is a compatibility issue with python3-redis; a few issues on upstream's Github project seem to suggest the two projects are more interconnected that one might initially believe. Apparently redis reverted or fixed the issue. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#1033621: node-matrix-js-sdk: CVE-2023-28427
Source: node-matrix-js-sdk Version: 9.11.0+~cs9.9.16-2 Severity: grave Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for node-matrix-js-sdk. CVE-2023-28427[0]: | Prototype pollution If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2023-28427 https://www.cve.org/CVERecord?id=CVE-2023-28427 [1] https://github.com/matrix-org/matrix-js-sdk/security/advisories/GHSA-mwq8-fjpf-c2gr Please adjust the affected versions in the BTS as needed. Regards, Salvatore
Bug#1033617: libopenexr-dev: Cannot just upgrade libopenexr-dev to 3.1.5-4 because of file conflict with older version of libilmbase-dev
for documentation purposes, I now fixed the issue for my systems by
force-removing the old package first with dpkg and then installing its
replacements with markauto:
sudo dpkg --remove --force-depends libilmbase-dev
sudo aptitude install lib{imath,openexr}-dev+M # or apt install --mark-auto
lib{imath,openexr}-dev
Bug#1033617: libopenexr-dev: Cannot just upgrade libopenexr-dev to 3.1.5-4 because of file conflict with older version of libilmbase-dev
Package: libopenexr-dev Version: 3.1.5-4 Severity: serious Justification: Policy 7.4 X-Debbugs-Cc: me+debian-b...@banananet.work Dear Maintainer, I cannot upgrade this package from version 2.5.7-1 to version 3.1.5-4 due to a file conflict with the package libilmbase-dev on version 2.5.4-1. I tried with apt & aptitude as well. Both want to replace libilmbase-dev with libopenexr-dev in a single execution of them, but fail to do that in a way that dpkg allows that (tries first to install the new package and then uninstall the old one). Currently I see no other solution than removing the old one first aside with all packages depending it on it, and then installing the new one with all packages which were removed before. They already have a "Breaks" & a "Replace" relationship, which seems to be right, but I assume adding a "Conflicts" relation will fix that, for "Breaks" "dpkg will refuse to allow the package […] to be unpacked unless the broken package is deconfigured first", while for "Conflicts" it says that "dpkg will refuse to allow them to be unpacked on the system at the same time". I marked this bug as serious as I think, even if another solution may be found, that still a Conflicts field on this package referring to the older one may be required unless that is not possible. However, I'm not 100% sure, so feel free to change the severity. Maybe I just ran into this problem due to other circumstances a stable user will not run into. Also I assume that if this configuration will be released into bookworm, others will having problems as well. Best Regards, Felix Stupp -- System Information: Debian Release: 12.0 APT prefers testing APT policy: (550, 'testing'), (500, 'testing-security'), (400, 'stable-updates'), (400, 'stable-security'), (400, 'stable'), (110, 'unstable'), (102, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-3-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libopenexr-dev depends on: pn libilmbase-dev ii libopenexr252.5.7-1 libopenexr-dev recommends no packages. libopenexr-dev suggests no packages. -- no debconf information
Bug#1033602: nvidia-graphics-drivers: dh_missing finds missing files and I think it is my fault
Now I am following your lead and what you wrote. Tried with the untouched source version and it worked. I have noticed that the dch foo edits the changelog so I tried to update it to the actual version. Now it fails at the checksums . since your method seems to differ from the kernel deb compilation I was asking myself how does he updates the checksums ? On Tue, 2023-03-28 at 17:16 +0200, Andreas Beckmann wrote: > On 28/03/2023 16.11, Renato Gallo wrote: > > First things first Thanks again I will try > > I based my experiment onto the master main git > > what should I clone to be reasonably safe and follow your lead ? > > 525 or better 530. master is ancient and stale (and is no longer > refreenced in metadata, so should really go away. > > > Andreas
Bug#1033602: nvidia-graphics-drivers: dh_missing finds missing files and I think it is my fault
On 28/03/2023 16.11, Renato Gallo wrote: First things first Thanks again I will try I based my experiment onto the master main git what should I clone to be reasonably safe and follow your lead ? 525 or better 530. master is ancient and stale (and is no longer refreenced in metadata, so should really go away. Andreas
Bug#1033602: nvidia-graphics-drivers: dh_missing finds missing files and I think it is my fault
Tried Now I am trying to build the new version and obviously it fails on the checksums. When you try with the kernel in debian/bin there's a gen.py command that does it. How do you update the checksums ? Thanks again :) On Tue, 2023-03-28 at 15:20 +0200, Andreas Beckmann wrote: > On 28/03/2023 11.24, Renato Gallo wrote: > > I am mainly blaming myself, and I would be grateful if you > > can give me a hint about what am I missing. > > You should start with rebuilding the package that is in the archive - > that obviously works for me and the buildds ;-) > This should help to separate errors on your side (please take no > offense > here, the documentation for working with these packages is likely > bad, > incomplete and outdated (patches welcome!), so its unfortunately hard > for outsiders to get the workflow running) from problems caused by > possible upstream layout changes ... > > Which packaging code did you base your work on? Branch 530 in git? (I > hope I pushed that after uploading the beta packages.) > > I only build these packages with gbp (git-buildpackage) backed by > pbuilder, but sbuild should work as well. I never used debuild (or > dpkg-buildpackage) directly on them. > > Just tried in a chroot with build-essential and devscripts installed: > > # apt-get build-dep nvidia-graphics-drivers > # su -s /bin/bash - nobody > $ cd /tmp > $ apt-get source nvidia-graphics-drivers > $ cd nvidia-graphics-drivers-530.30.02/ > $ dch foo > $ debuild > > and I got ../nvidia-graphics-drivers_530.30.02-1.1_amd64.changes > > Andreas
Bug#1033602: nvidia-graphics-drivers: dh_missing finds missing files and I think it is my fault
First things first Thanks again I will try I based my experiment onto the master main git what should I clone to be reasonably safe and follow your lead ? On Tue, 28 Mar 2023 15:20:47 +0200 Andreas Beckmann wrote: > On 28/03/2023 11.24, Renato Gallo wrote: > > I am mainly blaming myself, and I would be grateful if you can give me a hint about what am I missing. > > You should start with rebuilding the package that is in the archive - > that obviously works for me and the buildds ;-) > This should help to separate errors on your side (please take no offense > here, the documentation for working with these packages is likely bad, > incomplete and outdated (patches welcome!), so its unfortunately hard > for outsiders to get the workflow running) from problems caused by > possible upstream layout changes ... > > Which packaging code did you base your work on? Branch 530 in git? (I > hope I pushed that after uploading the beta packages.) > > I only build these packages with gbp (git-buildpackage) backed by > pbuilder, but sbuild should work as well. I never used debuild (or > dpkg-buildpackage) directly on them. > > Just tried in a chroot with build-essential and devscripts installed: > > # apt-get build-dep nvidia-graphics-drivers > # su -s /bin/bash - nobody > $ cd /tmp > $ apt-get source nvidia-graphics-drivers > $ cd nvidia-graphics-drivers-530.30.02/ > $ dch foo > $ debuild > > and I got ../nvidia-graphics-drivers_530.30.02-1.1_amd64.changes > > Andreas > >
Bug#1033608: Exception: ModuleNotFoundError: No module named 'core.pe.photo'
Package: dupeguru Version: 4.3.1-3+b1 Severity: grave Justification: renders package unusable The upstream vanilla build symlinks /usr/share/dupeguru/core/pe and /usr/share/dupeguru/qt/pe to /usr/lib/dupeguru/core/pe and /usr/lib/dupeguru/qt/pe respectively. In the debian package these symlinks are missing, and emptu directories are created instead (although the lib files are built and packaged). This causes an immediate exception on run. -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (501, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-5-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages dupeguru depends on: ii libc6 2.36-8 ii python3 3.11.2-1 ii python3-distro1.8.0-1 ii python3-mutagen 1.46.0-1 ii python3-pyqt5 5.15.9+dfsg-1 ii python3-semantic-version 2.9.0-2 ii python3-send2trash1.8.1~b0-2 ii python3-xxhash3.2.0-1+b1 dupeguru recommends no packages. dupeguru suggests no packages. -- no debconf information
Bug#1033602: nvidia-graphics-drivers: dh_missing finds missing files and I think it is my fault
On 28/03/2023 11.24, Renato Gallo wrote: I am mainly blaming myself, and I would be grateful if you can give me a hint about what am I missing. You should start with rebuilding the package that is in the archive - that obviously works for me and the buildds ;-) This should help to separate errors on your side (please take no offense here, the documentation for working with these packages is likely bad, incomplete and outdated (patches welcome!), so its unfortunately hard for outsiders to get the workflow running) from problems caused by possible upstream layout changes ... Which packaging code did you base your work on? Branch 530 in git? (I hope I pushed that after uploading the beta packages.) I only build these packages with gbp (git-buildpackage) backed by pbuilder, but sbuild should work as well. I never used debuild (or dpkg-buildpackage) directly on them. Just tried in a chroot with build-essential and devscripts installed: # apt-get build-dep nvidia-graphics-drivers # su -s /bin/bash - nobody $ cd /tmp $ apt-get source nvidia-graphics-drivers $ cd nvidia-graphics-drivers-530.30.02/ $ dch foo $ debuild and I got ../nvidia-graphics-drivers_530.30.02-1.1_amd64.changes Andreas
Bug#1030854: kded5: It keeps on crashing everytime I boot into the system
Package: kded5 Version: 5.103.0-1 Followup-For: Bug #1030854 X-Debbugs-Cc: dutchgig...@gmail.com still happening with Bookworm release... Hint: You are currently not seeing messages from other users and the system. Users in groups 'adm', 'systemd-journal' can see all messages. Pass -q to turn off this notice. PID: 13997 (kded5) UID: 1000 (verwijs) GID: 1000 (verwijs) Signal: 11 (SEGV) Timestamp: Tue 2023-03-28 14:44:49 CEST (5min ago) Command Line: /usr/bin/kded5 Executable: /usr/bin/kded5 Control Group: /user.slice/user-1000.slice/user@1000.service/session.slice/dbus.service Unit: user@1000.service User Unit: dbus.service Slice: user-1000.slice Owner UID: 1000 (verwijs) Boot ID: b42844118a6548a98d3b3f60093f2ecd Machine ID: caaee3f8a89d430081634817f93feaa6 Hostname: debian-verwijs Storage: /var/lib/systemd/coredump/core.kded5.1000.b42844118a6548a98d3b3f60093f2ecd.13997.168000748900.zst (present) Size on Disk: 3.7M Message: Process 13997 (kded5) of user 1000 dumped core. Module libsystemd.so.0 from deb systemd-252.6-1.amd64 Module libudev.so.1 from deb systemd-252.6-1.amd64 Stack trace of thread 14017: #0 0x7f068f6a9ccc n/a (libc.so.6 + 0x8accc) #1 0x7f068f65aef2 raise (libc.so.6 + 0x3bef2) #2 0x7f0690756b46 _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x5b46) #3 0x7f068f65af90 n/a (libc.so.6 + 0x3bf90) #4 0x7f068f6a9ccc n/a (libc.so.6 + 0x8accc) #5 0x7f068f65aef2 raise (libc.so.6 + 0x3bef2) #6 0x7f068f65af90 n/a (libc.so.6 + 0x3bf90) #7 0x7f068f6a9ccc n/a (libc.so.6 + 0x8accc) #8 0x7f068f65aef2 raise (libc.so.6 + 0x3bef2) #9 0x7f06727f13b0 g_closure_invoke (libgobject-2.0.so.0 + 0x163b0) #10 0x7f06728041a5 n/a (libgobject-2.0.so.0 + 0x291a5) #11 0x7f067280abf5 g_signal_emit_valist (libgobject-2.0.so.0 + 0x2fbf5) #12 0x7f067280adbf g_signal_emit (libgobject-2.0.so.0 + 0x2fdbf) #13 0x7f067293d115 n/a (libgio-2.0.so.0 + 0x103115) #14 0x7f068e86267f g_main_context_dispatch (libglib-2.0.so.0 + 0x5467f) #15 0x7f068e862a38 n/a (libglib-2.0.so.0 + 0x54a38) #16 0x7f068e862acc g_main_context_iteration (libglib-2.0.so.0 + 0x54acc) #17 0x7f06727d44bd n/a (libdconfsettings.so + 0xb4bd) #18 0x7f068e88ccfd n/a (libglib-2.0.so.0 + 0x7ecfd) #19 0x7f068f6a7fd4 n/a (libc.so.6 + 0x88fd4) #20 0x7f068f72866c n/a (libc.so.6 + 0x10966c) Stack trace of thread 13997: #0 0x7f068f71b0af __poll (libc.so.6 + 0xfc0af) #1 0x7f0690756150 n/a (libKF5Crash.so.5 + 0x5150) #2 0x7f0690756ad6 _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x5ad6) #3 0x7f068f65af90 n/a (libc.so.6 + 0x3bf90) #4 0x7f06705eeba4 _ZNK10PackageKit11Transaction4roleEv (libpackagekitqt5.so.1 + 0x1aba4) #5 0x7f067068ccae n/a (kded_apperd.so + 0xfcae) #6 0x7f067068cdf6 n/a (kded_apperd.so + 0xfdf6) #7 0x7f068fae8f4f n/a (libQt5Core.so.5 + 0x2e8f4f) #8 0x7f06705e2095 _ZN10PackageKit6Daemon22transactionListChangedERK11QStringList (libpackagekitqt5.so.1 + 0xe095) #9 0x7f068fae8f7c n/a (libQt5Core.so.5 + 0x2e8f7c) #10 0x7f06705fab38 n/a (libpackagekitqt5.so.1 + 0x26b38) #11 0x7f06705fbd73 n/a (libpackagekitqt5.so.1 + 0x27d73) #12 0x7f06905ad61b n/a (libQt5DBus.so.5 + 0x2361b) #13 0x7f068fadd6f0 _ZN7QObject5eventEP6QEvent (libQt5Core.so.5 + 0x2dd6f0) #14 0x7f0690962fae _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x162fae) #15 0x7f068fab16f8 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x2b16f8) #16 0x7f068fab4681 _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt5Core.so.5 + 0x2b4681) #17 0x7f068fb0a153 n/a (libQt5Core.so.5 + 0x30a153) #18 0x7f068e8627a9 g_main_context_dispatch (libglib-2.0.so.0 + 0x547a9) #19 0x7f068e862a38 n/a (libglib-2.0.so.0 + 0x54a38) #20 0x7f068e862acc g_main_context_iteration (libglib-2.0.so.0 + 0x54acc) #21 0x7f068fb09836 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x309836) #22 0x7f068fab017b
Bug#1033607: sogo: /usr/bin/sogo linked against wrong version of libgnustep-base
Package: sogo Version: 5.0.1-4+deb11u1 Severity: grave Justification: renders package unusable Dear Maintainer, The binary of /usr/sbin/sogod contained in bullseye is linked to libgnustep-base.so.1.24. However, the package depends on libgnustep-base.so.1.27, which is the current version of bullseye. Downgrading is not possible due to dependencies. I assume re-building the binary with correct dependencies will fix this. Kind regards, Phil -- System Information: Debian Release: 11.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-20-amd64 (SMP w/8 CPU threads) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8), LANGUAGE=en_GB.UTF-8 Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages sogo depends on: ii adduser 3.118 ii gnustep-base-runtime 1.27.0-3 ii init-system-helpers 1.60 ii libc6 2.31-13+deb11u5 ii libcrypt1 1:4.4.18-4 ii libcurl4 7.74.0-1.3+deb11u3 ii libgcc-s1 10.2.1-6 ii libglib2.0-0 2.66.8-1 ii libgnustep-base1.27 1.27.0-3 ii liblasso3 2.6.1-3 ii libmemcached111.0.18-4.2 ii liboath0 2.6.6-3 ii libobjc4 10.2.1-6 ii libsbjson2.3 2.3.2-4+b2 ii libsodium23 1.0.18-1 ii libsope1 5.0.1-2 ii libssl1.1 1.1.1n-0+deb11u3 ii libzip4 1.7.3-1 ii lsb-base 11.1.0 ii memcached 1.6.9+dfsg-1 ii sogo-common 5.0.1-4+deb11u1 ii systemd 247.3-7+deb11u1 ii zip 3.0-12 sogo recommends no packages. Versions of packages sogo suggests: ii default-mysql-server1.0.7 ii mariadb-server-10.5 [virtual-mysql-server] 1:10.5.18-0+deb11u1 -- Configuration Files: /etc/sogo/sogo.conf [Errno 13] Permission denied: '/etc/sogo/sogo.conf' -- no debconf information
Bug#1033408: apache2: Segmentation fault + 503 on frontpage on 2.4.56-1
Hi, Sorry for the delay, as it is a production server I won't be allowed to compile a new apache2 with the patch. FYI, I now have a second server (production too unfortunately) with the same issue. Rollbacked on 2.4.54 as well to solve the segfaults. I didn't try this workaround, but I guess disabling mod_http2 would "solve" the issue as well ? Le ven. 24 mars 2023 à 20:55, Salvatore Bonaccorso a écrit : > Hi, > > On Fri, Mar 24, 2023 at 05:17:34PM +0100, Fabien LE BERRE wrote: > > Yes it does look like the bug. The Backtrace looks a lot like the > coredump > > I've seen. > > Thanks for the heads up. Looking forward for the patch to be applied > > officially. > > Would you be able to have additionally test the patch on your case to > confirm? That would be great and helpful for releasing the regression > update. > > Regards, > Salvatore > -- *Fabien Le Berre** Homme de la situation* 01 86 95 54 04 - 37 rue des Mathurins - 75008 Paris Le ven. 24 mars 2023 à 20:55, Salvatore Bonaccorso a écrit : > Hi, > > On Fri, Mar 24, 2023 at 05:17:34PM +0100, Fabien LE BERRE wrote: > > Yes it does look like the bug. The Backtrace looks a lot like the > coredump > > I've seen. > > Thanks for the heads up. Looking forward for the patch to be applied > > officially. > > Would you be able to have additionally test the patch on your case to > confirm? That would be great and helpful for releasing the regression > update. > > Regards, > Salvatore > -- *Fabien Le Berre** Homme de la situation* 01 86 95 54 04 - 37 rue des Mathurins - 75008 Paris
Bug#1033170: libitext-rups-java: Does not work at all
Le 2023-03-28 05:28, tony mancill a écrit : The upload is ready. Any concerns? $ reverse-depends libitext-rups-java No reverse dependencies found $ reverse-depends -b libitext-rups-java No reverse dependencies found +1 for removing libitext-rups-java, and maybe libitext-rtf-java too.
Bug#1033602: nvidia-graphics-drivers: dh_missing finds missing files and I think it is my fault
Source: nvidia-graphics-drivers Version: 530.41.03 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Dear Maintainer, I am trying to debuild nvidia-graphics drivers 530.41.03 (since I would love to test the new 6.3.x kernels and I have read that the new version supports those, I'd love to see if it is true) I tried to follow the README.sources included in the git Since I could not find the instruction to debuild the code I tried to use debuild -us -uc as usual Sadly at the end of the process dh_missing finds missing files (I'd like to know how those can be included in the build) The outcome I am expecting is to have the 530.41.03 dkms, bins, libs, debs ... etc, so I can test I am mainly blaming myself, and I would be grateful if you can give me a hint about what am I missing. Thanks in advance for your time and effort. p.s. queue the boring error log make[2]: Leaving directory '/usr/src/nvidia/nvidia-graphics-drivers' dh_lintian dh_perl dh_link dh_compress dh_fixperms dh_missing dh_missing: warning: kernel-open/Kbuild exists in debian/tmp but is not installed to anywhere (related file: "debian/tmp/kernel/Kbuild") dh_missing: warning: kernel-open/Makefile exists in debian/tmp but is not installed to anywhere (related file: "debian/tmp/kernel/Makefile") dh_missing: warning: kernel-open/common/inc/conftest.h exists in debian/tmp but is not installed to anywhere dh_missing: warning: kernel-open/common/inc/cpuopsys.h exists in debian/tmp but is not installed to anywhere dh_missing: warning: kernel-open/common/inc/nv-caps.h exists in debian/tmp but is not installed to anywhere dh_missing: warning: kernel-open/common/inc/nv-dmabuf.h exists in debian/tmp but is not installed to anywhere dh_missing: warning: kernel-open/common/inc/nv-firmware.h exists in debian/tmp but is not installed to anywhere dh_missing: warning: kernel-open/common/inc/nv-gpu-info.h exists in debian/tmp but is not installed to anywhere dh_missing: warning: kernel-open/common/inc/nv-hash.h exists in debian/tmp but is not installed to anywhere dh_missing: warning: kernel-open/common/inc/nv-hypervisor.h exists in debian/tmp but is not installed to anywhere dh_missing: warning: kernel-open/common/inc/nv-ioctl-numa.h exists in debian/tmp but is not installed to anywhere dh_missing: warning: kernel-open/common/inc/nv-ioctl-numbers.h exists in debian/tmp but is not installed to anywhere dh_missing: warning: kernel-open/common/inc/nv-ioctl.h exists in debian/tmp but is not installed to anywhere dh_missing: warning: kernel-open/common/inc/nv-kernel-interface-api.h exists in debian/tmp but is not installed to anywhere dh_missing: warning: kernel-open/common/inc/nv-kref.h exists in debian/tmp but is not installed to anywhere dh_missing: warning: kernel-open/common/inc/nv-kthread-q.h exists in debian/tmp but is not installed to anywhere dh_missing: warning: kernel-open/common/inc/nv-linux.h exists in debian/tmp but is not installed to anywhere dh_missing: warning: kernel-open/common/inc/nv-list-helpers.h exists in debian/tmp but is not installed to anywhere dh_missing: warning: kernel-open/common/inc/nv-lock.h exists in debian/tmp but is not installed to anywhere dh_missing: warning: kernel-open/common/inc/nv-memdbg.h exists in debian/tmp but is not installed to anywhere dh_missing: warning: kernel-open/common/inc/nv-mm.h exists in debian/tmp but is not installed to anywhere dh_missing: warning: kernel-open/common/inc/nv-modeset-interface.h exists in debian/tmp but is not installed to anywhere dh_missing: warning: kernel-open/common/inc/nv-msi.h exists in debian/tmp but is not installed to anywhere dh_missing: warning: kernel-open/common/inc/nv-pci-types.h exists in debian/tmp but is not installed to anywhere dh_missing: warning: kernel-open/common/inc/nv-pci.h exists in debian/tmp but is not installed to anywhere dh_missing: warning: kernel-open/common/inc/nv-pgprot.h exists in debian/tmp but is not installed to anywhere dh_missing: warning: kernel-open/common/inc/nv-procfs-utils.h exists in debian/tmp but is not installed to anywhere dh_missing: warning: kernel-open/common/inc/nv-procfs.h exists in debian/tmp but is not installed to anywhere dh_missing: warning: kernel-open/common/inc/nv-proto.h exists in debian/tmp but is not installed to anywhere dh_missing: warning: kernel-open/common/inc/nv-register-module.h exists in debian/tmp but is not installed to anywhere dh_missing: warning: kernel-open/common/inc/nv-retpoline.h exists in debian/tmp but is not installed to anywhere dh_missing: warning: kernel-open/common/inc/nv-time.h exists in debian/tmp but is not installed to anywhere dh_missing: warning: kernel-open/common/inc/nv-timer.h exists in debian/tmp but is not installed to anywhere dh_missing: warning: kernel-open/common/inc/nv.h exists
Bug#1033598: mlbstreamer: Can't authenticate against 2023 mlb.tv
Package: mlbstreamer
Version: 0.0.11.dev0+git20190330-1
Severity: grave
Tags: upstream
With a valid account, the stack-trace produced looks like:
[play:32 ] [ ERROR] Uncaught exception
Traceback (most recent call last):
File "/bin/mlbplay", line 11, in
load_entry_point('mlbstreamer==0.0.11.dev0', 'console_scripts',
'mlbplay')()
File "/usr/lib/python3/dist-packages/mlbstreamer/play.py", line 374, in main
proc = play_stream(
File "/usr/lib/python3/dist-packages/mlbstreamer/play.py", line 153, in
play_stream
stream = state.session.get_stream(media)
^^^
File "/usr/lib/python3/dist-packages/mlbstreamer/session.py", line 834, in
get_stream
"Authorization": self.access_token,
^
File "/usr/lib/python3/dist-packages/mlbstreamer/session.py", line 548, in
access_token
self.refresh_access_token()
File "/usr/lib/python3/dist-packages/mlbstreamer/session.py", line 587, in
refresh_access_token
raise Exception(authz_content)
The project has been discontinued upstream for a couple of years, so
this won't be fixed.
For the record, yt-dlp is a viable alternative since it gained a
working and maintained MLBTV extractor.
Cheers,
--
Seb
