I tried the same thing in Spacewalk 2.0 as Amedeo Salvati. 1. Creating an Repository for: http://resources.ovirt.org/pub/ovirt-3.4/rpm/el6Server/
2. Creating an x86-64 channel for ovirt and linking it to the repository above. When syncing, the log ends with: Linking packages to channel. ERROR: Package arch ppc64 incompatible with channel ovirt-el6-server-x86-64-3.4 Sync completed. Total time: 0:00:28 The packages do not link into the associated channel -- they stay stuck in limbo the in the "Packages in no channels" under Channels -> Manage Software Channels -> Manage Software Packages Mixing x86-64 and ppc64 in the same x86-64 Channel appears to NOT work. On 1/14/2014 9:19 AM, Paul Robert Marino wrote: > This is just a warning don't worry about that you might be syncing to > the wrong yum repo. It doesn't actually break any thing or cause the > sync to result in a failure. > In truth its very odd to mix x86 and ppc packages in the same repo, > and while it can be done it was not intended in the original spec for > yum repos. > > On Tue, Jan 14, 2014 at 6:42 AM, Amedeo Salvati <[email protected]> wrote: >> Hi guys! >> >> I'm trying to import on spacewalk2.0 a new repository which contains on >> remote repo some packages based on ppc64 arch (I need only x86_64 and noarch >> rpms), to better understand the remote repo is ovirt-3.3.2 available on: >> >> http://resources.ovirt.org/releases/3.3.2/rpm/EL/6/ >> >> if you looking on it, you can see that repodata is built on top for all >> archs (i686, x86_64, noarch, ppc64...) so when I execute spacewalk-repo-sync >> against it I got this error: "ERROR: Package arch ppc64 incompatible with >> channel ovirt-3.3.2" >> >> I've tried also, with -f switch and with -e exclude filters, but always I >> got the same error! >> >> Do you know if there are any option to exclude ppc64 rpms and import others? >> >> This is a sample spacewalk-repo-sync output: >> >> # spacewalk-repo-sync -c ovirt-3.3.2 -t yum -f >> Repo URL: http://resources.ovirt.org/releases/3.3.2/rpm/EL/6/ >> Packages in repo: 111 >> Packages already synced: 0 >> Packages to sync: 94 >> 1/94 : glusterfs-3.4.0-8.el6-0.x86_64 >> 2/94 : glusterfs-devel-3.4.0-8.el6-0.x86_64 >> .... (cut) >> 86/94 : vdsm-hook-vmfex-4.13.2-1.el6-0.noarch >> 87/94 : vdsm-python-4.13.2-1.el6-0.ppc64 <-- ppc64 rpm >> 88/94 : vdsm-4.13.2-1.el6-0.ppc64 <-- ppc64 rpm >> 89/94 : vdsm-debuginfo-4.13.2-1.el6-0.ppc64 <-- ppc64 rpm >> 90/94 : vdsm-python-cpopen-4.13.2-1.el6-0.ppc64 <-- ppc64 rpm >> 91/94 : vdsm-python-4.13.2-1.el6-0.i686 >> 92/94 : vdsm-python-cpopen-4.13.2-1.el6-0.i686 >> 93/94 : vdsm-debuginfo-4.13.2-1.el6-0.i686 >> 94/94 : vdsm-4.13.2-1.el6-0.i686 >> Linking packages to channel. >> ERROR: Package arch ppc64 incompatible with channel ovirt-3.3.2 >> Sync completed. >> Total time: 0:00:09 >> >> best regards >> a >> >> _______________________________________________ >> Spacewalk-list mailing list >> [email protected] >> https://www.redhat.com/mailman/listinfo/spacewalk-list > > _______________________________________________ > Spacewalk-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/spacewalk-list > _______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
