Arch Linux User Repository

There is a known breakage with Python 3.14, an MR is merged upstream to fix it, need to wait for a new release for a new build.

The next build will bring the holland-mariadb-dump package as well, we are missing it in AUR.

I have cleaned up the dependencies, removing python-future and optimizing a few. The package is working locally, please let me know if you run into any problems.

If possible, please remove the dependency on python-furure/ make the package working without python-future:

WARNING: python-future package is not compatible with Python 3.13

The python-future project was created in 2013 to attempt to save Python from the schism of version incompatibility that was threatening to tear apart the language (as Perl 6 contributed to the death of Perl).

That time is now past. Thanks to a huge porting effort across the Python community, Python 3 eventually thrived. Python 2 reached its end of life in 2020 and the python-future package should no longer be necessary. Use it to help with porting legacy code to Python 3 but don’t depend on it for new code.

If you use packages that depend on it, please contact maintainers and/or upstream of these packages and try to work out whether this dependency is really needed.

Regards and thanks for this package!

Unfortunately the Holland Backup project seems to be stalled (last commit was more than 2 years ago) and already showing signs of its age (it does not run unpatched under Python 3.11 and up). Since I stopped using it myself, I decided to disown this AUR package. Farewell!

Cloning the git repository (master branch) and installing it manually using python -m build and python -m installer seems to work fine.

Holland requires some patching to work with Python 3.11.

I have thrown together this zsh function to do a clean rebuild (note yay -Rcs):

pacman_upgrade_holland () {
    local PKGBUILD=$(mktemp)
    local patch=$(mktemp)
    trap "rm -f $PKGBUILD $patch" EXIT
    cat >! $PKGBUILD <<'EOF'
--- /home/acc/.cache/yay/holland/PKGBUILD       2023-09-24 18:13:15.130979110 -0700
+++ /home/acc/bak/PKGBUILD      2023-09-24 18:45:18.591404175 -0700
@@ -23,6 +23,7 @@
 prepare() {
   cd "${srcdir}"
   find -name setup.cfg -delete
+  patch -d "${srcdir}/${pkgname}-${pkgver}" -i $patch -p0
 }

 build() {
EOF
    cat >! $patch <<'EOF'
--- holland/core/command/command.py.orig    2021-12-02 10:23:56.000000000 -0800
+++ holland/core/command/command.py 2023-09-24 17:36:30.828740377 -0700
@@ -86,6 +86,10 @@
     description = " "

     def __init__(self):
+        if self.name in SUBPARSER.choices:
+            self.optparser = SUBPARSER.choices[self.name]
+            return
+
         self.optparser = SUBPARSER.add_parser(
             self.name,
             help="%s %s" % (self.name, self.description),
EOF
    yay -Rcs --noconfirm holland 2> /dev/null
    pacman_install \
        --answerclean All \
        --answeredit All \
        --cleanmenu \
        --editmenu \
        --editor patch \
        --editorflags "-Nbfi\ $PKGBUILD" \
        --noconfirm \
        --rebuild \
        holland{,-{mysql{,dump},pgdump}}
}

Holland now requires the pymysql Python package, so I added python-pymysql to the dependency list in release 1.2.1-2.

I noticed nightly failures with holland 1.2.1 in my backup timers, and it turns out it was complaining that no module pymysql could be found. I believe it may have started with the update to 1.2.1, I didn't catch the issue for a long time.

FYI, the package requires python-configobj now:

pkg_resources.DistributionNotFound: The 'configobj>=4.6.0' distribution was not found and is required by holland