Bug#803721: marked as done (kdm stopped working and is now stuck on a lightdm saved session)
Your message dated Sun, 16 Apr 2023 07:12:46 +0200 with message-id and subject line kdm has been superseded by sddm has caused the Debian Bug report #803721, regarding kdm stopped working and is now stuck on a lightdm saved session 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.) -- 803721: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803721 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: kdm Version: 4:4.11.22-3 Severity: grave -- System Information: Debian Release: stretch/sid Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.2.0-1-amd64 (SMP w/8 CPU cores) 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 kdm depends on: ii adduser 3.113+nmu3 ii debconf [debconf-2.0] 1.5.57 ii kde-runtime 4:15.08.2-1 ii kde-wallpapers-default 4:15.04.2-1 ii kde-workspace-kgreet-plugins 4:4.11.22-3 ii libc6 2.19-22 ii libkdecore5 4:4.14.13-1 ii libkdeui5 4:4.14.13-1 ii libkio5 4:4.14.13-1 ii libknewstuff3-4 4:4.14.13-1 ii libkworkspace4abi2 4:4.11.22-3 ii libpam0g 1.1.8-3.1 ii libqimageblitz4 1:0.0.6-4 ii libqt4-svg 4:4.8.7+dfsg-3 ii libqt4-xml 4:4.8.7+dfsg-3 ii libqtcore4 4:4.8.7+dfsg-3 ii libqtgui4 4:4.8.7+dfsg-3 ii libstdc++6 5.2.1-22 ii libx11-6 2:1.6.3-1 ii libxau6 1:1.0.8-1 ii libxdmcp6 1:1.1.2-1 ii libxtst6 2:1.2.2-1+b1 ii lsb-base 9.20150917 Versions of packages kdm recommends: ii konsole [x-terminal-emulator] 4:15.08.2-1 ii logrotate 3.8.7-2 ii openbox [x-window-manager] 3.6.1-2 ii xserver-xorg [xserver] 1:7.7+12 ii xterm [x-terminal-emulator]320-1 Versions of packages kdm suggests: ii kde-wallpapers 4:15.04.2-1 ii kdepasswd 4:15.08.1-1 -- debconf information: kdm/daemon_name: /usr/bin/kdm kdm/stop_running_server_with_children: false Dear maintainer: KDE is migrating to Plasma5 and many things break in the process. libqt5x11extras5 migrated into testing without their dependencies, but even after downgrading kdm did not work. Computer cannot start normally, I have to start it with: startx startkde. I tried to get a dm to work so installed lightdm, it did not work either. Neither does sddm. I completely purged lightdm, then issued command 'apt-get autoremove --purge', also removed all remnants in /usr/share. Still, kdm starts and goes to a lightdm saved session, which of course fails. I cannot understand how this can happen, as my system settings are set to start with a clean session. How can I delete this saved session that is stuck somewhere? I have been working on this for a while, some upgrades have been done to some nvidia packages and things improved somewhat, kdm still does not launch and goes to that saved session. Please help. --- End Message --- --- Begin Message --- Version: 4:4.11.22-3+rm kdm was last released with Debian 8 (jessie) in April 2015 and was removed from the Debian archive afterwards. It has been superseded by sddm. See https://bugs.debian.org/803635 for details on the removal. I'm closing the remaining bug reports now. Andreas--- End Message ---
Bug#1034310: [digikam] [Bug 466170] Digikam 7.9.0 (and 7.8.0) crashes on startup
On Fri, 14 Apr 2023 14:24:31 +0200 Rainer Dorsch wrote: > Thanks Marco, that is a good link. > > I provided a backtrace and upstream acknowledged the bug to be fixed in 8.1.0: Hello Rainer, I've looked at the upstream bug, and all the information you provided. That's awesome -- I wish that every bug submitter would be as thorough as you! It seems that, even with disabling the splash screen, you still experience the bug -- is that correct? I can say that I'm not experiencing any such crash. I created a new user to test from scratch. I see the splash screen come and go, then the pop-up that offers to download the faces data files. I can download them or not and it all works fine either way. So it's puzzling. I'm also using an x64 system, but I run on the "sid/ unstable" distribution so I have slightly different versions of the dependency packages. Maybe it's worth attempting an upgrade of some or all of these to see if the problem goes away? Perhaps start with libkf5configcore5, since the failing assert seems to be in that library: qt_assert_x(char const*, char const*, char const*, int) () at /lib/ x86_64-linux-gnu/libQt5Core.so.5 Here is the list from my system today. Versions of packages digikam depends on: ii digikam-data 4:7.9.0-1 ii digikam-private-libs 4:7.9.0-1+b2 ii libc6 2.36-9 ii libgcc-s1 12.2.0-14 ii libkf5configcore5 5.103.0-2 ii libkf5coreaddons5 5.103.0-1 ii libkf5i18n5 5.103.0-1 ii libmagick++-6.q16-8 8:6.9.11.60+dfsg-1.6 ii libqt5core5a 5.15.8+dfsg-7 ii libqt5gui55.15.8+dfsg-7 ii libqt5sql55.15.8+dfsg-7 ii libqt5sql5-mysql 5.15.8+dfsg-7 ii libqt5sql5-sqlite 5.15.8+dfsg-7 ii libqt5widgets55.15.8+dfsg-7 ii libstdc++612.2.0-14 ii perl 5.36.0-7 Versions of packages digikam recommends: ii brave-browser [www-browser] 1.50.119 ii ffmpegthumbs4:22.12.3-1 ii firefox-esr [www-browser] 102.10.0esr-1 ii google-chrome-stable [www-browser] 112.0.5615.121-1 ii konqueror [www-browser] 4:22.12.3-1 ii lynx [www-browser] 2.9.0dev.12-1 ii w3m [www-browser] 0.5.3+git20230121-2 Versions of packages digikam suggests: ii breeze-icon-theme 4:5.103.0-1 pn digikam-doc ii systemsettings 4:5.27.2-1 Best, -Steve signature.asc Description: This is a digitally signed message part.
Bug#1018747: fixed - gimp-gap recommends mplayer that is (finally) in bookworm
mplayer is (finally) in bookworm: Bug 1005899 is fixed. [2023-02-13] mplayer 2:1.5+svn38408-1 MIGRATED to testing https://tracker.debian.org/news/1420921/mplayer-215svn38408-1-migrated-to-testing/ So Bug#1018747 is fixed and gimp-gap can be returned to bookworm
Bug#1033782: marked as done (nvidia-graphics-drivers-tesla: CVE-2023-0184, CVE-2023-0189, CVE-2023-0180, CVE-2023-0183, CVE-2023-0185, CVE-2023-0187, CVE-2023-0198, CVE-2023-0199, CVE-2023-0188, CVE-2
Your message dated Sat, 15 Apr 2023 21:20:05 + with message-id and subject line Bug#1033782: fixed in nvidia-graphics-drivers-tesla 525.105.17-1 has caused the Debian Bug report #1033782, regarding nvidia-graphics-drivers-tesla: CVE-2023-0184, CVE-2023-0189, CVE-2023-0180, CVE-2023-0183, CVE-2023-0185, CVE-2023-0187, CVE-2023-0198, CVE-2023-0199, CVE-2023-0188, CVE-2023-0190, CVE-2023-0194, CVE-2023-0195, CVE-2023-0191 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.) -- 1033782: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033782 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: nvidia-graphics-drivers Severity: serious Tags: security upstream X-Debbugs-Cc: Debian Security Team Control: clone -1 -2 -3 -4 -5 -6 -7 -8 -9 -10 Control: reassign -2 src:nvidia-graphics-drivers-legacy-340xx 340.76-6 Control: retitle -2 nvidia-graphics-drivers-legacy-340xx: CVE-2023-0184, CVE-2023-0189, CVE-2023-0180, CVE-2023-0185, CVE-2023-0198, CVE-2023-0199, CVE-2023-0188, CVE-2023-0190, CVE-2023-0194, CVE-2023-0195, CVE-2023-0191 Control: tag -2 + wontfix Control: reassign -3 src:nvidia-graphics-drivers-legacy-390xx 390.48-4 Control: retitle -3 nvidia-graphics-drivers-legacy-390xx: CVE-2023-0184, CVE-2023-0189, CVE-2023-0180, CVE-2023-0185, CVE-2023-0198, CVE-2023-0199, CVE-2023-0188, CVE-2023-0190, CVE-2023-0194, CVE-2023-0195, CVE-2023-0191 Control: tag -3 + wontfix Control: reassign -4 src:nvidia-graphics-drivers-tesla-418 418.87.01-1 Control: retitle -4 nvidia-graphics-drivers-tesla-418: CVE-2023-0184, CVE-2023-0189, CVE-2023-0180, CVE-2023-0185, CVE-2023-0198, CVE-2023-0199, CVE-2023-0188, CVE-2023-0190, CVE-2023-0194, CVE-2023-0195, CVE-2023-0191 Control: tag -4 + wontfix Control: reassign -5 src:nvidia-graphics-drivers-tesla-450 450.51.05-1 Control: retitle -5 nvidia-graphics-drivers-tesla-450: CVE-2023-0184, CVE-2023-0189, CVE-2023-0180, CVE-2023-0185, CVE-2023-0198, CVE-2023-0199, CVE-2023-0188, CVE-2023-0190, CVE-2023-0194, CVE-2023-0195, CVE-2023-0191 Control: reassign -6 src:nvidia-graphics-drivers-tesla-460 460.32.03-1 Control: retitle -6 nvidia-graphics-drivers-tesla-460: CVE-2023-0184, CVE-2023-0189, CVE-2023-0180, CVE-2023-0185, CVE-2023-0187, CVE-2023-0198, CVE-2023-0199, CVE-2023-0188, CVE-2023-0190, CVE-2023-0194, CVE-2023-0195, CVE-2023-0191 Control: tag -6 + wontfix Control: close -6 460.106.00-3 Control: reassign -7 src:nvidia-graphics-drivers-tesla-470 470.57.02-1 Control: retitle -7 nvidia-graphics-drivers-tesla-470: CVE-2023-0184, CVE-2023-0189, CVE-2023-0180, CVE-2023-0185, CVE-2023-0187, CVE-2023-0198, CVE-2023-0199, CVE-2023-0188, CVE-2023-0190, CVE-2023-0194, CVE-2023-0195, CVE-2023-0191 Control: reassign -8 src:nvidia-graphics-drivers-tesla-510 510.47.03-1 Control: retitle -8 nvidia-graphics-drivers-tesla-510: CVE-2023-0184, CVE-2023-0189, CVE-2023-0180, CVE-2023-0183, CVE-2023-0185, CVE-2023-0187, CVE-2023-0198, CVE-2023-0199, CVE-2023-0188, CVE-2023-0190, CVE-2023-0194, CVE-2023-0195, CVE-2023-0191 Control: tag -8 + wontfix Control: close -8 510.85.02-2 Control: reassign -9 src:nvidia-graphics-drivers-tesla 510.85.02-1 Control: retitle -9 nvidia-graphics-drivers-tesla: CVE-2023-0184, CVE-2023-0189, CVE-2023-0180, CVE-2023-0183, CVE-2023-0185, CVE-2023-0187, CVE-2023-0198, CVE-2023-0199, CVE-2023-0188, CVE-2023-0190, CVE-2023-0194, CVE-2023-0195, CVE-2023-0191 Control: found -9 515.48.07-1 Control: found -9 525.60.13-1 Control: reassign -10 src:nvidia-open-gpu-kernel-modules 515.43.04-1 Control: retitle -10 nvidia-open-gpu-kernel-modules: CVE-2023-0184, CVE-2023-0189, CVE-2023-0180, CVE-2023-0183, CVE-2023-0185, CVE-2023-0187, CVE-2023-0198, CVE-2023-0199, CVE-2023-0188, CVE-2023-0190, CVE-2023-0194, CVE-2023-0195, CVE-2023-0191 Control: found -10 520.56.06-1 Control: found -10 525.85.12-1 Control: found -10 530.30.02-1 Control: found -1 340.24-1 Control: found -1 343.22-1 Control: found -1 396.18-1 Control: found -1 430.14-1 Control: found -1 455.23.04-1 Control: found -1 465.24.02-1 Control: found -1 495.44-1 Control: found -1 515.48.07-1 Control: found -1 520.56.06-1 Control: found -1 525.53-1 Control: found -1 530.30.02-1 Control: fixed -1 530.41.03-1 https://nvidia.custhelp.com/app/answers/detail/a_id/5452 CVE-2023-0189 NVIDIA GPU Display Driver for Linux contains a vulnerability in the kernel mode layer handler, which may lead to code execution, denial of service, escalation of privileges, information disclosure, and data tampering. CVE-2023-0184 NVIDIA GPU Display Driver for Windows and Linux contains a vulnerability in
Processed: jekyll: autopkgtest fails on arm64 (in UTC+8 timezone): a document with a date with timezone should have the expected date
Processing control commands: > tags -1 bookworm-ignore Bug #1034450 [src:jekyll] jekyll: autopkgtest fails on arm64 (in UTC+8 timezone): a document with a date with timezone should have the expected date Added tag(s) bookworm-ignore. -- 1034450: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034450 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1034450: jekyll: autopkgtest fails on arm64 (in UTC+8 timezone): a document with a date with timezone should have the expected date
Source: jekyll Version: 4.3.1+dfsg-1 Severity: serious Control: tags -1 bookworm-ignore User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), Your package has an autopkgtest, great. However, it fails on arm64 since mid 2022. I noticed that the two tests that failed are about timezones and our arm64 hosts are located in a UTC+8 timezone. Until 2023-04-13 the hosts were also configured in their local timezone, but changing that to UTC didn't solve the problem. Can you please investigate the situation and fix it? I copied some of the output at the bottom of this report. The release team has announced [1] that failing autopkgtest on amd64 and arm64 are considered RC in testing. [Release Team member hat on] Because we're currently in the hard freeze for bookworm, I have marked this bug as bookworm-ignore. Targeted fixes are still welcome. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html https://ci.debian.net/data/autopkgtest/testing/arm64/j/jekyll/32926900/log.gz Failure: Minitest::Result#test_: a document with a date with timezone should have the expected date. [/tmp/autopkgtest-lxc.a_d0zzn9/downtmp/build.XLd/src/test/test_document.rb:627] Minitest::Assertion: Expected: "2015/09/30" Actual: "2015/10/01" Failure: Minitest::Result#test_: a document with a date with timezone should return the expected date via Liquid. [/tmp/autopkgtest-lxc.a_d0zzn9/downtmp/build.XLd/src/test/test_document.rb:631] Minitest::Assertion: Expected: "2015/09/30" Actual: "2015/10/01" OpenPGP_signature Description: OpenPGP digital signature
Bug#1033011: marked as done (octave-dev: missing Breaks+Replaces against older liboctave-dev)
Your message dated Sat, 15 Apr 2023 18:35:23 + with message-id and subject line Bug#1033011: fixed in octave 8.2.0-1 has caused the Debian Bug report #1033011, regarding octave-dev: missing Breaks+Replaces against older liboctave-dev to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1033011: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033011 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: octave-dev Version: 6.3.0-1 Severity: serious liboctave-dev has been renamed octave-dev, but the latter misses a Breaks+Replaces against the former. As a consequence, upgrades from Buster to Bookworm with liboctave-dev installed can fail, because the new octave-dev wants to overwrite files which are provided by the old liboctave-dev. -- ⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot ⣾⠁⢠⠒⠀⣿⡁ Debian Developer ⢿⡄⠘⠷⠚⠋⠀ https://sebastien.villemot.name ⠈⠳⣄ https://www.debian.org --- End Message --- --- Begin Message --- Source: octave Source-Version: 8.2.0-1 Done: Sébastien Villemot We believe that the bug you reported is fixed in the latest version of octave, 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. Sébastien Villemot (supplier of updated octave 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: Sat, 15 Apr 2023 20:10:08 +0200 Source: octave Architecture: source Version: 8.2.0-1 Distribution: experimental Urgency: medium Maintainer: Debian Octave Group Changed-By: Sébastien Villemot Closes: 1033011 Changes: octave (8.2.0-1) experimental; urgency=medium . * New upstream version 8.2.0 * d/control: add missing Breaks+Replaces of octave-dev on old liboctave-dev (Closes: #1033011) Checksums-Sha1: b86faf08fed9664965d742e4563080c09ffdf779 3315 octave_8.2.0-1.dsc 8aea594c0878e5e249a31c4e7ac15745702a65b9 26970452 octave_8.2.0.orig.tar.xz 36686858eb6b0ad4d46a2bf89bca195d6652b577 195 octave_8.2.0.orig.tar.xz.asc 84064a04c8c57532c42f8f17d83a47032c499dbf 62136 octave_8.2.0-1.debian.tar.xz c9e6e9ca32b234a219fc73efc3b23353a72cfa95 26909 octave_8.2.0-1_amd64.buildinfo Checksums-Sha256: 442137dc016f4214b4c8d4f16e2fd2da61edcd09e0bae9059838a33b394b3c86 3315 octave_8.2.0-1.dsc b7b9d6e5004ff039450cfedd2a59ddbe2a3c22296df927a8af994182eb2670de 26970452 octave_8.2.0.orig.tar.xz 126011693c51c7fcdfbe4fbb5ec6cb3cd1f8dce6df946dd85ce821b255cf69c9 195 octave_8.2.0.orig.tar.xz.asc e27ff172f0b7db5e0c8311722072e141f67239d33674588517933b8fd2d54af0 62136 octave_8.2.0-1.debian.tar.xz 9bb95f58c0d78ade04d7a0ab8bed6d352df7bcd786563683ae0859005e49320f 26909 octave_8.2.0-1_amd64.buildinfo Files: 9c12ca66c76421b9d120726e2147aa4b 3315 math optional octave_8.2.0-1.dsc 32ef01053c0b85eae3fd01dd615cc761 26970452 math optional octave_8.2.0.orig.tar.xz f1b5ce62cf0ba01efc246fcc511ccce1 195 math optional octave_8.2.0.orig.tar.xz.asc d8eb4b57deaabb07578170ce1820031f 62136 math optional octave_8.2.0-1.debian.tar.xz 26972b107808eb6e23930e581f46034f 26909 math optional octave_8.2.0-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEU5UdlScuDFuCvoxKLOzpNQ7OvkoFAmQ663UACgkQLOzpNQ7O vkpQQw/+JkVTjSfKSFIUE3YX1chMeyzfX5Zu5/c+HG3TizEpEgklx83Ctz93kFIp ys+Lm4osSzew84m5pzCs37cR9scOYCjmJtA1DEUmDjxFsYjjVywo/pQ/QBrDUrG4 u+KuN75tmSUcCb4lADJlLwFvbplGmbcuces8fe5yYUhIjQs4SzWZ4kE7rBnv+lNM roXEE4k+g5Kw7rwyUjqaWtFb56NQdEAA/GbYPyALT7QVxTY446eTJvjPfzid3StN JIKFR8PpLl2QNnT99j+MjUTO5d1pa14PGIbna6D6Ta6cLMPI/Er4RVjpfXSSegCz 1M619zq8RNxltH1rCAnFyMSkwWfFCzS77lsbo41Z6Yzbkw26Rg8i+ltPxLp6rsIb UiiGUC4YC5gkOe3S5XYrcJh3gXW7T+wUMzJc88R7Ulydd17DyNqxVzqkdt4W4EMn 9LOKhul4ZVB5tbRfXin3XBXihSmLdfVAOfMIrYsLQIxFSMva/VxCzeevBs7z9tgE Zcry1vTWYkG3KwtLOMsS+Cv/LSfmzoiqvufGIgV4M3bRQzHqD/UgDQEtMyn7aIRq xaz8RdUTKzJPFW8L5U2fsTcD65vthYcK+dXOYRq+UeVO5zaRJvX4sq8xBn4qGBv6 DTgci2rstPaGp1nig0Iv1RRIsQELtinc5xZ2UnEj2qN8sLBBabo= =Q4Zx -END PGP SIGNATURE End Message ---
Bug#1034222: marked as done (tirex: dh_installsystemd doesn't handle files in /usr/lib/systemd/system)
Your message dated Sat, 15 Apr 2023 16:34:30 + with message-id and subject line Bug#1034222: fixed in tirex 0.7.0-3 has caused the Debian Bug report #1034222, regarding tirex: 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.) -- 1034222: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034222 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: tirex Version: 0.7.0-2 Severity: serious Tags: sid bookworm User: debhel...@packages.debian.org Usertags: systemd-files-in-usr-bookworm Dear Maintainer, It seems that your package tirex 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: tirex Source-Version: 0.7.0-3 Done: Bas Couwenberg We believe that the bug you reported is fixed in the latest version of tirex, 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. Bas Couwenberg (supplier of updated tirex package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 11 Apr 2023 10:20:03 +0200 Source: tirex Architecture: source Version: 0.7.0-3 Distribution: unstable Urgency: medium Maintainer: Debian GIS Project Changed-By: Bas Couwenberg Closes: 1034222 Changes: tirex (0.7.0-3) unstable; urgency=medium . * Team upload. * Add Rules-Requires-Root to control file. * Update lintian overrides. * Bump Standards-Version to 4.6.2, no changes. * Move systemd services to /lib/systemd. (closes: #1034222) Checksums-Sha1: 32545e9f982a28ca58d66db633cd118c3dc1dae5 2049 tirex_0.7.0-3.dsc 9b0b55444cc72d75122d3f56bf9e6488e9f642fd 10224 tirex_0.7.0-3.debian.tar.xz 4ef0786c6e8da4301e632ac6229ed75834ff04c4 16258 tirex_0.7.0-3_amd64.buildinfo Checksums-Sha256: 86b9c089fcf002a29de84813fa24104848962af5f2b6a4d60e331108e8a8bf97 2049 tirex_0.7.0-3.dsc c3b73d8a0e2337a0c58e898a99a3f66f7c8d45789852a975f66436385775605b 10224 tirex_0.7.0-3.debian.tar.xz cefa444c7e0726f0aef4b3f41c1219a5f8737be4205d8ba9db740978c86b487e 16258 tirex_0.7.0-3_amd64.buildinfo Files: 087e59f6704b50a2a7606b8c2259c2af 2049 science optional tirex_0.7.0-3.dsc c1e2ad7aad5193c73db2d0eb57561017 10224 science optional tirex_0.7.0-3.debian.tar.xz 977b169b74310045d5d6b0b5c87af7de 16258 science optional tirex_0.7.0-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEgYLeQXBWQI1hRlDRZ1DxCuiNSvEFAmQ6zgEACgkQZ1DxCuiN SvEkDw/+JTxVxO3Bza3UOwxxZK5eB1BCEQiXR292kc1zPz1tZpumDaCi9WgnjPus zEzPWowwmgwl1SBqPOU8hZtvO8VLvFLvdSkWp6U5wHUjIvMwB0aWhPEfcA809BNe eA5p7VBhVAqwfjLe0pVP+DKUDBteG4Mjeu+nlCJxU+xrPX7OrUnM5YVASD1oYngO gDTysIXDwKj4245SIlXmDKAycLk/gsJTaMJc2KXy5Wnoq+sXo+LXx7yilfvxE/IU NqBxhfB8856+3u1OjbigV0yFZJF5Z3zM2/fuj+DdLa2XsRiFVGj0FZLh/aE+1CRC XEJYeGpxaVOV+QhxOesBDbNo4bAvH496ZhocSDWn8bQ/l+7UjaVBGaPt4CXzbDw3 iDxQkA6zHp+7C3PxCI1zssur9IFmxsbY3uU9G8kPamusfsugwlK9h8mLjqcFfeXW iWt+6TKnnSwdLITbnXpRENlc/MvUUlWWVHckjZCYwwxiYxBi2hGCta0/ERd+yUNy erHomrRLpMkALTH+vp47dQghKt0iFlVBUMbyC7wX55/+pPFdBsYqEgx4UKT6nHDf
Bug#1033910: marked as done (ruby-kakasi-ffi: autopkgtest regression: Could not find 'kakasi' (>= 0))
Your message dated Sat, 15 Apr 2023 14:36:05 + with message-id and subject line Bug#1033910: fixed in ruby-kakasi-ffi 1.0.2-4 has caused the Debian Bug report #1033910, regarding ruby-kakasi-ffi: autopkgtest regression: Could not find 'kakasi' (>= 0) 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.) -- 1033910: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033910 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-kakasi-ffi Version: 1.0.2-3 Severity: serious Control: tags -1 bookworm-ignore sid bookworm trixie User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), Your package has an autopkgtest, great. However, it fails since March 2023. Can you please investigate the situation and fix it? I copied some of the output at the bottom of this report. The release team has announced [1] that failing autopkgtest on amd64 and arm64 are considered RC in testing. [Release Team member hat on] Because we're currently in the hard freeze for bookworm, I have marked this bug as bookworm-ignore. Targeted fixes are still welcome. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html https://ci.debian.net/data/autopkgtest/testing/amd64/r/ruby-kakasi-ffi/32098115/log.gz GEM_PATH= ruby3.1 -e gem\ \"kakasi\" /usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:311:in `to_specs': Could not find 'kakasi' (>= 0) among 91 total gem(s) (Gem::MissingSpecError) Checked in 'GEM_PATH=/home/debci/.local/share/gem/ruby/3.1.0:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0' , execute `gem env` for more information from /usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:323:in `to_spec' from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:62:in `gem' from -e:1:in `' OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: ruby-kakasi-ffi Source-Version: 1.0.2-4 Done: Nilesh Patra We believe that the bug you reported is fixed in the latest version of ruby-kakasi-ffi, 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. Nilesh Patra (supplier of updated ruby-kakasi-ffi 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: Sat, 15 Apr 2023 19:29:50 +0530 Source: ruby-kakasi-ffi Architecture: source Version: 1.0.2-4 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Team Changed-By: Nilesh Patra Closes: 1033910 Changes: ruby-kakasi-ffi (1.0.2-4) unstable; urgency=medium . * Team Upload. - Re-build against new ruby and get autopkgtests passing (Closes: #1033910) [ Debian Janitor ] * Apply multi-arch hints. + ruby-kakasi-ffi: Add Multi-Arch: same. . [ Nilesh Patra ] * Bump Standards-Version to 4.6.2 (no changes needed) Checksums-Sha1: 8be6204676ffb0e85c81689db9fe38d4c34d5c42 1470 ruby-kakasi-ffi_1.0.2-4.dsc c21dc8204157aa935100fa619488f5ecfc509e2b 3304 ruby-kakasi-ffi_1.0.2-4.debian.tar.xz eb21cccfa4460a1777fa5046547f069b4af41b78 8562 ruby-kakasi-ffi_1.0.2-4_amd64.buildinfo Checksums-Sha256: eff045af5eb8a87369ab1aec79a86e04cde36b631ccbf3017c6ef94941b334e4 1470 ruby-kakasi-ffi_1.0.2-4.dsc aea34cbfb386d93e854972f173ea683d0d0dcc73e27ee59ec625459c38d26476 3304 ruby-kakasi-ffi_1.0.2-4.debian.tar.xz d8f175845625f436b5908e65987ee4cebe1b227a98f1ffbcbdcb2f8e584714aa 8562 ruby-kakasi-ffi_1.0.2-4_amd64.buildinfo Files: 1731d0150d5399ddf8382ebdf95b014f 1470 ruby optional ruby-kakasi-ffi_1.0.2-4.dsc 8064f7d59d98447b0037da60f2882c66 3304 ruby optional ruby-kakasi-ffi_1.0.2-4.debian.tar.xz 1c34496ac199ff2ba14037dd94c64fe5 8562 ruby optional ruby-kakasi-ffi_1.0.2-4_amd64.buildinfo -BEGIN PGP SIGNATURE- iHUEARYIAB0WIQSglbZu4JAkvua
Bug#1034443: python3-brial: uninstallable on arcitectures where sagemath is unavailable, breaks building of singular
Package: python3-brial Version: 1.2.11-2 Severity: serious X-debbugs-cc: singu...@packages.debian.org python3-brial recently added a dependency on python3-sage, however python3-sage is only available on amd64, arm64, i386 and riscv64. This also means that the build-depends of singular on those architectures are unsatisfied. Strangely, when I look at the singular build log the only mentions of brial I see are in the Debian packaging steps, I don't see any mentions of it from the upstream build system. Grepping for brial in the polybori source doesn't reveal anything outside the debian dir either. I maintain a downstream distribution and, after removing the build-dependency, was able to build singular there without having any brial related packages installed. So assuming the dependency on python3-sage is real and unavoidable what I think needs to happen to get things back in a consistent state is. * The architecture list of python3-brial needs to be limited to architectures where python3-sage is available. * The build-dependency of singular on python3-brial needs to be either removed or limited to architectures where python3-sage is available * Removal of the old python3-brial packages needs to be requested.
Bug#1034350: marked as done (gnutls28: autopkgtest regression everywhere except amd64: src/nonexist-builddir/gnutls_ktls: not found)
Your message dated Sat, 15 Apr 2023 12:34:31 + with message-id and subject line Bug#1034350: fixed in gnutls28 3.7.9-2 has caused the Debian Bug report #1034350, regarding gnutls28: autopkgtest regression everywhere except amd64: src/nonexist-builddir/gnutls_ktls: not found 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.) -- 1034350: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034350 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gnutls28 Version: 3.7.9-1 Severity: serious Control: tags -1 bookworm-ignore User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), Your package has an autopkgtest, great. However, it fails everywhere but on amd64. If I understand correctly, the 32 bits architecture failures are due to datefudge/faketime (bug 1031553) and started in September 2022. The 64 bits architectures started to fail more recently in March 2023. Because some hosts on ci.debian.net have been upgraded to bookworm recently, I was fearing/suspecting it might be kernel related, but running the test on an amd64/bookworm kernel passes. Can you please investigate the situation and fix it? I copied some of the output at the bottom of this report. The release team has announced [1] that failing autopkgtest on amd64 and arm64 are considered RC in testing. [Release Team member hat on] Because we're currently in the hard freeze for bookworm, I have marked this bug as bookworm-ignore. Targeted fixes are still welcome. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html https://ci.debian.net/data/autopkgtest/testing/arm64/g/gnutls28/32726537/log.gz https://ci.debian.net/data/autopkgtest/testing/arm64/g/gnutls28/32726537/log.gz running [83]../../tests/ktls.sh ... /proc/modules:tls 114688 0 - Live 0x ../../tests/ktls.sh: 40: /tmp/autopkgtest-lxc.p44qznnk/downtmp/build.Wzp/src/nonexist-builddir/gnutls_ktls: not found FAIL [83]../../tests/ktls.sh OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: gnutls28 Source-Version: 3.7.9-2 Done: Andreas Metzler We believe that the bug you reported is fixed in the latest version of gnutls28, 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. Andreas Metzler (supplier of updated gnutls28 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: Sat, 15 Apr 2023 13:45:57 +0200 Source: gnutls28 Architecture: source Version: 3.7.9-2 Distribution: unstable Urgency: medium Maintainer: Debian GnuTLS Maintainers Changed-By: Andreas Metzler Closes: 1034350 Changes: gnutls28 (3.7.9-2) unstable; urgency=medium . * CI: Do not try to run tests/ktls.sh, it uses a helper binary. (Plus gnutls is not built with ktls support on Debian yet.) Closes: #1034350 Checksums-Sha1: d6dc5e7492511856c7e61c4f136044179597ea4b 3386 gnutls28_3.7.9-2.dsc 080e4755c76e7d8552154bc3e07f4d0c7b2aac35 85892 gnutls28_3.7.9-2.debian.tar.xz Checksums-Sha256: 65a8fe5a079115b9f2381d3071cbe4f5f00c2dc2a8ef04aab47523ae66f636e4 3386 gnutls28_3.7.9-2.dsc 1f5f0a73e1f0b25e481785398f7e213237810841ee3860475acbbcc9b0dd16bf 85892 gnutls28_3.7.9-2.debian.tar.xz Files: de6d31f658f4e7aae09dc4fe1fdb4ef8 3386 libs optional gnutls28_3.7.9-2.dsc ed0c5ed5a018dd70510798ecafd07d87 85892 libs optional gnutls28_3.7.9-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE0uCSA5741Jbt9PpepU8BhUOCFIQFAmQ6lSwACgkQpU8BhUOC FIQZww//ZzdHuavA4VIkS2rd/T2vg+IHBYzp1ciyg4yAVuly+xHYpmjXZ0vYOIEm OMEaAUA1zW8LC7uaMO04gLGuEtZhH3OyPvvTsxIWtkf/w6abUG6pQpUdk4GQho0g C2TbvWxIxCMNTfRqy6M2AgCmb5aY6XhBXbmrAAw8sxwT8SDiZvyXNoLBhrFJM7rL gKlelfPBUm4qZKCOrNfJRztj97Rr/ckJhaCCw7zMW8PUFUFP2clknYq+PiMKgPIK KkSUgjVLRLAdxK5oyNKtQ+ealU3WLT2whsiAzzgyXIZchC4B9CEzyPpIZNoYnj81 HGjGO2pf2ildJISnLjNJAFeBe8Of1I7pj29rZWnKkJBIHFO0U8yR/+ox/OFwrjfk nWrhSF/Q8fM86FUDcUIE9Sf8a9rEphz7M0JFs7/2f7uQIwlei0lE6X
Processed: tagging 999526, bug 999526 is forwarded to https://github.com/mdp-toolkit/mdp-toolkit/pull/94
Processing commands for cont...@bugs.debian.org:
> tags 999526 + upstream fixed-upstream patch
Bug #999526 [python3-mdp] mdp: FTBFS with numpy 1.21 (in experimental):
dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9
returned exit code 13
Bug #1002393 [python3-mdp] mdp: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.10 3.9" returned exit code 13
Added tag(s) upstream, patch, and fixed-upstream.
Added tag(s) upstream, patch, and fixed-upstream.
> forwarded 999526 https://github.com/mdp-toolkit/mdp-toolkit/pull/94
Bug #999526 [python3-mdp] mdp: FTBFS with numpy 1.21 (in experimental):
dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9
returned exit code 13
Bug #1002393 [python3-mdp] mdp: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.10 3.9" returned exit code 13
Set Bug forwarded-to-address to
'https://github.com/mdp-toolkit/mdp-toolkit/pull/94'.
Set Bug forwarded-to-address to
'https://github.com/mdp-toolkit/mdp-toolkit/pull/94'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1002393: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002393
999526: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999526
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1034209: pcscd: dh_installsystemd doesn't handle files in /usr/lib/systemd/system
Le 11/04/2023 à 09:37, bi...@debian.org a écrit : 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 I asked release.debian.org for an unblock in #1034434 Bye -- Dr. Ludovic Rousseau
Bug#1034225: marked as done (nvme-stas: dh_installsystemd doesn't handle files in /usr/lib/systemd/system)
Your message dated Sat, 15 Apr 2023 09:05:26 + with message-id and subject line Bug#1034225: fixed in nvme-stas 2.2.1-2 has caused the Debian Bug report #1034225, regarding nvme-stas: 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.) -- 1034225: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034225 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: nvme-staspass-extension-tomb Version: 1.3-2 Severity: serious Tags: sid bookworm User: debhel...@packages.debian.org Usertags: systemd-files-in-usr-bookworm Dear Maintainer, It seems that your package nvme-staspass-extension-tomb 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: nvme-stas Source-Version: 2.2.1-2 Done: Daniel Baumann We believe that the bug you reported is fixed in the latest version of nvme-stas, 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. Daniel Baumann (supplier of updated nvme-stas 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: Sat, 15 Apr 2023 10:30:08 +0200 Source: nvme-stas Architecture: source Version: 2.2.1-2 Distribution: sid Urgency: medium Maintainer: Daniel Baumann Changed-By: Daniel Baumann Closes: 1034225 Changes: nvme-stas (2.2.1-2) sid; urgency=medium . * Uploading to sid. * Trimming copyright file. * Updating upstream links in copyright. * Wrap and sorting debian directory. * Moving systemd unit directory until debhelper supports /usr/lib/systemd/system (Closes: #1034225). Checksums-Sha1: 8080141be5d129c2035f95ea73b76aa56e56a2e9 2194 nvme-stas_2.2.1-2.dsc 5543b77c732887a89643e7167e69aaf0f1d0c21d 2348 nvme-stas_2.2.1-2.debian.tar.xz f419459116d28f124d80a7b78371ed0cd528abed 8065 nvme-stas_2.2.1-2_amd64.buildinfo Checksums-Sha256: daccf01a9baafe5c6394b3cda853cedf7ae0bfb9229bfee6233af9f9c00a86a3 2194 nvme-stas_2.2.1-2.dsc ec37f04397aca31d02da40ea6159a38afb889672281b84d92a5aff88a89f861f 2348 nvme-stas_2.2.1-2.debian.tar.xz 32c27967a1c540406e08a57874ff045d7e9479651a9f28919f488d91f7694249 8065 nvme-stas_2.2.1-2_amd64.buildinfo Files: 03789fee069c8e6dc2ecf4704b44d4d8 2194 net optional nvme-stas_2.2.1-2.dsc ef9faf171015689a352d9033f9c3308b 2348 net optional nvme-stas_2.2.1-2.debian.tar.xz 2e8653272dc2d69e1bcd162f078b71a9 8065 net optional nvme-stas_2.2.1-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEgTbtJcfWfpLHSkKSVc8b+YaruccFAmQ6ZJ4ACgkQVc8b+Yar ucfjehAA2s7XncezM7YGH02qdKbJfHOgnHMjxW4EjlSPqzSyHdUL06ti6daKfDjI /rGgSlkj7dEBmA1yLsm617eI7IWxl/Vsry2mLiaN8eTlTLSiKF706tmz+M7iGJ3D HuGq2CAy4f/vO/MfN0kDROzE07MCe86ZZLSeKcbN+tNfb4Aw5ug9/pgKnHHYehim xXkBfm9W6YGVBz3LJJ+K7/LSZi0XfnO1bwUUj9Qk+Q6L0XX6B0JH/wKYUc8l7LbJ Exz6QB0Ip2lubwGcKnT6q5peUeC6mNXVRUBEGGIa6K9+8UGWo71vppu+pAC1v1Js eRrrkubKDBhrbFPibwu0x3eQ+iMhZyY0G8eqZbcESZ/A3g5bJy0LF4nToLxrYvW6 hWFA7e5cXw07FuVVwrlZPFTMx265/ho855ccCsXsl3ltGWmrVI91mnP7vdZew0d3 JU+xnQdQ4d
Bug#1033774: marked as done (nvidia-graphics-drivers: CVE-2023-0184, CVE-2023-0189, CVE-2023-0180, CVE-2023-0183, CVE-2023-0185, CVE-2023-0187, CVE-2023-0198, CVE-2023-0199, CVE-2023-0188, CVE-2023-01
Your message dated Sat, 15 Apr 2023 09:04:49 + with message-id and subject line Bug#1033774: fixed in nvidia-graphics-drivers 525.105.17-1 has caused the Debian Bug report #1033774, regarding nvidia-graphics-drivers: CVE-2023-0184, CVE-2023-0189, CVE-2023-0180, CVE-2023-0183, CVE-2023-0185, CVE-2023-0187, CVE-2023-0198, CVE-2023-0199, CVE-2023-0188, CVE-2023-0190, CVE-2023-0194, CVE-2023-0195, CVE-2023-0191 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.) -- 1033774: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033774 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: nvidia-graphics-drivers Severity: serious Tags: security upstream X-Debbugs-Cc: Debian Security Team Control: clone -1 -2 -3 -4 -5 -6 -7 -8 -9 -10 Control: reassign -2 src:nvidia-graphics-drivers-legacy-340xx 340.76-6 Control: retitle -2 nvidia-graphics-drivers-legacy-340xx: CVE-2023-0184, CVE-2023-0189, CVE-2023-0180, CVE-2023-0185, CVE-2023-0198, CVE-2023-0199, CVE-2023-0188, CVE-2023-0190, CVE-2023-0194, CVE-2023-0195, CVE-2023-0191 Control: tag -2 + wontfix Control: reassign -3 src:nvidia-graphics-drivers-legacy-390xx 390.48-4 Control: retitle -3 nvidia-graphics-drivers-legacy-390xx: CVE-2023-0184, CVE-2023-0189, CVE-2023-0180, CVE-2023-0185, CVE-2023-0198, CVE-2023-0199, CVE-2023-0188, CVE-2023-0190, CVE-2023-0194, CVE-2023-0195, CVE-2023-0191 Control: tag -3 + wontfix Control: reassign -4 src:nvidia-graphics-drivers-tesla-418 418.87.01-1 Control: retitle -4 nvidia-graphics-drivers-tesla-418: CVE-2023-0184, CVE-2023-0189, CVE-2023-0180, CVE-2023-0185, CVE-2023-0198, CVE-2023-0199, CVE-2023-0188, CVE-2023-0190, CVE-2023-0194, CVE-2023-0195, CVE-2023-0191 Control: tag -4 + wontfix Control: reassign -5 src:nvidia-graphics-drivers-tesla-450 450.51.05-1 Control: retitle -5 nvidia-graphics-drivers-tesla-450: CVE-2023-0184, CVE-2023-0189, CVE-2023-0180, CVE-2023-0185, CVE-2023-0198, CVE-2023-0199, CVE-2023-0188, CVE-2023-0190, CVE-2023-0194, CVE-2023-0195, CVE-2023-0191 Control: reassign -6 src:nvidia-graphics-drivers-tesla-460 460.32.03-1 Control: retitle -6 nvidia-graphics-drivers-tesla-460: CVE-2023-0184, CVE-2023-0189, CVE-2023-0180, CVE-2023-0185, CVE-2023-0187, CVE-2023-0198, CVE-2023-0199, CVE-2023-0188, CVE-2023-0190, CVE-2023-0194, CVE-2023-0195, CVE-2023-0191 Control: tag -6 + wontfix Control: close -6 460.106.00-3 Control: reassign -7 src:nvidia-graphics-drivers-tesla-470 470.57.02-1 Control: retitle -7 nvidia-graphics-drivers-tesla-470: CVE-2023-0184, CVE-2023-0189, CVE-2023-0180, CVE-2023-0185, CVE-2023-0187, CVE-2023-0198, CVE-2023-0199, CVE-2023-0188, CVE-2023-0190, CVE-2023-0194, CVE-2023-0195, CVE-2023-0191 Control: reassign -8 src:nvidia-graphics-drivers-tesla-510 510.47.03-1 Control: retitle -8 nvidia-graphics-drivers-tesla-510: CVE-2023-0184, CVE-2023-0189, CVE-2023-0180, CVE-2023-0183, CVE-2023-0185, CVE-2023-0187, CVE-2023-0198, CVE-2023-0199, CVE-2023-0188, CVE-2023-0190, CVE-2023-0194, CVE-2023-0195, CVE-2023-0191 Control: tag -8 + wontfix Control: close -8 510.85.02-2 Control: reassign -9 src:nvidia-graphics-drivers-tesla 510.85.02-1 Control: retitle -9 nvidia-graphics-drivers-tesla: CVE-2023-0184, CVE-2023-0189, CVE-2023-0180, CVE-2023-0183, CVE-2023-0185, CVE-2023-0187, CVE-2023-0198, CVE-2023-0199, CVE-2023-0188, CVE-2023-0190, CVE-2023-0194, CVE-2023-0195, CVE-2023-0191 Control: found -9 515.48.07-1 Control: found -9 525.60.13-1 Control: reassign -10 src:nvidia-open-gpu-kernel-modules 515.43.04-1 Control: retitle -10 nvidia-open-gpu-kernel-modules: CVE-2023-0184, CVE-2023-0189, CVE-2023-0180, CVE-2023-0183, CVE-2023-0185, CVE-2023-0187, CVE-2023-0198, CVE-2023-0199, CVE-2023-0188, CVE-2023-0190, CVE-2023-0194, CVE-2023-0195, CVE-2023-0191 Control: found -10 520.56.06-1 Control: found -10 525.85.12-1 Control: found -10 530.30.02-1 Control: found -1 340.24-1 Control: found -1 343.22-1 Control: found -1 396.18-1 Control: found -1 430.14-1 Control: found -1 455.23.04-1 Control: found -1 465.24.02-1 Control: found -1 495.44-1 Control: found -1 515.48.07-1 Control: found -1 520.56.06-1 Control: found -1 525.53-1 Control: found -1 530.30.02-1 Control: fixed -1 530.41.03-1 https://nvidia.custhelp.com/app/answers/detail/a_id/5452 CVE-2023-0189 NVIDIA GPU Display Driver for Linux contains a vulnerability in the kernel mode layer handler, which may lead to code execution, denial of service, escalation of privileges, information disclosure, and data tampering. CVE-2023-0184 NVIDIA GPU Display Driver for Windows and Linux contains a vulnerability in the kernel mod
Processed: Re: Bug#1034303: nvidia-cuda-toolkit breaks nvidia-cuda-samples autopkgtest on amd64: bad exit status: 2
Processing control commands: > reassign -1 dkms 3.0.10-6 Bug #1034303 [src:nvidia-cuda-toolkit, src:nvidia-cuda-samples] nvidia-cuda-toolkit breaks nvidia-cuda-samples autopkgtest on amd64: bad exit status: 2 Bug reassigned from package 'src:nvidia-cuda-toolkit, src:nvidia-cuda-samples' to 'dkms'. No longer marked as found in versions nvidia-cuda-samples/11.8~dfsg-2 and nvidia-cuda-toolkit/11.8.0-3. Ignoring request to alter fixed versions of bug #1034303 to the same values previously set Bug #1034303 [dkms] nvidia-cuda-toolkit breaks nvidia-cuda-samples autopkgtest on amd64: bad exit status: 2 Marked as found in versions dkms/3.0.10-6. > affects -1 + src:nvidia-cuda-toolkit src:nvidia-cuda-samples Bug #1034303 [dkms] nvidia-cuda-toolkit breaks nvidia-cuda-samples autopkgtest on amd64: bad exit status: 2 Added indication that 1034303 affects src:nvidia-cuda-toolkit and src:nvidia-cuda-samples > close -1 3.0.10-8 Bug #1034303 [dkms] nvidia-cuda-toolkit breaks nvidia-cuda-samples autopkgtest on amd64: bad exit status: 2 Marked as fixed in versions dkms/3.0.10-8. Bug #1034303 [dkms] nvidia-cuda-toolkit breaks nvidia-cuda-samples autopkgtest on amd64: bad exit status: 2 Marked Bug as done -- 1034303: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034303 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1034303: nvidia-cuda-toolkit breaks nvidia-cuda-samples autopkgtest on amd64: bad exit status: 2
Control: reassign -1 dkms 3.0.10-6 Control: affects -1 + src:nvidia-cuda-toolkit src:nvidia-cuda-samples Control: close -1 3.0.10-8 On 12/04/2023 21.58, Paul Gevers wrote: So, shouldn't it be reassigned to dkms, closed and annotated as Affecting nvidia-cuda-toolkit and nvidia-cuda-samples? Done. Andreas
Bug#1034232: marked as done (nvme-cli: dh_installsystemd doesn't handle files in /usr/lib/systemd/system)
Your message dated Sat, 15 Apr 2023 08:50:16 + with message-id and subject line Bug#1034232: fixed in nvme-cli 2.4+really2.3-3 has caused the Debian Bug report #1034232, regarding nvme-cli: 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.) -- 1034232: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034232 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: nvme-cli Version: 2.3-2 Severity: serious Tags: sid bookworm User: debhel...@packages.debian.org Usertags: systemd-files-in-usr-bookworm Dear Maintainer, It seems that your package nvme-cli 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: nvme-cli Source-Version: 2.4+really2.3-3 Done: Daniel Baumann We believe that the bug you reported is fixed in the latest version of nvme-cli, 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. Daniel Baumann (supplier of updated nvme-cli 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: Sat, 15 Apr 2023 10:18:22 +0200 Source: nvme-cli Architecture: source Version: 2.4+really2.3-3 Distribution: sid Urgency: medium Maintainer: Daniel Baumann Changed-By: Daniel Baumann Closes: 1034232 Changes: nvme-cli (2.4+really2.3-3) sid; urgency=medium . * Uploading to sid. * Overwriting systemd unit directory until debhelper supports /usr/lib/systemd/system (Closes: #1034232). Checksums-Sha1: aa8c2c6a16c47bf2eecf21686e81307d681fa59d 2209 nvme-cli_2.4+really2.3-3.dsc def24ff4ec3be5df360b0209aa1a4aa80712929a 5712 nvme-cli_2.4+really2.3-3.debian.tar.xz 56d6b30bebb67be15358e8105e3dda3c5b7a4eaa 8992 nvme-cli_2.4+really2.3-3_amd64.buildinfo Checksums-Sha256: 0b7de08b6d7e9f015735ca71b05d4443a2105bffd3ec7293ce0b4d70a6bcdc2f 2209 nvme-cli_2.4+really2.3-3.dsc 1522c3c979d4f4855409c355349478ca94f0416396b81f69050b314f33a95f9d 5712 nvme-cli_2.4+really2.3-3.debian.tar.xz 6bc4dce89385b83b857712ec10c30d946073624b9613cac1352731df68769aa6 8992 nvme-cli_2.4+really2.3-3_amd64.buildinfo Files: 26ba0cef3d41d3fe4b6d25fba9d90d48 2209 admin optional nvme-cli_2.4+really2.3-3.dsc 9ceea23c97926b826aa18b1e9e05dd33 5712 admin optional nvme-cli_2.4+really2.3-3.debian.tar.xz dae4a06efd3928a47defc653873f916b 8992 admin optional nvme-cli_2.4+really2.3-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEgTbtJcfWfpLHSkKSVc8b+YaruccFAmQ6X4QACgkQVc8b+Yar uceTgxAAwZRF26VAVQzhkAKDh8hiM1N4S9xFKvt9NCY6J5r9LsdCwa+mLv4d0BGY SWfsa2QxZ318OyaWjwo6AnSJgNydPdEh4i5sOZQl4rX3CdaZkmNv2GF3ntDHZP+E tU3JU/nfTk+y7Qz+Lh8Bb3wHNX871K42uPWAt3SkhI7wNxi63Z+5VuqiilJd7L+T 1XxaIsJwkSdYrNeM0b5FWq8HIFpTOE5rWHvUGGj+AulsrAA6eHmpOabQwG9MIJSR 3Ltc5wNVeqtpYec6J19nFK0MPr3qeMKLJ2INZxb/PanC0POcUWEAS66W9FQFfV2i p92S7RlWU9XXAGSWH35Xn3gFVJQU+hK/4GYKykDUtesZH3GlerqONfP1i0cenQO3 zJI4WfIzExR4/Ky8hehZmZTyH77cGiqxilQclF5TH+8VLJSGlOCbS6em/8a32bMq cviR4jVjVE2q6YOJLDV3XSQZY7pQ970YCBqlthtP2t8/wQESX7CkG+c8A8P0QD
Bug#1034232: marked as done (nvme-cli: dh_installsystemd doesn't handle files in /usr/lib/systemd/system)
Your message dated Sat, 15 Apr 2023 08:34:13 + with message-id and subject line Bug#1034232: fixed in nvme-cli 2.4+really2.4-2 has caused the Debian Bug report #1034232, regarding nvme-cli: 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.) -- 1034232: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034232 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: nvme-cli Version: 2.3-2 Severity: serious Tags: sid bookworm User: debhel...@packages.debian.org Usertags: systemd-files-in-usr-bookworm Dear Maintainer, It seems that your package nvme-cli 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: nvme-cli Source-Version: 2.4+really2.4-2 Done: Daniel Baumann We believe that the bug you reported is fixed in the latest version of nvme-cli, 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. Daniel Baumann (supplier of updated nvme-cli 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: Sat, 15 Apr 2023 10:14:01 +0200 Source: nvme-cli Architecture: source Version: 2.4+really2.4-2 Distribution: experimental Urgency: medium Maintainer: Daniel Baumann Changed-By: Daniel Baumann Closes: 1034232 Changes: nvme-cli (2.4+really2.4-2) experimental; urgency=medium . * Uploading to experimental. * Overwriting systemd unit directory until debhelper supports /usr/lib/systemd/system (Closes: #1034232). Checksums-Sha1: 1ee948a143dfb6e37c1e7bda898f176b6ed61eb0 2226 nvme-cli_2.4+really2.4-2.dsc 1322b2b6d24453d73ba23b16323c649f19883e32 5604 nvme-cli_2.4+really2.4-2.debian.tar.xz 966d80f0460ae22d474b84b215087611854e48da 9022 nvme-cli_2.4+really2.4-2_amd64.buildinfo Checksums-Sha256: 7a4e251c8a32fe07f78724e8d933c29c8980569740394e33e08f532b084b1e15 2226 nvme-cli_2.4+really2.4-2.dsc 9878c6c6873662c7c286d6141b14887938db726232a1732eff4716e53d476085 5604 nvme-cli_2.4+really2.4-2.debian.tar.xz f597b4cb793977d3271cc10a45eb95670da56298cd0854ffddb6a3c212575b5a 9022 nvme-cli_2.4+really2.4-2_amd64.buildinfo Files: 50fa5ec0845cc1d61b5cfbad6ca27bb8 2226 admin optional nvme-cli_2.4+really2.4-2.dsc 0a50abd4540af9b82a7b4ddec12207aa 5604 admin optional nvme-cli_2.4+really2.4-2.debian.tar.xz 647e15c01f378d9fbf44af9b20c7c30d 9022 admin optional nvme-cli_2.4+really2.4-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEgTbtJcfWfpLHSkKSVc8b+YaruccFAmQ6XecACgkQVc8b+Yar ucf8gA/+JNy2uhui8LaM024alJFXnXZN8JZvlxW7KNMviERoOSg2qGNBdYuO0hhP EcDW24+ZIAY7Bdi4A9j82r1hHdQIZGgm4zwwyAzjnEt024cz2CSj3bqG/aaO0yGk k/nj/pRi6bGvfFM4MKHyDLGEYb5YxSJZEyulmlEiQXHV22YMpjXXX3295XPdKRuB EgSlkqXMa/5YL7tQP/aG6iSZ78yuxyzcXoSWTnyx5wuOAQFqZFjrbbW4n34vtLuI PwUJmv4sqhRdp7aU4yS2OZUxxRwxRn/mjLk6WF9QlYNkKqpq1uUU1YFEXJVfpvea Ti6HUHR3vsNnX99QIpqz5GZVGETiZgo3TAFyN0cPK4wD55yu3tHWDMaZO3hTUUqu HXbNdoV9fW50OWNCEpcdULs58M6fX/dzZm9Mo7x9fz6JXV3HQRavFLH+qJlhPVsy Abl9f3Q1cIGSnV7DENTNxJP3E5eyYAYcPGG
Bug#1034433: libsdl3-doc: missing Breaks+Replaces: libsdl1.2-dev (<< 3)
Package: libsdl3-doc Version: 3~git20230412+dfsg-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. This error may also be triggered by having a predecessor package from 'sid' installed while installing the package from 'experimental'. 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 .../libsdl3-doc_3~git20230412+dfsg-2_all.deb ... Unpacking libsdl3-doc (3~git20230412+dfsg-2) ... dpkg: error processing archive /var/cache/apt/archives/libsdl3-doc_3~git20230412+dfsg-2_all.deb (--unpack): trying to overwrite '/usr/share/man/man3/SDL_AddTimer.3.gz', which is also in package libsdl1.2-dev 1.2.15+dfsg2-8 Errors were encountered while processing: /var/cache/apt/archives/libsdl3-doc_3~git20230412+dfsg-2_all.deb cheers, Andreas libsdl1.2-dev=1.2.15+dfsg2-8_libsdl3-doc=3~git20230412+dfsg-2.log.gz Description: application/gzip
