See this long thread on the gcc list for issues with that CVE:
http://gcc.gnu.org/ml/gcc/2008-04/msg00115.html
Later,
Brad
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
> So, in most cases, I'd rather much more have a partial dump of the file that
> changed (normally a log file), than having to exclude it from the dump just
> to stop Amanda from complaining and then have no log file at all in case of a
> disaster.
>
> Anyway, if you don't think this is a goo
Claudio Martins wrote:
Hi again,
I dug a little in Amanda code and found the reason why it was still
complaining about Strange dumps, even though the behavior with respect to tar
exit codes had been fixed.
Please consider including the patch below on the next Debian Amanda packages
relea
Can we expect this update to migrate into testing soon?
The versions of tar and amanda in testing conspire to make backups of
busy systems a problem due to tar's behavior change when it comes to
changed files. 2.5.1p3 fixes amanda to cope with this change.
According to http://bjorn.haxx.se/d
4 matches
Mail list logo
