On Tue, 2017-03-21 at 18:11 +0100, Loïc Minier wrote:
> Hi!
>
> On Mon, Mar 20, 2017 at 8:29 PM, Jamie Strandboge
> wrote:
>
> >
> > The aksusbd case seems like it could be covered by existing interface
> > techniques. The providing snap slots the hasp interface and that interface
> > could
> >
Hi Maarten,
Thanks for your response. I would be grateful if you can spare some time to
check which snap(sensortag) you got working, if possible can you forward that
working snapcraft.yaml file.
Waiting eagerly for your response.
Regards,
Mritunjai
-Original Message-
From: snapcraft-
Hi!
On Mon, Mar 20, 2017 at 8:29 PM, Jamie Strandboge
wrote:
> The aksusbd case seems like it could be covered by existing interface
> techniques. The providing snap slots the hasp interface and that interface
> could
> add udev rules that point to (the snappy command aliased)
> /snap/bin/aksusb
hi,
Am Dienstag, den 21.03.2017, 11:23 + schrieb Nicolino Curalli:
> Hi Oli
> an further step:
> is it possibile to publish my new core snap on store, then permit to
> upgrade it to my new version of it?
>
no, we do not allow other core snaps, to make sure every snap sees the
same execution en
Hi Oli
an further step:
is it possibile to publish my new core snap on store, then permit to
upgrade it to my new version of it?
Ciao Nicolino
Il 21/03/2017 11:36, Oliver Grawert ha scritto:
> hi,
> Am Dienstag, den 21.03.2017, 10:27 + schrieb Nicolino Curalli:
>> hi Oli,
>> thanks a lot fo
Hey Didier,
I see, thanks for your answer!
All the best,
Tim Süberkrüb
On 20.03.2017 09:42, Didier Roche wrote:
Le 17/03/2017 à 19:13, Tim Süberkrüb a écrit :
Hey,
Hey Tim,
what is the process of contributing a cloud part to
https://wiki.ubuntu.com/snapcraft/parts (is it open for commu
hi,
Am Dienstag, den 21.03.2017, 18:26 +0800 schrieb Madper Xie:
>
> > Yes I noticed that in the README.txt. So I modified the boot cmd to
> `autoboot=bootz ${loadaddr} ${ramdisk_addr}:1c5 ${fdt_addr}` ...
> Still
> doesn't boot.
where does that 1c5 come from ?
please take a look at [1] where we
hi,
Am Dienstag, den 21.03.2017, 10:27 + schrieb Nicolino Curalli:
> hi Oli,
> thanks a lot for the answer.
>
> how could i rebuild a new image with my new core snap , built with
> procedure that your show me, by ubuntu-image?
you can follow the normal image building process [1] and use the
hi Oli,
thanks a lot for the answer.
how could i rebuild a new image with my new core snap , built with
procedure that your show me, by ubuntu-image?
Ciao
Nicolino
Il 20/03/2017 13:37, Oliver Grawert ha scritto:
> hi,
> On Di, 2017-03-14 at 11:29 +0100, Loïc Minier wrote:
>>
>> (So you want to
Hi Ogra,
On Tue, Mar 21, 2017 at 6:20 PM, Oliver Grawert wrote:
> hi,
> Am Dienstag, den 21.03.2017, 18:13 +0800 schrieb Madper Xie:
> > Hi Ogra,
> >
> > After adding the `#define CONFIG_SUPPORT_RAW_INITRD` the uboot still
> > complains `Wrong Ramdisk Image Format Ramdisk image is corrupt or
> >
hi,
Am Dienstag, den 21.03.2017, 11:20 +0100 schrieb Oliver Grawert:
>
> also a look at your boot.env.in
indeed i meant uboot.env.in
:)
ciao
oli
signature.asc
Description: This is a digitally signed message part
--
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or
hi,
Am Dienstag, den 21.03.2017, 18:13 +0800 schrieb Madper Xie:
> Hi Ogra,
>
> After adding the `#define CONFIG_SUPPORT_RAW_INITRD` the uboot still
> complains `Wrong Ramdisk Image Format Ramdisk image is corrupt or
> invalid`
> ...
>
> Is there any other macros should be defined?
well, your in
Hi Mritunjai,
I made the snap for an IoT Berlin demo. I remember making several Bluetooth
sensortag intends before I got one working. Not sure it was this snap or
another one I got working. I must admit that Bluetooth hasn't been playing
nice during my snap efforts :-(
Maarten
On 20 Mar 2017 12
Hi Ogra,
After adding the `#define CONFIG_SUPPORT_RAW_INITRD` the uboot still
complains `Wrong Ramdisk Image Format Ramdisk image is corrupt or invalid`
...
Is there any other macros should be defined?
BR,
Madper
On Mon, Mar 20, 2017 at 8:26 PM, Oliver Grawert wrote:
> hi,
> On Do, 2017-03-16
Hello Joseph,
As you said we generally export env. variables in launching script to
deploy a customized part,
not pretty sure we now have a plugin or something to support this "before
pull the source"...
BR.
Jin
On Tue, Mar 21, 2017 at 5:09 AM, Joseph Rushton Wakeling <
joseph.wakel...@webdrake.
15 matches
Mail list logo