On Sat, Mar 19, 2016 at 12:47:12AM -0400, Peter Colberg wrote: > On Sat, Mar 19, 2016 at 03:28:16PM +1100, Dmitry Smirnov wrote: > > I've uploaded with only one correction: I've added "watch" file to check > > for > > upstream releases. Apparently there is one new tag/release made 10 days ago. > > > > Tagged version is quite different from yours -- please check with upstream > > if > > necessary. I've also reported the following bug: > > > > https://github.com/cheggaaa/pb/issues/73 > > Thank you for the upload! > > The tag in question is 'go1.0', which points to commit e8c7cc5 from > Dec 2, 2014. This does not look like a proper release tag, rather > an internal tag for an old commit that works with Go version 1.0.
Now this stray tag shows up in uscan: uscan: Newest version of golang-github-cheggaaa-pb on remote site is 1.0, local version is 0.0~git20160304.0.a75ad33 uscan: => Newer package available from https://github.com/cheggaaa/pb/archive/go1.0.tar.gz Could you revert Debian commit 5699dec to restore the empty watch file and upload a second version? Otherwise the above tag would permanently show on tracker.debian.org, despite the package being up to date. Regards, Peter