Bug#771790: Fixed with 1.0.0

Hi, and sorry for the late reply. 1) OK 2) I use it on both stable, testing and unstable, but I'm OK with not having this available in testing or stable: in fact I think it is better not to have the buggy version available at all than to have it and then suffer potential data loss. 3) As you can

Bug#771790: Fixed with 1.0.0

OK, so talking to pabs@ on debian-mentors, seems like a good approach to take here is to do NMU uploads to unstable and stable. I'm happy to do the work there (short of uploading, since I can't). Second part: Marcos, do you use this package on stable, testing or unstable? Also note that dirty.js

Bug#771790: Fixed with 1.0.0

Thanks for pointing that out! But it hasn't been git-tagged, it failed the build on Travis, and it's only a couple of commits from 1.0.0 so it might make more sense to just go with 1.0.0. On Mon, May 15, 2017 at 11:34 AM, Marcos Marado wrote: > Hi, > > The latest

Bug#771790: Fixed with 1.0.0

Hi, The latest upstream version is 1.1.0, which is a bug fix release. Check here: https://github.com/felixge/node-dirty/commit/6285fce15d3bc76bc288259ed2a095cd2936e218 On Mon, May 15, 2017 at 7:03 PM Val Markovic wrote: > I have packaged up latest upstream version (1.0.0)

Bug#771790: Fixed with 1.0.0

I have packaged up latest upstream version (1.0.0) here: https://github.com/Valloric/dirty.js I've tested it out locally (using upstream's tutorial) on latest stretch RC with nodejs v4.8.2 and it's working fine. I'll look for a sponsor on debian-mentors to do a NMU.