A tested back port of the patch to 1.7 is attached in the ticket. The
developer who owns the ticket has refused to apply it to the 1.7 branch
because he feals we should focus on getting cobbler 2.2 to work so 1.8 can
be released instead of applying bug fixes to the current stable version.
You may
I am going to submit this in the ticket latter but I accidentally
locked my self out of bugzilla from my ip
I successfully back ported the patch to 1.7 tested it and confirmed its working
attached is the diff generated against the 1.7 branch of the git repo
On Wed, Aug 22, 2012 at 12:02 PM,
I also found this effects spacewalk-base as well
rpm -qf /usr/share/perl5/vendor_perl/RHN/DB/DataSource/xml/profile_queries.xml
spacewalk-base-1.7.28-1.el6.noarch
On Thu, Aug 23, 2012 at 7:04 PM, Paul Robert Marino prmari...@gmail.com wrote:
I am going to submit this in the ticket latter but
ive updated the ticket hopefully a new version can be generated soon
On Thu, Aug 23, 2012 at 7:06 PM, Paul Robert Marino prmari...@gmail.com wrote:
I also found this effects spacewalk-base as well
rpm -qf
/usr/share/perl5/vendor_perl/RHN/DB/DataSource/xml/profile_queries.xml
We are using Spacewalk 1.7 on a Scientific Linux 6 system, fully patched, with
an external PostgreSQL 8.4.12-1 on a Scientific Linux 6 server, again fully
patched.
I've just created a stored profile of a system since I want to later create
more similar systems. However when I select the
I've hit this one, but running PostgreSQL on the same box and it was Rhel5:
https://bugzilla.redhat.com/show_bug.cgi?id=809897
Possibly related/the cause.
-Original Message-
From: spacewalk-list-boun...@redhat.com
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Ree,
Thanks, somehow I missed that bugreport while searching. The output looks
similar enough that I'm guessing it's the same issue. I will wait for 1.8 to be
released as this Spacewalk install is used for production.
Thanks for the quick hints.
Regards,
--
Jan-Albert
Jan-Albert van Ree
Linux
Wow thanks for reminding me I want to see if that fix can be backported to
1.7
I've been working on back porting a few others and I forgot about this one.
On Aug 22, 2012 11:41 AM, Anton Pritchard-Meaker
anton.pritchard-mea...@kit-digital.com wrote:
I've hit this one, but running PostgreSQL on
Well I'm going to attempt to back port it into my test 1.7 instance if it
works ill submit the git diff against the 1.7 branch so an updated rpm can
be generated.
On Aug 22, 2012 11:50 AM, Ree, Jan-Albert van j.a.v@marin.nl wrote:
Thanks, somehow I missed that bugreport while searching. The
