sendfile 2.1b.20080616-8 is marked for autoremoval from testing on 2021-09-30
It is affected by these RC bugs:
969409: sendfile: weekly cron job should use mktemp instead of tempfile
https://bugs.debian.org/969409
This mail is generated by:
Processing commands for cont...@bugs.debian.org:
> reassign 502616 libwbxml2-1
Bug #502616 [libwbxml2-0] libwbxml2-0: Bad Request (0x40) while using MultiSync
0.90
Bug reassigned from package 'libwbxml2-0' to 'libwbxml2-1'.
No longer marked as found in versions wbxml2/0.9.2-6.
Ignoring request
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 31 Aug 2021 16:32:50 -0400
Source: sawfish-themes
Architecture: source
Version: 0.13.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group
Changed-By: Boyuan Yang
Changes:
sawfish-themes
sawfish-themes_0.13.0-1_source.changes uploaded successfully to localhost
along with the files:
sawfish-themes_0.13.0-1.dsc
sawfish-themes_0.13.0.orig.tar.gz
sawfish-themes_0.13.0-1.debian.tar.xz
sawfish-themes_0.13.0-1_amd64.buildinfo
Greetings,
Your Debian queue daemon (running
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 31 Aug 2021 15:04:19 -0400
Source: libgssglue
Architecture: source
Version: 0.4-3
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group
Changed-By: Boyuan Yang
Closes: 732574
Changes:
libgssglue
libgssglue_0.4-3_source.changes uploaded successfully to localhost
along with the files:
libgssglue_0.4-3.dsc
libgssglue_0.4.orig.tar.bz2
libgssglue_0.4-3.debian.tar.xz
libgssglue_0.4-3_amd64.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
This is derived (and slightly expanded) from the old-upstream revision
144.
---
tests/check_fstab/a | 1 +
tests/check_fstab/b | 1 +
tests/check_fstab/c | 1 +
tests/check_fstab/d | 1 +
tests/check_fstab/e | 1 +
5 files changed, 5 insertions(+)
create mode 100644 tests/check_fstab/a
create
The memory provided by `buf` is still reference by `path` and used after
the free call. Delay the freeing until after using it.
---
src/realpath.c | 12 ++--
1 file changed, 10 insertions(+), 2 deletions(-)
diff --git a/src/realpath.c b/src/realpath.c
index 1cf7eaf..9133605 100644
---
Package: pmount
Version: 0.9.23-6
Tags: patch
Dear Debian maintainers
I stumbled over a use-after-free bug in pmount. It's in its realpath
implementation when dealing with stacked symlinks, i.e. symlinks pointing to
symlinks. (Ironically, pmount "switched to a [self-made] implementation of
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 31 Aug 2021 10:54:30 -0400
Source: elida
Architecture: source
Version: 0.4.0
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group
Changed-By: Boyuan Yang
Closes: 776955
Changes:
elida (0.4.0)
elida_0.4.0_source.changes uploaded successfully to localhost
along with the files:
elida_0.4.0.dsc
elida_0.4.0.tar.xz
elida_0.4.0_amd64.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
Hi Madie,
Last year I wrote a lot of patches for pmount, amongst which two
remove the bundled implementation of realpath and switch to the
"modern" interface
char *realpath(const char *restrict path, NULL);
which has been supported by the libc for quite some time. The original
program
Processing commands for cont...@bugs.debian.org:
> tags 993376 + upstream
Bug #993376 [gtkpod] gtkpod: CVE-2021-32732 - stack overflow in embedded
AtomicParsley code APar_read64
Added tag(s) upstream.
> tags 993375 + upstream
Bug #993375 [gtkpod] gtkpod: CVE-2021-37231 - stack-buffer overflow in
Package: gtkpod
Version: 2.1.5-6
Severity: important
Tags: security
https://github.com/wez/atomicparsley/issues/32
See also #993366
gtkpod embeds a vulnerable version of AtomicParsley which causes a stack
overflow,
however the data file used to test atomicparsley upstream is not recognised by
Package: gtkpod
Version: 2.1.5-8
Severity: important
Tags: security
gtkpod embeds a vulnerable version of AtomicParsley, however, the data file
used to
test atomicparsley upstream is not recognised by gtkpod.
https://github.com/wez/atomicparsley/issues/30
Processing control commands:
> reopen -1
Bug #993348 {Done: Dirk Eddelbuettel } [anacron] anacron:
dangling symlinks under /etc/systemd/system
'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.
Bug
Control: reopen -1
Control: notfixed -1 r-cran-bh/1.74.0-2
Hello Dirk,
On 2021-08-31 12:24:03 +, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the anacron package:
>
> #993348: anacron: dangling symlinks under
Your message dated Tue, 31 Aug 2021 12:20:32 +
with message-id
and subject line Bug#993348: fixed in r-cran-bh 1.74.0-2
has caused the Debian Bug report #993348,
regarding anacron: dangling symlinks under /etc/systemd/system
to be marked as done.
This means that you claim that the problem
Package: anacron
Version: 2.3-31+b1
Severity: normal
anacron has left dangling symlinks:
lrwxrwxrwx 1 root root 35 2015-06-18 10:28:00
/etc/systemd/system/multi-user.target.wants/anacron.service ->
/lib/systemd/system/anacron.service
lrwxrwxrwx 1 root root 33 2017-06-02 10:42:36
19 matches
Mail list logo
