gmane.linux.redhat.fedora.testers

spin-kickstarts got changed after RC4

Bruno Wolff III — 2012-05-23T12:42:32

There has been a commit to the F17 branch of spin-kickstarts that looks
to have occurred after all of the RC4 spins were built. If we need to
do an RC5, then either the builds should use the spin-kickstarts repo
as of before that commit or we'll want to do another spin-kickstarts
package. The commit only affects SoaS.

[Test-Announce] Fedora 17 FINAL Go/No-Go Meeting (#2), Thursday,May 24, < at >13:00 Eastern

Robyn Bergeron — 2012-05-23T12:16:21

Please join us on irc.freenode.net in #fedora-meeting-1 for this 
important meeting, wherein we shall determine the shipment readiness of 
F17 Final.

Thursday, May 24, 2012 < at > 17:00 UTC (13:00 EDT/10:00 PDT)

"Before each public release Development, QA and Release Engineering meet 
to determine if the release criteria are met for a particular release. 
This meeting is called the Go/No-Go Meeting."

"Verifying that the Release criteria are met is the responsibility of 
the QA Team."

For more details about this meeting see:
https://fedoraproject.org/wiki/Go_No_Go_Meeting

In the meantime: Keep an eye on the blocker list here:
http://fedoraproject.org/wiki/Current_Release_Blockers

Let's ship the beefy miracle, folks! :)

-Robyn
_______________________________________________
test-announce mailing list
test-announce< at >lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce

[Test-Announce] Fedora Board, FESCo,and FAmSCo elections: Town hall meeting schedule

Robyn Bergeron — 2012-05-23T11:43:56

As you have (hopefully) heard by now, elections for the Fedora Board, 
FESCo, and FAmSCo are quickly approaching.

In each election cycle, a series of town hall meetings is held to give 
community members and opportunity to ask candidates questions - and hear 
their answers - via IRC.

The town hall schedule for the upcoming election is as follows:

Fedora Project Board:
* Tuesday, May 29, 2012 at 17:00 UTC
* Wednesday, May 30, 2012 at 20:00 UTC

FESCo (Fedora Engineering Steering Committee):
* Wednesday, May 30, 2012 at 17:00 UTC
* Thursday, May 31, 2012 at 20:00 UTC

FAmSCo (Fedora Ambassadors Steering Committee):
* Sunday, May 27, 2012 at 16:00 UTC
* Monday, May 28 at 17:00 UTC

Not sure what time that is? Use a handy-dandy time zone calculator to 
find out when to show up:
http://www.timeanddate.com/worldclock/converter.html

Important information about how you can participate in the town halls 
via IRC, as well as the details of each town hall meeting, can be seen 
on the wiki here:

http://fedoraprojec

Re: dracut kernel-panci

Frank Murphy — 2012-05-23T11:09:22


managed to get on to Vm machine.
panics before getting to above debug switches.


Will boot if dracut downgraded to previous:
dracut-018-53.git20120509.fc18
and --force initramfs

F17 boxes with dracut-018-40.git20120522.fc17 boot fine.

Full serial console capture with debug switch's included:
http://frankly3d.eu/kernel-panic

Re: dracut kernel-panci

Frank Murphy — 2012-05-23T10:22:12

This is a snip from  serial console, will get to box later this evening.

[    2.474250] Refined TSC clocksource calibration: 2402.495 MHz.
[    2.480737] input: ImExPS/2 Generic Explorer Mouse as 
/devices/platform/i8042/serio1/input/input2
[    2.486190] md: Waiting for all devices to be available before autodetect
[    2.489062] md: If you don't use raid, use raid=noautodetect
[    2.496160] md: Autodetecting RAID arrays.
[    2.498194] md: Scanned 0 and added 0 devices.
[    2.500101] md: autorun ...
[    2.501416] md: ... autorun DONE.
[    2.503585] VFS: Cannot open root device 
"mapper/luks-c19c397b-248d-4e6b-9a54-2a5d592f9d0d" or 
unknown-block(0,0): error -6
[    2.508111] Please append a correct "root=" boot option; here are the 
available partitions:
[    2.511797] 0b00         1048575 sr0  driver: sr
[    2.513906] Kernel panic - not syncing: VFS: Unable to mount root fs 
on unknown-block(0,0)
[    2.521261] Pid: 1, comm: swapper/0 Not tainted 3.4.0-2.fc18.x86_64 #1
[    2.521437] usb 1-1: New U

Re: dracut kernel-panci

Harald Hoyer — 2012-05-23T10:10:31

Am 23.05.2012 11:17, schrieb Frank Murphy:

How exactly does the kernel panic look like? Normally, you are dropped to a shell.

you can get more debug info, if you add "rd.debug rd.shell loglevel=77" to the
kernel command line.

dracut kernel-panci

Frank Murphy — 2012-05-23T09:17:38

Anyone else have a kernel-panic
with initramfs created by:
dracut-018-74.git20120522.fc18

Re: yum-presto to get multicore support

Adam Pribyl — 2012-05-23T06:57:50


I personally never noticed that, but maybe my download is that fast, the 
rebuild progress is so minor, it's invisible on the bar when the 
"rebuilding rpms" message shows.

Anyway interesting..

Adam Pribyl

abrt backtrace failures

Chuck Anderson — 2012-05-23T04:06:20

During F17 RC testing, twice now [1][2] I've been unable to submit
bugs using abrt because the backtrace was considered "unusable" by
abrt.

1. Is there a problem with the debuginfo's or abrt functionality
during this F17 final RC stage?

2. What happened to the Retrace Server?  I don't see that option for
F17, only Local GNU Debugger.

3. Can the abrt behavior be changed to allow the bug to be created,
but perhaps without the "bad" backtrace, or perhaps marked in some way
so it is known to have a "bad" backtrace? 

It is still helpful to the bug reporter to have abrt create the bug
with as much info as possible, with the expectation that better/usable
backtraces could be attached later manually if possible.

It is frustrating to be informed of a crash by abrt and go through all
the effort to submit the bug report via abrt, only to be told "sorry,
I'm not going to let you submit this bug report because it doesn't
meet our standards of quality".  Frankly, it's a waste of the
reporter's time and it conditions

[Test-Announce] Fedora 17 Final Release Candidate 4 (RC4) AvailableNow!

Andre Robatino — 2012-05-23T02:41:27

As per the Fedora 17 schedule [1], Fedora 17 Final Release Candidate 4
(RC4) is now available for testing. Content information, including
changes, can be found at https://fedorahosted.org/rel-eng/ticket/5196 .
Please see the following pages for download links (including delta ISOs)
and testing instructions. Normally dl.fedoraproject.org should provide
the fastest download, but download-ib01.fedoraproject.org is available
as a mirror (with an approximately 1 hour lag) in case of trouble. To
use it, just replace "dl" with "download-ib01" in the download URL.

Installation:

https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test

Base:

https://fedoraproject.org/wiki/Test_Results:Current_Base_Test

Desktop:

https://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test

Security Lab:

https://fedoraproject.org/wiki/Test_Results:Current_Security_Lab_Test

Ideally, all Alpha, Beta, and Final priority test cases for Installation
[2], Base [3], Desktop [4], and Security Lab [5] should pass in orde

Re: NetworkManager-0.9.4.0-8.git20120502.fc17.x86_64

Bruno Wolff III — 2012-05-23T02:27:16

On Tue, May 22, 2012 at 16:44:25 -0600,
   Peter Gueckel <pgueckel< at >gmail.com> wrote:

1:0.9.4.0-9 is available and might fix this. (The error is in the uninstall
script, and I haven't tried uninstalling that one yet.)

NetworkManager-0.9.4.0-8.git20120502.fc17.x86_64

Peter Gueckel — 2012-05-22T22:44:25

Non-fatal POSTUN scriptlet failure in rpm package 
1:NetworkManager-0.9.4.0-8.git20120502.fc17.x86_64

/var/tmp/rpm-tmp.LIDIm9: line 6: syntax error near unexpected token `fi'

/var/tmp/rpm-tmp.LIDIm9: line 6: `fi'

warning: %postun(NetworkManager-1:0.9.4.0-8.git20120502.fc17.x86_64) scriptlet failed, 
exit status 2

Re: [Test-Announce] Fedora 17 Final Release Candidate 3 (RC3)Available Now!

Adam Williamson — 2012-05-22T19:16:21

Heads up: there will be an RC4, but the change will be very small:

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

one line :)

It fixes https://bugzilla.redhat.com/show_bug.cgi?id=823861 . All RC3
testing (except the serial install test, obviously) will still be valid,
so please go ahead with testing RC3. I'll transfer RC3 results into the
RC4 matrix once RC4 is built. Thanks!

Re: Could not browse Windows shares in local network with Nautilus

Adam Williamson — 2012-05-22T18:25:50

Well, you can track the update history of a package just by going to
https://admin.fedoraproject.org/updates/ and searching for the package
by name (note SRPM name, not binary RPM name). Each update page has
links to the Koji (buildsystem) page for the build, from which you could
download older builds, and install them with 'yum downgrade XXX.rpm' to
try them out. Just try downgrading possibly-related packages and see if
it starts working.

You can use 'yum history' to see what packages were changed in a given
update, if you can narrow it down to a specific update that you think
broke things: 'yum history list' gives a list of yum transactions, and
'yum history info (number)' will give you the packages that changed in a
specific transaction.

Re: Firewalld + persistant configurations

Emilio Lopez — 2012-05-22T16:39:58

I think, that the changes done by GUI are permanent at least those one
done in KDE.

Emilio.

Fedora 17 updates-testing report

2012-05-22T15:57:32

The following Fedora 17 Security updates need testing:

    https://admin.fedoraproject.org/updates/FEDORA-2012-8083/xen-4.1.2-17.fc17
    https://admin.fedoraproject.org/updates/FEDORA-2012-6334/sectool-0.9.5-7.fc17
    https://admin.fedoraproject.org/updates/FEDORA-2012-8194/python-tornado-2.2.1-1.fc17
    https://admin.fedoraproject.org/updates/FEDORA-2012-7939/openssl-1.0.0j-1.fc17
    https://admin.fedoraproject.org/updates/FEDORA-2012-7971/libgssglue-0.4-0.fc17
    https://admin.fedoraproject.org/updates/FEDORA-2012-7976/ikiwiki-3.20120516-1.fc17
    https://admin.fedoraproject.org/updates/FEDORA-2012-7998/sudo-1.8.3p1-7.fc17


The following Fedora 17 Critical Path updates have yet to be approved:

    https://admin.fedoraproject.org/updates/FEDORA-2012-8244/udisks2-1.94.0-5.fc17
    https://admin.fedoraproject.org/updates/FEDORA-2012-8245/colord-0.1.21-1.fc17
    https://admin.fedoraproject.org/updates/FEDORA-2012-8228/zeitgeist-0.9.0-1.fc17
    https://admin.fedoraproject.org/updates/FEDORA-2012-8235

Re: circular dependency loop in rawhide repo?

Kevin Fenzi — 2012-05-22T15:08:27

On Mon, 21 May 2012 21:23:56 -0400
"G.Wolfe Woodbury" <redwolfe< at >gmail.com> wrote:


Try removing the --skip-broken? 

This may result in some things that cannot upgrade, but you can then
remove them or otherwise deal with them and re-run. 

kevin

yum-presto to get multicore support

Andre Robatino — 2012-05-22T12:46:04


See https://bugzilla.redhat.com/show_bug.cgi?id=701711#c3 where Jonathan Dieter
says that it's supposed to already be doing the rebuild during drpm download.

Re: yum-presto to get multicore support

Tom Horsley — 2012-05-22T11:56:04

On Tue, 22 May 2012 11:49:18 +0000 (UTC)
Andre Robatino wrote:


It sure looks like it to me. I have a "gkrellm" monitor running, and
I don't see the cpu jump till after the last one is fetched and it
says "rebuilding rpms...".

yum-presto to get multicore support

Andre Robatino — 2012-05-22T11:49:18


Are you sure that's what it currently does? I thought I'd seen the progress
substantially higher than 0% at the instant the drpm downloads finish.

Re: yum-presto to get multicore support

Tom Horsley — 2012-05-22T11:22:05

On Tue, 22 May 2012 10:45:37 +0000 (UTC)
Andre Robatino wrote:


Actually, what would be even more useful is to start the building
of the rpms from the drpms as soon as the first drpm is fetched
instead of waiting till all of them are fetched before starting
the rebuilding.