Op 1/01/2026 om 10:17 schreef Wouter Verhelst:
Op 2025-12-31 17:38, schreef Pieter Lenaerts:
[...]
but also https://wiki.debian.org/DontBreakDebian.
This argument boils down to whether you believe I, a Debian Developer
who's been active in the project for almost 25 years now, will do
things in my private repository that might break your Debian.
I'm not worried about things you do. I'm worried about other people
compromising your private repo intentionally or by accident (which
happened at the trixie release).
[...]
- D. Upstream won't support issues. Not sure if this is really the
case. I may be making this assumption wrongly? And even so,
determining whether an issue is an upstream or a packager issue
should not be too big a concern.
I think you may be misunderstanding here what I wrote in my previous
mail about this.
Great! Thanks for clearing that up!
[...]
+/- F. Debian is moving slowly to update urgent upstream package
releases. I'm not putting this in pro nor in the con category:
F.1 In general, new releases are I believe not very urgent. F2. I
think with backports there is a solution for moving too slowly. On
the one hand F3. adding bpo takes additional effort from the
sysadmin, but on the other hand F4. I feel a lot more comfortable
adding bpo than adding a third party repo.
I think that subjective feeling is perhaps not warranted.
Yes, we could use backports, but then there's more process involved,
and we'd have to teach users to always enable it. That sounds like a
bad idea to me.
Yes, we could also try to do stable updates, but I'm not sure the
stable release managers would feel it's warranted, especially not if
there's only backwards compatible spec changes. I'd have to check with
them though.
I think this point is where we can conclude.
I agree that bpo vs the 3rd party repo through extrepo or the
eid-archive package does not add a lot of value vs the effort.
Stable updates would be "better", but I agree that it would not be the
easiest or fastest of discussions. And it should not be.
So, I agree the current solution is the better approach. I'm closing
this ITP bug and will continue using eid-mw via the third party repository.
Thanks for your time!
Pieter
