| Git Clone URL: | https://aur.archlinux.org/xnviewmp.git (read-only, click to copy) |
|---|---|
| Package Base: | xnviewmp |
| Description: | An efficient multimedia viewer, browser and converter. |
| Upstream URL: | https://www.xnview.com/en/xnviewmp/ |
| Keywords: | graphics |
| Licenses: | custom |
| Submitter: | oliwer |
| Maintainer: | Corax |
| Last Packager: | Corax |
| Votes: | 307 |
| Popularity: | 2.46 |
| First Submitted: | 2008-07-25 19:01 (UTC) |
| Last Updated: | 2024-09-03 14:45 (UTC) |
@Raphis It was probably changed (without using a new filename) by Pierre, upstream.
You're correct. The PKGBUILD needs to be updated (again) to use the correct hash.
EDIT: Indeed. The file (with the same name) was modified on the XnView server on 2024/09/02. Even though this PKGBUILD was updated two days earlier on 2024/08/31, for the same exact version: 1.8.0.
Hi, the SHA256 checksum is wrong for the current 1.8.0-1 release. Changing it in the build files allows the installation, this is the correct one: 35182740675ddab0a51ad20e14f31b258a3126bb136b766210d5eeb31eaa5de3
@Mr.Spock: This is most likely an issue with upstream XnView, best to file a bug report here: https://newsgroup.xnview.com/viewforum.php?f=62
crashes everytime when opening and moving around on a picture > 64 MP
1.7.1 was released with some important fixes :)
@flan_suse: sorry for the very late reply. You're right, I actually spotted this a while back but didn't find the motivation to make the move. I was a little concerned that I might miss updates, but there are some pretty reactive people reporting new versions here so that should be fine. There will still be issues when Pierre decides to change an already released tar (it happened again recently), but this is fortunately not anywhere as frequent as regular updates. I'll make the switch for this package and xnviewmp-system-libs now.
Upstream does not version the released archives
They actually do.
I think you should update the PKGBUILD so that it pulls the tarballs from this URL:
https://download.xnview.com/old_versions/XnView_MP/
This will avoid the issue of "invalid SHA256", since it will download a specific version, rather than the generic "XnViewMP-linux-x64.tgz".
So instead of this:
source=("XnViewMP-linux-x64_${pkgver}-rel${srcrel}.tgz::https://download.xnview.com/XnViewMP-linux-x64.tgz"
You should have this:
source=("XnViewMP-linux-x64_${pkgver}-rel${srcrel}.tgz::https://download.xnview.com/old_versions/XnView_MP/XnView_MP-${pkgver}-linux-x64.tgz"
Don't be fooled by "old_versions" in the URL. Pierre adds the files on the same day of release.
looks like checksum is outdated for tgz. 1.6.0-1 (14/10) should be: f5a1a620c785ea7e8bbadac646d3cbe6202b183124769c1153a7b05f61ca9d75
@Corax, maybe it will help. The correct SHA256 for current XnViewMP-linux-x64.tgz file is 3816b6a86223e1a9bbf93ab6c61526ddcb2b8b3ff662408f2b88647e5ba7a9a8
here update fails with validation of sha256... so I flag out of date as requested.
Pinned Comments
Corax commented on 2017-01-21 15:34 (UTC) (edited on 2017-02-12 19:23 (UTC) by Corax)
Corax commented on 2017-01-20 21:49 (UTC) (edited on 2023-10-30 20:39 (UTC) by Corax)
If makepkg fails because the checksum is incorrect, please flag the package out-of-date and I will update the PKGBUILD.
The PKGBUILD now references the latest versioned archive, as a result of which it should keep working if a new version is released. However, upstream sometimes updates released archives in place, in which case the checksum will fail and a manual intervention is required.