Dne 13.5.2011 8:59, bearwere napsal(a):
> I get the same behaviour. I wrote to this list about a month ago, to
> no avail. I tried full resync of repositories, which didn't help. I
> guess spacewalk-data-fsck is a bit broken, but that doesn't seem to
> affect any functionality, so I don't worry muc
I get the same behaviour. I wrote to this list about a month ago, to no
avail. I tried full resync of repositories, which didn't help. I guess
spacewalk-data-fsck is a bit broken, but that doesn't seem to affect any
functionality, so I don't worry much.
On 13.05.2011 13:46, David Hrbáč wrote:
Dne 12.5.2011 11:53, Matthew Darcy napsal(a):
> I've had this problem on 3 test spacewalk clean build.
>
> I'm using spacewalk 1.3 Oracle XE on Centos 5.6 x86_64 platform.
>
> I've got a base channel that contains 3 repos
> 1.) centos 5 x86_64 core repo sync'd on a daily basis from the mirror
> ht
I've had this problem on 3 test spacewalk clean build.
I'm using spacewalk 1.3 Oracle XE on Centos 5.6 x86_64 platform.
I've got a base channel that contains 3 repos
1.) centos 5 x86_64 core repo sync'd on a daily basis from the mirror
http://mirror.ox.ac.uk/sites/mirror.centos.org/5/os/x86_64/
