On 03/09/15 12:49 PM, Andrey Rahmatullin wrote:
On Thu, Sep 03, 2015 at 06:30:13PM +0200, Matthias Bodenbinder wrote:
Am 03.09.2015 um 18:12 schrieb Martin Steigerwald:
Packages from Debian Unstable enter the next-stable testing distribution
automatically, when a list of requirements is fulfilled: [...] The package
does not introduce new release critical bugs.
So and now *who* reports these?
Then rethink from there.
Well, I would expect a minimum of testing from the package maintainers even
before a package is uploaded to unstable. I assume for the case at hand that
the package maintainers were pretty much aware about the broken KDE desktop.
The maintainers are well aware that packages may behave badly during
large transitions and that shouldn't stop them from uploading, as it's the
only way forward.
Sorry, but before releasing a major package to "testing", shouldn't it
be tested against the "testing" environment? If a package requires other
packages from sid to run properly, isn't that a mistake in the
dependencies list that would be caught by installing the package on
"testing" from sid?
I know that large tangled transitions can be messy but when faced with
one, doesn't it make sense to do a little extra testing before letting
it out? There are a lot of KDE users out there, so this isn't some
obscure package that affects only a couple of people.