From: David Bremner <david@tethera.net>
To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>,
debian mipsel buildd maintainers <mipsel@buildd.debian.org>,
Notmuch Mail <notmuch@notmuchmail.org>
Subject: Re: build failures on mipsel
Date: Mon, 04 Jun 2018 23:44:25 -0300 [thread overview]
Message-ID: <87d0x6osty.fsf@tethera.net> (raw)
In-Reply-To: <87wove9q35.fsf@fifthhorseman.net>
Daniel Kahn Gillmor <dkg@fifthhorseman.net> writes:
>
>
> I've tried to replicate the problem over on eller.debian.org (the mipsel
> porterbox) but when i build 0.27~rc1 over there in an schroot, i don't
> even get to T357 because the emacs_fcc_message() function hangs in this
> loop (is this known to not work in an schroot or under similar
> situations?):
Try:
$ make test-binaries && ./T357-index-decryption.sh
That works for me on eller, so there must be some difference between the
two environments (buildd versus porterbox)
d
next prev parent reply other threads:[~2018-06-05 2:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-04 21:52 build failures on mipsel Daniel Kahn Gillmor
2018-06-05 2:44 ` David Bremner [this message]
2018-06-06 14:15 ` Daniel Kahn Gillmor
2018-06-06 14:59 ` David Bremner
2018-06-05 18:12 ` Tomi Ollila
2018-06-06 14:30 ` Daniel Kahn Gillmor
2018-06-06 14:47 ` Tomi Ollila
2018-06-06 17:05 ` Daniel Kahn Gillmor
2018-06-07 13:58 ` Daniel Kahn Gillmor
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://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d0x6osty.fsf@tethera.net \
--to=david@tethera.net \
--cc=dkg@fifthhorseman.net \
--cc=mipsel@buildd.debian.org \
--cc=notmuch@notmuchmail.org \
/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://yhetil.org/notmuch.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).