On Tue, Jun 14, 2016 at 07:43:27PM +0200, Emilio Pozuelo Monfort wrote: > On 25/02/16 02:28, James McCoy wrote: > > On Mon, Feb 22, 2016 at 07:39:44PM +0100, Emilio Pozuelo Monfort wrote: > >> On 21/02/16 16:54, James McCoy wrote: > >>> On Wed, Feb 17, 2016 at 11:46:53PM -0500, James McCoy wrote: > >>>> FTBFS: > >>>> > >>>> * webdis: > >>>> + #811343 filed with patch
No action seen on this. I can try to push this upstream. The package hasn't seen any activity in almost a year (even with an upstream release in the interim). I could NMU this. > >>>> * tmate: > >>>> + New upstream version is needed > >>>> + Will file a bug for this > >>> > >>> Filed #815381. Fixed in experimental. > >>>> * kumofs: > >>>> + configure script expects the C++ library (libmsgpack) and therefore > >>>> fails > >>>> + Trivial patch to remove that expectation leads to a compile failure > >>>> due to mixing code with C and C++ linkage > >>>> + No upstream activity in 5+ years > >>>> + Debian maintainer MIA > >>> > >>> Given the above and a popcon of 5, should an RM bug be filed? > >> > >> Yeah I'd say so. > > > > #815845 filed. This has been removed from the archive. libdata-messagepack-perl has an upstream pre-release which works with the new msgpack-c. I've poked them to see if they're ready to make an official release. There's still been no reaction to my patch against libdata-messagepack-stream-perl upstream. I can poke them again. > How is this progressing? To summarize: + Will NMU webdis with my proposed patch and send it upstream + tmate is fixed in experimental + libdata-messagepack-perl has a fix upstream but no "stable" release including it + libdata-messagepack-stream-perl could be NMUed once libdata-messagepack-perl is available. Also, a new package has appeared in the interim which needs the new msgpack-c. Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
