unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: debian mipsel buildd maintainers <mipsel@buildd.debian.org>,
	Notmuch Mail <notmuch@notmuchmail.org>
Subject: Re: build failures on mipsel
Date: Wed, 06 Jun 2018 13:05:15 -0400	[thread overview]
Message-ID: <87po139778.fsf@fifthhorseman.net> (raw)
In-Reply-To: <871sdk9edk.fsf@fifthhorseman.net>

On Wed 2018-06-06 10:30:15 -0400, Daniel Kahn Gillmor wrote:
> Furthermore, i can't replicate the failure from the buildd when building
> on eller either.  So neither bremner nor i were able to replicate the
> problem.
>
> mipsel porters, do you have any suggestions for next-step debugging?

I notice that the two failures for notmuch

  https://buildd.debian.org/status/fetch.php?pkg=notmuch&arch=mipsel&ver=0.27%7Erc0-1&stamp=1527466396&raw=0
  https://buildd.debian.org/status/fetch.php?pkg=notmuch&arch=mipsel&ver=0.27%7Erc1-1&stamp=1528017305&raw=0

are both built on the buildd mipsel-manda-03.debian.org.

perhaps there's something wrong with that buildd?  maybe a giveback
would let another build daemon take a crack at the package.

mipsel folks, could you give back the experimental version of notmuch to
the mipsel buildd network and try to avoid having it land on
mipsel-manda-03?

thanks,

      --dkg

  parent reply	other threads:[~2018-06-06 17:05 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
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 [this message]
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=87po139778.fsf@fifthhorseman.net \
    --to=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).