Arch Linux User Repository

@brfransen

Fixed in calamares-git: added python and required Python modules (python-yaml, python-jsonschema) to depends to properly support Calamares Python functionality.

Please use calamares-git when Python support is required (WITH_PYTHONQT=ON). I maintain separate builds with and without Python support depending on the configuration.

The build warnings are due to Python 3.14 + upstream pybind11/Calamares compatibility (deprecated internal APIs).

They are non-fatal and do not affect the build or runtime.

python should be a dep as many of the modules require python for them to be built.

Hello everyone! This package was previously orphaned, and I’m happy to take over as the new maintainer. I will keep it updated and address any issues as best as I can. Please don’t hesitate to report bugs or suggestions—your feedback is always welcome!

I have the same issue as @wellyxs:

-- Installing: /home/excalibur/.cache/paru/clone/calamares/pkg/calamares/usr/share/calamares/settings.conf
==> Tidying install...
  -> Removing libtool files...
  -> Purging unwanted files...
  -> Removing static library files...
  -> Stripping unneeded symbols from binaries and libraries...
  -> Compressing man and info pages...
==> Checking for packaging issues...
==> Creating package "calamares"...
  -> Generating .PKGINFO file...
  -> Generating .BUILDINFO file...
  -> Generating .MTREE file...
  -> Compressing package...
==> Starting package_calamares-qt5()...
/home/excalibur/.cache/paru/clone/calamares/PKGBUILD: line 176: cd: /home/excalibur/.cache/paru/clone/calamares/src/calamares-qt5-3.3.8/build: No such file or directory
==> ERROR: A failure occurred in package_calamares-qt5().
    Aborting...

paru can't install AUR dependencies so above was manually built with makepkg -sif.

My guess is that I'm building for Qt6 but above was trying to package for Qt5:

==> Starting prepare()...
qt6-base already exists
Update qt6-base? (y/n) :

latest version is 3.3.8

everytime when I compile calamares I have the following error:

==> Iniciando package_calamares-qt5()... /home/welly/Packages/calamares/PKGBUILD: linha 176: cd: /home/welly/Packages/calamares/src/calamares-qt5-3.3.5/build: Arquivo ou diretório inexistente ==> ERRO: Uma falha ocorreu em package_calamares-qt5(). Abortando...

Am consistently getting the following build/link error:

/bin/ld: /usr/lib/libQt6Quick.so.6.6.3: undefined reference to `QFont::stringToTag(char const*)@Qt_6'
/bin/ld: /usr/lib/libQt6Quick.so.6.6.3: undefined reference to `QFont::tagToString(unsigned int)@Qt_6'
/bin/ld: /usr/lib/libQt6Quick.so.6.6.3: undefined reference to `QFont::setFeature(unsigned int, unsigned int)@Qt_6'
/bin/ld: /usr/lib/libQt6Quick.so.6.6.3: undefined reference to `QFont::featureValue(unsigned int) const@Qt_6'
collect2: error: ld returned 1 exit status
make[2]: *** [src/libcalamaresui/CMakeFiles/test_libcalamaresuipaste.dir/build.make:152: test_libcalamaresuipaste] Error 1
make[1]: *** [CMakeFiles/Makefile2:5038: src/libcalamaresui/CMakeFiles/test_libcalamaresuipaste.dir/all] Error 2
make: *** [Makefile:166: all] Error 2
==> ERROR: A failure occurred in build().
    Aborting...

I'm more than a little concerned that you're building out qt6-base-6.7.0, but arch is currently pushing qt-6.6.3, so we have a gigantic version conflict. I'm going to speculate that this is why we're seeing the link error. I want to emphasize that no version of calamares currently builds, and already-built versions won't run.

Please take a look at the README.md.