Hi,

On 3/9/26 17:38, Sven Geuer wrote:
On Mon, 2026-03-09 at 22:16 +0700, Arnaud Rebillout wrote:
If you mean about creating a forky/testing testbed on a trixie system,
then the change will need to be backported I suppose.

That's exactly what I meant. Not sure whether this is a relevant
scenario at all.


All ci.d.n workers except for loong64 are running stable, so yes a point release fix would be needed to land this properly on infrastructure.

On 3/9/26 12:27, Arnaud Rebillout wrote:
> Or is it missing on trixie/loong64
> (didn't find a way to check, rmadison doesn't tell about loong64)?


loong64 only exists for unstable at this moment.

On 3/9/26 05:44, Arnaud Rebillout wrote:
> @elbrus: I believe the fix doesn't need to apply to trixie, but only
> to forky onward. Please tell me if I'm mistaken.


I don't really care, but Sven wants trixie to default to isc-dhcp-client as it always has, because without that, the test of his package keeps failing on (old)stable.

Paul

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature

Reply via email to