strange architecture limitation
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core (Ubuntu) |
Fix Released
|
High
|
James Page | ||
Saucy |
Fix Released
|
High
|
James Page |
Bug Description
juju-core is "Architecture: amd64 i386" without an obvious explanation that I can see. In general, we shouldn't arbitrarily architecture-
Personally I'd prefer if juju-core were just Architecture: any and we'd just have an obvious and quick dep-wait on powerpc, but at least it seems that we should add armhf; I thought we wanted to make this work there?
If this isn't possible right now for some reason (i.e. it will build but be broken), then I think it'd be helpful to have a comment explaining what's going on.
Related branches
Changed in juju-core (Ubuntu): | |
importance: | Undecided → High |
status: | New → Triaged |
Changed in juju-core (Ubuntu): | |
assignee: | nobody → James Page (james-page) |
status: | Triaged → In Progress |
goyaml requires CGO support; this is not enabled in the golang package outside of x86 for 1.0 releases; however this should be sorted for 1.1 at which point we can switch to any.