Re: Proposed MBF - removal of pcre3 by Bookworm

2023-07-03 Thread Matthew Vernon
Alastair McKinstry  writes:

>> On Thu, Jun 29, 2023 at 08:55:11PM +0100, Matthew Vernon wrote:
>>> Bookworm is now out; I will shortly be increasing the severity of
>>> the outstanding bugs to RC, with the intention being to remove
>>> src:pcre3 from Debian before the trixie release.

[snip]

> There's significant work creating and testing patches for this
> transition. Marking removal is too much.

PCRE upstream have been wanting to be shot of old-pcre for a very long
time now (pcre2 has been available since 2015, and was first in Debian
stretch), and it's been essentially unsupported for a number of years
now; I had originally hoped we could ditch it from bookworm. I thought
the beginning of a release cycle was the natural time to bump to RC
severity to try and make sure we can remove pcre3 in good time for
trixie.

Regards,

Matthew

-- 
"At least you know where you are with Microsoft."
"True. I just wish I'd brought a paddle."
http://www.debian.org



Re: Proposed MBF - removal of pcre3 by Bookworm

2023-07-02 Thread Marco d'Itri
On Jul 02, Peter Pentchev  wrote:

> On the other hand, the bugs have been open for an year and a half now...
For something which has worked just fine for many years.

-- 
ciao,
Marco


signature.asc
Description: PGP signature


Re: Proposed MBF - removal of pcre3 by Bookworm

2023-07-02 Thread Peter Pentchev
On Sun, Jul 02, 2023 at 10:14:58AM +0100, Alastair McKinstry wrote:
> 
> On 01/07/2023 14:44, Michael Stone wrote:
> > On Thu, Jun 29, 2023 at 08:55:11PM +0100, Matthew Vernon wrote:
> > > Bookworm is now out; I will shortly be increasing the severity of
> > > the outstanding bugs to RC, with the intention being to remove
> > > src:pcre3 from Debian before the trixie release.
> > 
> > You don't think that marking packages for removal two weeks after the
> > bug is filed is a little much?
> 
> There's significant work creating and testing patches for this transition.
> Marking removal is too much.

On the other hand, the bugs have been open for an year and a half now...

G'luck,
Peter

-- 
Peter Pentchev  r...@ringlet.net r...@debian.org p...@storpool.com
PGP key:http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint 2EE7 A7A5 17FC 124C F115  C354 651E EFB0 2527 DF13


signature.asc
Description: PGP signature


Re: Proposed MBF - removal of pcre3 by Bookworm

2023-07-02 Thread Alastair McKinstry



On 01/07/2023 14:44, Michael Stone wrote:

On Thu, Jun 29, 2023 at 08:55:11PM +0100, Matthew Vernon wrote:
Bookworm is now out; I will shortly be increasing the severity of the 
outstanding bugs to RC, with the intention being to remove src:pcre3 
from Debian before the trixie release.


You don't think that marking packages for removal two weeks after the 
bug is filed is a little much?


There's significant work creating and testing patches for this 
transition. Marking removal is too much.



--
Alastair McKinstry,
GPG: 82383CE9165B347C787081A2CBE6BB4E5D9AD3A5
ph: +353 87 6847928 e: alast...@sceal.ie, im: @sceal.ie:mckinstry



Re: Proposed MBF - removal of pcre3 by Bookworm

2023-07-01 Thread Graham Inggs
Hi Matthew

On Thu, 29 Jun 2023 at 20:18, Matthew Vernon  wrote:
> Bookworm is now out; I will shortly be increasing the severity of the
> outstanding bugs to RC, with the intention being to remove src:pcre3
> from Debian before the trixie release.

Thanks for driving this forward!

There's a transition tracker [1] which might be helpful.

Regards
Graham


[1] https://release.debian.org/transitions/html/pcre3-to-pcre2.html



Re: Proposed MBF - removal of pcre3 by Bookworm

2023-07-01 Thread Michael Stone

On Sat, Jul 01, 2023 at 09:44:27AM -0400, Michael Stone wrote:

On Thu, Jun 29, 2023 at 08:55:11PM +0100, Matthew Vernon wrote:
Bookworm is now out; I will shortly be increasing the severity of 
the outstanding bugs to RC, with the intention being to remove 
src:pcre3 from Debian before the trixie release.


You don't think that marking packages for removal two weeks after the 
bug is filed is a little much?


Apologies, the original bug report apparently slipped under the radar.



Re: Proposed MBF - removal of pcre3 by Bookworm

2023-07-01 Thread Michael Stone

On Thu, Jun 29, 2023 at 08:55:11PM +0100, Matthew Vernon wrote:
Bookworm is now out; I will shortly be increasing the severity of the 
outstanding bugs to RC, with the intention being to remove src:pcre3 
from Debian before the trixie release.


You don't think that marking packages for removal two weeks after the 
bug is filed is a little much?




Re: Proposed MBF - removal of pcre3 by Bookworm

2023-06-29 Thread Scott Kitterman
On Thursday, June 29, 2023 3:55:11 PM EDT Matthew Vernon wrote:
> Hi,
> 
> On 13/11/2021 11:41, Matthew Vernon wrote:
> > TL;DR> pcre3 is obsolete and upstream don't want to fix it any more. I
> > propose a MBF to track our progress in getting rid of it for Bookworm
> 
> Bookworm is now out; I will shortly be increasing the severity of the
> outstanding bugs to RC, with the intention being to remove src:pcre3
> from Debian before the trixie release.
> 
> While upstream never did produce a porting guide, though there was some
> useful discussion of some of the issues on the relevant issue report[0];
> additionally, the glib gregex change set to make the change is quite
> comprehensive[1].
> 
> Regards,
> 
> Matthew
> [0] https://github.com/PCRE2Project/pcre2/issues/51
> [1] https://gitlab.gnome.org/GNOME/glib/-/merge_requests/2529

Here's the postfix change, for another example:

https://github.com/vdukhovni/postfix/commit/
3b0ac407f313135ffd74e248ad88abd2ad6dfe09

Scott K


signature.asc
Description: This is a digitally signed message part.


Re: Proposed MBF - removal of pcre3 by Bookworm

2023-06-29 Thread Sven Joachim
On 2023-06-29 20:55 +0100, Matthew Vernon wrote:

> On 13/11/2021 11:41, Matthew Vernon wrote:
>
>> TL;DR> pcre3 is obsolete and upstream don't want to fix it any
>> more. I propose a MBF to track our progress in getting rid of it for
>> Bookworm
>
> Bookworm is now out; I will shortly be increasing the severity of the
> outstanding bugs to RC, with the intention being to remove src:pcre3
> from Debian before the trixie release.

Please add the sid and trixie tags to these bugs so that people who care
about Debian (old)stable can concentrate on the bugs which actually
matter for these distributions.

Thanks,
   Sven



Re: Proposed MBF - removal of pcre3 by Bookworm

2023-06-29 Thread Matthew Vernon

Hi,

On 13/11/2021 11:41, Matthew Vernon wrote:

TL;DR> pcre3 is obsolete and upstream don't want to fix it any more. I 
propose a MBF to track our progress in getting rid of it for Bookworm


Bookworm is now out; I will shortly be increasing the severity of the 
outstanding bugs to RC, with the intention being to remove src:pcre3 
from Debian before the trixie release.


While upstream never did produce a porting guide, though there was some 
useful discussion of some of the issues on the relevant issue report[0]; 
additionally, the glib gregex change set to make the change is quite 
comprehensive[1].


Regards,

Matthew
[0] https://github.com/PCRE2Project/pcre2/issues/51
[1] https://gitlab.gnome.org/GNOME/glib/-/merge_requests/2529



Re: Proposed MBF - removal of pcre3 by Bookworm

2021-11-13 Thread Matthew Vernon
Matthew Vernon  writes:

> User: matthew-pcre...@lists.debian.org

Sigh, always one typo gets through. That should be:
User: matthew-pcre...@debian.org

Regards,

Matthew

-- 
"At least you know where you are with Microsoft."
"True. I just wish I'd brought a paddle."
http://www.debian.org