Skip Menu |

This queue is for tickets about the AnyEvent-DBI CPAN distribution.

Report information
The Basics
Id: 122863
Status: open
Priority: 0/
Queue: AnyEvent-DBI

Owner: Nobody in particular
Requestors: SREZIC [...]
Cc: schmorp [...]

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

CC: schmorp [...]
Subject: Undeclared dependency AnyEvent::Fork
Download (untitled) / with headers
text/plain 882b
t/00_load.t fails if AnyEvent::Fork is not installed: ... Can't locate AnyEvent/ in @INC (you may need to install the AnyEvent::Fork module) (@INC contains: /home/cpansand/.cpan/build/2017082200/AnyEvent-DBI-3.0-0/blib/lib /home/cpansand/.cpan/build/2017082200/AnyEvent-DBI-3.0-0/blib/arch /opt/perl-5.27.3/lib/site_perl/5.27.3/x86_64-linux /opt/perl-5.27.3/lib/site_perl/5.27.3 /opt/perl-5.27.3/lib/5.27.3/x86_64-linux /opt/perl-5.27.3/lib/5.27.3 .) at /home/cpansand/.cpan/build/2017082200/AnyEvent-DBI-3.0-0/blib/lib/AnyEvent/ line 65. BEGIN failed--compilation aborted at /home/cpansand/.cpan/build/2017082200/AnyEvent-DBI-3.0-0/blib/lib/AnyEvent/ line 65. Compilation failed in require at t/00_load.t line 3. BEGIN failed--compilation aborted at t/00_load.t line 3. t/00_load.t ........ Dubious, test returned 2 (wstat 512, 0x200) Failed 1/1 subtests ...
Subject: Re: [ #122863] Undeclared dependency AnyEvent::Fork
Date: Tue, 22 Aug 2017 17:32:50 +0200
To: Slaven_Rezic via RT <bug-AnyEvent-DBI [...]>
From: Marc Lehmann <schmorp [...]>
Hi! Please send your bug report to the official contact/author address for the module in question (or send it to, that's fine as well). What follows is the rationale for this request, you don't have to read it if you don't care. Why is this necessary? has many deficiencies which makes it tedious and hard to use, increasing the workload on the people who provide all the perl modules you probably appreciate (and that is really to be avoided - module authors should be able to invest all their time into improving their modules and not fighting with's bugs). Still, for some people, is useful to have, and some people even like it and really want to use it. That is fine, too. Unfortunately, the designers of didn't make their "service" optional - you can neither opt-in nor opt-out of as a module author. Just like a spammer, forces its "service" (whether wanted or unwanted) on everybody. Just like a spammer, they don't care for the people they actively hurt. Just like a spammer, they don't don't care to fix these issues and make their "service" ethically acceptable. You cannot even configure it to redirect tickets to somewhere else. Unfortunately, ignoring is not an option either: for people reporting possible bugs there is no indication that their report will be ignored, and for module authors it means they miss potentially vital bug reports such as yours (and of course it's a great impression if has lots of bug reports that are unanswered, making a module look unmaintained when in fact the opposite might be true). I am sorry that this wasted a bit of your time, but please understand that I am just as much a victim as you are - the problem is the unethical stance of the providers who force their "service" on everybody. Please redirect your bug report as stated in the beginning of this mail, and please consider petitioning the providers to stop their unethical behaviour and allow opt-in, opt-out, or some redirect option. One last issue: many people mail me that this can be "fixed" by including the bugtracker element in my module meta file. This is not true: 1. This field only affects and maybe similar services. (Many people confuse with for some reason). 2. It doesn't even work (there are still links to displayed). 3. Even if does no longer display the link, it doesn't actually affect (and tests have shown that people go to regardless) Even *iff* would start listening on the bugtracker field, however, it's still wrong. I have a lot of modules, and each time a service like comes out, I would have to make dummy releases for all my modules. This not only creates a lot of extra work for me (I take releases very seriously) but also users, who would wonder why there is a new release. Thanks a lot, Marc Lehmann <> Last updated: 2012-04-22

This service is sponsored and maintained by Best Practical Solutions and runs on infrastructure.

Please report any issues with to