with the current qmail-mysql ebuild "qmail-getpw" output looks like darookee1001369 but it should be something like darookee1001100/var/toaster/darookee the patch and the new ebuild fixes this problem Reproducible: Always Steps to Reproduce: 1. cd /var/qmail/bin 2. ./qmail-getpw username Actual Results: the wrong output was given user1001369 Expected Results: give the right output user1001100/home/user Portage 2.0.47-r10 (default-x86-1.4, gcc-3.2.2, glibc-2.3.1-r4) ================================================================= System uname: 2.4.19 i686 AMD Athlon(tm) Processor GENTOO_MIRRORS="http://ftp.snt.utwente.nl/pub/os/linux/gentoo/ http://gentoo.oregonstate.edu/ http://www.ibiblio.org/pub/Linux/distributions/gentoo" CONFIG_PROTECT="/etc /var/qmail/control /usr/share/config /usr/kde/2/share/config /usr/kde/3/share/config /usr/X11R6/lib/X11/xkb" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" PORTDIR="/usr/portage" DISTDIR="/usr/portage/distfiles" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR_OVERLAY="/usr/local/portage" USE="x86 oss 3dnow apm arts avi crypt cups encode gif imlib jpeg kde gnome libg++ mikmod mmx motif mpeg ncurses nls oggvorbis pdflib png quicktime sdl spell svga truetype xml2 xmms xv zlib gdbm berkdb slang readline java mysql X gpm tcpd pam libwww ssl perl python gtk qt opengl ldap" COMPILER="gcc3" CHOST="i686-pc-linux-gnu" CFLAGS="-mcpu=athlon-tbird -O3 -pipe" CXXFLAGS="-mcpu=athlon-tbird -O3 -pipe" ACCEPT_KEYWORDS="x86" MAKEOPTS="-j2" AUTOCLEAN="yes" SYNC="rsync://rsync.gentoo.org/gentoo-portage" FEATURES="sandbox ccache"
Created attachment 11867 [details, diff] the patch to fix the bug... it moves the mysql disconnect line in qmail-getpw.c
Created attachment 11868 [details] the new ebuild including patching with the fix-patch... just copy it into your overlay dir and emerge it...
thanks for this. I'm re-writing the qmail ebuilds soon, so is going to get included in there.
What's the status of this?
ok, qmail-mysql-1.03-r13 is now in place. it _should_ work. It's based on my qmail-1.03-r13 package. I've integerted your patch into the latest upstream patch. I've hardmasked it as I don't have a setup to test it out myself (my qmail setup is too production to test this out). Please give it a whirl and report back here. I'm going to pass your patch upstream as well.
upstream reports the offical fix for this problem is actually included in his 1.1.9 patch, so i'll be reverting to just the 1.1.9 patch and not your extra patch.
clearing up my bug tracking
So what's happening with this bugreport now? patches proposed are from 2003 and report is still open.
Hmmmm?
uhm? can we finally get rid of qmail-mysql, please? vpopmail can handle mysql quite well...
in p.mask now, going to be removed on 31 Sep 2007
done