redland-bindings_1.0.17.1+dfsg-2_amd64.changes ACCEPTED into unstable, unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 01 Aug 2022 21:23:03 +0200 Source: redland-bindings Binary: librdf-perl librdf-perl-dbgsym python3-librdf python3-librdf-dbgsym ruby-librdf ruby-librdf-dbgsym Architecture: source amd64 Version: 1.0.17.1+dfsg-2

redland-bindings_1.0.17.1+dfsg-2_amd64.changes is NEW

binary:python3-librdf is NEW. binary:python3-librdf is NEW. Your package has been put into the NEW queue, which requires manual action from the ftpteam to process. The upload was otherwise valid (it had a good OpenPGP signature and file hashes are valid), so please be patient. Packages are

Processing of redland-bindings_1.0.17.1+dfsg-2_amd64.changes

redland-bindings_1.0.17.1+dfsg-2_amd64.changes uploaded successfully to localhost along with the files: redland-bindings_1.0.17.1+dfsg-2.dsc redland-bindings_1.0.17.1+dfsg-2.debian.tar.xz librdf-perl-dbgsym_1.0.17.1+dfsg-2_amd64.deb librdf-perl_1.0.17.1+dfsg-2_amd64.deb

Re: qtav: FTBFS with ffmpeg 5.0

Heads up for those following this bug: qtav appears to be unmaintained upstream. My only interest in the package was to enable video playback in digikam. Digikam upstream has taken most of the qtav code, incorporated into digikam source tree and fixed it up. The next release of digikam

Bug#982459: mdadm examine corrupts host ext4

On Sun, 31 Jul 2022, Chris Hofstaedtler wrote: I can't see a difference that should matter from userspace. I have stared a bit at the kernel code... there have been quite some changes and fixes in this area. Which kernel version were you running when testing this? Could you retry on