** Tags removed: blocker
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1494441
Title:
ppc64el: cannot find package "encoding"
To manage notifications about this bug go to:
https://bugs.launchpad.ne
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 => Inv
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
I can confirm that when upgraded to
Linux rugby 3.13.0-52-generic #86-Ubuntu SMP Mon May 4 04:34:50 UTC 2015
aarch64 aarch64 aarch64 GNU/Linux
The oops has gone away. I think this can be marked as closed/fixed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
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
Bugs, which is subscribed to Ubu
Robie, do you have permissions to target this bug to W only?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1452457
Title:
Please import golang-1.4.2 from debian/sid
To manage notifications about th
HI Brad,
I don't have sudo permission on rugby, I cannot run this command. Can
you ?
rugby(~) % apport-collect 1448811
You need to run 'sudo apt-get install python-apport' for apport-collect to work.
On Mon, Apr 27, 2015 at 10:30 AM, Brad Figg wrote:
> This bug is missing log files that will ai
Public bug reported:
We have an arm64 xgene system running 14.04.1 which leaks processes when
the kernel oopses
[928109.838289] Unable to handle kernel paging request at virtual address
42083b48a0
[928109.845776] pgd = ffc00a50b000
[928109.849254] [42083b48a0] *pgd=00420bb45003, *pmd=000
The fix for gccgo-5 has landed upstream
https://gcc.gnu.org/viewcvs/gcc?view=revision&revision=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
I have confirmed that the bug was fixed upstream with revision
https://gcc.gnu.org/viewcvs/gcc?view=revision&revision=221643
@doko, is it possible to get this patch into V ?
On Wed, Mar 25, 2015 at 10:32 AM, Bug Watch Updater
<1432...@bugs.launchpad.net> wrote:
> Launchpad has imported 9 comment
Upstream issue https://github.com/golang/go/issues/10217
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1432497
Title:
/usr/bin/go-5 does not recursively go get packages
To manage notifications abou
After a lot of assing about today I have been able to verify that the
problem exists in the upstream gccgo branch (from the gcc svn server).
This isn't a bug in out packaging.
That said, I have no idea what the bug is yet, but at least I know
where to look.
On Mon, Mar 16, 2015 at 10:28 PM, David
Yes this is different to go 1.4.2.
Yes, I will file a bug upstream.
Yes, this was tested in a march 11 2015 vivid server install
On Mon, Mar 16, 2015 at 9:55 PM, Matthias Klose wrote:
> is this different than with golang 1.4.2? If yes, please could you file
> a bug report upstream? Also please
Public bug reported:
The version of the Go tool shipped with gccgo 5.0 does not correctly
recursively download dependencies of a package
dfc@ubuntu:~$ dpkg -S $(which go-5)
gccgo-5: /usr/bin/go-5
dfc@ubuntu:~$ go get -u -v -d github.com/juju/juju/...
github.com/juju/juju (download)
This is wrong
The attached patch for gccgo-1.2.1~ubuntu1 ensures that the external
test package is always presented to the linker before the internal test
package.
Tested against juju/juju 1.23 (something) by building and running all
tests.
No linking failures during the test run
** Patch added:
"1425788-pla
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1392094
Title:
golang is unava
** Changed in: juju-core
Status: Triaged => Fix Committed
** Changed in: gcc-4.9 (Ubuntu)
Status: In Progress => Invalid
** Changed in: juju-core
Assignee: (unassigned) => Dave Cheney (dave-cheney)
--
You received this bug notification because you are a member of Ub
** Branch linked: lp:~dave-cheney/goose/100-more-gccgo-fixes
** Changed in: gcc-4.9 (Ubuntu)
Status: Confirmed => In Progress
** Changed in: gcc-4.9 (Ubuntu)
Assignee: (unassigned) => Dave Cheney (dave-cheney)
--
You received this bug notification because you are a member of
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
Bugs, which is subscr
Public bug reported:
Upstream bug report
https://code.google.com/p/go/issues/detail?id=8612
** Affects: gccgo-4.9 (Ubuntu)
Importance: Undecided
Status: Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
Fixed upstream https://groups.google.com/d/topic/gofrontend-
dev/rit51azZQU8/discussion in the 4.9 branch and trunk
** Changed in: gccgo-4.9 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
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 bina
This new failure looks different (based on the dmesg output), please
open a new issue.
On Wed, Jul 23, 2014 at 8:36 AM, Matt Bruzek
wrote:
> ** Attachment added: "the dmesg output from stilson-01 with version 1.18.1
> installed."
>
> https://bugs.launchpad.net/ubuntu/+source/gccgo-4.9/+bug/1
Hi Matt,
Can you please post the output of dmesg, that is the canonical way to
diagnose this issue atm.
On Thu, Jul 10, 2014 at 5:23 AM, Matt Bruzek
wrote:
> I installed the debian packages from the CI server
> http://juju-ci.vapour.ws:8080/job/publish-revision/588/
> My understanding is these
Matthias, I've tested this fix with Juju and it looks like it has fixed
the problem with 64k kernels.
I've moved this to fix committed, I hope this is the correct status.
** Changed in: gccgo-4.9 (Ubuntu Trusty)
Status: Confirmed => Fix Committed
--
You received this bug notification bec
I've been testing this, it's looking good so far. I'd like to run one
more test overnight before giving a thumbs up/down.
On Sun, May 4, 2014 at 2:29 PM, Launchpad Bug Tracker
<1304...@bugs.launchpad.net> wrote:
> ** Branch linked: lp:debian/gcc-4.9
>
> --
> You received this bug notification beca
An excellent point. Timers are managed by a single goroutine and a
priority queue of events to wait on and channels to send the timer
event. It should be doable to write some code that stresses timers.
However I don't believe that SIGALARM is used, well at least not in gc
which most of the gccgo s
Hi Anton,
I've been looking at another angle via a different crash. I see a
crash if a child process gets a signal, which sort of reflects back on
the parent.
Are there any alignment requirements for signal handling on 64k kernels
?
Dave
On Wed, Apr 16, 2014 at 4:28 PM, Anton Blanchard wrote:
On Wed, Apr 16, 2014 at 4:26 PM, Anton Blanchard wrote:
> I've made some progress with these fails. A lot of the confusion is
> around the way gccgo hooks the SEGV handler and attempts to backtrace
> all goroutines (the code is in runtime_tracebackothers())
>
> It does this by calling runtime_gogo
Anton:
I've done some experiments with the peano.go test and confirmed that
gccgo on ppc is correctly configured to not use f-split-stack. It turns
out the peano.go can't pass without split stacks. On gccgo/ppc64 the
program crashes at a stack depth of
Program received signal SIGSEGV, Segmentati
Look in dmesg, it'll tell you what is failing.
On Fri, Apr 11, 2014 at 2:03 PM, Curtis Hovey wrote:
> ** Changed in: juju-core
> Milestone: None => 1.19.0
>
> --
> You received this bug notification because you are subscribed to juju-
> core.
> Matching subscriptions: MOAR JUJU SPAM!
> https:
Thanks Anton, this is great debugging.
I tried the peano experiment on my -8 (4k) kernel and it failed as
expected.
I talked to the upstream who said that ./configure should detect that
-fsplit-stack isn't supported on PPC and fall back to giving each
goroutine a full stack.
I will investigate t
See also, https://bugs.launchpad.net/juju-core/+bug/1303787
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1304754
Title:
gccgo compiled binaries are killed by SEGV on 64k ppc64el kernels
To manage
Public bug reported:
On kernels 3.13-18 and 3.13-23 (there may be others) the kernel is
killing gccgo compiled binaries
[18519.444748] jujud[19277]: bad frame in setup_rt_frame:
nip lr
[18519.673632] init: juju-agent-ubuntu-local main process (19
Public bug reported:
sudo apt-get install lxc -y
Setting up lxc (1.0.2-0ubuntu2) ...
AppArmor parser error for /etc/apparmor.d/lxc-containers in
/etc/apparmor.d/abstractions/lxc/container-base at line 6: syntax error,
unexpected TOK_END_OF_RULE, expecting TOK_MODE
AppArmor parser error for /etc
Awesome!
On Mon, Mar 31, 2014 at 12:54 PM, Michael Hudson-Doyle
wrote:
> Hi, this looks like this bug:
> https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1279620. I'll be
> posting libc debs to try with soon.
>
> --
> You received this bug notification because you are subscribed to juju-
>
** 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/1289067
Title:
arm64 multiple definition of `launchpad.net_juju_core_cmd._.0
To manage
m was later than the patch we applied
Then the patch for this issue
https://codereview.appspot.com/download/issue80300043_60001.diff
will apply cleanly.
** Changed in: gccgo-go (Ubuntu)
Status: New => In Progress
** Changed in: gccgo-go (Ubuntu)
Assignee: (unassigned) =>
** Changed in: juju-core
Milestone: 1.20.0 => 1.18.0
** Changed in: juju-core
Assignee: (unassigned) => Dave Cheney (dave-cheney)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1289067
Apparently if I put this link
https://code.google.com/p/go/issues/detail?id=7627
in the bug report, magic gnomes spring into action.
** Bug watch added: Go Issue Tracker #7627
http://code.google.com/p/go/issues/detail?id=7627
--
You received this bug notification because you are a member of
For those playing along at home, the issue is triggered by launchpad.net
/juju-core/agent (to name one) using _external_ testing, not internal
testing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/128
This afternoon I confirmed that even with the latest cmd/go from the
upstream trunk this error still occurs, and still occurs on all
platforms, even amd64, not just gccgo only platforms.
The underlying cause is duplicate symbols being present, essentially the
package under test is compiled twice,
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
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 wrote:
> ** 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.launchpa
Public bug reported:
See https://bugs.launchpad.net/juju-core/+bug/1292353
gccgo compiled Go programs are not stand alone, they required the
runtime libgo.so.5 library.
This library is currently distributed with gccgo-4.9 which itself has
many dependencies on various gcc components.
Is it possi
Committed
** Changed in: juju-core
Assignee: (unassigned) => Dave Cheney (dave-cheney)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1273769
Title:
ppc64el enablement for juju/lxc
To manage
On Fri, Mar 14, 2014 at 5:59 AM, Mark Ramm
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 notificati
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
Public bug reported:
Could you please import this important bug fix
https://groups.google.com/d/msg/gofrontend-dev/_1zJwofY85w/v3PzdR2rYKIJ
or pull it from mainline.
** Affects: gccgo-4.9 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because yo
Confirmed. Thanks for turning around a fix so quickly
On Tue, Mar 4, 2014 at 8:39 PM, Matthias Klose wrote:
> fixed in 4.9-20140303-0ubuntu2
>
>
> ** Changed in: gccgo-4.9 (Ubuntu)
>Status: Confirmed => Fix Released
>
> --
> You received this bug notification because you are subscribed to
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1240260
Title:
juju bootstrap does not honor https_proxy in envir
** Changed in: gcc-defaults (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1285946
Title:
gccgo compiled packages issue warnings during assembly
To manage noti
Public bug reported:
Compiling packages using gccgo-go, so gccgo-4:4.9 produces warning
messages during compilation
eg.
# launchpad.net/juju-core/state/apiserver
/tmp/ccTOvYAn.s: Assembler messages:
/tmp/ccTOvYAn.s:31003: Warning: setting incorrect section attributes for
.rodata.__go_tdn_launch
Public bug reported:
Compiling packages using gccgo-go, so gccgo-4:4.9 produces warning
messages during compilation
eg.
# launchpad.net/juju-core/state/apiserver
/tmp/ccTOvYAn.s: Assembler messages:
/tmp/ccTOvYAn.s:31003: Warning: setting incorrect section attributes for
.rodata.__go_tdn_launch
** Changed in: gccgo-go (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1275620
Title:
gccgo-go segfaults, something related to alternatives
To ma
Not yet, I had to hack my working copy.
On Tue, Feb 25, 2014 at 8:46 PM, John A Meinel 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
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
69
Oh dear, same problem with gccgo-go 4.9
ubuntu@juju-hp-machine-1:~$ go get -v launchpad.net/juju-core/...
Segmentation fault (core dumped)
full path and it works
ubuntu@juju-hp-machine-1:~$ /usr/bin/go get -v launchpad.net/juju-core/...
launchpad.net/juju-core (download)
ii gccgo
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/powerpc6
** Branch linked: lp:~dave-cheney/juju-core/167-simplestreams-add-trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1273769
Title:
ppc64el enablement for juju/lxc
To manage notifications about
On Fri, Feb 7, 2014 at 7:37 PM, Antonio Rosales
<1276...@bugs.launchpad.net>wrote:
> 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
Public bug reported:
When executed via $PATH, ie
$ go
The command segfaults during an early mmap operation
futex(0x3fffabd2a49c, FUTEX_WAKE_PRIVATE, 2147483647) = 0
open("go", O_RDONLY|O_CLOEXEC) = 3
fcntl(3, F_SETFD, FD_CLOEXEC) = 0
mmap(NULL, 4096, PROT_READ, MAP_PRIVATE
oh dear, this is what I was afraid of
On Wed, Jan 29, 2014 at 5:45 AM, Curtis Hovey 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-
>
I'm trying really hard to get these upstreamed, really.
On Wed, Jan 22, 2014 at 8:39 AM, Michael Hudson-Doyle <
michael.hudson...@canonical.com> wrote:
> Public bug reported:
>
> Hi,
>
> There have been some patches to the go tool floating around that make it
> work better with gccgo and we shou
Hi James,
What do these status messages mean ?
Cheers
Dave
On Fri, Jan 10, 2014 at 12:40 AM, James Page wrote:
> ** Changed in: juju-core (Ubuntu Trusty)
>Status: Confirmed => Won't Fix
>
> ** Changed in: golang (Ubuntu Trusty)
>Status: Confirmed => Won't Fix
>
> --
> You rec
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 outp
I'm working with the upstream to resolve this issue, but I think it may not
be a super fast resolution.
How do I go about requesting this new package be bought into the archive
for T ?
On Thu, Dec 12, 2013 at 5:47 PM, James Henstridge <
james.henstri...@canonical.com> wrote:
> Looking at the pa
https://code.google.com/p/go/issues/detail?id=6927
** Bug watch added: Go Issue Tracker #6927
http://code.google.com/p/go/issues/detail?id=6927
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1259414
I think this is a bug upstream which has flowed down in debian.
godoc moved into an external repository in 1.2, but *should* have been
included in the src tarball.
Rasing issue upstream.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
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 bootst
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1243762
Title:
[MIR] j
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 n
We worked around the problem.
** Changed in: juju-core
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1197326
Title:
environs/ec2: juju 1.11.2 cannot bootstrap whe
Go 1.1.2 has been released.
https://groups.google.com/d/msg/golang-nuts/6kBXPSm-awo/QwOC_EUKMdYJ
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1202027
Title:
go version 1.1.2 will be released on Au
Mine must be out of date,
alarm(~) % objdump -v
GNU objdump (GNU Binutils) 2.23.1
On Fri, Jul 19, 2013 at 5:16 PM, Robie Basak <1187...@bugs.launchpad.net> wrote:
> What version objdump are you using? I get:
>
> private flags = 5000402: [Version5 EABI] [hard-float ABI] [has entry
> point]
>
> GNU
umm, re that patch, objdump says
private flags = 5000402: [Version5 EABI] [has entry point]
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1187722
Title:
dpkg-shlibdeps fails on armhf ELF binaries t
yup, i'll take care of that upstream.
https://codereview.appspot.com/11485045
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1187722
Title:
dpkg-shlibdeps fails on armhf ELF binaries that do not defi
Excellent. Thanks for getting this sorted.
On Thu, Jul 18, 2013 at 12:44 AM, Bug Watch Updater
<1200...@bugs.launchpad.net> wrote:
> ** Changed in: golang (Debian)
>Status: Unknown => New
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://
Public bug reported:
Go version 1.1.2 will be released on August 13th.
https://groups.google.com/d/msg/golang-dev/X5Wf2lA47-8/GdET1npH1gEJ
1.1.2 will include several compiler fixes, which fortunately we haven't
needed yet on Juju, but Murphys law says we will need them the day after
the Saucy re
To clarify my previous statements.
* I do not disagree with the debian policy, it is there for a good reason
* Having said that, it stripping Go binaries doesn't work, and nobody is
looking at making it work, so there is that.
Thanks for patching the build formula.
--
You received this bug not
We are stripping the binaries.
alarm(~) % file ./go.1
./go.1: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV),
dynamically linked (uses shared libs), stripped
That is why it falis.
On Tue, Jul 16, 2013 at 12:46 AM, Robie Basak
<1200...@bugs.launchpad.net> wrote:
> go binary from saucy at
To quote myself: "Please do not strip Go binaries, it is not
supported, not tested, is often broken, and doesn't do what you want"
To unpack that a bit
* not supported, as in, we don't support it, and recommend against it when asked
* not tested, we don't test stripped binaries as part of the bui
It'll take me a while to reproduce this build environment. My pandaboard
does not run saucy. Can anyone provide me with the binary and .core file
?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1200255
I'm guessing either
a. it really is an illegal instruction, but that is unlikely
b. unaligned dword mul or something like that
can you please, a upload the juju binary and i'll try it on my machine,
or the binary and the core dump, or at least the gdb backtrace and
disasm.
c. outside possibility
I'll hold this bug. I believe a fix is going to land upstream soon.
We'll figure out how to backport it then.
** Changed in: golang (Ubuntu)
Assignee: (unassigned) => Dave Cheney (dave-cheney)
--
You received this bug notification because you are a member of Ubuntu
B
Public bug reported:
Go 1.1.1 was released a week ago. Like all .1 releases, it's the one you
want. We need this for Juju, specifically juju on arm.
https://groups.google.com/d/msg/golang-nuts/iJFhI8K5a2Y/ICf4fVqg3yEJ
It isn't available in upstream yet, and I haven't had any luck enticing
the up
*** This bug is a duplicate of bug 1140716 ***
https://bugs.launchpad.net/bugs/1140716
I believe this is a regression in 3.5.0-27-generic, this didn't happen
on my X220 with 3.5.0-25-generic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Still happens in 12.10 ~ Feb 1 2013 with all updates applied. Appears to
be related to the amount of data buffered to be written to the USB
device.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/859539
This happens for me as well, possibly related to
https://bugs.launchpad.net/ubuntu/+source/usb-creator/+bug/859539
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1072760
Title:
coredump during bootlo
** Changed in: juju-core
Milestone: 1.9.7 => None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/802117
Title:
juju ssh/scp commands cause spurious key errors, should use a
different known_host
** 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
Bugs,
** Changed in: juju-core
Milestone: 1.9.5 => 1.9.6
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/802117
Title:
juju ssh/scp commands cause spurious key errors, should use a
different known_hos
** Changed in: juju-core
Milestone: 1.9.4 => 1.9.5
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/802117
Title:
juju ssh/scp commands cause spurious key errors, should use a
different known_hos
** Changed in: juju-core
Milestone: None => 2.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1078213
Title:
juju-machine-agent.log/logs are not logrotated
To manage notifications about this bu
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
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Using 3.4.0-201-omap4 (from the alpha-2 sdcard image) the serial console
worked fine on my pandaboard.
On upgrading to 3.4.0-202-omap4, the last thing heard from the serial
console is "booting the kernel".
No getty, no login, nada.
The host is working fine and accessible ov
Public bug reported:
Host: pandaboard (OMAP4)
OS: 12.04 LTS Server -> 12.10 Alpha 1
Since upgrading dmesg is full of these lines
[ 389.288543] ti_hdmi_4xxx_phy_enable: hotplug absent after delay
[ 400.632293] ti_hdmi_4xxx_phy_enable: hotplug absent after delay
[ 411.976043] ti_hdmi_4xxx_phy_e
I am glad to confirm that
% grep GRUB_CMDLINE_LINUX_DEFAULT /etc/default/grub
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash intel_idle.max_cstate=3 nohpet"
allows my S10-3 to wake from sleep under 12.04.LTS/amd64
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
98 matches
Mail list logo
