Your message dated Mon, 24 Aug 2026 14:28:02 +0200
with message-id <aow4has5-z9FJP8c@debian>
and subject line Re: alsa-ucm-conf: backport 1.2.16 to trixie
has caused the Debian Bug report #1141067,
regarding alsa-ucm-conf: backport 1.2.16 to trixie
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 [email protected]
immediately.)
--
1141067: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1141067
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: alsa-ucm-conf
Version: 1.2.16-1
Severity: wishlist
X-Debbugs-Cc: [email protected], [email protected],
[email protected]
Dear Maintainer,
I am planning to perform a backport of 1.2.16 to trixie to enable
hardware that require the latest upstream changes. I plan to upload a
backport in the coming days and accordingly push the changes to Salsa in
a new debian/trixie-backports branch.
If you see any issue with that or would like to perform the backport
yourself, please chime in! Per the backport contributors guide [1] it is
nice to have the same maintainer for the backport, although not strictly
required.
Thanks!
Agathe
[1] https://backports.debian.org/Contribute/ ยง Maintainer
--- End Message ---
--- Begin Message ---
Backport was uploaded to trixie: 1.2.16.1-1~bpo13+1
--- End Message ---
