Package Details: libmagick6 6.9.13.10-1

Git Clone URL: https://aur.archlinux.org/imagemagick6.git (read-only, click to copy)
Package Base: imagemagick6
Description: An image viewing/manipulation program (legacy 6.9.13-* series; library)
Upstream URL: https://legacy.imagemagick.org/
Keywords: ImageMagick
Licenses: custom
Submitter: arojas
Maintainer: None
Last Packager: yochananmarqos
Votes: 10
Popularity: 0.000000
First Submitted: 2021-01-29 14:32 (UTC)
Last Updated: 2024-05-05 20:16 (UTC)

Pinned Comments

yochananmarqos commented on 2021-09-08 21:45 (UTC) (edited on 2022-08-27 21:36 (UTC) by yochananmarqos)

DO NOT report issues if you’re using an AUR helper (including Pamac aka Add/Remove Software). If you have a problem, build it manually and see if you can reproduce the issue.

Please don't spam the comments if the package is out of date. Just flag it out of date.

Latest Comments

« First ‹ Previous 1 .. 3 4 5 6 7 8 9 10 11 12 13 Next › Last »

Kunda commented on 2021-08-28 13:53 (UTC) 

Preparing...
Checking libmagick6 dependencies...
Resolving dependencies...
Checking inter-conflicts...

Building imagemagick6...
==> Making package: imagemagick6 6.9.12.19-2 (Sat 28 Aug 2021 09:47:04 AM EDT)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found ImageMagick6-6.9.12-19.tar.gz
==> ERROR: arch-fonts.diff was not found in the build directory and is not a URL.
Failed to build imagemagick6

tumblingthrough commented on 2021-08-27 14:39 (UTC)

@gudwin Many thanks again, but it's now been fixed as per your suggestion. Update went through without error.

lual commented on 2021-08-27 07:46 (UTC)

Thank you @gudwin for the hint how to edit the PKGBUILD to get rid of this peeve. It worked for me also.

gudwin commented on 2021-08-25 19:43 (UTC)

@tumblingthrough I was able to build it here with pamac doing the following ... after doing "pamac update" when it asks if I want to edit the PKGBUILD I selected 'e' (for editing) and then edited the following variables:

_pkgver=6.9.12-20

pkgrel=1

sha256sums=('8fa7addb7eac2dd417c7fbed46ff9dd5614abf7cefea4d786375306bec2659b1' 'a85b744c61b1b563743ecb7c7adad999d7ed9a8af816650e3ab9321b2b102e73')

I then saved the new PKGBUILD and it compiled without errors. It seems to me that, for some reason, the PKGBUILD is still pointing to the old version ... and this is the reason it only tries to rebuild version 6.9.12-19 instead of building 6.9.12-20. At least it worked for me.

tumblingthrough commented on 2021-08-25 07:40 (UTC)

@gudwin Really appreciate your work on this. This package has been driving me nuts, I haven't been able to get it to build since the previous update, whatever suggestions have been put here. Am looking forward to not having to worry about it!

gudwin commented on 2021-08-23 14:23 (UTC)

I manually made a git clone of https://aur.archlinux.org/imagemagick6.git and interestingly enough, there the PKG file is correct:

_pkgver=6.9.12-20

pkgrel=1

and also the correct sha256sum the question there is ... why when I try to do a pamac update, it grabs the wrong PKG file ? Where is the catch ? I would suspect a bug on pamac ... but why this happens only with the libmagick6 package ?

gudwin commented on 2021-08-23 14:15 (UTC)

I tried to edit the PKG file and change:

_pkgver=6.9.12-19 pkgrel=2

to

_pkgver=6.9.12-20 pkgrel=1

but it seems the sha256sum is apparently wrong Probably we will need a newer update to correct that ?

gudwin commented on 2021-08-23 14:07 (UTC)

Ah ... I noticed the PKG file is still saying that: _pkgver=6.9.12-19 shouln´t it be 6.9.12-20 ?

gudwin commented on 2021-08-23 13:57 (UTC)

What is wrong with this package update ? No matter how many times I do the update, the package always remain as needing an upgrade ... and when I use pamac to update, it signalizes:

Warning: libmagick6-6.9.12.19-2 is up to date -- reinstalling

There should be something wrong with the build, which does not signalize the update was already performed ! The same was happening a few days ago when the package was last updated.

politas commented on 2021-08-23 00:09 (UTC)

Is there something else one might require to address that, so the next update doesn't also require a clean update?

Can we get an answer to this question? It's getting to be quite a hassle having to regularly reset the build files for just this one package.

« First ‹ Previous 1 .. 3 4 5 6 7 8 9 10 11 12 13 Next › Last »