Arch Linux User Repository

dcpomatic-git and it's depend "lib" packages where switched back to "bleeding edge" master branch! Use at own risk!

For production use better switch back to stable package at https://aur.archlinux.org/packages/dcpomatic/

Remember to deinstall all the "dcpomatic libs" when you switch from git to none git versions of my packages.

@cfenell:

The normal none XYZ-git packages are working for both of the pkg maintainers. Don't be alarmed if the source line in this none '-git' contains some git-src and no tar.xz files. At the moment, we pull many of the sources with git tags.

Make sure that you remove all packages (including dependency libs that where installed from AUR). Then clean up all build caches/downloads/SRC dir's of AUR-Helper tools (if you use one of them) and makepkg. Please start with as clean as possible build location.

Please don't contact Carl (upstream) about any of the "-git" AUR packages. These are "bleeding edge/test packages for AUR building of future dcpomatic releases". They are used only in the case of major changes that would break the normal packages. The usage of these "-git" versions of our packages are "at your own risk" (see pinned comment form 2018). Plase instead use dcpomatic libdcp libsub libcxml without the "-git" tag. They offer newer versions then the "-git" packages at the moment.

The github issue tracker you seemed to have used is not used for dcpomatic bug tracking. Please consult the development page at https://dcpomatic.com/development for dev information as for example the Bug-Tracker. On top of that the AUR-Packaging does not use any Bug Tracker, we have used the comment section in the AUR or eMail in the past.

If you have problems with the "normal" packages, you can contact me via email, I would be glad to help you.

It's not perfect to have the "-git" version up here on the AUR. Deleting them would mean that it would be a lot more work to reactivate them when we will need them in the future on major version jumps like maybe 2.16.X -> 2.18.0

Hi, the libdcp and libdcp-git pkgbuilds have failed to compile for some time now. The author has fixed the issues I have reported in the main branch at https://github.com/cth103/libdcp

It seems that the development of dcpomatic and its dependencies has moved fully to github from git.carlh.net. For example I now also got

Fatal: invalid reference: origin/v1.8.x

@mrpewpew: as said before ... the "xxxxxx-git" versions of my arch linux packages are "bleeding edge" and i'm trying to reduce the need of keeping multiple -git and none-git versions to a minimum. At the moment i'm not supplying a libasdcp-cth-git besides the stable libasdcp-cth which is used by both stable and develop-unstable-bleeding versions of my packages. I usually only use the "xxx-git" packages to do some pre-stable release build testing.

You could try to install the development git version by hand using the development version on http://carlh.net/asdcplib but i advice against using the resulting DCP's from the unstable-bleeding-edge dev versions of dcpomatic for anything else then test purposes.

If you give me a valid reason why i should invest time in supporting a libasdcp-cth-git package i might consider doing so in the future ...

Unfortunately, the package doesn't build anymore. The error message is : ../src/smpte_subtitle_asset.cc:50:10: fatal error: asdcp/KM_log.h: No such file or directory

dcpomatic-git and it's depend "lib" packages where switched back to "bleeding edge" master branch! Use at own risk!

For production use better switch back to stable package at https://aur.archlinux.org/packages/dcpomatic/

Remember to deinstall all the "dcpomatic libs" when you switch from git to none git versions of my packages.

@TilmanV: Thank you for the version info! It's fixed now.

PKGVer in PKGBUILD and SRCINFO are different. This causes an infinite updateloop.