Encryptpad not installing because a missing package - botan2

Support AUR
1

I had encryptpad installed a while ago and now a new update came along. This new version won’t compile because of a missing package, “botan2”. I saw it in the repo (2.3) but it won’t install either because of some errors. Any idea what is wrong ? Thanks.

.....
g++ -fstack-protector -m64 -pthread -fPIC -fvisibility=hidden -std=c++11 -D_REENTRANT -O3 -momit-leaf-frame-pointer -Wall -Wextra -Wpedantic -Wstrict-aliasing -Wstrict-overflow=5 -Wcast-align -Wmissing-declarations -Wpointer-arith -Wcast-qual -Wzero-as-null-pointer-constant -Wnon-virtual-dtor -Ibuild/include -Ibuild/include/external -c ./src/lib/pubkey/ed25519/ed25519_key.cpp -o build/obj/lib/pubkey_ed25519_key.o
Dans le fichier inclus depuis build/include/botan/internal/ed25519_internal.h:14,
                 depuis ./src/lib/pubkey/ed25519/ed25519.cpp:12:
build/include/botan/internal/ed25519_fe.h: Dans le constructeur « Botan::FE_25519::FE_25519(int) »:
build/include/botan/internal/ed25519_fe.h:32:26: erreur: « invalid_argument » n'est pas un membre de « std »
   32 |             { throw std::invalid_argument("Invalid FE_25519 initial value"); }
      |                          ^~~~~~~~~~~~~~~~
build/include/botan/internal/ed25519_fe.h: Dans le constructeur « Botan::FE_25519::FE_25519(std::initializer_list<int>) »:
build/include/botan/internal/ed25519_fe.h:40:26: erreur: « invalid_argument » n'est pas un membre de « std »
   40 |             { throw std::invalid_argument("Invalid FE_25519 initializer list"); }
      |                          ^~~~~~~~~~~~~~~~
Dans le fichier inclus depuis ./src/lib/pubkey/ed25519/ed25519_fe.cpp:11:
build/include/botan/internal/ed25519_fe.h: Dans le constructeur « Botan::FE_25519::FE_25519(int) »:
build/include/botan/internal/ed25519_fe.h:32:26: erreur: « invalid_argument » n'est pas un membre de « std »
   32 |             { throw std::invalid_argument("Invalid FE_25519 initial value"); }
      |                          ^~~~~~~~~~~~~~~~
build/include/botan/internal/ed25519_fe.h: Dans le constructeur « Botan::FE_25519::FE_25519(std::initializer_list<int>) »:
build/include/botan/internal/ed25519_fe.h:40:26: erreur: « invalid_argument » n'est pas un membre de « std »
   40 |             { throw std::invalid_argument("Invalid FE_25519 initializer list"); }
      |                          ^~~~~~~~~~~~~~~~
make: *** [Makefile:1211: build/obj/lib/pubkey_ed25519_fe.o] Error 1
make: *** Attente des tâches non terminées....
make: *** [Makefile:1208: build/obj/lib/pubkey_ed25519.o] Error 1
make : on quitte le répertoire « /var/tmp/pamac-build-maurice/botan-2.3/src/Botan-2.3.0 »
==> ERREUR : Une erreur s’est produite dans build().
    Abandon…
2

encryptpad is a custom build using AUR build script → AUR (en) - encryptpad

botan2 is not yet in stable → Packages

So you have to wait until next stable snap - or switch to testing branch - you decide.

EDIT:

Package build as expected on unstable branch.

 $ pamac build encryptpad
[...]
==> Creating package "encryptpad"...
  -> Generating .PKGINFO file...
  -> Generating .BUILDINFO file...
  -> Generating .MTREE file...
  -> Compressing package...
==> Leaving fakeroot environment.
==> Finished making: encryptpad 0.5.0.2-11 (søn 21 maj 2023 14:53:15 CEST)
==> Cleaning up...
3

Is there a possibility to return encryptpad to a previous version ? I had it installed before and was running fine but I remove it to investigate the problem. Now of course it is trying to install the latest version.

4

That happens when you enable automatic rebuild of AUR packages when using stable branch.

Only you have the package created previously.

You may check your build cache - where depends on the helper used.

If you use makepkg you will always have the builded packages either in the source folder or in the folder configured in .makepkg.conf.

5

no there is no trace of the previous version. I don’t want to switch branch to testing as it open a new can of worms. Thankfully the program web page offer an “appimage” (5.0.2) and with the appimagelauncher work fine.

6

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.