Bug#1021032: (no subject)
On Mon, 3 Oct 2022 07:46:54 +0100 Rik Mills wrote: Comment from the launchpad counterpart to this bug below: https://bugs.launchpad.net/ubuntu/+source/vlc/+bug/1991418/comments/10 "So, hate to rain on your parade, but as I wrote yesterday, the problem doesn't occur with upstream (building manually) 3.0.17.4. So there are ostensibly no patches to backport from upstream 3.0.18-rc2. This is probably an issue in the Debian packaging or at least that is triggered by Debian packaging. Since it seems to affect only the Qt UI, it is most probably a problem with the last Qt update. Again, please check with --no-embedded-video." Running with --no-embedded-video does indeed work, but as expected is ugly with the video in a separate floating window.
Bug#1021163: lomiri-indicator-network: binary-all FTBFS
Source: lomiri-indicator-network Version: 1.0.0~git20220718.2ca3619-2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=lomiri-indicator-network&arch=all&ver=1.0.0~git20220718.2ca3619-2&stamp=1664719442&raw=0 ... debian/rules override_dh_missing make[1]: Entering directory '/<>' dh_missing --fail-missing dh_missing: warning: usr/libexec/lomiri-indicator-network/lomiri-indicator-network-secret-agent exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/libexec/lomiri-indicator-network/lomiri-indicator-network-service exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/share/unity/indicators/com.lomiri.indicator.network exists in debian/tmp but is not installed to anywhere dh_missing: error: missing files, aborting The following debhelper tools have reported what they installed (with files per package) * dh_install: liblomiri-connectivity-qt1-1 (1), liblomiri-connectivity-qt1-dev (3), lomiri-connectivity-doc (3), lomiri-indicator-network (4), qml-module-lomiri-connectivity (1) * dh_installdocs: liblomiri-connectivity-qt1-1 (0), liblomiri-connectivity-qt1-dev (0), lomiri-connectivity-doc (0), lomiri-indicator-network (3), qml-module-lomiri-connectivity (0) * dh_installexamples: liblomiri-connectivity-qt1-1 (0), liblomiri-connectivity-qt1-dev (3), lomiri-connectivity-doc (0), lomiri-indicator-network (0), qml-module-lomiri-connectivity (0) If the missing files are installed by another tool, please file a bug against it. When filing the report, if the tool is not part of debhelper itself, please reference the "Logging helpers and dh_missing" section from the "PROGRAMMING" guide for debhelper (10.6.3+). (in the debhelper package: /usr/share/doc/debhelper/PROGRAMMING.gz) Be sure to test with dpkg-buildpackage -A/-B as the results may vary when only a subset is built If the omission is intentional or no other helper can take care of this consider adding the paths to debian/not-installed. make[1]: *** [debian/rules:31: override_dh_missing] Error 25
Bug#1021164: lomiri-indicator-network: binary-any FTBFS
Source: lomiri-indicator-network Version: 1.0.0~git20220718.2ca3619-2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=lomiri-indicator-network&ver=1.0.0~git20220718.2ca3619-2 ... debian/rules override_dh_install make[1]: Entering directory '/<>' # drop upstart files rm -Rfv debian/tmp/usr/share/upstart/ removed 'debian/tmp/usr/share/upstart/xdg/autostart/lomiri-indicator-network.desktop' removed directory 'debian/tmp/usr/share/upstart/xdg/autostart' removed directory 'debian/tmp/usr/share/upstart/xdg' removed 'debian/tmp/usr/share/upstart/systemd-session/upstart/lomiri-indicator-network-secret-agent.override' removed 'debian/tmp/usr/share/upstart/systemd-session/upstart/lomiri-indicator-network.override' removed directory 'debian/tmp/usr/share/upstart/systemd-session/upstart' removed directory 'debian/tmp/usr/share/upstart/systemd-session' removed 'debian/tmp/usr/share/upstart/sessions/lomiri-indicator-network-secret-agent.conf' removed 'debian/tmp/usr/share/upstart/sessions/lomiri-indicator-network.conf' removed directory 'debian/tmp/usr/share/upstart/sessions' removed directory 'debian/tmp/usr/share/upstart/' # empty directory rmdir debian/tmp/usr/share/doc/lomiri-connectivity-doc/qml/html/images/ dh_install dh_install: warning: Cannot find (any matches for) "usr/share/ayatana/indicators/com.lomiri.indicator.network" (tried in ., debian/tmp) dh_install: warning: lomiri-indicator-network missing files: usr/share/ayatana/indicators/com.lomiri.indicator.network dh_install: warning: Cannot find (any matches for) "usr/lib/*/lomiri-indicator-network/*" (tried in ., debian/tmp) dh_install: warning: lomiri-indicator-network missing files: usr/lib/*/lomiri-indicator-network/* dh_install: error: missing files, aborting make[1]: *** [debian/rules:28: override_dh_install] Error 25
Bug#1021165: armhf: floatn-common.h:214:9: error: multiple types in one declaration
Source: gcc-snapshot Version: 1:20220920-1 Severity: grave Per original reference: --- Comment #1 from Andrew Pinski --- Is this a packaging issue? > ignoring nonexistent directory > "/usr/lib/gcc-snapshot/lib/gcc/arm-linux-gnueabihf/13/include-fixed/arm-linux-gnueabihf" ignoring nonexistent directory "/usr/lib/gcc-snapshot/lib/gcc/arm-linux-gnueabihf/13/include-fixed" Gcc 13 requires some (older) glibc headers to be fixed up . See: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107128
Bug#1021043: marked as done (linphone: std::logic_error in src/account/account.cpp:LinphonePrivate::Account::notifyPublishStateChanged())
Your message dated Mon, 03 Oct 2022 08:49:19 +
with message-id
and subject line Bug#1021043: fixed in linphone 5.0.37-6
has caused the Debian Bug report #1021043,
regarding linphone: std::logic_error in
src/account/account.cpp:LinphonePrivate::Account::notifyPublishStateChanged()
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1021043: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021043
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linphone-desktop
Version: 4.3.2-2
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: d...@fifthhorseman.net
I've used linphone for years. Recently (i think with the upgrade to
4.3.2-2) it no longer works for me, crashing with a range of errors.
Working with my longstanding configuration, i see the following on stderr:
0 dkg@alice:~$ linphone
[17:53:37:555][0x562cdf49f5f0][Info]"Starting Linphone (bin: linphone)"
[17:53:37:555][0x562cdf49f5f0][Info]"Use locale: en_US"
[17:53:37:610][0x562cdf49f5f0][Info]Available fonts : ([REDACTED FOR LENGTH])
[17:53:37:611][0x562cdf49f5f0][Info]"Running app..."
[17:53:37:660][0x562cdf49f5f0][Info]"Activated selectors:" ("custom", "en_US",
"unix", "linux", "debian")
[17:53:37:661][0x562cdf49f5f0][Info]"Registering types..."
[17:53:37:662][0x562cdf49f5f0][Info]"Registering shared types..."
[17:53:37:662][0x562cdf49f5f0][Info]"Registering tool types..."
[17:53:37:662][0x562cdf49f5f0][Info]"Registering shared tool types..."
[17:53:37:804][0x562cdf49f5f0][Info]"Loading main view..."
[17:53:37:928][0x562cdf49f5f0][Info]"Launch async core creation."
[17:53:38:078][0x562cdf49f5f0][Info]Core is starting "Starting up"
[17:53:38:123][0x562cdf49f5f0][Info]Core is running "On"
[17:53:38:123][0x562cdf49f5f0][Info]"Set `Friends` path:
`/home/dkg/.local/share/linphone/friends.db`"
[17:53:38:138][0x562cdf49f5f0][Info]"Set `CallLogs` path:
`/home/dkg/.local/share/linphone/call-history.db`"
[17:53:38:144][0x562cdf49f5f0][Info]Using ZrtpSecrets path :
"/home/dkg/.local/share/linphone/zidcache"
[17:53:38:144][0x562cdf49f5f0][Info]Using UserCertificate path :
"/home/dkg/.local/share/linphone/usr-crt/"
[17:53:38:144][0x562cdf49f5f0][Info]Using RootCa path :
"/usr/share/linphone/rootca.pem"
[17:53:38:145][0x562cdf49f5f0][Info]"Start iterate"
[17:53:38:181][0x562cdf49f5f0][Info]Sip addresses model from Chats : 34 ms.
[17:53:38:192][0x562cdf49f5f0][Info]Sip addresses model from Calls : 10 ms.
[17:53:38:192][0x562cdf49f5f0][Info]Sip addresses model from Refs : 0 ms.
[17:53:38:193][0x562cdf49f5f0][Info]Sip addresses model from Contacts : 0 ms.
[17:53:38:193][0x562cdf49f5f0][Info]Sip addresses model initialized in: 45 ms.
[17:53:38:242][0x562cdf49f5f0][Info]"Notify event count: 0."
[17:53:38:242][0x562cdf49f5f0][Info]"CoreManager initialized"
[17:53:38:471][0x562cdf49f5f0][Info]"Open Linphone app."
[17:53:38:471][0x562cdf49f5f0][Info]"Creating subwindow:
`qrc:/ui/views/App/Calls/CallsWindow.qml`."
[17:53:38:534][0x562cdf49f5f0][Info]"Subwindow status: `1`."
[17:53:38:574][0x562cdf49f5f0][Info]"Creating subwindow:
`qrc:/ui/views/App/Settings/SettingsWindow.qml`."
[17:53:38:641][0x562cdf49f5f0][Info]"Subwindow status: `1`."
[17:53:39:708][0x562cdf49f5f0][Info]"Notify event count: 0."
terminate called after throwing an instance of 'std::logic_error'
what(): basic_string: construction from null is not valid
Aborted
134 dkg@alice:~$
I decided that maybe there was something wrong with my configuration,
so i moved ~/.config/linphone, ~/.linphonerc, and
~/.local/share/linphone out of the way to start fresh.
When i did that, and restarted linphone, i got the following error:
0 dkg@alice:~$ linphone
2022-09-30 18:31:09:410 bctbx-error-bctbx_file_open: Error open No such file or
directory
[18:31:09:422][0x564abb71f5f0][Info]"Starting Linphone (bin: linphone)"
[18:31:09:422][0x564abb71f5f0][Info]"Use locale: en_US"
[18:31:09:466][0x564abb71f5f0][Info]Available fonts : ([REDACTED FOR LENGTH])
[18:31:09:467][0x564abb71f5f0][Info]"Running app..."
[18:31:09:500][0x564abb71f5f0][Info]"Activated selectors:" ("custom", "en_US",
"unix", "linux", "debian")
[18:31:09:500][0x564abb71f5f0][Info]"Registering types..."
[18:31:09:501][0x564abb71f5f0][Info]"Registering shared types..."
[18:31:09:501][0x564abb71f5f0][Info]"Registering tool types..."
[18:31:09:501][0x564abb71f5f0][Info]"Registering shared tool types..."
[18:31:09:595][0x564abb71f5f0][Info]"Loading main view..."
[18:31:09:698][0x564abb71f5f0][Info]"Launch async core creation."
[18:31:09:804][0x564abb71f5f0][Info]Core is starting "Starting up"
[
Bug#1021165: Gcc 13 requires some (older) glibc headers to be fixed up .
For reference: malat@amdahl /tmp % apt-cache policy libc6-dev libc6-dev: Installed: 2.35-1 Candidate: 2.35-1 Version table: *** 2.35-1 500 500 https://deb.debian.org/debian sid/main armhf Packages 100 /var/lib/dpkg/status
Bug#965502: dvi2ps: NMU 5.1j-1.5
Hi, I have just uploaded a NMU which fixes this. debdiff is attached. Thanks, Bastiandiff -Nru dvi2ps-5.1j/debian/changelog dvi2ps-5.1j/debian/changelog --- dvi2ps-5.1j/debian/changelog2021-02-05 16:21:48.0 +0100 +++ dvi2ps-5.1j/debian/changelog2022-10-03 11:32:23.0 +0200 @@ -1,3 +1,10 @@ +dvi2ps (5.1j-1.5) unstable; urgency=medium + + * Non-maintainer upload. + * Update to debhelper-compat 10 (Closes: #965502). + + -- Bastian Germann Mon, 03 Oct 2022 09:32:23 + + dvi2ps (5.1j-1.4) unstable; urgency=medium * Non-maintainer upload. diff -Nru dvi2ps-5.1j/debian/compat dvi2ps-5.1j/debian/compat --- dvi2ps-5.1j/debian/compat 2019-02-17 13:29:43.0 +0100 +++ dvi2ps-5.1j/debian/compat 1970-01-01 01:00:00.0 +0100 @@ -1 +0,0 @@ -5 diff -Nru dvi2ps-5.1j/debian/control dvi2ps-5.1j/debian/control --- dvi2ps-5.1j/debian/control 2019-02-17 13:29:43.0 +0100 +++ dvi2ps-5.1j/debian/control 2022-10-03 11:31:10.0 +0200 @@ -2,8 +2,8 @@ Section: tex Priority: optional Maintainer: OHURA Makoto -Build-Depends: debhelper (>= 5.0.0), dh-autoreconf, nkf, libkpathsea-dev, vflib3-dev, - libfreetype6-dev, autotools-dev, pkg-config, po-debconf +Build-Depends: debhelper-compat (= 10), nkf, libkpathsea-dev, vflib3-dev, + libfreetype-dev, pkg-config, po-debconf Standards-Version: 3.8.4 Package: dvi2ps
Bug#1020532: crash text ...
Ok, after reinstallng gimp I get the same bug, but this time with this crash text: ``` GNU Image Manipulation Program version 2.10.32 git-describe: GIMP_2_10_32 Build: unknown rev 0 for linux # C compiler # Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/12/lto-wrapper OFFLOAD_TARGET_NAMES=nvptx-none:amdgcn-amdhsa OFFLOAD_TARGET_DEFAULT=1 Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Debian 12.1.0-8' --with-bugurl=file:///usr/share/doc/gcc-12/README.Bugs --enable-languages=c,ada,c++,go,d,fortran,objc,obj-c++,m2 --prefix=/usr --with-gcc-major-version-only --program-suffix=-12 --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-plugin --enable-default-pie --with-system-zlib --enable-libphobos-checking=release --with-target-system-zlib=auto --enable-objc-gc=auto --enable-multiarch --disable-werror --enable-cet --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-offload-targets=nvptx-none=/build/gcc-12-WXbu70/gcc-12-12.1.0/debian/tmp-nvptx/usr,amdgcn-amdhsa=/build/gcc-12-WXbu70/gcc-12-12.1.0/debian/tmp-gcn/usr --enable-offload-defaulted --without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu Thread model: posix Supported LTO compression algorithms: zlib zstd gcc version 12.1.0 (Debian 12.1.0-8) # Libraries # using babl version 0.1.96 (compiled against version 0.1.92) using GEGL version 0.4.38 (compiled against version 0.4.38) using GLib version 2.74.0 (compiled against version 2.72.3) using GdkPixbuf version 2.42.9 (compiled against version 2.42.9) using GTK+ version 2.24.33 (compiled against version 2.24.33) using Pango version 1.50.10 (compiled against version 1.50.9) using Fontconfig version 2.13.1 (compiled against version 2.13.1) using Cairo version 1.16.0 (compiled against version 1.16.0) ``` > fatal error: Speicherzugriffsfehler Stack trace: ``` # Stack traces obtained from PID 11067 - Thread 11067 # [New LWP 11068] [New LWP 11069] [New LWP 11070] [New LWP 11071] [New LWP 11072] [New LWP 11073] [New LWP 11074] [New LWP 11075] [New LWP 11076] [New LWP 11077] [New LWP 11078] [New LWP 11079] [New LWP 11080] [New LWP 11081] [New LWP 11162] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". __GI___libc_read (nbytes=256, buf=0x7fff1aa79e70, fd=16) at ../sysdeps/unix/sysv/linux/read.c:26 Id Target Id Frame * 1Thread 0x7f4ce1a5d380 (LWP 11067) "gimp"__GI___libc_read (nbytes=256, buf=0x7fff1aa79e70, fd=16) at ../sysdeps/unix/sysv/linux/read.c:26 2Thread 0x7f4ce0f22640 (LWP 11068) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 3Thread 0x7f4ce0721640 (LWP 11069) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 4Thread 0x7f4cdff20640 (LWP 11070) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 5Thread 0x7f4cdf71f640 (LWP 11071) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 6Thread 0x7f4cdef1e640 (LWP 11072) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 7Thread 0x7f4cde71d640 (LWP 11073) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 8Thread 0x7f4cddf1c640 (LWP 11074) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 9Thread 0x7f4cdd71b640 (LWP 11075) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 10 Thread 0x7f4cdcf1a640 (LWP 11076) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 11 Thread 0x7f4cb640 (LWP 11077) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 12 Thread 0x7f4cbf7fe640 (LWP 11078) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 13 Thread 0x7f4cbe9ff640 (LWP 11079) "gmain" 0x7f4ce22fda3f in __GI___poll (fds=0x5623a95d3140, nfds=2, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 14 Thread 0x7f4cbe1fe640 (LWP 11080) "gdbus" 0x7f4ce22fda3f in __GI___poll (fds=0x5623a95e7510, nfds=2, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 15 Thread 0x7f4c9d3ff640 (LWP 11081) "async" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 16 Thread 0x7f4c927fc640 (LWP 11162) "swap writer" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 Thread 16 (Thread
Bug#965502: marked as done (dvi2ps: Removal of obsolete debhelper compat 5 and 6 in bookworm)
Your message dated Mon, 03 Oct 2022 10:04:03 + with message-id and subject line Bug#965502: fixed in dvi2ps 5.1j-1.5 has caused the Debian Bug report #965502, regarding dvi2ps: Removal of obsolete debhelper compat 5 and 6 in bookworm to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 965502: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965502 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: dvi2ps Version: 5.1j-1.3 Severity: normal Usertags: compat-5-6-removal Hi, The package dvi2ps uses debhelper with a compat level of 5 or 6, which is deprecated and scheduled for removal[1]. Please bump the debhelper compat at your earliest convenience /outside the freeze/! * Compat 13 is recommended (supported in stable-backports) * Compat 7 is the bare minimum PLEASE KEEP IN MIND THAT the release team *DOES NOT* accept uploads with compat bumps during the freeze. If there is any risk that the fix for this bug might not migrate to testing before 2021-01-01[3] then please postpone the fix until after the freeze. At the time of filing this bug, compat 5 and 6 are expected to be removed "some time during the development cycle of bookworm". Thanks, ~Niels [1] https://lists.debian.org/debian-devel/2020/07/msg00065.html [2] https://release.debian.org/bullseye/FAQ.html [3] The choice of 2021-01-01 as a "deadline" is set before the actual freeze deadline to provide a safe cut off point for most people. Mind you, it is still your responsibility to ensure that the upload makes it into testing even if you upload before that date. --- End Message --- --- Begin Message --- Source: dvi2ps Source-Version: 5.1j-1.5 Done: Bastian Germann We believe that the bug you reported is fixed in the latest version of dvi2ps, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 965...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastian Germann (supplier of updated dvi2ps package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 03 Oct 2022 09:32:23 + Source: dvi2ps Architecture: source Version: 5.1j-1.5 Distribution: unstable Urgency: medium Maintainer: OHURA Makoto Changed-By: Bastian Germann Closes: 965502 Changes: dvi2ps (5.1j-1.5) unstable; urgency=medium . * Non-maintainer upload. * Update to debhelper-compat 10 (Closes: #965502). Checksums-Sha1: 36c8115b470190185e1c565bf4425631fab7e252 1576 dvi2ps_5.1j-1.5.dsc 3b757a7c9e029830ce41736a25ddee46becfa476 22068 dvi2ps_5.1j-1.5.debian.tar.xz 5438159c262fa202f6e393e7a1fcd5ec10bd0ff2 5833 dvi2ps_5.1j-1.5_source.buildinfo Checksums-Sha256: c5adb1155d69688ebb1cfede53b1ab0c592061a77d4762b19deaf6c0aa4eccec 1576 dvi2ps_5.1j-1.5.dsc d918cad51f94c5c800ed47f29671ae434b49c6342d83006a5d36dcd4e2ec 22068 dvi2ps_5.1j-1.5.debian.tar.xz 0d3da9a4ca7ef1e5524e56297aa52f8370f64a01d941f5f9b8bea6e37168eb60 5833 dvi2ps_5.1j-1.5_source.buildinfo Files: 40be3f00122d3c4cf455b2f48175b5fa 1576 tex optional dvi2ps_5.1j-1.5.dsc 3f9b27a7b64b842e32ddf32ed34be456 22068 tex optional dvi2ps_5.1j-1.5.debian.tar.xz df5b19bec5d77215ce203a4438a428ad 5833 tex optional dvi2ps_5.1j-1.5_source.buildinfo -BEGIN PGP SIGNATURE- iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmM6rV8QHGJhZ2VAZGVi aWFuLm9yZwAKCRAfXHqLRVZDFDkGDACxiF+CNN+9ihxdNmaXo61CEJdGvixVJzCu vO+GHzA2ZueZf1W4Z2ZLJuygnLdDprq8NOibGxrN9zLs59lPslwgCM56cbDrCLuZ OzgKZJnlOxJxS0F1VmcSV14HuBnwC/gsaPZsWcUKyq+PBMOzfx/Ugfwq9k4O9urU RCxYtFkUQTw0Ypc1zerjBMOOEdjoAztpg6wPyV8WapiibAZyA9w4DjgRSeWrG1Hh Hm/5pAaVe2q2ZrdJUBhnSHIK+K4dgqKy6z0t/zMXrWV1JBeEYSt+Xao+E4Y4aEop k7yIhBeKLce4v9iWyPNgrQPszs7toIFVAUhyq8OB84aEAva45XBhtER7TvgzqnD/ 0qtQKKBGSIZa1zbr7WjSArW5I5DqPL62diMR9Kv9YFXmRngYX6ExWuoAkzVKx045 RjuUnuebA/KtNQ+V64J+6L15VpZgWLulO/9NKPJKJYijx9WzVwDBVZBHA923O8il XTIvh4C0gtKs5vNNK4D7e1hwejTg2c4= =IYPa -END PGP SIGNATURE End Message ---
Bug#999152: marked as done (xfonts-100dpi: missing required debian/rules targets build-arch and/or build-indep)
Your message dated Mon, 03 Oct 2022 10:06:52 + with message-id and subject line Bug#999152: fixed in xfonts-100dpi 1:1.0.5 has caused the Debian Bug report #999152, regarding xfonts-100dpi: missing required debian/rules targets build-arch and/or build-indep to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 999152: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999152 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: xfonts-100dpi Version: 1:1.0.4+nmu1.1 Severity: important Justification: Debian Policy section 4.9 Tags: bookworm sid User: debian...@lists.debian.org Usertags: missing-build-arch-indep Dear maintainer, Your package does not include build-arch and/or build-indep targets in debian/rules. This is required by Debian Policy section 4.9, since 2012. https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules Please note that this is also a sign that the packaging of this software could benefit from a refresh. For example, packages using 'dh' cannot be affected by this issue. This mass bug filing was discussed on debian-devel@ in https://lists.debian.org/debian-devel/2021/11/msg00052.html . The severity of this bug will be changed to 'serious' after a month. Best, Lucas --- End Message --- --- Begin Message --- Source: xfonts-100dpi Source-Version: 1:1.0.5 Done: Timo Aaltonen We believe that the bug you reported is fixed in the latest version of xfonts-100dpi, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 999...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Timo Aaltonen (supplier of updated xfonts-100dpi package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 03 Oct 2022 12:28:06 +0300 Source: xfonts-100dpi Built-For-Profiles: noudeb Architecture: source Version: 1:1.0.5 Distribution: unstable Urgency: medium Maintainer: Debian X Strike Force Changed-By: Timo Aaltonen Closes: 976571 999152 Changes: xfonts-100dpi (1:1.0.5) unstable; urgency=medium . [ Julien Cristau ] * Add Vcs-* control fields. * Use https for xorg.freedesktop.org URLs in packaging. . [ Simon McVittie ] * d/rules: Add missing build-arch, build-indep targets (Policy §4.9) (Closes: #999152) * d/control: Declare that the build does not require (fake)root * Use dh_update_autotools_config to update config.guess, config.sub (Closes: #976571) . [ Timo Aaltonen ] * control: Migrate to debhelper-compat, bump to 13. * control: Drop versioned constraint on xfonts-utils. * control: Bump policy to 4.6.1. Checksums-Sha1: c33fcc54d0bd2c48a4377780a672a42e756711c5 1689 xfonts-100dpi_1.0.5.dsc 0e6b8a039204ebe74d09ad3b601f636b8c8b2e85 3490487 xfonts-100dpi_1.0.5.tar.gz ecf111432e9133b04a8bca412429d9e16c692601 7617 xfonts-100dpi_1.0.5_source.buildinfo Checksums-Sha256: e1bf4657cb7685cd64719ebe16c2c1df3664c532aad1280aed65a8afc9d618bb 1689 xfonts-100dpi_1.0.5.dsc 9954d42f63ac47b8d8cad48b2d7d4e39e998da818681cabbd42ac0ef43311859 3490487 xfonts-100dpi_1.0.5.tar.gz 1430643ac6b7e753a70044fd14ed8c495e267357ef8beecde35604f749c82daf 7617 xfonts-100dpi_1.0.5_source.buildinfo Files: 6482d05d00961be4aa68ef3c58b71c9f 1689 fonts optional xfonts-100dpi_1.0.5.dsc 2056d82c42a6bfc2a8414b3ede6e5167 3490487 fonts optional xfonts-100dpi_1.0.5.tar.gz eebe22520f450701369f8ec1180344e7 7617 fonts optional xfonts-100dpi_1.0.5_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEdS3ifE3rFwGbS2Yjy3AxZaiJhNwFAmM6q0AACgkQy3AxZaiJ hNx35xAAoO96GHM8QlkQpGUyKt5tZ8zoUNFqovYm0XHgkUI46BcKMWUE1QSxZ4Js tNykfQo8ZCCzRWdp0nUkY/f57qhuEUB5tQHgJBJMFhvRuUjU+nDD2igXFgNgW+uI 6cdA8F9SGuFrPcBtAQwnUZf+zKx7ZdzFvYSi2h9Jtl2wXcBL+5opUU2RIog3MYcv 6w8w2EIAT1PgNtEYgAQUUpxSd1LEr3d1oNlThvD/8XG31guA5R4jHpe//pR2jfaD ECxuqvSWeZR55zdVq8GFOceQ8TkjcdQfd+C2feYCILalsCLolRvZCZ1X6m2wHoM+ WXGfTFLBs8I+iw/xPn3+beW4YHTGxGCGhhJaVSV216Vx60KTXfJ+hT+nq07MLA4g zwZUxS0r2E6T4AWKdjtzRbM/V+kFuobaXwDVmmCDI9aOWeTZnXNCQc0AHPutNeex bVXEFndocuPy+cAicqQ/ZU5jr06g/UOgaBnvn0YULH+FLe7gWaMm1YDKGL07B0pg G1lRq11QeEhNOgYj0iV7aqcFJwDKxOeB7qtIzXYvHLh7vD8nZ/TJakwD3uI0X25z 4PfpPY53Fmg69YQJtC1CJr1ac9IHO8EnUqD0oze
Bug#998154: marked as done (contains non-DSFG-free files)
Your message dated Mon, 03 Oct 2022 11:05:10 + with message-id and subject line Bug#998154: fixed in smlnj 110.79-7 has caused the Debian Bug report #998154, regarding contains non-DSFG-free files to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 998154: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998154 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: smlnj Version: 110.76-2 Severity: serious Tags: upstream Since at least oldoldoldstable, the SML/NJ sources have included non-free files. In 110.76-2, these non-free files include at least ckit.tgz, which contains the files ckit/src/parser/util/error.sml and ckit/src/parser/util/error.sml and ckit/src/parser/util/error-sig.sml. These files are: (* * Copyright (c) 1996 by Satish Chandra, Brad Richards, Mark D. Hill, * James R. Larus, and David A. Wood. * * Teapot is distributed under the following conditions: * * You may make copies of Teapot for your own use and modify those copies. * * All copies of Teapot must retain our names and copyright notice. * * You may not sell Teapot or distributed Teapot in conjunction with a * commercial product or service without the expressed written consent of * the copyright holders. * * THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR IMPLIED * WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF * MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. * *) In the sources for 110.79-6 (unstable), they can be found in extracted form at the same location The restriction on distribution in conjunction with a commercial product or service is in violation of point 6 of the DFSG. -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.14.0-1-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages smlnj depends on: ii smlnj-runtime 110.79-6 Versions of packages smlnj recommends: ii libsmlnj-smlnj 110.79-6 Versions of packages smlnj suggests: pn smlnj-doc -- no debconf information -- |)|/ Ryan Kavanagh | 4E46 9519 ED67 7734 268F |\|\ https://rak.ac | BD95 8F7B F8FC 4A11 C97A signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: smlnj Source-Version: 110.79-7 Done: Barak A. Pearlmutter We believe that the bug you reported is fixed in the latest version of smlnj, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 998...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Barak A. Pearlmutter (supplier of updated smlnj package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 03 Oct 2022 09:27:56 +0100 Source: smlnj Architecture: source Version: 110.79-7 Distribution: unstable Urgency: medium Maintainer: Barak A. Pearlmutter Changed-By: Barak A. Pearlmutter Closes: 837735 998154 Changes: smlnj (110.79-7) unstable; urgency=medium . [ Debian Janitor ] * Trim trailing whitespace. * Use secure URI in debian/watch. * Use secure URI in Homepage field. . [ Barak A. Pearlmutter ] * Cherry-pick upstream copyright fix as patch (closes: #998154) * Bump debhelper from old 9 to 13. * Update standards version to 4.6.1, no changes needed. * Rules do not require root. * Adopt package (closes: #837735) Checksums-Sha1: a8ffc8b0f6f2a8aa58e70fb8ec39e49f086a2f3a 3164 smlnj_110.79-7.dsc 575a91534f5f9ac1b70fb50670e346ac90cab318 19396 smlnj_110.79-7.debian.tar.xz 6aaac51b9939e8afd20c15e9a4f62e95c4678d33 7396 smlnj_110.79-7_source.buildinfo Checksums-Sha256: a15b0b2a1bb31316cc1c7adecaf5f5a4ac7e6c041eb27491b5e7fdc8cd72 3164 smlnj_110.79-7.dsc 078590fbf002ba5c2efbe63b5456295a3a76ef9a9d0346be21b06cd91cef83fc 19396 s
Bug#1020532: gimp: text element crashes gimp
On Mon, 03 Oct 2022 at 11:43:47 +0200, Dr. Nikolaus Klepp wrote: > Ok, after reinstallng gimp I get the same bug, but this time with this crash > text: You don't need to reinstall gimp, but you do need to make sure the libglib2.0-0 package is version 2.74.0-2 or later. It should migrate to testing today, but it might take a day or two for your mirror to catch up. libglib2.0-0 version 2.74.0-1 has the bug that causes this crash, and reporting it again is not going to get it fixed any sooner. libglib2.0-0 version 2.74.0-2 is believed to have a fix for this crash. smcv
Bug#998997: marked as done (xfonts-75dpi: missing required debian/rules targets build-arch and/or build-indep)
Your message dated Mon, 03 Oct 2022 11:57:00 + with message-id and subject line Bug#998997: fixed in xfonts-75dpi 1:1.0.5 has caused the Debian Bug report #998997, regarding xfonts-75dpi: missing required debian/rules targets build-arch and/or build-indep to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 998997: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998997 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: xfonts-75dpi Version: 1:1.0.4+nmu1.1 Severity: important Justification: Debian Policy section 4.9 Tags: bookworm sid User: debian...@lists.debian.org Usertags: missing-build-arch-indep Dear maintainer, Your package does not include build-arch and/or build-indep targets in debian/rules. This is required by Debian Policy section 4.9, since 2012. https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules Please note that this is also a sign that the packaging of this software could benefit from a refresh. For example, packages using 'dh' cannot be affected by this issue. This mass bug filing was discussed on debian-devel@ in https://lists.debian.org/debian-devel/2021/11/msg00052.html . The severity of this bug will be changed to 'serious' after a month. Best, Lucas --- End Message --- --- Begin Message --- Source: xfonts-75dpi Source-Version: 1:1.0.5 Done: Timo Aaltonen We believe that the bug you reported is fixed in the latest version of xfonts-75dpi, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 998...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Timo Aaltonen (supplier of updated xfonts-75dpi package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 03 Oct 2022 12:36:08 +0300 Source: xfonts-75dpi Built-For-Profiles: noudeb Architecture: source Version: 1:1.0.5 Distribution: unstable Urgency: medium Maintainer: Debian X Strike Force Changed-By: Timo Aaltonen Closes: 976471 998997 Changes: xfonts-75dpi (1:1.0.5) unstable; urgency=medium . [ Julien Cristau ] * Update Vcs-Git URL to https. * Switch xorg.freedesktop.org URLs in packaging to https. . [ Simon McVittie ] * d/control: Update Vcs-* for migration to salsa.debian.org * d/rules: Add missing build-arch, build-indep targets (Policy §4.9) (Closes: #998997) * d/control: Declare that the build does not require (fake)root * d/rules: Use dh_update_autotools_config to update config.guess, config.sub (Closes: #976471) . [ Timo Aaltonen ] * control, rules: Migrate to debhelper-compat, bump to 13. * control: Drop versioned constraint on xfonts-utils. * control: Bump policy to 4.6.1. Checksums-Sha1: 9738f7f10754fa3a0c4ca79fb047aa6b392b814b 1675 xfonts-75dpi_1.0.5.dsc 1e917f6b87255fd02132620be8d8939251da9796 2964267 xfonts-75dpi_1.0.5.tar.gz 0d63c39bc58047b6c635b1546a4ae157146130b2 7613 xfonts-75dpi_1.0.5_source.buildinfo Checksums-Sha256: 14aeb34b7d62a2cd2f01ee59b8e648078ff9a243f33b7acd92fe709431139d60 1675 xfonts-75dpi_1.0.5.dsc d0e6777e78ef3ef40ea3860792a7ef13346b658246a1908964ab3b4da2edb73a 2964267 xfonts-75dpi_1.0.5.tar.gz a3e40e404e5b5812deb1c6c4eac0aeb26fc0334080b315861052d97e970966ec 7613 xfonts-75dpi_1.0.5_source.buildinfo Files: 2bd941dd677b529f0143f48fdceac2f3 1675 fonts optional xfonts-75dpi_1.0.5.dsc 6eb1eddd468b90ccdd44faa73b7339f4 2964267 fonts optional xfonts-75dpi_1.0.5.tar.gz 9a87a400c909a884414426eec68e83e4 7613 fonts optional xfonts-75dpi_1.0.5_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEdS3ifE3rFwGbS2Yjy3AxZaiJhNwFAmM6xyIACgkQy3AxZaiJ hNyRvg//YCFNuKAN8Pj1FGyH990UutYKzfEorAlbMByT9T67FlBEBTgj13QEpsyk g+4rA0lUqLvZWlJIUp2XcaIFlzwoSyGfetPyAVcxDY8h1vxea32ktTPK/ZkUDvSJ 5s5++qDiHMPyiSyCGNO6r6UwZqlGuRuCs6P7P/zlqMfPZFSEHJIF03EWy10/UGD1 iSC4lvYvoTxO/jOuylr1DdmhAsyEsWDNbWPU+scN8XkPI1/Hi0vpX4v8VHSH45sh 2NWU4ayNIgnda/D5g7nX7iDuN+CvpOuq5HCvnaTbiZ+osJ73bCetnO3MYH0Hgk3l 9g5lluZok4dM1Q0hl67a4bEpxdOaP2EjXXZrZg+2IXB/yEG7CBN5yaugS0cSewQ+ 7YVvz4OX4jJeruMzitSb3tTNU9zm9etB/kmVpUj3bimP778rOj9czB5EKo6mpogh DbgVcKEwYVM6iHuW/kZla9mhnXgqYiAWstKtb/4oaY9XHNtcvRKvNiqaswdIzb0H JYYU443LmAiCXGU1YberkktPnZ+cdXUa2xjnq
Bug#1021182: xserver-xorg-video-vmware: FTBFS against GCC-12
Package: xserver-xorg-video-vmware
Version: 1:13.3.0-3build1
Severity: serious
Tags: ftbfs patch
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: nathan.teodo...@canonical.com
Dear Maintainer,
I'm forwarding the upstream patch to fix FTBFS against GCC-12.
It was already committed to Ubuntu via LP: #1991117[1].
[1]: https://launchpad.net/bugs/1991117
Author: Rudi Heitbaum
From: Nathan Pratta Teodosio
Origin:
https://gitlab.freedesktop.org/xorg/driver/xf86-video-vmware/-/commit/77b8183b
Date: Sun, 8 May 2022 03:00:10 +
Subject: [PATCH] vmwgfx: fix missing array notation
Applied-Upstream: commit: 77b8183b
Fixes error identified by gcc-12.1.0 compiler
make
CC libvmwgfx_la-vmwgfx_tex_video.lo
vmwgfx_tex_video.c: In function 'stop_video':
vmwgfx_tex_video.c:240:20: error: the comparison will always evaluate as 'true'
for the address of 'yuv' will never be NULL [-Werror=address]
240 |if (priv->yuv[i]) {
|^~~~
---
vmwgfx/vmwgfx_tex_video.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/vmwgfx/vmwgfx_tex_video.c b/vmwgfx/vmwgfx_tex_video.c
index acc2b56..480a5f1 100644
--- a/vmwgfx/vmwgfx_tex_video.c
+++ b/vmwgfx/vmwgfx_tex_video.c
@@ -237,7 +237,7 @@ stop_video(ScrnInfoPtr pScrn, pointer data, Bool shutdown)
for (i=0; i<3; ++i) {
for (j=0; j<2; ++j) {
- if (priv->yuv[i]) {
+ if (priv->yuv[j][i]) {
xa_surface_destroy(priv->yuv[j][i]);
priv->yuv[j][i] = NULL;
}
Bug#1020007: marked as done (user-mode-linux: FTBFS: build-dependency not installable: linux-source-5.18)
Your message dated Mon, 03 Oct 2022 12:23:59 + with message-id and subject line Bug#1020007: fixed in user-mode-linux 5.19um1 has caused the Debian Bug report #1020007, regarding user-mode-linux: FTBFS: build-dependency not installable: linux-source-5.18 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1020007: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020007 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: user-mode-linux Version: 5.18um1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220917 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper (>> 12.0.0), quilt, linux-source-5.18, > docbook-to-man, xz-utils, m4, kmod, libvdeplug-dev | libvdeplug2-dev, > libpcap-dev, bc, dpkg (>= 1.16.2), libssl-dev, bison, flex, gcc-multilib, > build-essential, fakeroot > Filtered Build-Depends: debhelper (>> 12.0.0), quilt, linux-source-5.18, > docbook-to-man, xz-utils, m4, kmod, libvdeplug-dev, libpcap-dev, bc, dpkg (>= > 1.16.2), libssl-dev, bison, flex, gcc-multilib, build-essential, fakeroot > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [957 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [471 B] > Get:5 copy:/<>/apt_archive ./ Packages [548 B] > Fetched 1976 B in 0s (145 kB/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > 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: > sbuild-build-depends-main-dummy : Depends: linux-source-5.18 but it is not > installable > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://qa-logs.debian.net/2022/09/17/user-mode-linux_5.18um1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220917;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220917&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: user-mode-linux Source-Version: 5.19um1 Done: Ritesh Raj Sarraf We believe that the bug you reported is fixed in the latest version of user-mode-linux, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1020...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ritesh Raj Sarraf (supplier of updated user-mode-linux package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 30 Sep 2022 20:38:23 +0530 Source: user-mode-linux Architecture:
Bug#1012885: abseil: Patch
Source: abseil
Version: 0~20210324.2-4.
Followup-For: Bug #1012885
X-Debbugs-Cc: nathan.teodo...@canonical.com
Dear Maintainer,
I'm forwarding the from upstream patch to fix this issue.
Already committed to Ubuntu Kinetic (LP: #1991253[1])
[1]: https://launchpad.net/bugs/1991253
From: Derek Mauro
Date: Wed, 15 Jun 2022 07:42:49 -0700
Subject: [PATCH] any_test: expand the any emplace bug suppression, since it
has gotten worse in GCC 12
Applied-Upstream: commit: a184bab83ffcffc2aaac49a3900361158ab3890f
PiperOrigin-RevId: 455128070
Change-Id: Ia866e59d4e2e810aea16afe492d58013c5661a2b
---
absl/types/any_test.cc | 33 +++--
1 file changed, 15 insertions(+), 18 deletions(-)
diff --git a/absl/types/any_test.cc b/absl/types/any_test.cc
index 70e4ba22b1..d382b927c2 100644
--- a/absl/types/any_test.cc
+++ b/absl/types/any_test.cc
@@ -754,26 +754,23 @@ TEST(AnyTest, FailedCopy) {
// Test the guarantees regarding exceptions in emplace.
TEST(AnyTest, FailedEmplace) {
- {
-BadCopyable bad;
-absl::any target;
-ABSL_ANY_TEST_EXPECT_BAD_COPY(target.emplace(bad));
- }
+ BadCopyable bad;
+ absl::any target;
+ ABSL_ANY_TEST_EXPECT_BAD_COPY(target.emplace(bad));
+}
- {
-BadCopyable bad;
-absl::any target(absl::in_place_type);
-ABSL_ANY_TEST_EXPECT_BAD_COPY(target.emplace(bad));
-#if defined(ABSL_USES_STD_ANY) && defined(__GLIBCXX__)
-// libstdc++ std::any::emplace() implementation (as of 7.2) has a bug: if
an
-// exception is thrown, *this contains a value.
-#define ABSL_GLIBCXX_ANY_EMPLACE_EXCEPTION_BUG 1
-#endif
-#if defined(ABSL_HAVE_EXCEPTIONS) && \
-!defined(ABSL_GLIBCXX_ANY_EMPLACE_EXCEPTION_BUG)
-EXPECT_FALSE(target.has_value());
+// GCC and Clang have a bug here.
+// Ine some cases, the exception seems to be thrown at the wrong time, and
+// target may contain a value.
+#ifdef __GNUC__
+TEST(AnyTest, DISABLED_FailedEmplaceInPlace) {
+#else
+TEST(AnyTest, FailedEmplaceInPlace) {
#endif
- }
+ BadCopyable bad;
+ absl::any target(absl::in_place_type);
+ ABSL_ANY_TEST_EXPECT_BAD_COPY(target.emplace(bad));
+ EXPECT_FALSE(target.has_value());
}
} // namespace
Bug#1020307: marked as done (src:qtfeedback-opensource-src: fails to migrate to testing for too long: uploader built arch:all binaries)
Your message dated Mon, 03 Oct 2022 12:35:15 + with message-id and subject line Bug#1020307: fixed in qtfeedback-opensource-src 5.0~git20180903.a14bd0b-5 has caused the Debian Bug report #1020307, regarding src:qtfeedback-opensource-src: fails to migrate to testing for too long: uploader built arch:all binaries to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1020307: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020307 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: qtfeedback-opensource-src Version: 5.0~git20180903.a14bd0b-3 Severity: serious Control: close -1 5.0~git20180903.a14bd0b-4 Tags: sid bookworm pending 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 60 days as having a Release Critical bug in testing [1]. Your package src:qtfeedback-opensource-src has been trying to migrate for 61 days [2]. Hence, I am filing this bug. 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 bookworm, so it doesn't affect (old-)stable. Your package is only blocked because the arch:all binary package(s) aren't built on a buildd. Unfortunately the Debian infrastructure doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will shortly do a no-changes source-only upload to DELAYED/15, closing this bug. Please let me know if I should delay or cancel that upload. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=qtfeedback-opensource-src OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: qtfeedback-opensource-src Source-Version: 5.0~git20180903.a14bd0b-5 Done: Mike Gabriel We believe that the bug you reported is fixed in the latest version of qtfeedback-opensource-src, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1020...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mike Gabriel (supplier of updated qtfeedback-opensource-src package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 03 Oct 2022 14:05:07 +0200 Source: qtfeedback-opensource-src Architecture: source Version: 5.0~git20180903.a14bd0b-5 Distribution: unstable Urgency: medium Maintainer: Debian Qt/KDE Maintainers Changed-By: Mike Gabriel Closes: 1020307 Changes: qtfeedback-opensource-src (5.0~git20180903.a14bd0b-5) unstable; urgency=medium . * Re-upload source-only to unstable as is. (Closes: #1020307). Checksums-Sha1: 6b979935299a5c478c159bc90052b7f2064a 2754 qtfeedback-opensource-src_5.0~git20180903.a14bd0b-5.dsc 25e399cafe99b6ef804980d267fb459d08999010 10104 qtfeedback-opensource-src_5.0~git20180903.a14bd0b-5.debian.tar.xz bde5e4595d6ff90a3ea4e46f569a37a6e060ffe8 13970 qtfeedback-opensource-src_5.0~git20180903.a14bd0b-5_source.buildinfo Checksums-Sha256: d0be7793ea3258fb8c4bf1261e11ed198a72999c0f8e1e5917edb65343c1561c 2754 qtfeedback-opensource-src_5.0~git20180903.a14bd0b-5.dsc 2be342397ca47e8ef0a2795d674af6c5860a9fcabd5a0ab85f59fb6b68eee89d 10104 qtfeedback-opensource-src_5.0~git20180903.a14bd0b-5.debian.tar.xz 0d336676deabefeafa0d2f2f3479aa5e7cf9a67e585f09d83f44962d755edf3e 13970 qtfeedback-opensource-src_5.0~git20180903.a14bd0b-5_source.buil
Processed: Bug#1021163 marked as pending in lomiri-indicator-network
Processing control commands: > tag -1 pending Bug #1021163 [src:lomiri-indicator-network] lomiri-indicator-network: binary-all FTBFS Added tag(s) pending. -- 1021163: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021163 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1021163: marked as pending in lomiri-indicator-network
Control: tag -1 pending Hello, Bug #1021163 in lomiri-indicator-network reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/ubports-team/lomiri-indicator-network/-/commit/713420f7f651e2c05d36a9e7fe5551a00f7a9427 debian/lomiri-indicator-network.install: Fix some installation paths. (Closes: #1021163, #1021164). (this message was generated automatically) -- Greetings https://bugs.debian.org/1021163
Bug#1021164: marked as pending in lomiri-indicator-network
Control: tag -1 pending Hello, Bug #1021164 in lomiri-indicator-network reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/ubports-team/lomiri-indicator-network/-/commit/713420f7f651e2c05d36a9e7fe5551a00f7a9427 debian/lomiri-indicator-network.install: Fix some installation paths. (Closes: #1021163, #1021164). (this message was generated automatically) -- Greetings https://bugs.debian.org/1021164
Processed: Bug#1021164 marked as pending in lomiri-indicator-network
Processing control commands: > tag -1 pending Bug #1021164 [src:lomiri-indicator-network] lomiri-indicator-network: binary-any FTBFS Added tag(s) pending. -- 1021164: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021164 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1021163: marked as done (lomiri-indicator-network: binary-all FTBFS)
Your message dated Mon, 03 Oct 2022 13:04:27 + with message-id and subject line Bug#1021163: fixed in lomiri-indicator-network 1.0.0~git20220718.2ca3619-3 has caused the Debian Bug report #1021163, regarding lomiri-indicator-network: binary-all FTBFS to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1021163: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021163 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: lomiri-indicator-network Version: 1.0.0~git20220718.2ca3619-2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=lomiri-indicator-network&arch=all&ver=1.0.0~git20220718.2ca3619-2&stamp=1664719442&raw=0 ... debian/rules override_dh_missing make[1]: Entering directory '/<>' dh_missing --fail-missing dh_missing: warning: usr/libexec/lomiri-indicator-network/lomiri-indicator-network-secret-agent exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/libexec/lomiri-indicator-network/lomiri-indicator-network-service exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/share/unity/indicators/com.lomiri.indicator.network exists in debian/tmp but is not installed to anywhere dh_missing: error: missing files, aborting The following debhelper tools have reported what they installed (with files per package) * dh_install: liblomiri-connectivity-qt1-1 (1), liblomiri-connectivity-qt1-dev (3), lomiri-connectivity-doc (3), lomiri-indicator-network (4), qml-module-lomiri-connectivity (1) * dh_installdocs: liblomiri-connectivity-qt1-1 (0), liblomiri-connectivity-qt1-dev (0), lomiri-connectivity-doc (0), lomiri-indicator-network (3), qml-module-lomiri-connectivity (0) * dh_installexamples: liblomiri-connectivity-qt1-1 (0), liblomiri-connectivity-qt1-dev (3), lomiri-connectivity-doc (0), lomiri-indicator-network (0), qml-module-lomiri-connectivity (0) If the missing files are installed by another tool, please file a bug against it. When filing the report, if the tool is not part of debhelper itself, please reference the "Logging helpers and dh_missing" section from the "PROGRAMMING" guide for debhelper (10.6.3+). (in the debhelper package: /usr/share/doc/debhelper/PROGRAMMING.gz) Be sure to test with dpkg-buildpackage -A/-B as the results may vary when only a subset is built If the omission is intentional or no other helper can take care of this consider adding the paths to debian/not-installed. make[1]: *** [debian/rules:31: override_dh_missing] Error 25 --- End Message --- --- Begin Message --- Source: lomiri-indicator-network Source-Version: 1.0.0~git20220718.2ca3619-3 Done: Mike Gabriel We believe that the bug you reported is fixed in the latest version of lomiri-indicator-network, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1021...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mike Gabriel (supplier of updated lomiri-indicator-network package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 03 Oct 2022 14:45:30 +0200 Source: lomiri-indicator-network Architecture: source Version: 1.0.0~git20220718.2ca3619-3 Distribution: unstable Urgency: medium Maintainer: Debian UBports Team Changed-By: Mike Gabriel Closes: 1021163 1021164 Changes: lomiri-indicator-network (1.0.0~git20220718.2ca3619-3) unstable; urgency=medium . * debian/lomiri-indicator-network.install: + Fix some installation paths. (Closes: #1021163, #1021164). Checksums-Sha1: 8d0a3ccb19616943eed94d7279c90b8c6e157ddb 3213 lomiri-indicator-network_1.0.0~git20220718.2ca3619-3.dsc 7e2122d17168e54662ca00d8d464e7f47795be3f 22108 lomiri-indicator-network_1.0.0~git20220718.2ca3619-3.debian.tar.xz e03237bc7918d3ef7cfdcc236054af52f6de1d35 16400 lomiri-indicator-network_1.0.0~git20220718.2ca3619-3_source.buildinfo Checksums-Sha256: 3a8c51904205fec3fe815b0dba15082a046d4ad941966c1dee6a7e15d2c9a2d4 3213 lomiri-indicator-network_1.0.0~git20220718.2ca3619-3.dsc 97bd57ac1467f3366451d9bd57ec12e655cee430022d52b72909714e19063f31 22108
Bug#1021164: marked as done (lomiri-indicator-network: binary-any FTBFS)
Your message dated Mon, 03 Oct 2022 13:04:27 + with message-id and subject line Bug#1021164: fixed in lomiri-indicator-network 1.0.0~git20220718.2ca3619-3 has caused the Debian Bug report #1021164, regarding lomiri-indicator-network: binary-any FTBFS to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1021164: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021164 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: lomiri-indicator-network Version: 1.0.0~git20220718.2ca3619-2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=lomiri-indicator-network&ver=1.0.0~git20220718.2ca3619-2 ... debian/rules override_dh_install make[1]: Entering directory '/<>' # drop upstart files rm -Rfv debian/tmp/usr/share/upstart/ removed 'debian/tmp/usr/share/upstart/xdg/autostart/lomiri-indicator-network.desktop' removed directory 'debian/tmp/usr/share/upstart/xdg/autostart' removed directory 'debian/tmp/usr/share/upstart/xdg' removed 'debian/tmp/usr/share/upstart/systemd-session/upstart/lomiri-indicator-network-secret-agent.override' removed 'debian/tmp/usr/share/upstart/systemd-session/upstart/lomiri-indicator-network.override' removed directory 'debian/tmp/usr/share/upstart/systemd-session/upstart' removed directory 'debian/tmp/usr/share/upstart/systemd-session' removed 'debian/tmp/usr/share/upstart/sessions/lomiri-indicator-network-secret-agent.conf' removed 'debian/tmp/usr/share/upstart/sessions/lomiri-indicator-network.conf' removed directory 'debian/tmp/usr/share/upstart/sessions' removed directory 'debian/tmp/usr/share/upstart/' # empty directory rmdir debian/tmp/usr/share/doc/lomiri-connectivity-doc/qml/html/images/ dh_install dh_install: warning: Cannot find (any matches for) "usr/share/ayatana/indicators/com.lomiri.indicator.network" (tried in ., debian/tmp) dh_install: warning: lomiri-indicator-network missing files: usr/share/ayatana/indicators/com.lomiri.indicator.network dh_install: warning: Cannot find (any matches for) "usr/lib/*/lomiri-indicator-network/*" (tried in ., debian/tmp) dh_install: warning: lomiri-indicator-network missing files: usr/lib/*/lomiri-indicator-network/* dh_install: error: missing files, aborting make[1]: *** [debian/rules:28: override_dh_install] Error 25 --- End Message --- --- Begin Message --- Source: lomiri-indicator-network Source-Version: 1.0.0~git20220718.2ca3619-3 Done: Mike Gabriel We believe that the bug you reported is fixed in the latest version of lomiri-indicator-network, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1021...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mike Gabriel (supplier of updated lomiri-indicator-network package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 03 Oct 2022 14:45:30 +0200 Source: lomiri-indicator-network Architecture: source Version: 1.0.0~git20220718.2ca3619-3 Distribution: unstable Urgency: medium Maintainer: Debian UBports Team Changed-By: Mike Gabriel Closes: 1021163 1021164 Changes: lomiri-indicator-network (1.0.0~git20220718.2ca3619-3) unstable; urgency=medium . * debian/lomiri-indicator-network.install: + Fix some installation paths. (Closes: #1021163, #1021164). Checksums-Sha1: 8d0a3ccb19616943eed94d7279c90b8c6e157ddb 3213 lomiri-indicator-network_1.0.0~git20220718.2ca3619-3.dsc 7e2122d17168e54662ca00d8d464e7f47795be3f 22108 lomiri-indicator-network_1.0.0~git20220718.2ca3619-3.debian.tar.xz e03237bc7918d3ef7cfdcc236054af52f6de1d35 16400 lomiri-indicator-network_1.0.0~git20220718.2ca3619-3_source.buildinfo Checksums-Sha256: 3a8c51904205fec3fe815b0dba15082a046d4ad941966c1dee6a7e15d2c9a2d4 3213 lomiri-indicator-network_1.0.0~git20220718.2ca3619-3.dsc 97bd57ac1467f3366451d9bd57ec12e655cee430022d52b72909714e19063f31 22108 lomiri-indicator-network_1.0.0~git20220718.2ca3619-3.debian.tar.xz edbb43a32e9734e94341415f1d452ba6084167800167955fd530ebbe953d7a09 16400 lomiri-indicator-network_1.0.0~git20220718.2ca3619-3_source.buildinfo Files: 372e1ae39f98074fb34a79bbf50372a4 3213 misc optional lomiri-indicator-network_1.0.0~git20220718.2ca3619-3.
Bug#1021193: binutils-arm-none-eabi ftbfs
Package: src:binutils-arm-none-eabi Version: 17 Severity: serious Tags: sid bookworm setting deb_upstream_version in debian/rules fails: $ echo 2.39-1+17 | cut -d. -f1-3 2.39-1+17 That should work as well: $ echo 2.39-1ubuntu1+17ubuntu1 | cut -d. -f1-3 2.39-1ubuntu1+17ubuntu1 using | sed 's/-.*$//' instead of the cut command should work in both cases.
Processed: Bug#1021139 marked as pending in barbican
Processing control commands: > tag -1 pending Bug #1021139 [src:barbican] barbican: CVE-2022-3100 Added tag(s) pending. -- 1021139: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021139 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1021139: marked as pending in barbican
Control: tag -1 pending Hello, Bug #1021139 in barbican reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/services/barbican/-/commit/a0859b04a217d5578eaaa54df888cb6d8b817ddc * CVE-2022-3100: access policy bypass via query string injection. Added upstream patch: query_string_were_mistakenly_being_used_in_the_patch (Closes: #1021139). (this message was generated automatically) -- Greetings https://bugs.debian.org/1021139
Processed: tagging 1009031
Processing commands for cont...@bugs.debian.org: > # at least no public fix available > tags 1009031 - fixed-upstream Bug #1009031 [libgit-raw-perl] libgit-raw-perl: FTBFS with libgit2 1.3.0 Removed tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 1009031: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009031 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1009643: [Pkg-puppet-devel] Bug#1009643: Puppet: Fails to work with Ruby 3.0
Hi! * Antoine Beaupré [Tue Aug 30, 2022 at 05:15:58PM -0400]: > On 2022-08-25 14:19:42, Antoine Beaupré wrote: > > > For what it's worth, I have tested lavamind's Puppet 7 package from > > experimental, on bookworm, and it works fine: > > > > https://tracker.debian.org/pkg/puppet-agent > > > > ... I am not sure how to express this in the BTS here, because it's a > > different source package, so I can't mark it as fixed there without > > first marking it as affecting that other package, but it never affected > > it. > > The correct way seems to be to move this bug report back to src:puppet > where it belongs, which this message should do. AFAICT (thanks to our daily Grml ISO builds) this RC bug caused puppet to get removed from Debian/testing, so unless this gets fixed we won't have puppet in bookworm? Is anyone taking care of this? regards -mika- signature.asc Description: PGP signature
Bug#1009643: [Pkg-puppet-devel] Bug#1009643: Puppet: Fails to work with Ruby 3.0
On 2022-10-03 18:21:46, Michael Prokop wrote: > AFAICT (thanks to our daily Grml ISO builds) this RC bug caused > puppet to get removed from Debian/testing, so unless this gets fixed > we won't have puppet in bookworm? Is anyone taking care of this? Puppet 5 has been EOL for years. It's a good thing it's gone from bookworm, and a deliberate act on part of the Puppet package maintainers. We've packaged puppet-agent 7 and uploaded to unstable, it should trickle down in bookworm in a day or two if all goes well. We're working on packaging puppetserver 7. You can follow that work and more here: https://wiki.debian.org/Teams/Puppet/Work A. -- Imagine a world in which every single person on the planet is given free access to the sum of all human knowledge. - Jimmy Wales, co-founder of Wikipedia
Bug#1009643: [Pkg-puppet-devel] Bug#1009643: Puppet: Fails to work with Ruby 3.0
* Antoine Beaupré [Mon Oct 03, 2022 at 12:28:06PM -0400]: > On 2022-10-03 18:21:46, Michael Prokop wrote: > > AFAICT (thanks to our daily Grml ISO builds) this RC bug caused > > puppet to get removed from Debian/testing, so unless this gets fixed > > we won't have puppet in bookworm? Is anyone taking care of this? > > Puppet 5 has been EOL for years. It's a good thing it's gone from > bookworm, and a deliberate act on part of the Puppet package > maintainers. ACK :) > We've packaged puppet-agent 7 and uploaded to unstable, it should > trickle down in bookworm in a day or two if all goes well. Oh, that's great news! :) > We're working on packaging puppetserver 7. You can follow that work and > more here: > https://wiki.debian.org/Teams/Puppet/Work Thanks, both for your fast response as well as working on the puppet packaging! \o/ regards -mika- signature.asc Description: PGP signature
Processed: Re: Bug#1019974: uim: FTBFS on armhf: [Makefile:871: installed-modules.scm] Segmentation fault
Processing control commands: > tags -1 patch Bug #1019974 [src:uim] uim: FTBFS on armel/armhf: [Makefile:871: installed-modules.scm] Segmentation fault Added tag(s) patch. -- 1019974: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019974 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1019974: uim: FTBFS on armhf: [Makefile:871: installed-modules.scm] Segmentation fault
Control: tags -1 patch On Sat, Sep 17, 2022 at 09:43:49PM +0300, Dmitry Shachnev wrote: >... > make -C ../uim uim-module-manager && \ > LIBUIM_SYSTEM_SCM_FILES=/home/mitya57/uim-1.8.8/sigscheme/lib > LIBUIM_SCM_FILES=/home/mitya57/uim-1.8.8/scm > LIBUIM_PLUGIN_LIB_DIR=/home/mitya57/uim-1.8.8/uim/.libs UIM_DISABLE_NOTIFY=1 > ../uim/uim-module-manager \ > --path ../scm --register "anthy" "anthy-utf8" "skk" "tutcode" > "byeoru" "latin" "elatin" "m17nlib" "xmload" "pyload" "viqr" "ipa-x-sampa" > "look" "ajax-ime" "google-cgiapi-jp" "baidu-olime-jp" "yahoo-jp" > make[3]: Entering directory '/home/mitya57/uim-1.8.8/uim' > make[3]: 'uim-module-manager' is up to date. > make[3]: Leaving directory '/home/mitya57/uim-1.8.8/uim' > make[2]: *** [Makefile:871: installed-modules.scm] Segmentation fault > > Full build log is attached. > > This can also be seen on reproducible builds server: > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/armhf/uim.html > > Also attached is valgrind output of the failed command. The workaround below fixes the build. I looked through the backtrace in gdb, but debugging a Scheme interpreter is outside of what I am feeling comfortable doing. > Dmitry Shachnev cu Adrian --- debian/rules.old2022-10-03 08:32:51.572032357 + +++ debian/rules2022-10-03 08:34:11.469273120 + @@ -8,6 +8,12 @@ export DEB_LDFLAGS_MAINT_APPEND = -Wl,--as-needed +# workaround for #1019974 +ifneq (,$(filter $(DEB_HOST_ARCH), armel armhf x32)) + export DEB_CFLAGS_MAINT_APPEND += -O1 +endif + + DPKG_EXPORT_BUILDFLAGS = 1 include /usr/share/dpkg/buildflags.mk
Bug#1020692: marked as done (Proposed RM: condor -- RoQA; unmaintained in Debian; depends on Python2; RC buggy)
Your message dated Mon, 3 Oct 2022 19:29:45 +0200 with message-id and subject line Re: Proposed RM: condor -- RoQA; unmaintained in Debian; depends on Python2; RC buggy has caused the Debian Bug report #1020692, regarding Proposed RM: condor -- RoQA; unmaintained in Debian; depends on Python2; RC buggy to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1020692: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020692 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: condor Version: 8.6.8~dfsg.1-2 Severity: serious I propose to remove src:condor for Debian. It looks unmaintained, still depends on Python2 and has various RC bugs open for a long time. If there are no objections, I'll reassign the bug in two weeks (or later) to the ftp.debian.org metapackage. Ansgar --- End Message --- --- Begin Message --- On Sun, 25 Sep 2022 13:59:47 +0200 Ansgar wrote: I propose to remove src:condor for Debian. It looks unmaintained, still depends on Python2 and has various RC bugs open for a long time. If there are no objections, I'll reassign the bug in two weeks (or later) to the ftp.debian.org metapackage. Hi Ansgar, Please see the RM effort at #1020692. Closing this in favour of that bug. Thanks, Bastian--- End Message ---
Processed: [bts-link] source package src:joblib
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:joblib > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #1020820 (http://bugs.debian.org/1020820) > # Bug title: joblib: CVE-2022-21797 > # * https://github.com/joblib/joblib/issues/1128 > # * remote status changed: (?) -> closed > # * closed upstream > tags 1020820 + fixed-upstream Bug #1020820 [src:joblib] joblib: CVE-2022-21797 Added tag(s) fixed-upstream. > usertags 1020820 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 1020820: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020820 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1021043: closed by Debian FTP Masters (reply to Dennis Filder ) (Bug#1021043: fixed in linphone 5.0.37-6)
On Mon 2022-10-03 08:51:05 +, Debian Bug Tracking System wrote: > linphone (5.0.37-6) unstable; urgency=medium > . >* Import upstream fix for crashes on PUBLISH messages without > SIP-Etags (Closes: #1021043). Dennis, thanks for this prompt fix! To confirm: I've upgraded to liblinphone10 5.0.37-6, and linphone-desktop works for me again without any of the crashes i was seeing. With great appreciation, --dkg signature.asc Description: PGP signature
Processed: found 1021139 in 1:11.0.0-3
Processing commands for cont...@bugs.debian.org: > found 1021139 1:11.0.0-3 Bug #1021139 [src:barbican] barbican: CVE-2022-3100 Marked as found in versions barbican/1:11.0.0-3. > thanks Stopping processing here. Please contact me if you need assistance. -- 1021139: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021139 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1021121: marked as done (not installable due to new python3-matrix-nio)
Your message dated Mon, 03 Oct 2022 18:35:55 + with message-id and subject line Bug#1021121: fixed in pantalaimon 0.10.5-1 has caused the Debian Bug report #1021121, regarding not installable due to new python3-matrix-nio to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1021121: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021121 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-pantalaimon Version: 0.10.4-2 Severity: grave Tags: fixed-upstream Hi, I've uploaded python3-matrix-nio 0.20.0 to unstable to close a security issue. Sadly python3-pantalaimon has a versioned dependency making it now uninstallable: python3-matrix-nio (<< 0.20). There is a new upstream version (0.10.5) bumping just this dependency so I would propose to rather drop the version locking. I'm filling this bug instead as the package is already in the group. Cheers Jochen --- End Message --- --- Begin Message --- Source: pantalaimon Source-Version: 0.10.5-1 Done: Jochen Sprickerhof We believe that the bug you reported is fixed in the latest version of pantalaimon, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1021...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jochen Sprickerhof (supplier of updated pantalaimon package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 03 Oct 2022 20:09:20 +0200 Source: pantalaimon Architecture: source Version: 0.10.5-1 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Jochen Sprickerhof Closes: 1021121 Changes: pantalaimon (0.10.5-1) unstable; urgency=medium . * QA upload. * New upstream version * Drop version restriction (Closes: #1021121) Checksums-Sha1: 1463a8ee7b900713dd68e61d6cbc60a9362b44f1 2357 pantalaimon_0.10.5-1.dsc 4f4247bc69c4a80069bf5e20c380bbc09606b544 2495662 pantalaimon_0.10.5.orig.tar.gz 62c157c9112275be581b678c7306463d779a2c8e 4296 pantalaimon_0.10.5-1.debian.tar.xz 2b9311c8437d15680b7703704445d3eafff0b923 8068 pantalaimon_0.10.5-1_source.buildinfo Checksums-Sha256: 62b2c88eb4ddda731d52871e54b7697bcd5ad59ffc2e99dd21ce3a165a10e3d7 2357 pantalaimon_0.10.5-1.dsc 970e79db0692a23c0e2d7f6ee9e3cd67b482b5a3fcb739cc899806494748db77 2495662 pantalaimon_0.10.5.orig.tar.gz 770c3b9b936faa94d9776a244319bc34768b04ee75307102e62e5df70c11cb7f 4296 pantalaimon_0.10.5-1.debian.tar.xz 57957d372419225164fefeb7a51c811fb2f1f5e856136ca3a34f4c9d0919c45b 8068 pantalaimon_0.10.5-1_source.buildinfo Files: e82acc45382fa7a14d75169bd66a587f 2357 net optional pantalaimon_0.10.5-1.dsc 5beb37157633007e96a7ba8965367a4d 2495662 net optional pantalaimon_0.10.5.orig.tar.gz e867362d26b4107e2bf250d05a4f5609 4296 net optional pantalaimon_0.10.5-1.debian.tar.xz 8cd5cca5bf8e935172b76d99e5cb7886 8068 net optional pantalaimon_0.10.5-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEc7KZy9TurdzAF+h6W//cwljmlDMFAmM7J4wACgkQW//cwljm lDNIMA//eN0ogaB2VnrP5jgFG/AIGTsnQ8WLGm6GUe7ARYigj1TliURKEnQVYHCl PwGgpJzCeXb0fdiZvPhcKQ5RtRzzIse4h1u2vxqh33nmqdHhhfGeHO6i7IxPrQO/ n3mCt18jTUjPO2tdf40AEtDfisd33WPEhx4YLgb1dl2ZefKm7jHyf10FVUILcFf5 iRhvd3BY7GbwsG/4TICiouBJTPzRhj2Kea6+C7g/F2VIBC3f1nSUC4Av/1sjec+q fSS9GnYyJNV8vdiTAhi0snupOmb/JJZWUrI776U7lXQDW/BACLrzauWTmXyWPzC4 DwCseZQPS5tvW5GpIvuMEiQTRD7LrCceI/a8VswyQtwsbLMayZ5OlbsxKmujQeHr 89D1ABIATfGfC1I8zY2aBcBjQ3ln3h4Nl79ol3fFFaCy4LUxr2QFK2AHrfcBDkt+ Oq2eJnTMcneMs3/OCfg/FsFCupEhJYb6ppB8ESKB+eXkf1uwPhx8r32JLeu0lfLA sqbBK9nX/Pv7Am1X99kadpHkZ7oEvAsY3q4fTeAJ+XjIGZM+YmSOhUAum/6JPBCc Xr9likoUxkHWLXNXqcGyT83nExskmdSm0TgtWvrd5wTZ7FJKQv5xRThhE9+4/u// +eIqoh5Qhs/9Df4TlCMkdVuldLA7LtW3LHEfnerr9wx/8pGXpOQ= =UmvT -END PGP SIGNATURE End Message ---
Bug#1021032: Your mail
On Mon, 3 Oct 2022 07:46:54 +0100 Rik Mills wrote: ... > Since it seems to affect only the Qt UI, it is most probably a > problem with the last Qt update. Again, please check with > --no-embedded-video." > > I have the same black screen problem. "vlc --no-embedded-video" circumvents/solves the problem. My timeline as well strengthens your statement that QT might be responsible for the black screen as this fits my update timeline: last vlc update was September, 23., and it worked until yesterdays QT update. Thanks Michael
Bug#968997: fwupdmgr: "Successfully" updates BIOS firmware, no effect on reboot
On Fri, 10 Sep 2021 10:35:31 +0200 Julian Andres Klode wrote: Control: reassign -1 shim Control: affects -1 fwupd On Fri, Sep 10, 2021 at 09:27:11AM +0200, Norbert Schulz wrote: > Package: fwupd > Version: 1.2.14-1~deb10u1 > Followup-For: Bug #968997 > > Dear Maintainer, > > this bug still exist for a long time. I removed all packages relating fwupd and install it from scratch but > no install of the firmware on reboot. Sure, that's expected, shim 15.4 is not able to load fwupd without additional patches, which have not been applied yet, so it's not going to get better by reinstalling fwupd. shim-unsigned has been updated to 15.6 which has the right patches in. But for some reason, shim-signed is still at 15.4.
Processed: Set severity to grave
Processing commands for cont...@bugs.debian.org: > severity 1001064 grave Bug #1001064 [src:electrum] electrum: Please package new upstream release Bug #1012361 [src:electrum] New upstream version 4.2.2 Severity set to 'grave' from 'wishlist' Severity set to 'grave' from 'wishlist' > thanks Stopping processing here. Please contact me if you need assistance. -- 1001064: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001064 1012361: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012361 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1021032: VLC sound
Hi! Has anyone noticed the actual version on Sid and the previous one do not reproduce sound from videos with AAC audio? I have some MKV videos with AAC ( aac (LC), 48000 Hz, 5.1, fltp) and they sound nicely in any other player but complete silence with VLC. I don't know if it could be related to this bug. Should I create a new bug? Thank you
Bug#968997: fwupdmgr: "Successfully" updates BIOS firmware, no effect on reboot
On Mon, Oct 03, 2022 at 09:22:02PM +0200, Vincent Bernat wrote: >On Fri, 10 Sep 2021 10:35:31 +0200 Julian Andres Klode >wrote: >> Control: reassign -1 shim >> Control: affects -1 fwupd >> >> On Fri, Sep 10, 2021 at 09:27:11AM +0200, Norbert Schulz wrote: >> > Package: fwupd >> > Version: 1.2.14-1~deb10u1 >> > Followup-For: Bug #968997 >> > > Dear Maintainer, >> > > this bug still exist for a long time. I removed all packages relating >> fwupd and install it from scratch but > no install of the firmware on >> reboot. >> >> Sure, that's expected, shim 15.4 is not able to load fwupd without >> additional patches, which have not been applied yet, so it's >> not going to get better by reinstalling fwupd. > >shim-unsigned has been updated to 15.6 which has the right patches in. But >for some reason, shim-signed is still at 15.4. We've had problems in submitting shim 15.6 to Microsoft for signing. We're working on a solution, but it's going to take a little longer yet. -- Steve McIntyre, Cambridge, UK.st...@einval.com < liw> everything I know about UK hotels I learned from "Fawlty Towers"
Processed: librust-libgit2-sys-dev: Depends: libgit2-dev (< 1.4~~) but 1.5.0+ds-6 is to be installed
Processing control commands: > affects -1 src:rust-bat src:rust-cargo-c src:rust-cargo-outdated > src:rust-debcargo src:rust-git-absorb Bug #1021213 [librust-libgit2-sys-dev] librust-libgit2-sys-dev: Depends: libgit2-dev (< 1.4~~) but 1.5.0+ds-6 is to be installed Added indication that 1021213 affects src:rust-bat, src:rust-cargo-c, src:rust-cargo-outdated, src:rust-debcargo, and src:rust-git-absorb > close -1 0.13.2-1 Bug #1021213 [librust-libgit2-sys-dev] librust-libgit2-sys-dev: Depends: libgit2-dev (< 1.4~~) but 1.5.0+ds-6 is to be installed Marked as fixed in versions rust-libgit2-sys/0.13.2-1. Bug #1021213 [librust-libgit2-sys-dev] librust-libgit2-sys-dev: Depends: libgit2-dev (< 1.4~~) but 1.5.0+ds-6 is to be installed Marked Bug as done -- 1021213: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021213 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1021213: librust-libgit2-sys-dev: Depends: libgit2-dev (< 1.4~~) but 1.5.0+ds-6 is to be installed
Package: librust-libgit2-sys-dev Version: 0.12.24-5 Severity: serious Tags: ftbfs Control: affects -1 src:rust-bat src:rust-cargo-c src:rust-cargo-outdated src:rust-debcargo src:rust-git-absorb Control: close -1 0.13.2-1 The following packages have unmet dependencies: librust-libgit2-sys-dev : Depends: libgit2-dev (< 1.4~~) but 1.5.0+ds-6 is to be installed
Bug#1012587: marked as done (/usr/share/doc/yubikey-manager empty)
Your message dated Mon, 03 Oct 2022 21:12:06 + with message-id and subject line Bug#1012587: fixed in yubikey-manager 4.0.9-1 has caused the Debian Bug report #1012587, regarding /usr/share/doc/yubikey-manager empty to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1012587: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012587 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: yubikey-manager Version: 4.0.7-1 Severity: serious Justification: Policy 2.3, Policy 4.4 /usr/share/doc/yubikey-manager is completly empty. Thus, the required copyright and changelog files are missing. [3/5072]mh@drop:~ $ dpkg --list yubikey-manager | cat Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ NameVersion Architecture Description +++-===---== ii yubikey-manager 4.0.7-1 all Python library and command line tool for configuring a YubiKey [4/5073]mh@drop:~ $ dpkg --listfiles yubikey-manager | cat /. /usr /usr/bin /usr/bin/ykman /usr/lib /usr/lib/python3 /usr/lib/python3/dist-packages /usr/lib/python3/dist-packages/ykman /usr/lib/python3/dist-packages/ykman/cli /usr/lib/python3/dist-packages/ykman/cli/__init__.py /usr/lib/python3/dist-packages/ykman/cli/__main__.py /usr/lib/python3/dist-packages/ykman/cli/aliases.py /usr/lib/python3/dist-packages/ykman/cli/apdu.py /usr/lib/python3/dist-packages/ykman/cli/config.py /usr/lib/python3/dist-packages/ykman/cli/fido.py /usr/lib/python3/dist-packages/ykman/cli/info.py /usr/lib/python3/dist-packages/ykman/cli/oath.py /usr/lib/python3/dist-packages/ykman/cli/openpgp.py /usr/lib/python3/dist-packages/ykman/cli/otp.py /usr/lib/python3/dist-packages/ykman/cli/piv.py /usr/lib/python3/dist-packages/ykman/cli/util.py /usr/share /usr/share/doc /usr/share/man /usr/share/man/man1 /usr/share/man/man1/ykman.1.gz /usr/share/doc/yubikey-manager [5/5074]mh@drop:~ $ ls -al /usr/share/doc/yubikey-manager total 0 drwxr-xr-x 1 root root0 Nov 1 2020 ./ drwxr-xr-x 1 root root 100K Jun 8 17:09 ../ [6/5075]mh@drop:~ $ Greetings Marc -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.18.2-zgws1 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE=en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages yubikey-manager depends on: ii pcscd 1.9.7-1 ii python3 3.10.4-1+b1 ii python3-click 8.0.3-1 ii python3-cryptography 3.4.8-2 ii python3-fido2 0.9.1-1 ii python3-ykman 4.0.7-1 Versions of packages yubikey-manager recommends: ii libyubikey-udev 1.20.0-3 yubikey-manager suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: yubikey-manager Source-Version: 4.0.9-1 Done: Florian Schlichting We believe that the bug you reported is fixed in the latest version of yubikey-manager, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1012...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Florian Schlichting (supplier of updated yubikey-manager package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 03 Oct 2022 22:22:24 +0200 Source: yubikey-manager Architecture: source Version: 4.0.9-1 Distribution: unstable Urgency: medium Maintainer: Debian Authentication Maintainers Changed-By: Florian Schlichting Closes: 1012587 Changes: yubikey-manager (4.0.9-1) unstable; urgency=medium . * Team upload . * New upstream version 4.0.9 * Update maximum supported version of python3-cryptography and python3-fido2, require at least python3-click 7.0 * Re-do the dir_to_symlink transition, to also catch systems closely following unstable (closes: #1012587) * Dr
Bug#1021032: marked as done (vlc: playing videos results in a black screen)
Your message dated Mon, 03 Oct 2022 21:11:54 + with message-id and subject line Bug#1021032: fixed in vlc 3.0.17.4-5 has caused the Debian Bug report #1021032, regarding vlc: playing videos results in a black screen to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1021032: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021032 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: vlc Version: 3.0.17.4-4+b2 Severity: important X-Debbugs-Cc: arraybo...@gmail.com Dear Maintainer, When attempting to play back MP4 videos using VLC, only a black screen is displayed, sometimes with the VLC logo still slightly visible in the background. This problem appears to have been caused by the introduction of ffmpeg5 into Debian. Steps to reproduce: 1. Download a .mp4 video. Any video should work, I personally use drone footage from Pexels. 2. Open the video using VLC. Using Media -> Open File... from within the GUI works, as well as using the command line (vlc ./video.mp4). Expected result: The video should play back properly, allowing audio to be heard and video to be seen. Actual result: The screen remains black (or, if you open the video from the command line, the VLC logo can be seen dimly in the area where the video should be). The playback slider moves normally, as if the video was playing back properly. Additional notes: This bug was first discovered in Ubuntu 22.10 Kinetic Kudu, however it is also easily reproducible using Debian Sid. The bug exists both on physical and virtual hardware on Ubuntu, and I have been able to replicate it in a virtual machine on Debian. -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.19.0-2-amd64 (SMP w/4 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) LSM: AppArmor: enabled Versions of packages vlc depends on: ii vlc-bin 3.0.17.4-4+b2 ii vlc-plugin-base 3.0.17.4-4+b2 ii vlc-plugin-qt3.0.17.4-4+b2 ii vlc-plugin-video-output 3.0.17.4-4+b2 Versions of packages vlc recommends: ii vlc-l10n 3.0.17.4-4 ii vlc-plugin-access-extra3.0.17.4-4+b2 ii vlc-plugin-notify 3.0.17.4-4+b2 ii vlc-plugin-samba 3.0.17.4-4+b2 ii vlc-plugin-skins2 3.0.17.4-4+b2 ii vlc-plugin-video-splitter 3.0.17.4-4+b2 ii vlc-plugin-visualization 3.0.17.4-4+b2 Versions of packages vlc suggests: pn vlc-plugin-fluidsynth pn vlc-plugin-jack pn vlc-plugin-pipewire pn vlc-plugin-svg Versions of packages libvlc-bin depends on: ii libc62.35-1 ii libvlc5 3.0.17.4-4+b2 Versions of packages libvlc5 depends on: ii libc62.35-1 ii libvlccore9 3.0.17.4-4+b2 Versions of packages libvlc5 recommends: ii libvlc-bin 3.0.17.4-4+b2 Versions of packages vlc-bin depends on: ii libc6 2.35-1 ii libvlc-bin 3.0.17.4-4+b2 ii libvlc5 3.0.17.4-4+b2 Versions of packages vlc-plugin-access-extra depends on: ii libc62.35-1 ii libsrt1.5-gnutls 1.5.1-1 ii libvlccore9 [vlc-plugin-abi-3-0-0f] 3.0.17.4-4+b2 ii libvncclient10.9.13+dfsg-4 ii libxcb-composite01.15-1 ii libxcb-shm0 1.15-1 ii libxcb1 1.15-1 Versions of packages vlc-plugin-base depends on: ii liba52-0.7.4 0.7.4-20 ii libarchive13 3.6.0-1 ii libaribb24-0 1.0.3-2 ii libasound2 1.2.7.2-1 ii libass9 1:0.16.0-1 ii libavahi-client3 0.8-6 ii libavahi-common3 0.8-6 ii libavc1394-0 0.5.4-5 ii libavcodec59 7:5.1.1-2+b1 ii libavformat597:5.1.1-2+b1 ii libavutil57 7:5.1.1-2+b1 ii libbluray2 1:1.3.3-1 ii libc62.35-1 ii libcairo21.16.0-6 ii libcddb2 1.3.2-7 ii libchromaprint1 1.5.1-2+b1 ii libdav1d61.0.0-2 ii libdbus-1-3 1.14.2-1 ii libdc1394-25 2.2.6-4 ii libdca0 0.0.7-2 ii libdvbpsi10
Bug#1017391: marked as done (kpmcore: FTBFS on armel)
Your message dated Tue, 4 Oct 2022 00:30:49 +0300 with message-id and subject line Fixed in 22.08.1-2 has caused the Debian Bug report #1017391, regarding kpmcore: FTBFS on armel to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1017391: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017391 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: kpmcore Version: 22.04.3-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) https://buildd.debian.org/status/fetch.php?pkg=kpmcore&arch=armel&ver=22.04.3-1&stamp=1660159654&raw=0 dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libkpmcore12/DEBIAN/symbols doesn't match completely debian/libkpmcore12.symbols --- debian/libkpmcore12.symbols (libkpmcore12_22.04.3-1_armel) +++ dpkg-gensymbolsZIKJOW 2022-08-10 19:27:21.143130917 + @@ -1391,9 +1391,14 @@ _ZTIN2FS8reiserfsE@Base 22.04.3 _ZTIN2FS9bitlockerE@Base 22.04.3 _ZTIN2FS9linuxswapE@Base 22.04.3 - _ZTISt11_Mutex_baseILN9__gnu_cxx12_Lock_policyE2EE@Base 22.04.3 - _ZTISt16_Sp_counted_baseILN9__gnu_cxx12_Lock_policyE2EE@Base 22.04.3 - _ZTISt23_Sp_counted_ptr_inplaceI11SmartStatusSaIvELN9__gnu_cxx12_Lock_policyE2EE@Base 22.04.3 + _ZTIN9__gnu_cxx7__mutexE@Base 22.04.3-1 + _ZTISt11_Mutex_baseILN9__gnu_cxx12_Lock_policyE1EE@Base 22.04.3-1 +#MISSING: 22.04.3-1# _ZTISt11_Mutex_baseILN9__gnu_cxx12_Lock_policyE2EE@Base 22.04.3 + _ZTISt16_Sp_counted_baseILN9__gnu_cxx12_Lock_policyE1EE@Base 22.04.3-1 +#MISSING: 22.04.3-1# _ZTISt16_Sp_counted_baseILN9__gnu_cxx12_Lock_policyE2EE@Base 22.04.3 + _ZTISt19_Sp_make_shared_tag@Base 22.04.3-1 + _ZTISt23_Sp_counted_ptr_inplaceI11SmartStatusSaIvELN9__gnu_cxx12_Lock_policyE1EE@Base 22.04.3-1 +#MISSING: 22.04.3-1# _ZTISt23_Sp_counted_ptr_inplaceI11SmartStatusSaIvELN9__gnu_cxx12_Lock_policyE2EE@Base 22.04.3 _ZTS10DiskDevice@Base 22.04.3 _ZTS10FileSystem@Base 22.04.3 _ZTS10PartWidget@Base 22.04.3 @@ -1464,10 +1469,14 @@ _ZTSN2FS8reiserfsE@Base 22.04.3 _ZTSN2FS9bitlockerE@Base 22.04.3 _ZTSN2FS9linuxswapE@Base 22.04.3 - _ZTSSt11_Mutex_baseILN9__gnu_cxx12_Lock_policyE2EE@Base 22.04.3 - _ZTSSt16_Sp_counted_baseILN9__gnu_cxx12_Lock_policyE2EE@Base 22.04.3 + _ZTSN9__gnu_cxx7__mutexE@Base 22.04.3-1 + _ZTSSt11_Mutex_baseILN9__gnu_cxx12_Lock_policyE1EE@Base 22.04.3-1 +#MISSING: 22.04.3-1# _ZTSSt11_Mutex_baseILN9__gnu_cxx12_Lock_policyE2EE@Base 22.04.3 + _ZTSSt16_Sp_counted_baseILN9__gnu_cxx12_Lock_policyE1EE@Base 22.04.3-1 +#MISSING: 22.04.3-1# _ZTSSt16_Sp_counted_baseILN9__gnu_cxx12_Lock_policyE2EE@Base 22.04.3 _ZTSSt19_Sp_make_shared_tag@Base 22.04.3 - _ZTSSt23_Sp_counted_ptr_inplaceI11SmartStatusSaIvELN9__gnu_cxx12_Lock_policyE2EE@Base 22.04.3 + _ZTSSt23_Sp_counted_ptr_inplaceI11SmartStatusSaIvELN9__gnu_cxx12_Lock_policyE1EE@Base 22.04.3-1 +#MISSING: 22.04.3-1# _ZTSSt23_Sp_counted_ptr_inplaceI11SmartStatusSaIvELN9__gnu_cxx12_Lock_policyE2EE@Base 22.04.3 _ZTV10DiskDevice@Base 22.04.3 _ZTV10FileSystem@Base 22.04.3 _ZTV10PartWidget@Base 22.04.3 @@ -1538,7 +1547,8 @@ _ZTVN2FS8reiserfsE@Base 22.04.3 _ZTVN2FS9bitlockerE@Base 22.04.3 _ZTVN2FS9linuxswapE@Base 22.04.3 - _ZTVSt23_Sp_counted_ptr_inplaceI11SmartStatusSaIvELN9__gnu_cxx12_Lock_policyE2EE@Base 22.04.3 + _ZTVSt23_Sp_counted_ptr_inplaceI11SmartStatusSaIvELN9__gnu_cxx12_Lock_policyE1EE@Base 22.04.3-1 +#MISSING: 22.04.3-1# _ZTVSt23_Sp_counted_ptr_inplaceI11SmartStatusSaIvELN9__gnu_cxx12_Lock_policyE2EE@Base 22.04.3 _ZZNSt19_Sp_make_shared_tag5_S_tiEvE5__tag@Base 22.04.3 _ZZZN10KAboutDataC4ERK7QStringS2_S2_S2_N13KAboutLicense10LicenseKeyES2_S2_S2_S2_Ed_NKUlvE_clEvE15qstring_literal@Base 22.04.3 _ZZZN14KPluginFactory17instantiatePluginI11CoreBackendEENS_6ResultIT_EERK15KPluginMetaDataP7QObjectRK5QListI8QVariantEENKUlvE_clEvE15qstring_literal@Base 22.04.3 dh_makeshlibs: error: failing due to earlier errors Cheers -- Sebastian Ramacher --- End Message --- --- Begin Message --- Version: 22.08.1-2 kpmcore (22.08.1-2) unstable; urgency=medium [ Aurélien COUDERC ] * Update symbols from buildd’s logs. -- Aurélien COUDERC Mon, 03 Oct 2022 22:17:49 +0200--- End Message ---
Bug#1020005: marked as done (nbdkit: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity)
Your message dated Mon, 03 Oct 2022 23:05:11 + with message-id and subject line Bug#1020005: fixed in nbdkit 1.32.2-3 has caused the Debian Bug report #1020005, regarding nbdkit: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1020005: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020005 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: nbdkit Version: 1.32.2-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220917 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > rm -f test-old-plugins-x86_64-Linux-v1.12.8.sh > test-old-plugins-x86_64-Linux-v1.12.8.sh-t > f=`echo "test-old-plugins-x86_64-Linux-v1.12.8.sh" | /bin/sed > 's/test-old-plugins-\(.*\).sh/\1/'`; \ > echo 'script=test-old-plugins-x86_64-Linux-v1.12.8.sh exec > $srcdir/test-old-plugins.sh' "$f" > test-old-plugins-x86_64-Linux-v1.12.8.sh-t > chmod 0755 test-old-plugins-x86_64-Linux-v1.12.8.sh-t > mv test-old-plugins-x86_64-Linux-v1.12.8.sh-t > test-old-plugins-x86_64-Linux-v1.12.8.sh > PASS: test-old-plugins-x86_64-Linux-v1.12.8.sh > rm -f test-old-plugins-x86_64-Linux-v1.18.2.sh > test-old-plugins-x86_64-Linux-v1.18.2.sh-t > f=`echo "test-old-plugins-x86_64-Linux-v1.18.2.sh" | /bin/sed > 's/test-old-plugins-\(.*\).sh/\1/'`; \ > echo 'script=test-old-plugins-x86_64-Linux-v1.18.2.sh exec > $srcdir/test-old-plugins.sh' "$f" > test-old-plugins-x86_64-Linux-v1.18.2.sh-t > chmod 0755 test-old-plugins-x86_64-Linux-v1.18.2.sh-t > mv test-old-plugins-x86_64-Linux-v1.18.2.sh-t > test-old-plugins-x86_64-Linux-v1.18.2.sh > PASS: test-old-plugins-x86_64-Linux-v1.18.2.sh > PASS: test-connect > PASS: test-newstyle > PASS: test-oldstyle > E: Build killed with signal TERM after 150 minutes of inactivity The full build log is available from: http://qa-logs.debian.net/2022/09/17/nbdkit_1.32.2-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220917;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220917&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: nbdkit Source-Version: 1.32.2-3 Done: Hilko Bengen We believe that the bug you reported is fixed in the latest version of nbdkit, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1020...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Hilko Bengen (supplier of updated nbdkit package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 03 Oct 2022 23:08:08 +0200 Source: nbdkit Architecture: source Version: 1.32.2-3 Distribution: unstable Urgency: medium Maintainer: Hilko Bengen Changed-By: Hilko Bengen Closes: 1020005 Changes: nbdkit (1.32.2-3) unstable; urgency=medium . * Add workaround for curl-based tests (Closes: #1020005) Checksums-Sha1: 0d39e98b5e639490006bdf565fff8ad8cf108fee 3222 nbdkit_1.32.2-3.dsc 908b88552120587bd6f374f56bd586e3eba4040a 11604 nbdkit_1.32.2-3.debian.tar.xz 70ad7d61701eeefc1ea1b34235322b659c6ae493 16561 nbdkit_1.32.2-3_source.buildinfo Checksums-Sha256: f9f886cfe144c84e64a5eee66a05d2107252a7d558ad4d2d9b0ac5e818373928 3222 nbdkit_1.32.2-3.dsc e84060f0e5388ca597f9107ae85be6210c16239424cd325e453d6a9ff75b0566 11604 nbdkit_1.32.2-3.debian.tar.xz 4614749aa768b591d2c4273532c6f1fd41fc4e721609a78f3b5486909954bbe1 16561 nbdkit_1.32.2-3_source.buildinfo Files:
Bug#1021219: lomiri-indicator-network: Depends: indicator-common but it is not installable
Package: lomiri-indicator-network Version: 1.0.0~git20220718.2ca3619-3 Severity: serious The following packages have unmet dependencies: lomiri-indicator-network : Depends: indicator-common but it is not installable
Bug#1020885: marked as done (libshumate-1.0-1: move pkg-config file to the -dev package)
Your message dated Mon, 03 Oct 2022 23:19:33 + with message-id and subject line Bug#1020885: fixed in libshumate 1.0.1-2 has caused the Debian Bug report #1020885, regarding libshumate-1.0-1: move pkg-config file to the -dev package to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1020885: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020885 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libshumate-1.0-1 Version: 1.0.1-1 Control: found -1 1.0.0~alpha.1-1 Severity: serious File: /usr/lib/x86_64-linux-gnu/pkgconfig/shumate-1.0.pc User: debian...@lists.debian.org Usertags: adequate missing-pkgconfig-dependency The shumate-1.0.pc file should be moved from the libshumate-1.0-1 package to the libshumate-dev package, since the shumate-1.0.pc is only used at compile time. This issue has been present since version 1.0.0~alpha.1-1 according to the binary packages available on the snapshot.debian.org service. from the release team advised me on #debian-gnome that this issue represents a serious issue, hence the severity above. This issue was detected by adequate, hence the usertags above. -- System Information: Debian Release: bookworm/sid APT prefers testing-debug APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental') merged-usr: no Architecture: amd64 (x86_64) Kernel: Linux 5.19.0-2-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8), LANGUAGE=en_AU:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libshumate-1.0-1 depends on: ii libc62.34-8 ii libcairo21.16.0-6 ii libgdk-pixbuf-2.0-0 2.42.9+dfsg-1 ii libglib2.0-0 2.74.0-1 ii libgraphene-1.0-01.10.8-1 ii libgtk-4-1 4.8.1+ds-1 ii libshumate-common1.0.1-1 ii libsoup-3.0-03.2.0-1 ii libsqlite3-0 3.39.3-1 libshumate-1.0-1 recommends no packages. libshumate-1.0-1 suggests no packages. -- no debconf information -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part --- End Message --- --- Begin Message --- Source: libshumate Source-Version: 1.0.1-2 Done: Matthias Geiger We believe that the bug you reported is fixed in the latest version of libshumate, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1020...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Geiger (supplier of updated libshumate package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 03 Oct 2022 14:34:45 -0700 Source: libshumate Built-For-Profiles: noudeb Architecture: source Version: 1.0.1-2 Distribution: unstable Urgency: medium Maintainer: Debian GNOME Maintainers Changed-By: Matthias Geiger Closes: 1020885 Changes: libshumate (1.0.1-2) unstable; urgency=medium . * Move shumate-1.0.pc to -dev package (Closes: #1020885) Checksums-Sha1: 56b427c502e751617c22e463e3ad373fb413f91a 2486 libshumate_1.0.1-2.dsc ec8879937b4a2a434b727dc213411798b97ee197 5960 libshumate_1.0.1-2.debian.tar.xz 3d4f468771fffb73d93c8a3c1b5eba05952c09bc 18419 libshumate_1.0.1-2_source.buildinfo Checksums-Sha256: 901f59b9abe9621e4e709479832bd91dc5938ac7ba22b012da8090134642516f 2486 libshumate_1.0.1-2.dsc 10fcac30d914dc004018ef182b2b7b42cb69cee00448d8281aa46ec62e482fd4 5960 libshumate_1.0.1-2.debian.tar.xz 39f53dad58f9d2e0ada02b76f16dfe2af123e1df8d975e9920c3f27275e9c38e 18419 libshumate_1.0.1-2_source.buildinfo Files: 4793c12a3eb9e205c0151387ead2ca04 2486 libs optional libshumate_1.0.1-2.dsc 66ea2195f32c0cb090fec6f1d6740fca 5960 libs optional libshumate_1.0.1-2.debian.tar.xz 784870a72168ab9b69cb8d3811e4b6c4 18419 libs optional libshumate_1.0.1-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAmM7aLIACgkQ5mx3Wuv+ bH2IVA/+Lrrnusm/ZmjQQXGTnmCG3+gd2y2+hx
Processed: Bug#1021219 marked as pending in lomiri-indicator-network
Processing control commands: > tag -1 pending Bug #1021219 [lomiri-indicator-network] lomiri-indicator-network: Depends: indicator-common but it is not installable Added tag(s) pending. -- 1021219: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021219 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1021219: marked as pending in lomiri-indicator-network
Control: tag -1 pending Hello, Bug #1021219 in lomiri-indicator-network reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/ubports-team/lomiri-indicator-network/-/commit/a688c9bc1718ff4c7ef853b491de0a0bf2614eab debian/control: Switch from obsolete indicator-common to ayatana-indicator-common. (Closes: #1021219). (this message was generated automatically) -- Greetings https://bugs.debian.org/1021219
Bug#1021219: marked as done (lomiri-indicator-network: Depends: indicator-common but it is not installable)
Your message dated Mon, 03 Oct 2022 23:36:29 + with message-id and subject line Bug#1021219: fixed in lomiri-indicator-network 1.0.0~git20220718.2ca3619-4 has caused the Debian Bug report #1021219, regarding lomiri-indicator-network: Depends: indicator-common but it is not installable to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1021219: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021219 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: lomiri-indicator-network Version: 1.0.0~git20220718.2ca3619-3 Severity: serious The following packages have unmet dependencies: lomiri-indicator-network : Depends: indicator-common but it is not installable --- End Message --- --- Begin Message --- Source: lomiri-indicator-network Source-Version: 1.0.0~git20220718.2ca3619-4 Done: Mike Gabriel We believe that the bug you reported is fixed in the latest version of lomiri-indicator-network, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1021...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mike Gabriel (supplier of updated lomiri-indicator-network package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 04 Oct 2022 01:23:57 +0200 Source: lomiri-indicator-network Architecture: source Version: 1.0.0~git20220718.2ca3619-4 Distribution: unstable Urgency: medium Maintainer: Debian UBports Team Changed-By: Mike Gabriel Closes: 1021219 Changes: lomiri-indicator-network (1.0.0~git20220718.2ca3619-4) unstable; urgency=medium . * debian/control: + In Depends:, switch from obsolete indicator-common to ayatana-indicator- common. (Closes: #1021219). Checksums-Sha1: 83f71308deb1b2cec693aaca14d9a4b5cf982879 3213 lomiri-indicator-network_1.0.0~git20220718.2ca3619-4.dsc d95634167b7b45dc41f13cff954713cc6c540e5e 22164 lomiri-indicator-network_1.0.0~git20220718.2ca3619-4.debian.tar.xz 456eb9d5eda6c57a8b160bb419761e95e0316f9e 16400 lomiri-indicator-network_1.0.0~git20220718.2ca3619-4_source.buildinfo Checksums-Sha256: 1ed62e84fd9f73152655de86b3b8b2d5852d862b322bf2d364a06f2919feb9fb 3213 lomiri-indicator-network_1.0.0~git20220718.2ca3619-4.dsc 0d50a4898725c6fcdf35ef90335ce7ff70fc71a87c52fe8784f1407a9a52a688 22164 lomiri-indicator-network_1.0.0~git20220718.2ca3619-4.debian.tar.xz 73ddd30fcac3465d267b97237a4b392735afa6bb407bce91f48828986d973767 16400 lomiri-indicator-network_1.0.0~git20220718.2ca3619-4_source.buildinfo Files: b65073039fc4bf086eb303784089bdf9 3213 misc optional lomiri-indicator-network_1.0.0~git20220718.2ca3619-4.dsc d8a66902ab623643d483621a174cb113 22164 misc optional lomiri-indicator-network_1.0.0~git20220718.2ca3619-4.debian.tar.xz a1559b7328897425f86c3d4cfb2fca5f 16400 misc optional lomiri-indicator-network_1.0.0~git20220718.2ca3619-4_source.buildinfo -BEGIN PGP SIGNATURE- iQJJBAEBCAAzFiEEm/uu6GwKpf+/IgeCmvRrMCV3GzEFAmM7byMVHHN1bndlYXZl ckBkZWJpYW4ub3JnAAoJEJr0azAldxsx8Q0P/AxeMFKBlpa72PB3Fdo+svOA9wbz gA1uAIx6UvpzcCf/GFVOd65JcIk3gilnYBsZM3vNXo4fp6fuFFYuUPz9u8n+Wgfs gLh+vxZeeMQaynVHEY2hfmkFsGsuMe/hYhUDQ4QDzEc7dU6z3xoho9F26WnhSGkz QkufVJE+Y94rhYTLjoaQUmB66KCWZXIYogMkeX6eQdNo0kNKR+5MZaEKAPTOiAca yffhkzfJkh/U76D4OptvlhyR1lJztJYPwug6ht9sSF4eskAbH9PXVBdzWRbzs0MA EhNF/ZlUMgXck3/iQDmS/xWRVbFN2dr0BJ0SraopcSMBqmjTSdXzMTx1XeVU0Kbt +lwPiGulbFRxQGo1kROQ7NTyJp7uRxvu3qYUkRDifQLA8IEWzqorT6/3FMJ598PY LmRXaqDrBZ0e9gS5Gv+/5YgyyyoJ/j2xkA8yyumU46fO+k9wCBHJx9GN98qLC3Zk l1bE0nHM/q1fGUxMnH1ihv/CXChD4aVzieaNzT+E/OGCX+T2gKv9xcRBXXSygE9n dk17+9z8JWNA/7eYvvjTEqbv9HDDSNyxX0PA8Sj93P9vR9ZHd1U5YhEcYjT2Hx0n 3Zi+/boiiONtRavG0quc1u624Syimzed8noU5MF2JbBQZCsw6BFle+GSQXmPfQRC 4tMPOUni6NWf6xOs =9yd9 -END PGP SIGNATURE End Message ---
Bug#1020714: marked as done (cryptsetup: cryptroot-* autopkgtests fall-back to shell and hang on errors)
Your message dated Tue, 04 Oct 2022 01:18:58 + with message-id and subject line Bug#1020714: fixed in cryptsetup 2:2.5.0-4 has caused the Debian Bug report #1020714, regarding cryptsetup: cryptroot-* autopkgtests fall-back to shell and hang on errors to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1020714: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020714 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cryptsetup Version: 2:2.5.0-2 Severity: serious Dear maintainer, I was starting at some 14 hour failures in testing [1] due to merged-/usr, which apparently you already fixed in unstable. However, the reason for that long run was not the failure itself, but the fact that your tests drop to shell on error and apparently waits for user input. One failure with 2:2.5.0-3 in unstable has the same problem. This is pretty bad for our infrastructure as normally your test is much faster and it shouldn't wait for the time out. Can you please fix that? Paul [1] https://ci.debian.net/packages/c/cryptsetup/testing/amd64/ https://ci.debian.net/data/autopkgtest/unstable/amd64/c/cryptsetup/26349209/log.gz The partition table has been altered. Calling ioctl() to re-read partition table. [1.904096] vda: vda1 vda2 vda3 vda4 vda5 Syncing disks. + echo -n topsec[1.908756] vda: vda1 vda2 vda3 vda4 vda5 ret + cryptsetup luksFormat --batch-mode --key-file=/rootfs.key --type=luks2 --pbkdf=argon2id --pbkdf-force-iterations=4 --pbkdf-memory=32 -- /dev/vda5 Device /dev/vda5 does not exist or access denied. + echo ALERT! Couldn't setup system, dropping to a shell. ALERT! Couldn't setup system, dropping to a shell. + sh -i # autopkgtest [19:14:06]: ERROR: timed out on command "su -s /bin/bash root -c set -e; export USER=`id -nu`; . /etc/profile >/dev/null 2>&1 || true; . ~/.profile >/dev/null 2>&1 || true; buildtree="/tmp/autopkgtest-lxc.6pwp9hgu/downtmp/build.q7w/src"; mkdir -p -m 1777 -- "/tmp/autopkgtest-lxc.6pwp9hgu/downtmp/cryptroot-sysvinit-artifacts"; export AUTOPKGTEST_ARTIFACTS="/tmp/autopkgtest-lxc.6pwp9hgu/downtmp/cryptroot-sysvinit-artifacts"; export ADT_ARTIFACTS="$AUTOPKGTEST_ARTIFACTS"; mkdir -p -m 755 "/tmp/autopkgtest-lxc.6pwp9hgu/downtmp/autopkgtest_tmp"; export AUTOPKGTEST_TMP="/tmp/autopkgtest-lxc.6pwp9hgu/downtmp/autopkgtest_tmp"; export ADTTMP="$AUTOPKGTEST_TMP"; export DEBIAN_FRONTEND=noninteractive; export LANG=C.UTF-8; export DEB_BUILD_OPTIONS=parallel=64; unset LANGUAGE LC_CTYPE LC_NUMERIC LC_TIME LC_COLLATE LC_MONETARY LC_MESSAGES LC_PAPER LC_NAME LC_ADDRESS LC_TELEPHONE LC_MEASUREMENT LC_IDENTIFICATION LC_ALL;rm -f /tmp/autopkgtest_script_pid; set -C; echo $$ > /tmp/autopkgtest_script_pid; set +C; trap "rm -f /tmp/autopkgtest_script_pid" EXIT INT QUIT PIPE; cd "$buildtree"; export AUTOPKGTEST_NORMAL_USER=debci; export ADT_NORMAL_USER=debci; chmod +x /tmp/autopkgtest-lxc.6pwp9hgu/downtmp/build.q7w/src/debian/tests/cryptroot-sysvinit; touch /tmp/autopkgtest-lxc.6pwp9hgu/downtmp/cryptroot-sysvinit-stdout /tmp/autopkgtest-lxc.6pwp9hgu/downtmp/cryptroot-sysvinit-stderr; /tmp/autopkgtest-lxc.6pwp9hgu/downtmp/build.q7w/src/debian/tests/cryptroot-sysvinit 2> >(tee -a /tmp/autopkgtest-lxc.6pwp9hgu/downtmp/cryptroot-sysvinit-stderr >&2) > >(tee -a /tmp/autopkgtest-lxc.6pwp9hgu/downtmp/cryptroot-sysvinit-stdout);" (kind: test) --- End Message --- --- Begin Message --- Source: cryptsetup Source-Version: 2:2.5.0-4 Done: Guilhem Moulin We believe that the bug you reported is fixed in the latest version of cryptsetup, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1020...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Guilhem Moulin (supplier of updated cryptsetup package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 04 Oct 2022 01:14:30 +0200 Source: cryptsetup Architecture: source Version: 2:2.5.0-4 Distribution: unstable Urgency: medium Maintainer: Debian Cryptsetup Team Changed-By: Guilhem Moulin Closes: 1020553 1020714 Changes: cryptsetup (2:2.5.0-4) unstable; urgency=medium . * suspend.conf: Improve description and typofix.
Bug#1021232: librust-gdk4-sys-dev: uninstallable
Package: librust-gdk4-sys-dev Version: 0.3.1-1+b1 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Package is uninstallable: depends on missing librust-system-deps-3+default-dev -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmM7uZYACgkQLHwxRsGg ASHRVxAAk2wc9cdkLsLW7nXvVRkEh/IwV3OTCZik6sk2vg7Es/Q1VHVm2m3JHwAq II7jaGDDHy39HaTjyWoLW7oc0mElXkWdWR3hY2jcjEDwXaIBM68VO17ufDD4D7UH U+6jDeeJbnY2qqX1n/7Ok24WwBhrP6dAtJKDISlwShd4NPwKAkwINjcciJ5tAYx9 FUmg3cQyduCVrm8A6mgcWrqFev5R2pac0EH7A8QNCJRrRAqy//JD21bGIIZJe6wn M2C06BQULco87xM1JE4NNV/wbKEHNTE379cNEbtovxq72ggghcfAz9PWIByowbT9 u1LrowwVX6KHbzfQMHdP2zBq/V5wLd48d45OIiJ3wnmhbqAhxNNu2Ubhq53DZWhT vVbxSegxhOxttMRt+U3xpz7zVSsa0VnRW4EI1X7lylrJMb2hygmJfEGYR3aCBK8u W2E5r4BRUmUDjb6gMGlU+AeIRCJZtVSvJoA3tRLFdiEWwwif4wfVWbvsPtKOvpKr xcjWE9p3i7RM8pdrXylHo0UyYl6MFk86pRj7HNYSEwKWEb5w4wKMKo07HdVSEGg6 UOdKxA8Hi707JpngN/CBtBFkTd15/9E6fJ4hSIhaRzsjnfn8ReNQ1yY24u0TxywY dMXzWnTypaGlFiK1gfpzKhdVGM76SMKub067RgH/pGChveOGRlw= =MRFc -END PGP SIGNATURE-
Bug#1021233: librust-gsk4-sys-dev: uninstallable
Package: librust-gsk4-sys-dev Version: 0.3.1-1+b1 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Package is uninstallable: depends on missing librust-system-deps-3+default-dev -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmM7ueEACgkQLHwxRsGg ASEy5A//WegyNEHMRDKgii15c0JiYqk0uC59SB/FRITDzweTaCLy0wc9ZrE5bfIg NiE5lWIWvZngBqAl45Cw5Mm3C3Y4ni2IrpA+Kh/Oiav5pY0eQBEbSfqC40xVyFXY LYbyVg4sR9Qq+IAX/S0ab5sPmCBjxu/BmqyY6Yq87nDpOInm7ap7oKX7EPf84DxM jgJUV/dRqAScJRLH3OPm9UvQ9ApUUDz5sAE6LPwigSkbtcMswOUwND/Ebr6Ym6/W 8JkrXSHIQC1yASzs98w0QPXO5ixgO+HHW/oyd/Pjhyg2b702YkTsqEngCbF0kk6F /lcyrT/T0hpfJvrxaR7f0js6T3D89WFL5FIw3+K7YzRwM/o6sLgsVsoRZJtne0cS CNMZOXWEO8+BhRFgL0nAij2kSCAnsyPwWRFiDYUoxl7cTYfwkj8Eq22PyVxa+RMX HDHEaI6c0w11xMay1dgCUVBRE2ywtNRkOnUh7sCZ3O4vNvdQ6fRXi7uSmMnR26dD c80weUu1cPnh5fid7w9SCfQbcBGjaRsqqPv8QuLkMNfH2uyEY8zrjD2qIrh3akIN GzwLGUz6qziTi5i1xjgqMcf47kZ7Hk0B+QsNZ7/wnVMj5/lDh90LWQqezKqEj/XM w5zkY+PlhhUXsxbFSIFJukbiKsjkg++G9TYKCw+tSoMoRUFdORw= =zaIf -END PGP SIGNATURE-
Bug#1021234: librust-gtk4-sys-dev: uninstallable
Package: librust-gtk4-sys-dev Version: 0.3.1-1+b1 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Package is uninstallable: depends on missing librust-system-deps-3+default-dev -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmM7uiYACgkQLHwxRsGg ASE+Mg//WX8RPN+9bsfRs7rlx2UOXZxkXiNoL3lkLPaKMnnTyY0c7MK98MUOBiDp yjRkrhDtShvUogKJ9mxfAgqD4WYhjXha9Duej322mGvB+QEEaMXnLyhRDJ8Tv5M+ QNeBbyAPHQKrPXwSXDpf3ytpmzJxVGh5zRhbKZLwXxnnIr4Fb+rsfhEhPaDeybjz RVLRW8+BBjRtzObMknx+RIw+iI2EtTu4uflEKqfGqALIYiedT9BYULoIYUMr2np0 +0qcRAB8FXHo0QfXb9+oFbsRN0J95JVzjHmXlOz0TKr6Kigd7rjY2MLa8QGtbmNf /MudsFAJNQB3jC/zQnFegAPmDrADgX+bfHIktxNclqRxcco7LUCF4AOXlvFKgXvm QJ+Imx0nVLglKsJdgvTLAwFwYHorKqgtgaejrZ5u/MjIdoI0MD2eIYpHBZMibO3p 61jSF3RXoOVKlbwpv1NzFQIe1xQG+7Sam9e0jjBwFjP2kRwbAuFkRhZdFJK2+wRd kH9EwfzT4zug21rWiPNSUrUJhs/molpzzBH2wPZ+WTi8DNdF1sCReaA4I0rPio5X hZl2L1aIffSnqPDXJNf8wEqI6W+WO0S9PEP/o+ehdptDol+RhG/iHdB/DZBs4PEL S014jOOKd29m0w5nlZwGB1kjn4tpaIrDR2/pA52U2CYLRMRZAFI= =q2vb -END PGP SIGNATURE-
Bug#1019855: marked as done (Fwd: libc6: immediately crashes with SIGILL on 4th gen Intel Core CPUs (seems related to AVX2 instructions), bricking the whole system)
Your message dated Tue, 04 Oct 2022 05:20:22 + with message-id and subject line Bug#1019855: fixed in glibc 2.35-2 has caused the Debian Bug report #1019855, regarding Fwd: libc6: immediately crashes with SIGILL on 4th gen Intel Core CPUs (seems related to AVX2 instructions), bricking the whole system to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1019855: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019855 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libc6 Version: 2.31-13+deb11u4 Severity: critical Dear Maintainer, After an upgrade to version +deb11u4 on my system running Haswell (4th gen Intel Core) CPU, most of the programs including bash or dpkg are immediately crashing with SIGILL. The problem seems to be caused/ related to AVX2 and changes made to some functions utilizing this instruction set. I don't know much about Debian bug reporting, so forgive me any mistakes I've made. The issue is on both host, LXC and Docker. I have described more on this link: https://github.com/debuerreotype/docker-debian-artifacts/issues/175 where I also linked my coredump from example program and described stuff more thoroughly. Coredump link directly just in case: https://github.com/debuerreotype/docker-debian-artifacts/files/9569748/core.bash.10.2663c40e671041e6b40c882a70b83c3f.1480736.166318582400.zip Also log lines from kernel: kernel: [834669.721253] traps: dpkg[1455373] trap invalid opcode ip:7fa39701951d sp:7ffc4ad26e58 error:0 in libc-2.31.so[7fa396edd000+15a000] kernel: [834669.732958] traps: dpkg[1455374] trap invalid opcode ip:7f529ca9551d sp:7fffb6f0a238 error:0 in libc-2.31.so[7f529c959000+15a000] kernel: [834669.840128] traps: dpkg[1455375] trap invalid opcode ip:7f1874cc951d sp:7fffc2c2f5d8 error:0 in libc-2.31.so[7f1874b8d000+15a000] kernel: [834669.907918] traps: dpkg[1455378] trap invalid opcode ip:7f3b4f8d851d sp:7fff3ec970f8 error:0 in libc-2.31.so[7f3b4f79c000+15a000] kernel: [834712.152139] traps: passwd[1455693] trap invalid opcode ip:7fefee4b52b7 sp:7cb506b8 error:0 in libc-2.31.so[7fefee37d000+15a000] Not sure what exactly might be causing the issue, but if these changes aren't pulled, potentially anyone with this or similar CPU as me will upgrade and end up with bricked system. I will proceed to try using `clearcpuid=293` kernel flag myself, but consider how many distros depend on Debian, live CDs etc, with people unable to figure out why their system became useless, unable to trace the source, and blaming it just on Linux... I'm filling this bug report from my downgraded host system to the previous libc6 version. * What led up to the situation? apt upgrade... * What exactly did you do (or not do) that was effective (or ineffective)? downgrade to +deb11u3 * What was the outcome of this action? everything works on the older version * What outcome did you expect instead? -- System Information: Debian Release: 11.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.15.39-1-pve (SMP w/4 CPU threads) 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 Versions of packages libc6 depends on: ii libcrypt1 1:4.4.18-4 ii libgcc-s1 10.2.1-6 Versions of packages libc6 recommends: ii libidn2-0 2.3.0-5 pn libnss-nis pn libnss-nisplus Versions of packages libc6 suggests: ii debconf [debconf-2.0] 1.5.77 pn glibc-doc ii libc-l10n 2.31-13+deb11u3 ii locales2.31-13+deb11u3 -- debconf information: glibc/disable-screensaver: glibc/restart-services: glibc/kernel-not-supported: glibc/kernel-too-old: libraries/restart-without-asking: false glibc/restart-failed: glibc/upgrade: true --- End Message --- --- Begin Message --- Source: glibc Source-Version: 2.35-2 Done: Aurelien Jarno We believe that the bug you reported is fixed in the latest version of glibc, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1019...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software
Processed: notfound 1020776 in 1:5.2+dfsg-11+deb11u2
Processing commands for cont...@bugs.debian.org: > notfound 1020776 1:5.2+dfsg-11+deb11u2 Bug #1020776 [qemu-system-data] qemu-system-data in bullseye-backports is too old No longer marked as found in versions qemu/1:5.2+dfsg-11+deb11u2. > thanks Stopping processing here. Please contact me if you need assistance. -- 1020776: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020776 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1021235: python-pymeasure: please switch to QtWidgets.QTreeWidgetItem
Source: python-pymeasure Version: 0.9.0-1 Severity: serious Hello, I noticed there is also a 0.10.0 version, but probably in order to fix autopkgtests/build against new python-pyqtgraph some additional patches are needed, e.g. 4d35e9eebb548453867b4c562a80eb5851918186 fcd8df95e9f1da17c87917c64f3f5abf96a9aa3d 7014231851cf731aa253c41da9e6e38abfd81ead 26f8bdbf236527bbe3c1800f37ccbe1e6be8b841 ee586f4f5ee0fba1b77d48f3052549b99f520324 Sorry for breaking your package in sid, I didn't know there was this reverse-dependency when I uploaded. G.
Processed: found 1020776 in 1:7.1+dfsg-2~bpo11+2
Processing commands for cont...@bugs.debian.org: > found 1020776 1:7.1+dfsg-2~bpo11+2 Bug #1020776 [qemu-system-data] qemu-system-data in bullseye-backports is too old There is no source info for the package 'qemu-system-data' at version '1:7.1+dfsg-2~bpo11+2' with architecture '' Unable to make a source version for version '1:7.1+dfsg-2~bpo11+2' Ignoring request to alter found versions of bug #1020776 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 1020776: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020776 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1019855: Fwd: libc6: immediately crashes with SIGILL on 4th gen Intel Core CPUs (seems related to AVX2 instructions), bricking the whole system
Hi On 2022-09-25 13:43, Aurelien Jarno wrote: > > Running a quick diff against old procinfo reveals that "flags" has the > > following new entries now: > > > > tsc_deadline_timer ssbd ibrs ibpb stibp bmi1 bmi2 md_clear flush_l1d > > > > > it looks like that the BMI2 > > > instructions support has been added in a microcode update > > > > As such it does appear that indeed this is the case. > > Thanks for the confirmation, it seems that the microcode update is also > useful for security reasons in order to mitigate the speculative > execution side channel issues (the famous spectre/meltdown). > > Neverthless the AVX2 code should not use BMI2 instructions if they are > not available. This has been fixed upstream and in the sid package. Next step is to get it fixed for stable. Regards Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net
