2
0
mirror of https://gitlab.com/apparmor/apparmor synced 2025-08-21 17:47:10 +00:00

docs: update documentation to point bug reporting to gitlab

Move suggested bug reporting from launchpad to gitlab

Signed-off-by: John Johansen <john.johansen@canonical.com>
Acked-by: Steve Beattie <steve.beattie@canonical.com>
This commit is contained in:
John Johansen 2020-05-02 20:40:55 -07:00
parent 7ca90ab637
commit c386d93581
38 changed files with 48 additions and 49 deletions

View File

@ -35,14 +35,13 @@ and questions to the
[AppArmor mailing list](https://lists.ubuntu.com/mailman/listinfo/apparmor).
Bug reports can be filed against the AppArmor project on
[launchpad](https://bugs.launchpad.net/apparmor) or reported to the mailing
[GitLab](https://gitlab.com/apparmor/apparmor/-/issues) or reported to the mailing
list directly for those who wish not to register for an account on
launchpad. See the
GitLab. See the
[wiki page](https://gitlab.com/apparmor/apparmor/wikis/home#reporting-bugs)
for more information.
Security issues can be filed as security bugs on launchpad
or directed to `security@apparmor.net`. Additional details can be found
Security issues can be filed in GitLab by opening up a new [issue](https://gitlab.com/apparmor/apparmor/-/issues) and selecting the tick box ```This issue is confidential and should only be visible to team members with at least Reporter access.``` or directed to `security@apparmor.net`. Additional details can be found
in the [wiki](https://gitlab.com/apparmor/apparmor/wikis/home#reporting-security-vulnerabilities).
@ -58,9 +57,9 @@ The AppArmor userspace tools do not collect information on the system user beyon
Users may submit information as part of an email, bug report or merge request, etc. and that will be recorded as part of the mailing list, bug/issue tracker, or code repository but only as part of a user initiated action.
The AppArmor project does not collect information from contributors beyond their interactions with the AppArmor project, code, and community. However contributors are subject to the terms and conditions and privacy policy of the individual platforms (currently GitLab and LaunchPad) should they choose to contribute through those platforms. And those platforms may collect data on the user that the AppArmor project does not.
The AppArmor project does not collect information from contributors beyond their interactions with the AppArmor project, code, and community. However contributors are subject to the terms and conditions and privacy policy of the individual platforms (currently GitLab) should they choose to contribute through those platforms. And those platforms may collect data on the user that the AppArmor project does not.
Currently both GitLab an LaunchPad require a user account to submit patches or report bugs and issues. If a contributor does not wish to create an account for these platforms the mailing list is available. Membership in the list is not required. Content from non-list members will be sent to moderation, to ensure that it is on topic, so there may be a delay in choosing to interact in this way.
Currently GitLab requires a user account to submit patches or report bugs and issues. If a contributor does not wish to create an account for these platforms the mailing list is available. Membership in the list is not required. Content from non-list members will be sent to moderation, to ensure that it is on topic, so there may be a delay in choosing to interact in this way.
-------------

View File

@ -94,7 +94,7 @@ if any unexpected error or condition is encountered.
=head1 BUGS
If you find any bugs, please report them at
L<https://bugs.launchpad.net/apparmor/+filebug>.
L<https://gitlab.com/apparmor/apparmor/-/issues>.
=head1 SEE ALSO

View File

@ -83,7 +83,7 @@ aa-exec.
=head1 BUGS
If you find any bugs, please report them at
L<https://bugs.launchpad.net/apparmor/+filebug>.
L<https://gitlab.com/apparmor/apparmor/-/issues>
=head1 SEE ALSO

View File

@ -144,7 +144,7 @@ policy from the apparmor module. It uses the /proc filesystem to determine
which processes are confined and so is susceptible to race conditions.
If you find any additional bugs, please report them at
L<https://bugs.launchpad.net/apparmor/+filebug>.
L<https://gitlab.com/apparmor/apparmor/-/issues>.
=head1 SEE ALSO

View File

@ -135,7 +135,7 @@ may not work correctly. For Apache 2.4 users, you should enable the mpm_prefork
module.
There are likely other bugs lurking about; if you find any, please report
them at L<https://bugs.launchpad.net/apparmor/+filebug>.
them at L<https://gitlab.com/apparmor/apparmor/-/issues>.
=head1 SEE ALSO

View File

@ -1,3 +1,3 @@
What little documentation exists is in include/aalogparse.h.
Please file bugs using https://bugs.launchpad.net/apparmor/+filebug
Please file bugs using https://gitlab.com/apparmor/apparmor/-/issues

View File

@ -248,7 +248,7 @@ The output when run:
=head1 BUGS
None known. If you find any, please report them at
L<https://bugs.launchpad.net/apparmor/+filebug>. Note that
L<https://gitlab.com/apparmor/apparmor/-/issues>. Note that
aa_change_hat(2) provides no memory barriers between different areas of a
program; if address space separation is required, then separate processes
should be used.

View File

@ -196,7 +196,7 @@ used (in addition to the one for 'i_cant_be_trusted_anymore', above):
=head1 BUGS
None known. If you find any, please report them at
L<https://bugs.launchpad.net/apparmor/+filebug>. Note that using
L<https://gitlab.com/apparmor/apparmor/-/issues>. Note that using
aa_change_profile(2) without execve(2) provides no memory barriers between
different areas of a program; if address space separation is required, then
separate processes should be used.

View File

@ -157,7 +157,7 @@ before exiting in libapparmor version 2.12 and newer.
=head1 BUGS
None known. If you find any, please report them at
L<https://bugs.launchpad.net/apparmor/+filebug>.
L<https://gitlab.com/apparmor/apparmor/-/issues>.
=head1 SEE ALSO

View File

@ -115,7 +115,7 @@ The apparmor filesystem mount could not be found
=head1 BUGS
None known. If you find any, please report them at
L<https://bugs.launchpad.net/apparmor/+filebug>.
L<https://gitlab.com/apparmor/apparmor/-/issues>.
=head1 SEE ALSO

View File

@ -127,7 +127,7 @@ confinement data.
=head1 BUGS
None known. If you find any, please report them at
L<https://bugs.launchpad.net/apparmor/+filebug>.
L<https://gitlab.com/apparmor/apparmor/-/issues>.
=head1 SEE ALSO

View File

@ -156,7 +156,7 @@ errno before exiting in libapparmor version 2.12 and newer.
=head1 BUGS
None known. If you find any, please report them at
L<https://bugs.launchpad.net/apparmor/+filebug>.
L<https://gitlab.com/apparmor/apparmor/-/issues>.
=head1 SEE ALSO

View File

@ -170,7 +170,7 @@ before exiting in libapparmor version 2.12 and newer.
=head1 BUGS
None known. If you find any, please report them at
L<https://bugs.launchpad.net/apparmor/+filebug>.
L<https://gitlab.com/apparmor/apparmor/-/issues>.
=head1 SEE ALSO

View File

@ -123,7 +123,7 @@ query and can change at any point in the future.
=head1 BUGS
None known. If you find any, please report them at
L<https://bugs.launchpad.net/apparmor/+filebug>.
L<https://gitlab.com/apparmor/apparmor/-/issues>.
=head1 SEE ALSO

View File

@ -63,7 +63,7 @@ on error.
=head1 BUGS
None known. If you find any, please report them at
L<https://bugs.launchpad.net/apparmor/+filebug>.
L<https://gitlab.com/apparmor/apparmor/-/issues>.
=head1 SEE ALSO

View File

@ -208,7 +208,7 @@ The output when run:
=head1 BUGS
None known. If you find any, please report them at
L<https://bugs.launchpad.net/apparmor/+filebug>. Note that using
L<https://gitlab.com/apparmor/apparmor/-/issues>. Note that using
aa_stack_profile(2) without execve(2) provides no memory barriers between
different areas of a program; if address space separation is required, then
separate processes should be used.

View File

@ -31,7 +31,7 @@ aa-teardown unloads all AppArmor profiles
=head1 BUGS
If you find any bugs, please report them at
L<https://bugs.launchpad.net/apparmor/+filebug>.
L<https://gitlab.com/apparmor/apparmor/-/issues>.
=head1 SEE ALSO

View File

@ -404,7 +404,7 @@ All other options override previously set values.
=head1 BUGS
If you find any bugs, please report them at
L<https://bugs.launchpad.net/apparmor/+filebug>.
L<https://gitlab.com/apparmor/apparmor/-/issues>.
=head1 SEE ALSO

View File

@ -39,7 +39,7 @@ working as you expect.
Feedback on these unsupported profiles is welcomed; any
contributions for this directory should be clearly licensed
-- we recommend using the GPL. Please submit bug reports to the
AppArmor issue tracker at https://bugs.launchpad.net/apparmor/+filebug
AppArmor issue tracker at https://gitlab.com/apparmor/apparmor/-/issues
Please submit proposed changes as a merge request at
https://gitlab.com/apparmor/apparmor/merge_requests
Alternately, you may contact us via the apparmor@lists.ubuntu.com

View File

@ -32,7 +32,7 @@ The I<--remove> option can be used to remove the audit mode for the profile.
=head1 BUGS
If you find any bugs, please report them at
L<https://bugs.launchpad.net/apparmor/+filebug>.
L<https://gitlab.com/apparmor/apparmor/-/issues>.
=head1 SEE ALSO

View File

@ -56,7 +56,7 @@ the newly generated minimal AppArmor profile.
This program does not perform full static analysis of executables, so
the profiles generated are necessarily incomplete. If you find any bugs,
please report them at
L<https://bugs.launchpad.net/apparmor/+filebug>.
L<https://gitlab.com/apparmor/apparmor/-/issues>.
=head1 SEE ALSO

View File

@ -32,7 +32,7 @@ together and removes all comments from the file.
=head1 BUGS
If you find any bugs, please report them at
L<https://bugs.launchpad.net/apparmor/+filebug>.
L<https://gitlab.com/apparmor/apparmor/-/issues>.
=head1 SEE ALSO

View File

@ -49,7 +49,7 @@ Note that 'deny' rules will be enforced even in complain mode.
=head1 BUGS
If you find any bugs, please report them at
L<https://bugs.launchpad.net/apparmor/+filebug>.
L<https://gitlab.com/apparmor/apparmor/-/issues>.
=head1 SEE ALSO

View File

@ -35,8 +35,8 @@ displays a short usage statement.
=head1 BUGS
None. Please report any you find to Launchpad at
L<https://bugs.launchpad.net/apparmor/+filebug>.
None. Please report any you find to gitlab at
L<https://gitlab.com/apparmor/apparmor/-/issues>.
=head1 SEE ALSO

View File

@ -49,7 +49,7 @@ this behavior.
=head1 BUGS
If you find any bugs, please report them at
L<https://bugs.launchpad.net/apparmor/+filebug>.
L<https://gitlab.com/apparmor/apparmor/-/issues>.
=head1 SEE ALSO

View File

@ -314,8 +314,8 @@ To output a manifest file based on aa-easyprof arguments:
=head1 BUGS
If you find any additional bugs, please report them to Launchpad at
L<https://bugs.launchpad.net/apparmor/+filebug>.
If you find any additional bugs, please report them to GitLab at
L<https://gitlab.com/apparmor/apparmor/-/issues>.
=head1 SEE ALSO

View File

@ -51,7 +51,7 @@ utility must be run to change this behavior.
=head1 BUGS
If you find any bugs, please report them at
L<https://bugs.launchpad.net/apparmor/+filebug>.
L<https://gitlab.com/apparmor/apparmor/-/issues>.
=head1 SEE ALSO

View File

@ -81,7 +81,7 @@ and any other profiles that were generated, into enforce mode and exit.
=head1 BUGS
If you find any bugs, please report them at
L<https://bugs.launchpad.net/apparmor/+filebug>.
L<https://gitlab.com/apparmor/apparmor/-/issues>.
=head1 SEE ALSO

View File

@ -165,7 +165,7 @@ user wants to quit. See capability(7) for details.
=head1 BUGS
If you find any bugs, please report them at
L<https://bugs.launchpad.net/apparmor/+filebug>.
L<https://gitlab.com/apparmor/apparmor/-/issues>.
=head1 SEE ALSO

View File

@ -26,7 +26,7 @@ B<aa-mergeprof>
=head1 BUGS
If you find any bugs, please report them at
L<https://bugs.launchpad.net/apparmor/+filebug>.
L<https://gitlab.com/apparmor/apparmor/-/issues>.
=head1 SEE ALSO

View File

@ -109,8 +109,8 @@ the deprecated ~/.apparmor/notify.conf if it exists):
B<aa-notify> needs to be able to read the logfiles containing the
AppArmor DENIED messages.
If you find any additional bugs, please report them to Launchpad at
L<https://bugs.launchpad.net/apparmor/+filebug>.
If you find any additional bugs, please report them to Gitlab at
L<https://gitlab.com/apparmor/apparmor/-/issues>.
=head1 SEE ALSO

View File

@ -41,8 +41,8 @@ dry run; only prints the names of profiles that would be removed
=head1 BUGS
None. Please report any you find to Launchpad at
L<https://bugs.launchpad.net/apparmor/+filebug>.
None. Please report any you find to Gitlab at
L<https://gitlab.com/apparmor/apparmor/-/issues>.
=head1 SEE ALSO

View File

@ -179,8 +179,8 @@ Restarting the sandbox will resolve the issue.
=head1 BUGS
If you find any bugs, please report them to Launchpad at
L<https://bugs.launchpad.net/apparmor/+filebug>.
If you find any bugs, please report them to Gitlab at
L<https://gitlab.com/apparmor/apparmor/-/issues>.
=head1 SEE ALSO

View File

@ -69,7 +69,7 @@ program is unsuitable for forensics use and is provided only as an aid
to profiling all network-accessible processes in the lab.
If you find any bugs, please report them at
L<https://bugs.launchpad.net/apparmor/+filebug>.
L<https://gitlab.com/apparmor/apparmor/-/issues>.
=head1 SEE ALSO

View File

@ -41,7 +41,7 @@ def handle_exception(*exc_info):
cgitb_hook = cgitb.Hook(display=1, file=file, format='text', context=10)
cgitb_hook.handle(exc_info)
file.write('Please consider reporting a bug at https://bugs.launchpad.net/apparmor/\n')
file.write('Please consider reporting a bug at https://gitlab.com/apparmor/apparmor/-/issues\n')
file.write('and attach this file.\n')
print(''.join(traceback.format_exception(*exc_info)), file=sys.stderr)
@ -49,7 +49,7 @@ def handle_exception(*exc_info):
print('An unexpected error occoured!', file=sys.stderr)
print('', file=sys.stderr)
print('For details, see %s' % path, file=sys.stderr)
print('Please consider reporting a bug at https://bugs.launchpad.net/apparmor/', file=sys.stderr)
print('Please consider reporting a bug at https://gitlab.com/apparmor/apparmor/-/issues', file=sys.stderr)
print('and attach this file.', file=sys.stderr)
def enable_aa_exception_handler():

View File

@ -103,7 +103,7 @@ Lines starting with # are comments and are ignored.
=head1 BUGS
If you find any bugs, please report them at
L<https://bugs.launchpad.net/apparmor/+filebug>.
L<https://gitlab.com/apparmor/apparmor/-/issues>.
=head1 SEE ALSO

View File

@ -70,7 +70,7 @@ setup (name='apparmor',
long_description='Python libraries for AppArmor utilities',
author='AppArmor Developers',
author_email='apparmor@lists.ubuntu.com',
url='https://launchpad.net/apparmor',
url='https://gitlab.com/apparmor/apparmor',
license='GPL-2',
cmdclass={'install': Install},
package_dir={'apparmor': 'staging'},

View File

@ -48,7 +48,7 @@ but it may help you understand your profiles better.
B<apparmor.vim> does not properly detect dark versus light backgrounds.
Patches accepted. If you find any bugs, please report them at
L<https://bugs.launchpad.net/apparmor/+filebug>.
L<https://gitlab.com/apparmor/apparmor/-/issues>.
=head1 SEE ALSO