roundup-users Mailing List for Roundup Issue Tracker (Page 485)

So I downloaded both 0.30pre1 and the CVS versions, and get the same error:

1) install package
2) create instance in /tmp/roundup_temp
3) create localconfig and edit appropriately
4) configure roundup.cgi appropriately
5) configure Apache appropriately
6) just to be sure, chmod -R a+rwx /tmp/roundup_temp
7) echo test | mail -s '[issue] test' bugs@<domain name>
8) go to page at http://localhost/cgi-bin/roundup/test/index
9) get long stack trace, which I can't figure out.  Cut-and-pasted below

Help, please!

error: (22, 'Invalid argument') Python 2.1.1
/usr/bin/python

A problem occurred while running a Python script. Here is the sequence of function calls leading up to the error, with the most recent (innermost) call first. The exception attributes are:
      args = (22, 'Invalid argument')

/usr/local/ActivePython-2.1/lib/python2.1/site-packages/roundup/backends/back_anydbm.py in getnode(self=<_roundup_instance_1.dbinit.Database instance>, classname='priority', nodeid='', cldb=None)
  106         '''
  107         db = cldb or self.getclassdb(classname)
  108         if not db.has_key(nodeid):
       db = <bsddb object>, global has_key = undefined, nodeid = ''
  109             raise IndexError, nodeid
  110         res = marshal.loads(db[nodeid])

/usr/local/ActivePython-2.1/lib/python2.1/site-packages/roundup/hyperdb.py in get(self=<roundup.roundupdb.Class instance>, nodeid='', propname='name', default=[])
  239         of this class or a KeyError is raised.
  240         """
  241         d = self.db.getnode(self.classname, nodeid)
       d = undefined, self = <roundup.roundupdb.Class instance>, global db = undefined, global getnode = undefined, global classname = undefined, nodeid = ''
  242 
  243         # convert the marshalled data to instances

/usr/local/ActivePython-2.1/lib/python2.1/site-packages/roundup/roundupdb.py in get(self=<roundup.roundupdb.Class instance>, nodeid='', propname='name', default=[])
  118             return hyperdb.Class.get(self, nodeid, propname, default)
  119         else:
  120             return hyperdb.Class.get(self, nodeid, propname)
       global hyperdb = <module 'roundup.hyperdb' from '/usr/local/Activ...lib/python2.1/site-packages/roundup/hyperdb.pyc'>, global Class = <class roundup.roundupdb.Class>, global get = undefined, self = <roundup.roundupdb.Class instance>, nodeid = '', propname = 'name'
  121 
  122     def getprops(self, protected=1):

/usr/local/ActivePython-2.1/lib/python2.1/site-packages/roundup/htmltemplate.py in index (client=<_roundup_instance_1.interfaces.Client instance>, templates='/tmp/roundup_test/html', db=<_roundup_instance_1.dbinit.Database instance>, classname='issue', filterspec={'status': ['1', '2', '3', '4', '5', '6', '7']}, filter=[], columns=['id', 'activity', 'title', 'status', 'assignedto'], sort=['-activity'], group=['priority'], show_display_form=1, nodeids=['1'], col_re=<SRE_Pattern object>)
  557                             l.append('[unselected %s]'%prop.classname)
  558                         else:
  559                             l.append(group_cl.get(cl.get(nodeid, name), key))
       l = [], global append = undefined, group_cl = <roundup.roundupdb.Class instance>, global get = undefined, cl = <_roundup_instance_1.dbinit.IssueClass instance>, nodeid = '1', name = 'priority', key = 'name'
  560                     elif isinstance(prop, hyperdb.Multilink):
  561                         group_cl = db.classes[prop.classname]

/usr/local/ActivePython-2.1/lib/python2.1/site-packages/roundup/cgi_client.py in list (self=<_roundup_instance_1.interfaces.Client instance>, sort=['-activity'], group=['priority'], filter=[], columns=['id', 'activity', 'title', 'status', 'assignedto'], filterspec={'status': ['1', '2', '3', '4', '5', '6', '7']})
  205 
  206         htmltemplate.index(self, self.TEMPLATES, self.db, cn, filterspec,
  207             filter, columns, sort, group)
       filter = [], columns = ['id', 'activity', 'title', 'status', 'assignedto'], sort = ['-activity'], group = ['priority']
  208         self.pagefoot()
  209 

/usr/local/ActivePython-2.1/lib/python2.1/site-packages/roundup/cgi_client.py in index(self=<_roundup_instance_1.interfaces.Client instance>)
  178             filterspec = self.default_index_filterspec
  179         return self.list(columns=columns, filter=filter, group=group,
  180             sort=sort, filterspec=filterspec)
       sort = ['-activity'], filterspec = {'status': ['1', '2', '3', '4', '5', '6', '7']}
  181 
  182     # XXX deviates from spec - loses the '+' (that's a reserved character

On Mon, 8 Oct 2001 20:21, Patrick Ohly wrote:
> I think 0.2.8 didn't send out a mail after creating the node. I'll
> check again at home, because even though I have seen mails generated
> via nosy lists (with the [<class><number>] tag), I hadn't configured
> my system correctly at the beginning (noone was listening on port smtp)
> and may have missed that.
> 
> Still, even if roundup sends out mails for each new node, I fear people
> would be prone to reply to the first mail they get, leading to the
> problem described above.

Sorry, I misunderstood the problem, I see it now. Not really much that can be 
done about it that I can think of except...


> As much as I like the idea of simply using CC:
> to setup the initial nosy list, wouldn't it be better to e.g. parse
> the message body for lines with CC: <user name> and use those instead?

Alternately, you can append [nosy=joe,fred,mary,lisa] to the subject to 
pre-set the nosy list users. That is:

Subject: [issue] Problems with the corkscrew [nosy=mary,joe; priority=urgent]


    Richard

On Mon, Oct 08, 2001 at 08:06:28PM +1000, Richard Jones wrote:
> On Mon, 8 Oct 2001 19:19, Patrick Ohly wrote:
> > But what happens when those other users group-reply to the
> > original mail? Their replies would have the subject
> > "Re: [<class name>] subject", which as far as I understand
> > the original white paper would create new nodes, instead of adding
> > their comments to the existing one.
> 
> The e-mail that is sent out to the nosy list has a brand new subject line, 
> not that of the original. It inserts the correct issue nodeid into the [] at 
> the start.

I think 0.2.8 didn't send out a mail after creating the node. I'll
check again at home, because even though I have seen mails generated
via nosy lists (with the [<class><number>] tag), I hadn't configured
my system correctly at the beginning (noone was listening on port smtp)
and may have missed that.

Still, even if roundup sends out mails for each new node, I fear people
would be prone to reply to the first mail they get, leading to the
problem described above. As much as I like the idea of simply using CC:
to setup the initial nosy list, wouldn't it be better to e.g. parse
the message body for lines with CC: <user name> and use those instead?

-- 
Freundliche Gruesse / Best Regards

Patrick Ohly
Software Engineer
--------------------------------------------------------------------
//// pallas 
Pallas GmbH / Hermuelheimer Str. 10 / 50321 Bruehl / Germany
Pat...@pa... / www.pallas.com
Tel +49-2232-1896-30 / Fax +49-2232-1896-29
--------------------------------------------------------------------

On Mon, 8 Oct 2001 19:19, Patrick Ohly wrote:
> But what happens when those other users group-reply to the
> original mail? Their replies would have the subject
> "Re: [<class name>] subject", which as far as I understand
> the original white paper would create new nodes, instead of adding
> their comments to the existing one.

The e-mail that is sent out to the nosy list has a brand new subject line, 
not that of the original. It inserts the correct issue nodeid into the [] at 
the start.


    Richard

Hi all,

I have played around with roundup and have a general question
regarding the mail interface: when a message with
subject "[<class name>] subject" is sent with To: or CC: to
roundup, then a new node is created, with possibly many other
users in the initial nosy-list of the node.

But what happens when those other users group-reply to the 
original mail? Their replies would have the subject
"Re: [<class name>] subject", which as far as I understand
the original white paper would create new nodes, instead of adding
their comments to the existing one.

Or is this problem taken care of by a special handling of
subject lines starting with "Re:"?

-- 
Freundliche Gruesse / Best Regards

Patrick Ohly
Software Engineer
--------------------------------------------------------------------
//// pallas 
Pallas GmbH / Hermuelheimer Str. 10 / 50321 Bruehl / Germany
Pat...@pa... / www.pallas.com
Tel +49-2232-1896-30 / Fax +49-2232-1896-29
--------------------------------------------------------------------

>>> Richard Jones wrote
> Votes please:    (Please vote  +1, 0 -1  for yes, don't care, no)
> 
> 1. Should passwords be encrypted in the database?

If using crypt, 0. It's not that much better. Using SHA? +1.

> 2. Should the roundup-admin tool automatically perform its actions as "admin"?

So long as the docs carefully carefully mention this, and on the O/Ss 
that can do it, the installer sets appropriate permissions, +1.

(Unix can be set up correctly, dunno about windows, macos9, or other 
toys :)

Anthony

Issue:
At the moment, passwords are not encrypted in the database - they're readable 
by anyone who can read the database file. Encrypting the database would be 
achieved using a new property Type called Password, which would have 
appropriate get/set/compare routines, and would have to be treated specially 
in numerous places in the code. It would also require processing of any 
currently installed databases, if people were to opt for the encryption. An 
obviously, an encryption scheme would have to be determined (though I'd be 
happy enough with crypt).

Issue:
I personally find it annoying to have to enter user/password information to 
use roundup-admin. I propose that the roundup-admin tool be modified to 
always connect as "admin" and that the database files use an access mode that 
prohibits "other" people from reading/writing. At the moment, if you have 
access to the database files, you have all the passwords.


Votes please:    (Please vote  +1, 0 -1  for yes, don't care, no)

1. Should passwords be encrypted in the database?
2. Should the roundup-admin tool automatically perform its actions as "admin"?


    Richard

My start on the documentation is on the web at 
http://roundup.sourceforge.net/doc/ (also in the CVS doc/ directory). You'll 
probably recognise the content as being from the INSTALL.txt file, "pydoc 
roundup.mailgw" and "roundup-admin morehelp".

One issue I have with this is that the documentation is now duplicated. Yecch.

More to come - it's too close to midnight now :)


    Richard

[cc'ed to the mailing list]

On Tue, 25 Sep 2001 09:05, Chris Barker wrote:
> since there seems to be no activity on the SourceForge mailing lists for
> this project, I thought I'd send you a note.

Please, use the mailing list. There's no activity because people keep sending 
me private e-mail! I've decided to start CC'ing these e-mails to the list so 
people know it's still alive.


> I downloaded and installed roundup v. 0.2.8, but have been having
> trouble getting it to work. I'm running Linux (Redhat 6.1). It unpacked
> and installed OK, and the tests ran without problem. In fact, I think I
> have it istalled and running, I just need a littel more docs on how to
> use it.
>
> I couldn't figure out what to do about the mail aliases, but I think
> that's probably my lack of *nix sys admin skills. I've been running
> Linux as a workstation for years, but never administered my own mail at
> all.
> 
> Anyway, besides the mail stuff, I got roundup-server running. but I
> can't do anything because when I connect to it, it wants a user name and
> password, and I can't figure out how to add a user.

Yes, the documentation is extremely thin. Unfortunately, I'm heading into 
another product release at work, so time's a bit thin. I'll try to knock 
together something tomorrow though - it really does need to be done quite 
desperately. If there's any other areas of confusing, please let me know. As 
the developer, I'm about the worst person to be doing the documentation :)

The specific answer to your question:
 . log in as "admin" using the password you supplied when you set the
   instance up. If you used the "extended" schema, you can then use the link
   at the top of the page to add a user. If you used the "default" schema, or
   want to use the command line, then...
 . use the roundup-admin command line tool. With no arguments, it spits out
   usage help.

If you're still stuck, let me know - then I'll know what to cover in the 
documentation :)


       Richard

You'll need the python-devel package to match your python package.


>>> Richard Jones wrote
> On Friday 17 August 2001 09:18, Brian Dorsey wrote:
> > I'm at a bit of a loss about where to look from here... anyone have any
> > hints?
> 
> OK, redhat 7.1 doesn't come with python 2.1. How did python 2.1 get 
> installed? If it was by anything other than "make install" then you're in 
> trouble. If it was installed using an RPM, is there a "python development" 
> RPM that accompanies the python RPM?
> 
> 
>     Richard
> 
> _______________________________________________
> Roundup-users mailing list
> Rou...@li...
> http://lists.sourceforge.net/lists/listinfo/roundup-users
> 

-- 
Anthony Baxter     <an...@in...>   
It's never too late to have a happy childhood.

OK, that worked!

Specifically, I had installed the 2.1 rpm and installing the python development rpm made it work. 

Thanks a bunch for your quick help! Unfortunately, I'm going to have to wait until tomorrow to actually play with it. ;)

Take care,
-Brian

On Fri, Aug 17, 2001 at 09:28:50AM +1000, Richard Jones wrote:
> On Friday 17 August 2001 09:18, Brian Dorsey wrote:
> > I'm at a bit of a loss about where to look from here... anyone have any
> > hints?
> 
> OK, redhat 7.1 doesn't come with python 2.1. How did python 2.1 get 
> installed? If it was by anything other than "make install" then you're in 
> trouble. If it was installed using an RPM, is there a "python development" 
> RPM that accompanies the python RPM?
> 
> 
>     Richard
> 
> _______________________________________________
> Roundup-users mailing list
> Rou...@li...
> http://lists.sourceforge.net/lists/listinfo/roundup-users

On Friday 17 August 2001 09:18, Brian Dorsey wrote:
> I'm at a bit of a loss about where to look from here... anyone have any
> hints?

OK, redhat 7.1 doesn't come with python 2.1. How did python 2.1 get 
installed? If it was by anything other than "make install" then you're in 
trouble. If it was installed using an RPM, is there a "python development" 
RPM that accompanies the python RPM?


    Richard

Hello all!

Roundup looks like a great tool. I'm trying to set it up to see how it works and I'm running into trouble. I've got some python and linux admin experience, but am certainly no expert. 

When I attempt to install roundup, I get:

[root@localhost roundup-0.2.6]# python setup.py install
Running unit tests...
bsddb3 module not found, skipping bsddb3 DBTestCase
bsddb3 module not found, skipping bsddb3 DBTestCase
........................
----------------------------------------------------------------------
Ran 24 tests in 14.330s

OK
packing up templates in roundup/templates/classic
packing up templates in roundup/templates/extended
running install
Traceback (most recent call last):
  File "setup.py", line 51, in ?
    scripts = ['roundup-admin', 'roundup-mailgw', 'roundup-server']
  File "/var/tmp/python2-2.1-root/usr/lib/python2.1/distutils/core.py", line 138, in setup
  File "/var/tmp/python2-2.1-root/usr/lib/python2.1/distutils/dist.py", line 899, in run_commands
  File "/var/tmp/python2-2.1-root/usr/lib/python2.1/distutils/dist.py", line 918, in run_command
  File "/usr/lib/python2.1/cmd.py", line 112, in ensure_finalized
    return self.default(line)
  File "/var/tmp/python2-2.1-root/usr/lib/python2.1/distutils/command/install.py", line 256, in finalize_options
  File "/var/tmp/python2-2.1-root/usr/lib/python2.1/distutils/sysconfig.py", line 366, in get_config_vars
  File "/var/tmp/python2-2.1-root/usr/lib/python2.1/distutils/sysconfig.py", line 302, in _init_posix
distutils.errors.DistutilsPlatformError: invalid Python installation: unable to open /usr/lib/python2.1/config/Makefile (No such file or directory)
[root@localhost roundup-0.2.6]#


I didn't know what to make of that, so I did a search for kicks:
[root@localhost roundup-0.2.6]# find / -name Makefile |grep python
/usr/local/zope2.3.3/lib/python/Products/PythonScripts/zbytecodehacks/Makefile
/usr/local/zope2.3.3/lib/python/Products/PythonScripts/zbytecodehacks/code_gen/Makefile
/usr/local/zope2.3.3/lib/python/Shared/DC/xml/pyexpat/expat/Makefile


But that doesn't look like what we're looking for, either... I'm running RedHat 7.1:
[root@localhost python2.1]# cat /proc/version
Linux version 2.4.2-2 (ro...@po...) (gcc version 2.96 20000731 (Red Hat Linux 7.1 2.96-79)) #1 Sun Apr 8 20:41:30 EDT 2001

And Python 2.1:
[root@localhost python2.1]# python
Python 2.1 (#1, Jun  7 2001, 10:56:49)
[GCC 2.96 20000731 (Red Hat Linux 7.1 2.96-81)] on linux2
Type "copyright", "credits" or "license" for more information.
>>>


I'm at a bit of a loss about where to look from here... anyone have any hints?

Take care,
-Brian

Sorry, I didn't read your email well enough. It will be fixed in the CVS some 
time today (I've got some other changes that need testing).

BTW, dunno if your system has it, but the grep on my system can do recursive 
searches. "grep -r isLinkType ." does an equivalent search to the above.


    Richard

Looks like the following patch should fix the problem.

--
Misha

Index: cgi_client.py
===================================================================
RCS file: /cvsroot/roundup/roundup/roundup/cgi_client.py,v
retrieving revision 1.20
diff -u -b -r1.20 cgi_client.py
--- cgi_client.py	2001/08/12 06:32:36	1.20
+++ cgi_client.py	2001/08/15 15:44:14
@@ -19,7 +19,7 @@
 
 import os, cgi, pprint, StringIO, urlparse, re, traceback, mimetypes
 
-import roundupdb, htmltemplate, date
+import roundupdb, htmltemplate, date, hyperdb
 
 class Unauthorised(ValueError):
     pass
@@ -124,7 +124,7 @@
             if key[0] == ':': continue
             prop = props[key]
             value = self.form[key]
-            if isinstance(prop.isLinkType or prop, hyperdb.Multilink):
+            if isinstance(prop, hyperdb.Link) or isinstance (prop, hyperdb.Multilink):
                 if type(value) == type([]):
                     value = [arg.value for arg in value]
                 else:
@@ -376,7 +376,7 @@
             if len(nosy) == 1 and uid in nosy:
                 nosy = 0
         if (nosy and props.has_key('messages') and
-                props['messages'].isMultilinkType and
+                isinstance (props['messages'], hyperdb.Multilink) and
                 props['messages'].classname == 'msg'):
 
             # handle the note
Index: date.py
===================================================================
RCS file: /cvsroot/roundup/roundup/roundup/date.py,v
retrieving revision 1.10
diff -u -b -r1.10 date.py
--- date.py	2001/08/07 00:24:42	1.10
+++ date.py	2001/08/15 15:44:14
@@ -116,7 +116,7 @@
              1. an interval from this date to produce another date.
              2. a date from this date to produce an interval.
         """
-        if other.isDate:
+        if isinstance (other, Date):
             # TODO this code will fall over laughing if the dates cross
             # leap years, phases of the moon, ....
             a = calendar.timegm((self.year, self.month, self.day, self.hour,
Index: htmltemplate.py
===================================================================
RCS file: /cvsroot/roundup/roundup/roundup/htmltemplate.py,v
retrieving revision 1.19
diff -u -b -r1.19 htmltemplate.py
--- htmltemplate.py	2001/08/12 06:32:36	1.19
+++ htmltemplate.py	2001/08/15 15:44:15
@@ -94,8 +94,7 @@
             # TODO: pull the value from the form
             if isinstance(propclass, hyperdb.Multilink): value = []
             else: value = ''
-        if isinstance((propclass.isStringType or propclass, hyperdb.Date) or
-                propclass.isIntervalType):
+        if isinstance (propclass, hyperdb.String) or isinstance (propclass, hyperdb.Date) or isinstance (propclass, hyperdb.Interval):
             size = size or 30
             if value is None:
                 value = ''
@@ -297,7 +296,7 @@
             value = self.filterspec.get(property, [])
         else:
             value = []
-        if isinstance(propclass.isLinkType or propclass, hyperdb.Multilink):
+        if isinstance(propclass, hyperdb.Link) or isinstance (propclass, hyperdb.Multilink):
             linkcl = self.db.classes[propclass.classname]
             l = []
             k = linkcl.labelprop()
Index: hyperdb.py
===================================================================
RCS file: /cvsroot/roundup/roundup/roundup/hyperdb.py,v
retrieving revision 1.15
diff -u -b -r1.15 hyperdb.py
--- hyperdb.py	2001/08/12 06:32:36	1.15
+++ hyperdb.py	2001/08/15 15:44:15
@@ -675,7 +675,7 @@
                             av = an[prop] = av.lower()
                         if bv and bv[0] in string.uppercase:
                             bv = bn[prop] = bv.lower()
-                    if isinstance(propclass.isStringType or propclass, Date):
+                    if isinstance (propclass, String) or isinstance (propclass, Date):
                         if dir == '+':
                             r = cmp(av, bv)
                             if r != 0: return r

On Wed, Aug 15, 2001 at 09:08:10AM +1000, Richard Jones wrote:
> On Tuesday 14 August 2001 23:17, Mikhail Sobolev wrote:
> > What's the idea behind having Issue and Support classes?
> 
> They each have different attributes. A support node needs to know about the 
> company requesting the support, the level of support, the source, ... An 
> issue doesn't need to know any of that.
> 
> If you find that neither of the two standard schemas fits your needs, you 
> have complete control to change it in the instance home.
Thanks.

After a small consideration, I believe the question should be re-phrased.  As
far as I understand, an "issue" will always be an "issue" and a "support" will
always be a "support".  You cannot change the type of the item, it's the
submitter who decides what type her request is of.  That means a single
instance of roundup would serve as two completely independent databases.  So my
question is: what could be the idea for having two (or more) completely
independent databases in one instance of roundup?

--
Misha

On Wed, Aug 15, 2001 at 09:06:22AM +1000, Richard Jones wrote:
> On Tuesday 14 August 2001 19:16, Mikhail Sobolev wrote:
> > I updated my roundup copy from CVS and found that isLinkType is the name
> > under question.
> 
> Sorry, under question where?
In my message. :)))

> >  What is it?  My
> >
> >     find . -type f -exec fgrep isLinkType {} \;
> >
> > revealed only use of this name but it's not defined anywhere.
> 
> The current CVS no longer uses the isFooType symbols. Are you saying that I 
> missed one in the CVS code?
Yes.

$ cvs -z6 -q update -dP
$ find . -type f -exec fgrep -l isLinkType {} \;
./roundup/cgi_client.py
./roundup/htmltemplate.py

--
Misha

On Tuesday 14 August 2001 23:17, Mikhail Sobolev wrote:
> What's the idea behind having Issue and Support classes?

They each have different attributes. A support node needs to know about the 
company requesting the support, the level of support, the source, ... An 
issue doesn't need to know any of that.

If you find that neither of the two standard schemas fits your needs, you 
have complete control to change it in the instance home.


    Richard

On Tuesday 14 August 2001 19:16, Mikhail Sobolev wrote:
> I updated my roundup copy from CVS and found that isLinkType is the name
> under question.

Sorry, under question where?


>  What is it?  My
>
>     find . -type f -exec fgrep isLinkType {} \;
>
> revealed only use of this name but it's not defined anywhere.

The current CVS no longer uses the isFooType symbols. Are you saying that I 
missed one in the CVS code?


    Richard

What's the idea behind having Issue and Support classes?

--
Misha

I updated my roundup copy from CVS and found that isLinkType is the name
under question.  What is it?  My

    find . -type f -exec fgrep isLinkType {} \;

revealed only use of this name but it's not defined anywhere.

Thanks,

--
Misha

On Monday 13 August 2001 22:45, Mikhail Sobolev wrote:
> Just to not see a wrong message if the subject line is missing. :)

Fixed in CVS, thanks.


    Richard

On Monday 13 August 2001 22:36, Richard Jones wrote:
> On Mon, 13 Aug 2001 08:14, Mikhail Sobolev wrote:
> > Traceback (most recent call last):
> >   File "test/test_dates.py", line 39, in testDate
> >     y, m, d, x, x, x, x, x, x = time.gmtime()
> > TypeError: function requires at least one argument
>
> doh! me and my 2.1-isms :)

This is fixed in the CVS.


    Richard

Just to not see a wrong message if the subject line is missing. :)

--
Misha

Index: mailgw.py
===================================================================
RCS file: /cvsroot/roundup/roundup/roundup/mailgw.py,v
retrieving revision 1.13
diff -u -b -r1.13 mailgw.py
--- mailgw.py	2001/08/12 06:32:36	1.13
+++ mailgw.py	2001/08/13 12:43:50
@@ -167,7 +167,7 @@
         Parse the message as per the module docstring.
         '''
         # handle the subject line
-        subject = message.getheader('subject')
+        subject = message.getheader('subject', '')
         m = subject_re.match(subject)
         if not m:
             raise MailUsageError, '''

On Mon, 13 Aug 2001 08:14, Mikhail Sobolev wrote:
> Traceback (most recent call last):
>   File "test/test_dates.py", line 39, in testDate
>     y, m, d, x, x, x, x, x, x = time.gmtime()
> TypeError: function requires at least one argument

doh! me and my 2.1-isms :)


> Another note is about the mail interface (I have not had time to try the
> system since I installed it :).  I created a special alias which pipes
> everything to a special program.  I am running Postfix MTA, and it looks
> like there is a problem with permissions: the file created by
> roundup-mailgw cannot be accessed via web.  I believe, I'll be able to
> work out this, but the permissions issue is worth mentioning in a readme
> file. :))

Yeah, file permissions are a nasty problem. I'm not sure what a good, general 
solution is yet. Suggestions welcome.


    Richard