Hi Aditya,
On Fri, Apr 09, 2021 at 08:18:15PM -0700, Aditya Panchal wrote:
> Hope you are doing well. It is possible to use the `legacycontour` package
> available here: https://github.com/matplotlib/legacycontour and follow the
> instructions by Alan listed here:
>
Processing commands for cont...@bugs.debian.org:
> clone 986479 -1
Bug #986479 [ftp.debian.org] RM rsnapshot -- RoM; RoQA; no longer maintained by
upstream
Bug 986479 cloned as bug 986709
> reassign -1 src:rsnapshot
Bug #986709 [ftp.debian.org] RM rsnapshot -- RoM; RoQA; no longer maintained by
This will be fixed soon, I would like to include an autopkgtest in the
package, otherwise this would have been updated already.
On Fri, 9 Apr 2021 at 20:27, Salvatore Bonaccorso wrote:
>
> Source: mosquitto
> Version: 2.0.9-1
> Severity: grave
> Tags: security upstream
> Justification: user
Your message dated Fri, 09 Apr 2021 22:18:25 +
with message-id
and subject line Bug#986592: fixed in kaptive 0.7.3-2
has caused the Debian Bug report #986592,
regarding kleborate: flaky arm64 autopkgtest: Mutex is not owned by current
thread
to be marked as done.
This means that you claim
Control: reassign -1 kaptive 0.7.3-1
Andreas Tille writes:
> Thanks a lot. Its very relieving to know a competent person behind
> this
I appreciate the kind words, but am alas unclear on where precisely
BLAST+ is going wrong here. That said, I do see that future releases
will incorporate an
Processing control commands:
> reassign -1 kaptive 0.7.3-1
Bug #986592 [src:kleborate] kleborate: flaky arm64 autopkgtest: Mutex is not
owned by current thread
Bug reassigned from package 'src:kleborate' to 'kaptive'.
No longer marked as found in versions kleborate/2.0.1-1.
Ignoring request to
On 8 April 2021 at 11:29, Graham Inggs wrote:
| Control: forwarded -1 https://deb.li/6f4z
|
| TMB upstream have submitted a bug report [1] to R-forge.
|
| > Headers need update corresponding to new SuiteSparse version 5.7.1
| >
| > SuiteSparse was recently updated from version 4.2.1 to 5.7.1,
Processing commands for cont...@bugs.debian.org:
> found 986251 3.1.2-0+deb10u1
Bug #986251 {Done: Salvatore Bonaccorso }
[src:python-bleach] python-bleach: CVE-2021-23980
Marked as found in versions python-bleach/3.1.2-0+deb10u1.
> thanks
Stopping processing here.
Please contact me if you need
Processing commands for cont...@bugs.debian.org:
> tags 986525 + upstream
Bug #986525 [src:yarl] yarl: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p 3.9 returned exit code 13
Added tag(s) upstream.
> forwarded 986525 https://github.com/aio-libs/yarl/issues/563
I can confirm this, and the backtrace looks similar:
#0 0x00080005 in ?? ()
#1 0x77a1d879 in _Unwind_ForcedUnwind_Phase2 (exc=0x55614e90,
context=0x7fffdd70, frames_p=0x7fffdc78) at
../../../src/libgcc/unwind.inc:170
#2 0x77a1e14d in _Unwind_Resume
Source: mosquitto
Version: 2.0.9-1
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 mosquitto.
CVE-2021-28166[0]:
| In Eclipse Mosquitto version 2.0.0 to 2.0.9, if
Control: found -1 2.9.15.1-2
Hi,
it appears this conffile handling problem is caused by a not good
enough attempt to move the old conffile /etc/cron.daily/5snort to
/etc/cron.daily/snort-common.
This was introduced in version 2.9.15.1-2 commit 8780db8c, to
snort-common.preinst:
+#
Processing control commands:
> found -1 2.9.15.1-2
Bug #984614 [snort-common] snort-common: prompting due to modified conffiles
which were not modified by the user: /etc/cron.daily/snort-common
Marked as found in versions snort/2.9.15.1-2.
--
984614:
Your message dated Fri, 09 Apr 2021 18:03:35 +
with message-id
and subject line Bug#986274: fixed in pikepdf 1.17.3+dfsg-5
has caused the Debian Bug report #986274,
regarding pikepdf: CVE-2021-29421
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Package: prometheus-mongodb-exporter
Version: 1.0.0+git20180522.e755a44-1+b20
Severity: grave
Tags: upstream
Justification: renders package unusable
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Paragoumba
To: Debian Bug Tracking System
here the backtrace
Type "apropos word" to search for commands related to "word"...
Reading symbols from numptyphysics...
Reading symbols from
/usr/lib/debug/.build-id/1c/669beb5cdc6578b37b1e53e575baefe21524ff.debug...
(gdb) r
Starting program: /usr/games/numptyphysics
[Thread debugging using
Package: numptyphysics
Version: 0.2+svn157-0.4
Severity: grave
X-Debbugs-Cc: pi...@debian.org
the prgram do not start and crash at startup
-- System Information:
Debian Release: bullseye/sid
APT prefers stable-debug
APT policy: (500, 'stable-debug'), (500, 'proposed-updates-debug'), (500,
Control: tags 986051 confirmed moreinfo
Hi Sam,
On Sun, Mar 28, 2021 at 02:13:29PM -0400, Sam Hartman wrote:
> [ Reason ]
> In #985739 it was pointed out that internal symbols disappeared from
> libk5crypto.
> My bad; I noticed this, confirmed they were not externally visible, approved
> the
Processing control commands:
> forwarded -1 https://github.com/diaspora/diaspora/issues/8229
Bug #986286 [diaspora-installer] diaspora-installer: fails to install: Your
bundle is locked to mimemagic (0.3.5), but that version could not be found
Set Bug forwarded-to-address to
Control: forwarded -1 https://github.com/diaspora/diaspora/issues/8229
On Fri, 02 Apr 2021 14:21:14 +0200 Andreas Beckmann
> Fetching gem metadata from https://gems.diasporafoundation.org/..
> Fetching gem metadata from https://rubygems.org/..
> [ESC][31mYour bundle is locked to
Pinging this bug to avoid autoremoval, before migration of a fixed
package could happen.
One would hope the autoremovals logic would take care of such
things, but apparently not.
Chris
On Fri, Apr 09, 2021 at 08:13:52AM -0400, Aaron M. Ucko wrote:
> Don't worry, I am still looking into this crash, and had primarily
> intended that comment as a public note to myself -- the crash occured
> within a (presumably valid) call to ncbi-blast+, and wound up taking
> quite a few tries to
Andreas Tille writes:
> Thanks a lot for your investigation. Unfortunately I have no idea how
> to proceed from here. Does anybody have an idea? I mean a better idea
> than just stating this package does not work on arm64 which would
> probably some last resort.
Don't worry, I am still
Your message dated Fri, 09 Apr 2021 12:03:25 +
with message-id
and subject line Bug#986565: fixed in git-flow 1.12.3-2
has caused the Debian Bug report #986565,
regarding unusable with current git
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Le 9/04/21 à 11:09, Simon McVittie a écrit :
On Fri, 09 Apr 2021 at 10:37:59 +0200, Laurent Bigonville wrote:
The dep8 specification says:
Tests can expect that the ``$HOME`` environment variable to be set
to a directory that exists and is writeable by the user running the test.
But when
Your message dated Fri, 09 Apr 2021 11:18:47 +
with message-id
and subject line Bug#986427: fixed in psgml 1.4.0-12
has caused the Debian Bug report #986427,
regarding psgml: causes emacs-gtk to fail to upgrade from buster to bullseye
to be marked as done.
This means that you claim that the
Your message dated Fri, 9 Apr 2021 11:21:42 +0200
with message-id
and subject line Re: Bug#98: greenbone-security-assistant trying to access
the network during the build
has caused the Debian Bug report #98,
regarding greenbone-security-assistant trying to access the network during the
On Fri, 09 Apr 2021 at 10:37:59 +0200, Laurent Bigonville wrote:
> The dep8 specification says:
>
> Tests can expect that the ``$HOME`` environment variable to be set
> to a directory that exists and is writeable by the user running the test.
>
> But when using schroot (not tried anythong else),
Your message dated Fri, 09 Apr 2021 09:00:12 +
with message-id
and subject line Bug#985245: fixed in python-ppmd 0.3.3-2
has caused the Debian Bug report #985245,
regarding src:ppmd: reintroduced with lower version number, different project?
to be marked as done.
This means that you claim
Package: src:greenbone-security-assistant
Version: 20.8.0-2
Severity: serious
greenbone-security-assistant ftbfs, trying to access the network.
even after adding node-babel-cli as a b-d:
https://launchpad.net/~doko/+archive/ubuntu/toolchain/+sourcepub/12280131/+listing-archive-extra
The build
Control: tags -1 + fixed-upstream
Fixed in Matrix upstream svn rev 3376 [1].
[1]
https://r-forge.r-project.org/scm/viewvc.php?view=rev=matrix=3376
Processing control commands:
> tags -1 + fixed-upstream
Bug #980809 [src:rmatrix] rmatrix: breaks autopkgtest of r-cran-glmmtmb on s390x
Added tag(s) fixed-upstream.
--
980809: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980809
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Processing control commands:
> reopen -1
Bug #985401 {Done: Guillem Jover } [dpkg] dpkg: libreoffice
buster->bullseye upgrade failures
Bug reopened
Ignoring request to alter fixed versions of bug #985401 to the same values
previously set
--
985401:
Control: reopen -1
On 08/04/2021 19.22, Guillem Jover wrote:
Otherwise, I don't see a bug in dpkg for this here. And I'd be
inclined to close this.
I've managed to solve most of the upgrade paths by propagating some
Conflicts from libreoffice-common to libreoffice-core, s.t. the packages
get
Package: autopkgtest
Version: 5.16
Severity: serious
Hello,
The dep8 specification says:
Tests can expect that the ``$HOME`` environment variable to be set
to a directory that exists and is writeable by the user running the test.
But when using schroot (not tried anythong else), $HOME is set
Processing commands for cont...@bugs.debian.org:
> # version in buster is also affected
> found 986637 2.0.2-1+deb10u1
Bug #986637 [speedtest-cli] speedtest-cli: ValueError: invalid literal for
int() with base 10
Marked as found in versions speedtest-cli/2.0.2-1+deb10u1.
> thanks
Stopping
Your message dated Fri, 9 Apr 2021 10:22:40 +0200
with message-id
and subject line Re: Bug#986655: Warning: Journal has been rotated since unit
was started. Log output is incomplete or unavailable
has caused the Debian Bug report #986655,
regarding Warning: Journal has been rotated since unit
Your message dated Fri, 09 Apr 2021 08:10:08 +
with message-id
and subject line Bug#986268: fixed in firmware-ast 20140808-2
has caused the Debian Bug report #986268,
regarding Should be in non-free, not main; no source code
to be marked as done.
This means that you claim that the problem
Hi Aaron,
On Fri, Apr 09, 2021 at 12:01:21AM -0400, Aaron M. Ucko wrote:
> Never mind, this appears to be a different issue, per a backtrace
> obtained with EXCEPTION_STACK_TRACE_LEVEL=Error and a great deal of
> patience:
>
> Error: tblastn encountered an error:
> terminate called after
39 matches
Mail list logo
