tag:blogger.com,1999:blog-32839543564377946172024-02-17T13:30:02.782-08:00The Perl NOCthe perl.org infrastructure weblog!Unknownnoreply@blogger.comBlogger224125tag:blogger.com,1999:blog-3283954356437794617.post-90522774061832855552024-02-17T13:29:00.000-08:002024-02-17T13:29:04.744-08:00@cpan.org email deliverability issues<p>We've come across some snags with emails sent to <span style="font-family: courier;">@cpan.org</span> addresses since switching our forwarding system. Delays and bounces are happening more often than usual.</p><p>While we understand this is inconvenient, addressing this issue will require significant technical adjustments. As a result, we are unable to offer a specific timeframe for a resolution at this time.</p><p>Bottom line: if an receiving an email is urgent or crucial, don't use <span style="font-family: courier;">@cpan.org</span>. For important emails, opt for using another address with better deliverability.</p>Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-3283954356437794617.post-61647983905313572352022-06-11T14:25:00.001-07:002022-06-11T14:25:42.781-07:00CPAN: ftp.cpan.org depreciation<p>As a followup to the <a href="https://log.perl.org/2021/02/cpan-mirror-list-changes.html">CPAN Mirror List changes from last year</a>, we're announcing that FTP service on <span style="font-family: courier;">ftp.cpan.org</span> and <span style="font-family: courier;">ftp.perl.org </span>is being deprecated. This means that any CPAN clients configured to use them will fail to fetch modules.</p><p>For the past several years, CPAN clients have defaulted to <span style="font-family: courier;">www.cpan.org </span>to fetch modules, so this should only affect users using very old CPAN clients (usually associated with old versions of Perl) who did not explicitly set a mirror.</p><p>We're not setting a firm timeline on this depreciation, but there are only a small number of compatible FTP mirrors remaining, and the number is shrinking over time. At some point, there will no longer be any remaining FTP mirrors, and the service will be terminated. Because these mirrors are run by independent volunteers, we don't have a good way of measuring actual traffic.</p><p>If you think you might be using a CPAN client configured to use <span style="font-family: courier;">ftp.cpan.org</span> or <span style="font-family: courier;">ftp.perl.org</span>, please check, and reconfigure to use the globally available <span style="font-family: courier;">www.cpan.org</span> instead.</p><p>If you're using CPAN.pm, you can configure <span style="font-family: courier;">www.cpan.org</span> as the mirror with these commands:</p><blockquote style="border: none; margin: 0px 0px 0px 40px; padding: 0px; text-align: left;"><p><span style="font-family: courier;">o conf urllist https://www.cpan.org/</span> </p></blockquote><blockquote style="border: none; margin: 0px 0px 0px 40px; padding: 0px; text-align: left;"><p><span style="font-family: courier;">o conf commit</span></p></blockquote><p>(If your perl doesn't have <span style="font-family: courier;">Net::SSLEay</span> installed to support TLS, you can just use <span style="font-family: courier;">http://www.cpan.org/)</span> </p>Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-3283954356437794617.post-9412702587836308182021-05-09T21:29:00.006-07:002021-05-09T21:29:59.578-07:00Weekend Outage<p>You may have noticed that some perl.org services were unavailable this weekend. Email continued to flow, and no data was lost.</p><p>The short version of the story is that we were bitten by <a href="https://github.com/containerd/containerd/issues/5280#issuecomment-813707613" target="_blank">this bug.</a> and learned a <b>lot</b> about how Kubernetes works while we figured out what the issue was.</p><p>Sorry for any inconvenience!</p>Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-3283954356437794617.post-25840632069885597412021-02-22T09:39:00.002-08:002021-02-22T09:39:49.187-08:00CPAN Mirror List Changes<p>We sent the below email to all the CPAN Mirror contacts yesterday:</p><blockquote style="border: none; margin: 0px 0px 0px 40px; padding: 0px; text-align: left;"><h1 style="text-align: justify;">An Important Update about the CPAN Mirror List</h1><p style="text-align: justify;">You're receiving this email because you're listed as a contact point for a CPAN mirror. Thank you! The mirror network has been a huge part of CPAN’s success. Soon, the way clients use CPAN mirrors is changing. You don't need to do anything, but after reading this email, you might want to.</p><p style="text-align: justify;">Some background: For a long time, when the CPAN client (aka CPAN.pm) started up for the first time, it prompted users to configure it by picking a nearby mirror. The assumption was that it would be best to find a geographically nearby mirror. This necessitated the keeping of a central list of mirrors which the client could retrieve and offer as a menu. That's the CPAN Mirror List, maintained by the Perl NOC.</p><p style="text-align: justify;">In 2011, the client changed behavior to configure itself automatically, meaning that most new users never saw this list. Furthermore, www.cpan.org was pointed at a global CDN, meaning that traffic could be routed efficiently without client configuration. The CDN also meant that users wouldn’t need to worry about out of date or down mirrors..</p><p style="text-align: justify;">After ten years of CPAN defaulting to the CDN, we are going to stop maintaining the mirror list. It will still be present, but have only one entry: www.cpan.org. This means that anyone attempting to pick a mirror from the list will only find this one option. The mirror status site will be replaced with a static page. As has always been the case, the CPAN client can be configured manually to use any mirror, whether or not it's on the mirror list.</p><p style="text-align: justify;">Users who have configured their CPAN clients to point at your mirror will continue to hit it. No new users are likely to find it -- but after all, they were already very unlikely to do so! That said, you do not need to shut down your mirror. If you use your mirror, you can keep mirroring. We’re not removing or changing the ability to mirror. If you know you have users of your mirror who would like to keep using it, please feel free to keep mirroring it.</p><p style="text-align: justify;">On the other hand, if you would like to stop mirroring CPAN, feel free to do that, too. Clients have always had to deal with their mirror going away, and they will be fine if you choose to shut down your mirror.</p><p style="text-align: justify;">We have not set a firm date for the emptying of the mirror list, but we expect it to happen no earlier than mid-February and no later than June 2021.</p><p style="text-align: justify;">If you have any questions, please email us at <cpan at perl.org>.</p><p style="text-align: justify;">Concerned this is fake? A copy of this email can be found at https://log.perl.org/2021/02/cpan-mirror-list-changes.html.</p><p style="text-align: justify;">Finally: Thanks! The mirror network helped make CPAN practical for many years, and CPAN helped make Perl a success. You were part of this endeavor, and we appreciate it!<span style="text-align: left;"> </span></p></blockquote><blockquote style="border: none; margin: 0px 0px 0px 40px; padding: 0px; text-align: left;"><p style="text-align: justify;"><span face="Arial, Helvetica, sans-serif" style="background-color: white; color: #222222; font-size: small;">-- The </span><span class="il" face="Arial, Helvetica, sans-serif" style="background-color: white; color: #222222; font-size: small;">CPAN</span><span face="Arial, Helvetica, sans-serif" style="background-color: white; color: #222222; font-size: small;"> </span><span class="il" face="Arial, Helvetica, sans-serif" style="background-color: white; color: #222222; font-size: small;">Mirror</span><span face="Arial, Helvetica, sans-serif" style="background-color: white; color: #222222; font-size: small;"> </span><span class="il" face="Arial, Helvetica, sans-serif" style="background-color: white; color: #222222; font-size: small;">List</span><span face="Arial, Helvetica, sans-serif" style="background-color: white; color: #222222; font-size: small;"> </span><span face="Arial, Helvetica, sans-serif" style="background-color: white; color: #222222; font-size: small;">Admins</span></p></blockquote><p> </p>Unknownnoreply@blogger.comtag:blogger.com,1999:blog-3283954356437794617.post-90604669321457710502021-01-27T20:01:00.007-08:002021-02-06T17:25:52.116-08:00perl.com hijacked <p> The perl.com domain was hijacked this morning, and is currently pointing to a parking site. Work is ongoing to attempt to recover it.</p><p> We encourage you NOT to visit the domain, as there are some signals that it may be related to sites that have distributed malware in the past.</p><p> Some users may have it selected as their CPAN mirror. To update your mirror in CPAN.pm use <span style="font-family: courier;">o conf urllist http://www.cpan.org/</span></p><p><span style="font-family: courier;"></span></p><blockquote><p><span style="font-family: courier;"># perl -MCPAN -eshell<br />cpan shell -- CPAN exploration and modules installation (v2.20)<br />Enter 'h' for help.</span></p><p><span style="font-family: courier;">cpan[1]> o conf urllist http://www.cpan.org/<br />Please use 'o conf commit' to make the config permanent!<br />cpan[2]> o conf commit<br />commit: wrote '/root/.cpan/CPAN/MyConfig.pm'</span></p></blockquote><p><span style="font-family: courier;"></span></p><div>Update 2021-01-28:</div><div><br /></div><blockquote style="border: none; margin: 0px 0px 0px 40px; padding: 0px;"><div style="text-align: left;">Work is underway to attempt to recover the domain. If you're looking for the content, you can visit <a href="https://perldotcom.perl.org">perldotcom.perl.org</a>.</div></blockquote><div><br /></div><div>Update 2021-01-30:</div><div><br /></div><blockquote style="border: none; margin: 0px 0px 0px 40px; padding: 0px;"><div><div style="text-align: left;">Network Solutions is working with Tom Christiansen, the rightful registrant, on the recovery of the Perl.com domain. There is no estimated timeline for its recovery but the process is underway. The Perl.com site is temporarily at <a href="http://perldotcom.perl.org">perldotcom.perl.org</a>. Anyone using a perl.com host for their CPAN mirror should use <a href="http://www.cpan.org">www.cpan.org</a> instead. Please direct all inquiries to brian d foy (brian.d.foy@gmail.com).</div></div></blockquote><br />Update 2021-02-01:<div><br /><blockquote style="border: none; margin: 0px 0px 0px 40px; padding: 0px; text-align: left;">We have contacted Network Solutions and verified that cpan.org is in the right hands and secured.</blockquote><div><br /></div>Update 2021-02-02:<div><br /><blockquote style="border: none; margin: 0px 0px 0px 40px; padding: 0px;"><div style="text-align: left;">Verisign has restored the proper nameservers (*.<a href="http://bitnames.com/">bitnames.com</a>) for <a href="http://perl.com/">perl.com</a>. You should see addresses in 151.101/16. If you still see something different, please leave a comment in <a href="https://www.blogger.com/#">GitHub issue</a> <a href="https://www.blogger.com/#">#313</a>. Some providers or services may have sinkholed or blocked Perl.com; if you are still seeing that, please let us know.</div></blockquote><div><br /></div>Update 2021-02-05:<blockquote><div>Network Solutions has recovered the domain and your whois output should reflect that. If you notice that your firewalls or other security layers still mark perl.com as compromised, please leave us a note at <a href="https://github.com/tpf/perldotcom/issues/313">https://github.com/tpf/perldotcom/issues/313</a>.<p> </p></div></blockquote></div></div>Unknownnoreply@blogger.comtag:blogger.com,1999:blog-3283954356437794617.post-67063640248553831182020-12-04T17:40:00.009-08:002021-02-21T15:37:13.245-08:00rt.cpan.org will sunset on March 1st, 2021<p>Update 2/21/2021:</p><blockquote style="border: none; margin: 0px 0px 0px 40px; padding: 0px;"><p style="text-align: left;">Updated information about the future of rt.cpan.org can be found at https://news.perlfoundation.org/post/rt-cpan-org-future</p></blockquote><p>Update 2020-12-13:</p><blockquote style="border: none; margin: 0px 0px 0px 40px; padding: 0px;"><p>rt.cpan.org will be sunset on March 1st, 2021 due to low and declining use.</p>Back when we started this service, it filled a need by providing a place for CPAN authors to track bug reports and feature requests. In recent years <a href="https://www.blogger.com/#">github.com</a> and other sites have added issue tracking to their git repo hosting and many CPAN authors have migrated to these sites.<br /><p><span style="color: #222222;">If you are a CPAN author, there are several tools to help you migrate existing tickets:</span></p></blockquote><p style="text-align: left;"></p><ul style="text-align: left;"><ul><li><span face="Arial, Helvetica, sans-serif" style="color: #222222;">https://github.com/dagolden/zzz-rt-to-github</span></li><li><span face="Arial, Helvetica, sans-serif" style="color: #222222;">https://github.com/houseabsolute/RTx-ToGitHub</span></li></ul></ul><p style="text-align: left;"></p><p style="text-align: left;"><span face="Arial, Helvetica, sans-serif" style="color: #222222;"><span style="background-color: white;"></span></span></p><blockquote style="border: none; margin: 0px 0px 0px 40px; padding: 0px; text-align: left;"><div>See Dave Cross' <a href="https://perlhacks.com/2020/12/rt-action-plan-for-cpan-authors/">Plan for CPAN Authors</a>, which describes steps you may wish to take to transition to a new bug tracking system. </div><p>We're still finalizing the details, but the plan is to provide a static historical archive. </p><p>This post will be updated as we figure things out.</p></blockquote><p>Original Post 2020-12-04: </p><blockquote style="border: none; margin: 0px 0px 0px 40px; padding: 0px;"><p style="text-align: left;">(Encompassed by 2020-12-13 update.)</p></blockquote>Unknownnoreply@blogger.comtag:blogger.com,1999:blog-3283954356437794617.post-87638638936615506432020-04-27T21:19:00.000-07:002020-04-27T21:20:13.445-07:00cpan.org email supported by PoboxEarlier this year we quietly switched the infrastructure that forwards ${author}@cpan.org email addresses from our home-grown solution to Pobox’s Bulk Forwarding system. Our system wasn’t keeping up with the spam-filtering needs of these widely published email addresses.<br />
<br />
<a href="https://www.pobox.com/">Pobox</a> is now detecting over 93% of the incoming email to @cpan.org as spam and taking care of it. That’s tens of thousands of spam emails a day that aren’t forwarded on. (Almost 2.5 million emails a month!) Said another way -- less than 7% of emails sent to @cpan.org are valid!<br />
<br />
Beyond improved spam filtering, there’s also better forwarding due to support for SRS (for SPF) and ARC-Seals for DMARC. (The email is less likely to be rejected by the recipient mail server.)<br />
<br />
On behalf of all the CPAN authors, we’d like to thank Pobox.com (part of the <a href="https://www.fastmail.com/">Fastmail</a> family) for providing us this amazing service.Unknownnoreply@blogger.com2tag:blogger.com,1999:blog-3283954356437794617.post-23637897422429332662019-10-30T20:56:00.000-07:002019-10-30T20:56:38.267-07:00Perl bugs now on GitHub<br />For over 17 years, the Perl NOC has hosted an <a href="https://bestpractical.com/rt">RT</a> instance for Perlbug, the system that tracks and manages Perl bugs and feature requests. Two weekends ago, it <a href="https://www.nntp.perl.org/group/perl.perl5.porters/2019/10/msg256484.html">transitioned to GitHub</a>. Background is available in <a href="https://www.nntp.perl.org/group/perl.perl5.porters/2019/10/msg256405.html">this thread.</a><div>
<br /></div>
<div>
We'd especially like to thank <a href="https://github.com/toddr">Todd Rinaldo</a> who led the migration and did most of the work. His attention to detail cannot be understated. 17 years of data (some of which had been migrated to RT from the <i>previous</i> system) required <b>a lot</b> of tweaking and polishing to make it look nice. His hard work shows in the <a href="https://github.com/perl/perl5/issues">result</a>.</div>
<div>
<br /></div>
<div>
It's been fun and interesting to support this particular piece of Perl development for so long. We're excited about the new possibilities that GitHub's platform enables for Perl's fourth decade.</div>
Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-3283954356437794617.post-10571712664374311302019-09-16T22:30:00.004-07:002019-09-16T22:30:48.390-07:00Henk Penning<div style="font-family: LucidaGrande; font-size: 13px;">
It is with great sadness that we must report that Henk "HPP" Penning passed away this summer. For the last decade he was the sole maintainer of the CPAN mirrors list, patiently working with hundreds of mirror operators around the world. He also managed the system that monitored the status of those mirrors, ensuring that out of date mirrors were quickly detected and removed. His “instant mirroring” client was used by many mirrors to ensure that their copy of CPAN was up to date within minutes of a new package being added.<br /><br />Even through the end, he carefully, gracefully, and with lots of patience made sure others had access to the systems he was running. He quietly worked in the background, but every Perl developer benefited from his work, knowingly or not.<br /><br />He was also member of the Apache Software Foundation (and also managed their mirror network). They posted a very <a href="https://www.apache.org/memorials/henk_penning.html">nice memorial page</a> that's worth reading.</div>
<div style="font-family: LucidaGrande; font-size: 13px;">
<br /></div>
<div style="font-family: LucidaGrande; font-size: 13px;">
We remember Henk for his ever present kindness and helpfulness. The Perl and broader open source communities are will miss him.</div>
<div style="font-family: LucidaGrande; font-size: 13px;">
<br /></div>
<div style="font-family: LucidaGrande; font-size: 13px;">
- Ask & Robert</div>
Ask Bjørn Hansenhttp://www.blogger.com/profile/18151118918935346897noreply@blogger.com0tag:blogger.com,1999:blog-3283954356437794617.post-71742122514731717362019-06-08T10:28:00.000-07:002019-06-09T11:40:23.263-07:00New perldoc siteOur friends at <a href="https://opusvl.com/">OpusVL</a> have built a beautiful new<a href="https://perldoc.perl.org/"> perldoc.perl.org</a> site.<br />
<br />
The site automatically gets updated with <a href="https://perldoc.perl.org/5.30.0/">new versions</a>, and all the <a href="https://perldoc.perl.org/functions/say.html">old URLs</a> should work.<br />
<br />
To report bugs, make pull requests or feature suggestions, see the GitHub projects: <a href="https://github.com/OpusVL/perldoc.perl.org-engine">perldoc.perl.org-engine</a> and <a href="https://github.com/OpusVL/perldoc.perl.org-export">perldoc.perl.org-export</a>.<br />
<br />
(The site is still on the <a href="https://www.fastly.com/">Fastly CDN</a>, so it should load nice and fast anywhere).Ask Bjørn Hansenhttp://www.blogger.com/profile/18151118918935346897noreply@blogger.com0tag:blogger.com,1999:blog-3283954356437794617.post-23554196649836479922019-04-30T20:46:00.003-07:002019-04-30T20:46:41.090-07:00Maintenance WeekWe're making some changes to the perl NOC hosting infrastructure this week. There may be some instability. We'll do our best to minimize it. When we're done, we'll post an update with what's changed....Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-3283954356437794617.post-15134758803543238362019-01-27T10:35:00.001-08:002019-01-27T22:19:24.297-08:00Email OutageDue to a server failure, perl.org and cpan.org email is not currently flowing. We're working on repairing it, but it may take several hours.<br />
<br />
Update: The instance has suffered significant file-system corruption. We're attempting to restore from a backup. This may result in the loss of a small amount of mail that had been received but not yet delivered.<br />
<br />
Update: Mail is flowing again. It may take a few hours for the backlog to clear.Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-3283954356437794617.post-20357583118534575152018-07-29T10:28:00.001-07:002018-07-29T10:28:04.709-07:00Server maintenanceWe're doing <a href="https://status.ntppool.org/incidents/cppkb77x1pbm">maintenance today</a> to the servers and network setup; disruptions to the CPAN master mirror, PAUSE, rt.cpan.org, rt.perl.org and the perl.org mailing lists may happen through the next ~8 hours (and possibly after as we finish things up).<br />
<br />
Many of the servers are getting new drives or SSDs and the network setup will get a small overhaul if all goes well.Ask Bjørn Hansenhttp://www.blogger.com/profile/18151118918935346897noreply@blogger.com0tag:blogger.com,1999:blog-3283954356437794617.post-14111674807533107232018-07-01T18:21:00.002-07:002018-07-01T23:23:44.773-07:00Network issues: Where'd the magic smoke go?We had a router failure on Saturday night, which took the perl.org network equipment offline for most of the night. We were able to cobble things back together, but as of now (Sunday afternoon) we're still working out some kinks in our solution. In particular we're not getting the throughput we expect. You may notice that some services are slower than normal.<br />
<br />
We'll update this blog post with any significant updates.<br />
<br />
<b>Update July 1, 2018 10:00pm: <span style="font-family: "courier new" , "courier" , monospace;"> </span></b><span style="font-size: 13px;"><span style="font-family: "courier new" , "courier" , monospace;">set hw.vtnet.tso_disable=1</span></span> is the magic that got our speeds back up and helped with some other weirdness. <br />
<div>
<span style="font-family: "roboto" , sans-serif; font-size: 13px;"><br /></span>
<span style="font-family: "roboto" , sans-serif; font-size: 13px;"></span><br />
<div style="-webkit-text-stroke-width: 0px; color: black; font-family: "Times New Roman"; font-size: medium; font-style: normal; font-variant-caps: normal; font-variant-ligatures: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-decoration-color: initial; text-decoration-style: initial; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px;">
</div>
<br />
<div style="margin: 0px; text-decoration-color: initial; text-decoration-style: initial;">
<b style="-webkit-text-stroke-width: 0px; color: black; font-family: "Times New Roman"; font-style: normal; font-variant-caps: normal; font-variant-ligatures: normal; letter-spacing: normal; text-transform: none; white-space: normal; word-spacing: 0px;">Update July 1, 2018 11:23pm:</b><b style="-webkit-text-stroke-width: 0px; color: black; font-family: "Times New Roman"; font-style: normal; font-variant-caps: normal; font-variant-ligatures: normal; font-weight: 400; letter-spacing: normal; text-transform: none; white-space: normal; word-spacing: 0px;"> <span style="font-family: "courier new" , "courier" , monospace;"> </span></b>IPv6 is working again too. Time for sleep.</div>
</div>
<div class="Mu SP" data-tooltip="July 1, 2018 at 8:51:40 PM UTC-7" id=":rp.ma" style="font-family: Roboto, sans-serif; font-size: 13px; line-height: 16px; margin-bottom: 6px; margin-left: 9px; margin-right: 9px; opacity: 1; transition: opacity 0.218s ease 0s; word-break: break-word; word-wrap: break-word;">
<div class="xH" id=":rp.at" style="color: #263238; text-align: center;">
</div>
<span class="tL8wMe EMoHub" dir="ltr" id=":rp.co" style="color: #263238;"></span></div>
Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-3283954356437794617.post-80842163863926864732018-06-26T20:44:00.000-07:002018-06-26T20:44:03.482-07:00search.cpan.org ➡️ metacpan.orgYesterday, we threw the switch and routed all traffic for <a href="http://search.cpan.org/">search.cpan.org</a> to <a href="http://metacpan.org/">metacpan.org</a>! <br />
<br />
The MetaCPAN team has worked hard to ensure that almost all links continue to work and that it will be a painless experience for users. <br />
<br />
Olaf Alders, founder of MetaCPAN, has written <a href="https://www.perl.com/article/saying-goodbye-to-search-cpan-org/">a perl.com article where you can read more about the switch</a>.<br />
<br />
<a href="https://log.perl.org/2018/05/goodbye-search-dot-cpan-dot-org.html">A fond farewell to search.cpan.org</a>. We'll miss you!<br />
<br />Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-3283954356437794617.post-40177848134107460952018-06-06T21:20:00.005-07:002018-06-06T21:20:33.812-07:00CPANRatings going read-only<a href="https://cpanratings.perl.org/">CPANRatings</a> has gone read-only due to low traffic. Existing ratings will still be visible, but it is no longer possible to add new ratings.<br />
<br />
In a few months, we expect that <a href="https://metacpan.org/">MetaCPAN</a> will add review functionality. You can already favorite modules there and see the most popular modules counts.<br />
<br />
Why are we doing this? First, we haven't had time to give the site the attention it deserves in quite a while. There are numerous open bugs and feature requests in the <a href="https://github.com/perlorg/perlweb/labels/cpanratings">GitHub issue tracker.</a> Second, it gets extremely low traffic. Only a few hundred visitors a week, rarely leaving reviews. This will also allow us to shut down a few dependent services and free up resources for other use.<br />
<br />
We know that CPANRatings is important to its (few) users and the community, and we look forward to the MetaCPAN replacement. The current site will remain in read-only mode until the replacement is finished.Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-3283954356437794617.post-12069134757938468452018-05-16T21:29:00.001-07:002018-05-19T18:24:45.479-07:00The end of an era: Saying goodbye to search.cpan.orgIt's with sad hearts that we are announcing that <a href="http://search.cpan.org/">search.cpan.org</a> will be retired on the 25th of June 2018.<br />
<br />
Graham Barr originally wrote the site nearly 20 years ago -- it first went live in early 1999 -- and it quickly became an invaluable resource for Perl developers around the world.<br />
<br />
The ability to search <a href="http://www.cpan.org/">CPAN</a> (Comprehensive Perl Archive Network) and read Perl module documentation online helped spark many developers interest in Perl and helped to build the Perl community.<br />
<br />
The site was originally hosted by <a href="http://www.wustl.edu/">Washington University in St. Louis</a> on a single Solaris box. For his work on search.cpan.org, Graham won a <a href="https://www.perl.org/advocacy/white_camel/2002.html">White Camel award in 2002</a>.<br />
<br />
The site was later moved to the <a href="https://log.perl.org/">Perl NOC</a>. US mirrors were hosted by <a href="http://www.yellowbot.com/">YellowBot</a> and <a href="https://www.phyber.com/">Phyber</a> and a European mirror has been hosted by <a href="http://digitalcraftsmen.com/">digital craftsmen</a> for the last 10 years. These amazing people and companies helped make the site a success.<br />
<br />
In recent years maintenance has become a burden. Most of the site is running 2005 era Perl code. Luckily, there is now a viable alternative: <a href="https://metacpan.org/">MetaCPAN.org</a>. The MetaCPAN team has been getting ready for the transition and is nearly ready to take over.<br />
<br />
Shortly, a link will be added to all pages on search.cpan.org to inform users of the upcoming change. After about a month, all traffic will be redirected to the equivalent MetaCPAN page.<br />
<br />
We would like to thank all who have assisted with this project. An extra special thanks to Graham for his hard work and unwavering support of search.cpan.org for all these years. To search.cpan.org -- we will miss you.<br />
<br />
<b>Update #1 (2018-05-19)</b>: There's some confusion around whether or not existing search.cpan.org URLs will continue to work. They will! The vast majority of of them will be transparently served by MetaCPAN pages. You do not need to update any links right now.Unknownnoreply@blogger.com44tag:blogger.com,1999:blog-3283954356437794617.post-61811632668015761402018-03-24T16:30:00.002-07:002018-03-24T16:30:30.021-07:00Goodbye BitcardFourteen years ago, it seemed like a good idea to have perl.org SSO solution. So, we built one -- Bitcard -- and deployed it across perl.org and related sites. Today, it doesn't make much sense. Nobody wants yet another account to keep track of -- especially only for limited use such as perl.org related sites.<br />
<br />
We're switching our authentication systems to use <a href="https://www.auth0.com/">Auth0</a>. If you want to have a login just for us, you still can. You can also use your Google, GitHub, or Facebook account, and Auth0 will proxy the identity. Through the magic of OAuth2, we don't get access to anything except your name and email address.<br />
<br />
If you are logging into a perl.org site for the first time with Auth0, be sure to use the same email address you used with Bitcard, or your may end up with a new account.<br />
<br />
rt.perl.org and rt.cpan.org have already switched to Auth0. There's a few stragglers remaining, and then we'll shut down Bitcard. It has served us well.<br />
<br />
Thanks again to Auth0 for their great service!<br />
<br />
<br />
<br />
<br />Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-3283954356437794617.post-17874288589490867802017-08-31T17:17:00.005-07:002017-08-31T17:51:08.882-07:00TLS only for www.cpan.orgwww.cpan.org has supported TLS <a href="http://log.perl.org/2017/03/fast-and-secure-perl-docs-and-cpan.html">since Ma</a><a href="http://log.perl.org/2017/03/fast-and-secure-perl-docs-and-cpan.html">rch</a>. We're planning to make it <a href="https://blog.chromium.org/2017/04/next-steps-toward-more-connection.html?utm_source=wnc_10038795&utm_medium=gamma&utm_campaign=wnc_10038795&utm_content=msg_100078324&hl=en">TLS-only later in September,</a> pending feedback. To start the process the <a href="https://www.cpan.org/">homepage</a> now redirects to the TLS version. Over the next days and weeks we'll make more and more of the URLs TLS-only.<br />
<br />
Please let us know if this causes problems for common CPAN clients.<br />
<br />
(IPv6 has also been <a href="http://log.perl.org/2011/06/wwwcpanorg-now-on-ipv6.html?showComment=1504227020792#c4620529093618562149">re-enabled</a> for <a href="http://www.cpan.org/">www.cpan.org</a>).Ask Bjørn Hansenhttp://www.blogger.com/profile/18151118918935346897noreply@blogger.com3tag:blogger.com,1999:blog-3283954356437794617.post-23383324726951284872017-06-12T20:15:00.001-07:002017-06-12T20:15:10.104-07:00pm.org group hosting shutting downAs announced to the pm group leader mailing list, the pm.org group website hosting service is shutting down at the end of June 2017. Sites will be maintained read-only for a period of time, but cannot be updated after that point.<br />
<br />
Group leaders should contact pm.org support to point DNS to at an alternate hosting service if they wish to be able to edit their sites.Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-3283954356437794617.post-58615506099616248492017-05-13T22:00:00.000-07:002017-05-13T22:59:24.362-07:00Network Maintenance (May 14, 2017 - 05:00 UTC)Our hosting facility (<a href="http://www.phyber.com/">Phyber</a>) is performing maintenance in order to upgrade their networking equipment. This may result in some perl.org services being unavailable for the next few hours as hardware is forklifted.<br />
<br />
Affected services may include:<br />
<ul>
<li>perl.org email and mailing lists</li>
<li>pm.org email and mailing lists</li>
<li>rt.perl.org</li>
<li>rt.cpan.org</li>
<li>pause.perl.org</li>
<li>nntp.perl.org</li>
<li>some perl.org websites</li>
<li>search.cpan.org from some locations</li>
<li>(and others)</li>
</ul>
<div>
The new hardware sure looks pretty!</div>
<div>
<br /></div>
<div class="separator" style="clear: both; text-align: center;">
<a href="http://www.cisco.com/c/dam/en/us/td/docs/routers/asr9000/software/asr9k_r4-2/getting_started/configuration/guide/gs42over.fm/_jcr_content/renditions/gs42over-2.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="http://www.cisco.com/c/dam/en/us/td/docs/routers/asr9000/software/asr9k_r4-2/getting_started/configuration/guide/gs42over.fm/_jcr_content/renditions/gs42over-2.jpg" /></a></div>
<div>
<br /></div>
Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-3283954356437794617.post-36585899371259456152017-05-13T12:15:00.002-07:002017-05-13T12:15:27.999-07:00perl.org has a new look!Thanks to Babs Veloso (<a href="https://twitter.com/babsveloso">@babsveloso</a>) for her hard work on creating a fresh new look for the perl.org websites! <a href="http://www.perl.org/">It's live now</a>!<br />
<br />
Thew new design is clean and responsive for a better experience on sizes and shapes of devices. It brings the site up to date with current best practices for design and implementation. We're very excited. It's hard to believe it's been almost 8 years since we launched the <a href="http://log.perl.org/2009/11/a-new-look-for-perlorg.html">previous look</a>. Unknownnoreply@blogger.com1tag:blogger.com,1999:blog-3283954356437794617.post-91868870827262521792017-03-18T15:27:00.002-07:002017-05-29T23:49:08.170-07:00Fast and secure Perl docs and CPAN modules with help from Fastly<div style="text-align: center;">
<br /></div>
<div class="separator" style="clear: both; text-align: center;">
<a href="https://www.fastly.com/assets/logo_retina-6c0c411741bae625f3eb00957f02ff862a8ae2aba046fa3aaed76d6232433564.png?width=260" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="108" data-original-width="260" src="https://www.fastly.com/assets/logo_retina-6c0c411741bae625f3eb00957f02ff862a8ae2aba046fa3aaed76d6232433564.png?width=260" /></a></div>
<div style="text-align: center;">
<br /></div>
<div class="" style="clear: both; text-align: center;">
</div>
<div class="" style="clear: both; text-align: center;">
<span style="text-align: left;"><span style="text-align: center;">We'd like to thank Fastly </span>for hosting <a href="https://www.cpan.org/">www.cpan.org</a> and <a href="https://perldoc.perl.org/">perldoc.perl.org</a> on their world class global CDN. </span></div>
<div class="" style="clear: both; text-align: center;">
<span style="text-align: left;"><br /></span></div>
<div class="" style="clear: both; text-align: center;">
<span style="text-align: left;">As of last week, the sites are also available using https://!</span></div>
<div class="" style="clear: both; text-align: center;">
<span style="text-align: left;"><br /></span></div>
<div class="" style="clear: both; text-align: center;">
<span style="text-align: left;"> So you can now securely read the Perl core documentation or download over 180,000 modules at lightning fast speeds.</span></div>
Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-3283954356437794617.post-58227057617197382752016-11-25T12:49:00.002-08:002016-11-25T12:49:54.017-08:00Email upgradesOver the last many months Robert has worked on upgrading cleaning up some of the (more than a decade old) email forwarding and spam filtering infrastructure.<br />
<br />
We switched some more MX records over the last 24 hours and some domains and email addresses didn't work correctly. The relevant DNS changes have been reverted. We'll try again sometime soon.Ask Bjørn Hansenhttp://www.blogger.com/profile/18151118918935346897noreply@blogger.com0tag:blogger.com,1999:blog-3283954356437794617.post-85706028713027899812016-06-10T22:31:00.000-07:002016-06-10T22:31:00.577-07:00Thanks to Digital CraftsmenI just wanted to take a moment to give a quick "thank you" to Ben, Fahimul, Simon and the rest of the team at <a href="https://www.digitalcraftsmen.com/">Digital Craftsmen</a>. They host the European <a href="http://search.cpan.org/">CPAN Search</a> mirror. Recently they noticed the mirror wasn't performing as well as it should have been. Then they helped quickly track down and resolve the issue. Most hosting providers won't do that. So...<br />
<blockquote class="tr_bq">
<br />Dear Digital Craftsmen, </blockquote>
<blockquote class="tr_bq">
Thank you for your help and continued support of Perl!</blockquote>
<blockquote class="tr_bq">
-The perl.org Team.</blockquote>
Unknownnoreply@blogger.com0