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: 1
Popularity: 0.78
First Submitted: 2024-04-29 17:56 (UTC)
Last Updated: 2024-12-22 17:27 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 Next › Last »

simona commented on 2024-12-25 22:42 (UTC)

==> ERRORE: PKGBUILD non esiste.

Auerhuhn commented on 2024-12-25 21:55 (UTC)

@simona Thank you. Let’s look at one of the failing tests.

When you run the following command line from the directory where the PKGBUILD is, what is the exact error message that appears?

makepkg -s --nocheck --noarchive && (cd src/labelle-1.3.2 && rm -rf tmp_install && python -m installer --destdir=tmp_install dist/labelle-1.3.2-py3-none-any.whl && PYTHONPATH="${PWD}/tmp_install/usr/lib/python3.13/site-packages" dbus-run-session xvfb-run -s '-nolisten local' pytest -vvx -k 'test_barcode_with_text_render_engine_alignment[left]' src)

simona commented on 2024-12-25 18:45 (UTC)

/home/simona/.cache/yay/labelle/src/labelle-1.3.2/src/labelle/lib/render_engines/tests/test_render_engines.py:317
================================================== short test summary info ===================================================
ERROR src/labelle/lib/render_engines/tests/test_render_engines.py::test_barcode_with_text_render_engine
ERROR src/labelle/lib/render_engines/tests/test_render_engines.py::test_barcode_with_text_render_engine_alignment[left]
ERROR src/labelle/lib/render_engines/tests/test_render_engines.py::test_barcode_with_text_render_engine_alignment[center]
ERROR src/labelle/lib/render_engines/tests/test_render_engines.py::test_barcode_with_text_render_engine_alignment[right]
ERROR src/labelle/lib/render_engines/tests/test_render_engines.py::test_barcode_with_text_render_engine_font_size_ratio[0.2]
ERROR src/labelle/lib/render_engines/tests/test_render_engines.py::test_barcode_with_text_render_engine_font_size_ratio[0.4]
ERROR src/labelle/lib/render_engines/tests/test_render_engines.py::test_barcode_with_text_render_engine_font_size_ratio[0.6]
ERROR src/labelle/lib/render_engines/tests/test_render_engines.py::test_barcode_with_text_render_engine_font_size_ratio[0.8]
ERROR src/labelle/lib/render_engines/tests/test_render_engines.py::test_barcode_with_text_render_engine_font_size_ratio[1.0]
ERROR src/labelle/lib/render_engines/tests/test_render_engines.py::test_barcode_render_engine

Auerhuhn commented on 2024-12-25 18:28 (UTC)

@simona Please post the error message you are getting.

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.

« First ‹ Previous 1 2 3 Next › Last »