Re: Initial uploads of alsa-lib and alsa-ucm-conf for trixie-backports
Agathe Porte <[email protected]> Mon, 13 Jul 2026 14:08:44 +0200
| Newsgroups | gmane.linux.debian.backports.general |
|---|---|
| Message-ID | <alTUeh5hskPzOuzv@debian> |
Hello again, 2026-07-11 08:59 CEST, Micha Lenk: > Hi Loïc, > > Am 9. Juli 2026 20:57:40 MESZ schrieb Loic Minier <[email protected]>: > >New ALSA releases often bring new functionality and support for new > >platforms; a backport was requested for alsa-lib here: > >https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029272 > >and Agathe proposed one in that bug, as well as for alsa-ucm-conf there: > >https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1141067 > > > >My employer (Qualcomm) regularly contributes patches to ALSA upstream, > >mainly to support new IoT platforms, some accessories and a few laptops, so > >we're keen to contribute to trixie-backports. :-) > > > >Agathe prepared the first alsa-lib one, that I'll sponsor since she's just > >requested being added to the backports ACL. > > Thank you for your contribution to Debian backports. I've just added Agathe to the backports ACL. > > Best regards, > Micha I do not have rights to push my debian/trixie-backports branch to the alsa-lib repository, so it currently lives in my fork: https://salsa.debian.org/gagath/alsa-lib/-/tree/debian/trixie-backports?ref_type=heads Can you grant me salsa access so I can push this branch with the final changelog from trixie-backports? I will likely encounter the same issue with alsa-ucm-conf. I guess adding me to the ALSA team should do the trick. Thanks! Agathe.