Mailinglist Archive: opensuse (1495 mails)

[Jan Kupec <jkupec@xxxxxxx>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Rodney Baker wrote:
> On Fri, 3 Apr 2009 06:05:52 Jan Kupec wrote:
> > 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).

Yes it's trivial. But the fix is one thing, rolling it out is another.
We really can't afford back-porting of fixes to minor problems, due to
resources it consumes and due to the risk of break something in the process.

But rest assured we do consider whether to release an update carefully.

> > 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?

Please note that this discussion with Robert Williams that i had in bug
487613 lead us to conclusion that his problem was actually bug 469872.
And Robert was on 11.1 (see comment #2 in 487613). Really, so far
_nobody_ said that this rapid growth of zypper.log happens also on 11.0
(still, we're considering to release 469872)!

One more time to sum it up:
bug 487613 - zypp-refresh.log not rotated - _slowly_ grows, nothing
serious, affects 11.0.
bug 469872 - zypper.log grows to gigabytes in few seconds! Critical.
Reported on 11.1 only.

I hope i dissolved also the last traces of misunderstanding now :O)

> 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 

No, as noted above these two bugs are completely unrelated.

> 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...

Yes, exactly, they're not related at all.

- --
cheers,
jano


 Ján Kupec
 YaST team
- ---------------------------------------------------------(PGP)---
 Key ID: 637EE901
 Fingerprint: 93B9 C79B 2D20 51C3 800B  E09B 8048 46A6 637E E901
- ---------------------------------------------------------(IRC)---
 Server: irc.freenode.net
 Nick: jniq
 Channels: #zypp #yast #suse #susecz
- ---------------------------------------------------------(EOF)---
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.11 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

iEYEARECAAYFAknZ6ggACgkQgEhGpmN+6QGEpwCfT7cL1IldXsfc91Q1LxH4du43
tcoAniBjnfQ9EXFgOl8sesejUOmG3Xl0
=I2u0
-----END PGP SIGNATURE-----
-- 
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx