On Fri, Feb 10, 2017 at 09:41:52PM +0100, Joseph Rushton Wakeling wrote:
> Attempting to compile this program resulted in a segfault in GCC (which LDC
> invokes in order to link programs).
[...]
> Anyway, does anyone have any thoughts?
Hi Joe, can you grab the dmesg output that might include DENIE
On 10/02/17 21:41, Joseph Rushton Wakeling wrote:
Running `ldc -v` for verbose output, the precise call that segfaulted was:
/usr/bin/gcc hello.o -o hello -L/snap/ldc2/3/bin/../lib -lphobos2-ldc
-ldruntime-ldc -Wl,--gc-sections -lrt -ldl -lpthread -lm -m64
My suspicion is that that `libphobos2-
Hi all,
So, earlier today I tried out my ldc2 snap on an Ubuntu 14.04 system for the
first time.
sudo snap install --classic --edge ldc2
worked just fine, but I ran into problems as soon as I tried to compile a simple
'hello world' program:
void main()
{
import std.stdi
On Fri, Feb 10, 2017 at 8:39 PM, Joseph Rushton Wakeling
wrote:
> On 08/02/17 17:15, Joseph Rushton Wakeling wrote:
>>
>> On 07/02/17 21:17, Thomas Voß wrote:
>>>
>>>
>>> https://bugs.launchpad.net/ubuntu/+source/xorg-server-lts-xenial/+bug/1655724
>>> was released to the updates pocket today.
>>
On 08/02/17 17:15, Joseph Rushton Wakeling wrote:
On 07/02/17 21:17, Thomas Voß wrote:
https://bugs.launchpad.net/ubuntu/+source/xorg-server-lts-xenial/+bug/1655724
was released to the updates pocket today.
Thanks! I'll hopefully be able to report back to you tomorrow whether all works
as exp
On Thu, Feb 09, 2017 at 04:43:33PM -0300, Sergio Schvezov wrote:
> El jueves, 9 de febrero de 2017 16h'23:34 ART, Colin Watson
> escribió:
> >Oh, in fact, that looks just about perfect for us. With that patch I
> >think LP could just export SNAPCRAFT_SETUP_CORE=1 when building snaps,
> >right?
>
Hi, I've been struggling with getting dbus interface exposed. I am getting
this error during runtime:
GLib.Error: g-dbus-error-quark:
GDBus.Error:org.freedesktop.DBus.Error.AccessDenied:
Connection ":1.1160" is not allowed to own the service
"com.screenly.playlist" due to security policies in the c
ve only the plugin output into a subfolder?
> >
> > Thanks,
> > Ruddick
> >
> > --
> > Snapcraft mailing list
> > Snapcraft@lists.snapcraft.io
> > Modify settings or unsubscribe at: https://lists.ubuntu.com/
> > mailman/listinfo/snapcraft
> >
&
On Tue, Feb 7, 2017 at 3:54 PM, Didier Roche wrote:
> Le 07/02/2017 à 14:05, Simos Xenitellis a écrit :
>> On Tue, Feb 7, 2017 at 9:13 AM, Didier Roche wrote:
>>> Le 06/02/2017 à 10:56, Simos Xenitellis a écrit :
Hi All,
I wrote an article about creating a snap for an existing Pyth
I tried exporting that before running spread, and that didn't change the
result.
Thanks,
Max
On Thu, Feb 9, 2017 at 2:26 PM, Thomas Voß
wrote:
> Hey Max,
>
> as a quick test, would you mind trying to set
>
> TAR_OPTIONS='--format=posix'
>
> in the environment you run spread in?
>
> Thanks,
>
You can use a separate part for the stage packages:
parts:
part1:
...
organize:
'*': opt/
part2:
plugin: nil
stage-packages:
- some-great-package
On Thu, Feb 9, 2017 at 11:47 PM, Ruddick Lawrence wrote:
> I just discovered that a part with:
>
> organize:
> '
That's interesting, Simon. Good idea having available both $SNAP_DATA
and /media. We'll do.
But now, let's back to original topic: chroot into snap.
After solving the issue Thomas found related with the path of the
document, I see now there are two operations not allowed in strict
confinement: mkn
The program "app1" is not mine. It consists of two parts.
I create snapcraft.yaml
apps:
engine:
command: $SNAP/opt/app1/engine --start
plugs: [home, unity7, x11, pulseaudio, network, network-bind]
player:
command: $SNAP/opt/app1/player "$@"
plugs: [home
I think you have to support both as otherwise you may miss certain setups
of nextcloud. One may be configured to use $SNAP_DATA/$SNAP_COMMON to store
its data, another one may use /media/.. to do that. In the end there needs
to be some kind of communication happen between both snaps.
Either the ne
Ah, thanks. I'd better use content then.
On 10/02/17 09:38, Simon Fels wrote:
> On 10.02.2017 09:16, Roberto Mier Escandón wrote:
>> I tried content sharing and works fine in this case, Nextcloud exposing
>> a slot to its documents folder. I think I saw somewhere this is only
>> valid for a 1-1
On 10.02.2017 09:16, Roberto Mier Escandón wrote:
> I tried content sharing and works fine in this case, Nextcloud exposing
> a slot to its documents folder. I think I saw somewhere this is only
> valid for a 1-1 plug-slot, so that only 1 snap can use that slot at the
> same time. Is that correct
I tried content sharing and works fine in this case, Nextcloud exposing
a slot to its documents folder. I think I saw somewhere this is only
valid for a 1-1 plug-slot, so that only 1 snap can use that slot at the
same time. Is that correct? Can removable-media improve this?
On 10/02/17 08:05, Kyle
Le 09/02/2017 à 17:12, Kyle Fazzari a écrit :
>
> On 02/09/2017 01:04 AM, Didier Roche wrote:
>> Ok, sorry for the catchy email title but couldn't resist :)
>>
>> So, I'm in the situation where one snap would need to get configuration
>> and access to some files from other snaps. It's really simila
18 matches
Mail list logo
