Bug 2171317 - [packaging] 110.0-3 (110.0 build 3) lacks version anchor on nss >= 3.88 (3.87 won't suffice for page loading)
Summary: [packaging] 110.0-3 (110.0 build 3) lacks version anchor on nss >= 3.88 (3.87...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: firefox
Version: 39
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-02-19 21:56 UTC by Jan Pokorný [poki]
Modified: 2024-11-27 21:05 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-11-27 21:05:08 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1789539 0 unspecified CLOSED firefox-72.0.1-1.fc31 doesn't render ANY page, all pages are blank (needs nss and nspr bump in spec file) 2023-02-19 21:57:37 UTC

Description Jan Pokorný [poki] 2023-02-19 21:56:03 UTC
I think I've seen this before, and indeed: [bug 1789539].

Can something be done about this apparently fragile lack of explicit
lockstep at times (for when one updates packages selectively, which
for something as exposed as web browser could be pretty justified)?

Where casual SONAME/symbol versioning fails us?  Is it because of the
tight firefox-nss development coupling that some best practices on the
ABI/API compat front are neglected?

Coincidentally, I've just noticed that automatic dependencies generation
seems to receive a new wave of attention if that might help in this
use case as well:

https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/EZFX5ARQWOXBUXID4HH74ETD2QBF2DPB/

* * *

In particular:

* firefox-110.0-2.fc39.x86_64 + nss-3.87.0-1.fc38.x86_64 -> OK
* firefox-110.0-3.fc39.x86_64 + nss-3.87.0-1.fc38.x86_64 -> no page loading
* firefox-110.0-2.fc39.x86_64 + nss-3.88.1-2.fc39.x86_64 -> OK

Comment 1 Jan Pokorný [poki] 2023-02-19 21:57:38 UTC
* firefox-110.0-3.fc39.x86_64 + nss-3.88.1-2.fc39.x86_64 -> OK

Comment 2 Fedora Release Engineering 2023-08-16 07:07:20 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 39 development cycle.
Changing version to 39.

Comment 3 Aoife Moloney 2024-11-08 10:46:44 UTC
This message is a reminder that Fedora Linux 39 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 39 on 2024-11-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '39'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 39 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 4 Aoife Moloney 2024-11-27 21:05:08 UTC
Fedora Linux 39 entered end-of-life (EOL) status on 2024-11-26.

Fedora Linux 39 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.