I don't know how to trigger and therefore test this and sadly don't have
the time to play around with this as well. So no, I can't guarantee
anything. If that fix is contained in UB 20.04 already and it's too
risky for you to backport to UB 18.04, I'll simply continue ignoring the
problem, as I
> @Thorsten - is there a reasonable way to trigger the issue[...]
I really don't know how to manually trigger that issue beyond what is
described in the commit message already. I only recognized the problem
and reported it after ignoring it in the past.
> A field (which should be displayed as
Public bug reported:
Sysstat provided by UB 18.04 contains an error leading to missing column
values for "%gnice" under some circumstances. That error has been fixed
by changing only two lines of code. So it would be great if you would
consider backporting that fix for UB 18.04 and 20.04, because
Public bug reported:
Hi all,
to make a long story short: There's a segfault in svnserve 1.9.3
distributed by UB 16.04 LTSm which is very likely available in 1.9.7
distributed with UB 18.04 LTS as well and has been fixed upstream by the
following patch in version 1.9.9:
> My unimportant opinion is - yes - it should find and try to compress all old
> files.
> Because there is no guarantee the job ran on the former days.
I get your point and therefore simply disabled compression for now,
which was responsible the error mails from cron.
> Also thinking about your
Public bug reported:
I've additionally described that problem on some other topic on SO:
https://superuser.com/questions/1214566/why-does-the-behaviour-of-find-
differ-using-daystart-and-mtime-0-vs-0
My web apps hosted by Tomcat7 log into /var/log/tomcat7 as well, with
the only difference that
Public bug reported:
> Unescaped left brace in regex is deprecated, passed through in regex; marked
> by <-- HERE in m/\"%{ <-- HERE Referer}i\"/ at /usr/lib/cgi-bin/awstats.pl
> line 9043.
> Unescaped left brace in regex is deprecated, passed through in regex; marked
> by <-- HERE in m/\"%{
