Processed: r-bioc-delayedarray: tests fail on Debian unstable & testing

Processing commands for cont...@bugs.debian.org: > reassign 979555 src:r-bioc-delayedarray Bug #979555 [r-bioc-delayedarray] r-bioc-delayedarray: tests fail on Debian unstable & testing Bug reassigned from package 'r-bioc-delayedarray' to 'src:r-bioc-delayedarray'. No longer marked as found in ve

Processed: numba ftbfs in unstable with python3.9 as supported python3 version

Processing commands for cont...@bugs.debian.org: > severity 972246 serious Bug #972246 [src:numba] numba ftbfs in unstable with python3.9 as supported python3 version Severity set to 'serious' from 'important' > tags 972246 + fixed-upstream Bug #972246 [src:numba] numba ftbfs in unstable with pyt

Processed: severity of 979439 is grave

Processing commands for cont...@bugs.debian.org: > severity 979439 grave Bug #979439 [hunspell-it] hunspell-it: Italian spell check cannot recognize simple words Severity set to 'grave' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 979439: https:/

Bug#980071: gnome-shell: Using suspend in the gnome-shell power off/log out menu does log out and suspend in the wrong order

Package: gnome-shell Version: 3.38.2-1 Severity: grave Tags: security Justification: user security hole X-Debbugs-Cc: ago_debian...@protonmail.com, Debian Security Team When I use the suspend option in the power off/log out menu, gnome-shell first logs me off, as if I clicked log off instead. T

Bug#980035: [Aptitude-devel] Bug#980035: aptitude: segmentation fault when starting aptitude

On 2021-01-14 02:14:29 +0100, Axel Beckert wrote: > Since Julian has uploaded a fix as apt/2.1.18, would you mind checking > if you can still reproduce the issue in any way? I couldn't manage to reproduce it with apt 2.1.18. -- Vincent Lefèvre - Web: 100% accessible va

Processed: tagging 975160

Processing commands for cont...@bugs.debian.org: > tags 975160 + pending Bug #975160 [src:librecad] librecad: FTBFS: lib/engine/lc_splinepoints.cpp:1564:23: error: invalid use of incomplete type ‘class QPainterPath’ Added tag(s) pending. > thanks Stopping processing here. Please contact me if y

Bug#975166: marked as done (connectome-workbench: FTBFS: qwt_painter_command.h:85:22: error: field ‘clipPath’ has incomplete type ‘QPainterPath’)

Your message dated Thu, 14 Jan 2021 01:18:26 + with message-id and subject line Bug#975166: fixed in connectome-workbench 1.4.2-2 has caused the Debian Bug report #975166, regarding connectome-workbench: FTBFS: qwt_painter_command.h:85:22: error: field ‘clipPath’ has incomplete type ‘QPainter

Processed: Re: [Aptitude-devel] Bug#980035: aptitude: segmentation fault when starting aptitude

Processing control commands: > clone -1 -2 Bug #980035 [aptitude] aptitude: segmentation fault when starting aptitude Bug 980035 cloned as bug 980075 > retitle -2 aptitude-run-state-bundle: uses some local files instead of only > those from the bundle Bug #980075 [aptitude] aptitude: segmentation

Bug#980035: [Aptitude-devel] Bug#980035: aptitude: segmentation fault when starting aptitude

Control: clone -1 -2 Control: retitle -2 aptitude-run-state-bundle: uses some local files instead of only those from the bundle Control: tag -2 - security Control: tag -1 + moreinfo Control: severity -2 normal Hi Vincent, Vincent Lefevre wrote: > With the bundle, the crash occurs while the UI is

Bug#966172: marked as done (pgplot5: FTBFS with GCC 10: Error: Type mismatch in argument 'pixmap' at (1); passed INTEGER(8) to INTEGER(1))

Your message dated Thu, 14 Jan 2021 01:03:53 + with message-id and subject line Bug#966172: fixed in pgplot5 5.2.2-19.4 has caused the Debian Bug report #966172, regarding pgplot5: FTBFS with GCC 10: Error: Type mismatch in argument 'pixmap' at (1); passed INTEGER(8) to INTEGER(1) to be marke

Bug#980030: marked as done (vim-gtk3: gvim Could not load pixbuf defaults to vim with no gui)

Your message dated Wed, 13 Jan 2021 19:15:49 -0500 with message-id <20210114001549.5hrqfefuldi3p4x5@localhost> and subject line Re: Bug#980030: vim-gtk3: gvim Could not load pixbuf defaults to vim with no gui has caused the Debian Bug report #980030, regarding vim-gtk3: gvim Could not load pixbuf

Bug#975166: connectome-workbench: FTBFS: qwt_painter_command.h:85:22: error: field ‘clipPath’ has incomplete type ‘QPainterPath

Dear Maintainer, I tried to build your package in a sid chroot environment and I confirm that patch fixes this issue. Kind Regards

Processed: Re: djangorestframework FTBFS with pytest 6

Processing control commands: > tag -1 moreinfo Bug #977061 [src:djangorestframework] djangorestframework FTBFS with pytest 6 Added tag(s) moreinfo. > severity -1 important Bug #977061 [src:djangorestframework] djangorestframework FTBFS with pytest 6 Severity set to 'important' from 'serious' --

Bug#977061: djangorestframework FTBFS with pytest 6

Control: tag -1 moreinfo Control: severity -1 important Hey Christian, On Thu, 10 Dec 2020 19:40:08 +0100 Christian Kastner wrote: djangorestframework FTBFS with pytest 6 in experimental. I'm unable to reproduce the bug with pytest 6.0.2-2 from unstable. Also, according to ci.debian.net, th

Bug#975166: connectome-workbench: FTBFS: qwt_painter_command.h:85:22: error: field ‘clipPath’ has incomplete type ‘QPainterPath

Great, thanks for the info and the buzz -- missed this, will try now and upload if all good. Cheers, On Wed, 13 Jan 2021, s3v wrote: > Dear Maintainer, > I tried to build your package in a sid chroot environment > and I confirm that patch fixes this issue. > Kind Regards -- Yaroslav O. Halc

Processed: severity of 980038 is serious

Processing commands for cont...@bugs.debian.org: > severity 980038 serious Bug #980038 [kodi-pvr-hts] kodi-pvr-hts causing Kodi to segfault Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 980038: https://bugs.debian.org/c

Bug#975672: Bug#979245: RFS: xylib/1.6-0.1 [RC] [NMU] -- Library for reading x-y data from several file formats

On 1/11/21 3:45 AM, Stuart Prescott wrote: >> In any case, I've changed my upload to a QA upload now and reuploaded >> it to Salsa and Mentors. > > I see bartm beat me to uploading it. Are you sure? I didn't receive any emails about an upload, and the tracker doesn't say anything about a recent u

Bug#980007: tcmu: VE-2021-3139

Control: retitle -1 tcmu: VE-2021-3139 On Tue, Jan 12, 2021 at 09:15:30PM +0100, Salvatore Bonaccorso wrote: > Source: tcmu > Version: 1.5.2-5 > Severity: grave > Tags: security upstream > Justification: user security hole > X-Debbugs-Cc: car...@debian.org, Debian Security Team > > > Hi, > > T

Processed: Re: Bug#980007: tcmu: VE-2021-3139

Processing control commands: > retitle -1 tcmu: VE-2021-3139 Bug #980007 [src:tcmu] tcmu: CVE-2020-28374 Changed Bug title to 'tcmu: VE-2021-3139' from 'tcmu: CVE-2020-28374'. -- 980007: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980007 Debian Bug Tracking System Contact ow...@bugs.debian

Processed: closing 904576

Processing commands for cont...@bugs.debian.org: > close 904576 Bug #904576 [python3-hug] python3-hug: fails to install with Python 3.7 Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 904576: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904

Bug#951923: marked as done (gdebi: FTBFS: test failures)

Your message dated Wed, 13 Jan 2021 19:18:44 + with message-id and subject line Bug#951923: fixed in gdebi 0.9.5.7+nmu4 has caused the Debian Bug report #951923, regarding gdebi: FTBFS: test failures to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#977132: python-pygal FTBFS with pytest 6

Dear Maintainer, after applying this patch [1], I was able to build your package in my sid chroot environment. Kind Regards. [1] https://github.com/Kozea/pygal/commit/19e539

Bug#980061: caribou: Segfault as regression of xorg CVE-2020-25712 fix that cause security issue for cinnamon

Source: caribou Version: 0.4.21-7 Severity: grave Tags: patch security upstream Forwarded: https://gitlab.gnome.org/GNOME/caribou/-/merge_requests/3 Hi, after xorg CVE-2020-25712 fix a regression is intruduced that make possible crash caribou and add a security issue for cinnamon that use it as vi

Bug#963838: marked as done (datapacker: FTBFS: Missing required argument --size)

Your message dated Wed, 13 Jan 2021 17:34:44 + with message-id and subject line Bug#963838: fixed in datapacker 1.0.3 has caused the Debian Bug report #963838, regarding datapacker: FTBFS: Missing required argument --size to be marked as done. This means that you claim that the problem has be

Processed: Re: racon: FTBFS: fatal error: bioparser/bioparser.hpp: No such file or directory

Processing control commands: > tags -1 help Bug #979727 [src:racon] racon: FTBFS: fatal error: bioparser/bioparser.hpp: No such file or directory Added tag(s) help. > tags -1 - pending Bug #979727 [src:racon] racon: FTBFS: fatal error: bioparser/bioparser.hpp: No such file or directory Removed t

Bug#979562: lightdm session termination does not stop xscreensaver

Hallo, * Jamie Zawinski [Mon, Jan 11 2021, 01:13:10PM]: > > my .icewm/startup file at the moment contains: > > > > xscreensaver -nosplash -log wtf-xscreensaver.txt & > > > > When icewm starts, I see the splash screen for a brief moment (not joking, > > looks -nosplash has no effect there), but it

Bug#979727: racon: FTBFS: fatal error: bioparser/bioparser.hpp: No such file or directory

Control: tags -1 help Control: tags -1 - pending Hi, there is a remaining build time test issue which I reported upstream: https://github.com/lbcb-sci/racon/issues/50 I have no idea how to fix this since gdb does not really give a good hint about the SIGSEGV that occures. Kind regards

Bug#971296: rekall: Switch to python3-pycryptodome

* Sascha Steinbiss: > Just bringing this up again... I would be in favour of removing it > completely. Would be happy to file a RM from unstable if there are no > objections. I agree and have filed the RM bug. Cheers, -Hilko

Bug#933928: macsyfinder: Upstream released Python3 version but "error: 'setuptools' is not supported. Please use 'pip' instead."

Control: tags -1 - upstream Hi, upstream has released a Python3 version of macsyfinder which I pushed to Git[1]. When trying to build I get a strange error: dh_auto_install -O--buildsystem=pybuild I: pybuild base:232: /usr/bin/python3 setup.py install --root '/build/macsyfinder-2.0~rc1/debi

Processed: macsyfinder: Upstream released Python3 version but "error: 'setuptools' is not supported. Please use 'pip' instead."

Processing control commands: > tags -1 - upstream Bug #936977 [src:macsyfinder] macsyfinder: Python2 removal in sid/bullseye Removed tag(s) upstream. -- 936977: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936977 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: macsyfinder: Upstream released Python3 version but "error: 'setuptools' is not supported. Please use 'pip' instead."

Processing control commands: > tags -1 - upstream Bug #933928 [src:macsyfinder] macsyfinder: Port to Python3 needed Removed tag(s) upstream. -- 933928: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933928 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: Re: ABI breakage from 1.4.1 to 1.4.2

Processing control commands: > tag -1 patch Bug #971754 [src:srt] ABI breakage from 1.4.1 to 1.4.2 Added tag(s) patch. -- 971754: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971754 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#971754: ABI breakage from 1.4.1 to 1.4.2

Control: tag -1 patch Hi, On Thu, 7 Jan 2021 20:52:39 +0100 Paul Gevers wrote: > On Tue, 06 Oct 2020 16:38:49 +0300 =?utf-8?q?Sebastian_Dr=C3=B6ge?= > wrote: > > 1.4.2 broke ABI by adding some fields to the CBytePerfMon structure. > > See https://github.com/Haivision/srt/issues/1592 for details

Bug#973433: linux-image-5.9.0-1-amd64: kernel dies with: kernel: BUG: NULL pointer dereference

Source: linux Source-Version: 5.9.11-1 Hi Simon, On Fri, Oct 30, 2020 at 11:09:40AM +0100, Simon Kainz wrote: > Package: src:linux > Version: 5.9.1-1 > Severity: critical > Justification: breaks the whole system > > Dear Maintainer, > > Please see the attached crash dump. This machine is a SLU

Bug#979817: marked as done (lld: missing Breaks+Replaces: llvm (= 1:11.0-51+nmu1))

Your message dated Wed, 13 Jan 2021 15:34:43 + with message-id and subject line Bug#979817: fixed in llvm-defaults 0.51+nmu3 has caused the Debian Bug report #979817, regarding lld: missing Breaks+Replaces: llvm (= 1:11.0-51+nmu1) to be marked as done. This means that you claim that the probl

Bug#979443: marked as done (chromium: desktop GUI locks up as Xorg process goes to 100%)

Your message dated Wed, 13 Jan 2021 16:17:47 +0100 with message-id <20210113151747.2nrr6gnduszq3bp2@bogus> and subject line Bug#979443: fixed in chromium 87.0.4280.141-0.1 has caused the Debian Bug report #979443, regarding chromium: desktop GUI locks up as Xorg process goes to 100% to be marked as

Processed: tagging 979443

Processing commands for cont...@bugs.debian.org: > tags 979443 + pending Bug #979443 [chromium] chromium: desktop GUI locks up as Xorg process goes to 100% Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 979443: https://bugs.debian.org/cgi-b

Processed: Re: Bug#979834: chromiums shows … nothing but errors on the console

Processing control commands: > tag -1 + moreinfo unreproducible Bug #979834 [chromium] chromiums shows … nothing but errors on the console Added tag(s) unreproducible and moreinfo. > severity -1 important Bug #979834 [chromium] chromiums shows … nothing but errors on the console Severity set to 'i

Bug#979834: chromiums shows … nothing but errors on the console

Control: tag -1 + moreinfo unreproducible Control: severity -1 important Hi Gregor, Chiming in, even though I'm not a chromium maintainer, as I just pulled in the new version from sid and cannot reproduce the issue, under either Wayland/sway or X11 (in both case on my x230 laptop (Intel Ivy Bridg

Bug#980054: marked as done (jquery-goodies_12-2_all.changes REJECTED)

Your message dated Wed, 13 Jan 2021 15:04:00 + with message-id and subject line Bug#980054: fixed in jquery-goodies 12-3 has caused the Debian Bug report #980054, regarding jquery-goodies_12-2_all.changes REJECTED to be marked as done. This means that you claim that the problem has been dealt

Bug#980035: [Aptitude-devel] Bug#980035: Bug#980035: aptitude: segmentation fault when starting aptitude

On 2021-01-13 15:07:26 +0100, Axel Beckert wrote: > Vincent: Got the bundle, thanks! Wasn't able to provoke a segfault > with it, even not after pressing "u". With the bundle, the crash occurs while the UI isn't displayed yet. But I can see in particular: 2300077 stat("/var/lib/dpkg/status", {st_

Bug#980054: marked as pending in jquery-goodies

Control: tag -1 pending Hello, Bug #980054 in jquery-goodies 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/js-team/jquery-goodies/-/commit/8cd4da337babeb34eb8

Processed: Bug#980054 marked as pending in jquery-goodies

Processing control commands: > tag -1 pending Bug #980054 [src:jquery-goodies] jquery-goodies_12-2_all.changes REJECTED Added tag(s) pending. -- 980054: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980054 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: reopening 979866, notfixed 979866 in knxd/0.14.41-5

Processing commands for cont...@bugs.debian.org: > reopen 979866 Bug #979866 {Done: Matthias Urlichs } [src:knxd] knxd FTBFS everywhere: autoconf issues 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may need to re-add them. Bu

Bug#978220: Bug#964198: hylafax: diff for NMU version 3:6.0.7-3.1

Hello Bastien, thank you very much for your NMU. Bye, Giuseppe

Bug#980035: [Aptitude-devel] Bug#980035: Bug#980035: aptitude: segmentation fault when starting aptitude

Hi, Vincent Lefevre wrote: > Hmm... I think that you should forget that test. I thought > that aptitude-run-state-bundle would only depend on files from > aptitude-segv.bundle, but it still reads some other files from > /var/lib according to strace. And now I get > > --- Upgradable Packages (65)

Bug#980035: aptitude: segmentation fault when starting aptitude

On 2021-01-13 12:04:57 +0100, Vincent Lefevre wrote: > On 2021-01-13 11:24:33 +0100, Vincent Lefevre wrote: > > A bundle is available for a limited time: > > > > https://www.vinc17.net/aptitude-segv.bundle > > > > I can reproduce the crash (but not always) with > > > > aptitude-run-state-bun

Processed: tagging 979942, tagging 980023, tagging 979747

Processing commands for cont...@bugs.debian.org: > tags 979942 + sid bullseye Bug #979942 {Done: Bastien Roucariès } [node-browser-pack] node-browser-pack: node-uglify is deprecated in favor of uglifyjs Added tag(s) bullseye and sid. > tags 980023 + sid bullseye Bug #980023 [src:petri-foo] petri-

Bug#980054: jquery-goodies_12-2_all.changes REJECTED

Source: jquery-goodies Version: 12-2 Severity: serious - Message transféré de Debian FTP Masters - From: Debian FTP Masters To: all Build Daemon Date: Wed, 13 Jan 2021 14:24:56 + Subject: jquery-goodies_12-2_all.changes REJECTED Message-Id: Version check failed: Your upload in

Bug#980035: [Aptitude-devel] Bug#980035: aptitude: segmentation fault when starting aptitude

On 2021-01-13 14:46:21 +0100, Vincent Lefevre wrote: > On 2021-01-13 12:31:05 +0100, Julian Andres Klode wrote: > > Smells like 980037? Bug in APT's cache building upon mremap() in new > > code path in 2.1.16/17. > > Yes, I first rebuilt apt, and > > aptitude-run-state-bundle aptitude-segv.bund

Processed (with 1 error): Re: [Aptitude-devel] Bug#980035: Bug#980035: aptitude: segmentation fault when starting aptitude

Processing control commands: > clone -1 -2 Bug #980035 [aptitude] aptitude: segmentation fault when starting aptitude Bug 980035 cloned as bug 980053 > retile -2 aptitude-create-state-bundle should include more files from > file:/// URLs Unknown command or malformed arguments to command. > sever

Bug#980035: [Aptitude-devel] Bug#980035: Bug#980035: aptitude: segmentation fault when starting aptitude

Control: clone -1 -2 Control: retile -2 aptitude-create-state-bundle should include more files from file:/// URLs Control: severity -2 minor Control: submitter -2 Axel Beckert Control: tag -2 - security Hi Julian and Vincent, Julian Andres Klode wrote: > > I got a first "segmentation fault" jus

Bug#979629: marked as done (src:topgit: invalid maintainer address)

Your message dated Wed, 13 Jan 2021 13:49:54 + with message-id and subject line Bug#979629: fixed in topgit 0.8-2 has caused the Debian Bug report #979629, regarding src:topgit: invalid maintainer address to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#980035: [Aptitude-devel] Bug#980035: aptitude: segmentation fault when starting aptitude

On 2021-01-13 12:31:05 +0100, Julian Andres Klode wrote: > Smells like 980037? Bug in APT's cache building upon mremap() in new > code path in 2.1.16/17. Yes, I first rebuilt apt, and aptitude-run-state-bundle aptitude-segv.bundle was still crashing, then applied the patch suggested at http

Processed: bug 920339 is forwarded to https://github.com/matrix-org/synapse/issues/9099

Processing commands for cont...@bugs.debian.org: > forwarded 920339 https://github.com/matrix-org/synapse/issues/9099 Bug #920339 {Done: Andrej Shadura } [matrix-synapse] matrix-synapse: installation process hangs under sysvinit due to matrix-synapse daemon not closing file descriptor from debco

Processed: limit source to hylafax, tagging 964198, tagging 978220

Processing commands for cont...@bugs.debian.org: > limit source hylafax Limiting to bugs with field 'source' containing at least one of 'hylafax' Limit currently set to 'source':'hylafax' > tags 964198 + pending Bug #964198 [src:hylafax] CVE-2020-15397 CVE-2020-15396 Ignoring request to alter tag

Bug#978220: hylafax: diff for NMU version 3:6.0.7-3.1

Control: tags 964198 + patch Control: tags 964198 + pending Control: tags 978220 + patch Control: tags 978220 + pending Dear maintainer, I've prepared an NMU for hylafax (versioned as 3:6.0.7-3.1) and uploaded it to DELAYED/7. Please feel free to tell me if I should delay it longer. Regards. d

Processed: hylafax: diff for NMU version 3:6.0.7-3.1

Processing control commands: > tags 964198 + patch Bug #964198 [src:hylafax] CVE-2020-15397 CVE-2020-15396 Added tag(s) patch. > tags 964198 + pending Bug #964198 [src:hylafax] CVE-2020-15397 CVE-2020-15396 Added tag(s) pending. > tags 978220 + patch Bug #978220 [src:hylafax] hylafax: FTBFS: Incom

Processed: hylafax: diff for NMU version 3:6.0.7-3.1

Processing control commands: > tags 964198 + patch Bug #964198 [src:hylafax] CVE-2020-15397 CVE-2020-15396 Ignoring request to alter tags of bug #964198 to the same tags previously set > tags 964198 + pending Bug #964198 [src:hylafax] CVE-2020-15397 CVE-2020-15396 Ignoring request to alter tags of

Bug#920339: Bug#935654: matrix-synapse: /etc/init.d/matrix-synapse stop doesn't work

Hi, On Mon, 11 Jan 2021, at 23:24, de...@sumpfralle.de wrote: > Hello, > > > On Sun, 10 Jan 2021 17:34:57 +0100 wrote: > > > * Forcing start-stop-daemon to create the PID file. > > Synapse seems to fail to do this, see > > https://github.com/matrix-org/synapse/issues/9066 > > indeed matri

Processed: unarchiving 920339

Processing commands for cont...@bugs.debian.org: > unarchive 920339 Bug #920339 {Done: Andrej Shadura } [matrix-synapse] matrix-synapse: installation process hangs under sysvinit due to matrix-synapse daemon not closing file descriptor from debconf Unarchived Bug 920339 > thanks Stopping process

Bug#980048: FTBFS: -Werror=array-bounds in dlls/shell32/cpanelfolder.c

Source: wine Version: 5.0.3-1 Severity: serious Tags: upstream fixed-upstream patch ftbfs Justification: fails to build from source (but built successfully in the past) wine_5.0.3-1 failed to build from source on all architectures. Was the upload perhaps tested with an older toolchain than the one

Bug#978975: marked as done (ruby-em-redis FTBFS on IPV6-only buildds)

Your message dated Wed, 13 Jan 2021 12:19:00 + with message-id and subject line Bug#978975: fixed in ruby-em-redis 0.3.0+gh-3 has caused the Debian Bug report #978975, regarding ruby-em-redis FTBFS on IPV6-only buildds to be marked as done. This means that you claim that the problem has been

Bug#979866: marked as done (knxd FTBFS everywhere: autoconf issues)

Your message dated Wed, 13 Jan 2021 12:18:25 + with message-id and subject line Bug#979866: fixed in knxd 0.14.41-5 has caused the Debian Bug report #979866, regarding knxd FTBFS everywhere: autoconf issues to be marked as done. This means that you claim that the problem has been dealt with.

Bug#969597: libzstd: Please correct version in symbol file

Hi Andreas, On 1/11/21 5:49 PM, Andreas Tille wrote: Hi Alex, On Mon, Jan 11, 2021 at 02:48:50PM +0100, Alex Mestiashvili wrote: No, I didn't correct this specific issue. Just added the new symbols from the new release. However a patch or a list of "all" symbols is very welcome. I'd like to

Bug#980035: [Aptitude-devel] Bug#980035: aptitude: segmentation fault when starting aptitude

On Wed, Jan 13, 2021 at 10:29:17AM +0100, Vincent Lefevre wrote: > Package: aptitude > Version: 0.8.13-2+b1 > Severity: grave > Justification: renders package unusable > Tags: security > > I got a first "segmentation fault" just after updating ('u' in the TUI). > Now, each time I run aptitude, a s

Bug#979760: marked as done (vdjtools: autopkgtest failure: "java: not found")

Your message dated Wed, 13 Jan 2021 11:03:51 + with message-id and subject line Bug#979760: fixed in vdjtools 1.2.1+git20190311-4 has caused the Debian Bug report #979760, regarding vdjtools: autopkgtest failure: "java: not found" to be marked as done. This means that you claim that the probl

Bug#980035: aptitude: segmentation fault when starting aptitude

On 2021-01-13 11:24:33 +0100, Vincent Lefevre wrote: > A bundle is available for a limited time: > > https://www.vinc17.net/aptitude-segv.bundle > > I can reproduce the crash (but not always) with > > aptitude-run-state-bundle aptitude-segv.bundle > > on this machine and on another one. Wh

Bug#980035: aptitude: segmentation fault when starting aptitude

A bundle is available for a limited time: https://www.vinc17.net/aptitude-segv.bundle I can reproduce the crash (but not always) with aptitude-run-state-bundle aptitude-segv.bundle on this machine and on another one. -- Vincent Lefèvre - Web: 100% accessible val

Bug#980033: libucx0: UCX ERROR rdma_create_event_channel failed: No such device

On 13/01/2021 09:16, Drew Parsons wrote: Package: libucx0 Version: 1.10.0~rc1-2 Severity: serious Justification: debci Our next round of whack-a-mole comes from the new UCX. pmix 4.0.0-3 seems to have fixed the pmix error from bug#979744. debci tests next report a problem with UCX, with op

Bug#971296: rekall: Switch to python3-pycryptodome

Hi all, [..]> I just discovered that rekall is no longer maintained at the upstream > level so I'm wondering if we should not just remove the package. > > Hilko, Sascha, what do you think? Just bringing this up again... I would be in favour of removing it completely. Would be happy to file a RM

Bug#980035: aptitude: segmentation fault when starting aptitude

On 2021-01-13 10:29:17 +0100, Vincent Lefevre wrote: > However, if I run "strace -f -o str.out aptitude", I don't always > get a segmentation fault. So there may be another reason. When it crashes, this seems to be at the same place: [...] 2237416 read(3, "ym_19981025-8_amd64.deb\nSize: 11"..., 3

Bug#979843: python-django: autopkgtest regression in testing: 'image/vnd.mozilla.apng' != 'image/png'

Hi Paul, > sorry, I missed the follow up somehow. Mea culpa Oh, not at all! Thank you for working on the autopkgtest stuff and handling all the replies from these RC bugs. Best wishes, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org 🍥 chris-lamb.co.uk `-

Bug#980035: aptitude: segmentation fault when starting aptitude

Package: aptitude Version: 0.8.13-2+b1 Severity: grave Justification: renders package unusable Tags: security I got a first "segmentation fault" just after updating ('u' in the TUI). Now, each time I run aptitude, a segmentation occurs one second after starting it. I suppose that it doesn't like

Bug#980033: libucx0: UCX ERROR rdma_create_event_channel failed: No such device

Package: libucx0 Version: 1.10.0~rc1-2 Severity: serious Justification: debci Our next round of whack-a-mole comes from the new UCX. pmix 4.0.0-3 seems to have fixed the pmix error from bug#979744. debci tests next report a problem with UCX, with openmpi 4.1.0-5 pmix 4.0.0-3 ucx 1.10.0~rc1-