pkg info --required-by db5

byrnejb

byrnejb

I receive this message following pkg upgrades:
Code: 
Message from db5-5.3.28_9:

--
===>   NOTICE:

The db5 port currently does not have a maintainer. As a result, it is
. . .

This port is deprecated; you may wish to reconsider installing it:
EOLd, potential security issues, maybe use db18 instead.
It is scheduled to be removed on or after 2022-06-30.
. . .

I check for dependencies (which uses the --required-by option) and see this:
Code: 
pkg info --required-by db5
db5-5.3.28_9:
    apr-1.7.0.1.6.1_2

But, when I go to remove it I see this:
Code: 
pkg remove db5
Checking integrity... done (0 conflicting)
Deinstallation has been requested for the following 5 packages (of 0 packages in the universe):

Installed packages to be REMOVED:
    apr: 1.7.0.1.6.1_2
    db5: 5.3.28_9
    p5-subversion: 1.14.2
    serf: 1.3.9_6
    subversion: 1.14.2_2

Number of packages to be removed: 5

The operation will free 75 MiB.

Proceed with deinstalling packages? [y/N]:

Why are not all the packages that will be removed along with db5 reported with pkg info --required-by
 
Because it only lists direct dependencies. Then you can run pkg info --required-by apr to see what depends on apr, and so on.
 
It seems somewhat counterintuitive, but package dependencies form a more complex web. There are other packages dependant on db5; in effect you're going to pull the rug out from under them (so they will be deleted as well):
Code: 
# pkg rall-depends subversion
serf-1.3.9_6
utf8proc-2.8.0
expat-2.5.0
gnupg-2.3.8
gettext-runtime-0.21.1
apr-1.7.0.1.6.1_2
sqlite3-3.40.1,1
liblz4-1.9.4,1
# pkg rall-depends serf
apr-1.7.0.1.6.1_2
# pkg rall-depends apr
expat-2.5.0
gdbm-1.23
db5-5.3.28_9
Alternatively to your command you could issue a dry run: pkg delete -n db5

However, this leaves quite some packages depending on db5.
 
On my system, libreoffice is the biggest "offender" of needing db5.
Code: 
root@FBSDNUC:~ # pkg info -r db5
db5-5.3.28_9:
    redland-1.0.17_4
    apr-1.7.0.1.6.1_2
root@FBSDNUC:~ # pkg info -r redland
redland-1.0.17_4:
    libreoffice-7.4.4.2
root@FBSDNUC:~ # pkg info -r apr
apr-1.7.0.1.6.1_2:
    libreoffice-7.4.4.2
    serf-1.3.9_6
root@FBSDNUC:~ # pkg info -r serf
serf-1.3.9_6:
    libreoffice-7.4.4.2
 
This issue has all ingredients for a never ending story.

PRs have been filed:

PR 261523
PR 261525
PR 263123

Reading these PRs is great entertainment - unfortunately.

It is a symptom of a shrinking base of FreeBSD Ports maintainers. Only a few get applauded loudly when entering the careening ship, while a larger number gets silently off board.

May I ask what is being done for attracting new maintainers who stay “committed to the community” for a longer term? Do we offer classes, webinars etc. for educating willing people or are “we” still better in scaring those having served long time?
 
Some linux distro's just dropped BerkeleyDB for another database...
Why not use kyotocabinet ?
At least the password db in freebsd is already db18 ...
 
Alain De Vos said:
Isn't it time to drop the dead monkey...
Click to expand...
Nope. DB1.85 is dead simple, still efficient for the things it CAN do. It doesn't offer transactions nor thread-safety, but none of this is needed for the system databases. It's under original BSD license and very small, so perfect for inclusion in the libc of a BSD system.
 
You must log in or register to reply here.
Back
Top