Your message dated Mon, 25 May 2020 12:38:08 +0200
with message-id <87blmc9u5r.fsf@manticora>
and subject line Re: Bug#928233: apparmor-profiles-extra: Description omits 
experimental status (?)
has caused the Debian Bug report #928233,
regarding apparmor-profiles-extra: Description omits experimental status (?)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
928233: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928233
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: apparmor-profiles,apparmor-profiles-extra
Severity: minor

Dear maintainer:

I'd like to have the following descriptions more consistent
with each other:

Package: apparmor-profiles
Description: experimental profiles for AppArmor security policies

Package: apparmor-profiles-extra
Description: Extra profiles for AppArmor Security policies


Apparently, profiles in apparmor-profiles are more stable and tested,
but they are described as "experimental" while the ones in
apparmor-profiles-extra are not.

Would it make sense to change the second description so that it reads
"Extra experimental profiles" or "even more experimental profiles"?

(Or, alternatively, remove "experimental" from apparmor-profiles
since that's already in the extended description).

Thanks.

--- End Message ---
--- Begin Message ---
Hi,

10 months later, I'm closing this bug since it was apparently opened
based on a misconception, and in its current state it is
not actionable.

Still, I do remain interested in the answer to this question:

intrigeri (2019-07-17):
> So I'll treat this bug report as a potential documentation issue:
>
> I'm curious what made you think otherwise — is there documentation we
> need to update/fix somewhere?

Thanks,
cheers!

--- End Message ---

Reply via email to