On 24/08/2017 16:44, Lisandro Damián Nicanor Pérez Meyer wrote:
The sole fact that you wrote this make it clear that you don't understand how
transitions works and what they are for. Stuff was available in experimental
but KDE stuff didn't actually needed to be compiled against experimental's Qt.
But some kde package were obviously because upgrading qt5.9.1 in
experimental was pulling only kde 5.28 stuff while unstable did not have
it due to dependencies while other did not recompile making kde in
experimental rather broken for months...
And let's not forget that in the meantime we ended preparing the packages in
experimental and got the slot for the transition both gcc and cmake changed
bringing up new bugs.
Granted.
So please Eric, try to avoid this comments, you are both misleading users and
showing that you really don't understand what's going on.
As a end user (but with years and years of debian useage (>20)), I think
I'm still entitled to tell you :
1) Potentially breaking one of the main graphical interfaces for weeks
via a dist-upgrade is painful especially when default installed kde
package manager actual settings do a dist-upgrade equivalent that
removes most kde stuff. BTW I'm not impacted but my list of hold
package keeps growing. Ok we are few months after a stable release so
that's less important because less user need unstable...
2) kde environment as a whole being maybe the most demanding qt test
bench applications, it may had been useful to check hat kde is running
fine *before* transitioning : reading FTBS bug opened, it appears that
some essential kde package indeed have never been compiled with qt 5.9.1
(and current cmake but that's another story as it was done in //).
Seamlessly, kde 5.37 is currently landing in experimental but is also
currently uninstallable for the very same root reason.
Again, wrong. 5.37 stuff is in hold there due to various packages being in the
NEW queue waiting for a FTP master to review them. Once they pass that queue
the maintainer needs to check that everything is OK and then push it to
unstable, as long as something doe snot requires a transition too.
Ok.
Again please refrain to make this comments in the future.
I'm afraid I may continue because you've been too good before with very
smooths transitions because they were tested via experimental by several
people like me before landing unstable...
I do appreciate a lot your work, take this critic as an hint to do even
better next time :-)
-- eric
-- eric
