The following Fedora 20 Security updates need testing:
Age URL
174 https://admin.fedoraproject.org/updates/FEDORA-2014-5897/nrpe-2.15-2.fc20
68
https://admin.fedoraproject.org/updates/FEDORA-2014-9474/pipelight-0.2.7.3-3.fc20
43
The following Fedora 19 Security updates need testing:
Age URL
362
https://admin.fedoraproject.org/updates/FEDORA-2013-19963/openstack-glance-2013.1.4-1.fc19
174 https://admin.fedoraproject.org/updates/FEDORA-2014-5896/nrpe-2.15-2.fc19
125
Compose started at Thu Oct 23 07:15:02 UTC 2014
Broken deps for armhfp
--
[PyQuante]
PyQuante-libint-1.6.4-11.fc21.1.armv7hl requires libint(armv7hl-32) =
0:1.1.6-2.fc21
[audtty]
audtty-0.1.12-9.fc20.armv7hl requires
Compose started at Thu Oct 23 05:15:02 UTC 2014
Broken deps for i386
--
[3Depict]
3Depict-0.0.16-3.fc22.i686 requires libmgl.so.7.2.0
[Agda]
ghc-Agda-2.3.2.2-5.fc22.i686 requires libHSterminfo-0.3.2.5-ghc7.6.3.so
The following Fedora 21 Security updates need testing:
Age URL
13
https://admin.fedoraproject.org/updates/FEDORA-2014-12483/python-oauth2-1.5.211-8.fc21
6
https://admin.fedoraproject.org/updates/FEDORA-2014-12934/drupal7-7.32-1.fc21
1
Hello,
I've recently gotten a new workstation at university. It came with
Windows 7 and of course, I added Fedora 21 to the mix. However, each
time I log into Windows and reboot, it seems to get stuck in a kind of
boot loop at BIOS - probably can't find grub. Would anyone know what
causes this?
On 10/23/2014 11:47 AM, Ankur Sinha wrote:
Hello,
I've recently gotten a new workstation at university. It came with
Windows 7 and of course, I added Fedora 21 to the mix. However, each
time I log into Windows and reboot, it seems to get stuck in a kind of
boot loop at BIOS - probably can't
Felix Miata composed on 2014-10-21 01:23 (UTC-0400):
I may have narrowed down the problem to this:
13 working installations:
rpcbind.service enabled
14 broken installations:
rpcbind.service static
Turns out finding the solution was stymied
Today at Go/No-Go meeting it was decided to slip Fedora 21 Beta release
as we did not have release candidate (RC) available in time. However we
will try one day slip.
The next Go/No-Go meeting is on Friday, Oct 24, the same time at
#fedora-meeting-2 channel.
Any help with release validation once
I suggest searching or paying on grub-help@ and maybe their devel list what
ZISD is. Funny though GRUB suggests others not use what GRUB usurps.
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/24/14 01:47, Ankur Sinha wrote:
Hello,
I've recently gotten a new workstation at university. It came with
Windows 7 and of course, I added Fedora 21 to the mix. However, each
time I log into Windows and reboot, it seems to get stuck in a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/24/14 06:18, Ed Greshko wrote:
Google ZISD.
or Google zisd grub for a better list of reading material.
- --
If you can't laugh at yourself, others will gladly oblige.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
On Fri, 2014-10-24 at 06:18 +0800, Ed Greshko wrote:
Google ZISD. Look at screen. See GRUB and ZISD - Cool Solutions |
Novell as second entry.
Click on link.
https://www.novell.com/communities/coolsolutions/grub-and-zisd/
I actually tried that - it didn't seem to work. Instead of one
On 10/23/2014 03:50 PM, Ankur Sinha wrote:
I actually tried that - it didn't seem to work. Instead of one sector
with ZISD, now I have 2.
The post is from 2008 and is probably referring to legacy GRUB.
From the error I had posted earlier, I think GRUB2 leaves the sector
occupied by ZISD be.
On Oct 23, 2014 4:50 PM, Ankur Sinha sanjay.an...@gmail.com wrote:
On Fri, 2014-10-24 at 06:18 +0800, Ed Greshko wrote:
Google ZISD. Look at screen. See GRUB and ZISD - Cool Solutions |
Novell as second entry.
Click on link.
On 10/23/2014 04:36 PM, Pete Travis wrote:
The post is telling you how to move the bits manually. It's mostly
relevant to admins migrating from the pre-2008 version of the software
doing the writing, to the version that knows better. Since you said
that GRUB is trashed after every Windows
I have noticed this for a while now using Fedora 21 alpha, that whenever a
kernel upgrade is performed and the the grub menu is updated as a result,
if I just reboot the system, the latest kernel is not automatically
selected and therefore started. Instead a particular previous kernel
version is
On 10/23/2014 05:01 PM, Napoleon Quashie wrote:
I have noticed this for a while now using Fedora 21 alpha, that
whenever a kernel upgrade is performed and the the grub menu is
updated as a result, if I just reboot the system, the latest kernel is
not automatically selected and therefore
On 10/23/2014 05:01 PM, Napoleon Quashie wrote:
I have noticed this for a while now using Fedora 21 alpha, that whenever
a kernel upgrade is performed and the the grub menu is updated as a
result, if I just reboot the system, the latest kernel is not
automatically selected and therefore started.
On Fri, 2014-10-24 at 01:01 +0100, Napoleon Quashie wrote:
I have noticed this for a while now using Fedora 21 alpha, that whenever a
kernel upgrade is performed and the the grub menu is updated as a result,
if I just reboot the system, the latest kernel is not automatically
selected and
20 matches
Mail list logo
