[Bug 1490299] Re: Environment variables "GOBIN", "GOEXE" etc. not set
Go install takes a package path, not a file. Please consult this document, https://golang.org/doc/code.html This is not a channel for support request using Go, I recommend you ask on the irc channel, slack, or the golang-nuts mailing list. ** Changed in: golang (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to golang in Ubuntu. https://bugs.launchpad.net/bugs/1490299 Title: Environment variables "GOBIN", "GOEXE" etc. not set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang/+bug/1490299/+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 1490299] Re: Environment variables GOBIN, GOEXE etc. not set
GORUN, GOBIN, GOEXE etc are optional environment variables and are not required to use Go. In fact, you really shouldn't set them Looking at the screenshot you provided the reason your program did not compile is you have a syntax error, you want fmt.Printf (capital P). Please feel free to reopen this bug if you think I have not addressed your problem. You may also find it useful to drop by irc, #golang on freenode, the slack channel, or the golang-nuts mailing list. ** Changed in: golang (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to golang in Ubuntu. https://bugs.launchpad.net/bugs/1490299 Title: Environment variables GOBIN, GOEXE etc. not set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang/+bug/1490299/+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 1452457] [NEW] Please import golang-1.4.2 from debian/sid
Public bug reported: Please import golang-1.4.2 from debian/sid into Wily https://packages.debian.org/sid/golang ** Affects: golang (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to golang in Ubuntu. https://bugs.launchpad.net/bugs/1452457 Title: Please import golang-1.4.2 from debian/sid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang/+bug/1452457/+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 1452457] Re: Please import golang-1.4.2 from debian/sid
Robie, do you have permissions to target this bug to W only? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to golang in Ubuntu. https://bugs.launchpad.net/bugs/1452457 Title: Please import golang-1.4.2 from debian/sid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang/+bug/1452457/+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 1381671] Re: reboot tests fail to build on gccgo
The fix for gccgo-5 has landed upstream https://gcc.gnu.org/viewcvs/gcc?view=revisionrevision=221782 Can gccgo-5 in Vivid be rebuilt at or after revision 221782. The patch is also available and should apply cleanly to gccgo-go in Trusty. https://codereview.appspot.com/222890043 ** Changed in: gcc-4.9 (Ubuntu) Status: Incomplete = In Progress ** Changed in: gcc-4.9 (Ubuntu) Status: In Progress = Invalid ** Changed in: gccgo-go (Ubuntu) Status: Invalid = In Progress -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to gccgo-go in 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-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 1392094] Re: golang is unavailable for arm64
The gc compiler (http://golang.org/) does not support arm64 ** Changed in: golang (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to golang in Ubuntu. https://bugs.launchpad.net/bugs/1392094 Title: golang is unavailable for arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1392094/+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 1364562] Re: Intermittent go test crashes on ppc64el
Sorry Casey, I don't know where you got that revision of the compiler from, but it's too old and busted. Try the one from trusty-proposed. ** Changed in: gccgo-go (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to gccgo-go in Ubuntu. https://bugs.launchpad.net/bugs/1364562 Title: Intermittent go test crashes on ppc64el To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gccgo-go/+bug/1364562/+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
Re: [Bug 1347322] Re: juju ssh results in a panic: runtime error
btw. This has nothing to do with ssh, it is to do with the length of time the juju cli process is running for. Normally this is a very short period, but juju ssh forks ssh as a child then waits for it to finish. The crash is caused by a bug in the previous runtime (compiled statically into the binary) when the garbage collector had been running for long enough to call madvise(DONT_NEED, ...) with the wrong page size. On Sat, Jul 26, 2014 at 8:22 AM, Matt Bruzek matthew.bru...@canonical.com wrote: With sinzui's help I have compiled the latest version of Juju 1.20.2 with the gccgo-4.9_4.9.1-1ubuntu3_ppc64el.deb. NOT able to reproduce the “juju ssh” panic/problem having several ssh sessions open simultaneously and having output streaming for over 2 hours. For clarity and review here are the details of how we build the deb packages for Juju with the gccgo 4.9.1 compiler on the CI machine stilson-09 (a P8 64k page size machine). ubuntu@stilson-09:~⟫ uname -a Linux stilson-09 3.13.0-24-generic #47-Ubuntu SMP Fri May 2 23:29:18 UTC 2014 ppc64le ppc64le ppc64le GNU/Linux ubuntu@stilson-09:~⟫ getconf PAGE_SIZE 65536 ubuntu@stilson-09:~⟫ more /proc/cpuinfo processor : 0 cpu : POWER8E (raw), altivec supported clock : 4116.00MHz revision: 2.0 (pvr 004b 0200) processor : 1 cpu : POWER8E (raw), altivec supported clock : 4116.00MHz revision: 2.0 (pvr 004b 0200) timebase: 51200 platform: pSeries model : IBM pSeries (emulated by qemu) machine : CHRP IBM pSeries (emulated by qemu) Downloaded the following packages from: https://launchpad.net/ubuntu/utopic/ppc64el/gccgo-4.9/4.9.1-1ubuntu3 binutils_2.24.51.20140709-1ubuntu1_ppc64el.deb cpp-4.9_4.9.1-1ubuntu3_ppc64el.deb gcc-4.9_4.9.1-1ubuntu3_ppc64el.deb gcc-4.9-base_4.9.1-1ubuntu3_ppc64el.deb gccgo-4.9_4.9.1-1ubuntu3_ppc64el.deb libatomic1_4.9.1-1ubuntu3_ppc64el.deb libgcc1_4.9.1-1ubuntu3_ppc64el.deb libgcc-4.9-dev_4.9.1-1ubuntu3_ppc64el.deb libgo5_4.9.1-1ubuntu3_ppc64el.deb libgomp1_4.9.1-1ubuntu3_ppc64el.deb libitm1_4.9.1-1ubuntu3_ppc64el.deb Installed the packages on stilson-09: ubuntu@stilson-09:~/gccgo⟫ sudo dpkg -i *.deb ubuntu@stilson-09:~/gccgo⟫ dpkg -l | grep gcc ii gcc4:4.8.2-1ubuntu6 ppc64el GNU C compiler ii gcc-4.84.8.3-3ubuntu0.2 ppc64el GNU C compiler ii gcc-4.8-base:ppc64el 4.8.3-3ubuntu0.2 ppc64el GCC, the GNU Compiler Collection (base package) ii gcc-4.94.9.1-1ubuntu3 ppc64el GNU C compiler ii gcc-4.9-base:ppc64el 4.9.1-1ubuntu3 ppc64el GCC, the GNU Compiler Collection (base package) ii gccgo 4:4.9-1ubuntu6 ppc64el Go compiler, based on the GCC backend ii gccgo-4.9 4.9.1-1ubuntu3 ppc64el GNU Go compiler ii gccgo-go 1.2.1-0ubuntu1 ppc64el Go tool for use with gccgo ii libgcc-4.8-dev:ppc64el 4.8.3-3ubuntu0.2 ppc64el GCC support library (development files) ii libgcc-4.9-dev:ppc64el 4.9.1-1ubuntu3 ppc64el GCC support library (development files) ii libgcc1:ppc64el1:4.9.1-1ubuntu3 ppc64el GCC support library Built Juju from source on stilson-09: sinzui ~/Work/juju-release-tools/make-source-packages.bash stable juju-core_1.20.2.tar.gz 'Curtis Hovey curtis.ho...@canonical.com' 1340893 1345014 1344940 1345832 1307434 1347371 1337091 1342747 1343301 1341589 sinzui ~/Work/juju-release-tools/build-package-with-dsc.bash ubuntu@stilson-09 '' /home/curtis/Downloads/tmp.WUZeXOfFz1/juju-core_1.20.2-0ubuntu1~14.04.1~juju1.dsc Resulting in: ubuntu@stilson-09:~⟫ ls -l juju-build total 17332 -rw-r--r-- 1 ubuntu ubuntu 6944 Jul 25 15:05 juju_1.20.2-0ubuntu1~14.04.1~juju1_all.deb drwxrwxr-x 7 ubuntu ubuntu 4096 Jul 25 15:04 juju-core-1.20.2 -rw--- 1 ubuntu ubuntu 8356 Jul 25 15:04 juju-core_1.20.2-0ubuntu1~14.04.1~juju1.debian.tar.gz -rw--- 1 ubuntu ubuntu 1183 Jul 25 15:04 juju-core_1.20.2-0ubuntu1~14.04.1~juju1.dsc -rw-rw-r-- 1 ubuntu ubuntu 3133 Jul 25 15:05 juju-core_1.20.2-0ubuntu1~14.04.1~juju1_ppc64el.changes -rw-r--r-- 1 ubuntu ubuntu 14341816 Jul 25 15:05 juju-core_1.20.2-0ubuntu1~14.04.1~juju1_ppc64el.deb -rw-rw-r-- 1 ubuntu ubuntu 3354392 Jul 25 15:03 juju-core_1.20.2.orig.tar.gz -rw-r--r-- 1 ubuntu ubuntu 7020 Jul 25 15:05 juju-local_1.20.2-0ubuntu1~14.04.1~juju1_all.deb -rw-r--r-- 1 ubuntu ubuntu 7022 Jul 25 15:05 juju-local-kvm_1.20.2-0ubuntu1~14.04.1~juju1_all.deb I copied these deb
[Bug 1289067] Re: arm64 multiple definition of `launchpad.net_juju_core_cmd._.0
** Changed in: juju-core Status: Triaged = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to gccgo-go in Ubuntu. https://bugs.launchpad.net/bugs/1289067 Title: arm64 multiple definition of `launchpad.net_juju_core_cmd._.0 To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1289067/+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 1294455] [NEW] mongodb-server leaks debug information during remove
Public bug reported: $ sudo apt-get remove mongodb-server Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: libgoogle-perftools4 libtcmalloc-minimal4 libv8-3.14.5 mongodb-clients Use 'apt-get autoremove' to remove them. The following packages will be REMOVED: mongodb-server 0 upgraded, 0 newly installed, 1 to remove and 4 not upgraded. After this operation, 16.2 MB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ... 81169 files and directories currently installed.) Removing mongodb-server (1:2.4.9-1ubuntu1) ... arg: remove mongodb stop/waiting Processing triggers for man-db (2.6.6-1) ... Third last line looks like some debug that wasn't quashed. ** Affects: mongodb (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mongodb in Ubuntu. https://bugs.launchpad.net/bugs/1294455 Title: mongodb-server leaks debug information during remove To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mongodb/+bug/1294455/+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
Re: [Bug 1273769] Re: ppc64el enablement for juju/lxc
You can mark this fix release against, 1.17.5 for what it's worth On Mon, Mar 17, 2014 at 3:36 PM, John A Meinel j...@arbash-meinel.comwrote: ** Changed in: juju-core Milestone: 1.18.0 = 1.17.6 -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1273769 Title: ppc64el enablement for juju/lxc Status in juju-core: Fix Committed Status in cloud-utils package in Ubuntu: Fix Released Status in juju-core package in Ubuntu: Triaged Status in lxc package in Ubuntu: Fix Released Bug description: After some initial testing of juju (with local provider) on ppc64el - we need todo some work to fully enable this option. 1) LXC templates need to support ppc64el as a valid container arch 2) ubuntu-cloudimg-query is not avaliable on ppc64el 3) Juju is explicit in its support for x84 and arm - so enablement work is needed here as well. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lxc 1.0.0~beta3-0ubuntu1 ProcVersionSignature: User Name 3.13.0-2.17-generic 3.13.0-rc7 Uname: Linux 3.13.0-2-generic ppc64le ApportVersion: 2.13.2-0ubuntu2 Architecture: ppc64el Date: Tue Jan 28 16:49:03 2014 ProcEnviron: TERM=screen-256color-bce PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1273769/+subscriptions -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1273769 Title: ppc64el enablement for juju/lxc To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1273769/+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
Re: [Bug 1273769] Re: ppc64el enablement for juju/lxc
On Fri, Mar 14, 2014 at 5:59 AM, Mark Ramm mark.ramm-christen...@canonical.com wrote: Dave, can you turn you hack of your working copy into a branch proposal? All my outstanding changes have long since been committed to trunk ** Changed in: juju-core Importance: High = Critical -- You received this bug notification because you are subscribed to juju- core. Matching subscriptions: MOAR JUJU SPAM! https://bugs.launchpad.net/bugs/1273769 Title: ppc64el enablement for juju/lxc Status in juju-core: Triaged Status in cloud-utils package in Ubuntu: Fix Released Status in juju-core package in Ubuntu: Triaged Status in lxc package in Ubuntu: Fix Released Bug description: After some initial testing of juju (with local provider) on ppc64el - we need todo some work to fully enable this option. 1) LXC templates need to support ppc64el as a valid container arch 2) ubuntu-cloudimg-query is not avaliable on ppc64el 3) Juju is explicit in its support for x84 and arm - so enablement work is needed here as well. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lxc 1.0.0~beta3-0ubuntu1 ProcVersionSignature: User Name 3.13.0-2.17-generic 3.13.0-rc7 Uname: Linux 3.13.0-2-generic ppc64le ApportVersion: 2.13.2-0ubuntu2 Architecture: ppc64el Date: Tue Jan 28 16:49:03 2014 ProcEnviron: TERM=screen-256color-bce PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1273769/+subscriptions -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1273769 Title: ppc64el enablement for juju/lxc To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1273769/+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 1273769] Re: ppc64el enablement for juju/lxc
I'm going to mark this as fix committed for juju-core.
The prereq changes to lxc and cloud templates have been released
Juju now understands ppc64{el,le} as an arch and can bootstrap
ubuntu@winton-02:~/src/launchpad.net/juju-core$ juju switch local
julocal - local
ubuntu@winton-02:~/src/launchpad.net/juju-core$ juju bootstrap --upload-tools
Logging to /home/ubuntu/.juju/local/log/cloud-init-output.log on remote host
Starting MongoDB server (juju-db-ubuntu-local)
Bootstrapping Juju machine agent
Starting Juju machine agent (juju-agent-ubuntu-local)
ubuntu@winton-02:~/src/launchpad.net/juju-core$ juju status
environment: local
machines:
0:
agent-state: down
agent-state-info: (started)
agent-version: 1.17.5.1
dns-name: localhost
instance-id: localhost
series: trusty
services: {}
** Changed in: juju-core
Status: Triaged = Fix Committed
** Changed in: juju-core
Assignee: (unassigned) = Dave Cheney (dave-cheney)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1273769
Title:
ppc64el enablement for juju/lxc
To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1273769/+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
Re: [Bug 1284376] Re: Go 1.2.1 will be released in early March
On Fri, Mar 7, 2014 at 1:49 AM, Robie Basak 1284...@bugs.launchpad.net wrote: As this is past feature freeze, what are the options for getting these fixes into Trusty? Is this a bugfix-only release, or will it introduce new features? If only bugfixes, then being beyond feature freeze is not a problem. If features, then we need a feature freeze exception from the release team. Absolutely bugfix only, and even then we didn't choose to backport several less critical bugs. From the upstream thread: (Does that mean the version of Go in 14.04 will be the same forever? If our future releases are backward compatible, can't they be included? What's the policy?) Short answer: after release, backported high impact bugfixes only, no new features. Do upstream maintain a stable branch with a bugfix-only policy? If so, then a standing exception to stay up-to-date against that branch is possible, subject to quality requirements. Thanks. 1.2.1 is the last of the 1.2.x series, the next version will be 1.3 which will ship after Trusty so is not relevant. Full policy, rationale, procedure etc: https://wiki.ubuntu.com/StableReleaseUpdates I see that 1.2.1 appears released, and from a quick look it seems that it's bugfix only. Can somebody please confirm? If this is right then we can just do it. ** Tags added: upgrade-software-version ** Changed in: golang (Ubuntu) Status: New = Triaged ** Changed in: golang (Ubuntu) Importance: Undecided = Medium ** Changed in: golang (Ubuntu) Milestone: None = ubuntu-14.04-beta-2 -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1284376 Title: Go 1.2.1 will be released in early March Status in golang package in Ubuntu: Triaged Bug description: From https://groups.google.com/d/msg/golang- dev/VkSwKuEx4hY/M2FmC4xum6gJ, Go 1.2.1 will be released shortly, I heard a date of March 1, I am trying to confirm. It will contain, at this stage, these fixes 7219 database/sql: last connection in pool not handed out correctly 6987 net: ignore WSAECONNRESET AcceptEx error 6776 runtime: code text inspection confused by gdb breakpoints 6946 runtime: crash in GoroutineProfile 5139 runtime: fatal error: notewakeup - double wakeup As this is past feature freeze, what are the options for getting these fixes into Trusty? At this stage, with the change window on Go 1.3 closing at the end of the week, it is unlikely there will ever be a Go 1.2.2 (knock on wood). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang/+bug/1284376/+subscriptions -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to golang in Ubuntu. https://bugs.launchpad.net/bugs/1284376 Title: Go 1.2.1 will be released in early March To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang/+bug/1284376/+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 1240260] Re: juju bootstrap does not honor https_proxy in environment when fetching tools
I'm pretty sure this is fixed. ** Changed in: juju-core Milestone: None = 1.18.0 -- 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/1240260 Title: juju bootstrap does not honor https_proxy in environment when fetching tools To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1240260/+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
Re: [Bug 1273769] Re: ppc64el enablement for juju/lxc
Not yet, I had to hack my working copy. On Tue, Feb 25, 2014 at 8:46 PM, John A Meinel j...@arbash-meinel.com wrote: I'm pretty sure the arch changes haven't landed yet, right? (mapping the values of uname -m to the names we'll be using for the juju packages/tarballs) On Mon, Feb 17, 2014 at 10:02 PM, James Page james.p...@ubuntu.com wrote: ** Changed in: juju-core (Ubuntu) Status: Confirmed = Triaged -- You received this bug notification because you are subscribed to juju- core. https://bugs.launchpad.net/bugs/1273769 Title: ppc64el enablement for juju/lxc To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1273769/+subscriptions -- You received this bug notification because you are subscribed to juju- core. Matching subscriptions: MOAR JUJU SPAM! https://bugs.launchpad.net/bugs/1273769 Title: ppc64el enablement for juju/lxc Status in juju-core: Triaged Status in cloud-utils package in Ubuntu: Fix Released Status in juju-core package in Ubuntu: Triaged Status in lxc package in Ubuntu: Fix Released Bug description: After some initial testing of juju (with local provider) on ppc64el - we need todo some work to fully enable this option. 1) LXC templates need to support ppc64el as a valid container arch 2) ubuntu-cloudimg-query is not avaliable on ppc64el 3) Juju is explicit in its support for x84 and arm - so enablement work is needed here as well. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lxc 1.0.0~beta3-0ubuntu1 ProcVersionSignature: User Name 3.13.0-2.17-generic 3.13.0-rc7 Uname: Linux 3.13.0-2-generic ppc64le ApportVersion: 2.13.2-0ubuntu2 Architecture: ppc64el Date: Tue Jan 28 16:49:03 2014 ProcEnviron: TERM=screen-256color-bce PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1273769/+subscriptions -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1273769 Title: ppc64el enablement for juju/lxc To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1273769/+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 1284376] [NEW] Go 1.2.1 will be released in early March
Public bug reported: From https://groups.google.com/d/msg/golang- dev/VkSwKuEx4hY/M2FmC4xum6gJ, Go 1.2.1 will be released shortly, I heard a date of March 1, I am trying to confirm. It will contain, at this stage, these fixes 7219 database/sql: last connection in pool not handed out correctly 6987 net: ignore WSAECONNRESET AcceptEx error 6776 runtime: code text inspection confused by gdb breakpoints 6946 runtime: crash in GoroutineProfile 5139 runtime: fatal error: notewakeup - double wakeup As this is past feature freeze, what are the options for getting these fixes into Trusty? At this stage, with the change window on Go 1.3 closing at the end of the week, it is unlikely there will ever be a Go 1.2.2 (knock on wood). ** Affects: golang (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to golang in Ubuntu. https://bugs.launchpad.net/bugs/1284376 Title: Go 1.2.1 will be released in early March To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang/+bug/1284376/+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 1280919] [NEW] gccgo-go needs to be build by gccgo-4.9
Public bug reported: $ ldd /usr/bin/go linux-vdso64.so.1 = (0x3fff8767) libgo.so.4 = /usr/lib/powerpc64le-linux-gnu/libgo.so.4 (0x3fff86b04000) libgcc_s.so.1 = /lib/powerpc64le-linux-gnu/libgcc_s.so.1 (0x3fff86ae1000) libc.so.6 = /lib/powerpc64le-linux-gnu/libc.so.6 (0x3fff8692c000) libpthread.so.0 = /lib/powerpc64le-linux-gnu/libpthread.so.0 (0x3fff868fd000) libm.so.6 = /lib/powerpc64le-linux-gnu/libm.so.6 (0x3fff8682c000) /lib64/ld64.so.2 (0x46eb9000) gccgo-go is built against gccgo-4.8 and has several issues such as $ go mmap errno 19 fatal error: mmap Could this package please be rebuilt using gccgo-4.9 as a dependency. ** Affects: gccgo-go (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to gccgo-go in Ubuntu. https://bugs.launchpad.net/bugs/1280919 Title: gccgo-go needs to be build by gccgo-4.9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gccgo-go/+bug/1280919/+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 1273769] Re: ppc64el enablement for juju/lxc
** Branch linked: lp:~dave-cheney/juju-core/167-simplestreams-add-trusty -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1273769 Title: ppc64el enablement for juju/lxc To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1273769/+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
Re: [Bug 1276909] Re: error detecting hardware characteristics: unrecognised architecture: aarch64
On Fri, Feb 7, 2014 at 7:37 PM, Antonio Rosales 1276...@bugs.launchpad.netwrote: After discussion John and Dan the mapping for arm and ppc should look like: aarch64 should map to arm64 This one should be the other way around ppc64 should map to ppc64el The files affected look to be /environs/manual/init.go and scripts /release-public-tools/release-public-tools.sh -thanks, Antonio ** Changed in: juju-core Milestone: 1.18.0 = 1.17.3 -- You received this bug notification because you are subscribed to juju- core. Matching subscriptions: MOAR JUJU SPAM! https://bugs.launchpad.net/bugs/1276909 Title: error detecting hardware characteristics: unrecognised architecture: aarch64 Status in juju-core: Triaged Status in juju-core package in Ubuntu: Triaged Bug description: dannf@trusty:~$ dpkg -l juju Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---= un juju none none (no description available) dannf@trusty:~$ cat ~/.juju/environments.yaml default: manual environments: manual: type: manual bootstrap-host: bootstrap.dannf bootstrap-user: dannf dannf@trusty:~$ juju add-machine ssh:arm64.dannf ERROR error detecting hardware characteristics: unrecognised architecture: aarch64 dannf@trusty:~$ To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1276909/+subscriptions -- 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/1276909 Title: error detecting hardware characteristics: unrecognised architecture: aarch64 To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1276909/+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
Re: [Bug 1273712] Re: jujud dies on ppc64el architecture
oh dear, this is what I was afraid of
On Wed, Jan 29, 2014 at 5:45 AM, Curtis Hovey cur...@canonical.com wrote:
** Changed in: juju-core
Status: New = Triaged
** Changed in: juju-core
Importance: Undecided = High
--
You received this bug notification because you are subscribed to juju-
core.
Matching subscriptions: MOAR JUJU SPAM!
https://bugs.launchpad.net/bugs/1273712
Title:
jujud dies on ppc64el architecture
Status in juju-core:
Triaged
Status in gcc-4.8 package in Ubuntu:
New
Status in juju-core package in Ubuntu:
New
Bug description:
local provider bootstrapped ok:
juju status --debug
2014-01-28 15:02:33 INFO juju.provider.local environprovider.go:35
opening environment local
2014-01-28 15:02:34 DEBUG juju state.go:75 waiting for DNS name(s) of
state server instances [localhost]
2014-01-28 15:02:34 INFO juju apiclient.go:118 state/api: dialing wss://
10.0.3.1:17070/
2014-01-28 15:02:34 INFO juju apiclient.go:128 state/api: connection
established
environment: local
machines:
0:
agent-state: pending
dns-name: 10.0.3.1
instance-id: localhost
series: trusty
services: {}
2014-01-28 15:02:34 INFO juju.cmd supercommand.go:298 command finished
However the jujud process just keeps on exiting:
2014-01-28 15:00:39 INFO juju runner.go:262 worker: start
authenticationworker
2014-01-28 15:00:39 DEBUG juju.state.apiserver apiserver.go:102 - [1]
machine-0
{RequestId:6,Type:Logger,Request:LoggingConfig,Params:{Entities:[{Tag:machine-0}]}}
2014-01-28 15:00:39 DEBUG juju.state.apiserver apiserver.go:102 - [1]
machine-0
{RequestId:7,Type:Provisioner,Request:Life,Params:{Entities:[{Tag:machine-0}]}}
2014-01-28 15:00:39 DEBUG juju.state.apiserver apiserver.go:109 - [1]
machine-0 8.777ms
{RequestId:4,Response:{Results:[{Life:alive,Error:null}]}}
Machiner[].Life
2014-01-28 15:00:39 DEBUG juju.state.apiserver apiserver.go:102 - [1]
machine-0
{RequestId:8,Type:KeyUpdater,Request:AuthorisedKeys,Params:{Entities:[{Tag:machine-0}]}}
2014-01-28 15:00:39 DEBUG juju.state.apiserver apiserver.go:102 - [1]
machine-0
{RequestId:9,Type:Machiner,Request:SetStatus,Params:{Entities:[{Tag:machine-0,Status:started,Info:,Data:null}],Machines:null}}
panic: runtime error: growslice: cap out of range [recovered]
panic: runtime error: growslice: cap out of range
goroutine 64 [running]:
bson.handleErr
/build/buildd/juju-core-1.17.0/src/
labix.org/v2/mgo/bson/bson.go:387
launchpad.net_juju_core_version.String.N38_launchpad.net_juju_core_version.Binary
/build/buildd/juju-core-1.17.0/src/
launchpad.net/juju-core/version/version.go:75
launchpad.net_juju_core_version.GetBSON.N38_launchpad.net_juju_core_version.Binary
/build/buildd/juju-core-1.17.0/src/
launchpad.net/juju-core/version/version.go:81
labix.org_v2_mgo_bson.addElem.pN29_labix.org_v2_mgo_bson.encoder
/build/buildd/juju-core-1.17.0/src/
labix.org/v2/mgo/bson/encode.go:243
labix.org_v2_mgo_bson.addStruct.pN29_labix.org_v2_mgo_bson.encoder
/build/buildd/juju-core-1.17.0/src/
labix.org/v2/mgo/bson/encode.go:156
labix.org_v2_mgo_bson.addDoc.pN29_labix.org_v2_mgo_bson.encoder
/build/buildd/juju-core-1.17.0/src/
labix.org/v2/mgo/bson/encode.go:112
labix.org_v2_mgo_bson.addElem.pN29_labix.org_v2_mgo_bson.encoder
/build/buildd/juju-core-1.17.0/src/
labix.org/v2/mgo/bson/encode.go:400
labix.org_v2_mgo_bson.addElem.pN29_labix.org_v2_mgo_bson.encoder
/build/buildd/juju-core-1.17.0/src/
labix.org/v2/mgo/bson/encode.go:257
labix.org_v2_mgo_bson.addElem.pN29_labix.org_v2_mgo_bson.encoder
/build/buildd/juju-core-1.17.0/src/
labix.org/v2/mgo/bson/encode.go:247
labix.org_v2_mgo_bson.addSlice.pN29_labix.org_v2_mgo_bson.encoder
/build/buildd/juju-core-1.17.0/src/
labix.org/v2/mgo/bson/encode.go:210
labix.org_v2_mgo_bson.addDoc.pN29_labix.org_v2_mgo_bson.encoder
/build/buildd/juju-core-1.17.0/src/
labix.org/v2/mgo/bson/encode.go:114
labix.org_v2_mgo_bson.addElem.pN29_labix.org_v2_mgo_bson.encoder
/build/buildd/juju-core-1.17.0/src/
labix.org/v2/mgo/bson/encode.go:338
labix.org_v2_mgo_bson.addSlice.pN29_labix.org_v2_mgo_bson.encoder
/build/buildd/juju-core-1.17.0/src/
labix.org/v2/mgo/bson/encode.go:210
labix.org_v2_mgo_bson.addDoc.pN29_labix.org_v2_mgo_bson.encoder
/build/buildd/juju-core-1.17.0/src/
labix.org/v2/mgo/bson/encode.go:114
labix.org_v2_mgo_bson.addElem.pN29_labix.org_v2_mgo_bson.encoder
/build/buildd/juju-core-1.17.0/src/
labix.org/v2/mgo/bson/encode.go:338
labix.org_v2_mgo_bson.addElem.pN29_labix.org_v2_mgo_bson.encoder
/build/buildd/juju-core-1.17.0/src/
labix.org/v2/mgo/bson/encode.go:254
labix.org_v2_mgo_bson.addStruct.pN29_labix.org_v2_mgo_bson.encoder
Re: [Bug 1243762] Re: [MIR] juju-core, golang
Hi James, What do these status messages mean ? Cheers Dave On Fri, Jan 10, 2014 at 12:40 AM, James Page james.p...@ubuntu.com wrote: ** Changed in: juju-core (Ubuntu Trusty) Status: Confirmed = Won't Fix ** Changed in: golang (Ubuntu Trusty) Status: Confirmed = Won't Fix -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1243762 Title: [MIR] juju-core, golang Status in “golang” package in Ubuntu: Confirmed Status in “juju-core” package in Ubuntu: Confirmed Status in “golang” source package in Trusty: Won't Fix Status in “juju-core” source package in Trusty: Won't Fix Bug description: MIR for juju-core and toolchain for Trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang/+bug/1243762/+subscriptions -- 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/1243762 Title: [MIR] juju-core, golang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang/+bug/1243762/+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
Re: [Bug 1250007] Re: Bootstrapping azure causes memory to fill
I'm very certain this will be a bug in printing an error message who's string (Error()) routine calls itself, recursively. So it only happens during an error, and make things infinitely worse @jamespage, if you can reproduce the issue, can you hit the process with a SIGQUIT and post whatever output you can, the stack trace will point to the offending code. On Fri, Dec 13, 2013 at 5:27 AM, Curtis Hovey cur...@canonical.com wrote: We have never seen this in automated or manual testing, both of which use machines with 2-4Gs of memory. Does this happen with 1.16.5? ** Changed in: juju-core Status: New = Incomplete -- You received this bug notification because you are subscribed to juju- core. Matching subscriptions: MOAR JUJU SPAM! https://bugs.launchpad.net/bugs/1250007 Title: Bootstrapping azure causes memory to fill Status in juju-core: Incomplete Status in “juju-core” package in Ubuntu: New Bug description: When running 'juju bootstrap -e azure' my memory is completely filling up (16GB +8GB swap) within about 1-2 minutes, leaving me with an unusable system. I have also tried using the package in the ppa which I experienced the same issue. Distributor ID: Ubuntu Description: Ubuntu 13.10 Release: 13.10 Codename: saucy juju-core: Installed: 1.16.0-0ubuntu1 Candidate: 1.16.0-0ubuntu1 Version table: *** 1.16.0-0ubuntu1 0 500 http://gb.archive.ubuntu.com/ubuntu/ saucy/universe amd64 Packages 500 http://archive.ubuntu.com/ubuntu/ saucy/universe amd64 Packages 100 /var/lib/dpkg/status Is there any specific logs you need with this bug report?? If so i will get those to you asap. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: juju 1.16.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Mon Nov 11 09:28:09 2013 Dependencies: gcc-4.8-base 4.8.1-10ubuntu8 juju-core 1.16.0-0ubuntu1 libc6 2.17-93ubuntu4 libgcc1 1:4.8.1-10ubuntu8 multiarch-support 2.17-93ubuntu4 InstallationDate: Installed on 2013-10-28 (13 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True PackageArchitecture: all SourcePackage: juju-core UpgradeStatus: Upgraded to saucy on 2013-11-10 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1250007/+subscriptions -- 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/1250007 Title: Bootstrapping azure causes memory to fill To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1250007/+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
Re: [Bug 1241666] Re: Cannot create simple streams for Ubuntu trusty series
Matt, what version of the juju client are you running ? juju version will tell you. I think you are using 1.16.0, you should use a newer version. On Wed, Nov 13, 2013 at 4:14 PM, Matt Rae 1241...@bugs.launchpad.net wrote: running into the same error with juju -v bootstrap: $ juju -v bootstrap verbose is deprecated with the current meaning, use show-log 2013-11-13 05:07:24 INFO juju.environs open.go:156 environment info already exists; using New not Prepare 2013-11-13 05:07:25 INFO juju.environs.tools tools.go:181 filtering tools by released version 2013-11-13 05:07:25 INFO juju.environs.tools tools.go:85 reading tools with major.minor version 1.16 2013-11-13 05:07:25 INFO juju.environs.tools tools.go:96 filtering tools by series: precise 2013-11-13 05:07:26 WARNING juju.cmd.juju bootstrap.go:204 no tools available, attempting to retrieve from https://juju-dist.s3.amazonaws.com/ 2013-11-13 05:07:26 INFO juju.environs.sync sync.go:66 listing available tools listing available tools 2013-11-13 05:07:27 INFO juju.environs.sync sync.go:90 found 34 tools found 34 tools 2013-11-13 05:07:27 INFO juju.environs.sync sync.go:94 found 13 recent tools (version 1.16.3) found 13 recent tools (version 1.16.3) 2013-11-13 05:07:27 INFO juju.environs.sync sync.go:100 listing target bucket listing target bucket 2013-11-13 05:07:45 INFO juju.environs.sync sync.go:113 found 13 tools in target; 0 tools to be copied found 13 tools in target; 0 tools to be copied 2013-11-13 05:07:45 INFO juju.environs.sync sync.go:118 copied 0 tools copied 0 tools 2013-11-13 05:07:45 INFO juju.environs.sync sync.go:120 generating tools metadata generating tools metadata 2013-11-13 05:07:46 INFO juju.environs.tools simplestreams.go:293 Fetching tools to generate hash: http://10.0.0.4/MAAS/api/1.0/files/?key=fc0e8c4e-4c20-11e3-b375-525400c5247eop=get_by_key 2013-11-13 05:07:47 INFO juju.environs.tools simplestreams.go:293 Fetching tools to generate hash: http://10.0.0.4/MAAS/api/1.0/files/?key=fe8c5cee-4c20-11e3-b375-525400c5247eop=get_by_key 2013-11-13 05:07:48 INFO juju.environs.tools simplestreams.go:293 Fetching tools to generate hash: http://10.0.0.4/MAAS/api/1.0/files/?key=01545db4-4c21-11e3-b375-525400c5247eop=get_by_key 2013-11-13 05:07:48 INFO juju.environs.tools simplestreams.go:293 Fetching tools to generate hash: http://10.0.0.4/MAAS/api/1.0/files/?key=67218400-4c17-11e3-b375-525400c5247eop=get_by_key 2013-11-13 05:07:49 INFO juju.environs.tools simplestreams.go:293 Fetching tools to generate hash: http://10.0.0.4/MAAS/api/1.0/files/?key=03b0c336-4c21-11e3-b375-525400c5247eop=get_by_key 2013-11-13 05:07:50 INFO juju.environs.tools simplestreams.go:293 Fetching tools to generate hash: http://10.0.0.4/MAAS/api/1.0/files/?key=6c28b6b2-4c17-11e3-b375-525400c5247eop=get_by_key 2013-11-13 05:07:50 INFO juju.environs.tools simplestreams.go:293 Fetching tools to generate hash: http://10.0.0.4/MAAS/api/1.0/files/?key=062cf832-4c21-11e3-b375-525400c5247eop=get_by_key 2013-11-13 05:07:51 INFO juju.environs.tools simplestreams.go:293 Fetching tools to generate hash: http://10.0.0.4/MAAS/api/1.0/files/?key=08e1d6a6-4c21-11e3-b375-525400c5247eop=get_by_key 2013-11-13 05:07:51 INFO juju.environs.tools simplestreams.go:293 Fetching tools to generate hash: http://10.0.0.4/MAAS/api/1.0/files/?key=0b63deb0-4c21-11e3-a44c-525400c5247eop=get_by_key 2013-11-13 05:07:52 INFO juju.environs.tools simplestreams.go:293 Fetching tools to generate hash: http://10.0.0.4/MAAS/api/1.0/files/?key=0fd07d3c-4c21-11e3-a44c-525400c5247eop=get_by_key 2013-11-13 05:07:53 INFO juju.environs.tools simplestreams.go:293 Fetching tools to generate hash: http://10.0.0.4/MAAS/api/1.0/files/?key=126cbf74-4c21-11e3-a44c-525400c5247eop=get_by_key 2013-11-13 05:07:53 INFO juju.environs.tools simplestreams.go:293 Fetching tools to generate hash: http://10.0.0.4/MAAS/api/1.0/files/?key=14fdadf2-4c21-11e3-a44c-525400c5247eop=get_by_key 2013-11-13 05:07:54 INFO juju.environs.tools simplestreams.go:293 Fetching tools to generate hash: http://10.0.0.4/MAAS/api/1.0/files/?key=176c84d2-4c21-11e3-a44c-525400c5247eop=get_by_key 2013-11-13 05:07:54 ERROR juju supercommand.go:282 invalid series trusty $ apt-cache policy juju juju: Installed: 1.16.0-0ubuntu1~ctools1 Candidate: 1.16.0-0ubuntu1~ctools1 Version table: *** 1.16.0-0ubuntu1~ctools1 0 500 http://ubuntu-cloud.archive.canonical.com/ubuntu/ precise-updates/cloud-tools/main amd64 Packages 100 /var/lib/dpkg/status 0.5+bzr531-0ubuntu1.3 0 500 http://10.0.0.1/ubuntu/ precise-updates/universe amd64 Packages 500 http://10.0.0.1/ubuntu/ precise-security/universe amd64 Packages 0.5+bzr531-0ubuntu1 0 500 http://10.0.0.1/ubuntu/ precise/universe amd64 Packages -- You received this bug notification because you are subscribed to juju- core. Matching subscriptions: MOAR
[Bug 1243762] Re: [MIR] juju-core, golang
Go 1.2 will be released 1 December. When that happens the 1.1 series will be EOL. Is it possible to have 1.2 included in Trusty ? -- 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/1243762 Title: [MIR] juju-core, golang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang/+bug/1243762/+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
Re: [Bug 1242237] Re: Mongodb server ignores --smallfiles if other paramethers are set in the command line
HA! Ja'cuse Mongo! I always suspected something like this was
happening, thanks for confirming Kapil.
On Tue, Oct 22, 2013 at 12:38 AM, Kapil Thangavelu
1242...@bugs.launchpad.net wrote:
** Also affects: juju-core
Importance: Undecided
Status: New
--
You received this bug notification because you are subscribed to juju-
core.
Matching subscriptions: MOAR JUJU SPAM!
https://bugs.launchpad.net/bugs/1242237
Title:
Mongodb server ignores --smallfiles if other paramethers are set in
the command line
Status in juju-core:
New
Status in “mongodb” package in Ubuntu:
New
Bug description:
I've found out that while `mongodb --smallfiles --conf=something`
makes mongodb actually using small files, while something more large
like `/usr/bin/mongod --auth --dbpath=/home/braiam/.juju/local/db
--sslOnNormalPorts --sslPEMKeyFile
'/home/braiam/.juju/local/server.pem' --sslPEMKeyPassword ignored
--bind_ip 0.0.0.0 --port 37017 --noprealloc --syslog --smallfiles`
completely fails with the following log:
Oct 20 02:41:05 vm-2 mongod.37017[5159]: Sun Oct 20 02:41:05
[initandlisten] options: { auth: true, bind_ip: 0.0.0.0, dbpath:
/home/braiam/.juju/local/db, noprealloc: true, port: 37017, smallfiles:
true, sslOnNormalPorts: true, sslPEMKeyFile:
/home/braiam/.juju/local/server.pem, sslPEMKeyPassword: password,
syslog: true }
Oct 20 02:41:05 vm-2 mongod.37017[5159]: Sun Oct 20 02:41:05
[initandlisten] journal dir=/home/braiam/.juju/local/db/journal
Oct 20 02:41:05 vm-2 mongod.37017[5159]: Sun Oct 20 02:41:05
[initandlisten] recover : no journal files present, no recovery needed
Oct 20 02:41:05 vm-2 mongod.37017[5159]: Sun Oct 20 02:41:05 [initandlisten]
Oct 20 02:41:05 vm-2 mongod.37017[5159]: Sun Oct 20 02:41:05
[initandlisten] ERROR: Insufficient free space for journal files
Oct 20 02:41:05 vm-2 mongod.37017[5159]: Sun Oct 20 02:41:05
[initandlisten] Please make at least 422MB available in
/home/braiam/.juju/local/db/journal or use --smallfiles
Oct 20 02:41:05 vm-2 mongod.37017[5159]: Sun Oct 20 02:41:05 [initandlisten]
Oct 20 02:41:05 vm-2 mongod.37017[5159]: Sun Oct 20 02:41:05
[initandlisten] exception in initAndListen: 15926 Insufficient free space for
journals, terminating
This of course should happen if the `--smallfiles` parameter is
passed.
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: mongodb-server 1:2.2.4-0ubuntu1
ProcVersionSignature: Ubuntu 3.9.0-0.4userns5-generic 3.9.0
Uname: Linux 3.9.0-0-generic x86_64
NonfreeKernelModules: atm xt_recent ipt_REJECT xt_LOG xt_limit xt_tcpudp
xt_addrtype xt_state iptable_filter bluetooth veth aufs ebt_ip ebtable_broute
ebtable_nat ebtable_filter ebtables ipt_MASQUERADE iptable_nat
nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack ip_tables
x_tables bridge stp llc ip_gre gre dm_crypt psmouse microcode i2c_piix4
joydev serio_raw mac_hid rbd virtio_balloon libceph libcrc32c acpiphp
hid_generic usbhid hid crc32_pclmul ghash_clmulni_intel aesni_intel
aes_x86_64 xts lrw gf128mul ablk_helper cryptd floppy cirrus syscopyarea
sysfillrect sysimgblt ttm drm_kms_helper drm
ApportVersion: 2.9.2-0ubuntu8.3
Architecture: amd64
Date: Sun Oct 20 02:56:51 2013
MarkForUpload: True
ProcEnviron:
TERM=screen
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: mongodb
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1242237/+subscriptions
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mongodb in Ubuntu.
https://bugs.launchpad.net/bugs/1242237
Title:
Mongodb server ignores --smallfiles if other paramethers are set in
the command line
To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1242237/+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
[Blueprint servercloud-s-juju-2-delivery] Delivering Juju 2.0 into Ubuntu
Blueprint changed by Dave Cheney: Work items changed: Work items for ubuntu-13.06: + Get Go 1.1 into the archive: TODO + [dave-cheney] verify that Juju works with gccgo: TODO Upload juju-core point release: TODO Work items for ubuntu-13.07: Upload juju-core point release: 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 Backport juju-core to 12.04, 12.10 and 13.04: TODO Work items: Investigate automated releases of juju-core into Ubuntu: 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 802117] Re: juju ssh/scp commands cause spurious key errors, should use a different known_hosts file
** Changed in: juju-core Milestone: 1.9.7 = None -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/802117 Title: juju ssh/scp commands cause spurious key errors, should use a different known_hosts file To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/802117/+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 802117] Re: juju ssh/scp commands cause spurious key errors, should use a different known_hosts file
** Changed in: juju-core Status: Confirmed = Triaged ** Changed in: juju-core Milestone: 1.9.6 = 1.9.7 ** Changed in: juju-core Assignee: Dave Cheney (dave-cheney) = (unassigned) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/802117 Title: juju ssh/scp commands cause spurious key errors, should use a different known_hosts file To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/802117/+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 802117] Re: juju ssh/scp commands cause spurious key errors, should use a different known_hosts file
** Changed in: juju-core Milestone: 1.9.5 = 1.9.6 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/802117 Title: juju ssh/scp commands cause spurious key errors, should use a different known_hosts file To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/802117/+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 802117] Re: juju ssh/scp commands cause spurious key errors, should use a different known_hosts file
** Changed in: juju-core Milestone: 1.9.4 = 1.9.5 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/802117 Title: juju ssh/scp commands cause spurious key errors, should use a different known_hosts file To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/802117/+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 802117] Re: juju ssh/scp commands cause spurious key errors, should use a different known_hosts file
Yes, we should do this. ** Changed in: juju-core Milestone: None = 1.9.4 ** Changed in: juju-core Assignee: (unassigned) = Dave Cheney (dave-cheney) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/802117 Title: juju ssh/scp commands cause spurious key errors, should use a different known_hosts file To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/802117/+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 1078213] Re: juju-machine-agent.log/logs are not logrotated
** Changed in: juju-core Milestone: None = 2.0 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/1078213 Title: juju-machine-agent.log/logs are not logrotated To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1078213/+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
