Bug#999334: android-platform-tools: FTBFS: error: no member named 'unique_lock' in namespace 'std'

control: tags -1 +help I pushed a few patches to salsa that can resolve previously reported ftbfs issues, however there're still other ftbfs issues. For amd64, pbuilder reports: :12:24: error: expected newline .cfi_restore_state .cfi_def_cfa rsp,(144 + 16*8) ^

Processed: Re: Bug#999334: android-platform-tools: FTBFS: error: no member named 'unique_lock' in namespace 'std'

Processing control commands: > tags -1 +help Bug #999334 [src:android-platform-tools] android-platform-tools: FTBFS: error: no member named 'unique_lock' in namespace 'std' Added tag(s) help. -- 999334: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999334 Debian Bug Tracking System Contact

Bug#1004230: libgpuarray: please drop upstreamtestsclblas until bug 949767 is fixed

Source: libgpuarray Version: 0.7.6-8 Severity: serious Justification: blocks other packages from migrating Dear maintainer, The autopkgtest of libgpuarray fails with libclblas-dev and libclblas2 installed due to bug #949767. Because those binaries are not available in testing, the upstreamtests

Bug#1003907: fails to successfully associate

I will drop this patch, this does not solve the issue. 2022年1月23日(日) 10:30 Masashi Honma : > > 2022年1月19日(水) 19:13 Michael Biebl : > > I tried the various versions from snapshots.d.o > > > > 2:2.9.0-23 - works > > 2:2.9.0+git20200221+f65da0c-1 - works > > 2:2.9.0+git20200517+dd2daf0-1 - doesn't

Bug#1000717: marked as done (supysonic: FTBFS on Python 3.10)

Your message dated Sat, 22 Jan 2022 23:50:44 -0500 with message-id <69af2bb2-3f79-6a8b-67af-02c031efb...@debian.org> and subject line close supysonic FTBFS has caused the Debian Bug report #1000717, regarding supysonic: FTBFS on Python 3.10 to be marked as done. This means that you claim that the

Bug#1003003: marked as done (libqalculate FTBFS on architectures where char is unsigned)

Your message dated Sun, 23 Jan 2022 04:48:41 + with message-id and subject line Bug#1003003: fixed in libqalculate 3.22.0-3 has caused the Debian Bug report #1003003, regarding libqalculate FTBFS on architectures where char is unsigned to be marked as done. This means that you claim that the

Bug#1004223: minetest-server: ItemStack meta injection vulnerability in Minetest 5.3

Package: minetest-server Version: 5.3.0+repack-2.1 Severity: grave Tags: patch security Justification: user security hole X-Debbugs-Cc: nils+debian-report...@dieweltistgarnichtso.net, Debian Security Team Dear Maintainer, Minetest 5.3 contains a serious security issue by default. The

Bug#1003907: fails to successfully associate

2022年1月19日(水) 19:13 Michael Biebl : > I tried the various versions from snapshots.d.o > > 2:2.9.0-23 - works > 2:2.9.0+git20200221+f65da0c-1 - works > 2:2.9.0+git20200517+dd2daf0-1 - doesn't work > 2:2.9.0+git20210909+a75fdcd-1 - doesn't work > 2:2.9.0+git20211018+2e122945fa53-1 - doesn't work >

Bug#984063: marked as done (insighttoolkit4: ftbfs with GCC-11)

Your message dated Sat, 22 Jan 2022 23:04:05 + with message-id and subject line Bug#984063: fixed in insighttoolkit4 4.13.3withdata-dfsg2-1 has caused the Debian Bug report #984063, regarding insighttoolkit4: ftbfs with GCC-11 to be marked as done. This means that you claim that the problem

Processed: Re: Bug#1002527: postinst ignores USER from /etc/default/milter-greylist when invoking chown ... /var/lib/milter-greylist

Processing commands for cont...@bugs.debian.org: > retitle 1002527 milter-greylist -u user does not correctly ensure user can > update greylist.db Bug #1002527 [milter-greylist] postinst ignores USER from /etc/default/milter-greylist when invoking chown ... /var/lib/milter-greylist Changed Bug

Bug#1002527: postinst ignores USER from /etc/default/milter-greylist when invoking chown ... /var/lib/milter-greylist

retitle 1002527 milter-greylist -u user does not correctly ensure user can update greylist.db quit * Adrian Bunk [220120 21:43]: > On Thu, Dec 23, 2021 at 02:12:04PM -0500, Marvin Renich wrote: > >... > > With an existing installation of milter-greylist set up to work with > > chrooted postfix

Bug#995356: python-parameterized: autopkgtest regression: AssertionError in tearDownModule

Hi, On Thu, 30 Sep 2021 11:07:17 +0200 Paul Gevers wrote: With a recent upload of python-parameterized the autopkgtest of python-parameterized fails in testing when that autopkgtest is run with the binary packages of python-parameterized from unstable. It passes when run with only packages

Bug#1004216: missing directory: /usr/share/fonts/truetype/

Source: fonts-ipaexfont Version: 00401-3 Followup-For: Bug #1004216 Dear maintainer, I fixed the issue with the attached debdiff, which I uploaded to DELAYED/10. Please let me know if I should cancel my upload. Paul diff --git a/debian/changelog b/debian/changelog index e2d00aa..f21e606 100644

Bug#1004214: Acknowledgement (kodi: Segfaults on menu selection)

Control: severity -1 important Hi Stephen! Thanks for the bugreport! However, the "grave" severity is too high for it given I see the following issues: * Your logfile attached in the previous message pasted to Kodi hastebin ( https://paste.kodi.tv/ovifonuziy.kodi ) shows the presence of

Processed: Re: Bug#1004214: Acknowledgement (kodi: Segfaults on menu selection)

Processing control commands: > severity -1 important Bug #1004214 [kodi] kodi: Segfaults on menu selection Severity set to 'important' from 'grave' -- 1004214: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004214 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#995351: src:fonts-ipaexfont: piuparts detected issue: /usr/share/fonts/truetype/ doesn't exist

Control: clone -1 -2 Control: reopen -2 Control: retitle -2 missing directory: /usr/share/fonts/truetype/ Hi, I checked the piuparts log, and it seems to me that the alternatives methode is used in a directory that's not guaranteed to exist. I think the solution to the problem is trivial.

Processed: Re: src:fonts-ipaexfont: piuparts detected issue: /usr/share/fonts/truetype/ doesn't exist

Processing control commands: > clone -1 -2 Bug #995351 {Done: Paul Gevers } [src:fonts-ipaexfont] src:fonts-ipaexfont: fails to migrate to testing for too long: piuparts regression Bug 995351 cloned as bug 1004216 > reopen -2 Bug #1004216 {Done: Paul Gevers } [src:fonts-ipaexfont]

Bug#997845: marked as done (growlight: autopkgtest regression: log repeats until it times out)

Your message dated Sat, 22 Jan 2022 21:52:05 +0100 with message-id and subject line Re: Bug#997845: bug 997845 has caused the Debian Bug report #997845, regarding growlight: autopkgtest regression: log repeats until it times out to be marked as done. This means that you claim that the problem

Bug#1004214: Acknowledgement (kodi: Segfaults on menu selection)

Output from starting in terminal: failed to open zone.tab libva info: VA-API version 1.13.0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/r600_drv_video.so libva info: Found init function __vaDriverInit_1_13 libva info: va_openDriver() returns 0 Segmentation fault Attaching Kodi's own

Processed: update bts with meta info

Processing commands for cont...@bugs.debian.org: > reassign 1004094 src:python-imageio 2.4.1-3 Bug #1004094 {Done: Graham Inggs } [src:pillow, src:python-imageio] pillow breaks python-imageio autopkgtest: assert (150, 200, 3) == (150, 200, 4) Bug reassigned from package 'src:pillow,

Bug#1004214: kodi: Segfaults on menu selection

Package: kodi Version: 2:19.3+dfsg1-1+b1 Severity: grave Justification: renders package unusable X-Debbugs-Cc: marathon.duran...@gmail.com Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Start up Kodi and select

Processed: Re: Bug#1004204: libqt5webenginecore5: Fails to upgrade to Sid version

Processing control commands: > severity -1 important Bug #1004204 [libqt5webenginecore5] libqt5webenginecore5: Fails to upgrade to Sid version Severity set to 'important' from 'critical' -- 1004204: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004204 Debian Bug Tracking System Contact

Bug#1004204: libqt5webenginecore5: Fails to upgrade to Sid version

Control: severity -1 important On Saturday, 22 January 2022 19:02:27 CET Elijah wrote: > pkg-deb (subprocess): decompressing archive > '/var/cache/apt/archives/libqt5webenginecore5_5.15.8+dfsg-1_amd64.deb' > (size=39497412) member 'data.tar': lzma error: compressed data is corrupt What happens

Bug#1004212: berkeley-abc: autopkgtest regression on arm64, i386 and ppc64el: Segmentation fault

Source: berkeley-abc Version: 1.01+20211229git48498af+dfsg-1 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of berkeley-abc the autopkgtest of berkeley-abc fails in testing when that

Bug#1004211: dirty.js: autopkgtest failure on armhf and ppc64el

Source: dirty.js Version: 1.1.3-1 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: fails-always Dear maintainer(s), You recently added an autopkgtest to your package dirty.js, great. However, it fails on armhf and ppc64el. Currently this

Processed: src:datalad: fails to migrate to testing for too long: FTBFS

Processing control commands: > close -1 0.15.3-1 Bug #1004210 [src:datalad] src:datalad: fails to migrate to testing for too long: FTBFS The source 'datalad' and version '0.15.3-1' do not appear to match any binary packages Marked as fixed in versions datalad/0.15.3-1. Bug #1004210

Bug#1004210: src:datalad: fails to migrate to testing for too long: FTBFS

Source: datalad Version: 0.15.0-2 Severity: serious Control: close -1 0.15.3-1 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1002359 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and

Bug#996375: marked as done (chromium build-depends on removed package.)

Your message dated Sat, 22 Jan 2022 19:17:18 + with message-id and subject line Bug#996375: fixed in chromium 97.0.4692.71-0.1~deb11u1 has caused the Debian Bug report #996375, regarding chromium build-depends on removed package. to be marked as done. This means that you claim that the

Bug#995212: marked as done (chromium: Update to version 94.0.4606.61 (security-fixes))

Your message dated Sat, 22 Jan 2022 19:17:17 + with message-id and subject line Bug#995212: fixed in chromium 97.0.4692.71-0.1~deb11u1 has caused the Debian Bug report #995212, regarding chromium: Update to version 94.0.4606.61 (security-fixes) to be marked as done. This means that you claim

Bug#1003243: marked as done (wordpress: WordPress 5.8.3 Security Release)

Your message dated Sat, 22 Jan 2022 19:18:06 + with message-id and subject line Bug#1003243: fixed in wordpress 5.7.5+dfsg1-0+deb11u1 has caused the Debian Bug report #1003243, regarding wordpress: WordPress 5.8.3 Security Release to be marked as done. This means that you claim that the

Bug#984063: [Debian-med-packaging] Bug#984063: Closing bug (Was: Bug#984063: itk libtiff test issues (Was: Bug#984063))

Thanks a lot! Am Sat, Jan 22, 2022 at 07:15:25PM +0100 schrieb Étienne Mollier: > Hi Andreas, > > Andreas Tille, on 2022-01-16: > > I think the roadmap that ITK4 will be deleted as soon as possible > > is clear. However, if it might serve as an intermediate means > > to support some remaining

Bug#997829: marked as done (libipc-shareable-perl: autopkgtest regression on armhf and i386)

Your message dated Sat, 22 Jan 2022 18:19:07 + with message-id and subject line Bug#997829: fixed in libipc-shareable-perl 1.06-2 has caused the Debian Bug report #997829, regarding libipc-shareable-perl: autopkgtest regression on armhf and i386 to be marked as done. This means that you

Bug#997829: marked as pending in libipc-shareable-perl

Control: tag -1 pending Hello, Bug #997829 in libipc-shareable-perl 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#997829 marked as pending in libipc-shareable-perl

Processing control commands: > tag -1 pending Bug #997829 [src:libipc-shareable-perl] libipc-shareable-perl: autopkgtest regression on armhf and i386 Added tag(s) pending. -- 997829: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997829 Debian Bug Tracking System Contact

Bug#1000896: Bug#997829: libipc-shareable-perl: autopkgtest regression on armhf and i386

On Sat, 22 Jan 2022 18:57:30 +0200, Niko Tyni wrote: > Given % 2^32 == 3567587327 it's pretty clear that the > requested size does not fit into 32 bits (shmget(2) takes a size_t) > so just its lower bits get passed in. Not sure if perl should protest > somehow there. Thanks for the

Bug#997829: Bug#1000896: Bug#997829: libipc-shareable-perl: autopkgtest regression on armhf and i386

On Sat, Jan 15, 2022 at 11:20:51PM +0100, gregor herrmann wrote: > On Mon, 25 Oct 2021 19:59:39 +0200, gregor herrmann wrote: > No reaction so far at https://github.com/stevieb9/ipc-shareable/issues/14 > > Failures are visible at > https://qa.debian.org/excuses.php?package=libipc-shareable-perl

Bug#1002390: marked as done (python3-babeltrace does not work with Python 3.10)

Your message dated Sat, 22 Jan 2022 16:33:42 + with message-id and subject line Bug#1002390: fixed in babeltrace 1.5.8-2 has caused the Debian Bug report #1002390, regarding python3-babeltrace does not work with Python 3.10 to be marked as done. This means that you claim that the problem has

Bug#1004156: src:adapt: fails to migrate to testing for too long: FTBFS

Hi Paul, On Fri, Jan 21, 2022 at 10:22:43PM +0100, Paul Gevers wrote: > If you believe your package is unable to migrate to testing due to issues > beyond your control, don't hesitate to contact the Release Team. No, that's not it; I've just not been able to look at the problem, due to being too

Bug#1004194: loguru: CVE-2022-0329

Source: loguru Version: 0.5.3-4 Severity: grave Tags: security upstream Justification: user security hole Forwarded: https://github.com/Delgan/loguru/issues/563 X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for loguru. CVE-2022-0329[0]: |

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

Your message dated Sat, 22 Jan 2022 15:18:39 + with message-id and subject line Bug#998937: fixed in aspell-cs 0.51.0-1.3 has caused the Debian Bug report #998937, regarding aspell-cs: missing required debian/rules targets build-arch and/or build-indep to be marked as done. This means that

Bug#1003165: scikit-learn in unstable FTBFS on arm64, armel, armhf, i386, ppc64el and s390x

Source: scikit-learn Followup-For: Bug #1003165 Hi, I have uploaded the attached debdiff as NMU to DELAYED/2. Please let me know if I should cancel the upload. Paul diff --git a/debian/changelog b/debian/changelog index 7816bd5..2cf4db0 100644 --- a/debian/changelog +++ b/debian/changelog @@

Processed: debianutils: tries to overwrite /usr/share/man/fr/man1/readlink.1.gz, also in manpages-fr

Processing commands for cont...@bugs.debian.org: > notfound 1004167 5.5-1 Bug #1004167 [debianutils] debianutils: tries to overwrite /usr/share/man/fr/man1/readlink.1.gz, also in manpages-fr No longer marked as found in versions debianutils/5.5-1. > found 1004167 5.6-0.1 Bug #1004167

Bug#1003964: marked as done (cmark-gfm: shlibs too relaxed for unstable ABI)

Your message dated Sat, 22 Jan 2022 13:00:10 + with message-id and subject line Bug#1003964: fixed in cmark-gfm 0.29.0.gfm.2-2 has caused the Debian Bug report #1003964, regarding cmark-gfm: shlibs too relaxed for unstable ABI to be marked as done. This means that you claim that the problem

Processed: clone 1001168

Processing commands for cont...@bugs.debian.org: > clone 1001168 -1 Bug #1001168 [src:hkl] hkl: FTBFS on mipsel: FAIL: trajectory.py Bug 1001168 cloned as bug 1004184 1004184 was blocked by: 1000774 1000435 1004184 was not blocking any bugs. Ignoring request to alter blocking bugs of bug #1004184

Bug#1000435: Matplotlib crashes on mips64el in lines.py

On Sat, 22 Jan 2022 17:06:00 +0800 YunQiang Su wrote:> On Tue, 23 Nov 2021 08:08:23 +0100 Ole Streicher wrote:> > Source: matplotlib> > Severity: serious> > Version: 3.5.0-1> > Control: affects -1 yt> > Control: affects -1 astropy> >> > With the new

Bug#1004181: wolfssl: CVE-2022-23408

Source: wolfssl Version: 5.0.0-1 Severity: grave Tags: security upstream Justification: user security hole Forwarded: https://github.com/wolfSSL/wolfssl/pull/4710 X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for wolfssl. CVE-2022-23408[0]:

Processed: Re: debianutils: tries to overwrite /usr/share/man/fr/man1/readlink.1.gz, also in manpages-fr

Processing control commands: > tag -1 + patch Bug #1004167 [debianutils] debianutils: tries to overwrite /usr/share/man/fr/man1/readlink.1.gz, also in manpages-fr Added tag(s) patch. -- 1004167: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004167 Debian Bug Tracking System Contact

Bug#1004167: debianutils: tries to overwrite /usr/share/man/fr/man1/readlink.1.gz, also in manpages-fr

Control: tag -1 + patch On Sat, 22 Jan 2022 04:08:18 +0100 Vincent Lefevre wrote: > I get the following error when I want to upgrade: > > Unpacking debianutils (5.6-0.1) over (5.5-1) ... > dpkg: error processing archive > /var/cache/apt/archives/debianutils_5.6-0.1_amd64.deb (--unpack): >

Processed: nodejs: CVE-2021-44531 CVE-2021-44532 CVE-2021-44533 CVE-2022-21824

Processing control commands: > found -1 12.22.5~dfsg-2~11u1 Bug #1004177 [src:nodejs] nodejs: CVE-2021-44531 CVE-2021-44532 CVE-2021-44533 CVE-2022-21824 Marked as found in versions nodejs/12.22.5~dfsg-2~11u1. -- 1004177: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004177 Debian Bug

Bug#1004177: nodejs: CVE-2021-44531 CVE-2021-44532 CVE-2021-44533 CVE-2022-21824

Source: nodejs Version: 12.22.7~dfsg-2 Severity: grave Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Control: found -1 12.22.5~dfsg-2~11u1 Hi, The following vulnerabilities were published for nodejs. CVE-2021-44531[0]: | Improper handling of URI Subject

Bug#1001168: [Debian-pan-maintainers] Bug#1001168: hkl: FTBFS on mipsel: FAIL: trajectory.py

PICCA Frederic-Emmanuel 于2022年1月22日周六 17:28写道： > > Is it not better to use the > > DEB__MAINT_APPEND > > variable in order to deal with this issue ? Thanks, you are right. the patch looks better now. -- YunQiang Su matplotlib-mips64el-o3.diff Description: Binary data

Bug#1001168: [Debian-pan-maintainers] Bug#1001168: hkl: FTBFS on mipsel: FAIL: trajectory.py

Is it not better to use the DEB__MAINT_APPEND variable in order to deal with this issue ?

Bug#1004103: calcurse FTBFS on big endian

Hi Adrian, Thanks for reporting this. I will check this and revert back. From: "Adrian Bunk" To: "Debian Bug Tracking System" Date: 21/01/2022 03:00 AM Subject:[EXTERNAL] Bug#1004103: calcurse FTBFS on big endian Source: calcurse Version: 4.7.1-1 Severity: serious Tags:

Bug#1001168: hkl: FTBFS on mipsel: FAIL: trajectory.py

Graham Inggs 于2022年1月22日周六 16:48写道： > > On Sat, 22 Jan 2022 at 10:45, YunQiang Su wrote: > > Sure. I will. > > Thank you! Patch sent: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000435 -- YunQiang Su

Bug#1000435: Matplotlib crashes on mips64el in lines.py

On Tue, 23 Nov 2021 08:08:23 +0100 Ole Streicher wrote: > Source: matplotlib > Severity: serious > Version: 3.5.0-1 > Control: affects -1 yt > Control: affects -1 astropy > > With the new matplotlib version, I now have crashes with a segmentation fault > in at least two of my packages on

Bug#1001168: hkl: FTBFS on mipsel: FAIL: trajectory.py

On Sat, 22 Jan 2022 at 10:45, YunQiang Su wrote: > Sure. I will. Thank you!

Bug#1001168: hkl: FTBFS on mipsel: FAIL: trajectory.py

Graham Inggs 于2022年1月22日周六 16:42写道： > > On Sat, 22 Jan 2022 at 10:12, YunQiang Su wrote: > > Let's have a try to build matplotlib with -O3, and try to build hkl with it. > > If it works, we can workaround it for now. > > I will continue to dig the real problem of gcc (maybe). > > To be clear,

Bug#1001168: hkl: FTBFS on mipsel: FAIL: trajectory.py

On Sat, 22 Jan 2022 at 10:12, YunQiang Su wrote: > Let's have a try to build matplotlib with -O3, and try to build hkl with it. > If it works, we can workaround it for now. > I will continue to dig the real problem of gcc (maybe). To be clear, will you try building matplotlib with -O3 and if it

Bug#1001168: hkl: FTBFS on mipsel: FAIL: trajectory.py

Graham Inggs 于2022年1月22日周六 15:42写道： > > Hi YunQiang Su > > Have you been able to make any progress with this issue? > > If not, then we should consider asking ftp-master for temporary > removal of the affected mips64el packages from testing. We'd like to > move the python3-defaults transition