Hello [1st issue - dpkg symlink bug workaround]
On 2005-05-18 Roberto C. Sanchez wrote: > Quoting sean finney <[EMAIL PROTECTED]>: > <SNIP> > > so at this point, we're not sure what to do to cover this last problem, > > as we have no guarantee the preinst of mysql-server-4.1 will even run > > before mysql-server/woody is removed. the only fix we can think of is > > to remove the two directories from the files.list of the woody package. > > > > so we've come up with three options, none of which are great: > > > <SNIP> > > I may be misunderstanding what you are saying. But, I think that if you > create a package called mysql-server-4.1-upgrage (or something else > suitable) and then you make you make mysql-server-4.1 predepend on it, then > mysql-server-4.1-upgrade can check for the existence of the symlinks. No, predepends can be used to ensure that some other package has already been completely installed i.e. postinst had been executed before the depending package even gets unpackaged. But that won't help here. apt-get calculates that mysql-server (3.23) has to be removed in order to get mysql-server-4.1 installed so it would first completely remove mysql-server (3.23) and *then* maybe install your temporary package which would be as useless as our current preinst hack. As a direct upgrade from mysql-server (3.23) to mysql-server-4.1 without a prior upgrade to mysql-server (4.0) is quite unlikely, I would like to see our last upload, which in addition has some notes in README.Debian and the Debconf installation notes regarding this, to be accepted for Sarge. Relevant versions are 4.1.11a-2 and 4.0.24-10. [2nd issue - statically linked db3] The new bug #308966 explains that mysql-server and libnss-db produce segfault crashes as mysql-server until now still had the obsolete BDB engine enabled which uses a statically linked local db3 version. Thus BDB support could now complete been removed as luckily support for BDB was not present on most architectures, disabled by default and being warned at startup for a while now and will most likely be removed in 5.0 upstream anyway. I have a package ready (4.1.11a-3), do you want it for Sarge, Steve, or do we rather live with this bug? bye, -christian- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
