Hello Mike,

You would be right, if the oel6-public-latest repo has fewer packages then mine. But it has more then 24000 (on online repo). I tried to delete and recreate the channel which caused the re-sync the repository but it didn't solve the issue.

Balint

On 11/12/13 15:39, Michael Snyder wrote:

The source repo is possibly a rolling version repository (oel6-public-latest-x86_64). If your sync'd repository has existed for a relatively long time, your repository likely has older packages that have been removed from the source repository. That would explain the discrepancy in package count.

I have found this to be the case with the Fedora EPEL repo, where conflicting or obsolete packages are removed from the repo as an evolutionary requirement.

If you do not have any dependencies on your local repository, you could remove all packages from your local copy of the repo, and then run the sync operation again. You'll likely find it comes back with the 19000-something count that the source repo at Oracle currently contains, if it is indeed a rolling version repository and based on my experiences...

Good Luck!

Mike

Michael Snyder *|*Digital River *|*Principal Engineer, Cloud Engineering

*msny...@digitalriver.com <mailto:msny...@digitalriver.com> |*digitalriver.com <http://www.digitalriver.com/>

p: +1 952-225-3257 *| *c: +1 952-491-1185 *| *f: +1 952-392-0972

10380 Bren Road West, Minnetonka, MN 55343, USA

*From:*spacewalk-list-boun...@redhat.com [mailto:spacewalk-list-boun...@redhat.com] *On Behalf Of *Balint Szigeti
*Sent:* Wednesday, December 11, 2013 9:16 AM
*To:* spacewalk-list@redhat.com
*Subject:* [Spacewalk-list] OEL repo sync

Hello All,

Simple I don't get it, if the process find 24357 packages, why it didn't download all?

Sync started: Wed Dec 11 14:47:12 2013
['/usr/bin/spacewalk-repo-sync', '--channel', 'oel6-public-latest-x86_64', '--type', 'yum']
Repo URL: http://public-yum.oracle.com/repo/OracleLinux/OL6/latest/x86_64/
*Packages in repo:             24357
Packages already synced:      19412
Packages to sync:                27*
1/27 : php-odbc-5.3.3-27.el6_5-0.x86_64
2/27 : php-common-5.3.3-27.el6_5-0.x86_64
3/27 : php-imap-5.3.3-27.el6_5-0.x86_64
4/27 : php-dba-5.3.3-27.el6_5-0.x86_64
5/27 : php-intl-5.3.3-27.el6_5-0.x86_64
6/27 : php-bcmath-5.3.3-27.el6_5-0.x86_64
7/27 : php-fpm-5.3.3-27.el6_5-0.x86_64
8/27 : php-gd-5.3.3-27.el6_5-0.x86_64
9/27 : php-zts-5.3.3-27.el6_5-0.x86_64
10/27 : php-devel-5.3.3-27.el6_5-0.x86_64
11/27 : php-enchant-5.3.3-27.el6_5-0.x86_64
12/27 : php-xml-5.3.3-27.el6_5-0.x86_64
13/27 : php-ldap-5.3.3-27.el6_5-0.x86_64
14/27 : php-pdo-5.3.3-27.el6_5-0.x86_64
15/27 : php-pgsql-5.3.3-27.el6_5-0.x86_64
16/27 : php-recode-5.3.3-27.el6_5-0.x86_64
17/27 : php-embedded-5.3.3-27.el6_5-0.x86_64
18/27 : php-cli-5.3.3-27.el6_5-0.x86_64
19/27 : php-tidy-5.3.3-27.el6_5-0.x86_64
20/27 : php-mysql-5.3.3-27.el6_5-0.x86_64
21/27 : php-xmlrpc-5.3.3-27.el6_5-0.x86_64
22/27 : php-soap-5.3.3-27.el6_5-0.x86_64
23/27 : php-pspell-5.3.3-27.el6_5-0.x86_64
24/27 : php-5.3.3-27.el6_5-0.x86_64
25/27 : php-snmp-5.3.3-27.el6_5-0.x86_64
26/27 : php-mbstring-5.3.3-27.el6_5-0.x86_64
27/27 : php-process-5.3.3-27.el6_5-0.x86_64
Linking packages to channel.
Repo http://public-yum.oracle.com/repo/OracleLinux/OL6/latest/x86_64/ has comps file comps.xml. Repo http://public-yum.oracle.com/repo/OracleLinux/OL6/latest/x86_64/ has 1266 errata.
*Sync completed.
Total time: 0:16:26*

There is almost 5000 packages difference. Why? How could I fix it? I tried to run the /usr/bin/spacewalk-repo-sync --channel oel6-public-latest-x86_64 --type yum command from cron, console, the errata-import script run this command every night as well, and still not sync.

Does somebody meet this issue in Spacewalk 2.0 ?

Balint



_______________________________________________
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

_______________________________________________
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Reply via email to