On zaterdag 9 juli 2016 14:45:34 CEST Martin Steigerwald wrote:
> Am Samstag, 9. Juli 2016, 12:25:14 CEST schrieb Andrej Kacian:
> > On Sat, 09 Jul 2016 12:00:20 +0200
> > 
> > Martin Steigerwald <mar...@lichtvoll.de> wrote:
> > > Diederik, I think this is about "I want an always stable and releaseable
> > > testing" again.
> > 
> > I disagree. This is more about knowing if the package combination
> > I am currently running is worth testing and reporting found bugs on, or
> > whether I am in some temporary state where some packages I should
> > have are still waiting in the queue, and any bug report I make would
> > only waste time of the packagers, or whoever else will be reviewing it.
> 
> Or do you think Debian/Kubuntu Qt/KDE packagers always know which versions
> of  which packages go together nicely or not? These effects of mixed KDE
> Frameworks packages between 5.22 and 5.23 have been unknown to them as
> well.

The part I have quoted above is the exact reason I'm participating in this 
thread. 
I do not care about people who think testing is a rolling release, whatever 
that is, or 'stable' with more recent packages. Those people should just read 
the links about testing you provided earlier and adjust their expectations 
accordingly.

But that is not the (main) idea I got about the participants of this thread.
I noticed various bug reports where the cause was the same and the solution as 
well, namely making sure that various framework packages are at the same 
version. And as you said, I also didn't know that mixture of framework package 
versions could cause issues. 
Today I learned on IRC that with upstream KDE it has been known from the start 
that the framework packages should be released together.
As a consequence, and also from the various bug reports and this thread, I 
think there should be (some) versioned dependency between the various 
framework packages.
Even though it won't matter for the Stretch release as they will be all the 
same versions, I do think it would be an improvement of the Debian packages in 
general and that's why I'm (mostly) interested in this issue.

As I'm quite sure that various Debian Qt/KDE maintainers follow this list as 
well, I think the relevant info will land with them and if needed will be 
acted upon.

Cheers,
  Diederik

Attachment: signature.asc
Description: This is a digitally signed message part.

Reply via email to