@whoseos It doesn't work for me :/ Using the system libraries, it does launch but it crashes very early: http://pastebin.com/F464DCFD
Do you have any particular library installed?
Search Criteria
Package Details: xnviewmp 1.8.3-1
Package Actions
| 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: | 311 |
| Popularity: | 1.58 |
| First Submitted: | 2008-07-25 19:01 (UTC) |
| Last Updated: | 2024-11-16 14:49 (UTC) |
Dependencies (2)
- qt5-multimedia
- glib2 (glib2-gitAUR, glib2-selinuxAUR, glib2-patched-thumbnailerAUR) (optional) – support for moving files to trash
Required by (0)
Sources (2)
Corax commented on 2016-10-15 17:57 (UTC)
Corax commented on 2016-10-15 17:25 (UTC) (edited on 2016-10-15 17:58 (UTC) by Corax)
@whoseos Sounds great! As I mentioned before, for now the qt5 dependencies are useless for now... If it works using the system Qt5 libraries, then that's definitely the way to go!
I'm going to review your patch and replacement script, if it works fine for me too I'm also going to see what can be cleaned up (like the packaged qt5 libraries) before updating the PKGBUILD :)
whoseos commented on 2016-10-15 15:50 (UTC) (edited on 2016-10-15 15:52 (UTC) by whoseos)
@Corax, xnviewmp is not able to use the system theme on KDE Plasma with the included qt5 libraries: http://imgur.com/a/uESZh. To fix this the application has to use the system's global qt5 libraries instead of it's own, which can be achieved by removing the qt.conf file and prepending "/usr/lib:" to LD_LIBRARY_PATH and QT_PLUGIN_PATH in the xnview.sh startup script.
I've uploaded a patch for the PKGBUILD @ http://ix.io/1wnQ and the replacement xnview.sh file @ http://ix.io/1wnk .
It would be great if you could include the changes in the package :)
Corax commented on 2016-10-09 16:02 (UTC)
@martinpoljak Great, adopted :) I've updated the PKGBUILD.
martinpoljak commented on 2016-10-09 13:43 (UTC)
@Corax, if you would like to do, I do it; I'm maintaining it time to time as it's been orphaned. I've disowned it, so claim it!
Corax commented on 2016-10-09 13:37 (UTC)
@martinpoljak If you don't have time to maintain this package, I'd be happy to adopt it.
Corax commented on 2016-10-09 13:35 (UTC)
The current version of the downloaded archives is 0.83 (change pkgver accordingly), here are the md5sums :
md5sums_x86_64=('3c2c5032a0be2b1f0976b50adad8c80b')
md5sums_i686=('4673c827de8aa326761433b2eda85a6b')
phiresky commented on 2016-09-19 12:19 (UTC)
@lmat The failed checksums are caused by the upstream dev not using versioned packages. You can use updpkgsums to fix this locally until the package is updated.
lmat commented on 2016-09-17 22:31 (UTC)
I just tried it out, and it fails to install with "==> Validating source_i686 files with md5sums...
XnViewMP-linux.tgz ... FAILED
==> ERROR: One or more files did not pass the validity check!"
I tried the post that grayich gave in PKGBUILD, but that didn't fix the issue. I'm not exactly waiting on this software, and I have many more to try for photo printing solution. But I thought I would drop a note here for what it's worth!
Corax commented on 2016-07-23 23:15 (UTC)
I'm wondering, why does the package depends on qt5-* at all? XnViewMP is shipped with all the Qt5 libraries it needs, if you use the startup script you don't need Qt5 packages to be installed. Or is that done to pull the dependencies of Qt5 itself?
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.