Your message dated Tue, 12 Sep 2017 12:46:00 +0000
with message-id <[email protected]>
and subject line Fixed
has caused the Debian Bug report #875252,
regarding torbirdy: debian/watch looks at a page that has no upstream
tarball/XPI
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
875252: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875252
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: torbirdy
Version: 0.2.2-1
Severity: normal
Hi!
Before commit ff02a45 we were looking in
https://www.torproject.org/dist/torbirdy/, where Torbirdy upstream
release are distributed. And then uscan would repack the XPI into
a tarball for us (I guess :)
That commit made debian/watch look at
https://gitweb.torproject.org/torbirdy.git/refs instead. There was
probably a good reason for it back then (e.g. simplicity!), but
currently that cgit page has no tarball/XPI download option, so since
a while DMD, tracker & friends have been complaining about
debian/watch and worse, they were not able to make it obvious to us
that 0.2.3 wanted to be packaged.
Reverting that commit seems to fix the problem:
$ uscan --no-download
uscan: Newest version of torbirdy on remote site is 0.2.3, local version is
0.2.2
uscan: => Newer package available from
https://www.torproject.org/dist/torbirdy/torbirdy-0.2.3.xpi
But I don't know what other updates in the packaging relied on that
commit, so I won't dare pushing the revert to Vcs-Git.
Cheers!
--- End Message ---
--- Begin Message ---
I fixed this in 0.2.3-1.
--- End Message ---
