[Slackbuilds-users] Lua 5.4 upgrade

Mon Oct 28 10:42:05 UTC 2024

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)

https://ponce.cc/slackware/sources/repo/lpeg-1.1.0.tar.gz

you can use that, if you prefer

Matteo

Il giorno lun 28 ott 2024 alle ore 11:33 Nick Smallbone <nick at smallbone.se>
ha scritto:

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