Bug#1101532: systemd: unable to migrate to Testing because of removed packages

[Raphael Hertzog]

Hello,

On Mon, 31 Mar 2025, Luca Boccassi wrote:
> Paul, could you please confirm whether resolved is a key package and
> thus cannot be removed anymore, or isn't and can? Thanks.

We don't care. Nobody wants to see systemd-resolved removed from Debian.

> So, just one simple question: why the **** should I even bother
> anymore?

I can't answer that question for you. But if you are no longer enjoying
working on systemd, then you should consider to step back and let other
co-maintainers handle it for a while at least. That's healthier than this
current fight.

BTW, did you run your decision to remove the package with them or was that
an unilateral decision?

I'm explicitly ccing all the co-maintainers so that they can chime in and
share their sentiments on what happened.

On Mon, 31 Mar 2025, Stefano Rivera wrote:
> Speaking for myself, as a technical committee member, I haven't run any of
> this by the rest of the committee.

I wanted to reply roughly what Stefano said. So I'm not repeating but just
+1 his reply.

The two main points are:
- the patch for mdns only changed the default value of the setting,
  nothing else, and that's just what was asked
- dealing with the regression compared to bookworm can be done with
  release notes and debian/NEWS entries

Cheers,
-- 
  ⢀⣴⠾⠻⢶⣦⠀   Raphaël Hertzog <hertzog at debian.org>
  ⣾⠁⢠⠒⠀⣿⡁
  ⢿⡄⠘⠷⠚⠋    The Debian Handbook: https://debian-handbook.info/get/
  ⠈⠳⣄⠀⠀⠀⠀   Debian Long Term Support: https://deb.li/LTS