On 15.05.24 23:49, Andres Salomon wrote:
Package: ninja-build
Version: 1.12.1-1
Severity: serious
Tags: affects -1 chromium
X-Debbugs-Cc: Andres Salomon
Chromium in unstable breaks with ninja-build 1.12. See here for example, where the same chromium
version (124.0.6367.201-1) built fine on
On 15.05.24 23:49, Andres Salomon wrote:
Package: ninja-build
Version: 1.12.1-1
Severity: serious
Tags: affects -1 chromium
X-Debbugs-Cc: Andres Salomon
Chromium in unstable breaks with ninja-build 1.12. See here for example, where the same chromium
version (124.0.6367.201-1) built fine on
Hi,
On 30.12.23 16:06, Guilhem Moulin wrote:
Control: tag -1 + patch
Hi,
I had a look at these issues for Buster (LTS). Unfortunately the
upstream project appears to be inactive.
On Fri, 22 Dec 2023 at 14:50:57 +0100, Moritz Mühlenhoff wrote:
CVE-2023-34194[0]:
| StringEqual in
On Fri, 8 Dec 2023 15:48:27 +0100 Emanuele Rocca wrote:
> Hi Simon,
>
> On 2023-12-07 08:39, Simon Josefsson wrote:
> > During debci autopkgtest of a new version of libgssglue on i386 I got
> > a failure like this, which is fatal and execution halts.
> >
> > 117s vex x86->IR: unhandled
On 04.12.23 22:03, Matthias Klose wrote:
Package: src:libseccomp
Version: 2.5.4-2
Severity: serious
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12
libseccomp ftbfs on i386. probably not related to Python 3.12, but blocks the
addition of Python 3.12
Seems like
On 04.12.23 22:03, Matthias Klose wrote:
Package: src:libseccomp
Version: 2.5.4-2
Severity: serious
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12
libseccomp ftbfs on i386. probably not related to Python 3.12, but blocks the
addition of Python 3.12
Seems like
Hi,
On 03.11.23 15:39, Miao Wang wrote:
Package: libseccomp2
Version: 2.5.4-1+loong64
Severity: normal
Tags: patch
libseccomp2 in debian ports lonng64 cannot work properly because it is using a
wrong mapping between syscall numbers and names, which can be reproduced by
first installing package
Control: tags -1 - patch
Hi,
On 06.09.23 10:27, zhangdandan wrote:
Would it be possible to include the support for LoongArch in the next upload?
Your opinions are welcome.
If you have any questions, you can contact me at any time.
[1]:https://github.com/seccomp/libseccomp
Control: tag -1 pending
Hello,
Bug #1052785 in golang-github-jinzhu-now 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:
Control: tag -1 pending
Hello,
Bug #1052787 in golang-github-mattn-go-sqlite3 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:
Control: tag -1 pending
Hello,
Bug #1052819 in golang-github-mattn-go-runewidth 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:
Hi Luca,
On Mon, 12 Jun 2023 15:33:45 +0100 Luca Boccassi wrote:
> Dear Release Team,
>
> We would like to upload the latest stable point release of systemd 252
> to bookworm-p-u. Stable release branches are maintained upstream with
> the intention of providing bug fixes only and no
Hi Luca,
On Mon, 12 Jun 2023 15:33:45 +0100 Luca Boccassi wrote:
> Dear Release Team,
>
> We would like to upload the latest stable point release of systemd 252
> to bookworm-p-u. Stable release branches are maintained upstream with
> the intention of providing bug fixes only and no
Package: udev
Version: 247.3-7+deb11u2
Tags: bullseye
Since udev 247.3-7+deb11u2 /dev/serial/by-id/* symlinks are not created anymore for USB serial
devices.
This is a regression from backporting
udev-always-create-device-symlinks-for-USB-disks.patch
It was fixed upstream by
Package: udev
Version: 247.3-7+deb11u2
Tags: bullseye
Since udev 247.3-7+deb11u2 /dev/serial/by-id/* symlinks are not created anymore for USB serial
devices.
This is a regression from backporting
udev-always-create-device-symlinks-for-USB-disks.patch
It was fixed upstream by
Package: systemd-zram-generator
Version: 1.1.2-2
systemd-zram-generator provides a default configuration for zram0 but doesn't
start it
automatically on package installation.
It's only active after calling systemctl daemon-reload manually or rebooting.
I think the package should call
On 29.03.23 10:28, Mayer, Dirk wrote:
make[3]: Nothing to be done for 'install-data-am'.
/usr/lib/python3/dist-packages/setuptools/command/install.py:34:
SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip
and other standards-based tools.
warnings.warn(
Control: tag -1 pending
Hello,
Bug #1003044 in python-dateutil 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:
On Sun, 05 Mar 2023 18:50:06 +0100 Arnout Vandecappelle
wrote:
This still fails to address the original issue: an irrelevant warning is
printed when performing a fairly mundane thing (requesting a nonexistent
timezone).
That part could be easily fixed. We can just remove the fallback from
On Sun, 05 Mar 2023 18:50:06 +0100 Arnout Vandecappelle
wrote:
This still fails to address the original issue: an irrelevant warning is
printed when performing a fairly mundane thing (requesting a nonexistent
timezone).
That part could be easily fixed. We can just remove the fallback from
On 21.02.23 20:46, Sandro Tosi wrote:
it produces output on stderr, which many tools consider it an error
and fails build.
When raising the severity of a bug to grave I would expect some concrete details
on what exactly is broken instead of a hand-wavy "breaks some stuff".
But anyway let's
On 21.02.23 20:46, Sandro Tosi wrote:
it produces output on stderr, which many tools consider it an error
and fails build.
When raising the severity of a bug to grave I would expect some concrete details
on what exactly is broken instead of a hand-wavy "breaks some stuff".
But anyway let's
On Sat, 7 Jan 2023 03:34:19 -0500 Sandro Tosi wrote:
> python-dateutil expects to have 'dateutil-zoneinfo.tar.gz' in it's directory
> tree, but this file is removed in the packaging.
>
> Error:
> "/usr/lib/python3/dist-packages/dateutil/zoneinfo/__init__.py:26: UserWarning:
> I/O error(2):
On Sat, 7 Jan 2023 03:34:19 -0500 Sandro Tosi wrote:
> python-dateutil expects to have 'dateutil-zoneinfo.tar.gz' in it's directory
> tree, but this file is removed in the packaging.
>
> Error:
> "/usr/lib/python3/dist-packages/dateutil/zoneinfo/__init__.py:26: UserWarning:
> I/O error(2):
On 23.11.22 21:48, Adam D. Barratt wrote:
Control: tags -1 + confirmed
On Sun, 2022-10-30 at 10:31 +0100, Felix Geyer wrote:
Fixing the no-dsa tagged CVE-2021-42260
[ Impact ]
DoS vulnerability
Please go ahead.
Uploaded, thanks!
Felix
On 23.11.22 21:48, Adam D. Barratt wrote:
Control: tags -1 + confirmed
On Sun, 2022-10-30 at 10:31 +0100, Felix Geyer wrote:
Fixing the no-dsa tagged CVE-2021-42260
[ Impact ]
DoS vulnerability
Please go ahead.
Uploaded, thanks!
Felix
Control: tag -1 pending
Hello,
Bug #1024037 in pytaglib 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:
On Sun, 13 Nov 2022 09:10:37 +0100 Matthias Klose wrote:
Package: src:python-crc32c
Version: 2.3-1
Severity: serious
Tags: sid bookworm ftbfs
User: debian-pyt...@lists.debian.org
Usertag: python3.11
[...]
In file included from crc32c_arm64.c:22:
On Sun, 13 Nov 2022 09:10:37 +0100 Matthias Klose wrote:
Package: src:python-crc32c
Version: 2.3-1
Severity: serious
Tags: sid bookworm ftbfs
User: debian-pyt...@lists.debian.org
Usertag: python3.11
[...]
In file included from crc32c_arm64.c:22:
Control: tag -1 pending
Hello,
Bug #1023912 in python-uinput 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:
@@
+tinyxml (2.6.2-4+deb11u1) bullseye; urgency=medium
+
+ * Import fix for CVE-2021-42260.
+- Add CVE-2021-42260.patch
+
+ -- Felix Geyer Thu, 20 Oct 2022 16:32:51 +0200
+
tinyxml (2.6.2-4) unstable; urgency=medium
[ Helmut Grohne ]
diff -Nru tinyxml-2.6.2/debian/patches/CVE-2021-42260.patch
@@
+tinyxml (2.6.2-4+deb11u1) bullseye; urgency=medium
+
+ * Import fix for CVE-2021-42260.
+- Add CVE-2021-42260.patch
+
+ -- Felix Geyer Thu, 20 Oct 2022 16:32:51 +0200
+
tinyxml (2.6.2-4) unstable; urgency=medium
[ Helmut Grohne ]
diff -Nru tinyxml-2.6.2/debian/patches/CVE-2021-42260.patch
hinx-4.patch
+
+ -- Felix Geyer Sat, 29 Oct 2022 09:59:26 +0200
+
speedcrunch (0.12.0-5) unstable; urgency=medium
* d/patches, d/control: fix docs build with Sphinx >= 2.0
diff -Nru
speedcrunch-0.12.0/debian/patches/0007-fix-docs-build-with-Sphinx-4.patch
speedcrunch-0.12.0/debian/pat
hinx-4.patch
+
+ -- Felix Geyer Sat, 29 Oct 2022 09:59:26 +0200
+
speedcrunch (0.12.0-5) unstable; urgency=medium
* d/patches, d/control: fix docs build with Sphinx >= 2.0
diff -Nru
speedcrunch-0.12.0/debian/patches/0007-fix-docs-build-with-Sphinx-4.patch
speedcrunch-0.12.0/debian/pat
On Wed, 21 Sep 2022 22:33:39 +0200 Libor Klepáč wrote:
Package: docker.io
Followup-For: Bug #908603
Hello Maintainers,
could you please consider backporting docker.io version 20.10.17 to stable?
We are hitting problem with graylog docker image.
of
+containers (Closes: #989490)
+ * Explicitly pass the containerd socket path to dockerd to make sure it
+doesn't start containerd on its own.
+
+ -- Felix Geyer Mon, 30 May 2022 20:34:49 +0200
+
docker.io (20.10.5+dfsg1-1+deb11u1) bullseye; urgency=medium
* Backport patches for CVE-2021-41089
of
+containers (Closes: #989490)
+ * Explicitly pass the containerd socket path to dockerd to make sure it
+doesn't start containerd on its own.
+
+ -- Felix Geyer Mon, 30 May 2022 20:34:49 +0200
+
docker.io (20.10.5+dfsg1-1+deb11u1) bullseye; urgency=medium
* Backport patches for CVE-2021-41089
Control: tags -1 patch
On Tue, 12 Oct 2021 13:47:08 +0200 pedeb wrote:
Hi Andrew,
Looks like the systemd unit is not properly configured. I had the same
the same problem and here is a solution.
Meanwhile this is not solved in debian, you can place the systemd unit
in a way that is not
On 03.12.21 17:40, Adam D. Barratt wrote:
Control: tags -1 + confirmed
On Thu, 2021-11-25 at 19:29 +0100, Felix Geyer wrote:
On Sun, 10 Oct 2021 14:34:30 +0200 Felix Geyer
wrote:
libseccomp 2.5.1 only knows about syscall up to Linux 5.8.
The proposed changes add the syscalls up to Linux 5.14
On 03.12.21 17:40, Adam D. Barratt wrote:
Control: tags -1 + confirmed
On Thu, 2021-11-25 at 19:29 +0100, Felix Geyer wrote:
On Sun, 10 Oct 2021 14:34:30 +0200 Felix Geyer
wrote:
libseccomp 2.5.1 only knows about syscall up to Linux 5.8.
The proposed changes add the syscalls up to Linux 5.14
On Sun, 10 Oct 2021 14:34:30 +0200 Felix Geyer wrote:
Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu
[ Reason ]
libseccomp 2.5.1 only knows about syscall up to Linux 5.8.
The proposed changes add the syscalls up to Linux
On Sun, 10 Oct 2021 14:34:30 +0200 Felix Geyer wrote:
Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu
[ Reason ]
libseccomp 2.5.1 only knows about syscall up to Linux 5.8.
The proposed changes add the syscalls up to Linux
; urgency=medium
+
+ * Add support for syscalls up to Linux 5.14.
+
+ -- Felix Geyer Sun, 10 Oct 2021 13:35:59 +0200
+
libseccomp (2.5.1-1) unstable; urgency=medium
* New upstream release.
diff -Nru libseccomp-2.5.1/debian/patches/series
libseccomp-2.5.1/debian/patches/series
--- libseccomp
; urgency=medium
+
+ * Add support for syscalls up to Linux 5.14.
+
+ -- Felix Geyer Sun, 10 Oct 2021 13:35:59 +0200
+
libseccomp (2.5.1-1) unstable; urgency=medium
* New upstream release.
diff -Nru libseccomp-2.5.1/debian/patches/series
libseccomp-2.5.1/debian/patches/series
--- libseccomp
Hi,
On 30.09.21 08:40, Johannes Schauer Marin Rodrigues wrote:
Hi Felix,
On Fri, 17 Sep 2021 07:15:16 +0200 Johannes Schauer Marin Rodrigues
wrote:
you set the upstream bug to https://github.com/seccomp/libseccomp/issues/336
but I don't think that is correct. The failures is not the same
Hi,
On 30.09.21 08:40, Johannes Schauer Marin Rodrigues wrote:
Hi Felix,
On Fri, 17 Sep 2021 07:15:16 +0200 Johannes Schauer Marin Rodrigues
wrote:
you set the upstream bug to https://github.com/seccomp/libseccomp/issues/336
but I don't think that is correct. The failures is not the same
Felix Geyer pushed to branch master at Debian Security Tracker /
security-tracker
Commits:
fd1859a8 by Felix Geyer at 2021-02-20T09:33:19+01:00
Add links to fixes for Docker CVEs
- - - - -
1 changed file:
- data/CVE/list
Changes:
=
data/CVE/list
Package: zfsutils-linux
Version: 0.8.5-1
/usr/lib/zfs-linux/trim fails if one of the pools doesn't support trim (e.g. is
on a HDD).
zpool trim seems to return exit code 255 in these cases.
Since the script is started with sh -e trim is never run on any subsequent
pools.
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
util-linux doesn't know about the new capabilities from Linux 5.9 yet, e.g.:
% setpriv --bounding-set -all echo test
setpriv: libcap-ng is too old for "all" caps
The problem is not
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
util-linux doesn't know about the new capabilities from Linux 5.9 yet, e.g.:
% setpriv --bounding-set -all echo test
setpriv: libcap-ng is too old for "all" caps
The problem is not
On Wed, 23 Sep 2020 01:18:59 +0200 Paul Menzel wrote:
Package: pipewire
Version: 0.3.12-1
Severity: normal
Forwarded: https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/293
Dear Debian folks,
If PipeWire is started first in the user session, it prevents PulseAudio
from accessing the
On Wed, 23 Sep 2020 01:18:59 +0200 Paul Menzel wrote:
Package: pipewire
Version: 0.3.12-1
Severity: normal
Forwarded: https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/293
Dear Debian folks,
If PipeWire is started first in the user session, it prevents PulseAudio
from accessing the
Package: gnome-settings-daemon
Version: 3.38.0-2
Tags: fixed-upstream
gsd-housekeeping segfaults every few minutes when /home is on a filesystem that
lacks atime
(for example ZFS with atime=off):
>
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
util-linux doesn't know about the new capabilities from Linux 5.8 yet, e.g.:
% setpriv --bounding-set -all echo test
setpriv: libcap-ng is too old for "all" caps
The problem is not
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
util-linux doesn't know about the new capabilities from Linux 5.8 yet, e.g.:
% setpriv --bounding-set -all echo test
setpriv: libcap-ng is too old for "all" caps
The problem is not
for CVE-2020-13401 (Closes: #962141)
+
+ -- Felix Geyer Sun, 14 Jun 2020 22:12:29 +0200
+
docker.io (18.09.1+dfsg1-7.1+deb10u1) buster-security; urgency=medium
[ Arnaud Rebillout ]
diff -Nru
docker.io-18.09.1+dfsg1/debian/patches/cve-2020-13401-disable-IPv6-router-advertisements.patch
Hi Andreas,
On 24.03.20 14:14, Martijn de Gouw wrote:
Package: cmake
Version: 3.13.2-1~bpo9+1
Severity: important
Dear Maintainer,
cmake in stretch-backports depends on libarchive13 (>= 3.3.3),
but libarchive13 (3.2.2-2+deb9u2) is the highest available version for
stretch (including
On 10.02.20 02:24, Brian Clinkenbeard wrote:
I believe I am also having this issue. "find_package(SDL2 REQUIRED)" in
CMakeLists.txt yields the following error:
-- Target architecture: x86_64
CMake Error at
/usr/share/cmake-3.16/Modules/FindPackageHandleStandardArgs.cmake:146
(message):
Source: boost1.71
Version: 1.71.0-5
Severity: serious
The boost1.71 python autopkgtest fails with cmake >= 3.16 because the python
include path isn't added correctly.
In debian/tests/srcs/python/CMakeLists.txt the variable Python_INCLUDE_DIR
is used but the correct variable is
Source: boost1.71
Version: 1.71.0-5
Severity: serious
The boost1.71 python autopkgtest fails with cmake >= 3.16 because the python
include path isn't added correctly.
In debian/tests/srcs/python/CMakeLists.txt the variable Python_INCLUDE_DIR
is used but the correct variable is
Hi,
On 2020-02-04 11:41, Kyuma Ohta wrote:
Package: libsdl2-dev
Version: 2.0.10+dfsg1-2
Severity: important
Dear Maintainer,
From this version, building any softwares with CMake,
not configurable.
This is *REGRESSION* of fix of BUG #946496.
Please revert this fix, or apply fixes to CMake
Hi David,
On 20.12.19 08:10, David Griffith wrote:
Package: libsdl2-gfx-dev
Version: 1.0.4+dfsg-3
Severity: important
I tried to compile a program that requires SDL2_gfxPrimitives_font.h
from libsdl2-gfx-dev. Specifically I tried to compile
https://github.com/lkundrak/koules from the SDL2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 26 Jan 2020 15:59:12 +0100
Source: snapcast
Architecture: source
Version: 0.18.0-1
Distribution: unstable
Urgency: medium
Maintainer: Felix Geyer
Changed-By: Felix Geyer
Changes:
snapcast (0.18.0-1) unstable; urgency=medium
Hi Laurent,
On 25.01.20 10:39, Laurent Bigonville wrote:
Package: purple-plugin-pack
Version: 2.7.0-3
Severity: normal
Tags: patch pending
Dear maintainer,
I've prepared an NMU for purple-plugin-pack (versioned as 2.7.0-3.1) and
uploaded it to DELAYED/10. Please feel free to tell me if I
Hi Hugh,
On 10.12.19 23:18, Hugh McMaster wrote:
At this point, I don’t see anything preventing us from adding the extra
include path, although I’m going to do some tests builds of various
SDL2-based programs to be certain.
Neverball could also be patched to call pkg-config with SDL2_ttf,
On 2020-01-15 03:21, Mattia Rizzolo wrote:
Oh wow.
So it turns out that my attempt at hastening the rebuilds by
pre-installed the new binaries in the choort backfired here.
Having said that, reading that .cmake file is't not clear to me why it
would skip the test if libxslt1-dev is not
On 14.01.20 23:33, Mattia Rizzolo wrote:
Hi Felix,
thank you for the quick follow up
On Tue, Jan 14, 2020 at 10:29:26PM +0100, Felix Geyer wrote:
your package failed to rebuild in a sid/amd64 chroot against libslt 1.1.34.
The problem seems to be that cmake's FindLibXslt can't deal
Hi Mattia,
On 14.01.20 21:42, Mattia Rizzolo wrote:
Source: cmake
Version: 3.15.4-1
Severity: important
Tags: ftbfs
User: libx...@packages.debian.org
Usertags: ftbfs-34
Dear maintainer,
your package failed to rebuild in a sid/amd64 chroot against libslt 1.1.34.
In particular, that version is
On 11.01.20 02:58, Scott Kitterman wrote:
I gave this a try and I still get apparmor denials:
Jan 10 20:54:13 relay02 kernel: [ 1372.562938] audit: type=1400
audit(1578707653.245:28): apparmor="DENIED" operation="open" profile="/usr/bin/
quasselcore" name="/proc/sys/kernel/random/boot_id"
On 08.12.19 14:03, Hugh McMaster wrote:
After reviewing the four proposals, I too prefer the pkg-config solution to
the others. That said, your proposal using the Debian-specific header is
wonderfully simple.
In the longer term, I'm hoping there will be a push at some point to no
longer install
Hi LLVM maintainers,
On Mon, 25 Nov 2019 21:59:48 +0100 Paul Gevers wrote:
> Source: llvm-toolchain-9
> Version: 1:9.0.0-3
> Severity: serious
> X-Debbugs-CC: debian...@lists.debian.org, cm...@packages.debian.org
> Tags: sid bullseye
> User: debian...@lists.debian.org
> Usertags: needs-update
>
Hi LLVM maintainers,
On Mon, 25 Nov 2019 21:59:48 +0100 Paul Gevers wrote:
> Source: llvm-toolchain-9
> Version: 1:9.0.0-3
> Severity: serious
> X-Debbugs-CC: debian...@lists.debian.org, cm...@packages.debian.org
> Tags: sid bullseye
> User: debian...@lists.debian.org
> Usertags: needs-update
>
Hi Simon,
On 27.11.19 20:18, Simon McVittie wrote:
> In an attempt to unblock this bug I've implemented several versions of a
> solution to it, so that the SDL2 maintainers can choose their favourite
> and merge it.
>
> [...]
>
> Do the SDL2 maintainers have any comments on these MRs, or
Source: oce
Version: 0.18.2-3
Severity: serious
The oce autopkgtest fails since cmake 3.15 entered unstable:
> CMake Warning (dev) in CMakeLists.txt:
> No project() command is present. The top-level CMakeLists.txt file must
> contain a literal, direct call to the project() command. Add a
Source: oce
Version: 0.18.2-3
Severity: serious
The oce autopkgtest fails since cmake 3.15 entered unstable:
> CMake Warning (dev) in CMakeLists.txt:
> No project() command is present. The top-level CMakeLists.txt file must
> contain a literal, direct call to the project() command. Add a
Source: wslay
Version: 1.1.0-1
Severity: serious
The wslay autopkgtest fails since cmake 3.15 entered unstable:
> CMake Warning (dev) in CMakeLists.txt:
> No project() command is present. The top-level CMakeLists.txt file must
> contain a literal, direct call to the project() command. Add
Source: oce
Version: 0.18.2-3
Severity: serious
The oce autopkgtest fails since cmake 3.15 entered unstable:
> CMake Warning (dev) in CMakeLists.txt:
> No project() command is present. The top-level CMakeLists.txt file must
> contain a literal, direct call to the project() command. Add a
Source: wslay
Version: 1.1.0-1
Severity: serious
The wslay autopkgtest fails since cmake 3.15 entered unstable:
> CMake Warning (dev) in CMakeLists.txt:
> No project() command is present. The top-level CMakeLists.txt file must
> contain a literal, direct call to the project() command. Add
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 15 Nov 2019 18:12:53 +0100
Source: libseccomp
Architecture: source
Version: 2.4.2-2
Distribution: unstable
Urgency: medium
Maintainer: Kees Cook
Changed-By: Felix Geyer
Changes:
libseccomp (2.4.2-2) unstable; urgency=medium
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 13 Nov 2019 00:00:49 +0100
Source: libseccomp
Architecture: source
Version: 2.4.2-1
Distribution: unstable
Urgency: medium
Maintainer: Kees Cook
Changed-By: Felix Geyer
Closes: 936917
Changes:
libseccomp (2.4.2-1) unstable
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 12 Nov 2019 20:11:25 +0100
Source: cmake
Architecture: source
Version: 3.15.4-1
Distribution: unstable
Urgency: medium
Maintainer: Debian CMake Team
Changed-By: Felix Geyer
Closes: 944090
Changes:
cmake (3.15.4-1) unstable
Hi Helmut,
On 23.10.19 09:47, Helmut Grohne wrote:
Package: cmake
Version: 3.13.4-1
Tags: patch upstream
User: debian-cr...@lists.debian.org
Usertags: ftcbfs
Control: affects -1 + src:flann src:hyphy src:liggghts src:sopt
FindMPI.cmake uses compiler wrappers such as mpicc to discover the
Hi Peter,
On Mon, 01 Oct 2018 14:10:30 + Peter Spiess-Knafl
wrote:
Source: libjsoncpp
Source-Version: 1.8.4-1
We believe that the bug you reported is fixed in the latest version of
libjsoncpp, which is due to be installed in the Debian FTP archive.
A unit test of cmake 3.15 fails
ere upgraded: root:
(sd-pam) (544), systemd (1, 543), [...]
--
Felix Geyer
Berater
Tel.: +49 2166 9901-0
Fax:+49 2166 9901-100
E-Mail: felix.ge...@credativ.de
PGP:D1DF 8149 7643 8822 7283 92DC 1004 DA1C FF6D B892
https://www.credativ.de
credativ GmbH, HRB Mönchengladbach 12080
USt-ID-Num
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 15 Oct 2019 00:16:32 +0200
Source: pyudev
Architecture: source
Version: 0.21.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team
Changed-By: Felix Geyer
Closes: 942179
Changes:
pyudev (0.21.0
Control: tag -1 pending
Hello,
Bug #942179 in pyudev 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:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 03 Sep 2019 19:59:35 +0200
Source: docker.io
Architecture: source
Version: 18.09.1+dfsg1-7.1+deb10u1
Distribution: buster-security
Urgency: medium
Maintainer: Dmitry Smirnov
Changed-By: Felix Geyer
Closes: 932673 933002
On 08.10.19 20:57, Christian Göttsche wrote:
Package: quassel-core
Version: 1:0.13.1-1
Severity: wishlist
Currently quassel-core requires the SELinux process permission execmem.
This is not a problem by itself, but for a 24/7 daemon hanging on the
internet it would be nice to not require it.
On 08.10.19 20:57, Christian Göttsche wrote:
Package: quassel-core
Version: 1:0.13.1-1
Severity: wishlist
Currently quassel-core requires the SELinux process permission execmem.
This is not a problem by itself, but for a 24/7 daemon hanging on the
internet it would be nice to not require it.
Control: tags -1 + fixed-upstream
On Thu, 03 Oct 2019 19:10:50 +0200 Domenico Cufalo wrote:
Package: gnome-shell-extension-dashtodock
Version: 66-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
* What led up to the situation?
Latest upgrade to Gnome 3.34
Control: tags -1 + fixed-upstream
On Thu, 03 Oct 2019 19:10:50 +0200 Domenico Cufalo wrote:
Package: gnome-shell-extension-dashtodock
Version: 66-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
* What led up to the situation?
Latest upgrade to Gnome 3.34
Package: gnome-shell-extension-suspend-button
Version: 0~git20180827-2
Severity: serious
Tags: fixed-upstream
The suspend button extension fails to load on Gnome 3.34, making it
completely unusable:
JS WARNING:
[/usr/share/gnome-shell/extensions/suspend-button@laserb/extension.js
165]:
Package: gnome-shell-extension-suspend-button
Version: 0~git20180827-2
Severity: serious
Tags: fixed-upstream
The suspend button extension fails to load on Gnome 3.34, making it
completely unusable:
JS WARNING:
[/usr/share/gnome-shell/extensions/suspend-button@laserb/extension.js
165]:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 19 Sep 2019 23:50:39 +0200
Source: libsdl2
Architecture: source
Version: 2.0.10+dfsg1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian SDL packages maintainers
Changed-By: Felix Geyer
Closes: 892087 924610 939249
Felix Geyer pushed to branch master at Debian Security Tracker /
security-tracker
Commits:
b1899cfb by Felix Geyer at 2019-09-19T20:16:33Z
Correct libsdl2 version of DLA-1714-1
- - - - -
b367d975 by Felix Geyer at 2019-09-19T20:16:34Z
CVE-2019-7637/libsdl2 already fixed in 2.0.6+dfsg1-4
See
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 18 Sep 2019 19:42:25 +0200
Source: sdl-image1.2
Architecture: source
Version: 1.2.12-12
Distribution: unstable
Urgency: medium
Maintainer: Debian SDL packages maintainers
Changed-By: Felix Geyer
Changes:
sdl-image1.2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 17 Sep 2019 22:34:12 +0200
Source: libsdl1.2
Architecture: source
Version: 1.2.15+dfsg2-5
Distribution: unstable
Urgency: medium
Maintainer: Debian SDL packages maintainers
Changed-By: Felix Geyer
Closes: 924609
Changes
Felix Geyer pushed to branch master at Debian Security Tracker /
security-tracker
Commits:
4c00bb2e by Felix Geyer at 2019-09-17T20:33:09Z
Mark CVE-2019-13626 as not affecting libsdl1.2
Support for 24-bit PCM WAVE has been introduced in SDL 2.0.
Additionally the unchecked encoded variable
On Thu, 12 Sep 2019 23:20:14 +0200 Paul Menzel wrote:
Package: aqbanking-tools
Version: 5.8.2-0.1
Severity: important
Dear Debian folks,
Unfortunately, I am unable to do a transactions with abtransfers,
and get the error below from the Berlin Volksbank (hbci11.fiducia.de).
9050::Die
On Fri, 23 Aug 2019 12:08:10 +0200 Matthias Merz wrote:
Package: gnucash
Version: 1:3.6-1
Severity: important
Dear Maintainer,
German legislation requires some changes to HBCI, rendering the HBCI
interface of gnucash 3.6-1 in Debian mostly useless due to missing
requirements.
As mentioned in
1 - 100 of 6553 matches
Mail list logo
