Bug#1094245: New upstream version xxx

On Fri, 7 Mar 2025 17:45:29 +0100 (CET) Thorsten Glaser wrote: > >> Note that problem back then was that the shipped archived > >> contained m4 files so the autogen step did not "help". > > the attack actually *relied* on doing so. > Just to clarify what your saying here: the attack relied on

Bug#1084761: Patch for usr.bin.evince?

Can confirm same issue. Anyone have a reasonable  patch we can make to the the usr.bin.evince profile to fix this?

Bug#866340: Debian 12 Bookworm

Just discovered this on Debian 12 bookworm which doesn't even have a syslog daemon by default anymore. How did this get even out of testing? Cheers.

Bug#1094245: New upstream version xxx

Hi Sebastian. On 29/1/25 06:41, Sebastian Andrzej Siewior wrote: I plan to switch to cmake at some point. Then we don't have to worry about autoconf magic. Sounds good. override_dh_update_autotools_config:     ./autogen.sh How is this different from the current autoreconf step that i

Bug#1094245: New upstream version xxx

Package: xz-utils Version: 5.6.3 Severity: normal Tags: security Presumably these commits are taking some upstream release archive and extracting it over main branch of https://salsa.debian.org/debian/xz-utils.git? git log --pretty=format:'%h%x09%an%x09%ad%x09%s' --grep "New upstream ver

Bug#1068024: Fwd: Accepted xz-utils 5.6.3-1 (source) into unstable

Hello. Looks fine, but somewhat disconcerting / confusing to see 450 commits from Jia Tan on upstream v5.6.2 and 630 on debian/unstable and debian/5.6.2-1 in https://salsa.debian.org/debian/xz-utils as a result of merge commit 6bd3e4a. On Fri, 25 Oct 2024 08:00:22 +0200 Sebastian Andrzej Siewi

Bug#986709: (no subject)

FYI linked issue and summary of issue from upstream perspective: https://github.com/rsnapshot/rsnapshot/issues/279#issuecomment-860001348

Bug#986709: rsnapshot is stable, not dead

On Fri, 28 May 2021 15:39:28 -0500 Michael Lustfield wrote: > On Fri, 28 May 2021 19:56:47 +0100 > David Cantrell wrote: > > > [...] > > So what, exactly, is unmaintained about it? Looks to me like it has > > exactly the amount of maintenance that is required for mature software. > > I'm not go

Bug#793684: Upstream issue link

Upstream cannot reproduce on 1.4.3 or latest master. Upstream issue: https://github.com/rsnapshot/rsnapshot/issues/285. -- PGP: 0xA53455C1

Bug#573254: (no subject)

Issue still exists in upstream. Is considered very minor and won't be fixed. See https://github.com/rsnapshot/rsnapshot/issues/281 Thanks, Sam. -- PGP: 0xA53455C1

Bug#793687: (no subject)

Cannot reproduce on upstream source. This appears to have been fixed in upstream master and in last tagged release (1.4.3, Nov 17 2019). Thanks, Sam. -- PGP: 0xA53455C1

Bug#859099: (no subject)

Cannot reproduce. This appears to have been fixed in upstream master and in last tagged release (1.4.3, Nov 17 2019). Thanks, Sam. -- *PGP*: 0xA53455C1

Bug#934349: (no subject)

This is fixed on latest upstream master. As yet, there is no tagged version that includes the fix for this however. -- PGP: 0xA53455C1

Bug#869247: (no subject)

This is expected behavior. rsnapshot man page:    cmd_preexec    Full path (plus any arguments) to preexec script (optional).  This script will run immediately before each backup operation (but not any rotations). If the