Re: debian/watch: Ignoring pre-release on GittHub

2022-12-13 Thread Kentaro Hayashi
Hi, 2022年12月8日(木) 20:40 Andrius Merkys : > > On 2022-12-08 12:59, Kentaro Hayashi wrote: > > 2022年12月5日(月) 16:41 Stephan Lachnit : > >> > >> You can try to take a look at the GitHub API, e.g. [1]. > >> > >> Inside is an `prerelease` entry. Not sure how easy this is to > >> implement in uscan thou

Re: debian/watch: Ignoring pre-release on GittHub

2022-12-08 Thread Andrius Merkys
On 2022-12-08 12:59, Kentaro Hayashi wrote: 2022年12月5日(月) 16:41 Stephan Lachnit : You can try to take a look at the GitHub API, e.g. [1]. Inside is an `prerelease` entry. Not sure how easy this is to implement in uscan though. Cheers, Stephan [1]: https://api.github.com/repos/lutris/lutris/r

Re: debian/watch: Ignoring pre-release on GittHub

2022-12-08 Thread Kentaro Hayashi
2022年12月5日(月) 16:41 Stephan Lachnit : > > You can try to take a look at the GitHub API, e.g. [1]. > > Inside is an `prerelease` entry. Not sure how easy this is to > implement in uscan though. > > Cheers, > Stephan > > [1]: https://api.github.com/repos/lutris/lutris/releases?per_page=100 Thanks, I

Re: debian/watch: Ignoring pre-release on GittHub

2022-12-04 Thread Stephan Lachnit
You can try to take a look at the GitHub API, e.g. [1]. Inside is an `prerelease` entry. Not sure how easy this is to implement in uscan though. Cheers, Stephan [1]: https://api.github.com/repos/lutris/lutris/releases?per_page=100

debian/watch: Ignoring pre-release on GittHub

2022-12-04 Thread Kentaro Hayashi
Hi, Recently, I've faced an issue with debian/watch with pre-released version. Here is the scenario: 1. upstream releases x.y.z with pre-release label. (tagged with x.y.z) 2. new release x.y.z was detected on developer dashboard (https://qa.debian.org/developer.php) 3. upstream releases x.y.z as