El 12/12/16 a las 18:33, Jamie Strandboge escribió:
2. snapcraft doesn't allow you to specify it (which is good since the
implementation doesn't work correctly)
This is because we agreed to bring it back in 16 with a more
integrated/polished design. I believe the code in snapd are just
On Sat, 2016-12-10 at 14:29 +0100, l-snapcr...@znn.info wrote:
> Hi Snapcrafter,
>
> in the documentation about keys in the yaml i saw a mention of "daemon:
> dbus" (1), but i could not find an explanation in the documentation of a
> real world example how it is used on github.
>
> Can someone
I've used the same wrapper script configuration[1] as you're doing. If
you make pgbouncer a daemon it will be run as root, so the wrapper will
be able to create the config files without a problem. You should use
$SNAP_DATA rather than $SNAP_USER_DATA for this.
Coming soon (in snapd 2.18 I think)
I've only seen this a couple times, if it's happening to you frequently it
may be a problem with your network connection. Perhaps we need a store
endpoint in China like we did for the developer portal?
On Dec 8, 2016 8:31 PM, "XiaoGuo Liu" wrote:
> Hi,
>
> I do not
Le 10/12/2016 à 14:29, l-snapcr...@znn.info a écrit :
> Hi Snapcrafter,
Hey lightonflux,
> in the documentation about keys in the yaml i saw a mention of "daemon:
> dbus" (1), but i could not find an explanation in the documentation of a
> real world example how it is used on github.
>
> Can
I tried this too, and the “dbus” key value was rejected. Looks like this might
be a moldie oldie?
Michi.
> On 12 Dec. 2016, at 17:41 , Didier Roche wrote:
>
> Le 10/12/2016 à 14:29, l-snapcr...@znn.info a écrit :
>> Hi Snapcrafter,
>
> Hey lightonflux
>>
>> in the