On Mon, Feb 13, 2017 at 01:32:55PM -0800, Vagrant Cascadian wrote: > The other obvious option is to not ship a version in stretch and rely on > stretch-backports, if diffoscope development hasn't yet settled down > enough (will it ever) for a Debian stable release cycle...
THAT'S NOT POSSIBLE. backports master have *always* be against such method. If you upload something to backports you're committing to ship that in the next stable release. (capitalized, as it happens too often that somebody wants to do it, and then it causes a lot of noise in debian-backports (either IRC or ML), everybody gets more annoyed, etc.) > How does trydiffoscope fit into the picture? Is it sufficiently isolated > that the heavy lifting offloaded to a network service is more > maintainable for a stable release? It's a difference source package, with a difference schedule, etc. How does it fit in this topic? :) -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
Description: PGP signature
_______________________________________________ Reproducible-builds mailing list Reproducibleemail@example.com http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds