This issue should be corrected now as of 2.1-beta5. There is a juju-2
symlink you can depend on that will point to the latest juju-2 binary on
your system.
** Changed in: juju-core (Ubuntu)
Status: Confirmed => Invalid
** Changed in: juju
Status: Triaged => Invalid
** Changed in:
I can confirm this works on xenial after installing squashfuse.
root@clean-lark:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.1 LTS
Release:16.04
Codename: xenial
root@clean-lark:~# uname -a
Linux clean-lark 4.4.0-63-generic
Yakkety still has 1.0.43.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1630789
Title:
normal users can't run snaps inside of LXD containers
To manage notifications about this bug go to:
I have verified both xenial and yakkety functionality. In particular,
I've been using this version on xenial for some time without realizing
it hadn't yet been verified (I'm always running -proposed).
I'll note the bash completion functionality is the same as the previous
package, and doesn't
** Also affects: juju
Importance: Undecided
Status: New
** Changed in: juju
Milestone: None => 2.1-rc1
** Changed in: juju
Status: New => Triaged
** Changed in: juju
Importance: Undecided => Critical
** Changed in: juju
Assignee: (unassigned) => Menno Smits
** Changed in: phablet-tools
Assignee: Nicholas Skaggs (nskaggs) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1269163
Title:
phablet-click-test-setup should support launch
Hello,
GRUB binary doesn't have the cryptos to do the signs verification unlike
shim, so the chainload process fails under Secure Boot.
As Valmar said, for the OpenSUSE version of GRUB2, Michael Chang came
out with a patch on 2012 that make GRUB rely on shim verification to
chainload other
Has anyone figured out a way around this bug? Haven't been able to
deploy since.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1658844
Title:
most recent version does not install
*** This bug is a duplicate of bug 1565950 ***
https://bugs.launchpad.net/bugs/1565950
All gcry modules should be included, since any user can choose a
different cipher or hash and using a custom grub config file does not
prevent, for example, the boot of a pendrive on a different system,
Public bug reported:
if I try to use the software updater or the terminal to upgrade, I get this
message:
Could not calculate the upgrade
An unresolvable problem occurred while calculating the upgrade.
This can be caused by:
* Upgrading to a pre-release version of Ubuntu
* Running the
I have the same problem as Travis. Never used the screen reader, then
this suddenly spawned four instances and started spouting gibberish.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1496542
Title:
** Description changed:
- Juju 1.25.8 is a stable update containing critical bug fixes, for backup
- restore, charm metrics, and mac os sierra for the 1.25 series.
+ Juju 1.25.8 is a stable update containing critical bug fixes including
+ backup restore, charm metrics, openstack security group
Public bug reported:
Upgrading from 10.04 to 12.04 using PXE boot
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: ubiquity 2.10.16
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
Uname: Linux 3.2.0-23-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.0.1-0ubuntu5
** Branch linked: lp:~juju-qa/ubuntu/xenial/juju/2.0.2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1648894
Title:
[SRU] Juju 2.0.2
To manage notifications about this bug go to:
Public bug reported:
This syncs juju with the upstream releases bringing the latest bugfixes.
[SRU Information]
juju-core has a stable release exception, including for major version updates,
https://wiki.ubuntu.com/JujuUpdates.
[Impact]
A full list of targeted bugs can be seen against the
Public bug reported:
(do humor my lack of full understanding of these packages).
Was having issues sorting with COLLATE "en_US.UTF-8" on ubuntu 16.04,
told it was related to glibc.
On ubuntu 14.04 (with eglibc 2.19) I could sort a file of 2 million
lines of international text (<40chars per
** Branch linked: lp:~juju-qa/ubuntu/trusty/juju/juju-1.25.8
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1646913
Title:
[SRU] Juju 1.25.8
To manage notifications about this bug go to:
** Also affects: juju-core (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1646913
Title:
[SRU] Juju 1.25.8
To manage notifications about this
Public bug reported:
Juju 1.25.8 is a stable update containing critical bug fixes, for backup
restore, charm metrics, and mac os sierra for the 1.25 series.
[SRU Information]
juju-core has a stable release exception, including for major version
updates, https://wiki.ubuntu.com/JujuUpdates.
** Changed in: juju-release-tools
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1631038
Title:
Need /etc/sysctl.d/10-juju.conf
To manage notifications
Just adding a comment to note that indeed on 32-bit arches both the
install and upgrade show the DEBCONF message and remove all associated
binaries.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags removed: verification-needed
** Tags added: v-done-yakkety
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1617440
Title:
[SRU] Juju 2 GA
To manage notifications about this bug go to:
@Nicolas, /usr/lib/sysctl.d/ does override /etc/sysctl.conf. Note, these
settings are already an increase from the default. These are lower
values than in the wiki, but are deemed safe enough to deploy to all
users. You should absolutely bump these values should you wish to run a
more production
Works properly for yakkety. juju.conf installed and values set properly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1631038
Title:
Need /etc/sysctl.d/10-juju.conf
To manage notifications about
** Tags removed: verification-needed
** Tags added: v-done-xenial v-failed-yakkety
** Tags removed: v-failed-yakkety
** Tags added: verification-needed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags removed: verification-done
** Tags added: v-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1617440
Title:
[SRU] Juju 2 GA
To manage notifications about this bug go to:
Installing xenial build, I am no longer prompted on supported
architectures.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Xenial package installed and working as expected.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1617440
Title:
[SRU] Juju 2 GA
** Changed in: juju-core (Ubuntu Xenial)
Status: New => Fix Committed
** Changed in: juju-core (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** 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.
Updating to say this works properly in xenial, but not in yakkety.
Yakkety is missing the sysctl file; it's not installed. This needs to be
corrected in the debian/rules.
** Tags removed: verification-needed
** Tags added: verification-done verification-failed
--
You received this bug
I am now able to bootstrap using LXD 2.0.5.
juju bootstrap lxd lxd
Creating Juju controller "lxd" on lxd/localhost
Looking for packaged Juju agent version 2.0.0 for amd64
To configure your system to better support LXD containers, please see:
As per http://autopkgtest.ubuntu.com/packages/j/juju-core, the test was
skipped and the autopkgtest suite succeeded.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Diff shows LXD is added, and we can see from yakkety and zesty the tests
are running on new LXD uploads.
https://launchpadlibrarian.net/290947340/juju-
core_2.0~beta15-0ubuntu2.16.04.1_2.0.0-0ubuntu0.16.04.1.diff.gz
** Tags removed: verification-needed
** Tags added: verification-done
--
You
** Description changed:
Juju errors with: invalid config: lxd version 2.1, juju needs at least
2.0.0
As seen here:
http://reports.vapour.ws/releases/issue/57b5c506749a567eabd11a4a
Full log not given here because it contains certs. See above link for
full logs.
+
+ [SRU
** Description changed:
Juju's autopkgtests don't execute when a new version of LXD is uploaded.
This means a breaking change uploaded into LXD isn't caught before LXD
lands.
This is because juju 2.0 doesn't depend on LXD directly, but instead
lists it as a recommends. The juju-1
** Description changed:
In order to increase the number of containers that can be used with the
lxd provider we need an /etc/sysctl.d/10-juju.conf file setting:
- fs.inotify.max_user_watches = 524288
- fs.inotify.max_user_instances = 256
+ fs.inotify.max_user_watches = 524288
+
** Description changed:
Since --upload-tools is now no longer needed, juju needs to fallback to
using bundled jujud in the case where no matching agents are found in
streams. For example,
6:38:07 INFO juju.environs.manual init.go:120 series: zakkety,
characteristics: arch=amd64
** Changed in: juju-core (Ubuntu Xenial)
Status: Triaged => In Progress
** Changed in: juju-core (Ubuntu Xenial)
Assignee: (unassigned) => Nicholas Skaggs (nskaggs)
** Changed in: juju-core (Ubuntu)
Assignee: (unassigned) => Nicholas Skaggs (nskaggs)
--
You received
** Changed in: juju-core (Ubuntu Yakkety)
Status: In Progress => Fix Released
** Changed in: juju-core (Ubuntu Yakkety)
Assignee: (unassigned) => Nicholas Skaggs (nskaggs)
** Changed in: juju-core (Ubuntu Xenial)
Assignee: (unassigned) => Nicholas Skaggs (nskaggs)
** Changed in: juju-core (Ubuntu Zesty)
Assignee: (unassigned) => Nicholas Skaggs (nskaggs)
** Changed in: juju-core (Ubuntu Yakkety)
Assignee: (unassigned) => Nicholas Skaggs (nskaggs)
** Changed in: juju-core (Ubuntu Xenial)
Assignee: (unassigned) => Nicholas Skaggs
** Also affects: juju-core (Ubuntu)
Importance: Undecided
Status: New
** Changed in: juju-core (Ubuntu)
Status: New => In Progress
** Changed in: juju-core (Ubuntu)
Assignee: (unassigned) => Nicholas Skaggs (nskaggs)
--
You received this bug notification becau
Well, unfortunatly, upgrading to 1.8 disables both the bluetooth module
and touchscreen on my device(Asus T300 chi), leaving me with no input
options. I suppose that's a separate problem, but it's rather hard to
file. I'll try to find my adapter, borrow a USB keyboard from someone
and file it.
** Summary changed:
- [SRU] Juju 2-rc3 for Xenial
+ [SRU] Juju 2 GA
** Description changed:
- Juju 2.0 is not quite final, as per the risks and timeline outlined in
- the FFe for Xenial, bug 1545913. As such, we intend to release SRU's
- post-xenial release. This updates juju to an upgradeable
Public bug reported:
On startup
ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: libheimbase1-heimdal:amd64 1.7~git20160703+dfsg-1
Uname: Linux 4.8.1-040801-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
AptOrdering:
libheimbase1-heimdal:amd64: Install
NULL: ConfigurePending
NULL:
% apt-cache policy libgbm1-lts-vivid
N: Unable to locate package libgbm1-lts-vivid
2016-10-12 23:51 GMT+02:00 Timo Aaltonen :
> apt-cache policy
> libgbm1-lts-vivid
>
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Well, it's certainly a problem which appeared after I did the upgrade.
There were no issues before this point.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1632593
Title:
Xorg does not utilize the
** Description changed:
Juju 2.0 is not quite final, as per the risks and timeline outlined in
the FFe for Xenial, bug 1545913. As such, we intend to release SRU's
- post-xenial release. This updates juju to the lastest 2.0 milestone
- version.
+ post-xenial release. This updates juju to an
** Summary changed:
- [SRU] Juju 2 beta 17 for Xenial
+ [SRU] Juju 2-rc3 for Xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1617440
Title:
[SRU] Juju 2-rc3 for Xenial
To manage
Can someone please change this to be about the package containing the
do-release-upgrade command?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1632593
Title:
Xorg does not utilize the 3D graphics
Public bug reported:
After using my system for a period of time, usually less than an hour,
the screen starts to corrupt. It will vary in intensity, until the
system either crashes, or everything goes back to normal for a while.
When the system does crash, not even the sysrq-key works.
** Attachment added: "Fotos.zip"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1632740/+attachment/4759954/+files/Fotos.zip
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1632740
Title:
I reinstalled the package, no dice. I then looked around for it, and
found that it had been renamed to old.libgbm1.so, along with the file it
linked to. I renamed both, removing the "old.", and now 3D works. It's
definitely still a bug though.
--
You received this bug notification because you
The package is installed, but the file is not there.
On 12 Oct 2016 13:50, "Timo Aaltonen" wrote:
> your logfile disagrees
>
> [ 8.117] (EE) Failed to load /usr/lib/xorg/modules/libglamoregl.so:
> libgbm.so.1: cannot open shared object file: No such file or directory
>
No, I have not. Libgbm1 is installed, as well as all other packages
included in the ubuntu-desktop meta-package.
** Changed in: xorg (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Everything worked fine in 16.04. I then upgraded to 16.10 a bit early to
see if I could find any bugs, and immediately noticed that Unity was
running in low-graphics mode, and YouTube chugs noticably.
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: xorg 1:7.7+13ubuntu4
1.0.41 was backported which has the fix. This should be released.
** Changed in: snap-confine (Ubuntu Xenial)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Yes, this problem most definitely occurs with the Yakkety proposed
kernel, I tried using the most recent build of 16.10 that comes with
4.8, and the graphical problems persist.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
All kernels after 4.7.4 have this exact same issue with Broadwell
integrated graphics, including the official 4.8 release and the previous
rc builds.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: juju-release-tools
Status: In Progress => Fix Released
** Changed in: juju-core (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
The current ubuntu (xenial / yakkety) packages are missing needed
updates. Specifically, juju needs golang.org/x/crypto/acme/autocert.
I can note that sid contains these updated packages, but yakkety is
still missing them. See https://packages.debian.org/sid/all/golang-
** Description changed:
The juju team is requesting an FFE for juju. Juju-2 represents API
changes and new features and bugfixes for juju. This FFE is intended to
cover the acceptance of the updated juju package.
Timeline
- We have released 16 betas of juju-2 so far over the
Given juju2 is now RC and has promises of being upgradeable, I think
this is safe to move forward on. For folks who have to have it, it will
be in the stable juju ppa.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Since my last comment, I have been trying the modesetting driver
periodically and it seems that a fairly recent update has fixed the
screen wrapping I was seeing on my Lemur. My operating system is still
Xubuntu 16.04. I have been using the modesetting driver since last night
and I have seen no
** Description changed:
I would like to report a severe graphics regression, involving frequent
rainbow-glitching and flickering on a x64 computer with Intel Broadwell
5500U processor w/ integrated graphics. This issue was not present on
kernel v4.7.4, which I will continue to use. Due to
I was unable to use apport-collect but I believe the information I have
provided is sufficient. I am running Ubuntu 16.04.1 LTS with kernel
v4.7.5-generic on a x64 HP Spectre x360 with Broadwell GT2 5500
integrated graphics.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
Public bug reported:
I would like to report a severe graphics regression, involving frequent
rainbow-glitching and flickering on a x64 computer with Intel Broadwell
5500U processor w/ integrated graphics. This issue was not present on
kernel v4.7.4, which I will continue to use. Due to
** Changed in: juju-core (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1578550
Title:
ftbfs on yakkety
To manage notifications about this bug go to:
@mwhudson, I utilized the tool locally and everything seemed fine. For
now, bug 1564500 prevents a full CI run until it lands in xenial proper.
I think we should discuss a set of autopkgtests to help bridge the gap
in the interim.
That said, given 3.2.9 is in yakkety we've not seen any issues in
Looks good.
/usr/lib/juju/mongo3.2/bin/mongo
MongoDB shell version: 3.2.9
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1605976
** Changed in: juju-core (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1484132
Title:
[FFe] juju-core 1.25
To manage notifications about this bug go to:
** No longer affects: charm-tools (Ubuntu)
** No longer affects: charm (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
Martin, the edge channel in the snap store has replaced the daily ppa.
This ppa is where we release betas:
https://launchpad.net/~juju/+archive/ubuntu/devel
Now as to landing this fix, we've pushed packages to proposed as you've
seen, but encountered various failures with beta16 and now beta17.
Rather than excluding tmpfs, just exclude /run/lxcfs/controllers. This
is the check_all_disks command I'm now using in my /etc/nagios-
plugins/config/disk.cfg:
# 'check_all_disks' command definition
define command{
command_namecheck_all_disks
command_line
** Summary changed:
- [SRU] Juju 2 beta 16 for Xenial
+ [SRU] Juju 2 beta 17 for Xenial
** Description changed:
Juju 2.0 is not quite final, as per the risks and timeline outlined in
the FFe for Xenial, bug 1545913. As such, we intend to release SRU's
post-xenial release. This updates
*** This bug is a security vulnerability ***
Public security bug reported:
Many VPN providers will give a Certificate Revocation List crl.pem file in
their OpenVPN packages. The CRL list is becoming increasingly important after
the Heartbleed bug was exposed, leaving many servers vulnerable to
Public bug reported:
Juju 2.0 is not quite final, as per the risks and timeline outlined in
the FFe for Xenial, bug 1545913. As such, we intend to release SRU's
post-xenial release. This updates juju to the lastest 2.0 milestone
version.
[SRU Information]
juju-core has a stable release
** Changed in: juju-release-tools
Status: Triaged => In Progress
** Changed in: juju-core (Ubuntu)
Status: New => In Progress
** Changed in: juju-release-tools
Assignee: (unassigned) => Nicholas Skaggs (nskaggs)
** Changed in: juju-core (Ubuntu)
Assignee: (u
Public bug reported:
The juju team is requesting an FFE for juju. Juju-2 represents API
changes and new features and bugfixes for juju. This FFE is intended to
cover the acceptance of the updated juju package.
Timeline
We have released 16 betas of juju-2 so far over the xenial and now
@mwhudson, once mongo3.2.8 is in the proposed queue for xenial, we can
ensure a CI test run or two before landing. Let us know.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1605976
Title:
[2.0]
** Changed in: juju-mongodb3.2 (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1596095
Title:
[needs packaging] 3.2.4-0ubuntu4 available in xenial or
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1612713
Title:
Please merge debian version of golang-juju-loggo-dev
To manage
Tested 2.0~beta15-0ubuntu2.16.04.1. Works as expected.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1613718
Title:
[SRU] Juju
** Changed in: juju-release-tools
Status: New => Triaged
** Changed in: juju-release-tools
Importance: Undecided => High
--
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
** Changed in: juju-release-tools
Status: New => Triaged
** Changed in: juju-release-tools
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1614724
Title:
Juju
I cannot reproduce this myself, on our CI servers, nor could lazypower
who I asked to try on his machine.
See an upgrade: http://paste.ubuntu.com/23070808/.
My only thought is perhaps you manually mucked with /usr/bin/juju and
somehow that's causing you issues now.
** Changed in:
** Also affects: conjure-up
Importance: Undecided
Status: New
** Also affects: charm-tools
Importance: Undecided
Status: New
** Also affects: charm (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: conjure-up
** No longer affects: charm-tools
**
** Also affects: juju-core-1 (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: juju-core-1 (Ubuntu)
** Also affects: juju-core (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: juju-core
--
You received this bug notification because you are a
$ dpkg-divert --list | grep juju
diversion of /usr/bin/juju to /usr/bin/juju.default by juju-1-default
** Attachment added: "dpkg-divert --list | grep juju"
https://bugs.launchpad.net/juju-release-tools/+bug/1614959/+attachment/4724019/+files/divert
--
You received this bug notification
Expected output should look something like this:
$ ls -al /usr/bin/juju*
lrwxrwxrwx 1 root root 6 Aug 16 16:04 /usr/bin/juju -> juju-1
lrwxrwxrwx 1 root root 9 Aug 16 16:04 /usr/bin/juju-1 -> juju-1.25
-rwxr-xr-x 1 root root 68 Aug 16 16:04 /usr/bin/juju-1.25
-rwxr-xr-x 1 root root 67 Jul 28
** Attachment added: "ls -al /usr/bin/juju*"
https://bugs.launchpad.net/ubuntu/+source/juju-core-1/+bug/1614959/+attachment/4723996/+files/ls%20usr%20binjuju
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "juju-xenial-upgrade-log"
https://bugs.launchpad.net/ubuntu/+source/juju-core-1/+bug/1614959/+attachment/4723998/+files/juju-xenial-upgrade-log
** Also affects: juju-release-tools
Importance: Undecided
Status: New
--
You received this bug notification because
Public bug reported:
After upgrading from 1.25.5 on xenial to 1.25.6-0ubuntu1.16.04.1,
/usr/bin/juju has disappeared. Attached are the upgrade logs, as well as
an ls of /usr/bin/juju* after the upgrade showing the diversion, but
missing /usr/bin/juju.
** Affects: juju-release-tools
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1611855
Title:
[SRU] Juju 1.25.6
To manage notifications about this bug go to:
Tested on xenial. Deploys, tearsdown, installs and removes cleanly, and
works with juju-1-default as expected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1611855
Title:
[SRU] Juju 1.25.6
To
** Description changed:
The current package in ubuntu is old and the maintainer is no longer
able to maintain the package. I'd like to request we replace this
package with the debian version which is newer and has a maintainer.
+
+ NOTE: juju-core in xenial would like to depend on this
** Changed in: juju-core-1 (Ubuntu)
Status: Incomplete => Fix Committed
** Changed in: juju-core (Ubuntu)
Status: Invalid => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@mwhudson, a new version of juju-core-1, 1.25.6, is being uploaded into
yakkety. I agree with the package removal, but given the extended
timeline for juju 2.0, it's possible yakkety retains juju-core-1. Let's
revisit this before FF. I definitely agree with not including it in Z.
--
You received
Public bug reported:
Juju 2.0 is not quite final, as per the risks and timeline outlined in
the FFe for Xenial, bug 1545913. As such, we intend to release SRU's
post-xenial release. This updates juju to the lastest 2.0 milestone
version.
[SRU Information]
juju-core has a stable release
I've restored the debhelper script to version 7 as released. The
juju-1-default.links file was present in my version, heh, but not added
and thus not in the repository. This too has been corrected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
501 - 600 of 2587 matches
Mail list logo