Bug 546462 – app-admin/logrotate links against libacl no matter what

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Bjarke Istrup Pedersen (RETIRED) 2015-04-13 14:21:43 UTC]

It seems like logrotate links against libacl no matter what, if libacl is installed.

I can see the WITH_ACL is passed to emake - this is wrong from what I can read in the INSTALL file, where it says it should be done when ./configure is being run (we don't run it, it seems).

Reproducible: Always

Steps to Reproduce:
1. emerge sys-apps/acl
2. USE="-acl" emerge logrotate
3. ldd /usr/sbin/logrotate
Actual Results:  
It links against libacl, even though the acl use flag is disabled.

Expected Results:  
It should only enable ACL support if the use flag is enabled.

This breaks logrotate, since it is not possible to use it without libacl being installed.

I'm compiling packages on one machine for use on another machine, which is how I found out, since the build machine has libacl installed, but the target machine does not (and should not).

[Comment 1 Chema Alonso Josa (RETIRED) 2015-04-16 12:48:57 UTC]

Yes, something is wrong with emake. I'll fix this in the following days.

Thanks for the report.

[Comment 2 Bjarke Istrup Pedersen (RETIRED) 2015-04-16 14:32:08 UTC]

Thanks :-)

[Comment 3 Chema Alonso Josa (RETIRED) 2015-04-21 09:26:41 UTC]

Fixed. Please test.

+*logrotate-3.8.9-r1 (21 Apr 2015)
+
+  21 Apr 2015; Chema Alonso <[e-mail]> +logrotate-3.8.9-r1.ebuild,
+  metadata.xml:
+  Bump to fix bug #485848 and bug #546462
+