Package Details: labelle 1.3.2-2

Git Clone URL: https://aur.archlinux.org/labelle.git (read-only, click to copy)
Package Base: labelle
Description: Linux Software to print with LabelManager PnP from Dymo
Upstream URL: https://github.com/labelle-org/labelle
Licenses: Apache-2.0
Replaces: dymoprint
Submitter: Auerhuhn
Maintainer: Auerhuhn
Last Packager: Auerhuhn
Votes: 0
Popularity: 0.000000
First Submitted: 2024-04-29 17:56 (UTC)
Last Updated: 2024-12-22 17:27 (UTC)

Latest Comments

« First ‹ Previous 1 2

simona commented on 2024-12-25 08:56 (UTC)

no more builds

Auerhuhn commented on 2024-12-24 11:04 (UTC)

You’re welcome @Nestor_013!

Nestor_013 commented on 2024-12-24 10:28 (UTC)

@Auerhuhn Thanks for clarification. I'm quickly lost with all these dependencies.

Auerhuhn commented on 2024-12-24 09:53 (UTC) (edited on 2024-12-24 09:54 (UTC) by Auerhuhn)

@Nestor_013 python-diffimg is not a direct dependency of this package. It is pulled via the python-pytest-image-diff checkdepends.

The general rule is that AUR packages that depend on Python need to be rebuilt whenever Python gets a new minor update.

Some package owners push empty pkgrel bumps out of courtesy to spare users the manual effort, but not all maintainers do so, in which case you have to force-rebuild the package manually.

Nestor_013 commented on 2024-12-24 09:45 (UTC)

Hi, it seems that dependency on 'diffimg' is missing.

...
File "/usr/lib/python3.13/site-packages/pytest_image_diff/image_diff.py", line 5, in <module>
from diffimg import diff
ModuleNotFoundError: No module named 'diffimg'
==> ERROR: A failure occurred in check().
Aborting...
...

Auerhuhn commented on 2024-10-04 21:47 (UTC)

Hi @simona, the issue you reported is unrelated to the labelle package.

You may want to file it against the python-imgdiff package instead. Alternatively, consider running your build in a clean chroot to avoid the issue altogether.

simona commented on 2024-10-04 18:39 (UTC)

python-imgdiff: /usr/bin/imgdiff è già presente nel filesystem (appartiene a imgpatchtools-git)

Auerhuhn commented on 2024-05-04 15:42 (UTC)

Thanks for the pointer @agarbathi. Fixed.

The reason for the error is that the upstream maintainers have added a leading v to the release version and re-published the release with the changed version.

It seems plausible that the SHA of the tarball changes when this happens, so I have accepted the change of hash this particular time, despite the upstream release having the same content as before.

agarbathi commented on 2024-05-04 15:34 (UTC)

Please update the PKGBuild. Path is wrong. Thanks

« First ‹ Previous 1 2