Thanks for the reply, Paul. Unfortunately, that doesn't seem to be the case for me. If I run the sync from the command line, it completes in seconds with the X86_64 error message (syncing from the GUI also doesn't work, obviously). Also, in the "Full Software Channel List", while other channels show the number of packages acquired during the sync, the Samba channel shows a zero. It seems I've tried every combination of entry when creating the channel/repo, and it errors, one way or the other. What really ticks me off is that I once had the channel working. I just don't remember how. Arrrrgh!
Dimitri On Monday 05 August 2013 7:07:18 pm Paul Robert Marino wrote: > The error message isn't wrong the repo on the site is > just strange. All that means is it can't sync the X86_64 > packages so it will ignore them the rest should sync > fine. > > I get the same error from HP's ProLiant repos because it > contains source rpms however the channels in spacewalk > still work despite the errors. > > > > -- Sent from my HP Pre3 > > On Aug 5, 2013 18:10, Thomas Foster > <[email protected]> wrote: > > change the architecture to x86_64 for the repo..then try > and sync > > > On Mon, Aug 5, 2013 at 4:50 PM, Dimitri Yioulos > <[email protected]> wrote: > > On the Spacewalk server? > > With respect, what difference should it make? The > Spacewalk server is built on CentOS 6, but has Spacewalk > repos for CentOS 5 that sync just fine. > > Dimitri > > On Monday 05 August 2013 4:34:10 pm Thomas Foster wrote: > > What's the output of yum repolist ? > > > > On Mon, Aug 5, 2013 at 4:14 PM, Dimitri Yioulos > > <[email protected]>wrote: > > > Thomas, > > > > > > Yes, and yes. > > > > > > Dimitri > > > > > > On Monday 05 August 2013 4:00:26 pm Thomas Foster wrote: > > > > Did you just add the repo? If so, did you yum > > > > clean metadata? > > > > > > > > On Mon, Aug 5, 2013 at 3:41 PM, Lewis Donofrio > > > > > > <[email protected]>wrote: > > > > > I'm new here but why not use 2nd party Centos > > > > > repo's for samba? > > > > > > > > > > -- > > > > > ________________________________________________ > > > > >___ > > > > > > > > > >____ ____________ > > > > > > > > > > https://www.vizify.com/lewis-donofrio - > > > > > > > > > > 734-743-1743 > > > > > > > > > > On Mon, Aug 5, 2013 at 3:26 PM, Dimitri Yioulos > > > > > > <[email protected]>wrote: > > > > >> H, all. > > > > >> > > > > >> I recently upgraded Spacewalk to the latest and > > > > >> greatest from version 1.8. Unfortunately, the > > > > >> upgrade didn't go well, and all of my settings > > > > >> were lost. The silver lining here is that, by > > > > >> recreating everything, I learned a lot (or, at > > > > >> least, refreshed my memory). > > > > >> > > > > >> However, I'm having a problem getting on > > > > >> recreated cahnnel/repo working. Many of our > > > > >> Linux boxes use Samba; the packages come from > > > > >> Sernet. I created the channel and repo for my > > > > >> CentOS 5 systems, but the repo won't sync. When > > > > >> I try to sync from the command line, here's the > > > > >> output I get: > > > > >> > > > > >> spacewalk-repo-sync --channel sernet-samba-el5 > > > > >> --type yum Repo URL: > > > > >> http://ftp.sernet.de/pub/samba/3.6/rhel/5 > > > > >> Packages in repo: 22 > > > > >> Packages already synced: 0 > > > > >> Packages to sync: 22 > > > > >> 1/22 : samba3-utils-3.6.17-45.el5-0.x86_64 > > > > >> 2/22 : samba3-winbind-3.6.17-45.el5-0.x86_64 > > > > >> 3/22 : > > > > >> libsmbclient-devel-3.6.17-45.el5-0.x86_64 4/22 > > > > >> : libwbclient0-32bit-3.6.17-45.el5-0.i386 5/22 > > > > >> : libwbclient-devel-3.6.17-45.el5-0.x86_64 6/22 > > > > >> : samba3-doc-3.6.17-45.el5-0.x86_64 7/22 : > > > > >> libwbclient0-3.6.17-45.el5-0.x86_64 8/22 : > > > > >> samba3-3.6.17-45.el5-0.x86_64 > > > > >> 9/22 : samba3-debuginfo-3.6.17-45.el5-0.x86_64 > > > > >> 10/22 : samba3-client-3.6.17-45.el5-0.x86_64 > > > > >> 11/22 : libsmbclient0-3.6.17-45.el5-0.x86_64 > > > > >> 12/22 : > > > > >> samba3-winbind-32bit-3.6.17-45.el5-0.i386 13/22 > > > > >> : samba3-winbind-3.6.17-45.el5-0.i386 14/22 : > > > > >> libwbclient0-3.6.17-45.el5-0.i386 15/22 : > > > > >> samba3-3.6.17-45.el5-0.i386 > > > > >> 16/22 : samba3-client-3.6.17-45.el5-0.i386 > > > > >> 17/22 : samba3-debuginfo-3.6.17-45.el5-0.i386 > > > > >> 18/22 : libsmbclient-devel-3.6.17-45.el5-0.i386 > > > > >> 19/22 : samba3-doc-3.6.17-45.el5-0.i386 > > > > >> 20/22 : libsmbclient0-3.6.17-45.el5-0.i386 > > > > >> 21/22 : samba3-utils-3.6.17-45.el5-0.i386 > > > > >> 22/22 : libwbclient-devel-3.6.17-45.el5-0.i386 > > > > >> Linking packages to channel. > > > > >> ERROR: Package arch x86_64 incompatible with > > > > >> channel sernet-samba-el5 > > > > >> Sync completed. > > > > >> Total time: 0:00:06 > > > > >> > > > > >> The machines to be updated are 32-bit. I chose > > > > >> IA-32 as the Architecture, and the repo url is > > > > >> http://ftp.sernet.de/pub/samba/3.6/rhel/5. If > > > > >> I make it > > > > >> http://ftp.sernet.de/pub/samba/3.6/rhel/5/i386, > > > > >> I get "ERROR: Cannot retrieve repository > > > > >> metadata (repomd.xml) for repostory: > > > > >> sernet-samba-el5. Please verify its path and > > > > >> try again. > > > > >> > > > > >> What's frustrating is that I did have this > > > > >> working before. Any help would be greatly > > > > >> appreciated. > > > > >> > > > > >> Dimitri > > > > >> > > > > >> -- > > > > >> This message has been scanned for viruses and > > > > >> dangerous content by MailScanner, and is > > > > >> believed to be clean. > > > > >> > > > > >> _______________________________________________ > > > > >> Spacewalk-list mailing list > > > > >> [email protected] > > > > >> https://www.redhat.com/mailman/listinfo/spacewa > > > > >>lk- list > > > > > > > > > > -- > > > > > > > > > > > > > > > _______________________________________________ > > > > > Spacewalk-list mailing list > > > > > [email protected] > > > > > https://www.redhat.com/mailman/listinfo/spacewal > > > > >k-l ist > > > > > > -- > > > This message has been scanned for viruses and > > > dangerous content by MailScanner, and is > > > believed to be clean. > > > > > > _______________________________________________ > > > Spacewalk-list mailing list > > > [email protected] > > > https://www.redhat.com/mailman/listinfo/spacewalk-li > > >st > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > > _______________________________________________ > Spacewalk-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/spacewalk-list -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. _______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
