[Bug 853661] New: apparmor_parser: spelling issue: cannot
https://bugzilla.novell.com/show_bug.cgi?id=853661 https://bugzilla.novell.com/show_bug.cgi?id=853661#c0 Summary: apparmor_parser: spelling issue: cannot Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: AppArmor AssignedTo: suse-beta@cboltz.de ReportedBy: ke@suse.com QAContact: qa-bugs@suse.de Found By: Documentation Blocker: --- During boot (IIRC), apparmor_parser (?) several times says something with "can not". But this should be spelled "cannot". -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=853661 https://bugzilla.novell.com/show_bug.cgi?id=853661#c1 Christian Boltz <suse-beta@cboltz.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |ke@suse.com --- Comment #1 from Christian Boltz <suse-beta@cboltz.de> 2013-12-04 23:55:27 CET --- I just had an interesting discussion about this on #apparmor with jjohansen ;-) and he argued both are correct, it's just that "cannot" is more common. http://www.alexfiles.com/cannot-vs-can-not/ says that they have a slightly different meaning, but that seems to be something debated between experts. After posting this link on #apparmor, sbeattie and sarnold joined the discussion, and it went into a quite funny english lesson. Thanks for giving a starting point ;-) Anyway, the more interesting part is - where do the messages you see come from? Grepping the AppArmor sources found some matches in comments and a match in the apparmor(7) manpage - but I didn't notice anything that could be printed to the user. To find out where your ;-) "can not" comes from - what's the full message you see? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=853661 https://bugzilla.novell.com/show_bug.cgi?id=853661#c2 Karl Eichwalder <ke@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|ke@suse.com | --- Comment #2 from Karl Eichwalder <ke@suse.com> 2013-12-05 08:55:34 CET --- Thanks for the English lesson ;) If you "cannot" find it in the aa sources, it is probably a systemd thingie. Feel free to set this bug to invalid or worksforme. I'll open a new bug, if I have better evidence (maybe, after the next boot...). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=853661 https://bugzilla.novell.com/show_bug.cgi?id=853661#c3 Christian Boltz <suse-beta@cboltz.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |UPSTREAM --- Comment #3 from Christian Boltz <suse-beta@cboltz.de> 2013-12-16 19:31:11 CET --- Actually I fixed something after your bugreport, but not what you reported ;-) As already indicated, the apparmor(7) manpage had one "can not", and while fixing it, we noticed that the whole section needed an update. My commit (bzr r2284) for updating the manpage had the title "can ?not fix apparmor.pod" *g* - and "can ?not" seems to become a running gag on #apparmor and the mailinglist ;-) I can ?not find something in the "resolution" field that would be the correct resolution for this kind of "bugreport <-> totally different, but still related, fix" relationship. I'll use UPSTREAM because that seems to be the closest match. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com