Bug 2035953 - request version bump of f35 pcre2 pkg builds from v10.37 -> v10.39
Summary: request version bump of f35 pcre2 pkg builds from v10.37 -> v10.39
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: pcre2
Version: 35
Hardware: All
OS: All
unspecified
unspecified
Target Milestone: ---
Assignee: Lukas Javorsky
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-12-28 20:02 UTC by pgnet.dev
Modified: 2022-01-16 01:18 UTC (History)
3 users (show)

Fixed In Version: pcre2-10.39-1.fc35
Clone Of:
Environment:
Last Closed: 2022-01-16 01:18:54 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description pgnet.dev 2021-12-28 20:02:38 UTC
request bump of f35 pcre2 pkg builds, @

 https://src.fedoraproject.org/rpms/pcre2

for f35 from v10.37 -> v10.39, same as rawhide, and increasingly used by upstream pkgs

v10.39 is current release

https://www.pcre.org/
There are two major versions of the PCRE library. The current version, PCRE2, released in 2015, is now at version 10.39.

released,

 Oct 29, 2021

Comment 1 Lukas Javorsky 2022-01-07 08:22:49 UTC
Hi,

Can you please tell me what's the reason you want this rebase to happen?

In packages like pcre/pcre2, we need to strongly evaluate if it's really necessary to rebase in the existing distros because it could cause a lot of trouble in case that the new versions are not compatible.

Comment 2 pgnet.dev 2022-01-07 08:44:48 UTC
> we need to strongly evaluate if it's really necessary to rebase in the existing distros because it could cause a lot of trouble in case that the new versions are not compatible.

mainly, it's the stable-release where current development+support lies.

included in the list of general bug fixes,

  https://github.com/PhilipHazel/pcre2/compare/pcre2-10.37...pcre2-10.39

are specific build system & JIT improvements

key (for us) upstream packages are building/testing against it, e.g. the nginx ecosystem

to build those locally, or @ COPR, currently requires local installs of updated pcre2 versions, and/or spec file / build-system workaround

atm, building + installing for f35 @ separate COPR

 https://copr.fedorainfracloud.org/coprs/pgfed/pcre2/

works.  and the resultant COPR repo is used subsequently for attachment to other builds, like nginx.

doable, sure.  tho, personal COPRs not ideal for wider deployment -- and are messy to manage.

Comment 4 Lukas Javorsky 2022-01-12 12:00:22 UTC
I will check the compatibility between the versions.

Comment 5 Lukas Javorsky 2022-01-14 11:20:39 UTC
I've checked the header files and the libraries symbols and it looks like it should be compatible.

I'm going to build the package and push it to the testing repo.

Comment 6 Fedora Update System 2022-01-14 12:26:35 UTC
FEDORA-2022-fe313597b9 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-fe313597b9

Comment 7 pgnet.dev 2022-01-14 13:35:08 UTC
installed these rpms on a test F35 instance, and built up a couple of servers with the libs.

so far, so good -- no immediately obvious probs

thx!

Comment 8 Fedora Update System 2022-01-15 02:15:53 UTC
FEDORA-2022-fe313597b9 has been pushed to the Fedora 35 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-fe313597b9`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-fe313597b9

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 9 Fedora Update System 2022-01-16 01:18:54 UTC
FEDORA-2022-fe313597b9 has been pushed to the Fedora 35 stable repository.
If problem still persists, please make note of it in this bug report.


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