Bug 188587

The problem are not the few new lines, the problems are to make a working update.
So we decides already more than once not to do so.

(In reply to comment #1)
> The problem are not the few new lines, the problems are to make a working
> update.

There were already several requests for this (bug 143648, bug 151692) and also some people built the package on their own without filing a bugzilla.

Thorsten, please at least explain what "update problems" you know or expect.
(Maybe I or someone else can help - but I need to know the problem first ;-)

Also consider to provide the package FTP-only with a big fat warning "this is unsupported, expect update problems!" in the description.
This would be ways better than forcing people to patch the specfile and rebuild the package on their own which is more error-prone (and will probably cause the same update problems too).


For those who need the package, I just created it in the build service:   
    http://software.opensuse.org/download/home:/cboltz/
It's the package from 10.1 + Christian's specfile patch + mysql-devel added to BuildRequires.  (Since the BuildService doesn't support to have a version per distribution (yet?), don't expect me to do a version upgrade soon. I need the package for 10.1 ;-)
(Christian, feel free to test the package. In case you find any problem, please drop me a note.)

I use mysql-authentication for courier-imap (together with mysql lookup for exim as MTA, see bug 188586) in a productive environment on a suse 9.3 box. 
Using a mysql-db is a really good thing for virtualuser mailsystems! 

There could be issues with updating: the config-file and directory layout changes with this release. 
But this is true for ldap-authentication too, which is provided in the suse rpm.

thanks for the BuildService. Could you provide this for the exim package too?

I explained it already more than once: You have to make sure that with database updates all data will be converted and you will not lose any data.
And as we know with other packages: this is nearly impossible.

(In reply to comment #4)
> I explained it already more than once: You have to make sure that with 
> database updates all data will be converted and you will not lose any data.

This problem is already handled in the mysql package for all databases. This includes the user database for courier-authlib for free ;-)

> And as we know with other packages: this is nearly impossible.

Like with the postfix-mysql package? *SCNR*
(it uses the same database if setup properly - and is shipped with SUSE Linux. ;-)

I had (nearly - bug 188134) no problems with MySQL upgrades yet (since SUSE Linux 7.0!), so I don't see why this should be impossible.

And: There's no advantage in forcing the user to patch the specfile - there will probably be the same "update problems" (if any).
The only difference: currently, it's a self-compiled package, there's no support from SUSE for it. But you could also do this by adding an "unsupported" note to the package and save your users lots of work.


# rpm -qpl courier-authlib-mysql-0.58-1.1.i586.rpm
/usr/lib/libauthmysql.so -> libauthmysql.so.0.0.0
/usr/lib/libauthmysql.so.0 -> libauthmysql.so.0.0.0
/usr/lib/libauthmysql.so.0.0.0
/usr/share/doc/packages/courier-authlib-mysql
/usr/share/doc/packages/courier-authlib-mysql/README.authmysql.myownquery

I don't see any file that could cause problems or data loss here, just a *.so with its symlinks and a README. There's no default configuration included, so there's nothing that could break *eg*

That's the difference: As community you don't need to care about such things, we do.

Please Thorsten, can you explain shortly a situation which will lead to data loss (or loss of functionality] . Then i have no problem to agree with the decision not to include a possibly dangerous feature. 
Do you speak about security updates of the packages (mysql or courier) or of release upgrades (10.0 to 10.1)?

I speak about update from older distributions to newer one, if the mysql libraries, interfaces and other stuff changes.
Something which happens from time to time, even if not everybody runs into this issues. But some people did.

Doest this not affect any package which uses mysql? And there are quite a few of them shipped with Suse:
- pure-ftpd (with mysql userdb)
- cyrus-sasl-sqlauxprop (with mysql support)
- postfix-mysql
- lighttpd-mod_mysql_vhost
...
Why makes the situation for these packages different?

It isn't really different, some maintainers have more time to write code to workaround the update problems, but in most cases we declared the update of this packages as unsupported. What doesn't make customers, who wished this feature, not really happier.

Thorsten, I [start to] understand why you don't want the -mysql package ;-)
I would volunteer as co-maintainer, but unfortunately my knownledge of C programming is nearly nonexisting :-(

Could you at least include the required lines in the specfile _commented out_ (+ a link to this bug for explanation)? This shouldn't hurt you regarding support, but makes recompiling easier.

since some hours, this bug has a wrong status ;-)

http://lists4.opensuse.org/opensuse-commit/2006-08/msg00007.html

--- courier-authlib/courier-authlib.changes 2006-03-27 11:54:10.000000000 +0200
 +++ courier-authlib/courier-authlib.changes 2006-08-01 12:15:31.000000000 +0200
 @@ -1,0 +2,5 @@
 +Tue Aug 1 12:14:40 CEST 2006 - mskibbe@xxxxxxx
 +
 +- Add mysql, pipe, pgsql sub-packages 

-> Fixed for 10.2 :-)

cOOl :-) Thanks!