Bug#986709: (no subject)
FYI linked issue and summary of issue from upstream perspective: https://github.com/rsnapshot/rsnapshot/issues/279#issuecomment-860001348
Bug#986709: rsnapshot is stable, not dead
On Fri, 28 May 2021 15:39:28 -0500 Michael Lustfield wrote: > On Fri, 28 May 2021 19:56:47 +0100 > David Cantrell wrote: > > > [...] > > So what, exactly, is unmaintained about it? Looks to me like it has > > exactly the amount of maintenance that is required for mature software. > > I'm not going to strawman my justifications; it's not terribly relevant anyway. > Absolutely anyone is free to disagree with me and continue maintenance of the > package. If needed, I'll even sponsor the upload. > > https://mentors.debian.net/intro-maintainers (read 1-2, start at 3) > > Hi Michael, I don't understand this. Wouldn't it be easier if you orhpaned the package since it's already in stable? Thanks, Sam.
Processed: tagging 990072
Processing commands for cont...@bugs.debian.org: > tags 990072 + buster Bug #990072 [lxc] lxc-attach fails after debian 10.10 update Bug #990075 [lxc] lxc-attach fails after debian 10.10 update Added tag(s) buster. Added tag(s) buster. > thanks Stopping processing here. Please contact me if you need assistance. -- 990072: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990072 990075: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990075 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#914315: libwebp-dev: New versions fix disclosed heap use-after-free
Processing control commands: > severity -1 wishlist Bug #914315 [libwebp-dev] libwebp-dev: New versions fix disclosed heap use-after-free Severity set to 'wishlist' from 'grave' -- 914315: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914315 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#914315: libwebp-dev: New versions fix disclosed heap use-after-free
Control: severity -1 wishlist On 2021-03-16 09:27:12 +, Laurence Parry wrote: > Tags: fixed-upstream > > Using webp-dev on buster with test file bug.c from the second bug > mentioned above compiled with -lwebp, malloc reported: "free(): > corrupted unsorted chunks" within WebPIDelete(). > > This suggests to me that the bug may be exploitable on systems with > libwebp6 installed - of which there are far more than when this > package was introduced. > https://qa.debian.org/popcon-graph.php?packages=libwebp-dev+libwebp6+libwebpmux3+libwebpdemux2+webp&show_installed=on&want_legend=on&want_ticks=on&from_date=2016-03-01&date_fmt=%25Y-%25m&beenhere=1 > > As such, I've raised the priority. I don't know which packages use > libwebp6 in threaded mode, but a change in this may not be noted in > changelogs anyway. > > As the maintainer appears inactive, I request assistance from the > security team to address this issue. Fixes for the security issues have been uploaded. Reducing the severity of this bug back to wishlist as this is now a "please package new upstream release" bug report. Cheers > > Best regards, > -- > Laurence "GreenReaper" Parry - Inkbunny administrator > https://www.greenreaper.co.uk/ - https://inkbunny.net/ -- Sebastian Ramacher signature.asc Description: PGP signature
Processed: affects 990082
Processing commands for cont...@bugs.debian.org: > affects 990082 release.debian.org Bug #990082 [shim-signed] High chance of boot problems with buster's version of arm64 shim Added indication that 990082 affects release.debian.org > thanks Stopping processing here. Please contact me if you need assistance. -- 990082: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990082 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#990082: High chance of boot problems with buster's version of arm64 shim
Package: shim-signed Version: 1.36~1+15.4-5~deb10u1 Severity: grave Argh. In pre-release testing I found problems with shim on signed versions of shim on arm64. The shim binary crashes very early (Synchronous Exception). Because of that problem, I took the hard decision to disable Secure Boot support for arm64 in Debian Buster until a solution could be found: https://wiki.debian.org/SecureBoot#arm64_problems In testing a new build to go into Buster, I found that non-signed versions were working fine on various machines. Unfortunately, it seems that the boot issues might be affected by environment. Trying the same binary build today as part of the 10.10 point release, booting an installer image crashes repeatably in a VM. It also seems that at least one of Debian's own arm64 hosts has been similarly affected. :-( Arm64 users are **strongly** advised to be careful about upgrading to the latest Buster point release (10.10). If upgrading immediately, it is recommended to disable remove shim-signed and reinstall GRUB on those systems to ensure that they will continue to boot: # apt-get remove shim-signed # dpkg --reconfigure grub-efi-amd64 and disable Secure Boot in their system firmware if it's enabled. I'm working on a more user-friendly fix now, and I hope to push it out via the Buster security archive shortly. This will still not be *working* Secure Boot for arm64, as we're still awaiting better toolchain support to make that work. -- System Information: Debian Release: 10.9 APT prefers stable-debug APT policy: (500, 'stable-debug'), (500, 'stable'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-0.bpo.5-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_CPU_OUT_OF_SPEC Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages shim-signed depends on: ii grub-efi-amd64-bin 2.02+dfsg1-20+deb10u4 ii grub2-common 2.02+dfsg1-20+deb10u4 ii shim-helpers-amd64-signed 1+15.4+2~deb10u1 Versions of packages shim-signed recommends: pn secureboot-db shim-signed suggests no packages. -- debconf information excluded
Processed: affects 990072
Processing commands for cont...@bugs.debian.org: > affects 990072 + release.debian.org Bug #990072 [lxc] lxc-attach fails after debian 10.10 update Bug #990075 [lxc] lxc-attach fails after debian 10.10 update Ignoring request to set affects of bug 990072 to the same value previously set Ignoring request to set affects of bug 990075 to the same value previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 990072: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990072 990075: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990075 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: affects 990072
Processing commands for cont...@bugs.debian.org: > affects 990072 + release.debian.org Bug #990072 [lxc] lxc-attach fails after debian 10.10 update Bug #990075 [lxc] lxc-attach fails after debian 10.10 update Added indication that 990072 affects release.debian.org Added indication that 990075 affects release.debian.org > thanks Stopping processing here. Please contact me if you need assistance. -- 990072: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990072 990075: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990075 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#990072: lxc-attach fails after debian 10.10 update
Processing control commands: > tags -1 + moreinfo Bug #990072 [lxc] lxc-attach fails after debian 10.10 update Bug #990075 [lxc] lxc-attach fails after debian 10.10 update Added tag(s) moreinfo. Added tag(s) moreinfo. -- 990072: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990072 990075: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990075 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#990072: lxc-attach fails after debian 10.10 update
Control: tags -1 + moreinfo Hi Matthew, if the kernel downgrade fixes the issue for your then likely there is the regression in the linux upload. Can you verify if the following patch fixes your issue? https://lore.kernel.org/stable/20210614102643.875096...@linuxfoundation.org/ Regards, Salvatore
Bug#989545: libgl1-mesa-dri: si_texture.c:1727 si_texture_transfer_map - failed to create temporary texture to hold untiled copy
Control: reassign -1 src:llvm-toolchain-11 1:11.0.1-2 Control: affects -1 libgl1-mesa-dri Control: tags -1 patch On 2021-06-07 09:42:44 +0200, Rubin Simons wrote: > Package: libgl1-mesa-dri > Version: 20.3.4-1 > Severity: grave > Tags: upstream > Justification: renders package unusable > > Dear Maintainer, > > I'm using a Radeon Vega Frontier Edition with a Talos Blackbird Power9 system > (ppc64le). I'm constantly running into the issue mentioned here: > https://gitlab.freedesktop.org/mesa/mesa/-/issues/4107 > > The above issue documents an issue in mesa caused by a bug in LLVM. Yes, so let's reassign it there. llvm maintainers, please cherry pick https://github.com/llvm/llvm-project/commit/c5a1eb9b0a76 if possible. Cheers > > The issue manifests itself when using Firefox, or in Gnome, when clicking on > the top-bar, which crashes gnome-shell. Any crash always logs the following: > > EE ../src/gallium/drivers/radeonsi/si_texture.c:1727 si_texture_transfer_map > - failed to create temporary texture to hold untiled copy > LLVM triggered Diagnostic Handler: Illegal instruction detected: VOP* > instruction violates constant bus restriction > renamable $vgpr4 = V_CNDMASK_B32_e32 32768, killed $vgpr4, implicit killed > $vcc, implicit $exec > LLVM failed to compile shader > radeonsi: can't compile a main shader part > > It would be great if the resolution mentioned in the linked mesa issue #4107 > could be applied (I think this would require recompilation with an LLVM that > has said fix and/or a more general update of the LLVM runtime?). What I > understand from the upstream report is that the issue is not isolated to > non-x86 platforms, so I would imagine any Debian Bullseye user with a Vega > based Radeon would be impacted. > > *** Reporter, please consider answering these questions, where appropriate *** > >* What led up to the situation? > - Install Debian Bullseye + gnome-core on a Radeon Vega based system. >* What exactly did you do (or not do) that was effective (or > ineffective)? > - Click on Gnome top-bar after login. Watch X crash. Maximize any > window. Watch X crash. >* What was the outcome of this action? > - Frequent X crashes, graphics drawing corruption in Firefox. Above log > message appears frequently in logs. >* What outcome did you expect instead? > - A working system! > > *** End of the template - remove these template lines *** > > > VGA-compatible devices on PCI bus: > -- > :03:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. > [AMD/ATI] Vega 10 XTX [Radeon Vega Frontier Edition] [1002:6863] > 0005:02:00.0 VGA compatible controller [0300]: ASPEED Technology, Inc. ASPEED > Graphics Family [1a03:2000] (rev 41) > > Contents of /etc/X11/xorg.conf.d: > - > total 4 > -rw-r--r-- 1 root root 639 Jun 3 14:56 00-devices.conf > > /etc/modprobe.d contains no KMS configuration files. > > Kernel version (/proc/version): > --- > Linux version 5.10.0-7-powerpc64le (debian-ker...@lists.debian.org) (gcc-10 > (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) > #1 SMP Debian 5.10.40-1 (2021-05-28) > > No Xorg X server log files found. > > udev information: > - > P: > /devices/pci:00/:00:00.0/:01:00.0/:02:00.0/:03:00.1/sound/card0/input10 > L: 0 > E: > DEVPATH=/devices/pci:00/:00:00.0/:01:00.0/:02:00.0/:03:00.1/sound/card0/input10 > E: SUBSYSTEM=input > E: PRODUCT=0/0/0/0 > E: NAME="HDA ATI HDMI HDMI/DP,pcm=11" > E: PHYS="ALSA" > E: PROP=0 > E: EV=21 > E: SW=140 > E: MODALIAS=input:bvpe-e0,5,kramlsfw6,8, > E: USEC_INITIALIZED=5707489 > E: ID_INPUT=1 > E: ID_INPUT_SWITCH=1 > E: ID_PATH=pci-:03:00.1 > E: ID_PATH_TAG=pci-_03_00_1 > E: ID_FOR_SEAT=input-pci-_03_00_1 > E: TAGS=:seat: > E: CURRENT_TAGS=:seat: > > P: > /devices/pci:00/:00:00.0/:01:00.0/:02:00.0/:03:00.1/sound/card0/input10/event10 > N: input/event10 > L: 0 > E: > DEVPATH=/devices/pci:00/:00:00.0/:01:00.0/:02:00.0/:03:00.1/sound/card0/input10/event10 > E: SUBSYSTEM=input > E: DEVNAME=/dev/input/event10 > E: MAJOR=13 > E: MINOR=74 > E: USEC_INITIALIZED=5864423 > E: ID_INPUT=1 > E: ID_INPUT_SWITCH=1 > E: ID_PATH=pci-:03:00.1 > E: ID_PATH_TAG=pci-_03_00_1 > E: LIBINPUT_DEVICE_GROUP=0/0/0:ALSA > E: TAGS=:power-switch: > E: CURRENT_TAGS=:power-switch: > > P: > /devices/pci:00/:00:00.0/:01:00.0/:02:00.0/:03:00.1/sound/card0/input5 > L: 0 > E: > DEVPATH=/devices/pci:00/:00:00.0/:01:00.0/:02:00.0/:03:00.1/sound/card0/input5 > E: SUBSYSTEM=input > E: PRODUCT=0/0/0/0 > E: NAME="HDA ATI HDMI HDMI/DP,pcm=3" > E: PHYS="ALSA" > E: PROP=0 > E: EV=21 > E: SW=140 > E: MODALIAS=input:bvpe-e0,5,kramlsfw6,8, > E: USEC_INITIALIZED=5707853 > E: ID_INPUT=1 > E: ID
Processed: Re: Bug#989545: libgl1-mesa-dri: si_texture.c:1727 si_texture_transfer_map - failed to create temporary texture to hold untiled copy
Processing control commands: > reassign -1 src:llvm-toolchain-11 1:11.0.1-2 Bug #989545 [libgl1-mesa-dri] libgl1-mesa-dri: si_texture.c:1727 si_texture_transfer_map - failed to create temporary texture to hold untiled copy Bug reassigned from package 'libgl1-mesa-dri' to 'src:llvm-toolchain-11'. No longer marked as found in versions mesa/20.3.4-1. Ignoring request to alter fixed versions of bug #989545 to the same values previously set Bug #989545 [src:llvm-toolchain-11] libgl1-mesa-dri: si_texture.c:1727 si_texture_transfer_map - failed to create temporary texture to hold untiled copy Marked as found in versions llvm-toolchain-11/1:11.0.1-2. > affects -1 libgl1-mesa-dri Bug #989545 [src:llvm-toolchain-11] libgl1-mesa-dri: si_texture.c:1727 si_texture_transfer_map - failed to create temporary texture to hold untiled copy Added indication that 989545 affects libgl1-mesa-dri > tags -1 patch Bug #989545 [src:llvm-toolchain-11] libgl1-mesa-dri: si_texture.c:1727 si_texture_transfer_map - failed to create temporary texture to hold untiled copy Added tag(s) patch. -- 989545: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989545 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#990081: golang-uber-goleak: ftbfs with gccgo-go
Package: golang-uber-goleak Version: 1.1.0-2 Severity: serious This package ftbfs when built with gccgo-go (build log attached) diff --git a/debian/control b/debian/control index 90d37eb..9d17b02 100644 --- a/debian/control +++ b/debian/control @@ -6,7 +6,7 @@ Testsuite: autopkgtest-pkg-go Priority: optional Build-Depends: debhelper-compat (= 12), dh-golang, - golang-any, + gccgo-go, golang-github-stretchr-testify-dev Standards-Version: 4.5.1 Vcs-Browser: https://salsa.debian.org/go-team/packages/golang-uber-goleak This causes build failure in bullseye-backports as gccgo-go is preferred over golang-go. Either the dependency should be changed to golang-go or the failure with gccgo-go should be fixed. sbuild (Debian sbuild) 0.79.1 (22 April 2020) on mahishi +==+ | golang-uber-goleak 1.1.0-2 (amd64) Sat, 19 Jun 2021 19:26:08 + | +==+ Package: golang-uber-goleak Version: 1.1.0-2 Source Version: 1.1.0-2 Distribution: unstable Machine Architecture: amd64 Host Architecture: amd64 Build Architecture: amd64 Build Type: binary I: NOTICE: Log filtering will replace 'var/run/schroot/mount/unstable-amd64-sbuild-20ebc20d-645c-44ee-b371-d75872567fe5' with '<>' I: NOTICE: Log filtering will replace 'build/golang-uber-goleak-FU5ilk/resolver-VvoqLt' with '<>' +--+ | Update chroot| +--+ Get:1 http://deb.debian.org/debian unstable InRelease [161 kB] Get:2 http://deb.debian.org/debian unstable/main Sources.diff/Index [63.6 kB] Get:3 http://deb.debian.org/debian unstable/main amd64 Packages.diff/Index [63.6 kB] Get:4 http://deb.debian.org/debian unstable/main Sources T-2021-06-19-1401.23-F-2021-06-11-0801.30.pdiff [55.7 kB] Get:4 http://deb.debian.org/debian unstable/main Sources T-2021-06-19-1401.23-F-2021-06-11-0801.30.pdiff [55.7 kB] Get:5 http://deb.debian.org/debian unstable/main amd64 Packages T-2021-06-19-1401.23-F-2021-06-11-0801.30.pdiff [71.4 kB] Get:5 http://deb.debian.org/debian unstable/main amd64 Packages T-2021-06-19-1401.23-F-2021-06-11-0801.30.pdiff [71.4 kB] Fetched 415 kB in 5s (83.1 kB/s) Reading package lists... Reading package lists... Building dependency tree... Reading state information... Calculating upgrade... The following packages were automatically installed and are no longer required: bsdextrautils fontconfig-config fonts-dejavu-core krb5-locales libbrotli1 libbsd0 libc-devtools libdeflate0 libexpat1 libfontconfig1 libfreetype6 libgd3 libjbig0 libjpeg62-turbo libmd0 libnss-nis libnss-nisplus libpng16-16 libtiff5 libwebp6 libx11-6 libx11-data libxau6 libxcb1 libxdmcp6 libxpm4 manpages manpages-dev sensible-utils ucf Use 'apt autoremove' to remove them. The following packages will be upgraded: auto-apt-proxy libhogweed6 libnettle8 3 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 600 kB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://deb.debian.org/debian unstable/main amd64 libnettle8 amd64 3.7.3-1 [270 kB] Get:2 http://deb.debian.org/debian unstable/main amd64 libhogweed6 amd64 3.7.3-1 [320 kB] Get:3 http://deb.debian.org/debian unstable/main amd64 auto-apt-proxy all 13.3 [9320 B] debconf: delaying package configuration, since apt-utils is not installed Fetched 600 kB in 0s (1898 kB/s) (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 18699 files and directories currently installed.) Preparing to unpack .../libnettle8_3.7.3-1_amd64.deb ... Unpacking libnettle8:amd64 (3.7.3-1) over (3.7.2-3) ... Setting up libnettle8:amd64 (3.7.3-1) ... (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database
Processed: tagging 990079
Processing commands for cont...@bugs.debian.org: > tags 990079 + security Bug #990079 [chromium] chromium: Update Chromium to 91.0.4472.114 Added tag(s) security. > thanks Stopping processing here. Please contact me if you need assistance. -- 990079: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990079 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 989872
Processing commands for cont...@bugs.debian.org: > tags 989872 + buster Bug #989872 [src:thunderbird] thunderbird-dbgsym: uninstallable cruft package in buster Added tag(s) buster. > thanks Stopping processing here. Please contact me if you need assistance. -- 989872: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989872 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#987388: marked as done (Crash of amdgpu on Debian 11 Bullseye)
Your message dated Sat, 19 Jun 2021 18:43:59 +0100 with message-id <726398e3-85dc-6286-d4a6-337295ab9...@iremonger.me.uk> and subject line Re: Crash of amdgpu on Debian 11 Bullseye has caused the Debian Bug report #987388, regarding Crash of amdgpu on Debian 11 Bullseye 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.) -- 987388: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987388 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: xserver-xorg-video-amdgpu Version: 19.1.0-2 Severity: critical Hi. Today I reinstalled a machine on Debian 11 Bullseye from testing (it was on Debian 10 Buster) and I had a crash of the AMD R9 380. I could no longer change tty and Xorg was frozen, I could only move the mouse, the keyboard shortcut to reboot the kernel was not working. After manual shutdown (electrical) I found undred lines of this in syslog: Apr 22 22:36:18 maxime-pc kernel: [18427.590382] amdgpu :01:00.0: amdgpu: 3fb1172e pin failed Apr 22 22:36:18 maxime-pc kernel: [18427.590464] [drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer with error -12 Apr 22 22:36:18 maxime-pc kernel: [18427.605898] amdgpu :01:00.0: amdgpu: 03ab56e3 pin failed Apr 22 22:36:18 maxime-pc kernel: [18427.606010] [drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer with error -12 Apr 22 22:36:18 maxime-pc kernel: [18427.609057] amdgpu :01:00.0: amdgpu: 03ab56e3 pin failed Apr 22 22:36:18 maxime-pc kernel: [18427.609139] [drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer with error -12 Apr 22 22:36:18 maxime-pc kernel: [18427.610566] amdgpu :01:00.0: amdgpu: 03ab56e3 pin failed Apr 22 22:36:18 maxime-pc kernel: [18427.610644] [drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer with error -12 Apr 22 22:36:18 maxime-pc kernel: [18427.644577] amdgpu :01:00.0: amdgpu: 3fb1172e pin failed Apr 22 22:36:18 maxime-pc kernel: [18427.644659] [drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer with error -12 [...] Apr 22 22:37:15 maxime-pc kernel: [18484.803085] sysrq: HELP : loglevel(0-9) reboot(b) crash(c) terminate-all-tasks(e) memory-full-oom-kill(f) kill-all-tasks(i) thaw-filesystems(j) sak(k) show-backtrace-all-active-cpus(l) show-memory-usa ge(m) nice-all-RT-tasks(n) poweroff(o) show-registers(p) show-all-timers(q) unraw(r) sync(s) show-task-states(t) unmount(u) force-fb(v) show-blocked-tasks(w) dump-ftrace-buffer(z) Apr 22 22:37:15 maxime-pc kernel: [18484.803096] sysrq: HELP : loglevel(0-9) reboot(b) crash(c) terminate-all-tasks(e) memory-full-oom-kill(f) kill-all-tasks(i) thaw-filesystems(j) sak(k) show-backtrace-all-active-cpus(l) show-memory-usa ge(m) nice-all-RT-tasks(n) poweroff(o) show-registers(p) show-all-timers(q) unraw(r) sync(s) show-task-states(t) unmount(u) force-fb(v) show-blocked-tasks(w) dump-ftrace-buffer(z) Apr 22 22:37:18 maxime-pc kernel: [18487.595072] sysrq: HELP : loglevel(0-9) reboot(b) crash(c) terminate-all-tasks(e) memory-full-oom-kill(f) kill-all-tasks(i) thaw-filesystems(j) sak(k) show-backtrace-all-active-cpus(l) show-memory-usa ge(m) nice-all-RT-tasks(n) poweroff(o) show-registers(p) show-all-timers(q) unraw(r) sync(s) show-task-states(t) unmount(u) force-fb(v) show-blocked-tasks(w) dump-ftrace-buffer(z) Apr 22 22:37:18 maxime-pc kernel: [18487.875072] sysrq: HELP : loglevel(0-9) reboot(b) crash(c) terminate-all-tasks(e) memory-full-oom-kill(f) kill-all-tasks(i) thaw-filesystems(j) sak(k) show-backtrace-all-active-cpus(l) show-memory-usa ge(m) nice-all-RT-tasks(n) poweroff(o) show-registers(p) show-all-timers(q) unraw(r) sync(s) show-task-states(t) unmount(u) force-fb(v) show-blocked-tasks(w) dump-ftrace-buffer(z) (here I was typing on the emergency kernel reboot shortcut on keyboard) I don't know what could be the reason for this. But the problem has never occurred on Debian 10 Buster. Thanks. Max. --- End Message --- --- Begin Message --- Closing bug as per Maxime's previous message, reopen if problems recur. --Simon--- End Message ---
Bug#990079: chromium: Update Chromium to 91.0.4472.114
Package: chromium Version: 90.0.4430.212-1 Severity: grave Numerous security holes have been fixed in the latest version: https://security-tracker.debian.org/tracker/source-package/chromium
Bug#989888: marked as done (gnuradio-dev,gnuradio: ships files already in gr-soapy)
Your message dated Sat, 19 Jun 2021 16:49:43 + with message-id and subject line Bug#989888: fixed in gnuradio 3.9.2.0-2 has caused the Debian Bug report #989888, regarding gnuradio-dev,gnuradio: ships files already in gr-soapy 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.) -- 989888: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989888 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gnuradio-dev,gnuradio Version: 3.9.2.0-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Selecting previously unselected package gnuradio. Preparing to unpack .../113-gnuradio_3.9.2.0-1_amd64.deb ... Unpacking gnuradio (3.9.2.0-1) ... dpkg: error processing archive /tmp/apt-dpkg-install-E5LhJj/113-gnuradio_3.9.2.0-1_amd64.deb (--unpack): trying to overwrite '/usr/share/gnuradio/grc/blocks/soapy_sink.block.yml', which is also in package gr-soapy 2.1.3.1-1 Selecting previously unselected package gnuradio-dev:amd64. Preparing to unpack .../170-gnuradio-dev_3.9.2.0-1_amd64.deb ... Unpacking gnuradio-dev:amd64 (3.9.2.0-1) ... dpkg: error processing archive /tmp/apt-dpkg-install-E5LhJj/170-gnuradio-dev_3.9.2.0-1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libgnuradio-soapy.so', which is also in package gr-soapy 2.1.3.1-1 Errors were encountered while processing: /tmp/apt-dpkg-install-E5LhJj/113-gnuradio_3.9.2.0-1_amd64.deb /tmp/apt-dpkg-install-E5LhJj/170-gnuradio-dev_3.9.2.0-1_amd64.deb cheers, Andreas gr-soapy=2.1.3.1-1_gnuradio-dev=3.9.2.0-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: gnuradio Source-Version: 3.9.2.0-2 Done: A. Maitland Bottoms We believe that the bug you reported is fixed in the latest version of gnuradio, 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 989...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. A. Maitland Bottoms (supplier of updated gnuradio package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 19 Jun 2021 10:05:57 -0400 Source: gnuradio Architecture: source Version: 3.9.2.0-2 Distribution: experimental Urgency: medium Maintainer: A. Maitland Bottoms Changed-By: A. Maitland Bottoms Closes: 989888 Changes: gnuradio (3.9.2.0-2) experimental; urgency=medium . * Add Breaks+Replaces for gr-soapy (Closes: #989888) Checksums-Sha1: 91d83188967bfd26d4c38a0156703fac706f42aa 5071 gnuradio_3.9.2.0-2.dsc 3cbb52509d65f706d1abb197a516eb1b7b51f3a6 1472000 gnuradio_3.9.2.0-2.debian.tar.xz 12c2ca361810d64bca9382bdcdb120a106b1d88f 35956 gnuradio_3.9.2.0-2_amd64.buildinfo Checksums-Sha256: 69c39186b5ac70f1e5f999e2558a52b99e369954cb2e13c88f3203cfe7887d05 5071 gnuradio_3.9.2.0-2.dsc 0574abddec801e4038fc04a10931a290f72c5d3cbd842984fc3c1033e4a55918 1472000 gnuradio_3.9.2.0-2.debian.tar.xz 35668efb60e27748d3c7990fdef0e65d859fce9b226e494742a8d92078fdd485 35956 gnuradio_3.9.2.0-2_amd64.buildinfo Files: 5dc371dc44c5c3e4b2b75dd3bab9fc03 5071 comm optional gnuradio_3.9.2.0-2.dsc 4f6d1275c6e54d6bf8697c5d62767b5b 1472000 comm optional gnuradio_3.9.2.0-2.debian.tar.xz 33ab0c6e5172eb455fc3a5884840a78f 35956 comm optional gnuradio_3.9.2.0-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEB8qH3cTCsGJAtrF0UEHxiR9E4JAFAmDOG7EACgkQUEHxiR9E 4JCW0w/7B9UewMk6oN5But4tAieoRKpRX6n9kGzIZ/g+76D6NDxt0nXXHmZvZWkN TOoZnzj9Z70yRkkC1wzg01nADwDueH1L22RTZinvtsgfXRsqlyEeVxwbni1xBrpa m9fHn/icdeUFDCbyZzwuJDroLAwohzTLrDcvxMgvm7dp7EqhzB9MgWwpaKNOc1GG 5cb4RFWGV4MeXvjO9wH6nM5L+GqFHDK+UkwNgg55oKomt2oWATNWItM9CLrt/O0a 5525I/qhsz9HScKouZ0ZwQztOI9F7KMUQjzff5nH5GEmF78NmqbLW3Dy1YrqmePy dyuEockPbvgzCVeHv7PmoBrJRppgxurx5yqL
Processed: forcibly merging 990072 990075
Processing commands for cont...@bugs.debian.org: > forcemerge 990072 990075 Bug #990072 [lxc] lxc-attach fails after debian 10.10 update Bug #990075 [lxc] lxc-attach fails after debian 10.10 update Merged 990072 990075 > thanks Stopping processing here. Please contact me if you need assistance. -- 990072: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990072 990075: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990075 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#990072: Update
Reverting to previous kernel resolves the issue temporarily. Previous kernel is: 4.19.0-16-amd64 #1 SMP Debian 4.19.181-1 (2021-03-19) x86_64 GNU/Linux
Bug#990075:
Sorry, seems to be duplicate https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990072
Bug#987461: libuima-adapter-soap-java is empty
On Sat, Jun 19, 2021 at 10:29:25PM +0900, Hideki Yamane wrote: > control: tags -1 +patch > > On Sat, 24 Apr 2021 18:40:31 +0200 Chris Hofstaedtler wrote: > > It appears the change itself was intentional: > > > > > uimaj (2.10.2-2) unstable; urgency=medium > > > > > > * No longer build the uimaj-adapter-soap module > > > > > > -- Emmanuel Bourg Fri, 30 Nov 2018 09:07:17 +0100 > > > > However, the binary package should probably also have been removed. > > > > Maintainers, please come to a conclusion regarding the now empty binary > > package. > > Okay, libuima-adapter-soap-java has no reverse dependency. > > $ apt-rdepends -r libuima-adapter-soap-java > Reading package lists... Done > Building dependency tree... Done > Reading state information... Done > libuima-adapter-soap-java > > > So let's remove its binary package and add Breaks: to it. > MR is here, could someone review it, please? > https://salsa.debian.org/java-team/uimaj/-/merge_requests/1 Thank you for addressing this. I will handle the merge and upload. Just one quick question... Why is the Breaks necessary? Is it there to force removal of libuima-adapter-soap-java when libuima-core-java is upgraded? Cheers, tony
Bug#988707: marked as done (qthid-fcd-controller: triggers lintian autoreject tag 'bogus-mail-host')
Your message dated Sat, 19 Jun 2021 14:20:15 + with message-id and subject line Bug#988707: fixed in qthid-fcd-controller 4.1-6 has caused the Debian Bug report #988707, regarding qthid-fcd-controller: triggers lintian autoreject tag 'bogus-mail-host' 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.) -- 988707: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988707 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: qthid-fcd-controller Version: 4.1-5 Severity: serious Hi, src:qthid-fcd-controller triggers the lintian autoreject tag 'bogus-mail-host', i.e. if the package would be reuploaded today without changes, it would be automatically rejected by ftp-master. https://lintian.debian.org/tags/bogus-mail-host E Uploaders anar...@koumbit.og Andreas --- End Message --- --- Begin Message --- Source: qthid-fcd-controller Source-Version: 4.1-6 Done: A. Maitland Bottoms We believe that the bug you reported is fixed in the latest version of qthid-fcd-controller, 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 988...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. A. Maitland Bottoms (supplier of updated qthid-fcd-controller package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 19 Jun 2021 07:52:10 -0400 Source: qthid-fcd-controller Architecture: source Version: 4.1-6 Distribution: unstable Urgency: medium Maintainer: Debian Hamradio Maintainers Changed-By: A. Maitland Bottoms Closes: 988707 Changes: qthid-fcd-controller (4.1-6) unstable; urgency=medium . * Update package and move to Hamradio Maintainers group (Closes: #988707) Checksums-Sha1: a2c962175d06b4c002d77e51fc1441ca5bff31b7 2552 qthid-fcd-controller_4.1-6.dsc 1cc8c2851dd5e419cbad9e9cffc369f5374dfa92 16524 qthid-fcd-controller_4.1-6.debian.tar.xz 133191f68099af3751b5f8f5ef658986a94657a4 11077 qthid-fcd-controller_4.1-6_amd64.buildinfo Checksums-Sha256: 83f3c578e036e2f759e0191c370c6307458cfc0ff03e37480ad617d77b077ba2 2552 qthid-fcd-controller_4.1-6.dsc 027da84424a06d46f395c665352348c4c9f066a02e882d405aff3f4454903204 16524 qthid-fcd-controller_4.1-6.debian.tar.xz db00c68407786ca035d5485515111fc39205eb9baef79e1ca86c2cdaae7d2cd5 11077 qthid-fcd-controller_4.1-6_amd64.buildinfo Files: f70ac7fba7f0a072bd0cbdca99ec6a21 2552 science optional qthid-fcd-controller_4.1-6.dsc 380fd2d3f17275f8ce4e4d9b24bd1937 16524 science optional qthid-fcd-controller_4.1-6.debian.tar.xz d37a5fb4f9395fc3391fa29caa8e07d6 11077 science optional qthid-fcd-controller_4.1-6_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEB8qH3cTCsGJAtrF0UEHxiR9E4JAFAmDN9MIACgkQUEHxiR9E 4JAOkhAAi4ePgSXMbyCphRrwi+5TH1fx7jK2nx30NbYPAUSutQB1dvwAbjDZRxv6 aDrFcaAr/w145L1PghIRVu9EA/EbiiBQgtZKQnEOVC6vL5DdLOQErBUpkG3wLNqd ksCauS9ufUX1ZZDoLqrufAEYEcEVk+SHcCdI2mxiG06rZLIhwweawS3LvN0Svbl4 +W8lRoCUv2uVUEwj4kMyyzOSJkjktqMMkDW7Vtd8MVm8eOXK5HvV8QguMAUN3Vem FPAUq0QhIXLZd9RLxG/OztRIkO5L0i1K3bacEnECt5immpFHVfswlMg7REyUL2FO stSTkCVnDCF/FsIH9WuW5hn+bpdN6BvHacQHE0odCIQcGeIkAPOPKBqrtunYZdyL 82tF+me7jqmLG3ulsA1J0KrlLDhwqvV6PohDHT9Y3KCkFyMAmmcx0K1nNiNqqncF OGWi19dE3DavN6vfWZ9fV1iY4oJQSOnNfne308Q8M0KRsqqYRCuEvyXUR4QbjZhl 5FFNfKQC7Du5nmjkh+1QQAM+KFxGvfh83yaW0HoWVqGcLx8zlu5tg1MNIuHvSuY3 UEzh3zXqwoMNToZhgz21vVT6PEqTx/iI/yLzEFQBU0mzliDgWabJ/arvCcXOfTZj hjt0SppIa1JgbhALEd8fHRU3q19Gi945fBi255mKN91QUT2zXQE= =ThE9 -END PGP SIGNATURE End Message ---
Bug#963382: marked as done (kubectx: FTBFS: not ok 4 list contexts when no kubeconfig exists)
Your message dated Sat, 19 Jun 2021 14:19:33 + with message-id and subject line Bug#963382: fixed in kubectx 0.9.3-1 has caused the Debian Bug report #963382, regarding kubectx: FTBFS: not ok 4 list contexts when no kubeconfig exists 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.) -- 963382: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963382 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: kubectx Version: 0.6.3-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200620 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > bats test/kubectx.bats > 1..16 > ok 1 --help should not fail > ok 2 -h should not fail > ok 3 switch to previous context when no one exists > not ok 4 list contexts when no kubeconfig exists > # (in test file test/kubectx.bats, line 32) > # `[[ "$output" = "" ]]' failed > # W0621 07:29:20.9644054474 loader.go:223] Config not found: > /tmp/tmp.az9itKYJqk/config > # W0621 07:29:21.0039844482 loader.go:223] Config not found: > /tmp/tmp.az9itKYJqk/config > ok 5 get one context and list contexts > ok 6 get two contexts and list contexts > ok 7 get two contexts and select contexts > ok 8 get two contexts and switch between contexts > ok 9 get one context and switch to non existent context > ok 10 rename context > ok 11 rename current context > ok 12 delete context > ok 13 delete current context > ok 14 delete non existent context > ok 15 delete several contexts > ok 16 delete several contexts including a non existent one > make[1]: *** [debian/rules:10: override_dh_auto_test] Error 1 The full build log is available from: http://qa-logs.debian.net/2020/06/20/kubectx_0.6.3-2_unstable.log 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! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: kubectx Source-Version: 0.9.3-1 Done: ChangZhuo Chen (陳昌倬) We believe that the bug you reported is fixed in the latest version of kubectx, 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 963...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. ChangZhuo Chen (陳昌倬) (supplier of updated kubectx package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 19 Jun 2021 16:25:56 +0800 Source: kubectx Architecture: source Version: 0.9.3-1 Distribution: unstable Urgency: medium Maintainer: ChangZhuo Chen (陳昌倬) Changed-By: ChangZhuo Chen (陳昌倬) Closes: 963382 Changes: kubectx (0.9.3-1) unstable; urgency=medium . * New upstream release. * Bump compat to 13. * Bump Standards-Version to 4.5.1. * Set Rules-Requires-Root to no. * Fix test cases (Closes: #963382). Checksums-Sha1: a0128935754fc174b402e4b2b9a4ea362c556774 1848 kubectx_0.9.3-1.dsc d80be82358311e692c0be66dc02598a050f40490 520511 kubectx_0.9.3.orig.tar.gz 7885a9c6aca7bf38af8642c595ec03253b761c68 2476 kubectx_0.9.3-1.debian.tar.xz 54ee5759172c32c2527c5281909dce3f4b937d6e 5875 kubectx_0.9.3-1_source.buildinfo Checksums-Sha256: 704a5f6b54cb199160297e5e9210da2c5695be3f56bb1f2ef15284dd71a4f08d 1848 kubectx_0.9.3-1.dsc c9f1323f759605405ef8240d6fa64e741b788d978dff25d624a90af2760e778d 520511 kubectx_0.9.3.orig.tar.gz 4b649eb5dafe27729b222e94738ba598ee4d728b87cdf81a06803ab04a293655 2476 kubectx_0.9.3-1.debian.tar.xz bb68c3db354b823cc80be29610ee8df49a565a57ca1171333b31022d52952354 5875 kubectx_0.9.3-1_source.buildinfo Files: e2434a1bfd07d51b842fdc4a7bf44cc1 1848 devel optional kubectx_0.9.3-1.dsc 481281285a42c48914fcd66828333c6f 520511 devel optional kubectx_0.9.3.orig.tar.gz fd3217957292208a9c01cb5c2a1f390d 2476 devel optional kubectx_0.9.3-1.debian.tar.xz 0532d2b4510c77add168ad1e4582dfa2 5875 devel optional kubectx_0.9.3-1_source.buildinfo -BE
Bug#990075: lxc-attach fails after debian 10.10 update
Package: lxc Version: 1:3.1.0+really3.0.3-8 Severity: grave Justification: renders package unusable Dear Maintainer, Applied latest apt updates (debian 10.10) and rebooted. After reboot, lxc-attach doesn't work. from /var/log/apt/history.log: Start-Date: 2021-06-19 12:27:42 Commandline: apt-get dist-upgrade Requested-By: matthew (1011) Install: linux-headers-4.19.0-17-common:amd64 (4.19.194-1, automatic), linux-headers-4.19.0-17-amd64:amd64 (4.19.194-1, automatic), linux-image-4.19.0-17-amd64:amd64 (4.19.194-1, automatic) Upgrade: libapt-inst2.0:amd64 (1.8.2.2, 1.8.2.3),apt:amd64 (1.8.2.2, 1.8.2.3), mariadb-common:amd64 (1:10.3.27-0+deb10u1, 1:10.3.29-0+deb10u1), linux-compiler-gcc-8-x86:amd64 (4.19.181-1, 4.19.194-1), libklibc:amd64 (2.0.6-1, 2.0.6-1+deb10u1), libcpupower1:amd64 (4.19.181-1, 4.19.194-1), libapt-pkg5.0:amd64 (1.8.2.2, 1.8.2.3), shim-helpers-amd64-signed:amd64 (1+15+1533136590.3beb971+7+deb10u1, 1+15.4+5~deb10u1), linux-image-amd64:amd64 (4.19+105+deb10u11, 4.19+105+deb10u12), libgcrypt20:amd64 (1.8.4-5, 1.8.4-5+deb10u1), linux-headers-amd64:amd64 (4.19+105+deb10u11, 4.19+105+deb10u12), libhogweed4:amd64 (3.4.1-1, 3.4.1-1+deb10u1), apt-utils:amd64 (1.8.2.2, 1.8.2.3), shim-unsigned:amd64 (15+1533136590.3beb971-7+deb10u1, 15.4-5~deb10u1), shim-signed:amd64 (1.33+15+1533136590.3beb971-7, 1.36~1+deb10u1+15.4-5~deb10u1), libnettle6:amd64 (3.4.1-1, 3.4.1-1+deb10u1), libxml2:amd64 (2.9.4+dfsg1-7+deb10u1, 2.9.4+dfsg1-7+deb10u2), libmariadb3:amd64 (1:10.3.27-0+deb10u1, 1:10.3.29-0+deb10u1), libgnutls30:amd64 (3.6.7-4+deb10u6, 3.6.7-4+deb10u7), linux-kbuild-4.19:amd64 (4.19.181-1, 4.19.194-1), klibc-utils:amd64 (2.0.6-1, 2.0.6-1+deb10u1), libglib2.0-0:amd64 (2.58.3-2+deb10u2, 2.58.3-2+deb10u3), shim-signed-common:amd64 (1.33+15+1533136590.3beb971-7, 1.36~1+deb10u1+15.4-5~deb10u1), linux-cpupower:amd64 (4.19.181-1, 4.19.194-1), base-files:amd64 (10.3+deb10u9, 10.3+deb10u10) End-Date: 2021-06-19 12:29:41 $ lxc-attach mar-mon1 lxc-attach: mar-mon1: lsm/lsm.c: lsm_process_label_set_at: 174 Operation not permitted - Failed to set AppArmor label "lxc-mar-mon1_//&:lxc-mar-mon1_<-var-lib-lxc>:unconfined" The lxc-config file contains lxc.apparmor.profile = generated lxc.apparmor.allow_nesting = 1 The generated apparmor seems unchanged when I compare it to containers on a server I didn't reboot. I did reboot 2 servers after this debian update, and both have this problem. -- System Information: Debian Release: 10.10 APT prefers stable APT policy: (500, 'stable'), (90, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-17-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages lxc depends on: ii debconf [debconf-2.0] 1.5.71 ii libc6 2.28-10 ii libcap21:2.25-2 ii libgnutls303.6.7-4+deb10u7 ii liblxc11:3.1.0+really3.0.3-8 ii libseccomp22.3.3-4 ii libselinux12.8-1+b1 ii lsb-base 10.2019051400 Versions of packages lxc recommends: ii apparmor 2.13.2-10 ii bridge-utils 1.6-2 pn debootstrap ii dirmngr2.2.12-1+deb10u1 pn dnsmasq-base ii gnupg 2.2.12-1+deb10u1 ii iproute2 4.20.0-2+deb10u1 ii iptables 1.8.2-4 pn libpam-cgfs pn lxc-templates ii lxcfs 3.0.3-2 ii openssl1.1.1d-0+deb10u6 pn rsync pn uidmap Versions of packages lxc suggests: pn btrfs-progs pn lvm2 pn python3-lxc
Bug#987461: libuima-adapter-soap-java is empty
control: tags -1 +patch On Sat, 24 Apr 2021 18:40:31 +0200 Chris Hofstaedtler wrote: > It appears the change itself was intentional: > > > uimaj (2.10.2-2) unstable; urgency=medium > > > > * No longer build the uimaj-adapter-soap module > > > > -- Emmanuel Bourg Fri, 30 Nov 2018 09:07:17 +0100 > > However, the binary package should probably also have been removed. > > Maintainers, please come to a conclusion regarding the now empty binary > package. Okay, libuima-adapter-soap-java has no reverse dependency. $ apt-rdepends -r libuima-adapter-soap-java Reading package lists... Done Building dependency tree... Done Reading state information... Done libuima-adapter-soap-java So let's remove its binary package and add Breaks: to it. MR is here, could someone review it, please? https://salsa.debian.org/java-team/uimaj/-/merge_requests/1 -- Regards, Hideki Yamane henrich @ debian.org/iijmio-mail.jp
Processed: Re: Bug#987461: libuima-adapter-soap-java is empty
Processing control commands: > tags -1 +patch Bug #987461 [libuima-adapter-soap-java] libuima-adapter-soap-java is empty Added tag(s) patch. -- 987461: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987461 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#990072: lxc-attach fails after debian 10.10 update
Package: lxc Version: 1:3.1.0+really3.0.3-8 Severity: grave Justification: renders package unusable Dear Maintainer, Applied latest apt updates (debian 10.10) and rebooted. After reboot, lxc-attach doesn't work. from /var/log/apt/history.log: Start-Date: 2021-06-19 12:27:42 Commandline: apt-get dist-upgrade Requested-By: matthew (1011) Install: linux-headers-4.19.0-17-common:amd64 (4.19.194-1, automatic), linux-headers-4.19.0-17-amd64:amd64 (4.19.194-1, automatic), linux-image-4.19.0-17-amd64:amd64 (4.19.194-1, automatic) Upgrade: libapt-inst2.0:amd64 (1.8.2.2, 1.8.2.3), apt:amd64 (1.8.2.2, 1.8.2.3), mariadb-common:amd64 (1:10.3.27-0+deb10u1, 1:10.3.29-0+deb10u1), linux-compiler-gcc-8-x86:amd64 (4.19.181-1, 4.19.194-1), libklibc:amd64 (2.0.6-1, 2.0.6-1+deb10u1), libcpupower1:amd64 (4.19.181-1, 4.19.194-1), libapt-pkg5.0:amd64 (1.8.2.2, 1.8.2.3), shim-helpers-amd64-signed:amd64 (1+15+1533136590.3beb971+7+deb10u1, 1+15.4+5~deb10u1), linux-image-amd64:amd64 (4.19+105+deb10u11, 4.19+105+deb10u12), libgcrypt20:amd64 (1.8.4-5, 1.8.4-5+deb10u1), linux-headers-amd64:amd64 (4.19+105+deb10u11, 4.19+105+deb10u12), libhogweed4:amd64 (3.4.1-1, 3.4.1-1+deb10u1), apt-utils:amd64 (1.8.2.2, 1.8.2.3), shim-unsigned:amd64 (15+1533136590.3beb971-7+deb10u1, 15.4-5~deb10u1), shim-signed:amd64 (1.33+15+1533136590.3beb971-7, 1.36~1+deb10u1+15.4-5~deb10u1), libnettle6:amd64 (3.4.1-1, 3.4.1-1+deb10u1), libxml2:amd64 (2.9.4+dfsg1-7+deb10u1, 2.9.4+dfsg1-7+deb10u2), libmariadb3:amd64 (1:10.3.27-0+deb10u1, 1:10.3.29-0+deb10u1), libgnutls30:amd64 (3.6.7-4+deb10u6, 3.6.7-4+deb10u7), linux-kbuild-4.19:amd64 (4.19.181-1, 4.19.194-1), klibc-utils:amd64 (2.0.6-1, 2.0.6-1+deb10u1), libglib2.0-0:amd64 (2.58.3-2+deb10u2, 2.58.3-2+deb10u3), shim-signed-common:amd64 (1.33+15+1533136590.3beb971-7, 1.36~1+deb10u1+15.4-5~deb10u1), linux-cpupower:amd64 (4.19.181-1, 4.19.194-1), base-files:amd64 (10.3+deb10u9, 10.3+deb10u10) End-Date: 2021-06-19 12:29:41 $ lxc-attach mar-mon1 lxc-attach: mar-mon1: lsm/lsm.c: lsm_process_label_set_at: 174 Operation not permitted - Failed to set AppArmor label "lxc-mar-mon1_//&:lxc-mar-mon1_<-var-lib-lxc>:unconfined" The lxc-config file contains lxc.apparmor.profile = generated lxc.apparmor.allow_nesting = 1 The generated apparmor seems unchanged when I compare it to containers on a server I didn't reboot. I did reboot 2 servers after this debian update, and both have this problem. -- System Information: Debian Release: 10.10 APT prefers stable APT policy: (500, 'stable'), (90, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-17-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages lxc depends on: ii debconf [debconf-2.0] 1.5.71 ii libc6 2.28-10 ii libcap21:2.25-2 ii libgnutls303.6.7-4+deb10u7 ii liblxc11:3.1.0+really3.0.3-8 ii libseccomp22.3.3-4 ii libselinux12.8-1+b1 ii lsb-base 10.2019051400 Versions of packages lxc recommends: ii apparmor 2.13.2-10 ii bridge-utils 1.6-2 pn debootstrap ii dirmngr2.2.12-1+deb10u1 pn dnsmasq-base ii gnupg 2.2.12-1+deb10u1 ii iproute2 4.20.0-2+deb10u1 ii iptables 1.8.2-4 pn libpam-cgfs pn lxc-templates ii lxcfs 3.0.3-2 ii openssl1.1.1d-0+deb10u6 pn rsync pn uidmap Versions of packages lxc suggests: pn btrfs-progs pn lvm2 pn python3-lxc -- debconf information excluded
Processed: severity of 989615 is grave
Processing commands for cont...@bugs.debian.org:
> severity 989615 grave
Bug #989615 {Done: Henrique de Moraes Holschuh }
[src:intel-microcode] intel-microcode: CVE-2020-24511 CVE-2020-24512
CVE-2020-24513 CVE-2020-24489 (INTEL-SA-00464, INTEL-SA-00465, INTEL-SA-00442)
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
989615: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989615
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#988089: [debian-mysql] Bug#988089: Bug#988089: mariadb-server: MariaDB uninstalled on dist-upgrade Debian 10 -> 11
> Op za 22 mei 2021 om 23:30 schreef Otto Kekäläinen : > > Would somebody like to review/test it? Doesn't seem to be working for me: # apt full-upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following packages will be REMOVED: libpython-stdlib mariadb-client-10.3 mariadb-client-core-10.3 mariadb-server mariadb-server-10.3 mariadb-server-core-10.3 python python-minimal The following packages will be upgraded: galera-3 libpython2-stdlib libpython2.7-minimal libpython2.7-stdlib python2 python2-minimal python2.7 python2.7-minimal 8 upgraded, 0 newly installed, 8 to remove and 0 not upgraded. # apt dist-upgrade -o Debug::pkgDepCache::AutoInstall=1 -o Debug::pkgDepCache::Marker=1 -o Debug::pkgProblemResolver=1 Reading package lists... Done Building dependency tree... Done Reading state information... Done MarkInstall initramfs-tools-core:amd64 < 0.140 @ii mK NPb IPb > FU=0 ignore old unsatisfied important dependency on pigz:amd64 Delayed Removing: libpython-stdlib:amd64 as upgrade is not an option for python2.7-minimal:amd64 (2.7.18-7) Delayed Removing: python:amd64 as upgrade is not an option for python2.7-minimal:amd64 (2.7.18-7) Delayed Removing: python-minimal:amd64 as upgrade is not an option for python2.7-minimal:amd64 (2.7.18-7) MarkInstall python2.7-minimal:amd64 < 2.7.16-2+deb10u1 -> 2.7.18-7 @ii umU Ib > FU=0 MarkDelete libpython-stdlib:amd64 < 2.7.16-1 @ii mK Ib > FU=0 MarkDelete python:amd64 < 2.7.16-1 @ii mK Ib > FU=0 MarkDelete python-minimal:amd64 < 2.7.16-1 @ii mK Ib > FU=0 MarkInstall iptables:amd64 < 1.8.7-1 @ii mK NPb IPb > FU=0 ignore old unsatisfied important dependency on nftables:amd64 MarkInstall mariadb-server:amd64 < 1:10.3.29-0+deb10u1 -> 1:10.5.10-2 @ii umU Ib > FU=0 Installing mariadb-server-10.5:amd64 as Depends of mariadb-server:amd64 Delayed Removing: mariadb-server-10.3:amd64 as upgrade is not an option for mariadb-server-10.5:amd64 (1:10.5.10-2) Delayed Removing: mariadb-server-10.3:amd64 as upgrade is not an option for mariadb-server-10.5:amd64 (1:10.5.10-2) MarkInstall mariadb-server-10.5:amd64 < none -> 1:10.5.10-2 @un uN Ib > FU=0 Installing galera-4:amd64 as Depends of mariadb-server-10.5:amd64 MarkKeep galera-3:amd64 < 25.3.25-2 -> 25.3.31-2+b1 @ii umU > FU=0 Delayed Removing: galera-3:amd64 as upgrade is not an option for galera-4:amd64 (26.4.8-1) Delayed Removing: galera-3:amd64 as upgrade is not an option for galera-4:amd64 (26.4.8-1) Delayed Removing: galera-3:amd64 as upgrade is not an option for galera-4:amd64 (26.4.8-1) Delayed Removing: galera-3:amd64 as upgrade is not an option for galera-4:amd64 (26.4.8-1) MarkInstall galera-4:amd64 < none -> 26.4.8-1 @un uN Ib > FU=0 MarkDelete galera-3:amd64 < 25.3.25-2 | 25.3.31-2+b1 @ii umH Ib > FU=0 Installing mariadb-client-10.5:amd64 as Depends of mariadb-server-10.5:amd64 Delayed Removing: mariadb-client-10.3:amd64 as upgrade is not an option for mariadb-client-10.5:amd64 (1:10.5.10-2) Delayed Removing: mariadb-client-10.3:amd64 as upgrade is not an option for mariadb-client-10.5:amd64 (1:10.5.10-2) Delayed Removing: mariadb-client-core-10.3:amd64 as upgrade is not an option for mariadb-client-10.5:amd64 (1:10.5.10-2) MarkInstall mariadb-client-10.5:amd64 < none -> 1:10.5.10-2 @un uN Ib > FU=0 Installing mariadb-client-core-10.5:amd64 as Depends of mariadb-client-10.5:amd64 Delayed Removing: mariadb-client-core-10.3:amd64 as upgrade is not an option for mariadb-client-core-10.5:amd64 (1:10.5.10-2) Delayed Removing: mariadb-client-core-10.3:amd64 as upgrade is not an option for mariadb-client-core-10.5:amd64 (1:10.5.10-2) MarkInstall mariadb-client-core-10.5:amd64 < none -> 1:10.5.10-2 @un uN Ib > FU=0 MarkDelete mariadb-client-core-10.3:amd64 < 1:10.3.29-0+deb10u1 @ii mK Ib > FU=0 MarkDelete mariadb-client-10.3:amd64 < 1:10.3.29-0+deb10u1 @ii mK Ib > FU=0 Installing mariadb-server-core-10.5:amd64 as Depends of mariadb-server-10.5:amd64 Delayed Removing: mariadb-server-core-10.3:amd64 as upgrade is not an option for mariadb-server-core-10.5:amd64 (1:10.5.10-2) Delayed Removing: mariadb-server-10.3:amd64 as upgrade is not an option for mariadb-server-core-10.5:amd64 (1:10.5.10-2) Delayed Removing: mariadb-server-core-10.3:amd64 as upgrade is not an option for mariadb-server-core-10.5:amd64 (1:10.5.10-2) MarkInstall mariadb-server-core-10.5:amd64 < none -> 1:10.5.10-2 @un uN Ib > FU=0 MarkDelete mariadb-server-core-10.3:amd64 < 1:10.3.29-0+deb10u1 @ii mK Ib > FU=0 MarkDelete mariadb-server-10.3:amd64 < 1:10.3.29-0+deb10u1 @ii mK Ib > FU=0 MarkKeep python-minimal:amd64 < 2.7.16-1 @ii mR > FU=0 MarkInstall libcap2-bin:amd64 < 1:2.44-1 @ii mK NPb IPb > FU=0 ignore old unsatisfied important dependency on libpam-cap:a
Processed: reassign 962493 to ftp.debian.org ..., severity of 962493 is normal
Processing commands for cont...@bugs.debian.org: > reassign 962493 ftp.debian.org Bug #962493 [python3-backports.tempfile] python3-backports.tempfile seems to be useless Bug reassigned from package 'python3-backports.tempfile' to 'ftp.debian.org'. No longer marked as found in versions python-backports.tempfile/1.0-4. Ignoring request to alter fixed versions of bug #962493 to the same values previously set > retitle 962493 RM: python-backports.tempfile -- RoM: deprecated, no longer > useful Bug #962493 [ftp.debian.org] python3-backports.tempfile seems to be useless Changed Bug title to 'RM: python-backports.tempfile -- RoM: deprecated, no longer useful' from 'python3-backports.tempfile seems to be useless'. > severity 962493 normal Bug #962493 [ftp.debian.org] RM: python-backports.tempfile -- RoM: deprecated, no longer useful Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 962493: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962493 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 962494 to ftp.debian.org ..., severity of 962494 is normal
Processing commands for cont...@bugs.debian.org: > reassign 962494 ftp.debian.org Bug #962494 [python3-backports.weakref] python3-backports.weakref seems to be useless Bug reassigned from package 'python3-backports.weakref' to 'ftp.debian.org'. No longer marked as found in versions python-backports.weakref/1.0-3. Ignoring request to alter fixed versions of bug #962494 to the same values previously set > retitle 962494 RM: python-backport.weakref -- RoM: deprecated, no longer > useful Bug #962494 [ftp.debian.org] python3-backports.weakref seems to be useless Changed Bug title to 'RM: python-backport.weakref -- RoM: deprecated, no longer useful' from 'python3-backports.weakref seems to be useless'. > severity 962494 normal Bug #962494 [ftp.debian.org] RM: python-backport.weakref -- RoM: deprecated, no longer useful Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 962494: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962494 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: fix versions
Processing commands for cont...@bugs.debian.org: > notfound 990026 cron/3.0pl1-134 Bug #990026 [cron] cron: Reduced charset in MAILTO causes breakage No longer marked as found in versions cron/3.0pl1-134. > found 990026 cron/3.0pl1-137 Bug #990026 [cron] cron: Reduced charset in MAILTO causes breakage Marked as found in versions cron/3.0pl1-137. > -- Stopping processing here. Please contact me if you need assistance. -- 990026: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990026 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
