Le dimanche 9 novembre 2025, 10:40:32 heure normale d’Europe centrale Sami
Erjomaa a écrit :
> On Sun, 9 Nov 2025 at 11:22, Aurélien COUDERC <[email protected]> wrote:
>
> > Hi,
> >
> > Le 9 novembre 2025 09:59:16 GMT+01:00, Sami Erjomaa <
> > [email protected]> a écrit :
> > >On Sun, 9 Nov 2025 at 10:21, Aurélien COUDERC <[email protected]> wrote:
> >
> > >Hi,
> > >
> > >Wouldn't this force a rebuild of all the packages that depend on the
> > >plasma-version-base-${plasma-version:major}.${plasma-version:minor} every
> > >time when the version changes?
> >
> > And how would would you expect packages not to be rebuilt when there's a
> > new upstream version ?
>
>
> I've understood that not all packages get a new upstream version on each
> release. So there could be a case where some packages remain in for example
> version 6.5 when 6.6 is released.
Ah OK.
So no that never happens :
- upstream always releases everything for every point release X.Y.Z,
- we generally upload all packages in Debian following upstream releases but we
may skip some of the patch releases when we’re close to a Debian release (for
ex trixie has mix of 6.3.[456]),
- But we never want users to mix 6.x with 6.y packages, that’s the whole point.
> >Could this same or at least similar result be reached with stricter
> > >dependencies in the packages?
> > >Example: currently plasma-workspace has dependency kwin-wayland (>=
> > >4:6.2.90~). What if this and all the similar dependencies are updated to
> > >something like kwin-wayland (>=
> > >4:${plasma-version:major}.${plasma-version:minor}~). Wouldn't that prevent
> > >installing plasma-workspace in testing before kwin-wayland has also
> > >migrated?
> >
> > Yes it would.
> > But I'm not willing neither to identify these relationship manually that
> > are already not explicit in the upstream build system, and even less to
> > manage their maintenancd for every new release.
> >
>
> I wouldn't do that manually either. I thought that the same script could be
> used to automate the dependencies.
Yes but the main issue is ensuring we have all the correct relations.
If you miss one it will bite you at some point.
So since upstream doesn’t support mixing 6.x and 6.y with each other anyway we
may as well impose all packages being from the same 6.x main release as my
proposal does.
Anyway, thanks for the feedback.
Happy hacking,
--
Aurélien
