Opened 8 years ago
Closed 8 years ago
#15885 closed enhancement (worksforme)
HTML version page
| Reported by: | sebastic | Owned by: | stoecker |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Trac | Version: | |
| Keywords: | Cc: | sebastic |
Description (last modified by )
The josm Debian package uses uscan(1) to check for new tested snapshots, it does this by requesting a URL and parsing the <a href> elements in the HTML and checks for the available versions.
There is no JOSM download page which includes the SVN revision for tested & latest in the download link, so a simple PHP script (josmredir.php) is currently used to download https://josm.openstreetmap.de/version and generate a simple HTML page with links including the SVN revision.
The Alioth server where the josmredir.php is currently hosted will be shutdown in the near future, and Debian doesn't provide webservers with PHP or CGI to its developers which could be used instead of Alioth.
Would it be possible to host an HTML variant of the version page which provides similar functionality?
Output like the following would be sufficient:
<!DOCTYPE html> <html> <head> <title>JOSM Versions</title> <meta http-equiv="Content-Type" content="text/html;charset=utf-8" /> </head> <body> <h1>JOSM Versions</h1> <ul> <li><a href="https://josm.openstreetmap.de/josm-tested.jar?rev=13367">josm-tested.jar: 13367</a></li> <li><a href="https://josm.openstreetmap.de/josm-latest.jar?rev=13385">josm-latest.jar: 13385</a></li> <li><a href="https://josm.openstreetmap.de/download/windows/josm-setup.exe?rev=13367">josm-setup.exe: 13367</a></li> <li><a href="https://josm.openstreetmap.de/download/macosx/josm-macosx.zip?rev=13367">josm-macosx.zip: 13367</a></li> </ul> </body> </html>
Attachments (0)
Change History (10)
comment:1 by , 8 years ago
follow-up: 3 comment:2 by , 8 years ago
Wouldn't a text version including the link be enough?
Unfortunately not, uscan only supports <a href> elements and ignores everything else.
comment:3 by , 8 years ago
Replying to sebastic:
Wouldn't a text version including the link be enough?
Unfortunately not, uscan only supports
<a href>elements and ignores everything else.
Hmm. Would it be an option to ask uscan to update their functionality?
I don't like the proposed format at all, as in 1-2 years somebody will ask why "https://josm.openstreetmap.de/josm-tested.jar?rev=13367" with an older revision still delivers the newest one and it will take a lot of time to find out why we actually create such strange links.
comment:4 by , 8 years ago
I could expand the list at DevelopersGuide/Schedule with links to the tested versions. Would that help?
But this means the filename will no longer be josm-tested.jar, but like josm-snapshot-13367.jar
follow-up: 6 comment:5 by , 8 years ago
Hmm. Would it be an option to ask uscan to update their functionality?
Not really, uscan already expects that the link is to the source tarball, and in the josm package we only use it for the SVN revision since the source is only available in SVN and needs some work to combine various sources (josm, i18n & translations from Launchpad).
The link parameter not reflecting the version that will be downloaded is indeed broken by design.
I could expand the list at DevelopersGuide/Schedule with links to the tested versions. Would that help?
The schedule is already a pretty good alternative as-is. IIRC it's manually updated unlike the version file, so there is the risk of missing releases because the list was not updated.
comment:6 by , 8 years ago
Replying to anonym:
I could expand the list at DevelopersGuide/Schedule with links to the tested versions. Would that help?
The schedule is already a pretty good alternative as-is. IIRC it's manually updated unlike the version file, so there is the risk of missing releases because the list was not updated.
Why do you think it is manually updated? We do nothing manually which can be automated properly.
follow-up: 8 comment:7 by , 8 years ago
Why do you think it is manually updated? We do nothing manually which can be automated properly.
I thought I remembered something like that. If the ReleaseLog is updated along with the version file, I think we can leave things as-is, and I'll update the debian/watch file to use the Schedule page to get the SVN revision of the most recent tested snapshot.
comment:8 by , 8 years ago
Replying to sebastic:
Why do you think it is manually updated? We do nothing manually which can be automated properly.
I thought I remembered something like that.
In the past we manually assigned the status "Free to modify" or "Stabilization" and added the planned date of the next release. See e.g. https://josm.openstreetmap.de/wiki/DevelopersGuide/Schedule?version=137
However this was then not really maintained so I changed this with https://josm.openstreetmap.de/wiki/DevelopersGuide/Schedule?sfp_email=&sfph_mail=&action=diff&version=139&old_version=138&sfp_email=&sfph_mail=
The table with the past releases is automatic since 7 years https://josm.openstreetmap.de/wiki/DevelopersGuide/Schedule?version=3
comment:9 by , 8 years ago
| Description: | modified (diff) |
|---|
comment:10 by , 8 years ago
| Resolution: | → worksforme |
|---|---|
| Status: | new → closed |
I've updated the josm package to use the Schedule wiki to check for new tested snapshots.
Possible: Yes. But parsing a HTML version sounds strange to me when the HTML than is thrown away. Wouldn't a text version including the link be enough?
Like