Revision as of 10:19, 21 March 2020

Mark libdb as deprecated

Summary

This change should inform maintainers and developers about effort to remove libdb in future.

Owner

Name: Filip Januš
Email: fjanus@redhat.com

Current status

Targeted release: Fedora 33
Last updated: 2020-03-21
Tracker bug: <will be assigned by the Wrangler>
Release notes tracker: <will be assigned by the Wrangler>

Detailed Description

We would like to remove libdb from Fedora in future, because BerkeleyDB 6.x has a more restrictive license than the previous versions (AGPLv3 vs. LGPLv2) and due many projects can't use it. Nowadays Fedora uses the old version (5.3.28) and we can't update to newer. Due to many projects have libdb dependency, we propose few steps to complete removal. First step would mark libdb as deprecated package in Fedora 33. Next steps in Fedora 35 would provide converting tool for existing databases and mark libdb as orphaned.

Benefit to Fedora

We would like to have most recent releases of components in Fedora, which are supported by upstreams. But due to licence of BerkeleyDB we need to hold old BerkeleyDB version in Fedora.

Scope

Proposal owners: Not needed for this change - only deprecation

Other developers: Developers should prepare own projects(scripts, programs, packages, ...) for the next change and for the complete libdb removal.

Release engineering: #Releng issue number (a check of an impact with Release Engineering is needed)

Policies and guidelines: Not needed for this change - only deprecation

Trademark approval: Not needed for this change - only deprecation

Upgrade/compatibility impact

This change hasn't direct impact onto actual dependencies. Purpose of this change is inform and prepare people to future change which will affect many components.

Here is short discussion from Fedora-devel list.

As I mentioned above we would like to remove libdb in the best case in Fedora 35. And time between F33 and F35 we would like to use for discussion about solution, which could transfer existing libdb databases to other and try to find solution for components which supports only libdb.

User Experience

There is no change for users. Package is marked only as deprecated package and behaves as before.

Dependencies

Libdb has many dependencies:
389-ds-base
apr-util-bdb
bind-sdb
bogofilter
cld
clisp
cyrus-sasl-lib
dsniff
evolution-data-server
exim
heimdal
iproute
ipv6calc
isync
jabberd
jigdo
jigdo-gui
kdesvn
libetpan
libopendkim
libserf
lizardfs-master
mesos
mod_dav_svn
mod_perl
mod_qos
mod_security
netatalk
nmh
nss_updatedb
nvi
opendkim
openldap-servers
opensips-db_berkeley
opensmtpd
pam
pam_abl
pam_ccreds
perdition
perl-BDB
perl-BerkeleyDB
perl-DB_File
perl-eperl
php-dba
pl
postfix
python3-bsddb3
rapidsvn
redland
reprepro
rpm
rsvndump
sendmail
sks
spamprobe
squid
squidGuard
subversion
tqsllib
trustedqsl
webalizer
xemacs

Contingency Plan

Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
Contingency deadline: N/A (not a System Wide Change)
Blocks release? No
Blocks product? None

Documentation

There is no upstream documentation, but here is a list of dependencies with some useful comments and here some possible alternatives.

Release Notes

@@ Line 41: / Line 41: @@
 == Benefit to Fedora ==
 We would like to have most recent releases of components in Fedora, which are supported by upstreams. But due to licence of BerkeleyDB we need to hold old BerkeleyDB version in Fedora.
 <!-- What is the benefit to the distribution?  Will the software we generate be improved? How will the process of creating Fedora releases be improved?
@@ Line 72: / Line 71: @@
 == Scope ==
 * Proposal owners: Not needed for this change - only deprecation
 <!-- What work do the feature owners have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
-* Other developers:
+* Other developers: Developers should prepare own projects(scripts, programs, packages, ...) for the next change and for the complete libdb removal.
-Developers should prepare own projects(scripts, programs, packages, ...) for the next change and for the complete libdb removal.
 <!-- What work do other developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
@@ Line 92: / Line 89: @@
 This change hasn't direct impact onto actual dependencies. Purpose of this change is inform and prepare people to future change which will affect many components.
-Here is short discussion from Fedora-devel list: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/O442UPRAGHD6ZN77GWTARY2VXP24VFBC/#O442UPRAGHD6ZN77GWTARY2VXP24VFBC
+[https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/O442UPRAGHD6ZN77GWTARY2VXP24VFBC/#O442UPRAGHD6ZN77GWTARY2VXP24VFBC Here] is short discussion from Fedora-devel list.
 As I mentioned above we would like to remove libdb in the best case in Fedora 35. And time between F33 and F35 we would like to use for discussion about solution, which could transfer existing libdb databases to other and try to find solution for components which supports only libdb.
 <!-- What happens to systems that have had a previous versions of Fedora installed and are updated to the version containing this change? Will anything require manual configuration or data migration? Will any existing functionality be no longer supported? -->
 <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 <!-- This does not need to be a full-fledged document. Describe the dimensions of tests that this change implementation is expected to pass when it is done.  If it needs to be tested with different hardware or software configurations, indicate them.  The more specific you can be, the better the community testing can be.
@@ Line 117: / Line 109: @@
 <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 == User Experience ==
 There is no change for users. Package is marked only as deprecated package and behaves as before.
 <!-- If this change proposal is noticeable by users, how will their experiences change as a result?
@@ Line 132: / Line 121: @@
   - Green has been scientifically proven to be the most relaxing color. The move to a default background color of green with green text will result in Fedora users being the most relaxed users of any operating system.
 -->
 == Dependencies ==
 *Libdb has many dependencies:
@@ Line 198: / Line 186: @@
 *xemacs
 <!-- What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this change depends?  In other words, completion of another change owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate?  Other upstream projects like the kernel (if this is not a kernel change)? -->
 == Contingency Plan ==
@@ Line 215: / Line 202: @@
 <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 There is no upstream documentation, but [[User:Pkubat/Draft_-_Removing_BerkeleyDB_from_Fedora|here]] is a list of dependencies with some useful comments and [[User:Pkubat/BerkeleyDB_alternatives|here]] some possible alternatives.
 == Release Notes ==

Search

Changes/Libdb deprecated: Difference between revisions