Can someone update ap22-mod_security to list/depend on db48 package? [root@u163 13:14:14 /]# pkg which /usr/local/lib/mod_security2.so /usr/local/lib/mod_security2.so was installed by package ap22-mod_security-2.7.7_3 [root@u163 13:14:18 /]# ldd /usr/local/lib/mod_security2.so | grep db libdb-4.8.so.0 => /usr/local/lib/libdb-4.8.so.0 (0x8018f0000) [root@u163 13:14:32 /]# pkg which /usr/local/lib/libdb-4.8.so.0 /usr/local/lib/libdb-4.8.so.0 was installed by package db48-4.8.30.0_2 so if you try to remove db48, it will complain that ap22-mod_security depends on it. Thanks!
The dependency is pulled in via apr which depends on BerkeleyDB. If pkg complains, the dependency works as intended.
Well, probably I wasn't specific, what I meant is that, removing db48 package via "pkg remove db48" should warn that there's packages, which are still depend on it, for example, ap22-mod_security (which is indeed has libdb-4.8.so.0 as required): [root@u163 14:51:01 /]# pkg info ap22-mod_security ap22-mod_security-2.7.7_3 Name : ap22-mod_security Version : 2.7.7_3 Installed on : Tue Jun 24 16:32:50 MSK 2014 Origin : www/mod_security Architecture : freebsd:10:x86:64 Prefix : /usr/local Categories : www security Licenses : APACHE20 Maintainer : walter@lifeforms.nl WWW : http://www.modsecurity.org/ Comment : Intrusion detection and prevention engine Options : LUA : off MLOGC : off Shared Libs required: libxml2.so.2 libpcre.so.3 libgdbm.so.4 libexpat.so.6 libdb-4.8.so.0 libaprutil-1.so.0 libapr-1.so.0 but currently, removing db48 does not have this warning: [root@u163 14:52:02 /]# pkg remove db48 Checking integrity... done (0 conflicting) Deinstallation has been requested for the following 1 packages (of 0 packages in the universe): Installed packages to be REMOVED: db48-4.8.30.0_2 The operation will free 12 MB. Proceed with deinstalling packages? [y/N]: PS: taking it to the apr side, apr has libdb-5.3.so.0 in the requirements, which is provided by db5 (db5-5.3.28_1) package. Thanks.
Did you install mod_security from ports or packages? It looks like you upgraded BerkeleyDB from 4.8 to 5.3 and forgot to rebuild mod_security
Installed from ports with "pkg install", I'm still using apache22-2.2.27_6
so, if ap22-mod_security lists libdb-4.8.so.0 as required library, should this bug filled against pkg utility? thanks.
I've looked into this, but can't seem to reproduce. Even if I forcibly remove and reinstall db, the dependency is there. -- # sudo pkg remove db5 Checking integrity... done (0 conflicting) Deinstallation has been requested for the following 7 packages (of 0 packages in the universe): Installed packages to be REMOVED: db5-5.3.28_2 apr-1.5.1.1.5.4 (depends on db5-5.3.28_2) serf-1.3.8 (depends on db5-5.3.28_2) subversion-1.8.10_3 (depends on db5-5.3.28_2) apache24-2.4.10_2 (depends on db5-5.3.28_2) mod_php56-5.6.3 (depends on db5-5.3.28_2) ap24-mod_security-2.7.7_3 (depends on db5-5.3.28_2) The operation will free 93 MB. -- Now I'm not an experienced porter, so I don't know if I should add a hard dependency on db in the Makefile. I'm preparing a new version for ModSecurity 2.9.0 so this would be a good time to address it.
OP, have you had any more trouble? Since I couldn't reproduce on many machines, I'm inclined to think this was a prior pkg database corruption, but since pkg has moved on immensely in the meantime, it's probably not realistic to get to the bottom of it, and I'd prefer to close this PR.
I think we can close this bug (fixed/invalid?!), since I've upgraded freebsd to latest version and don't have any problems so far. Thanks.
Closing per submitter feedback.