Cheers,
> Nicolino.
>
>
>
>
>
> Il 29/03/2017 22:00, Michael Hudson-Doyle ha scritto:
> >
> > This should be fixed in the latest edge version of the core snap. Let me
> > know how it goes if you try it!
> >
> > Cheers,
> > mwh
>
>
>
> --
>
On 28 March 2017 at 15:58, Michael Hudson-Doyle <
michael.hud...@canonical.com> wrote:
>
>
> On 28 March 2017 at 10:38, Michael Hudson-Doyle <
> michael.hud...@canonical.com> wrote:
>
>>
>>
>> On 28 March 2017 at 02:50, Nicolino Curalli wrote:
>&
On 28 March 2017 at 10:38, Michael Hudson-Doyle <
michael.hud...@canonical.com> wrote:
>
>
> On 28 March 2017 at 02:50, Nicolino Curalli wrote:
>
>> Hi all,
>>
>> we have a strange output on console after the first boot: the first boot
>> go straig
On 28 March 2017 at 02:50, Nicolino Curalli wrote:
> Hi all,
>
> we have a strange output on console after the first boot: the first boot
> go straight without any traceback.
>
> We use our kernel snap on a orangepi plus 2e board (kernel 4.9).
>
> The traceback is the following:
>
>
> [ OK ] Re
On 14 March 2017 at 23:56, John Lenton wrote:
> As a followup, I added a mutex around pthread_create, and around the
> exec syscall, and the problem went away. This all in go's runtime; not
> a huge diff but they probably don't want the overhead (and that seems
> reasonable to me).
> Next I'm goi
On 14 March 2017 at 12:21, John Lenton wrote:
> On 13 March 2017 at 21:05, Michael Hudson-Doyle
> wrote:
> > If I add a
> > time.Sleep(1*time.Millisecond) to a_go.go before the exec, the setuid bit
> > is respected every time.
>
> on my way to bed, I'll give
On 14 March 2017 at 10:05, Michael Hudson-Doyle <
michael.hud...@canonical.com> wrote:
>
>
> On 14 March 2017 at 01:59, John Lenton wrote:
>
>> This one is slightly more interesting.
>>
>> You need 1.8 (or patched <1.8 as per the previous thread) for this
On 14 March 2017 at 01:59, John Lenton wrote:
> This one is slightly more interesting.
>
> You need 1.8 (or patched <1.8 as per the previous thread) for this one
> to make sense; without it you're just going to get drowned in warning
> messages and not see the real issue.
>
> This one is the real
PS: I guess I should back port that Go fix to all supported Go releases?
On 12 March 2017 at 21:37, Michael Hudson-Doyle <
michael.hud...@canonical.com> wrote:
> Before we get into this, what is the actual problem here? Just the ugly
> messages?
>
> On 11 March 2017 at 02:5
Before we get into this, what is the actual problem here? Just the ugly
messages?
On 11 March 2017 at 02:58, Alfonso Sanchez-Beato <
alfonso.sanchez-be...@canonical.com> wrote:
> On Fri, Mar 10, 2017 at 10:22 AM, John Lenton
> wrote:
>
> > Hello!
> >
> > We're seeing a weird issue with either go
On 6 March 2017 at 02:48, Sergio Schvezov
wrote:
> On Tue, Feb 28, 2017 at 6:11 PM, Michael Hudson-Doyle <
> michael.hud...@canonical.com> wrote:
>
>> Hi,
>>
>> The magic of classic confinement snaps is all in passing special flags
>> when linking a
On 10 February 2017 at 19:16, Simon Fels wrote:
> On 10.02.2017 01:44, Michael Hudson-Doyle wrote:
> > Very much inspired by debdiff, I wrote a little script to compare two
> > snaps. It looks like this:
> >
> > (master)mwhudson@aeglos:/opt/opensource/snaps/go$ snapdif
Hi,
The magic of classic confinement snaps is all in passing special flags when
linking an executable. If I've read things right, snapcraft does this by
wrapping any command you execute with BasePlugin.run() with some shell code
that sets LDFLAGS.
Unfortunately, for the go classic snap the underl
On 7 February 2017 at 09:25, Michael Hudson-Doyle <
michael.hud...@canonical.com> wrote:
>
> I think this makes sense as a way to distribute Go to people who want to
> use Go on their machines. I maintain a PPA with backports of new versions
> of Go to older releases of Ubu
Very much inspired by debdiff, I wrote a little script to compare two
snaps. It looks like this:
(master)mwhudson@aeglos:/opt/opensource/snaps/go$ snapdiff
go-17-mwhudson_1.snap go-17-mwhudson_2.snap
Only in second snap, go-17-mwhudson_2.snap:
-rw-rw-r-- root/root 839 2017-02-03 11:
On 6 February 2017 at 02:55, Shuduo Sang wrote:
>
>
> On Fri, Feb 3, 2017 at 4:52 PM, Shuduo Sang
> wrote:
>
>> Hi,
>>
>> I got following output after run it:
>>
>> $ go-17-mwhudson.go-17
>> /snap/go-17-mwhudson/2/gowrapper: line 3: /snap/go-17-mwhudson/2/bin/go:
>> No such file or directory
>>
Prompted by some upstream discussion, I've made a snap of Go (just 1.7.4
for now):
$ sudo snap install --edge --classic go-17-mwhudson
It has aliases for go-17 (which will probably be the final snap of the snap
if this ends up being official) and go (the thinking being that there will
also be go-
On 30 January 2017 at 07:48, Joseph Rushton Wakeling <
joseph.wakel...@webdrake.net> wrote:
> Hello all,
>
[...]
> Second: the `source-tag:` settings for the 3 parts should all match. Is
> there any way of defining a common value that they can all use (to make
> sure that in future there is le
On 25 January 2017 at 11:28, Michael Hudson-Doyle <
michael.hud...@canonical.com> wrote:
>
> You have to do this "asciinema rec -c 'PYTHONHOME=/usr python3
> urwid/examples/pop_up.py '" instead (and even that ends up using python3
> from the core snap,
On 25 January 2017 at 11:02, Sergio Schvezov
wrote:
> On Wed, 25 Jan 2017 08:17:17 +1300, Michael Hudson-Doyle wrote:
> > Hm, I was assuming that the PYTHONHOME leaking was due to things in the
> > snap specifically (is the source to the snap available?), but are they
> set
&g
Hm, I was assuming that the PYTHONHOME leaking was due to things in the
snap specifically (is the source to the snap available?), but are they set
by snapd or snap-confine or something?
Cheers,
mwh
On 24 January 2017 at 00:09, Gustavo Niemeyer wrote:
>
> I'm wondering if maybe we should simply
PYTHONHOME also leaks into the recording environment.
On 20 January 2017 at 13:03, Michael Hudson-Doyle <
michael.hud...@canonical.com> wrote:
> This confused me for a while: https://asciinema.org/
> a/2ua1d08k6v8jiyy1m2uyvn8rx (spoiler: python3 inside 'asciinema rec' is
&
This confused me for a while:
https://asciinema.org/a/2ua1d08k6v8jiyy1m2uyvn8rx (spoiler: python3 inside '
asciinema rec' is python3 from the core snap).
Cheers,
mwh
On 18 January 2017 at 22:16, Mark Shuttleworth wrote:
> Hi folks
>
> (For those of you who Gmail does not filter this email on
>
On 18 January 2017 at 12:13, Manik Taneja wrote:
>
>
> On Tue, Jan 17, 2017 at 1:30 PM, Michael Hudson-Doyle <
> michael.hud...@canonical.com> wrote:
>>
>>
>> Well snap create-user is mostly there exactly so that console-conf can
>> invoke it.
On 13 January 2017 at 08:14, Max Brustkern
wrote:
> So I created a system directory with the contents of /lib/systemd/system.
> I edited that file to contain the environment variables:
> nuclearbob@localhost:~$ cat /lib/systemd/system/snapd.service
> [Unit]
> Description=Snappy daemon
> Requires=
On 21 December 2016 at 22:51, Luther Goh Lu Feng wrote:
> During setup, console-conf will download the SSH key registered with your
> Store account, The ssh key is used for first login.
>
> Is there a way to configure Ubuntu Core such that the source of the ssh
> key can be from elsewhere? eg for
Oh wait, I haven't made a subiquity release with that change yet. Sorry!
(Blame baby brain)
sent from my phone, please excuse brevity
On 15 Dec 2016 08:05, "Oliver Grawert" wrote:
> hi,
> Am Donnerstag, den 15.12.2016, 07:47 +1300 schrieb Michael Hudson-
> Doyle:
>
sent from my phone, please excuse brevity
On 15 Dec 2016 01:19, "Oliver Grawert" wrote:
hi,
Am Mittwoch, den 14.12.2016, 13:22 +1300 schrieb Michael Hudson-Doyle:
> What version of core do you have? This should be clearer with the
> latest versions, you shouldn't see the l
What version of core do you have? This should be clearer with the latest
versions, you shouldn't see the login prompt until you set a password.
Cheers,
mwh
sent from my phone, please excuse brevity
On 14 Dec 2016 09:47, "Dan Kegel" wrote:
Trying ubuntu core on the pi3 for the first time. Inst
On 17 November 2016 at 07:30, Jacques Supcik wrote:
> Hello.
>
> During the installation of ubuntu core, we have to give an e-mail address
> to link the device with an Ubuntu account. It is possible to then add
> additional accounts to the device (e.g. to allow multiple sysadmins to
> manage a de
On 10 November 2016 at 00:50, Oliver Grawert wrote:
> hi,
> Am Mittwoch, den 09.11.2016, 16:07 +1300 schrieb Michael Hudson-Doyle:
> >
> >
> > I tried to test my packages first by fixing up our build of the core
> > snap (https://launchpad.net/~canonical-foundation
On 8 November 2016 at 07:41, Michael Hudson-Doyle <
michael.hud...@canonical.com> wrote:
>
>
> On 8 November 2016 at 00:24, Oliver Grawert wrote:
>
>> hi,
>> Am Montag, den 07.11.2016, 17:27 +1300 schrieb Michael Hudson-Doyle:
>> > Hi all,
>> >
On 8 November 2016 at 00:24, Oliver Grawert wrote:
> hi,
> Am Montag, den 07.11.2016, 17:27 +1300 schrieb Michael Hudson-Doyle:
> > Hi all,
> > I've been working on a rewrite of console-conf's networking bits,
> > with the intent of making the UI a bit clearer
Hi all,
I've been working on a rewrite of console-conf's networking bits, with the
intent of making the UI a bit clearer and more dynamic (e.g. if you stick a
USB Ethernet adapter in after you've started console-conf, it shows up in
the UI).
I've tested this locally but this is the sort of thing
On 7 September 2016 at 21:52, Oliver Grawert wrote:
>
> depending on the console (console-conf isnt actually great with serial)
> you will not see the "please press enter" message that starts the
> config tool though.
I'd love to know why this isn't working, btw. We're just using agetty's -f
opt
dc/gadget/driver/unbind'
>
> and then reboot. I now boot in 24 seconds instead of 140 seconds :)
>
> Thanks!
>
Glad to hear it, and sorry for the trouble.
Cheers,
mwh
> Le 09/01/2016 à 11:19 PM, Michael Hudson-Doyle a écrit :
>
>
>
> On 2 September 2016 at 00:
On 2 September 2016 at 00:44, Yann Sionneau
wrote:
> I'm not sure I understand everything in the bug ticket as I am not a
> systemd / networkd / netplan expert at all.
>
> But :
>
> root@Paros:~# cat /etc/netplan/00-
> 00-initial-config.yaml 00-snapd-config.yaml
> root@Paros:~# cat /etc/netplan/
37 matches
Mail list logo
