Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#73850 - [discord] wrong sha256sum

Attached to Project: Community Packages
Opened by ozraru (ozraru) - Friday, 18 February 2022, 05:46 GMT
Last edited by T.J. Townsend (blakkheim) - Thursday, 01 June 2023, 19:32 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To morganamilo (morganamilo)
Filipe Laíns (FFY00)
T.J. Townsend (blakkheim)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

discord package failing to build
because sha256sum of LICENSE.html and OSS-LICENSES.html is unstatic.

additionally, domain is old (discordapp.com -> discord.com)

Additional info:
discord 0.0.17-1
https://archlinux.org/packages/community/x86_64/discord/
https://github.com/archlinux/svntogit-community/commit/e200f75f32a0c34daceef8ead2815cd7419e4a31
   diffs.log (5.7 KiB)
This task depends upon

Closed by  T.J. Townsend (blakkheim)
Thursday, 01 June 2023, 19:32 GMT
Reason for closing:  Upstream
Comment by morganamilo (morganamilo) - Saturday, 19 February 2022, 23:17 GMT
Yeah with discord not providing a static url there's not much that can be done. I've updated it a few times and it changes again. Doesn't effect the build package so I don't partially care.
Comment by Jared Johnstone (ipaq) - Friday, 28 April 2023, 01:07 GMT
Appears to have happened again though given there is already a build available for 0.0.27(-1).

Is there a way to fetch those without worrying about their sha256sum? It's not like they play a role in verifying the tar.gz contents.

The two source pages https://discord.com/terms & https://discord.com/licenses are very long, dynamically generated HTML pages which are highly likely to flip bits as new dependencies are added and terms are updated.
Comment by T.J. Townsend (blakkheim) - Wednesday, 10 May 2023, 13:29 GMT
It's possible to change the checksums to 'SKIP' in the PKGBUILD, but a better long-term solution would be to file an upstream support request to include the relevant files in the distributed tarball. Have you tried that?
Comment by T.J. Townsend (blakkheim) - Thursday, 01 June 2023, 19:32 GMT
I asked discord support to include the license files in their tarball for future releases. That's all we can do.

Loading...