On Sun, 2007-02-11 at 11:24 +0100, Dirk Meyer wrote:
It should work now as expected, I will prepare new ebuilds today.
May I know where to find the ebuilds? Is it in Gentoo's bugzilla or some
other location??
Thanks
-
Ow Mun Heng wrote:
On Sun, 2007-02-11 at 11:24 +0100, Dirk Meyer wrote:
It should work now as expected, I will prepare new ebuilds today.
May I know where to find the ebuilds? Is it in Gentoo's bugzilla or some
other location??
On Saturday 10 February 2007, Dirk Meyer wrote:
Harm Geerts wrote:
Things that jump out so far:
during install:
both freevo-core and freevo-ui install /usr/share/freevo/mbus.conf
Fixed
during setup:
`freevo setup` must first be run as root in order to
create
Harm Geerts wrote:
You'll get a sandbox violation writing everywhere except the staging area.
The staging area is a temporary install image where portage installs the
application before committing it to the live filesystem.
So yes, you would get a violation for writing to /tmp
OK, I see that
Hi,
again an update on current SVN.
o The config format now has completly changed to the new kaa.config
based ini format. This means no local_config.py and no
freevo_config.py anymore. Call 'freevo setup' after updating.
o Some plugins are broken now because they still need the old style
On Saturday 10 February 2007, Dirk Meyer wrote:
Hi,
again an update on current SVN.
o The config format now has completly changed to the new kaa.config
based ini format. This means no local_config.py and no
freevo_config.py anymore. Call 'freevo setup' after updating.
o Some plugins
Things that jump out so far:
during install:
both freevo-core and freevo-ui install /usr/share/freevo/mbus.conf
during setup:
`freevo setup` must first be run as root in order to
create /var/lib/freevo/freevo_config.py
Only when /var/lib/freevo/freevo_config.py exists are regular users able to
Harm Geerts wrote:
The problem is that setup.py imports freevo.conf which sets up the DATADIR,
LOGDIR and the logfile handler. I'm using FEATURES=usersandbox which tries
to run as much as possible under the portage user (which has uid 250).
Compiling source
in
Harm Geerts wrote:
Things that jump out so far:
during install:
both freevo-core and freevo-ui install /usr/share/freevo/mbus.conf
Fixed
during setup:
`freevo setup` must first be run as root in order to
create /var/lib/freevo/freevo_config.py
Only when /var/lib/freevo/freevo_config.py
On Saturday 10 February 2007, Dirk Meyer wrote:
Harm Geerts wrote:
The problem is that setup.py imports freevo.conf which sets up the
DATADIR, LOGDIR and the logfile handler. I'm using FEATURES=usersandbox
which tries to run as much as possible under the portage user (which has
uid 250).
10 matches
Mail list logo