mysql-workbench 6.0.9 is the last 6.0.x version before the new 6.1 series. It has been in the tree for a month. Please test and mark stable this version and its dependency. =dev-db/vsqlite++-0.3.12 =dev-db/mysql-workbench-6.0.9
One note that might be of interrest. I just had problems building mysql-workbench 6.0.9. It failed three times and only worked after I disabled parallel builds, i.e. commented out MAKEOPTS="-j3".
I further inspected my problem with building mysql-workbench 6.0.9 and noticed that the machine (2 GB RAM) I used went out of memory and cc1plus was killed by the kernel. A test on a 4 GB machine did not cause any problems. So, no real problem with mysql-workbench, I would say.
(In reply to Dirk Gouders from comment #1) > One note that might be of interrest. > > I just had problems building mysql-workbench 6.0.9. > > It failed three times and only worked after I disabled parallel builds, i.e. > commented out MAKEOPTS="-j3". I also experienced this while building 6.1.6, I noticed that it only uses 1 cpu core to build. Why is this happening? Is parallel build disabled in the ebuild?
ping for arches: any reason that this old bug is still pending?
(In reply to Hans de Graaff from comment #4) > ping for arches: any reason that this old bug is still pending? lack off manpower, as usual </offtopic>
emerge -1 =dev-db/mysql-workbench-6.0.9 pulls unstable deps: # required by dev-db/mysql-workbench-6.0.9 # required by =dev-db/mysql-workbench-6.0.9 (argument) =dev-db/vsqlite++-0.3.13 ~amd64
(In reply to Chema Alonso from comment #6) > emerge -1 =dev-db/mysql-workbench-6.0.9 pulls unstable deps: > > # required by dev-db/mysql-workbench-6.0.9 > # required by =dev-db/mysql-workbench-6.0.9 (argument) > =dev-db/vsqlite++-0.3.13 ~amd64 Yes, this is why I also asked to stable vsqlite++-0.3.12.
Sorry, bypassed the first comment :-/. Done now. amd64 stable.
ppc stable
x86 stable, last arch, closing! Thanks all!