[apparmor] Bug#800132: [pkg-apparmor] Bug#800132: libapparmor-dev: arch-dependent file in "Multi-Arch: same" package

[intrigeri]

Hi Tyler,

[this started as https://bugs.debian.org/800132, but now redirecting
upstream; hence, full quoting this time.]

Christian Boltz wrote (27 Sep 2015 10:20:06 GMT) :
> Am Sonntag, 27. September 2015 schrieb Jakub Wilk:
>> libapparmor-dev is marked as "Multi-Arch: same", but the following
>> file is architecture-dependent:
>> 
>> /usr/share/man/man2/aa_getcon.2.gz
>> 
>> An example diff between i386 and amd64 (after ungzipping) is attached.

> The aa_getcon manpage is NOT arch-dependent - the difference is just a 
> timestamp/date.

> pod2man includes the last modification date of the pod file in the 
> generated manpage.

> Thanks to the libapparmor-mention-dbus-method-in-getcon-man.patch, 
> aa_getcon.pod gets a new timestamp on build (when applying the patch).

> The easiest solution is to submit the patch upstream, so that Debian 
> doesn't have anything that touches the aa_getcon.pod timestamp ;-)

Good catch, thanks :)

We pulled this patch from the Ubuntu packaging.

The patch [1] header says:

 Description: Document D-Bus getcon method in aa_getcon man page
  .
  This patch should be submitted to upstream AppArmor after the AppArmor
  mediation patches are submitted to upstream D-Bus.
 Author: Tyler Hicks
 Forwarded: no

[1] https://sources.debian.net/patches/patch/apparmor/2.10-2/libapparmor-mention-dbus-method-in-getcon-man.patch/

The blocker (AppArmor support in upstream D-Bus) is now gone, right?
Tyler, do you think this patch should now go upstream, or is there
anything that needs to be done first?

Cheers,
-- 
intrigeri