[Bug 1381671] Re: reboot tests fail to build on gccgo
** Changed in: gccgo-go (Ubuntu Trusty) Status: New => Opinion ** Changed in: gccgo-go (Ubuntu Trusty) Status: Opinion => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1381671 Title: reboot tests fail to build on gccgo To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1381671/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 920525] Re: bzr crashed with TypeError in __new__(): object of type 'NoneType' has no len()
*** This bug is a duplicate of bug 914363 *** https://bugs.launchpad.net/bugs/914363 ** Changed in: bzr-gtk Assignee: Curtis Hovey (sinzui) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/920525 Title: bzr crashed with TypeError in __new__(): object of type 'NoneType' has no len() To manage notifications about this bug go to: https://bugs.launchpad.net/bzr-gtk/+bug/920525/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 457784] Re: When bugs reporting tries to report bug in Kubuntu, using Konqueror, "I am affected by this bug" picker does not works
** Changed in: launchpad Assignee: Curtis Hovey (sinzui) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/457784 Title: When bugs reporting tries to report bug in Kubuntu, using Konqueror, "I am affected by this bug" picker does not works To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/457784/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1044991] Re: IndexError accessing deprecated GtkStyle
** Changed in: bzr-gtk 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/1044991 Title: IndexError accessing deprecated GtkStyle To manage notifications about this bug go to: https://bugs.launchpad.net/bzr-gtk/+bug/1044991/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 182271] Re: with kde4 plasma asking for root password instead of user's
** Changed in: ubuntu Assignee: Registry Administrators (registry) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/182271 Title: with kde4 plasma asking for root password instead of user's To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/182271/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 253279] Re: kwin (KDE4) consumes 99% of CPU
** Changed in: kdebase-kde4 (Ubuntu) Assignee: Registry Administrators (registry) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/253279 Title: kwin (KDE4) consumes 99% of CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdebase-kde4/+bug/253279/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 176681] Re: KDE4 slightly breaks KDE3 mime types
** Changed in: kdebase-kde4 (Ubuntu) Assignee: Registry Administrators (registry) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/176681 Title: KDE4 slightly breaks KDE3 mime types To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdebase-kde4/+bug/176681/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 151141] Re: When switching from nv to nvidia driver lose screen resolution; nvidia doesn't use EDID freq. data even though that data is correct
** Changed in: jockey Assignee: Registry Administrators (registry) => (unassigned) ** Changed in: jockey (Ubuntu) Assignee: Registry Administrators (registry) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/151141 Title: When switching from nv to nvidia driver lose screen resolution; nvidia doesn't use EDID freq. data even though that data is correct To manage notifications about this bug go to: https://bugs.launchpad.net/jockey/+bug/151141/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1475260] Re: instances cannot resolve their own hostname
** Changed in: juju Milestone: 2.2-beta2 => 2.2-beta3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1475260 Title: instances cannot resolve their own hostname To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1475260/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1602192] Re: when starting many LXD containers, they start failing to boot with "Too many open files"
** Changed in: juju Milestone: 2.2-beta2 => 2.2-beta3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1602192 Title: when starting many LXD containers, they start failing to boot with "Too many open files" To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1602192/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1475260] Re: instances cannot resolve their own hostname
** Changed in: juju Milestone: 2.2-beta1 => 2.2-beta2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1475260 Title: instances cannot resolve their own hostname To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1475260/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1602192] Re: when starting many LXD containers, they start failing to boot with "Too many open files"
** Changed in: juju Milestone: 2.2-beta1 => 2.2-beta2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1602192 Title: when starting many LXD containers, they start failing to boot with "Too many open files" To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1602192/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1665160] Re: MachineSuite.TestMachineWorkers timed out waiting for workers zesty because dbus is in interactive mode
Is the unit test messing with the services on the host system? I hope not. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1665160 Title: MachineSuite.TestMachineWorkers timed out waiting for workers zesty because dbus is in interactive mode To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1665160/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1665160] Re: MachineSuite.TestMachineWorkers timed out waiting for workers zesty because dbus is in interactive mode
** Changed in: juju Status: Incomplete => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1665160 Title: MachineSuite.TestMachineWorkers timed out waiting for workers zesty because dbus is in interactive mode To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1665160/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1665160] Re: MachineSuite.TestMachineWorkers timed out waiting for workers zesty
** Also affects: dbus (Ubuntu) Importance: Undecided Status: New ** Summary changed: - MachineSuite.TestMachineWorkers timed out waiting for workers zesty + MachineSuite.TestMachineWorkers timed out waiting for workers zesty because dbus is in interactive mode -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1665160 Title: MachineSuite.TestMachineWorkers timed out waiting for workers zesty because dbus is in interactive mode To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1665160/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1613864] Re: Missing "juju-2"/"juju2" command.
** 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/1613864 Title: Missing "juju-2"/"juju2" command. To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1613864/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1543660] Re: juju needs to fix the yaml parser
** Changed in: juju 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/1543660 Title: juju needs to fix the yaml parser To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1543660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1536525] Re: juju-local: Don't depend on rsyslog
** Changed in: juju-core/1.25 Milestone: 1.25.10 => None -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1536525 Title: juju-local: Don't depend on rsyslog To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1536525/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1648894] Re: [SRU] Juju 2.0.2
I have prepared a git branch to place 2.0.2 into xenial https://code.launchpad.net/~juju-qa/ubuntu/+source/juju-core/+git/juju-core/+ref/xenial-2.0.2 This branch imported juju 2.0.2 and updated d/copyright and d/changelog. Note that I see a warning that there are no translations for the debconf. This is true and one day we might have them. $ lintian -iIE --pedantic juju-core_2.0.2-0ubuntu0.16.04.1.dsc && echo "Lintian OK" I: juju-core source: no-complete-debconf-translation ** Patch added: "debdiff of juju-core_2.0.0-0ubuntu0.16.04.2.dsc juju-core to_2.0.2-0ubuntu0.16.04.1.dsc" https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1648894/+attachment/4792075/+files/zesty-juju-core-2.0.2.diff ** Branch unlinked: 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: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1648894/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1648894] Re: [SRU] Juju 2.0.2
I have prepared a git branch to place 2.0.2 into yakkety https://code.launchpad.net/~juju-qa/ubuntu/+source/juju-core/+git/juju-core/+ref/yakkety-2.0.2 This branch imported juju 2.0.2 and updated d/copyright and d/changelog. ** Patch added: "debdiff of juju-core_2.0.0-0ubuntu0.16.10.3.dsc juju-core_2.0.2-0ubuntu0.16.10.1.dsc" https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1648894/+attachment/4792060/+files/yakkety-juju-core-2.0.2.diff -- 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: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1648894/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1648894] Re: [SRU] Juju 2.0.2
I have prepared a git branch to place 2.0.2 into zesty https://code.launchpad.net/~juju-qa/ubuntu/+source/juju-core/+git/juju-core/+ref/zesty-2.0.2 This branch imported juju 2.0.2 and updated d/copyright and d/changelog. I had some misadventure with gbp import-orig because the ubuntu repo didn't provide master or upstream branches. I forced the selection of upstream's changes when merging. git merge -s recursive -X theirs upstream/2.0.2 ** Patch added: "debdiff juju-core_2.0.0-0ubuntu2.dsc juju-core_2.0.2-0ubuntu1.dsc" https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1648894/+attachment/4792027/+files/juju-core-2.0.2.diff -- 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: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1648894/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1536525] Re: juju-local: Don't depend on rsyslog
** Changed in: juju-core/1.25 Milestone: 1.25.9 => 1.25.10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1536525 Title: juju-local: Don't depend on rsyslog To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1536525/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1647299] Re: maas container networking broken: Internet connection for 0/lxd/1 failed
The fixed lxd packages were delivered and tested good. ** Changed in: juju Status: Triaged => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1647299 Title: maas container networking broken: Internet connection for 0/lxd/1 failed To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1647299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1647299] Re: maas container networking broken: Internet connection for 0/lxd/1 failed
** No longer affects: juju-ci-tools -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1647299 Title: maas container networking broken: Internet connection for 0/lxd/1 failed To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1647299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1647299] Re: maas container networking broken: Internet connection for 0/lxd/1 failed
We can see the lxd package got an update to 2.0.8-0ubuntu1 on 2016-12-02/03 and
it has bug 1647312 reported against it about containers do not comeback after a
reboot. The failing containers were fine when they were started. The container
was rebooted and the replay of the operational tests failed:
INFO Reboot complete and all hosts ready for retest.
INFO Assessing internet connection for 0/lxd/1
ERROR Command '('juju', '--show-log', 'ssh', '-m',
'functional-container-networking-maas-2-1:functional-container-networking-maas-2-1',
'--proxy', '0/lxd/1', 'ip route show')' returned non-zero exit status 1
The failures had server_version":"2.0.8" all the successes are
server_version":"2.0.5"
** Also affects: lxd (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/1647299
Title:
maas container networking broken: Internet connection for 0/lxd/1
failed
To manage notifications about this bug go to:
https://bugs.launchpad.net/juju/+bug/1647299/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1640079] Re: LXDs doesn't start after a reboot
** Changed in: juju Milestone: None => 2.1-rc1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1640079 Title: LXDs doesn't start after a reboot To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1640079/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1640079] Re: LXDs doesn't start after a reboot
** Changed in: juju Milestone: 2.1-beta2 => None -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1640079 Title: LXDs doesn't start after a reboot To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1640079/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1640079] Re: LXDs doesn't start after a reboot
** Changed in: juju Milestone: 2.1-beta1 => 2.1-beta2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1640079 Title: LXDs doesn't start after a reboot To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1640079/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1536525] Re: juju-local: Don't depend on rsyslog
** Changed in: juju-core/1.25 Milestone: 1.25.8 => 1.25.9 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1536525 Title: juju-local: Don't depend on rsyslog To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1536525/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1604988] Re: Inconsistent licence in github.com/juju/utils/series
** Changed in: juju-core/1.25 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/1604988 Title: Inconsistent licence in github.com/juju/utils/series To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1604988/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1612645] Re: New EC2 region in India (ap-south-1 - Mumbai)
** Changed in: juju-core/1.25 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/1612645 Title: New EC2 region in India (ap-south-1 - Mumbai) To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1612645/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1564168] Re: juju list-credentials --show-secrets does not display passwords
** Changed in: juju Milestone: 2.0.1 => None -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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/juju/+bug/1564168/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1570651] Re: Manpages for juju aliases drop version
** Changed in: juju Milestone: 2.0.1 => None -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1570651 Title: Manpages for juju aliases drop version To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1570651/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1475260] Re: instances cannot resolve their own hostname
** Changed in: juju Milestone: 2.0.1 => None -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1475260 Title: instances cannot resolve their own hostname To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1475260/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1616949] Re: guest on bridge becomes inaccessible
** Tags added: jujuqa -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1616949 Title: guest on bridge becomes inaccessible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1616949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1635639] Re: Seccomp error with 2.0.5-0ubuntu1~ubuntu16.04.1 on s390x
** Changed in: juju-ci-tools Status: In Progress => 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/1635639 Title: Seccomp error with 2.0.5-0ubuntu1~ubuntu16.04.1 on s390x To manage notifications about this bug go to: https://bugs.launchpad.net/juju-ci-tools/+bug/1635639/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1635639] Re: Seccomp error with 2.0.5-0ubuntu1~ubuntu16.04.1 on s390x
** Changed in: juju-ci-tools Status: Fix Committed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1635639 Title: Seccomp error with 2.0.5-0ubuntu1~ubuntu16.04.1 on s390x To manage notifications about this bug go to: https://bugs.launchpad.net/juju-ci-tools/+bug/1635639/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1635639] Re: Seccomp error with 2.0.5-0ubuntu1~ubuntu16.04.1 on s390x
Current and new lxd containers are still broken. We see errors like this lxc start xenial-manual-a xenial-manual-b xenial-manual-c error: Error calling 'lxd forkstart xenial-manual-a /var/lib/lxd/containers /var/log/lxd/xenial-manual-a/lxc.conf': err='exit status 1' lxc 20161021035819.243 ERROR lxc_seccomp - seccomp.c:get_new_ctx:224 - Seccomp error -17 (File exists) adding arch: 15 lxc 20161021035819.243 ERROR lxc_start - start.c:lxc_init:430 - failed loading seccomp policy lxc 20161021035819.243 ERROR lxc_start - start.c:__lxc_start:1313 - failed to initialize the container ** Description changed: The s390x host used to Juju testing spontaneously broke today. The disk filled up, we restarted so that we could remove unused kernels. We discovered that lxc1 cannot create containers any more. $ sudo lxc-create -t ubuntu-cloud -n curtis -- -r xenial -a s390x $ sudo lxc-start -o lxc.log -n curtis lxc-start: tools/lxc_start.c: main: 344 The container failed to start. lxc-start: tools/lxc_start.c: main: 346 To get more details, run the container in foreground mode. lxc-start: tools/lxc_start.c: main: 348 Additional information can be obtained by setting the --logfile and --logpriority options. - $ cat lxc.log - lxc-start 20161020121833.069 ERRORlxc_seccomp - seccomp.c:get_new_ctx:224 - Seccomp error -17 (File exists) adding arch: 15 - lxc-start 20161020121833.069 ERRORlxc_start - start.c:lxc_init:430 - failed loading seccomp policy - lxc-start 20161020121833.069 ERRORlxc_start - start.c:__lxc_start:1313 - failed to initialize the container - lxc-start 20161020121838.075 ERRORlxc_start_ui - tools/lxc_start.c:main:344 - The container failed to start. - lxc-start 20161020121838.075 ERRORlxc_start_ui - tools/lxc_start.c:main:346 - To get more details, run the container in foreground mode. - lxc-start 20161020121838.075 ERRORlxc_start_ui - tools/lxc_start.c:main:348 - Additional information can be obtained by setting the --logfile and --logpriority options. - + $ cat lxc.log + lxc-start 20161020121833.069 ERRORlxc_seccomp - seccomp.c:get_new_ctx:224 - Seccomp error -17 (File exists) adding arch: 15 + lxc-start 20161020121833.069 ERRORlxc_start - start.c:lxc_init:430 - failed loading seccomp policy + lxc-start 20161020121833.069 ERRORlxc_start - start.c:__lxc_start:1313 - failed to initialize the container + lxc-start 20161020121838.075 ERRORlxc_start_ui - tools/lxc_start.c:main:344 - The container failed to start. + lxc-start 20161020121838.075 ERRORlxc_start_ui - tools/lxc_start.c:main:346 - To get more details, run the container in foreground mode. + lxc-start 20161020121838.075 ERRORlxc_start_ui - tools/lxc_start.c:main:348 - Additional information can be obtained by setting the --logfile and --logpriority options. # sinzui: checking when s390x seccomp support was added to the - # kernel, to see if it's just a missing config in our kernel that'd fix that - # cleanly or if we'd need it backported to 4.4 which would be a bit more + # kernel, to see if it's just a missing config in our kernel that'd fix that + # cleanly or if we'd need it backported to 4.4 which would be a bit more # annoying # sinzui: config-4.4.0-45-generic is what you're running right? # stgraber uname-a says 4.4.0-45-generic # stgraber> sinzui: you can workaround it by putting a file # with lxc.seccomp= # in /usr/share/lxc/config/common.conf.d/, that should get you going again - WORK AROUND + WORK AROUND for LXC 1 # on the s390x-slave sudo vim /usr/share/lxc/config/common.conf.d/10-secomp-hack.conf $ cat /usr/share/lxc/config/common.conf.d/10-secomp-hack.conf # Advised to stgraber to add this file after seeing lxc-start fail with # lxc-start 20161020121833.069 ERRORlxc_seccomp - seccomp. lxc.seccomp= -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1635639 Title: Seccomp error with 2.0.5-0ubuntu1~ubuntu16.04.1 on s390x To manage notifications about this bug go to: https://bugs.launchpad.net/juju-ci-tools/+bug/1635639/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1635639] [NEW] Seccomp error with 2.0.5-0ubuntu1~ubuntu16.04.1 on s390x
Public bug reported: The s390x host used to Juju testing spontaneously broke today. The disk filled up, we restarted so that we could remove unused kernels. We discovered that lxc1 cannot create containers any more. $ sudo lxc-create -t ubuntu-cloud -n curtis -- -r xenial -a s390x $ sudo lxc-start -o lxc.log -n curtis lxc-start: tools/lxc_start.c: main: 344 The container failed to start. lxc-start: tools/lxc_start.c: main: 346 To get more details, run the container in foreground mode. lxc-start: tools/lxc_start.c: main: 348 Additional information can be obtained by setting the --logfile and --logpriority options. $ cat lxc.log lxc-start 20161020121833.069 ERRORlxc_seccomp - seccomp.c:get_new_ctx:224 - Seccomp error -17 (File exists) adding arch: 15 lxc-start 20161020121833.069 ERRORlxc_start - start.c:lxc_init:430 - failed loading seccomp policy lxc-start 20161020121833.069 ERRORlxc_start - start.c:__lxc_start:1313 - failed to initialize the container lxc-start 20161020121838.075 ERRORlxc_start_ui - tools/lxc_start.c:main:344 - The container failed to start. lxc-start 20161020121838.075 ERRORlxc_start_ui - tools/lxc_start.c:main:346 - To get more details, run the container in foreground mode. lxc-start 20161020121838.075 ERRORlxc_start_ui - tools/lxc_start.c:main:348 - Additional information can be obtained by setting the --logfile and --logpriority options. # sinzui: checking when s390x seccomp support was added to the # kernel, to see if it's just a missing config in our kernel that'd fix that # cleanly or if we'd need it backported to 4.4 which would be a bit more # annoying # sinzui: config-4.4.0-45-generic is what you're running right? # stgraber uname-a says 4.4.0-45-generic # stgraber> sinzui: you can workaround it by putting a file # with lxc.seccomp= # in /usr/share/lxc/config/common.conf.d/, that should get you going again WORK AROUND # on the s390x-slave sudo vim /usr/share/lxc/config/common.conf.d/10-secomp-hack.conf $ cat /usr/share/lxc/config/common.conf.d/10-secomp-hack.conf # Advised to stgraber to add this file after seeing lxc-start fail with # lxc-start 20161020121833.069 ERRORlxc_seccomp - seccomp. lxc.seccomp= ** Affects: juju-ci-tools Importance: Critical Assignee: Curtis Hovey (sinzui) Status: Fix Committed ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Tags: jujuqa lxd regression s390x ** Also affects: lxc Importance: Undecided Status: New ** Project changed: lxc => juju-ci-tools ** Changed in: juju-ci-tools Status: New => Fix Committed ** Changed in: juju-ci-tools Importance: Undecided => Critical ** Changed in: juju-ci-tools Assignee: (unassigned) => Curtis Hovey (sinzui) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1635639 Title: Seccomp error with 2.0.5-0ubuntu1~ubuntu16.04.1 on s390x To manage notifications about this bug go to: https://bugs.launchpad.net/juju-ci-tools/+bug/1635639/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1564157] Re: juju list-credentials fails to display
** Changed in: juju 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/1564157 Title: juju list-credentials fails to display To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1564157/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1475260] Re: instances cannot resolve their own hostname
** Changed in: juju Milestone: 2.0-rc3 => 2.0.0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1475260 Title: instances cannot resolve their own hostname To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1475260/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1564157] Re: juju list-credentials fails to display
** Changed in: juju Milestone: 2.0-rc3 => 2.0.0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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/juju/+bug/1564157/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1605976] Re: [2.0] bump mongod to 3.2.9
** Changed in: juju 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/1605976 Title: [2.0] bump mongod to 3.2.9 To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1605976/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1612645] Re: New EC2 region in India (ap-south-1 - Mumbai)
** Changed in: juju 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/1612645 Title: New EC2 region in India (ap-south-1 - Mumbai) To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1612645/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1564168] Re: juju list-credentials --show-secrets does not display passwords
** Changed in: juju Milestone: 2.0.0 => 2.0.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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/juju/+bug/1564168/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1570651] Re: Manpages for juju aliases drop version
** Changed in: juju Milestone: 2.0.0 => 2.0.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1570651 Title: Manpages for juju aliases drop version To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1570651/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1475260] Re: instances cannot resolve their own hostname
** Changed in: juju Milestone: 2.0-rc2 => None -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1475260 Title: instances cannot resolve their own hostname To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1475260/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1614969] Re: Juju packaging allows builds for unsupported architectures
This is fixed in he base juju-core2 branch. It only builds 64-bit versions. ** Changed in: juju-release-tools Assignee: (unassigned) => Curtis Hovey (sinzui) ** Changed in: juju-release-tools 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/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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1475260] Re: instances cannot resolve their own hostname
** Changed in: juju Milestone: 2.0-beta18 => 2.0-beta19 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1475260 Title: instances cannot resolve their own hostname To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1475260/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1604988] Re: Inconsistent licence in github.com/juju/utils/series
** Changed in: juju 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/1604988 Title: Inconsistent licence in github.com/juju/utils/series To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1604988/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1317896] Re: juju-restore requires mongodb-clients
This is essentially fixed by juju-mongodb3.2 and juju-mongo-tools3.2. The client and the tools are installed on the controller. ** Changed in: juju-core 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/1317896 Title: juju-restore requires mongodb-clients To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1317896/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1471237] Re: Mongo causes juju to fail: bad record MAC
** Description changed: This is a meta bug. mongo 2.6 can drop or corrupt connections. This bug will be fixed when either juju find a way to restore the connection, or a fixed mongodb is distributed and available to precise users and above. + + See http://reports.vapour.ws/releases/issue/559694bd749a5660bd8b8f07 for + a history of the issue in Juju CI. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1471237 Title: Mongo causes juju to fail: bad record MAC To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1471237/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1349949] Re: Juju's mongodb does not need to log every command in syslog
** Changed in: juju 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/1349949 Title: Juju's mongodb does not need to log every command in syslog To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1349949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1605976] Re: [2.0] bump mongod to 3.2.8
** Project changed: juju-core => juju -- 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] bump mongod to 3.2.8 To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1605976/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1612645] Re: New EC2 region in India (ap-south-1 - Mumbai)
** Also affects: juju-release-tools 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/1612645 Title: New EC2 region in India (ap-south-1 - Mumbai) To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1612645/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1612645] Re: New EC2 region in India (ap-south-1 - Mumbai)
** 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/1612645 Title: New EC2 region in India (ap-south-1 - Mumbai) To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1612645/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1570657] Re: Bash completion needed for versioned juju commands
** Changed in: juju-core 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/1570657 Title: Bash completion needed for versioned juju commands To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1570657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1570651] Re: Manpages for juju aliases drop version
** Changed in: juju-core Milestone: 2.0-beta14 => 2.0-beta15 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1570651 Title: Manpages for juju aliases drop version To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1570651/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1349949] Re: Juju's mongodb does not need to log every command in syslog
** Changed in: juju-core Milestone: 2.0-beta14 => 2.0-beta15 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1349949 Title: Juju's mongodb does not need to log every command in syslog To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1349949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1570657] Re: Bash completion needed for versioned juju commands
** Changed in: juju-core Milestone: 2.0-beta14 => 2.0-beta15 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1570657 Title: Bash completion needed for versioned juju commands To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1570657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1564662] Re: Juju binaries should be stripped
** Changed in: juju-core Milestone: 2.0.0 => 2.0-beta14 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1564662 Title: Juju binaries should be stripped To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1564662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1349949] Re: Juju's mongodb does not need to log every command in syslog
** Changed in: juju-core Milestone: 2.0-beta13 => 2.0-beta14 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1349949 Title: Juju's mongodb does not need to log every command in syslog To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1349949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1570651] Re: Manpages for juju aliases drop version
** Changed in: juju-core Milestone: 2.0-beta13 => 2.0-beta14 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1570651 Title: Manpages for juju aliases drop version To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1570651/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1570657] Re: Bash completion needed for versioned juju commands
** Changed in: juju-core Milestone: 2.0-beta13 => 2.0-beta14 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1570657 Title: Bash completion needed for versioned juju commands To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1570657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1570657] Re: Bash completion needed for versioned juju commands
** Changed in: juju-core/1.25 Milestone: 1.25.6 => 1.25.7 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1570657 Title: Bash completion needed for versioned juju commands To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1570657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1570660] Re: Plugins not included in juju manpages
** Changed in: juju-core/1.25 Milestone: 1.25.6 => 1.25.7 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1570660 Title: Plugins not included in juju manpages To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1570660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1570650] Re: Use juju-mongodb2.6 for 1.25 on xenial
** Changed in: juju-core/1.25 Milestone: 1.25.6 => 1.25.7 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1570650 Title: Use juju-mongodb2.6 for 1.25 on xenial To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1570650/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1570651] Re: Manpages for juju aliases drop version
** Changed in: juju-core/1.25 Milestone: 1.25.6 => 1.25.7 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1570651 Title: Manpages for juju aliases drop version To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1570651/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1349949] Re: Juju's mongodb does not need to log every command in syslog
** Changed in: juju-core Milestone: 2.0-beta11 => 2.0-beta12 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1349949 Title: Juju's mongodb does not need to log every command in syslog To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1349949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1570657] Re: Bash completion needed for versioned juju commands
** Changed in: juju-core Milestone: 2.0-beta11 => 2.0-beta12 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1570657 Title: Bash completion needed for versioned juju commands To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1570657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1570651] Re: Manpages for juju aliases drop version
** Changed in: juju-core Milestone: 2.0-beta11 => 2.0-beta12 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1570651 Title: Manpages for juju aliases drop version To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1570651/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1588403] Re: Tab completion missing in Juju 2.0 betas
** Changed in: juju-core 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/1588403 Title: Tab completion missing in Juju 2.0 betas To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1588403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1596638] Re: python2 cannot import lsb_release on yakkety and now xenial
This issue is now seen in xenial. This was not a problem a few hours ago. We can see on xenial now. These versions 9.20160110ubuntu4 and 9.20160110ubuntu0.1 remove the py2 module, but do not provide a py2 package to install. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1596638 Title: python2 cannot import lsb_release on yakkety and now xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/1596638/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1596638] Re: python2 cannot import lsb_release on yakkety and now xenial
** Summary changed: - python2 cannot import lsb_release on yakkety + python2 cannot import lsb_release on yakkety and now xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1596638 Title: python2 cannot import lsb_release on yakkety and now xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/1596638/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1596638] [NEW] python2 cannot import lsb_release on yakkety
Public bug reported: python2 cannot import lsb_release on yakkety. `locate` shows "lsb- release" installed several files, but /usr/lib/python2.7/dist-packages/lsb_release.py is missing from disk. This was seen on an aws instance provisioned using the 20160526 daily image. ** Affects: lsb (Ubuntu) Importance: Undecided Status: New ** Tags: jujuqa -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1596638 Title: python2 cannot import lsb_release on yakkety To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/1596638/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1596095] [NEW] [needs packaging] 3.2.4-0ubuntu4 available in xenial or trusty
Public bug reported: The Juju team wants juju-mongodb 3.2.4-0ubuntu4 backported to xenial- updates and trusty-backports. The xenial backport is very desirable because developers and customers are asking for the mongo-client (in the newer package) to fix production issues. The trusty backport is needed for Juju2 to enter RC. the juju-qa team are available to test the backported packages with Juju. ** Affects: juju-mongodb3.2 (Ubuntu) Importance: Undecided Status: New ** Tags: jujuqa needs-packaging -- 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 trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-mongodb3.2/+bug/1596095/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1570651] Re: Manpages for juju aliases drop version
** Changed in: juju-core Milestone: 2.0-beta10 => 2.0-beta11 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1570651 Title: Manpages for juju aliases drop version To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1570651/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1349949] Re: Juju's mongodb does not need to log every command in syslog
** Changed in: juju-core Milestone: 2.0-beta10 => 2.0-beta11 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1349949 Title: Juju's mongodb does not need to log every command in syslog To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1349949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1570657] Re: Bash completion needed for versioned juju commands
** Changed in: juju-core Milestone: 2.0-beta10 => 2.0-beta11 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1570657 Title: Bash completion needed for versioned juju commands To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1570657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1570651] Re: Manpages for juju aliases drop version
** Changed in: juju-core Milestone: 2.0-beta9 => 2.0-beta10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1570651 Title: Manpages for juju aliases drop version To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1570651/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1576318] Re: juju register not clear that you're creating a new password
** Changed in: juju-core 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/1576318 Title: juju register not clear that you're creating a new password To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1576318/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1349949] Re: Juju's mongodb does not need to log every command in syslog
** Changed in: juju-core Milestone: 2.0-beta9 => 2.0-beta10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1349949 Title: Juju's mongodb does not need to log every command in syslog To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1349949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1570657] Re: Bash completion needed for versioned juju commands
** Changed in: juju-core Milestone: 2.0-beta9 => 2.0-beta10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1570657 Title: Bash completion needed for versioned juju commands To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1570657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1576318] Re: juju register not clear that you're creating a new password
** Changed in: juju-core Milestone: None => 2.0-beta9 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1576318 Title: juju register not clear that you're creating a new password To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1576318/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1570657] Re: Bash completion needed for versioned juju commands
** Changed in: juju-core Milestone: 2.0-beta8 => 2.0-beta9 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1570657 Title: Bash completion needed for versioned juju commands To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1570657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1570651] Re: Manpages for juju aliases drop version
** Changed in: juju-core Milestone: 2.0-beta8 => 2.0-beta9 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1570651 Title: Manpages for juju aliases drop version To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1570651/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1556981] Re: [needs-packaging] Juju 1.25.5 is not in wily and trusty
** Description changed: Juju 1.25.5 enables maas 1.9, and several AWS instance types and regions. It included fixes many bugs reported against 1.24.7 [SRU Information] juju-core has a stable release exception in https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions, including for major version updates. Since there are multiple verifications required, they are listed here as a work item whiteboard status type thing rather than try and track them in a single tag. Please do not mark verification-done or remove block- proposed until all following items have passed. If any of these items fail, this bug should be marked verification-failed immediately. [Wily Fix] [sinzui] Backport wily source package and prepare diffs for wily: DONE [rbasak] Review package: DONE [rbasak] Upload to wily proposed (wily-proposed): DONE - [sinzui] Upstream QA test against wily: TODO - [sinzui] Test streams with wily-proposed: TODO - [sinzui] Test juju-quickstart against wily-proposed: TODO - [sinzui] Test juju-deployer against wily-proposed: TODO - [sinzui] Test client and cloud server upgrade against wily-proposed: TODO - [sinzui] Test client manual bootstrap and add-machine against wily-proposed: TODO + [sinzui] Upstream QA test against wily: DONE + [sinzui] Test streams with wily-proposed: DONE + [sinzui] Test juju-quickstart against wily-proposed: DONE + [sinzui] Test juju-deployer against wily-proposed: DONE + [sinzui] Test client and cloud server upgrade against wily-proposed: DONE + [sinzui] Test client manual bootstrap and add-machine against wily-proposed: DONE [Trusty Fix] [sinzui] Backport trusty source package and prepare diffs for trusty: DONE [rbasak] Review package: DONE [rbasak] Upload to trusty proposed (trusty-proposed): DONE - [sinzui] Upstream QA test against trusty: TODO - [sinzui] Test streams with trusty-proposed: TODO - [sinzui] Test juju-quickstart against trusty-proposed: TODO - [sinzui] Test juju-deployer against trusty-proposed: TODO - [sinzui] Test client and cloud server upgrade against trusty-proposed: TODO - [sinzui] Test client manual bootstrap and add-machine against trusty-proposed: TODO + [sinzui] Upstream QA test against trusty: DONE + [sinzui] Test streams with trusty-proposed: DONE + [sinzui] Test juju-quickstart against trusty-proposed: DONE + [sinzui] Test juju-deployer against trusty-proposed: DONE + [sinzui] Test client and cloud server upgrade against trusty-proposed: DONE + [sinzui] Test client manual bootstrap and add-machine against trusty-proposed: DONE -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1556981 Title: [needs-packaging] Juju 1.25.5 is not in wily and trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1556981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1556981] Re: [needs-packaging] Juju 1.25.5 is not in wily and trusty
The juju-qa team tests of 1.25.5-0ubuntu3~14.04.1 in trusty-proposed pass. The juju is compatible with the agents in streams. It is fit for cloud deployments.It is suitable for devel and testing using the local- provider. the manual-provider can be used in production scenarios. The juju is compatible with the juju-deployer and juju-quickstart in trusty- release/trusty-updates ** 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/1556981 Title: [needs-packaging] Juju 1.25.5 is not in wily and trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1556981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1556981] Re: [needs-packaging] Juju 1.25.5 is not in wily and trusty
The juju-qa team tests of 1.25.5-0ubuntu3~15.10.1 pass. The juju is compatible with the agents in streams. It is fit for cloud deployments. It is suitable for devel and testing using the local- provider. the manual-provider can be used in production scenarios. The juju is compatible with the juju-deployer and juju-qquickstart in wily- release/wily-updates -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1556981 Title: [needs-packaging] Juju 1.25.5 is not in wily and trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1556981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1583740] [NEW] mongo client is missing
Public bug reported: Admins and developers are unable to access to the juju mongodb instance to investigation issues. The mongo client is built, but not included in the juju-mongodb3.2 package. Juju doesn't need it. Users who need to investigate db issues need to locate and install a third-party binary. This issue affects both yakkety an xenial. ** Affects: juju-mongodb3.2 (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1583740 Title: mongo client is missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-mongodb3.2/+bug/1583740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1583740] Re: mongo client is missing
I have prepared branches for both yakkety and xenial to provide the wanted client https://code.launchpad.net/~sinzui/ubuntu/+source/juju-mongodb32/+git/juju-mongodb32/+ref/ubuntu-yakkety and https://code.launchpad.net/~sinzui/ubuntu/+source/juju-mongodb32/+git/juju-mongodb32/+ref/ubuntu-xenial ** Tags added: patch ** Changed in: juju-mongodb3.2 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1583740 Title: mongo client is missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-mongodb3.2/+bug/1583740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1556981] Re: [needs-packaging] Juju 1.25.5 is not in wily and trusty
^ Both the wily and trusty packages were verified to pass their respective ADT tests. The repo has the pristine-tar files. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1556981 Title: [needs-packaging] Juju 1.25.5 is not in wily and trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1556981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1556981] Re: [needs-packaging] Juju 1.25.5 is not in wily and trusty
I prepared a backport of juju-core-1 1.25.5-0ubuntu3 for wily. https://git.launchpad.net/~sinzui/ubuntu/+source/juju-core/log/?h =ubuntu-wily This is *not* a no-change backport because the source package was renamed to juju-core-1 in xenial. Most the the debian/ changes relate to the rename. I made the minimal change to wily's debian/ dir for this backport. plus two small changes: * d/copyright: Backported with changes to src Updated info for src/gopkg.in/juju/charm.v5/* to now match commit 84c8fe478fa1b1e67eb552831de5fd2603085c51 * d/control: Added juju-1 to conflicts as a courtesy to users of alternate packages. Note that the copyright file was was written by Adam Conrad for Xenial for readability. Cases where the copyright holders added their names to common licences were removed as the inline licences. Attached are both a diff of the minimal debian changes and a larger diff of between the xenial source tree and the wily source tree. The later shows the source has not changed and that the majority of debian differences are because the different package names. ** Attachment added: "diffs of debian and from xenial to wily" https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1556981/+attachment/4664173/+files/wily-diffs.tar.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1556981 Title: [needs-packaging] Juju 1.25.5 is not in wily and trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1556981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1556981] Re: [needs-packaging] Juju 1.25.5 is not in wily and trusty
I prepared a backport of juju-core-1 1.25.5-0ubuntu3 for trusty. https://git.launchpad.net/~sinzui/ubuntu/+source/juju-core/log/?h =ubuntu-trusty This is *not* a no-change backport because the source package was renamed to juju-core-1 in xenial. Most the the debian/ changes relate to the rename. I made the minimal change to trusty's debian/ dir for this backport. plus two small changes: * d/copyright: Backported with changes to src Updated info for src/gopkg.in/juju/charm.v5/* to now match commit 84c8fe478fa1b1e67eb552831de5fd2603085c51 * d/control: Added juju-1 to conflicts as a courtesy to users of alternate packages. Note that the copyright file was was written by Adam Conrad for Xenial for readability. Cases where the copyright holders added their names to common licences were removed as the inline licences. Attached are both a diff of the minimal debian changes and a larger diff of between the xenial source tree and the trusty source tree. The later shows the source has not changed and that the majority of debian differences are because the different package names. ** Attachment added: "diffs of debian and from xenial to trusty" https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1556981/+attachment/4664180/+files/trusty-diffs.tar.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1556981 Title: [needs-packaging] Juju 1.25.5 is not in wily and trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1556981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1570651] Re: Manpages for juju aliases drop version
** Changed in: juju-core Milestone: 2.0-beta7 => 2.0-beta8 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1570651 Title: Manpages for juju aliases drop version To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1570651/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1349949] Re: Juju's mongodb does not need to log every command in syslog
** Changed in: juju-core Milestone: 2.0-beta7 => 2.0-beta8 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1349949 Title: Juju's mongodb does not need to log every command in syslog To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1349949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1570660] Re: Plugins not included in juju manpages
** Changed in: juju-core Milestone: 2.0-beta7 => 2.0-beta8 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1570660 Title: Plugins not included in juju manpages To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1570660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1570657] Re: Bash completion needed for versioned juju commands
** Changed in: juju-core Milestone: 2.0-beta7 => 2.0-beta8 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1570657 Title: Bash completion needed for versioned juju commands To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1570657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1581284] Re: --sslPEMKeyPassword parameter must be passed with = on yakkety
** Changed in: juju-core 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/1581284 Title: --sslPEMKeyPassword parameter must be passed with = on yakkety To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1581284/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1556981] Re: [needs-packaging] Juju 1.25.45is not in wily and trusty
** Summary changed: - [needs-packaging] Juju 1.25.4 is not in xenial, wily, and trusty + [needs-packaging] Juju 1.25.45is not in wily and trusty ** Description changed: - Juju 1.25.4 enabled maas 1.9 and fixes many bugs reported against 1.25.0 + Juju 1.25.5 enables maas 1.9, and several AWS instance types and + regions. It included fixes many bugs reported against 1.24.7 [SRU Information] juju-core has a stable release exception in https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions, including for major version updates. Since there are multiple verifications required, they are listed here as a work item whiteboard status type thing rather than try and track them in a single tag. Please do not mark verification-TODO or remove block- proposed until all following items have passed. If any of these items fail, this bug should be marked verification-failed immediately. - - [Devel Fix] - - [sinzui] Prepare source package and diffs: TODO - [rbasak] Review package: TODO - [rbasak] Upload to the development release (xenial-proposed): TODO - - [sinzui] Upstream QA test against xenial: TODO - [sinzui] Test streams with xenial-proposed: TODO - [sinzui] Test juju-quickstart against xenial-proposed: TODO - [sinzui] Test juju-deployer against xenial-proposed: TODO - [sinzui] Test client and cloud server upgrade against xenial-proposed: TODO - [sinzui] Test client manual bootstrap and add-machine against xenial-proposed: TODO [Wily Fix] [sinzui] Backport wily source package and prepare diffs for wily: TODO [rbasak] Review package: TODO [rbasak] Upload to wily proposed (wily-proposed): TODO [sinzui] Upstream QA test against wily: TODO [sinzui] Test streams with wily-proposed: TODO [sinzui] Test juju-quickstart against wily-proposed: TODO [sinzui] Test juju-deployer against wily-proposed: TODO [sinzui] Test client and cloud server upgrade against wily-proposed: TODO [sinzui] Test client manual bootstrap and add-machine against wily-proposed: TODO - [Trusty Fix] [sinzui] Backport trusty source package and prepare diffs for trusty: TODO [rbasak] Review package: TODO [rbasak] Upload to trusty proposed (trusty-proposed): TODO [sinzui] Upstream QA test against trusty: TODO [sinzui] Test streams with trusty-proposed: TODO [sinzui] Test juju-quickstart against trusty-proposed: TODO [sinzui] Test juju-deployer against trusty-proposed: TODO [sinzui] Test client and cloud server upgrade against trusty-proposed: TODO [sinzui] Test client manual bootstrap and add-machine against trusty-proposed: TODO ** Summary changed: - [needs-packaging] Juju 1.25.45is not in wily and trusty + [needs-packaging] Juju 1.25.5 is not in wily and trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1556981 Title: [needs-packaging] Juju 1.25.5 is not in wily and trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1556981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
