[apparmor] 2.8 Nominations

Christian Boltz apparmor at cboltz.de
Thu Jan 3 11:25:05 UTC 2013


Am Mittwoch, 2. Januar 2013 schrieb Steve Beattie:
> On Wed, Jan 02, 2013 at 04:27:33PM -0800, Steve Beattie wrote:
> > On Tue, Dec 18, 2012 at 11:21:20PM +0100, Christian Boltz wrote:

> Sorry about that, I was both on holiday and ill for most of that week
> of December.

Sounds like a bad combination...

> That leaves the following that I nominated for 2.8.1:
> >   2079 - libapparmor - add pkgconfig support

Assuming it won't break anything - no objections.

However I have a packaging question ;-)
The .spec I'm using contains (for historical reasons[tm] - at least I 
doubt I added it myself)

    # re-define _libdir to /lib or /lib64
    %define _libdir /%{_lib}

This means the *.pc file ends up in /lib*/pkgconfig - but all *.pc files 
typically seem to be in /usr/lib*/pkgconfig/.

The easiest way to fix this would be not to re-define _libdir. This 
would also mean the following files would move to /usr/lib*/:

-rw-r--r-- 1 root root 56862 23. Dez 18:03 /lib64/libapparmor.a
lrwxrwxrwx 1 root root    20 25. Dez 19:59 /lib64/libapparmor.so -> libapparmor.so.1.0.2
lrwxrwxrwx 1 root root    20 25. Dez 16:47 /lib64/libapparmor.so.1 -> libapparmor.so.1.0.2
-rwxr-xr-x 1 root root 47155 23. Dez 18:03 /lib64/libapparmor.so.1.0.2
-rw-r--r-- 1 root root 12472 23. Dez 18:03 /lib64/libimmunix.a
lrwxrwxrwx 1 root root    19 25. Dez 19:59 /lib64/libimmunix.so -> libimmunix.so.1.0.2
lrwxrwxrwx 1 root root    19 25. Dez 16:47 /lib64/libimmunix.so.1 -> libimmunix.so.1.0.2
-rwxr-xr-x 1 root root 18391 23. Dez 18:03 /lib64/libimmunix.so.1.0.2

Which side effects would moving those libs cause?
Or is there a way to have the libs in /lib*/ and the *.pc file in /usr/lib*/?

If it causes too many problems, I'd prefer to delay it to 3.0.
(Maybe I'll do an online update to 2.8.1 for openSUSE 12.2 - but only
if I can use the same package that I also commit to Factory ;-)

BTW: I have packages with a trunk snapshot in 
(not tested yet)

> > I'm more ambivalent about the following trunk commits. I'm
> > nominating
> > them for 2.8, but could be convinced to that they should not be
> > included:
> >   2069 - profiles - install extras into
> >   /usr/share/apparmor/extra-profiles/ 

I doubt we should do this in a minor release. The extra profiles were in 
/etc for years, so delaying the move to the 3.0 release won't hurt.
OTOH, confusing users by moving files around in a minor release _will_ 

(But you should of course backport the updated mailinglist address in 
the extra profiles README, which was part of that commit IIRC.)

> >   2078 - profiles - add winbindd profile

I won't strongly object, but introducing a new profile in a bugfix 
release might not be the best idea. Yes, the profile works on openSUSE
without problems, but it might still cause problems on other distributions
(for example, if they use different /var paths for the samba stuff).

> > Christian, if you'd like to do the merge for the ones you nominated
> > yourself, that's fine by me, but if you'd rather I do them while I'm
> > merging my nominations that are acceptable to others, that's cool,
> > too.
> This offer still stands.

Did you really think a lazybone like me will say "no" if someone offers 
to do the work? ;-)  I'll be happy if you merge all patches ;-)


Christian Boltz
> ....Ommmmmm    ....Ommmmmm    .....Ommmmmm
> Pendel ----Pendel-----Pendel------
Mensch Axel: Sonst machst Du das doch mit der Glaskugel. Ist die schon
wieder in der Spülmaschine? [Axel Lindlau u. Volker Kroll in suse-linux]

More information about the AppArmor mailing list