Cristian Rodríguez wrote:

On 19/08/09 18:57, Sandy Drobic wrote:

...

At least for Opensuse 11.0 64bit the build is still broken.

what you show here, is a different issue, you are still running old 5.2.x mysql module against a new PHP 5.3.x version, this does not work, and the package manager will not let you to upgrade that way.

The only command I executed was "zypper update". It ran without a complaint. Here's the output of the installed php and mysql rpms: rpm -qa | grep mysql libmysqlclient15-5.0.51a-27.2 perl-DBD-mysql-4.006-41.1 libmysqlclient-devel-5.0.51a-27.2 mysql-5.0.51a-27.2 libmysqlclient_r15-5.0.51a-27.2 mysql-client-5.0.51a-27.2 php5-mysql-5.3.0-31.2 rpm -qa | grep php php5-openssl-5.3.0-31.2 php5-gd-5.3.0-31.2 php5-zlib-5.3.0-31.2 php5-json-5.3.0-31.2 php5-bz2-5.3.0-31.2 php5-tokenizer-5.3.0-31.2 php5-hash-5.3.0-31.2 php5-ctype-5.3.0-31.2 php5-sqlite-5.3.0-31.2 php5-mbstring-5.3.0-31.2 php5-xmlwriter-5.3.0-31.2 php5-iconv-5.3.0-31.2 php5-xmlreader-5.3.0-31.2 php5-5.3.0-31.2 php5-mcrypt-5.3.0-31.2 php5-dom-5.3.0-31.2 selfphp-4.1-85.1 php5-zip-5.3.0-31.2 php5-imap-5.3.0-31.2 apache2-mod_php5-5.3.0-31.2 phpMyAdmin-3.2.0-1.1 php5-pdo-5.3.0-31.2 php5-gettext-5.3.0-31.2 php5-mysql-5.3.0-31.2 The php_mysql module is still broken on my box. This message came after I restarted the apache server and executed the connection script: PHP Warning: Cannot load module 'mysql' because required module 'mysqlnd' is not loaded in Unknown on line 0 [Thu Aug 20 08:55:19 2009] [notice] Apache/2.2.8 (Linux/SUSE) mod_ssl/2.2.8 OpenSSL/0.9.8g PHP/5.3.0 configured -- resuming normal operations /usr/sbin/httpd2-prefork: symbol lookup error: /usr/lib64/php5/extensions/mysqli.so: undefined symbol: _mysqlnd_palloc_rinit By the way, what made the php team decide to upgrade the version? Was the maintenance of the old version too much work? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Cristian Rodríguez wrote:

On 20/08/09 03:04, Sandy Drobic wrote:

...

By the way, what made the php team decide to upgrade the version? Was the maintenance of the old version too much work?

It is always too much work in the long term to keep non-latest-stable versions.

The shorter maintenance period of 18 month will counter that quite a bit, I think. On the other hand I am VERY glad that this was not a critical production machine, just my private server installation.

The error you mention has been fixed too.

Confirmed, the mysql_connect funktion works again. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Cristian Rodríguez wrote:

On 20/08/09 10:24, Sandy Drobic wrote:

...

The shorter maintenance period of 18 month will counter that quite a bit, I think. On the other hand I am VERY glad that this was not a critical production machine, just my private server installation.

You shouldnt use server:php repository in production machines unless you reallly know what are you doing.. it may break at anytime.

Now that you say it, it probably is the reason why I don't have the repository active on my production machines. (^-^) I only use the php script to display the most recent entries of rejected mails. Though I will check the rest of the php applications in the next days. Thanks for your fast help here. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On 20/08/09 15:39, Anthony Simonelli wrote:

Are you advising not to use this repository?

Im advising to use it with care, most OBS repositories are intented for development.

If the answer is only the official SuSE repositories, how do I get such applications for my server?

This repositories generally work, but the only supported are the official ones. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On 20/08/09 17:32, Hans Witvliet wrote:

But do you mean, one can not safely use the 11.1_repo's under server, network, filesystems, Apache, Apache: mozilla,.....????

Again, they work, most of the time, but they are not supported, that does not mean that bugs will not be fixed or that you shouldn't fill bug reports. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Fri, 2009-08-21 at 08:46 +0200, Andreas Jaeger wrote:

On Thursday 20 August 2009 23:37:01 Cristian Rodríguez wrote:

...

On 20/08/09 17:32, Hans Witvliet wrote:

...

But do you mean, one can not safely use the 11.1_repo's under server, network, filesystems, Apache, Apache: mozilla,.....????

Again, they work, most of the time, but they are not supported, that does not mean that bugs will not be fixed or that you shouldn't fill bug reports.

Nothing is supported - you will not get a support contract for openSUSE 11.1 either. ;)

The question here is I think more of trust - can we trust every package that is in the build service? I would trust factory and its devel projects more than e.g. home projects since the former undergo review by others,

Hi Andreas,Christiam, Jim,.. Jim, no, it's not a question of official support. If people want that, i allways recommend them to use SLE instead of "open_*". It is indeed a question of trust. AFAICR, everything that ends without a build-failure will appear for everybody to see on the OBS (Yes, one has to enable to make it global vissible) But this means the only criterea currently, is wether it compiles ok or not. That is certainly not enough to place any trust in. Let me give you one example: RPM's for apache2-mod_auth_kerb-* can _ONLY_ be fond on the OBS. They are not on the dvd, or in the only-distro, only on the OBS, the place I assume i can trust in repositories/Apache:/Modules/openSUSE_11.1/x86_64 and a some highly volatile places in obs-users-home-directories. I'm gratefull if people are willing to look at any issue's reported in bugzilla that only resides on the OBS. Wasn't even expecting this! But outside the obvious (!) testing areas, i was expecting something more than: "It builds, so here it is!". Same with the php-issue (or any other): packages that "might work" should only be found in factory, devel, home/ etc etc. Does that sound unreasonable? I stopped building my own rpm's simply because they are available on the oBS. But now i wonder wether that was a good move. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On 21/08/09 15:24, Jim Henderson wrote:

I understand what you're saying, I just see it differently. Some people use OBS to maintain packages for their own installation and don't do extensive testing with them.

This is how I personally do this packages. 1. Build 2. Roll them in a real life enviroment. 3. See how broken they are. 4. debug an/or fix the problems. 6. GOTO 1 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On 21/08/09 16:10, Jim Henderson wrote:

Yeah, and probably many do the same sort of thing - but how many environments are tested?

Only 64bit openSUSE 11.1 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

All, Am I right in believing OBS does not have a self rating quality indicator? ie. Sourceforge lets the maintainer specify the quality level - alpha / beta / production. It seems we should have something similar in obs. I believe the server:databases repository has multiple sub-tiers based on the quality of what the maintainer thinks is in there. In this case he could tag his stable branch, etc. appropriately. Then the obs search tool could have the ability to only search for "stable" releases, or "tested" releases or whatever is the nomenclature is. Currently there is no good way to know what the packager thinks of what is in the various repos. Greg -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Fri, 21 Aug 2009 21:56:46 +0200, Hans Witvliet wrote:

From what you write, i conclude you agree with me 101%; As you write: "...for their own installation..."

Well, I didn't really comment about those that are outside the "home directories", so I don't see how you read agreement into what I said. In fairness, I never really knew there was an area outside the home directories. Given that there is (apparently), it again would come down to understanding how much testing goes into those repositories. As I wrote to Christian a minute ago, there are so many permutations of repos that can be selected, is it a reasonable assumption that they're all tested with each other on all platforms? Maybe, maybe not, but that's a judgment call I think each user should make. That's not to say they shouldn't make it without some understanding of how things are done. Suppose I install only from official repos, but I want the nxclient RPM from nomachine.com - does that now invalidate the *entire* configuration from being "official" in some way?

All i'm saying is that for those general projects a (much) higher standard of quality / stability should be observed.

Now *that* I don't disagree with, so long as those general projects are managed in an appropriate manner. Jim -- Jim Henderson Please keep on-topic replies on the list so everyone benefits -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org