Skip Menu |

Preferred bug tracker

Please visit the preferred bug tracker to report your issue.

This queue is for tickets about the Alien-SVN CPAN distribution.

Report information
The Basics
Id: 76867
Status: rejected
Priority: 0/
Queue: Alien-SVN

People
Owner: Nobody in particular
Requestors: ribasushi [...] leporine.io
Cc:
AdminCc:

Bug Information
Severity: Important
Broken in: (no value)
Fixed in: (no value)



Subject: Global destruction detection is not thread-safe
Your distribution is using the construct END { $global_destroy = 1 } in [1], which is not thread safe as described here [2]. Please consider switching to https://metacpan.org/release/Devel-GlobalDestruction, which has both an XS and a PurePerl variant, both of which are tested to behave correctly under ithreads. Cheers [1] http://cpansearch.perl.org/src/MSCHWERN/Alien-SVN-v1.7.3.1/src/subversion/subversion/bindings/swig/perl/native/Core.pm [2] https://metacpan.org/source/DOY/Devel-GlobalDestruction-0.05/lib/Devel/GlobalDestruction.pm#L36
Thank you for your report, but this is just a redistribution of the SVN Perl bindings. No work is done here. Issues should be reported to the Subversion project. http://subversion.apache.org/reporting-issues.html Because bugs reported to Subversion must be reported in person and shepherded through their process, we cannot just forward the report upstream. Sorry for the inconvenience.
re-opening to track the ongoing issue; please close when SVN is fixed upstream.
Was this ever reported upstream?  It is very important that you do so else it will not get fixed.  Due to SVN's bug reporting policies, we cannot report and shepherd SVN bugs for you.
https://subversion.apache.org/reporting-issues.html

As for holding this open, the proper place to track bugs in Subversion's Perl bindings is in the Subversion bug tracker.  The proper place to add tests is also in the Subversion project.  It doesn't make sense to hold open SVN bugs in Alien::SVN's tracker just because it was reported to us, we'd wind up duplicating everything.

While I understand this issue is not resolved, reporting and tracking it here isn't going to get it resolved.  I'm again rejecting this ticket.


On Fri Jul 05 13:49:26 2013, ETHER wrote:
Show quoted text
> re-opening to track the ongoing issue; please close when SVN is fixed
> upstream.