From: Andrey Repin <anrdaemon@yandex.ru>
To: Lemures Lemniscati via Cygwin-announce via Cygwin
<cygwin@cygwin.com>,
cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: lua-5.3.6-2
Date: Mon, 31 May 2021 00:38:57 +0300 [thread overview]
Message-ID: <1104601526.20210531003857@yandex.ru> (raw)
In-Reply-To: <announce.20210520072725.5DC3.50F79699@gmail.com>
Greetings, Lemures Lemniscati via Cygwin-announce via Cygwin!
> The following packages have been uploaded to the Cygwin distribution:
> * lua-5.3.6-2
> * liblua5.3-5.3.6-2
> * liblua-devel-5.3.6-2
> * lua-5.3.6-2-src
> * lua-debuginfo-5.3.6-2
> Lua is a powerful, light-weight programming language designed for extending
> applications. Lua is also frequently used as a general-purpose, stand-alone
> language.
> --
> This is an update to the upstream release 5.3.6 with some bug-fix
> patches:
> https://www.lua.org/bugs.html#5.4.2-2
> https://www.lua.org/bugs.html#5.4.2-3
> In this cygwin update, some files come with version number:
> e.g: lua5.3.exe, which is symlinked from lua by alternatives.
2021/05/29 18:02:19 running: C:\Programs\Cygwin_64\bin\bash.exe --norc --noprofile "/etc/postinstall/lua.sh"
bash.exe: warning: could not find /tmp, please create!
failed to read link /usr/bin/lua: No such file or directory
failed to link /usr/bin/lua -> /etc/alternatives/lua: No such file or directory
failed to link /usr/bin/luac -> /etc/alternatives/luac: No such file or directory
failed to link /usr/lib/liblua.dll.a -> /etc/alternatives/liblua.dll.a: No such file or directory
failed to link /usr/lib/pkgconfig/lua.pc -> /etc/alternatives/lua.pc: No such file or directory
failed to link /usr/share/man/man1/lua.1.gz -> /etc/alternatives/lua.1.gz: No such file or directory
failed to link /usr/share/man/man1/luac.1.gz -> /etc/alternatives/luac.1.gz: No such file or directory
2021/05/29 18:02:19 abnormal exit: exit code=2
$ cygcheck -vf /etc/postinstall/lua.sh
/etc/postinstall/lua.sh: found in package lua-5.3.6-2
--
With best regards,
Andrey Repin
Saturday, May 29, 2021 10:01:15
Sorry for my terrible english...
next prev parent reply other threads:[~2021-05-30 21:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-02 3:20 [ANNOUNCEMENT] lua 5.3.5-1 Yaakov Selkowitz
2021-05-19 22:27 ` [ANNOUNCEMENT] Updated: lua-5.3.6-2 Lemures Lemniscati via Cygwin-announce
2021-05-27 8:49 ` Fergus Daly
2021-05-27 9:52 ` Lemures Lemniscati
2021-05-30 21:38 ` Andrey Repin [this message]
2021-05-30 23:30 ` Lemures Lemniscati
2021-05-31 4:12 ` Lemures Lemniscati
2021-05-31 8:54 ` Andrey Repin
2021-05-31 9:26 ` Andrey Repin
2021-05-31 10:41 ` Lemures Lemniscati
2021-06-01 14:39 ` Updated: lua-5.3.6-3 Lemures Lemniscati
2021-06-01 14:41 ` [ANNOUNCEMENT] " Lemures Lemniscati via Cygwin-announce
2021-06-04 13:16 ` Jon Turney
2021-06-04 16:10 ` Lemures Lemniscati
2021-06-05 22:26 ` [ANNOUNCEMENT] Updated: lua-5.3.6-4 Lemures Lemniscati via Cygwin-announce
2021-05-19 22:47 ` [ANNOUNCEMENT] Test: lua-5.4.3-1 Lemures Lemniscati via Cygwin-announce
2021-06-01 14:46 ` [ANNOUNCEMENT] Test: lua-5.4.3-2 Lemures Lemniscati via Cygwin-announce
2021-06-05 22:36 ` [ANNOUNCEMENT] Test: lua-5.4.3-3 Lemures Lemniscati via Cygwin-announce
2022-03-06 13:29 ` [ANNOUNCEMENT] Test: lua-5.4.4-1 Lemures Lemniscati via Cygwin-announce
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1104601526.20210531003857@yandex.ru \
--to=anrdaemon@yandex.ru \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).