I have put together a working ebuild for 2.3.12 In addition to features of the 2.3.11 and earlier ebuilds, this one also supports the "threads" USE flag, allowing one to compile mico with or without thread support. This is important for us, as our inhouse software works far better with threads disabled.
Created attachment 79239 [details] mico 2.3.12 ebuild ebuild file
gtk dep isn't present
*** Bug 133532 has been marked as a duplicate of this bug. ***
Does this use QT3 or QT4? Their own docs aren't too clear.
cardoe, your use.local.desc entry is wrong. net-misc/mico - Enable QT GUI Toolkit (remove when package leaves portage or is fixed)
(In reply to comment #4) > Does this use QT3 or QT4? Their own docs aren't too clear. > looks like 3..
ebuild uses QTDIR without inheriting qt3 or qt4 eclass.
I fixed qt and tcltk USE flag issues.
There's an outstanding security bug... http://www.mico.org/down.html
can we get this stable? I'm not particuarly keen on stabling/keeping stuff that no one is maintaining.
alpha, x86: please check if the ebuild looks good. If it does, please test, commit and stable it, since we have no maintainer here. If it doesnt look clean or you dont want it stable, just say that and we'll find another solution (thats probably masking and killing, if no maintainer can be found)
lots of nice fun errors on x86 for building. Missing headers for one it appears. such as qapp, qsocknot, qtmico... I'll probably give more info later, but for now I'm gone for the night.
Hello, Just as Joshua stated, i was also unable to compile mico-2.3.12 for x86 with the following error messages: c++ -I. -I../include -O2 -Wall -Os -mcpu=i686 -pipe -I/usr/include/gtk-1.2 -I/usr/include/glib-1.2 -I/usr/lib/glib/include -c qtmico.cc -o qtmico.o In file included from qtmico.cc:29: ../include/mico/qtmico.h:33:18: qapp.h: No such file or directory ../include/mico/qtmico.h:39:22: qsocknot.h: No such file or directory ../include/mico/qtmico.h:42:20: qtimer.h: No such file or directory In file included from qtmico.cc:29: ../include/mico/qtmico.h:49: error: syntax error before `{' token ../include/mico/qtmico.h:53: error: syntax error before `public' ../include/mico/qtmico.h:56: error: destructors must be member functions ../include/mico/qtmico.h: In function `QTDispatcher* get_dispatcher()': ../include/mico/qtmico.h:60: error: `qtd_' undeclared (first use this function) ../include/mico/qtmico.h:60: error: (Each undeclared identifier is reported only once for each function it appears in.)
Broken on Alpha the same way as x86. We have other corba implementations in portage so I'll vote for masking + removing if nobody wants to maintain mico.
It's masked for now for security. Nothing in the tree depends on it etc etc etc.
x86 is gone as this is now resolved in some way or form.
Bye bye mico...
Reassigning to Security.
Sending it to enhancement scope pending complete removal.
Punted in 30 days (Oct 16th)
Punted by phreak a while back...
Thx masterdriverz but please don't close security bugs:-) Security please vote for mask GLSA.
We might be in for some laughter if we surface with a maskglsa for this one now ... I tend to vote NO.
(In reply to comment #22) > Thx masterdriverz but please don't close security bugs:-) Sorrry, didn't think
joining frilled (0.5 no)
Voting full NO and closing. Feel free to reopen if you disagree.
Hello, It seems that I am arriving after the battle but here is my situation. I am trying to create an ebuild for OpenFOAM, A Computer Fluid Dynamics (CFD) toolbox. The beast comes with it's own mico (2.3.11) but I had hoped to avoid to use that one and use instead the Gentoo one (maintained, well I had hoped...) I am discovering now that mico is removed... How to solve that? I need OpenFOAM and I am not really willing to get a flawed mico in the system but what can be done? Daniel
As this is a dependency of OpenFOAM, I've added this ebuild to the sunrise overlay.
(In reply to comment #28) > As this is a dependency of OpenFOAM, I've added this ebuild to the sunrise > overlay. Did you also fix the code issues raised in this bug?
I've dropped the qt USE-Flag, if you meant that.
(In reply to comment #9) > There's an outstanding security bug... Is this known to be fixed in 2.3.12 (and thus in 2.3.13)? (see bug#257984)
Created attachment 181281 [details, diff] mico-2.3.12-secfix1.diff The upstream patch for the security bug.
The patch is applied in 2.3.13, but it seems 2.3.12 is affected. Putting 2.3.13 is not unreasonable from a security POV.
