On Thu, 15 Jan 2009 06:34:31 +0100, Cristóbal Palmer
wrote:
I found this page in the wiki:
https://fedorahosted.org/spacewalk/wiki/Deb_support_in_spacewalk
And wondered how I can help. I'm happy to test, provide additional
virtual machine clients or spacewalk hosts, etc.
Ping off-list if t
I found this page in the wiki:
https://fedorahosted.org/spacewalk/wiki/Deb_support_in_spacewalk
And wondered how I can help. I'm happy to test, provide additional
virtual machine clients or spacewalk hosts, etc.
Ping off-list if that's appropriate.
Thanks,
--
Cristóbal Palmer
ibiblio.org syste
Clifford Perry wrote:
Jan Pazdziora wrote:
On Wed, Jan 14, 2009 at 08:57:38AM -0400, Devan Goodwin wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Actually, this AVC denial is about different problem. So it was not
a good example.
But nevertheless: shouldn't we decide for env or direct
Thanks Jeff,
Will give that a try tomorrow morning.
Vikram
On Thu, Jan 15, 2009 at 12:27 AM, Jeff Ortel wrote:
> Hey Vikram,
>
> I'd suggest you follow the developer setup instructions on the Spacewalk
> wiki:
>
> https://fedorahosted.org/spacewalk/wiki/DevelopmentWorkstationSetup
>
> ~jeff
>
Hey Vikram,
I'd suggest you follow the developer setup instructions on the Spacewalk
wiki:
https://fedorahosted.org/spacewalk/wiki/DevelopmentWorkstationSetup
~jeff
Vikram Rai wrote:
Hi,
We were trying to install spacewalk using souce on Redhat 5 Enterprise
Server and after giving the co
Devan Goodwin wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 13 Jan 2009 17:11:25 +0530
"Gurjeet Singh" wrote:
Hi All,
I am a bit late in doing this, but I think it is necessary, so
here it goes.
The migration of the Spacewalk project to support Postgres has
started, a
Jan Pazdziora wrote:
On Wed, Jan 14, 2009 at 08:57:38AM -0400, Devan Goodwin wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Actually, this AVC denial is about different problem. So it was not
a good example.
But nevertheless: shouldn't we decide for env or direct path in the
shebang lin
Please hold your commits to master for now, we're finalizing Spacewalk 0.4
builds. If you've got 0.4 bugs to fix, please definitely use master. If
not, hold off or use a branch for now.
Thanks
jesus
--
jesus m. rodriguez| jes...@redhat.com
sr. software engineer | irc: zeus
rhn sate
Pradeep Kilambi wrote:
John hit a similar issue recently. But it was happening only on x86_64
version and i386 iso was working fine. We suspected his setup. But now
since we have another reproducer, can you open a bug on this and assign
it to me. I'll take a peek at it sometime this week.
Tha
Devan Goodwin wrote:
On Wed, 14 Jan 2009 12:13:20 +0100
Jan Pazdziora wrote:
On Wed, Jan 14, 2009 at 10:36:37AM +0100, Jan Pazdziora wrote:
I propose to phase out
#!/usr/bin/env python
in favour of
#!/usr/bin/python
in our python scripts.
Speak now or forever hold
On Wed, Jan 14, 2009 at 08:57:38AM -0400, Devan Goodwin wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> > Actually, this AVC denial is about different problem. So it was not
> > a good example.
> >
> > But nevertheless: shouldn't we decide for env or direct path in the
> > shebang li
Gurjeet Singh wrote:
Hi All,
I am a bit late in doing this, but I think it is necessary, so here
it goes.
The migration of the Spacewalk project to support Postgres has
started, and EnterpriseDB is collaborating with Redhat and Spacewalk
developers on this. For now, the people invo
Devan Goodwin wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 14 Jan 2009 12:13:20 +0100
Jan Pazdziora wrote:
On Wed, Jan 14, 2009 at 10:36:37AM +0100, Jan Pazdziora wrote:
I propose to phase out
#!/usr/bin/env python
in favour of
#!/usr/bin/python
in
John hit a similar issue recently. But it was happening only on x86_64
version and i386 iso was working fine. We suspected his setup. But now
since we have another reproducer, can you open a bug on this and assign
it to me. I'll take a peek at it sometime this week.
Thanks,
~ Prad
Mike McCun
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 14 Jan 2009 12:13:20 +0100
Jan Pazdziora wrote:
> On Wed, Jan 14, 2009 at 10:36:37AM +0100, Jan Pazdziora wrote:
> >
> > I propose to phase out
> >
> > #!/usr/bin/env python
> >
> > in favour of
> >
> > #!/usr/bin/python
> >
> >
On 1/14/09, Jan Pazdziora wrote:
> On Wed, Jan 14, 2009 at 11:35:49AM +, travellig travellig wrote:
>> >>
>> >> osa-dispatcher is only needed if you wanna use osad from the clients.
>> >> Since osad is not a default package, I don't see why osa-dispatcher
>> >> should be installed by default w
On Wed, Jan 14, 2009 at 11:35:49AM +, travellig travellig wrote:
> >>
> >> osa-dispatcher is only needed if you wanna use osad from the clients.
> >> Since osad is not a default package, I don't see why osa-dispatcher
> >> should be installed by default with spacewalk.
> >
> > One reason is tha
On 1/14/09, Jan Pazdziora wrote:
> On Thu, Jan 08, 2009 at 09:42:13AM -0500, Pradeep Kilambi wrote:
>> Milan Zazrivec wrote:
>>> Is there any reason why we don't pull osa-dispatcher & jabberpy with
>>> spacewalk.rpm? (both packages are commented out in spacewalk.spec)
>>
>> osa-dispatcher is only
On Wed, Jan 14, 2009 at 10:36:37AM +0100, Jan Pazdziora wrote:
>
> I propose to phase out
>
> #!/usr/bin/env python
>
> in favour of
>
> #!/usr/bin/python
>
> in our python scripts.
>
> Speak now or forever hold your peace.
>
> Note that we already use the second form 182 times i
On Thu, Jan 08, 2009 at 09:42:13AM -0500, Pradeep Kilambi wrote:
> Milan Zazrivec wrote:
>> Is there any reason why we don't pull osa-dispatcher & jabberpy with
>> spacewalk.rpm? (both packages are commented out in spacewalk.spec)
>
> osa-dispatcher is only needed if you wanna use osad from the cli
I propose to phase out
#!/usr/bin/env python
in favour of
#!/usr/bin/python
in our python scripts.
Speak now or forever hold your peace.
Note that we already use the second form 182 times in non-test
scripts, while we use env 63 times.
The current problem that I'm solving is
21 matches
Mail list logo
