Package: xscreensaver
Version: 6.06+dfsg1-3+deb12u1
### Issue description
Currently (2024-05), on a "stable" installation which is up-to-date,
xscreensaver displays a message that it is too old and should be
updated.
Security-aware users might think that xscreensaver contacted upstream's
.0 +
+++ keepassxc-2.7.7/debian/changelog2024-03-23 08:07:12.0 +
@@ -1,3 +1,10 @@
+keepassxc (2.7.7+dfsg.1-1~pre1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Pre-release new upstream version with passkey support enabled.
+
+ -- Guenther Brunthaler Sa
Package: vde2
Version: 2.3.2+r586-1
Severity: normal
X-Debbugs-Cc: 5i6itdpybzgshcivvdxsj...@nurfuerspam.de
Dear Maintainer,
Preliminary remark: Even though I am using Devuan rather then Debian, I
have verified that the problem still exists in the current "stretch"
version
Am Sat, 5 Mar 2022 13:32:24 +0100
schrieb Guilhem Moulin :
> I believe cryptdisks_start(8) and cryptdisks_stop(8) processes
> mappings in the order given on the command line, which is
> intentional. Are you talking about SysV init scripts?
Yes, you are right. The problem actually refers
to
Package: cryptsetup
Version: 2:2.3.7-1+deb11u1
### Issue description
When creating nested dmcrypt mappings in /etc/crtypttab,
cryptdisks_start processes them from top to bottom.
The means that a some encrypted base device will be unlocked before any
nested encrypted devices based on it.
While
Here is the (now closed) upstream ticket:
https://github.com/jirka-h/haveged/issues/66
Here is the commit where the patch has been applied:
https://github.com/jirka-h/haveged/commit/a4b69d65a8dfc5a9f52ff8505c7f58dcf8b9234f
avoiding the problem.
(Patch created 2021-11-03 by Guenther Brunthaler.)
Index: haveged-1.9.14/src/haveged.c
===
--- haveged-1.9.14.orig/src/haveged.c
+++ haveged-1.9.14/src/haveged.c
@@ -429,7 +429,7 @@ int main(int argc, char **argv)
I just noticed that the line in Debian 9
"$quiet" = "y"
was explicitly changed into
"${quiet?}" = "y"
in Debian 10, so I wonder whether this was really a regression by
mistake, or rather a deliberate way to break all existing hook scripts
which source
Package: initramfs-tools-core
Version: 0.133
initramfs hook scripts which source
. /usr/share/initramfs-tools/scripts/functions
and then later use one of the log_*() functions such as
log_begin_msg "Installing terminfo entries: $tinfos"
will make the hook script fail with the message "quiet:
Adding statistics in order to provide an estimate about the extent of
the of changes:
$ diffstat didiwiki_0.5-13_p1-2018.258.patch
didi.c |7 +++
http.c |6 ++
wiki.c | 16
wikitext.h |8 +---
4 files changed, 30 insertions(+), 7
It seems it was not such a good idea to paste the .ar archive directly
into the mail body.
I assume it got reformatted by my mail client, and will be rejected by
"ar" as a consequence.
I have enclosed the patch again as an attachment in this follow-up
posting, fixing that problem.
.patch/
004_reduced_logging_opt.patch/
005_https_support.patch/
006_delete_empty_pages.patch/
007_backwards_compatible_automigrate_away_nul.patch/
/0 0 0 0 644 1415 `
From b35d756add96aa2c69d7e43beae90cda58730cec Mon Sep 17 00:00:00 2001
From: Guenther Brunthaler
Date: Thu, 13 Sep
12 matches
Mail list logo
