can't add comments to my own bug

Alex Lancaster alexl at users.sourceforge.net
Sun Mar 9 22:25:40 UTC 2008


>>>>> "JS" == Jon Stanley  writes:

JS> On Sun, Mar 9, 2008 at 7:01 AM, Alex Lancaster
JS> <alexl at users.sourceforge.net> wrote:

>  Surely you should always be able to add (at least a comment) to a bug
>> if you are the reporter, even if it's another product:

JS> Nah, lovely bugzilla product security there.

Looks like it was moved to a different product after I filed.
Nonetheless it seems odd that a reporter can't even comment on their
own bug, otherwise how are you supposed to provide feedback about
whether it's fixed?

>> https://bugzilla.redhat.com/show_bug.cgi?id=213764

JS> This should probably be a ticket in the infrastructure Trac
JS> instance these days, if it's not already - but it looks like Jesse
JS> fixed it??

Unfortunately not quite fixed, should I open up a ticket on
infrastructure Trac (URL?).  Here's the comment I was trying to add:

 > I have just committed code to pungi to re-enable repoview creation.
 > Repoview recently had some improvements made that will make it
 > easier for mirrors to digest and to shorten the time it takes to
 > generate content.
 
 Thanks it looks like, repoview is now enabled for Fedora 8 it appears:
 
 http://download.fedora.redhat.com/pub/fedora/linux/releases/8/Everything/i386/os/repoview/
 
 (but not for Fedora 7 for some reason)
 
 however it doesn't include updates, so it's not very useful for
 finding packages that have been added after the release.
 
 > Next I will be modifying the rawhide compose process to also have
 > repoview content.
 
 Seems this isn't enabled yet, no rawhide repoview where you might
 expect it:
 
 http://download.fedora.redhat.com/pub/fedora/linux/development/i386/os/
 




More information about the fedora-devel-list mailing list