Freevo-1.7.5 and Freevo-1.8.0rc1 will be released this weekend.
Sorry guys for not responding earlyer but I came acros a bug that
slipped in after 1.7.3 in the webserver.
I'am starting freevo from initscript with something like:
su - freevo -c freevo -fs
All seems wel but if I restart it it
Duncan Webb wrote:
Freevo-1.7.5 and Freevo-1.8.0rc1 will be released this weekend.
So I will try to release new kaa versions as well, the last releases
are uploaded at April 18th, 2007.
kaa.base 0.2 (notifier and kaa.db improvements)
kaa.imlib2 0.2.2 (only bugfixes, no new features)
The numbering for the 1.X branch is coming up close to 2.0, at what
point will the work on 1.X stop and work be strictly done on 2.0?
-
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the
Ryan Roth wrote:
The numbering for the 1.X branch is coming up close to 2.0, at what
point will the work on 1.X stop and work be strictly done on 2.0?
I just had the same thought but we could use double digits, 1.10,
1.11.x, etc.
-Rob
signature.asc
Description: OpenPGP digital signature
Freevo-1.7.5 and Freevo-1.8.0rc1 will be released this weekend.
Sorry guys for not responding earlyer but I came acros a bug that
slipped in after 1.7.3 in the webserver.
I'am starting freevo from initscript with something like:
su - freevo -c freevo -fs
All seems wel but if I restart it it
On Wed, 19 Dec 2007, Jaap Struyk wrote:
Freevo-1.7.5 and Freevo-1.8.0rc1 will be released this weekend.
Sorry guys for not responding earlyer but I came acros a bug that
slipped in after 1.7.3 in the webserver.
I'am starting freevo from initscript with something like:
su - freevo -c freevo
On Wed, 19 Dec 2007, Jaap Struyk wrote:
Freevo-1.7.5 and Freevo-1.8.0rc1 will be released this weekend.
In 1.7-4
Of course I thought this was my install in the first place...
I've seen that, but didn't realise the exact sequence that triggered it
but no matter how I start the webserver
Freevo-1.7.5 and Freevo-1.8.0rc1 will be released this weekend.
Sorry guys for not responding earlyer but I came acros a bug that
slipped in after 1.7.3 in the webserver.
I'am starting freevo from initscript with something like:
su - freevo -c freevo -fs
All seems wel but if I restart it
