Debian's /tmpest in a teapot

Posted Jun 4, 2024 18:43 UTC (Tue) by pizza (subscriber, #46)
In reply to: Debian's /tmpest in a teapot by mb
Parent article: Debian's /tmpest in a teapot

> Well, but you should. You are changing the Debian world here.

No, he (nor the other systemd developers) is doing nothing of the sort. *DEBIAN* is changing its own world.

Debian's /tmpest in a teapot

Posted Jun 4, 2024 19:28 UTC (Tue) by mb (subscriber, #50428) [Link] (5 responses)

Please grep the Debian systemd package changelogs for "bluca".

Debian's /tmpest in a teapot

Posted Jun 4, 2024 20:46 UTC (Tue) by pizza (subscriber, #46) [Link] (4 responses)

> Please grep the Debian systemd package changelogs for "bluca".

Sounds like you need to file a release blocker bug with Debian, but since this is fundamentally about overruling a Debian packager's decision, you'll probably need to escalate this to the TC or to a full project-wide vote.

Either way, you'll need a better technical argument than "I don't like it and I can't be arsed to make a one-liner configuration change"

Debian's /tmpest in a teapot

Posted Jun 4, 2024 20:50 UTC (Tue) by bluca (subscriber, #118303) [Link]

It's even sillier than that, given it's only enabled for new installs, not on upgrades: "I don't like it and I can't be arsed to make a one-liner configuration change if I ever were to reinstall from scratch"

Debian's /tmpest in a teapot

Posted Jun 4, 2024 21:25 UTC (Tue) by mb (subscriber, #50428) [Link] (2 responses)

> Either way, you'll need a better technical argument

Yes. Changes don't require technical argument. "Only one reason is needed: I have decided as such." (bluca). And the users require technical argument against it. I got it and I will respect it.

I will certainly remember that rule.

Debian's /tmpest in a teapot

Posted Jun 4, 2024 21:57 UTC (Tue) by pizza (subscriber, #46) [Link] (1 responses)

> Changes don't require technical argument.

Except for the numerous times the technical merit of the "new" default has been explained, even in this thread. And then there's also the little detail where where the rest of the Linux world has been doing it this "new" way for about a decade. Those discussions (including technical arguments) are all part of their public record.

> "Only one reason is needed: I have decided as such."

Hate to break this to you, but the overwhelming majority of Debian packages also fall under this category - Both the packager and the upstream authors make countless such decisions every single day.

And again, if you (or whomever) doesn't like these decisions, feel free to invoke the Debian process for overruling a packager and/or upstream.

Second request

Posted Jun 4, 2024 21:59 UTC (Tue) by corbet (editor, #1) [Link]

I repeat: this has all been said, no more minds will be changed (if any ever were). I think we can stop this back-and-forth now.