roundup-users

Re: [Roundup-users] Troubles installing

[steve j. <st...@si...>]

Quoting Richard Jones (ri...@bi...):

> On Thursday 02 August 2001 16:29, steve jenson wrote:
> > Is there a 'preferred' db library to go with? Granted, roundup should work
> > fine with any libarary that correctly wraps bdb but I'd rather have it up
> > and running sooner rather than later.
> 
> Well, it should work with no troubles using either the anydbm or bsddb 
> backends (anydbm will actually use bsddb through dbhash if it's installed, 
> but not bsddb3). Could you try that and let me know how it goes?

I went with anybdm. It built and installed like a charm but now I get an odd
error when I run roundup-admin init:

[stevej@missdevil stevej]$ roundup-admin init
Enter instance home: /usr/local/www/roundup
Templates: classic, extended
Select template [classic]:
Back ends: anydbm, bsddb
Select backend [anydbm]:
Admin Password:
       Confirm:
Traceback (most recent call last):
  File "/usr/local/bin/roundup-admin", line 404, in ?
    sys.exit(main())
  File "/usr/local/bin/roundup-admin", line 370, in main
    return do_init(instance_home, args)
  File "/usr/local/bin/roundup-admin", line 124, in do_init
    init.init(instance_home, template, backend, adminpw)
  File "/usr/local/lib/python2.1/site-packages/roundup/init.py", line 56, in init
    instance.init(adminpw)
TypeError: object is not callable: <module 'roundup.init' from '/usr/local/lib/python2.1/site-packages/roundup/init.pyc'>

 
what do you think?


steve

-- 
steve jenson <st...@si...> http://sieve.net/
PGP fingerprint: 79D0 4836 11E4 A43A 0179  FC97 3AE2 008E 1E57 6138

Re: [Roundup-users] Troubles installing

[steve j. <st...@si...>]

Quoting Richard Jones (ri...@bi...):

> On Thursday 02 August 2001 16:29, steve jenson wrote:
> > Is there a 'preferred' db library to go with? Granted, roundup should work
> > fine with any libarary that correctly wraps bdb but I'd rather have it up
> > and running sooner rather than later.
> 
> Well, it should work with no troubles using either the anydbm or bsddb 
> backends (anydbm will actually use bsddb through dbhash if it's installed, 
> but not bsddb3). Could you try that and let me know how it goes?

I went with anybdm. It built and installed like a charm but now I get an odd
error when I run roundup-admin init:

[stevej@missdevil stevej]$ roundup-admin init
Enter instance home: /usr/local/www/roundup
Templates: classic, extended
Select template [classic]:
Back ends: anydbm, bsddb
Select backend [anydbm]:
Admin Password:
       Confirm:
Traceback (most recent call last):
  File "/usr/local/bin/roundup-admin", line 404, in ?
    sys.exit(main())
  File "/usr/local/bin/roundup-admin", line 370, in main
    return do_init(instance_home, args)
  File "/usr/local/bin/roundup-admin", line 124, in do_init
    init.init(instance_home, template, backend, adminpw)
  File "/usr/local/lib/python2.1/site-packages/roundup/init.py", line 56, in init
    instance.init(adminpw)
TypeError: object is not callable: <module 'roundup.init' from '/usr/local/lib/python2.1/site-packages/roundup/init.pyc'>

 
what do you think?


steve

PS. I sent this last night but it never seemed to get out (my DSL was
hopping up and down) so my apologies for any duplicates.

-- 
steve jenson <st...@si...> http://sieve.net/
PGP fingerprint: 79D0 4836 11E4 A43A 0179  FC97 3AE2 008E 1E57 6138

Re: [Roundup-users] Troubles installing

[Richard J. <ri...@bi...>]

On Friday 03 August 2001 04:35, steve jenson wrote:
> Quoting Richard Jones (ri...@bi...):
> > On Thursday 02 August 2001 16:29, steve jenson wrote:
> > > Is there a 'preferred' db library to go with? Granted, roundup should
> > > work fine with any libarary that correctly wraps bdb but I'd rather
> > > have it up and running sooner rather than later.
> >
> > Well, it should work with no troubles using either the anydbm or bsddb
> > backends (anydbm will actually use bsddb through dbhash if it's
> > installed, but not bsddb3). Could you try that and let me know how it
> > goes?
>
> I went with anybdm. It built and installed like a charm but now I get an
> odd error when I run roundup-admin init:
>
> [stevej@missdevil stevej]$ roundup-admin init
> Enter instance home: /usr/local/www/roundup

The short answer is that the instance name you've chosen has clashed with an 
installed python package - namely the roundup package. Choose another name, 
and you'll be ok.

I really should have the init command check to see if you're duplicating an 
existing module name when you select your instance home. Hrm. I think we've 
found a flaw in the "instances are packages" idea here. Grr. 



     Richard

Re: [Roundup-users] Troubles installing

[Richard J. <ri...@bi...>]

On Friday 03 August 2001 09:27, Richard Jones wrote:
> The short answer is that the instance name you've chosen has clashed with
> an installed python package - namely the roundup package. Choose another
> name, and you'll be ok.
>
> I really should have the init command check to see if you're duplicating an
> existing module name when you select your instance home. Hrm. I think we've
> found a flaw in the "instances are packages" idea here. Grr.

Even better - I've fixed this so that the import can handle "roundup" (or any 
other existing python package name) as the tail of the instance home.



     Richard

Re: [Roundup-users] Troubles installing

[steve j. <st...@si...>]

Quoting Richard Jones (ri...@bi...):

> On Friday 03 August 2001 09:27, Richard Jones wrote:
> > The short answer is that the instance name you've chosen has clashed with
> > an installed python package - namely the roundup package. Choose another
> > name, and you'll be ok.
> >
> > I really should have the init command check to see if you're duplicating an
> > existing module name when you select your instance home. Hrm. I think we've
> > found a flaw in the "instances are packages" idea here. Grr.
> 
> Even better - I've fixed this so that the import can handle "roundup" (or any 
> other existing python package name) as the tail of the instance home.

Great! I'm having a bear of a time with mod_rewrite, for some reason
I didn't compile it in with everything else oh so long ago.. time for
a recompile since apxs says that mod_rewrite.c isn't a DSO. 

soon, though. 

cheers,
steve


-- 
steve jenson <st...@si...> http://sieve.net/
PGP fingerprint: 79D0 4836 11E4 A43A 0179  FC97 3AE2 008E 1E57 6138

Re: [Roundup-users] Troubles installing

[steve j. <st...@si...>]

Apache rebuilt, RewriteEngine is acting fine and dandy except that 
for http://bugs.sieve.net/roundup/roundup.cgi/ it gives me a 403 -
Forbidden page, which seems odd as the page doesn't actually exist.

As an experiment, I placed roundup.cgi into the cgi-bin/ directory and
tried playing with it from there, and when I go to:

http://bugs.sieve.net/cgi-bin/roundup.cgi/e-lang 

and it pops up an HTTP authorization box, I put in admin and the
password I entered at init time. Not surprisingly, it didn't work.

I'll be honest, I tried following your instructions to the very letter,
on multiple occasions. I'm quite surprised it's not working, it seems
straight-forward enough.

cheers,
steve

Quoting steve jenson (st...@si...):

> Quoting Richard Jones (ri...@bi...):
> 
> > On Friday 03 August 2001 09:27, Richard Jones wrote:
> > > The short answer is that the instance name you've chosen has clashed with
> > > an installed python package - namely the roundup package. Choose another
> > > name, and you'll be ok.
> > >
> > > I really should have the init command check to see if you're duplicating an
> > > existing module name when you select your instance home. Hrm. I think we've
> > > found a flaw in the "instances are packages" idea here. Grr.
> > 
> > Even better - I've fixed this so that the import can handle "roundup" (or any 
> > other existing python package name) as the tail of the instance home.
> 
> Great! I'm having a bear of a time with mod_rewrite, for some reason
> I didn't compile it in with everything else oh so long ago.. time for
> a recompile since apxs says that mod_rewrite.c isn't a DSO. 
> 
> soon, though. 
> 
> cheers,
> steve
> 
> 
> -- 
> steve jenson <st...@si...> http://sieve.net/
> PGP fingerprint: 79D0 4836 11E4 A43A 0179  FC97 3AE2 008E 1E57 6138
> 
> _______________________________________________
> Roundup-users mailing list
> Rou...@li...
> http://lists.sourceforge.net/lists/listinfo/roundup-users

-- 
steve jenson <st...@si...> http://sieve.net/
PGP fingerprint: 79D0 4836 11E4 A43A 0179  FC97 3AE2 008E 1E57 6138

Re: [Roundup-users] Troubles installing

[Richard J. <ri...@op...>]

On Sun, 5 Aug 2001 05:30, steve jenson wrote:
> Apache rebuilt, RewriteEngine is acting fine and dandy except that
> for http://bugs.sieve.net/roundup/roundup.cgi/ it gives me a 403 -
> Forbidden page, which seems odd as the page doesn't actually exist.

Yes, you should get some other kind of error here, not an auth error. Do you 
have some other site-wide authentication in place? I'm very rusty when it 
comes to Apache, I'm afraid.


> As an experiment, I placed roundup.cgi into the cgi-bin/ directory and
> tried playing with it from there, and when I go to:
>
> http://bugs.sieve.net/cgi-bin/roundup.cgi/e-lang
>
> and it pops up an HTTP authorization box, I put in admin and the
> password I entered at init time. Not surprisingly, it didn't work.

Yes, that's what I'd expect to see.


> I'll be honest, I tried following your instructions to the very letter,
> on multiple occasions. I'm quite surprised it's not working, it seems
> straight-forward enough.

If you print the auth information in the CGI script, what do you get? In the 
main() function, print the auth variable. You should see a short base64 
string.

Are you sure that the RewriteRule line is not broken over two lines?

Sorry, I can't think of anything else at the moment...


    Richard

Re: [Roundup-users] Troubles installing

[steve j. <st...@si...>]

Quoting Richard Jones (ri...@op...):

> On Sun, 5 Aug 2001 05:30, steve jenson wrote:
> > Apache rebuilt, RewriteEngine is acting fine and dandy except that
> > for http://bugs.sieve.net/roundup/roundup.cgi/ it gives me a 403 -
> > Forbidden page, which seems odd as the page doesn't actually exist.
> 
> Yes, you should get some other kind of error here, not an auth error. Do you 
> have some other site-wide authentication in place? I'm very rusty when it 
> comes to Apache, I'm afraid.

When I woke up this morning, I realized that I had forgotten to turn the 
ExecCGI function on for this directory. Now the rewrite rule works great but
I have the same error, ValueError: No such instance ""  when I attempt to
access:

http://bugs.sieve.net/roundup/roundup.cgi/


> > As an experiment, I placed roundup.cgi into the cgi-bin/ directory and
> > tried playing with it from there, and when I go to:
> >
> > http://bugs.sieve.net/cgi-bin/roundup.cgi/e-lang
> >
> > and it pops up an HTTP authorization box, I put in admin and the
> > password I entered at init time. Not surprisingly, it didn't work.
> 
> Yes, that's what I'd expect to see.

You would expect to see the authorization box or you would expect to see it
not work also?  

> > I'll be honest, I tried following your instructions to the very letter,
> > on multiple occasions. I'm quite surprised it's not working, it seems
> > straight-forward enough.
> 
> If you print the auth information in the CGI script, what do you get? In the 
> main() function, print the auth variable. You should see a short base64 
> string.

umm.. this is strange, Somehow placing

print auth

on line 50 resulted in the authorization working. Now there is a something, 
as can be seen in the following screenshots:

http://sieve.net/images/first_admin.png

When I click on the admin link at the top, I get the following page:

http://sieve.net/images/clicked_on_admin.png

or if I click on the any of the links below
[ID|Activity|Priority|Title|Status|AssignedTo], I get the following
error screen:

http://sieve.net/images/clicked_on_id.png

An interesting note, the link that this screen shot shows is the following:

http://bugs.sieve.net/roundup/roundup.cgi/issue?status=1,2,3,4,5,6,7&:columns=id,activity,priority,title,status,assignedto&:group=id,activity,priority&:sort=id,-activity

and if I place a e-lang/ between roundup.cgi/ and issue, I get back to the 
first_admin.png screen.


Hopefully I haven't confused the issue,
steve

BTW, if you want the admin password please feel free to send me a private
email.

-- 
steve jenson <st...@si...> http://sieve.net/
PGP fingerprint: 79D0 4836 11E4 A43A 0179  FC97 3AE2 008E 1E57 6138

Re: [Roundup-users] Troubles installing

[Richard J. <ri...@bi...>]

On Monday 06 August 2001 07:45, steve jenson wrote:
> Quoting Richard Jones (ri...@op...):
> > On Sun, 5 Aug 2001 05:30, steve jenson wrote:
> > > Apache rebuilt, RewriteEngine is acting fine and dandy except that
> > > for http://bugs.sieve.net/roundup/roundup.cgi/ it gives me a 403 -
> > > Forbidden page, which seems odd as the page doesn't actually exist.
> >
> > Yes, you should get some other kind of error here, not an auth error. Do
> > you have some other site-wide authentication in place? I'm very rusty
> > when it comes to Apache, I'm afraid.
>
> When I woke up this morning, I realized that I had forgotten to turn the
> ExecCGI function on for this directory. Now the rewrite rule works great
> but I have the same error, ValueError: No such instance ""  when I attempt
> to access:
>
> http://bugs.sieve.net/roundup/roundup.cgi/

The CGI is expecting you to nominate a roundup instance as per:

 http://bugs.sieve.net/cgi-bin/roundup.cgi/e-lang/
                                           ^^^^^^

where you've edited the ROUNDUP_INSTANCE_HOMES in the CGI script so that 
'e-lang' points to the instance home directory. Which is what you've done 
below...


> > > I'll be honest, I tried following your instructions to the very letter,
> > > on multiple occasions. I'm quite surprised it's not working, it seems
> > > straight-forward enough.
> >
> > If you print the auth information in the CGI script, what do you get? In
> > the main() function, print the auth variable. You should see a short
> > base64 string.
>
> umm.. this is strange, Somehow placing
>
> print auth
>
> on line 50 resulted in the authorization working.

That's worrying. Or did you do this in conjunction with the ExecCGI above?


> Now there is a something,
> as can be seen in the following screenshots:

The problem you're seeing is that the CGI isn't too smart about the URLs it 
generates - if the URL you use to access it is:

 http://bugs.sieve.net/cgi-bin/roundup.cgi/e-lang

then the urls in the page (eg. '<a href="user1">My Details</a>') will result 
in an absolute URL of:

 http://bugs.sieve.net/cgi-bin/roundup.cgi/user1

... which is trying to access the "user1" instance of roundup, which doesn't 
exist. Simply adding a trailing '/' to the first URL will fix it. I'm going 
to amend the documentation and CGI so that we're forced to append "index" to 
the URL. So both of these will work:

 http://bugs.sieve.net/cgi-bin/roundup.cgi/e-lang/
 http://bugs.sieve.net/cgi-bin/roundup.cgi/e-lang/index


Thanks for the invaluable feedback!


      Richard