On Tue, Sep 08, 2009 at 12:06:46PM -0500, Dennis Gilmore wrote:
On Tuesday 08 September 2009 11:52:43 am Brandon Perkins wrote:
As I understand it, the main concern that Miroslav was having in this
case was avoiding installing new versions of packages from Spacewalk
that are also shipped
2009/9/8 Dennis Gilmore den...@ausil.us:
On Friday 04 September 2009 07:33:36 am Miroslav Suchý wrote:
Today, we have both Spacewalk (and proxy) packages together in one repo
with client packages.
If somebody will install Spacewalk on RHEL he will get as side effect
all those client packages
On Tuesday 08 September 2009 11:52:43 am Brandon Perkins wrote:
Jesus M. Rodriguez wrote:
2009/9/8 Dennis Gilmore den...@ausil.us:
On Friday 04 September 2009 07:33:36 am Miroslav Suchý wrote:
Today, we have both Spacewalk (and proxy) packages together in one repo
with client packages.
On Friday 04 September 2009 07:33:36 am Miroslav Suchý wrote:
Today, we have both Spacewalk (and proxy) packages together in one repo
with client packages.
If somebody will install Spacewalk on RHEL he will get as side effect
all those client packages (rhnlib, yum-rhn-plugin,
On Tue, Sep 08, 2009 at 10:41:18AM -0500, Dennis Gilmore wrote:
We cant easily do this. Without creating a maintenance headache for
ourselves.
mash grabs all the packages from a koji tag and puts them into a repo.
taking
into account inheritance.
To implement this we would need to
On Mon, Sep 07, 2009 at 08:42:23AM +0200, Miroslav Suchý wrote:
Jesus M. Rodriguez wrote:
yum/0.7/proxy
yum/0.7/server
IMO this does not bring any benefit. A lot of packages are common. If
you install proxy, yum will not install Spacewalk server packages and
vice versa.
Right. On the
Miroslav Suchý wrote:
I suggest to split yum repo to two parts. One is Spacewalk and Proxy.
Second is client tools.
Do you agree? Do you disagree? Any comments?
OK. No objections heard.
Jesus can you give me contact on RH person responsible of
http://spacewalk.redhat.com/yum/ ?
If I
Jan Pazdziora wrote:
On Mon, Sep 07, 2009 at 08:42:23AM +0200, Miroslav Suchý wrote:
Jesus M. Rodriguez wrote:
yum/0.7/proxy
yum/0.7/server
IMO this does not bring any benefit. A lot of packages are common. If
you install proxy, yum will not install Spacewalk server packages and
vice
Today, we have both Spacewalk (and proxy) packages together in one repo
with client packages.
If somebody will install Spacewalk on RHEL he will get as side effect
all those client packages (rhnlib, yum-rhn-plugin, rhn-client-tools),
which will get him to unsupported state.
I'm not sure if this
Brandon Perkins wrote:
I completely agree, I would just also add rhnsd to the list:
rhn-client-tools
rhnlib
rhnsd
yum-rhn-plugin
This looks like the authoritative list when I looked through Koji.
There is for sure others:
rhcfg*
rhn-custom-info
osad
I did not investigate it. Neither for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Miroslav Suchý wrote:
Brandon Perkins wrote:
I completely agree, I would just also add rhnsd to the list:
rhn-client-tools
rhnlib
rhnsd
yum-rhn-plugin
This looks like the authoritative list when I looked through Koji.
There is for sure
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brandon Perkins wrote:
Miroslav Suchý wrote:
Brandon Perkins wrote:
I completely agree, I would just also add rhnsd to the list:
rhn-client-tools
rhnlib
rhnsd
yum-rhn-plugin
This looks like the authoritative list when I looked through
2009/9/4 Miroslav Suchý msu...@redhat.com:
Today, we have both Spacewalk (and proxy) packages together in one repo with
client packages.
If somebody will install Spacewalk on RHEL he will get as side effect all
those client packages (rhnlib, yum-rhn-plugin, rhn-client-tools), which will
get
13 matches
Mail list logo
