Hello!
Status summary:
* MariaDB 10.5 for Debian is pending at
https://salsa.debian.org/mariadb-team/mariadb-10.5/ since last weekend
but still waiting for contributions on
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988089, #976147 and
#977137.
* MariaDB 10.3 for Debian is pending at
http
close 987279 1.4.6+really1.4.2-2
thanks
Processing commands for cont...@bugs.debian.org:
> close 987279 1.4.6+really1.4.2-2
Bug #987279 [src:nim] nim: amd64 binaries built by maintainer; needs source-ony
upload
Marked as fixed in versions nim/1.4.6+really1.4.2-2.
Bug #987279 [src:nim] nim: amd64 binaries built by maintainer; needs sour
If I am not mistaken, this is a release critical bug. Is there a fix
for testing on the way as well?
On Do, Mai 13, 2021 at 16:51, Debian Bug Tracking System
wrote:
This is an automatic notification regarding your Bug report
which was filed against the gnome-sound-recorder package:
#98829
Your message dated Thu, 13 May 2021 22:04:17 +
with message-id
and subject line Bug#957233: fixed in freefem++ 3.61.1+dfsg1-6
has caused the Debian Bug report #957233,
regarding freefem++: ftbfs with GCC-10
to be marked as done.
This means that you claim that the problem has been dealt with.
On 2021-05-10 12:16:09, Noah Meyerhans wrote:
> On Mon, May 10, 2021 at 09:00:34PM +0200, Moritz Mühlenhoff wrote:
> > > Hi, since this package was brought into Debian in ~2018, there have been
> > > several transformations in the GCE guest software stack and thus the
> > > current landscape is ver
Source: pydantic
Version: 1.7.3-1
Severity: grave
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team
Hi,
The following vulnerability was published for pydantic.
Note, strictly speaking the severity is slightly choosen inaproritate
for the type of security issue. Makin
Package: src:xen
Version: 4.14.1+11-gb0b734a8b3-1
Severity: critical
Justification: causes serious data loss
X-Debbugs-Cc: debian...@virtualzone.hu
Dear Maintainer,
after a clean install of bullseye/testing the xen dmesg shows the following
message:
(XEN) AMD-Vi: IO_PAGE_FAULT: :01:00.1 d0 a
Hi Yves-Alexis,
On Thu, May 13, 2021 at 07:05:37PM +0200, Yves-Alexis Perez wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On Tue, 2021-05-11 at 21:45 +0200, Salvatore Bonaccorso wrote:
> > The following vulnerability was published for thunar.
> >
> > CVE-2021-32563[0]:
> > > An
Your message dated Thu, 13 May 2021 18:33:31 +
with message-id
and subject line Bug#988394: fixed in thunar 4.16.8-1
has caused the Debian Bug report #988394,
regarding thunar: CVE-2021-32563
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package src:nekobee
> # 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
Set
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package solo-python
> # 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
Set
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Tue, 2021-05-11 at 21:45 +0200, Salvatore Bonaccorso wrote:
> The following vulnerability was published for thunar.
>
> CVE-2021-32563[0]:
> > An issue was discovered in Thunar before 4.16.7 and 4.17.x before
> > 4.17.2. When called with a regula
Your message dated Thu, 13 May 2021 16:48:30 +
with message-id
and subject line Bug#988292: fixed in gnome-sound-recorder 3.38.1-1
has caused the Debian Bug report #988292,
regarding gnome-sound-recorder: Potential data loss and regression (recordings
not saved or unusable)
to be marked as do
On Thu, 15 Apr 2021 23:00:22 -0700 Sunil Mohan Adapa
wrote:
> Hi,
>
> The problem is not limited to amd64. I see this problem on arm64. On a
> FreedomBox arm64 image, on a Raspberry Pi 3B+ (when booted with UEFI
> firmware[1]) when grub efi packages are upgraded, boot fails with the
> error 'symb
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This is the missing part for Debian-11 bulls-eye:
> andrew@bulls-eye:~/HandBrake$ ate show libayatana-appindicator-dev
> Package: libayatana-appindicator-dev
> Version: 0.5.5-2
> State: installed
> Automatically installed: no
> Priority: optiona
Your message dated Thu, 13 May 2021 14:33:30 +
with message-id
and subject line Bug#984956: fixed in openmpi 4.1.0-9
has caused the Debian Bug report #984956,
regarding openmpi-bin: with mpirun --host : orte crashes with
FORCE-TERMINATE [...] plm_base_launch_support.c
to be marked as done.
T
Your message dated Thu, 13 May 2021 16:03:14 +0200
with message-id <8a27d1fe-4437-28ea-3240-8f4aed1f4...@debian.org>
and subject line Closing the bug
has caused the Debian Bug report #988463,
regarding crashes on startup with X11
to be marked as done.
This means that you claim that the problem has
Package: gnome-control-center
Version: 1:3.38.4-1
Severity: serious
X-Debbugs-Cc: oleb...@debian.org
Dear maintainer,
when starting gnome-control-center, I get a crash with the following
stacktrace:
(gdb) bt
#0 0x750d3b79 in _cogl_renderer_handle_native_event (renderer=0x0,
event=0x7fff
Package: trac
Version: 1.5.2+dfsg-2
Severity: serious
IMHO, the current version of Trac is not suitable for including
it in a stable release. I'll try to provide backports of future
version 1.6.x for Debian 11.
Processing control commands:
> severity -1 important
Bug #988328 [src:golang-github-pquerna-cachecontrol]
golang-github-pquerna-cachecontrol: FTBFS in tests constant 9223372036854775807
overflows int
Severity set to 'important' from 'serious'
--
988328: https://bugs.debian.org/cgi-bin/bugrepor
ControL: severity -1 important
On Thu, 2021-05-13 at 12:43 +0100, peter green wrote:
> The package is arch all.
>
> While I don't think it's explicitly spelled out anywhere, my
> understanding
> is that it has never been a requirement for arch all packages to
> build
> on all architectures. So IM
During a rebuild of the package, it is seen that the package fails in
one of the tests, commonly on 32 bit systems. So far, I can see it fails
on armhf and i386.
The package is arch all.
While I don't think it's explicitly spelled out anywhere, my understanding
is that it has never been a r
On Tue, 04 May 2021 at 15:47:03 +0200, Cyril Brulebois wrote:
> would it seem reasonable to add a hack in whatever would make sense
> (pango1.0, harfbuzz, and/or gtk+2.0), but only in the udeb build, so
> that we dodge the issue for Bullseye without impacting installed
> systems/deb packages? If gi
Hi Håvard,
On Wed, May 12, 2021 at 9:05 PM Håvard Flaget Aasen
wrote:
> Thanks for the sponsoring Utkarsh!
You're very welcome! :)
> I made a package for stretch as well, and uploaded it to mentors. [0]
> Though I'm not sure about this lts stuff. So far this package I made
> just targets "stret
On Mon, May 03, 2021 at 07:58:06AM +0200, Tobias Frost wrote:
>...
> > I don't actually know the procedures for a security update, in any case.
> > so if anyone has advice on next steps, I'd appreciate it.
>
> https://www.debian.org/doc/manuals/developers-reference/pkgs.html#bug-security
> and
> h
Processing control commands:
> severity -1 serious
Bug #975270 [rdiff-backup] rdiff-backup: Can't talk to the version from buster
Severity set to 'serious' from 'important'
--
975270: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975270
Debian Bug Tracking System
Contact ow...@bugs.debian.or
Hi,
On Mon, 10 May 2021 at 16:09, Grégory David wrote:
>
> Package: libboost-python-dev
> Version: 1.74.0.3
> Severity: grave
> Justification: renders package unusable
> X-Debbugs-Cc: d...@groolot.net
>
> Dear Maintainer,
>
>* What led up to the situation?
> When I try to compile `mididi
See in part the discussion upstream at :
https://github.com/open-mpi/ompi/issues/8596
One workaround might be to use the internal pmix. 4.1.0-4 worked, and
using the internal pmix works, BUT reverting to using internal pmix has
big testing consequences:
We'd move libpmix.so.2 from the extern
Processing commands for cont...@bugs.debian.org:
> block 988440 with 988444 988445
Bug #988440 [src:golang-github-seccomp-containers-golang]
golang-github-seccomp-containers-golang: Keep out of bookworm
988440 was not blocked by any bugs.
988440 was not blocking any bugs.
Added blocking bug(s) of
Processing commands for cont...@bugs.debian.org:
> retitle 988440 golang-github-seccomp-containers-golang: Keep out of bookworm
Bug #988440 [src:golang-github-seccomp-containers-golang] Keep out of bookwork
Changed Bug title to 'golang-github-seccomp-containers-golang: Keep out of
bookworm' from
Source: golang-github-seccomp-containers-golang
Version: 0.3.2-1
Severity: serious
Tags: bookworm sid
Hello,
golang-github-seccomp-containers-golang is now deprecated upstream and
has been replaced by containers-common
This package should be removed of the archive when the rdeps updated to
not d
Source: slurm-wlm
Version: 20.11.5-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 slurm-wlm.
CVE-2021-31215[0]:
| SchedMD Slurm before 20.02.7 and 20.03.x through
33 matches
Mail list logo
