Bug#1034217: marked as done (qbittorrent-nox: dh_installsystemd doesn't handle files in /usr/lib/systemd/system)
Your message dated Fri, 21 Apr 2023 06:49:33 + with message-id and subject line Bug#1034217: fixed in qbittorrent 4.5.2-2 has caused the Debian Bug report #1034217, regarding qbittorrent-nox: dh_installsystemd doesn't handle files in /usr/lib/systemd/system 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.) -- 1034217: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034217 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: qbittorrent-nox Version: 4.5.2-1 Severity: serious Tags: sid bookworm User: debhel...@packages.debian.org Usertags: systemd-files-in-usr-bookworm Dear Maintainer, It seems that your package qbittorrent-nox is shipping files (.service, .socket or .timer) in /usr/lib/systemd/system. This is not supported by the version of dh_installsystemd/debhelper currently in unstable and bookworm (See: #1031695). That means that currently your service might not be enabled at boot and/or started as expected. With the freeze currently in effect, debhelper will not be fixed for bookworm. As a result, could you please move these files to /lib/systemd/system instead so they are properly detected by debhelper? As soon as debhelper is supporting (not until bookworm+1 aka Trixie) you will be able to move them back to the newer location. Note that bookworm is currently in hard freeze, please limit the changes you are uploading to the ones fixing RC bugs. Also note that you might have to request a freeze exception to the release team. See: https://release.debian.org/testing/freeze_policy.html Feel free to contact me if you have any questions. Kind regards, Laurent Bigonville The list of packages has been generated with the following command: apt-file search -x '^/usr/lib/systemd/system/.*\.(service|timer|socket)$'|cut -d: -f1|sort -u --- End Message --- --- Begin Message --- Source: qbittorrent Source-Version: 4.5.2-2 Done: Christian Marillat We believe that the bug you reported is fixed in the latest version of qbittorrent, 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 1034...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christian Marillat (supplier of updated qbittorrent 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: Fri, 21 Apr 2023 08:29:03 +0200 Source: qbittorrent Architecture: source Version: 4.5.2-2 Distribution: unstable Urgency: medium Maintainer: Christian Marillat Changed-By: Christian Marillat Closes: 1034217 Changes: qbittorrent (4.5.2-2) unstable; urgency=medium . * Move systemd file to /lib/systemd/system (was /usr/lib/systemd/system) (Closes: #1034217) Checksums-Sha1: f613dcf6f83af75202a025d69d2d416d80938eed 1942 qbittorrent_4.5.2-2.dsc 22a43c2c0258d4ffad607ef041458c9ddf5aa67d 120688 qbittorrent_4.5.2-2.debian.tar.xz 82498a392d42b94dfacfd5816b80dc9d1ddd813b 11540 qbittorrent_4.5.2-2_source.buildinfo Checksums-Sha256: 9790d6a8a5950bb4297ae11469e5e349add9e1b7bbb2583f53b21f8a8ba7c4d8 1942 qbittorrent_4.5.2-2.dsc 30eadf7ea7e5997e983337bca35eb22395e69d358dbed1f89a79cad01ed97b5b 120688 qbittorrent_4.5.2-2.debian.tar.xz e1ba1c8da1120f0fbe5b22dbd82a87e3c79204080cb08b4ed14cfc8be0b813b6 11540 qbittorrent_4.5.2-2_source.buildinfo Files: 5ee09dace11d7e58bab27e005e9f719b 1942 net optional qbittorrent_4.5.2-2.dsc 68d0c5943ec838a4eaf15cd33cf47e40 120688 net optional qbittorrent_4.5.2-2.debian.tar.xz 6d6c7ccefca99f18e94a04b3d1a5fa3e 11540 net optional qbittorrent_4.5.2-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEpAH/mTaPofmBUt51XICMK2VVgRcFAmRCLWsACgkQXICMK2VV gRdWlA/6AsgqQie8zmtg2TlHTyuYm5G4BoSUMBdgdE8kNfN7n+JojUYc+wcvKkF9 jvlXpYhR3GDwDM084iiGggVpFuOjLCuZLYbHB/w37AoiHNyOkHkoZEzWgL4otTlT 1vZyOtPyl+3s06xd0SIPHfoocW2CIIysLzhhWcqpjd0pTP6Lu5/SabW6wlRfDm+X dPF3u76pSG9BOLlQTp/pn5RFFgm/eCXPzJGZE8FO/9iQYnBlCtVsj6lWl68b5Avb bAWV0o2Lsvz3UQlwf4ncxAmMs8BzNg9vA4a/LYSG4Z4BYSx4zr5b6FdQhrVkTddK hV3u0/+ro/Ndv271XUqe5Zj60sEl6LWkVVU0qzmGYIzmt0NT1rEollNv5wVBwFHP 2xs9kCmZ59ew5zLHx/w1XxJXqLYQQqxNM/K8zk51HZndi1wSj51WZ+k0qUv+BagK Kz36StdYHkMXeeeI505w+r45z9yPqAlg2PYiLvr5xkElaaf4biH1JXtu33a/d7Ns iPkIsTB/qyH4fEMiSdmhZ/NQIWiHzrJksqmcPcfL
Bug#1033617: libopenexr-dev: Cannot just upgrade libopenexr-dev to 3.1.5-4 because of file conflict with older version of libilmbase-dev
Hi! On Thu, Apr 20, 2023 at 7:15 PM Andreas Metzler wrote: > Hello Paul, > > I will not have time for a NMU before next week, I can probably fit it > in then. > If it's ok for you, I'll fix it during the weekend. Cheers. -- Matteo F. Vescovi || Debian Developer GnuPG KeyID: 4096R/0x8062398983B2CF7A
Processed: Re: inkscape: canvas stops updating completely when trying to edit a text box
Processing control commands: > forwarded -1 https://gitlab.com/inkscape/inkscape/-/issues/3664 Bug #1034289 [inkscape] inkscape: canvas stops updating completely when trying to edit a text box Set Bug forwarded-to-address to 'https://gitlab.com/inkscape/inkscape/-/issues/3664'. -- 1034289: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034289 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1034289: inkscape: canvas stops updating completely when trying to edit a text box
Source: inkscape Followup-For: Bug #1034289 X-Debbugs-Cc: giuseppe.bilo...@gmail.com, debian-gtk-gn...@lists.debian.org Control: forwarded -1 https://gitlab.com/inkscape/inkscape/-/issues/3664 Dear Maintainer (and cc'ing the GTK-GNOME list), Following on from Giuseppe's upstream link: > Additional information: the issue I'm seeing seems to match upstream > issue #3664 > https://gitlab.com/inkscape/inkscape/-/issues/3664 ... to a further-upstream bug[1] in the GTK issue tracker, there's a reference to GDK window repainting as the possible cause[2] (with a suggested fix). The (untested) patch I've attached here applies the suggested change to src:gtk+3.0 (and was created from version gtk+3.0-3.24.37 of it). I don't yet have an environment prepared to build and test it, but will try to create one soon. Thanks, James [1] - https://gitlab.gnome.org/GNOME/gtk/-/issues/2560 [2] - https://gitlab.gnome.org/GNOME/gtk/-/issues/2560#note_757809 Description: gdkwindow: allow frame paint events to occur for non-toplevel windows . Partially-reverts upstream commit fc569f1ac6ff108afc17f7f439480273826af3a6. Author: James Addison Bug: https://gitlab.gnome.org/GNOME/gtk/-/issues/2560 Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034289 Last-Update: 2023-04-21 --- gtk+3.0-3.24.37.orig/gdk/gdkwindow.c +++ gtk+3.0-3.24.37/gdk/gdkwindow.c @@ -3253,7 +3253,7 @@ gdk_window_begin_draw_frame (GdkWindow return NULL; } - if (gdk_window_has_native (window) && gdk_window_is_toplevel (window)) + if (gdk_window_has_native (window)) gdk_window_begin_paint_internal (window, region); impl_class = GDK_WINDOW_IMPL_GET_CLASS (window->impl); @@ -3307,7 +3307,7 @@ gdk_window_end_draw_frame (GdkWindow return; } - if (gdk_window_has_native (window) && gdk_window_is_toplevel (window)) + if (gdk_window_has_native (window)) gdk_window_end_paint_internal (window); impl_class = GDK_WINDOW_IMPL_GET_CLASS (window->impl);
Bug#1031152: system-config-printer: unlock button in system-config-printer provides no elevated permissions dialog
On my Debian 11 XFCE machine this works correctly. Make sure "PolicyKit Authentication Agent" is checked under "Session and Startup" -> "Application Autostart". In Debian 12 under Sway the GNOME Authentication Agent segfaults, but I will take this up under separate cover. I was able to work around the issue for the moment by using lxpolkit for the authentication agent instead.
Bug#1028301: marked as done (grub: grub-probe doesn't detect that file is on cryptfs on new installation)
Your message dated Thu, 20 Apr 2023 21:34:44 + with message-id and subject line Bug#1028301: fixed in grub2 2.06-9 has caused the Debian Bug report #1028301, regarding grub: grub-probe doesn't detect that file is on cryptfs on new installation to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1028301: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028301 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: grub-common Version: 2.06-7 Severity: serious File: /usr/sbin/grub-probe Hello, On a newly installed laptop, it seems that grub-probe is not able to detect that files are on an encrypted FS. New laptop: $ sudo grub-probe -t abstraction /usr/share/images/desktop-base/desktop-grub.png lvm $ sudo lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS nvme0n1 259:00 476,9G 0 disk ├─nvme0n1p1 259:10 512M 0 part /boot/efi ├─nvme0n1p2 259:20 488M 0 part /boot └─nvme0n1p3 259:30 476G 0 part └─nvme0n1p3_crypt 254:00 475,9G 0 crypt ├─new_laptop--vg-root254:10 27,9G 0 lvm / ├─new_laptop--vg-swap_1 254:20 976M 0 lvm [SWAP] ├─new_laptop--vg-home254:3040G 0 lvm /home └─new_laptop--vg-libvirt 254:4060G 0 lvm /var/lib/libvirt Old laptop: $ sudo grub-probe -t abstraction /usr/share/images/desktop-base/desktop-grub.png cryptodisk luks gcry_rijndael gcry_rijndael gcry_sha256 lvm $ sudo lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS sda8:01 0B 0 disk nvme0n1 259:00 476,9G 0 disk ├─nvme0n1p1 259:10 512M 0 part /boot/efi ├─nvme0n1p2 259:20 244M 0 part /boot └─nvme0n1p3 259:30 476,2G 0 part └─nvme0n1p3_crypt 254:00 476,2G 0 crypt ├─old_laptop--vg-root254:10 27,9G 0 lvm / ├─old_laptop--vg-swap_1 254:20 31,7G 0 lvm [SWAP] ├─old_laptop--vg-home254:30 120G 0 lvm /home ├─old_laptop--vg-sid_amd64_sbuild254:40 5G 0 lvm ├─old_laptop--vg-flatpak 254:5050G 0 lvm /var/lib/flatpak ├─old_laptop--vg-libvirt 254:6075G 0 lvm /var/lib/libvirt ├─old_laptop--vg-docker 254:7010G 0 lvm /var/lib/docker ├─old_laptop--vg-acng254:8010G 0 lvm /var/cache/apt-cacher-ng └─old_laptop--vg-buster_amd64_sbuild 254:90 5G 0 lvm Setting this as serious as this seems to be a regression, this at least breaks grub ability to display the theme wallpaper. Kind regards, Laurent Bigonville --- End Message --- --- Begin Message --- Source: grub2 Source-Version: 2.06-9 Done: Steve McIntyre <93...@debian.org> We believe that the bug you reported is fixed in the latest version of grub2, 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 1028...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Steve McIntyre <93...@debian.org> (supplier of updated grub2 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 20 Apr 2023 20:35:11 +0100 Source: grub2 Architecture: source Version: 2.06-9 Distribution: unstable Urgency: medium Maintainer: GRUB Maintainers Changed-By: Steve McIntyre <93...@debian.org> Closes: 1001248 1012865 1020769 1025698 1028301 1031594 1033657 Changes: grub2 (2.06-9) unstable; urgency=medium . [ Steve McIntyre ] * postinst: make config_item() more robust * Add debconf logic for GRUB_DISABLE_OS_PROBER to make it easier to control things here. Particularly useful for the installer. Closes: #1031594, #1012865, #1025698. * Add luks2 to the signed grub efi images. Closes: #1001248 . [ Ben Hutchings ] * Fix probing of LUKS2 devices (Closes: #1028301): - disk/cryptodisk: When cheatmounting, use the sector info of the cheat device - osdep/devmapper/getroot
Bug#1031370:
Hi, I've submitted a merge request on Salsa to fix this. https://salsa.debian.org/python-team/packages/python-werkzeug/-/merge_requests/3 Regards, Robin
Processed: tagging 1031370
Processing commands for cont...@bugs.debian.org: > tags 1031370 + patch Bug #1031370 [src:python-werkzeug] python-werkzeug: CVE-2023-23934 CVE-2023-25577 Ignoring request to alter tags of bug #1031370 to the same tags previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 1031370: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031370 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1031370
Processing commands for cont...@bugs.debian.org: > tags 1031370 + patch Bug #1031370 [src:python-werkzeug] python-werkzeug: CVE-2023-23934 CVE-2023-25577 Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 1031370: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031370 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1034310: [digikam] [Bug 466170] Digikam 7.9.0 (and 7.8.0) crashes on startup
Just a note to say that I have used a Debian "testing" chroot environment and can reproduce the reported crash. I will be investigating more in the coming days. -Steve signature.asc Description: This is a digitally signed message part.
Processed: Re: Bug#1034610: grub-common no longer supports labels
Processing control commands: > severity -1 important Bug #1034610 [grub-common] grub-common no longer supports labels Severity set to 'important' from 'critical' -- 1034610: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034610 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1034610: grub-common no longer supports labels
Control: severity -1 important Hi! On Wed, Apr 19, 2023 at 02:52:31PM -0300, Dario Susman wrote: >Package: grub-common >Version: 2.06-8 >Severity: critical >Justification: breaks the whole system > >Dear Maintainer, > >After upgrading to latest version of grub-common and kernel, the system >wouldn't boot up with the latest kernel. The device paths changed, sda1 >to sdb1. I noticed that the grub config changed to use UUIDs, however >/etc/default/grub is set to use LABELS. Which is something I prefer to >do. > >It seems that grub-mkinfo no longer supports the GRUB_ENABLE_LINUX_LABEL >parameters and has to be re-written for it to work. Looking in the history, I can't see where we've ever supported this. Can you tell me which version(s) ever had this working for you please? -- Steve McIntyre, Cambridge, UK.st...@einval.com Welcome my son, welcome to the machine.
Bug#1033617: libopenexr-dev: Cannot just upgrade libopenexr-dev to 3.1.5-4 because of file conflict with older version of libilmbase-dev
On 2023-04-20 Paul Gevers wrote: > Hi Andreas, > On Fri, 31 Mar 2023 15:06:14 +0200 Andreas Metzler wrote: > > I think 2.5.7-2 was the last sourceful < 3 upload, so (<< 2.5.7-3) > > should work. > And to be backports and other local packages, I think that could/should be > (<< 2.5.7-3~). > Can a/this fix be uploaded soon please? We're trying to pick a bookworm > release date and a fix should be in. Hello Paul, I will not have time for a NMU before next week, I can probably fit it in then. cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'
Bug#1033832: marked as pending in php-db
Control: tag -1 pending Hello, Bug #1033832 in php-db 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/php-team/pear/php-db/-/commit/f2123b042898f37b5a1cc9408ddbe24d3e4ce4b8 Add a patch for PHP 8.2 dynamic properties (Closes: #1033832) (this message was generated automatically) -- Greetings https://bugs.debian.org/1033832
Processed: Bug#1033832 marked as pending in php-db
Processing control commands: > tag -1 pending Bug #1033832 [src:php-db] php-db: autopkgtest regression: FAIL DB::DB_Error[DB-1.11.0/tests/db_error.phpt] Ignoring request to alter tags of bug #1033832 to the same tags previously set -- 1033832: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033832 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1034190: More security bugs in game loading
On Thu, 2023-04-20 at 10:01 +0200, Paul Gevers wrote: > Hi Ben, > > On Mon, 10 Apr 2023 22:01:04 +0200 Ben Hutchings > wrote: > > Package: sgt-puzzles > > Severity: serious > > The fix for this bug will not automatically migrate to testing because > the package doesn't have autopkgtests and we're in the freeze. The > changes are massive, They're actually not that massive, but split into a lot of small patches. > so I'd like to confirm in an unblock bug that all > changes are indeed targeted fixes before unblocking. Can you file such > an unblock request if you don't want the package to be autoremoved (or > add a non-superficial autopkgtest if that makes sense)? Yes, I will file an unblock request. Ben. -- Ben Hutchings Editing code like this is akin to sticking plasters on the bleeding stump of a severed limb. - me, 29 June 1999 signature.asc Description: This is a digitally signed message part
Bug#1033424: marked as done (image-factory: FTBFS in testing: AssertionError: pylint found issues:)
Your message dated Thu, 20 Apr 2023 10:39:58 +
with message-id
and subject line Bug#1033424: fixed in image-factory 1.0.2-1.1
has caused the Debian Bug report #1033424,
regarding image-factory: FTBFS in testing: AssertionError: pylint found issues:
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.)
--
1033424: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033424
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: image-factory
Version: 1.0.2-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230323 ftbfs-bookworm
Hi,
During a rebuild of all packages in testing (bookworm), your package failed
to build on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> python3 -m unittest discover -v
> test_black (tests.test_black.BlackTestCase.test_black)
> Test: Run black code formatter on Python source code. ... Running following
> command:
> black --check --diff -l 99 image-factory tests
> ok
> test_empty_config (tests.test_cli.TestCLI.test_empty_config)
> Test empty configuration file. ... ok
> test_example_config (tests.test_cli.TestCLI.test_example_config)
> Test exapmle image-factory.conf file. ... ok
> test_override_cache_dir (tests.test_cli.TestCLI.test_override_cache_dir)
> Test overriding the cache directory. ... ok
> test_flake8 (tests.test_flake8.Flake8TestCase.test_flake8)
> Test: Run flake8 on Python source code. ... Running following command:
> /usr/bin/python3 -m flake8 --max-line-length=99 image-factory tests
> ok
> test_invalid (tests.test_helper.TestParseBytes.test_invalid)
> Test parse_bytes("invalid") ... ok
> test_parse_1_g (tests.test_helper.TestParseBytes.test_parse_1_g)
> Test parse_bytes("1G") ... ok
> test_parse_2_tb (tests.test_helper.TestParseBytes.test_parse_2_tb)
> Test parse_bytes("2 TB") ... ok
> test_parse_512_mib (tests.test_helper.TestParseBytes.test_parse_512_mib)
> Test parse_bytes("512 MiB") ... ok
> test_isort (tests.test_isort.IsortTestCase.test_isort)
> Test: Run isort on Python source code. ... Running following command:
> isort --check-only --diff -l 99 image-factory tests
> ok
> test_pylint (tests.test_pylint.PylintTestCase.test_pylint)
> Test: Run pylint on Python source code. ... Running following command:
> /usr/bin/python3 -m pylint --rcfile=/<>/tests/pylint.conf --
> image-factory tests
> FAIL
> test_chmod_dnf_log (tests.test_sudo_helper.TestSudoHelper.test_chmod_dnf_log)
> Test read access for dnf log file. ... ok
> test_chmod_log_file
> (tests.test_sudo_helper.TestSudoHelper.test_chmod_log_file)
> Test read access for mounted /var/log/... ... ok
> test_chmod_recursive
> (tests.test_sudo_helper.TestSudoHelper.test_chmod_recursive)
> Test chmod recursively ... ok
> test_chmod_remove_root
> (tests.test_sudo_helper.TestSudoHelper.test_chmod_remove_root)
> Test chmod remove mounted /root permission ... ok
> test_chmod_root (tests.test_sudo_helper.TestSudoHelper.test_chmod_root)
> Test chmod mounted /root ... ok
> test_chmod_var_log (tests.test_sudo_helper.TestSudoHelper.test_chmod_var_log)
> Test write access for mounted /var/log/... ... ok
> test_mount (tests.test_sudo_helper.TestSudoHelper.test_mount)
> Test mounting. ... ok
> test_reject_escaping
> (tests.test_sudo_helper.TestSudoHelper.test_reject_escaping)
> Test rejecting ../../etc/shadow. ... ok
> test_umount (tests.test_sudo_helper.TestSudoHelper.test_umount)
> Test unmounting. ... ok
>
> ==
> FAIL: test_pylint (tests.test_pylint.PylintTestCase.test_pylint)
> Test: Run pylint on Python source code.
> --
> Traceback (most recent call last):
> File "/<>/tests/test_pylint.py", line 74, in test_pylint
> self.fail("\n".join(msgs))
> AssertionError: pylint found issues:
> * Module image-factory
> image-factory:64:12: W0719: Raising too general exception: Exception
> (broad-exception-raised)
> image-factory:138:8: W0719: Raising too general exception: Exception
> (broad-exception-raised)
> image-factory:166:8: W0719: Raising too general exception: Exception
> (broad-exception-raised)
>
> --
> Ran 20 tests in 8.079s
>
> FAILED (failures=1)
> make[1]: *** [Makefile:13: check] Error 1
> make[1]: Leaving directory '/<>'
> dh_auto_test: error: make -j8 check returned exit code 2
The full build log is available from:
http://qa-logs.debian.net/2023/03/23/image-factory_1.0.2-1_testing.log
A
Bug#1033617: libopenexr-dev: Cannot just upgrade libopenexr-dev to 3.1.5-4 because of file conflict with older version of libilmbase-dev
Hi Andreas, On Fri, 31 Mar 2023 15:06:14 +0200 Andreas Metzler wrote: I think 2.5.7-2 was the last sourceful < 3 upload, so (<< 2.5.7-3) should work. And to be backports and other local packages, I think that could/should be (<< 2.5.7-3~). Can a/this fix be uploaded soon please? We're trying to pick a bookworm release date and a fix should be in. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#910861: marked as done (Tool for managing users and groups will not start any more)
Your message dated Thu, 20 Apr 2023 11:28:08 +0200 with message-id <1749151f-6349-03bc-0d20-1c639ac0d...@debian.org> and subject line mate-system-tools has been removed from Debian has caused the Debian Bug report #910861, regarding Tool for managing users and groups will not start any more 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.) -- 910861: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910861 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: mate-system-tools Version: 1.8.1+dfsg1-2 Severity: grave Tags: Dear maintainer I use Debian Jessie with the MATE desktop environment. The application for adding and removing users and groups (command: mate-users-admin) will not start any more when clicking: System > Management > Users and groups System log: Oct 11 13:51:30 desktop-computer kernel: [ 1141.192153] traps: mate-users-admi[2865] trap int3 ip:7f982286b261 sp:7ffda2bb4830 error:0 Oct 11 13:51:30 desktop-computer kernel: [ 1141.192157] in libglib-2.0.so.0.5000.3[7f982281b000+112000] When using a terminal window: root@desktop-computer:/home/maarten# mate-users-admin (mate-users-admin:5553): Gtk-ERROR **: GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported Traceer/breekpunt-instructie root@desktop-computer:/home/maarten# I did not have this problem earlier. I do not have any broken packages and debsums -as indicated that all my packages are intact. Synaptic (package manager) tells that mate-system-tools also contains the tool for adjusting the date and time, and the tool for setting the network options. These two tools were found easily in the Configuration Centre. However, those tools also do not start any more. Debian Jessie is being advised for production machines. I hope that this programming error gets corrected soon. With kind regards Maarten --- End Message --- --- Begin Message --- Version: 1.8.1+dfsg1-2+rm mate-system-tools was last released with Debian 8 (jessie) in April 2015 and has been removed from the Debian archive afterwards. See https://bugs.debian.org/812730 for details on the removal. Regular security support for jessie ended in June 2018 and LTS support ended in June 2020. I'm closing the remaining bug reports now. Andreas--- End Message ---
Bug#861029: marked as done (AttributeError: When using gi.repository you must not import static modules like "gobject")
Your message dated Thu, 20 Apr 2023 11:24:44 +0200 with message-id and subject line aptdaemon has been superseded by packagekit has caused the Debian Bug report #861029, regarding AttributeError: When using gi.repository you must not import static modules like "gobject" 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.) -- 861029: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861029 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: aptdaemon Version: 1.1.1-4+deb8u1 Severity: grave Justification: renders package unusable $ aptdcon Traceback (most recent call last): File "/usr/bin/aptdcon", line 25, in import aptdaemon.console File "/usr/lib/python3/dist-packages/aptdaemon/console.py", line 49, in from . import client File "/usr/lib/python3/dist-packages/aptdaemon/client.py", line 43, in _GObject = GObject.GObject File "/usr/lib/python3/dist-packages/gi/__init__.py", line 64, in __getattr__ raise AttributeError(_static_binding_error) AttributeError: When using gi.repository you must not import static modules like "gobject". Please change all occurrences of "import gobject" to "from gi.repository import GObject". See: https://bugzilla.gnome.org/show_bug.cgi?id=709183 -- System Information: Debian Release: 9.0 APT prefers stable APT policy: (500, 'stable'), (70, 'unstable'), (60, 'testing'), (50, 'experimental'), (40, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-2-rt-amd64 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages aptdaemon depends on: ii gir1.2-glib-2.01.51.5-1 ii policykit-10.113-5 ii python33.5.3-1 ii python3-aptdaemon 1.1.1-4+deb8u1 ii python3-gi 3.22.0-2 pn python3:any Versions of packages aptdaemon recommends: pn lintian aptdaemon suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Version: 1.1.1+bzr982-1+rm aptdaemon was last released with Debian 8 (jessie) in April 2015 and has been removed from the Debian archive afterwards. See https://bugs.debian.org/825272 for details on the removal. Regular security support for jessie ended in June 2018 and LTS support ended in June 2020. I'm closing the remaining bug reports now. Andreas--- End Message ---
Bug#826213: marked as done (w3c-dtd-xhtml: inconsistencies in copyright file)
Your message dated Thu, 20 Apr 2023 11:15:07 +0200 with message-id and subject line w3c-dtd-xhtml has been superseded by w3c-sgml-lib has caused the Debian Bug report #826213, regarding w3c-dtd-xhtml: inconsistencies in copyright 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.) -- 826213: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=826213 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: w3c-dtd-xhtml Version: 1.2-4 Severity: serious Justification: Policy §12.5 1. The file /usr/share/doc/w3c-dtd-xhtml/copyright is not encoded as UTF-8, which is a MUST in Policy. 2. very long; for a 'tl;dr' see below (grep for 'CONCLUSION') The following sentence can be found in the file… | According to http://www.w3.org/Consortium/Legal/IPR-FAQ-2620.html, | "while schemas and DTDs are frequently part of our specifications and | seemingly fall under the document copyright terms, you may use them under | the W3C Software License." … but this is not true, this information is not contained within that document any more. I’ve done some web.archive.org digging, and the last version in which it was included is: http://web.archive.org/web/20090817142721/http://www.w3.org/Consortium/Legal/IPR-FAQ-2620.html#DTD | Check the actual schema or DTDs for a specific license. | | Otherwise, while schemas and DTDs are frequently part of our specifications and seemingly fall | under the [73]document copyright terms, you may use them under the [74]W3C Software License. The | software license requires that you include/retain the copyright attribution and that you indicate | any modification that you make. In the case of DTDs and schema, you must indicate your change by | changing the namespace and/or public identifier so to distinguish your altered version from the W3C | version. We further appreciate a couple sentences regarding who made the modifications, when, and | what changes were made — a common software documentation practice. | | We expect to revisit this topic as meta-data schemas become an increasingly important part of W3C | specifications and as the meta-data schema definition capabilities of XML and RDF advance. | | [added 19990323; tweaked 20030102] So this information no longer applies. However, either statement is a licence grant that’s not revoked, so I guess this still works. There is an older grant at http://web.archive.org/web/20021125050943/http://www.w3.org/Consortium/Legal/IPR-FAQ-2620.html#DTD which does not allow general default to the software licence however. Actually, the oldest grant still found is: http://web.archive.org/web/2815195302/http://www.w3.org/Consortium/Legal/IPR-FAQ-2620.html#DTD | Schemas (and DTDs) are frequently part of our specifications and seemingly fall under the | [58]document copyright terms. However, as long as you do not use the same formal namespace or | public identifier to identify that modified W3C schema/DTD (which might confuse applications), you | may treat the schema/DTD under the [59]software terms. This means that you are permitted to make a | derivative or modified W3C schema/DTD, but even under the [60]software terms you are obligated to | include/retain the W3C copyright notice. We further appreciate a couple sentences regarding who | made the modifications, when, and what changes were made in the original DTD -- a common software | documentation practice. | | We expect to revisit this topic as metadata schemas become and increasingly important part of W3C | specifications and as the metadata schema definition capabilities of XML and RDF advance. | | [added 19990323] The problem with these grants, all of them, is that any document published past their date (i.e. between 20090817 and 20100217, the exact cutoff point being unclear) is *NOT* covered by them. In the case of all files included in this package, they probably are older than the cutoff date. The extra grant is useful for files like xhtml1-frameset.dtd which lacks an explicit licence grant, and the entities files, whose grant is restricted, although XHTML 1.1 thankfully has a separate, much easier grant. The relevant licence to use, by the way, is this (I checked it, and it’s identical to the subsequent archive snapshot): http://web.archive.org/web/20090815033126/http://www.w3.org/Consortium/Legal/2002/copyright-software-20021231 The “short notice” should also be added to the Debian copyright file as it’s part of the licence. It is (again, same as next snapshot): http://web.archive.org/web/20090814014731/http://www.w3.org/Consortium
Bug#1034190: More security bugs in game loading
Hi Ben, On Mon, 10 Apr 2023 22:01:04 +0200 Ben Hutchings wrote: Package: sgt-puzzles Severity: serious The fix for this bug will not automatically migrate to testing because the package doesn't have autopkgtests and we're in the freeze. The changes are massive, so I'd like to confirm in an unblock bug that all changes are indeed targeted fixes before unblocking. Can you file such an unblock request if you don't want the package to be autoremoved (or add a non-superficial autopkgtest if that makes sense)? Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#1031152: system-config-printer: unlock button in system-config-printer provides no elevated permissions dialog
On Sun, 12 Feb 2023 09:06:02 -0500 Alexis wrote: [...] > > > * What was the outcome of this action? > > The following error was thrown: > > Gtk-WARNING **: 08:47:30.475: Error acquiring permission: Failed to acquire permission for action-id org.opensuse.cupspkhelper.mechanism.all-edit Do you have the cups-pk-helper package installed? system-config-printer-common already recommends that package. The definition of Recommends is: "This declares a strong, but not absolute, dependency. The Recommends field should list packages that would be found together with this one in all but unusual installations.", so you should probably also install recommended packages. Kind regards, Laurent Bigonville
Bug#1034629: pdf-presenter-console: pdfpc terminates with symbol lookup error
Package: pdf-presenter-console Version: 4.6.0-1 Severity: grave Justification: renders package unusable X-Debbugs-Cc: jaesc...@l3s.de Dear Maintainer, When starting pdfpc it immediately dies with the following error message: > pdfpc slides.pdf pdfpc: symbol lookup error: /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37: undefined symbol: gst_transcoder_get_sync_signal_adapter -- System Information: Debian Release: 12.0 APT prefers testing APT policy: (500, 'testing'), (50, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-7-amd64 (SMP w/12 CPU threads; PREEMPT) Locale: LANG=de_DE.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 pdf-presenter-console depends on: ii libc6 2.36-9 ii libcairo2 1.16.0-7 ii libgdk-pixbuf-2.0-0 2.42.10+dfsg-1+b1 ii libgee-0.8-20.20.6-1 ii libglib2.0-02.74.6-2 ii libgstreamer-plugins-base1.0-0 1.22.0-3 ii libgstreamer1.0-0 1.22.0-2 ii libgtk-3-0 3.24.37-2 ii libjson-glib-1.0-0 1.6.6-1 ii libmarkdown22.2.7-2 ii libpango-1.0-0 1.50.12+ds-1 ii libpangocairo-1.0-0 1.50.12+ds-1 ii libpoppler-glib822.12.0-2+b1 ii libqrencode44.1.1-1 ii libsoup2.4-12.74.3-1 ii libwebkit2gtk-4.0-372.40.0-3 ii libx11-62:1.8.4-2 Versions of packages pdf-presenter-console recommends: ii gstreamer1.0-gtk3 1.22.0-5 pdf-presenter-console suggests no packages. -- no debconf information
Processed: bug 1034609 is forwarded to https://github.com/agronholm/sqlacodegen/issues/239
Processing commands for cont...@bugs.debian.org: > forwarded 1034609 https://github.com/agronholm/sqlacodegen/issues/239 Bug #1034609 [sqlacodegen] Fails to start under Python 3.11 Set Bug forwarded-to-address to 'https://github.com/agronholm/sqlacodegen/issues/239'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1034609: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034609 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
