[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Fw: fedora legacy broken upgrade paths (was: Broken upgrade paths inFC+FE 2006-06-28)



Hi Chris,

Thought you might wish to be aware of the following for current Fedora Core releases... it looks like we in Legacy botched up the upgrade path for the current Mozilla product, Mozilla-1.7.13-xxxx.

Might we be able to figure out a way to overcome this?  Also-- as we in Legacy work on other formerly-core packages, do you, Chris, or you, Josh, or any of you on this mailing list have any suggestions on what we need to do to coordinate our package naming so we don't botch up any future upgrade paths?

Incidentally, Chris or Josh:  Is there any news about the Mozilla-1.7.13 backports I have been given to understand you are working with to fix the most critical of the Mozilla vulnerability issues?  Once there are Mozilla-1.7.13 packages released for RHEL, are there plans to subsequently release similar packages for FC5, FC6, rawhide?

Thanks a bunch in advance!

    Warm Regards,

    David Eisenstein


----- Original Message ----- 
From: "Axel Thimm" <Axel Thimm ATrpms net>
To: <fedora-legacy-list redhat com>
Cc: "Discussion related to Fedora Extras" <fedora-extras-list redhat com>
Sent: Thursday, June 29, 2006 12:48 AM
Subject: fedora legacy broken upgrade paths (was: Broken upgrade paths inFC+FE 2006-06-28)


> --
> fedora-legacy-list mailing list
> fedora-legacy-list redhat com
> https://www.redhat.com/mailman/listinfo/fedora-legacy-list
Hi,

I extracted the FL relevant parts of broken upgrade paths. This is
part of an automated mail sent to the fedora-extras list:

On Wed, Jun 28, 2006 at 09:10:24AM -0400, buildsys fedoraproject org wrote:
> mozilla:
>   3: 37:1.7.13-1.3.1.legacy (FL3-updates)
>   4: 37:1.7.13-1.1.fc4 (FC4-updates)
>   5: 37:1.7.13-1.1.fc5 (FC5-updates)
>   6: 37:1.7.13-1.1.fc5 (FC6)

This happend because instead of "fc3" the disttag was chosen to be
simply "3" which is rpm-bigger than any "fcX".

The only way to fix FL broken paths is to bump the evr of the
subsequent releases :/

FL or a spokesman of FL like Jesse need to lobby FC or FE for
something like this to happen. Let's hope there will be some new
security issue in mozilla 1.7.13 soon ;)
-- 
Axel.Thimm at ATrpms.net

Attachment: ATT00111.dat
Description: Binary data


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]