Hi,

I was using pages such as:
  http://qa.debian.org/developer.php?login=pkg-ime-de...@lists.alioth.debian.org
to track the upstream version of my Debian packages.  The upstrean
version comes from uscan i.e. tarball.

Recent a friendly "FTBFS on amd64" bug report gave me a wake up call.
  https://bugs.debian.org/746136

I realized that I overlooked the upstream ML message.
| ibus 1.5.6 is released:
| https://github.com/ibus/ibus/releases/tag/1.5.6
| ...

Yes, this release is done by the git tag.  There is no public pointer
to the tarball.  Their previous tarball place does not have the new
tarball.

Since this package is maintained by Red Hat folks, I could find it wrapped in 
either
src.rpm or by itself on http://arm.koji.fedoraproject.org site.

 URL is found as follows:
 http://arm.koji.fedoraproject.org/koji/buildinfo?buildID=191821 page (stable)
  link to 
http://arm.koji.fedoraproject.org//packages/ibus/1.5.6/3.fc21/src/ibus-1.5.6-3.fc21.src.rpm
 http://arm.koji.fedoraproject.org/koji/rpminfo?rpmID=1046360 page (linked from 
stable page)
  link to 
http://arm.koji.fedoraproject.org/koji/fileinfo?rpmID=1046360&filename=ibus-1.5.6.tar.gz

Is there any easy way to set up uscan for this kind of situation?

Please note buildID is stable for the upstream tar package but rpmID
changes with each src.rpm release.

Regards,

Osamu


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140427145048.GB15890@goofy

Reply via email to