CEPH filesystem development
 help / color / mirror / Atom feed
From: Ken Dreyer <kdreyer@redhat.com>
To: Loic Dachary <loic@dachary.org>,
	David Zafman <david.zafman@inktank.com>,
	ceph-devel@vger.kernel.org
Subject: Re: Some gitbuilders not working
Date: Fri, 09 Jan 2015 06:40:57 -0700	[thread overview]
Message-ID: <54AFDA69.2080002@redhat.com> (raw)
In-Reply-To: <54AFAE7D.5070402@dachary.org>

On 01/09/2015 03:33 AM, Loic Dachary wrote:
> On 09/01/2015 07:55, David Zafman wrote:
>>
>> We are seeing gitbuilder failures.  This is what I saw on one.
>>
>> error: Failed build dependencies:
>> xmlstarlet is needed by ceph-1:0.90-821.g680fe3c.el7.x86_64
> 
> This is because https://github.com/ceph/ceph/pull/3036 was recently merged.
> However, https://github.com/ceph/autobuild-ceph/pull/19 added xmlstarlet
> about a month ago. Maybe some gitbuilder machines were not updated
> accordingly. If I'm not mistaken this is a manual process but I'm not sure
> exactly how to do it myself.

I'm not entirely sure of the SOP to apply fabfile changes across our
infrastructure, either. Is there a simple "push this fabfile change
everywhere" command for gitbuilder?

In the long term we'll want to get to a point where we're building
Ceph's RPM packages using mock [1] instead of rpmbuild so that mock can
resolve these sort of things automatically without having to deal with
installing new BuildRequires by hand.

- Ken

[1] http://fedoraproject.org/wiki/Projects/Mock


  parent reply	other threads:[~2015-01-09 13:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-09  6:55 Some gitbuilders not working David Zafman
2015-01-09 10:33 ` Loic Dachary
2015-01-09 13:34   ` Loic Dachary
2015-01-09 13:40   ` Ken Dreyer [this message]
2015-01-09 15:16     ` Sage Weil
2015-01-14 16:56       ` Ken Dreyer
2015-01-14 17:22         ` Loic Dachary
2015-01-14 17:30         ` Sage Weil
  -- strict thread matches above, loose matches on Subject: below --
2015-01-09  6:56 David Zafman

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=54AFDA69.2080002@redhat.com \
    --to=kdreyer@redhat.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=david.zafman@inktank.com \
    --cc=loic@dachary.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox