[Expired for ubuntu-cloud-archive because there has been no activity for
60 days.]
** Changed in: cloud-archive
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad
** Changed in: cloud-archive
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1289489
Title:
Installing MAAS from cloud-tools-next on precise fails
To m
Hi Ryan, I tried this in a pristine precise VM with the current version of maas
in cloud-tools-next (1.5+bzr2252-0ubuntu1~ctools0) and didn't get any errors
during install. I didn't get errors when I ran the upgrade test from
cloud-tools to cloud-tools-next either so I'm closing this as invalid.
** Also affects: cloud-archive
Importance: Undecided
Status: New
** Changed in: maas
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1289489
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: maas (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1289489
** Changed in: maas
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1289489
Title:
Installing MAAS from cloud-tools-next on precise fails
To manage not
On Friday 07 Mar 2014 17:20:42 you wrote:
> Assigned to both ubuntu mpackage and maas trunk because the package
> should have a versioned dependency on python-django-south, which should
> have come from upstream.
I don't think this should be on upstream, the package versioning is all done
in pack
Assigned to both ubuntu mpackage and maas trunk because the package
should have a versioned dependency on python-django-south, which should
have come from upstream.
** Also affects: maas (Ubuntu)
Importance: Undecided
Status: New
** Changed in: maas
Assignee: (unassigned) => Andres
