[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+r1Zhj6H8+g_F+caPvWrCouPk-Cib62wACG+uH=s3_Ato_qhQ@mail.gmail.com>
Date: Thu, 30 Nov 2017 16:15:22 -0700
From: Jim Davis <jim.epost@...il.com>
To: Paolo Pisati <paolo.pisati@...onical.com>
Cc: Masahiro Yamada <yamada.masahiro@...ionext.com>,
Michal Marek <michal.lkml@...kovi.net>,
Behan Webster <behanw@...verseincode.com>,
Matthias Kaehlcke <mka@...omium.org>,
VinÃcius Tinti <viniciustinti@...il.com>,
linux-kbuild <linux-kbuild@...r.kernel.org>,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3] scripts/package: snap-pkg target
On Wed, Nov 29, 2017 at 10:05 AM, Paolo Pisati
<paolo.pisati@...onical.com> wrote:
> On Wed, Nov 29, 2017 at 8:33 AM, Masahiro Yamada
> <yamada.masahiro@...ionext.com> wrote:
>>
>> Worked for me too,
>> after updating snapcraft.
>>
>>
>> Is it really impossible to check the snapcraft version?
>> What is the minimum version? 2.35 ?
>
> The minimum version is 2.35+ - what is about to become 2.36 anytime soon now.
If I run /snap/bin/snapcraft --version now on that Ubuntu 16.04 VM I
am getting 2.36+git2.ae61453.
I noticed that if I tried to make snap-pkg with the O=/some/dir option
the tar step failed but the rest of the build continued, and seems to
have finished successfully. Should the snap-pkg target stop after a
tar failure?
--
Jim
Powered by blists - more mailing lists