reposync expectations

[Bob Lightfoot]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 06/23/2014 02:19 PM, James Antill wrote:
> On Mon, 2014-06-23 at 20:00 +0200, Anders Blomdell wrote:
>> On 2014-06-23 16:50, James Antill wrote:
>>> On Sat, 2014-06-21 at 20:54 -0400, Bob Lightfoot wrote:
>>>> Dear Yum Developers: I recently ran reposync on a remote
>>>> repo {http://buildlogs.centos.org/centos/7/os/x86_64-latest/}
>>>> from my Centos6-i686 system in an attempt to mirror the repo.
>>>> Reposync downloaded 4726 rpms. Performing the identical task
>>>> from my Centos6-X86_64 system resulted in 8468 rpms being
>>>> downloaded. I would expect the mirroring of a repo to be
>>>> identical regardless of arch of the host/local system. Is
>>>> this a valid expectation?
>>> 
>>> No, from the man page:
>>> 
>>> -a ARCH, --arch=ARCH Act as if running the specified  arch
>>> (default:  current  arch, note:  does  not  override
>>> $releasever. x86_64 is a superset for i*86.).
>> Suggested patch is here:
>> 
>> http://lists.baseurl.org/pipermail/yum-devel/2014-May/010622.html
>
>> 
> Look at how repoquery works, with --archlist. That's probably what
> you want to do (you can probably ignor the code for when
> YumBase.arch doesn't exist now). But that should work to allow
> multiple arches, and have a default basearch and auto. setup for
> x86_64 etc.
> 
Perhaps to provide a little background will clarify things for
everyone.  I was working to test the latest buildlogs release of
Centos 7 and given my ISP situation {slow DSL} a local mirror is the
most efficient method for doing this.  The box hosting the local repo
is C6-i686 file server, but as we all know C7 is only x86_64 with some
i686 libs for compatability.  It was suggested that since rsync was
not yet configured for the C7 repo that reposync would work to create
a local mirror of the repo.  And if the system running the reposync
command is x86_64 this is true.  If I understand the posts back to me
correctly then using the --arch=x86_64 should resolve the issue on the
i686 system also, which testing proves it does.

So the bottom line is to a new user, it is less than crystal clear
that you need to use the arch flag to sync a repo for one arch on another.

Thanks for the explanations.

Bob
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJTqH63AAoJEKqgpLIhfz3Xg6QH/RmQ6iIbcIDnJjdx3OgNY8no
iF+HxXc5FiBJyvb1m+8G3izcrD1W9lRC9EVUZ+r+0M3OB2a7dSxB0gOtSB0aphDH
Qw4uLNt92ZfWJuMRmO3P0Y3eVfNOBVMiEwPSmW77J5rmL8oSFtUzEOqkxfnjO1ZS
P7efziwHgUP1LUvMRW9EuwVVE2sDfoT1ASFrlQG1pBWyV9WDQ1PHE+Gzhg3gsx6Z
TBFdvM6/1H50POq1UWuB8gobJIZysrxCNYfCe70/4vef1bCfxMR2RqpT5A6B3bFx
uCcDQt1BlsI/XzBaBnMqhkyZiSdE/AtP+MvDvjVxUPmFpYvexvDUuG1hYVf/5iA=
=dGO3
-----END PGP SIGNATURE-----