Bug#980596: mkvtoolnix: FTBFS: src/merge/reader_detection_and_creation.cpp:164:54: internal compiler error: Segmentation fault

On 20 janv. 2021 21:29, Lucas Nussbaum wrote: > Source: mkvtoolnix > Version: 52.0.0-1 > Severity: serious > Justification: FTBFS on amd64 > Tags: bullseye sid ftbfs > Usertags: ftbfs-20210120 ftbfs-bullseye > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on

Bug#980683: marked as pending in plasma-discover

Control: tag -1 pending Hello, Bug #980683 in plasma-discover 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#980683 marked as pending in plasma-discover

Processing control commands: > tag -1 pending Bug #980683 [src:plasma-discover] plasma-discover: FTBFS: dh_install: error: missing files, aborting Added tag(s) pending. -- 980683: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980683 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#980683: marked as done (plasma-discover: FTBFS: dh_install: error: missing files, aborting)

Your message dated Thu, 21 Jan 2021 08:33:51 + with message-id and subject line Bug#980683: fixed in plasma-discover 5.20.5-2 has caused the Debian Bug report #980683, regarding plasma-discover: FTBFS: dh_install: error: missing files, aborting to be marked as done. This means that you claim

Bug#972377: can't reproduce

can't reproduce

Bug#980434: Boot failure triggered by USB on rockpro64-rk3399 and pinebook-pro-rk3399

On 21/01/2021 03:08, Vagrant Cascadian wrote: > It seems rockpro64-rk3399 and pinebook-pro-rk3399 fail to boot when usb > is started. It hangs indefinitely at: > > ## Flattened Device Tree blob at 01f0 > Booting using the fdt blob at 0x1f0 > > I have observed this also using

Bug#980740: r-bioc-geoquery: flaky autopkgtests failing to download test data

Hi Graham, so what is you suggestion? Simply droping the test is possibly not the best solution. Marking it flaky comes to mind. What do you think? Kind regards Andreas. On Thu, Jan 21, 2021 at 10:52:49AM +0200, Graham Inggs wrote: > Source: r-bioc-geoquery > Version: 2.58.0+dfsg-1 >

Processed: tagging 980681

Processing commands for cont...@bugs.debian.org: > tags 980681 + pending Bug #980681 [src:ktimetracker] ktimetracker: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j4 test ARGS\+=-j4 returned exit code 2 Added tag(s) pending. > thanks Stopping processing here. Please contact me

Bug#980090: marked as done (r-cran-dbplyr: autopkgtest regression)

Your message dated Thu, 21 Jan 2021 11:46:32 +0100 with message-id and subject line Re: r-cran-dbplyr: autopkgtest regression has caused the Debian Bug report #980090, regarding r-cran-dbplyr: autopkgtest regression to be marked as done. This means that you claim that the problem has been dealt

Bug#980740: r-bioc-geoquery: flaky autopkgtests failing to download test data

Source: r-bioc-geoquery Version: 2.58.0+dfsg-1 Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: flaky Hi Maintainer The autopkgtests of r-bioc-geoquery seem to download large amounts of test data from the internet, and these

Bug#978172: evolution-data-server: FTBFS: CheckFunctionExists.c:17: undefined reference to `res_query'

severity 978172 normal retitle 978172 Decide whether libphonenumber or its users should B-D against libboost dev packages thanks EDS builds fine again, now that libphonenumber has reintroduced the B-D against libboost dev packages libphonenumber maintainer wants use to depend on boost dev

Processed (with 1 error): Re: evolution-data-server: FTBFS: CheckFunctionExists.c:17: undefined reference to `res_query'

Processing commands for cont...@bugs.debian.org: > severity 978172 normal Bug #978172 [src:evolution-data-server,src:libphonenumber] evolution-data-server: FTBFS: libphonenumber-dev no longer depends on libboost-dev as needed when defining I18N_PHONENUMBERS_USE_BOOST Severity set to 'normal'

Bug#980740: r-bioc-geoquery: flaky autopkgtests failing to download test data

Hi Andreas On Thu, 21 Jan 2021 at 11:19, Andreas Tille wrote: > so what is you suggestion? Simply droping the test is possibly > not the best solution. Marking it flaky comes to mind. What > do you think? If it were my package, I would probably drop the tests that download from the internet,

Processed: tagging 980695

Processing commands for cont...@bugs.debian.org: > tags 980695 + pending Bug #980695 [src:tellico] tellico: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j1 test XDG_DATA_DIRS=/<>/test_root/usr/share:/usr/local/share:/usr/share HOME=/tmp/tellico-home.OAHYcd

Bug#980435: osdsh: Silent SIGSEGV at startup

Hi, On Wed, 20 Jan 2021, at 19:36, Celelibi wrote: > > > Nowadays, osdsh crashes without a message. > > > The cause I identified is that it looks for a symbol "mixerdevice" in > > > the shared library libosdshmixer.so which doesn't exist. > > > Since the return of dlsym isn't checked, it

Bug#980681: marked as done (ktimetracker: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j4 test ARGS\+=-j4 returned exit code 2)

Your message dated Thu, 21 Jan 2021 11:18:31 + with message-id and subject line Bug#980681: fixed in ktimetracker 4:5.0.1-3 has caused the Debian Bug report #980681, regarding ktimetracker: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j4 test ARGS\+=-j4 returned exit code 2

Bug#980695: marked as done (tellico: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j1 test XDG_DATA_DIRS=/<>/test_root/usr/share:/usr/local/share:/usr/share HOME=/tmp/telli

Your message dated Thu, 21 Jan 2021 11:34:11 + with message-id and subject line Bug#980695: fixed in tellico 3.3.4-2 has caused the Debian Bug report #980695, regarding tellico: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j1 test

Bug#980589: [Pkg-electronics-devel] Bug#980589: libsigrok: FTBFS: tests/strutil.c:157:2: error: too few arguments to function ‘_ck_assert_failed’

This is a result of the new "check" 0.15.2 package (updated from 0.12.0), in particular upstream commit 82540c5428d3818b64d6a8aefb601e722520651f: https://github.com/libcheck/check/commit/82540c5428d3818b64d6a8aefb601e722520651f "For users of these APIs who do pass a message there will be a new

Bug#980202: convert fails to create image with text

reassign 980202 imagemagick 8:6.9.11.57+dfsg-1 thanks convert +matte -depth 1 -colorspace Gray -pointsize 12 -units PixelsPerInch -density 300 label:"The quick brown fox" test.png used to create an image like the test-old.png attachment In 8:6.9.11.57+dfsg-1, the same call produces an image

Processed: convert fails to create image with text

Processing commands for cont...@bugs.debian.org: > reassign 980202 imagemagick 8:6.9.11.57+dfsg-1 Bug #980202 [src:gscan2pdf] FTBFS: gscan2pdf tests fail Bug reassigned from package 'src:gscan2pdf' to 'imagemagick'. No longer marked as found in versions gscan2pdf/2.10.2-1. Ignoring request to

Bug#957406: kmscube: ftbfs with GCC-10

Version: kmscube/0.0.0~git20210103-1 Hi, On Fri, Apr 17, 2020 at 11:03:44AM +, Matthias Klose wrote: > Package: src:kmscube > Version: 0.0.0~git20170617-2 > Severity: normal > Tags: sid bullseye > User: debian-...@lists.debian.org > Usertags: ftbfs-gcc-10> > Please keep this issue open in

Bug#957406: marked as done (kmscube: ftbfs with GCC-10)

Your message dated Thu, 21 Jan 2021 10:49:57 +0100 with message-id <20210121094957.ga6...@bogon.m.sigxcpu.org> and subject line Re: Bug#957406: kmscube: ftbfs with GCC-10 has caused the Debian Bug report #957406, regarding kmscube: ftbfs with GCC-10 to be marked as done. This means that you claim

Processed: affects 980715

Processing commands for cont...@bugs.debian.org: > affects 980715 - src:evolotion-data-server Bug #980715 [src:ignition-transport] tighten dependencies on libprotobuf-dev Removed indication that 980715 affects > thanks Stopping processing here. Please contact me if you need assistance. --

Processed: affects 980714

Processing commands for cont...@bugs.debian.org: > affects 980714 - src:evolotion-data-server Bug #980714 [src:ignition-msgs] tighten dependencies on libprotobuf-dev Removed indication that 980714 affects > thanks Stopping processing here. Please contact me if you need assistance. -- 980714:

Processed: Re: [Android-tools-devel] Bug#980644: android-sdk-platform-tools-common: no Multi-Arch annotation prevents adb upgrade

Processing control commands: > severity -1 normal Bug #980644 [android-sdk-platform-tools-common] android-sdk-platform-tools-common: no Multi-Arch annotation prevents adb upgrade Severity set to 'normal' from 'serious' -- 980644: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980644 Debian

Bug#980644: [Android-tools-devel] Bug#980644: android-sdk-platform-tools-common: no Multi-Arch annotation prevents adb upgrade

Control: severity -1 normal Right now, we can only commit to supporting the arches that upstream supports (amd64 and arm64), so I'm downgrading the severity. I could never wrap my head around the Multi-Arch: stuff. I would accept a merge request on salsa for this, if it passes in

Bug#980710: marked as done (mpi4py: FTBFS: ld: cannot find -llmpe)

Your message dated Thu, 21 Jan 2021 09:41:59 +0100 with message-id <20210121084158.ga25...@ramacher.at> and subject line Re: Bug#980710: mpi4py: FTBFS: ld: cannot find -llmpe has caused the Debian Bug report #980710, regarding mpi4py: FTBFS: ld: cannot find -llmpe to be marked as done. This means

Bug#972767: frr: diff for NMU version 7.4-1.1

Control: tags 972767 + pending Dear maintainer, I've prepared an NMU for frr (versioned as 7.4-1.1) and uploaded it to DELAYED/7. Please feel free to tell me if I should cancel it. cu Adrian diff -Nru frr-7.4/debian/changelog frr-7.4/debian/changelog --- frr-7.4/debian/changelog 2020-08-10

Bug#980715: closing 980715, reassign 980586 to src:ignition-msgs, reassign 980590 to src:ignition-msgs ...

# not needed close 980715 reassign 980586 src:ignition-msgs reassign 980590 src:ignition-msgs forcemerge 980714 980586 980590 affects 980714 + src:gazebo src:ignition-fuel-tools thanks

Processed: frr: diff for NMU version 7.4-1.1

Processing control commands: > tags 972767 + pending Bug #972767 [src:frr] frr ftbfs with python3.9 Added tag(s) pending. -- 972767: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972767 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#980674: marked as done (civetweb: FTBFS: cp: cannot stat '/usr/share/nodejs/jquery/dist/jquery.min.js': No such file or directory)

Your message dated Thu, 21 Jan 2021 15:33:26 + with message-id and subject line Bug#980674: fixed in civetweb 1.13+dfsg-5 has caused the Debian Bug report #980674, regarding civetweb: FTBFS: cp: cannot stat '/usr/share/nodejs/jquery/dist/jquery.min.js': No such file or directory to be marked

Bug#975931: should be fixed with pocl 1.6 ?

pocl 1.6-3 has migrated to testing on 2021-01-13, and upstream declares that v1.6 includes "Support for Clang/LLVM 11". Can you try your reproducer now ? Thanks Paolo

Processed: closing 980715, reassign 980586 to src:ignition-msgs, reassign 980590 to src:ignition-msgs ...

Processing commands for cont...@bugs.debian.org: > # not needed > close 980715 Bug #980715 [src:ignition-transport] tighten dependencies on libprotobuf-dev Marked Bug as done > reassign 980586 src:ignition-msgs Bug #980586 [src:gazebo] gazebo: FTBFS: time.pb.h:59:51: error:

Bug#980750: linux-image-5.10.0-1-amd64: no compatibility with new AMD RX 6800 generation graphics cards

Package: src:linux Version: 5.10.5-1 Severity: grave Tags: d-i Justification: renders package unusable X-Debbugs-Cc: compte.perso.de-al...@bbox.fr hello to all . this post to ask you for help . it seems indeed that the kernel 5.10.0-1 sid is not yet ready to support the latest amd graphics cards

Bug#980629: nheko: FTBFS: internal compiler error

reassign 980629 gcc-10 10.2.1-6 thanks Fedora ran into the same issue: https://bugzilla.redhat.com/show_bug.cgi?id=1918341 and someone linked to a patch that supposedly fixes this: https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=2b27f37f90cb66e277b734c605639e2f00a2e942 So I guess reassigning

Processed: Re: Bug#980629: nheko: FTBFS: internal compiler error

Processing commands for cont...@bugs.debian.org: > reassign 980629 gcc-10 10.2.1-6 Bug #980629 [src:nheko] nheko: FTBFS: internal compiler error Bug reassigned from package 'src:nheko' to 'gcc-10'. No longer marked as found in versions nheko/0.7.2-3. Ignoring request to alter fixed versions of

Processed: severity of 733094 is critical

Processing commands for cont...@bugs.debian.org: > severity 733094 critical Bug #733094 [uvcdynctrl] fills disk writing to /var/log/uvcdynctrl-udev.log Severity set to 'critical' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 733094:

Bug#922981: ca-certificates-java: "update-ca-certificates -f" doesn't update "/etc/ssl/certs/java/cacerts"

Control: tag -1 - patch + moreinfo There is more to it ... update-ca-certificates provides the hook scripts with +/- prefixed certificates on stdin. But ca-certificates runs update-ca-certificates twice: once during configure step (without hooks, which may not be callable because their packages

Processed: severity of 980750 is important

Processing commands for cont...@bugs.debian.org: > severity 980750 important Bug #980750 [src:linux] linux-image-5.10.0-1-amd64: no compatibility with new AMD RX 6800 generation graphics cards Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if you

Processed: Re: ca-certificates-java: "update-ca-certificates -f" doesn't update "/etc/ssl/certs/java/cacerts"

Processing control commands: > tag -1 - patch + moreinfo Bug #922981 [ca-certificates-java] ca-certificates-java: /etc/ca-certificates/update.d/jks-keystore doesn't update /etc/ssl/certs/java/cacerts Removed tag(s) patch. Bug #922981 [ca-certificates-java] ca-certificates-java:

Processed: your mail

Processing commands for cont...@bugs.debian.org: > fixed 980090 2.0.0-1 Bug #980090 {Done: "Michael R. Crusoe" } [src:r-cran-dbplyr] r-cran-dbplyr: autopkgtest regression Marked as fixed in versions r-cran-dbplyr/2.0.0-1. > End of message, stopping processing here. Please contact me if you need

Bug#980673: marked as pending in python-babel

Control: tag -1 pending Hello, Bug #980673 in python-babel 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#980673 marked as pending in python-babel

Processing control commands: > tag -1 pending Bug #980673 [src:python-babel] python-babel: FTBFS: test failed Added tag(s) pending. -- 980673: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980673 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#980599: marked as done (kitinerary: FTBFS: phonenumber.pb.h:47:51: error: ‘AuxiliaryParseTableField’ in namespace ‘google::protobuf::internal’ does not name a type; did you mean ‘AuxillaryParseTab

Your message dated Thu, 21 Jan 2021 14:24:46 +0100 with message-id <22077935.6Emhk5qWAg@tuxin> and subject line Re: Bug#980599: kitinerary: FTBFS: phonenumber.pb.h:47:51: error: ‘AuxiliaryParseTableField’ in namespace ‘google::protobuf::internal’ does not name a type; did you mean

Bug#980714: marked as done (tighten dependencies on libprotobuf-dev)

Your message dated Thu, 21 Jan 2021 15:03:31 + with message-id and subject line Bug#980714: fixed in ignition-msgs 5.1.0+dfsg-7 has caused the Debian Bug report #980714, regarding tighten dependencies on libprotobuf-dev to be marked as done. This means that you claim that the problem has

Bug#980586: marked as done (gazebo: FTBFS: time.pb.h:59:51: error: ‘AuxiliaryParseTableField’ in namespace ‘google::protobuf::internal’ does not name a type; did you mean ‘AuxillaryParseTableField’?)

Your message dated Thu, 21 Jan 2021 15:03:31 + with message-id and subject line Bug#980714: fixed in ignition-msgs 5.1.0+dfsg-7 has caused the Debian Bug report #980714, regarding gazebo: FTBFS: time.pb.h:59:51: error: ‘AuxiliaryParseTableField’ in namespace ‘google::protobuf::internal’ does

Bug#972021: pysph ftbfs with python3.9 as supported python version

> Package: src:pydantic > Version: 1.0~b0~20191115.gite3d5e10-2 > Severity: important > Tags: sid bullseye > User: debian-pyt...@lists.debian.org > Usertags: python3.9 > > > make[1]: Leaving directory '/<>' >dh_auto_test -a -O--buildsystem=pybuild > I: pybuild base:217: cd

Bug#972021: marked as done (pysph ftbfs with python3.9 as supported python version)

Your message dated Thu, 21 Jan 2021 14:41:56 +0100 with message-id and subject line Close #972021 has caused the Debian Bug report #972021, regarding pysph ftbfs with python3.9 as supported python version to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#980435: marked as done (osdsh: Silent SIGSEGV at startup)

Your message dated Thu, 21 Jan 2021 11:49:57 + with message-id and subject line Bug#980435: fixed in osdsh 0.7.0-10.5 has caused the Debian Bug report #980435, regarding osdsh: Silent SIGSEGV at startup to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#980617: marked as done (racon: FTBFS: build-dependency not installable: libthread-pool-dev (>= 3.0.2))

Your message dated Thu, 21 Jan 2021 13:12:28 +0100 with message-id <6bdd1dc7-d334-47c3-a109-528496953...@debian.org> and subject line Re: racon: FTBFS: build-dependency not installable: libthread-pool-dev (>= 3.0.2) has caused the Debian Bug report #980617, regarding racon: FTBFS:

Bug#980639: marked as pending in python-eventlet

Control: tag -1 pending Hello, Bug #980639 in python-eventlet 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#980639 marked as pending in python-eventlet

Processing control commands: > tag -1 pending Bug #980639 [src:python-eventlet] python-eventlet: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i python{version} -p 3.9 returned exit code 13 Added tag(s) pending. -- 980639: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980639

Bug#980684: Bug#980691: gnome-software: FTBFS: Package 'jcat', required by 'fwupd', not found

Control: retitle 980691 gnome-software: FTBFS: Package 'jcat', required by 'fwupd', not found Control: retitle 980684 gnome-firmware: FTBFS: Package 'jcat', required by 'fwupd', not found Control: reassign 980691 libfwupd-dev 1.5.5-2 Control: reassign 980684 libfwupd-dev 1.5.5-2 Control: merge

Processed: Re: Bug#980691: gnome-software: FTBFS: Package 'jcat', required by 'fwupd', not found

Processing control commands: > retitle 980691 gnome-software: FTBFS: Package 'jcat', required by 'fwupd', > not found Bug #980691 [src:gnome-software] gnome-software: FTBFS: dh_auto_configure: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. --wrap-mode=nodownload --buildtype=plain

Bug#980688: marked as done (seaborn: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13)

Your message dated Thu, 21 Jan 2021 12:18:59 + with message-id and subject line Bug#980688: fixed in seaborn 0.11.1-1 has caused the Debian Bug report #980688, regarding seaborn: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13 to be

Bug#980673: marked as done (python-babel: FTBFS: test failed)

Your message dated Thu, 21 Jan 2021 13:04:46 + with message-id and subject line Bug#980673: fixed in python-babel 2.8.0+dfsg.1-6 has caused the Debian Bug report #980673, regarding python-babel: FTBFS: test failed to be marked as done. This means that you claim that the problem has been

Processed: your mail

Processing commands for cont...@bugs.debian.org: > reassign 980599 libphonenumber 7.1.0-7 Bug #980599 {Done: Sandro Knauß } [src:kitinerary] kitinerary: FTBFS: phonenumber.pb.h:47:51: error: ‘AuxiliaryParseTableField’ in namespace ‘google::protobuf::internal’ does not name a type; did you

Processed: Re: Bug#980691: gnome-software: FTBFS: Package 'jcat', required by 'fwupd', not found

Processing control commands: > retitle 980691 gnome-software: FTBFS: Package 'jcat', required by 'fwupd', > not found Bug #980691 [libfwupd-dev] gnome-software: FTBFS: Package 'jcat', required by 'fwupd', not found Bug #980684 [libfwupd-dev] gnome-firmware: FTBFS: Package 'jcat', required by

Bug#977848: marked as done (libfprint: FTBFS on mips*)

Your message dated Thu, 21 Jan 2021 13:03:55 + with message-id and subject line Bug#977848: fixed in libfprint 1:1.90.7-1 has caused the Debian Bug report #977848, regarding libfprint: FTBFS on mips* to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#980473: ModuleNotFoundError: No module named 'Crypto'

Hi, Patch applied, waiting for sponsorship. Cheers, Arias Emmanuel @eamanu yaerobi.com On Tue, Jan 19, 2021 at 6:30 PM Sebastian Ramacher wrote: > Control: tags -1 + patch > > On 2021-01-20 01:52:54 +1100, Konomi Kitten wrote: > > Package: python3-otr > > Version: python3-potr > > Severity:

Processed: tagging 975801

Processing commands for cont...@bugs.debian.org: > tags 975801 + pending Bug #975801 [src:python-aioxmpp] python-aioxmpp: FTBFS: TypeError: 'Lock' object is not iterable Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 975801:

Processed: tagging 975822

Processing commands for cont...@bugs.debian.org: > tags 975822 + pending Bug #975822 [src:pyramid-jinja2] pyramid-jinja2: Missing build dependency on python3-webtest Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 975822:

Bug#971309: marked as done (ansible: Switch to python3-pycryptodome)

Your message dated Thu, 21 Jan 2021 14:10:08 + with message-id and subject line Bug#971309: fixed in ansible-base 2.10.4-1 has caused the Debian Bug report #971309, regarding ansible: Switch to python3-pycryptodome to be marked as done. This means that you claim that the problem has been

Bug#977814: should be fixed with clazy 1.9-3

Hi I see "pass" for clazy/1.9-3 with llvm-toolchain-11/1:11.0.1-2: https://ci.debian.net/packages/c/clazy/testing/amd64/ I also tried this here on unstable and the autopkgtest did pass. Can you check and if confirmed as fixed close this bug? Thanks, Paolo

Bug#980696: ceres-solver: FTBFS: make[3]: *** No rule to make target '/usr/lib/x86_64-linux-gnu/libunwind.so', needed by 'bin/visibility_based_preconditioner_test'. Stop.

Control: reassign -1 libgoogle-glog-dev 0.4.0-3 Control: retitle -1 missing dependency on libunwind-dev Control: affects -1 src:ceres-solver Hi, * Lucas Nussbaum [2021-01-20 21:54]: make[3]: *** No rule to make target '/usr/lib/x86_64-linux-gnu/libunwind.so', needed by

Processed: Re: Bug#980696: ceres-solver: FTBFS: make[3]: *** No rule to make target '/usr/lib/x86_64-linux-gnu/libunwind.so', needed by 'bin/visibility_based_preconditioner_test'. Stop.

Processing control commands: > reassign -1 libgoogle-glog-dev 0.4.0-3 Bug #980696 [src:ceres-solver] ceres-solver: FTBFS: make[3]: *** No rule to make target '/usr/lib/x86_64-linux-gnu/libunwind.so', needed by 'bin/visibility_based_preconditioner_test'. Stop. Bug reassigned from package

Bug#980634: [Debichem-devel] Bug#980634: gromacs: FTBFS: Errors while running CTest

This is *probably* a side effect of the ongoing, messy mpich/pmix/ucx transition in unstable, but that has so many moving parts that it'll take a bit to figure out which version of which package is responsible.

Bug#948105: marked as done (Remove build dep on libuhttpmock-dev)

Your message dated Thu, 21 Jan 2021 16:48:58 + with message-id and subject line Bug#948105: fixed in libgdata 0.17.13-2 has caused the Debian Bug report #948105, regarding Remove build dep on libuhttpmock-dev to be marked as done. This means that you claim that the problem has been dealt

Bug#980658: marked as pending in pygame-sdl2

Control: tag -1 pending Hello, Bug #980658 in pygame-sdl2 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#980658 marked as pending in pygame-sdl2

Processing control commands: > tag -1 pending Bug #980658 [src:pygame-sdl2] pygame-sdl2: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 Added tag(s) pending. -- 980658: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980658 Debian Bug Tracking System

Processed: [bts-link] source package src:macsyfinder

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:macsyfinder > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user

Processed: [bts-link] source package src:flask-security

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:flask-security > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user

Processed: petsc: breaks multiple autopkgtests: undefined reference to 'MPIU_SUM'

Processing control commands: > affects -1 deal.ii dolfin meshr slepc4py Bug #980751 [src:petsc] petsc: breaks multiple autopkgtests: undefined reference to 'MPIU_SUM' Added indication that 980751 affects deal.ii, dolfin, meshr, and slepc4py -- 980751:

Bug#980751: petsc: breaks multiple autopkgtests: undefined reference to 'MPIU_SUM'

Source: petsc Version: 3.14.3+dfsg1-1 Severity: serious X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks Control: affects -1 deal.ii dolfin meshr slepc4py Hi Maintainer The recent upload of petsc 3.14.3+dfsg1-1 appears to have caused the autopkgtests of

Bug#980434: Boot failure triggered by USB on rockpro64-rk3399 and pinebook-pro-rk3399

U-Boot 2020.07 worked, broken on rockpro64 by commit 3ae64582fb8ceead4fc464cd2055eb3eaef78ccc (refs/bisect/bad) Author: Jagan Teki Date: Mon Jul 20 14:53:09 2020 +0530 rockchip: rockpro64: Enable USB3.0 Host Enable USB3.0 Host support for RockPro64 boards. Signed-off-by:

Bug#980434: marked as pending in u-boot

Control: tag -1 pending Hello, Bug #980434 in u-boot 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#980434 marked as pending in u-boot

Processing control commands: > tag -1 pending Bug #980434 [u-boot-rockchip] u-boot-rockchip: rockpro64-rk3399 and pinebook-pro-rk3399 fail to boot Added tag(s) pending. -- 980434: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980434 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#980434: marked as done (u-boot-rockchip: rockpro64-rk3399 and pinebook-pro-rk3399 fail to boot)

Your message dated Fri, 22 Jan 2021 05:03:51 + with message-id and subject line Bug#980434: fixed in u-boot 2021.01+dfsg-2 has caused the Debian Bug report #980434, regarding u-boot-rockchip: rockpro64-rk3399 and pinebook-pro-rk3399 fail to boot to be marked as done. This means that you

Bug#980579: marked as done (ruby-librarian: FTBFS: Could not find 'thor' (~> 0.15))

Your message dated Thu, 21 Jan 2021 20:49:50 + with message-id and subject line Bug#980579: fixed in ruby-librarian 0.6.4-2 has caused the Debian Bug report #980579, regarding ruby-librarian: FTBFS: Could not find 'thor' (~> 0.15) to be marked as done. This means that you claim that the

Bug#980772: python-pysaml2: CVE-2021-21239: Unspecified xmlsec1 key-type preference

Source: python-pysaml2 Version: 6.1.0-3 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for python-pysaml2. CVE-2021-21239[0]: | PySAML2 is a pure python implementation

Bug#970717: marked as done (kubernetes: abuse of "embedded code copies" | hundreds of vendored libraries)

Your message dated Thu, 21 Jan 2021 22:27:44 + with message-id and subject line has caused the Debian Bug report #970717, regarding kubernetes: abuse of "embedded code copies" | hundreds of vendored libraries to be marked as done. This means that you claim that the problem has been dealt

Processed: Re: namazu2-index-tools: contains namazu.1 manpage after separate arch-indep build

Processing commands for cont...@bugs.debian.org: > # see below for reason for this clone > clone 979301 -1 Bug #979301 [namazu2-index-tools] namazu2-index-tools: contains namazu.1 manpage after separate arch-indep build Bug 979301 cloned as bug 980776 > found -1 2.0.21-22 Bug #980776

Bug#980564: marked as done (chromium: 88.0.4324.96 stable release)

Your message dated Thu, 21 Jan 2021 23:34:38 + with message-id and subject line Bug#980564: fixed in chromium 88.0.4324.96-0.1 has caused the Debian Bug report #980564, regarding chromium: 88.0.4324.96 stable release to be marked as done. This means that you claim that the problem has been

Bug#980773: python-pysaml2: CVE-2021-21238: Processing of invalid SAML XML documents

Source: python-pysaml2 Version: 6.1.0-3 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for python-pysaml2. CVE-2021-21238[0]: | PySAML2 is a pure python implementation

Bug#971289: beaker: Switch to python3-pycryptodome

I think there are several issues: The first issue is the mere presence of tests. The source package has code to run the upstream tests (via "nose"); that is precisely one of the reasons for the Build-Depends on python3-crypto. However, these tests are not run (anymore) because upstream now

Processed: severity of 976146 is grave

Processing commands for cont...@bugs.debian.org: > #renders package unusable by default > severity 976146 grave Bug #976146 [pipx] pipx broken with python 3.9 Severity set to 'grave' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 976146:

Bug#980654: marked as pending in node-esprima

Control: tag -1 pending Hello, Bug #980654 in node-esprima 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#980654 marked as pending in node-esprima

Processing control commands: > tag -1 pending Bug #980654 [src:node-esprima] node-esprima: FTBFS: Error: Cannot find module '@types/estree' Added tag(s) pending. -- 980654: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980654 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#980682: marked as done (liblist-objects-withutils-perl: FTBFS: dh_auto_test: error: make -j1 test TEST_VERBOSE=1 returned exit code 2)

Your message dated Fri, 22 Jan 2021 00:03:50 + with message-id and subject line Bug#980682: fixed in liblist-objects-withutils-perl 2.028003-2 has caused the Debian Bug report #980682, regarding liblist-objects-withutils-perl: FTBFS: dh_auto_test: error: make -j1 test TEST_VERBOSE=1 returned

Bug#957129: ddrutility: diff for NMU version 2.8-1.1

Control: tags 957129 + patch Control: tags 957129 + pending -- Dear maintainer, I've prepared an NMU for ddrutility (versioned as 2.8-1.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should cancel it. -- Regards Sudip diff -Nru ddrutility-2.8/debian/changelog

Processed: ddrutility: diff for NMU version 2.8-1.1

Processing control commands: > tags 957129 + patch Bug #957129 [src:ddrutility] ddrutility: ftbfs with GCC-10 Added tag(s) patch. > tags 957129 + pending Bug #957129 [src:ddrutility] ddrutility: ftbfs with GCC-10 Added tag(s) pending. -- 957129:

Bug#980603: [3dprinter-general] Bug#980603: cura: FTBFS: cura/PrinterOutput/Models/MaterialOutputModel.py:6: error: Module 'PyQt5.QtCore' has no attribute 'pyqtProperty'

Re: Lucas Nussbaum > > 14/14 Test #1: code-style ...***Failed 61.38 sec > > cura/PrinterOutput/Models/MaterialOutputModel.py:6: error: Module > > 'PyQt5.QtCore' has no attribute 'pyqtProperty' Fwiw cura still works fine here, so I'd claim this is a test-only problem which

Processed (with 5 errors): your mail

Processing commands for cont...@bugs.debian.org: > severity #892326 grave Bug #892326 [src:herisvm] herisvm: tests fail Severity set to 'grave' from 'wishlist' > It does not seem to be functional, it is abandoned by the upstream since 2019, Unknown command or malformed arguments to command. >

Bug#957797: marked as done (simh: ftbfs with GCC-10)

Your message dated Thu, 21 Jan 2021 23:10:10 + with message-id and subject line Bug#957797: fixed in simh 3.8.1-6.1 has caused the Debian Bug report #957797, regarding simh: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#980709: dolfin: FTBFS: tests failed

Lucas Nussbaum wrote: Source: dolfin Version: 2019.2.0~git20200629.946dbd3+lfs-4 ... During a rebuild of all packages in sid, your package failed to build on amd64. Hi Lucas, there have been various test failures associated with the recent openmpi upgrade. They seem to be resolved now.

Processed: vflib3: diff for NMU version 3.6.14.dfsg-3+nmu5

Processing control commands: > tags 957909 + patch Bug #957909 [src:vflib3] vflib3: ftbfs with GCC-10 Added tag(s) patch. > tags 957909 + pending Bug #957909 [src:vflib3] vflib3: ftbfs with GCC-10 Added tag(s) pending. -- 957909: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957909 Debian

Bug#957909: vflib3: diff for NMU version 3.6.14.dfsg-3+nmu5

Control: tags 957909 + patch Control: tags 957909 + pending -- Dear maintainer, I've prepared an NMU for vflib3 (versioned as 3.6.14.dfsg-3+nmu5) and uploaded it to DELAYED/2. Please feel free to tell me if I should cancel it. -- Regards Sudip diff -Nru vflib3-3.6.14.dfsg/debian/changelog

Bug#980665: marked as done (twitter-bootstrap4: FTBFS: Error: Cannot find module 'rollup-plugin-babel')

Your message dated Thu, 21 Jan 2021 20:39:28 + with message-id and subject line Bug#980665: fixed in twitter-bootstrap4 4.5.2+dfsg1-5 has caused the Debian Bug report #980665, regarding twitter-bootstrap4: FTBFS: Error: Cannot find module 'rollup-plugin-babel' to be marked as done. This

Processed (with 2 errors): reassign 980675 to src:libjsonp-java, merging 980371 980675, affects 980371

Processing commands for cont...@bugs.debian.org: > reassign 980675 src:libjsonp-java Bug #980675 [src:antlr4] antlr4: FTBFS: Could not resolve dependencies for project org.antlr:antlr4:jar:4.7.2 Bug reassigned from package 'src:antlr4' to 'src:libjsonp-java'. No longer marked as found in

Bug#980652: marked as pending in select2.js

Control: tag -1 pending Hello, Bug #980652 in select2.js 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:

  1   2   >