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

On Saturday 15 December 2001 11:57 pm, you wrote:
> REPs (Roundup Enhancement Proposals):
> I do not know, if these are recognised and planned or so. So please give
> *me* a try ;-):
> 1) Title field: The "title" field should be a textarea or a "description"
> should be considered. The size as it is now is too small (only for me?).

As Titus pointed out - why does the title need to be so big? Why note include 
the additional information in the note field?


> 2) Mailing: How about users, who do not have a permanent connection to
> their mail servers? How do they send mails, which failed to be sent, when a
> connection could not be established. Could there be a button "Send unsent
> mails"? Seems like reinventing a mail client...

This is a tricky one, and I can't see an immediate solution to it. I guess 
the message objects could have a "needs to be sent" flag, and we could test 
that once in a while, or on demand. Or perhaps there needs to be a spool dir 
that we put write the message to, and then try to send all the messages in 
there. That would be how mailing list software would work...


> 3) Only admins should be able to add users.

This has been asked for by other users - I'll modify the default HTML 
headings so this is the case.


> 4) There should be an interface to add new products in extended instances.
> The way I do it now, is: Edit the template, safe my db, init the instance,
> copy the appropriate files.

The products are stored in the database - you need to use the roundup-admin 
tool to firstly list the current products, then retire the ones you don't 
want to have or create the new ones you want to add. For example:


[richard@ike ~/src/roundup/roundup]% ./roundup-admin -i /tmp/test
Roundup {version} ready for input.
Type "help" for help.
roundup> list product
   1: Bizar Shop
   2: Bizar Shop Developer
   3: Bizar Shop Manual
   4: Bizar Shop Developer Manual
roundup> retire product1
roundup> retire product2
roundup> retire product3
roundup> retire product4
roundup> create product
Order (String): 1
Name (String): Our Widget
5
roundup> create product
Order (String): 2
Name (String): Our Sprocket
6
roundup> create product
Order (String): 3
Name (String): Our Gadget
7
roundup> l product
   5: Our Widget
   6: Our Sprocket
   7: Our Gadget
roundup> commit
roundup> exit...


> 5) Status "unread": Shouldn't this be set as default?

I think you're right...


> Errors - appologies if they are features, which I haven't understood yet:
>
> 1) I have added a user but misspelled his password. Now this user cannot
> login and I cannot admin his account. We are locked out, so to say.

There was a problem in 0.3.0 with people being unable to change their 
password. This is fixed in the CVS code, and 0.3.1 (which I hope to release a 
preview of Real Soon).


    Richard

-> REPs (Roundup Enhancement Proposals):
-> I do not know, if these are recognised and planned or so. So please give
-> *me* a try ;-):
-> 1) Title field: The "title" field should be a textarea or a "description"
-> should be considered. The size as it is now is too small (only for me?).

The titles on individual issues?  What about using the description field?

-> 2) Mailing: How about users, who do not have a permanent connection to their
-> mail servers? How do they send mails, which failed to be sent, when a
-> connection could not be established. Could there be a button "Send unsent
-> mails"? Seems like reinventing a mail client...

I'm not sure what you mean: roundup itself presumably is running on a
Web server, which has access to a mail server.  In this case, the mail
server will take care of all of the mail.  Roundup doesn't send the mail
directly to the user; it only sends it to the mail server, which takes
care of sending it to the user, including any batching that's necessary.

-> 5) Status "unread": Shouldn't this be set as default?

I agree ;)

--t

Hello all,

cool tool, your Roundup! I considered to write something similar when I saw
Bugzilla. Then I found Roundup and decided to give it a try. Very usable,
indeed!


REPs (Roundup Enhancement Proposals):
I do not know, if these are recognised and planned or so. So please give
*me* a try ;-):
1) Title field: The "title" field should be a textarea or a "description"
should be considered. The size as it is now is too small (only for me?).

2) Mailing: How about users, who do not have a permanent connection to their
mail servers? How do they send mails, which failed to be sent, when a
connection could not be established. Could there be a button "Send unsent
mails"? Seems like reinventing a mail client...

3) Only admins should be able to add users.

4) There should be an interface to add new products in extended instances.
The way I do it now, is: Edit the template, safe my db, init the instance,
copy the appropriate files.

5) Status "unread": Shouldn't this be set as default?


Errors - appologies if they are features, which I haven't understood yet:

1) I have added a user but misspelled his password. Now this user cannot
login and I cannot admin his account. We are locked out, so to say.


Cheers
Franz


--------------------------------------------------------
DATEC Datentechnik GmbH
	Software Development
	Retrieval Computing
A-6890 LUSTENAU, Schmiedgasse 7
Tel	+43 5577 630 04-0
Fax	+43 5577 630 04-40
Mobile
	+43 664 214 57 43
E-Mail
	fg...@da...
WWW	www.datec.at (in Partnerschaft mit Amazon.de)

On Sat, 15 Dec 2001 03:39, Patrick Ohly wrote:
> running the current CVS version of roundup
> I found that although I have python 2.1.1
> the version check still prevents running roundup.

Yes, I noticed this yesterday, but couldn't fix it 'cos our office net 
connection was down all day :(


    Richard

On Wed, 2001-12-12 at 22:58, Richard Jones wrote: 
> On Tuesday 11 December 2001 4:04 am, Patrick Ohly wrote:
> > - The biggest change is the support for message threading with
> >   In-Reply-To in the message headers.
[...] 

> Hrm - the mechanism is a nice idea - but requires that the message-id also be 
> stored on each node. You can't support threading in the web interface without 
> it.
In my patch a message-id is assigned to an issue as soon as the first 
msg node is sent as email to someone. My reasoning was that the email 
parts (incoming/outgoing) know about message-ids, while the rest simply 
ignores them. 

Extending this threading to the web interface is indeed challenging, 
and I don't think I would find the time to do it right now, especially 
as I haven't looked at this code (and the ideas behind it) at all yet. 

How would you visualize the tree structure of the msg nodes? How 
would you select one msg to which you want to reply? I don't have 
answers to those questions yet. 

> I have fixed the other issues you mention in the CVS - I would appreciate it 
> if you could produce your newer patches against that.

Thanks a lot for including the patches, I'll switch to CVS now.
I have added my inreplyto patches again, but (independently of
that, as I think) now I have one major problem:

Sending an email that creates a new issue does not work if
the author is unknown:

----  traceback of failure  ----
Traceback (most recent call last):
  File "/usr/lib/python2.1/site-packages/roundup/mailgw.py", line 141,
in handle_Message
    return self.handle_message(message)
  File "/usr/lib/python2.1/site-packages/roundup/mailgw.py", line 561,
in handle_message
    content=content, files=files, inreplyto=inreplyto)
  File "/usr/lib/python2.1/site-packages/roundup/roundupdb.py", line
185, in create
    newid = Class.create(self, **propvalues)
  File "/usr/lib/python2.1/site-packages/roundup/roundupdb.py", line 94,
in create
    nodeid = hyperdb.Class.create(self, **propvalues)
  File "/usr/lib/python2.1/site-packages/roundup/hyperdb.py", line 163,
in create
    raise IndexError, '%s has no node %s'%(link_class, value)
IndexError: user has no node 2

The line numbers are slightly off due to my patches. If you
think they are relevant than let me know and I will try again
without them.

Anyway, the database contains only the admin user at this time,
and the message sent to roundup should add pat...@pa...
as new user, but somehow doesn't:

From: 	Patrick Ohly <Pat...@pa...>
To: 	tool-issues <too...@pa...>
Subject: [issue] Test of tool-issues
Date: 	14 Dec 2001 18:35:15 +0100

too...@pa... is the ISSUE_TRACKER_EMAIL.
If the user is added manually the same email creates
the issue just fine.

-- 
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
--------------------------------------------------------------------

Hi,

running the current CVS version of roundup
I found that although I have python 2.1.1
the version check still prevents running roundup.

This is due to a typo:
$ python
Python 2.1.1 (#1, Nov 11 2001, 18:19:24) 
[GCC 2.95.4 20011006 (Debian prerelease)] on linux2
Type "copyright", "credits" or "license" for more information.
>>> import sys
>>> print sys.version_info
(2, 1, 1, 'final', 0)
>>> sys.version_info[:2]
(2, 1)
>>> sys.version_info[:3]
(2, 1, 1)
>>> sys.version_info[:3] < (2,1,1)
0

version_check.py should use sys.version_info[:3]
and not sys.version_info[:2].

-- 
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
--------------------------------------------------------------------

[sorry it's taken so long to get back to you about this]
[also, please use the mailing lists, not mail me directly]

On Thu, 6 Dec 2001 16:40, Sastry Govindu wrote:
>   I am trying to enhance your system to include a URL for
> discussions on an issue. I am looking at the possibility of
> adding this URL to the end of History in the Issue page. The
> url will be of the form
> http://hostname/servlet?issueid=issueid&username=userid

I'm not sure what you mean by "a URL for discussions on an issue"


> This servlet will be storing and retreiving information from
> a seperate database. I could get the issue id but how should
> I get the currently logged in user?

There is no way to get it at present withough modifying the html templating. 
This could be added - but I need more information about what it is you're 
trying to do .. it might be there's an easier way...


      Richard

Hi there all,
I use the email interface for roundup.
When replying to emails from roundup,
I notice that roundup strips the quoted stuff (ie prefixed with '> '.
Which makes it a little hard to read since I tend to just quote little
bits and answer them. Without the context the reply is a bit hard
to read. Can this be changed by configuration?

Eg. if the reply to an email looks like this.

#---- cut here
> an sub-issue aaaaa in my email 
reply to sub-issue aaaaaa here
> another sub-issue bbbbbbb in my email
reply to issue sub-bbbbbb here
#--- end here

in roundup, this becomes
#--- cut here
reply to sub-issue aaaaaa here
reply to sub-issue bbbbbb here
#--- end here

As u can see, the context is lost.
Any suggestions?

Many thanks in advance,
Chai
Tel +61 3 8892 4606   +61 401 688 408 (m)

Hi there all,
Had a question.
One thing I'd like to be able to do is to Bcc copies of my email
to external people to roundup but roundup refuses to do anything with
Message/Rfc822 parts of the message (which is what bcc does, original
email is included in a mime message as a part with type
Message/Rfc822). Likewise, forwarding also fails as it uses the same
mime type. Any clues on this?
I understand this also depends on how BCC is done.
me/mew (via emacs) does it via a mime attachement of
the original email, I think outlook does it differently.
So it'd work if the bcc was done using outlook but not
using Me.
Pointers?

Many thanks in advance,
Chai
Tel +61 3 8892 4606   +61 401 688 408 (m)

On Tuesday 11 December 2001 4:04 am, Patrick Ohly wrote:
> I did some further modifications myself, which I attach as diffs
> to this mail:
>
> - The envelope-from should be set to the roundup-admin and not
>   roundup itself, to prevent feeding delivery reports into roundup
>   (call to smtp.sendmail() in roundupdb.py).

Accepted.


> - I found it inconvenient that all mails from roundup have roundup
>   as From:, as searching for comments by a particular user cannot
>   be done by header. Therefore I add the author's name to From:,
>   but still keep the roundup address there, because not all email
>   systems allow faked email addresses, while choosing the username
>   should be okay, and it prevents that a "reply to all" is sent to the
>   author twice (once directly, once via roundup).

Also accepted. And the more important benefit of keeping roundup as the from: 
is that roundup gets a copy of the response :)


> - The biggest change is the support for message threading with
>   In-Reply-To in the message headers. There are three situations
>   here: a reply by email to an existing issue where we have
>   a In-Reply-To which is dropped by roundup when storing this
>   reply in its database and then bouncing it to the nosy list;
>   an issue is modified by web; creating a new issue via email
>   and bouncing it back to the author.
>
>   What I did is adding a "inreplyto" property to my issue and
>   msg classes. If the mail gateway adds a msg node, it sets its
>   inreplyto to the same value that the incoming email had,
>   and the roundupdb code adds it again when it sends this msg.
>   This solves the first case and allows deep nesting just as in
>   normal email discussions. Using the message id if it is a new
>   issue solves the last case.
>
>   The roundupdb also treats the very first msg for an issue
>   in a special way: it creates the Message-Id itself (from
>   the roundup email address and the designator), and stores
>   this id in the inreplyto property of the issue. This id is
>   used for all msgs which don't have their own inreplyto, e.g.
>   for those created via web. That way one can have at
>   least a "flat" thread which is anchored in the first msg for
>   this issue.
>
> There are a few issues with these patches: roundupdb should still
> work if the inreplyto property is not present in the database scheme,
> but catching KeyError is perhaps not the best solution to do that.
> I know that mailgw breaks when trying to set the inreplyto property
> if it isn't there - I don't really know how to do it better in the
> self.db.msg.create() call. I also don't know how to store None
> as property value - should the property be omitted? mailgw currently
> stores empty strings instead, which isn't quite the same.

Hrm - the mechanism is a nice idea - but requires that the message-id also be 
stored on each node. You can't support threading in the web interface without 
it. And having threading in the web interface would be pretty doovy - as I 
think about it, it's actually one of the problems I have with most bug 
trackers - the inability to directly comment on something someone said much 
earlier in the life of an issue. Threading would help that a lot. Do you feel 
up to producing a new patch with messageid generation for web messages?

I have fixed the other issues you mention in the CVS - I would appreciate it 
if you could produce your newer patches against that.


> The last issue is that adding these properties was done by
> simply adding inreplyto=String() to the constructor for issue and
> msg in dbinit.py. Now there are issues that don't have a valid
> value for this property and "roundup-admin table issue" fails with
>    Error: issue has no property "inreplyto"
>
> Is this an error in roundup-admin, or should I have added these
> properties in some better way?

This should be handled properly. I'll fix it.


     Richard

 Richard Jones wrote:
>On Wednesday 12 December 2001 4:32 pm, Damon M. Conway wrote:
>> damon@chiba ~/temp2/roundup-cvs/roundup/roundup/backends> python
>> Python 2.0 (#1, Dec  4 2001, 17:06:44)
>> [GCC 2.95.3 20010315 (release)] on linux2
>> Type "copyright", "credits" or "license" for more information.
>>
>> >>> import anydbm, dumbdbm
>> >>> assert anydbm._defaultmod != dumbdbm
>> >>> del anydbm
>> >>> del dumbdbm
>> >>> import back_anydbm
>>
>> Hey, lookie there.  Imagine that.
>
>Yeah :)
>
>Still doesn't fix the problem that if you import backends, which does the
>above commands, you don't actually get back_anydbm...
>
>I wonder if maybe it's a python 2.0 problem? Could you try 2.1.1?

Well, I upgraded to python 2.1.1, and now it seg faults.  When I run python
by itself and import (roundup.backends) I seem to be getting the proper
results tho.

damon@chiba ~/temp2/roundup-cvs/roundup> python
Python 2.1.1 (#1, Dec 12 2001, 10:56:43)
[GCC 2.95.3 20010315 (release)] on linux2
Type "copyright", "credits" or "license" for more information.
>>> import roundup.backends
>>> dir(roundup.backends)
['__all__', '__builtins__', '__doc__', '__file__', '__name__', '__path__',
'anydbm', 'back_anydbm', 'back_bsddb', 'bsddb']
>>> 

So, if I can figure out why python is segfaulting, I think it might work.

Thanks,
Damon

--
"UNIX was not designed to stop you from doing stupid things, because that
 would also stop you from doing clever things."  --Doug Gwyn

On Mon, 2001-12-10 at 18:04, Patrick Ohly wrote:
> I did some further modifications myself, which I attach as diffs
> to this mail:
[...]

Hmm, I guess I was hoping for a slightly more enthusiastic response
to my suggestions ;-) Have I missed something, or was there really
no response at all?

I was thinking about introducing roundup to our teams now, but
I'd like to know if these additional features have any chance of
getting into the mainstream roundup first.

-- 
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:
>On Wednesday 12 December 2001 4:32 pm, Damon M. Conway wrote:
>> damon@chiba ~/temp2/roundup-cvs/roundup/roundup/backends> python
>> Python 2.0 (#1, Dec  4 2001, 17:06:44)
>> [GCC 2.95.3 20010315 (release)] on linux2
>> Type "copyright", "credits" or "license" for more information.
>>
>> >>> import anydbm, dumbdbm
>> >>> assert anydbm._defaultmod != dumbdbm
>> >>> del anydbm
>> >>> del dumbdbm
>> >>> import back_anydbm
>>
>> Hey, lookie there.  Imagine that.
>
>Yeah :)
>
>Still doesn't fix the problem that if you import backends, which does the
>above commands, you don't actually get back_anydbm...

True...

>I wonder if maybe it's a python 2.0 problem? Could you try 2.1.1?

Erm, I'll check on that package tommorrow.  Last time I checked, it was
still broken (the Gentoo package that is).  If not, I'll work on manually
compiling python 2.1.1.

>> Damon - I think it's bedtime.
>
>OK - we can try again tomorrow if you're up for it :)

Yep, it's not like they expect me to really work at the office anyway. :)

Thanks,
Damon

--
"UNIX was not designed to stop you from doing stupid things, because that
 would also stop you from doing clever things."  --Doug Gwyn

On Wednesday 12 December 2001 4:32 pm, Damon M. Conway wrote:
> damon@chiba ~/temp2/roundup-cvs/roundup/roundup/backends> python
> Python 2.0 (#1, Dec  4 2001, 17:06:44)
> [GCC 2.95.3 20010315 (release)] on linux2
> Type "copyright", "credits" or "license" for more information.
>
> >>> import anydbm, dumbdbm
> >>> assert anydbm._defaultmod != dumbdbm
> >>> del anydbm
> >>> del dumbdbm
> >>> import back_anydbm
>
> Hey, lookie there.  Imagine that.

Yeah :)

Still doesn't fix the problem that if you import backends, which does the 
above commands, you don't actually get back_anydbm...

I wonder if maybe it's a python 2.0 problem? Could you try 2.1.1?


> Damon - I think it's bedtime.

OK - we can try again tomorrow if you're up for it :)


    Richard

 Richard Jones wrote:
>On Wednesday 12 December 2001 4:17 pm, Damon M. Conway wrote:
>> >>> import anydbm, dumbdmb
>>
>> Traceback (most recent call last):
>>   File "<stdin>", line 1, in ?
>> ImportError: No module named dumbdmb
>
>*cough* that's "dumbdbm" not "dumbdmb" :)
>
>the rest of the tests fail because of this... please re-try them...

erm...ya. :)  *blush*

damon@chiba ~/temp2/roundup-cvs/roundup/roundup/backends> python
Python 2.0 (#1, Dec  4 2001, 17:06:44) 
[GCC 2.95.3 20010315 (release)] on linux2
Type "copyright", "credits" or "license" for more information.
>>> import anydbm, dumbdbm
>>> assert anydbm._defaultmod != dumbdbm
>>> del anydbm
>>> del dumbdbm
>>> import back_anydbm
>>> 

Hey, lookie there.  Imagine that.

Damon - I think it's bedtime.

--
"UNIX was not designed to stop you from doing stupid things, because that
 would also stop you from doing clever things."  --Doug Gwyn

On Wednesday 12 December 2001 4:17 pm, Damon M. Conway wrote:
> >>> import anydbm, dumbdmb
>
> Traceback (most recent call last):
>   File "<stdin>", line 1, in ?
> ImportError: No module named dumbdmb

*cough* that's "dumbdbm" not "dumbdmb" :)

the rest of the tests fail because of this... please re-try them...


    Richard

 Richard Jones wrote:
>On Wednesday 12 December 2001 3:58 pm, Damon M. Conway wrote:
>>  Richard Jones wrote:
>> >On Wednesday 12 December 2001 3:29 pm, Damon M. Conway wrote:
>> >
>> >What do you get if you:
>> >
>> >% python
>> >
>> >>>> import roundup.backends
>> >>>> dir(roundup.backends)
>> >
>> >['__all__', '__builtins__', '__doc__', '__file__', '__name__', '__path
>__'
>> >,
>> >'anydbm', 'back_anydbm', 'back_bsddb', 'back_bsddb3', 'bsddb', 'bsddb3
>']
>>
>> Python 2.0 (#1, Dec  4 2001, 17:06:44)
>> [GCC 2.95.3 20010315 (release)] on linux2
>> Type "copyright", "credits" or "license" for more information.
>>
>> >>> import roundup.backends
>> >>> dir(roundup.backends)
>>
>> ['__all__', '__builtins__', '__doc__', '__file__', '__name__', '__path_
>_']
>>
>>
>> Hmmm, I'm missing some things.
>>
>> damon@chiba ~/temp2/roundup-cvs/roundup> ls roundup/backends/
>> CVS/         __init__.pyc    back_anydbm.pyc  back_bsddb.pyc
>> back_bsddb3.pyc
>> __init__.py  back_anydbm.py  back_bsddb.py    back_bsddb3.py
>> damon@chiba ~/temp2/roundup-cvs/roundup>
>
>Hang on - do you still have the modified dumbdbm.py in your roundup source 
>root directory? If so, please delete it and re-try the tests.

Nope, I haven't put it into my CVS source tree.

>Otherwise, please cd to the roundup/backends directory and try:
>
>>>> import anydbm, dumbdbm
>>>> assert anydbm._defaultmod != dumbdbm
>>>> del anydbm
>>>> del dumbdbm
>>>> import back_anydbm
>>>> 

damon@chiba ~/temp2/roundup-cvs/roundup/roundup/backends> python
Python 2.0 (#1, Dec  4 2001, 17:06:44) 
[GCC 2.95.3 20010315 (release)] on linux2
Type "copyright", "credits" or "license" for more information.
>>> import anydbm, dumbdmb
Traceback (most recent call last):
  File "<stdin>", line 1, in ?
ImportError: No module named dumbdmb
>>> assert anydbm._defaultmod != dumbdbm
Traceback (most recent call last):
  File "<stdin>", line 1, in ?
NameError: There is no variable named 'dumbdbm'
>>> del anydbm
>>> del dumbdbm
Traceback (most recent call last):
  File "<stdin>", line 1, in ?
NameError: There is no variable named 'dumbdbm'
>>> import back_anydbm
>>> 

There isn't anything in my roundup/backends dealing with dumbdbm.  I take
it there should be?

Damon

--
"UNIX was not designed to stop you from doing stupid things, because that
 would also stop you from doing clever things."  --Doug Gwyn

On Wednesday 12 December 2001 3:58 pm, Damon M. Conway wrote:
>  Richard Jones wrote:
> >On Wednesday 12 December 2001 3:29 pm, Damon M. Conway wrote:
> >>  Richard Jones wrote:
> >> > On Wednesday 12 December 2001 2:53 pm, Damon M. Conway wrote:
> >> > > damon@chiba ~/temp2/roundup-cvs/roundup> cvs update
> >> > > P roundup/backends/back_anydbm.py
> >> >
> >> >What does 'P' mean? My man page only mentions 'U A R M C ?'...
> >>
> >> Apparently, it means patched.  Basically, it means "I succeeded in
> >> updating this file."
> >
> >Ah, thanks :)
>
> No problem.  Glad I could answer one of your questions. :)
>
> >> >OK, that's odd. You're up-to-date with the CVS (barring whatever that
> >> > 'P' means). The anydbm module should work, and if it doesn't, then
> >> > "python -c 'import roundup.backends.back_anydbm'" should fail in a
> >> > useful manner. For the moment, I'm stumped... I'll keep thinking about
> >> > it though ...
> >>
> >> Perhaps something with my python installation?
> >
> >What do you get if you:
> >
> >% python
> >
> >>>> import roundup.backends
> >>>> dir(roundup.backends)
> >
> >['__all__', '__builtins__', '__doc__', '__file__', '__name__', '__path__'
> >,
> >'anydbm', 'back_anydbm', 'back_bsddb', 'back_bsddb3', 'bsddb', 'bsddb3']
>
> Python 2.0 (#1, Dec  4 2001, 17:06:44)
> [GCC 2.95.3 20010315 (release)] on linux2
> Type "copyright", "credits" or "license" for more information.
>
> >>> import roundup.backends
> >>> dir(roundup.backends)
>
> ['__all__', '__builtins__', '__doc__', '__file__', '__name__', '__path__']
>
>
> Hmmm, I'm missing some things.
>
> damon@chiba ~/temp2/roundup-cvs/roundup> ls roundup/backends/
> CVS/         __init__.pyc    back_anydbm.pyc  back_bsddb.pyc
> back_bsddb3.pyc
> __init__.py  back_anydbm.py  back_bsddb.py    back_bsddb3.py
> damon@chiba ~/temp2/roundup-cvs/roundup>

Hang on - do you still have the modified dumbdbm.py in your roundup source 
root directory? If so, please delete it and re-try the tests.

Otherwise, please cd to the roundup/backends directory and try:

>>> import anydbm, dumbdbm
>>> assert anydbm._defaultmod != dumbdbm
>>> del anydbm
>>> del dumbdbm
>>> import back_anydbm
>>> 


     Richard

 Richard Jones wrote:
>On Wednesday 12 December 2001 3:29 pm, Damon M. Conway wrote:
>>  Richard Jones wrote:
>> > On Wednesday 12 December 2001 2:53 pm, Damon M. Conway wrote:
>> > > damon@chiba ~/temp2/roundup-cvs/roundup> cvs update
>> > > P roundup/backends/back_anydbm.py
>> >
>> >What does 'P' mean? My man page only mentions 'U A R M C ?'...
>>
>> Apparently, it means patched.  Basically, it means "I succeeded in updating
>> this file."
>
>Ah, thanks :)

No problem.  Glad I could answer one of your questions. :)

>> >OK, that's odd. You're up-to-date with the CVS (barring whatever that 'P'
>> >means). The anydbm module should work, and if it doesn't, then
>> >"python -c 'import roundup.backends.back_anydbm'" should fail in a useful
>> >manner. For the moment, I'm stumped... I'll keep thinking about it though
>> >...
>>
>> Perhaps something with my python installation?
>
>What do you get if you:
>
>% python
>>>> import roundup.backends
>>>> dir(roundup.backends)
>['__all__', '__builtins__', '__doc__', '__file__', '__name__', '__path__'
>, 
>'anydbm', 'back_anydbm', 'back_bsddb', 'back_bsddb3', 'bsddb', 'bsddb3']
>>>> 

Python 2.0 (#1, Dec  4 2001, 17:06:44)
[GCC 2.95.3 20010315 (release)] on linux2
Type "copyright", "credits" or "license" for more information.
>>> import roundup.backends
>>> dir(roundup.backends)
['__all__', '__builtins__', '__doc__', '__file__', '__name__', '__path__']
>>> 

Hmmm, I'm missing some things.

damon@chiba ~/temp2/roundup-cvs/roundup> ls roundup/backends/
CVS/         __init__.pyc    back_anydbm.pyc  back_bsddb.pyc
back_bsddb3.pyc
__init__.py  back_anydbm.py  back_bsddb.py    back_bsddb3.py
damon@chiba ~/temp2/roundup-cvs/roundup>

Damon

--
"UNIX was not designed to stop you from doing stupid things, because that
 would also stop you from doing clever things."  --Doug Gwyn

On Wednesday 12 December 2001 3:29 pm, Damon M. Conway wrote:
>  Richard Jones wrote:
> > On Wednesday 12 December 2001 2:53 pm, Damon M. Conway wrote:
> > > damon@chiba ~/temp2/roundup-cvs/roundup> cvs update
> > > P roundup/backends/back_anydbm.py
> >
> >What does 'P' mean? My man page only mentions 'U A R M C ?'...
>
> Apparently, it means patched.  Basically, it means "I succeeded in updating
> this file."

Ah, thanks :)


> >OK, that's odd. You're up-to-date with the CVS (barring whatever that 'P'
> >means). The anydbm module should work, and if it doesn't, then
> >"python -c 'import roundup.backends.back_anydbm'" should fail in a useful
> >manner. For the moment, I'm stumped... I'll keep thinking about it though
> >...
>
> Perhaps something with my python installation?

What do you get if you:

% python
>>> import roundup.backends
>>> dir(roundup.backends)
['__all__', '__builtins__', '__doc__', '__file__', '__name__', '__path__', 
'anydbm', 'back_anydbm', 'back_bsddb', 'back_bsddb3', 'bsddb', 'bsddb3']
>>> 


    Richard

 Richard Jones wrote:
>On Wednesday 12 December 2001 2:53 pm, Damon M. Conway wrote:
>> >So you get no changes if you do a "cvs up" right now? Do the tests run
> OK
>> > now?
>>
>> damon@chiba ~/temp2/roundup-cvs/roundup> cvs login
>> (Logging in to ano...@cv...)
>> CVS password:
>> damon@chiba ~/temp2/roundup-cvs/roundup> cvs update
>> P roundup/backends/back_anydbm.py
>
>What does 'P' mean? My man page only mentions 'U A R M C ?'...

Apparently, it means patched.  Basically, it means "I succeeded in updating
this file."

>> damon@chiba ~/temp2/roundup-cvs/roundup> python -c 'import test;test.go()'
>> Traceback (most recent call last):
>>   File "<string>", line 1, in ?
>>   File "test/__init__.py", line 22, in ?
>>     import test_dates, test_schema, test_db, test_multipart, test_mailsplit
>>   File "test/test_schema.py", line 22, in ?
>>     from roundup.backends import anydbm
>> ImportError: cannot import name anydbm
>> damon@chiba ~/temp2/roundup-cvs/roundup>
>
>OK, that's odd. You're up-to-date with the CVS (barring whatever that 'P'
>means). The anydbm module should work, and if it doesn't, then
>"python -c 'import roundup.backends.back_anydbm'" should fail in a useful
>manner. For the moment, I'm stumped... I'll keep thinking about it though
>...

Perhaps something with my python installation?

Damon

--
"UNIX was not designed to stop you from doing stupid things, because that
 would also stop you from doing clever things."  --Doug Gwyn

On Wednesday 12 December 2001 2:53 pm, Damon M. Conway wrote:
> >So you get no changes if you do a "cvs up" right now? Do the tests run OK
> > now?
>
> damon@chiba ~/temp2/roundup-cvs/roundup> cvs login
> (Logging in to ano...@cv...)
> CVS password:
> damon@chiba ~/temp2/roundup-cvs/roundup> cvs update
> P roundup/backends/back_anydbm.py

What does 'P' mean? My man page only mentions 'U A R M C ?'...


> damon@chiba ~/temp2/roundup-cvs/roundup> python -c 'import test;test.go()'
> Traceback (most recent call last):
>   File "<string>", line 1, in ?
>   File "test/__init__.py", line 22, in ?
>     import test_dates, test_schema, test_db, test_multipart, test_mailsplit
>   File "test/test_schema.py", line 22, in ?
>     from roundup.backends import anydbm
> ImportError: cannot import name anydbm
> damon@chiba ~/temp2/roundup-cvs/roundup>

OK, that's odd. You're up-to-date with the CVS (barring whatever that 'P' 
means). The anydbm module should work, and if it doesn't, then
"python -c 'import roundup.backends.back_anydbm'" should fail in a useful 
manner. For the moment, I'm stumped... I'll keep thinking about it though...


    Richard

 Richard Jones wrote:
>On Wednesday 12 December 2001 2:29 pm, Damon M. Conway wrote:
>>  Richard Jones wrote:
>> >
>> >Erm, that's odd. What does "python -c 'import
>> > roundup.backends.back_anydbm'" say?
>>
>> Odd, it gives me nothing.  I should do that in the source root, correct
>?
>
>That's what I'd expect. That means that the import worked with no exceptions. 
>That means that you should now get no errors in the tests...

Ok.

>So you get no changes if you do a "cvs up" right now? Do the tests run OK
> now?

damon@chiba ~/temp2/roundup-cvs/roundup> cvs login
(Logging in to ano...@cv...)
CVS password: 
damon@chiba ~/temp2/roundup-cvs/roundup> cvs update
cvs server: Updating .
cvs server: Updating bin
cvs server: Updating cgi-bin
cvs server: Updating doc
cvs server: Updating doc/images
cvs server: Updating roundup
cvs server: Updating roundup/backends
P roundup/backends/back_anydbm.py
cvs server: Updating roundup/templates
cvs server: Updating roundup/templates/classic
cvs server: Updating roundup/templates/classic/detectors
cvs server: Updating roundup/templates/classic/html
cvs server: Updating roundup/templates/extended
cvs server: Updating roundup/templates/extended/detectors
cvs server: Updating roundup/templates/extended/html
cvs server: Updating roundup/templates/extended/html_templates
cvs server: Updating templates
cvs server: Updating templates/detectors
cvs server: Updating templates/templates
cvs server: Updating test
cvs server: Updating test/data
cvs server: Updating tests
cvs server: Updating tools
damon@chiba ~/temp2/roundup-cvs/roundup> python -c 'import test;test.go()'
Traceback (most recent call last):
  File "<string>", line 1, in ?
  File "test/__init__.py", line 22, in ?
    import test_dates, test_schema, test_db, test_multipart, test_mailsplit
  File "test/test_schema.py", line 22, in ?
    from roundup.backends import anydbm
ImportError: cannot import name anydbm
damon@chiba ~/temp2/roundup-cvs/roundup> 

Damon

--
"UNIX was not designed to stop you from doing stupid things, because that
 would also stop you from doing clever things."  --Doug Gwyn

On Wednesday 12 December 2001 2:29 pm, Damon M. Conway wrote:
>  Richard Jones wrote:
> >
> >Erm, that's odd. What does "python -c 'import
> > roundup.backends.back_anydbm'" say?
>
> Odd, it gives me nothing.  I should do that in the source root, correct?

That's what I'd expect. That means that the import worked with no exceptions. 
That means that you should now get no errors in the tests...


> >The CVS has a newer version of the database checking - could you give that
> > a try please?
>
> I did.  That was in the source dir of the cvs tree I just checked out after
> reading your email.

So you get no changes if you do a "cvs up" right now? Do the tests run OK now?


    Richard

 Richard Jones wrote:
>On Wednesday 12 December 2001 1:52 pm, Damon M. Conway wrote:
>>  Richard Jones wrote:
>> >I believe I've just fixed the problems some users were having when run
>nin
>> >g
>> >the unit tests on certain platforms. Could those users please get the 
>lat
>> >est
>> >CVS (instructions are on http://roundup.sf.net/ in the project pages) 
>and
>> > run
>> >the unit tests again using:
>> >
>> >   python -c 'import test;test.go()'
>>
>> Hmm, no matter what I do, I get this error.
>>
>> damon@chiba ~/temp2/roundup-cvs/roundup> python -c 'import test;test.go
>()'
>> Traceback (most recent call last):
>>   File "<string>", line 1, in ?
>>   File "test/__init__.py", line 22, in ?
>>     import test_dates, test_schema, test_db, test_multipart, test_mails
>plit
>>   File "test/test_schema.py", line 22, in ?
>>     from roundup.backends import anydbm
>> ImportError: cannot import name anydbm
>
>Erm, that's odd. What does "python -c 'import roundup.backends.back_anydbm'" 
>say?

Odd, it gives me nothing.  I should do that in the source root, correct?

damon@chiba ~/temp2/roundup-cvs/roundup> ls
BUILD.txt    I18N_PROGRESS.txt  README.txt  roundup/         setup.py
tools/
CHANGES.txt  INSTALL.txt        bin/        roundup-admin*   templates/
CVS/         MANIFEST.in        cgi-bin/    roundup-mailgw*  test/
ChangeLog    MIGRATION.txt      doc/        roundup-server*  tests/
damon@chiba ~/temp2/roundup-cvs/roundup> python -c 'import
roundup.backends.back_anydbm'
damon@chiba ~/temp2/roundup-cvs/roundup> 

My wrapping kinda fubars that, but it should be clear what happened.

>The CVS has a newer version of the database checking - could you give that a 
>try please?

I did.  That was in the source dir of the cvs tree I just checked out after
reading your email.

Damon

--
"UNIX was not designed to stop you from doing stupid things, because that
 would also stop you from doing clever things."  --Doug Gwyn