On Mon, Jan 14, 2013 at 3:38 PM, Reindl Harald <[email protected]> wrote: > Am 15.01.2013 00:00, schrieb Jan Engelhardt: >> On Monday 2013-01-14 23:44, Reindl Harald wrote: >> >>> what does systemd-analyze try to tell me? >>> systemd-197 itself works fine >>> >>> [root@testserver:~]$ systemd-analyze >>> Traceback (most recent call last): >>> File "/usr/bin/systemd-analyze", line 23, in <module> >>> from gi.repository import Gio >>> ImportError: No module named gi.repository >> >> python is telling you about a missing (python) module named >> gi.repository > > but > > * where does it comre from (gi.repository doe snot tell me anything)
this is up to your distribution to provide, unfortunately. > * when was it introduced > * why does the package it not pull as dependencie with hopefully > not again circle-deps to a lot of other packages > > does systemd really need to introduce one 3rd party component > after the next (libmicrohttpd as example) which will sooner > or later terrible break due incompatible changes in this minefiled I don't think it's as bad as you portray it, but I have an intern software engineer that I will be making systemd-analyze (the non-plot parts - the plot parts should be replaced by bootchart IMO) rewrite in C, so hopefully we can put some of this behind us soon enough. If there are folks interested in this, let me know, so I can coordinate the efforts. Auke _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
