[Bug 1508120] Re: please break out embedded code copies into archive packages
Here's the ppa with the packages: https://launchpad.net/~nskaggs/+archive/ubuntu/juju/+packages And here's the status for each dependency mentioned. http://paste.ubuntu.com/15569917/ -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1508120 Title: please break out embedded code copies into archive packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1508120/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1508120] Re: please break out embedded code copies into archive packages
Jamie, the additional packages are: golang-github-altoros-gosigma golang-github-dustin-go-humanize golang-github-gabriel-samfira-sys golang-github-gosuri-uitable golang-github-joyent-gocommon golang-github-joyent-gomanta golang-github-joyent-gosdc golang-github-joyent-gosign golang-github-mattn-go-runewidth golang-gnuflag-dev golang-gopkg-errgo.v1 golang-gopkg-goose.v1 golang-gopkg-lxc-go-lxc.v2 golang-gopkg-macaroon.v1 golang-gopkg-natefinch-npipe.v2 These are currently packaged in my ppa and should be ready for upload for Y. There are 2 additional that are not targeted. google.golang.org/cloud gopkg.in/macaroon-bakery.v1 have a spiderweb of depends, and I think we would prefer to leave them as embeds, but we can work on it during Y and come to a solution. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1508120 Title: please break out embedded code copies into archive packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1508120/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1545913] Re: [FFe] juju-core 2.0
Adam has built the initial version desired for upload: https://launchpad.net/~adam-stokes/+archive/ubuntu/juju-pkg -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1545913 Title: [FFe] juju-core 2.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1545913/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1564168] [NEW] juju list-credentials --show-secrets does not display passwords
Public bug reported: juju list-credentials --show-secrets does not display password data, unless used with --format yaml. The following commands all fail to show additonal information using --show-secrets juju list-credentials --show-secrets juju list-credentials --format json --show-secrets juju list-credentials --format tabular --show-secrets When used with --format yaml, --show-secrets works. juju list-credentials --format yaml --show-secrets ** Affects: juju-core (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1564168 Title: juju list-credentials --show-secrets does not display passwords To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1564168/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1564165] [NEW] Credentials file displays unhelpful message for syntax errors
Public bug reported: If credentials.yaml contains invalid syntax, the error is ERROR credentials.blarhg.google.credentials: expected string, got map which does not accurately convey 'blarhg' is not valid syntax. ** Affects: juju-core (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1564165 Title: Credentials file displays unhelpful message for syntax errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1564165/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1564163] [NEW] environment name in credentials file is not a tag
Public bug reported: It would be nice to include a tag of the environment name from my credentials file. aws: default-credential: balloons balloons: auth-type: access-key access-key: XXXxxx secret-key: xxx Given those credentials, I expect newly launched instance on aws to be tagged with 'balloons'. ** Affects: juju-core (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1564163 Title: environment name in credentials file is not a tag To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1564163/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1564157] [NEW] juju list-credentials fails to display
Public bug reported: When a cloud is not found in your credentials file, the credentials are not listed. In addition, the credentials error given is confusing, and non-consistent. nskaggs@pixel:~$ juju list-credentials ERROR removing secrets from credentials for cloud maas18: cloud maas18 not found nskaggs@pixel:~$ juju list-credentials ERROR removing secrets from credentials for cloud munna-vmaas: cloud munna-vmaas not found nskaggs@pixel:~$ juju list-credentials ERROR removing secrets from credentials for cloud silcoon-vmaas: cloud silcoon-vmaas not found nskaggs@pixel:~$ juju list-credentials ERROR removing secrets from credentials for cloud jujuqa-stack: cloud jujuqa-stack not found nskaggs@pixel:~$ juju list-credentials ERROR removing secrets from credentials for cloud maas19: cloud maas19 not found nskaggs@pixel:~$ juju list-credentials ERROR removing secrets from credentials for cloud silcoon-vmaas: cloud silcoon-vmaas not found nskaggs@pixel:~$ juju list-credentials ERROR removing secrets from credentials for cloud silcoon-vmaas: cloud silcoon-vmaas not found Juju should still list all credentials in the file, as well as displaying a friendly warning about any clouds it cannot find. ** Affects: juju-core (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1564157 Title: juju list-credentials fails to display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1564157/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1545913] Re: [FFe] juju-core 2.0
** Description changed: - The Juju team is preparing for a 2.0-beta1 release in time for the - xenial feature freeze date (18-Feb), but not all features required for - 2.0 will be ready by that date. We believe we will have a complete and - stable Juju 2.0 by the time of the xenial release, but we need to - request a feature freeze exception for the following features: + The juju team is requesting an FFE for juju-core. Juju2 represents API + changes and new features and bugfixes for juju. We are NOT requesting a + place on any image for xenial. This FFE is intended to cover the + acceptance of the updated juju-core package, as well as the new package + juju-core-1.25, which is a new version of the existing juju-core package + allowing the existing juju1 binary to be installed. - - Juju-GUI in Core - - Removal of LXC from 2.0 codebase - - Model migration - - MAAS 2.0 support - - Keystone 3 support - - Resources (validation of file extension, notification of resource updates available from the charm store) - - Multi-model backup / restore enhancements - - Additional cloud credentials requirements - - Additional MAAS Spaces support + User-Facing Features / Changes + -- + * New Terminology + * Command Name Changes + * New Juju home directory + * Multi-Model Support Active by Default + * New Bootstrap and Cloud Management Experience + * Native Support for Charm Bundles + * Multi Series Charms + * Improved Local Charm Deployment + * LXC Local Provider No Longer Available + * LXD Provider + * LXD Containers + * Microsoft Azure Resource Manager Provider + * Bootstrap Constraints, Series + * Juju Logging Improvements + * Unit Agent Improvements + * API Login with Macaroons + * MAAS Spaces + * Resources + * Juju Status Improvements + * Relation Get and Set Compatibility + * Support for new AWS M4 Instance Types + * Support for win10 and win2016 + + The full list of changes can be found here: https://lists.ubuntu.com/archives/juju/2016-March/006922.html + and in the final release notes. - These features are critical for a final Juju 2.0 release. + Timeline + + We have released 2 alphas, and 3 betas for juju2 so far, in addition 3 alpha builds of 1.26 which became 2.0. All targeted 2.0 features are now implemented, and we anticipate releasing one release candidate before a final stable build. Juju missed uploading any versions of 2.0 to the archive itself, as well as the initial projected date of having beta1 in xenial before feature freeze. However, juju has been released regularly during the development cycle inside the juju ppa. You can see the details on the delivered features and milestones on https://launchpad.net/juju-core/2.0. The final stable build will be ready in time for the xenial release. + + Upgrades + + Users upgrading from trusty will find their juju2 version updated. The current juju-core package will become juju-core1. Users upgrading from wily and trusty will get juju2 as part of the upgrade. Update-alternatives will provide support for toggling /usr/bin/juju between juju1 and juju2 binaries. + + We have tested to ensure the intended behavior occurs for the following + scenarios; + + Trusty + No juju -> install juju on xenial, juju-core is installed. + Juju-core -> juju-core-1.25 and juju-core installed, update-alternatives toggles + + + Wily + No juju -> install juju on xenial, juju-core is installed. + Juju-core -> juju-core-1.25 and juju-core installed, update-alternatives toggles + + Risks + - + Although juju itself is now feature complete for 2.0, the MAAS 2.0 support will require additional work to be fully supported. MAAS 2.0 is currently under development as well, and is an alpha3 at the time of this writing. Juju will need to add support for the final version of MAAS 2.0, and this is a risk of occurring after xenial is released. If so, we expect to release an sru for juju-core soon after xenial releases to provide this support. + + Quality / Testing + - + As this version breaks API with 1.0, testing for features regressions as well as fixing old bugs and avoiding new bugs has been important. The juju team and the greater juju community has been testing 2.0 to ensure it’s stable and ready to support all of the 1.0 workloads in addition to making use of the new 2.0 features. + + In comparison to juju-1.25: + + * Tests improvements including + * MAAS testing improved + * Container networking + * 9 non-voting tests are now voting + * New tests for all 2.0 features + * Powerpc toolchain is vastly improved + * No test regressions! + * S390 builds reliably, is fully tested and is treated the same as other supported architectures + * 114 bugs has been fixed + + Juju practices continuous integration and testing of the juju source + tree. All voting tests must pass for ubuntu before release. For example, + for beta3, you can see all tests are passing on ubuntu. The full details + are
[Bug 1561633] [NEW] help should work properly with alternatives
Public bug reported: When calling help using juju2 directly, it refers to using the commands as 'juju', rather than juju2. The help should be dynamic as well with the alternatives packaging so when juju2 help is called directly, it also specifies the use of juju2. ** Affects: juju-core (Ubuntu) Importance: Undecided Status: New ** Tags: packaging -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1561633 Title: help should work properly with alternatives To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1561633/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1561210] Re: juju-core should depend on python3
** Tags added: packaging -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1561210 Title: juju-core should depend on python3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1561210/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1560315] Re: [needs packaging] juju2 beta is not in xenial
I've added 12 dependencies for the go modules used by juju as depends in in the control file. This is a step back in the proper direction. There are a couple more depends we could add based upon what's in the archive that is currently breaking the build (one of them is lxd). Beyond that, we'll need to start getting packages created for the other dependencies we need. I trust these changes make it more palatable towards entering into universe. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1560315 Title: [needs packaging] juju2 beta is not in xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1560315/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1561210] [NEW] juju-core should depend on python3
Public bug reported: Juju needs to depend solely on python3, not python2. Python2 is targeted for removal from the images, and the quest continues to lower our python2 dependencies. https://blueprints.launchpad.net/ubuntu/+spec/foundations-x-python3-only ** Affects: juju-core (Ubuntu) Importance: Undecided Status: New ** Tags: python3 ** Tags added: python3 ** Summary changed: - juju-core depends on python2 + juju-core should depend on python3 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1561210 Title: juju-core should depend on python3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1561210/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 994192] Re: package lxc 0.7.5-3ubuntu52 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Turns out the kernel I am running does not support bridging. Changing the kernel fixes the issue ** Changed in: lxc (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/994192 Title: package lxc 0.7.5-3ubuntu52 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/994192/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 994192] Re: package lxc 0.7.5-3ubuntu52 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
-- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/994192 Title: package lxc 0.7.5-3ubuntu52 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/994192/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 994192] [NEW] package lxc 0.7.5-3ubuntu52 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: I was attempting to setup a juju enviroment using lxc as a local enviroment. Trying to install lxc failed with this error.. Setting up lxc (0.7.5-3ubuntu52) ... start: Job failed to start invoke-rc.d: initscript lxc-net, action "start" failed. dpkg: error processing lxc (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: lxc E: Sub-process /usr/bin/dpkg returned an error code (1) Removing and re-installing doesn't change anything. I attempted to run the script manually, but it doesn't seem to exist? ls -al /var/dpkg/info/lxc* /var/lib/dpkg/info/lxc.list/var/lib/dpkg/info/lxc.postrm ProblemType: Package DistroRelease: Ubuntu 12.04 Package: lxc 0.7.5-3ubuntu52 Uname: Linux 3.2.7 x86_64 ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 Date: Thu May 3 12:48:53 2012 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) SourcePackage: lxc Title: package lxc 0.7.5-3ubuntu52 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package precise -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/994192 Title: package lxc 0.7.5-3ubuntu52 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/994192/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
