Re: No "19" yet in Bugzilla version field

2013-02-07 Thread John Reiser
> Is there magic for bugs against 18 that are also bugs in 19 once branch > happens? I have participated in several bugzilla reports of this kind (bug in Fedora N remains unfixed as Fedora N+1 appears with "new" package) but I have not seen any "magic". The original reporter, or some person with

Re: No "19" yet in Bugzilla version field

2013-02-07 Thread Chris Murphy
On Feb 7, 2013, at 8:44 PM, Adam Williamson wrote: > > Right. Reports go against Rawhide till branching. Appropriate ones will be > magically transferred to 19 at branch time, I believe. Is there magic for bugs against 18 that are also bugs in 19 once branch happens? Chris Murphy -- test mai

Re: No "19" yet in Bugzilla version field

2013-02-07 Thread Adam Williamson
On 07/02/13 06:26 PM, Bruno Wolff III wrote: On Thu, Feb 07, 2013 at 20:47:34 -0500, "Clyde E. Kunkel" wrote: --- Comment #2 from Simon Green --- The Fedora team manage their Bugzilla product attributes directly. https://bugzilla.redhat.com/show_bug.cgi?id=908988 OK, Fedora team, punted

Fedora 16 updates-testing report

2013-02-07 Thread updates
The following Fedora 16 Security updates need testing: Age URL 58 https://admin.fedoraproject.org/updates/FEDORA-2012-20157/libproxy-0.4.11-1.fc16 6 https://admin.fedoraproject.org/updates/FEDORA-2013-1748/sssd-1.8.6-1.fc16 6 https://admin.fedoraproject.org/updates/FEDORA-2013-1713/l

Re: No "19" yet in Bugzilla version field

2013-02-07 Thread Bruno Wolff III
On Thu, Feb 07, 2013 at 20:47:34 -0500, "Clyde E. Kunkel" wrote: --- Comment #2 from Simon Green --- The Fedora team manage their Bugzilla product attributes directly. https://bugzilla.redhat.com/show_bug.cgi?id=908988 OK, Fedora team, punted over to you.:-) 19 hasn't branched yet. You p

Re: No "19" yet in Bugzilla version field

2013-02-07 Thread Clyde E. Kunkel
On 02/07/2013 08:47 PM, Clyde E. Kunkel wrote: --- Comment #2 from Simon Green --- The Fedora team manage their Bugzilla product attributes directly. https://bugzilla.redhat.com/show_bug.cgi?id=908988 OK, Fedora team, punted over to you.:-) I see closed as notabug since 19 only becomes ac

No "19" yet in Bugzilla version field

2013-02-07 Thread Clyde E. Kunkel
--- Comment #2 from Simon Green --- The Fedora team manage their Bugzilla product attributes directly. https://bugzilla.redhat.com/show_bug.cgi?id=908988 OK, Fedora team, punted over to you.:-) -- Regards, OldFart -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin

Failure to load images with gpicview, mirage in Rawhide

2013-02-07 Thread Steven I Usdansky
Rawhide, fully updated after being away for two weeks. I get a segfault when trying to load a jpg or png file in gpicview; mirage gives me a "Cannot load image" message in the status bar. No problems loading images in GIMP. Not sure which component is at fault. Ideas? -- test mailing list test@l

[Fedora QA] #341: X graphics Test Week for F19

2013-02-07 Thread Fedora QA
#341: X graphics Test Week for F19 --+ Reporter: martix| Owner: mholec@… Type: task | Status: new Priority: major | Milestone: Fedora 19 Component: Test Day | Version: Keywords:| Blocked By: Bloc

Re: Draft onboarding process changes

2013-02-07 Thread Rahul Sundaram
Hi On Thu, Feb 7, 2013 at 12:19 AM, Adam Williamson wrote: https://fedoraproject.org/**wiki/QA:Update_feedback_**guidelines. >> >> >> Ideally, bodhi should link to this >> > > It does. It's the first link under 'Welcome to bodhi

Re: [Fedora QA] #339: Gnome 3.8 Test Day

2013-02-07 Thread Fedora QA
#339: Gnome 3.8 Test Day ---+--- Reporter: martix| Owner: mholec@… Type: task | Status: new Priority: major | Milestone: Fedora 19 Component: Test Day |Version: Resolution:| Keywords: Blocked By:

[Fedora QA] #340: KDE 4.10 Test Day

2013-02-07 Thread Fedora QA
#340: KDE 4.10 Test Day --+ Reporter: martix| Owner: mholec@… Type: task | Status: new Priority: major | Milestone: Fedora 19 Component: Test Day | Version: Keywords:| Blocked By: Blocking:

Re: [Fedora QA] #339: Gnome 3.8 Test Day

2013-02-07 Thread Fedora QA
#339: Gnome 3.8 Test Day ---+--- Reporter: martix| Owner: mholec@… Type: task | Status: new Priority: major | Milestone: Fedora 19 Component: Test Day |Version: Resolution:| Keywords: Blocked By:

[Fedora QA] #339: Gnome 3.8 Test Day

2013-02-07 Thread Fedora QA
#339: Gnome 3.8 Test Day --+--- Reporter: martix| Owner: mholec@… Type: task | Status: new Priority: major | Milestone: Component: Blocker bug tracker page

[Fedora QA] #338: Request for F19 Network Manager Test Day

2013-02-07 Thread Fedora QA
#338: Request for F19 Network Manager Test Day --+ Reporter: martix| Owner: mholec@… Type: task | Status: new Priority: major | Milestone: Fedora 19 Component: Test Day | Version: Keywords:| Block

Re: Did gnome 3.7.5 break things for anyone else?

2013-02-07 Thread Bruno Wolff III
On Thu, Feb 07, 2013 at 10:57:03 -0500, Matthias Clasen wrote: - Original Message - It hadn't been gone in Fedora as of a couple of days ago. It's possible it went away with 3.7.5. Yes, the fallback session was dropped in gnome-session 3.7.5. What happened on your system ? Did you

Re: Did gnome 3.7.5 break things for anyone else?

2013-02-07 Thread Matthias Clasen
- Original Message - > It hadn't been gone in Fedora as of a couple of days ago. It's > possible > it went away with 3.7.5. Yes, the fallback session was dropped in gnome-session 3.7.5. What happened on your system ? Did you get the failwhale (that is what's supposed to happen if the sh

The heroes of Fedora 18 Final testing – Bugzilla

2013-02-07 Thread Kamil Paral
I have gathered user contribution statistics from Bugzilla regarding F18 Final (Beta->Final) period. Thank you everyone who contributed, the number of reporters is stunning. The full report is available at: https://kparal.wordpress.com/2013/02/04/the-heroes-of-fedora-18-final-testing-bugzilla/ -

Re: Proposing Blocker/Freeze Exception Bugs Through the Blocker Tracking App

2013-02-07 Thread Kamil Paral
> OK, I think its being my mistake... > Is the bug id section is to define which bug is the blocker/freeze > exception? > If so then my comment is wrong on my part. This is a good feedback. When I think about it, the label could be much clearer if we use "Proposed bug number" (or similar) instead