From: Efraim Flashner <efraim@flashner.co.il>
To: raingloom <raingloom@riseup.net>
Cc: 41433-done@debbugs.gnu.org
Subject: bug#41433: Sway fails at configure step
Date: Sun, 24 May 2020 08:51:43 +0300 [thread overview]
Message-ID: <20200524055143.GA858@E5400> (raw)
In-Reply-To: <20200523030021.2d79d1f6@riseup.net>
[-- Attachment #1: Type: text/plain, Size: 1143 bytes --]
On Sat, May 23, 2020 at 03:00:21AM +0200, raingloom wrote:
> On Thu, 21 May 2020 15:21:16 +0300
> Efraim Flashner <efraim@flashner.co.il> wrote:
>
> > On Thu, May 21, 2020 at 07:00:46AM +0200, raingloom wrote:
> > > Sway package is broken, when it gets to configure it fails with:
> > >
> > > ```
> > > ../source/meson.build:1:0: ERROR: lexer
> > > ```
> > >
> > > No idea what that means, as I barely know Meson.
> >
> > On which architecture? Running a recent commit? I just built sway with
> > current HEAD without any problems on x86_64.
> >
>
> It was on x64, with a recent commit at the time, but it seems to be
> fixed now. Not sure what the issue was.
> Will this be closed if I write:
>
> Closing.
you have to reply to bug#-done@debbugs.gnu.org and that'll close it.
Alternatively you can send a message to control@debbugs.gnu.org with the
text:
----
close 41433
thanks
----
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2020-05-24 5:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-21 5:00 bug#41433: Sway fails at configure step raingloom
2020-05-21 12:21 ` Efraim Flashner
[not found] ` <20200523030021.2d79d1f6@riseup.net>
2020-05-24 5:51 ` Efraim Flashner [this message]
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=20200524055143.GA858@E5400 \
--to=efraim@flashner.co.il \
--cc=41433-done@debbugs.gnu.org \
--cc=raingloom@riseup.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).