New mock logging
by Orion Poplawski
How do I get rid of the:
2007-11-09 16:46:03,285 - util.py:194:DEBUG:
prefix that seems to have appeared with mock 0.8 (0.8.4)? At least from
the build.log. Might be useful in the other logs...
Thanks!
--
Orion Poplawski
Technical Manager 303-415-9701 x222
NWRA/CoRA Division FAX: 303-415-9702
3380 Mitchell Lane orion(a)cora.nwra.com
Boulder, CO 80301 http://www.cora.nwra.com
16 years, 6 months
bug or feature (default kernel kind)
by Christoph Höger
hi,
after removing my test-xen-kernel, kernel updates behaved strangely.
Whenever there was a new kernel the old one was selected as boot-default.
After some hints I took a look at /etc/sysconfig/kernel where the line
UPDATEDEFAULT=yes
looked perfectly normal. But
DEFAULTKERNEL=kernel-xen
was strange (and propably the source of the misbehavior).
Shouldn't that line get reset, when the last xen-kernel gets removed?
regards
christoph
16 years, 6 months
chain build in F-8
by Adrian Reber
I updated libmpd in F-8 and F-7 and I would now like to build gmpc which
depends on the new version of libmpd. chain-build failed for me with
F-8. What is the correct way to get libmpd in my buildroot? Do I have to
push it to testing? Just wait a bit longer? Thanks.
Adrian
16 years, 6 months
Re: Praise for F-8
by Nicolas Mailhot
Le Lun 12 novembre 2007 11:29, ne... a écrit :
>> Provide us with double error or some such output...
>> And some HW info and take a look at
> AMD X2 4400+ Gigabyte GA-K8NS Ultra-939 mobo, 2x 80GB & 1x 200GB
> Western Digital hard drives.
I can't speak for the install part since I use a rolling rawhide setup
but this hardware should work fine once installed (I have a AMD X2
4400+ + Gigabyte GA-K8N Ultra-9 mobo, maxtor drives)
--
Nicolas Mailhot
16 years, 6 months
F8 fresh install, fdisk shows /dev/dm-X devices
by Ahmed Kamal
Hi,
I just installed F8 fresh installation. The previous system (where the LVM
volume where created was FC6). After I booted into F8. "fdisk -l" returns
unusual /dev/dm-? devices. These seem to be the LVM's physical volume
partitions. Not sure why they're being picked up here! Here's the full
output
fdisk -l
Disk /dev/sda: 120.0 GB, 120034123776 bytes
255 heads, 63 sectors/track, 14593 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x1a581a57
Device Boot Start End Blocks Id System
/dev/sda1 * 1 2019 16217586 7 HPFS/NTFS
/dev/sda2 2020 9261 58171365 f W95 Ext'd (LBA)
/dev/sda3 9262 14561 42572250 83 Linux
/dev/sda4 14562 14593 257040 88 Linux plaintext
/dev/sda5 2020 5206 25599546 b W95 FAT32
/dev/sda6 5207 5510 2441848+ 82 Linux swap / Solaris
/dev/sda7 5511 6726 9767488+ 8e Linux LVM
/dev/sda8 6727 7942 9767488+ 8e Linux LVM
/dev/sda9 7943 9248 10490413+ 8e Linux LVM
/dev/sda10 9249 9261 104391 83 Linux
Disk /dev/dm-0: 10.7 GB, 10737418240 bytes
255 heads, 63 sectors/track, 1305 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000
Disk /dev/dm-0 doesn't contain a valid partition table
Disk /dev/dm-1: 9995 MB, 9995026432 bytes
255 heads, 63 sectors/track, 1215 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000
Disk /dev/dm-1 doesn't contain a valid partition table
Disk /dev/dm-2: 9986 MB, 9986637824 bytes
255 heads, 63 sectors/track, 1214 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000
Disk /dev/dm-2 doesn't contain a valid partition table
16 years, 6 months
Orphaning beecrypt
by Tomas Mraz
Hi Fedora developers,
I'm orphaning beecrypt in Fedora development branch as rpm as the only
previous user of beecrypt now uses NSS for cryptography. I'll still keep
its ownership for Fedora 7 and 8 branches. If noone steps up beecrypt
will be retired from Fedora development branch.
--
Tomas Mraz
No matter how far down the wrong road you've gone, turn back.
Turkish proverb
16 years, 6 months
LSB init scripts - automatic start
by Orion Poplawski
Jon Ciesla (limb) wrote:
> Author: limb
>
> Update of /cvs/pkgs/rpms/moodle/F-8
> In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv17700
>
> Modified Files:
> moodle.init moodle.spec sources
> Log Message:
> Bump to upstream, fix initscript for bugfix 246986.
>
>
>
> Index: moodle.init
> ===================================================================
> RCS file: /cvs/pkgs/rpms/moodle/F-8/moodle.init,v
> retrieving revision 1.2
> retrieving revision 1.3
> diff -u -r1.2 -r1.3
> --- moodle.init 13 Apr 2007 22:54:23 -0000 1.2
> +++ moodle.init 8 Nov 2007 17:30:09 -0000 1.3
> @@ -10,6 +10,17 @@
> # description: Enable the Moodle cron job
> #
>
> +### BEGIN INIT INFO
> +# Provides: lsb-moodle
> +# Required-Start: $local_fs $network $remote_fs
> +# Required-Stop: $local_fs $network $remote_fs
> +# Default-Start: 2 3 4 5
> +# Default-Stop: 0 1 6
> +# Short-Description: start and stop Moodle cron job
> +# Description: Moodle is an online courseware system
> +### END INIT INFO
I believe this (having Default-Start) will enable the service by
default. Previously, most packages ("Extras") are not supposed to be
enabled by default (have - in chkconfig line). Please be aware.
--
Orion Poplawski
Technical Manager 303-415-9701 x222
NWRA/CoRA Division FAX: 303-415-9702
3380 Mitchell Lane orion(a)cora.nwra.com
Boulder, CO 80301 http://www.cora.nwra.com
16 years, 6 months
Re: When will CVS be replaced by modern version control system?
by Nicolas Mailhot
Le Lun 12 novembre 2007 15:38, Christopher Aillon a écrit :
> I think Matej was implying we should point to the upstream repo and
> tagname instead of a tarball.
Please don't. Users want to know what fedora added to the tarball they
can download upstream (and check this tarball md5/sha1), not get a raw
VCS dump.
Also many upstreams perform manual changes on VCS dumps before turning
them into release archives, and you don't want to lose these changes
because they lead to strange bugs people that build from released
sources can not reproduce.
--
Nicolas Mailhot
16 years, 6 months
