Re: Fedora 14 Beta Blocker Meeting :: Friday, 2010-09-10 @ 16:00 UTC (12 PM EDT)

2010-09-13 Thread John Poelstra 
John Poelstra said the following on 09/09/2010 05:19 PM Pacific Time:
> When: Friday, 2010-09-10 @ 16:00 UTC (12 PM EDT)
> Where: #fedora-bugzappers on irc.freenode.net
>
> Without these bugs fixed we can't compose the Fedora 14 Beta Release
> Candidate on 2010-09-16.
>


==
#fedora-bugzappers: Fedora 14 Beta Blocker Meeting
==


Meeting started by poelcat at 16:02:33 UTC. The full logs are available
at
http://meetbot.fedoraproject.org/fedora-bugzappers/2010-09-10/fedora-bugzappers.2010-09-10-16.02.log.html
.



Meeting summary
---
* roll call  (poelcat, 16:02:51)
   * attendees nirik adamw jlaska poelcat jsmith  (poelcat, 16:05:37)

* https://bugzilla.redhat.com/show_bug.cgi?id=608992  (poelcat,
   16:05:45)
   * ACTION: https://bugzilla.redhat.com/show_bug.cgi?id=608992 waiting
 for a new build, needs to happen soon  (poelcat, 16:07:25)

* https://bugzilla.redhat.com/show_bug.cgi?id=621027  (poelcat,
   16:07:34)
   * ACTION: https://bugzilla.redhat.com/show_bug.cgi?id=621027 asking
 mizmo to update the bug and remind design team of change deadline on
 2010-09-14  (poelcat, 16:12:53)

* https://bugzilla.redhat.com/show_bug.cgi?id=628239  (poelcat,
   16:13:08)
   * ACTION: https://bugzilla.redhat.com/show_bug.cgi?id=628239 need to
 continue debugging before we can figure out where it needs to be
 fixed  (poelcat, 16:20:05)

* https://bugzilla.redhat.com/show_bug.cgi?id=629719  (poelcat,
   16:20:22)
   * ACTION: https://bugzilla.redhat.com/show_bug.cgi?id=629719
 attempting to reproduce. If we cannot do so with TC1 testing will
 close INSUFFICIENT_DATA  (poelcat, 16:28:36)

* https://bugzilla.redhat.com/show_bug.cgi?id=630490  (poelcat,
   16:28:41)
   * ACTION: https://bugzilla.redhat.com/show_bug.cgi?id=630490 fix is in
 hand, maintainer expects to build new package tonight  (poelcat,
 16:45:36)

* https://bugzilla.redhat.com/show_bug.cgi?id=630781  (poelcat,
   16:45:48)
   * ACTION: https://bugzilla.redhat.com/show_bug.cgi?id=630781 really
 need more information from reporter; if no further information or
 similiar reports by next week, will consider dropping  (poelcat,
 16:53:24)

* https://bugzilla.redhat.com/show_bug.cgi?id=631620  (poelcat,
   16:53:32)
   * ACTION: https://bugzilla.redhat.com/show_bug.cgi?id=631620 fix and
 new packages anticipated this weekend, needs testing by kde, xfce
 and other desktops depending on HAL  (poelcat, 17:05:05)

* https://bugzilla.redhat.com/show_bug.cgi?id=632489  (poelcat,
   17:05:25)
   * ACTION: https://bugzilla.redhat.com/show_bug.cgi?id=632489 accepted
 as a blocker, fixed needed no later than 2010-09-14  (poelcat,
 17:14:11)

* https://bugzilla.redhat.com/show_bug.cgi?id=632510  (poelcat,
   17:14:18)
   * ACTION: https://bugzilla.redhat.com/show_bug.cgi?id=632510 accepted
 blocker; need to ammend blocker criteria to be more specific, devel
 believes it's an easy fix they expect to make soon  (poelcat,
 17:25:40)

* open discussion  (poelcat, 17:25:44)
   * ACTION: jlaska to propose adjusting beta release criteria to
 accomodate rescue-mode + networking (see 632510)  (jlaska, 17:26:18)

Meeting ended at 17:31:28 UTC.




Action Items

* https://bugzilla.redhat.com/show_bug.cgi?id=608992 waiting for a new
   build, needs to happen soon
* https://bugzilla.redhat.com/show_bug.cgi?id=621027 asking mizmo to
   update the bug and remind design team of change deadline on 2010-09-14
* https://bugzilla.redhat.com/show_bug.cgi?id=628239 need to continue
   debugging before we can figure out where it needs to be fixed
* https://bugzilla.redhat.com/show_bug.cgi?id=629719 attempting to
   reproduce. If we cannot do so with TC1 testing will close
   INSUFFICIENT_DATA
* https://bugzilla.redhat.com/show_bug.cgi?id=630490 fix is in hand,
   maintainer expects to build new package tonight
* https://bugzilla.redhat.com/show_bug.cgi?id=630781 really need more
   information from reporter; if no further information or similiar
   reports by next week, will consider dropping
* https://bugzilla.redhat.com/show_bug.cgi?id=631620 fix and new
   packages anticipated this weekend, needs testing by kde, xfce and
   other desktops depending on HAL
* https://bugzilla.redhat.com/show_bug.cgi?id=632489 accepted as a
   blocker, fixed needed no later than 2010-09-14
* https://bugzilla.redhat.com/show_bug.cgi?id=632510 accepted blocker;
   need to ammend blocker criteria to be more specific, devel believes
   it's an easy fix they expect to make soon
* jlaska to propose adjusting beta release criteria to accomodate
   rescue-mode + networking (see 632510)




Action Items, by person
---
* jlaska
   * jlaska to propose adjusting beta release criteria to accomodate
 rescue-mode + networking (see 632510)
* **UNASSIGNED**
   * https://bugzilla.redhat.com/show_bug.cgi?id=

Re: [Test-Announce] Fedora 14 Beta Blocker Meeting :: Friday, 2010-09-10 @ 16:00 UTC (12 PM EDT)

2010-09-13 Thread Tom Horsley 
On Mon, 13 Sep 2010 09:21:41 -0400
James Laska wrote:

> I've added this to F14Blocker as hard drive installs are covered under
> the final release criteria... 

I tested the hard drive install at the same time I was testing
the vesa driver, and hard drive install was indeed working OK
in TC1 (as was the ATI driver). I already updated the bugzilla
to say that.

> The question for this bug is whether the issue is specific to your
> hardware, or generic enough for most users.

Since I just found that bug already in bugzilla, there is at
least one other person who gets it :-). But the actual message
does say it is more like a warning where it is just printing
the walkback for information rather than a "real" crash.
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

Re: [Test-Announce] Fedora 14 Beta Blocker Meeting :: Friday, 2010-09-10 @ 16:00 UTC (12 PM EDT)

2010-09-13 Thread James Laska 
Thanks for the feedback Tom, comments below.

On Thu, 2010-09-09 at 21:59 -0400, Tom Horsley wrote:
> This one seemed pretty bad to me:
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=627073
> 
> Maybe the ATI problem is fixed now (it sort of seemed like
> it might already have been fixed but didn't quite make it
> into F14 alpha), but vesa also not working was pretty mysterious.

I don't think we have criteria that VESA must work in all instances,
however that is our fallback so it would certainly be good to have
fixed.  From your comments, it seems that the primary ATI driver now
works as of F-14-Beta-TC1.

/me still thinking on this bug

> I'd certainly hope this one is fixed as well:
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=627058
> 
> Hard disk install is the simplest way for me to install,
> and it was a pain that it didn't work.
> 
> And this one doesn't seem to actually hurt anything,
> but it is always worrisome to get kernel errors :-)

I believe this should be resolved in F-14-TC1, can you confirm?

http://git.fedorahosted.org/git/?p=anaconda.git;a=commitdiff;h=80f744369736d6dbd689ed4b7d17a71e3bcdbf74

I've added this to F14Blocker as hard drive installs are covered under
the final release criteria... 

"The installer must be able to use all supported local and
remote package source options"

> https://bugzilla.redhat.com/show_bug.cgi?id=626026
> 
> (I'm still seeing the same error in the latest kernel
> provided in the f14 repos).

The question for this bug is whether the issue is specific to your
hardware, or generic enough for most users.  I *suspect* this would be
covered under the following Final release criteria, but is contingent
upon how common this failure is for other users:

"In most cases, there must be no SELinux 'AVC: denied' messages
or abrt crash notifications on initial boot and subsequent
login"

Can you confirm that ABRT does indeed detect and notify you of the
kernel crash?

Thanks,
James


signature.asc
Description: This is a digitally signed message part
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

Re: [Test-Announce] Fedora 14 Beta Blocker Meeting :: Friday, 2010-09-10 @ 16:00 UTC (12 PM EDT)

2010-09-09 Thread Tom Horsley 
This one seemed pretty bad to me:

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

Maybe the ATI problem is fixed now (it sort of seemed like
it might already have been fixed but didn't quite make it
into F14 alpha), but vesa also not working was pretty mysterious.

I'd certainly hope this one is fixed as well:

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

Hard disk install is the simplest way for me to install,
and it was a pain that it didn't work.

And this one doesn't seem to actually hurt anything,
but it is always worrisome to get kernel errors :-)

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

(I'm still seeing the same error in the latest kernel
provided in the f14 repos).
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

[Test-Announce] Fedora 14 Beta Blocker Meeting :: Friday, 2010-09-10 @ 16:00 UTC (12 PM EDT)

2010-09-09 Thread John Poelstra 
When: Friday, 2010-09-10 @ 16:00 UTC (12 PM EDT)
Where: #fedora-bugzappers on irc.freenode.net

Without these bugs fixed we can't compose the Fedora 14 Beta Release 
Candidate on 2010-09-16.

We'll be discussing these bugs to determine if they meet the criteria, 
should stay on the list, and are getting the attention they need:

629719 :: NEW :: anaconda :: Anaconda Maintenance Team :: 
FormatCreateError: ('invalid device specification', '/dev/md127p3') :: 
https://bugzilla.redhat.com/show_bug.cgi?id=629719

628239 :: NEW :: anaconda :: Anaconda Maintenance Team :: Fedora 14 
Alpha "reduced graphics" creates vesa-using xorg.conf but doesn't 
blacklist nouveau :: https://bugzilla.redhat.com/show_bug.cgi?id=628239

608992 :: NEW :: livecd-tools :: David Huff :: Add "Boot system with 
basic video driver" option at the initial screen :: 
https://bugzilla.redhat.com/show_bug.cgi?id=608992

630781 :: NEW :: systemd :: Kernel Maintainer List :: systemd hangs on 
"Clocksource tsc unstable" error and causes the system to freeze after 
cpu-scaling detection :: https://bugzilla.redhat.com/show_bug.cgi?id=630781

630490 :: NEW :: systemd :: Lennart Poettering :: disabled units still 
get bus activated :: https://bugzilla.redhat.com/show_bug.cgi?id=630490

631620 :: NEW :: systemd :: Lennart Poettering :: ordering cycles exist 
(+ breaking them deletes wrong services) :: 
https://bugzilla.redhat.com/show_bug.cgi?id=631620

621027 :: NEW :: fedora-logos :: Tom "spot" Callaway :: Graphical screen 
in anaconda shows F-13 :: https://bugzilla.redhat.com/show_bug.cgi?id=621027

If you are the owner of any of these bugs, kindly update the comments 
with your feedback as to whether you believe it is a blocker and what 
your plans for fixing the bug are.

Do you have an issue you believe should be fixed before the Fedora 14 
Beta ships?  Please consider the following criteria when escalating an 
issue: https://fedoraproject.org/wiki/Fedora_14_Beta_Release_Criteria

John

The command used to generate the list of bugs above is:
$ bugzilla query --blocked=611991 \
 
--bug_status=NEW,ASSIGNED,NEEDINFO,ON_DEV,MODIFIED,POST,ON_QA,FAILS_QA,PASSES_QA,REOPENED,VERIFIED,RELEASE_PENDING
 
\
 --outputformat="%{bug_id} :: %{bug_status} :: %{component} :: 
%{assigned_to} :: %{summary} :: %{url}"

NOTE: It this command doesn't work on Fedora 14.
___
test-announce mailing list
test-annou...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test