[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1120848: trixie-pu: package clatd/2.1.0-2+deb13u1



Control: tags -1 - moreinfo

Hi Adam,

On Sat, 06 Dec 2025 16:41:00 +0000 "Adam D. Barratt" <adam@adam-barratt.org.uk> wrote:
> Control: tags -1 + moreinfo
> 
> On Mon, 2025-11-17 at 15:43 +0100, Daniel Gr=C3=B6ber wrote:
> > [ Reason ]
> > clatd is currently completely non-functional in Trixie. A packaging
> > bug I did't get around to in time "systemd units not getting
> > installed" #1101004 made using it a manual affair. Now I've found
> > #1082060 in tayga actually breaks it completely.
> 
> -+	install -D -m0644 scripts/*.service $(SYSTEMD_SYSSERVICEDIR)/
> ++	install -D -m0644 scripts/clatd.systemd $(SYSTEMD_SYSSERVICEDIR)/clatd.s=
> ervice
> ++	#install -D -m0644 scripts/clatd@.systemd $(SYSTEMD_SYSSERVICEDIR)/clatd=
> @.service
> 
> Why is a commented line for a template service added? Surely it should eith=
> er be installed or not mentioned at all?

I was working on this and the unstable branch in parallel and hadn't quite
settled on whether the per-interface daemon would work out so I left it
there as a note for later, well for now I suppose :-).

It turned out I cannot enable this in stable without bringing in another
patch "Read [both] global and interface specific config file"
https://salsa.debian.org/debian/clatd/-/commit/ac1c4e16bdf7553ed89810774cc70c414480a0ec

This one didn't seem suitable for a s-u however so I added it only to
the unstable upload.

To be clear: *Not* installing clatd@.service is intentional.

It is still mentioned in clatd.conf in my p-u which is a bit inconsistent:

> # /etc/clatd/INTERFACE.conf: per-interface settings (clatd@INTERFACE.service)

I would actually mildly prefer leaving it that way to avoid a conffile
prompt on upgrade from Trixie -> Forky.

What do you think?

Thanks,
--Daniel

Attachment: signature.asc
Description: PGP signature


Reply to: