** Description changed: The current juju packaging specifies all for architecture, but juju itself only officially supports 64-bit architectures. We should update - juju, conjure-up, charm, and charm-tools to specify to build on only - supported architectures for all ppa and archive versions. We should also - remove existing builds from xenial and yakkety that are for unsupported - architectures. + juju, to build on only supported architectures for all ppa and archive + versions. We should also remove existing builds from xenial that are for + unsupported architectures. + + [SRU Information] + + [Impact] + This change removes 32-bit builds of juju and replaces it with a debconf message instead. See https://lists.ubuntu.com/archives/ubuntu-release/2016-September/003882.html + + [Verification] + First confirm a supported arch install works without issue. No prompting should occur. + + Then, try the same on a 32-bit machine. All existing juju binaries and + files should be removed, and you should be prompted with the debconf + message about an unsupported client. + + [Regression Potential] + For 32-bit users, this is removing a binary package. However, beta15 package of juju2 isn't supported. For the supported arches, the only regression potential is seeing a needless debconf message.
** No longer affects: juju-core-1 (Ubuntu) ** No longer affects: conjure-up (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1614969 Title: Juju packaging allows builds for unsupported architectures To manage notifications about this bug go to: https://bugs.launchpad.net/juju-release-tools/+bug/1614969/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
