[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: More kdebase make errors - ksysgaurd & strlcpy
From:       JW <jw () centraltexasit ! com>
Date:       2002-12-13 0:21:00
[Download RAW message or body]

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

On Thursday 12 December 2002 10:02, Jonathan Singer wrote:
> (We're talking about a reasonably normal Linux system, right? 

Yes

> 1) A transient bug that wil quickly get caught. Wait a few hours or a day
> and update and try again. This will fix most of them. Don't bother telling
> anyone about it -- if you're curious, you may want to go to one of the KDE
> channels on irc.openprojects.net and asking if others are seeing it. Also,
> do a 'make clean' or 'make -f admin/Makefile cvs-clean'.
>
> 2) If it's still there after a few days, it's probably specific to you.
> Probably you need to delete old moc or object files or something like that.
> You can ask on the list, but I usually wait for someone else to do it for
> me (as you just did with ksysguard, which I've had problems with for days.)
> Again, try IRC first.

I see you have a little bit of a different viewpoint then I do. You're waiting 
for someone else to see it, report it, fix it. But if everyone waited on 
everyone else, a bug would never be fixed until the maintainer/author noticed 
and fixed it. So... why not report it sooner than later? It would seem like 
the sooner it's reported, the sooner it might be fixed. I see that cvs 
commits were made for ksysgaurd. While I can't be sure it was as a result of 
my saying something, it does seem likely. For example you said you've had 
probs with ksysguard for days. Don't you think, if you had repotred it "days" 
ago, that is might have been noticed & fixed sooner, and possibly it would 
have already been fixed/workign by the time I got to it? What advantage was 
the time delay between when you first noticed it and I reported it?

Another problem with "waiting an hour or a day" (beside the fact that it 
prevents me from doing what I'm trying to do at the moment I have time to do 
it) is that in the time it took for any given particular bug to be fixed, 
other have been introduced. I'm a little curious how this happens. I assume 
because developers, when testing changes they've made, do not recompile all 
of e.g. kdebase but instead compile only inside their own component. As an 
example of this, kdebase has not compiled for 4 days now (for me) - every 
time any given bug goes away, another bug shows up preventing make from 
finishing.

Are there "official" bug reporters that we should wait on or something?

> In the meantime, compile with 'make -k' and install what you can. You can
> 'make -k install' too, but it's probably safer to edit the Makefile to
> remove the offending directory.

Sadly, make -k is also failing. I assume that means there's pretty bad 
problems.

Sorry. I set out 5 days ago to compile KMail and all this time later I still 
can't, because I can't finish up with kdebase. It is somewhat disappointing.

Thanks for your time.

- -- 

- ----------------------------------------------------
Jonathan Wilson
Cedar Creek Software     http://www.cedarcreeksoftware.com

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE9+SfxQ5u80xXOLBcRAuvSAKCr174/x6OL/zmXacvqZlGzyowfxQCgigay
jQwZxJ+4cmIYgifSjJlD4Dg=
=O4uY
-----END PGP SIGNATURE-----


>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]