After upgrading to version 1.5.0 and removing this component from my
host, I was no longer able to run as a windows service.

Is this component still required in order to run Roundup Issue Tracker
as a windows service?

In message <1388164230.8.0.283533984591.issue2550827@psf.upfronthosting.co.za> 
<1388164230.8.0.283533984591.issue2550827@psf.upfronthosting.co.za>,
Matt writes:
>After upgrading to version 1.5.0 and removing this component from my
>host, I was no longer able to run as a windows service.
>
>Is this component still required in order to run Roundup Issue Tracker
>as a windows service?

The requirement for pywin32 seems to have been removed in the commit
referred to by this message:

  http://sourceforge.net/mailarchive/message.php?msg_id=30153584

What python vendor/version are you using?

Also can you start the server manually (i.e. not as a service).

When you try to run it as a service are there any tracebacks or event
logs?

Thanks for that link, there is more info there than I appreciated from
reading the Changes.txt. I see that it does state: "You can run Roundup
as a Windows service if pywin32_ is installed." in the Optional
Components Section...

I am running python V2.6.6 from http://www.python.org/ and I could start
the server from the command line...

Perhaps the changes.txt could be made more explicit?

Thanks for your advise...

In message
 <1388165759.72.0.941138301996.issue2550827@psf.upfronthosting.co.za>
 <1388165759.72.0.941138301996.issue2550827@psf.upfronthosting.co.za>,
 Matt writes:

>Matt added the comment:
>
>Thanks for that link, there is more info there than I appreciated from
>reading the Changes.txt. I see that it does state: "You can run Roundup
>as a Windows service if pywin32_ is installed." in the Optional
>Components Section...

Yes, in doc/installation.txt it does state the pywin32_ requirement.

>I am running python V2.6.6 from http://www.python.org/ and I could start
>the server from the command line...

Good, I don't think you would do that under windows without pywin32_
before the 1.4.21 release.

>Perhaps the changes.txt could be made more explicit?

Yes, I can see where the confusion is. Maybe we can change the two
lines in CHANGES.txt:

  - pywin32 is no longer required to run on Windows (anatoly techtonik)
  - Rewritten portalocker.py logic in ctypes for Windows (anatoly techtonik)

to:

  - Rewritten portalocker.py logic in ctypes for Windows to remove
    dependency on pywin32. Running roundup as a service still needs
    pywin32. (anatoly techtonik)

Anatoly is that acceptable? Do you have other thoughts on how to make
this requirement clearer?

(Adding Anatoly to the nosy list, as he got asked a question. ;)) 
To me it seems doc/installation.txt should also be improved to be more 
specific.

I see a reference to win32serviceutil in roundup\scripts\roundup_server.py
There can be a pure Python ctypes alternative, but I am not using Roundup
servers on Windows, so I am not the one to implement it, because I can't
test it properly.

see issue2550680

Anatoly you said:
> I am not the one to implement it, because I can't
> test it properly.

If this seems to be easy to code, I can try running it on windows.

I accidentally removed Anatoly's msg5026 from the thread. Hopefully
somebody on roundup-devel can put it back.

I have updated the section about running roundup as a windows service to
mention the requirement for pywin32. So it's mentioned in the
installation.txt guide plus the admin doc now.

I updated docs, no activity since. this I think addresses the original
confusion. Closing.