The following Fedora 20 Security updates need testing:
Age URL
74
https://admin.fedoraproject.org/updates/FEDORA-2013-19198/quassel-0.9.1-1.fc20
35
https://admin.fedoraproject.org/updates/FEDORA-2013-22130/chicken-4.8.0.5-1.fc20
28
The following Fedora 18 Security updates need testing:
Age URL
37
https://admin.fedoraproject.org/updates/FEDORA-2013-21875/389-ds-base-1.3.0.9-1.fc18
24
https://admin.fedoraproject.org/updates/FEDORA-2013-22949/net-snmp-5.7.2-7.fc18
20
The following Fedora 19 Security updates need testing:
Age URL
73
https://admin.fedoraproject.org/updates/FEDORA-2013-19262/quassel-0.9.1-1.fc19
66
https://admin.fedoraproject.org/updates/FEDORA-2013-19963/openstack-glance-2013.1.4-1.fc19
24
Trimmed to lastest attempt.
On 12/27/2013 01:54 PM, Adam Williamson wrote:
On Fri, 2013-12-27 at 08:42 -0500, Robert Moskowitz wrote:
Thanks for responding. Trimed down to things to reply to...
On 12/27/2013 02:59 AM, Adam Williamson wrote:
Sometimes when I selected LVM for the
On Tue, 2013-12-31 at 12:49 -0500, Robert Moskowitz wrote:
If you have a copy of program.log (and ideally all the other logs...)
from one of those failures, we could try and figure it out.
Instructions on generating (or capturing) the logs?
They're in /tmp while the installation is
The following Fedora 19 Security updates need testing:
Age URL
73
https://admin.fedoraproject.org/updates/FEDORA-2013-19262/quassel-0.9.1-1.fc19
66
https://admin.fedoraproject.org/updates/FEDORA-2013-19963/openstack-glance-2013.1.4-1.fc19
24
The following Fedora 20 Security updates need testing:
Age URL
74
https://admin.fedoraproject.org/updates/FEDORA-2013-19198/quassel-0.9.1-1.fc20
35
https://admin.fedoraproject.org/updates/FEDORA-2013-22130/chicken-4.8.0.5-1.fc20
25
On 12/31/2013 01:14 PM, Adam Williamson wrote:
On Tue, 2013-12-31 at 12:49 -0500, Robert Moskowitz wrote:
If you have a copy of program.log (and ideally all the other logs...)
from one of those failures, we could try and figure it out.
Instructions on generating (or capturing) the logs?
On Tue, 2013-12-31 at 14:13 -0500, Robert Moskowitz wrote:
On 12/31/2013 01:14 PM, Adam Williamson wrote:
On Tue, 2013-12-31 at 12:49 -0500, Robert Moskowitz wrote:
If you have a copy of program.log (and ideally all the other logs...)
from one of those failures, we could try and figure it
On 12/31/2013 02:50 PM, Adam Williamson wrote:
On Tue, 2013-12-31 at 14:13 -0500, Robert Moskowitz wrote:
On 12/31/2013 01:14 PM, Adam Williamson wrote:
On Tue, 2013-12-31 at 12:49 -0500, Robert Moskowitz wrote:
If you have a copy of program.log (and ideally all the other logs...)
from one
On Dec 31, 2013, at 1:25 PM, Robert Moskowitz r...@htt-consult.com wrote:
You got them. let me know if anything else is needed to get this working.
It takes ~ 2hrs to do a test.
I don't see any kernel configs for EFI that aren't already enabled in config.
And there isn't a debug option
On 12/31/2013 04:46 PM, Chris Murphy wrote:
On Dec 31, 2013, at 1:25 PM, Robert Moskowitz r...@htt-consult.com wrote:
You got them. let me know if anything else is needed to get this working. It
takes ~ 2hrs to do a test.
I don't see any kernel configs for EFI that aren't already enabled
On Dec 31, 2013, at 4:39 PM, Robert Moskowitz r...@htt-consult.com wrote:
On 12/31/2013 05:00 PM, bugzi...@redhat.com wrote:
https://bugzilla.redhat.com/show_bug.cgi?id=1006304
In additional info, include computer model and firmware revision. And then
attach your program.log, anaconda-tb,
On 12/31/2013 07:18 PM, Chris Murphy wrote:
On Dec 31, 2013, at 4:39 PM, Robert Moskowitz r...@htt-consult.com wrote:
On 12/31/2013 05:00 PM, bugzi...@redhat.com wrote:
https://bugzilla.redhat.com/show_bug.cgi?id=1006304
In additional info, include computer model and firmware revision. And
On Dec 31, 2013, at 5:27 PM, Robert Moskowitz r...@htt-consult.com wrote:
On 12/31/2013 07:18 PM, Chris Murphy wrote:
On Dec 31, 2013, at 4:39 PM, Robert Moskowitz r...@htt-consult.com wrote:
On 12/31/2013 05:00 PM, bugzi...@redhat.com wrote:
On Dec 31, 2013, at 5:34 PM, Chris Murphy li...@colorremedies.com wrote:
Since you only have Fedora to boot, the simplest fix might be to delete all
of the NVRAM entries, and hope that in a reboot or two, it does sufficient
garbage collection that you can then try another installation.
On 12/31/2013 07:34 PM, Chris Murphy wrote:
On Dec 31, 2013, at 5:27 PM, Robert Moskowitz r...@htt-consult.com wrote:
On 12/31/2013 07:18 PM, Chris Murphy wrote:
On Dec 31, 2013, at 4:39 PM, Robert Moskowitz r...@htt-consult.com wrote:
On 12/31/2013 05:00 PM, bugzi...@redhat.com wrote:
On 12/31/2013 08:00 PM, Chris Murphy wrote:
On Dec 31, 2013, at 5:34 PM, Chris Murphy li...@colorremedies.com wrote:
Since you only have Fedora to boot, the simplest fix might be to delete all of
the NVRAM entries, and hope that in a reboot or two, it does sufficient garbage
collection that
The following Fedora 19 Security updates need testing:
Age URL
74
https://admin.fedoraproject.org/updates/FEDORA-2013-19262/quassel-0.9.1-1.fc19
67
https://admin.fedoraproject.org/updates/FEDORA-2013-19963/openstack-glance-2013.1.4-1.fc19
24
The following Fedora 20 Security updates need testing:
Age URL
75
https://admin.fedoraproject.org/updates/FEDORA-2013-19198/quassel-0.9.1-1.fc20
35
https://admin.fedoraproject.org/updates/FEDORA-2013-22130/chicken-4.8.0.5-1.fc20
26
The following Fedora 18 Security updates need testing:
Age URL
38
https://admin.fedoraproject.org/updates/FEDORA-2013-21875/389-ds-base-1.3.0.9-1.fc18
24
https://admin.fedoraproject.org/updates/FEDORA-2013-22949/net-snmp-5.7.2-7.fc18
18
21 matches
Mail list logo
