Processing control commands:
> reassign -1 src:numba
Bug #971100 [src:dolfinx] dolfinx: FTBFS: unsatisfiable build-dependency:
python3-llvmlite (< 0.34) but 0.34.0-1 is to be installed
Bug reassigned from package 'src:dolfinx' to 'src:numba'.
No longer marked as found in versions
Source: dolfinx
Followup-For: Bug #971100
Control: reassign -1 src:numba
Control: fixed -1 0.51.2-1
dolfinx does not depend on python3-llvmlite, it depends on numba.
numba depends on python3-llvmlite and has just been updated to resolve
the problem.
Reassigning and closing.
On 2020-10-01 12:36, Debian Bug Tracking System wrote:
This is an automatic notification regarding your Bug report
which was filed against the python3-llvmlite package:
#970867: python3-llvmlite: llvmlite 0.34 depends on incompatible llvm-9
It has been closed by Debian FTP Masters
(reply to
Your message dated Thu, 01 Oct 2020 05:03:50 +
with message-id
and subject line Bug#970694: fixed in numba 0.51.2-1
has caused the Debian Bug report #970694,
regarding numba: FTBFS: unsat-dependency: python3-llvmlite:amd64 (< 0.34)
to be marked as done.
This means that you claim that the
Your message dated Thu, 01 Oct 2020 05:03:50 +
with message-id
and subject line Bug#971148: fixed in numba 0.51.2-1
has caused the Debian Bug report #971148,
regarding umap-learn: FTBFS: unsatisfiable build-dependency: python3-llvmlite
(< 0.34) but 0.34.0-1 is to be installed
to be marked as
Your message dated Thu, 01 Oct 2020 04:33:42 +
with message-id
and subject line Bug#970867: fixed in llvmlite 0.34.0-2
has caused the Debian Bug report #970867,
regarding python3-llvmlite: llvmlite 0.34 depends on incompatible llvm-9
to be marked as done.
This means that you claim that the
Your message dated Thu, 01 Oct 2020 04:18:32 +
with message-id
and subject line Bug#936632: fixed in gnumeric 1.12.48-1
has caused the Debian Bug report #936632,
regarding gnumeric: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been
Your message dated Thu, 01 Oct 2020 04:18:32 +
with message-id
and subject line Bug#967143: fixed in gnumeric 1.12.48-1
has caused the Debian Bug report #967143,
regarding gnumeric: Unversioned Python removal in sid/bullseye
to be marked as done.
This means that you claim that the problem
Processing control commands:
> block 970717 by -1
Bug #970717 [src:kubernetes] kubernetes: abuse of "embedded code copies" |
hundreds of vendored libraries
970717 was not blocked by any bugs.
970717 was not blocking any bugs.
Added blocking bug(s) of 970717: 971515
--
970717:
Your message dated Thu, 01 Oct 2020 00:35:16 +
with message-id
and subject line Bug#970818: fixed in mrpt 1:2.1.0-2
has caused the Debian Bug report #970818,
regarding mrpt: FTBFS on mipse64el: E: Build killed with signal TERM after 150
minutes of inactivity
to be marked as done.
This means
Processing commands for cont...@bugs.debian.org:
> severity 970717 serious
Bug #970717 [src:kubernetes] kubernetes: abuse of "embedded code copies" |
hundreds of vendored libraries
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need
Control: unmerge -1
Control: clone -1 -2
Control: merge -1 971422
Control: reopen -2
Control: reassign -2 mssh 2.2-5
Control: severity -2 minor
Control: tag -2 = upstream
Control: retitle -2 mssh: Should use a non-NULL callback in
vte_terminal_spawn_async()
Hi again,
Axel Beckert wrote:
>
Processing control commands:
> unmerge -1
Bug #970356 {Done: Simon McVittie } [libvte-2.91-0] assertion
failed in vte_terminal_spawn_with_fds_async
Bug #971422 {Done: Simon McVittie } [libvte-2.91-0]
libvte-2.91-0: vte_terminal_spawn_async doesn't accept NULL callback since 0.62
Disconnected
Your message dated Wed, 30 Sep 2020 22:33:45 +
with message-id
and subject line Bug#971128: fixed in gazebo 11.1.0+dfsg-1
has caused the Debian Bug report #971128,
regarding gazebo: FTBFS: ld: libgazebo_gui.so.11.0.0: undefined reference to
Processing commands for cont...@bugs.debian.org:
> fixed 961993 1:0.4.26-1
Bug #961993 {Done: Simon McVittie } [libgegl-0.4-0] gimp
crashes on start up
Marked as fixed in versions gegl/1:0.4.26-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
961993:
Control: clone -1 -2
Control: unmerge -2
Control: reopen -2
Control: reassign -2 mssh 2.2-5
Control: severity -2 minor
Control: tag -2 = upstream
Control: retitle -2 mssh: Should use a non-NULL callback in
vte_terminal_spawn_async()
Dear Simon,
Simon McVittie wrote:
> I would recommend making
Processing control commands:
> clone -1 -2
Bug #970356 {Done: Simon McVittie } [libvte-2.91-0] assertion
failed in vte_terminal_spawn_with_fds_async
Bug #971422 {Done: Simon McVittie } [libvte-2.91-0]
libvte-2.91-0: vte_terminal_spawn_async doesn't accept NULL callback since 0.62
Failed to
On Wed, 30 Sep 2020 20:09:10 +0300 =?UTF-8?B?T3R0byBLZWvDpGzDpGluZW4=?=
wrote:
> Control: forwarded -1 https://jira.mariadb.org/browse/MDEV-21835
>
> Note that the upstream MariaDB uses OpenSSL both for building the
> server and the client. In Debian OpenSSL is forbidden in the current
> state
Processing commands for cont...@bugs.debian.org:
> reassign 961993 libgegl-0.4-0
Bug #961993 {Done: Simon McVittie } [gimp] gimp crashes on
start up
Bug reassigned from package 'gimp' to 'libgegl-0.4-0'.
No longer marked as found in versions gimp/2.10.18-1.
No longer marked as fixed in versions
The last upstream version 6.3.0 has support for Rails 6.
I have imported the package in the Ruby team salsa group (it was missing
for some reason), at the place expected from the Vcs fields.
I upgraded roughly the package, and noticed (only?)
two test failures (and no error), that I could not fix
Processing commands for cont...@bugs.debian.org:
> forcemerge 964499 964500
Bug #964499 [src:linux] Kernel panic with 5.7.0-1 & i7-9800X
Bug #964499 [src:linux] Kernel panic with 5.7.0-1 & i7-9800X
Marked as found in versions linux/5.7.6-1.
Bug #964500 [src:linux] 5.7.0-1: Kernel panic with
Processing control commands:
> close -1 10.2.0-1
Bug #971447 [src:gcc-10-doc] src:gcc-10-doc: fails to migrate to testing for
too long: binaries are not build for non-free packages
The source 'gcc-10-doc' and version '10.2.0-1' do not appear to match any
binary packages
Marked as fixed in
Source: gcc-10-doc
Version: 10.1.0-1
Severity: serious
Control: close -1 10.2.0-1
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and
Processing control commands:
> close -1 2.1.5-10-22
Bug #971446 [src:inventor] src:inventor: fails to migrate to testing for too
long: FTBFS on i386 and mipsel
Marked as fixed in versions inventor/2.1.5-10-22.
Bug #971446 [src:inventor] src:inventor: fails to migrate to testing for too
long:
Source: inventor
Version: 2.1.5-10-21
Severity: serious
Control: close -1 2.1.5-10-22
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing
Correction to the previous email:
The server builds (apparently statically) with WolfSSL while the
client uses GnuTLS (dynamically):
# mariadb -Bse 'SHOW VARIABLES' | grep -e version_ssl_library
version_ssl_library WolfSSL 4.4.0
# ldd $(which mariadbd) | grep -e crypt -e tls -e ssl
Your message dated Wed, 30 Sep 2020 18:33:28 +
with message-id
and subject line Bug#971435: fixed in charls 2.1.0+dfsg-2
has caused the Debian Bug report #971435,
regarding libcharls2: libcharls.so.2 vs. libCharLS.so.2
to be marked as done.
This means that you claim that the problem has been
Your message dated Wed, 30 Sep 2020 18:33:28 +
with message-id
and subject line Bug#971435: fixed in charls 2.1.0+dfsg-2
has caused the Debian Bug report #971435,
regarding blender: error while loading shared libraries: libCharLS.so.2: cannot
open shared object file
to be marked as done.
Your message dated Wed, 30 Sep 2020 18:33:28 +
with message-id
and subject line Bug#971431: fixed in charls 2.1.0+dfsg-2
has caused the Debian Bug report #971431,
regarding qmapshack: fails to start: missing library libCharLS.so.2
to be marked as done.
This means that you claim that the
Your message dated Wed, 30 Sep 2020 18:33:28 +
with message-id
and subject line Bug#971435: fixed in charls 2.1.0+dfsg-2
has caused the Debian Bug report #971435,
regarding qmapshack: fails to start: missing library libCharLS.so.2
to be marked as done.
This means that you claim that the
Your message dated Wed, 30 Sep 2020 18:33:28 +
with message-id
and subject line Bug#971425: fixed in charls 2.1.0+dfsg-2
has caused the Debian Bug report #971425,
regarding libcharls2: libcharls.so.2 vs. libCharLS.so.2
to be marked as done.
This means that you claim that the problem has been
Your message dated Wed, 30 Sep 2020 18:33:28 +
with message-id
and subject line Bug#971431: fixed in charls 2.1.0+dfsg-2
has caused the Debian Bug report #971431,
regarding blender: error while loading shared libraries: libCharLS.so.2: cannot
open shared object file
to be marked as done.
Your message dated Wed, 30 Sep 2020 18:33:28 +
with message-id
and subject line Bug#971425: fixed in charls 2.1.0+dfsg-2
has caused the Debian Bug report #971425,
regarding blender: error while loading shared libraries: libCharLS.so.2: cannot
open shared object file
to be marked as done.
Your message dated Wed, 30 Sep 2020 18:33:28 +
with message-id
and subject line Bug#971431: fixed in charls 2.1.0+dfsg-2
has caused the Debian Bug report #971431,
regarding libcharls2: libcharls.so.2 vs. libCharLS.so.2
to be marked as done.
This means that you claim that the problem has been
Your message dated Wed, 30 Sep 2020 18:33:28 +
with message-id
and subject line Bug#971425: fixed in charls 2.1.0+dfsg-2
has caused the Debian Bug report #971425,
regarding qmapshack: fails to start: missing library libCharLS.so.2
to be marked as done.
This means that you claim that the
Your message dated Wed, 30 Sep 2020 17:33:36 +
with message-id
and subject line Bug#971422: fixed in vte2.91 0.62.0-3
has caused the Debian Bug report #971422,
regarding libvte-2.91-0: vte_terminal_spawn_async doesn't accept NULL callback
since 0.62
to be marked as done.
This means that you
Your message dated Wed, 30 Sep 2020 17:33:36 +
with message-id
and subject line Bug#971422: fixed in vte2.91 0.62.0-3
has caused the Debian Bug report #971422,
regarding assertion failed in vte_terminal_spawn_with_fds_async
to be marked as done.
This means that you claim that the problem has
I filed an upstream bug at
https://github.com/cyrusimap/cyrus-sasl/issues/624 with the beginnings
of a patch, but the build then fails elsewhere and I didn't make much
more progress. Looks like some variables changed types.
Processing control commands:
> tag -1 pending
Bug #971422 [libvte-2.91-0] libvte-2.91-0: vte_terminal_spawn_async doesn't
accept NULL callback since 0.62
Bug #970356 [libvte-2.91-0] assertion failed in
vte_terminal_spawn_with_fds_async
Ignoring request to alter tags of bug #971422 to the same
Control: tag -1 pending
Hello,
Bug #971422 in vte2.91 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:
close 971096 0.4.3-2
thanks
Control: forwarded -1 https://jira.mariadb.org/browse/MDEV-21835
Note that the upstream MariaDB uses OpenSSL both for building the
server and the client. In Debian OpenSSL is forbidden in the current
state (or so has e.g. Clint Byrum stated), so in Debian we build using
alternatives, which for
Processing control commands:
> forwarded -1 https://jira.mariadb.org/browse/MDEV-21835
Bug #971367 [src:mariadb-10.5] mariadb-10.5 should not embed wolfssl
Set Bug forwarded-to-address to 'https://jira.mariadb.org/browse/MDEV-21835'.
--
971367:
Hello Jörg,
just a suspicion, but the "trap" might
point to a intentional process exit.
Is there something interesting near that
trap line visible in "journalctl -e"?
Otherwise if you have a coredump handler
like e.g. systemd-coredump installed, these
trap line should trigger a core to be
Control: tag -1 pending
On Tue, 2020-09-29 at 20:55 +0200, Wolfram Sang wrote:
> Package: seascope
>
> Version: 0.9+8a669e0e-2
>
> Severity: grave
>
> Justification: renders package unusable
>
> Dear Maintainer,
>
> after upgrading to bullseye, starting seascope failed for me:
>
> No module
Processing control commands:
> tag -1 pending
Bug #971389 [seascope] seascope: Dependency to 'python3-pyqt5.qtsvg' missing,
does not start
Added tag(s) pending.
--
971389: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971389
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Processing control commands:
> reassign 970356 libvte-2.91-0 0.62.0-1
Bug #970356 [libvte-2.91-0] assertion failed in
vte_terminal_spawn_with_fds_async
Bug #971422 [libvte-2.91-0] libvte-2.91-0: vte_terminal_spawn_async doesn't
accept NULL callback since 0.62
Ignoring request to reassign bug
Processing control commands:
> reassign 970356 libvte-2.91-0 0.62.0-1
Bug #970356 [mssh] assertion failed in vte_terminal_spawn_with_fds_async
Bug reassigned from package 'mssh' to 'libvte-2.91-0'.
No longer marked as found in versions mssh/2.2-5.
Ignoring request to alter fixed versions of bug
Processing commands for cont...@bugs.debian.org:
> affects 971425 src:gdal src:gdcm
Bug #971425 [libcharls2] libcharls2: libcharls.so.2 vs. libCharLS.so.2
Bug #971431 [libcharls2] blender: error while loading shared libraries:
libCharLS.so.2: cannot open shared object file
Bug #971435
Control: reassign 970356 libvte-2.91-0 0.62.0-1
Control: affects 970356 + mssh
Control: severity 971422 serious
Control: forcemerge 971422 970356
Control: tags 971422 + fixed-upstream pending
On Wed, 30 Sep 2020 at 15:22:37 +0100, Simon McVittie wrote:
> On Wed, 30 Sep 2020 at 15:12:09 +0100,
On 2020-09-30 10:40:29 +0200, Bram Fransen wrote:
> Its looks like its not solved for the latest version 450.66-1
This bug is for nvidia-graphics-drivers-legacy-390xx, whose latest
version is 390.138-4. You need to report another bug for the right
package.
--
Vincent Lefèvre - Web:
Your message dated Wed, 30 Sep 2020 14:36:29 +
with message-id
and subject line Bug#971115: fixed in r-bioc-dada2 1.16.0+dfsg-2
has caused the Debian Bug report #971115,
regarding r-bioc-dada2: FTBFS: ld: cannot find /usr/lib/x86_64-linux-gnu: file
format not recognized
to be marked as done.
Processing control commands:
> block -1 by 971425
Bug #971435 [libcharls2] qmapshack: fails to start: missing library
libCharLS.so.2
Bug #971425 [libcharls2] libcharls2: libcharls.so.2 vs. libCharLS.so.2
Bug #971431 [libcharls2] blender: error while loading shared libraries:
libCharLS.so.2:
Your message dated Wed, 30 Sep 2020 14:36:40 +
with message-id
and subject line Bug#971109: fixed in r-cran-rstan 2.21.2-2
has caused the Debian Bug report #971109,
regarding r-cran-rstan: FTBFS: ld: cannot find /usr/lib/x86_64-linux-gnu: file
format not recognized
to be marked as done.
Control: block -1 by 971425
Control: affects 971425 src:qmapshack
On 9/30/20 4:13 PM, Norbert Preining wrote:
> but there seems to be some case-hiccup and qmapshack needs recompilation
> or some more fixes?
charls was updated to 2.1.0+dfsg-1 yesterday which caused this, see: #971425
It FTBFS on
Your message dated Wed, 30 Sep 2020 14:36:40 +
with message-id
and subject line Bug#971233: fixed in r-cran-rstan 2.21.2-2
has caused the Debian Bug report #971233,
regarding src:r-cran-rstan: fails to migrate to testing for too long:
autopkgtest regression and missing build on armel
to be
Hi Sebastian,
> This is #971425.
Oh dear, I imagined something like this, what an incredible change.
Let us hope they fix it rather soon.
THanks
Norbert
--
PREINING Norbert https://www.preining.info
Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live +
Control: reassign -1 libcharls2 2.1.0+dfsg-1
Control: forcemerge 971425 -1
Control: affects -1 qmapshack
On 2020-09-30 23:13:04, Norbert Preining wrote:
> Package: qmapshack
> Version: 1.15.0-1
> Severity: grave
> Justification: renders package unusable
> X-Debbugs-Cc: norb...@preining.info
>
>
Processing control commands:
> reassign -1 libcharls2 2.1.0+dfsg-1
Bug #971435 [qmapshack] qmapshack: fails to start: missing library
libCharLS.so.2
Bug reassigned from package 'qmapshack' to 'libcharls2'.
No longer marked as found in versions qmapshack/1.15.0-1.
Ignoring request to alter fixed
Control: forwarded 971422 https://gitlab.gnome.org/GNOME/vte/-/issues/286
On Wed, 30 Sep 2020 at 15:12:09 +0100, Simon McVittie wrote:
> The documentation for vte_terminal_spawn_async() and its newer version
> vte_terminal_spawn_with_fds_async() says it's valid to call them with a
> NULL
Processing control commands:
> reassign -1 libcharls2 2.1.0+dfsg-1
Bug #971431 [blender] blender: error while loading shared libraries:
libCharLS.so.2: cannot open shared object file
Bug reassigned from package 'blender' to 'libcharls2'.
No longer marked as found in versions
Processing commands for cont...@bugs.debian.org:
> affects 971431 blender
Bug #971431 [libcharls2] blender: error while loading shared libraries:
libCharLS.so.2: cannot open shared object file
Bug #971425 [libcharls2] libcharls2: libcharls.so.2 vs. libCharLS.so.2
Added indication that 971431
Processing control commands:
> severity -1 serious
Bug #971425 [libcharls2] libcharls2: libcharls.so.2 vs. libCharLS.so.2
Severity set to 'serious' from 'important'
--
971425: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971425
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
On Wed, 16 Sep 2020 10:16:49 +0200 SZALAY Attila wrote:
> Hi Jean-Marc,
>
> Please check if a core file is available related to the segmentation
> fault. If there is any please make it available for me/us.
>
> Also, can you run syslog-ng-debun with the -r parameter and send the
> generated
Control: retitle 971422 libvte-2.91-0: vte_terminal_spawn_async doesn't accept
NULL callback since 0.62
On Wed, 30 Sep 2020 at 12:12:22 +0200, Pascal wrote:
> as described in this bug : https://bugs.debian.org/cgi-
> bin/bugreport.cgi?bug=970356
> It's impossible to launch mssh .
>
> mssh -a
Package: qmapshack
Version: 1.15.0-1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: norb...@preining.info
Hi
on Debian/sid I see
$ qmapshack
qmapshack: error while loading shared libraries: libCharLS.so.2: cannot open
shared object file: No such file or directory
Processing commands for cont...@bugs.debian.org:
> severity #971343 important
Bug #971343 [gnome-shell] Animated background/wallpaper (changing over time)
causes system freeze on Nouveau
Severity set to 'important' from 'critical'
> Analyzing at what point the problem was solved without the
Your message dated Wed, 30 Sep 2020 13:48:24 +
with message-id
and subject line Bug#971220: fixed in dput-ng 1.31
has caused the Debian Bug report #971220,
regarding dput-ng: FTBFS: /<>/dput/exceptions.py:docstring of
dput.exceptions.NoSuchConfigError:1:duplicate object description of
Processing control commands:
> tag -1 pending
Bug #971220 [src:dput-ng] dput-ng: FTBFS:
/<>/dput/exceptions.py:docstring of
dput.exceptions.NoSuchConfigError:1:duplicate object description of
dput.exceptions.NoSuchConfigError, other instance in library/exceptions, use
:noindex: for one of
Control: tag -1 pending
Hello,
Bug #971220 in dput-ng 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:
Processing control commands:
> tags -1 patch
Bug #969141 [doxygen] websocketpp: errors while generating documentation &
FTBFS with doxygen 1.8.19
Added tag(s) patch.
--
969141: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969141
Debian Bug Tracking System
Contact ow...@bugs.debian.org
control: tags -1 patch
Ciao Paolo,
the issue looks already solved upstream with this commit
https://github.com/doxygen/doxygen/commit/d067baf495d0415283ce724ad32cb9a08dc17c83
G.
On Wed, 30 Sep 2020 11:35:35 +0200 Gianfranco Costamagna
wrote:
> control: reassign -1 doxygen
> control: severity
Your message dated Wed, 30 Sep 2020 12:48:51 +
with message-id
and subject line Bug#971161: fixed in evemu 2.7.0-3
has caused the Debian Bug report #971161,
regarding evemu: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned
exit code 2
to be marked as done.
This means that you
Control: tag -1 pending
Hello,
Bug #971161 in evemu 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:
Processing control commands:
> tag -1 pending
Bug #971161 [src:evemu] evemu: FTBFS: dh_auto_test: error: make -j4 check
VERBOSE=1 returned exit code 2
Added tag(s) pending.
--
971161: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971161
Debian Bug Tracking System
Contact
Hi Simon,
> > Patch attached (although it might mean some Python substvar apparatus
> > is not working as expected).
>
> I don't think it's expected to work automatically in this case: I think
> hard-coding the dependency, as in your patch, is likely to be the only
> solution.
Sounds eminently
Processing commands for cont...@bugs.debian.org:
> retitle 971418 jhbuild: Missing dependency on python3-distutils
Bug #971418 [jhbuild] jhbuild: Missing dependency on python3-distuils
Changed Bug title to 'jhbuild: Missing dependency on python3-distutils' from
'jhbuild: Missing dependency on
On Wed, 30 Sep 2020 at 10:40:53 +0100, Chris Lamb wrote:
> Patch attached (although it might mean some Python substvar apparatus
> is not working as expected).
I don't think it's expected to work automatically in this case: I think
hard-coding the dependency, as in your patch, is likely to be the
Package: jhbuild
Version: 3.38.0-1
Severity: serious
Tags: patch
Hi,
This package is missing a binary dependency on python3-distutils:
$ jhbuild
Traceback (most recent call last):
File "/usr/bin/jhbuild", line 29, in
import jhbuild.main
File
Processing control commands:
> reassign -1 doxygen
Bug #969141 [src:websocketpp] websocketpp: errors while generating
documentation & FTBFS with doxygen 1.8.19
Bug reassigned from package 'src:websocketpp' to 'doxygen'.
Ignoring request to alter found versions of bug #969141 to the same values
Your message dated Wed, 30 Sep 2020 09:33:26 +
with message-id
and subject line Bug#947547: fixed in osc 0.168.2-2
has caused the Debian Bug report #947547,
regarding osc: Missing dependency on python3-m2crypto
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Wed, 30 Sep 2020 09:33:51 +
with message-id
and subject line Bug#971113: fixed in websocketpp 0.8.2-2
has caused the Debian Bug report #971113,
regarding websocketpp: FTBFS: error: /usr/include/wchar.h:35:10: fatal error:
'stddef.h' file not found [clang]
to be marked as
On Tue, 29 Sep 2020 at 22:29:29 -0300, Leandro Cunha wrote:
> > * Is this a new installation, or have you been using this hardware with
> > Linux for a while? If you've been using it previously, have you had
> > other graphics- or freeze-related issues with it?
>
> Only in version 3.36.3
Processing commands for cont...@bugs.debian.org:
> found 935677 2.16.0-5
Bug #935677 {Done: Apollon Oikonomopoulos } [src:ganeti]
ganeti-2.16: Depends on to be removed packages (python2/python-ipaddr
specifically)
Marked as found in versions ganeti/2.16.0-5.
> thanks
Stopping processing here.
Processing commands for cont...@bugs.debian.org:
> fixed 935677 3.0.0~rc1-1
Bug #935677 {Done: Apollon Oikonomopoulos } [src:ganeti]
ganeti-2.16: Depends on to be removed packages (python2/python-ipaddr
specifically)
Marked as fixed in versions ganeti/3.0.0~rc1-1.
> thanks
Stopping processing
Its looks like its not solved for the latest version 450.66-1
sudo dpkg-reconfigure nvidia-kernel-dkms
[10:35:07]
Uninstall Beginning
Module: nvidia-current
Version: 450.66
Kernel: 5.7.0-3-amd64 (x86_64)
-
Status: Before uninstall, this
control: fixed -1 1:11.0.0~+rc4-1
control: close -1
G.
On Fri, 18 Sep 2020 22:07:28 +0200 Paul Gevers wrote:
> Source: llvm-toolchain-11
> Version: 1:11.0.0~+rc2-5
> X-Debbugs-CC: debian...@lists.debian.org
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: fails-always
>
> Dear
Processing control commands:
> fixed -1 1:11.0.0~+rc4-1
Bug #970570 [src:llvm-toolchain-11] llvm-toolchain-11: autopkgtest failure:
Should find 3 warnings
Marked as fixed in versions llvm-toolchain-11/1:11.0.0~+rc4-1.
> close -1
Bug #970570 [src:llvm-toolchain-11] llvm-toolchain-11: autopkgtest
On Wed, 30 Sep 2020, Ahzo wrote:
>
> Sep 29, 2020, 07:14 by rguent...@suse.de:
>
> > I've filed > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97236
> >
> > Someone needs to create a testcase or provide instructions how to
> > reproduce the bug.
> >
>
> Thanks for taking care of this issue
Source: dolfinx
Followup-For: Bug #970864
Upstream have suggested running tests with
DOLFINX_JIT_CFLAGS="-g0 -O0"
Bug-resolving progress is currently hampered by the llvmlite fiasco.
Processing commands for cont...@bugs.debian.org:
> reassign 935677 src:ganeti
Bug #935677 {Done: Apollon Oikonomopoulos } [ganeti-2.16]
ganeti-2.16: Depends on to be removed packages (python2/python-ipaddr
specifically)
Bug reassigned from package 'ganeti-2.16' to 'src:ganeti'.
No longer marked
Your message dated Wed, 30 Sep 2020 06:03:40 +
with message-id
and subject line Bug#961735: fixed in siconos 4.3.0+dfsg-1
has caused the Debian Bug report #961735,
regarding siconos: FTBFS with mumps 5.3.1
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Wed, 30 Sep 2020 06:03:41 +
with message-id
and subject line Bug#962219: fixed in siconos 4.3.0+dfsg-1
has caused the Debian Bug report #962219,
regarding siconos: autopkgtest needs update for new version of boost-defaults:
deprecation warning on stderr
to be marked as
Your message dated Wed, 30 Sep 2020 06:03:40 +
with message-id
and subject line Bug#957794: fixed in siconos 4.3.0+dfsg-1
has caused the Debian Bug report #957794,
regarding siconos: ftbfs with GCC-10
to be marked as done.
This means that you claim that the problem has been dealt with.
If
94 matches
Mail list logo
