kwave is marked for autoremoval from testing

kwave 21.08.0-1 is marked for autoremoval from testing on 2022-05-09 It (build-)depends on packages with these RC bugs: 1008424: audiofile: FTBFS: dh_auto_test: error: make -j8 check VERBOSE=1 returned exit code 2 https://bugs.debian.org/1008424 This mail is generated by: https://salsa.debian

Bug#1004610: ffmpegthumbs: diff for NMU version 4:21.12.3-1.1

Le dimanche 3 avril 2022, 20:22:47 CEST Sebastian Ramacher a écrit : > Control: tags 1004610 + patch > Control: tags 1004610 + pending > > Dear maintainer, Dear Sebastian, > I've prepared an NMU for ffmpegthumbs (versioned as 4:21.12.3-1.1) and > uploaded it to DELAYED/7. Please feel free to tel

Processing of ffmpegthumbs_21.12.3-1.1_source.changes

ffmpegthumbs_21.12.3-1.1_source.changes uploaded successfully to localhost along with the files: ffmpegthumbs_21.12.3-1.1.dsc ffmpegthumbs_21.12.3-1.1.debian.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org)

Processed: ffmpegthumbs: diff for NMU version 4:21.12.3-1.1

Processing control commands: > tags 1004610 + patch Bug #1004610 [src:ffmpegthumbs] ffmpegthumbs: FTBFS with ffmpeg 5.0 Added tag(s) patch. > tags 1004610 + pending Bug #1004610 [src:ffmpegthumbs] ffmpegthumbs: FTBFS with ffmpeg 5.0 Added tag(s) pending. -- 1004610: https://bugs.debian.org/cgi-b

Bug#1004610: ffmpegthumbs: diff for NMU version 4:21.12.3-1.1

Control: tags 1004610 + patch Control: tags 1004610 + pending Dear maintainer, I've prepared an NMU for ffmpegthumbs (versioned as 4:21.12.3-1.1) and uploaded it to DELAYED/7. Please feel free to tell me if I should delay it longer. Cheers -- Sebastian Ramacher diff -Nru ffmpegthumbs-21.12.3/de

Bug#1008862: trace from Unstable

Hi Russell, I'm not quite sure what you'd expect a maintainer to do about this. If you think this is a bug, then I suggest you report it upstream. -- Med vänliga hälsningar Patrick Franz

Bug#1008885: loops endlessly about (failed?) mariadb start

Package: akonadi-server Version: 4:21.12.3-2 Severity: normal Hi, to see whether KDE Wayland works better when started via gdm3 instead of sddm (spoiler: No, same way of broken as with sddm), I exchanged sddm with gdm3. After going back to KDE X11 Session, I found my log being spammed with the fo