I built the EPEL local repo before I started messing with cobbler so it was local. The first time I did the epel testing I used your suggestion as documented. The first time it appeared to pull them down as expected and then choked when it was populating the local repo. All the previous speaking as an end user who is still getting familiar with th RH way of package mgmt... > -----Original Message----- > From: et-mgmt-tools-bounces@xxxxxxxxxx > [mailto:et-mgmt-tools-bounces@xxxxxxxxxx] On Behalf Of Michael DeHaan > Sent: Thursday, August 30, 2007 11:16 AM > To: Fedora/Linux Management Tools > Subject: Re: Cobbler install/kickstart question > > Maute, Kevin P CTR AFRL/VAOO wrote: > > I backed out epel5 testing for now, epel5 works fine. > > > > Weird. Works for me, and if normal EPEL works, testing is the > same. Any > weird proxies/filtering in the way? > > Here's the commands I used ... > > # cobbler repo add --name=e5t64 > --mirror=http://download.fedora.redhat.com/pub/epel/testing/5/x86_64/ > # cobbler reposync > > As I've said, in the worst case you can clean out > /var/www/cobbler/repo_mirror/$name-of-repo, delete the repo > definition, > and retry... though I'm not entirely sure that would help. Good luck! > > --Michael > > _______________________________________________ > et-mgmt-tools mailing list > et-mgmt-tools@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/et-mgmt-tools > _______________________________________________ et-mgmt-tools mailing list et-mgmt-tools@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/et-mgmt-tools
