WIP: spectrum and needed dependencies testers wanted

classic Classic list List threaded Threaded
30 messages Options
12
Reply | Threaded
Open this post in threaded view
|

WIP: spectrum and needed dependencies testers wanted

Sebastian Reitenbach
Hi,

attached tarballs for the spextrum XMPP transport/gateway, and the needed
dependencies. I have a bit older version working for me on i386 and sparc64,
tested together with ejabberd. Besides the regression tests for gloox are
failing miserably, e.g. segfaults here and there.... I use the ICQ transport
regularly. MSN and AIM I have enabled too, but since I don't have an account,
they are not well tested. Its is right now compiling on my sparc, which sill
till take a long time since a bunch of dependencies also need to compile. If
someone could test building on amd64 would be great. Also I'd like to know if
it would work with other xmpp servers like jabberd2 or openfire.

Also the ports still needs some cleanups, so general comments/rants about them
are also welcome ;)

From the spectrum DESCR:
Spectrum is an XMPP transport/gateway. It allows XMPP users to communicate
with their friends who are using one of the supported networks. It supports
a wide range of different networks such as ICQ, XMPP (Jabber, GTalk), AIM,
MSN, Facebook, Twitter, Gadu-Gadu, IRC and SIMPLE.


cheers,
Sebastian

py-xmpppy.tar.gz (1K) Download Attachment
poco.tar.gz (9K) Download Attachment
gloox.tar.gz (2K) Download Attachment
spectrum.tar.gz (2K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: WIP: spectrum and needed dependencies testers wanted

viq-2
On Thu, Jul 22, 2010 at 03:09:40PM +0200, Sebastian Reitenbach wrote:

> Hi,
>
> attached tarballs for the spextrum XMPP transport/gateway, and the needed
> dependencies. I have a bit older version working for me on i386 and sparc64,
> tested together with ejabberd. Besides the regression tests for gloox are
> failing miserably, e.g. segfaults here and there.... I use the ICQ transport
> regularly. MSN and AIM I have enabled too, but since I don't have an account,
> they are not well tested. Its is right now compiling on my sparc, which sill
> till take a long time since a bunch of dependencies also need to compile. If
> someone could test building on amd64 would be great. Also I'd like to know if
> it would work with other xmpp servers like jabberd2 or openfire.
>
> Also the ports still needs some cleanups, so general comments/rants about them
> are also welcome ;)
>
> From the spectrum DESCR:
> Spectrum is an XMPP transport/gateway. It allows XMPP users to communicate
> with their friends who are using one of the supported networks. It supports
> a wide range of different networks such as ICQ, XMPP (Jabber, GTalk), AIM,
> MSN, Facebook, Twitter, Gadu-Gadu, IRC and SIMPLE.
>
>
> cheers,
> Sebastian
I'm interested in this, I will do some testing on i386 and amd64.
I guess I will provide answers per port, to keep it organized.
--
viq

attachment0 (203 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

gloox (WAS: Re: WIP: spectrum and needed dependencies testers wanted)

viq-2
In reply to this post by Sebastian Reitenbach
This looks ok and builds fine on amd64, though a couple comments:

Personally as this is only a library I think I would put it in devel

The configure script picks up ggrep and gsed when installed, I found
some tricks to force the base ones to be used, do we want to bother?

I see explicit "use ssl" flag, so the complaints about not finding
gnutls are ignorable, but what about libidn?
--
viq

attachment0 (203 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: gloox (WAS: Re: WIP: spectrum and needed dependencies testers wanted)

Stuart Henderson
On 2010/07/24 14:23, viq wrote:
> This looks ok and builds fine on amd64, though a couple comments:
>
> Personally as this is only a library I think I would put it in devel

If some place other than devel/ makes sense, I think it's better to use
it, devel is huge already.

> The configure script picks up ggrep and gsed when installed, I found
> some tricks to force the base ones to be used, do we want to bother?

Only if they make it into the packages..if it's only using it for build
and providing build works either way, it's alright to leave it.

> I see explicit "use ssl" flag, so the complaints about not finding
> gnutls are ignorable, but what about libidn?
> --
> viq


Reply | Threaded
Open this post in threaded view
|

poco (Re: WIP: spectrum and needed dependencies testers wanted)

viq-2
In reply to this post by Sebastian Reitenbach
poco or libpoco?

It builds fine on amd64, I had problems with this when I was trying
earlier.

You're hardcoding /usr/local in patches, I believe usually it's
recommended to use ${LOCALBASE} and run ${SUBST_CMD} on those files in
pre-configure - someone please correct me if I'm wrong.

Minor nitpick, could add a space in
patch-Foundation_src_Timezone_UNIX_cpp ;)

$ make port-lib-depends-check
poco-1.3.6.2(net/poco):
WANTLIB:       expat.9 (/usr/local/lib/libPocoXML.so.0.0) (system lib)
Missing lib:   pcre.2 (/usr/local/lib/libPocoFoundation.so.0.0) (NOT REACHABLE)
Missing lib:   sqlite3.14 (/usr/local/lib/libPocoSQLite.so.0.0) (NOT REACHABLE)
WANTLIB:       z.4 (/usr/local/lib/libPocoFoundation.so.0.0) (system lib)
        WANTLIB += expat z
*** Error code 1 (ignored)


--- a/net/poco/Makefile
+++ b/net/poco/Makefile
@@ -23,8 +23,11 @@ PERMIT_DISTFILES_CDROM= Yes
 PERMIT_DISTFILES_FTP= Yes
 
 WANTLIB += c crypto m pthread ssl stdc++ iodbc iodbcinst mysqlclient
+WANTLIB += ezpat z pcre sqlite3
 LIB_DEPENDS= ::databases/iodbc \
- ::databases/mysql
+ ::databases/mysql \
+ ::databases/sqlite3 \
+ ::devel/pcre
 
 USE_GMAKE= Yes
 SEPARATE_BUILD= simple

--
viq

attachment0 (203 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: gloox (WAS: Re: WIP: spectrum and needed dependencies testers wanted)

viq-2
In reply to this post by Stuart Henderson
On Sat, Jul 24, 2010 at 02:26:56PM +0100, Stuart Henderson wrote:
> On 2010/07/24 14:23, viq wrote:
> > This looks ok and builds fine on amd64, though a couple comments:
> >
> > Personally as this is only a library I think I would put it in devel
>
> If some place other than devel/ makes sense, I think it's better to use
> it, devel is huge already.

Understood.
 
> > The configure script picks up ggrep and gsed when installed, I found
> > some tricks to force the base ones to be used, do we want to bother?
>
> Only if they make it into the packages..if it's only using it for build
> and providing build works either way, it's alright to leave it.

grepping strings in libs revealed nothing, so I guess it's fine.

> > I see explicit "use ssl" flag, so the complaints about not finding
> > gnutls are ignorable, but what about libidn?

So, do we want it to find and use libidn?

> > --
> > viq
>

--
viq

attachment0 (203 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: gloox (WAS: Re: WIP: spectrum and needed dependencies testers wanted)

viq-2
In reply to this post by viq-2
This has some test infrastructure, but it requires a bit of patching
(uses make -C which exists only in gmake), and a bunch of tests fail or
dump core.
--
viq

attachment0 (203 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

spectrum (WAS: Re: WIP: spectrum and needed dependencies testers wanted)

viq-2
In reply to this post by Sebastian Reitenbach
They released version 0.3.1,
http://spectrum.im/projects/spectrum/wiki/Changelog
But it hardcodes installation of spectrum.cfg to /etc so that would need
to be patched, and it removes the sqlite schema, in repository logs it says
"Remove unused outdated sqlite.sql schema." So for now trying the posted
version, and it builds fine. Didn't get to trying it yet, that will come
soon ;)
--
viq

attachment0 (203 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: spectrum (WAS: Re: WIP: spectrum and needed dependencies testers wanted)

Sebastian Reitenbach
viq wrote:
> They released version 0.3.1,
> http://spectrum.im/projects/spectrum/wiki/Changelog
> But it hardcodes installation of spectrum.cfg to /etc so that would need
> to be patched, and it removes the sqlite schema, in repository logs it says
> "Remove unused outdated sqlite.sql schema." So for now trying the posted
> version, and it builds fine. Didn't get to trying it yet, that will come
> soon ;)
>  
Thanks for all the feedback. I'll update those in the next days, and
resend them here.

cheers,
Sebastian

Reply | Threaded
Open this post in threaded view
|

Re: WIP: spectrum and needed dependencies testers wanted

Sebastian Reitenbach
In reply to this post by viq-2
Hi,

On Saturday 24 July 2010 02:17:53 pm viq wrote:

> On Thu, Jul 22, 2010 at 03:09:40PM +0200, Sebastian Reitenbach wrote:
> > Hi,
> >
> > attached tarballs for the spextrum XMPP transport/gateway, and the needed
> > dependencies. I have a bit older version working for me on i386 and
> > sparc64, tested together with ejabberd. Besides the regression tests for
> > gloox are failing miserably, e.g. segfaults here and there.... I use the
> > ICQ transport regularly. MSN and AIM I have enabled too, but since I
> > don't have an account, they are not well tested. Its is right now
> > compiling on my sparc, which sill till take a long time since a bunch of
> > dependencies also need to compile. If someone could test building on
> > amd64 would be great. Also I'd like to know if it would work with other
> > xmpp servers like jabberd2 or openfire.
> >
> > Also the ports still needs some cleanups, so general comments/rants about
> > them are also welcome ;)
> >
> > From the spectrum DESCR:
> > Spectrum is an XMPP transport/gateway. It allows XMPP users to
> > communicate with their friends who are using one of the supported
> > networks. It supports a wide range of different networks such as ICQ,
> > XMPP (Jabber, GTalk), AIM, MSN, Facebook, Twitter, Gadu-Gadu, IRC and
> > SIMPLE.
> >
> >
> > cheers,
> > Sebastian
>
> I'm interested in this, I will do some testing on i386 and amd64.
> I guess I will provide answers per port, to keep it organized.
Since I updated all but py-xmpppy I answer on this one here again.
changes since then:
 * poco: fix the usage of the hardcoded paths, fix WANTLIB/LIB_DEPENDS
 * gloox: link against libidn,
             use gmake to make the regress test happy (but there are still a
lot of segfaults)
 * spectrum: update to 0.3.1,
                   add user _spectrum with the port.
                   spectrumctl now works too

However, when I start spectrum services directly via spectrum or spectrumctl I
get a bunch of the following warnings:


spectrum:/usr/local/lib/libpcre.so.2.3:
/usr/local/lib/libPocoFoundation.so.0.0 : WARNING: symbol(_pcre_ucd_stage2)
size mismatch, relink your program
spectrum:/usr/local/lib/libpcre.so.2.3:
/usr/local/lib/libPocoFoundation.so.0.0 : WARNING: symbol(_pcre_utt_names)
size mismatch, relink your program
spectrum:/usr/local/lib/libpcre.so.2.3:
/usr/local/lib/libPocoFoundation.so.0.0 : WARNING: symbol(_pcre_utt) size
mismatch, relink your program
spectrum:/usr/local/lib/libpcre.so.2.3:
/usr/local/lib/libPocoFoundation.so.0.0 : WARNING: symbol(_pcre_OP_lengths)
size mismatch, relink your program
spectrum:/usr/local/lib/libpcre.so.2.3:
/usr/local/lib/libPocoFoundation.so.0.0 : WARNING: symbol(_pcre_ucd_records)
size mismatch, relink your program
spectrum:/usr/local/lib/libpcre.so.2.3:
/usr/local/lib/libPocoFoundation.so.0.0 : WARNING: symbol(_pcre_ucd_stage2)
size mismatch, relink your program
spectrum:/usr/local/lib/libpcre.so.2.3:
/usr/local/lib/libPocoFoundation.so.0.0 : WARNING: symbol(_pcre_utt_names)
size mismatch, relink your program
spectrum:/usr/local/lib/libpcre.so.2.3:
/usr/local/lib/libPocoFoundation.so.0.0 : WARNING: symbol(_pcre_utt) size
mismatch, relink your program
spectrum:/usr/local/lib/libpcre.so.2.3:
/usr/local/lib/libPocoFoundation.so.0.0 : WARNING: symbol(_pcre_OP_lengths)
size mismatch, relink your program
spectrum:/usr/local/lib/libpcre.so.2.3:
/usr/local/lib/libPocoFoundation.so.0.0 : WARNING: symbol(_pcre_ucd_records)
size mismatch, relink your program

IIRC, I had seem them before with the other version too, but forgot to mention
it. The box is a i386, with a fairly new snapshot. All the ports installed on
that box were compiled on it. Spectrum actually works, but I don't know why
those warnings are showing up.
And which program to relink? net/poco devel/pcre or net/spectrum?
Any hint where I should look regarding above warnings would be highly
appreciated.


cheers,
Sebastian

gloox.tar.gz (3K) Download Attachment
poco.tar.gz (9K) Download Attachment
spectrum.tar.gz (3K) Download Attachment
py-xmpppy.tar.gz (1K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: WIP: spectrum and needed dependencies testers wanted

David Coppa
2010/7/26 Sebastian Reitenbach <[hidden email]>:

> However, when I start spectrum services directly via spectrum or spectrumctl I
> get a bunch of the following warnings:
>
>
> spectrum:/usr/local/lib/libpcre.so.2.3:
> /usr/local/lib/libPocoFoundation.so.0.0 : WARNING: symbol(_pcre_ucd_stage2)
> size mismatch, relink your program
> spectrum:/usr/local/lib/libpcre.so.2.3:
> /usr/local/lib/libPocoFoundation.so.0.0 : WARNING: symbol(_pcre_utt_names)
> size mismatch, relink your program
> spectrum:/usr/local/lib/libpcre.so.2.3:
> /usr/local/lib/libPocoFoundation.so.0.0 : WARNING: symbol(_pcre_utt) size
> mismatch, relink your program
> spectrum:/usr/local/lib/libpcre.so.2.3:
> /usr/local/lib/libPocoFoundation.so.0.0 : WARNING: symbol(_pcre_OP_lengths)
> size mismatch, relink your program
> spectrum:/usr/local/lib/libpcre.so.2.3:
> /usr/local/lib/libPocoFoundation.so.0.0 : WARNING: symbol(_pcre_ucd_records)
> size mismatch, relink your program
> spectrum:/usr/local/lib/libpcre.so.2.3:
> /usr/local/lib/libPocoFoundation.so.0.0 : WARNING: symbol(_pcre_ucd_stage2)
> size mismatch, relink your program
> spectrum:/usr/local/lib/libpcre.so.2.3:
> /usr/local/lib/libPocoFoundation.so.0.0 : WARNING: symbol(_pcre_utt_names)
> size mismatch, relink your program
> spectrum:/usr/local/lib/libpcre.so.2.3:
> /usr/local/lib/libPocoFoundation.so.0.0 : WARNING: symbol(_pcre_utt) size
> mismatch, relink your program
> spectrum:/usr/local/lib/libpcre.so.2.3:
> /usr/local/lib/libPocoFoundation.so.0.0 : WARNING: symbol(_pcre_OP_lengths)
> size mismatch, relink your program
> spectrum:/usr/local/lib/libpcre.so.2.3:
> /usr/local/lib/libPocoFoundation.so.0.0 : WARNING: symbol(_pcre_ucd_records)
> size mismatch, relink your program
>
> IIRC, I had seem them before with the other version too, but forgot to mention
> it. The box is a i386, with a fairly new snapshot. All the ports installed on
> that box were compiled on it. Spectrum actually works, but I don't know why
> those warnings are showing up.
> And which program to relink? net/poco devel/pcre or net/spectrum?
> Any hint where I should look regarding above warnings would be highly
> appreciated.

Dunno why, but even with option "--unbundled", it still wants some
files from its internal pcre stuff:

ifdef POCO_UNBUNDLED
        objects += $(pcre_utf8_objects)
        SYSLIBS += -lpcre -lz
else
        objects += $(zlib_objects) $(pcre_objects) $(pcre_utf8_objects)
endif

And these objects clash with system pcre.

Ciao,
David

>
> cheers,
> Sebastian
>

Reply | Threaded
Open this post in threaded view
|

Re: WIP: spectrum and needed dependencies testers wanted

Sebastian Reitenbach
Hi,
On Monday 26 July 2010 05:31:48 pm David Coppa wrote:
> 2010/7/26 Sebastian Reitenbach <[hidden email]>:
> > However, when I start spectrum services directly via spectrum or
> > spectrumctl I get a bunch of the following warnings:
> >
> >
<zap zarap>

>
> Dunno why, but even with option "--unbundled", it still wants some
> files from its internal pcre stuff:
>
> ifdef POCO_UNBUNDLED
>         objects += $(pcre_utf8_objects)
>         SYSLIBS += -lpcre -lz
> else
>         objects += $(zlib_objects) $(pcre_objects) $(pcre_utf8_objects)
> endif
>
> And these objects clash with system pcre.
That was the hint I needed. Commenting out the objects += line fixed made the
warnings disappear, and it even still seems to work.

I appended a new version including a patch. If someone could take a look at
the patches, and especially the CXXFLAGS in the files/OpenBSD file, if the
parameters in there make sense. I added some comments why I chose the
parameters to make it easier to understand. If that's fine, I'd like to submit
patches upstream to get the OpenBSD related stuff in there.

cheers,
Sebastian

Reply | Threaded
Open this post in threaded view
|

Re: poco: was WIP: spectrum and needed dependencies testers wanted

Sebastian Reitenbach
In reply to this post by David Coppa
Hi,

this time with attachement.

On Monday 26 July 2010 05:31:48 pm David Coppa wrote:
> 2010/7/26 Sebastian Reitenbach <[hidden email]>:
> > However, when I start spectrum services directly via spectrum or
> > spectrumctl I get a bunch of the following warnings:
> >
> >
<zap zarap>

>
> Dunno why, but even with option "--unbundled", it still wants some
> files from its internal pcre stuff:
>
> ifdef POCO_UNBUNDLED
>         objects += $(pcre_utf8_objects)
>         SYSLIBS += -lpcre -lz
> else
>         objects += $(zlib_objects) $(pcre_objects) $(pcre_utf8_objects)
> endif
>
> And these objects clash with system pcre.
That was the hint I needed. Commenting out the objects += line fixed made the
warnings disappear, and it even still seems to work.

I appended a new version including a patch. If someone could take a look at
the patches, and especially the CXXFLAGS in the files/OpenBSD file, if the
parameters in there make sense. I added some comments why I chose the
parameters to make it easier to understand. If that's fine, I'd like to submit
patches upstream to get the OpenBSD related stuff in there.

cheers,
Sebastian


poco.tar.gz (10K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

py-xmpppy: was: WIP: spectrum and needed dependencies testers wanted

Sebastian Reitenbach
In reply to this post by Sebastian Reitenbach
On Thursday 22 July 2010 03:09:40 pm Sebastian Reitenbach wrote:

I updated the net/py-xmpppy port tarball since I sent it last time here with
the others. Changes:
Added a missing MODPY_SETUPTOOLS =      Yes
added spaces between the variables and values in the ports Makefile.

It compiles for me on sparc/sparc64/i386, tested together with spectrum on
i386.

from pkg/DESCR:

xmpppy is a Python library that is targeted to provide easy scripting
with Jabber. Similar projects are Twisted Words and jabber.py.

This library was not designed from scratch. It inherits some code from
jabberpy and have very similar API in many places. Though it is separate
project since it have almost completely different architecture and
primarily aims to work with jabberd2 - the new Open Source Jabber Server.

Its small, should be easy to review, do I get an OK to check this in?

cheers,
Sebastian

Reply | Threaded
Open this post in threaded view
|

Re: py-xmpppy: was: WIP: spectrum and needed dependencies testers wanted

Sebastian Reitenbach
Hi,

grr, this time with tarball attached.

Sebastian

On Wednesday 28 July 2010 12:30:56 pm Sebastian Reitenbach wrote:

> On Thursday 22 July 2010 03:09:40 pm Sebastian Reitenbach wrote:
>
> I updated the net/py-xmpppy port tarball since I sent it last time here
> with the others. Changes:
> Added a missing MODPY_SETUPTOOLS =      Yes
> added spaces between the variables and values in the ports Makefile.
>
> It compiles for me on sparc/sparc64/i386, tested together with spectrum on
> i386.
>
> from pkg/DESCR:
>
> xmpppy is a Python library that is targeted to provide easy scripting
> with Jabber. Similar projects are Twisted Words and jabber.py.
>
> This library was not designed from scratch. It inherits some code from
> jabberpy and have very similar API in many places. Though it is separate
> project since it have almost completely different architecture and
> primarily aims to work with jabberd2 - the new Open Source Jabber Server.
>
> Its small, should be easy to review, do I get an OK to check this in?
>
> cheers,
> Sebastian


py-xmpppy.tar.gz (1K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: gloox (WAS: Re: WIP: spectrum and needed dependencies testers wanted)

Sebastian Reitenbach
In reply to this post by viq-2
Hi,

On Saturday 24 July 2010 05:07:43 pm viq wrote:
> This has some test infrastructure, but it requires a bit of patching
> (uses make -C which exists only in gmake), and a bunch of tests fail or
> dump core.

now the ports uses gmake to make the tests happy. There are still a lot
failing, but at least gloox works so far for me. Reported to build on
amd64/i386/sparc/sparc64/mips64. For sparc use the gcc3 module.
Further now link against libidn, and it is not linking against gnutls in case
it is installed. And added some spaces between variables and = in the ports
Makefile.

Is it OK to get in?

cheers,
Sebastian

gloox.tar.gz (3K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: gloox (WAS: Re: WIP: spectrum and needed dependencies testers wanted)

Landry Breuil-5
On Wed, Jul 28, 2010 at 03:37:34PM +0200, Sebastian Reitenbach wrote:

> Hi,
>
> On Saturday 24 July 2010 05:07:43 pm viq wrote:
> > This has some test infrastructure, but it requires a bit of patching
> > (uses make -C which exists only in gmake), and a bunch of tests fail or
> > dump core.
>
> now the ports uses gmake to make the tests happy. There are still a lot
> failing, but at least gloox works so far for me. Reported to build on
> amd64/i386/sparc/sparc64/mips64. For sparc use the gcc3 module.
> Further now link against libidn, and it is not linking against gnutls in case
> it is installed. And added some spaces between variables and = in the ports
> Makefile.
>
> Is it OK to get in?

--with-libidn=/usr/local is wrong, use ${LOCALBASE}. VERSION is useless.

otherwise ok

Reply | Threaded
Open this post in threaded view
|

Re: spectrum (WAS: Re: WIP: spectrum and needed dependencies testers wanted)

Sebastian Reitenbach
In reply to this post by viq-2
viq wrote:
> They released version 0.3.1,
> http://spectrum.im/projects/spectrum/wiki/Changelog
> But it hardcodes installation of spectrum.cfg to /etc so that would need
> to be patched, and it removes the sqlite schema, in repository logs it says
> "Remove unused outdated sqlite.sql schema." So for now trying the posted
> version, and it builds fine. Didn't get to trying it yet, that will come
> soon ;)
>  
With a lot of feedback from viq, updated to 0.3.1.
I added a user _spectrum and group _spectrum so that the spectrumctl can
change userid to that user. The homedirectory of that user has to
exists, otherwise spectrumctl throws errors.
The directories /var/spectrum and /var/log/spectrum are created from the
port. I decided to put everything below /var/spectrum besides the logs.
Hope that's fine. The example configuration file was updated accordingly.

Maybe additionally a README.OpenBSD needed?

cheers,
Sebastian

spectrum.tar.gz (2K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: spectrum (WAS: Re: WIP: spectrum and needed dependencies testers wanted)

Sebastian Reitenbach
Hi,

forget the other mail, now the right tarball attached.

Sebastian

Sebastian Reitenbach wrote:

> viq wrote:
>> They released version 0.3.1,
>> http://spectrum.im/projects/spectrum/wiki/Changelog
>> But it hardcodes installation of spectrum.cfg to /etc so that would need
>> to be patched, and it removes the sqlite schema, in repository logs
>> it says
>> "Remove unused outdated sqlite.sql schema." So for now trying the posted
>> version, and it builds fine. Didn't get to trying it yet, that will come
>> soon ;)
>>  
> With a lot of feedback from viq, updated to 0.3.1.
> I added a user _spectrum and group _spectrum so that the spectrumctl
> can change userid to that user. The homedirectory of that user has to
> exists, otherwise spectrumctl throws errors.
> The directories /var/spectrum and /var/log/spectrum are created from
> the port. I decided to put everything below /var/spectrum besides the
> logs. Hope that's fine. The example configuration file was updated
> accordingly.
>
> Maybe additionally a README.OpenBSD needed?
>
> cheers,
> Sebastian


spectrum.tar.gz (4K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: spectrum (WAS: Re: WIP: spectrum and needed dependencies testers wanted)

viq-2
On Sat, Jul 31, 2010 at 04:37:24PM +0200, Sebastian Reitenbach wrote:

> Hi,
>
> forget the other mail, now the right tarball attached.
>
> Sebastian
>
> Sebastian Reitenbach wrote:
> >viq wrote:
> >>They released version 0.3.1,
> >>http://spectrum.im/projects/spectrum/wiki/Changelog
> >>But it hardcodes installation of spectrum.cfg to /etc so that would need
> >>to be patched, and it removes the sqlite schema, in repository
> >>logs it says
> >>"Remove unused outdated sqlite.sql schema." So for now trying the posted
> >>version, and it builds fine. Didn't get to trying it yet, that will come
> >>soon ;)
> >With a lot of feedback from viq, updated to 0.3.1.
> >I added a user _spectrum and group _spectrum so that the
> >spectrumctl can change userid to that user. The homedirectory of
> >that user has to exists, otherwise spectrumctl throws errors.
> >The directories /var/spectrum and /var/log/spectrum are created
> >from the port. I decided to put everything below /var/spectrum
> >besides the logs. Hope that's fine. The example configuration file
> >was updated accordingly.
> >
> >Maybe additionally a README.OpenBSD needed?
> >
> >cheers,
> >Sebastian
>
Following patch needs to be applied to PLIST, otherwise you end up with
locale files being mode 640 root:_spectrum

--- /tmp/net/spectrum/pkg/PLIST Sat Jul 31 13:51:54 2010
+++ pkg/PLIST   Sat Jul 31 17:28:08 2010
@@ -40,6 +40,8 @@
 @group ${SPGROUP}
 @mode 640
 @sample ${SYSCONFDIR}/spectrum/spectrum.cfg
+@group
+@mode
 share/locale/cs/LC_MESSAGES/spectrum.mo
 share/locale/de/LC_MESSAGES/spectrum.mo
 share/locale/pl/LC_MESSAGES/spectrum.mo

Another thing is, in lib/python2.5/site-packages/spectrum/doc/ there is
interactive.py which after running spectrum gets bytecompiled creating
interactive.pyc which remains after package removal. Solution I saw
employed so far is to compile it at package creation time, so it ends up
in PLIST. Don't ask me how to do it though ;)

The mysql schema should probably be installed, for those who want to use
it, maybe the munin monitoring script? Maybe some -extras package?

--
viq

attachment0 (203 bytes) Download Attachment
12