Same way we did our 32-bit mirror, which seems fine.
When I clear out my local mirror and try to do a reposync,
it only manages to pull down 'noarch' packages. My hunch is it's
related to this being a 32-bit OS somehow.
[root@repoman ~]# cobbler version
Cobbler 2.0.11
source: ?, ?
build time: Tue Apr 26 19:05:50 2011
[root@repoman ~]# cobbler repo report --name epel-x64
Name : epel-x64
Arch : x86_64
Breed : yum
Comment :
Createrepo Flags :
Environment Variables : {}
Keep Updated : True
Mirror :
http://download.fedora.redhat.com/pub/epel/5/x86_64/
Mirror locally : True
Owners : ['admin']
Priority : 99
RPM List : ['puppet', 'koan', 'facter',
'rubygems', 'scponly', 'monit', 'erlang',
'ejabberd', 'nginx', 'git',
'rubygem-stomp', 'php53-mcrypt', 'php-pear-Mail',
'memcached', 'htop',
'atop']
Yum Options : {}
[root@repoman ~]# cobbler reposync --only epel-x64
task started: 2012-01-23_092438_reposync
task started (id=Reposync, time=Mon Jan 23 09:24:38 2012)
hello, reposync
run, reposync, run!
creating: /var/www/cobbler/repo_mirror/epel-x64/.origin/epel-x64.repo
running: /usr/bin/yumdownloader --resolve --disablerepo=*
--enablerepo=epel-x64 -c
/var/www/cobbler/repo_mirror/epel-x64/.origin/epel-x64.repo
--destdir=/var/www/cobbler/repo_mirror/epel-x64 puppet koan facter
rubygems scponly monit erlang ejabberd nginx git rubygem-stomp
php53-mcrypt php-pear-Mail memcached htop atop
received on stdout: No Match for argument scponly
No Match for argument monit
No Match for argument erlang
No Match for argument ejabberd
No Match for argument nginx
No Match for argument git
No Match for argument php53-mcrypt
No Match for argument memcached
No Match for argument htop
No Match for argument atop
--> Running transaction check
---> Package facter.noarch 0:1.6.2-1.el5 set to be updated
---> Package koan.noarch 0:2.0.11-2.el5 set to be updated
---> Package php-pear-Mail.noarch 0:1.1.14-5.el5.1 set to be updated
.....
.....
On 20 January 2012 16:39, Corey Kovacs <corey.kovacs(a)gmail.com> wrote:
Works fine for me. How did you set your repository up?
On Jan 20, 2012 9:26 AM, "Dick Davies" <rasputnik(a)hellooperator.net>
wrote:
>
> Does cobbler reposync work for anybody else?
>
> seems it can only sync repos that match the major os version and
> architecture
> of the server running cobbler. It's been like this for a while (we're
> on the EPEL
> latest of cobbler) but it's starting to be a real pain.
>
> Just wondered if it was a known issue.
> _______________________________________________
> cobbler mailing list
> cobbler(a)lists.fedorahosted.org
>
https://fedorahosted.org/mailman/listinfo/cobbler
_______________________________________________
cobbler mailing list
cobbler(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler