Re: d/s/support: Explicit info about backports and supported Debian releases

[Rene Engelhard <rene@debian.org>]

Hi,

Am 23.01.26 um 14:58 schrieb Gioele Barabucci:
> Example of a simple `d/s/support` file that I would use for my own packages:
>
> ```
> debian/stable
> debian/unstable
> ```
This doesn't make sense.

Assume I put debian/stable into it. Because I only care about backports to the last stable.

Now  that one becomes stable itself. Does it need to be changed to debian/oldstable? keep it? Thus claiming to suport only itself which is wrong?

(e.g. I *do* backport trixie to bookworm-backports if needed, like on security updates or stable updates)

And how to update it? A p-u upload?


> #### Example 2. "The package targets stable and oldstable; oldoldstable is also targeted, but by another developer."
>
> ```
> debian/oldoldstable anotherdev@example.org
> debian/oldstable
> debian/stable
> debian/unstable
> ```
oldoldstable is by definition another developer. Even for oldstable... As long as stuff is in (old)stable and supported official, OK.

If that one is given to LTS one needs *another* upload to update this field to the LTS people?

> ## Open questions:
I think the most open question is why you want to add another field which will quickly get out of date, only fixable by (o-)o-p-u and put more burden on maintainers for (almost) no gain.,


Regards,


Rene