Re: Retiring the pcre package from Fedora

Of course, only the deprecation will be moved to F38. The removal is stalled until the deprecation is completed. Once done, the new Fedora change will start from the beginning, containing the removal. It looks like the community is okay with moving the deprecation to F38, so I'll move it. On Tue

Re: Retiring the pcre package from Fedora

On Tue, Aug 23, 2022 at 10:23 AM Lukas Javorsky wrote: > > Hello Zbigniew, > > I would love to have it on F38, but I'm not sure it would be enough time for > all of the maintainers whose packages depend on the old pcre. > > Ben, do you think we can make this to F38? Moving the *deprecation* to F

Re: Retiring the pcre package from Fedora

Hello Zbigniew, I would love to have it on F38, but I'm not sure it would be enough time for all of the maintainers whose packages depend on the old pcre. Ben, do you think we can make this to F38? Thank you for answering. Lukas On Fri, Aug 19, 2022 at 3:33 PM Ben Cotton wrote: > On Thu, Aug

Re: Retiring the pcre package from Fedora

On Thu, Aug 18, 2022 at 5:30 AM Zbigniew Jędrzejewski-Szmek wrote: > > Why F39? Shouldn't the deprecation (and the work on porting) be already > happening for F38? I'm going to wait to process the proposal until we have an answer to this question. (I believe Lukas is out of the office, so it may

Re: Retiring the pcre package from Fedora

On Thu, Aug 18, 2022 at 11:21:05AM +0200, Lukas Javorsky wrote: > I've just finished the pcre deprecation change [1]. > If anyone is interested, please take a look. > > [1] https://fedoraproject.org/wiki/PcreDeprecation Why F39? Shouldn't the deprecation (and the work on porting) be already happ

Re: Retiring the pcre package from Fedora

I've just finished the pcre deprecation change [1]. If anyone is interested, please take a look. [1] https://fedoraproject.org/wiki/PcreDeprecation Lukas On Wed, Aug 17, 2022 at 2:43 PM Lukas Javorsky wrote: > Hi Richard, > > The Fedora 39 System Wide changes are scheduled for Jun 2023, so tha

Re: Retiring the pcre package from Fedora

Hi Richard, The Fedora 39 System Wide changes are scheduled for Jun 2023, so that would be the deadline for this. However, after feedback, I've decided to create a pcre deprecation change at first so it's broken into more pieces and it's better documented. When it's ready, I'll paste the link for

Re: Retiring the pcre package from Fedora

On Wed, Aug 17, 2022 at 02:25:06PM +0200, Lukas Javorsky wrote: > The Fedora change for this topic is created [1]. > > [1] https://fedoraproject.org/wiki/PcreRetirement It would be helpful to have an actual deadline written in there. "Fedora 39" requires an indirection. Are we talking 2023? 202

Re: Retiring the pcre package from Fedora

The Fedora change for this topic is created [1]. [1] https://fedoraproject.org/wiki/PcreRetirement On Mon, Aug 15, 2022 at 11:46 AM Lukas Javorsky wrote: > Hi, > > I've decided to write a Fedora change that will contain all of the > information about this possible retirement. > > I have to fill

Re: Retiring the pcre package from Fedora

Hi, I've decided to write a Fedora change that will contain all of the information about this possible retirement. I have to fill the dependencies that will be affected by this change, so I'm looking for the tool/command which will give them to me. I've seen multiple suggestions here in this thre

Re: Retiring the pcre package from Fedora

Due to static linking, not all functions will be included in the executable and therefore some simple "hello world" binaries will not need sysprof-capture-static. However, anything that used the .pc file will need it. Technically, you could also use glib's static library without dependent .a libr

Re: Retiring the pcre package from Fedora

On Tue, Jul 26, 2022 at 10:59 AM Daniel P. Berrangé wrote: > On Tue, Jul 26, 2022 at 10:10:15AM +0200, Kalev Lember wrote: > > > > On 7/26/22 07:47, Paolo Bonzini wrote: > > > On 7/24/22 15:42, Kalev Lember wrote: > > > > On Sun, Jul 24, 2022 at 8:58 AM Paolo Bonzini > > >

Re: Retiring the pcre package from Fedora

On Tue, Jul 26, 2022 at 10:10:15AM +0200, Kalev Lember wrote: > > On 7/26/22 07:47, Paolo Bonzini wrote: > > On 7/24/22 15:42, Kalev Lember wrote: > > > On Sun, Jul 24, 2022 at 8:58 AM Paolo Bonzini > > > wrote: > > > > > > > > > > > >     Il sab 23 lug 2022, 19:12

Re: Retiring the pcre package from Fedora

On Sat, Jul 23, 2022 at 11:09:29AM +0100, Richard W.M. Jones wrote: > > virt-p2v-1:1.42.1-1.fc37.src > > This is a real one. virt-p2v uses a small library called "miniexpect" > which is based on pcre but needs to be ported to pcre2. Fixed upstream now, I'll put it into Fedora after the next upst

Re: Retiring the pcre package from Fedora

On Sun, Jul 24, 2022 at 08:58:18AM +0200, Paolo Bonzini wrote: > Il sab 23 lug 2022, 19:12 Adam Williamson ha > scritto: > > > This of course begs a question: did qemu also have a non-static pcre > > requirement at the time? But it seems not: > > > > [adamw@xps13k qemu (f36 %)]$ git show 0835325:

Re: Retiring the pcre package from Fedora

On Tue, Jul 26, 2022 at 10:19:55AM +0200, Paolo Bonzini wrote: > On Tue, Jul 26, 2022 at 10:10 AM Kalev Lember wrote: > > Does this look right to you? Do you want me to add them in other > > branches as well or is rawhide sufficient for now? > > Rawhide is enough, for other branches QEMU is worki

Re: Retiring the pcre package from Fedora

On Tue, Jul 26, 2022 at 10:10 AM Kalev Lember wrote: > Does this look right to you? Do you want me to add them in other > branches as well or is rawhide sufficient for now? Rawhide is enough, for other branches QEMU is working around it by requiring pcre-static. Thanks! I'm now debugging the SIG

Re: Retiring the pcre package from Fedora

On 7/25/22 10:23, Mamoru TASAKA wrote: Kalev Lember wrote on 2022/07/25 0:45: Those both sound a lot like regressions in g_regex_match() to me. If you have time, any chance you could create smaller reproducers and file issues for these upstream at https://gitlab.gnome.org/GNOME/glib ? For is

Re: Retiring the pcre package from Fedora

On 7/26/22 07:47, Paolo Bonzini wrote: On 7/24/22 15:42, Kalev Lember wrote: On Sun, Jul 24, 2022 at 8:58 AM Paolo Bonzini > wrote:     Il sab 23 lug 2022, 19:12 Adam Williamson     mailto:adamw...@fedoraproject.org>> ha     scritto:     This of course begs a

Re: Retiring the pcre package from Fedora

On 7/24/22 15:42, Kalev Lember wrote: On Sun, Jul 24, 2022 at 8:58 AM Paolo Bonzini > wrote: Il sab 23 lug 2022, 19:12 Adam Williamson mailto:adamw...@fedoraproject.org>> ha scritto: This of course begs a question: did qemu also have a non-stati

Re: repoquery-fu (was Re: Retiring the pcre package from Fedora)

On Mon, Jul 25, 2022 at 1:50 AM Demi Marie Obenour wrote: > > Rust *already* has full dynamic linking support, and this is used > on Android to save space and memory. What Rust does not have is > a stable ABI. Therefore, when Rust code changes, all Rust code > depending on it must be recompiled.

Re: Retiring the pcre package from Fedora

On Fri, 2022-07-22 at 14:52 +0200, Petr Pisar wrote: > V Fri, Jul 22, 2022 at 02:24:00PM +0200, Lukas Javorsky napsal(a): > > As from the pcre-8.45, the upstream stopped supporting this > > library. The > > recommended procedure is to switch onto the new pcre2 library that > > has full > > upstream

Re: Retiring the pcre package from Fedora

On Sat, Jul 23, 2022 at 5:55 PM Kevin Kofler via devel wrote: > > We just need to accept that we need to maintain pcre as a compatibility > library for the foreseeable future. I'm sympathetic to your "we shouldn't block people from maintaining things if they want to" argument, but I have to disag

Re: Retiring the pcre package from Fedora

V Mon, Jul 25, 2022 at 11:38:49AM +0200, Lukas Javorsky napsal(a): > I'm still going to create a COPR build for every dependent package with > change from "pcre" to "pcre2" requirement, so I can report each of the > components, if it's able to just simply change to pcre2 or need to port. If you fi

Re: Retiring the pcre package from Fedora

Quite a lot of reading but thanks everyone for the emails. Few observations I get from this email thread (correct me if I misunderstood anything): 1) We don't have a unified process for how to do such a retirement/orphan package workflow. 2) We don't have a deterministic unified tool/script for

Re: Retiring the pcre package from Fedora

Kalev Lember wrote on 2022/07/25 0:45: On Sun, Jul 24, 2022 at 4:45 PM Mamoru TASAKA wrote: Kalev Lember wrote on 2022/07/24 22:42: glib2 switched to pcre2 in rawhide recently. Can you check if qemu needs to be updated for that now so that it BuildRequires pcre2-static instead? https://s

Re: repoquery-fu (was Re: Retiring the pcre package from Fedora)

On Sat, Jul 23, 2022 at 2:01 PM Neal Gompa wrote: > > On Sat, Jul 23, 2022 at 7:47 AM Fabio Valentini wrote: > > > > - the sets of dependent packages overlap between concurrently created side > > tags > > So what? If we're not tracking rebuilds in Git anymore, this is no > longer a serious probl

Re: Retiring the pcre package from Fedora

On Sun, Jul 24, 2022 at 4:45 PM Mamoru TASAKA wrote: > Kalev Lember wrote on 2022/07/24 22:42: > > glib2 switched to pcre2 in rawhide recently. Can you check if qemu needs > to > > be updated for that now so that it BuildRequires pcre2-static instead? > > > > > https://src.fedoraproject.org/rpms/

Re: Retiring the pcre package from Fedora

Kalev Lember wrote on 2022/07/24 22:42: On Sun, Jul 24, 2022 at 8:58 AM Paolo Bonzini wrote: glib2 switched to pcre2 in rawhide recently. Can you check if qemu needs to be updated for that now so that it BuildRequires pcre2-static instead? https://src.fedoraproject.org/rpms/glib2/c/34b203d

Re: Retiring the pcre package from Fedora

On Sun, Jul 24, 2022 at 8:58 AM Paolo Bonzini wrote: > > > Il sab 23 lug 2022, 19:12 Adam Williamson ha > scritto: > >> This of course begs a question: did qemu also have a non-static pcre >> requirement at the time? But it seems not: >> >> [adamw@xps13k qemu (f36 %)]$ git show 0835325:qemu.spec

Re: Retiring the pcre package from Fedora

Il sab 23 lug 2022, 19:12 Adam Williamson ha scritto: > This of course begs a question: did qemu also have a non-static pcre > requirement at the time? But it seems not: > > [adamw@xps13k qemu (f36 %)]$ git show 0835325:qemu.spec | grep pcre > BuildRequires: glibc-static pcre-static glib2-static

Re: Retiring the pcre package from Fedora

Stewart Smith via devel wrote: > cppcheck can be built without HAVE_RULES which will avoid pcre at the > expense of functionality. I do not think that it makes sense to build stuff with reduced functionality just to avoid a pcre dependency. We just need to accept that we need to maintain pcre as

Re: Retiring the pcre package from Fedora

Lukas Javorsky writes: > Hi, > > As from the pcre-8.45, the upstream stopped supporting this > library. The recommended procedure is to switch onto the new pcre2 > library that has full upstream support. [1] I was looking into doing this as much as possible for AL2022 and managed to dig a bit on

Re: Retiring the pcre package from Fedora

On 23. 07. 22 0:22, Maxwell G via devel wrote: (It seems my previous message didn't send properly...) On 22/07/22 10:24PM, Fabio Valentini wrote: the script that determines leaf packages in the Rust SIG Can you provide a link to this? $ (dnf repoquery --whatrequires pcre ; dnf repoquery --

Re: Retiring the pcre package from Fedora

On Sat, 2022-07-23 at 11:09 +0100, Richard W.M. Jones wrote: > > > qemu-2:7.0.0-6.fc37.src > > I looked at the qemu sources and I can't see where they need pcre (or > pcre2 for that matter) ... So I've no idea why the spec file > BuildRequires pcre-static. Behold, the glory of git: [adamw@xps1

Re: Retiring the pcre package from Fedora

On Fri, Jul 22, 2022 at 3:28 PM Richard W.M. Jones wrote: > > On Fri, Jul 22, 2022 at 02:24:00PM +0200, Lukas Javorsky wrote: > > perl > > Wait what, Perl _depends_ on PCRE ...?! > Uhh? I don't see any direct PCRE dependency in the package spec or generated packages...? But yeah, that one i

Re: Retiring the pcre package from Fedora

On Fri, Jul 22, 2022 at 10:24:08PM +0200, Fabio Valentini wrote: > -> pcre or any of its subpackages are BuildRequired by: > [...] > ocaml-pcre-0:7.5.0-6.fc37.src So two OCaml packages need this: coccinelle -> https://sympa.inria.fr/sympa/arc/cocci/2022-07/msg00026.html (scroll down a bit

Re: Retiring the pcre package from Fedora

On 22/07/2022 14:24, Lukas Javorsky wrote: As from the pcre-8.45, the upstream stopped supporting this library. The recommended procedure is to switch onto the new pcre2 library that has full upstream support. [1] Feel free to transfer this package to me. FAS: xvitaly I will continue maintena

Re: Retiring the pcre package from Fedora

Fabio Valentini wrote: > It would be entirely possible to mark the package as deprecated, but > also give it to new maintainers. Why not leave the decision to the new maintainers then? I do not see a good reason to prevent adding software depending on pcre (1) as long as somebody maintains pcre

Re: Retiring the pcre package from Fedora

On Sat, Jul 23, 2022 at 12:23 AM Kevin Kofler via devel wrote: > > Fabio Valentini wrote: > > Given that there's a very long list of affected packages, just > > dropping the package in a few weeks would have disastrous effects on > > Fedora. > > I also see core components of several Editions and S

Re: repoquery-fu (was Re: Retiring the pcre package from Fedora)

On Fri, Jul 22, 2022 at 11:47 PM Maxwell G wrote: > > On 22/07/22 10:24PM, Fabio Valentini wrote: > > the script that determines leaf packages in the Rust SIG > > Can you provide a link to this? I can, now that I've published it (again): https://pagure.io/ironthree/fedora-rust-sig-leaf-check It'

Re: Retiring the pcre package from Fedora

Fabio Valentini wrote: > Given that there's a very long list of affected packages, just > dropping the package in a few weeks would have disastrous effects on > Fedora. > I also see core components of several Editions and Spins on that list, > so I assume just dropping pcre would also make QA, Rele

Re: Retiring the pcre package from Fedora

(It seems my previous message didn't send properly...) On 22/07/22 10:24PM, Fabio Valentini wrote: > the script that determines leaf packages in the Rust SIG Can you provide a link to this? > $ (dnf repoquery --whatrequires pcre ; dnf repoquery --whatrequires > pcre-cpp ; dnf repoquery --whatre

repoquery-fu (was Re: Retiring the pcre package from Fedora)

On 22/07/22 10:24PM, Fabio Valentini wrote: > the script that determines leaf packages in the Rust SIG Can you provide a link to this? > $ (dnf repoquery --whatrequires pcre ; dnf repoquery --whatrequires > pcre-cpp ; dnf repoquery --whatrequires pcre-devel ; dnf repoquery > --whatrequires pcre-s

Re: Retiring the pcre package from Fedora

Hi, Lukas Javorsky writes: > i3 > i3-gaps there is a patch to make i3 (and thus i3-gaps) compatible with pcre2 [1], which has been merged upstream. I can cherry pick it and rebuild i3 in Rawhide without requiring pcre, if this is urgent. Otherwise I'd rather wait for the next upstream release.

Re: Retiring the pcre package from Fedora

* Lukas Javorsky [22/07/2022 14:24] : > > perl-HTML-Template-Pro I'll build against pcre2 in the coming days (probably this weekend). Emmanuel ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedo

Re: Retiring the pcre package from Fedora

On Fri, Jul 22, 2022 at 08:24:32AM -0500, Richard Shaw wrote: > On Fri, Jul 22, 2022 at 8:22 AM Lukas Javorsky wrote: > > Thanks for all of the replies, > > The list of affected packages I've provided was generated using the 'dnf > repoquery --alldeps --whatrequires pcre' > Is th

Re: Retiring the pcre package from Fedora

On Fri, Jul 22, 2022 at 02:24:00PM +0200, Lukas Javorsky wrote: > coccinelle This is an optional dependency but we'd lose a particular feature by disabling it. I have asked upstream if they plan to port to PCRE2. Also the OCaml bindings they are using for regexps don't support PCRE2 (see below).

Re: Retiring the pcre package from Fedora

V Fri, Jul 22, 2022 at 03:21:02PM +0200, Lukas Javorsky napsal(a): > The list of affected packages I've provided was generated using the 'dnf > repoquery --alldeps --whatrequires pcre' > > Is this command giving the right output or should I use another? If so > which one? > If I run your command o

Re: Retiring the pcre package from Fedora

On Fri, Jul 22, 2022 at 03:21:02PM +0200, Lukas Javorsky wrote: > Thanks for all of the replies, > > The list of affected packages I've provided was generated using the 'dnf > repoquery --alldeps --whatrequires pcre' > Is this command giving the right output or should I use another? If so > which

Re: Retiring the pcre package from Fedora

Thanks for all of the replies, The list of affected packages I've provided was generated using the 'dnf repoquery --alldeps --whatrequires pcre' Is this command giving the right output or should I use another? If so which one? We will definitely discuss all of these concerns within the team and g

Re: Retiring the pcre package from Fedora

On Fri, Jul 22, 2022 at 8:25 AM Lukas Javorsky wrote: > > As a result of this announcement, the older PCRE library in Fedora will be > retired. > Without upstream support, we don't have enough capacity to keep up with the > security and bugs-related issues, and thus we will support only the new

Re: Retiring the pcre package from Fedora

On 22/07/2022 14:24, Lukas Javorsky wrote: As from the pcre-8.45, the upstream stopped supporting this library. If it builds from sources we can maintain it in downstream due to a big number of dependent packages. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___

Re: Retiring the pcre package from Fedora

On Fri, Jul 22, 2022 at 2:25 PM Lukas Javorsky wrote: > > Hi, > > As from the pcre-8.45, the upstream stopped supporting this library. The > recommended procedure is to switch onto the new pcre2 library that has full > upstream support. [1] > > As a result of this announcement, the older PCRE li

Re: Retiring the pcre package from Fedora

V Fri, Jul 22, 2022 at 02:24:00PM +0200, Lukas Javorsky napsal(a): > As from the pcre-8.45, the upstream stopped supporting this library. The > recommended procedure is to switch onto the new pcre2 library that has full > upstream support. [1] > > As a result of this announcement, the older PCRE l

Retiring the pcre package from Fedora

Hi, As from the pcre-8.45, the upstream stopped supporting this library. The recommended procedure is to switch onto the new pcre2 library that has full upstream support. [1] As a result of this announcement, the older PCRE library in Fedora will be retired. Without upstream support, we don't hav