Here's what I just used to recreate all my channels and repos for Spacewalk 2.7. For security patches and general updates, I'm using channels combining repos for both main and universe. We don't tend to use multiverse packages, so we haven't created the channels & repos for that because it's not worth it to us allocating the disk space. So you might want to tweak this, either to have separate main and universe channels or to add multiverse. We also deploy from CD or VM template cloning, so I didn't bother adding a universe repo for the base channel. I've also got a custom channel for locally patched spacewalk client builds.
I'm curious to hear whether other Ubuntu Spacewalk users do things differently and how/why. spacecmd softwarechannel_create ' -n "Ubuntu 14.04 (x86_64)" -l "trusty" -a amd64-deb -c sha256 -p "" ' spacecmd softwarechannel_create ' -n "trusty-backports" -l "trusty-backports" -a amd64-deb -c sha256 -p "trusty" ' spacecmd softwarechannel_create ' -n "trusty-security" -l "trusty-security" -a amd64-deb -c sha256 -p "trusty" ' spacecmd softwarechannel_create ' -n "trusty-spacewalk-client" -l "trusty-spacewalk-client" -a amd64-deb -c sha256 -p "trusty" ' spacecmd softwarechannel_create ' -n "trusty-updates" -l "trusty-updates" -a amd64-deb -c sha256 -p "trusty" ' spacecmd softwarechannel_create ' -n "Ubuntu 16.04 (x86_64)" -l "xenial" -a amd64-deb -c sha256 -p "" ' spacecmd softwarechannel_create ' -n "xenial-backports" -l "xenial-backports" -a amd64-deb -c sha256 -p "xenial"' spacecmd softwarechannel_create ' -n "xenial-security" -l "xenial-security" -a amd64-deb -c sha256 -p "xenial"' spacecmd softwarechannel_create ' -n "xenial-updates" -l "xenial-updates" -a amd64-deb -c sha256 -p "xenial" ' spacecmd repo_create ' -n "External - Ubuntu 14.04 backports x86_64" -u "http://ca.archive.ubuntu.com/ubuntu/dists/trusty-backports/main/binary-amd64/" -t deb' spacecmd repo_create ' -n "External - Ubuntu 14.04 security x86_64" -u "http://ca.archive.ubuntu.com/ubuntu/dists/trusty-security/main/binary-amd64/" -t deb' spacecmd repo_create ' -n "External - Ubuntu 14.04 universe security x86_64" -u "http://ca.archive.ubuntu.com/ubuntu/dists/trusty-security/universe/binary-amd64/" -t deb' spacecmd repo_create ' -n "External - Ubuntu 14.04 universe updates x86_64" -u "http://ca.archive.ubuntu.com/ubuntu/dists/trusty-updates/universe/binary-amd64/" -t deb' spacecmd repo_create ' -n "External - Ubuntu 14.04 updates x86_64" -u "http://ca.archive.ubuntu.com/ubuntu/dists/trusty-updates/main/binary-amd64/" -t deb' spacecmd repo_create ' -n "External - Ubuntu 14.04 x86_64" -u "http://ca.archive.ubuntu.com/ubuntu/dists/trusty/main/binary-amd64/" -t deb' spacecmd repo_create ' -n "External - Ubuntu 16.04 backports x86_64" -u "http://ca.archive.ubuntu.com/ubuntu/dists/xenial-backports/main/binary-amd64/" -t deb' spacecmd repo_create ' -n "External - Ubuntu 16.04 security x86_64" -u "http://ca.archive.ubuntu.com/ubuntu/dists/xenial-security/main/binary-amd64/" -t deb' spacecmd repo_create ' -n "External - Ubuntu 16.04 universe security x86_64" -u "http://ca.archive.ubuntu.com/ubuntu/dists/xenial-security/universe/binary-amd64/" -t deb' spacecmd repo_create ' -n "External - Ubuntu 16.04 universe updates x86_64" -u "http://ca.archive.ubuntu.com/ubuntu/dists/xenial-updates/universe/binary-amd64/" -t deb' spacecmd repo_create ' -n "External - Ubuntu 16.04 updates x86_64" -u "http://ca.archive.ubuntu.com/ubuntu/dists/xenial-updates/main/binary-amd64/" -t deb' spacecmd repo_create ' -n "External - Ubuntu 16.04 x86_64" -u "http://ca.archive.ubuntu.com/ubuntu/dists/xenial/main/binary-amd64/" -t deb' spacecmd softwarechannel_addrepo '"trusty" "External - Ubuntu 14.04 x86_64"' spacecmd softwarechannel_addrepo '"trusty-backports" "External - Ubuntu 14.04 backports x86_64"' spacecmd softwarechannel_addrepo '"trusty-security" "External - Ubuntu 14.04 security x86_64"' spacecmd softwarechannel_addrepo '"trusty-security" "External - Ubuntu 14.04 universe security x86_64"' spacecmd softwarechannel_addrepo '"trusty-updates" "External - Ubuntu 14.04 universe updates x86_64"' spacecmd softwarechannel_addrepo '"trusty-updates" "External - Ubuntu 14.04 updates x86_64"' spacecmd softwarechannel_addrepo '"xenial" "External - Ubuntu 16.04 x86_64"' spacecmd softwarechannel_addrepo '"xenial-backports" "External - Ubuntu 16.04 backports x86_64"' spacecmd softwarechannel_addrepo '"xenial-security" "External - Ubuntu 16.04 security x86_64"' spacecmd softwarechannel_addrepo '"xenial-security" "External - Ubuntu 16.04 universe security x86_64"' spacecmd softwarechannel_addrepo '"xenial-updates" "External - Ubuntu 16.04 universe updates x86_64"' spacecmd softwarechannel_addrepo '"xenial-updates" "External - Ubuntu 16.04 updates x86_64"' spacecmd softwarechannel_setsyncschedule '"trusty" 0 5 1 8 * ?' spacecmd softwarechannel_setsyncschedule '"trusty-backports" 0 15 1 8 * ?' spacecmd softwarechannel_setsyncschedule '"trusty-security" 0 16 1 8 * ?' spacecmd softwarechannel_setsyncschedule '"trusty-updates" 0 20 1 8 * ?' spacecmd softwarechannel_setsyncschedule '"xenial" 0 30 1 8 * ?' spacecmd softwarechannel_setsyncschedule '"xenial-backports" 0 40 1 8 * ?' spacecmd softwarechannel_setsyncschedule '"xenial-security" 0 41 1 8 * ?' spacecmd softwarechannel_setsyncschedule '"xenial-updates" 0 50 1 8 * ?' Paul-Andre Panon Senior systems administrator Office: 604.629.5182 ext 2341 Mobile: 604.679.1617 -----Original Message----- From: Paul-Andre Panon Sent: Wednesday, August 9, 2017 10:47 AM To: [email protected] Subject: Re: [Spacewalk-list] Help setting up Ubuntu channel(s) On Tue, 8 Aug 2017 20:18:41, Dimitri Yioulos <[email protected]> wrote: >It's more that I'm having problems getting the repos right. For example, >based on stuff I've read, I'm trying >to use the following Ubuntu repo: >http://us.archive.ubuntu.com/ubuntu/dists/xenial/main/binary-amd64/. >But, >when I run repo-sync, I get the following: >[root@spacewalk dyioulos]# /usr/bin/spacewalk-repo-sync --channel >ubuntu-16.04-lts-main >15:28:27 ====================================== >15:28:27 | Channel: ubuntu-16.04-lts-main >15:28:27 ====================================== >15:28:27 Sync of channel started. >15:28:27 Repo URL: >http://us.archive.ubuntu.com/ubuntu/dists/xenial/main/binary-amd64/ >15:28:27 ERROR: Cannot retrieve repository metadata (repomd.xml) for >repository: ubuntu_dists_xenial_main_binary-amd64_. Please verify its path and >try again >15:28:27 Repo URL: >http://de.archive.ubuntu.com/ubuntu/dists/xenial-security/main/binary-amd64/ >15:28:28 ERROR: Cannot retrieve repository metadata (repomd.xml) for >repository: ubuntu_dists_xenial-security_main_binary-amd64_. Please verify its >path and try again >15:28:28 Sync of channel completed in 0:00:00. >15:28:28 Total time: 0:00:00 >Note this - ERROR: Cannot retrieve repository metadata (repomd.xml). Isn't >repodm.xml yum-related? >Anyway, as I said above, I primarily need the help >getting the repos set up. >Best, >Dimitri Check that your channels have the right settings for checksum type (SHA256) and Architecture (AMD64 Debian). If they don't then you will need to delete and recreate them. Paul-Andre Panon Senior systems administrator _______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
