Bug#965605: marked as done (jigl: Removal of obsolete debhelper compat 5 and 6 in bookworm)

Your message dated Sun, 26 Dec 2021 06:29:35 +0100 with message-id <20211226052935.gn13...@beskar.mdcc.cx> and subject line Re: #965605: jigl: Removal of obsolete debhelper compat 5 and 6 in bookworm has caused the Debian Bug report #965605, regarding jigl: Removal of obsolete debhelper compat 5

Processed: block 999540 with 1002372

Processing commands for cont...@bugs.debian.org: > block 999540 with 1002372 Bug #999540 [src:qiskit-terra] qiskit-terra: FTBFS with matplotlib 3.5 (in experimental): dh_auto_test: error: pybuild --test -i python{version} -p 3.9 returned exit code 13 999540 was not blocked by any bugs. 999540

Processed: affects 1002372

Processing commands for cont...@bugs.debian.org: > affects 1002372 src:qiskit-terra Bug #1002372 [src:nbconvert] nbconvert: FTBFS: AttributeError: module 'mistune' has no attribute 'BlockGrammar' Added indication that 1002372 affects src:qiskit-terra > thanks Stopping processing here. Please

Processed: block 999519 with 1000435

Processing commands for cont...@bugs.debian.org: > block 999519 with 1000435 Bug #999519 {Done: Stefano Rivera } [src:xrayutilities] xrayutilities: FTBFS with matplotlib 3.5 (in experimental): dh_auto_test: error: pybuild --test -i python{version} -p 3.9 -s custom "--test-args={interpreter}

Bug#965492: marked as done (dlocate: Removal of obsolete debhelper compat 5 and 6 in bookworm)

Your message dated Sun, 26 Dec 2021 03:33:48 + with message-id and subject line Bug#965492: fixed in dlocate 1.08 has caused the Debian Bug report #965492, regarding dlocate: Removal of obsolete debhelper compat 5 and 6 in bookworm to be marked as done. This means that you claim that the

Bug#1001350: marked as done (sslsplit: FTBFS with openssl 3)

Your message dated Sun, 26 Dec 2021 02:25:58 + with message-id and subject line Bug#1001350: fixed in sslsplit 0.5.5-2 has caused the Debian Bug report #1001350, regarding sslsplit: FTBFS with openssl 3 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#965858: marked as done (userv: Removal of obsolete debhelper compat 5 and 6 in bookworm)

Your message dated Sun, 26 Dec 2021 01:50:32 + with message-id and subject line Bug#965858: fixed in userv 1.2.1~beta1 has caused the Debian Bug report #965858, regarding userv: Removal of obsolete debhelper compat 5 and 6 in bookworm to be marked as done. This means that you claim that the

Processed: limit source to userv, tagging 985998, tagging 965858

Processing commands for cont...@bugs.debian.org: > limit source userv Limiting to bugs with field 'source' containing at least one of 'userv' Limit currently set to 'source':'userv' > tags 985998 + pending Bug #985998 [src:userv] userv FTCBFS: successfully builds a broken package Added tag(s)

Processed: checksecurity: diff for NMU version 2.0.16+nmu3

Processing control commands: > tags 965448 + patch Bug #965448 [src:checksecurity] checksecurity: Removal of obsolete debhelper compat 5 and 6 in bookworm Added tag(s) patch. > tags 965448 + pending Bug #965448 [src:checksecurity] checksecurity: Removal of obsolete debhelper compat 5 and 6 in

Processed: checksecurity: diff for NMU version 2.0.16+nmu3

Processing control commands: > tags 965448 + patch Bug #965448 [src:checksecurity] checksecurity: Removal of obsolete debhelper compat 5 and 6 in bookworm Ignoring request to alter tags of bug #965448 to the same tags previously set > tags 965448 + pending Bug #965448 [src:checksecurity]

Bug#965448: checksecurity: diff for NMU version 2.0.16+nmu3

Control: tags 965448 + patch Control: tags 965448 + pending Control: tags 999082 + patch Control: tags 999082 + pending Dear maintainer, I've prepared an NMU for checksecurity (versioned as 2.0.16+nmu3) and uploaded it to DELAYED/7. Please feel free to tell me if I should delay it longer.

Bug#999307: jargon: diff for NMU version 4.0.0-5.3

Control: tags 777483 + pending Control: tags 999307 + patch Control: tags 999307 + pending Dear maintainer, I've prepared an NMU for jargon (versioned as 4.0.0-5.3) and uploaded it to DELAYED/7. Please feel free to tell me if I should delay it longer. Regards. -- .''`.

Processed: jargon: diff for NMU version 4.0.0-5.3

Processing control commands: > tags 777483 + pending Bug #777483 [src:jargon] jargon: please make the build reproducible Ignoring request to alter tags of bug #777483 to the same tags previously set > tags 999307 + patch Bug #999307 [src:jargon] jargon: missing required debian/rules targets

Bug#994521: Acknowledgement (ledmon: libsgutils2-2 1.46 update breaks ledmon)

It has now been 3 months since this package has been broken in testing. Is it safe to assume this package is abandoned? On Fri, Sep 17, 2021 at 12:48 AM Debian Bug Tracking System < ow...@bugs.debian.org> wrote: > Thank you for filing a new Bug report with Debian. > > You can follow progress on

Processed: jargon: diff for NMU version 4.0.0-5.3

Processing control commands: > tags 777483 + pending Bug #777483 [src:jargon] jargon: please make the build reproducible Added tag(s) pending. > tags 999307 + patch Bug #999307 [src:jargon] jargon: missing required debian/rules targets build-arch and/or build-indep Added tag(s) patch. > tags

Bug#999224: nrg2iso: diff for NMU version 0.4-4.1

Control: tags 901451 + pending Control: tags 999224 + patch Control: tags 999224 + pending Dear maintainer, I've prepared an NMU for nrg2iso (versioned as 0.4-4.1) and uploaded it to DELAYED/7. Please feel free to tell me if I should delay it longer. Regards. -- .''`.

Processed: nrg2iso: diff for NMU version 0.4-4.1

Processing control commands: > tags 901451 + pending Bug #901451 [src:nrg2iso] nrg2iso FTCBFS: upstream Makefile hard codes the build architecture compiler gcc Added tag(s) pending. > tags 999224 + patch Bug #999224 [src:nrg2iso] nrg2iso: missing required debian/rules targets build-arch and/or

Processed: nrg2iso: diff for NMU version 0.4-4.1

Processing control commands: > tags 901451 + pending Bug #901451 [src:nrg2iso] nrg2iso FTCBFS: upstream Makefile hard codes the build architecture compiler gcc Ignoring request to alter tags of bug #901451 to the same tags previously set > tags 999224 + patch Bug #999224 [src:nrg2iso] nrg2iso:

Processed: pcaputils: diff for NMU version 0.8-1.1

Processing control commands: > tags 901211 + pending Bug #901211 [src:pcaputils] pcaputils FTCBFS: does not pass cross tools to make Ignoring request to alter tags of bug #901211 to the same tags previously set > tags 965769 + patch Bug #965769 [src:pcaputils] pcaputils: Removal of obsolete

Bug#965769: pcaputils: diff for NMU version 0.8-1.1

Control: tags 901211 + pending Control: tags 965769 + patch Control: tags 965769 + pending Control: tags 999325 + patch Control: tags 999325 + pending Dear maintainer, I've prepared an NMU for pcaputils (versioned as 0.8-1.1) and uploaded it to DELAYED/7. Please feel free to tell me if I should

Processed: pcaputils: diff for NMU version 0.8-1.1

Processing control commands: > tags 901211 + pending Bug #901211 [src:pcaputils] pcaputils FTCBFS: does not pass cross tools to make Ignoring request to alter tags of bug #901211 to the same tags previously set > tags 965769 + patch Bug #965769 [src:pcaputils] pcaputils: Removal of obsolete

Processed: pcaputils: diff for NMU version 0.8-1.1

Processing control commands: > tags 901211 + pending Bug #901211 [src:pcaputils] pcaputils FTCBFS: does not pass cross tools to make Added tag(s) pending. > tags 965769 + patch Bug #965769 [src:pcaputils] pcaputils: Removal of obsolete debhelper compat 5 and 6 in bookworm Added tag(s) patch. >

Bug#1001591: python3-mistune: latest upgrade breaks matrix-mirage package

Maybe mistune 2.x should have its own package? Or keep python3-mistune at 2.x and introduce a python3-mistune1 package? I'm upstream for schema-salad, we don't know how to upgrade to 2.x because so much has been broken and there is no upgrading guide.

Bug#1002326: python-schema-salad: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit code 13

On Wed, 22 Dec 2021 08:57:03 +0100 Lucas Nussbaum wrote: > Source: python-schema-salad > Version: 8.2.20211104054942-1 > Severity: serious > Justification: FTBFS > Tags: bookworm sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20211220 ftbfs-bookworm > > Hi, > > During a rebuild of all

Bug#1002274: marked as pending in jetty9

Control: tag -1 pending Hello, Bug #1002274 in jetty9 reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Processed: Bug#1002274 marked as pending in jetty9

Processing control commands: > tag -1 pending Bug #1002274 [src:jetty9] jetty9: FTBFS: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:3.1.1:copy (copy-servlet-api-deps) on project jetty-home: Unable to find/resolve artifact. Cannot access central

Processed: Re: Bug#997273: virt-v2v: FTBFS: (.text+0x12a): undefined reference to `rpl_free'

Processing control commands: > reassign -1 libguestfs Bug #997273 [src:virt-v2v] virt-v2v: FTBFS: (.text+0x12a): undefined reference to `rpl_free' Bug reassigned from package 'src:virt-v2v' to 'libguestfs'. No longer marked as found in versions virt-v2v/1.44.0-1. Ignoring request to alter fixed

Bug#997273: virt-v2v: FTBFS: (.text+0x12a): undefined reference to `rpl_free'

control: reassign -1 libguestfs control: fixed -1 libguestfs/1:1.46.2-1 The root cause seems to lie in the libguestfs-ocaml library and it can no longer be reproduced with 1:1.46.2-1 which I have just uploaded. Cheers, -Hilko

Bug#1002625: wlr-randr autopkgtest failure with phoc 0.11

Package: wlr-randr Version: 0.2.0-1 Severity: serious The wlr-randr autopkgtest is failing with the new version of phoc https://ci.debian.net/data/autopkgtest/testing/amd64/w/wlr-randr/17846958/log.gz autopkgtest [22:48:44]: test command1: WLR_BACKENDS=headless WLR_LIBINPUT_NO_DEVICES=1 phoc

Processed: severity of 1002497 is normal

Processing commands for cont...@bugs.debian.org: > severity 1002497 normal Bug #1002497 [postfix] postfix: FTBFS Arch-All as rm on a write-protected file is interactive Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. --

Bug#1002525: r-cran-tmb: autopkgtest needs update for new version of rmatrix: Package version inconsistency detected.

Hi Nilesh, On 26 December 2021 at 00:20, Nilesh Patra wrote: | control: reassign -1 r-cran-tmb/1.7.22-1 | | Hi Dirk, | | On Thu, 23 Dec 2021 14:30:10 -0600 Dirk Eddelbuettel wrote: | > passfail | > | rmatrixfrom testing1.4-0-1 | > |

Bug#1002497: FTBFS Arch-All with interactive rm

On Saturday, December 25, 2021 3:43:24 PM EST Vincent Lefevre wrote: > Control: severity -1 serious > Control: tags -1 ftbfs > Control: retitle -1 postfix: FTBFS Arch-All as rm on a write-protected file > is interactive > On 2021-12-23 11:12:40 +0100, Daniel Baumann wrote: > > there seems to be

Bug#1002497: FTBFS Arch-All with interactive rm

On 2021-12-23 08:35:44 -0500, Scott Kitterman wrote: > Thanks. Fix staged in git for the next upload. It seems slightly odd to me > that this comes up now as it's been that way since at least 2012. Not really. Compared to postfix 3.6.3-1, "Rules-Requires-Root: no" has been added to

Bug#1002622: marked as done (schleuder: ActiveRecord >= 6.0 changes boolean serialization, makes existing mailing lists fail)

Your message dated Sat, 25 Dec 2021 20:49:07 + with message-id and subject line Bug#1002622: fixed in schleuder 3.6.0-4 has caused the Debian Bug report #1002622, regarding schleuder: ActiveRecord >= 6.0 changes boolean serialization, makes existing mailing lists fail to be marked as done.

Processed: Re: Bug#1002497: FTBFS Arch-All with interactive rm

Processing control commands: > severity -1 serious Bug #1002497 [postfix] FTBFS Arch-All with interactive rm Severity set to 'serious' from 'normal' > tags -1 ftbfs Bug #1002497 [postfix] FTBFS Arch-All with interactive rm Added tag(s) ftbfs. > retitle -1 postfix: FTBFS Arch-All as rm on a

Bug#996052: marked as done (gnome-shell-extension-disconnect-wifi: does not declare compatibility with GNOME Shell 41)

Your message dated Sat, 25 Dec 2021 22:06:35 +0200 with message-id <20211225200635.GA13543@localhost> and subject line Re: Bug#996052: gnome-shell-extension-disconnect-wifi: does not declare compatibility with GNOME Shell 41 has caused the Debian Bug report #996052, regarding

Bug#997513: closing 997513

close 997513 1:2.3.17.1+dfsg1-1 thanks This has been been resolved with 1:2.3.17.1+dfsg1-1 via commit e3d0747bb2ef86b3d146e2a8fcadce18d587db52

Processed: closing 997513

Processing commands for cont...@bugs.debian.org: > close 997513 1:2.3.17.1+dfsg1-1 Bug #997513 [src:dovecot] dovecot: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2 Marked as fixed in versions dovecot/1:2.3.17.1+dfsg1-1. Bug #997513 [src:dovecot] dovecot: FTBFS:

Bug#1002622: schleuder: ActiveRecord >= 6.0 changes boolean serialization, makes existing mailing lists fail

Package: schleuder Version: 3.6.0-3 Severity: grave Justification: renders package unusable Forwarded: https://0xacab.org/schleuder/schleuder/-/issues/505 Tags: fixed-upstream Since ActiveRecord >= 6.0, the SQLite3 connection adapter relies on boolean serialization to use 1 and 0, but does not

Bug#1002525: marked as done (r-cran-tmb: autopkgtest needs update for new version of rmatrix: Package version inconsistency detected.)

Your message dated Sat, 25 Dec 2021 19:07:08 + with message-id and subject line Bug#1002525: fixed in r-cran-tmb 1.7.22-2 has caused the Debian Bug report #1002525, regarding r-cran-tmb: autopkgtest needs update for new version of rmatrix: Package version inconsistency detected. to be marked

Processed: reassign

Processing commands for cont...@bugs.debian.org: > reassign 1002525 r-cran-tmb Bug #1002525 [src:r-cran-tmb] r-cran-tmb: autopkgtest needs update for new version of rmatrix: Package version inconsistency detected. Bug reassigned from package 'src:r-cran-tmb' to 'r-cran-tmb'. No longer marked as

Bug#1002525: r-cran-tmb: autopkgtest needs update for new version of rmatrix: Package version inconsistency detected.

control: reassign -1 r-cran-tmb/1.7.22-1 Hi Dirk, On Thu, 23 Dec 2021 14:30:10 -0600 Dirk Eddelbuettel wrote: > passfail > | rmatrixfrom testing1.4-0-1 > | r-cran-tmb from testing1.7.22-1 > | all others from

Bug#998929: marked as done (stfl: missing required debian/rules targets build-arch and/or build-indep)

Your message dated Sat, 25 Dec 2021 18:38:16 + with message-id and subject line Bug#998929: fixed in stfl 0.22-3 has caused the Debian Bug report #998929, regarding stfl: missing required debian/rules targets build-arch and/or build-indep to be marked as done. This means that you claim that

Bug#965873: marked as done (vtwm: Removal of obsolete debhelper compat 5 and 6 in bookworm)

Your message dated Sat, 25 Dec 2021 18:04:28 + with message-id and subject line Bug#965873: fixed in vtwm 5.4.7-7 has caused the Debian Bug report #965873, regarding vtwm: Removal of obsolete debhelper compat 5 and 6 in bookworm to be marked as done. This means that you claim that the

Processed: xbindkeys-config: diff for NMU version 0.1.3-2.3

Processing control commands: > tags 965882 + patch Bug #965882 [src:xbindkeys-config] xbindkeys-config: Removal of obsolete debhelper compat 5 and 6 in bookworm Ignoring request to alter tags of bug #965882 to the same tags previously set > tags 965882 + pending Bug #965882

Processed: xbindkeys-config: diff for NMU version 0.1.3-2.3

Processing control commands: > tags 965882 + patch Bug #965882 [src:xbindkeys-config] xbindkeys-config: Removal of obsolete debhelper compat 5 and 6 in bookworm Added tag(s) patch. > tags 965882 + pending Bug #965882 [src:xbindkeys-config] xbindkeys-config: Removal of obsolete debhelper compat

Bug#965882: xbindkeys-config: diff for NMU version 0.1.3-2.3

Control: tags 965882 + patch Control: tags 965882 + pending Control: tags 999054 + patch Control: tags 999054 + pending Dear maintainer, I've prepared an NMU for xbindkeys-config (versioned as 0.1.3-2.3) and uploaded it to DELAYED/7. Please feel free to tell me if I should delay it longer.

Processed: libcompface: diff for NMU version 1:1.5.2-5.1

Processing control commands: > tags 861345 + pending Bug #861345 [src:libcompface] libcompface FTCBFS: uses the build architecture compiler Ignoring request to alter tags of bug #861345 to the same tags previously set > tags 965632 + patch Bug #965632 [src:libcompface] libcompface: Removal of

Processed: libcompface: diff for NMU version 1:1.5.2-5.1

Processing control commands: > tags 861345 + pending Bug #861345 [src:libcompface] libcompface FTCBFS: uses the build architecture compiler Ignoring request to alter tags of bug #861345 to the same tags previously set > tags 965632 + patch Bug #965632 [src:libcompface] libcompface: Removal of

Bug#965632: libcompface: diff for NMU version 1:1.5.2-5.1

Control: tags 861345 + pending Control: tags 965632 + patch Control: tags 965632 + pending Control: tags 999263 + patch Control: tags 999263 + pending Dear maintainer, I've prepared an NMU for libcompface (versioned as 1:1.5.2-5.1) and uploaded it to DELAYED/7. Please feel free to tell me if I

Processed: libcompface: diff for NMU version 1:1.5.2-5.1

Processing control commands: > tags 861345 + pending Bug #861345 [src:libcompface] libcompface FTCBFS: uses the build architecture compiler Added tag(s) pending. > tags 965632 + patch Bug #965632 [src:libcompface] libcompface: Removal of obsolete debhelper compat 5 and 6 in bookworm Added

Bug#1002200: marked as done (wfuzz: FTBFS: AttributeError: 'NoneType' object has no attribute 'split')

Your message dated Sat, 25 Dec 2021 17:03:42 + with message-id and subject line Bug#1002182: fixed in dh-python 5.20211225 has caused the Debian Bug report #1002182, regarding wfuzz: FTBFS: AttributeError: 'NoneType' object has no attribute 'split' to be marked as done. This means that you

Bug#1002290: marked as done (dh_python3 needing contextvars -- not a problem with my package, then?)

Your message dated Sat, 25 Dec 2021 17:03:42 + with message-id and subject line Bug#1002182: fixed in dh-python 5.20211225 has caused the Debian Bug report #1002182, regarding dh_python3 needing contextvars -- not a problem with my package, then? to be marked as done. This means that you

Bug#1002182: marked as done (qutebrowser: FTBFS: AttributeError: 'NoneType' object has no attribute 'split')

Your message dated Sat, 25 Dec 2021 17:03:42 + with message-id and subject line Bug#1002182: fixed in dh-python 5.20211225 has caused the Debian Bug report #1002182, regarding qutebrowser: FTBFS: AttributeError: 'NoneType' object has no attribute 'split' to be marked as done. This means

Bug#1002207: marked as done (pantalaimon: FTBFS: AttributeError: 'NoneType' object has no attribute 'split')

Your message dated Sat, 25 Dec 2021 17:03:42 + with message-id and subject line Bug#1002182: fixed in dh-python 5.20211225 has caused the Debian Bug report #1002182, regarding pantalaimon: FTBFS: AttributeError: 'NoneType' object has no attribute 'split' to be marked as done. This means

Processed: Handling various gkrell* issues

Processing commands for cont...@bugs.debian.org: > # gkrellmwireless > tags 437038 pending Bug #437038 [gkrellmwireless] gkrellmwireless: not handling nostrip build option (policy 10.1) Added tag(s) pending. > tags 914827 pending Bug #914827 [src:gkrellmwireless] gkrellmwireless FTCBFS: many

Bug#994992: libpam-ssh: pam-ssh picks the from agent socket after login with ssh -A

Hello Stephan, thanks for your report. I guess that your issue is related to issue #995452 . I haved just merged them. Attached patch fixes the problem by omiting `session optional pam_ssh.so` from /etc/pam.d/sshd. Thanks for the patch. However note that it is not applicable because

Processed: libpam-ssh: pam-ssh picks the from agent socket after login with ssh -A

Processing commands for cont...@bugs.debian.org: > tags 994992 - patch Bug #994992 [libpam-ssh] libpam-ssh: pam-ssh picks the from agent socket after login with ssh -A Bug #995452 [libpam-ssh] libpam-ssh breaks the agent-forwarding of normal ssh Removed tag(s) patch. Removed tag(s) patch. >

Processed: tagging 876126, tagging 965845

Processing commands for cont...@bugs.debian.org: > tags 876126 + pending Bug #876126 [src:toilet] toilet FTCBFS: sets PKG_CONFIG_LIBDIR=/dev/null Added tag(s) pending. > tags 965845 + pending Bug #965845 [src:toilet] toilet: Removal of obsolete debhelper compat 5 and 6 in bookworm Added tag(s)

Processed: libpam-ssh: pam-ssh picks the from agent socket after login with ssh -A

Processing commands for cont...@bugs.debian.org: > severity 994992 critical Bug #994992 [libpam-ssh] libpam-ssh: pam-ssh picks the from agent socket after login with ssh -A Severity set to 'critical' from 'normal' > merge 994992 995452 Bug #994992 [libpam-ssh] libpam-ssh: pam-ssh picks the from

Bug#1001721: marked as done (pypy3: autopkgtest needs update for new version of setuptools: deprecation warning on stderr)

Your message dated Sat, 25 Dec 2021 16:19:45 + with message-id and subject line Bug#1001721: fixed in pypy3 7.3.7+dfsg-2 has caused the Debian Bug report #1001721, regarding pypy3: autopkgtest needs update for new version of setuptools: deprecation warning on stderr to be marked as done.

Processed (with 1 error): libpam-ssh: pam-ssh picks the from agent socket after login with ssh -A

Processing commands for cont...@bugs.debian.org: > merge 994992 995452 Bug #994992 [libpam-ssh] libpam-ssh: pam-ssh picks the from agent socket after login with ssh -A Unable to merge bugs because: severity of #995452 is 'critical' not 'normal' Failed to merge 994992: Did not alter merged bugs.

Bug#977340: marked as done (spip: Not compatible with php8.0)

Your message dated Sat, 25 Dec 2021 13:26:58 + with message-id and subject line Bug#977340: fixed in spip 4.0.1-1 has caused the Debian Bug report #977340, regarding spip: Not compatible with php8.0 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#998827: openorienteering-mapper: diff for NMU version 0.9.5-2.1

With regard to the changelog, I would like to point out that the test failure is probably not related to missing test data (or GDAL), but to a behavioral change in PROJ 8.2.0. References: https://github.com/OpenOrienteering/mapper/issues/2008

Bug#998827: openorienteering-mapper: diff for NMU version 0.9.5-2.1

Control: tags 998827 + patch Control: tags 998827 + pending Dear maintainer, I've prepared an NMU for openorienteering-mapper (versioned as 0.9.5-2.1) and uploaded it to DELAYED/14. Please feel free to tell me if I should cancel it. cu Adrian diff -Nru

Processed: openorienteering-mapper: diff for NMU version 0.9.5-2.1

Processing control commands: > tags 998827 + patch Bug #998827 [src:openorienteering-mapper] openorienteering-mapper: FTBFS with GDAL 3.4.0 Added tag(s) patch. > tags 998827 + pending Bug #998827 [src:openorienteering-mapper] openorienteering-mapper: FTBFS with GDAL 3.4.0 Added tag(s) pending.