Re: Stuck module upload for Date::Parse::Modern

On Sat, Jan 14, 2023, at 20:08, Ask Bjørn Hansen wrote: > `curl` on the box can validate the certificate okay (right now), for what > it’s worth. Sounds like it was related to SSL version. I filed https://github.com/andk/pause/pull/386 which may or may not be right. -- rjbs

Re: Stuck module upload for Date::Parse::Modern

I looked at the PAUSE logs: 2023-01-13 22:50:39 $$3234 v1049: Alert: nosuccesscount[0] error[Can't connect to www.perturb.org:443 (certificate verify failed)] (paused:701) My guess is that PAUSE's CAs are too old "or something". On Fri, Jan 13, 2023, at 19:25, Scott Baker wrote: > To whom it

Re: Move dev release tarballs to GitHub?

On Sun, Apr 3, 2022, at 13:52, Ricardo Signes wrote: > To test how well the tools will work when the release is only on backpan, I > have boldly deleted 5.11.4 via PAUSE. I'll check back on this in a week. Looking good. "plenv install" finds the file at metacpan, w

Re: Move dev release tarballs to GitHub?

On Tue, Apr 5, 2022, at 09:52, Todd Rinaldo wrote: > I’m unclear who decides if it’s OK for me to delete the dev versions of Perl > I’ve done. I’m happy to do it. Maybe we should put a policy or suggestion > into the release manager’s guide as a first step? I'm doing a quick bit of testing to

Re: Move dev release tarballs to GitHub?

On Fri, Mar 25, 2022, at 19:30, Robert Spier wrote: > Would you consider, instead of pushing them to CPAN, posting them to GitHub > using the releases functionality? Robert, I have considered it, and I think the short answer is, "It's worth considering." It will break some amount of

Re: Should URL in 02packages.details.txt be updated?

On Sat, Jan 15, 2022, at 7:11 PM, James E Keenan wrote: > Should the URL entry in '02packages.details.txt' be changed to that of > the redirect? Yes, and I have filed https://github.com/andk/pause/pull/378 -- rjbs

Re: Response to Rik's "Credit the first uploader" post

* David Golden [2016-02-16T00:04:05] > I'll try to restate the problems in my own words: > > (1) Last uploader as "point of contact" > > How often is this really a problem? For me, I'd say it averages a few times a month. I'm slowly getting this down by slogging at the problem,

Re: Should Test2 maintain $! and $@?

* Chad Granum [2016-01-11T19:53:15] > However. It is easy enough to have Test::Builder/More protect $! and $@ > without requiring Test2 to do so. I don't have really strong feelings here, but the general reaction on p5p over the years to "some core library changes $!

Software-License next steps

As I hope that my little experiment can end up being useful for other shared code, I'm posting this on cpan-workers. I can take it elsewhere, if it's more distracting than useful. ;) Karen Etheridge, Neil Bowers, and Leon Timmermans will be governing Software-License with me. You three: please

Re: democratizing some of my dists

* Alberto Simoes [2015-11-13T11:19:13] > Where is the list? :) https://github.com/Perl-Toolchain-Gang/Software-License -- rjbs signature.asc Description: PGP signature

Re: democratizing some of my dists

* Ricardo Signes <perl.cpanw...@rjbs.manxome.org> [2015-11-13T11:16:14] > I would like to run the distribution a bit more democratically. I'm not > sure how I want to do this in general, so I am going to screw around with how > things work, but will do so as little as I f

Re: democratizing some of my dists

* "David E. Wheeler" [2015-11-13T14:41:55] > Can you do that for some of my modules, too? :-) When I end up with something that I think works, you can have a copy of the charter. ;) -- rjbs signature.asc Description: PGP signature

Re: democratizing some of my dists

* Kent Fredric [2015-11-13T19:00:36] > On 14 November 2015 at 12:50, James E Keenan wrote: > > doesn't that mean that its ownership is already democratized? > > Not fully until he gives somebody else publish bits. In democracies, not every citizen can

Re: democratizing some of my dists

* James E Keenan <jk...@verizon.net> [2015-11-13T18:50:37] > On 11/13/2015 12:38 PM, Ricardo Signes wrote: > >* Alberto Simoes <a...@perl-hackers.net> [2015-11-13T11:19:13] > >>Where is the list? :) > > > >https://github.com/Perl-Toolchain-Gang/Softwa

Re: Need dependency-free way of capturing verbose function output in a variable

The core SelectSaver module is useful for this problem. use SelectSaver; { my $guard = SelectSaver-new($local_test_output_collecting_fh); run_test_code; } # the local fh got the test prints, but prints out here go to the previous # target -- rjbs signature.asc

Software::License - toolchain gang

I propose to hand Software::License over to the Perl-Toolchain-Gang org. Objections should be stated now. -- rjbs signature.asc Description: Digital signature

Module::Build leaving core?

There is a decent chance that Module::Build will be removed from the core perl distribution in v5.22.0. That decision is being made now on perl5-porters. http://www.nntp.perl.org/group/perl.perl5.porters/2013/05/msg202041.html We know that distributions built with Module::Build can be installed

Re: namespaces that differ only in case

* Alexandr Ciornii alexcho...@gmail.com [2012-03-31T16:49:34] CORBA-IDL on CPAN has package Attributes in one of modules, name similar to core module attributes. Class-PObject has INTEGER, similar to integer. They are included into CPAN index and CPAN shell finds them as upgrades to

Re: How to have Perl 5 and Perl 6 cohabitate nicely on CPAN

* Adam Kennedy a...@ali.as [2010-04-14T20:53:15] Alternative option, when we switch to Perl 6 also take the opportunity to switch to a specific named extension. D/DA/DAGOLDEN/Foo-Bar-1.23.c6z I haven't wanted to get into this thread, but I will say that I had the same idea as Adam, and

Re: CPAN Meta Spec Proposal discussion period has ended -- summary of results

* Adam Kennedy a...@ali.as [2009-11-02T18:24:26] I'd like to propose that all changes to the META.yml be fully and completely defined, without resort to the behaviour of external code. That is to say, all cases where a value must be in some enum should describe the full list, instead of

Re: CMSP 17. Better formalization of license field

* David Golden xda...@gmail.com [2009-10-11T21:49:28] On Sun, Oct 11, 2009 at 8:59 PM, Ricardo Signes perl.cpanw...@rjbs.manxome.org wrote: I am also happy to add a meta2_name method to all the Software::License classes to avoid a direct connection between SL and META, but I don't want

Re: CMSP 30. Trove-Like Categories

* Shlomi Fish shlo...@iglu.org.il [2009-10-10T06:57:11] With all due respect to tags, categories still have their advantage, and should be considered despite their lack of popularity among the latest fads on the web. One of the reason tags are popular may be due to an easier They've been

Re: CMSP 05. Schema

* David Golden xda...@gmail.com [2009-10-09T07:43:56] 05. Schema Proposal: The META spec should come along with a formal schema definition. (SlavenRezic) No strong feelings. Not a bad idea. I believe an Rx schema for 1.4 exists. -- rjbs

Re: CMSP 07. Enhance granularity of prerequisites

* David Golden xda...@gmail.com [2009-10-09T07:45:22] 07. Enhance granularity of prerequisites Agreed. Also suggest (08. Extensibly Group Prereqs) as related and useful. -- rjbs

Re: CMSP 10. Add a free-text prerequisite field

* David Golden xda...@gmail.com [2009-10-09T07:47:00] 10. Add a free-text prerequisite field Strongly oppose. The META file is meant to tell machines about dists. This will not be useful. -- rjbs

Re: CMSP 12. Allow Sequences (Arrays) for Prereqs

* David Golden xda...@gmail.com [2009-10-09T07:47:57] 12. Allow Sequences (Arrays) for Prereqs Strongly agreed. (I believe I proposed this.) -- rjbs

Re: CMSP 13. Add a post_depends set

* David Golden xda...@gmail.com [2009-10-09T07:48:25] 13. Add a post_depends set Proposal: Permit specifying of packages that should be installed to provide part of a packages functionality, but should be installed/built *after* the package is installed. (kentnl) No vote. I'm

Re: CMSP 14. Prerequisites should be mutually exclusive

* David Golden xda...@gmail.com [2009-10-09T07:48:50] 14. Prerequisites should be mutually exclusive No vote, no strong opinion. -- rjbs

Re: CMSP 15. Add development_requires

* David Golden xda...@gmail.com [2009-10-09T07:49:15] 15. Add development_requires Proposal: The development_requires field should specify all prerequisites only needed during development. For example this could include templating or other preprocessing modules needed to generate the

Re: CMSP 19. Make repository resource a hash

* David Golden xda...@gmail.com [2009-10-09T07:51:06] 19. Make repository resource a hash [Note, a separate Make repository more machine readable proposal has been merged into this one.] Agreed. -- rjbs

Re: CMSP 22. Clarify author field

* David Golden xda...@gmail.com [2009-10-09T07:52:22] 22. Clarify author field Proposal: I would like to see some clarification of what an author is, especially since the numbers of distros Agreed. * I think there are two things you want to know about the distribution: who to

Re: CMSP 23. Have a development version flag

* David Golden xda...@gmail.com [2009-10-09T07:52:45] 23. Have a development version flag Agreed. * Con: Development version'ness would not be determinable post-installation AdamKennedy Packlist 2.0? -- rjbs

Re: CMSP 29. Language

* David Golden xda...@gmail.com [2009-10-09T07:54:51] 29. Language Proposal: Perl 6 is coming. Some code in Perl 6 is already being uploaded to the CPAN. A new language field is an important part of the structure we need to allow Perl 6 to reuse the existing CPAN rather than to try to

Re: CMSP 33. Install Meta files and make them queryable

* David Golden xda...@gmail.com [2009-10-09T07:56:24] 33. Install Meta files and make them queryable Proposal: Using something like .packlist or File::ShareDir, the Meta file should be installed along with the distribution and Meta tools should allow easy querying of meta information for

Re: CMSP 02. Formally switch to YAML Tiny

* Steffen Mueller nj88ud...@sneakemail.com [2009-10-09T10:04:44] As for adopting JSON as the default format: What's the chances of including a full JSON parser in core? I believe they are good. JSON.pm has no weird prereqs, works admirably, and the author has no objections. -- rjbs

Re: CMSP 06. Data structures, not YAML

* Jarkko Hietaniemi j...@iki.fi [2009-10-09T10:11:35] I really don't think we should have Perl data structures in files (that means Perl code, right?), because that indicates doing an eval, and I don't want to eval any more random code off the 'net than necessary. Right. We definitely want a

Re: CMSP 20. Make bugtracker resource a hash

* Hans Dieter Pearcey h...@pobox.com [2009-10-09T08:34:14] Excerpts from David Golden's message of Fri Oct 09 07:51:29 -0400 2009: 20. Make bugtracker resource a hash Agree, given a fixed set of keys. Agreed, exactly so. -- rjbs

Re: CMSP 30. Trove-Like Categories

* David Golden xda...@gmail.com [2009-10-09T07:55:12] 30. Trove-Like Categories Seems like a organizational step backwards. Opposed. -- rjbs

Re: CMSP 31. Version changes

* Dieter This seems like getting people to agree on a machine-readable changelog format, which appears only slightly more likely than world peace. Am I misreading it? * Graham Barr gb...@pobox.com [2009-10-09T10:36:48] yeah. I can see the benefit of machine readable changelogs. I am

Re: CMSP 26. Specify a DLSIP resource

* David Golden xda...@gmail.com [2009-10-09T07:53:50] 26. Specify a DLSIP resource Proposal: DLSIP codes should be specified in META.* as a resource. Alternte proposal: DLSIP codes should be deleted from the internet and never discussed again in polite company. Opposed. -- rjbs

Re: CMSP 28. Short description

* Steffen Mueller nj88ud...@sneakemail.com [2009-10-09T10:49:40] We should always keep in mind how information ends up in META.XXX. Humans should not have to write META stuff. Therefore, the only moderately sane and established free-form source of information is module POD. Since that's

Re: CMSP 27. Long description

* Steffen Mueller nj88ud...@sneakemail.com [2009-10-09T10:54:31] Ricardo Signes wrote: Sure, why not? Because META should be *generated* from other sources. Where should free-form data come from? From the same thing that generates the META.yml file. Each dist tool will presumably have

Re: CMSP 18. Make dynamic_config mandatory

* David E. Wheeler da...@kineticode.com [2009-10-09T14:18:42] WTF is dynamic_config? If dynamic_config is set in your META.yml: true means you must run Makefile.PL or Build.PL and rely only on its output false means the META.yml is entirely authoritative If not given, the default value is

Re: CMSP 12. Allow Sequences (Arrays) for Prereqs

* Ruslan Zakirov ruslan.zaki...@gmail.com [2009-10-09T15:28:29] On Fri, Oct 9, 2009 at 3:47 PM, David Golden xda...@gmail.com wrote: 12. Allow Sequences (Arrays) for Prereqs [snip] order by using a sequence of pairs, Bundle's magic could probably be made obsolete, simplifying the

Re: CMSP 22. Clarify author field

* David Golden xda...@gmail.com [2009-10-09T16:41:45] Simplest: author is a list of contact points, which includes authors, maintainers, mailing lists, etc. I'd like to avoid a complex data structure. If we deprecate author, I'd rather see contacts merged into resources since we have

Re: CMSP 29. Language

* David Golden xda...@gmail.com [2009-10-09T07:54:51] 29. Language Branch available: http://github.com/rjbs/cpan-meta-spec/commits/29-language -- rjbs

Re: CMSP 19. Make repository resource a hash

* David Golden xda...@gmail.com [2009-10-09T07:51:06] 19. Make repository resource a hash Branch available: http://github.com/rjbs/cpan-meta-spec/commits/19-repository-hash -- rjbs

Re: CMSP 20. Make bugtracker resource a hash

* David Golden xda...@gmail.com [2009-10-09T07:51:29] 20. Make bugtracker resource a hash Branch available: http://github.com/rjbs/cpan-meta-spec/commits/20-bugtracker-hash -- rjbs

Re: CMSP 02. Formally switch to YAML Tiny

* David Golden xda...@gmail.com [2009-10-09T07:42:06] 02. Formally switch to YAML Tiny Branch available: http://github.com/rjbs/cpan-meta-spec/commits/02-yamltiny -- rjbs

cpan-distnameinfo for all

As threatened at QA09, I am going to fix a bug or two in CPAN::DistnameInfo. Then I am going to see if I can replace the similar code in CPANPLUS with it. Then I will probably look at PAUSE and CPAN to see if I can do the same. Any input or objections would be welcome at this time. -- rjbs