Re: KDE/Plasma 6.5.0 upgrade experiences

Hefee <[email protected]> Sun, 09 Nov 2025 14:34:19 +0100

Newsgroups	gmane.linux.debian.user.kde
Message-ID	<4175714.MHq7AAxBmi@tuxin>

Hey,

> 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.

Mixing is not allowed by upstream, so what packages do you use from older 
plasma versions? Normally if a 6.5 package remain it means upstream archived 
those, so we won't ship a new version and the old version remain in the 
archive. With the plasma-version-base solution by coucouf it would detect 
those packages and we can find solutions, if we on Debian doesn't want to 
follow those removals. Currently it is hard to even find those packages.

> > 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.

The automate dependency script need to be run by the maintainer on their 
computer. If the maintainer forgets to run it, that dependencies are not 
updated. The dh-sequence-plasma is called with every build, so this dependency 
is always updated.

signature.asc (application/pgp-signature, 833 B)