Hello,
I've just updated my snappy image and now it takes a very long time to
boot (140 seconds) because of
[FAILED] Failed to start Wait for Network to be Configured.
See 'systemctl status systemd-networkd-wait-online.service' for details.
which is :
https://www.freedesktop.org/software/systemd
I've been working on bringing up Ubuntu Core on some new hardware targets -
network switch whiteboxes.
Very recently, the first boot of Ubuntu Core has added a Profile Setup
step. I'm stuck in this step and can't get out. My target is now a
brick...
My Xenial Desktop development system is up to
On 01-Sep-2016, MikeB wrote:
1. I see a message saying 'Contacting the Store', then get the error
> "Creating user failed: error: bad user result: cannot create user for
> : no ssh keys found" -- OR -- 2. I immediately see the
> error "Creating user failed: error: bad user
> result: cannot create
Hi Yann,
Following up from our IRC exchange :-)
What would you expect to be working before network is up? Is it startup of
the snaps' services, or the console, or the Snapweb web UI etc. [1]?
Cheers,
- Loïc
[1] of course, still need to address Snapweb not starting properly with no
network
On
Hi Loic,
I expect the system to boot normally but everything needing internet
would not work obviously.
For instance indeed the snap services would be started, snapweb, the
uart console.
But indeed I would not expect the auto refresh of snaps to work.
PS : and in fact I have 2 interfaces with i
hi,
On Do, 2016-09-01 at 06:10 -0400, MikeB wrote:
> Very recently, the first boot of Ubuntu Core has added a Profile
> Setup step. I'm stuck in this step and can't get out. My target is
> now a brick...
>
i filed
https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1619245
for this ... f
hi,
On Do, 2016-09-01 at 11:30 +0200, Yann Sionneau wrote:
>
> Lots of embedded devices don't have a 24/24 network connection.
>
feel free to confirm:
https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1619258
ciao
oli
signature.asc
Description: This is a digitally signed message par
> On 1 Sep 2016, at 12:42, Oliver Grawert wrote:
>
> hi,
> On Do, 2016-09-01 at 06:10 -0400, MikeB wrote:
>
>> Very recently, the first boot of Ubuntu Core has added a Profile
>> Setup step. I'm stuck in this step and can't get out. My target is
>> now a brick...
>>
> i filed
> https://bugs
I feel like this is the bug I'm hitting.
But, how do you explain that my boot is stalled even if I have 2 NICs
with internet access?
One is via wifi, the other is via usb-ethernet.
Thanks!
Le 09/01/2016 à 01:47 PM, Oliver Grawert a écrit :
> hi,
> On Do, 2016-09-01 at 11:30 +0200, Yann Sionnea
hi,
On Do, 2016-09-01 at 14:05 +0200, Yann Sionneau wrote:
> I feel like this is the bug I'm hitting.
> But, how do you explain that my boot is stalled even if I have 2 NICs
> with internet access?
> One is via wifi, the other is via usb-ethernet.
> Thanks!
hmm, this sounds more like a different bu
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/00-initial-config.yaml
network:
version: 2
ethernets:
all:
Hi Mike
You are seeing the bootstrapping of a brand new all-snap OS, sorry for
the rough patches but we have just added this first-boot experience. The
rest is shaping up very nicely, that part is just brand new. We expect a
usable image on Friday this week, and a release candidate later in the
mo
Understood about the rough spots - it's the cost of playing on the edge.
This one was a bit more disruptive than usual. I'm looking forward to the
official release.
Cheers, Mike
On Thu, Sep 1, 2016 at 12:38 PM, Mark Shuttleworth wrote:
> Hi Mike
>
> You are seeing the bootstrapping of a brand
When automating the build process for snaps, I'd like to be able to provide
the release version as an argument to snapcraft, which could then be used
as a variable in the snapcraft.yaml.
For example, say I'd like to release "foo" version "1.2.3". I'd then like
to build the snap with version: 1.2.3
El 01/09/16 a las 14:05, Casey Marshall escribió:
When automating the build process for snaps, I'd like to be able to
provide the release version as an argument to snapcraft, which could
then be used as a variable in the snapcraft.yaml.
For example, say I'd like to release "foo" version "1.2.3
Readding the list
El 01/09/16 a las 14:27, Casey Marshall escribió:
On Thu, Sep 1, 2016 at 12:15 PM, Sergio Schvezov
mailto:sergio.schve...@canonical.com>>
wrote:
El 01/09/16 a las 14:05, Casey Marshall escribió:
When automating the build process for snaps, I'd like to be able
t
This is a pain point for me too. Most upstreams store the version number
in only one place, because editing more than one for every tagged
release is too boring.
When we add the snapcraft.yaml, I suspect that the version field will be
forgotten often, and it will not be in sync.
However, there ar
On 2016-09-01 11:40, Sergio Schvezov wrote:
> snapcraft set-version
> snapcraft
works for me.
signature.asc
Description: OpenPGP digital signature
--
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/snapcraft
On 31.08.2016 21:35, Joseph Rushton Wakeling wrote:
First things first, run `snapcraft stage`. Then edit the auto-generated
stage/etc/ldc2.conf and replace it with this:
https://gist.github.com/WebDrake/229645efeca14fa54b0b1c82bcbb6477
... which as you can see includes a compiler flag: `-gcc=ld
El 01/09/16 a las 18:06, Joseph Rushton Wakeling escribió:
On 31.08.2016 21:35, Joseph Rushton Wakeling wrote:
First things first, run `snapcraft stage`. Then edit the auto-generated
stage/etc/ldc2.conf and replace it with this:
https://gist.github.com/WebDrake/229645efeca14fa54b0b1c82bcbb647
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/
On 01.09.2016 23:18, Sergio Schvezov wrote:
El 01/09/16 a las 18:06, Joseph Rushton Wakeling escribió:
On 31.08.2016 21:35, Joseph Rushton Wakeling wrote:
First things first, run `snapcraft stage`. Then edit the auto-generated
stage/etc/ldc2.conf and replace it with this:
https://gist.github
On 27.08.2016 22:45, Joseph Rushton Wakeling wrote:
I thought I'd have a go at making a snap of LDC, the LLVM-based compiler for the
D programming language. I recognize that snapping a compiler might be jumping
ahead of the current intended use-case(s), but it's fun to see what could be
possible
Hello all,
With assertions finally being put to great use, it's time to kill the term
"sideloading". That term does a disservice to our conversations, because it
is vague and also limits the thinking around what is possible.
Whenever we use "sideloading", we mean one of two things:
1. The instal
On Thu, Sep 1, 2016 at 5:15 PM, Gustavo Niemeyer
wrote:
> Hello all,
>
> With assertions finally being put to great use, it's time to kill the term
> "sideloading". That term does a disservice to our conversations, because it
> is vague and also limits the thinking around what is possible.
>
> Whe
On 01.09.2016 23:52, Joseph Rushton Wakeling wrote:
Now create a file `prime/bin/gcc.wrapper` with the following contents:
https://gist.github.com/WebDrake/0081628d70b61e271006c9b8fa3454ef
(This is basically the command-gcc.wrapper that would be generated if I were
exposing the gcc command outsi
On Thu, Sep 01, 2016 at 07:15:25PM -0300, Gustavo Niemeyer wrote:
> With assertions finally being put to great use, it's time to kill the term
> "sideloading". That term does a disservice to our conversations, because it
What are assertions?
Thanks
signature.asc
Description: PGP signature
--
S
Thanks Evan, this is great and I've already copied a couple of times.
In a similar fashion, take a look at the script Kyle wrote to push the
branch to launchpad:
https://github.com/nextcloud/nextcloud-snap/blob/master/.travis.yml
The benefit here is that launchpad will build and publish for many
Hi Seth,
On Thu, Sep 1, 2016 at 8:36 PM, Seth Arnold
wrote:t
> On Thu, Sep 01, 2016 at 07:15:25PM -0300, Gustavo Niemeyer wrote:
> > With assertions finally being put to great use, it's time to kill the
> term
> > "sideloading". That term does a disservice to our conversations, because
> it
>
>
Consider also that we likely want to support remote unasserted installs for
alternate stores [1], so they are fully orthogonal concepts.
So we have all four local/remote asserted/unasserted combos. And I agree that
"sideloading" is no longer a useful term.
-bret
[1] With whatever warnings or o
On 01/09/16 17:52, Joseph Rushton Wakeling wrote:
> * is there any way to automate some of the stages of the above,
> e.g. the editing of stage/etc/ldc2.conf or the generation of
> prime/bin/gcc.wrapper ... ?
I think we need a recommended way to:
* carry patches for a part in the snap
On Sep 1, 2016 5:24 PM, "Leo Arias" wrote:
>
> Thanks Evan, this is great and I've already copied a couple of times.
>
> In a similar fashion, take a look at the script Kyle wrote to push the
> branch to launchpad:
> https://github.com/nextcloud/nextcloud-snap/blob/master/.travis.yml
Note that if
On Fri, Sep 2, 2016 at 6:34 AM Joseph Rushton Wakeling <
joseph.wakel...@webdrake.net> wrote:
> On 01.09.2016 23:52, Joseph Rushton Wakeling wrote:
> > Now create a file `prime/bin/gcc.wrapper` with the following contents:
> > https://gist.github.com/WebDrake/0081628d70b61e271006c9b8fa3454ef
> >
>
33 matches
Mail list logo
