Certainly removing the "--no-binary :all:" results in a build that builds.
I'll test and see if it works todayish.
Michael
On Mon, Jun 12, 2017 at 9:56 PM, Chris Smart wrote:
> On Mon, 12 Jun 2017, at 21:36, Michael Still wrote:
> > The experimental buildroot based ironic
On Mon, 12 Jun 2017, at 21:36, Michael Still wrote:
> The experimental buildroot based ironic python agent bans all binaries, I
> am not 100% sure why. Chris is the guy there.
>
Buildroot ironic python agent forces a build of all the
ironic-python-agent dependencies (as per requirements and
The experimental buildroot based ironic python agent bans all binaries, I
am not 100% sure why. Chris is the guy there.
I'm using that ipa as neither the coreos or tinyipa versions support the
broadcom nic in this here ibm x3550.
Michael
On 12 Jun 2017 8:56 PM, "Sean Dague"
On 06/12/2017 04:29 AM, Michael Still wrote:
> Hi,
>
> I'm trying to explain this behaviour in stable/newton, which specifies
> Routes==2.3.1 in upper-constraints:
>
> $ pip install --no-binary :all: Routes==2.3.1
> ...
> Could not find a version that satisfies the requirement Routes==2.3.1
>
On Mon, 12 Jun 2017, at 18:29, Michael Still wrote:
> Hi,
>
> This implies to me that perhaps Routes version 2.3.1 is a binary-only
> release and that stable/newton is therefore broken for people who don't
> like binary packages (in my case because they're building an install
> image
> for an
Hi,
I'm trying to explain this behaviour in stable/newton, which specifies
Routes==2.3.1 in upper-constraints:
$ pip install --no-binary :all: Routes==2.3.1
...
Could not find a version that satisfies the requirement Routes==2.3.1
(from versions: 1.5, 1.5.1, 1.5.2, 1.6, 1.6.1, 1.6.2, 1.6.3,