Bug#1057431: fakeupstream.cgi: add support for static.rust-lang.org
Hi Zixing,
The newest stable upstream release is advertised in more than one way allowing
to write regular debian/watch files. Here below I give two working examples.
| version=4
| https://forge.rust-lang.org/infra/other-installation-methods.html#source-code \
| https://static.rust-lang.org/dist/rustc-(\d+(?:\.\d+)*)-src\.tar\.gz
|
| $ uscan --safe --package rustc --upstream-version 1.70.0+dfsg1 --watchfile watch1
| Newest version of rustc on remote site is 1.74.1, local version is 1.70.0+dfsg1
| => Newer package available from:
| => https://static.rust-lang.org/dist/rustc-1.74.1-src.tar.gz
|
| version=4
| https://github.com/rust-lang/rust/tags \
| .*/rust-lang/rust/archive/refs/tags/(\d+(?:\.\d+)*)\.tar\.gz
|
| Newest version of rustc on remote site is 1.74.1, local version is 1.70.0+dfsg1
| => Newer package available from:
| => https://github.com/rust-lang/rust/archive/refs/tags/1.74.1.tar.gz
And the watch file currently in Debian works fine. The version on the package
tracker is correct. https://tracker.debian.org/pkg/rustc
| A new upstream version is available: 1.74.1 high
| A new upstream version 1.74.1 is available, you should consider packaging it.
Fakeupstream is for when the above would be impossible.
In my understanding of the described special use cases, they can be covered
separately. For example, some scraping script can collect the info 4x/day and
produce a html page suitable for debian/watch. The loops in your patch fit
better in such script than in a cgi script.
Or maybe upstream is willing to put the info you need on their website. Have
you asked them?
Cheers,
Bart
On Tue, Dec 12, 2023 at 03:06:53PM -0700, Zixing Liu wrote:
> Yes, while that is true, the page is updated frequently with older
> versions replaced with the new version.
> In Debian, usually, we can't package the latest version as quickly as
> possible due to bootstrapping requirements.
> Hence, a fakeupstream service is needed to retrieve a non-latest
> version from the upstream.
>
> Also, another use-case might be, you want a specific nightly or beta
> to test a certain regression. Since that page
> does not list the previous releases, it would be difficult to rely on
> it to retrieve a previous beta using uscan by
> specifying `--download-version`.
Reply to: