[WBEL-devel] Testers needed

[John Morris]

I just posted errata packages for cvs, openoffice and squid but have not
updated the yum headers. There is a reason for this.

Last weekend builder.whiteboxlinux.org was wiped clean and went into
service as the primary server for beau.org. This means a new build host
was needed. In preparation for migrating to an AMD64 buildhost at home, I
have built up a chroot environment for building normal ia32 packages. The
packages above were built in said environment and I'd like someone who
uses them to have a look before I unlease them to up2date/yum automated
downloading.

To get them before the mirror sync try:

http://whiteboxlinux.org/pub/3.0/en/updates/i386/cvs-1.11.2-18.i386.rpm
http://whiteboxlinux.org/pub/3.0/en/updates/i386/openoffice.org-1.1.0-15.EL.i386.rpm
http://whiteboxlinux.org/pub/3.0/en/updates/i386/openoffice.org-i18n-1.1.0-15.EL.i386.rpm
http://whiteboxlinux.org/pub/3.0/en/updates/i386/openoffice.org-libs-1.1.0-15.EL.i386.rpm
http://whiteboxlinux.org/pub/3.0/en/updates/i386/squid-2.5.STABLE3-5.3E.i386.rpm

[Johnny Hughes]

Post by John Morris
http://whiteboxlinux.org/pub/3.0/en/updates/i386/cvs-1.11.2-18.i386.rpm
http://whiteboxlinux.org/pub/3.0/en/updates/i386/openoffice.org-1.1.0-15.EL.i386.rpm
http://whiteboxlinux.org/pub/3.0/en/updates/i386/openoffice.org-i18n-1.1.0-15.EL.i386.rpm
http://whiteboxlinux.org/pub/3.0/en/updates/i386/openoffice.org-libs-1.1.0-15.EL.i386.rpm
http://whiteboxlinux.org/pub/3.0/en/updates/i386/squid-2.5.STABLE3-5.3E.i386.rpm

I downloaded and installed all via:

rpm -Uvh *

I have tested cvs and openoffice.org. They both seem to work correctly
for me as root and as non-root users.

I don't have squid running (but it was installed on this
Install-Everything test box). The install completed without errors.

-Johnny Hughes

[Greg Hosler (Greg Hosler)]

Post by Johnny Hughes

Post by John Morris
http://whiteboxlinux.org/pub/3.0/en/updates/i386/cvs-1.11.2-18.i386.rpm
http://whiteboxlinux.org/pub/3.0/en/updates/i386/openoffice.org-1.1.0-15.EL.i
386.rpm
http://whiteboxlinux.org/pub/3.0/en/updates/i386/openoffice.org-i18n-1.1.0-15
.EL.i386.rpm
http://whiteboxlinux.org/pub/3.0/en/updates/i386/openoffice.org-libs-1.1.0-15
.EL.i386.rpm
http://whiteboxlinux.org/pub/3.0/en/updates/i386/squid-2.5.STABLE3-5.3E.i386.
rpm

rpm -Uvh *
I have tested cvs and openoffice.org.

Did the openoffice.org rpm *really* upgrade ?

I have RHEL3, and when I did the equivelent on RHEL3, the openoffice.org rpms
do NOT upgrade. The reason is simple. The package name is different from the
originally installed one. The original openoffice rpm is openoffice.#; the
errata is named openoffice.org-# -- as near as I can tell, rpm would *never*
consider openoffice.org as a candidate for openoffice, and as far as I can
see, that's why the rpm -Fvh that I did, did not update the original
openoffice's rpms.

So... I'm curious. did your openoffice.org rpm really update ?

What does the following display:

rpm -qa "openoffice*"

best rgds,

-Greg

Post by Johnny Hughes
They both seem to work correctly
for me as root and as non-root users.
I don't have squid running (but it was installed on this
Install-Everything test box). The install completed without errors.
-Johnny Hughes
_______________________________________________
Whitebox-devel mailing list
http://beau.org/mailman/listinfo/whitebox-devel

+---------------------------------------------------------------------+
You can release software that's good, software that's inexpensive, or
software that's available on time. You can usually release software
that has 2 of these 3 attributes -- but not all 3.
| Greg Hosler ***@hosler.per.sg |
+---------------------------------------------------------------------+

[William Hooper]

Post by Greg Hosler (Greg Hosler)
Did the openoffice.org rpm *really* upgrade ?
I have RHEL3, and when I did the equivelent on RHEL3, the openoffice.org rpms
do NOT upgrade.

Worked for me using up2date (albeit against RHN not a yum repo). I'll
have to update the headers and try it on my WBEL machine... nope, doesn't
work (against a yum repo).

[Rex Dieter]

Post by Greg Hosler (Greg Hosler)

Post by Johnny Hughes

Post by John Morris
http://whiteboxlinux.org/pub/3.0/en/updates/i386/cvs-1.11.2-18.i386.rpm
http://whiteboxlinux.org/pub/3.0/en/updates/i386/openoffice.org-1.1.0-15.EL.i
386.rpm
http://whiteboxlinux.org/pub/3.0/en/updates/i386/openoffice.org-i18n-1.1.0-15
.EL.i386.rpm
http://whiteboxlinux.org/pub/3.0/en/updates/i386/openoffice.org-libs-1.1.0-15
.EL.i386.rpm
http://whiteboxlinux.org/pub/3.0/en/updates/i386/squid-2.5.STABLE3-5.3E.i386.
rpm

rpm -Uvh *
I have tested cvs and openoffice.org.

Did the openoffice.org rpm *really* upgrade ?
I have RHEL3, and when I did the equivelent on RHEL3, the openoffice.org rpms
do NOT upgrade. The reason is simple. The package name is different from the
originally installed one.

Yes, but, the packages *do* contain
Obsoletes:
tags, but unfortunately, recent rpm (rpm-4.2.1 and newer) apparently
broke this. )-:

-- Rex

[Lance Davis]

Post by Greg Hosler (Greg Hosler)

Post by Johnny Hughes
rpm -Uvh *
I have tested cvs and openoffice.org.

Did the openoffice.org rpm *really* upgrade ?
I have RHEL3, and when I did the equivelent on RHEL3, the openoffice.org rpms
do NOT upgrade. The reason is simple. The package name is different from the
originally installed one. The original openoffice rpm is openoffice.#; the
errata is named openoffice.org-# -- as near as I can tell, rpm would *never*
consider openoffice.org as a candidate for openoffice, and as far as I can
see, that's why the rpm -Fvh that I did, did not update the original
openoffice's rpms.

rpm -Fvh doesnt

Post by Greg Hosler (Greg Hosler)
So... I'm curious. did your openoffice.org rpm really update ?

rpm -Uvh does work

similarily with yum - yum update wont pick it up - but 'yum upgrade
openoffice' will.

Lance

[Johnny Hughes]

Post by Lance Davis

Post by Greg Hosler (Greg Hosler)

Post by Johnny Hughes
rpm -Uvh *
I have tested cvs and openoffice.org.

Did the openoffice.org rpm *really* upgrade ?
I have RHEL3, and when I did the equivelent on RHEL3, the openoffice.org rpms
do NOT upgrade. The reason is simple. The package name is different from the
originally installed one. The original openoffice rpm is openoffice.#; the
errata is named openoffice.org-# -- as near as I can tell, rpm would *never*
consider openoffice.org as a candidate for openoffice, and as far as I can
see, that's why the rpm -Fvh that I did, did not update the original
openoffice's rpms.

rpm -Fvh doesnt

Post by Greg Hosler (Greg Hosler)
So... I'm curious. did your openoffice.org rpm really update ?

rpm -Uvh does work

I have indeed verified that I only have openoffice.org and not
openoffice rpms ... and that:

rpm -Uvh

does do the upgrade correctly

all my shortcuts still work as well ...

Post by Lance Davis
similarily with yum - yum update wont pick it up - but 'yum upgrade
openoffice' will.
Lance

- Johnny Hughes

[John Morris]

Post by Greg Hosler (Greg Hosler)
Did the openoffice.org rpm *really* upgrade ?

Oh crud. I know I didn't notice the name change. The change extends down
to the rpm package name inside the .spec, probably a trademark issue since
OO.o insists that the program must NEVER be referred to as simply
OpenOffice but that the .org be included. Would be funny if RedHat got a
C&D letter.

Don't know how this one can be worked around, manual intervention is just
going to be required. Better post something on the webpage and in the
errata notice when I send that out in a bit.

[Simon J Mudd]

Post by John Morris

Post by Greg Hosler (Greg Hosler)
Did the openoffice.org rpm *really* upgrade ?

Oh crud. I know I didn't notice the name change. The change extends down
to the rpm package name inside the .spec, probably a trademark issue since
OO.o insists that the program must NEVER be referred to as simply
OpenOffice but that the .org be included. Would be funny if RedHat got a
C&D letter.
Don't know how this one can be worked around, manual intervention is just
going to be required. Better post something on the webpage and in the
errata notice when I send that out in a bit.

Perhaps you can create an empty openoffice (wrapper) package which
requires openoffice.org.

upgrading openoffice (wrapper) and fulfilling dependencies will
perform the required upgrade which leaves an empty package with the
original name which can be deleted later.

Just put in the rpm -qi output what the package is for and that it is
only required for the upgrade from the previous version.

Simon