RE: Release of 1.0

Incidentally, I haven't had a problem with a "clean" tree (no duplicate
versions, but multi arch), but that's with v0.99 running under rh7.2...

For RH7.2 clients we do not exclude the kernels because we switched from
lilo to grub (although we just discovered that grub doesn't work correctly
for mirrored drives :-( )

But I just verified that the up2date client did install the i686 version of
the kernel for those machines...
									-Rob

> -----Original Message-----
> From: Hunter Matthews [mailto:[email protected]]
> Sent: Thursday, March 14, 2002 12:22 PM
> To: Current Server Mailing List
> Subject: Re: [Current-server] Release of 1.0
> 
> 
> All, 
>    I have discovered a couple of bugs in 1.0
> 
> Specifically, multi-arch packages are broken, again.
> 
> This time, it appears that its a combo of a server bug (a bad 
> one) and a
> client bug (possibly, and if so, I'm confused).
> 
> I have a preliminary patch for the server, but we need an additional
> patch to work-around the client bug.
> 
> Work-arounds for people running 1.0 include:
>    Don't count on multi-arch packages workign correctly all 
> the time. In
> typical RH Linux tree's, this is only glibc, gzip, and the 
> kernel. Most
> people have the kernel excluded in their config file, which is why I
> think no one else has seen it.
> 
> If anyone else has seen problems with 1.0, please let me know. I'm
> trying hard for a 1.0.1 before the weekend.
> 
> if anyone knows why up2date 2.7.11 would accept an athlon 
> kernel package
> on an i686 client, let me know soonest.
> 
> 
> 
> On Mon, 2002-03-11 at 19:30, Hunter Matthews wrote:
> > All,
> >    I'll keep this short, as openssh and zlib are making my 
> life hard. 
> > Current 1.0 shipped today - its on the ftp site in tar ball and ftp
> > form.
> > 
> > Changes since 0.99.0 include:
> > New documentation on building site localized up2date and 
> rhn_register
> > pkgs
> > Bug fixes for various things
> > Cadmin now checks and won't run if current is running at 
> the same time.
> > Documentation updates.
> > 
> > I've _finally_ made the decision to use BitKeeper for network aware 
> > version control. Its a little weird, and no I don't like the license
> > either, but its the best available that i can see. If you don't like
> > BitKeer, I'll always take patches.
> > 
> > Efforts from here will be primarily on bug fixes for 1.0.x 
> and starting
> > work on the 1.1.x series, which is going to focus on the postgres 
> > patch.
> > 
> > 
> > -- 
> > Hunter Matthews                          Unix / Network 
> Administrator
> > Office: BioScience 145/244               Duke Univ. Biology 
> Department
> > Key: F0F88438 / FFB5 34C0 B350 99A4 BB02  9779 A5DB 8B09 F0F8 8438
> > Never take candy from strangers. Especially on the internet.
> > 
> > _______________________________________________
> > Current-server mailing list
> > [email protected]
> > http://lists.dulug.duke.edu/mailman/listinfo/current-server
> > 
> > 
> -- 
> Hunter Matthews                          Unix / Network Administrator
> Office: BioScience 145/244               Duke Univ. Biology Department
> Key: F0F88438 / FFB5 34C0 B350 99A4 BB02  9779 A5DB 8B09 F0F8 8438
> Never take candy from strangers. Especially on the internet.
> 
> _______________________________________________
> Current-server mailing list
> [email protected]
> http://lists.dulug.duke.edu/mailman/listinfo/current-server
>