Bug #112601 for common-sense: Non-reproducible build due to hash randomization

Hi! Please send your bug report to the official contact/author address for the module in question (or send it to rt.cpan.org@schmorp.de, 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? rt.cpan.org 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 rt.cpan.org's bugs). Still, for some people, rt.cpan.org is useful to have, and some people even like it and really want to use it. That is fine, too. Unfortunately, the designers of rt.cpan.org didn't make their "service" optional - you can neither opt-in nor opt-out of rt.cpan.org as a module author. Just like a spammer, rt.cpan.org 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 rt.cpan.org 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 rt.cpan.org 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 rt.cpan.org 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 rt.cpan.org 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 search.cpan.org and maybe similar services. (Many people confuse rt.cpan.org with search.cpan.org for some reason). 2. It doesn't even work (there are still links to rt.cpan.org displayed). 3. Even if search.cpan.org does no longer display the link, it doesn't actually affect rt.cpan.org (and tests have shown that people go to rt.cpan.org regardless) Even *iff* rt.cpan.org would start listening on the bugtracker field, however, it's still wrong. I have a lot of modules, and each time a service like rt.cpan.org 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 <rt.cpan.org@schmorp.de> Last updated: 2012-04-22

On Tue, Mar 01, 2016 at 04:15:07AM -0500, Peter Rabbitson via RT <bug-common-sense@rt.cpan.org> wrote: Show quoted text
Hi! Isn't this already a solved problem (PERL_HASH_SEED and friends)? If you want reproducible buildsa, that seems to be the way to go. -- The choice of a Deliantra, the free code+content MORPG -----==- _GNU_ http://www.deliantra.net ----==-- _ generation ---==---(_)__ __ ____ __ Marc Lehmann --==---/ / _ \/ // /\ \/ / schmorp@schmorp.de -=====/_/_//_/\_,_/ /_/\_\

On 03/06/2016 04:03 AM, Marc Lehmann via RT wrote: Show quoted text
I do not disagree with this. If reproducible builds were the endgoal - then yes, it makes sense to freeze the seed in order to help things get into a stable order. In my case however the build is a means-to-an-end: the target is a verbose CI environment which tests a project on a wide array of perl configurations (some of which 5.18+). As it is extremely unlikely an end user will peg their PERL_HASH_SEED, doing so in my test environment would compromise the results. The non-reproducibility of common/sense.pm is not critical, it was simply one of the very few things to jump out when doing environment comparison as shown in the (runnable) "oneliner" in this commit message: https://github.com/dbsrgits/dbix-class/commit/e48635f717. Given the overhead of calling sort once per build is beyond negligible, this ticket was filed. Thanks in advance!

On 03/07/2016 04:54 AM, Marc Lehmann wrote: Show quoted text
Can you elaborate on this? There may be some sort of env-dependent failing in sort that I am not aware of, and I'd like to know. Show quoted text
All I wanted to do is reduce the amount of "special casing" I have to do when analyzing the fingerprints of a typical[1] perllib. Thank you for considering the problem. Cheers [1] A typical perl install can not be expected to have any non-stock env settings present.