<div dir="ltr"><div>no, it isn't you, I had the same problem with wget and that certificate, that's why I mirrored it on my server (to use it with neovim)</div><div><br></div><div><a href="https://ponce.cc/slackware/sources/repo/lpeg-1.1.0.tar.gz">https://ponce.cc/slackware/sources/repo/lpeg-1.1.0.tar.gz</a></div><div><br></div><div>you can use that, if you prefer</div><div><br></div><div>Matteo<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Il giorno lun 28 ott 2024 alle ore 11:33 Nick Smallbone <<a href="mailto:nick@smallbone.se">nick@smallbone.se</a>> ha scritto:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi,<br>
<br>
I've just tested games/CorsixTH and it builds and runs fine.<br>
<br>
However, I have trouble downloading lua-lpeg with wget:<br>
<br>
% wget <a href="https://www.inf.puc-rio.br/~roberto/lpeg/lpeg-1.1.0.tar.gz--2024-10-28" rel="noreferrer" target="_blank">https://www.inf.puc-rio.br/~roberto/lpeg/lpeg-1.1.0.tar.gz<br>
--2024-10-28</a> 10:47:31-- <a href="https://www.inf.puc-rio.br/~roberto/lpeg/lpeg-1.1.0.tar.gz" rel="noreferrer" target="_blank">https://www.inf.puc-rio.br/~roberto/lpeg/lpeg-1.1.0.tar.gz</a><br>
Resolving <a href="http://www.inf.puc-rio.br" rel="noreferrer" target="_blank">www.inf.puc-rio.br</a> (<a href="http://www.inf.puc-rio.br" rel="noreferrer" target="_blank">www.inf.puc-rio.br</a>)... 139.82.16.205<br>
Connecting to <a href="http://www.inf.puc-rio.br" rel="noreferrer" target="_blank">www.inf.puc-rio.br</a> (<a href="http://www.inf.puc-rio.br" rel="noreferrer" target="_blank">www.inf.puc-rio.br</a>)|139.82.16.205|:443... connected.<br>
ERROR: cannot verify <a href="http://www.inf.puc-rio.br" rel="noreferrer" target="_blank">www.inf.puc-rio.br</a>'s certificate, issued by ‘CN=R11,O=Let's Encrypt,C=US’:<br>
Unable to locally verify the issuer's authority.<br>
To connect to <a href="http://www.inf.puc-rio.br" rel="noreferrer" target="_blank">www.inf.puc-rio.br</a> insecurely, use `--no-check-certificate'.<br>
<br>
I've tried it on a few machines (also non-Slackware ones), and the download fails with wget or curl, and succeeds with Firefox. Seems to be an SSL misconfiguration where the server isn't sending the whole certificate chain.<br>
<br>
Of course it might be a case of PEBKAC but if it isn't, would it make sense to mirror the tarball somewhere else?<br>
<br>
Nick<br>
<br>
On Sun, 27 Oct 2024, at 12:17 AM, B. Watson wrote:<br>
> For the past 2 weeks, the SBo team has been working on upgrading SBo's<br>
> lua package to Lua 5.4, to match Slackware-current's recent addition<br>
> of a lua package.<br>
><br>
> To make this work, a lot of scripts needed surgery. The result (or<br>
> actually the work in progress) is in the lua54-fixes git branch.<br>
><br>
> Major changes:<br>
><br>
> - lua has been upgraded to 5.4.<br>
> - lua 5.1 still exists, under the name lua51.<br>
> - lua52 and lua53 have been removed.<br>
> - all builds that used to use lua (5.1) now use either lua 5.4, or lua51,<br>
> or in a few cases luajit, for things that just won't work with 5.4.<br>
><br>
> If you maintain anything that depends on lua, lua52, or lua53, you<br>
> should check out the lua54-fixes branch, build your packages, and make<br>
> sure they work correctly.<br>
><br>
> I'm in the process of run-testing everything I'm able to (not just<br>
> build the package, but install and use it), but there are a few<br>
> things I can't test because they require hardware I don't have (e.g<br>
> roccat-tools and lxi-tools), or because they require more time/effort<br>
> to learn how to use, than I have available currently (e.g. prosody<br>
> and pdns).<br>
><br>
> The builds affected are listed here:<br>
><br>
> <a href="https://slackbuilds.org/advsearch.php?stype=revdep&q=lua" rel="noreferrer" target="_blank">https://slackbuilds.org/advsearch.php?stype=revdep&q=lua</a><br>
><br>
> <a href="https://slackbuilds.org/advsearch.php?stype=revdep&q=lua52" rel="noreferrer" target="_blank">https://slackbuilds.org/advsearch.php?stype=revdep&q=lua52</a><br>
><br>
> <a href="https://slackbuilds.org/advsearch.php?stype=revdep&q=lua53" rel="noreferrer" target="_blank">https://slackbuilds.org/advsearch.php?stype=revdep&q=lua53</a><br>
><br>
> If you see your build(s) there, please test the lua54-fixes versions<br>
> of them. Builds that mention lua/lua52/lua53 as optional in their READMEs<br>
> aren't listed here, but those should be checked too, if you have any.<br>
><br>
> If you're not familiar with git, you can get the modified builds by<br>
> doing this:<br>
><br>
> git clone <a href="https://git.slackbuilds.org/slackbuilds" rel="noreferrer" target="_blank">https://git.slackbuilds.org/slackbuilds</a> sboluatest<br>
> cd sboluatest<br>
> git checkout lua54-fixes<br>
><br>
> If you use sbopkg or sbotools, you can also configure those to use<br>
> the lua54-fixes branch (see the documentation, I don't use sbopkg or<br>
> sbotools often enough to write a how-to here).<br>
><br>
> It'd be best to do your testing on a clean install of Slackware 15.0,<br>
> possibly a VM or chroot. If you can't do this, you should at least<br>
> removepkg lua, lua52, lua53, and anything that you may have installed<br>
> that uses lua/lua52/lua53. Start out by building the updated lua (you<br>
> should end up with a package called lua-5.4.7-x86_64-1_SBo.tgz) and<br>
> the new lua51 package, then move on to your packages.<br>
><br>
> If you have any build errors, I'd really like to hear about them. I<br>
> don't *think* that should happen (I'm almost 100% certain that<br>
> everything I modifed will at least *build*). If it happens, please<br>
> send mail to the mailing list, with the build log.<br>
><br>
> If everything builds OK, but then doesn't actually work properly after<br>
> you install and run it, we really need to hear from you on the mailing<br>
> list.<br>
><br>
> If everything tests out OK, please let the list know that, too.<br>
><br>
> If you want to use the github discussion mentioned in Willy's update<br>
> email, you can, but *also* send your reports to this mailing list. I'm<br>
> not the only one working on this, but I've done about 95% of the work,<br>
> and I'm coordinating it. I don't have (nor want) a github account, for<br>
> various reasons, so please use the mailing list.<br>
><br>
> If there are no issues, or if there are issues that can be fixed this<br>
> week, the plan is to merge the lua54-fixes branch as part of next<br>
> week's update, which should happen Friday, November 1. If there are<br>
> problems that can't be fixed by then, we'll delay the merge until the<br>
> 8th, or even the 15th if need be.<br>
> _______________________________________________<br>
> SlackBuilds-users mailing list<br>
> <a href="mailto:SlackBuilds-users@slackbuilds.org" target="_blank">SlackBuilds-users@slackbuilds.org</a><br>
> <a href="https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users" rel="noreferrer" target="_blank">https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users</a><br>
> Archives - <a href="https://lists.slackbuilds.org/pipermail/slackbuilds-users/" rel="noreferrer" target="_blank">https://lists.slackbuilds.org/pipermail/slackbuilds-users/</a><br>
> FAQ - <a href="https://slackbuilds.org/faq/" rel="noreferrer" target="_blank">https://slackbuilds.org/faq/</a><br>
_______________________________________________<br>
SlackBuilds-users mailing list<br>
<a href="mailto:SlackBuilds-users@slackbuilds.org" target="_blank">SlackBuilds-users@slackbuilds.org</a><br>
<a href="https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users" rel="noreferrer" target="_blank">https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users</a><br>
Archives - <a href="https://lists.slackbuilds.org/pipermail/slackbuilds-users/" rel="noreferrer" target="_blank">https://lists.slackbuilds.org/pipermail/slackbuilds-users/</a><br>
FAQ - <a href="https://slackbuilds.org/faq/" rel="noreferrer" target="_blank">https://slackbuilds.org/faq/</a><br>
<br>
</blockquote></div>