On Mon, Mar 17, 2014 at 11:33:28AM +0100, Cyril Brulebois wrote: > Changelog says: > | 14/03/2014 - feature improvement and gui redesign - version 1.2.6 > > but what it doesn't mention is that it breaks sync against stable (1.2.5):
It is written in the Debian changelog and in the NEWS file. It is nowere written that you can combine smd version X with smd version Y when X and Y are different. The upstream (that is me) was an asshole, he did not want to clutter the code with retrocompatibility stuff. The packager (that is me) made a backport to alleviate the pain. > Does the protocol version intentionally changes on every release?! Are > you really forcing a server + client*s* lockstep upgrade? No, only when there is a difference in the protocol. This time there was a difference. So yes, this time I'm forcing a lockstep upgrade (with both the upstream and maintainer hat on). > so adding -backports@ to X-D-Cc since I didn't see a discussion about > a possible exception for this package. No exception was asked for or granted. It just happened that the NEW queue of bpo was processed in less than 5 days, that is what it will hopefully take to smd to migrate to jessie. Yes the maintainer (me of course) was a bad ass and speculated about the timing and did the upload to the bpo queue before smd hit testing. So now, the best thing for all of us, is that you lower the severity of the bug and let smd move to jessie, given that the bpo package is already in place. An apt-get update/install on your machine running stable will fix things. Sorry for the inconvenience. -- Enrico Tassi -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
