Re: [Spacewalk-list] xstream CVE-2017-7957

Eric: > The xstream package that is pulled in with Spacewalk 2.6 is vulnerable > to this.  Is there an upgraded package anywhere that anyone knows about?   > > Not sure what to do with some of the old jpackage packages that are all > Spacewalk dependencies.more and  more of these are getting

Re: [Spacewalk-list] running rhn_check from cron

> On 1 Dec 2017, at 9:13 am, Jay McCanta wrote: > > The Berkley stuff was so fragile in out environment, was almost walked away > from Spacewalk. Switching to SQLite fixed those. And if you’re using the embedded PostgreSQL database, you could use that too:

Re: [Spacewalk-list] running rhn_check from cron

The Berkley stuff was so fragile in out environment, was almost walked away from Spacewalk. Switching to SQLite fixed those. Sent from my iPhone On Nov 30, 2017, at 1:32 PM, Avi Miller > wrote: EXTERNAL MAIL:

Re: [Spacewalk-list] Repository Sync List

Yes! Thank You for the Feature and the fast response! From: spacewalk-list-boun...@redhat.com [mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Avi Miller Sent: Thursday, November 30, 2017 3:32 PM To: spacewalk-list@redhat.com Subject: Re: [Spacewalk-list] Repository Sync List EXTERNAL

Re: [Spacewalk-list] Repository Sync List

Hi, > On 1 Dec 2017, at 7:28 am, Ron Skantz wrote: > > Seems like I used to have a python script: repo_sync_schedule.py > The script would list the current schedule for syncing each channel wit it’s > repository. I added this to spacecmd a while back: # spacecmd

[Spacewalk-list] Repository Sync List

I am currently running Spacewalk 2.6 Seems like I used to have a python script: repo_sync_schedule.py The script would list the current schedule for syncing each channel wit it’s repository. Maybe it was a part of an old Spacewalk version, but I am looking for this functionality. Anybody

[Spacewalk-list] running rhn_check from cron

I am looking at using spacewalk for orchestration - for instance, I want to be able to upgrade an app on a group of servers every month without any downtime.  To do this, I would need to ensure that the app installs successfully on every server within a specific time frame.  I have osad running

Re: [Spacewalk-list] broken/bad update notices

Hi again, Apologies, it’s 6:15am here and I’m only on my first coffee. :) I didn’t fully read your initial email and I thought the errors were occurring during a spacewalk-repo-sync to our sources. > On 1 Dec 2017, at 6:16 am, Avi Miller wrote: > > >> On 1 Dec 2017,

Re: [Spacewalk-list] broken/bad update notices

Hi, > On 1 Dec 2017, at 2:20 am, Robin Beardsley wrote: > > While doing a yum update I see all of these messages and I’m really not sure > where they are coming from, my spacewalk server or the external repository? > Has anyone seen this? I’ll look into it. It might

[Spacewalk-list] xstream CVE-2017-7957

The xstream package that is pulled in with Spacewalk 2.6 is vulnerable to this.  Is there an upgraded package anywhere that anyone knows about?   Not sure what to do with some of the old jpackage packages that are all Spacewalk dependencies.more and  more of these are getting flagged by

[Spacewalk-list] broken/bad update notices

While doing a yum update I see all of these messages and I'm really not sure where they are coming from, my spacewalk server or the external repository? Has anyone seen this? Loaded plugins: langpacks, rhnplugin, versionlock This system is receiving updates from Spacewalk server. Update notice

Re: [Spacewalk-list] create distribution channel map

Afify, Sherif S (IBS): > Whenever I try to create distribution channel map for RHEL 7 clients I got > the below error , any one faced that before ? > > "New Distribution Channel Mapping 'Red Hat Enterprise Linux Server' cannot be > created. Release - Architecture combination already exists."