Re: Backporting uacme 1.8.0 to trixie
Micha Lenk <[email protected]> Mon, 06 Apr 2026 10:39:08 +0200
| Newsgroups | gmane.linux.debian.backports.general |
|---|---|
| Message-ID | <[email protected]> |
------IB1MLQZWBXM168USE1ACNB35II46SL Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi Andrea, Andrea Pappacoda <tachi@debian=2Eorg> hat am 05=2E04=2E2026 21:01 CEST ges= chrieben: > [=2E=2E=2E] I have both uploaded the new version to unstable and backpor= ted=20 > the testing version to trixie=2E Thanks for your upload to trixie-backports=2E I've just ACCEPTED it from t= he BACKPORTS-NEW queue=2E Please note that the "d/control: undo forky only changes" (i=2Ee=2E undoin= g the Debian policy update and drop of the Priority field) wouldn't have been necessary=2E These are changes that do no harm in trixie and can stay=2E However, this is only FYI=2E There is no further action required on the backport=2E Regards, Micha ------IB1MLQZWBXM168USE1ACNB35II46SL Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable <!DOCTYPE html><html><body><div dir=3D"auto">Hi Andrea,<br><br>Andrea Pappa= coda <tachi@debian=2Eorg> hat am 05=2E04=2E2026 21:01 CEST geschriebe= n:<br>> [=2E=2E=2E] I have both uploaded the new version to unstable and= backported <br>> the testing version to trixie=2E<br><br>Thanks for you= r upload to trixie-backports=2E I've just ACCEPTED it from the<br>BACKPORTS= -NEW queue=2E<br><br>Please note that the "d/control: undo forky only chang= es" (i=2Ee=2E undoing the<br>Debian policy update and drop of the Priority = field) wouldn't have been<br>necessary=2E These are changes that do no harm= in trixie and can stay=2E<br><br>However, this is only FYI=2E There is no = further action required on the<br>backport=2E<br><br>Regards,<br>Micha</div= ></body></html> ------IB1MLQZWBXM168USE1ACNB35II46SL--