db5.3 underwent a license change upstream, and thus newer versions are unsuitable for Debian. A lot of packages apparently already migrated away. A good plan would seem to be to get packages adopt a migration strategy for forky, and then remove db5.3 from duke. Filing with severity: serious for visibility during the forky development cycle, and can be downgraded before the forky release. Chris
* Chris Hofstaedtler <zeha@debian.org> [251003 10:17]: Copying this bug to db-defaults. Chris
* Chris Hofstaedtler <zeha@debian.org> [251003 10:17]:
This will need bugs filed against the rdeps.
dak claims, when trying `dak rm -R -n db-defaults db5.3`:
Checking reverse dependencies...
# Broken Depends:
389-ds-base: 389-ds-base
animals: animals
apr-util: libaprutil1t64
apt: apt-utils
bdbvu: bdbvu
bmf: bmf
bogofilter: bogofilter-bdb
bruteforce-wallet: bruteforce-wallet
c-icap: c-icap
c-icap-modules: libc-icap-mod-urlcheck
chise-base: libchise1t64
clisp: clisp-module-berkeley-db
cyrus-imapd: cyrus-common [amd64 arm64 mips64el ppc64el riscv64 s390x]
cyrus-sasl2: libsasl2-modules-db
sasl2-bin
dsniff: dsniff
evolution-data-server: evolution-data-server
libebackend-1.2-11t64
exim4: exim4-base
exim4-daemon-heavy
exim4-daemon-light
freespeech: freephone
gnucobol3: libcob4t64
gridengine: gridengine-client
heimdal: libhdb9t64-heimdal
libotp0t64-heimdal
hpsockd: hpsockd
inn2: inn2
iproute2: iproute2
isync: isync
jabberd2: jabberd2
jack-audio-connection-kit: libjack0
jackd2: libjack-jackd2-0
jigdo: jigdo-file
kamailio: kamailio-berkeley-bin
kamailio-berkeley-modules
libberkeleydb-perl: libberkeleydb-perl
libetpan: libetpan20t64
libguestfs: libguestfs0t64
libical3: libical-dev
libical3t64
libnss-db: libnss-db
libpam-abl: libpam-abl
libpam-ccreds: libpam-ccreds
libpinyin: libpinyin-utils
libpinyin15
libzhuyin15
librcc: librcc0
litecoin: litecoin-qt [amd64 arm64 armel armhf i386 mips64el ppc64el riscv64]
litecoind [amd64 arm64 armel armhf i386 mips64el ppc64el riscv64]
mailutils: libmailutils-dev
libmu-dbm9t64
mailutils-mda
mailutils-pop3d
moc: moc
netatalk: netatalk
netatalk-tools
nmh: nmh
nss-updatedb: nss-updatedb
nvi: nvi
onak: onak
opendkim: libopendkim11
opendkim
opendkim-tools
opensmtpd: opensmtpd
perdition: perdition
perl: libperl5.40
php8.4: php8.4-dba
postfix: postfix
python-bsddb3: python3-bsddb3
python3.13: libpython3.13-dbg
libpython3.13-stdlib
python3.14: libpython3.14-dbg
libpython3.14-stdlib
redland: librdf0t64
reprepro: reprepro
rulex: librulexdb-dev
librulexdb0
sendmail: sendmail-bin
skksearch: skksearch
skktools: skktools
sks: sks
spamprobe: spamprobe
squidguard: squidguard
subversion: libsvn1
swi-prolog: swi-prolog-bdb
syrep: syrep
tcpstat: tcpstat
vacation: vacation
webalizer: webalizer
xastir: xastir
xemacs21: xemacs21-mule
xemacs21-mule-canna-wnn
xemacs21-nomule
# Broken Build-Depends:
389-ds-base: libdb-dev
animals: libdb5.3++-dev
apr-util: libdb-dev
apt: libdb-dev
bdbvu: libdb5.3++-dev
bind9: libdb-dev
bmf: libdb-dev (5.1 >=)
bogofilter: libdb-dev (4.6.19 >=)
boxbackup: libdb-dev (4.7 >=)
bruteforce-wallet: libdb-dev
c-icap: libdb-dev
c-icap-modules: libdb-dev
chise-base: libdb-dev (4.8 >=)
clisp: libdb-dev
diffoscope: db-util
dovecot: libdb-dev
dsniff: libdb-dev
evolution-data-server: db-util
libdb-dev
exim4: libdb5.3-dev
freespeech: libdb-dev
libdb5.3t64
fsvs: libdb-dev
glusterfs: libdb-dev
gnucobol3: libdb-dev
gnucobol4: libdb-dev
gridengine: libdb-dev
heimdal: libdb-dev
hpsockd: libdb-dev
inn2: libdb-dev
iproute2: libdb-dev
isync: libdb-dev
jabberd2: libdb-dev
jack-audio-connection-kit: libdb-dev
jackd2: libdb-dev
jigdo: libdb-dev (4.8 >=)
kamailio: libdb-dev
libberkeleydb-perl: libdb-dev
libetpan: libdb-dev
libguestfs: db-util
libical3: libdb-dev
libnss-db: libdb-dev (4.6 >)
libpam-abl: libdb-dev
libpam-ccreds: libdb-dev
libpinyin: libdb-dev
librcc: libdb-dev
litecoin: libdb5.3++-dev
mailutils: libdb-dev
mit-scheme: libdb-dev
moc: libdb-dev
monero: libdb-dev
netatalk: libdb-dev
nmh: libdb-dev
nss-updatedb: libdb-dev (4.7 >=)
nvi: libdb-dev
opendkim: libdb-dev
opensmtpd: libdb-dev
pam: libdb-dev
perdition: libdb-dev
perl: libdb-dev
php8.4: libdb-dev
poedit: libdb-dev
postfix: libdb-dev
python-bsddb3: libdb5.3-dev
python3.13: libdb-dev
python3.14: libdb-dev
redland: libdb-dev
reprepro: libdb-dev
rulex: libdb-dev
libdb5.3t64
sendmail: libdb-dev
skksearch: libdb-dev
skktools: libdb-dev
sks: libdb-dev
spamprobe: libdb-dev
squidguard: libdb-dev
subversion: libdb5.3-dev
swi-prolog: libdb-dev
syrep: libdb-dev (5.1 >=)
tcpstat: libdb-dev
vacation: libdb-dev (5.1 >=)
webalizer: libdb-dev (4.7 >=)
wvstreams: libdb-dev
xastir: libdb-dev
xemacs21: libdb-dev
I've now checked, Berkeley DB is also released under AGPL. https://www.oracle.com/downloads/licenses/berkeleydb-oslicense.html Why is that a real issue? According to the Wiki, Debian also ships other AGPL software.
Hello,
I posted an MR recently that would help address the issue with libnss-db. The proposed MR creates a db5.3-free `libc6-libnss-db` package as part of glibc that provides the `libnss-db.so.2` and is a direct functional replacement for the stand-alone libnss-db. It would allow as seamless as possible a transition between the two, and uses existing code in glibc that is both db5.3-free and actively maintained upstream. https://salsa.debian.org/glibc-team/glibc/-/merge_requests/38 I also opened bug #1132249 to discuss
in an interesting turn of events, libdb is seeing serious development activity now under a new upstream maintainer there is also a new bugfix release v5.3.29 from April 23 https://github.com/berkeleydb/libdb/releases/tag/v5.3.29 the new maintainer has made this statement in the project readme: This repository is two things at once: 1. A historical archive of Berkeley DB — the complete published lineage of releases and official patches that could be recovered, preserved as tags and GitHub Releases for reference and git diff-able history. 2. A living fork under active development on the master branch, where new work (bug fixes, portability, performance, and new features) happens.
Would be nice if the author would put Co-authored-by: tags on their commits identifying the used LLM tooling. Also I somewhat doubt that a new file (os_atomic.c) can be copyrighted 2013 by Oracle. Oh well. Chris
I would still rather removed Berkeley DB from Debian than rely on a single maintainer who seems to be knowledgeable in the databases, but still they are j Ondrej -- Ondřej Surý (He/Him) ondrej@sury.org A gentle nudge is always appreciated if I take a little longer to reply.