Package: logrotate
Version: 3.14.0-4
Severity: normal
Short backstory: A server I've access to might have been hacked. Due to
logrotate not being tweaked when the system was provisioned to keep more
than the default 4 weeks' worth of logs, it's hard to do a complete
forensics job.
Sure, this
Package: lxc
Version: 1:3.1.0+really3.0.3-2
Severity: normal
Apologies if this is a duplicate. This issue may relate to bug #919185
but a different file is concerned so I'm uncertain if this is a seperate
issue or not.
Basically, I've just upgraded 3.0.3-2 to 3.1.0+really3.0.3-2 and I'm
getting
Hi Thomas,
On 25 February 2018 at 18:42, Thomas Liske <tho...@fiasko-nw.net> wrote:
>
> Hi,
>
>
> Francis M <fmc...@gmail.com> writes:
>
>> s/2.12/2.11+git20180213-1/
>
> it has been released[1] upstream as needrestart 3.0.
Aha, thanks for that, I shal
s/2.12/2.11+git20180213-1/
Apologies for the noise, I made the mistake of typing my previous e-mail before
my morning coffee.
I've tested the above 2.11 release from experimental on a few systems and don't
see anything abnormal. As before, if there's anything I can do to help
get this into
the
Hi there,
I'm hitting this bug on a number of stretch-based systems. Is there
anything blocking 2.12 being uploaded to stretch-backports that I
could help with?
Thanks in advance,
Francis
Package: bugzilla
Version: 2.22.1-2.2
Severity: grave
Justification: renders package unusable
The default installation of Bugzilla is 2.22.1-2.2
The default installation of perl is 5.10
Bugzilla 2.22.1-2.2 does not work with perl 5.10
See e.g.:
6 matches
Mail list logo
