Of course!
https://bugs.launchpad.net/launchpad-buildd/+bug/1663920
Thanks!
On Feb 11, 2017 12:42 PM, "Colin Watson" wrote:
> On Sat, Feb 11, 2017 at 12:05:37PM -0600, Gregory Lutostanski wrote:
> > Is there any way I can let the git source from snapcraft not pull
> > recusively? Or might we b
On Sat, Feb 11, 2017 at 12:05:37PM -0600, Gregory Lutostanski wrote:
> Is there any way I can let the git source from snapcraft not pull
> recusively? Or might we be able to have launchpad builders have a git proxy
> (perhaps via GIT_PROXY_COMMAND, like in
> https://stackoverflow.com/questions/7838
So I've got a snapcraft.yaml that builds fine locally, but it has
submodules from a remote git:// repo (rather than https://), this means the
HTTP and HTTPS proxies don't help -- which leads to errors on launchpad
builders.
I tried to change the submodule url in the prepare step, but snapcraft
alr
On Sat, Feb 11, 2017 at 10:56 AM, Mark Shuttleworth wrote:
> What am I missing?
It's not you, it's us. I was just playing with mosh and I see that
copying the snapcraft.yaml to the part/src dir is not enough. It also
needs to be in part/build. I don't have a workaround for that, we'll
need to cha
OK, glad it's a known issue.
The 'source-type: git' piece didn't fix anything for me, though, I still
see the dirty-commit version number.
snap/snapcraft.yaml contains this:
parts:
keepalived:
plugin: autotools
source: .
source-type: git
What am I missing?
Mark
On 11/02/17 16:3
On 11/02/17 17:31, Joseph Rushton Wakeling wrote:
And `dmesg | grep -i gcc` gave this output:
Slightly more detailed dmesg output from `dmesg | grep -e "gcc" -e "ldc2"`:
[0.00] Linux version 4.4.0-62-generic (buildd@lcy01-33) (gcc version
4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #83~14
Hello!
This is bug: https://bugs.launchpad.net/snapcraft/+bug/1662388
We will discuss if removing the yaml is needed at all. But in the
meantime, add source-type: git.
pura vida.
--
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at:
https://lists.ubuntu.com/
On 11/02/17 00:48, Seth Arnold wrote:
Hi Joe, can you grab the dmesg output that might include DENIED lines as
well as the kernel's segfault report?
Sure -- thanks for the thought! :-)
I just reproduced the issue in a VirtualBox install of 14.04 to get these
details. Kernel report in kern.lo
Hi folks
In a branch with a snap/snapcraft.yaml I am seeing that git reports a
version with a dirty commit (suffix+) for snaps built from the branch.
Is there a way to prevent this, or is snapcraft doing something during
the snapping process which will cause git to think the checkout is dirty?
Ma
