Until courier-unicode is officially released this workaround will make it work

Quoting: https://sourceforge.net/p/courier/mailman/message/59348126/

* all: workaround for a conflict between gcc 16 in Fedora 44 and autoconf.  
If manually compiling any package it is necessary to explicitly specify the  
--std=gnu++17 option, configure won't figure it out. This is done by adding  
the option to CXXFLAGS. Pass "CXXFLAGS=--std=gnu++17" parameter to the  
configure script, or add it to the existing one

Maybe the AUR pkg maintainer will integrate the change below in the PKGBUILD ?

./configure --prefix=/usr CXXFLAGS=--std=gnu++17

Thanks in advance

You did upgrade courier-unicode before upgrading courier-imap? I don't use courier-imap (and the AUR version is not the latest though recent changes have mostly been irrelevant to Arch) but it should just pick up whatever version of courier-unicode is installed at compilation time I would think.

Hello. I use courier only as an IMAP server (so no courier-mta, just courier-imap). After upgrading courier-imap and courier-unicode to the latest versions in the AUR as of today's date, courier fails to load, giving the error "/usr/bin/imaplogin: error while loading shared libraries: libcourier-unicode.so.7: cannot open shared object file: No such file or directory". It seems this package updated the library from so.7 to so.8, but courier is still expecting .7? I worked around this by making a symlink ln -s "libcourier-unicode.so.8.0.0 libcourier-unicode.so.7", and it seems to work now, but that's a kludge. Just FYI

Version 2.3.0 released. You'll probably need to rebuild courier-mta.

I'm not sure how to go about fixing this either. On my system I get the following:

[courier-unicode]# file -S -bizL courier-unicode-2.2.6.tar.bz2
application/x-tar; charset=binary compressed-encoding=application/x-bzip2; charset=binary

Whatever the mechanism, when tar acts on a .tar.bz2 file it uses bzip2 to decompress, then unpacks the archive. You might have to ask around for help!

Hey sorry for the long delay, i'm not sure what you mean by "mime/magic settings"? I found a package in the AUR called "mimemagic" and I installed it, but I am still getting the error. I had a quick look at file.sh but it is incomprehensible to me, i wouldn't know where to start in trying to modify it so it uses bsdtar.

@train_wreck looks like your system is using bzip2 to extract, which won't do the tar file. It should look like:

==> Validating source files with sha256sums... courier-unicode-2.2.5.tar.bz2 ... Passed ==> Extracting sources... -> Extracting courier-unicode-2.2.5.tar.bz2 with bsdtar ==> Starting build()...

In /usr/share/makepkg/source/file.sh the code is using "file -S -bizL" to check the downloaded file. So perhaps your mime/magic settings need to be checked?

Hello, this package is failing to build with the following error:

==> Making package: courier-unicode 2.2.5-1 (Mon 21 Nov 2022 11:18:38 PM CST) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Retrieving sources... -> Downloading courier-unicode-2.2.5.tar.bz2... % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 779 0 779 0 0 2085 0 --:--:-- --:--:-- --:--:-- 2082 100 795 0 795 0 0 1570 0 --:--:-- --:--:-- --:--:-- 1570 100 1036 0 1036 0 0 1646 0 --:--:-- --:--:-- --:--:-- 1646 100 393 100 393 0 0 378 0 0:00:01 0:00:01 --:--:-- 378 100 581k 100 581k 0 0 340k 0 0:00:01 0:00:01 --:--:-- 1200k ==> Validating source files with sha256sums... courier-unicode-2.2.5.tar.bz2 ... Passed ==> Extracting sources... -> Extracting courier-unicode-2.2.5.tar.bz2 with bzip2 ==> Starting build()... /home/user/11-21-22/courier-unicode/PKGBUILD: line 20: cd: /home/user/11-21-22/courier-unicode/src/courier-unicode-2.2.5: No such file or directory ==> ERROR: A failure occurred in build(). Aborting...

It is looking for a directory "courier-unicode-2.2.5" but this does not exist. Within the parent folder there are 2 files, courier-unicode-2.2.5.tar and courier-unicode-2.2.5.tar.bz2. I had to untar the .tar file, then it built.

Wow, you're fast! I just updated courier-unicode on my Raspi4 and it worked just fine. Thank you so much!!!

Done, but I can't verify it works!