Bug#1019724: bug#57604: Bug#1019724: warning: stray \ before - causes autopkgtest failure

[Paul Eggert]

On 9/19/22 05:32, Santiago Ruano Rincón wrote:


as you can read below, there are 4235 packages including the
warning in their build logs. Funnily, grep is also in the list :-)


Grep is on the list because Debian indirectly requires ucf to build 
Grep, and ucf issues the warning about stray \ because ucf mistakenly 
uses a Perlism in a grep regular expression 
. This particular warning doesn't break 
anything; it merely alerts installers of a screwup that happens to work 
but relies on undefined results.


We're thinking about adding a configure-time option to Grep to disable 
warnings about egrep/fgrep, to address the original Grep bug report 
. I'm not so sure about disabling warnings 
about bad escapes, as these warnings are so often a win and so rarely a 
loss, as is the case with ucf. Of course there is a tradeoff here 
between (a) having to wade through a bunch of annoying warnings, and (b) 
fixing packages so that they don't rely on undefined results.


Since the main issue here seems to be libtool-related test failures, how 
about patching libtool and letting the affected packages use the patched 
libtool? You can find a patch here:


https://savannah.gnu.org/patch/index.php?10282
https://savannah.gnu.org/patch/download.php?file_id=53720

The libtool test failures are false alarms, so another option would be 
to ignore the failures until libtool gets fixed.



For more on this thorny topic, please see:

https://www.gnu.org/software/grep/manual/html_node/Problematic-Expressions.html

The stray \ issue is the 19th bullet.

Bug#1019724: warning: stray \ before - causes autopkgtest failure

[Santiago Ruano Rincón]

El 18/09/22 a las 07:57, Lucas Nussbaum escribió:
> Hi,
> 
> On 16/09/22 at 21:35 +0200, Paul Gevers wrote:
> > Hi Santiago,
> > 
> > On 15-09-2022 09:26, Paul Gevers wrote:
> > > I am trying to schedule autopkgtests in unstable on amd64 for all source
> > > packages that have one.
> > 
> > All results are now in. Only several test failed due this warning: the known
> > dpkg and cjet and the newly found nagios-plugins-contrib, logcheck and
> > xautolock (see links below).
> > 
> > > Lucas, are you in the position to do an archive rebuild to check for the
> > > grep warnings (see full history at [1]). When you submit bugs, can you
> > > please file them as important, as apparently upstream wants to turn
> > > these warnings into failures in the future, but in Debian Santiago is
> > > going to silence the warning soon, so FTBFS due to this isn't an RC
> > > problem on the short term.
> > > 
> > > Santiago, please keep the grep with warning in unstable until either all
> > > tests are finished or we abort this plan.
> > 
> > To be honest, without bug 1019326 in ucf and bug 1019725 in libtool fixed,
> > I'm not sure how much value an archive rebuild would be at this stage.
> > 
> > So I think it would be good to silence the warning now in Debian. As
> > discussed before, ideally with a way to turn it on (or make it error) such
> > that we can do archive wide QA before the behavior is changed to error out
> > upstream. I can understand it if you want to wait with deploying that
> > optional behavior until upstream has implemented it.

Dear grep developers,

Just to say that I am also in favor to *temporarily* silence the stray-\
warnings. In the Debian context, the most problematic are the failing
autopkgtests, since they could block the transition of a package from
unstable to testing. Even if there are a few packages, as listed above
(including dpkg), that currently have a failing test due to the stray-\
warning, it would be great to avoid new autopkgtests fails due to that.

Also, as you can read below, there are 4235 packages including the
warning in their build logs. Funnily, grep is also in the list :-)

> I did an archive rebuild (not specifically for this). Grepping the logs,
> the following 4235 packages exhibit the warning.
> 
[snip]
> gregwar-captcha grep gretl gri grisbi groff gromacs groonga grub2 grub
[snip]

You can find the warnings in e.g. the last amd64 3.8-2 build:
https://buildd.debian.org/status/fetch.php?pkg=grep=amd64=3.8-2=1662998047=0

(Thanks Lucas for running the archive rebuild!)

Hopefully, these are "just warnings" for now. I do agree the erroneous
patterns should be fixed, but I would prefer if we could have a smoother
transition before they result in grep errors.
As proposed by Paul Gevers, could you please consider silencing the
stray-\ warning for now, and adding a mechanism (envvar or option, as
you prefer) to enable them?

Cheers,

 -- S


signature.asc
Description: PGP signature

Bug#1019724: warning: stray \ before - causes autopkgtest failure

[Lucas Nussbaum]

Hi,

On 16/09/22 at 21:35 +0200, Paul Gevers wrote:
> Hi Santiago,
> 
> On 15-09-2022 09:26, Paul Gevers wrote:
> > I am trying to schedule autopkgtests in unstable on amd64 for all source
> > packages that have one.
> 
> All results are now in. Only several test failed due this warning: the known
> dpkg and cjet and the newly found nagios-plugins-contrib, logcheck and
> xautolock (see links below).
> 
> > Lucas, are you in the position to do an archive rebuild to check for the
> > grep warnings (see full history at [1]). When you submit bugs, can you
> > please file them as important, as apparently upstream wants to turn
> > these warnings into failures in the future, but in Debian Santiago is
> > going to silence the warning soon, so FTBFS due to this isn't an RC
> > problem on the short term.
> > 
> > Santiago, please keep the grep with warning in unstable until either all
> > tests are finished or we abort this plan.
> 
> To be honest, without bug 1019326 in ucf and bug 1019725 in libtool fixed,
> I'm not sure how much value an archive rebuild would be at this stage.
> 
> So I think it would be good to silence the warning now in Debian. As
> discussed before, ideally with a way to turn it on (or make it error) such
> that we can do archive wide QA before the behavior is changed to error out
> upstream. I can understand it if you want to wait with deploying that
> optional behavior until upstream has implemented it.

I did an archive rebuild (not specifically for this). Grepping the logs,
the following 4235 packages exhibit the warning.

389-ds-base 4ti2 a2ps aalib abcl abind abinit abiword abntex acct
acepack acorn ada-reference-manual adapta-gtk-theme adasockets adios
adminer adms adolc adplay adplug advi aeskulap afflib agg aghermann
aiksaurus aircrack-ng alberta ale alex allegro4.4 alsa-oss alsaplayer
altree amanda amide amp amphp-amp amsynth ancient angband anjuta ann
anosql anymeal apcupsd apertium-lex-tools apertium apophenia apparmor
appindicator3-sharp apvlv arctica-greeter aria2 ario arpack++ arpack
array-info asc asn1c aspell aspic asunder asymptote asyncpg atf
atlas-cpp atlas-ecmwf atlas atril auctex audiofile augeas
auto-multiple-choice autoconf-archive autoconf2.13 autoconf2.64
autoconf2.69 autoconf autodia autogen automake-1.16 automake1.11 avahi
avifile avr-libc avrdude axiom backup-manager bacula ball ballz balsa
bamf barcode base-passwd bash bats bbe bc bcron beast-mcmc beast2-mcmc
belenios berusky2 berusky bgw-replstatus bibclean biber bibtex2html
bibtool bind9 binutils-arm-none-eabi binutils-avr binutils-bpf
binutils-djgpp binutils-h8300-hms binutils-m68hc1x binutils-mingw-w64
binutils-mipsen binutils-or1k-elf binutils-riscv64-unknown-elf
binutils-sh-elf binutils-xtensa-lx106 binutils-z80 binutils biobambam2
biometric-authentication bioperl-run bioperl biosig bird2 bird bison++
bkchem blackbox blends blis bliss blitz++ blktrace bochs boinc bongo
boolstuff boost1.74 boot bornagain boxbackup bppsuite brasero breathe
brial brian brickos buddy build-essential-mipsen build-essential
burgerspace buzztrax byobu bzflag bzip2 c++-annotations c-ares cadabra2
cairo caja-actions caja-eiciel caja-extensions caja-seahorse caja
cakephp cal3d calf calligra camlimages camlp5 canl-c canna cantor
capnproto car caribou cassbeam cattle-1.0 cbm cc-tool ccfits cclive
cconv cdck cddlib cdftools cdo celery cffi cfgrib cfi cfitsio cflow cgal
cgdb chafa chasen check-manifest check-postgres check chezscheme chicken
chktex choqok christianriesen-base32 christianriesen-otp chron
ciderwebmail cimg cjk cl-alexandria cl-asdf cl-clx-sbcl cl-esrap clamav
clanlib claws-mail cli-common clipper clisp cln clp clustalo cluster
clutter-1.0 clutter-gst-3.0 clutter-gtk clutter-imcontext clzip cmph
cnvkit coccinelle cockpit cod-tools code-saturne codeblocks codec2
codecrypt codetools cogl cohomcalg coinor-cgl coinor-csdp coinor-dylp
coinor-ipopt coinor-osi coinor-symphony coinor-vol coinutils collectd
colorhug-client colpack comedilib compiz-plugins-experimental
compiz-plugins-extra compiz-plugins-main compiz complexity composer
concordance conky connman-ui consfigurator coolkey coq-iris coreutils
courier-authlib courier-unicode courier cowdancer cpio cpl-plugin-fors
cpl-plugin-hawki cpl-plugin-vimos cpl cpluff cpptest cppunit cpputest
crac cracklib2 crash creduce critterding cross-toolchain-base-mipsen
cross-toolchain-base-ports csmith cssc ctemplate cups-bjnp cups-filters
cups-pk-helper cups curl curtain cutils cvc4 cvs cvxopt cwebx cwidget
cxref cxxtest cylc-flow cyrus-imapd cysignals d-itg dahdi-tools daps dar
dasher dasm dasprid-enum date dateutils db5.3 dbconfig-common dbi
dbus-c++ dbus-glib dbus dbuskit ddccontrol-db ddccontrol ddd
dde-calendar ddskk deap deb-gview debci debian-edu-doc debian-el
debian-faq debian-handbook debian-history
debian-installer-netboot-images debian-keyring debian-policy
debian-reference debmake-doc debomatic dee deepin-album
deepin-deb-installer dejagnu denemo derivations desmume

Bug#1019724: warning: stray \ before - causes autopkgtest failure

[Paul Gevers]

Hi Santiago,

On 15-09-2022 09:26, Paul Gevers wrote:
I am trying to schedule autopkgtests in unstable on amd64 for all source 
packages that have one.


All results are now in. Only several test failed due this warning: the 
known dpkg and cjet and the newly found nagios-plugins-contrib, logcheck 
and xautolock (see links below).


Lucas, are you in the position to do an archive rebuild to check for the 
grep warnings (see full history at [1]). When you submit bugs, can you 
please file them as important, as apparently upstream wants to turn 
these warnings into failures in the future, but in Debian Santiago is 
going to silence the warning soon, so FTBFS due to this isn't an RC 
problem on the short term.


Santiago, please keep the grep with warning in unstable until either all 
tests are finished or we abort this plan.


To be honest, without bug 1019326 in ucf and bug 1019725 in libtool 
fixed, I'm not sure how much value an archive rebuild would be at this 
stage.


So I think it would be good to silence the warning now in Debian. As 
discussed before, ideally with a way to turn it on (or make it error) 
such that we can do archive wide QA before the behavior is changed to 
error out upstream. I can understand it if you want to wait with 
deploying that optional behavior until upstream has implemented it.


Paul

https://ci.debian.net/data/autopkgtest/unstable/amd64/n/nagios-plugins-contrib/26117196/log.gz
/37.20211217/check_ssl_cert/check_ssl_cert_2.15.0/check_ssl_cert/ line 1125
https://ci.debian.net/data/autopkgtest/unstable/amd64/l/logcheck/26123766/log.gz
https://ci.debian.net/data/autopkgtest/unstable/amd64/x/xautolock/26130620/log.gz
--> 
https://sources.debian.org/src/xautolock/1%3A2.2-7/debian/tests/help/ line 5


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1019724: warning: stray \ before - causes autopkgtest failure

[Guillem Jover]

On Wed, 2022-09-14 at 17:31:16 +0200, Santiago Ruano Rincón wrote:
> Yeah, sorry. I lately realised not all the packages would autoreconf
> during building time.
> 
> So silencing these warnings would make sense.

Please consider implementing a way to be able to conditionally re-enable
locally these warnings so that we can try to hunt down and fix those,
otherwise we might end up hitting these once we revert the silencing,
for example for code paths that are not commonly exercised.

I've mentioned this on the upstream bug report, but it would be nicer
if you could coordinate a way upstream might be happy with, say using
a specific environment variable or similar.

Thanks,
Guillem

Bug#1019724: warning: stray \ before - causes autopkgtest failure

[Rene Engelhard]

Hi,

Am 15.09.22 um 15:50 schrieb Paul Gevers:

On 15-09-2022 09:26, Paul Gevers wrote:
I am trying to schedule autopkgtests in unstable on amd64 for all 
source packages that have one.


And the first results are coming in. I'm not sure how to proceed 
though, see below.


Lucas, are you in the position to do an archive rebuild to check for 
the grep warnings (see full history at [1]). When you submit bugs, 
can you please file them as important, as apparently upstream wants 
to turn these warnings into failures in the future, but in Debian 
Santiago is going to silence the warning soon, so FTBFS due to this 
isn't an RC problem on the short term.


I wonder if this is going to be useful. The first couple of hits I 
inspected, the warning didn't occur in the autopkgtest itself, but 
during installation of required packages.



Packages using ucf, yes.

See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019326



E.g.
https://ci.debian.net/data/autopkgtest/unstable/amd64/l/lintian-brush/26114550/log.gz 

shows the warning while running update-perl-sax-parsers during 
installation libxml-sax-perl


and
https://ci.debian.net/data/autopkgtest/unstable/amd64/g/golang-github-lib-pq/26114898/log.gz 


shows the warning while installing postgresql-common

A lot of tests use postgresql, so weeding that out isn't going to be 
trivial.


Any ideas? (I'll of course file bugs against postqresql-common and 
whatever contains update-perl-sax-parsers, but I'll need more 
automation for the rest) 


Doesn't make sense imho, as neither has a bug and it's actually ucf in 
many cases doing the grep in question.


Regards,


Rene

Bug#1019724: warning: stray \ before - causes autopkgtest failure

[Paul Gevers]

Hi all,

On 15-09-2022 09:26, Paul Gevers wrote:
I am trying to schedule autopkgtests in unstable on amd64 for all source 
packages that have one.


And the first results are coming in. I'm not sure how to proceed though, 
see below.


Lucas, are you in the position to do an archive rebuild to check for the 
grep warnings (see full history at [1]). When you submit bugs, can you 
please file them as important, as apparently upstream wants to turn 
these warnings into failures in the future, but in Debian Santiago is 
going to silence the warning soon, so FTBFS due to this isn't an RC 
problem on the short term.


I wonder if this is going to be useful. The first couple of hits I 
inspected, the warning didn't occur in the autopkgtest itself, but 
during installation of required packages.


E.g.
https://ci.debian.net/data/autopkgtest/unstable/amd64/l/lintian-brush/26114550/log.gz
shows the warning while running update-perl-sax-parsers during 
installation libxml-sax-perl


and
https://ci.debian.net/data/autopkgtest/unstable/amd64/g/golang-github-lib-pq/26114898/log.gz
shows the warning while installing postgresql-common

A lot of tests use postgresql, so weeding that out isn't going to be 
trivial.


Any ideas? (I'll of course file bugs against postqresql-common and 
whatever contains update-perl-sax-parsers, but I'll need more automation 
for the rest) Lucas, do you need to and if so how do you normally handle 
such cases for the rebuilds?


Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1019724: warning: stray \ before - causes autopkgtest failure

[Paul Gevers]

Hi Santiago, Lucas,

On 14-09-2022 17:31, Santiago Ruano Rincón wrote:

Note that the release team issued a block for now:

https://release.debian.org/britney/hints/jcristau

and proposed to test with a archive rebuild before introducing it again.



Dear Release Team, just to be sure of being on the same page: if you are
proposing to rebuild the whole archive, should I wait before silencing
the warnings, for being able to (mass-)bug filing?


I am trying to schedule autopkgtests in unstable on amd64 for all source 
packages that have one.


Lucas, are you in the position to do an archive rebuild to check for the 
grep warnings (see full history at [1]). When you submit bugs, can you 
please file them as important, as apparently upstream wants to turn 
these warnings into failures in the future, but in Debian Santiago is 
going to silence the warning soon, so FTBFS due to this isn't an RC 
problem on the short term.


Santiago, please keep the grep with warning in unstable until either all 
tests are finished or we abort this plan.


Paul

[1] https://bugs.debian.org/1019724


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1019724: warning: stray \ before - causes autopkgtest failure

[Santiago Ruano Rincón]

Hi Jochen,

El 14/09/22 a las 15:16, Jochen Sprickerhof escribió:
> Hi Santiago,
> 
> * Santiago Ruano Rincón  [2022-09-14 10:36]:
> > > this causes build failures:
> > > 
> > > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/arm64/libtool.html
> > > 
> > > and also autopkgtest failures:
> > > 
> > > https://ci.debian.net/data/autopkgtest/unstable/amd64/d/dpkg/26032114/log.gz
> > > https://ci.debian.net/data/autopkgtest/unstable/amd64/c/cjet/26041201/log.gz
> > > 
> > > The first autopkgtest failure is in libtool which is vendored by a lot
> > > of packages so will probably take a long time to fix.
> > > 
> > 
> > Fixing this would require fixing libtool only, isn't that right?
> 
> I don't think so, as it is in a lot of packages:
> 
> https://codesearch.debian.net/search?q=Configured+with%3A%22+%7C+%24GREP+%22+%5C-L
> 
> (Note that the buggy libtool.m4 is included into configure.)

Yeah, sorry. I lately realised not all the packages would autoreconf
during building time.

So silencing these warnings would make sense.

> 
> > > P.S.: I will send a bug with a patch to the libtool maintainer.
> > 
> > Please do.
> 
> Done as #1019725.
> 
> > P.S. I am letting Severity: serious for now to prevent migration to
> > testing. But *I* am considering this rather Severity: important, at
> > most.
> 
> Note that the release team issued a block for now:
> 
> https://release.debian.org/britney/hints/jcristau
> 
> and proposed to test with a archive rebuild before introducing it again.

ACK.

Dear Release Team, just to be sure of being on the same page: if you are
proposing to rebuild the whole archive, should I wait before silencing
the warnings, for being able to (mass-)bug filing?

Thanks,

 -- Santiago


signature.asc
Description: PGP signature

Bug#1019724: warning: stray \ before - causes autopkgtest failure

[Jochen Sprickerhof]

Hi Santiago,

* Santiago Ruano Rincón  [2022-09-14 10:36]:

this causes build failures:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/arm64/libtool.html

and also autopkgtest failures:

https://ci.debian.net/data/autopkgtest/unstable/amd64/d/dpkg/26032114/log.gz
https://ci.debian.net/data/autopkgtest/unstable/amd64/c/cjet/26041201/log.gz

The first autopkgtest failure is in libtool which is vendored by a lot
of packages so will probably take a long time to fix.



Fixing this would require fixing libtool only, isn't that right?


I don't think so, as it is in a lot of packages:

https://codesearch.debian.net/search?q=Configured+with%3A%22+%7C+%24GREP+%22+%5C-L

(Note that the buggy libtool.m4 is included into configure.)


P.S.: I will send a bug with a patch to the libtool maintainer.


Please do.


Done as #1019725.


P.S. I am letting Severity: serious for now to prevent migration to
testing. But *I* am considering this rather Severity: important, at
most.


Note that the release team issued a block for now:

https://release.debian.org/britney/hints/jcristau

and proposed to test with a archive rebuild before introducing it again.


signature.asc
Description: PGP signature

Bug#1019724: warning: stray \ before - causes autopkgtest failure

[Santiago Ruano Rincón]

Hi,

El 14/09/22 a las 09:04, Jochen Sprickerhof escribió:
> Package: grep
> Version: 3.8-2
> Severity: serious
> 
> Hi,
> 
> the new grep versions issues a warning on stderr:
> 
> stderr: /usr/bin/grep: warning: stray \ before -

FTR, this warning relates to:

  Regular expressions with stray backslashes now cause warnings, as
  their unspecified behavior can lead to unexpected results.
  For example, '\a' and 'a' are not always equivalent
  .  Similarly, regular expressions or
  subexpressions that start with a repetition operator now also cause
  warnings due to their unspecified behavior; for example, *a(+b|{1}c)
  now has three reasons to warn.  The warnings are intended as a
  transition aid; they are likely to be errors in future releases.

> 
> this causes build failures:
> 
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/arm64/libtool.html
> 
> and also autopkgtest failures:
> 
> https://ci.debian.net/data/autopkgtest/unstable/amd64/d/dpkg/26032114/log.gz
> https://ci.debian.net/data/autopkgtest/unstable/amd64/c/cjet/26041201/log.gz
> 
> The first autopkgtest failure is in libtool which is vendored by a lot
> of packages so will probably take a long time to fix.
> 

Fixing this would require fixing libtool only, isn't that right?

> Could you maybe silence the warning for now?
> 

Let's see how difficult is to fix this in libtool (and in any other
potentially affected package) first.

Let me also add some rationale from upstream, quoting it from
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=57604#47:

El 08/09/22 a las 02:21, Jim Meyering escribió:
> Hi Karl,
> 
> Sorry to cause you grief, but...
> 
> On Wed, Sep 7, 2022 at 7:49 PM Karl Berry  wrote:
[snip]
> > $ grep '\Q' /dev/null
> > grep: warning: stray \ before Q
> 
> > It would be nice to be able to turn those off too. (It hit me today.)
> 
> I would argue that it is (...) important to retain these
> stray-backslash warnings, because they tend to highlight real bugs.
> Consider these uses of \d:
> 
>   $ echo d | grep-3.7 '\d'
>   d
>   $ echo d | grep-3.8 '\d'
>   grep: warning: stray \ before d
> 
> Anyone used to PCRE regexps (who isn't, these days) knows that its
> "\d" is intended to match a digit, not the letter "d". With grep-3.7,
> you'd get misbehavior and no warning about your error. With grep-3.8,
> you'll get the diagnostic and maybe switch to using "grep -P", where
> "\d" works as expected -- switching from \d to [0-9] hurts readability
> and feels like dumbing-down, especially when there are two or more \d
> uses. Using PCRE's \Q...\E groups *without -P* is another issue that
> is now diagnosed.
>
...


> Should be this one:
> 
> https://sources.debian.org/src/grep/3.8-2/lib/dfa.c/#L1564
> 
> Cheers Jochen
> 
> P.S.: I will send a bug with a patch to the libtool maintainer.

Please do.

Cheers,

 -- Santiago

P.S. I am letting Severity: serious for now to prevent migration to
testing. But *I* am considering this rather Severity: important, at
most.


signature.asc
Description: PGP signature

Bug#1019724: warning: stray \ before - causes autopkgtest failure

[Jochen Sprickerhof]

Package: grep
Version: 3.8-2
Severity: serious

Hi,

the new grep versions issues a warning on stderr:

stderr: /usr/bin/grep: warning: stray \ before -

this causes build failures:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/arm64/libtool.html

and also autopkgtest failures:

https://ci.debian.net/data/autopkgtest/unstable/amd64/d/dpkg/26032114/log.gz
https://ci.debian.net/data/autopkgtest/unstable/amd64/c/cjet/26041201/log.gz

The first autopkgtest failure is in libtool which is vendored by a lot
of packages so will probably take a long time to fix.

Could you maybe silence the warning for now?

Should be this one:

https://sources.debian.org/src/grep/3.8-2/lib/dfa.c/#L1564

Cheers Jochen

P.S.: I will send a bug with a patch to the libtool maintainer.

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
merged-usr: no
Architecture: amd64 (x86_64)

Kernel: Linux 5.19.0-1-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages grep depends on:
ii  dpkg  1.21.9
ii  install-info  6.8-6
ii  libc6 2.34-8
ii  libpcre2-8-0  10.40-1

grep recommends no packages.

grep suggests no packages.

-- no debconf information