[Blueprint servercloud-s-juju-2-delivery] Delivering Juju 2.0 into Ubuntu
Blueprint changed by James Page: Work items changed: Work items for ubuntu-13.06: [racb] Get Go 1.1 into the archive: DONE [gz] Move to a source based juju-core release process: TODO Upload juju-core point release: POSTPONED Work items for ubuntu-13.07: Get golang 1.1.1 into the archive: DONE - Upload juju-core point release: TODO - Setup backports PPA for juju-core: TODO + Upload juju-core point release: DONE + Setup golang backports PPA: DONE + Setup juju-core backports PPA: TODO Setup devel PPA for juju-core: TODO [davewalker] Follow up on backports build being fixed for juju-core: INPROGRESS [gz] Backport Juju .7 into 12.04 and 12.10 to co-exist with juju 1.11+: TODO [dave-cheney] Push bi-weekly juju-core releases into Saucy/latest Ubuntu dev: TODO Work items for ubuntu-13.08: Upload juju-core point release: TODO Work items for ubuntu-13.09: Upload juju-core point release: TODO Work items for ubuntu-13.10: Upload juju-core final release: TODO Enable ARM support: TODO Backport juju-core to 12.04, 12.10 and 13.04: TODO Work items: Investigate automated releases of juju-core into Ubuntu: TODO [dave-cheney] verify that Juju works with gccgo: TODO -- Delivering Juju 2.0 into Ubuntu https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-2-delivery -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-s-juju-2-delivery] Delivering Juju 2.0 into Ubuntu
Blueprint changed by James Page: Work items changed: Work items for ubuntu-13.06: [racb] Get Go 1.1 into the archive: DONE - [gz] Move to a source based juju-core release process: TODO + [gz] Move to a source based juju-core release process: DONE Upload juju-core point release: POSTPONED Work items for ubuntu-13.07: Get golang 1.1.1 into the archive: DONE Upload juju-core point release: DONE Setup golang backports PPA: DONE Setup juju-core backports PPA: TODO Setup devel PPA for juju-core: TODO [davewalker] Follow up on backports build being fixed for juju-core: INPROGRESS [gz] Backport Juju .7 into 12.04 and 12.10 to co-exist with juju 1.11+: TODO [dave-cheney] Push bi-weekly juju-core releases into Saucy/latest Ubuntu dev: TODO Work items for ubuntu-13.08: Upload juju-core point release: TODO Work items for ubuntu-13.09: Upload juju-core point release: TODO Work items for ubuntu-13.10: Upload juju-core final release: TODO Enable ARM support: TODO Backport juju-core to 12.04, 12.10 and 13.04: TODO Work items: Investigate automated releases of juju-core into Ubuntu: TODO [dave-cheney] verify that Juju works with gccgo: TODO -- Delivering Juju 2.0 into Ubuntu https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-2-delivery -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1200878] [NEW] Upgrade breaks existing pyjuju deployment
Public bug reported: A recent saucy system upgrade replaced pyjuju with juju-core. Now my existing deployment breaks as follows: $ juju status error: no CA certificate in environment configuration No indication of what I'm supposed to do to fix this. Perhaps bug 1178314 is related, but I'm not sure. Breaking existing deployments is surely unacceptable in a system upgrade. If this is a general problem and not specific to my deployment (which has been running for a few months, in Canonistack), then pyjuju should be restored until the upgrade experience is smooth. (Fortunately, as I've discovered, /usr/lib/juju-0.7/bin/juju still works. This still seems rather non-obvious and suboptimal, though.) == Regression details == Discovered in version: 1.11.2-0ubuntu1 Last known good version: 0.7-0ubuntu1 --- ApportVersion: 2.10.2-0ubuntu4 Architecture: amd64 DistroRelease: Ubuntu 13.10 EcryptfsInUse: Yes InstallationDate: Installed on 2013-03-01 (133 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130223.1) MarkForUpload: True Package: juju-core 1.11.2-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.10.0-2.11-generic 3.10.0 Tags: saucy Uname: Linux 3.10.0-2-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip fuse lpadmin plugdev sambashare sbuild sudo uml-net ** Affects: juju-core (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected regression-release saucy ** Tags added: apport-collected saucy ** Description changed: A recent saucy system upgrade replaced pyjuju with juju-core. Now my existing deployment breaks as follows: $ juju status error: no CA certificate in environment configuration No indication of what I'm supposed to do to fix this. Perhaps bug 1178314 is related, but I'm not sure. - Breaking existing deployments is surely unacceptable in a system - upgrade. If this is a general problem and not specific to my deployment - (which has been running for a few months, in Canonistack), then pyjuju - should be restored until the upgrade experience is smooth. + Breaking existing deployments is surely unacceptable in a system upgrade. If this is a general problem and not specific to my deployment (which has been running for a few months, in Canonistack), then pyjuju should be restored until the upgrade experience is smooth. + --- + ApportVersion: 2.10.2-0ubuntu4 + Architecture: amd64 + DistroRelease: Ubuntu 13.10 + EcryptfsInUse: Yes + InstallationDate: Installed on 2013-03-01 (133 days ago) + InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130223.1) + MarkForUpload: True + Package: juju-core 1.11.2-0ubuntu1 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 3.10.0-2.11-generic 3.10.0 + Tags: saucy + Uname: Linux 3.10.0-2-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip fuse lpadmin plugdev sambashare sbuild sudo uml-net -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1200878 Title: Upgrade breaks existing pyjuju deployment To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1200878/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1200878] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1200878/+attachment/3735387/+files/ProcEnviron.txt ** Description changed: A recent saucy system upgrade replaced pyjuju with juju-core. Now my existing deployment breaks as follows: - $ juju status - error: no CA certificate in environment configuration + $ juju status + error: no CA certificate in environment configuration No indication of what I'm supposed to do to fix this. Perhaps bug 1178314 is related, but I'm not sure. - Breaking existing deployments is surely unacceptable in a system upgrade. If this is a general problem and not specific to my deployment (which has been running for a few months, in Canonistack), then pyjuju should be restored until the upgrade experience is smooth. - --- + Breaking existing deployments is surely unacceptable in a system + upgrade. If this is a general problem and not specific to my deployment + (which has been running for a few months, in Canonistack), then pyjuju + should be restored until the upgrade experience is smooth. + + (Fortunately, as I've discovered, /usr/lib/juju-0.7/bin/juju still + works. This still seems rather non-obvious and suboptimal, though.) + + == Regression details == + Discovered in version: 1.11.2-0ubuntu1 + Last known good version: 0.7-0ubuntu1 + --- ApportVersion: 2.10.2-0ubuntu4 Architecture: amd64 DistroRelease: Ubuntu 13.10 EcryptfsInUse: Yes InstallationDate: Installed on 2013-03-01 (133 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130223.1) MarkForUpload: True Package: juju-core 1.11.2-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.10.0-2.11-generic 3.10.0 Tags: saucy Uname: Linux 3.10.0-2-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip fuse lpadmin plugdev sambashare sbuild sudo uml-net -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1200878 Title: Upgrade breaks existing pyjuju deployment To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1200878/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1200878] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1200878/+attachment/3735386/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1200878 Title: Upgrade breaks existing pyjuju deployment To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1200878/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1201022] [NEW] package iscsitarget 1.4.20.3+svn490-2ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: corrupt btrfs ProblemType: Package DistroRelease: Ubuntu 13.10 Package: iscsitarget 1.4.20.3+svn490-2ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-1.8-generic 3.10.0-rc7 Uname: Linux 3.10.0-1-generic i686 ApportVersion: 2.10.2-0ubuntu4 Architecture: i386 Date: Sat Jul 13 04:04:44 2013 DuplicateSignature: package:iscsitarget:1.4.20.3+svn490-2ubuntu1:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2013-03-15 (120 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha i386 (20130314) MarkForUpload: True SourcePackage: iscsitarget Title: package iscsitarget 1.4.20.3+svn490-2ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.default.iscsitarget: 2013-06-22T00:50:07.501588 mtime.conffile..etc.iet.ietd.conf: 2013-07-06T05:53:49.906804 ** Affects: iscsitarget (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 need-duplicate-check saucy -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to iscsitarget in Ubuntu. https://bugs.launchpad.net/bugs/1201022 Title: package iscsitarget 1.4.20.3+svn490-2ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iscsitarget/+bug/1201022/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1201029] [NEW] Please merge backuppc 3.2.1-5.1 (main) from Debian unstable (main)
Public bug reported: Please merge backuppc 3.2.1-5.1 (main) from Debian unstable (main). ** Affects: backuppc (Ubuntu) Importance: Undecided Assignee: Jackson Doak (noskcaj) Status: In Progress ** Tags: upgrade-software-version ** Changed in: backuppc (Ubuntu) Status: New => In Progress ** Changed in: backuppc (Ubuntu) Assignee: (unassigned) => Jackson Doak (noskcaj) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to backuppc in Ubuntu. https://bugs.launchpad.net/bugs/1201029 Title: Please merge backuppc 3.2.1-5.1 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backuppc/+bug/1201029/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1201029] Re: Please merge backuppc 3.2.1-5.1 (main) from Debian unstable (main)
I've set everything up for an ubuntu version of this, I've still got everything for if other things need attaching ** Attachment added: "The new version ready for ubuntu" https://bugs.launchpad.net/ubuntu/+source/backuppc/+bug/1201029/+attachment/3736179/+files/backuppc-3.2.1-5.1ubuntu1.tar.gz -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to backuppc in Ubuntu. https://bugs.launchpad.net/bugs/1201029 Title: Please merge backuppc 3.2.1-5.1 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backuppc/+bug/1201029/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1179746] Re: the package shouldn't be installed if there is only one core
[Expired for irqbalance (Ubuntu) because there has been no activity for 60 days.] ** Changed in: irqbalance (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to irqbalance in Ubuntu. https://bugs.launchpad.net/bugs/1179746 Title: the package shouldn't be installed if there is only one core To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1179746/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
