Mailinglist Archive: opensuse (1495 mails)
| < Previous | Next > |
Re: [opensuse] Re: Why am I getting 14.6G zypper.log files?
- From: Rodney Baker <rodney.baker@xxxxxxxxxxxx>
- Date: Sat, 4 Apr 2009 16:57:41 +1030
- Message-id: <200904041657.51564.rodney.baker@xxxxxxxxxxxx>
On Fri, 3 Apr 2009 06:05:52 Jan Kupec wrote:
That is true - I could have been more specific about which bug I was referring
to as being marked WONTFIX (although I thought it was clear).
The fix is also ridiculously trivial and therefore would be easy to roll out
as an update (for those who can't fix it themselves).
But the comments on bug 487613 suggested that the symptoms were triggered by
the problem detailed in bug 46987.
Quoting yourself (Jan) from c#7 on #487613, "...The size suggests that there
was some kind of erroneous massive logging, i suspect bug 469872 (fixed, an
update for 11.1 is pending). So the file has grown up in very short time, well
before cron could execute logrotate."
And again on c#9, "OK, thanx. Note that until you apply the fix of bug 469872,
which is yet to be released, the log can eventually grow again (it happens on
network timeouts)."
Buf if the fix for 469872 is not to be release for 11.0 how can we apply it?
Since bug 487613 was reported for 11.0 (not 11.1) it follows logically that
469872 more than likely also applies to 11.0 (even though it was reported
under 11.1), therefore the fix for 11.1 should also be applied to 11.0. If
that is not the case, then 487613 is more likely *not* related to 469872...
Regards,
Rodney.
--
===================================================
Rodney Baker VK5ZTV
rodney.baker@xxxxxxxxxxxx
===================================================
Jim Henderson wrote:
On Wed, 01 Apr 2009 01:04:37 +1030, Rodney Baker wrote:
(it is
marked as WONTFIX for 11.0).
*And* *here* *we* *go* *again*.
Not directed at you, Rodney, but can someone PLEASE explain why critical
issues aren't being fixed in 11.0? I thought 11.0 was still being
supported.
Just a misunderstanding, Rodney did not say which of the two bugs is
marked wontfix.
That is true - I could have been more specific about which bug I was referring
to as being marked WONTFIX (although I thought it was clear).
bug 487613 is far from being critical. Read the comments there.
The fix is also ridiculously trivial and therefore would be easy to roll out
as an update (for those who can't fix it themselves).
bug 469872 is, and it will be released for 11.1. But we did not consider
releasing it for 11.0 so far (also, nobody reported the bug for 11.0).
Did it happen to you on 11.0? If so, post a comment to that bug, so that
we know.
But the comments on bug 487613 suggested that the symptoms were triggered by
the problem detailed in bug 46987.
Quoting yourself (Jan) from c#7 on #487613, "...The size suggests that there
was some kind of erroneous massive logging, i suspect bug 469872 (fixed, an
update for 11.1 is pending). So the file has grown up in very short time, well
before cron could execute logrotate."
And again on c#9, "OK, thanx. Note that until you apply the fix of bug 469872,
which is yet to be released, the log can eventually grow again (it happens on
network timeouts)."
Buf if the fix for 469872 is not to be release for 11.0 how can we apply it?
Since bug 487613 was reported for 11.0 (not 11.1) it follows logically that
469872 more than likely also applies to 11.0 (even though it was reported
under 11.1), therefore the fix for 11.1 should also be applied to 11.0. If
that is not the case, then 487613 is more likely *not* related to 469872...
So you see, your post is completely wrong. Before accusing somebody of
doing something bad, try harder to understand what are you talking about.
Links for your convenience:
https://bugzilla.novell.com/show_bug.cgi?id=469872
https://bugzilla.novell.com/show_bug.cgi?id=487613
Regards,
Rodney.
--
===================================================
Rodney Baker VK5ZTV
rodney.baker@xxxxxxxxxxxx
===================================================
| < Previous | Next > |