Re: Experimental Python interpreter snap

2017-02-23 Thread Stuart Bishop
On 23 February 2017 at 14:45, James Henstridge wrote: > So if I installed a package to $SNAP_USER_DATA for my > "python36-jamesh.python3" interpreter, the files would end up > somewhere under ~/snap/python36-jamesh/. > > If we then look at my simple hello-world example snap that uses the > conten

Re: Position-independent code and Ubuntu 16.10

2017-02-23 Thread Joseph Rushton Wakeling
On 22/02/17 00:39, Joseph Rushton Wakeling wrote: OK, fair enough. In my case I think it was the C-library parts of the D standard library that were being compiled without PIC. Seems OK to assume this may have been a project-specific thing, then (which is now fixed upstream). Just for the rec

Further ABI-related issues for ldc2 snap on 14.04 ... ?

2017-02-23 Thread Joseph Rushton Wakeling
Hello all, I've encountered a couple of further issues with the ldc2 compiler snap when it's installed on a 14.04 system. I'm sharing here to confirm if these are indeed ABI issues which might be fixable in terms of how snapcraft constructs the package. The first [1] relates to zlib, which

systemd-resolved and snaps

2017-02-23 Thread Kyle Fazzari
Hey all. I've received a bug report on a snap where the user was running a 16.10 Server install with the snap in question, and getting DNS errors. I've distilled the problem as much as I can but I cannot for the life of me figure out what's happening, so I thought maybe the list could point me in

Re: systemd-resolved and snaps

2017-02-23 Thread Stéphane Graber
On Thu, Feb 23, 2017 at 01:58:07PM -0800, Kyle Fazzari wrote: > Hey all. > > I've received a bug report on a snap where the user was running a 16.10 > Server install with the snap in question, and getting DNS errors. I've > distilled the problem as much as I can but I cannot for the life of me > f

Re: systemd-resolved and snaps

2017-02-23 Thread Steve Langasek
Hi Kyle, On Thu, Feb 23, 2017 at 01:58:07PM -0800, Kyle Fazzari wrote: > Hey all. > I've received a bug report on a snap where the user was running a 16.10 > Server install with the snap in question, and getting DNS errors. I've > distilled the problem as much as I can but I cannot for the life o

Re: systemd-resolved and snaps

2017-02-23 Thread Kyle Fazzari
On 02/23/2017 02:26 PM, Steve Langasek wrote: > Hi Kyle, > > On Thu, Feb 23, 2017 at 01:58:07PM -0800, Kyle Fazzari wrote: >> Hey all. > >> I've received a bug report on a snap where the user was running a 16.10 >> Server install with the snap in question, and getting DNS errors. I've >> distil

Creating and running tests for a snapcraft plugin

2017-02-23 Thread Joseph Rushton Wakeling
Hello all, I have started working on a snapcraft plugin for dub, a build/package manager for the D programming language. The plugin itself is ready (at least in a working draft), and now I'm working on the tests. Is there a simple way to run the tests for a single plugin, rather than the wh

Re: systemd-resolved and snaps

2017-02-23 Thread Steve Langasek
On Thu, Feb 23, 2017 at 02:39:27PM -0800, Kyle Fazzari wrote: > On 02/23/2017 02:26 PM, Steve Langasek wrote: > > acme-staging.api.letsencrypt.org is a CNAME. You are hitting bug #1647031, > > which we encountered when trying to roll out systemd-resolved by default for > > 17.04. This took a whi

Heads up: change in snapd test workers

2017-02-23 Thread Gustavo Niemeyer
Hello there, We're starting to blow up the 50 minutes time quota provided by Travis during CI of master, which means PRs may now fail for no reason other than taking too long. On quick inspection, prepare.sh claims to have fixed the original problem that motivated the ubuntu-core-16-64-fixme spre