Bug#913970: uscan: git mode: last tag not taken into account

2019-01-12 Thread Mattia Rizzolo
Control: tag -1 + patch - pending Control: severity -1 wishlist On Sun, Nov 18, 2018 at 09:42:30AM +0100, Xavier wrote: > I added a @TAG@ macro for this to avoid regression > (https://salsa.debian.org/debian/devscripts/merge_requests/85) > > Your debian/watch becomes: > > version=4 >

Bug#913970: uscan: git mode: last tag not taken into account

2018-11-18 Thread Xavier
Le 17/11/2018 à 22:20, Mattia Rizzolo a écrit : > On Sat, Nov 17, 2018 at 01:19:38PM -0500, Alexandre Viau wrote: >> For example, if a repository has a v0.3.0 tag and commits were done >> after the tag, the last commit being done on 2018-10-25 and having the >> hash f80706d, the version should

Bug#913970: uscan: git mode: last tag not taken into account

2018-11-18 Thread Xavier
Le 18/11/2018 à 01:23, Alexandre Viau a écrit : > On 2018-11-17 4:20 p.m., Mattia Rizzolo wrote: >> Even if they were discussed there, changing such detail would be a >> breaking change now, so I think it would be hard to do "by default". > > That would be unfortunate as I think this is a much

Bug#913970: uscan: git mode: last tag not taken into account

2018-11-17 Thread Alexandre Viau
On 2018-11-17 4:20 p.m., Mattia Rizzolo wrote: > Even if they were discussed there, changing such detail would be a > breaking change now, so I think it would be hard to do "by default". That would be unfortunate as I think this is a much better default and it was suggested from the start.

Bug#913970: uscan: git mode: last tag not taken into account

2018-11-17 Thread Alexandre Viau
On 2018-11-17 2:07 p.m., Xavier wrote: > I'll take a look. Thanks! > For now, you can use "pretty": > > version=4 > opts="pretty=0.3.0~git%cd.%h,mode=git,pgpmode=none" \ > https://github.com/collectd/go-collectd.git \ > HEAD > Sure, that helps in the meantime. -- Alexandre Viau

Bug#913970: uscan: git mode: last tag not taken into account

2018-11-17 Thread Mattia Rizzolo
On Sat, Nov 17, 2018 at 01:19:38PM -0500, Alexandre Viau wrote: > For example, if a repository has a v0.3.0 tag and commits were done > after the tag, the last commit being done on 2018-10-25 and having the > hash f80706d, the version should be: > - 0.3.0~git20181025.f80706d > > However, uscan

Bug#913970: uscan: git mode: last tag not taken into account

2018-11-17 Thread Xavier
Le 17/11/2018 à 19:19, Alexandre Viau a écrit : > Package: devscripts > Version: 2.18.9 > Severity: normal > > When using uscan's git mode on a repository that has tags, uscan does > not take into account the last tag when constructing the version number. > > For example, if a repository has a

Bug#913970: uscan: git mode: last tag not taken into account

2018-11-17 Thread Alexandre Viau
Package: devscripts Version: 2.18.9 Severity: normal When using uscan's git mode on a repository that has tags, uscan does not take into account the last tag when constructing the version number. For example, if a repository has a v0.3.0 tag and commits were done after the tag, the last commit