From: Leo Famulari <leo@famulari.name>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 7/7] gnu: Add prosody.
Date: Mon, 29 Aug 2016 21:36:31 -0400 [thread overview]
Message-ID: <20160830013631.GB19488@jasmine> (raw)
In-Reply-To: <87a8fx5gcp.fsf@elephly.net>
On Sun, Aug 28, 2016 at 12:37:42PM +0200, Ricardo Wurmus wrote:
> LuaSec is found by “util/dependencies.lua” or else we would see a
> complaint printed to stdout upon application start.
>
> Archlinux users also reported problems with latest prosody and latest
> luasec: https://bugs.archlinux.org/task/48480
>
> This makes me think that this is not a problem with this package per se,
> but with Prosody.
Okay, hopefully there is a fix available soon!
next prev parent reply other threads:[~2016-08-30 1:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-22 19:39 [PATCH 0/7] Add Prosody Ricardo Wurmus
2016-08-22 19:39 ` [PATCH 1/7] gnu: lua: Build with support for dynamic libraries Ricardo Wurmus
2016-08-22 20:05 ` Leo Famulari
2016-08-23 0:02 ` gno
2016-08-28 8:23 ` Ricardo Wurmus
2016-08-30 6:37 ` Leo Famulari
2016-08-22 19:39 ` [PATCH 2/7] gnu: lua: Use "license:" prefix Ricardo Wurmus
2016-08-22 19:39 ` [PATCH 3/7] gnu: Add lua5.1-expat Ricardo Wurmus
2016-08-22 19:53 ` Leo Famulari
2016-08-22 19:39 ` [PATCH 4/7] gnu: Add lua5.1-socket Ricardo Wurmus
2016-08-22 19:39 ` [PATCH 5/7] gnu: Add lua5.1-filesystem Ricardo Wurmus
2016-08-22 19:39 ` [PATCH 6/7] gnu: Add luasec Ricardo Wurmus
2016-08-22 19:39 ` [PATCH 7/7] gnu: Add prosody Ricardo Wurmus
2016-08-23 1:33 ` Leo Famulari
2016-08-28 10:37 ` Ricardo Wurmus
2016-08-30 1:36 ` Leo Famulari [this message]
2016-08-22 20:03 ` [PATCH 0/7] Add Prosody Leo Famulari
2016-08-22 20:37 ` Ricardo Wurmus
[not found] <9cf2a138-d37a-b88e-57f6-c053b0dbb670@gmail.com>
2016-08-30 8:44 ` [PATCH 1/7] gnu: lua: Build with support for dynamic libraries gno
2016-08-30 19:33 ` Efraim Flashner
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160830013631.GB19488@jasmine \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).