Bug#982310: libglib2.0-dev: Depends directly on libpcre3-dev (old) and indirectly on libpcre2-dev (new)

[Diederik de Haas]

FTR: https://gitlab.gnome.org/GNOME/glib/-/merge_requests/2529 seems to be the 
(latest) effort to actually resolve this issue upstream.

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

Bug#982310: libglib2.0-dev: Depends directly on libpcre3-dev (old) and indirectly on libpcre2-dev (new)

[Diederik de Haas]

Hi,

On maandag 8 februari 2021 19:01:21 CEST Simon McVittie wrote:
> Control: tags -1 + upstream wontfix
> Control: forwarded -1 https://gitlab.gnome.org/GNOME/glib/-/issues/1085

It looks like that is/was an excellent forward :-)

> If this is ever solved, it will have to be solved upstream. Fixing this
> in a Debian-specific way is not something that can usefully happen.
> 
> According to
> ,
> GRegex "cannot be moved to PCRE2 without breaking its API contract",
> so it might not be possible to solve this upstream either.

https://gitlab.gnome.org/GNOME/glib/-/issues/1085#note_1266560 by Christian 
Persch (who is also OP of that issue) seems to shine a new light on the issue 
in that it may be fixed upstream after all!

I don't have to knowledge/insight to determine that with certainty, so I've 
not adjusted any tags. But I hope/assume that you can.

Cheers,
  Diederik

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

Bug#982310: libglib2.0-dev: Depends directly on libpcre3-dev (old) and indirectly on libpcre2-dev (new)

[Simon McVittie]

Control: severity -1 wishlist
Control: tags -1 + upstream wontfix
Control: forwarded -1 https://gitlab.gnome.org/GNOME/glib/-/issues/1085

On Mon, 08 Feb 2021 at 16:53:41 +0100, Diederik de Haas wrote:
> I just did an "apt-get build-dep linux" and noticed that both old
> (pcre3) as new (pcre2) PCRE libs got installed.
> Quering aptitude as to why, pointed both towards libglib2.0-dev.
> That seems silly/weird to me, hence this bug report.

Unfortunately, GLib's GRegex API (which is considered to be deprecated)
is implemented in terms of PCRE 8.x (pcre3).

See also ,
,
.

If this is ever solved, it will have to be solved upstream. Fixing this
in a Debian-specific way is not something that can usefully happen.

According to
,
GRegex "cannot be moved to PCRE2 without breaking its API contract",
so it might not be possible to solve this upstream either.

smcv

Bug#982310: libglib2.0-dev: Depends directly on libpcre3-dev (old) and indirectly on libpcre2-dev (new)

[Diederik de Haas]

Package: libglib2.0-dev
Version: 2.66.6-1
Severity: normal

I just did an "apt-get build-dep linux" and noticed that both old
(pcre3) as new (pcre2) PCRE libs got installed.
Quering aptitude as to why, pointed both towards libglib2.0-dev.
That seems silly/weird to me, hence this bug report.

$ aptitude why libpcre2-16-0
i   libglib2.0-dev  Depends libselinux1-dev  
i A libselinux1-dev Depends libpcre2-dev 
i A libpcre2-devDepends libpcre2-16-0 (= 10.36-2)
$ aptitude why libpcre16-3
i   libglib2.0-dev Depends libpcre3-dev (>= 1:8.31) 
i A libpcre3-dev   Depends libpcre16-3 (= 2:8.39-13)


-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 
'unstable'), (500, 'testing'), (101, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-3-amd64 (SMP w/16 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libglib2.0-dev depends on:
ii  libffi-dev  3.3-5
ii  libglib2.0-02.66.6-1
ii  libglib2.0-bin  2.66.6-1
ii  libglib2.0-dev-bin  2.66.6-1
ii  libmount-dev2.36.1-7
ii  libpcre3-dev2:8.39-13
ii  libselinux1-dev 3.1-2+b2
ii  pkg-config  0.29.2-1
ii  zlib1g-dev  1:1.2.11.dfsg-2

libglib2.0-dev recommends no packages.

Versions of packages libglib2.0-dev suggests:
pn  libgirepository1.0-dev  
pn  libglib2.0-doc  

-- no debconf information