FTBFS on lucid
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
AppArmor |
Fix Released
|
Critical
|
Jamie Strandboge | ||
apparmor (Ubuntu) |
Fix Released
|
Critical
|
Jamie Strandboge |
Bug Description
Binary package hint: apparmor
Several of the basic network tests fail on lucid:
simple_
simple_
simple_
Eg:
$ debuild -us -uc
... it fails ...
$ cd parser/tst
$ ../apparmor_parser -S -I `pwd`/simple_tests < ./simple_
../apparmor_parser: cannot use or update cache, disable, or force-complain via stdin
AppArmor parser error, line 7: Invalid network entry.
[1]
Looking at network_ok_2.sd, I then tried commented out the different 'network' rules, and found that only inet and inet6 would work. I then noticed that in 9.10, /usr/include/
Changed in apparmor: | |
status: | New → Confirmed |
Changed in apparmor (Ubuntu): | |
status: | New → Confirmed |
importance: | Undecided → Critical |
Changed in apparmor: | |
importance: | Undecided → Critical |
Changed in apparmor (Ubuntu): | |
assignee: | nobody → Jamie Strandboge (jdstrand) |
Changed in apparmor: | |
assignee: | nobody → Jamie Strandboge (jdstrand) |
status: | Confirmed → Triaged |
Changed in apparmor (Ubuntu): | |
status: | Confirmed → Triaged |
Changed in apparmor: | |
status: | Triaged → In Progress |
Changed in apparmor: | |
status: | In Progress → Fix Released |
Looking in parser/Makefile, we have: linux/socket. h AF_\\([ A-Z0-9_ ]\\+\\) [ \\t]\\+ \\([0-9] \\+\\)\ \(.*\\) \$$/#ifndef AF_\\1\\n# define AF_\\1 \\2\\n# endif\\ nAA_GEN_ NET_ENT( \"\\L\\ 1\", \\UAF_\\1)\\n/p" $< > $@ \\(AF_MAX\ \)[ \\t]\\+ \\([0-9] \\+\\)\ \(.*\\) \$$/#define AA_\\1 \\2\n/p" $< >> $@
af_names.h: /usr/include/
LC_ALL=C sed -n -e '/$(__FILTER)/d' -e "s/^\#define[ \\t]\\+
# define local AF_MAX which may differ from that of bits/socket.h
LC_ALL=C sed -n -e "s/^\#define[ \\t]\\+
cat $@
af_names.h is included in parser_misc. This fails on the new /usr/include/ linux/socket. h and also doesn't work with /usr/include/ bits/socket. h