Reini Urban wrote:
Linda, You really need to ask on modu...@perl.org
---- I asked here first for a reality check. I got it and found it had to do with the certs being relocated to some "new and improved" standard location and not all the http utils know what is going on...
I noted that it didn't, for example, work through squid (it used to), but it does work directly. Having other things on my table, I haven't chased that one down.
I guess your P namespace was blocked, as you consistently acted foolish and violated https://pause.perl.org/pause/authenquery?ACTION=pause_namingmodule
==== Right....sorry to disillusion you, but it wasn't and I didn't.
But I see no problems with your perms for P and found nothing via http://grokbase.com/search?q=LAWALSH&f=gt%2Fperl%2Fmodules You can also check the 503 with https://pause.perl.org/pause/authenquery?ACTION=tail_logfile
---- That's useful thanks... My distro tends to do strange things with perl -- like embedding the versioned-library path in modules so they can't be used with any other perl version (the versioned library path being redundant when running most versions of perl) and putting version specific checks in all the "no-arch" (meaning pure perl) modules. Keeping that sorted while they also create symlinks from root to 'yet-to-be-mounted' mounted file systems for utils like 'mount' and moving system libs to yet-to-be-mounted file systems keeps one busy. Add moving of certs around w/o updating all the utils that use them to that list... ;-)
