Bug#984520: Goeie dag

Ek het hierdie sakegeleentheid -voorstel vir u wat ons sal baat; Ek sal ook daarvan hou dat jy dit sien. Groete, Frank William 64 980 4011

Processed: Re: Bug#993821: After upgrading libc, some services are unable to restart (including systemd-resolved)

Processing control commands: > reassign -1 libc6 Bug #993821 [systemd] After upgrading libc, some services are unable to restart (including systemd-resolved) Bug reassigned from package 'systemd' to 'libc6'. No longer marked as found in versions systemd/247.9-1. Ignoring request to alter fixed ve

Bug#993837: shotcut FTBFS with mlt 7

Source: shotcut Version: 21.01.29+ds-1 Severity: serious Tags: ftbfs bookworm sid https://buildd.debian.org/status/package.php?p=shotcut&suite=sid ... cd src/ && ( test -e Makefile || /usr/lib/qt5/bin/qmake -o Makefile /<>/src/src.pro 'QMAKE_CFLAGS_RELEASE=-g -O2 -ffile-prefix-map=/<>=. -fstack

Processed: kdenlive FTBFS with mlt 7

Processing control commands: > close -1 21.08.0-1 Bug #993836 [src:kdenlive] kdenlive FTBFS with mlt 7 Marked as fixed in versions kdenlive/21.08.0-1. Bug #993836 [src:kdenlive] kdenlive FTBFS with mlt 7 Marked Bug as done -- 993836: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993836 Debia

Bug#993836: kdenlive FTBFS with mlt 7

Source: kdenlive Version: 21.04.3-3 Severity: serious Tags: ftbfs Control: close -1 21.08.0-1 https://buildd.debian.org/status/package.php?p=kdenlive&suite=sid ... -- Checking for module 'mlt++' -- No package 'mlt++' found CMake Error at /usr/share/cmake-3.18/Modules/FindPackageHandleStandardA

Bug#993835: rnp FTBFS: rnp_tests.test_key_add_userid (Failed)

Source: rnp Version: 0.14.0-6 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=rnp&suite=sid ... test 135 Start 135: rnp_tests.test_key_add_userid 135: Test command: /<>/build/src/tests/rnp_tests "--gtest_filter=rnp_tests.test_key_add_userid" "--gtest_also_ru

Bug#993834: xgks FTBFS: dh_missing: error: missing files, aborting

Source: xgks Version: 2.6.1+dfsg.2-11 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=xgks&suite=sid ... dh_missing -a -O--sourcedirectory=src -O--no-parallel dh_missing: warning: usr/bin/gksdemo exists in debian/tmp but is not installed to anywhere dh_missing: w

Bug#993833: libguestfs FTBFS with Go 1.16

Source: libguestfs Version: 1:1.44.1-2 Severity: serious Tags: ftbfs bookworm sid https://buildd.debian.org/status/package.php?p=libguestfs&suite=sid ... Making all in golang make[4]: Entering directory '/<>/debian/build-1/golang' [ ../../../golang != . ] && ln -s /<>/debian/build-1/../../golang

Bug#993832: synfig FTBFS with mlt 7

Source: synfig Version: 1.4.0+dfsg-2 Severity: serious Tags: ftbfs bookworm sid https://buildd.debian.org/status/package.php?p=synfig&suite=sid ... checking for mlt++... configure: error: ** You need to install mlt++.

Bug#993820: marked as done (gnome-music: Gnome Music doesn't start.)

Your message dated Tue, 07 Sep 2021 01:19:16 + with message-id and subject line Bug#993820: fixed in gnome-music 40.1.1-4 has caused the Debian Bug report #993820, regarding gnome-music: Gnome Music doesn't start. to be marked as done. This means that you claim that the problem has been dealt

Bug#993820: marked as pending in gnome-music

Control: tag -1 pending Hello, Bug #993820 in gnome-music 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: https://salsa.debian.org/gnome-team/gnome-music/-/commit/06039f02700b2be082fa97

Processed: Bug#993820 marked as pending in gnome-music

Processing control commands: > tag -1 pending Bug #993820 [gnome-music] gnome-music: Gnome Music doesn't start. Added tag(s) pending. -- 993820: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993820 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#933751: mini-buildd (build-)depends on cruft package.

Stephan, On Fri, 28 Feb 2020 00:57:29 -0500 Scott Kitterman wrote: > > I am pressing for a release asap (~months), then everything will be > > fine again ;). > > The months are up to six now. How's it going? please do accelerate the release of mini-buildd from experimental to unstable: the fact

Bug#993491: marked as done (grilo-plugins: Please switch to tracker 3)

Your message dated Mon, 06 Sep 2021 22:33:48 + with message-id and subject line Bug#993491: fixed in grilo-plugins 0.3.13-3 has caused the Debian Bug report #993491, regarding grilo-plugins: Please switch to tracker 3 to be marked as done. This means that you claim that the problem has been d

Processed: SoapySDR transition is in progress

Processing commands for cont...@bugs.debian.org: > severity 993698 serious Bug #993698 [src:hacktv] hacktv: FTBFS with libsoapysdr 0.8 Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 993698: https://bugs.debian.org/cgi-bi

Processed: SoapySDR transition is in progress

Processing commands for cont...@bugs.debian.org: > severity 993699 serious Bug #993699 [src:libxtrx] libxtrx: FTBFS with libsoapysdr 0.8 Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 993699: https://bugs.debian.org/cgi-

Processed: SoapySDR transition is in progress

Processing commands for cont...@bugs.debian.org: > severity 993701 serious Bug #993701 [src:srslte] srslte: FTBFS with libsoapysdr 0.8 Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 993701: https://bugs.debian.org/cgi-bi

Bug#993820: gnome-music: Gnome Music doesn't start.

Package: gnome-music Version: 40.1.1-3 Severity: grave Justification: renders package unusable X-Debbugs-Cc: sebastianlacue...@gmail.com Package just doesn't start. Here's a console dump: $ gnome-music (org.gnome.Music:423406): Grilo-WARNING **: 18:36:18.430: [registry] ../src/grl-registry.c:151

Bug#993818: ruby-nokogiri: WARNING: Nokogiri was built against libxml version 2.9.12, but has dynamically loaded 2.9.10

Package: ruby-nokogiri Version: 1.11.7+dfsg-2 Severity: serious Justification: migration to testing blocked autopkgtest for cewl is failing in testing https://ci.debian.net/data/autopkgtest/testing/amd64/c/cewl/15073435/log.gz terceiro on irc: this type of warning is a PITA; I usually patch the

Bug#993817: ruby-licensee: autopkgtest regression on 9386

Package: ruby-licensee Version: 9.14.1-3 Severity: serious Control: forwarded -1 https://github.com/licensee/licensee/issues/503 Autopkgtest regression on i386 is blocking the migration to testing https://ci.debian.net/data/autopkgtest/testing/i386/r/ruby-licensee/15051694/log.gz Reported upstr

Processed: ruby-licensee: autopkgtest regression on 9386

Processing control commands: > forwarded -1 https://github.com/licensee/licensee/issues/503 Bug #993817 [ruby-licensee] ruby-licensee: autopkgtest regression on 9386 Set Bug forwarded-to-address to 'https://github.com/licensee/licensee/issues/503'. -- 993817: https://bugs.debian.org/cgi-bin/bug

Processed: fixed 977109 in 9.14.1-1

Processing commands for cont...@bugs.debian.org: > fixed 977109 9.14.1-1 Bug #977109 {Done: Cédric Boutillier } [ruby-licensee] ruby-licensee, autopkgtest failure with ruby-rugged 1.1.0 Marked as fixed in versions ruby-licensee/9.14.1-1. > thanks Stopping processing here. Please contact me if yo

Processed: Re: Astroquery doesn't work with Astropy 4.3.1

Processing control commands: > tags -1 patch Bug #993252 [python3-astroquery] Astroquery doesn't work with Astropy 4.3.1 Added tag(s) patch. -- 993252: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993252 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#993252: Astroquery doesn't work with Astropy 4.3.1

Control: tags -1 patch Hi Nilesh, Vincent, from astropy's CHANGES.rst, version 4.3: * astropy.utils.data.get_pkg_data_path is publicly scoped (previously the private function _find_pkg_data_path) for obtaining file paths without checking if the file/directory exists, as long as the package

Bug#993804: nfs-utils needs to take over libnfsidmap-regex

Source: nfs-utils Version: 1:2.5.4-1~exp1 Severity: serious Justification: needs to be fixed before landing in stable release X-Debbugs-Cc: car...@debian.org,gur...@phys.ethz.ch,manuel.maestin...@inf.ethz.ch Since 2-4-4-rc3+ upsream libnfsidmap-regex is maintained within nfs-utils source so we ne

Processed: Re: Bug#993316: systemd: missing /lib/systemd/system/rpcbind.service file

Processing control commands: > affects -1 rpcbind Bug #993316 [debhelper] rpcbind: missing /lib/systemd/system/rpcbind.service file Added indication that 993316 affects rpcbind -- 993316: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993316 Debian Bug Tracking System Contact ow...@bugs.debi

Bug#993316: systemd: missing /lib/systemd/system/rpcbind.service file

Control: affects -1 rpcbind On 2021-09-06 19:06:13 +0200, Niels Thykier wrote: > Control: reassign -1 debhelper > Control: affects -1 systemd This bug actually affects rpcbind. -- Vincent Lefèvre - Web: 100% accessible validated (X)HTML - Blog:

Processed: Re: Bug#993316: systemd: missing /lib/systemd/system/rpcbind.service file

Processing control commands: > reassign -1 debhelper Bug #993316 [rpcbind] rpcbind: missing /lib/systemd/system/rpcbind.service file Bug reassigned from package 'rpcbind' to 'debhelper'. No longer marked as found in versions rpcbind/1.2.6-2. Ignoring request to alter fixed versions of bug #993316

Bug#993316: systemd: missing /lib/systemd/system/rpcbind.service file

Control: reassign -1 debhelper Control: affects -1 systemd Michael Biebl: > Am 30.08.21 um 18:31 schrieb Vincent Lefevre: >> Package: systemd >> Version: 247.9-1 >> Severity: critical >> Justification: breaks unrelated software >> >> systemd provides a dangling symlink: >> >> $ ls -l /lib/systemd/

Bug#993716: bridge-utils: IPv6 network bridge fails after upgrading Buster to Bullseye

Hi all, I tried the fixes proposed here. Unfortunately, adding bridge_ports or bridge_hw did not solve the issue. The workaround of changing exit 1 to exit 0 in the /lib/ifupdown/settle-dad.sh "DAD timed out: section did cause networking to start up successfully, although it still logs the tim

Bug#993716: bridge-utils: IPv6 network bridge fails after upgrading Buster to Bullseye

PS: Additionally, I forgot to mention that adding dad-attempts 0 to the br0 inet6 config also solves the issues of networking failing. On 06/09/2021 14:17, Pieter Hollander wrote: Hi all, I tried the fixes proposed here. Unfortunately, adding bridge_ports or bridge_hw did not solve the issue.

Bug#992416: automake-1.16: autopkgtest failure: t/python-prefix.sh

Control: tags -1 + patch On Wed, 18 Aug 2021 at 12:29:19 +0200, Gianfranco Costamagna wrote: > Hello, looks some autopkgtest is failing with new version > https://ci.debian.net/data/autopkgtest/testing/amd64/a/automake-1.16/14607120/log.gz > > FAIL: t/python-prefix.sh >From the test-suite.log th

Processed: Re: Bug#992416: automake-1.16: autopkgtest failure: t/python-prefix.sh

Processing control commands: > tags -1 + patch Bug #992416 [src:automake-1.16] automake-1.16: autopkgtest failure: t/python-prefix.sh Added tag(s) patch. -- 992416: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992416 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#993789: Fails to install (idmapd.conf.5.gz also in libnfsidmap2)

Package: nfs-utils Severity: serious Version: 1:2.5.4-1~exp1 Tags: experimental Hi Anibal, after building the package, it fails to install: ---snip--- unpacking nfs-common (1:2.5.4-1~exp1) over (1:1.3.4-6) ... dpkg: error processing archive /var/cache/apt/archives/nfs-common_1%3a2.5.4-1~exp1_a

Bug#993252: Astroquery doesn't work with Astropy 4.3.1

On Mon, 6 Sept 2021 at 01:09, wrote: > Hi, > > I recently tried to update astroquery. > Indeed, version 0.4.3 solves the issue, but it introduces another bug > that prevents uploading. > I reported it upstream. > Patching the current version would probably be more efficient than > waiting for ups

Processed: bts

Processing commands for cont...@bugs.debian.org: > tag 993785 + patch Bug #993785 [nfs-utils] FTBFS on most architectures Added tag(s) patch. > tag 993785 + experimental Bug #993785 [nfs-utils] FTBFS on most architectures Added tag(s) experimental. > thanks Stopping processing here. Please contac

Processed: tagging 993785

Processing commands for cont...@bugs.debian.org: > tags 993785 + confirmed Bug #993785 [nfs-utils] FTBFS on most architectures Added tag(s) confirmed. > thanks Stopping processing here. Please contact me if you need assistance. -- 993785: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993785

Bug#993765: marked as done (mlt: binary-all FTBFS)

Your message dated Mon, 06 Sep 2021 13:49:01 + with message-id and subject line Bug#993765: fixed in mlt 7.0.1-3 has caused the Debian Bug report #993765, regarding mlt: binary-all FTBFS to be marked as done. This means that you claim that the problem has been dealt with. If this is not the c

Bug#993785: FTBFS on most architectures

Package: nfs-utils Severity: serious Version: 1:2.5.4-1~exp1 Hi Anibal, thank so much for uploading a new nfs-utils version, much appreciated. unfortunately it fails to build on most architectures, I can confirm that re-adding the dropped multiarch-patch fixes it (re-diffed patch applied).

Bug#962623: marked as done (ImportError: cannot import name 'parse_qs' from 'cgi' (/usr/lib/python3.8/cgi.py))

Your message dated Mon, 06 Sep 2021 12:03:49 + with message-id and subject line Bug#962623: fixed in graphite-web 1.1.8-1 has caused the Debian Bug report #962623, regarding ImportError: cannot import name 'parse_qs' from 'cgi' (/usr/lib/python3.8/cgi.py) to be marked as done. This means tha

Bug#992416: automake-1.16: autopkgtest failure: t/python-prefix.sh

$ cat ./t/python-prefix.log python-prefix: running python -V /packages/tmp/automake-1.16-1.16.4/t/ax/am-test-lib.sh: line 922: python: command not found SKIP t/python-prefix.sh (exit status: 77) not sure, what is going wrong here ... debian/tests/build sets PYTHON=python3... looking at python.m4

Bug#993783: snapd: AppArmor profile breaks snaps

Package: snapd Version: 2.51.7-1 Severity: grave Justification: renders package unusable X-Debbugs-Cc: andreakarim...@gmail.com Dear Maintainer, * What led up to the situation? Trying to run a "classic" snap. * What exactly did you do (or not do) that was effective (or ineffective)? Ju

Bug#993750: rgtk2: FTBFS on s390x: smoke-test failure: caught segfault

On 6 September 2021 at 09:39, Simon McVittie wrote: | On Sun, 05 Sep 2021 at 20:04:55 -0500, Dirk Eddelbuettel wrote: | > Please explain what a smoke-test failure is. | | Sorry, I thought this was a common term. | | A smoke-test for hardware: plug in the device and see whether smoke | comes out

Bug#993691: pytest-mpi: autopkgtest regression: Building wheel for mpi4py (PEP 517): finished with status 'error'

Source: pytest-mpi Followup-For: Bug #993691 Yeah, there's something right weird going on here. I can't reproduce locally. The error itself is an error. It shouldn't be trying to build a wheel for mpi4py in the first place. That implies it's downloading mpi4py source and rebuilding, the error h

Processed: missing Depends: python3-jinja2: xarray uses dask widgets

Processing commands for cont...@bugs.debian.org: > clone 993694 -1 Bug #993694 [python3-dask] missing Depends: python3-jinja2 Bug 993694 cloned as bug 993781 > reassign -1 src:python-xarray Bug #993781 [python3-dask] missing Depends: python3-jinja2 Bug reassigned from package 'python3-dask' to 'sr

Processed: bug 992901 is forwarded to https://gitlab.gnome.org/GNOME/geary/-/issues/1297

Processing commands for cont...@bugs.debian.org: > forwarded 992901 https://gitlab.gnome.org/GNOME/geary/-/issues/1297 Bug #992901 [src:geary] src:geary: fails to migrate to testing for too long due to ftbfs on armel Set Bug forwarded-to-address to 'https://gitlab.gnome.org/GNOME/geary/-/issues/

Bug#993136: marked as done (automake-1.16: autopkgtest failure with autoconf 2.71: t/deprecated-acinit.sh, t/init.sh)

Your message dated Mon, 6 Sep 2021 11:06:16 +0100 with message-id and subject line Re: Bug#993136: autopkgtest failure with autoconf 2.71: t/deprecated-acinit.sh, t/init.sh has caused the Debian Bug report #993136, regarding automake-1.16: autopkgtest failure with autoconf 2.71: t/deprecated-aci

Bug#993770: dazzdb: autopkgtest failure with glibc 2.32

Source: dazzdb Version: 1.0+git20201103.8d98c37-1 Severity: serious Forwarded: https://github.com/thegenemyers/DAZZ_DB/issues/41 X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: needs-update Hi Maintainer Since the upload of glibc 2.32-1 to unstable, dazzdb's au

Bug#993157: marked as done (libsdl2-mixer FTBFS: Error in tempfile() using template $srcdir/build-scripts/XXXXXXXXXX: Parent directory ($srcdir/build-scripts/) does not exist at /usr/bin/autoreconf li

Your message dated Mon, 06 Sep 2021 09:49:07 + with message-id and subject line Bug#993157: fixed in libsdl2-mixer 2.0.4+dfsg1-4 has caused the Debian Bug report #993157, regarding libsdl2-mixer FTBFS: Error in tempfile() using template $srcdir/build-scripts/XX: Parent directory ($src

Processed: retitle 992901 to src:geary: fails to migrate to testing for too long due to ftbfs on armel

Processing commands for cont...@bugs.debian.org: > retitle 992901 src:geary: fails to migrate to testing for too long due to > ftbfs on armel Bug #992901 [src:geary] src:perceptualdiff: fails to migrate to testing for too long due to ftbfs on armel Changed Bug title to 'src:geary: fails to migra

Bug#993743: xdemorse: autopkgtest regression: warning on stderr

control: tags -1 confirmed pending Hi Paul, On Sun, Sep 05, 2021 at 09:57:18PM +0200, Paul Gevers wrote: > Source: xdemorse > Version: 3.6.4-1 > X-Debbugs-CC: debian...@lists.debian.org, mo...@debian.org > Severity: serious > User: debian...@lists.debian.org > Usertags: regression > > Dear maint

Processed: Re: Bug#993743: xdemorse: autopkgtest regression: warning on stderr

Processing control commands: > tags -1 confirmed pending Bug #993743 [src:xdemorse] xdemorse: autopkgtest regression: warning on stderr Added tag(s) confirmed and pending. -- 993743: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993743 Debian Bug Tracking System Contact ow...@bugs.debian.org

Processed: retitle 993136 to automake-1.16: autopkgtest failure with autoconf 2.71: t/deprecated-acinit.sh, t/init.sh ...

Processing commands for cont...@bugs.debian.org: > retitle 993136 automake-1.16: autopkgtest failure with autoconf 2.71: > t/deprecated-acinit.sh, t/init.sh Bug #993136 [src:automake-1.16] automake's autopkg tests are failing with autoconf 2.71 Changed Bug title to 'automake-1.16: autopkgtest fa

Bug#993765: mlt: binary-all FTBFS

Source: mlt Version: 7.0.1-2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=mlt&arch=all&ver=7.0.1-2&stamp=1630919520&raw=0 ... debian/rules override_dh_install make[1]: Entering directory '/<>' dh_install chrpath -d -k /<>/debian/melt/usr/bin/melt-7 open: No such

Processed: tagging 993157

Processing commands for cont...@bugs.debian.org: > tags 993157 + pending Bug #993157 [src:libsdl2-mixer] libsdl2-mixer FTBFS: Error in tempfile() using template $srcdir/build-scripts/XX: Parent directory ($srcdir/build-scripts/) does not exist at /usr/bin/autoreconf line 403. Added tag(s

Bug#993716: bridge-utils: IPv6 network bridge fails after upgrading Buster to Bullseye

Hi! I'm CCing Josué because this seems to be more on ifupdown's side than on bridge-utils. > > auto br0 > > iface br0 inet static > > address 10.10.10.1 > > netmask 255.255.255.0 > > bridge_ports none > > bridge_stp off > > bridge_fd 0 > > > > iface br0 i

Bug#993621: marked as done (printer-driver-pnm2ppa: postinst failed: tempfile: not found)

Your message dated Mon, 06 Sep 2021 09:05:35 + with message-id and subject line Bug#993621: fixed in pnm2ppa 1.13-12 has caused the Debian Bug report #993621, regarding printer-driver-pnm2ppa: postinst failed: tempfile: not found to be marked as done. This means that you claim that the proble

Bug#993636: marked as done (printer-driver-pnm2ppa: Problem installation this version.)

Your message dated Mon, 06 Sep 2021 09:05:35 + with message-id and subject line Bug#993621: fixed in pnm2ppa 1.13-12 has caused the Debian Bug report #993621, regarding printer-driver-pnm2ppa: Problem installation this version. to be marked as done. This means that you claim that the problem

Bug#993750: rgtk2: FTBFS on s390x: smoke-test failure: caught segfault

On Sun, 05 Sep 2021 at 20:04:55 -0500, Dirk Eddelbuettel wrote: > Please explain what a smoke-test failure is. Sorry, I thought this was a common term. A smoke-test for hardware: plug in the device and see whether smoke comes out. If yes, reject it. If not, it *might* work as intended (but furthe

Bug#993729: marked as done (aalib: declares compliance with bogus not-yet-released Policy 4.6.1')

Your message dated Mon, 06 Sep 2021 08:34:49 + with message-id and subject line Bug#993729: fixed in aalib 1.4p5-50 has caused the Debian Bug report #993729, regarding aalib: declares compliance with bogus not-yet-released Policy 4.6.1' to be marked as done. This means that you claim that the

Bug#993143: marked as done (kconfig-frontends FTBFS: autoreconf: error: cannot create scripts/.autostuff/scripts: No such file or directory)

Your message dated Mon, 06 Sep 2021 08:36:22 + with message-id and subject line Bug#993143: fixed in kconfig-frontends 4.11.0.1+dfsg-6 has caused the Debian Bug report #993143, regarding kconfig-frontends FTBFS: autoreconf: error: cannot create scripts/.autostuff/scripts: No such file or dire

Processed: tagging 993759

Processing commands for cont...@bugs.debian.org: > tags 993759 + sid bookworm Bug #993759 [debhelper] uucp FTBFS: dh_installsystemd vs /usr-merge Added tag(s) bookworm and sid. > thanks Stopping processing here. Please contact me if you need assistance. -- 993759: https://bugs.debian.org/cgi-bin

Processed: grub-efi-amd64: upgrade works, boot fails (error: symbol `grub_is_lockdown` not found)

Processing commands for cont...@bugs.debian.org: > package grub-efi-amd64 Limiting to bugs with field 'package' containing at least one of 'grub-efi-amd64' Limit currently set to 'package':'grub-efi-amd64' > found 984760 2.02+dfsg1-20+deb10u4 Bug #984760 [grub-efi-amd64] grub-efi-amd64: upgrade

Bug#984760: grub-efi-amd64: upgrade works, boot fails (error: symbol `grub_is_lockdown` not found)

package grub-efi-amd64 found 984760 2.02+dfsg1-20+deb10u4 thanks Hello, I also had this issue when upgrading from stretch to buster. For me the BIOS allowed be to select the EFI image to boot, so I was able to boot into the system that way, then the fix was to: 1) run again update-grub2 and 2)