On Thu, Jun 09, 2005 at 12:29:00AM +0200, Romain GAILLEGUE wrote:
> Le mardi 07 juin 2005 à 23:17 +0200, Aleksander Piotrowski a écrit :
> > Marc Balmer <[EMAIL PROTECTED]> wrote:
> >
> > > - Please pack the archive with a category subdir, i.e.
> > > net/pyro/, not just pyro/ when submitting it.
> > >
> > > - The Makefile lacks the '# $OpenBSD$' marker on the first line
> > >
> > > - Please kill the variable ${VERSION} in the Makefile.
> > > It's only used once.
> >
> > - And please regen PLIST (make plist)
> >
> > - And maybe use SHARED_ONLY=Yes, not ONLY_FOR_SOMETHING
> >
> > Alek
>
> With the port...
Perhaps I am missing something, but this could be a problem:
Tried to test this on i386-current but when running the "Minimalist's
Pyro - using a Name Server" example from
http://pyro.sourceforge.net/manual/8-example.html
I get (despite my nameserver working perfectly well):
<[EMAIL PROTECTED]:tmp>$ python2.3 server.py
Pyro Server Initialized. Using Pyro V3.4
Traceback (most recent call last):
File "server.py", line 11, in ?
ns=Pyro.naming.NameServerLocator().getNS()
File
"/usr/ports/net/pyro/w-Pyro-3.4/fake-i386/usr/local/lib/python2.3/site-packages/Pyro/naming.py",
line 130, in getNS
reply = self.sendSysCommand('location',host,port,trace)
File
"/usr/ports/net/pyro/w-Pyro-3.4/fake-i386/usr/local/lib/python2.3/site-packages/Pyro/naming.py",
line 56, in sendSysCommand
result=self.__sendSysCommand(request, host, port, trace,
logerrors, Pyro.constants.NSROLE_SECONDARY)
File
"/usr/ports/net/pyro/w-Pyro-3.4/fake-i386/usr/local/lib/python2.3/site-packages/Pyro/naming.py",
line 123, in __sendSysCommand
raise errors.PyroError('Name Server not responding')
Pyro.errors.PyroError: Name Server not responding
