[Trac-dev] Trac 0.12 missing subversion dlls

Re: [Trac-dev] Trac 0.12 missing subversion dlls

Hi,

I have found it hard in the past to get all the DLL's lined up (and I
can't remember how i solved it in the past).

I think http://alagazam.net/ helped a lot (the binaries there have
everything you need I think).

Hope that helps,
  Mark

On Mon, Aug 1, 2011 at 10:00 PM, Paresh <paresh138 <at> gmail.com> wrote:
> Hi Guys
>
> I'm trying to set up a demo trac 0.12 om a 32bit windows 7 machine.
> I'm running python 2.7 and subversion 1.6.17 (SlikSvn for win32)
>
> Trac itself is running fine using tracd, but I need to get it linked up with
> svn.
>
> It's all going well, until I try to resync the repository, then I get this
> error
>
> TracError: Unsupported version control system "svn": DLL load failed: The
> specified module could not be found.
>
> In c:\python27\Lib\site-packages, I have unzipped
> svn-win32-1.6.15_py_2.7.zip (as per instructions here for python2.7) and
> checked my PYTHONPATH settings.
>
> Subversion works fine on the command line, so I think that is installed
> correctly.
>
> Using the dependancy walker, I profiled python.exe and typed in from 'svn
> import core' found the following dlls are reported missing:-
> IESHIMS.DLL
> LIBAPR-1.DLL
> LIBSVN_CLIENT-1.DLL
> LIBSVN_DELTA-1.DLL
> LIBSVN_RA-1.DLL
> LIBSVN_SUBR-1.DLL
> LIBSVN_WC-1.DLL
>
> The only LIBSVN dll I can see on my system is libsvn_swig_py-1.dll in
> c:\python27\Lib\site-packages\libsvn\.
> There is no libapr-1.dll either.
>
> I believe that IESHIMS.DLL is a red herring, but am willing to be corrected.
>
> Can anyone help?
>
> Paresh
>
> --
> You received this message because you are subscribed to the Google Groups
> "Trac Development" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/trac-dev/-/Ej4k_KobXJUJ.
> To post to this group, send email to trac-dev <at> googlegroups.com.
> To unsubscribe from this group, send email to
> trac-dev+unsubscribe <at> googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/trac-dev?hl=en.
>

--

-- 
You received this message because you are subscribed to the Google Groups "Trac Development" group.
To post to this group, send email to trac-dev <at> googlegroups.com.
To unsubscribe from this group, send email to trac-dev+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en.

Re: [Trac-dev] Trac 0.12 missing subversion dlls

On 8/1/2011 4:28 PM, Mark Mc Mahon wrote:
> Hi,
>
> I have found it hard in the past to get all the DLL's lined up (and I
> can't remember how i solved it in the past).
>
> I think http://alagazam.net/ helped a lot (the binaries there have
> everything you need I think).

... but Alagazam.net only has the bindings for Python 2.6, and Paresh
needs the bindings for Python 2.7.
What seems to be missing in his case is simply to have compatible
Subversion libraries in the PATH.

> On Mon, Aug 1, 2011 at 10:00 PM, Paresh <paresh138 <at> gmail.com> wrote:
>> ...
>> Subversion works fine on the command line, so I think that is installed
>> correctly.
>>
>> Using the dependancy walker, I profiled python.exe and typed in from 'svn
>> import core' found the following dlls are reported missing:-
>> IESHIMS.DLL
>> LIBAPR-1.DLL
>> LIBSVN_CLIENT-1.DLL
>> LIBSVN_DELTA-1.DLL
>> LIBSVN_RA-1.DLL
>> LIBSVN_SUBR-1.DLL
>> LIBSVN_WC-1.DLL

Those libraries are normally all located below the install path of
Subversion, but I don't know the "SlikSvn for win32" package, so maybe
the .dlls it comes with are simply not compatible with the bindings. I
use the CollabNet's 1.6.12 build of Subversion and it works fine. Maybe
the 1.6.15 build of Subversion from Alagazam also works (not tested).

>>
>> The only LIBSVN dll I can see on my system is libsvn_swig_py-1.dll in
>> c:\python27\Lib\site-packages\libsvn\.
>> There is no libapr-1.dll either.

Well, if that's really the case, then the Sliksvn "svn.exe" command line
was built statically. No .dll hell but no reuse either 

-- Christian

--

-- 
You received this message because you are subscribed to the Google Groups "Trac Development" group.
To post to this group, send email to trac-dev <at> googlegroups.com.
To unsubscribe from this group, send email to trac-dev+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en.

Re: [Trac-dev] Trac 0.12 missing subversion dlls

Re: [Trac-dev] Trac 0.12 missing subversion dlls

Re: [Trac-dev] Trac 0.12 missing subversion dlls

On 8/1/2011 5:08 PM, Paresh wrote:
> Christian
>
> I just read your reply.  Yes, I am using Python 2.7, but I can confirm
> that I ran the windows installer as specified above and after
> completing the install, 'from svn import core' worked in the python
> shell and also the trac-admin resync command worked - at least it
> didn't bomb out and it has scanned the correct number of commits for
> the repository and given the appearance of success :)

Yep, if you were talking about one of the Setup-Subversion-1.6.x.msi
package, that's consistent with what I said.
If you were talking about the Python 2.6 bindings
(svn-win32-1.6.x_py.zip) working in Python 2.7, that would be more
surprising 

-- Christian

--

-- 
You received this message because you are subscribed to the Google Groups "Trac Development" group.
To post to this group, send email to trac-dev <at> googlegroups.com.
To unsubscribe from this group, send email to trac-dev+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en.

Re: [Trac-dev] Trac 0.12 missing subversion dlls

[Trac-dev] Announcer replacing TracNotification

Hi
I wondered if the proposal [1] to replace the Trac notification system 
with the Announcer plugin was still on the table / in the works. What is 
the plan and how could one help?

The proposal page mentions API compatibility, i18n, subscription system 
improvements and a ticket review. Would simply leaving the current API 
in place as well (marked as deprecated) make sense? The plugin page [3] 
seems to suggest i18n support is working, and the subscription system 
seems to be quite advanced. I guess the started ticket review is 
probably out-of-date again by now?

I couldn't find any work in progress (unless the empty sandbox [2] 
really is the only WIP so far). Are there other preliminary tasks to be 
finished before an attempt to integrate the code makes sense? Or could 
one simply start with that to get things rolling again?

Peter

[1]: http://trac.edgewall.org/wiki/TracDev/Proposals/Announcer
[2]: http://trac.edgewall.org/wiki/TracDev/Branches/Announcer
[3]: http://trac-hacks.org/wiki/AnnouncerPlugin#Abouti18nl10nsupport

--

-- 
You received this message because you are subscribed to the Google Groups "Trac Development" group.
To post to this group, send email to trac-dev <at> googlegroups.com.
To unsubscribe from this group, send email to trac-dev+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en.

Re: [Trac-dev] Announcer replacing TracNotification

Hello Peter,

Am 03.08.2011 22:01, schrieb Peter Suter:
> Hi I wondered if the proposal [1] to replace the Trac notification
> system with the Announcer plugin was still on the table / in the
> works. What is the plan and how could one help?
Thanks for considering to contribute your time to this too. The original
plan discussed by Robert Corsaro (doki_pen) and me has been to bring
TracAnnouncer into better shape before moving a stabilized version over
to Trac core.

I've meant to go for it, when I did some documentation around the effort
started by Robert. It was a major internal rework coupled with a new
approach towards really flexible and still intuitive per-user configuration.

But then I became aware of sever lack of maintenance for AccountManager,
and work for it consumed too much of my spare time. Only recently Itamar
Ostricher (itamarost) came up with a bundle of fixes and improvements
for the TagsPlugin, so I'm still not quite there to dedicate all my time
to TracAnnouncer.

> The proposal page mentions API compatibility, i18n, subscription
> system improvements and a ticket review. Would simply leaving the
> current API in place as well (marked as deprecated) make sense?
Sure, leaving a wrapper preserving current TracNotification API was not
an option but more of a pre-requisite to make the migration acceptable
in the first place.

> The plugin page [3] seems to suggest i18n support is working, and the
> subscription system seems to be quite advanced. I guess the started
> ticket review is probably out-of-date again by now?
Well, i18n is working, but not yet for the message templates. Sure the
ticket review is bound to be outdated by now. Message encryption support
is still very unfinished and lacking much of the configuration support
I'd like to provide for it, to make it's application doable even without
much cryptography expertise.

> I couldn't find any work in progress (unless the empty sandbox [2] 
> really is the only WIP so far). Are there other preliminary tasks to
> be finished before an attempt to integrate the code makes sense? Or
> could one simply start with that to get things rolling again?
Only recently Ryan Ollos (rjollos) nudged me about TagsPlugin and
TracAnnouncer, and promised to donate some development time within the
next few months for pushing issues for both of them. Robert, as the
current maintainer, Ryan, you and me, this looks like it's going to happen.

Fixing and improving TracAnnouncer `trunk` branch, including the
additional TracNotification compatibility layer still seem like a good
approach.

You should get at least SVN commit for the start. I could request this
for you. Should I do so? We could arrange an experimental migration
branch or the like.

Another option, that I could support actively, would involve working on
a copy of the plugin code at Bitbucket with the added bonus of more
visible forks, pull requests and Mercurial Queues, if you'd favor that
kind of collaboration. I work with MQ a lot here locally before pushing
back to the t-h.o SVN repo.

As far as I know, finally pushing to the sandbox at t.e.o is reserved to
Robert and you, since Ryan and me lack access to it.

Yours,

Steffen Hoffmann
(hasienda)

Re: [Trac-dev] Announcer replacing TracNotification

My $0.02  I've been using TracAnnouncer for over a year and helped identify and fix a bug or two with Steffen.  I
support it as the way forward with Trac notifications - it's quite a bit more flexible than what's
currently in core (although I can see it benefit from some simplification improvements).  I also used it
with gpg encryption that required a few tweaks but otherwise good stuff.

Cheers.
- Rob

On Aug 4, 2011, at 10:14 AM, Steffen Hoffmann wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Hello Peter,
> 
> Am 03.08.2011 22:01, schrieb Peter Suter:
>> Hi I wondered if the proposal [1] to replace the Trac notification
>> system with the Announcer plugin was still on the table / in the
>> works. What is the plan and how could one help?
> Thanks for considering to contribute your time to this too. The original
> plan discussed by Robert Corsaro (doki_pen) and me has been to bring
> TracAnnouncer into better shape before moving a stabilized version over
> to Trac core.
> 
> I've meant to go for it, when I did some documentation around the effort
> started by Robert. It was a major internal rework coupled with a new
> approach towards really flexible and still intuitive per-user configuration.
> 
> But then I became aware of sever lack of maintenance for AccountManager,
> and work for it consumed too much of my spare time. Only recently Itamar
> Ostricher (itamarost) came up with a bundle of fixes and improvements
> for the TagsPlugin, so I'm still not quite there to dedicate all my time
> to TracAnnouncer.
> 
>> The proposal page mentions API compatibility, i18n, subscription
>> system improvements and a ticket review. Would simply leaving the
>> current API in place as well (marked as deprecated) make sense?
> Sure, leaving a wrapper preserving current TracNotification API was not
> an option but more of a pre-requisite to make the migration acceptable
> in the first place.
> 
>> The plugin page [3] seems to suggest i18n support is working, and the
>> subscription system seems to be quite advanced. I guess the started
>> ticket review is probably out-of-date again by now?
> Well, i18n is working, but not yet for the message templates. Sure the
> ticket review is bound to be outdated by now. Message encryption support
> is still very unfinished and lacking much of the configuration support
> I'd like to provide for it, to make it's application doable even without
> much cryptography expertise.
> 
>> I couldn't find any work in progress (unless the empty sandbox [2] 
>> really is the only WIP so far). Are there other preliminary tasks to
>> be finished before an attempt to integrate the code makes sense? Or
>> could one simply start with that to get things rolling again?
> Only recently Ryan Ollos (rjollos) nudged me about TagsPlugin and
> TracAnnouncer, and promised to donate some development time within the
> next few months for pushing issues for both of them. Robert, as the
> current maintainer, Ryan, you and me, this looks like it's going to happen.
> 
> Fixing and improving TracAnnouncer `trunk` branch, including the
> additional TracNotification compatibility layer still seem like a good
> approach.
> 
> You should get at least SVN commit for the start. I could request this
> for you. Should I do so? We could arrange an experimental migration
> branch or the like.
> 
> Another option, that I could support actively, would involve working on
> a copy of the plugin code at Bitbucket with the added bonus of more
> visible forks, pull requests and Mercurial Queues, if you'd favor that
> kind of collaboration. I work with MQ a lot here locally before pushing
> back to the t-h.o SVN repo.
> 
> As far as I know, finally pushing to the sandbox at t.e.o is reserved to
> Robert and you, since Ryan and me lack access to it.
> 
> Yours,
> 
> Steffen Hoffmann
> (hasienda)
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
> 
> iEYEARECAAYFAk46qV4ACgkQ31DJeiZFuHdfBQCeLI4nRxfM6d1FrmcvrmXJPqP+
> lIcAn37r/WFMFrQBd3W6woZ5hv5AvkQm
> =9RPN
> -----END PGP SIGNATURE-----
> 
> -- 
> You received this message because you are subscribed to the Google Groups "Trac Development" group.
> To post to this group, send email to trac-dev <at> googlegroups.com.
> To unsubscribe from this group, send email to trac-dev+unsubscribe <at> googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en.
> 

--

-- 
You received this message because you are subscribed to the Google Groups "Trac Development" group.
To post to this group, send email to trac-dev <at> googlegroups.com.
To unsubscribe from this group, send email to trac-dev+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en.