Bug#1002113: gr-gsm: FTBFS: ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:11: undefined reference to `pthread_create'

On Sat, Jan 29, 2022 at 02:33:25PM +0100, Petter Reinholdtsen wrote: > [Lucas Nussbaum] > > Relevant part (hopefully): > > > /usr/bin/ld: CMakeFiles/cmTC_af046.dir/src.c.o: in function `main': > > > ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:11: undefined reference > > > to `pthread_create'

Processed: Re: Bug#1004900: zim-tools: FTBFS on slow buildds

Processing commands for cont...@bugs.debian.org: > forwarded 1004900 https://github.com/openzim/zim-tools/issues/287 Bug #1004900 [src:zim-tools] zim-tools: FTBFS on slow buildds Set Bug forwarded-to-address to 'https://github.com/openzim/zim-tools/issues/287'. > thanks Stopping processing here.

Bug#1004330: makes the package useless with PHP 8

Hi Francesco, Francesco Potortì wrote: > I hope the package gets upgraded soon, because dokuwiki simply > stopped working with PHP 8 I have a more or less working package of the most recent upstream release plus one or two patches at https://salsa.debian.org/abe/dokuwiki It runs in production

Bug#994186: marked as done (libvkd3d1 uninstallable in experimental)

Your message dated Fri, 04 Feb 2022 01:48:37 + with message-id and subject line Bug#994186: fixed in vkd3d 1.2-7 has caused the Debian Bug report #994186, regarding libvkd3d1 uninstallable in experimental to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1004847: marked as done (nvidia-graphics-drivers: CVE-2022-21813, CVE-2022-21814)

Your message dated Fri, 04 Feb 2022 00:50:17 + with message-id and subject line Bug#1004847: fixed in nvidia-graphics-drivers-tesla-470 470.103.01-1 has caused the Debian Bug report #1004847, regarding nvidia-graphics-drivers: CVE-2022-21813, CVE-2022-21814 to be marked as done. This means

Bug#1004853: marked as done (nvidia-graphics-drivers-tesla-470: CVE-2022-21813, CVE-2022-21814)

Your message dated Fri, 04 Feb 2022 00:50:17 + with message-id and subject line Bug#1004853: fixed in nvidia-graphics-drivers-tesla-470 470.103.01-1 has caused the Debian Bug report #1004853, regarding nvidia-graphics-drivers-tesla-470: CVE-2022-21813, CVE-2022-21814 to be marked as done.

Processed: tagging 1002173

Processing commands for cont...@bugs.debian.org: > tags 1002173 + fixed-upstream Bug #1002173 [src:pympler] pympler: FTBFS: ImportError: cannot import name 'MutableMapping' from 'collections' (/usr/lib/python3.10/collections/__init__.py) Added tag(s) fixed-upstream. > thanks Stopping processing

Processed: postfix-mta-sts-resolver: diff for NMU version 1.0.0-4.1

Processing control commands: > tags 996048 + patch Bug #996048 [postfix-mta-sts-resolver] postfix-mta-sts-resolver: autopkgtest doesn't handle new version of ca-certificates nicely: rehash: warning: skipping ca-certificates.crt,it does not contain exactly one certificate or CRL Added tag(s)

Bug#996048: postfix-mta-sts-resolver: diff for NMU version 1.0.0-4.1

Control: tags 996048 + patch Control: tags 996048 + pending Dear maintainer, I've prepared an NMU for postfix-mta-sts-resolver (versioned as 1.0.0-4.1) and uploaded it to DELAYED/14. Please feel free to tell me if I should cancel it. cu Adrian diff -Nru

Processed: Re: Bug#984209: libsynthesis: diff for NMU version 3.4.0.47.5+syncevolution-1.5.3-1.1

Processing control commands: > forcemerge -1 1002146 Bug #984209 [src:libsynthesis] libsynthesis: ftbfs with GCC-11 Bug #1002146 [src:libsynthesis] libsynthesis: FTBFS: sysync_SDK/Sources/san.h:264:5: error: reference to ‘byte’ is ambiguous Severity set to 'important' from 'serious' Added tag(s)

Bug#1004330: makes the package useless with PHP 8

I hope the package gets upgraded soon, because dokuwiki simply stopped working with PHP 8 I used a stopgap, by looking at the Apache errors end modifying the php source files generating the error, but that's long and tedious. And I cannot be sure that everything works... -- Francesco

Bug#1004940: gr-iio seems to be integrated into gnuradio now

Package: gr-iio Version: 0.3-9 Severity: serious Tags: bookworm sid https://www.gnuradio.org/news/2022-01-17-gnuradio-v3.10.0.0-release/ - New in-tree module gr-iio

Bug#987689: marked as done (Upgrade to 2021.03)

Your message dated Fri, 04 Feb 2022 00:00:09 + with message-id and subject line Bug#987689: fixed in onetbb 2021.5.0-1 has caused the Debian Bug report #987689, regarding Upgrade to 2021.03 to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#997115: marked as done (tbb: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below)

Your message dated Fri, 04 Feb 2022 00:00:09 + with message-id and subject line Bug#997115: fixed in onetbb 2021.5.0-1 has caused the Debian Bug report #997115, regarding tbb: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below to be

Bug#965759: marked as done (opus-tools: Removal of obsolete debhelper compat 5 and 6 in bookworm)

Your message dated Thu, 03 Feb 2022 21:50:00 + with message-id and subject line Bug#965759: fixed in opus-tools 0.1.10-1.1 has caused the Debian Bug report #965759, regarding opus-tools: Removal of obsolete debhelper compat 5 and 6 in bookworm to be marked as done. This means that you claim

Bug#965538: marked as done (gcc-h8300-hms: Removal of obsolete debhelper compat 5 and 6 in bookworm)

Your message dated Thu, 03 Feb 2022 21:49:14 + with message-id and subject line Bug#965538: fixed in gcc-h8300-hms 1:3.4.6+dfsg2-4.2 has caused the Debian Bug report #965538, regarding gcc-h8300-hms: Removal of obsolete debhelper compat 5 and 6 in bookworm to be marked as done. This means

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

Your message dated Thu, 03 Feb 2022 21:48:57 + with message-id and subject line Bug#965491: fixed in dictconv 0.2-7.1 has caused the Debian Bug report #965491, regarding dictconv: Removal of obsolete debhelper compat 5 and 6 in bookworm to be marked as done. This means that you claim that

Bug#1004847: marked as done (nvidia-graphics-drivers: CVE-2022-21813, CVE-2022-21814)

Your message dated Thu, 03 Feb 2022 21:49:49 + with message-id and subject line Bug#1004847: fixed in nvidia-graphics-drivers 470.103.01-1 has caused the Debian Bug report #1004847, regarding nvidia-graphics-drivers: CVE-2022-21813, CVE-2022-21814 to be marked as done. This means that you

Bug#1002429: marked as done (openems: FTBFS: FileNotFoundError: [Errno 2] No such file or directory: 'debian/control')

Your message dated Thu, 03 Feb 2022 21:49:55 + with message-id and subject line Bug#1002429: fixed in openems 0.0.35+git20190103.6a75e98+dfsg.1-3.1 has caused the Debian Bug report #1002429, regarding openems: FTBFS: FileNotFoundError: [Errno 2] No such file or directory: 'debian/control'

Bug#1002180: marked as done (clamfs: FTBFS: stats.cxx:73:34: error: ‘mallinfo mallinfo()’ is deprecated [-Werror=deprecated-declarations])

Your message dated Thu, 03 Feb 2022 21:48:46 + with message-id and subject line Bug#1002180: fixed in clamfs 1.2.0-2.1 has caused the Debian Bug report #1002180, regarding clamfs: FTBFS: stats.cxx:73:34: error: ‘mallinfo mallinfo()’ is deprecated [-Werror=deprecated-declarations] to be

Bug#1002167: marked as done (hmat-oss: FTBFS: memory_instrumentation.cpp:145:39: error: ‘mallinfo mallinfo()’ is deprecated [-Werror=deprecated-declarations])

Your message dated Thu, 03 Feb 2022 21:49:19 + with message-id and subject line Bug#1002167: fixed in hmat-oss 1.2.0-2.2 has caused the Debian Bug report #1002167, regarding hmat-oss: FTBFS: memory_instrumentation.cpp:145:39: error: ‘mallinfo mallinfo()’ is deprecated

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

Your message dated Thu, 03 Feb 2022 21:34:56 + with message-id and subject line Bug#965713: fixed in makedev 2.3.1-95 has caused the Debian Bug report #965713, regarding makedev: Removal of obsolete debhelper compat 5 and 6 in bookworm to be marked as done. This means that you claim that the

Bug#1000872: marked as done (parl-desktop-world depends on removed package.)

Your message dated Thu, 03 Feb 2022 21:18:42 + with message-id and subject line Bug#1000872: fixed in debian-parl 1.9.30 has caused the Debian Bug report #1000872, regarding parl-desktop-world depends on removed package. to be marked as done. This means that you claim that the problem has

Bug#1001068: samba: Missing upstream commit 0a546be0 on bullseye, bookworm and sid (part of CVE-2020-25717)

Hi Jörg, On Fri, Dec 03, 2021 at 03:44:02PM +0100, Jörg Behrmann wrote: > Package: samba > Version: 2:4.13.13+dfsg-1~deb11u2 > Severity: important > X-Debbugs-Cc: t...@security.debian.org > > The upstream samba commit 0a546be0 is included in the buster security release > 2:4.9.5+dfsg-5+deb10u2

Processed: severity of 1001068 is serious, found 1001068 in 2:4.13.14+dfsg-1

Processing commands for cont...@bugs.debian.org: > severity 1001068 serious Bug #1001068 [samba] samba: Missing upstream commit 0a546be0 on bullseye, bookworm and sid (part of CVE-2020-25717) Severity set to 'serious' from 'important' > found 1001068 2:4.13.14+dfsg-1 Bug #1001068 [samba] samba:

Processed: bug 1001068 is forwarded to https://bugzilla.samba.org/show_bug.cgi?id=14901#c9

Processing commands for cont...@bugs.debian.org: > forwarded 1001068 https://bugzilla.samba.org/show_bug.cgi?id=14901#c9 Bug #1001068 [samba] samba: Missing upstream commit 0a546be0 on bullseye, bookworm and sid (part of CVE-2020-25717) Set Bug forwarded-to-address to

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

Your message dated Thu, 03 Feb 2022 20:36:44 + with message-id and subject line Bug#999240: fixed in sc 7.16-4.1 has caused the Debian Bug report #999240, regarding sc: missing required debian/rules targets build-arch and/or build-indep to be marked as done. This means that you claim that

Bug#1004935: connman: CVE-2022-23096 CVE-2022-23097 CVE-2022-23098

Source: connman Version: 1.36-2.3 Severity: grave Tags: security upstream Forwarded: https://lore.kernel.org/connman/20220125090026.5108-1-w...@monom.org/ X-Debbugs-Cc: car...@debian.org, Debian Security Team Control: found -1 1.36-2.2 Control: found -1 1.36-2.1~deb10u1 Control: found -1

Processed: connman: CVE-2022-23096 CVE-2022-23097 CVE-2022-23098

Processing control commands: > found -1 1.36-2.2 Bug #1004935 [src:connman] connman: CVE-2022-23096 CVE-2022-23097 CVE-2022-23098 Marked as found in versions connman/1.36-2.2. > found -1 1.36-2.1~deb10u1 Bug #1004935 [src:connman] connman: CVE-2022-23096 CVE-2022-23097 CVE-2022-23098 Marked as

Bug#1004790: avifile: should this package be removed?

Hi Sebastian, I've maintained onscripter, which uses avifile to play animation in game. So it is still needed for me for that package. I think I can spend my time fixing #1004789 - forward porting to ffmpeg 5.0. Will fix #1004789 and then close this bug too on next upload. Yours, Paul

Processed: Re: Bug#1004748: guestfs-tools ftbfs with new ocaml

Processing control commands: > tags -1 + patch Bug #1004748 [src:guestfs-tools] guestfs-tools ftbfs with new ocaml Added tag(s) patch. -- 1004748: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004748 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1004748: guestfs-tools ftbfs with new ocaml

Control: tags -1 + patch On Tuesday, February 01 2022, Matthias Klose wrote: > guestfs-tools ftbfs with new ocaml > > [...] > Use the equivalent signed form: +C+D+E+F+L+M+P+S+U+V+Y+Z+X+52-3. > Hint: Enabling or disabling a warning by its mnemonic name requires a + or - > prefix. > Hint: Did you

Processed: Re: Bug#1004071 closed by Debian FTP Masters (Bug#1004075: Removed package(s) from unstable)

Processing control commands: > reopen -1 Bug #1004071 {Done: Debian FTP Masters } [google-guest-agent,python3-google-compute-engine] google-guest-agent,python3-google-compute-engine: both ship /usr/bin/google_metadata_script_runner 'reopen' may be inappropriate when a bug has been closed with

Bug#1004071: closed by Debian FTP Masters (Bug#1004075: Removed package(s) from unstable)

Control: reopen -1 Control: reassign -1 google-guest-agent 2026.00-1 With python3-google-compute-engine gone, you should add Breaks+Replaces: python3-google-compute-engine to google-guest-agent, to ensure there are no upgrade issues if python3-google-compute-engine from oldstable is

Bug#1002259: marked as done (nodejs: FTBFS: TypeError: marked is not a function)

Your message dated Thu, 3 Feb 2022 20:13:57 +0100 with message-id and subject line Re: [Pkg-javascript-devel] Bug#1002259: nodejs: FTBFS: TypeError: marked is not a function has caused the Debian Bug report #1002259, regarding nodejs: FTBFS: TypeError: marked is not a function to be marked as

Bug#1004926: libgd-graph-perl: FTBFS with libgd-perl >= 2.75

Source: libgd-graph-perl Version: 1.48-2 Severity: serious Tags: upstream ftbfs sid bookworm Justification: fails to build from source Forwarded: https://rt.cpan.org/Ticket/Display.html?id=140940 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 As noticed by ci.d.n, libgd-graph-perl has test

Bug#987353: marked as done (CVE-2020-8903 CVE-2020-8907 CVE-2020-8933)

Your message dated Thu, 03 Feb 2022 18:03:07 + with message-id and subject line Bug#1004075: Removed package(s) from unstable has caused the Debian Bug report #987353, regarding CVE-2020-8903 CVE-2020-8907 CVE-2020-8933 to be marked as done. This means that you claim that the problem has

Bug#1004071: marked as done (google-guest-agent,python3-google-compute-engine: both ship /usr/bin/google_metadata_script_runner)

Your message dated Thu, 03 Feb 2022 18:03:07 + with message-id and subject line Bug#1004075: Removed package(s) from unstable has caused the Debian Bug report #1004071, regarding google-guest-agent,python3-google-compute-engine: both ship /usr/bin/google_metadata_script_runner to be marked

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

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

Processed: [bts-link] source package src:ruby-redis, src:ruby-fakeredis

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

Bug#1004740: exim4: SIGSEGV (maybe attempt to write to immutable memory) when sending a mail; message frozen

On 2022-02-03 17:30:28 +0100, Marc Haber wrote: > Do you see this TLS error with other remotes? No, but the machine only has 11 days of logs, while I don't use it much in these times. So that's almost nothing. -- Vincent Lefèvre - Web: 100% accessible validated

Bug#1004923: autopkgtest failure due to removed libRemoteIndex*.a

Source: llvm-toolchain-12 Version: 1:12.0.1-19 Severity: serious Hi, The following commit: https://salsa.debian.org/pkg-llvm-team/llvm-toolchain/-/commit/87ee3c332f9b0736064a588bdf974bbda0288d58 is causing an autopkgtest failure because the build system still requires the libraries

Bug#1004740: exim4: SIGSEGV (maybe attempt to write to immutable memory) when sending a mail; message frozen

On Thu, Feb 03, 2022 at 02:51:10PM +0100, Vincent Lefevre wrote: > On 2022-02-03 14:21:58 +0100, Marc Haber wrote: > > Is the bug repeatable by unfreezing the message and forcing a delivery > > attempt? If so, you might be able to get a core dump from the delivering > > exim. > > The delivery was

Bug#961834: Any updates?

Hello, is reported issue still valid? I use this theme in Debian Bookworm (Xfce 4.16) and I can't see any trouble with it. I would appreciate returning the package to the repo if there is no real blocker anymore. Thank you Zbynek

Processed: your mail

Processing commands for cont...@bugs.debian.org: > forwarded 1004461 https://github.com/agronholm/anyio/issues/417 Bug #1004461 [src:python-anyio] python-anyio FTBFS on IPV6-only buildds Set Bug forwarded-to-address to 'https://github.com/agronholm/anyio/issues/417'. > thanks Stopping processing

Bug#1004902: openrct2: FTBFS TTF.cpp:358:32: error: invalid conversion from 'const TTF_Font*' to 'TTF_Font*'

tags 1004902 + pending thanks Thanks for the report! I've fixed the error locally and plan to get a new version uploaded in the near future. Mathias On Thu, 2022-02-03 at 11:13 +0100, Andreas Beckmann wrote: > Source: openrct2 > Version: 0.3.5.1+ds-2 > Severity: serious > Tags: ftbfs >

Processed: Re: Bug#1004902: openrct2: FTBFS TTF.cpp:358:32: error: invalid conversion from 'const TTF_Font*' to 'TTF_Font*'

Processing commands for cont...@bugs.debian.org: > tags 1004902 + pending Bug #1004902 [src:openrct2] openrct2: FTBFS TTF.cpp:358:32: error: invalid conversion from 'const TTF_Font*' to 'TTF_Font*' Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need

Processed: bug #1002325 forwarded upstream

Processing commands for cont...@bugs.debian.org: > forwarded 1002325 https://github.com/enthought/envisage/issues/396 Bug #1002325 [src:python-envisage] python-envisage: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.10 3.9" returned exit code 13 Set Bug forwarded-to-address

Bug#1004740: exim4: SIGSEGV (maybe attempt to write to immutable memory) when sending a mail; message frozen

On 2022-02-03 14:21:58 +0100, Marc Haber wrote: > Is the bug repeatable by unfreezing the message and forcing a delivery > attempt? If so, you might be able to get a core dump from the delivering > exim. The delivery was successful. There was still a "TLS error on connection (recv): The TLS

Processed: Bug#994866 marked as pending in gmerlin

Processing control commands: > tag -1 pending Bug #994866 [gmerlin-data,libgmerlin-dev] gmerlin-data,libgmerlin-dev: both ship /usr/share/gmerlin/plugin.sym Added tag(s) pending. -- 994866: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994866 Debian Bug Tracking System Contact

Bug#994866: marked as pending in gmerlin

Control: tag -1 pending Hello, Bug #994866 in gmerlin 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:

Bug#1003785: marked as pending in gmerlin

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

Processing control commands: > tag -1 pending Bug #1003785 [src:gmerlin] gmerlin: FTBFS: format not a string literal and no format arguments Added tag(s) pending. -- 1003785: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003785 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#1004740: exim4: SIGSEGV (maybe attempt to write to immutable memory) when sending a mail; message frozen

On Thu, Feb 03, 2022 at 03:46:22AM +0100, Vincent Lefevre wrote: > On 2022-02-03 03:29:24 +0100, Vincent Lefevre wrote: > > On 2022-02-02 18:20:48 +0100, Andreas Metzler wrote: > > > Any chance of getting a coredump? > > > > exim didn't leave a coredump. I could see that Mutt disables coredumps >

Bug#997786: marked as done (python-cymruwhois: FTBFS: There is a syntax error in your configuration file: invalid syntax (conf.py, line 176))

Your message dated Thu, 03 Feb 2022 13:19:09 + with message-id and subject line Bug#997786: fixed in python-cymruwhois 1.6-4 has caused the Debian Bug report #997786, regarding python-cymruwhois: FTBFS: There is a syntax error in your configuration file: invalid syntax (conf.py, line 176) to

Bug#1004870: python-xarray: autopkgtest regression on s390x

We are having a look. Will check and update.   Thanks, Rajendra   - Original message -From: "Graham Inggs" To: "Debian Bug Tracking System" Cc:Subject: [EXTERNAL] Bug#1004870: python-xarray: autopkgtest regression on s390xDate: Thu, Feb 3, 2022 1:06 AM  Source: python-xarrayVersion:

Bug#1004902: openrct2: FTBFS TTF.cpp:358:32: error: invalid conversion from 'const TTF_Font*' to 'TTF_Font*'

Source: openrct2 Version: 0.3.5.1+ds-2 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Hi, openrct2 recently started to FTBFS, probably due to a change in a build dependency: /build/openrct2-0.3.5.1+ds/src/openrct2/drawing/TTF.cpp: In

Bug#1004900: zim-tools: FTBFS on slow buildds

Source: zim-tools Version: 3.1.0-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=zim-tools=riscv64 https://buildd.debian.org/status/logs.php?pkg=zim-tools=mips64el ... Expected equality of these values: ... -[INFO] Total time taken by zimcheck: 0 seconds.\n +[INFO]

Bug#1004517: marked as done ([pyvo] CI failure with astropy 5.0.1; please update to version 1.2.1)

Your message dated Thu, 03 Feb 2022 08:38:58 + with message-id and subject line Bug#1004517: fixed in pyvo 1.2.1-1 has caused the Debian Bug report #1004517, regarding [pyvo] CI failure with astropy 5.0.1; please update to version 1.2.1 to be marked as done. This means that you claim that