On Sat, Oct 22, 2016 at 05:35:45PM +0200, jcfp wrote: > > jQuery 3.x is backwards compatible with 1.x, so there should be no > > reason for that restriction on the part of sabnzbdplus. > > Actually, the very reason for the versioning of that dependency is that > jquery releases aren't backwards compatible [1]. In this specific case, > breaking changes in jquery 3 cause issues with libjs-bootstrap [2], used > by sabnzbdplus. As such, the dependency is correct. > > Bootstrap devs added an explicit check for and refused to run with the > incompatible jquery version [3] until compatibility was restored in > 3.3.7. That version was released only after the latest sabnzbdplus > upload and more importantly still isn't available in debian.
Fair enough. I just uploaded bootstrap 3.3.7 as well, then. > I strongly suggest shaping future major versions bumps of jquery more > along the lines of a transition instead of dumping problems on rdepends > like this. These jquery issues aren't new or unexpected, the obvious > attention upstream pays to minimizing the damage notwithstanding. I agree in principle, but unfortunately we do not have a sane way to do that yet. With native libraries at least the rebuilds can tell us whether rdeps at completely broken or not, but with Javascript one would have to either test all the rdeps, or wait for all of their maintainers to say "thumbs up"; both approaches will clearly not work. > Bug #680282 [4] in its core already signalled the very same problem > over four years ago. Saying Someone™ should maintain multiple co-installable versions of libraries is easy, what's hard is actually doing the work.
signature.asc
Description: PGP signature
