Arch Linux User Repository

Pushed a fix. Thanks for the report.

Yes.

Interesting. Am I assuming correctly that you have the AUR package qt4 installed (which provides lrelease-qt4) but don't have qt5-tools installed (which provides lrelease on my system)?

If yes, does it build correctly if you install qt5-tools?

qt4 linguist is installed and can be launched, yet fails in build stage:

==> Starting build()...
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a race-free mkdir -p... /usr/bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether make supports the include directive... yes (GNU style)
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether the compiler supports GNU C... yes
checking whether gcc accepts -g... yes
checking for gcc option to enable C11 features... none needed
checking whether gcc understands -c and -o together... yes
checking dependency style of gcc... gcc3
checking for ar... ar
checking the archiver (ar) interface... ar
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking how to print strings... printf
checking for a sed that does not truncate output... /usr/bin/sed
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for fgrep... /usr/bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking how to convert x86_64-pc-linux-gnu file names to x86_64-pc-linux-gnu format... func_convert_file_noop
checking how to convert x86_64-pc-linux-gnu file names to toolchain format... func_convert_file_noop
checking for /usr/bin/ld option to reload object files... -r
checking for file... file
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for archiver @FILE support... @
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for sysroot... no
checking for a working dd... /usr/bin/dd
checking how to truncate binary pipes... /usr/bin/dd bs=4096 count=1
checking for mt... no
checking if : is a manifest tool... no
checking for stdio.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for strings.h... yes
checking for sys/stat.h... yes
checking for sys/types.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking for gcc... (cached) gcc
checking whether the compiler supports GNU C... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to enable C11 features... (cached) none needed
checking whether gcc understands -c and -o together... (cached) yes
checking dependency style of gcc... (cached) gcc3
checking for g++... g++
checking whether the compiler supports GNU C++... yes
checking whether g++ accepts -g... yes
checking for g++ option to enable C++11 features... none needed
checking dependency style of g++... gcc3
checking how to run the C++ preprocessor... g++ -E
checking for ld used by g++... /usr/bin/ld -m elf_x86_64
checking if the linker (/usr/bin/ld -m elf_x86_64) is GNU ld... yes
checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking for g++ option to produce PIC... -fPIC -DPIC
checking if g++ PIC flag -fPIC -DPIC works... yes
checking if g++ static flag -static works... yes
checking if g++ supports -c -o file.o... yes
checking if g++ supports -c -o file.o... (cached) yes
checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking dynamic linker characteristics... (cached) GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking size of long unsigned int... 8
checking whether g++ supports C++11 features with -std=c++11... yes
checking for swig3.0... yes
checking for swig... no
checking for swig3.0... /usr/bin/swig3.0
checking for python2.7... /usr/bin/python2.7
checking for a version of Python >= '2.1.0'... yes
checking for the distutils Python package... yes
checking for Python include path... -I/usr/include/python2.7
checking for Python library path... -L/usr/lib -lpython2.7
checking for Python site-packages path... /usr/lib/python2.7/site-packages
checking python extra libraries... -ldl -lm
checking python extra linking flags... -Xlinker -export-dynamic
checking consistency of all components of python development environment... yes
checking python2.7 module: psutil... yes
AX_SWIG_PYTHON_CPPFLAGS: -I/usr/include/python2.7
checking for pyrcc4... yes
checking for lrelease... no
configure: error: missing lrelease in path, make sure qt4-linguist-tools is installed
==> ERROR: A failure occurred in build().
    Aborting...

MarsSeed, what on earth is your problem?

I've already asked you a few weeks ago to talk to me instead of filing deletion requests. Yet here we go again.

You claim this application is discontinued, despite the developer still working on it, albeit with a glacial speed.

You claim it is - and I quote the full extent of your problem description - "broken". Yet, it compiles, launches, and synchronizes fine for me. If that is not the case for you, please post a proper problem description in a comment here. I've always reacted to reproducible issues in a timely manner, but I'm not going guess what you might be seeing and debug hypotheticals.

You claim "since that time, there are even more breakages in its legacy dependency chain, so it is unbuildable." Yes, true, one of swig3's check dependencies was apparently deleted from the main repo sometime in the few weeks since I pushed this package. That's about the only point I'm willing to give you. Fixed.

You claim armory is "unneeded" even though people would loose the ability to access their wallets without it. If you don't need it, that's fine. Nobody is asking to maintain it. I'm the one putting in the work for that.

You claim it's been "definitely unbuildable on Arch Linux since Nov 2021, when most Python2 packages have been dropped from repo [...]". And yet those very same Python 2 dependencies are available on the AUR and mostly have submission dates from years ago. Must be a coincidence... There was a period of about three months in summer of 2021 where armory was unbuildable because of a bug in the AUR causing it to reject submissions, which it erroneously believed where still available from the repo. There were a number of reports on the dependencies during that time and the packages were pushed up as soon as that issue was resolved. Nov 2021 was uneventful from the PoV of armory dependencies. As far as I'm aware that was the only time where armory was unbuildable for an extended period.

You claim "[...] after which date at no point in time were all of this package's dependencies were [sic] in a working condition." Then kindly act constructively and point out which dependencies aren't working for you and what errors you're seeing. I may have missed something, but to me everything looks to be in working order.

(PS: On a mostly unrelated note: Why is there no button to respond to/dispute submitted requests?)