[Bug]: Checksum files for "latest-<version>" archives broken

[Ziris85]

⚠️ This issue respects the following points: ⚠️

• This is not a troubleshooting question, general support matter, or webserver/proxy problem, but likely a bug (if unsure, ask the Community Help Forum).
• This issue is not already reported on Github OR solved at the Community Help Forum (I've searched!).
• I'm using a maintained major version of Nextcloud Server and tested against the latest patch level. (Supported major versions and current patch levels).
• I agree to follow Nextcloud's Code of Conduct.
• I've tried my best to provide clear reproduction steps that someone unfamiliar with this bug could use to reproduce it.

Bug description

This is fairly minor, but "bug" is the only category that really fits. Also didn't find a more appropriate GH repo to file this against, so please redirect me if I missed something!

The checksum files include a non-existent "metadata" file in them. E.g.:

$ cat latest-34.tar.bz2.sha256 
d7ed36ac0e14a2d9bbd167d6f6d4fc498f0f39fcccdf304e67e35bfc42e4506d  latest-34.tar.bz2
3c7f8721a149e48c6535257c6ebebcc0075d7c429922450b50a2016613a0a77f  latest-34.metadata

$ cat latest-34.tar.bz2.sha512
3463dbbdeae5275a0791b115cf86aed41c5a138fdd19bb32ec12837a6698106b6f172e24fb1264a2d4e20b2b805bcf7841b2338e4e02f1fd5394fbed830cc695  latest-34.tar.bz2
f8c40685886beff04a9dd4fa92a9a3d0cbf1fe3bb77bbb7904f410ba6eae6992c5b1982681661b6c53f262e054d9da85d27ad4f86548e6f3ae6241673cef25c9  latest-34.metadata

$ curl -L https://download.nextcloud.com/server/releases/latest-34.metadata
File not found.

The minor-versioned releases as of v30.0.0 do appear to exist in the archives (e.g. https://download.nextcloud.com/server/releases/nextcloud-30.0.0.metadata), so perhaps the latest-<version>.metadata exist somewhere and just aren't being uploaded yet?

Steps to reproduce

1.Download checksum: curl -LO https://download.nextcloud.com/server/releases/latest-34.tar.bz2.sha256
2.Download archive: curl -LO https://download.nextcloud.com/server/releases/latest-34.tar.bz2
3. (Fail to) Download metadata: curl -LO curl -LO https://download.nextcloud.com/server/releases/latest-34.metadata
4. Checksum validation partial-fail:

$ sha256sum -c latest-34.tar.bz2.sha256 
latest-34.tar.bz2: OK
sha256sum: latest-34.metadata: No such file or directory
latest-34.metadata: FAILED open or read
sha256sum: WARNING: 1 listed file could not be read

Expected behavior

metadata file in archive exists for latest-<version> options.

Nextcloud Server version

34

Operating system

Debian/Ubuntu

PHP engine version

No response

Web server

No response

Database engine version

No response

Is this bug present after an update or on a fresh install?

No response

Are you using the Nextcloud Server Encryption module?

No response

What user-backends are you using?

• Default user-backend (database)
• LDAP/ Active Directory
• SSO - SAML
• Other

Configuration report

N/A

List of activated Apps

N/A

Nextcloud Signing status

N/A

Nextcloud Logs

N/A

Additional info

No response

[joshtrichards]

The versioned file bundle has it:

https://download.nextcloud.com/server/releases/nextcloud-34.0.3.tar.bz2
https://download.nextcloud.com/server/releases/nextcloud-34.0.3.metadata
https://download.nextcloud.com/server/releases/nextcloud-34.0.3.tar.bz2.sha256
https://download.nextcloud.com/server/releases/nextcloud-34.0.3.tar.bz2.sha512

I'm not sure offhand why the convenience link doesn't include it.

[Ziris85]

Indeed - if I download that metadata file and name it "latest-34.metadata" then it passes the checksum check. I assumed as well that the "latest-" options were, under the hood, just symlinks/convenience links. So hopefully this can just be a quick and easy archive structure tweak.