El 28/05/17 a las 12:53, Daurnimator escribió:
> On 28 May 2017 at 01:38, Santiago Ruano Rincón <santiag...@riseup.net> wrote:
> > In case you want to test it, I've uploaded a patched version to my
> > personal repo:
> > https://people.debian.org/~santiago/debian/santiago-unstable/
> 
> 
> If patching the upstream, please update the version in
> http/version.lua to something like version="0.1.debian-1"
> 
> However I'm hoping to make a 0.2 release today that includes the fix
> (as well as others that weren't reported to debian directly): please
> consider packaging that instead.

Thanks for the heads-up.  

Since Debian testing is currently frozen (and Stretch will be released
next month), only specific changes to solve release-critical bugs are
allowed to propagate from unstable to testing.
So, to have this bug fixed in the next stable release, it is needed to
patch the current version.

Why updating http/version.lua is needed?

Cheers,

Santiago

P.S.1 The 0.2 release could enter into unstable after Stretch release.

P.S.2 I am not the maintainer. Ondřej, do you agree with the changes? Do
you want to apply them by yourself? I'd happy to upload if it's OK to
you.

Attachment: signature.asc
Description: PGP signature

Reply via email to