is this RC?

Hello Due to unknown reasons I received the last two weeks only Debian mailing list mails but none from bug reports - they were stored on master instead :-(( So I missed a bug report agains mysql-server that tells me: /home/gchavdarov/mysql32/mysql-3.22.32# dpkg-buildpackage dpkg-buildpackage:

another ugly thing. RC or not?

Hi I've encountered another ugly thing. In this case not RC but I never saw it before and if debconf has changed, maybe other things are broken, too. Why do I get those error messages, that I didn't get 2 weeks ago and is a simeple recompile enough and accepted for frozen? bye, -christian-

when's a security fix grave enought for slink

Hello After the defacing of the apache web site using a spied mysql root password and then mysql to create a /root/.tcsh I was asked by a user if I don't like to backport the current mysql to slink as it is able to run under a non-root UID. I think it is not grave enough, but what do you think?

Re: is this RC?

On Sun, May 21, 2000 at 12:28:54AM +0200, Christian Hammers wrote: Now the problem is that not only the user but also the autobuilders for sparc etc. cannot build my server packages. Is that release critical? I believe so. We aim to provide working source as part of the license conditions.

Re: is this RC?

On Sun, 21 May 2000, Christian Hammers wrote: /home/gchavdarov/mysql32/mysql-3.22.32# dpkg-buildpackage dpkg-buildpackage: source package is mysql dpkg-buildpackage: source version is 3.22.32-1 dpkg-buildpackage: source maintainer is Christian Hammers [EMAIL PROTECTED] debian/rules clean

Problems with shared lib (-fPIC)

Hi. I'm having problems compiling a shared python extention, because lintian keeps complaining about foo.so not being compiled with the -fPIC option, but IT IS, as you can see from the output: --- cut --- Making all in compiled make[3]: Entering directory