Re: [opensuse] What happened to mysql? Broken after latest updatefrom BS::/server/database.

David,

...

...

On 4/14/2009 at 12:04, "David C. Rankin" wrote: Probable cause: Lack of sleep from trying to help my favorite distro keep from going over a cliff.

Sleep can be a very good thing and I'm quite sure it helps reducing frustration for everybody.

Further, and in direct response to your statement above, can you please explain to me what is wrong with me using http://download.opensuse.org/repositories/server:/database/ as a repository on my system? I do make heavy use of server apps and do like to stay current with changes so I don't experience culture shock with the wave of changes that come with each new releases. It softens the blow so to speak.

nothing directly 'wrong' with it, BUT: it's a community repository. not maintained with the same QA as openSUSE base repoistories and update repositories. As such, some packages might be published untested. I for example build plenty of packages in OBS (not the ones you were affected yet by luckily) but I have only 2 computers I can test them on, running OSS 11.1 and another one Factory. And in many apps, due to lack of knowledge, I couldn't possibly test if every single feature is working.

Next, also let me know, if it is no longer proper or appreciated for members of the community to try the new packages out and identify any problems with them. I always thought that was rather helpful so that any problem could be corrected and prevented from propagating into the next release. If that's not OK anymore, I'll stop and let someone else do it.

It is PERFECT if the community members help identity problems and REPORT them in a friendly manner, brought to the points, with simple facts. And as you're TESTING, I would say you should even EXPECT breakage (otherwise you would expect them already to be tested!)

I've been managing my boxes in the same manner, with a number of repositories since at least 10.0 (I don't think we had near the number of repos with 8.0-9.3), but it has only been in the last 6 months that packages seem to be broken on a regular basis. I find and document the problems and I find them, put the information out on the list for peer review, and file bug reports when appropriate. I really fail to see an issue with that.

The more repositories, the higher the chances of conflicts. Especially, as most repositories are no longer just 'additional' software but they start replacing base libraries. Just wait for one that will replace glibc on openSUSE 10.3 (this might actually be requested. VLC 1.0-pre1 for example does not compile on 10.3 due to a bug in glibc. And the 'community' is not strong enough (yet) to backport such extensive fixes and will probably just end up creating an updated package...) So as a resume: Keep up the testing work and reporting, but don't forget to get a healthy portion of sleep once in a while. Try to make the mails and reports as helpful as possible. Even if you're annoyed by another breakage: try to stay relaxed when writing a bug report. Maybe it helps to not 'just write' it when you see it, but reflect on it a bit. A report that does not attach a packager from the very beginning on but tells me what is wrong (be it with or without patch) is more likely to get attention than one that calls the packager a fool for not having remarked it by himself (NO: I do NOT say that you told somebody he was a fool! This is just an example to stress the point). Dominique -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org