Checking for BerkeleyDB in //usr/include/...no (expecting 4.8, got 6.0) Checking for BerkeleyDB in //usr/include/db-4-8...no Checking for BerkeleyDB in //usr/include/db48...no Checking for BerkeleyDB in //usr/include/db4.8...no Checking for BerkeleyDB in //usr/include/db-4...no Checking for BerkeleyDB in //usr/include/db4...no Error: Unable to find BerkeleyDB Try: 'configure --help' for options ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_hardened-j4-20230407-194512 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-13 * clang/llvm (if any): /usr/lib/llvm/16 16.0.1 Python 3.10.11 Available Ruby profiles: [1] ruby30 (with Rubygems) * Available Rust versions: [1] rust-1.68.2 * The following VMs are available for generation-2: 1) OpenJDK 17.0.6_p10 [openjdk-17] 2) OpenJDK 8.362_p09 [openjdk-8] 3) Eclipse Temurin JDK 17.0.6_p10 [openjdk-bin-17] *) Eclipse Temurin JDK 8.362_p09 [openjdk-bin-8] Available Java Virtual Machines: [1] openjdk-8 [2] openjdk-17 [3] openjdk-bin-8 system-vm [4] openjdk-bin-17 The Glorious Glasgow Haskell Compilation System, version 9.0.2 php cli (if any): HEAD of ::gentoo commit 3fa9b1f490be2bb3914f5244bdc2f9978bbf156b Author: Repository mirror & CI <repomirrorci@gentoo.org> Date: Sat Apr 8 07:46:56 2023 +0000 2023-04-08 07:46:56 UTC emerge -qpvO mail-client/neomutt [ebuild N ] mail-client/neomutt-20230322-r1 USE="berkdb gnutls gpgme kyotocabinet nls notmuch pgp-classic qdbm ssl tokyocabinet zstd -autocrypt -doc -gdbm -idn -kerberos -lmdb -lz4 -sasl (-selinux) -slang -smime-classic -test -zlib"
Created attachment 859739 [details] emerge-info.txt
Created attachment 859740 [details] emerge-history.txt
Created attachment 859741 [details] environment
Created attachment 859742 [details] etc.portage.tar.bz2
Created attachment 859743 [details] logs.tar.bz2
Created attachment 859744 [details] mail-client:neomutt-20230322-r1:20230408-083850.log
Created attachment 859745 [details] temp.tar.bz2
I cannot reproduce this problem. USE="berkdb gnutls gpgme kyotocabinet nls notmuch pgp-classic qdbm ssl tokyocabinet zstd -autocrypt -doc -gdbm -idn -kerberos -lmdb -lz4 -sasl (-selinux) -slang -smime-classic -test -zlib" sudo emerge --ask --verbose =mail-client/neomutt-20230322 In a clean gentoo/systemd container.
Please run again against neomutt-20230407
appeared recently at the tinderbox image 23.0_desktop_systemd-j4-20230502-024505
Created attachment 861062 [details] emerge-info.txt
Created attachment 861063 [details] emerge-history.txt
Created attachment 861064 [details] environment
Created attachment 861065 [details] etc.portage.tar.bz2
Created attachment 861066 [details] logs.tar.bz2
Created attachment 861067 [details] mail-client:neomutt-20230407:20230502-205440.log
Created attachment 861068 [details] temp.tar.bz2
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=15627b8c10ca978941176a0f5a8a3acf561c2537 commit 15627b8c10ca978941176a0f5a8a3acf561c2537 Author: Nicolas Bock <nicolasbock@gentoo.org> AuthorDate: 2023-05-05 13:45:17 +0000 Commit: Nicolas Bock <nicolasbock@gentoo.org> CommitDate: 2023-05-05 13:47:16 +0000 mail-client/neomutt: Cleanup Remove broken dependency on BerkeleyDB:6.0 and remove old version of neomutt. Closes: https://bugs.gentoo.org/904068 Signed-off-by: Nicolas Bock <nicolasbock@gentoo.org> mail-client/neomutt/Manifest | 1 - mail-client/neomutt/neomutt-20220429.ebuild | 171 ------------------------- mail-client/neomutt/neomutt-20230322-r1.ebuild | 2 - mail-client/neomutt/neomutt-20230407-r1.ebuild | 2 - 4 files changed, 176 deletions(-)
