On Fri, Aug 26, 2016 at 07:29:59PM +0200, gregor herrmann wrote: > On Thu, 25 Aug 2016 22:35:50 -0400, James McCoy wrote: > > > Getting libdata-messagepack(-stream)-perl updated to work with the new > > msgpack-c are the last two items blocking the msgpack-c transition > > (#815036). > > Jonas has already started work on libdata-messagepack-perl in git; I > hoped he would have the time to finish it and wanted to avoid messing > with the repo.
That was from before upstream made the 0.50 release, which includes support for the new msgpack-c version. Although, I see there's now been a 0.51 release (backing out the format changes) and 1.00 release (re-adding them) to comply with the implementation guidelines to handle upgrades of the MessagePack spec[0]. [0]: https://github.com/msgpack/msgpack-perl/issues/30#issuecomment-228441209 There is a pull request[1] against libdata-messagepack-stream-perl's upstream to integrate support for the new spec, which looks good (to my novice eyes) aside from an (as of yet) unanswered question about an XS API. [1]: https://github.com/typester/Data-MessagePack-Stream/pull/7 > > I had been considering NMUing the packages, but I noticed that they only > > seem to be used by libcatmandu-store-lucy-perl and libtext-xslate-perl > > (which themselves have no rdeps or build-rdeps). Are these packages > > actually needed or can they be removed? > > As Niko said, having the removed from testing is no issue IMO. Ok. Thank you both for following up. I'll give it a few more days for things to settle out in the PR and figure out whether I feel confident enough to do NMUs (if needed). Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
