Release Engineering

Tasklist

FS#67203 - [torrent] Missing .sig file

Attached to Project: Release Engineering
Opened by mpan (mpan) - Sunday, 05 July 2020, 22:11 GMT
Last edited by David Runge (dvzrv) - Friday, 18 February 2022, 18:20 GMT
Task Type Feature Request
Category ArchISO
Status Closed
Assigned To Pierre Schmitz (Pierre)
Jelle van der Waa (jelly)
David Runge (dvzrv)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Since June the torrent download page⁽¹⁾⁽²⁾ includes a PGP key ID. However, the key is useless because a .sig file is not present. To obtain it the user has to go to the download section⁽³⁾, which makes that information pretty useless.

Three options are available:
1. Add a link to the .sig file in the torrent/release page itself.
2. Remove the PGP key ID, which is confusing without the .sig file.
3. Include the .sig file in the torrent itself.

The 3rd option would be ideal, but it comes with serious caveats. A torrent allows either one file or one directory with files. To have the .sig file, both ISO and the .sig file would have to be packed into a directory. That would require rearranging directory structure on the webseed mirrors. Such a change would also break many automated scripts users may be using, not to mention the general dislike for the change in layout.

Therefore, perhaps, option #1 is the best.

____
⁽¹⁾ https://www.archlinux.org/releng/releases/2020.06.01/
⁽²⁾ https://www.archlinux.org/releng/releases/2020.07.01/
⁽³⁾ https://www.archlinux.org/download/
This task depends upon

Closed by  David Runge (dvzrv)
Friday, 18 February 2022, 18:20 GMT
Reason for closing:  Deferred
Additional comments about closing:  Closing in favor of https://gitlab.archlinux.org/archlinux/r eleng/-/issues/5
Comment by mpan (mpan) - Sunday, 05 July 2020, 22:13 GMT
Uhh, sorry for the title. Forgot to edit it. Should be: [torrent] Missing .sig file.
Comment by Eli Schwartz (eschwartz) - Sunday, 05 July 2020, 22:43 GMT
So is this an archweb bug, then?
Comment by mpan (mpan) - Sunday, 05 July 2020, 22:54 GMT
Depends on the solution chosen. #3 is release engineering, as far as I understand the purpose of that project.
Comment by David Runge (dvzrv) - Friday, 09 July 2021, 08:11 GMT
This is now tracked in releng#5 [1] and will be implemented in release promotion tooling that is currently being created for the releng and arch-boxes release artifacts.

[1] https://gitlab.archlinux.org/archlinux/releng/-/issues/5

Loading...