Compose started at Sat Jun 8 08:15:03 UTC 2013
Broken deps for x86_64
--
[bind10]
bind10-1.0.0-3.fc20.i686 requires liblog4cplus-1.1.so.5
bind10-1.0.0-3.fc20.x86_64 requires liblog4cplus-1.1.so.5()(64bit)
Compose started at Sat Jun 8 09:15:02 UTC 2013
Broken deps for x86_64
--
[deltacloud-core]
deltacloud-core-rhevm-1.1.3-1.fc19.noarch requires rubygem(rbovirt) =
0:0.0.18
[dragonegg]
dragonegg-3.1-19.fc19.x86_64 requires gcc
Joerg Lechner wrote:
... on an old PC (524MB Ram, 1,6 GHz, board KVTA5, 2 disks: 20GB Fedora
tests, 250GB Windows XP, PATA)
... The process installing the bootloader at the end of the installation
process took about half an hour.
It is best to investigate using VT2. Type CtrlAltF2 (where
I disabled NetworkManager, I enabled network, I copied in all my
/etc/sysconfig/network-scripts/ifcfg-* files, but I don't get
any networking on my fedora 19 install.
I've got this box connected to a dd-wrt router doing
tagged packets for vlan support, so the network setup
is a tad complex :-).
On Sat, 8 Jun 2013 10:39:09 -0400
Tom Horsley wrote:
Anyone know what might be missing that prevents this
stuff from working?
Finally found it: There was no /etc/sysconfig/network
file.
The ifup initscript pukes when it can't find that file.
I copied the one from fedora 18, and all my
Greetings all,
I am a long-time Fedora-enthusiast. Long-time as in since Fedora Core
1. I've always been an early adopter of releases although I've never
officially signed up as a tester.
Switching to my Network-Manager inquiry ... I'm currently using
NM-0.9.8.2-1, kernel
The following Fedora 19 Security updates need testing:
Age URL
53
https://admin.fedoraproject.org/updates/FEDORA-2013-5801/mantis-1.2.15-1.fc19
25
https://admin.fedoraproject.org/updates/FEDORA-2013-8116/clamav-0.97.8-1.fc19
14
On Sat, 2013-06-08 at 12:32 -0400, Joerg Lechner wrote:
Hi,
I made a new installation, I feel that I can understand this process a
little better after the help of John
Thank You
John's right, but half an hour is still pretty slow. Is it an old system
you're installing on? From USB or DVD or
On Tue, Jun 04, 2013 at 12:06:32PM +0300, Cristian Sava wrote:
virtual environment. All needed is stock or was packaged on F19
(rpmbuild -ta ... / rpmbuild -ba ...) and all is working fine (selinux
It took me a while to figure out you're not talking about Fedora
packages but RPMs/specfiles
On Sat, 2013-06-08 at 23:06 +0200, Branko Grubic wrote:
On Sun, 2013-06-09 at 00:16 +0400, Igor Gnatenko wrote:
$ systemd-analyze blame
29.565s chronyd.service
29.468s avahi-daemon.service
27.942s firewalld.service
27.813s restorecond.service
On Sat, 8 Jun 2013 13:02:31 -0400
Tom Horsley wrote:
Finally found it: There was no /etc/sysconfig/network
file.
And I see there is a bugzilla for this as well (which
I couldn't find till I knew what the problem was :-).
https://bugzilla.redhat.com/show_bug.cgi?id=972353
--
test mailing list
Might it be possible to defer construction of the yum database until
Firstboot?
Just want to make it clear this is something to consider for F20. I
think it is too late to make this sort of change in F19.
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
The following Fedora 17 Security updates need testing:
Age URL
338
https://admin.fedoraproject.org/updates/FEDORA-2012-10269/revelation-0.4.14-1.fc17
150
https://admin.fedoraproject.org/updates/FEDORA-2013-0455/fedora-business-cards-1-0.1.beta1.fc17
78
The following Fedora 18 Security updates need testing:
Age URL
151
https://admin.fedoraproject.org/updates/FEDORA-2013-0416/fedora-business-cards-1-0.1.beta1.fc18
85
https://admin.fedoraproject.org/updates/FEDORA-2013-3935/puppet-3.1.1-1.fc18
78
14 matches
Mail list logo
