[gentoo-dev] mysql-bin ebuild

[gentoo-dev] mysql-bin ebuild

[Francesco Riosa]

After some testing on MySQL ebuild for version 4.1.x and 5.0.x appear to 
me that is very difficult have a stable version of those databases with 
current glibc, gcc and maybe os-headers stable defaults (at least on x86 
and amd64).

Adding a dev-db/mysql-bin package seems the only short-term viable 
solution to have those versions of mysql in portage tree. Leaving out 
all the problems that dependant packages have after mysql 4.1.3 release.

I'm going to writing an ebuild that (maybe using alternatives.eclass) 
unpack the binary distribuited version of mysql in /opt/ dir and symlink 
all the programs to paths currently used from the source dist.

any input on how to write it in a way that permit it to be included in 
the portage tree very apreciated, expecially that from Robin H. Johnson 
a.k.a robbat2

ciao
Francesco

--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] mysql-bin ebuild

[Robin H. Johnson]

[-- Attachment #1: Type: text/plain, Size: 1581 bytes --]

On Tue, Feb 22, 2005 at 01:55:57PM +0100, Francesco Riosa wrote:
> After some testing on MySQL ebuild for version 4.1.x and 5.0.x appear to 
> me that is very difficult have a stable version of those databases with 
> current glibc, gcc and maybe os-headers stable defaults (at least on x86 
> and amd64).
> 
> Adding a dev-db/mysql-bin package seems the only short-term viable 
> solution to have those versions of mysql in portage tree. Leaving out 
> all the problems that dependant packages have after mysql 4.1.3 release.
> 
> I'm going to writing an ebuild that (maybe using alternatives.eclass) 
> unpack the binary distribuited version of mysql in /opt/ dir and symlink 
> all the programs to paths currently used from the source dist.
> 
> any input on how to write it in a way that permit it to be included in 
> the portage tree very apreciated, expecially that from Robin H. Johnson 
> a.k.a robbat2
I'd say it should be mutually exclusive of the source-built version
(DEPEND=!dev-db/mysql).  See about putting it's bindir into the PATH
instead of messing around with symlinks. However I think it should use
the same /var/lib/mysql for it's data directory.

By default it should provide the stock binaries, if USE=max, then
provide the mysql-max binaries, and if USE=debug, instead provide the
debugging binaries.

-- 
Robin Hugh Johnson
E-Mail     : robbat2@orbis-terrarum.net
Home Page  : http://www.orbis-terrarum.net/?l=people.robbat2
ICQ#       : 30269588 or 41961639
GnuPG FP   : 11AC BA4F 4778 E3F6 E4ED  F38E B27B 944E 3488 4E85

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

Re: [gentoo-dev] mysql-bin ebuild

[Francesco Riosa]

Robin H. Johnson ha scritto:

>On Tue, Feb 22, 2005 at 01:55:57PM +0100, Francesco Riosa wrote:
>  
>
>>After some testing on MySQL ebuild for version 4.1.x and 5.0.x appear to 
>>me that is very difficult have a stable version of those databases with 
>>current glibc, gcc and maybe os-headers stable defaults (at least on x86 
>>and amd64).
>>
>>Adding a dev-db/mysql-bin package seems the only short-term viable 
>>solution to have those versions of mysql in portage tree. Leaving out 
>>all the problems that dependant packages have after mysql 4.1.3 release.
>>
>>I'm going to writing an ebuild that (maybe using alternatives.eclass) 
>>unpack the binary distribuited version of mysql in /opt/ dir and symlink 
>>all the programs to paths currently used from the source dist.
>>
>>any input on how to write it in a way that permit it to be included in 
>>the portage tree very apreciated, expecially that from Robin H. Johnson 
>>a.k.a robbat2
>>    
>>
>I'd say it should be mutually exclusive of the source-built version
>(DEPEND=!dev-db/mysql).  See about putting it's bindir into the PATH
>instead of messing around with symlinks. However I think it should use
>the same /var/lib/mysql for it's data directory.
>  
>
Ok, I'll discover how to add a /etc/env.d/98mysql

>By default it should provide the stock binaries, if USE=max, then
>provide the mysql-max binaries, and if USE=debug, instead provide the
>debugging binaries.
>
>  
>
IUSE="max debug innodb berkdb selinux utf8 perl ruby"

with "max" and "debug" mutually exlusive,
"innodb" "berkdb" "selinux" "utf8"  modifying  the my.cnf file
"perl" "ruby" operating on RDEPEND
?

--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] mysql-bin ebuild

[Donnie Berkholz]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Robin H. Johnson wrote:
> I'd say it should be mutually exclusive of the source-built version
> (DEPEND=!dev-db/mysql).  See about putting it's bindir into the PATH
> instead of messing around with symlinks. However I think it should use
> the same /var/lib/mysql for it's data directory.

If you're gonna do this, I imagine there are some things that depend on
mysql so you might be best off turning it into a virtual and blocking
the virtual.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)

iD8DBQFCHiylXVaO67S1rtsRAhpmAKC2xVhAN0AIZO3MUjddwIXs9r+KtgCgohZL
DMqjhZxrdk3zx2WylAaoNQk=
=uJvg
-----END PGP SIGNATURE-----
--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] mysql-bin ebuild

[Francesco Riosa]

Donnie Berkholz ha scritto:

>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>Robin H. Johnson wrote:
>  
>
>>I'd say it should be mutually exclusive of the source-built version
>>(DEPEND=!dev-db/mysql).  See about putting it's bindir into the PATH
>>instead of messing around with symlinks. However I think it should use
>>the same /var/lib/mysql for it's data directory.
>>    
>>
>
>If you're gonna do this, I imagine there are some things that depend on
>mysql so you might be best off turning it into a virtual and blocking
>the virtual.
>  
>
Maybe after some time it has been in the tree keyworded "-*" (testing, 
testing, testing)?
Or it is a problem switch to virtual later ? Just to avoid modifing the 
source ebuild for the moment.



--
gentoo-dev@gentoo.org mailing list

[gentoo-dev] -* v.s. package.mask

[Georgi Georgiev]

I hope I am not really hijacking the thread, but:

maillog: 25/02/2005-10:18:12(+0100): Francesco Riosa types
> Maybe after some time it has been in the tree keyworded "-*" (testing, 
> testing, testing)?

What's the policy for "-*" v.s. "package.mask"? '-*' is pretty annoying
in my opinion. Is "-*" for really, really bad ebuilds or something?

-- 
\/   Georgi Georgiev   \/ If a 'train station' is where a train        \/
/\    chutz@gg3.net    /\ stops, what's a 'workstation'?               /\
\/  +81(90)6266-1163   \/                                              \/
--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] -* v.s. package.mask

[Francesco Riosa]

Georgi Georgiev ha scritto:

>I hope I am not really hijacking the thread, but:
>
>maillog: 25/02/2005-10:18:12(+0100): Francesco Riosa types
>  
>
>>Maybe after some time it has been in the tree keyworded "-*" (testing, 
>>testing, testing)?
>>    
>>
>
>What's the policy for "-*" v.s. "package.mask"? '-*' is pretty annoying
>in my opinion. Is "-*" for really, really bad ebuilds or something?
>  
>
Don't know well about gentoo policy about that, in this case, since it's 
something completely new I suggest the "-*" like a request to be tested 
from a developer on every arch before leave it at user testing.
In every case we are speaking of a still non-existing stuff.

--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] -* v.s. package.mask

[Ciaran McCreesh]

[-- Attachment #1: Type: text/plain, Size: 829 bytes --]

On Fri, 25 Feb 2005 19:13:27 +0900 Georgi Georgiev <chutz@gg3.net>
wrote:
| I hope I am not really hijacking the thread, but:
| 
| maillog: 25/02/2005-10:18:12(+0100): Francesco Riosa types
| > Maybe after some time it has been in the tree keyworded "-*"
| > (testing,  testing, testing)?
| 
| What's the policy for "-*" v.s. "package.mask"? '-*' is pretty
| annoying in my opinion. Is "-*" for really, really bad ebuilds or
| something?

-* is generally used to indicate that it's a binary package or something
similar which has no chance of working on archs that it's not keyworded
for. package.mask means maybe portable, but too broken for ~arch.

-- 
Ciaran McCreesh : Gentoo Developer (Vim, Fluxbox, shell tools)
Mail            : ciaranm at gentoo.org
Web             : http://dev.gentoo.org/~ciaranm


[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-dev] -* v.s. package.mask

[Chris Gianelloni]

[-- Attachment #1: Type: text/plain, Size: 1279 bytes --]

On Fri, 2005-02-25 at 19:13 +0900, Georgi Georgiev wrote:
> I hope I am not really hijacking the thread, but:
> 
> maillog: 25/02/2005-10:18:12(+0100): Francesco Riosa types
> > Maybe after some time it has been in the tree keyworded "-*" (testing, 
> > testing, testing)?
> 
> What's the policy for "-*" v.s. "package.mask"? '-*' is pretty annoying
> in my opinion. Is "-*" for really, really bad ebuilds or something?

Like many things in Gentoo, there is no hard and fast policy.  The
general rule is that you use -* when you don't want *anyone*
accidentally installing the ebuild.  A good example would be a newer
version of glibc that could potentially do something very nasty if the
user didn't follow the directions.  In this case, you would p.mask it
*and* use -*, to keep people who happen to have "sys-libs/glibc" in
their p.unmask.  This forces the person want to test to manually
intervene to get the package, and ensures that people running the
package *want* to run the package.

You will also see -* in binary ebuilds, as it tells people that this
will *only* work on the platforms in KEYWORDS, like KEYWORDS="-* x86
amd64" would do.

-- 
Chris Gianelloni
Release Engineering - Strategic Lead/QA Manager
Games - Developer
Gentoo Linux

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-dev] mysql-bin ebuild

[Martin Holzhauer]

hat about adding ICC to the bin ebuild for fetching the intelcompiler binaries?


On Fri, 25 Feb 2005 10:18:12 +0100, Francesco Riosa
<francesco@pnpitalia.it> wrote:
> Donnie Berkholz ha scritto:
> 
> >-----BEGIN PGP SIGNED MESSAGE-----
> >Hash: SHA1
> >
> >Robin H. Johnson wrote:
> >
> >
> >>I'd say it should be mutually exclusive of the source-built version
> >>(DEPEND=!dev-db/mysql).  See about putting it's bindir into the PATH
> >>instead of messing around with symlinks. However I think it should use
> >>the same /var/lib/mysql for it's data directory.
> >>
> >>
> >
> >If you're gonna do this, I imagine there are some things that depend on
> >mysql so you might be best off turning it into a virtual and blocking
> >the virtual.
> >
> >
> Maybe after some time it has been in the tree keyworded "-*" (testing,
> testing, testing)?
> Or it is a problem switch to virtual later ? Just to avoid modifing the
> source ebuild for the moment.
> 
> 
> --
> gentoo-dev@gentoo.org mailing list
> 
>
--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] mysql-bin ebuild

[Francesco Riosa]

Analized but no platform to test it here, maybe later

Martin Holzhauer ha scritto:

>hat about adding ICC to the bin ebuild for fetching the intelcompiler binaries?
>
>
>  
>
[snip]
--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] mysql-bin ebuild

[Francesco Riosa]

Robin H. Johnson ha scritto:

>On Tue, Feb 22, 2005 at 01:55:57PM +0100, Francesco Riosa wrote:
>  
>
>>After some testing on MySQL ebuild for version 4.1.x and 5.0.x appear to 
>>me that is very difficult have a stable version of those databases with 
>>current glibc, gcc and maybe os-headers stable defaults (at least on x86 
>>and amd64).
>>
>>Adding a dev-db/mysql-bin package seems the only short-term viable 
>>solution to have those versions of mysql in portage tree. Leaving out 
>>all the problems that dependant packages have after mysql 4.1.3 release.
>>
>>I'm going to writing an ebuild that (maybe using alternatives.eclass) 
>>unpack the binary distribuited version of mysql in /opt/ dir and symlink 
>>all the programs to paths currently used from the source dist.
>>
>>any input on how to write it in a way that permit it to be included in 
>>the portage tree very apreciated, expecially that from Robin H. Johnson 
>>a.k.a robbat2
>>    
>>
>I'd say it should be mutually exclusive of the source-built version
>(DEPEND=!dev-db/mysql).  See about putting it's bindir into the PATH
>instead of messing around with symlinks. However I think it should use
>the same /var/lib/mysql for it's data directory.
>
>By default it should provide the stock binaries, if USE=max, then
>provide the mysql-max binaries, and if USE=debug, instead provide the
>debugging binaries.
>
>  
>
- PATH & MANPATH added to /etc/env.d/98mysql
- include & lib both are simlynked, /etc/my.cnf too to avoid client 
problems.

http://bugs.gentoo.org/show_bug.cgi?id=83424
http://bugs.gentoo.org/attachment.cgi?id=52202&action=view

Best Regards,
Francesco Riosa
--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] mysql-bin ebuild

[Stuart Herbert]

On Tuesday 22 February 2005 12:55, Francesco Riosa wrote:
> After some testing on MySQL ebuild for version 4.1.x and 5.0.x appear to
> me that is very difficult have a stable version of those databases with
> current glibc, gcc and maybe os-headers stable defaults (at least on x86
> and amd64).
>
> Adding a dev-db/mysql-bin package seems the only short-term viable
> solution to have those versions of mysql in portage tree.

What is broken w/ the current stable glibc & gcc?

Best regards,
Stu
-- 
Stuart Herbert                                              stuart@gentoo.org
Gentoo Developer                                       http://www.gentoo.org/
                                                   http://stu.gnqs.org/diary/

GnuPG key id# F9AFC57C available from http://pgp.mit.edu
Key fingerprint = 31FB 50D4 1F88 E227 F319  C549 0C2F 80BA F9AF C57C
--
--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] mysql-bin ebuild

[Francesco Riosa]

Stuart Herbert ha scritto:

>On Tuesday 22 February 2005 12:55, Francesco Riosa wrote:
>
>>After some testing on MySQL ebuild for version 4.1.x and 5.0.x appear to
>>me that is very difficult have a stable version of those databases with
>>current glibc, gcc and maybe os-headers stable defaults (at least on x86
>>and amd64).
>>
>>Adding a dev-db/mysql-bin package seems the only short-term viable
>>solution to have those versions of mysql in portage tree.
>>
>
>What is broken w/ the current stable glibc & gcc?
>
>Best regards,
>Stu
>
The compiled sources from have problems with both ssl and ndbcluster, 
logs at [1], description of at [2], running the mysql bundled tests show 
various problems, from segfaults to hanging.
On the same systems, running the MySQL compiled sources goes well.
Saying that the problem is given from glibc, gcc and os-headers may be a 
limited point of view, because MySQL server and libraryes link against 
zlib, ncurses, readline, tcpwrappers, openssl too.
Anyway it's motived from bugs at [3] and seems to be not limited to 4.1 
and 5.0 series that I've tested.
The problems seems limited to the server because running a binary 
version from MySQL and connecting from a client built from my ebuilds 
goes fine.

I hope that Jeff Smelser is right saying that it's only a problem of 
mine, if so the need of a mysql-bin ebuild is drastically reduced ;)

[1] http://www.francesco-riosa.com/gentoo/old/logs/
[2] http://www.francesco-riosa.com/gentoo/old/logs/00README.txt
[3] http://bugs.mysql.com/bug.php?id=7851
    http://bugs.mysql.com/bug.php?id=7970
    http://bugs.mysql.com/bug.php?id=7971
--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] mysql-bin ebuild

[Jeff Smelser]

[-- Attachment #1: Type: text/plain, Size: 591 bytes --]

On Tuesday 22 February 2005 01:28 pm, Francesco Riosa wrote:

> I hope that Jeff Smelser is right saying that it's only a problem of
> mine, if so the need of a mysql-bin ebuild is drastically reduced ;)
>
> [1] http://www.francesco-riosa.com/gentoo/old/logs/
> [2] http://www.francesco-riosa.com/gentoo/old/logs/00README.txt
> [3] http://bugs.mysql.com/bug.php?id=7851
>     http://bugs.mysql.com/bug.php?id=7970
>     http://bugs.mysql.com/bug.php?id=7971

It says it was fixed in 4.0.24.. I am talking to a mysql dev about 4.1 and 5.. 
I will let u know what I find.

Jeff

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-dev] mysql-bin ebuild

[Francesco Riosa]

Stuart Herbert ha scritto:

>On Tuesday 22 February 2005 12:55, Francesco Riosa wrote:
>  
>
>>After some testing on MySQL ebuild for version 4.1.x and 5.0.x appear to
>>me that is very difficult have a stable version of those databases with
>>current glibc, gcc and maybe os-headers stable defaults (at least on x86
>>and amd64).
>>
>>Adding a dev-db/mysql-bin package seems the only short-term viable
>>solution to have those versions of mysql in portage tree.
>>    
>>
>
>What is broken w/ the current stable glibc & gcc?
>
>Best regards,
>Stu
>  
>
Since I'm impatient by nature ;)  I've tryed a fresh stage3 - amd64 - 
2004.3 [1] with no upgrade at all except for texinfo and libtools + 
dependancies.
All is gone straight and clean [2]. for the amd64 stuff I still need to 
upgrade to the latest stable version of the packages at [3], a work for 
tomorrow, the one with a "+" in front will be updated one by one and a 
compile/test of the mysql will be done between, so don't expect results 
too soon :( .
btw I'm thinked about the binary version of mysql in portage, it seem a 
good thing IMHO anyway, it's an alternative choice, and this may only be 
good (user side speaking;)


[1] 
http://www.francesco-riosa.com/gentoo/old/logs/OK_amd64_emerge-info-0050.txt
     
http://www.francesco-riosa.com/gentoo/old/logs/OK_x86_emerge-info-0040.txt
[2] 
http://www.francesco-riosa.com/gentoo/old/logs/mysql-4.1.10--x86_64--2.6.11-rc2-mm1--20050223-0117.txt.gz
     
http://www.francesco-riosa.com/gentoo/old/logs/mysql-4.1.11_alpha20050222--i686--2.6.8-gentoo-r3--20050222-2306.txt.gz

[3]
 [ebuild     U ] sys-devel/patch-2.5.9-r1 [2.5.9] -build -debug -static 0 kB
 [ebuild     U ] sys-libs/db-4.1.25_p1-r4 [4.1.25_p1-r3] -bootstrap -doc 
-java -nocxx -tcltk 0 kB
 [ebuild  N    ] sys-libs/gpm-1.20.1  (-selinux) 0 kB
 [ebuild     U ] sys-devel/gettext-0.14.1 [0.12.1-r2] -emacs +nls 0 kB
 [ebuild     U ] sys-apps/groff-1.19.1-r2 [1.19.1-r1] -X -debug 0 kB
 [ebuild     U ] sys-devel/libperl-5.8.5 [5.8.4-r1] +berkdb -debug -gdbm 
-ithreads (-uclibc) 0 kB
 [ebuild     U ] dev-lang/perl-5.8.5-r4 [5.8.4-r1] +berkdb -debug -doc 
-gdbm -ithreads -perlsuid (-uclibc) 0 kB
+[ebuild     U ] sys-devel/binutils-2.15.92.0.2-r1 [2.15.90.0.1.1-r3] 
-bootstrap -build -debug (-multitarget) +nls (-uclibc) 0 kB
+[ebuild     U ] sys-devel/bison-1.875d [1.875] -debug +nls -static 0 kB
+[ebuild     U ] sys-libs/zlib-1.2.2 [1.2.1-r3] -build -debug 0 kB
 [ebuild     U ] app-arch/bzip2-1.0.2-r5 [1.0.2-r3] -build -debug 
-static 0 kB
+[ebuild     U ] dev-libs/openssl-0.9.7e [0.9.7d-r1] -debug -emacs 
(-uclibc) 0 kB
 [ebuild     U ] dev-libs/expat-1.95.8 [1.95.7] -test 0 kB
 [ebuild     U ] dev-lang/python-2.3.4-r1 [2.3.4] -X +berkdb -bootstrap 
-build -debug -doc -gdbm +ipv6 +ncurses +readline +ssl -tcltk -ucs2 0 kB
 [ebuild     U ] sys-apps/portage-2.0.51-r15 [2.0.51-r2] -build -debug 
(-selinux) 0 kB
 [ebuild     U ] sys-devel/gcc-config-1.3.10-r1 [1.3.6-r3] 0 kB
+[ebuild  NS   ] sys-devel/gcc-3.4.3-r1  -bootstrap -boundschecking 
-build -debug +fortran -gcj -gtk -hardened (-ip28) +multilib -multislot 
(-n32) (-n64) +nls -nocxx -objc -static (-uclibc) 0 kB
 [ebuild     U ] sys-libs/libstdc++-v3-3.3.4 [3.3.3-r1] -debug +nls 0 kB
 [ebuild     U ] sys-apps/gawk-3.1.3-r2 [3.1.3-r1] -build +nls (-uclibc) 
0 kB
 [ebuild     U ] sys-libs/pam-0.77-r6 [0.77-r1] +berkdb -debug -pwdb 
(-selinux) 0 kB
+[ebuild     U ] sys-kernel/linux26-headers-2.6.8.1-r2 [2.6.6-r1] -build 
0 kB
 [ebuild  N    ] app-crypt/hashalot-0.3  0 kB
 [ebuild     U ] sys-apps/util-linux-2.12i-r1 [2.12-r4] +crypt* -debug 
+nls +pam +perl (-selinux) -static 0 kB
 [ebuild     U ] sys-apps/baselayout-1.9.4-r7 [1.9.4-r6] -bootstrap 
-build -debug -livecd (-selinux) -static (-uclibc) 0 kB
+[ebuild     U ] sys-libs/glibc-2.3.4.20041102 [2.3.4.20040808-r1] 
-build -debug -erandom -hardened +multilib +nls -nomalloccheck -nptl 
-nptlonly -pic +userlocales* 0 kB
 [ebuild     U ] sys-apps/man-1.5p [1.5m-r2] -debug +nls 0 kB
 [ebuild     U ] sys-apps/man-pages-2.01 [1.67] 0 kB
 [ebuild     U ] sys-apps/kbd-1.12-r3 [1.12-r2] +nls 0 kB
 [ebuild     U ] sys-apps/procps-3.2.4-r2 [3.2.3-r1] -debug 0 kB
 [ebuild     U ] app-arch/gzip-1.3.5-r5 [1.3.5-r2] -build -debug +nls 
-pic -static 0 kB
 [ebuild     U ] sys-apps/file-4.12 [4.10] -build -debug +python 0 kB
 [ebuild     U ] sys-apps/psmisc-21.5 [21.4] +nls (-selinux) 0 kB
 [ebuild     U ] app-arch/cpio-2.6-r1 [2.5] +nls 0 kB
+[ebuild  N    ] dev-perl/Locale-gettext-1.03  0 kB
 [ebuild     U ] sys-apps/help2man-1.33.1 [1.29] +nls 0 kB
 [ebuild     U ] sys-apps/coreutils-5.2.1-r4 [5.2.1] -acl -build -debug 
+nls (-selinux) -static (-uclibc) 0 kB
 [ebuild     U ] sys-apps/shadow-4.0.5-r3 [4.0.4.1-r3] -debug +nls +pam 
(-selinux) -skey 0 kB
+[ebuild     U ] net-misc/openssh-3.9_p1-r1 [3.8.1_p1-r1] -X509 -chroot 
-debug +ipv6 -kerberos -ldap +pam (-selinux) -sftplogging -skey 
-smartcard -static +tcpd (-uclibc) 0 kB
 [ebuild     U ] sys-apps/ed-0.2-r6 [0.2-r4] 0 kB

--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] mysql-bin ebuild

[Jeff Smelser]

[-- Attachment #1: Type: text/plain, Size: 841 bytes --]

On Tuesday 22 February 2005 06:55 am, Francesco Riosa wrote:

> After some testing on MySQL ebuild for version 4.1.x and 5.0.x appear to
> me that is very difficult have a stable version of those databases with
> current glibc, gcc and maybe os-headers stable defaults (at least on x86
> and amd64).

Really?? I dont see this.. Please tell me and I will talk to the mysql Dev's 
to figure this out.. They have relayed nothing of this.. Unless your talking 
gcc-3.4 or something.

> Adding a dev-db/mysql-bin package seems the only short-term viable
> solution to have those versions of mysql in portage tree. Leaving out
> all the problems that dependant packages have after mysql 4.1.3 release.

Why are we the only people having problems with this release? Help me 
understand this so we can get this figured out.

Jeff

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-dev] mysql-bin ebuild

[Francesco Riosa]

Jeff Smelser ha scritto:

>On Tuesday 22 February 2005 06:55 am, Francesco Riosa wrote:
>
>  
>
>>After some testing on MySQL ebuild for version 4.1.x and 5.0.x appear to
>>me that is very difficult have a stable version of those databases with
>>current glibc, gcc and maybe os-headers stable defaults (at least on x86
>>and amd64).
>>    
>>
>
>Really?? I dont see this.. Please tell me and I will talk to the mysql Dev's 
>to figure this out.. They have relayed nothing of this.. Unless your talking 
>gcc-3.4 or something.
>
>  
>
>>Adding a dev-db/mysql-bin package seems the only short-term viable
>>solution to have those versions of mysql in portage tree. Leaving out
>>all the problems that dependant packages have after mysql 4.1.3 release.
>>    
>>
>
>Why are we the only people having problems with this release? Help me 
>understand this so we can get this figured out.
>
>Jeff
>  
>
Jeff have you logged the output of
FEATURES="maketest" emerge mysql
and grepped it with
grep --color --regexp="\(\[ fail \]\|\[ pass \]\|\[ skipped \]\)"
?
Currently the function src_test() that run the MySQL tests have a forced 
"OK" result, since it is still in a beta stage.

grepping the results may show if there are failed tests.

... and if you are not using strange new stuff like ndb_cluster, don't 
worry, I'm using it as a production system from more than one year now 
;) only be sure to thest it very well before going to use it.

Cheers Francesco

--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] mysql-bin ebuild

[Jeff Smelser]

[-- Attachment #1: Type: text/plain, Size: 900 bytes --]

On Tuesday 22 February 2005 01:35 pm, you wrote:

> Jeff have you logged the output of
> FEATURES="maketest" emerge mysql
> and grepped it with
> grep --color --regexp="\(\[ fail \]\|\[ pass \]\|\[ skipped \]\)"
> ?

No, next build i can though..

> Currently the function src_test() that run the MySQL tests have a forced
> "OK" result, since it is still in a beta stage.
>
> grepping the results may show if there are failed tests.
>
> ... and if you are not using strange new stuff like ndb_cluster, don't
> worry, I'm using it as a production system from more than one year now
> ;) only be sure to thest it very well before going to use it.

Well, i did find the bug, and the dev I talked to said he knows about it and 
is being pushed for next release. 

Here is his reply:

Fixed in 4.1.11 and 5.0.3 as far as I can see in the source (renamed to 
internal_*)

Jeff

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-dev] mysql-bin ebuild

[Francesco Riosa]

Jeff Smelser ha scritto:

>On Tuesday 22 February 2005 01:35 pm, you wrote:
>
>  
>
>>Jeff have you logged the output of
>>FEATURES="maketest" emerge mysql
>>and grepped it with
>>grep --color --regexp="\(\[ fail \]\|\[ pass \]\|\[ skipped \]\)"
>>?
>>    
>>
>
>No, next build i can though..
>
>  
>
>>Currently the function src_test() that run the MySQL tests have a forced
>>"OK" result, since it is still in a beta stage.
>>
>>grepping the results may show if there are failed tests.
>>
>>... and if you are not using strange new stuff like ndb_cluster, don't
>>worry, I'm using it as a production system from more than one year now
>>;) only be sure to thest it very well before going to use it.
>>    
>>
>
>Well, i did find the bug, and the dev I talked to said he knows about it and 
>is being pushed for next release. 
>
>Here is his reply:
>
>Fixed in 4.1.11 and 5.0.3 as far as I can see in the source (renamed to 
>internal_*)
>
>Jeff
>  
>
tomorrow morning I'll run an update to the bk sources and try again, for 
both 4.1 and 5.0, the ebuilds should be out at 16:00 CET time.

Francesco
--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] mysql-bin ebuild

[Jeff Smelser]

[-- Attachment #1: Type: text/plain, Size: 311 bytes --]

On Tuesday 22 February 2005 02:26 pm, Francesco Riosa wrote:

> tomorrow morning I'll run an update to the bk sources and try again, for
> both 4.1 and 5.0, the ebuilds should be out at 16:00 CET time.

What did you find on this? I just wanted to make sure it was updated in 
bitkeeper.

Thanks,
Jeff

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-dev] mysql-bin ebuild

[Francesco Riosa]

Jeff Smelser ha scritto:

>On Tuesday 22 February 2005 02:26 pm, Francesco Riosa wrote:
>
>  
>
>>tomorrow morning I'll run an update to the bk sources and try again, for
>>both 4.1 and 5.0, the ebuilds should be out at 16:00 CET time.
>>    
>>
>
>What did you find on this? I just wanted to make sure it was updated in 
>bitkeeper.
>
>Thanks,
>Jeff
>  
>
Still running, since I've done other enanchemnts, for now mysql-4.1.10 
passed all test apart the "mysqldump" one, because of cp850 charachter set.
this on
default-linux/amd64/2004.3, gcc-3.4.3, glibc-2.3.4.20041102-r0, 
2.6.11-rc2-mm1 x86_64
default-linux/x86/2005.0, gcc-3.3.5, glibc-2.3.3.20040420-r2, 
2.6.8-gentoo-r3 i686
you can already dowload it from
http://www.francesco-riosa.com/gentoo/mysql_overlay-latest.tar.gz

btw USE="extraengine" will give you the federated-storage-engine 
requested in http://bugs.gentoo.org/show_bug.cgi?id=69846#c9 ... or at 
least it should for 5.0.3_alpha ebuild

http://www.francesco-riosa.com/gentoo/mysql_overlay_bk-latest.tar.gz

Cheers,
Francesco
--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] mysql-bin ebuild

[Francesco Riosa]

Jeff Smelser ha scritto:

>On Tuesday 22 February 2005 02:26 pm, Francesco Riosa wrote:
>
>  
>
>>tomorrow morning I'll run an update to the bk sources and try again, for
>>both 4.1 and 5.0, the ebuilds should be out at 16:00 CET time.
>>    
>>
>
>What did you find on this? I just wanted to make sure it was updated in 
>bitkeeper.
>
>Thanks,
>Jeff
>  
>
Still running, since I've done other enanchemnts, for now mysql-4.1.10 
passed all test apart the "mysqldump" one, because of cp850 charachter set.
this on
default-linux/amd64/2004.3, gcc-3.4.3, glibc-2.3.4.20041102-r0, 
2.6.11-rc2-mm1 x86_64
default-linux/x86/2005.0, gcc-3.3.5, glibc-2.3.3.20040420-r2, 
2.6.8-gentoo-r3 i686
you can already dowload it from
http://www.francesco-riosa.com/gentoo/mysql_overlay-latest.tar.gz

btw USE="extraengine" will give you the federated-storage-engine 
requested in http://bugs.gentoo.org/show_bug.cgi?id=69846#c9 ... or at 
least it should for 5.0.3_alpha ebuild

http://www.francesco-riosa.com/gentoo/mysql_overlay_bk-latest.tar.gz

Cheers,
Francesco
--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] mysql-bin ebuild

[Jeff Smelser]

[-- Attachment #1: Type: text/plain, Size: 442 bytes --]

On Thursday 24 February 2005 09:12 am, Francesco Riosa wrote:

> btw USE="extraengine" will give you the federated-storage-engine
> requested in http://bugs.gentoo.org/show_bug.cgi?id=69846#c9 ... or at
> least it should for 5.0.3_alpha ebuild

5.0.3 was giving me major issues so i am still on 5.0.2..  No clients could 
connect to it other than mysql command line.. Big problem.. ;)

Hopefully 503 will be released soon..

Jeff

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]