[tools] mrepo now has YOU support

Dag Wieers dag at wieers.com
Tue Nov 13 19:20:06 CET 2007


On Mon, 12 Nov 2007, Nicole Hähnel wrote:

> Dag Wieers schrieb:
> > On Fri, 9 Nov 2007, Nicole Hähnel wrote:
> > > Dag Wieers schrieb:
> > > > Great feedback, Nicole.
> > > >
> > > > Are you sure that you need the updates channel as well ? I would expect
> > > > (but could be terribly wrong) that the OES updates include the OS
> > > > updates
> > > > (as OES includes the OS).
> > > >
> > > > The reason why I am asking is because I would like to understand whether
> > > > OES is a seperate distribution or not. I think it is, but if you still
> > > > need the SLES10 updates channel, maybe I should make OES just a SLES10
> > > > repository.
> > > >
> > > > What do you think based on your experience ?
> > > >
> > > > PS Thanks for getting back, I was wondering this morning in the shower
> > > > what happened ans was going to contact you later today :)
> > > >
> > > >
> > > >
> > > You're right for the first version of OES.
> > > There is only one update channel which includes both update packages, for
> > > OES
> > > and SLES9.
> > >
> > > OES2 is an add-on which can be included during the installation of SLES10
> > > SP1.
> > > So OES2 is not included in SLES10 like OES in SLES9.
> > > Furthermore the update agent ZMD shows to channels for updates
> > > (OES2-Updates
> > > and SLES10SP1-Updates).
> >
> > Would it be possible for you to create a profile for both OES and OES2
> > that I can put in the next mrepo release ? It makes it much easier for
> > people to configure if they can rely on a working example.
>
> I hope these profiles are correct...
> One thing is a little bit obscure, if I update the OES1 servers with rug there
> are updates and patches in the channel
> and novell says only to install the patches, never the updates.
> I don't know the difference between updates and patches.
> Our servers are still running, although we install only the updates.
> Maybe anybody knows more about that?

The patch RPMs are differential RPMs against the previous version. The
update RPMS are the complete RPMs. Novell invented patch RPMs so that you
do not have to download complete RPMs for small changes to RPM packages.

But the result is a bit more complex to manage. In the end, the result
should be the same, but Novell probably advises patch RPMs because they
stress their own servers/bandwidth less and save you on bandwidth at the
same time.


> I'm happy to use mrepo to get all my updates for RHEL, SLES and OES on one
> server, so that I dont' have to build something wild to get all updates!

Yeah, the next step is to make sure we can create the metadata for yast
(both for NLD9/SLES9 and SLES10). I have heard that the createrepo is
modified (probably to support patch RPMs).

What we desperately lack is a single tool that can create different
metadata formats in a single run and does not require the latest and
greatest python. This is currently a problem, whether you have a recent
system as a distribution server, or an old system.

I have added your 2 config files.

-- 
--   dag wieers,  dag at wieers.com,  http://dag.wieers.com/   --
[Any errors in spelling, tact or fact are transmission errors]


More information about the tools mailing list