James Bunton writes:
- If you're running the transport with twistd, then the working directory
- is indeed the PATH variable in PyMSNt.tac
-
- If you're running the program with python directly, then you should not
- be in the src/ directory when running.
-
- cd /usr/local/PyMSNt
- python src/main.py
-
- That will start it correctly, with /usr/local/PyMSNt as the working
- directory.
Hmm, so, src/legacy/glue needs to deal wtih the file
possibly being in two different places.. Ugh.. For my use, I
can patch it up, but it might be something for you to think
about..
Part of the reason I thought it an issue was I thought I
remembered the shell script doing something like:
cd src;
exec -a PyMSNt python main.py $*
I suspect either my memory is faulty, or its changed somewhat
recently..
One last note, I did strip the "/src" bit out of the
path building for PyMSNt.tac.. It seemed silly (from here) to
have the extra (empty) level of directory in my filesystem.
(especially since the spool dir is specified as somewhere else.)
--
Eric Schnoebelen [EMAIL PROTECTED]
http://www.cirr.com
If a dog says "woof" and a cow says "moo", what does the Berkeley
demon on daddy's polo shirt say? -- Elizabeth Zwicky
From [EMAIL PROTECTED] Sat Nov 5 05:46:07 2005
From: [EMAIL PROTECTED] (Eric Schnoebelen)
Date: Sat Nov 5 05:46:12 2005
Subject: [py-transports] there's now a PyMSNt in pkgsrc-wip
Message-ID: <[EMAIL PROTECTED]>
I'm pleased to announce that I've generated a package for the
PyMSNt Jabber transport.
PyMSNt is a Jabber transport (connector/gateway) that connect a
Jabber (XMPP) server to the MSN network. Jabber users who also
have an MSN id can connect to the MSN network, and communicate
with other MSN members.
The package is py-jabber-msnt.
I think everythings done and working, but let me know what is
found broken..
For those on the py-transports list, pkgsrc-wip is the
works-in-progress tree for the pkgsrc packaging system. New
packages usually show up here first for debugging and
development, before being imported into the main tree.
pkgsrc works on a large number of operating systems, including
Linux, NetBSD, IRIX, Solaris, Interix and others.
--
Eric Schnoebelen [EMAIL PROTECTED]
http://www.cirr.com
If a dog says "woof" and a cow says "moo", what does the Berkeley
demon on daddy's polo shirt say? -- Elizabeth Zwicky
From [EMAIL PROTECTED] Sat Nov 5 12:26:48 2005
From: [EMAIL PROTECTED] (Norman Rasmussen)
Date: Sat Nov 5 12:26:51 2005
Subject: [py-transports] PyMSNt 0.10.1 - Twisted application changes
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
I've been using SVN for all my personal projects, and it's great. I
use it via ssh+svn, and the db is the new FSFS format.
On 10/29/05, Lars T. Mikkelsen <[EMAIL PROTECTED]> wrote:
> On Sat, Oct 29, 2005 at 06:53:04PM +1000, James Bunton wrote:
> > Unfortunately I've not had good experiences with SVN lately. Used it in
> > a school project. It was possibly just me not setting it up correctly,
> > but it broke itself regularly. I had to run svnadmin recover way too
> > many times for comfort.
>
> Subversion has been very stable since at least 1.0. The issues you are
> experiencing could be due to the fact that the Berkely DB repository
> data-store is not usable on network shares (e.g. NFS) - it *will*
> corrupt the repository. Subversion 1.1 introduced a new filesystem
> repository data-store (FSFS) which is more stable and usable on network
> shares. FSFS also became the default data-store in 1.2.
>
> Best regards,
> Lars
> _______________________________________________
> py-transports mailing list
> py-transports@blathersource.org
> http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports
>
--
- Norman Rasmussen
- Email: [EMAIL PROTECTED]
- Home page: http://norman.rasmussen.co.za/
From [EMAIL PROTECTED] Sat Nov 5 13:41:51 2005
From: [EMAIL PROTECTED] (Mike M. Volokhov)
Date: Sat Nov 5 14:00:15 2005
Subject: [py-transports] Re: there's now a PyMSNt in pkgsrc-wip
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
On Fri, 04 Nov 2005 23:46:07 -0600
[EMAIL PROTECTED] (Eric Schnoebelen) wrote:
>
> I'm pleased to announce that I've generated a package for the
> PyMSNt Jabber transport.
Hu, nice to found at least one of the Jabber transports packaged.
Unfortunately, I haven't any of MSN account, nor friends which have
such one. But I'd likely test PyICQt transport. Is it hard to package
it too, please?
--
Mishka.
From [EMAIL PROTECTED] Sat Nov 5 23:44:07 2005
From: [EMAIL PROTECTED] (James Bunton)
Date: Sat Nov 5 23:44:16 2005
Subject: [py-transports] PyMSNt: another nit: default avatar path hard
coded
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
That's why you're having these problems! :)
The transport relies on having that src/ directory there. Its not
empty, it has the start scripts and the .tac file as well as README and
COPYING.
In the next release it will have a test/ directory with unit tests.
If you've moved all those other files elsewhere I recommend you just
leave the src/ as is. The code assumes that the PYTHONPATH is src/, and
the system PATH is one level above that src/ directory.
Yes, there was a bug in 0.10.1 that ./PyMSNt didn't work. The correct
thing to do would have been
"cd /usr/local/PyMSNt && python src/main.py"
---
James
On 05/11/2005, at 4:41 PM, Eric Schnoebelen wrote:
>
> James Bunton writes:
> - If you're running the transport with twistd, then the working
> directory
> - is indeed the PATH variable in PyMSNt.tac
> -
> - If you're running the program with python directly, then you should
> not
> - be in the src/ directory when running.
> -
> - cd /usr/local/PyMSNt
> - python src/main.py
> -
> - That will start it correctly, with /usr/local/PyMSNt as the working
> - directory.
>
> Hmm, so, src/legacy/glue needs to deal wtih the file
> possibly being in two different places.. Ugh.. For my use, I
> can patch it up, but it might be something for you to think
> about..
>
> Part of the reason I thought it an issue was I thought I
> remembered the shell script doing something like:
>
> cd src;
> exec -a PyMSNt python main.py $*
>
> I suspect either my memory is faulty, or its changed somewhat
> recently..
>
> One last note, I did strip the "/src" bit out of the
> path building for PyMSNt.tac.. It seemed silly (from here) to
> have the extra (empty) level of directory in my filesystem.
> (especially since the spool dir is specified as somewhere else.)
>
> --
> Eric Schnoebelen [EMAIL PROTECTED]
> http://www.cirr.com
> If a dog says "woof" and a cow says "moo", what does the Berkeley
> demon on daddy's polo shirt say? -- Elizabeth Zwicky
> _______________________________________________
> py-transports mailing list
> py-transports@blathersource.org
> http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports
>
