launchpad-users team mailing list archive

["Chris Coulson" <chrisccoulson@xxxxxxxxxxxxxx>]

2009/1/20 shirish <shirishag75@xxxxxxxxx>

> Hi all,
>  I made a bug-report
>
> https://bugs.edge.launchpad.net/ubuntu/+source/apt-xapian-index/+bug/318632
>
> which was made to be a duplicate of this bug
>
> https://bugs.edge.launchpad.net/bugs/263187
>
> It has the following template/wording which I find
>
> a. uncomfortable
> b. not helpful at all
>
>
> [quote]
>
> Not allowed here
>
> Sorry, you don't have permission to access this page.
>
> You are logged in as Shirish Agarwal.
>
> [/quote]
>
> Now I don't understand is
>
> a. Why has it got forbidden.
> b.  Even if the bug has some privacy or some other issue (meaning some
> part of the bug which canonical wants to protect for some reason)
>
> there may be other parts in the bug which could perhaps be opened up
> so people could have some idea of what happened and what's being done
> about the same.
>
> So my question becomes two :-
>
> a. Is it possible to break a bug into a public as well as private
> (part of the bug) or anywhere in the roadmap?
>
> b. does anybody know why that bug is forbidden?
>
> Feel free to answer b. offlist if so desired.
> --
>          Regards,
>          Shirish Agarwal
>  My quotes in this email licensed under CC 3.0
> http://creativecommons.org/licenses/by-nc/3.0/
> http://flossexperiences.wordpress.com
> 065C 6D79 A68C E7EA 52B3  8D70 950D 53FB 729A 8B17
>
> _______________________________________________
> Mailing list: https://launchpad.net/~launchpad-users<https://launchpad.net/%7Elaunchpad-users>
> Post to     : launchpad-users@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~launchpad-users<https://launchpad.net/%7Elaunchpad-users>
> More help   : https://help.launchpad.net/ListHelp
>

Hi,

By default, all Apport crash reports are made private. This is because they
might contain confidential or sensitive information in the files that are
attached. Usually, a bug triager will check the report for such information
before deciding whether to make it public or not. That hadn't happened with
that report yet, as it appears nobody has looked at it. I've made it public
for you though.

Regards
Chris