Bug#1056587: texlive-latex-base: some math characters get replaced as of Debian's TeX Live 2023
Control: severity -1 wishlist Control: retitle -1 fmtutil should ignore TEXINPUTS set in root env On 28.11.2023 00:27, Debian Bug Tracking System wrote: Processing control commands: severiy -1 wishlist Unknown command or malformed arguments to command. title -1 fmtutil should ignore TEXINPUTS set in root env Unknown command or malformed arguments to command. -- sigfault OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1056556: Debugging techniques
Hi Dima, qick top post as I'm about to head out for work and I don't have access to my Debian mail there. I'll write you a more complete reply in ~12 hours when I'm back. Until then, the short answer is: you cannot re-run that apt-get in a shell because of the file descriptors that are passed, the pseudo terminal setup, proc handling, /dev/ptmx setup etc. This is also why it's not so easy (or even possible?) to copypaste the command and run it in a shell. A lot of things that mmdebstrap does are not possible (I think) in a shell because a careful dance of foreground and background processes talking with each other over pipes is constructed in many cases. It is possible to run the command you attempted to run from a shell but the command will be a bit different and thus it will not do exactly the same thing. What I would try in your situation is to not list the packages you want to install via --include but instead run mmdebstrap like this: mmdebstrap ... --variant=apt --chrooted-customize-hook=bash unstable /dev/null This will give you a shell inside a minimal chroot and from there you can mess around with apt pinning and run arbitrary apt-get install commands. Once you are happy, try to copy what you did in the shell interactively into --include options and --hooks. Hope that helps! cheers, josch Quoting Dima Kogan (2023-11-28 00:02:43) > Hi. I tried to do that apt pinning today, as you suggested. It still > fails in the same way as before: > > $ mmdebstrap > > I: installing remaining packages inside the chroot... > > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: >ros-noetic-cv-bridge : Depends: libopencv-dev but it is not installable >ros-noetic-grid-map-filters : Depends: libopencv-dev but it is not > installable >ros-noetic-image-geometry : Depends: libopencv-dev but it is not > installable > E: Unable to correct problems, you have held broken packages. > > The preferences file is there, but it isn't obviously doing anything. I > did some debugging just now to try to figure out why, and I'm reminded > of > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036929 > > Ideally the workflow I would like is > > 1. mmdebstrap does stuff. When it runs a command, it prints out EXACTLY >what it does, in a way that I can copy/paste it, and get the same >output > > 2. If it fails to do something, it drops me into a shell. Where I can paste >the command to reproduce the problem, and then poke around to fix it > > This probably isn't 100% possible here; but how would you debug this > otherwise? > > I'm attaching a patch that does some of (1.) above. This uses > String::ShellQuote to quote all the arguments so that the command string > can be pasted. I'm guessing you'd want to do some of that differently, > so it isn't super thorough. > > OK. Then I gave myself a shell in a spot that (I think?) sits right > before the failing "apt-get install": > > mmdebstrap \ > --essential-hook 'echo $$1; bash -i' \ > > > And pasting the command didn't work as I had hoped: > > root@fatty:# apt-get -o Dir::Bin::dpkg=env -o > DPkg::Options::=--unset=TMPDIR -o DPkg::Options::=dpkg -o > DPkg::Chroot-Directory=/tmp/mmdebstrap.i1wpW0WLMS --yes install > -oDpkg::Use-Pty=false tst-libopoencv > '?narrow(?or(?archive(^focal$),?codename(^focal$)),?architecture(arm64),?and(?or(?priority(required),?priority(important)),?not(?essential)))' > > E: Could not open lock file /var/lib/dpkg/lock-frontend - open (13: > Permission denied) > E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), > are you root? > > Any idea what the difference is? Here I'm running the external > "apt-get". Is the "apt-get install" supposed to happen inside the > chroot? There is no "apt-get" binary there yet. > > If I can quickly and repeatedly reproduce the failure, I can "apt-cache > policy libopencv-dev", and I can see if it's trying to use the > preferences file and such. Maybe I mistyped something. > > If the above diagnostic sequence cannot work, what would? > > Thanks much > signature.asc Description: signature
Bug#1055516: python3-jsonschema: New upstream version available
Hi, As per this: https://qa.debian.org/excuses.php?experimental=1&package=python-jsonschema version 4.19 introduces regressions in at least 5 packages... Patches to fix these are warmly welcome. Also, I'm not sure why this same page reports that the package is "uninstallable on arch arm64"... Cheers, Thomas Goirand (zigo)
Bug#1057028: node-stable: please remove me from uploaders
Source: node-stable Severity: wishlist Hello, Back in a day I packaged/sponsored a bunch of node packages needed by node-shiny-server. I ended up never using shiny-server and/or node-shiny-server, but with the responsibility for its dependencies. Thus I would like to be removed from the uploaders of this package. Best, Andrius OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1057027: node-pause: please remove me from uploaders
Source: node-pause Severity: wishlist Hello, Back in a day I packaged/sponsored a bunch of node packages needed by node-shiny-server. I ended up never using shiny-server and/or node-shiny-server, but with the responsibility for its dependencies. Thus I would like to be removed from the uploaders of this package. Best, Andrius OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1057024: node-client-sessions: please remove me from uploaders
Source: node-client-sessions Severity: wishlist Hello, Back in a day I packaged/sponsored a bunch of node packages needed by node-shiny-server. I ended up never using shiny-server and/or node-shiny-server, but with the responsibility for its dependencies. Thus I would like to be removed from the uploaders of this package. Best, Andrius OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1057026: node-morgan: please remove me from uploaders
Source: node-morgan Severity: wishlist Hello, Back in a day I packaged/sponsored a bunch of node packages needed by node-shiny-server. I ended up never using shiny-server and/or node-shiny-server, but with the responsibility for its dependencies. Thus I would like to be removed from the uploaders of this package. Best, Andrius OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1057025: node-ip-address: please remove me from uploaders
Source: node-ip-address Severity: wishlist Hello, Back in a day I packaged/sponsored a bunch of node packages needed by node-shiny-server. I ended up never using shiny-server and/or node-shiny-server, but with the responsibility for its dependencies. Thus I would like to be removed from the uploaders of this package. Best, Andrius OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1057023: devscripts: 'debclean --cleandebs' should also remove .buildinfo
Package: devscripts Version: 2.23.6 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 In its current form, 'debclean --cleandebs' leaves .buildinfo files. It would be desirable to remove these too. Martin-Éric -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAmVlkdsACgkQrh+Cd8S0 17ZezQ/+P2rIV0yOf+2NMpboTXI3dvHlLggHKGYxLRCzA4e/oAMMoaKDD9S+KcMH 02trR564dBs/RbUq9veEenHVQGFWGWJjKNqK9Cpk742qXEoFIzdBm9poT2/ScV7Y qYtabYft5n74yW9b1cOYcWMaYizRw2eXD/dBQOZL5hrDLTbcIvjcs9Oj1qBnFZ+f ed9MyugxMAOkOj2rwTUNqJdaH7A5e2GUVHpNDuzk7PzeYP0Vk+GdLWlOOYdUpmm/ rJk6+1xHT5/ivmZyt6QpoJR+kyn4WLo5OveI7tdz5hiJaOL7q81IAaZ6KuT7JZSQ RuS6f9fczA1aW0vBGCU60179YPqzrQy4UixgvzKtdGZnGXBsWM3tjMZK0fSL+27U +tCDWM9OgM9JU6tVkPniSQxYjHWJIcYnE4xlpXh7/KyLf651Ro0NPhJCtY3NHyCq hLGoD0/hSRfZZLW5MCl8EaTLX1b2TXG9U4W02VUZbwCVGx2+bmfCph8r4giTnzoC loUySiMMM98t8a9gRLr4a3obYdp5BqRqw2Z6u+haCV7xCynB9XYD0MXTrHSPP+kp 7rBBtgLJER0LNsiHft7N0TTQPezsC2nfnpWFgciRrj8CAPV17/zHwEwjiNKs1vii 0id8N7g0sc4rfJBzScDtktTtebxJ0XBwXI0QxDyDeu/qtk/DU3s= =bwjk -END PGP SIGNATURE-
Bug#1057022: RFS: purple-discord/0.9.2023.10.23.git.f8b0c59-1~bpo12+1 -- Discord messaging service plugin for libpurple
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "purple-discord": * Package name : purple-discord Version : 0.9.2023.10.23.git.f8b0c59-1~bpo12+1 Upstream contact : * URL : https://github.com/EionRobb/purple-discord/ * License : GPL-3+ * Vcs : Section : net The source builds the following binary packages: purple-discord - Discord messaging service plugin for libpurple To access further information about this package, please visit the following URL: https://mentors.debian.net/package/purple-discord/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/p/purple-discord/purple-discord_0.9.2023.10.23.git.f8b0c59-1~bpo12+1.dsc Changes since the last upload: purple-discord (0.9.2023.10.23.git.f8b0c59-1~bpo12+1) bookworm-backports; urgency=medium . * Rebuild for bookworm-backports. Regards, -- Patrick ZAJDA OpenPGP_0x9D4AD35BEA273DCA.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1051803: ITS: freespace2
Hi Sébastien, Can you please upload a copy of your git tree with 23.2.1+repack-1 at https://salsa.debian.org/games-team/freespace2 ? https://salsa.debian.org/twolife/freespace2/ stops at 23.2.0 while mentors is at 23.2.1 Dimitry: can this be a one-of team-upload ? Greetings, Le dim. 22 oct. 2023 à 19:03, Sébastien Noel a écrit : > > Ping ? > > > Le mercredi 20 septembre 2023 à 10:04 +0200, Sébastien Noel a écrit : > > Hi Dmitry !
Bug#1049455: Binutils: mips-gold patch was refreshed incorrectly
> > is the debian/patches/gold-mips patch still needed? For Debian, we can remove it now. The only problem is that the default output of gold will be always o32, but it won't be a problem for us: ld is merely called directly, and gold is not the default ld. > If yes, please could > you submit this upstream? > Yes. I submitted, while it is waiting for approval of gold maintainers.
Bug#1057021: lz4-java: FTBFS on i386 (only) due to JVM SIGSEGV
Source: lz4-java Severity: important lz4-java is FTBFS on i386 due to JVM segfaults during the test-suite: https://buildd.debian.org/status/logs.php?pkg=lz4-java&ver=1.8.0-4&arch=i386 The following bug has been filed against openjdk-17-jdk: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057019
Bug#1052376: lxpanel: no longer obeys its geometry settings
Package: lxpanel Version: 0.10.1-4.1 Followup-For: Bug #1052376 X-Debbugs-Cc: pitsior...@outlook.com I would like to publically thank Jeroen Diederen for patching lxpanel for me (thus the .1 at the end of the package version) and for showing us the github repo of lxde-continued. He has replied at the other bug report, the one about the gtk3 issues of the app (1052050). Oddly, all 7 patches that are there fixed only one of my issues above, the one with the panel going off screen. However, this was the most annoying one for me and I am thankfull for his work. I probably do not use the functionality the others patches provide. There is a newer version of lxpanel on the github page of lxde-continued, 0.10.2, and, if the lxde project is really abandoned by its own devs who moved to lxqt, I would like to see the maintainers updating lxpanel from there, assuming that debian has no plans of removing lxde as a whole anytime soon, and since its other other apps like lxterminal still work. p.s. Yea, vala-panel did not make it for me because of some crashes it regularly had and I removed it a week later. -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.5.0-4-amd64 (SMP w/2 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages lxpanel depends on: ii libasound2 1.2.10-1 ii libc62.37-12 ii libcairo21.18.0-1 ii libcurl3-gnutls 8.4.0-2 ii libfm-gtk3-4 1.3.2-4 ii libfm-modules1.3.2-4 ii libfm4 1.3.2-4 ii libgdk-pixbuf-2.0-0 2.42.10+dfsg-3 ii libglib2.0-0 2.78.1-4 ii libgtk-3-0 3.24.38-6 ii libiw30 30~pre9-14 ii libkeybinder-3.0-0 0.3.2-1.1 ii libmenu-cache3 1.1.0-1.1 ii libpango-1.0-0 1.51.0+ds-3 ii libwnck-3-0 43.0-3 ii libx11-6 2:1.8.7-1 ii libxkbfile1 1:1.1.0-1 ii libxml2 2.9.14+dfsg-1.3 ii lxmenu-data 0.1.5-2.1 ii lxpanel-data 0.10.1-4.1 Versions of packages lxpanel recommends: ii alacritty [x-terminal-emulator] 0.12.2-2+b1 ii dunst [notification-daemon] 1.9.2-1 ii libnotify-bin 0.8.2-1 ii notification-daemon 3.20.0-4+b1 pn pavucontrol | gnome-alsamixer ii rxvt-unicode [x-terminal-emulator] 9.31-1 ii xkb-data2.38-2 Versions of packages lxpanel suggests: ii brave-browser [www-browser] 1.60.118 ii chromium [www-browser] 119.0.6045.159-1 ii firefox [www-browser]120.0-2 -- no debconf information
Bug#1057020: libgdk-pixbuf-2.0-0: Fails to load webp
Package: libgdk-pixbuf-2.0-0 Version: 2.42.10+dfsg-3 Severity: important Dear Maintainer, libgdk-pixbuf-2.0-0 fails to load webp images. This is a regression also reported in arch here -> https://bbs.archlinux.org/viewtopic.php?id=287629 PR with patch is here -> https://github.com/aruiz/webp-pixbuf-loader/pull/73 See also #1056295 -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.5.12-x64v3-xanmod1 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.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 libgdk-pixbuf-2.0-0 depends on: ii libc62.37-12 ii libgdk-pixbuf2.0-common 2.42.10+dfsg-3 ii libglib2.0-0 2.78.1-4 ii libjpeg62-turbo 1:2.1.5-2 ii libpng16-16 1.6.40-2 ii libtiff6 4.5.1+git230720-2 ii shared-mime-info 2.2-1 Versions of packages libgdk-pixbuf-2.0-0 recommends: ii libgdk-pixbuf2.0-bin 2.42.10+dfsg-3 libgdk-pixbuf-2.0-0 suggests no packages. -- no debconf information
Bug#1057019: openjdk-17-jdk: SIGSEGV on i386 during lz4-java tests (PhaseIdealLoop::build_loop_late_post_work(Node*, bool)+0x14e)
Package: openjdk-17-jdk Version: 17.0.9+9-2 Severity: normal Dear Maintainer, lz4-java tests are failing consistently (well, twice so far on the buildds) with a JVM segfault, on the i386 arch only. I am not able to reproduce when cross-building on amd64 with --arch=i386 in a sbuild chroot, so I can't provide the error report or compiler replay data (yet), but the failure message is: # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0xf758ddce, pid=634517, tid=634556 # # JRE version: OpenJDK Runtime Environment (17.0.9+9) (build 17.0.9+9-Debian-2) # Java VM: OpenJDK Server VM (17.0.9+9-Debian-2, mixed mode, sharing, tiered, g1 gc, linux-x86) # Problematic frame: # V [libjvm.so+0x880dce] PhaseIdealLoop::build_loop_late_post_work(Node*, bool)+0x14e # # No core dump will be written. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again # # An error report file with more information is saved as: # /tmp/J0/hs_err_pid634517.log # # Compiler replay data is saved as: # /tmp/J0/replay_pid634517.log # # If you would like to submit a bug report, please visit: # https://bugs.debian.org/openjdk-17 The buildd logs are available here [1,2]; both fail with: # V [libjvm.so+0x880dce] PhaseIdealLoop::build_loop_late_post_work(Node*, bool)+0x14e [1] https://buildd.debian.org/status/fetch.php?pkg=lz4-java&arch=i386&ver=1.8.0-4&stamp=1701066936&raw=0 [2] https://buildd.debian.org/status/fetch.php?pkg=lz4-java&arch=i386&ver=1.8.0-4&stamp=1700852759&raw=0 I will try to reproduce with QEMU. Thank you, tony
Bug#1057018: zfs-dkms: VERIFY3 failed; PANIC at range_tree.c:435; cause all operations to hang until hard reboot
Package: zfs-dkms Version: 2.1.11-1 Severity: important Tags: lfs upstream X-Debbugs-Cc: j3cipgk39...@explodemail.com Dear Maintainer, When doing incremental replication of encrypted datasets, `zfs send` crashes and `zfs recv` hangs without responding to any kill signals. Any subsequent zfs operations hang infinitely until a hard power cycle is forced (due to reboot similarly hanging). The following appears in kernel log: ``` VERIFY3(size != 0) failed (0 != 0) PANIC at range_tree.c:435:range_tree_remove_impl() Showing stack for process 24 CPU: 1 PID: 24 Comm: z_wr_iss Tainted: P OE 5.9.0-5-amd64 #1 Debian 5.9.15-1 Hardware name: *REDACTED* Call Trace: dump_stack+0x6b/0x83 spl_panic+0xd4/0xfc [spl] ? kfpu_end+0x3f/0x70 [zcommon] ? zfs_btree_insert_into_leaf+0x22e/0x330 [zfs] ? abd_iterate_func.part.0+0x13b/0x1b0 [zfs] ? zfs_btree_add_idx+0xa5/0x230 [zfs] ? zfs_btree_find+0x5d/0x320 [zfs] ? zfs_btree_find+0x188/0x320 [zfs] range_tree_remove_impl+0xa92/0xf00 [zfs] ? metaslab_df_alloc+0x1c3/0x5c0 [zfs] ? multilist_sublist_insert_tail+0x2b/0x50 [zfs] metaslab_alloc_dva+0xbd3/0x14a0 [zfs] ? _cond_resched+0x16/0x40 metaslab_alloc+0xcf/0x280 [zfs] zio_dva_allocate+0xd4/0x8d0 [zfs] ? irq_exit_rcu+0x3e/0xc0 ? common_interrupt+0x77/0x130 ? asm_common_interrupt+0x1e/0x40 zio_execute+0x81/0x120 [zfs] taskq_thread+0x2df/0x520 [spl] ? wake_up_q+0xa0/0xa0 ? zio_gang_tree_free+0x60/0x60 [zfs] ? taskq_thread_spawn+0x50/0x50 [spl] kthread+0x11b/0x140 ? __kthread_bind_mask+0x60/0x60 ret_from_fork+0x22/0x30 INFO: task z_wr_iss:765697 blocked for more than 120 seconds. Tainted: P OE 5.9.0-5-amd64 #1 Debian 5.9.15-1 "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:z_wr_issstate:D stack:0 pid:765697 ppid: 2 flags:0x4000 Call Trace: __schedule+0x281/0x8a0 schedule+0x4a/0xb0 schedule_preempt_disabled+0xa/0x10 __mutex_lock.constprop.0+0x13a/0x480 metaslab_alloc_dva+0x413/0x14a0 [zfs] ? _cond_resched+0x16/0x40 metaslab_alloc+0xcf/0x280 [zfs] zio_dva_allocate+0xd4/0x8d0 [zfs] ? zio_vdev_io_done+0x49/0x220 [zfs] zio_execute+0x81/0x120 [zfs] taskq_thread+0x2df/0x520 [spl] ? wake_up_q+0xa0/0xa0 ? zio_gang_tree_free+0x60/0x60 [zfs] ? taskq_thread_spawn+0x50/0x50 [spl] kthread+0x11b/0x140 ? __kthread_bind_mask+0x60/0x60 ret_from_fork+0x22/0x30 INFO: task txg_sync:765752 blocked for more than 120 seconds. Tainted: P OE 5.9.0-5-amd64 #1 Debian 5.9.15-1 "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. ``` There is an upstream patch available: The fix should be present already in bookworm-backports but is sever enough that I believe it should be brought into stable. Upstream issue: https://github.com/openzfs/zfs/issues/11893 Upstream patch targeting 2.1.12: https://github.com/openzfs/zfs/pull/14843 -- System Information: Debian Release: 12.2 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.9.0-5-amd64 (SMP w/12 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages zfs-dkms depends on: ii debconf [debconf-2.0] 1.5.82 ii dkms 3.0.10-8+deb12u1 ii file 1:5.44-3 ii libc6-dev [libc-dev] 2.36-9+deb12u3 ii libpython3-stdlib 3.11.2-1+b1 ii lsb-release12.0-1 ii perl 5.36.0-7 ii python3-distutils 3.11.2-3 Versions of packages zfs-dkms recommends: ii linux-libc-dev 6.1.55-1 ii zfs-zed 2.1.11-1 ii zfsutils-linux 2.1.11-1 Versions of packages zfs-dkms suggests: pn debhelper -- debconf information: * zfs-dkms/note-incompatible-licenses: zfs-dkms/stop-build-for-unknown-kernel: true zfs-dkms/stop-build-for-32bit-kernel: true
Bug#1056295: geeqie: webp images no longer viewable
Seems like https://bbs.archlinux.org/viewtopic.php?id=287629 On Sun, 19 Nov 2023 19:44:17 -0800 Dean Hamstead wrote: > Package: geeqie > Version: 1:2.1-1 > Severity: important > > Dear Maintainer, > > Upon recent update, webp images are no longer viewable > > > Here is a file that is webp and previously viewable, but now gives an > erro and doesnt view > > > dean@wheeljack:~/pics$ file 271366_20211213110900.webp > 271366_20211213110900.webp: RIFF (little-endian) data, Web/P image, VP8 encoding, 1333x1999, Scaling: [none]x[none], YUV color, decoders should clamp > dean@wheeljack:~/pics$ geeqie 271366_20211213110900.webp > Error reading GIF file: Unrecognized image file format > > > This may be a library rather than geeqie itself, if so then please point > me in the right direction > > > -- System Information: > Debian Release: trixie/sid > APT prefers unstable > APT policy: (500, 'unstable'), (500, 'testing') > Architecture: amd64 (x86_64) > > Kernel: Linux 6.5.11-x64v3-xanmod1 (SMP w/16 CPU threads; PREEMPT) > Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE > Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.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 geeqie depends on: > ii geeqie-common 1:2.1-1 > ii libarchive13 3.7.2-1 > ii libc6 2.37-12 > ii libcairo2 1.18.0-1 > ii libdjvulibre21 3.5.28-2+b1 > ii libexiv2-27 0.27.6-1 > ii libffmpegthumbnailer4v5 2.2.2+git20220218+dfsg-2 > ii libgcc-s1 13.2.0-6 > ii libgdk-pixbuf-2.0-0 2.42.10+dfsg-3 > ii libglib2.0-0 2.78.1-4 > ii libgspell-1-2 1.12.2-1 > ii libgtk-3-0 3.24.38-6 > ii libheif1 1.17.1-1+b1 > ii libjpeg62-turbo 1:2.1.5-2 > ii libjxl0.7 0.7.0-10.2 > ii liblcms2-2 2.14-2 > ii liblua5.3-0 5.3.6-2 > ii libopenjp2-7 2.5.0-2 > ii libpango-1.0-0 1.51.0+ds-3 > ii libpangocairo-1.0-0 1.51.0+ds-3 > ii libpoppler-glib8 22.12.0-2+b1 > ii libraw23 0.21.1-7 > ii libstdc++6 13.2.0-6
Bug#924862: shaderc isn't needed
I asked mpv developers, and apparently libplacebo indeed now can handle shader compilation without need for shaderc. So this seems to be not even needed at all on Linux. See: https://github.com/mpv-player/mpv/issues/12982 Regards, Shmerl.
Bug#1057017: qtpositioning5-dev_5.15.8%2bdfsg-3_amd64.deb 404 Not Found
Package: qtpositioning5-dev Version: 5.15.8%2bdfsg-3_amd64 While attempting to install packages to compile a QT5 program on Debian 12, I get the following package error: #sudo apt install qtpositioning5-dev Err:3 http://deb.debian.org/debian bookworm/main amd64 qtpositioning5- dev amd64 5.15.8+dfsg-3 404 Not Found [IP: 199.232.30.132 80] Fetched 2,896 kB in 0s (6,285 kB/s) E: Failed to fetch http://deb.debian.org/debian/pool/main/q/qtlocation-opensource-src/qtpositioning5-dev_5.15.8%2bdfsg-3_amd64.deb 404 Not Found [IP: 199.232.30.132 80] E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing? I see other versions in the repository, but the version that is supposedly the most updated one doesn't exist on the server. Using Linux debian-main 6.1.0-12-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.52-1 (2023-09-07) x86_64 GNU/Linux, libc6 2.36-9+deb12u3
Bug#1056780: openmsx: Source-less Windows binary in source package (and other packaging issues)
I had a Debian Developer review my packaging work. I got the package version string wrong and was slightly vague about the debhelper version update in the changelog. Both of those things are now fixed and I have the fixed files pushed to the same GitHub repo as last time, https://github.com/ArrayBolt3/openmsx-packaging. -- Aaron Rainbolt Lubuntu Developer Matrix: @arraybolt3:matrix.org IRC: arraybolt3 on irc.libera.chat GitHub: https://github.com/ArrayBolt3
Bug#979688: Simplifying the list of image files for arm64 sunxi boards
On 27/11/2023 20:12, Vagrant Cascadian (@vagrant) wrote on salsa: >Thanks! Looks good to me, could you add (Closes: #XXX) on the first line of >the commit? Hi Vagrant, Thanks for agreeing to the merge request. I've added the Closes: note. I just wanted to note while the bug is still open, that I was originally aiming to simplify the list of files for each arm64 sunxi board in targets.mk, and from my point of view u-boot-sunxi-with-spl.bin is the only one still needed. I know that you said earlier (on 25/07/2023 17:39 in the bug report): > I am also a bit inclined to adding u-boot-sunxi-with-spl.bin rather than > replacing all the other parts, as there are some use-cases (e.g. an > image capable of booting both sunxi and rockchip systems at different > offsets) where the individual parts are still needed. but I'm not sure that's right, because I believe sunxi-spl.bin and u-boot-sunxi-with-spl.fit.itb always need to be concatenated to work, because the SPL is hard-coded to look for U-Boot proper immediately after itself, as determined by spl_mmc_get_uboot_raw_sector() in arch/arm/mach-sunxi/board.c. So I think any "One image to rule them all" that arranged the parts differently would need a custom build, not the files currently in the Debian u-boot binary packages. That said, I'm happy to see u-boot-sunxi-with-spl.bin included, so thank you very much for doing that and all the other things that came up in this sprawling bug report. Best wishes, Harold.
Bug#1054657: transition: r-bioc-biocgenerics
Le Wed, Nov 22, 2023 at 08:46:17PM +0100, Andreas Tille a écrit : > Control: tags -1 - moreinfo > > r-bioc-sparsearray is accepted in unstable. Hello everybody, would it be possible to have an estimation about when we can expect to start the Bioconductor transition ? I am contributing to Debian mostly on my work time and it would be super useful for me to have this information in order to better integrate it in my planning. Regarding my unavailable dates: it is Dec 2nd to 11th, and 23rd to Jan 8th. The next Bioconductor release has not been announced but will probably take place in April or May 2024. As time passes I am starting to wonder if we should just skip the current one... Have a nice day, Charles -- Charles Plessy Nagahama, Yomitan, Okinawa, Japan Debian Med packaging team http://www.debian.org/devel/debian-med Tooting from home https://framapiaf.org/@charles_plessy - You do not have my permission to use this email to train an AI -
Bug#1053405: darktable: FTBFS on arm64 (gcc bug?)
On Thu, 5 Oct 2023 08:56:00 +0200 Gianfranco Costamagna wrote: > control: reassign -1 src:gcc-13 > control: found -1 13.2.0-4 > control: affects -1 src:darktable. > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111677 > According to upstream, we need a patch that was added some days ago on 13 branch Can we disable openmp support in darktable for now? This bug has been blocking many transitions (that I care) for way too long. Thanks, Boyuan Yang > On Wed, 4 Oct 2023 08:21:31 +0200 Gianfranco Costamagna wrote: > > Hello, > > > > > > > > Do you think maybe there should be a debian gcc bug? after all, the > > > distinction you point to is a difference of debian version. > > > > > > > Not really sure, somewhat it fails with gcc-12 too, so it might be something that was even backported to older gcc, or something else > > > > > > For sure, it builds if we disable OPENMP support > > > > diff -Nru darktable-4.4.2/debian/changelog darktable- 4.4.2/debian/changelog > > --- darktable-4.4.2/debian/changelog2023-08-20 12:26:40.0 + > > +++ darktable-4.4.2/debian/changelog2023-10-03 15:58:01.0 + > > @@ -1,3 +1,10 @@ > > +darktable (4.4.2-1.1) unstable; urgency=medium > > + > > + * Disable openmp for arm64 builds (LP: #2038351) > > + See Debian bug: #1053405 > > + > > + -- Mitchell Dzurick Tue, 03 Oct 2023 08:58:01 -0700 > > + > > darktable (4.4.2-1) unstable; urgency=medium > > > > * Update to new upstream version 4.4.2. > > diff -Nru darktable-4.4.2/debian/rules darktable-4.4.2/debian/rules > > --- darktable-4.4.2/debian/rules2023-08-20 12:26:40.0 + > > +++ darktable-4.4.2/debian/rules2023-10-03 15:58:01.0 + > > @@ -20,7 +20,12 @@ > > dh $@ > > > > override_dh_auto_configure: cmake/version.cmake > > +ifeq ($(DEB_HOST_ARCH),arm64) > > + # Disable OPENMP for arm64 builds. See LP: #2038351 > > + dh_auto_configure -- -DBINARY_PACKAGE_BUILD=1 - DCMAKE_BUILD_TYPE=Release -DRAWSPEED_ENABLE_LTO=ON -DUSE_OPENMP=OFF > > +else > > dh_auto_configure -- -DBINARY_PACKAGE_BUILD=1 - DCMAKE_BUILD_TYPE=Release -DRAWSPEED_ENABLE_LTO=ON > > +endif > > > > describe-current-version: > > git describe --tags upstream | sed 's,^release-,,;s,-,+,;s,-,~,;' signature.asc Description: This is a digitally signed message part
Bug#921815: Versionnumber for closing the bug report
close 921815 1.0.114+deb10u1 thanks On Mon, 27 Nov 2023, Roland Clobus wrote: > Do you want to have a more exact version? Which I closed this issue, I used > the > version that is present in Buster. (Version: 1.0.114+deb10u1) > Going deeper into older versions didn't seen necessary to me. Yeah, that’s probably fine, thanks.
Bug#1056279: Looks like the systemctl links are gone but not the pm-utils ones
On 2023-11-27 at 03:54:16, Helmut Grohne (hel...@subdivi.de) wrote: > I don't have time to update the patch right now. Let me promise an update > this week, ok? Hi Helmut, My apologies for not responding earlier, but this is a rather thorny problem to solve and I have not had the mental "bandwidth" to dig into this yet. I wanted however to express my sincere appreciation for all of the work you have put into both understanding this problem and coming up with a solution. Francois
Bug#1057016: adjtimex: Move files from /lib, /sbin to /usr/lib, /usr/sbin
Package: adjtimex
Version: 1.29-11+b1
Severity: normal
Tags: patch
User: helm...@debian.org
Usertags: dep17m2
Dear Maintainer,
your package adjtimex ships files in /lib and /sbin. For the ongoing
UsrMerge effort [1] these directories should become "empty", IOW
packages should not install files there, but instead into the respective
directories in /usr.
It seems to me that adjtimex could move these files now. I'm attaching a
patch, that seems to work for me. However, please read the linked wiki
page and upload to experimental first, to receive info about problems
from "dumat" (also see [1]).
Also note, any backports to bookworm or earlier should undo these
changes.
Thanks for considering,
Chris
1. https://wiki.debian.org/UsrMerge
diff -Nru adjtimex-1.29/debian/adjtimex.init adjtimex-1.29/debian/adjtimex.init
--- adjtimex-1.29/debian/adjtimex.init 2021-04-27 17:11:49.0 +0200
+++ adjtimex-1.29/debian/adjtimex.init 2023-11-28 00:11:28.0 +0100
@@ -16,7 +16,7 @@
. /lib/lsb/init-functions
-test -x /sbin/adjtimex || exit 0
+test -x /usr/sbin/adjtimex || exit 0
# default values
TICK=1
@@ -31,7 +31,7 @@
case "$1" in
start|restart|force-reload)
echo -n "Regulating system clock..."
-/sbin/adjtimex -tick "$TICK" -frequency "$FREQ"
+/usr/sbin/adjtimex -tick "$TICK" -frequency "$FREQ"
echo "done."
;;
stop|status)
diff -Nru adjtimex-1.29/debian/adjtimex.install
adjtimex-1.29/debian/adjtimex.install
--- adjtimex-1.29/debian/adjtimex.install 2021-04-27 17:11:49.0
+0200
+++ adjtimex-1.29/debian/adjtimex.install 2023-11-28 00:11:43.0
+0100
@@ -1,3 +1,3 @@
-adjtimex sbin
+adjtimex usr/sbin
debian/adjtimexconfig usr/sbin
debian/contrib/ntp-drift_to_freq.sh usr/share/doc/adjtimex/contrib
diff -Nru adjtimex-1.29/debian/adjtimex.service
adjtimex-1.29/debian/adjtimex.service
--- adjtimex-1.29/debian/adjtimex.service 2021-04-27 17:11:49.0
+0200
+++ adjtimex-1.29/debian/adjtimex.service 2023-11-28 00:11:16.0
+0100
@@ -10,7 +10,7 @@
Type=oneshot
Environment="TICK=1" "FREQ=0"
EnvironmentFile=-/etc/default/adjtimex
-ExecStart=/sbin/adjtimex -tick ${TICK} -frequency ${FREQ}
+ExecStart=/usr/sbin/adjtimex -tick ${TICK} -frequency ${FREQ}
[Install]
WantedBy=sysinit.target
diff -Nru adjtimex-1.29/debian/changelog adjtimex-1.29/debian/changelog
--- adjtimex-1.29/debian/changelog 2021-04-27 17:11:49.0 +0200
+++ adjtimex-1.29/debian/changelog 2023-11-28 00:11:43.0 +0100
@@ -1,3 +1,10 @@
+adjtimex (1.29-11.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Move files from /lib, /sbin to /usr/lib, /usr/sbin. (Closes: #-1)
+
+ -- Chris Hofstaedtler Tue, 28 Nov 2023 00:11:43 +0100
+
adjtimex (1.29-11) unstable; urgency=medium
* debian/patches:
diff -Nru adjtimex-1.29/debian/patches/12-makefile.in-bindir.patch
adjtimex-1.29/debian/patches/12-makefile.in-bindir.patch
--- adjtimex-1.29/debian/patches/12-makefile.in-bindir.patch1970-01-01
01:00:00.0 +0100
+++ adjtimex-1.29/debian/patches/12-makefile.in-bindir.patch2023-11-28
00:11:43.0 +0100
@@ -0,0 +1,13 @@
+Index: adjtimex-1.29/Makefile.in
+===
+--- adjtimex-1.29.orig/Makefile.in
adjtimex-1.29/Makefile.in
+@@ -9,7 +9,7 @@ CFLAGS += @CFLAGS@ -Wall
+ prefix = @prefix@
+ man1dir=@mandir@/man1
+ exec_prefix = @exec_prefix@
+-bindir=/sbin
++bindir= @exec_prefix@/sbin
+ datadir = @datadir@
+ datarootdir = @datarootdir@
+
diff -Nru adjtimex-1.29/debian/patches/series
adjtimex-1.29/debian/patches/series
--- adjtimex-1.29/debian/patches/series 2021-04-27 17:11:49.0 +0200
+++ adjtimex-1.29/debian/patches/series 2023-11-28 00:10:09.0 +0100
@@ -9,3 +9,4 @@
09-adjtimex.8-Some-fixes-to-the-manual.patch
10-STA_NANO-confuses-adjtimex-8.patch
11-Fix-ntpdate-command.patch
+12-makefile.in-bindir.patch
Bug#1056770: braillefont: Description in debian/control has a new line in the middle of a sentence
Test results - Mail to 1056...@bugs.debian.org - - received by maintainer - *not* received by bug submitter - recorded in the bts (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056770#10) Mail to 1056770-submit...@bugs.debian.org - - *not* received by maintainer - received by bug submitter - recorded in the bts (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056770#13) Mail to both - - received by maintainer - received by bug submitter - recorded in the bts (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056770#18) signature.asc Description: This is a digitally signed message part.
Bug#969590: sqop: Cannot use certificates for signature verification?
Hi! On Mon, 2023-11-27 at 17:14:16 +0800, Blair Noctis wrote: > > Package: sqop > > Version: 0.17.0-2 > > Severity: normal > > > I was trying out sqop, to potentially add native support for it into > > dpkg-dev, but when trying to verify a signature, it does not seem work > > as expected and I'm at a loss due to the lack of man page (see the > > other report :). > > Since even oldstable (11/bulleye as of 2023-11-27) has 0.22.1 of sqop, and > stable (12/bookworm) has 0.27.3, unstable 0.31.0, is this still relevant? Ah, I think this can be closed, yes. dpkg even grew sqop support some time ago. Thanks, Guillem
Bug#1057015: ITP: qt6-grpc -- Qt 6 Protobuf & gRPC support
Package: wnpp Severity: wishlist Owner: Patrick Franz X-Debbugs-Cc: debian-de...@lists.debian.org, delta...@debian.org,debian-qt-...@lists.debian.org * Package name: qt6-grpc Version : 6.6.0 Upstream Contact: The Qt Company Ltd. * URL : https://www.qt.io/developers/ * License : GPL, LGPL, BSD Description : Qt 6 Protobuf & gRPC support Qt is a cross-platform C++ application framework. Qt's primary feature is its rich set of widgets that provide standard GUI functionality. This module contains support for protobuf and gRPC.
Bug#1056587: texlive-latex-base: some math characters get replaced as of Debian's TeX Live 2023
Control: severiy -1 wishlist Control: title -1 fmtutil should ignore TEXINPUTS set in root env On 27.11.2023 01:06, Norbert Preining wrote: Hello Norbert, Since I am not using Debian, nor developing for Debian, I think I stop arguing here. No need to discuss my opinion on that matter further. Feel free to bring it up to the TC, or d-d, or where ever you feel is the correct place. Many, many thanks for stepping in, I did not find the time to help here. For now I'd rather contact debian-mentors and ask for their opinion. I did not find any statement in the policy. Hilmar -- sigfault OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1056556: Debugging techniques
Hi. I tried to do that apt pinning today, as you suggested. It still
fails in the same way as before:
$ mmdebstrap
I: installing remaining packages inside the chroot...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
ros-noetic-cv-bridge : Depends: libopencv-dev but it is not installable
ros-noetic-grid-map-filters : Depends: libopencv-dev but it is not
installable
ros-noetic-image-geometry : Depends: libopencv-dev but it is not installable
E: Unable to correct problems, you have held broken packages.
The preferences file is there, but it isn't obviously doing anything. I
did some debugging just now to try to figure out why, and I'm reminded
of
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036929
Ideally the workflow I would like is
1. mmdebstrap does stuff. When it runs a command, it prints out EXACTLY
what it does, in a way that I can copy/paste it, and get the same
output
2. If it fails to do something, it drops me into a shell. Where I can
paste the command to reproduce the problem, and then poke around to
fix it
This probably isn't 100% possible here; but how would you debug this
otherwise?
I'm attaching a patch that does some of (1.) above. This uses
String::ShellQuote to quote all the arguments so that the command string
can be pasted. I'm guessing you'd want to do some of that differently,
so it isn't super thorough.
OK. Then I gave myself a shell in a spot that (I think?) sits right
before the failing "apt-get install":
mmdebstrap \
--essential-hook 'echo $$1; bash -i' \
And pasting the command didn't work as I had hoped:
root@fatty:# apt-get -o Dir::Bin::dpkg=env -o DPkg::Options::=--unset=TMPDIR
-o DPkg::Options::=dpkg -o DPkg::Chroot-Directory=/tmp/mmdebstrap.i1wpW0WLMS
--yes install -oDpkg::Use-Pty=false tst-libopoencv
'?narrow(?or(?archive(^focal$),?codename(^focal$)),?architecture(arm64),?and(?or(?priority(required),?priority(important)),?not(?essential)))'
E: Could not open lock file /var/lib/dpkg/lock-frontend - open (13:
Permission denied)
E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend),
are you root?
Any idea what the difference is? Here I'm running the external
"apt-get". Is the "apt-get install" supposed to happen inside the
chroot? There is no "apt-get" binary there yet.
If I can quickly and repeatedly reproduce the failure, I can "apt-cache
policy libopencv-dev", and I can see if it's trying to use the
preferences file and such. Maybe I mistyped something.
If the above diagnostic sequence cannot work, what would?
Thanks much
diff --git a/debian/control b/debian/control
index c82cdb3..e3f56a8 100644
--- a/debian/control
+++ b/debian/control
@@ -17,6 +17,7 @@ Architecture: all
Depends:
apt (>= 2.3.14),
python3 (>= 3.10),
+ libstring-shellquote-perl,
${misc:Depends},
${perl:Depends},
Recommends:
diff --git a/mmdebstrap b/mmdebstrap
index 0abdfc3..d52496d 100755
--- a/mmdebstrap
+++ b/mmdebstrap
@@ -46,6 +46,7 @@ use Socket;
use Time::HiRes;
use Math::BigInt;
use Text::ParseWords;
+use String::ShellQuote qw(shell_quote);
use version;
## no critic (InputOutput::RequireBriefOpen)
@@ -815,8 +816,6 @@ sub run_progress {
info "run_progress() received signal $_[0]: waiting for child...";
};
-debug("run_progress: exec " . (join ' ', ($get_exec->('${FD}';
-
# delay signals so that we can fork and change behaviour of the signal
# handler in parent and child without getting interrupted
my $sigset = POSIX::SigSet->new(SIGINT, SIGHUP, SIGPIPE, SIGTERM);
@@ -845,6 +844,8 @@ sub run_progress {
# redirect stderr to stdout so that we can capture it
open(STDERR, '>&', STDOUT) or error "cannot open STDOUT: $!";
my @execargs = $get_exec->($fd);
+my $cmd_string = shell_quote(@execargs);
+
# before apt 1.5, "apt-get update" attempted to chdir() into the
# working directory. This will fail if the current working directory
# is not accessible by the user (for example in unshare mode). See
@@ -853,8 +854,11 @@ sub run_progress {
chdir $chdir or error "failed chdir() to $chdir: $!";
}
eval { Devel::Cover::set_coverage("none") } if $is_covering;
+
+info("run_progress: running $cmd_string");
+
exec { $execargs[0] } @execargs
- or error 'cannot exec() ' . (join ' ', @execargs);
+ or error 'cannot exec() $cmd_string';
}
close $wfh;
@@ -947,7 +951,7 @@ sub run_progress {
if ($verbosity_level >= 1) {
print STDERR $output;
}
-error((join ' ', $get_exec->('<$fd>')) . '
Bug#1056587: texlive-latex-base: some math characters get replaced as of Debian's TeX Live 2023
On 25.11.2023 01:20, Vincent Lefevre wrote: Hi, I didn't break anything. Any user, including root, may have his own environment variables for his own use. This should never interfer with package installation. Why not unsetting TEXINPUTS in the postinst script? The specific file (glyphtounicode.tex) is only read during format generation AFAICT. So, if we unset the TEXINPUTS variable the fmtutil will again read the default and you will loose your custom file. So either leaving TEXINPUTS or clearing it will not get /your/ expected results. I guess you need a correctly fixed glyphtounicode.tex, which contains a correct fix, w/o breaking other things. Currently I don't understand, why a file glyphtounicode.tex sitting in /usr/local/share/texmf/tex/generic/pdftex/ is ignored during format generation, but this is not the topic of this bug. Hilmar -- sigfault OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1057014: virtualbox-guest-utils: Please move files from /lib, /sbin
Package: virtualbox-guest-utils Version: 7.0.12-dfsg-1 Severity: normal User: helm...@debian.org Usertags: dep17p9 Dear Maintainer, your package virtualbox-guest-utils installs at least these files: /lib/security/pam_vbox.so /sbin/mount.vboxsf For the ongoing UsrMerge effort [1], /lib and /sbin should become "empty", IOW packages should not install files there, but instead into the respective directory in /usr. I believe the files in your package are not affected by any relevant constraints and can be moved now. To do this, please read the details at [1]. Noteworthy: when providing backports to bookworm, for the backport the files should not move to /usr. Thanks, Chris 1. https://wiki.debian.org/UsrMerge
Bug#1056891: statsmodels and cython 3.0
This is also known as LP#2043284; upstream #8961 attempts to fix it, but isn't enough by itself (see salsa-ci for logs).
Bug#915583: patch for debian style
Hello,
the attached file (debian.css) sets up the custom style.
In order to work:
- add the 'python3-sphinx-rtd-theme' package to the dependencies
- in `conf.py.in`, replace:
html_theme = 'nature'
by
html_theme = 'sphinx_rtd_theme'
The generated conf.py file must contain:
# Overwrite theme to fit Debian colors
html_css_files = ['debian.css']
Please tell me if it does not work because I made several workarounds
in order to get it work without everything properly
installed/configured.
Cheers
--
Stéphane
/* Debian Cascading stylesheet for Sphinx */
div.related {
background-color: #C70036;
}
.rst-content h1, .rst-content h2, .rst-content h3, .rst-content h4, .rst-content h5, .rst-content h6 {
color: #C70036;
}
.wy-nav-top {
background-color: #C70036;
}
.wy-side-nav-search {
background-color: #C70036;
}
.rst-content a:link {
color: #0035C7;
text-decoration: none;
}
.rst-content a:visited {
color: #00207A;
text-decoration: none;
}
.rst-content a:link:hover {
color: #00207A;
text-decoration: underline;
}
/* Table in content */
.wy-table-responsive table td, .wy-table-responsive table th {
white-space: normal;
}
.rst-content table.docutils, .wy-table-bordered-all {
width: 100%;
}
.wy-table-responsive table.docutils thead tr {
background-color: #C70036;
border: 1px solid black;
color: black;
}
.wy-table-responsive table.docutils thead tr:hover {
color: #fcfcfc;
}
.wy-table-responsive table.docutils tbody tr:hover {
background-color:#66;
color: #FF;
}
.rst-content table.docutils:not(.field-list) tbody tr:hover:nth-child(2n-1), .wy-table-backed, .wy-table-odd td, .wy-table-striped tr:nth-child(2n-1) td {
background-color:#66;
}
/* Previous and next buttons */
.rst-footer-buttons .btn:hover {
text-decoration: none !important;
}
/* Version release more readable */
.wy-side-nav-search > div.version {
color: #FCFCFC;
}
/* Infos blocks */
div.warning {
border: 1px dashed #EFF500;
background-color: #eff50030;
}
div.note {
border: 1px dashed blue;
background-color: #ff30;
}
.warning, .note {
margin-left: 1em;
margin-right: 1em;
}
@media (max-width: 5in), (max-device-width: 5in){
.warning, .note {
margin-left: 0.5em;
margin-right: 0.5em;
}
}
/* Notes */
html.writer-html5 .rst-content aside.citation, html.writer-html5 .rst-content aside.footnote, html.writer-html5 .rst-content div.citation {
display: block;
}
Bug#1056828: pandas and cython 3.0
Control: severity -1 wishlist Switched to cython3-legacy for now. I do want to actually fix this at some point, but it probably makes sense for that to be after the pandas 2.x transition.
Bug#1057013: Regression: addgroup user group no longer works and should have been documented instead of removed
Package: adduser Version: 3.122 Severity: major File: /usr/sbin/addgroup A regression was caused with the unnecessary commit https://salsa.debian.org/debian/adduser/-/commit/8d42193438f6c1500fb36cd5c24bf682888a611c to close https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=664869 This undocumented syntax was known in use in scripting (such as nvidia tegra debian based distros). Instead of disabling two argument syntax this should instead be reverted and the manpage should be fixed to advertise this syntax since it is functional and in use. Thanks, theofficialgman
Bug#1057012: prlimit crashes when given unacceptable values
Package: util-linux Version: 2.39.2-6 Dear Maintainer, prlimit crashes with a segmentation fault when given an unacceptable value: $ prlimit --data=1073741824 printf 'hello\n' hello $ prlimit --data=0x4000 printf 'hello\n' Segmentation fault $ It should cleanly reject unacceptable values with an error message. This relates to my previous bug report about acceptable value formats being undocumented: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057011 - Michael -- System Information: Debian Release: trixie/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.5.0-4-amd64 (SMP w/32 CPU threads; PREEMPT) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages util-linux depends on: ii libblkid1 2.39.2-6 ii libc6 2.37-12 ii libcap-ng0 0.8.3-1+b3 ii libcrypt1 1:4.4.36-2 ii libmount1 2.39.2-6 ii libpam0g 1.5.2-9.1 ii libselinux13.5-1 ii libsmartcols1 2.39.2-6 ii libsystemd0255~rc3-2 ii libtinfo6 6.4+20231121-1 ii libudev1 255~rc3-2 ii libuuid1 2.39.2-6 ii zlib1g 1:1.3.dfsg-3 Versions of packages util-linux recommends: ii sensible-utils 0.0.20 Versions of packages util-linux suggests: ii dosfstools 4.2-1 ii kbd 2.5.1-1+b1 ii util-linux-extra2.39.2-6 ii util-linux-locales 2.39.2-6 -- no debconf information signature.asc Description: PGP signature
Bug#1057011: prlimit manual page should list units
Package: util-linux Version: 2.39.2-6 Severity: wishlist Dear Maintainer, The prlimit manual page lists the options that can be used to configure limits, but doesn't say what units are used for each or what forms of value are acceptable (for example: decimal, hexadecimal, or whether any suffixes like "G" are accepted). It should. Running prlimit without any arguments will list units for each setting, but that's not an obvious thing to try. - Michael -- System Information: Debian Release: trixie/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.5.0-4-amd64 (SMP w/32 CPU threads; PREEMPT) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages util-linux depends on: ii libblkid1 2.39.2-6 ii libc6 2.37-12 ii libcap-ng0 0.8.3-1+b3 ii libcrypt1 1:4.4.36-2 ii libmount1 2.39.2-6 ii libpam0g 1.5.2-9.1 ii libselinux13.5-1 ii libsmartcols1 2.39.2-6 ii libsystemd0255~rc3-2 ii libtinfo6 6.4+20231121-1 ii libudev1 255~rc3-2 ii libuuid1 2.39.2-6 ii zlib1g 1:1.3.dfsg-3 Versions of packages util-linux recommends: ii sensible-utils 0.0.20 Versions of packages util-linux suggests: ii dosfstools 4.2-1 ii kbd 2.5.1-1+b1 ii util-linux-extra2.39.2-6 ii util-linux-locales 2.39.2-6 -- no debconf information signature.asc Description: PGP signature
Bug#1057001: dh-debputy: HTML documentation is compressed
Sven Joachim: Package: dh-debputy Version: 0.1.9 Severity: normal I was playing around with dh-debputy and tried to convert xterm to it. That seems to mostly work, however two HTML files are now compressed: , | [...] ` It seems that the list of extensions not to compress was converted incorrectly from dh_compress, for the latter ignores *.htm* files, except for changelog.html. [...] Hi Sven Thanks for trying `debputy` and for reporting the bug. I just uploaded debputy/0.1.9.1, which should fix this bug and also remove the `doc-base` benign delta you are seeing. Best regards, Niels
Bug#1057010: open(2) should document ENOENT for trying to create file in deleted directory
Package: manpages-dev Version: 6.03-2 Dear Maintainer, 'man 2 open' lists 3 cases in which ENOENT can be returned: ENOENT O_CREAT is not set and the named file does not exist. ENOENT A directory component in pathname does not exist or is a dangling symbolic link. ENOENT pathname refers to a nonexistent directory, O_TMPFILE and one of O_WRONLY or O_RDWR were specified in flags, but this kernel version does not provide the O_TMPFILE functionality. I suggest another be listed: ENOENT The directory in which the file is to be created no longer exists. (Or the second case could be re-worded to cover that.) A simple test shows it can happen: $ mkdir foo $ cd foo $ rmdir ../foo $ touch bar touch: cannot touch 'bar': No such file or directory $ strace shows: openat(AT_FDCWD, "bar", O_WRONLY|O_CREAT|O_NOCTTY|O_NONBLOCK, 0666) = -1 ENOENT (No such file or directory) And POSIX requires openat(AT_FDCWD, ...) to be identical to open(...). O_CREAT was set, pathname included no directory component, and O_TMPFILE was not used--so ENOENT did not correspond to anything listed. The same result occurs if AT_FDCWD is replaced by a file descriptor for "foo"; in both cases, though, pathnames such as "../bar" still work. - Michael -- System Information: Debian Release: trixie/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.5.0-4-amd64 (SMP w/32 CPU threads; PREEMPT) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages manpages-dev depends on: ii manpages 6.03-2 manpages-dev recommends no packages. Versions of packages manpages-dev suggests: ii man-db [man-browser] 2.12.0-1 -- no debconf information signature.asc Description: PGP signature
Bug#1056780: openmsx: Source-less Windows binary in source package (and other packaging issues)
On 11/27/23 15:02, Manuel Bilderbeek wrote: On 27-11-2023 02:11, Aaron Rainbolt wrote: Alright, I have fully rebuilt the copyright file. I also ended up adding the source code for several releases of C-BIOS into the packaging. As this code is in the form of zipped files for the sake of size, it's not exactly practical to provide the new source package changes as a debdiff since debdiffs don't communicate binary file changes very well. So here's a .tar.gz of the new source package tree, detach-signed with my GPG key. https://github.com/ArrayBolt3/openmsx-packaging (I put it on GitHub since Gmail didn't want to let me send the package as a file attachment.) But why would you include the cbios sources in the openMSX package, as there is already a cbios package, which provides the binaries and has the sources as source package? Because openMSX vendors pre-built C-BIOS binaries, so therefore the source package must include the sources for it to be DFSG compliant. See https://www.debian.org/social_contract DFSG section 2. There is no build dependency on C-BIOS since C-BIOS binaries are provided in openMSX rather than sources. There is no binary dependency on C-BIOS either for the same reason. A user who downloads the source for the Debian openMSX package will not get all of the source, since there are multiple C-BIOS binaries with no source code. openMSX does point to the C-BIOS sources on SourceForge, but SourceForge isn't guaranteed to always exist. I do not think it is sufficient for some of the sources the user should have been given to just be "somewhere in the archive", leaving it up to the user to find them. Including C-BIOS source in the source package of openMSX ensures that even if all else fails (no upstream source, no way of pulling the C-BIOS source package for some reason) a user will always get the sources for the software they downloaded the source package of. (You probably will notice some superfluous-file-pattern warnings from Lintian when you build this - I do not understand why these are occurring as the file patterns it's griping about are *not* superfluous and don't appear to be overridden by any later statements in the copyright file. I suspect a Lintian bug here.) -- Kind regards, Manuel -- Aaron Rainbolt Lubuntu Developer Matrix: @arraybolt3:matrix.org IRC: arraybolt3 on irc.libera.chat GitHub: https://github.com/ArrayBolt3
Bug#1057009: consider updating crash to 8.0.4
reassign 1057009 crash found 1057009 8.0.3+ds1 thanks El 27/11/23 a las 21:59, Guillaume Morin escribió: Package: hello Version: 8.0.3+ds1 Severity: wishlist Hello, crash 8.0.4 has fixes for Linux 6.4+. Considering Linux 6.5 is availabe in sid, it would be useful to have it packaged. Thank you Guillaume.
Bug#1056780: openmsx: Source-less Windows binary in source package (and other packaging issues)
On 27-11-2023 02:11, Aaron Rainbolt wrote: Alright, I have fully rebuilt the copyright file. I also ended up adding the source code for several releases of C-BIOS into the packaging. As this code is in the form of zipped files for the sake of size, it's not exactly practical to provide the new source package changes as a debdiff since debdiffs don't communicate binary file changes very well. So here's a .tar.gz of the new source package tree, detach-signed with my GPG key. https://github.com/ArrayBolt3/openmsx-packaging (I put it on GitHub since Gmail didn't want to let me send the package as a file attachment.) But why would you include the cbios sources in the openMSX package, as there is already a cbios package, which provides the binaries and has the sources as source package? (You probably will notice some superfluous-file-pattern warnings from Lintian when you build this - I do not understand why these are occurring as the file patterns it's griping about are *not* superfluous and don't appear to be overridden by any later statements in the copyright file. I suspect a Lintian bug here.) -- Kind regards, Manuel
Bug#1057009: consider updating crash to 8.0.4
Package: hello Version: 8.0.3+ds1 Severity: wishlist Hello, crash 8.0.4 has fixes for Linux 6.4+. Considering Linux 6.5 is availabe in sid, it would be useful to have it packaged. Thank you Guillaume. -- Guillaume Morin
Bug#1057008: php-phpseclib3: CVE-2023-49316
Source: php-phpseclib3 Version: 3.0.33-1 Severity: important Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for php-phpseclib3. CVE-2023-49316[0]: | In Math/BinaryField.php in phpseclib before 3.0.34, excessively | large degrees can lead to a denial of service. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2023-49316 https://www.cve.org/CVERecord?id=CVE-2023-49316 [1] https://github.com/phpseclib/phpseclib/commit/964d78101a70305df33f442f5490f0adb3b7e77f Please adjust the affected versions in the BTS as needed. Regards, Salvatore
Bug#1057007: libconfig-model-tkui-perl: autopkgtest for libconfig-model-itself-perl fails with libconfig-model-tkui-perl 1.377
Package: libconfig-model-tkui-perl
Version: 1.377-1
Severity: normal
Tags: upstream
X-Debbugs-Cc: Dominique Dumont
Hi dod,
last week I updated libconfig-model-tkui-perl from 1.376-1 to 1.377-1
and now libconfig-model-itself-perl fails one of its autopkgtests, as
can be seen on https://tracker.debian.org/pkg/libconfig-model-tkui-perl
Relevant part from the test log at
https://ci.debian.net/data/autopkgtest/testing/amd64/libc/libconfig-model-itself-perl/40239936/log.gz
...
188s t/itself-editor.t ..
188s ok 1 - compiled
188s # You can play with the widget if you run the test with '--show' parameter
188s # Running tests in wr_root/itself-editor
188s ok 2 - loaded Master model
188s ok 3 - created master_model instance
188s ok 4 - loaded some data in master_model instance
188s ok 5 - Read Itself::Model and created instance
188s ok 6 - Read all models in data dir
188s ok 7 - window launched
188s ok 8 - Tk UI step 0 view done
188s ok 9 - Tk UI step 1 open_class done
188s ok 10 - Tk UI step 2 open_instance done
188s ok 11 - Tk UI step 3 save done
188s ok 12 - Tk UI step 4 open test window done
188s ok 13 - Tk UI step 5 reopen test window done
188s ok 14 - Tk UI step 6 exit done
188s # testing memory cycles. Please wait...
188s not ok 15 - memory cycles
188s
188s # Failed test 'memory cycles'
188s # at t/itself-editor.t line 155.
188s # Cycle #1
188s # Config::Model A->{instances} => %B
188s # %B->{itself_instance} => Config::Model::Instance C
188s # Config::Model::Instance C->{on_change_cb} => &D
188s # closure &D, $cw => $E
188s # $E => Config::Model::Itself::TkEditUI F
188s # Config::Model::Itself::TkEditUI F->{id} => Tk::After::Cancelled G
188s # Tk::After::Cancelled G->[0] => Config::Model::Itself::TkEditUI F
188s # Cycle #2
188s # Config::Model A->{instances} => %B
188s # %B->{itself_instance} => Config::Model::Instance C
188s # Config::Model::Instance C->{on_change_cb} => &D
188s # closure &D, $cw => $E
188s # $E => Config::Model::Itself::TkEditUI F
188s # Config::Model::Itself::TkEditUI F->{id} => Tk::After::Cancelled G
188s # Tk::After::Cancelled G->[4] => Tk::Callback H
188s # Tk::Callback H->[0] => &I
188s # closure &I, $cw => $J
188s # $J => Config::Model::Itself::TkEditUI F
188s # Cycle #3
188s # Config::Model A->{instances} => %B
188s # %B->{itself_instance} => Config::Model::Instance C
188s # Config::Model::Instance C->{on_change_cb} => &D
188s # closure &D, $cw => $E
188s # $E => Config::Model::Itself::TkEditUI F
188s # Config::Model::Itself::TkEditUI F->{instance} =>
Config::Model::Instance C
188s # Cycle #4
188s # Config::Model A->{instances} => %B
188s # %B->{itself_instance} => Config::Model::Instance C
188s # Config::Model::Instance C->{on_change_cb} => &D
188s # closure &D, $cw => $E
188s # $E => Config::Model::Itself::TkEditUI F
188s # Config::Model::Itself::TkEditUI F->{store_sub} => &K
188s # closure &K, $rw_obj => $L
188s # $L => Config::Model::Itself M
188s # Config::Model::Itself M->{config_model} => Config::Model A
188s # Cycle #5
188s # Config::Model A->{instances} => %B
188s # %B->{itself_instance} => Config::Model::Instance C
188s # Config::Model::Instance C->{on_change_cb} => &D
188s # closure &D, $cw => $E
188s # $E => Config::Model::Itself::TkEditUI F
188s # Config::Model::Itself::TkEditUI F->{store_sub} => &K
188s # closure &K, $rw_obj => $L
188s # $L => Config::Model::Itself M
188s # Config::Model::Itself M->{meta_instance} => Config::Model::Instance C
188s # Cycle #6
188s # Config::Model A->{instances} => %B
188s # %B->{itself_instance} => Config::Model::Instance C
188s # Config::Model::Instance C->{on_change_cb} => &D
188s # closure &D, $cw => $E
188s # $E => Config::Model::Itself::TkEditUI F
188s # Config::Model::Itself::TkEditUI F->{test_model} => Config::Model N
188s # Config::Model N->{instances} => %O
188s # %O->{MasterModel} => Config::Model::Instance P
188s # Config::Model::Instance P->{on_change_cb} => &Q
188s # closure &Q, $cw => $R
188s # $R => Config::Model::TkUI S
188s # Config::Model::TkUI S->{instance} => Config::Model::Instance P
188s # Cycle #7
188s # Config::Model A->{instances} => %B
188s # %B->{itself_instance} => Config::Model::Instance C
188s # Config::Model::Instance C->{on_change_cb} => &D
188s # closure &D, $cw => $E
188s # $E => Config::Model::Itself::TkEditUI F
188s # Config::Model::Itself::TkEditUI F->{test_widget} =>
Config::Model::TkUI S
188s # Config::Model::TkUI S->{instance} => Config::Model::Instance P
188s # Config::Model::Instance P->{on_change_cb} => &Q
188s # closure &Q, $cw => $R
188s # $R => Config::Model::TkUI S
188s 1..15
188s # Looks like you failed 1 test of 15.
188s Dubious, test returned 1 (wstat 256, 0x100)
188s Failed 1/15 subtests
I'm sorry I don't even have an i
Bug#1006737: Fwd: ITP: kind -- Tool for running local Kubernetes clusters using Docker container
* Package name : kind Version : 0.20.0 Upstream Author : Kubernetes SIGs * URL : https://github.com/kubernetes-sigs/kind * License : Apache-2.0 * Programming Lang: Go * Description : Tool for running local Kubernetes clusters using Docker container "nodes". kind is a tool for running local Kubernetes clusters using Docker container "nodes". kind was primarily designed for testing Kubernetes itself, but may be used for local development or CI. . (/site/static/images/kind-create-cluster.png) . kind consists of: . * Go packages (/pkg) implementing cluster creation (/pkg/cluster), image build (/pkg/build), etc. * A command line interface (kind (/main.go)) built on these packages. * Docker image(s) (/images) written to run systemd, Kubernetes, etc. * kubetest (https://github.com/kubernetes/test- infra/tree/master/kubetest) integration also built on these packages (WIP) . kind bootstraps each "node" with kubeadm (https://kubernetes.io/docs/reference/setup-tools/kubeadm/kubeadm/). For more details see the design documentation (https://kind.sigs.k8s.io/docs/design/initial).
Bug#1006737: ITP: kind -- Tool for running local Kubernetes clusters using Docker container
*Package name : kind Version : 0.20.0 Upstream Author : Kubernetes SIGs * URL : https://github.com/kubernetes-sigs/kind * License : Apache-2.0 * Programming Lang: Go * Description : Tool for running local Kubernetes clusters using Docker container "nodes". kind is a tool for running local Kubernetes clusters using Docker container "nodes". kind was primarily designed for testing Kubernetes itself, but may be used for local development or CI. . (/site/static/images/kind-create-cluster.png) . kind consists of: . * Go packages (/pkg) implementing cluster creation (/pkg/cluster), image build (/pkg/build), etc. * A command line interface (kind (/main.go)) built on these packages. * Docker image(s) (/images) written to run systemd, Kubernetes, etc. * kubetest (https://github.com/kubernetes/test- infra/tree/master/kubetest) integration also built on these packages (WIP) . kind bootstraps each "node" with kubeadm (https://kubernetes.io/docs/reference/setup-tools/kubeadm/kubeadm/). For more details see the design documentation (https://kind.sigs.k8s.io/docs/design/initial).
Bug#1057000: Broken OPENSSL_init_ssl
Control: severity -1 minor Control: tags -1 wontfix Control: close -1 On Mon, 27 Nov 2023 20:39:25 +0100 Ansgar wrote: > On Mon, 27 Nov 2023 19:11:44 +0100 Klaus Ethgen > wrote: > > merged-usr: no > > This is not supported by Debian and random breakage may occur. > Please only submit bugs that are reproducible on Debian and happen in a > supported configuration (or at least not in an explicitly not supported > configuration). > > This might be the case here (who knows). Or it might be due to Devuan's > mirrors. Or other changes introduced by Devuan. So the report should > probably be closed. > > > Versions of packages apt-listchanges depends on: > > ii apt 2.7.6devuan2 > > Please report Devuan bugs to Devuan's bug tracker. Debian cannot do > technical support for derivative distributions. Indeed, not only this is not the right package, but also this is not the right bug tracker for this. For more information, please consult: https://wiki.debian.org/UsrMerge Closing as not actionable. -- Kind regards, Luca Boccassi signature.asc Description: This is a digitally signed message part
Bug#1057002: init cannot respawn mingetty after update
Additional note: My system was migrated from etch up to current version and is not at all able to run with usrmerge. Regards Klaus -- Klaus Ethgen http://www.ethgen.ch/ pub 4096R/4E20AF1C 2011-05-16Klaus Ethgen Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C signature.asc Description: PGP signature
Bug#1057002: init cannot respawn mingetty after update
Hi, Am Mo den 27. Nov 2023 um 20:15 schrieb Chris Hofstaedtler: > > After the recent update, init runns cracy trying to run mingetty. > > Nov 27 20:00:01 ikki init: cannot execute "/sbin/mingetty" > [..] > > > merged-usr: no > > This is not a bug in mingetty, but your installation is not in a > supported state. Once you get your install fixed by usrmerge, it > will work. I cannot and will not ever use usrmerge as it is broken by design! Regards Klaus -- Klaus Ethgen http://www.ethgen.ch/ pub 4096R/4E20AF1C 2011-05-16Klaus Ethgen Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C signature.asc Description: PGP signature
Bug#1053066: Additional information
Dear Maintainers, Would it be possible to consider a merge request[1] that addresses this issue? Best Regards, Vladimir. [1] https://salsa.debian.org/java-team/netty/-/merge_requests/2
Bug#1057005: linux-image-6.1.0-13-amd64: Kernel Oops in nfs4_do_reclaim, which exits with irqs disabled
Package: src:linux Version: 6.1.55-1 Severity: important X-Debbugs-Cc: jamescope...@gmail.com Dear Maintainer, Hi, I have experienced an issue where my client lost access to an NFS server for a period of around 15 minutes, then immediately following server recovery, I experienced a kernel oops on the client (details below). What made this more severe was the fact that nfs4_do_reclaim exited with irqs disabled, which is possibly what resulted in a number of "rcu_preempt self-detected stall on CPU" errors and a very unstable system, leaving me no choice but to hit the reset button. BUG: unable to handle page fault for address: fff8 #PF: supervisor read access in kernel mode #PF: error_code(0x) - not-present page PGD 37de15067 P4D 37de15067 PUD 37de17067 PMD 0 Oops: [#1] PREEMPT SMP NOPTI CPU: 9 PID: 4154600 Comm: 192.168.253.7-m Not tainted 6.1.0-13-amd64 #1 Debian 6.1.55-1 Hardware name: System manufacturer System Product Name/PRIME X570-PRO, BIOS 3405 02/01/2021 RIP: 0010:complete+0x38/0x80 Code: 89 fb 4c 89 e7 e8 c8 d8 93 00 48 89 c5 8b 03 83 f8 ff 74 05 83 c0 01 89 03 48 8b 53 10 48 8d 43 10 48 39 c2 74 2e 48 8b 5b 10 <48> 8b 7b f8 e8 df cc fd ff 48 89 df e8 17 bd 43 00 84 c0 7 4 0e 48 RSP: 0018:b78d1e55bdc0 EFLAGS: 00010013 RAX: 9df24a45f2f8 RBX: RCX: RDX: RSI: RDI: 0001 RBP: 0247 R08: 9defc1f84040 R09: 9dee419a5910 R10: 0001 R11: 0001 R12: 9df24a45f2f0 R13: c12613a0 R14: 9dee5532d820 R15: 9defc1f84000 FS: () GS:9df54ec4() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: fff8 CR3: 0007eaf16000 CR4: 00350ee0 Call Trace: ? __die_body.cold+0x1a/0x1f ? page_fault_oops+0xd2/0x2b0 ? exc_page_fault+0xca/0x170 ? asm_exc_page_fault+0x22/0x30 ? complete+0x38/0x80 nfs4_do_reclaim+0x5b6/0x810 [nfsv4] nfs4_run_state_manager+0x882/0xab0 [nfsv4] ? __schedule+0x359/0xa20 ? preempt_count_add+0x6a/0xa0 ? nfs4_do_reclaim+0x810/0x810 [nfsv4] kthread+0xe9/0x110 ? kthread_complete_and_exit+0x20/0x20 ret_from_fork+0x22/0x30 Modules linked in: sd_mod uas usb_storage tcp_diag udp_diag inet_diag veth vhost_net vhost vhost _iotlb tun macvtap macvlan tap xt_CHECKSUM ipt_REJECT nf_reject_ipv4 cpufreq_powersave cpufreq_u serspace cpufreq_ondemand cpufreq_conservative rpcsec_gss_krb5 auth_rpcgss nfsv4 dns_resolver nf s lockd grace fscache netfs nft_masq sunrpc bridge nft_chain_nat xt_MASQUERADE xt_nat nf_nat xt_ multiport xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_tcpudp nft_compat nf_tables libcrc32c nfnetlink binfmt_misc intel_rapl_msr intel_rapl_common amd64_edac edac_mce_amd kvm_am d nouveau kvm irqbypass ghash_clmulni_intel sha512_ssse3 video sha512_generic drm_display_helper asus_ec_sensors cec evdev aesni_intel rc_core crypto_simd pl2303 drm_ttm_helper cryptd ttm usbs erial rapl drm_kms_helper sp5100_tco ccp pcspkr wmi_bmof mxm_wmi watchdog k10temp button acpi_cp ufreq sg nct6775 nct6775_core hwmon_vid 8021q garp stp mrp llc drm fuse loop dm_mod efi_pstore c onfigfs efivarfs ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 crc32c_generic mlx4_ib ib_uverbs ib_core mlx4_en hid_g eneric usbhid hid sr_mod cdrom ahci libahci xhci_pci xhci_hcd nvme libata mlx4_core crc32_pclmul nvme_core crc32c_intel usbcore igb scsi_mod t10_pi i2c_piix4 crc64_rocksoft crc64 i2c_algo_bit crc_t10dif scsi_common usb_common crct10dif_generic dca crct10dif_pclmul crct10dif_common wmi CR2: fff8 ---[ end trace ]--- RIP: 0010:complete+0x38/0x80 Code: 89 fb 4c 89 e7 e8 c8 d8 93 00 48 89 c5 8b 03 83 f8 ff 74 05 83 c0 01 89 03 48 8b 53 10 48 8d 43 10 48 39 c2 74 2e 48 8b 5b 10 <48> 8b 7b f8 e8 df cc fd ff 48 89 df e8 17 bd 43 00 84 c0 74 0e 48 RSP: 0018:b78d1e55bdc0 EFLAGS: 00010013 RAX: 9df24a45f2f8 RBX: RCX: RDX: RSI: RDI: 0001 RBP: 0247 R08: 9defc1f84040 R09: 9dee419a5910 R10: 0001 R11: 0001 R12: 9df24a45f2f0 R13: c12613a0 R14: 9dee5532d820 R15: 9defc1f84000 FS: () GS:9df54ec4() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: fff8 CR3: 0007eaf16000 CR4: 00350ee0 note: 192.168.253.7-m[4154600] exited with irqs disabled note: 192.168.253.7-m[4154600] exited with preempt_count 2 -- Package-specific info: ** Version: Linux version 6.1.0-13-amd64 (debian-ker...@lists.debian.org) (gcc-12 (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC Debian 6.1.55-1 (2023-09-29) ** Command line: BOOT_IMAGE=/vmlinuz-6.1.0-13-amd64 root=UUID=dc88b740-868e-4b8f-9e70-2a5d47104b70 ro ipv6.disable=1 nomodeset clocksource=hpet retbleed=off spec_rstac
Bug#1034800: lualib5.4 is missing expected symbols
control: tags -1 patch
grep LUALIB_API src/*.h >> list
grep LUAMOD_API src/*.h >> list
grep LUA_API src/*.h -R >> list
cat list | awk '{ print $3 }' > list2
cat list2 |sort > list
and then I diffd the list with debian/version-script
I found then 5 missing symbols:
lua_closeslot
lua_closethread
luaL_addgsub
lua_setcstacklimit
lua_State
diff attached.
On Mon, 24 Apr 2023 20:25:51 +0200 =?UTF-8?Q?Jan_Dr=c3=b6gehoff?=
wrote:
Package: liblua5.4
Version: 5.4.4-3
liblua5.4.so.0.0.0 is not exporting symbols that are expected to be present in
Lua 5.4.
Some examples:
- luaL_addgsub
- lua_closeslot
- lua_setcstacklimit
and likely many more
The header file from liblua5.4-dev still define those functions, leading to
undefined references.
diff -Nru lua5.4-5.4.6/debian/version-script lua5.4-5.4.6/debian/version-script
--- lua5.4-5.4.6/debian/version-script 2023-06-14 14:52:06.0 +0200
+++ lua5.4-5.4.6/debian/version-script 2023-11-27 16:23:09.0 +0100
@@ -6,6 +6,8 @@
lua_callk;
lua_checkstack;
lua_close;
+ lua_closeslot;
+ lua_closethread;
lua_compare;
lua_concat;
lua_copy;
@@ -35,6 +37,7 @@
lua_isstring;
lua_isuserdata;
lua_isyieldable;
+ luaL_addgsub;
lua_len;
lua_load;
lua_newstate;
@@ -66,6 +69,7 @@
lua_resume;
lua_rotate;
lua_setallocf;
+ lua_setcstacklimit;
lua_setfield;
lua_setglobal;
lua_sethook;
@@ -77,6 +81,7 @@
lua_settop;
lua_setupvalue;
lua_setwarnf;
+ lua_State;
lua_status;
lua_stringtonumber;
lua_toboolean;
OpenPGP_signature.asc
Description: OpenPGP digital signature
Bug#1056616: firefox: Firefox tab freeze when using BigBlueButton
Hi! On Mon, Nov 27, 2023 at 4:45 PM Sylvestre Ledru wrote: > Do you have RFP (Resist Fingerprinting) enabled? It's enabled (Enhanced Tracking Protection is on Strict) Best regards, Nelson
Bug#1025165: No opus transcoding available after asterisk install
> Adding "ADDONS_ENABLE += codec_opus_open_source" to debian/rules (e.g. > near the other ADDONS_ENABLE lines) addresses this issue. I've verified > that "core show translation" shows opus in the matrix after that. I'm > not sure why menuselect doesn't enable it by default. This same issue was reported in Ubuntu at https://bugs.launchpad.net/debian/+source/asterisk/+bug/2044135. However, I see the following entry in debian/changelog: * stop set obsolete menuselect option codec_opus_open_source from version 1:16.23.0~dfsg+~2.10-1. I wonder what the story behind the removal is. Moreover, the upstream readme file, at under Xopus/README.md in the source package says that "Opus is not only supported for pass-through but can be transcoded as well. This allows you to translate to/from other audio codecs [...] This can be achieved by enabling codec_opus via make menuselect". So I wonder if that is the actual identifier to be enabled (i.e., s/codec_opus_open_source/codec_opus/). -- Athos Ribeiro
Bug#1057000: Broken OPENSSL_init_ssl
On Mon, 27 Nov 2023 19:11:44 +0100 Klaus Ethgen wrote: > merged-usr: no This is not supported by Debian and random breakage may occur. Please only submit bugs that are reproducible on Debian and happen in a supported configuration (or at least not in an explicitly not supported configuration). This might be the case here (who knows). Or it might be due to Devuan's mirrors. Or other changes introduced by Devuan. So the report should probably be closed. > Versions of packages apt-listchanges depends on: > ii apt 2.7.6devuan2 Please report Devuan bugs to Devuan's bug tracker. Debian cannot do technical support for derivative distributions. Ansgar
Bug#1056616: firefox: Firefox tab freeze when using BigBlueButton
Hello Le 27/11/2023 à 19:50, Nelson A. de Oliveira a écrit : On Mon, Nov 27, 2023 at 10:24 AM Vincent Blut wrote: Seems like the Dark Reader extension is the culprit on my side. I can't seem to be able to reproduce the issue when I disable it. Probably yes: https://github.com/darkreader/darkreader/issues/11943 But Firefox should also not allow an extension to bring it to its knees like this. Do you have RFP (Resist Fingerprinting) enabled? Thanks Sylvestre
Bug#1057004: gcc-13: hurd-amd64 support
Package: gcc-13
Version: 13.2.0-7
Severity: important
Tags: patch
X-Debbugs-Cc: debian-h...@lists.debian.org
User: debian-h...@lists.debian.org
Usertags: hurd
Hello,
The attached patch adds support for hurd-amd64, could you apply it?
The part in hurd-amd64.diff comes from the upstream master commits,
which will thus be included in gcc 14.
The parts in hurd-multiarch.diff and hurd-multilib-multiarch.diff are
for long term, like gcc-multiarch.diff and gcc-multilib-multiarch.diff
for other archs.
Thanks,
Samuel
-- System Information:
Debian Release: trixie/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'unreleased'),
(500, 'testing-debug'), (500, 'stable-security'), (500, 'stable-debug'), (500,
'oldstable-proposed-updates-debug'), (500, 'oldstable-proposed-updates'), (500,
'oldoldstable-proposed-updates'), (500, 'oldoldstable'), (500,
'buildd-unstable'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1,
'experimental-debug'), (1, 'buildd-experimental'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, arm64
Kernel: Linux 6.5.0-1-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.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 gcc-13 depends on:
ii binutils 2.41-7
ii cpp-13 13.2.0-7
ii gcc-13-base13.2.0-7
ii libc6 2.37-12+b1
ii libcc1-0 13.2.0-7
ii libgcc-13-dev 13.2.0-7
ii libgcc-s1 13.2.0-7
ii libgmp10 2:6.3.0+dfsg-2
ii libisl23 0.26-3
ii libmpc31.3.1-1
ii libmpfr6 4.2.1-1
ii libstdc++6 13.2.0-7
ii libzstd1 1.5.5+dfsg2-2
ii zlib1g 1:1.2.13.dfsg-3
Versions of packages gcc-13 recommends:
ii libc6-dev 2.37-12+b1
Versions of packages gcc-13 suggests:
ii gcc-13-doc 13.2.0-1
pn gcc-13-locales
ii gcc-13-multilib 13.2.0-7
-- no debconf information
--
Samuel
---
Pour une évaluation indépendante, transparente et rigoureuse !
Je soutiens la Commission d'Évaluation de l'Inria.
diff --git a/debian/patches/hurd-amd64.diff b/debian/patches/hurd-amd64.diff
new file mode 100644
index 000..e7288ea
--- /dev/null
+++ b/debian/patches/hurd-amd64.diff
@@ -0,0 +1,127 @@
+commit 5707e9db9c398d311defc80c5b7822c9a07ead60
+Author: Samuel Thibault
+Date: Sat May 6 13:50:36 2023 +0200
+
+hurd: Add multilib paths for gnu-x86_64
+
+We need the multilib paths in gcc to find e.g. glibc crt files on
+Debian. This is essentially based on t-linux64 version.
+
+gcc/ChangeLog:
+
+* config/i386/t-gnu64: New file.
+* config.gcc [x86_64-*-gnu*]: Add i386/t-gnu64 to
+tmake_file.
+
+commit c768917402d4cba69a92c737e56e177f5b8ab0df
+Author: Samuel Thibault
+Date: Sat May 6 13:55:44 2023 +0200
+
+hurd: Ad default-pie and static-pie support
+
+This fixes the Hurd spec in the default-pie case, and adds static-pie
+support.
+
+gcc/ChangeLog:
+
+* config/i386/gnu.h: Use PIE_SPEC, add static-pie case.
+* config/i386/gnu64.h: Use PIE_SPEC, add static-pie case.
+
+diff --git a/src/gcc/config.gcc b/src/gcc/config.gcc
+index 3000379cafc..e62849c1230 100644
+--- a/src/gcc/config.gcc
b/src/gcc/config.gcc
+@@ -5973,6 +5973,9 @@ case ${target} in
+ visium-*-*)
+ target_cpu_default2="TARGET_CPU_$with_cpu"
+ ;;
++ x86_64-*-gnu*)
++ tmake_file="$tmake_file i386/t-gnu64"
++ ;;
+ esac
+
+ t=
+diff --git a/src/gcc/config/i386/t-gnu64 b/src/gcc/config/i386/t-gnu64
+new file mode 100644
+index 000..23ee6823d65
+--- /dev/null
b/src/gcc/config/i386/t-gnu64
+@@ -0,0 +1,38 @@
++# Copyright (C) 2002-2023 Free Software Foundation, Inc.
++#
++# This file is part of GCC.
++#
++# GCC is free software; you can redistribute it and/or modify
++# it under the terms of the GNU General Public License as published by
++# the Free Software Foundation; either version 3, or (at your option)
++# any later version.
++#
++# GCC is distributed in the hope that it will be useful,
++# but WITHOUT ANY WARRANTY; without even the implied warranty of
++# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
++# GNU General Public License for more details.
++#
++# You should have received a copy of the GNU General Public License
++# along with GCC; see the file COPYING3. If not see
++#
Bug#1057003: RM: linux-wlan-ng -- RoQA; effectively unmaintained; not in (old)stable
Package: ftp.debian.org Severity: normal User: ftp.debian@packages.debian.org Usertags: remove X-Debbugs-Cc: linux-wlan...@packages.debian.org Dear ftpmasters, please remove linux-wlan-ng, which are utilities for prims2 cards, from contrib. This package hasn't been in any release since 2016, so it missed oldstable and stable. It has seen a single upload since being removed, in 2016-09. This didn't seem to improve the situation. Thanks, Chris
Bug#1032533: liblua5.4-dev: 0003-extern_C.patch does not make sense, please remove
control: fixed -1 5.4.6-1 control: close -1 thanks On Wed, 08 Mar 2023 14:44:25 -0500 Jackson wrote: Package: liblua5.4-dev Version: 5.4.4-3 Severity: normal X-Debbugs-Cc: j.p.b...@zoho.com Hi, This patchfile undermines that Lua can be built as C++ to manage unwinding exceptions; according to the date, it has been in the Debian Lua repository for over seven years. For example, future releases of MAME (package: mame) will break using USE_SYSTEM_LUA_LIB if this fallacy not resolved, since they link their own copy. Was the patchfile created to overcome package building errors? If so, those should have been fixed as their own individual patches. Sincerely, Jackson -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.2.2-x64v2-xanmod1 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages liblua5.4-dev depends on: ii libc6-dev [libc-dev] 2.36-8 ii liblua5.4-0 5.4.4-3 ii libreadline-dev 8.2-1.3 Versions of packages liblua5.4-dev recommends: ii libtool-bin 2.4.7-5 ii pkg-config1.8.1-1 ii pkgconf [pkg-config] 1.8.1-1 liblua5.4-dev suggests no packages. -- no debconf information OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1056998: cdrom: Installation media changes after booting it
Hi, Ram Reddy wrote: > [...] usb drive [...] debian-12.2.0-amd64-netinst.iso [...] > [...] Integrity Test section [...] > ./boot/grub/efi.img failed the MD5 checksum verification. Your installation > media or this file may have been corrupted. > [...] > It was always byte 2303211, line 21165 which changed. I'd say that corruption of ISO image or USB is quite unlikely. It rather looks like some change was made to the FAT filesystem in the EFI partition by the parts of the installer which ran in your experiments. (I expect EFI firmware not to manipulate that filesystem ...) The EFI partition of this particular ISO begins at byte 2291712. The alteration thus happened 11499 bytes inside that partition and its filesystem. In the original ISO i see a sequence of 0-bytes there. It would be interesting to check whether any errors get reported if the ISO is presented on a read-only CD or DVD instead of a writable USB stick. (To be absolutely read-only it would have to be CD-R, unformatted CD-RW, DVD+R, DVD-R, or unformatted DVD-RW. The others can be overwritten without burn program.) Explanation why the file in the read-only ISO filesystem is reported as being altered: The partition shares its block range with the ISO file /boot/grub/efi.img which is mentioned in the ISO file /md5sum.txt . So the integrity check detects the difference between recorded MD5 and the MD5 of the altered FAT filesystem image file /boot/grub/efi.img. Have a nice day :) Thomas
Bug#1056997: libbmusb6: Let udev.pc decide where to install rules
Hi, * Steinar H. Gunderson [231127 19:16]: > On Mon, Nov 27, 2023 at 06:57:05PM +0100, Chris Hofstaedtler wrote: > Your patch is modifying debian/patches/debian-multiarch.diff, but this has > nothing to do with multiarch, right? It should just be a completely separate > patch, Yes, sorry I overlooked the fact that the existing patch was -just- for multiarch. > which should go upstream? It certainly can! Best, Chris
Bug#1057002: init cannot respawn mingetty after update
Control: severity -1 normal Control: tags -1 = wontfix * Klaus Ethgen [231127 19:13]: > Package: mingetty > Version: 1.08-5 > Severity: grave > > After the recent update, init runns cracy trying to run mingetty. > Nov 27 20:00:01 ikki init: cannot execute "/sbin/mingetty" [..] > merged-usr: no This is not a bug in mingetty, but your installation is not in a supported state. Once you get your install fixed by usrmerge, it will work. Chris
Bug#1057001: dh-debputy: HTML documentation is compressed
On 2023-11-27 19:54 +0100, Sven Joachim wrote:
> Package: dh-debputy
> Version: 0.1.9
> Severity: normal
>
> I was playing around with dh-debputy and tried to convert xterm to it.
> That seems to mostly work, however two HTML files are now compressed:
>
> ,
> | $ debdiff /var/cache/apt/archives/xterm_388-1_amd64.deb
> ../xterm_388-1_amd64.deb
> | [The following lists of changes regard files as different if they have
> | different names, permissions or owners.]
> |
> | Files in second .deb but not in first
> | -
> | -rw-r--r-- root/root /usr/share/doc-base/xterm.ctlseqs
> | -rw-r--r-- root/root /usr/share/doc-base/xterm.faq
> | -rw-r--r-- root/root /usr/share/doc/xterm/xterm.faq.html.gz
> | -rw-r--r-- root/root /usr/share/doc/xterm/xterm.log.html.gz
> |
> | Files in first .deb but not in second
> | -
> | -rw-r--r-- root/root /usr/share/doc-base/xterm.xterm-ctlseqs
> | -rw-r--r-- root/root /usr/share/doc-base/xterm.xterm-faq
> | -rw-r--r-- root/root /usr/share/doc/xterm/xterm.faq.html
> | -rw-r--r-- root/root /usr/share/doc/xterm/xterm.log.html
> |
> | Control files: lines which differ (wdiff format)
> |
> | Installed-Size: [-2438-] {+1710+}
> `
>
> It seems that the list of extensions not to compress was converted
> incorrectly from dh_compress, for the latter ignores *.htm* files,
> except for changelog.html.
Hopefully this is easy enough to reproduce and to fix, but if you want
to try yourself with xterm, I set up a branch on Salsa:
https://salsa.debian.org/joachim-guest/xterm/-/tree/debputy
Cheers,
Sven
Bug#1057002: init cannot respawn mingetty after update
Package: mingetty Version: 1.08-5 Severity: grave After the recent update, init runns cracy trying to run mingetty. Nov 27 20:00:01 ikki init: cannot execute "/sbin/mingetty" Nov 27 20:00:01 ikki init: cannot execute "/sbin/mingetty" Nov 27 20:00:01 ikki init: cannot execute "/sbin/mingetty" Nov 27 20:00:01 ikki init: cannot execute "/sbin/mingetty" Nov 27 20:00:01 ikki init: cannot execute "/sbin/mingetty" Nov 27 20:00:01 ikki init: cannot execute "/sbin/mingetty" Nov 27 20:00:01 ikki init: Id "4" respawning too fast: disabled for 5 minutes Nov 27 20:00:01 ikki init: cannot execute "/sbin/mingetty" Nov 27 20:00:01 ikki init: Id "3" respawning too fast: disabled for 5 minutes Nov 27 20:00:01 ikki init: Id "5" respawning too fast: disabled for 5 minutes Nov 27 20:00:01 ikki init: cannot execute "/sbin/mingetty" Nov 27 20:00:01 ikki init: Id "2" respawning too fast: disabled for 5 minutes Nov 27 20:00:01 ikki init: Id "6" respawning too fast: disabled for 5 minutes -- System Information: Debian Release: trixie/sid APT prefers experimental APT policy: (1, 'experimental') merged-usr: no Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.38 (SMP w/8 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_CPU_OUT_OF_SPEC, TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1), LANGUAGE=de_DE:de:en Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages mingetty depends on: ii libc6 2.37-12 mingetty recommends no packages. mingetty suggests no packages. -- no debconf information -- Klaus Ethgen http://www.ethgen.ch/ pub 4096R/4E20AF1C 2011-05-16Klaus Ethgen Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C signature.asc Description: PGP signature
Bug#1056997: libbmusb6: Let udev.pc decide where to install rules
On Mon, Nov 27, 2023 at 06:57:05PM +0100, Chris Hofstaedtler wrote: > your package ships a udev rules file in /lib/udev/rules.d, and currently > hard-codes this path. As part of the UsrMerge effort[1], the install > path for udev rules must and will change soon. To pick up this change > with a binNMU, your package can use pkg-config to determine the install > location. > > I'm attaching a patch to implement this. Hi. Your patch is modifying debian/patches/debian-multiarch.diff, but this has nothing to do with multiarch, right? It should just be a completely separate patch, which should go upstream? /* Steinar */ -- Homepage: https://www.sesse.net/
Bug#1057001: dh-debputy: HTML documentation is compressed
Package: dh-debputy
Version: 0.1.9
Severity: normal
I was playing around with dh-debputy and tried to convert xterm to it.
That seems to mostly work, however two HTML files are now compressed:
,
| $ debdiff /var/cache/apt/archives/xterm_388-1_amd64.deb
../xterm_388-1_amd64.deb
| [The following lists of changes regard files as different if they have
| different names, permissions or owners.]
|
| Files in second .deb but not in first
| -
| -rw-r--r-- root/root /usr/share/doc-base/xterm.ctlseqs
| -rw-r--r-- root/root /usr/share/doc-base/xterm.faq
| -rw-r--r-- root/root /usr/share/doc/xterm/xterm.faq.html.gz
| -rw-r--r-- root/root /usr/share/doc/xterm/xterm.log.html.gz
|
| Files in first .deb but not in second
| -
| -rw-r--r-- root/root /usr/share/doc-base/xterm.xterm-ctlseqs
| -rw-r--r-- root/root /usr/share/doc-base/xterm.xterm-faq
| -rw-r--r-- root/root /usr/share/doc/xterm/xterm.faq.html
| -rw-r--r-- root/root /usr/share/doc/xterm/xterm.log.html
|
| Control files: lines which differ (wdiff format)
|
| Installed-Size: [-2438-] {+1710+}
`
It seems that the list of extensions not to compress was converted
incorrectly from dh_compress, for the latter ignores *.htm* files,
except for changelog.html.
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.1.63-nouveau (SMP w/2 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)
Versions of packages dh-debputy depends on:
ii debhelper13.11.8
ii perl 5.36.0-10
ii python3 3.11.4-5+b1
ii python3-colorlog 6.7.0-1
ii python3-debian 0.1.49
ii python3-ruamel.yaml 0.17.21-1
Versions of packages dh-debputy recommends:
ii python3-argcomplete 3.1.4-1
dh-debputy suggests no packages.
-- no debconf information
Bug#1056616: firefox: Firefox tab freeze when using BigBlueButton
On Mon, Nov 27, 2023 at 10:24 AM Vincent Blut wrote: > Seems like the Dark Reader extension is the culprit on my side. I can't seem > to > be able to reproduce the issue when I disable it. Probably yes: https://github.com/darkreader/darkreader/issues/11943 But Firefox should also not allow an extension to bring it to its knees like this.
Bug#1057000: Broken OPENSSL_init_ssl
Those errors aren't coming from apt-listchanges. I don't know where they're coming from, all I can tell you is it's something else apt is calling, not apt-listchanges. There's zero ruby code in apt-listchanges. On November 27, 2023 1:11:44 PM EST, Klaus Ethgen wrote: >Package: apt-listchanges >Version: 3.27 >Severity: important > >After recent updates, apt-listchanges is somewhat broken: > Laden der Fehlerberichte ? 0% Fehlgeschlagen > Das Laden der Fehlerberichte vom Server ist mit folgender Fehlermeldung > fehlgeschlagen: > E: OPENSSL_init_ssl > Es könnte an Ihrem inaktiven Netzwerk oder an einem fehlerhaften > Proxy-Server liegen oder der BTS-Server ist nicht aktiv. Überprüfen Sie die > Netzwerkkonfiguration und versuchen Sie es erneut > Soll erneut versucht werden, die Informationen zu dem Fehler > herunterzuladen? [Y/n] > Jeweils ein Paket? [Y/n] > Jeweils ein Fehlerbericht? [Y/n] > > /usr/share/rubygems-integration/all/gems/soap4r-ruby1.9-2.0.5/lib/soap/streamHandler.rb:24: > warning: already initialized constant > SOAP::StreamHandler::RUBY_VERSION_STRING > > /usr/share/rubygems-integration/all/gems/soap4r-ruby1.9-2.0.5/lib/soap/streamHandler.rb:24: > warning: previous definition of RUBY_VERSION_STRING was here > Laden der Fehlerberichte ? Erledigt > »Found/Fixed«-Informationen werden ausgewertet ? Erledigt > Changelogs werden gelesen... Fertig > >So it seems that there is an incompatibility with some openssl updates. > >-- Package-specific info: >==> /etc/apt/listchanges.conf <== >[apt] >frontend=pager >email_address=root >confirm=0 >save_seen=/var/lib/apt/listchanges.db >which=both >no_network=false >email_format=text >headers=true >reverse=true > > >-- System Information: >Debian Release: trixie/sid > APT prefers experimental > APT policy: (1, 'experimental') >merged-usr: no >Architecture: amd64 (x86_64) >Foreign Architectures: i386 > >Kernel: Linux 6.1.38 (SMP w/8 CPU threads) >Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_CPU_OUT_OF_SPEC, >TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE >Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set >Shell: /bin/sh linked to /bin/dash >Init: sysvinit (via /sbin/init) > >Versions of packages apt-listchanges depends on: >ii apt2.7.6devuan2 >ii debconf [debconf-2.0] 1.5.82 >ii python33.11.4-5+b1 >ii python3-apt2.7.0 >ii python3-debconf1.5.82 >ii sensible-utils 0.0.20 >ii ucf3.0043+nmu1 > >apt-listchanges recommends no packages. > >Versions of packages apt-listchanges suggests: >ii eterm [x-terminal-emulator]0.9.6-7.1 >ii exim4-daemon-light [mail-transport-agent] 4.97-2 >ii firefox [www-browser] 120.0-2 >ii luakit [www-browser] 1:2.3.3-1 >ii python3-gi 3.46.0-1 >ii rxvt-unicode [x-terminal-emulator] 9.31-1 >ii w3m [www-browser] 0.5.3+git20230121-2 >ii xterm [x-terminal-emulator]388-1 > >-- debconf information: >* apt-listchanges/email-address: root >* apt-listchanges/which: both >* apt-listchanges/reverse: true >* apt-listchanges/email-format: text >* apt-listchanges/no-network: false >* apt-listchanges/save-seen: true >* apt-listchanges/confirm: false >* apt-listchanges/frontend: pager >* apt-listchanges/headers: true > >-- >Klaus Ethgen http://www.ethgen.ch/ >pub 4096R/4E20AF1C 2011-05-16Klaus Ethgen >Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C -- Sent from my phone. Please excuse brevity and autocorrect errors.
Bug#1056927: closed by Debian FTP Masters (reply to bott...@debian.org (A. Maitland Bottoms)) (Bug#1056927: fixed in hackrf 2023.01.1-3)
Control: reopen -1 Hi, * Debian Bug Tracking System [231127 18:45]: > #1056927: libhackrf0: Move files into /usr (incl. DEP17 P7 mitigation) Thanks for applying the patch quickly. However it appears the following part of the patch did not get applied 2023.01.1-3. Could you please double check? > diff -Nru hackrf-2023.01.1/debian/rules hackrf-2023.01.1/debian/rules > --- hackrf-2023.01.1/debian/rules 2023-10-15 02:26:21.0 +0200 > +++ hackrf-2023.01.1/debian/rules 2023-11-26 20:37:03.0 +0100 > @@ -43,3 +45,9 @@ > > override_dh_installdocs-indep: > dh_installdocs --indep > + > +override_dh_installudev: > + dh_installudev > + # This should be harmless for indep builds or after dh_installudev > changes the install path. > + set -e; if test -d debian/libhackrf0/lib/udev/rules.d; then mv > debian/libhackrf0/lib/udev debian/libhackrf0/usr/lib; fi > + set -e; if test -d debian/libhackrf0/lib; then rmdir > debian/libhackrf0/lib; fi Thanks, Chris
Bug#1057000: Broken OPENSSL_init_ssl
Package: apt-listchanges Version: 3.27 Severity: important After recent updates, apt-listchanges is somewhat broken: Laden der Fehlerberichte ? 0% Fehlgeschlagen Das Laden der Fehlerberichte vom Server ist mit folgender Fehlermeldung fehlgeschlagen: E: OPENSSL_init_ssl Es könnte an Ihrem inaktiven Netzwerk oder an einem fehlerhaften Proxy-Server liegen oder der BTS-Server ist nicht aktiv. Überprüfen Sie die Netzwerkkonfiguration und versuchen Sie es erneut Soll erneut versucht werden, die Informationen zu dem Fehler herunterzuladen? [Y/n] Jeweils ein Paket? [Y/n] Jeweils ein Fehlerbericht? [Y/n] /usr/share/rubygems-integration/all/gems/soap4r-ruby1.9-2.0.5/lib/soap/streamHandler.rb:24: warning: already initialized constant SOAP::StreamHandler::RUBY_VERSION_STRING /usr/share/rubygems-integration/all/gems/soap4r-ruby1.9-2.0.5/lib/soap/streamHandler.rb:24: warning: previous definition of RUBY_VERSION_STRING was here Laden der Fehlerberichte ? Erledigt »Found/Fixed«-Informationen werden ausgewertet ? Erledigt Changelogs werden gelesen... Fertig So it seems that there is an incompatibility with some openssl updates. -- Package-specific info: ==> /etc/apt/listchanges.conf <== [apt] frontend=pager email_address=root confirm=0 save_seen=/var/lib/apt/listchanges.db which=both no_network=false email_format=text headers=true reverse=true -- System Information: Debian Release: trixie/sid APT prefers experimental APT policy: (1, 'experimental') merged-usr: no Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.38 (SMP w/8 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_CPU_OUT_OF_SPEC, TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages apt-listchanges depends on: ii apt2.7.6devuan2 ii debconf [debconf-2.0] 1.5.82 ii python33.11.4-5+b1 ii python3-apt2.7.0 ii python3-debconf1.5.82 ii sensible-utils 0.0.20 ii ucf3.0043+nmu1 apt-listchanges recommends no packages. Versions of packages apt-listchanges suggests: ii eterm [x-terminal-emulator]0.9.6-7.1 ii exim4-daemon-light [mail-transport-agent] 4.97-2 ii firefox [www-browser] 120.0-2 ii luakit [www-browser] 1:2.3.3-1 ii python3-gi 3.46.0-1 ii rxvt-unicode [x-terminal-emulator] 9.31-1 ii w3m [www-browser] 0.5.3+git20230121-2 ii xterm [x-terminal-emulator]388-1 -- debconf information: * apt-listchanges/email-address: root * apt-listchanges/which: both * apt-listchanges/reverse: true * apt-listchanges/email-format: text * apt-listchanges/no-network: false * apt-listchanges/save-seen: true * apt-listchanges/confirm: false * apt-listchanges/frontend: pager * apt-listchanges/headers: true -- Klaus Ethgen http://www.ethgen.ch/ pub 4096R/4E20AF1C 2011-05-16Klaus Ethgen Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C signature.asc Description: PGP signature
Bug#1056960: aoetools: Installs files into /lib, /sbin
* Christoph Biedl [231127 18:01]: > Chris Hofstaedtler wrote... > > For the ongoing UsrMerge effort [1], these directories should become > > "empty", IOW packages should not install into these directories, but > > instead into /usr. > > [1] Dangling footnote error :-) Err, yes. I imagine you guessed it was supposed to link to https://wiki.debian.org/UsrMerge > Sure thing, and just another bit: I noticed qualified program names in > the init script that could see an adjustment as well. So in case you're > scanning the entire archive for adjustments like here, you might want to > point at such places as well. Adside from that, I'll remove these full > paths, in the spirit of policy 6.1. This is a good point, but at the same time the initramfs hooks tend to have absolute paths, and growing the diffs with a "lot of noise" is probably not helping (often time-constrained) maintainers. But please go ahead and apply these fixes, too! Thanks again, Chris
Bug#1007884: bullseye-pu: package glewlwyd/2.5.2-2+deb11u2
Hello Salvatore, Le 2023-11-27 à 13 h 01, Salvatore Bonaccorso a écrit : Small remark, the version ideally is set to 2.5.2-2+deb11u3. My very bad, must be a wrong dch command, here is a new debdiff. Thanks for noticing /Nicolasdiff -Nru glewlwyd-2.5.2/debian/changelog glewlwyd-2.5.2/debian/changelog --- glewlwyd-2.5.2/debian/changelog 2021-12-17 07:51:46.0 -0500 +++ glewlwyd-2.5.2/debian/changelog 2023-11-24 08:14:30.0 -0500 @@ -1,3 +1,18 @@ +glewlwyd (2.5.2-2+deb11u3) bullseye; urgency=medium + + * d/patches: Fix CVE-2022-27240 + possible buffer overflow during webauthn signature assertion + * d/patches: Fix CVE-2022-29967 + static_compressed_inmemory_website_callback.c in Glewlwyd + through 2.6.2 allows directory traversal + * d/glewlwyd-common.install: copy bootstrap, jquery, fork-awesome +instead of linking it + * d/patches: Fix CVE-2023-49208: + possible buffer overflow during FIDO2 signature validation + in webauthn registration + + -- Nicolas Mora Fri, 24 Nov 2023 08:15:30 -0500 + glewlwyd (2.5.2-2+deb11u2) bullseye; urgency=medium * d/patches: Fix possible privilege escalation (Closes: #1001849) diff -Nru glewlwyd-2.5.2/debian/control glewlwyd-2.5.2/debian/control --- glewlwyd-2.5.2/debian/control 2021-12-17 07:51:46.0 -0500 +++ glewlwyd-2.5.2/debian/control 2023-11-24 08:13:12.0 -0500 @@ -35,6 +35,10 @@ , node-i18next-http-backend , node-qrcode-generator , webpack + , fonts-fork-awesome + , libjs-jquery + , libjs-bootstrap4 + , libjs-popper.js Standards-Version: 4.5.1 Homepage: https://github.com/babelouest/glewlwyd Vcs-Browser: https://salsa.debian.org/debian-iot-team/oauth2/glewlwyd.git diff -Nru glewlwyd-2.5.2/debian/glewlwyd-common.install glewlwyd-2.5.2/debian/glewlwyd-common.install --- glewlwyd-2.5.2/debian/glewlwyd-common.install 2021-12-17 07:51:46.0 -0500 +++ glewlwyd-2.5.2/debian/glewlwyd-common.install 2023-11-24 08:13:12.0 -0500 @@ -1,5 +1,6 @@ -webapp-src/css/glewlwyd*.css usr/share/glewlwyd/webapp/css/ -webapp-src/css/*-custom.css usr/share/glewlwyd/webapp/css/ +webapp-src/css/* usr/share/glewlwyd/webapp/css/ +webapp-src/js/* usr/share/glewlwyd/webapp/js/ +webapp-src/fonts/* usr/share/glewlwyd/webapp/fonts/ webapp-src/locales/ usr/share/glewlwyd/webapp/ webapp-src/img/ usr/share/glewlwyd/webapp/ webapp-src/output/*.js usr/share/glewlwyd/webapp/ @@ -7,3 +8,4 @@ webapp-src/favicon.ico usr/share/glewlwyd/webapp/ debian/config.json usr/share/glewlwyd/templates/ +debian/config.json usr/share/glewlwyd/webapp/ diff -Nru glewlwyd-2.5.2/debian/glewlwyd-common.links glewlwyd-2.5.2/debian/glewlwyd-common.links --- glewlwyd-2.5.2/debian/glewlwyd-common.links 2021-12-17 07:51:46.0 -0500 +++ glewlwyd-2.5.2/debian/glewlwyd-common.links 1969-12-31 19:00:00.0 -0500 @@ -1,19 +0,0 @@ -usr/share/javascript/jquery/jquery.min.js usr/share/glewlwyd/webapp/js/jquery.min.js -usr/share/javascript/jquery/jquery.min.js usr/share/glewlwyd/webapp/js/jquery.min.js -usr/share/javascript/popper.js/umd/popper.min.js usr/share/glewlwyd/webapp/js/popper.min.js -usr/share/javascript/popper.js/umd/popper-utils.min.js usr/share/glewlwyd/webapp/js/popper-utils.min.js - -usr/share/nodejs/bootstrap/dist/js/bootstrap.min.js usr/share/glewlwyd/webapp/js/bootstrap.min.js -usr/share/nodejs/bootstrap/dist/js/bootstrap.min.js.map usr/share/glewlwyd/webapp/js/bootstrap.min.js.map -usr/share/nodejs/bootstrap/dist/css/bootstrap.min.css usr/share/glewlwyd/webapp/css/bootstrap.min.css -usr/share/nodejs/bootstrap/dist/css/bootstrap.min.css.map usr/share/glewlwyd/webapp/css/bootstrap.min.css.map - -usr/share/fonts-fork-awesome/css/fork-awesome.css usr/share/glewlwyd/webapp/css/fork-awesome.min.css -usr/share/fonts-fork-awesome/css/v5-compat.css usr/share/glewlwyd/webapp/css/v5-compat.min.css -usr/share/fonts/eot/fork-awesome/forkawesome-webfont.eot usr/share/glewlwyd/webapp/fonts/forkawesome-webfont.eot -usr/share/fonts/svg/fork-awesome/forkawesome-webfont.svg usr/share/glewlwyd/webapp/fonts/forkawesome-webfont.svg -usr/share/fonts/truetype/fork-awesome/forkawesome-webfont.ttf usr/share/glewlwyd/webapp/fonts/forkawesome-webfont.ttf -usr/share/fonts/woff/fork-awesome/forkawesome-webfont.woff usr/share/glewlwyd/webapp/fonts/forkawesome-webfont.woff -usr/share/fonts/woff/fork-awesome/forkawesome-webfont.woff2 usr/share/glewlwyd/webapp/fonts/forkawesome-webfont.woff2 - -etc/glewlwyd/config.json usr/share/glewlwyd/webapp/config.json diff -Nru glewlwyd-2.5.2/debian/patches/CVE-2022-29967.patch glewlwyd-2.5.2/debian/patches/CVE-2022-29967.patch --- glewlwyd-2.5.2/debian/patches/CVE-2022-29967.patch 1969-12-31 19:00:00.0 -0500 +++ glewlwyd-2.5.2/debian/patches/CVE-2022-29967.patch 2023-11-24 08:13:12.0 -0500 @@ -0,0 +1,263 @@ +--- a/src/static_compressed_inmemory
Bug#1056717: RM: postgresql-15 -- ROM; Superseded by postgresql-16
Re: To Debian Bug Tracking System > Please remove postgresql-15 from unstable. All reverse dependencies > have transitioned to postgresql-16. > > The remaining problems quoted below are arch:all packages not yet > decrufted (postgresql-15-*), or one binnmu away from being fixed > (glom, not sure why that was missed on riscv64, will get that done). Fwiw, glom has been binnmued, so the PG15 removal can proceed now. Christoph
Bug#1056999: tipp10: Missing dependency on libqt6sql6-sqlite
Package: tipp10 Version: 3.3.0-1 Severity: important Dear Maintainer, tipp10 didn't start but showed the following: ``` $tipp10 QSqlDatabase: QSQLITE driver not loaded QSqlDatabase: available drivers: ``` After installing `libqt6sql6-sqlite` it starts successfully, so I guess this dependency was forgotten. Best regards, Martin -- System Information: Debian Release: 12.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable-debug'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-13-amd64 (SMP w/4 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 tipp10 depends on: ii libc62.36-9+deb12u3 ii libgcc-s112.2.0-14 ii libqt6core6 6.4.2+dfsg-10 ii libqt6gui6 6.4.2+dfsg-10 ii libqt6multimedia66.4.2-5 ii libqt6printsupport6 6.4.2+dfsg-10 ii libqt6sql6 6.4.2+dfsg-10 ii libqt6widgets6 6.4.2+dfsg-10 ii libstdc++6 12.2.0-14 tipp10 recommends no packages. tipp10 suggests no packages. -- no debconf information signature.asc Description: PGP signature
Bug#1007884: bullseye-pu: package glewlwyd/2.5.2-2+deb11u2
Hi Nicolas, On Mon, Nov 27, 2023 at 08:00:39AM -0500, Nicolas Mora wrote: > Hello, > > Here is a new debdiff for the glewlwyd/2.5.2-2+deb11u2 package, which now > also includes the fix for CVE-2023-49208. > diff -Nru glewlwyd-2.5.2/debian/changelog glewlwyd-2.5.2/debian/changelog > --- glewlwyd-2.5.2/debian/changelog 2021-12-17 07:51:46.0 -0500 > +++ glewlwyd-2.5.2/debian/changelog 2023-11-24 08:14:30.0 -0500 > @@ -1,3 +1,18 @@ > +glewlwyd (2.5.2-2+deb11u2.1) bullseye; urgency=medium Small remark, the version ideally is set to 2.5.2-2+deb11u3. Regards, Salvatore
Bug#1056998: cdrom: Installation media changes after booting it
Package: cdrom Severity: normal X-Debbugs-Cc: raamredd...@gmail.com Dear Maintainer, I have downloaded a debian 12.2.0 netinst and verified its integrity with sha512sum -c --ignore-missing SHA512SUMS and wrote it to a usb drive with dd bs=2048 if=debian-12.2.0-amd64-netinst.iso of=/dev/sda oflag=sync status=progress I also verified that the contents were copied correctly with these two commands: cmp -n `stat -c '%s' debian-12.2.0-amd64-netinst.iso` debian-12.2.0-amd64-netinst.iso /dev/sda head -c $(stat -c '%s' debian-12.2.0-amd64-netinst.iso) /dev/sda | sha512sum which returned the same checksum. I also safely removed the drive, unplugged it, and plugged it back in, and used those two commands again with the same output. (to make sure the kernel buffer wasn't in use) After booting the Installer from that drive, however, and navigating to the Integrity Check section of the installer from its menu, it said that ./boot/grub/efi.img failed the MD5 checksum verification. Your installation media or this file may have been corrupted. After this, I chose to quit the installer and check the medias integrity again with the earlier two commands. sha512sum showed a different checksum, and cmp showed debian-12.2.0-amd64-netinst.iso /dev/sda differ: byte 2303211, line 21165 showing that the content of the drive changed since it previously passed. I also tried entering the installer, and aborting the installation without using the Integrity Test section. I did this because I thought that maybe mounting the media in the Integrity Test section of the installer somehow changed the data. However, after booting, cmp and sha512sum still showed the same difference. I also tried using ddrescue and verified that there were 0 issues with the blocks on the media, used a different usb drive, and tried 3 laptops. In all of these cases it was always byte 2303211, line 21165 which changed. To my knowledge, I don't think this is supposed to happen. I instead expected an outcome where the media would stay the same throughout the installation process. Lastly, the computer I was using was able to get 10 passes in memtest without any errors. Have a nice day, Ram
Bug#1056997: libbmusb6: Let udev.pc decide where to install rules
Package: libbmusb6
Version: 0.7.5-1
Severity: normal
Tags: patch
User: helm...@debian.org
Usertags: dep17m2
Dear Maintainer,
your package ships a udev rules file in /lib/udev/rules.d, and currently
hard-codes this path. As part of the UsrMerge effort[1], the install
path for udev rules must and will change soon. To pick up this change
with a binNMU, your package can use pkg-config to determine the install
location.
I'm attaching a patch to implement this.
Please apply at your earliest convenience.
Thanks,
Chris
diff -Nru bmusb-0.7.5/debian/changelog bmusb-0.7.5/debian/changelog
--- bmusb-0.7.5/debian/changelog2020-04-07 21:29:27.0 +0200
+++ bmusb-0.7.5/debian/changelog2023-11-27 18:41:53.0 +0100
@@ -1,3 +1,10 @@
+bmusb (0.7.5-1.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Defer placement of udev rules file to udev's pkg-config data.
+
+ -- Chris Hofstaedtler Mon, 27 Nov 2023 18:41:53 +0100
+
bmusb (0.7.5-1) unstable; urgency=medium
* New upstream release.
diff -Nru bmusb-0.7.5/debian/compat bmusb-0.7.5/debian/compat
--- bmusb-0.7.5/debian/compat 2016-07-26 13:29:10.0 +0200
+++ bmusb-0.7.5/debian/compat 1970-01-01 01:00:00.0 +0100
@@ -1 +0,0 @@
-9
diff -Nru bmusb-0.7.5/debian/control bmusb-0.7.5/debian/control
--- bmusb-0.7.5/debian/control 2019-04-19 10:00:21.0 +0200
+++ bmusb-0.7.5/debian/control 2023-11-27 18:41:53.0 +0100
@@ -1,7 +1,7 @@
Source: bmusb
Priority: optional
Maintainer: Steinar H. Gunderson
-Build-Depends: debhelper (>= 9), libusb-1.0-0-dev, pkg-config
+Build-Depends: debhelper-compat (= 13), libusb-1.0-0-dev, pkg-config, udev
Standards-Version: 3.9.8
Section: libs
diff -Nru bmusb-0.7.5/debian/libbmusb6.install
bmusb-0.7.5/debian/libbmusb6.install
--- bmusb-0.7.5/debian/libbmusb6.install2020-04-07 21:29:27.0
+0200
+++ bmusb-0.7.5/debian/libbmusb6.install2023-11-27 18:38:42.0
+0100
@@ -1,2 +1,2 @@
usr/lib/*/*.so.*
-lib/udev/rules.d/*
+${env:deb_udevdir}/rules.d/*
diff -Nru bmusb-0.7.5/debian/patches/debian-multiarch.diff
bmusb-0.7.5/debian/patches/debian-multiarch.diff
--- bmusb-0.7.5/debian/patches/debian-multiarch.diff2020-04-07
21:29:27.0 +0200
+++ bmusb-0.7.5/debian/patches/debian-multiarch.diff2023-11-27
18:39:46.0 +0100
@@ -7,16 +7,17 @@
===
--- bmusb-0.7.5.orig/Makefile
+++ bmusb-0.7.5/Makefile
-@@ -6,6 +6,8 @@ LN := ln
+@@ -6,6 +6,9 @@ LN := ln
RANLIB := ranlib
INSTALL := install
PREFIX := /usr
+DEB_MULTIARCH_TRIPLET := $(shell dpkg-architecture -qDEB_HOST_MULTIARCH)
+LIBDIR := $(PREFIX)/lib/$(DEB_MULTIARCH_TRIPLET)
++UDEVDIR := $(shell pkg-config --variable=udevdir udev)
LIB := libbmusb.a
SODEV := libbmusb.so
SONAME := libbmusb.so.6
-@@ -36,14 +38,16 @@ clean:
+@@ -36,14 +39,16 @@ clean:
install: all
$(INSTALL) -m 755 -o root -g root -d \
@@ -25,18 +26,20 @@
+ $(DESTDIR)$(LIBDIR) \
+ $(DESTDIR)$(LIBDIR)/pkgconfig \
$(DESTDIR)$(PREFIX)/include/bmusb \
- $(DESTDIR)/lib/udev/rules.d
+- $(DESTDIR)/lib/udev/rules.d
- $(INSTALL) -m 755 -o root -g root $(LIB) $(SOLIB)
$(DESTDIR)$(PREFIX)/lib
- $(LN) -sf $(SOLIB) $(DESTDIR)$(PREFIX)/lib/$(SONAME)
- $(LN) -sf $(SOLIB) $(DESTDIR)$(PREFIX)/lib/$(SODEV)
++ $(DESTDIR)$(UDEVDIR)/rules.d
+ $(INSTALL) -m 755 -o root -g root $(LIB) $(SOLIB) $(DESTDIR)$(LIBDIR)
+ $(LN) -sf $(SOLIB) $(DESTDIR)$(LIBDIR)/$(SONAME)
+ $(LN) -sf $(SOLIB) $(DESTDIR)$(LIBDIR)/$(SODEV)
$(INSTALL) -m 755 -o root -g root bmusb/bmusb.h bmusb/fake_capture.h
$(DESTDIR)$(PREFIX)/include/bmusb
- $(INSTALL) -m 644 -o root -g root bmusb.pc
$(DESTDIR)$(PREFIX)/lib/pkgconfig
-+ $(INSTALL) -m 644 -o root -g root bmusb.pc $(DESTDIR)$(LIBDIR)/pkgconfig
- $(INSTALL) -m 644 -o root -g root 70-bmusb.rules
$(DESTDIR)/lib/udev/rules.d
+- $(INSTALL) -m 644 -o root -g root 70-bmusb.rules
$(DESTDIR)/lib/udev/rules.d
-
++ $(INSTALL) -m 644 -o root -g root bmusb.pc $(DESTDIR)$(LIBDIR)/pkgconfig
++ $(INSTALL) -m 644 -o root -g root 70-bmusb.rules
$(DESTDIR)$(UDEVDIR)/rules.d
+ sed 's/@DEB_MULTIARCH_TRIPLET@/$(DEB_MULTIARCH_TRIPLET)/' < bmusb.pc >
$(DESTDIR)$(LIBDIR)/pkgconfig/bmusb.pc
+ chmod 0644 $(DESTDIR)$(LIBDIR)/pkgconfig/bmusb.pc
+ chown root:root $(DESTDIR)$(LIBDIR)/pkgconfig/bmusb.pc
diff -Nru bmusb-0.7.5/debian/rules bmusb-0.7.5/debian/rules
--- bmusb-0.7.5/debian/rules2016-07-26 13:41:34.0 +0200
+++ bmusb-0.7.5/debian/rules2023-11-27 18:41:53.0 +0100
@@ -1,4 +1,6 @@
#! /usr/bin/make -f
+export deb_udevdir = $(shell pkg-config --variable=udevdir udev | sed s,^/,,)
+
%:
dh $@
Bug#1056996: bluez FTBFS when udev.pc changes udevdir
Source: bluez
Version: 5.66-1
Severity: important
Tags: ftbfs patch
Hi,
similarly to #1052983, udev will also change udevdir in udev.pc soon.
When this happens, bluez will fail to build from source.
Please find a patch attached to fix this, by using udevdir. This means
you can apply this patch today (also true for #1052983).
The attached patch also moves hciconfig out of /bin, as /bin also needs
to become "empty" (= no package installs files there) for the UsrMerge
effort [1].
Please apply as soon as convenient.
Thanks for considering,
Chris
1. https://wiki.debian.org/UsrMerge
diff -Nru bluez-5.70/debian/bluez.install bluez-5.70/debian/bluez.install
--- bluez-5.70/debian/bluez.install 2023-10-24 08:17:00.0 +0200
+++ bluez-5.70/debian/bluez.install 2023-11-27 18:36:07.0 +0100
@@ -7,7 +7,7 @@
usr/bin/btattach
usr/bin/btmon
usr/bin/hciattach
-usr/bin/hciconfig bin/
+usr/bin/hciconfig
usr/bin/hcitool
usr/bin/sdptool
usr/bin/rctest
@@ -20,8 +20,8 @@
usr/bin/mpris-proxy
tools/btmgmt usr/bin
tools/obexctl usr/bin
-lib/udev/hid2hci
-lib/udev/rules.d/97-hid2hci.rules
+${env:deb_udevdir}/hid2hci
+${env:deb_udevdir}/rules.d/97-hid2hci.rules
attrib/gatttool usr/bin
#-- for systemd
lib/systemd/system/bluetooth.service
diff -Nru bluez-5.70/debian/changelog bluez-5.70/debian/changelog
--- bluez-5.70/debian/changelog 2023-10-24 08:17:00.0 +0200
+++ bluez-5.70/debian/changelog 2023-11-27 18:36:36.0 +0100
@@ -1,3 +1,11 @@
+bluez (5.70-1.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Defer udev file placement to udev's pkg-config data
+ * Install hciconfig into /usr/bin instead of /bin
+
+ -- Chris Hofstaedtler Mon, 27 Nov 2023 18:36:36 +0100
+
bluez (5.70-1) unstable; urgency=medium
* Update to 5.70.
diff -Nru bluez-5.70/debian/rules bluez-5.70/debian/rules
--- bluez-5.70/debian/rules 2023-10-24 08:17:00.0 +0200
+++ bluez-5.70/debian/rules 2023-11-27 18:35:36.0 +0100
@@ -41,6 +41,8 @@
skip_packages = -Nbluez-cups
endif
+export deb_udevdir = $(shell pkg-config --variable=udevdir udev | sed s,^/,,)
+
%:
dh $@ --exclude=.la
Bug#1056995: src:pry: fails to migrate to testing for too long: waiting for update of ruby-pry-byebug
Source: pry Version: 0.13.1-3 Severity: serious Control: close -1 0.14.2-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1054737 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:pry has been trying to migrate for 33 days [2]. Hence, I am filing this bug. The version in unstable can't migrate until ruby-pry-byebug is updated (bug 1054737), as both pry and ruby-pry-byebug are key packages. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=pry OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1056994: src:python-tblib: fails to migrate to testing for too long: FTBFS
Source: python-tblib Version: 2.0.0-2 Severity: serious Control: close -1 3.0.0-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1054938 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:python-tblib has been trying to migrate for 31 days [2]. Hence, I am filing this bug. The version in unstable failed to build as reported in bug 1054938. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=python-tblib OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1056993: src:php8.2: fails to migrate to testing for too long: triggers autopkgtest failures
Source: php8.2 Version: 8.2.10-2 Severity: serious Control: close -1 8.2.12-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:php8.2 has been trying to migrate for 31 days [2]. Hence, I am filing this bug. The version in unstable triggers multiple autopkgtest failures. The one in shaarli will go away soon because it already has an RC bug now, but php-imagick doesn't (it fails on armel). If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=php8.2 OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1056992: freerdp2: Please package version 3
Source: freerdp2 Version: 2.11.2+dfsg1-1 Severity: wishlist X-Debbugs-CC: sunwea...@debian.org FreeRDP 3.0.0 RC0 was just released. We should begin thinking about how we will handle its packaging. I believe it would require a major transition if we aim to keep only one version of FreeRDP in Debian. gnome-remote-desktop 46 is expected to be released in March requiring FreeRDP 3. Thank you, Jeremy Bícha
Bug#1056066: systemd: rsyslog fails to start if /dev/xconsole exists
Am 27.11.23 um 16:43 schrieb Sven Joachim: Control: found -1 8.2310.0-3 On 2023-11-16 18:14 +0100, Michael Biebl wrote: Am 16.11.23 um 18:12 schrieb Michael Biebl: b/ Move /dev/xconsole to run and turn /dev/xconsole into a symlink The latter b/ will require updates to the local copies in /etc/tmpfiles.d/ and /etc/rsyslog.d/ They would look like this now: $ cat /etc/rsyslog.d/xconsole.conf daemon.*;mail.*;\ news.err;\ *.=debug;*.=info;\ *.=notice;*.=warn |/run/xconsole $ cat /etc/tmpfiles.d/xconsole.conf # Type Path Mode UID GID Age Argument p /run/xconsole 0640 root adm L /dev/xconsole - - - - /run/xconsole And you need to drop BindPaths=-/dev/xconsole from rsyslog.service again. Thanks, I had edited the service file in /usr/lib/systemd/system accordingly. Unfortunately you forgot to apply that change to rsyslog's debian/rsyslog.service, and so rsyslogd failed to start again after upgrading to 8.2310.0-3. Argh, sorry. Will fix immediately. Not sure why I missed that... The NEWS item looks fine to me, though. Thanks. OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1056960: aoetools: Installs files into /lib, /sbin
Control: tags 1056960 pending Chris Hofstaedtler wrote... > your package aoetools installs some files into /lib and /sbin. I > understand this was to support split-/usr installs in the past. Telling stories, this was a deliberate change by an earlier maintainer of aoetools. I wanted to revert that anyway, but the tne moratorium happenened. Good thing this is history now. > For the ongoing UsrMerge effort [1], these directories should become > "empty", IOW packages should not install into these directories, but > instead into /usr. [1] Dangling footnote error :-) Sure thing, and just another bit: I noticed qualified program names in the init script that could see an adjustment as well. So in case you're scanning the entire archive for adjustments like here, you might want to point at such places as well. Adside from that, I'll remove these full paths, in the spirit of policy 6.1. > I think aoetools could move these files now. I am guessing that aoetools > would not see backports; if it did, please note that such changes must be > reverted for bookworm (or earlier). Backports are not planned but thanks for the reminder. Christoph signature.asc Description: PGP signature
Bug#1056991: lua5.4: Add packaging improvements from Ubuntu to Debian
Package: lua5.4 Version: 5.4.4-1 Severity: minor Tags: patch X-Debbugs-Cc: l...@voytek.dev Dear Maintainer, During the process of adding lua5.4 to the Ubuntu main package set I made some general improvements to the packaging, including DEP-8 tests, build cleanup, and a symbols file. I've created a merge request with the changes here: https://salsa.debian.org/lua-team/lua5.4/-/merge_requests/4 Thanks! -- System Information: Debian Release: bookworm/sid APT prefers jammy-updates APT policy: (500, 'jammy-updates'), (500, 'jammy-security'), (500, 'jammy'), (100, 'jammy-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.15.0-89-generic (SMP w/32 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages lua5.4 depends on: ii libc6 2.35-0ubuntu3.4 ii libreadline8 8.1.2-1 lua5.4 recommends no packages. lua5.4 suggests no packages. -- no debconf information
Bug#1054533: nvme-stas: autopkgtest fails on all architectures
Package: nvme-stas
Followup-For: Bug #1054533
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu noble ubuntu-patch
Control: tags -1 patch
Dear Maintainer,
Several test cases in nvme-stas 2.3-1 were making the autopkgtest fail.
In Ubuntu, the attached patch was applied to achieve the following:
* Add Test-Depends on nvme-cli to fix the absence of /etc/nvme/host{nqn,id}
when running the test suite. (LP: #2043792)
- This is only a workaround for autopkgtests. stafd can still fail with
the same error at runtime outside of autopkgtests when configured with
an appropriate "controller =" directive.
* Fix failing test from mocked libnvme version. (LP: #2043792)
* Fix legacy Udev test failing when multiples IPv6 addresses are set.
(LP: #2043792)
Thanks for considering the patch.
-- System Information:
Debian Release: trixie/sid
APT prefers mantic-updates
APT policy: (500, 'mantic-updates'), (500, 'mantic-security'), (500, 'mantic')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.1.0-16-generic (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru nvme-stas-2.3/debian/patches/fix-test-libnvme-version.patch
nvme-stas-2.3/debian/patches/fix-test-libnvme-version.patch
--- nvme-stas-2.3/debian/patches/fix-test-libnvme-version.patch 1970-01-01
01:00:00.0 +0100
+++ nvme-stas-2.3/debian/patches/fix-test-libnvme-version.patch 2023-11-21
09:29:41.0 +0100
@@ -0,0 +1,52 @@
+Description: Fix mock libnvme test so it works in GitHub actions & autopkgtest
+ Different Python test frameworks manage Python processes differently
+ when running tests. When running `python3 -m unittest` for instance, it
+ looks like the same process executes all the tests. Therefore when one
+ test module T1 imports a module, the module is not re-imported if needed
+ by T2.
+ .
+ This causes issues with test-defs.py which tries to mock the libnvme
+ module. Indeed, when it is previously imported by staslib, the mocked
+ libnvme module does not get re-imported.
+ .
+ Fixed by removing staslib and staslib.defs from the imported modules
+ before executing the test.
+Author: Olivier Gayot
+Origin: upstream,
https://github.com/linux-nvme/nvme-stas/commit/2efebdb4dec6d5a6341a577273a1ce7b57fe488c
+Bug-Ubuntu: https://launchpad.net/bugs/2043792
+Bug-Debian: https://bugs.debian.org/1054533
+Last-Update: 2023-11-27
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/test/test-defs.py
b/test/test-defs.py
+@@ -1,4 +1,5 @@
+ #!/usr/bin/python3
++import contextlib
+ import os
+ import sys
+ import unittest
+@@ -9,13 +10,17 @@
+ '''Testing defs.py by mocking the libnvme package'''
+
+ def test_libnvme_version(self):
+-# For unknown reasons, this test does
+-# not work when run from GitHub Actions.
+-if not os.getenv('GITHUB_ACTIONS'):
+-from staslib import defs
++# Ensure that we re-import staslib & staslib.defs if the current
Python
++# process has them already imported.
++with contextlib.suppress(KeyError):
++sys.modules.pop('staslib.defs')
++with contextlib.suppress(KeyError):
++sys.modules.pop('staslib')
+
+-libnvme_ver = defs.LIBNVME_VERSION
+-self.assertEqual(libnvme_ver, '?.?')
++from staslib import defs
++
++libnvme_ver = defs.LIBNVME_VERSION
++self.assertEqual(libnvme_ver, '?.?')
+
+ @classmethod
+ def setUpClass(cls): # called once before all the tests
diff -Nru
nvme-stas-2.3/debian/patches/fix-test-udev-failing-multiple-IPv6.patch
nvme-stas-2.3/debian/patches/fix-test-udev-failing-multiple-IPv6.patch
--- nvme-stas-2.3/debian/patches/fix-test-udev-failing-multiple-IPv6.patch
1970-01-01 01:00:00.0 +0100
+++ nvme-stas-2.3/debian/patches/fix-test-udev-failing-multiple-IPv6.patch
2023-11-21 09:29:41.0 +0100
@@ -0,0 +1,29 @@
+Description: Fix test-udev failing when multiple IPv6 addresses are used
+ test-udev was failing when an interface had more than one IPv6
+ addresses assigned. This was due to the test checking that the
+ number of assigned IPv6 addresses was exactly 1 (== 1) instead of
+ checking greater-equal to 1 (>= 1).
+Author: Martin Belanger
+Origin: upstream,
https://github.com/linux-nvme/nvme-stas/commit/66b42bdd83bb6a83b30da3aed5fea9ed4da882f6
+Bug: https://github.com/linux-nvme/nvme-stas/issues/403
+Bug-Ubuntu: https://launchpad.net/bugs/2043792
+Bug-Debian: https://bugs.debian.org/1054533
+Last-Update: 2023-11-27
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+diff --git a/test/test-udev.py b/test/test-udev.py
+index be257d9..ba484e0 100755
+--- a/test/test-udev.py
+++
Bug#921815: Versionnumber for closing the bug report
On 27/11/2023 09:25, Thorsten Glaser wrote: On Mon, 27 Nov 2023, Roland Clobus wrote: But did you also test whether /proc was not umounted? Before and after the debootstrap command, the output of mount inside the docker container is identical. Ah, okay. Your message read as if you only tested that debootstrap itself worked but didn’t mention the /proc parts. If this is indeed fixed, might be useful to figure out which version fixed it and then close with a version? Do you want to have a more exact version? Which I closed this issue, I used the version that is present in Buster. (Version: 1.0.114+deb10u1) Going deeper into older versions didn't seen necessary to me. With kind regards Roland Clobus OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1056770: braillefont: Description in debian/control has a new line in the middle of a sentence
Hi, and finally, this mail does address both 1056...@bugs.debian.org and 1056770-submit...@bugs.debian.org Thanks for taking part in this experiment. And indeed, from the first look, this seems to be a valid bug :) urbec signature.asc Description: This is a digitally signed message part.
Bug#1056692: libhamlib4: Add protective diversion for udev rules shared file
On Mon, Nov 27, 2023 at 11:09:50AM +, Miguel Landaeta wrote: > On Mon, Nov 27, 2023 at 6:54 AM tony mancill wrote: > > An override like the following should work for this: > https://salsa.debian.org/debian/libnjb/-/blob/master/debian/libnjb5.lintian-overrides > > Thanks for looking at this patch. Thank you for providing the patch and a bug report with good background documentation. Applied and uploaded. Cheers, tony
Bug#1056770: braillefont: Description in debian/control has a new line in the middle of a sentence
Hi, this mail does address only 1056...@bugs.debian.org urbec signature.asc Description: This is a digitally signed message part.
Bug#1056205: 1056...@bugs.debian.org
Hi Bernd, How important is this issue for you? Does it need to be fixed in the stable releases? I have no sense of urgency here. That is, we have not had any customer reports that the containerInfo plugin is not working on Canonical systems. I basically stumbled on the incorrect directory looking at another issue. Thanks for the suggestion about creating an account on salsa. I will wait until the assimilation into Broadcom proceeds at least until I get assigned a Broadcom user Id (email address). Thanks for taking care of this Regards, John
Bug#1056990: src:linuxcnc: fails to migrate to testing for too long: unresolved RC issue
Source: linuxcnc Version: 2.9.0~pre1+git20230208.f1270d6ed7-1 Severity: serious Control: close -1 2.9.1-2 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1055493 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:linuxcnc has been trying to migrate for 31 days [2]. Hence, I am filing this bug. The version in unstable is affected by bug 1055493. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=linuxcnc OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1056614: RM: tweepy -- ROM; broken, obsolete, associated service doesn't exist anymore
On Thu, 23 Nov 2023 21:38:59 + MigueL Landaeta wrote: Package: ftp.debian.org Severity: normal As title says. This package and all Twitter related packages should be removed from the archive. Twitter API access is broken, so there is no point keeping this in the archive. +1 Cheers Timo -- ⢀⣴⠾⠻⢶⣦⠀ ╭╮ ⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling │ ⢿⡄⠘⠷⠚⠋⠀ │ 9B03 EBB9 8300 DF97 C2B1 23BF CC8C 6BDD 1403 F4CA │ ⠈⠳⣄ ╰╯ signature.asc Description: PGP signature
Bug#1056989: libaacs: build aacs_info
Source: libaacs Version: 0.11.1-2 Severity: wishlist Hey. Upstream contains the aacs_info program at: src/examples/aacs_info.c would it be possible to build and package that (e.g. as libaacs-tools or so), too? Thanks, Chris.
Bug#1056066: systemd: rsyslog fails to start if /dev/xconsole exists
Control: found -1 8.2310.0-3 On 2023-11-16 18:14 +0100, Michael Biebl wrote: > Am 16.11.23 um 18:12 schrieb Michael Biebl: >> b/ Move /dev/xconsole to run and turn /dev/xconsole into a symlink >> The latter b/ will require updates to the local copies in >> /etc/tmpfiles.d/ and /etc/rsyslog.d/ >> They would look like this now: >> $ cat /etc/rsyslog.d/xconsole.conf >> daemon.*;mail.*;\ >> news.err;\ >> *.=debug;*.=info;\ >> *.=notice;*.=warn |/run/xconsole >> $ cat /etc/tmpfiles.d/xconsole.conf >> # Type Path Mode UID GID Age Argument >> p /run/xconsole 0640 root adm >> L /dev/xconsole - - - - /run/xconsole > > And you need to drop BindPaths=-/dev/xconsole from rsyslog.service again. Thanks, I had edited the service file in /usr/lib/systemd/system accordingly. Unfortunately you forgot to apply that change to rsyslog's debian/rsyslog.service, and so rsyslogd failed to start again after upgrading to 8.2310.0-3. The NEWS item looks fine to me, though. Cheers, Sven
Bug#979688: Including u-boot-sunxi-with-spl.bin in the u-boot-sunxi binary package
Control: tags -1 patch On 25/07/2023 17:39, Vagrant Cascadian wrote: > [...] > Admittedly, I lost track of where this issue stands, as some of it was > merged but obviously not all of it. It could perhaps benefit from > refreshed patches and possibly a merge request via salsa.debian.org. > [...] Hi Vagrant, I've now made a merge request as you suggested: https://salsa.debian.org/debian/u-boot/-/merge_requests/33 It's the same as the patch in my previous comment on this bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979688#50 Best wishes, Harold.
