2017-12-08 0:31 GMT+09:00 Masahiro Yamada :
> 2017-12-07 3:14 GMT+09:00 Paolo Pisati :
>> On Wed, Dec 6, 2017 at 11:36 AM, Masahiro Yamada
>> wrote:
>>> Just one question to Paolo:
>>>
>>> If some change
2017-12-08 0:31 GMT+09:00 Masahiro Yamada :
> 2017-12-07 3:14 GMT+09:00 Paolo Pisati :
>> On Wed, Dec 6, 2017 at 11:36 AM, Masahiro Yamada
>> wrote:
>>> Just one question to Paolo:
>>>
>>> If some change like firmware removal happens in the future,
>>> patching for snapcraft is necessary?
>>>
2017-12-07 3:14 GMT+09:00 Paolo Pisati :
> On Wed, Dec 6, 2017 at 11:36 AM, Masahiro Yamada
> wrote:
>> Just one question to Paolo:
>>
>> If some change like firmware removal happens in the future,
>> patching for snapcraft is
2017-12-07 3:14 GMT+09:00 Paolo Pisati :
> On Wed, Dec 6, 2017 at 11:36 AM, Masahiro Yamada
> wrote:
>> Just one question to Paolo:
>>
>> If some change like firmware removal happens in the future,
>> patching for snapcraft is necessary?
>> (i.e. users are required to upgrade snapcraft
On Wed, Dec 6, 2017 at 11:36 AM, Masahiro Yamada
wrote:
> Just one question to Paolo:
>
> If some change like firmware removal happens in the future,
> patching for snapcraft is necessary?
> (i.e. users are required to upgrade snapcraft from --edge ?)
>
> I
On Wed, Dec 6, 2017 at 11:36 AM, Masahiro Yamada
wrote:
> Just one question to Paolo:
>
> If some change like firmware removal happens in the future,
> patching for snapcraft is necessary?
> (i.e. users are required to upgrade snapcraft from --edge ?)
>
> I guess the answer is yes,
2017-12-06 6:23 GMT+09:00 Jim Davis :
> On Tue, Dec 5, 2017 at 4:43 AM, Paolo Pisati
> wrote:
>
>>> 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
2017-12-06 6:23 GMT+09:00 Jim Davis :
> On Tue, Dec 5, 2017 at 4:43 AM, Paolo Pisati
> wrote:
>
>>> 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
On Tue, Dec 5, 2017 at 4:43 AM, Paolo Pisati wrote:
>> 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
On Tue, Dec 5, 2017 at 4:43 AM, Paolo Pisati wrote:
>> 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?
>
> That
On Fri, Dec 1, 2017 at 12:15 AM, Jim Davis wrote:
>
> If I run /snap/bin/snapcraft --version now on that Ubuntu 16.04 VM I
> am getting 2.36+git2.ae61453.
Yep, the edge channel follows the bleeding edge:
$ snap info snapcraft
...
channels:
stable:2.35
On Fri, Dec 1, 2017 at 12:15 AM, Jim Davis wrote:
>
> If I run /snap/bin/snapcraft --version now on that Ubuntu 16.04 VM I
> am getting 2.36+git2.ae61453.
Yep, the edge channel follows the bleeding edge:
$ snap info snapcraft
...
channels:
stable:2.35(794) 53MB classic
On Fri, Dec 1, 2017 at 1:03 PM, Riku Voipio wrote:
>
> Since you are already patching snapcraft for this, why not embed the
> whole support in snapcraft? Eg something like snapcraft --kernel
> /path/to/kernel
>
> The key advantage you'll get is being able to support old
On Fri, Dec 1, 2017 at 1:03 PM, Riku Voipio wrote:
>
> Since you are already patching snapcraft for this, why not embed the
> whole support in snapcraft? Eg something like snapcraft --kernel
> /path/to/kernel
>
> The key advantage you'll get is being able to support old kernel versions too.
On 29 November 2017 at 19:05, Paolo Pisati wrote:
> On Wed, Nov 29, 2017 at 8:33 AM, Masahiro Yamada
> wrote:
>>
>> Worked for me too,
>> after updating snapcraft.
>>
>>
>> Is it really impossible to check the snapcraft version?
>> What
On 29 November 2017 at 19:05, Paolo Pisati wrote:
> On Wed, Nov 29, 2017 at 8:33 AM, Masahiro Yamada
> 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
On Wed, Nov 29, 2017 at 10:05 AM, Paolo Pisati
wrote:
> On Wed, Nov 29, 2017 at 8:33 AM, Masahiro Yamada
> wrote:
>>
>> Worked for me too,
>> after updating snapcraft.
>>
>>
>> Is it really impossible to check the snapcraft version?
>>
On Wed, Nov 29, 2017 at 10:05 AM, Paolo Pisati
wrote:
> On Wed, Nov 29, 2017 at 8:33 AM, Masahiro Yamada
> 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
On Wed, Nov 29, 2017 at 8:33 AM, Masahiro Yamada
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
On Wed, Nov 29, 2017 at 8:33 AM, Masahiro Yamada
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.
--
bye,
Weird, are you sure you are checking the snap version?
$ /snap/bin/snapcraft --version
snapcraft, version 2.35+git26.0474d85
$ snap info snapcraft
name: snapcraft
summary: easily create snaps
publisher: canonical
contact: snappy-canonical-storeacco...@canonical.com
description: |
Weird, are you sure you are checking the snap version?
$ /snap/bin/snapcraft --version
snapcraft, version 2.35+git26.0474d85
$ snap info snapcraft
name: snapcraft
summary: easily create snaps
publisher: canonical
contact: snappy-canonical-storeacco...@canonical.com
description: |
2017-11-29 4:35 GMT+09:00 Jim Davis :
> On Tue, Nov 28, 2017 at 10:14 AM, Paolo Pisati
> wrote:
>> On Mon, Nov 27, 2017 at 7:33 PM, Jim Davis wrote:
>>>
>>> With this patch applied to the 4.14 kernel source, and running make
2017-11-29 4:35 GMT+09:00 Jim Davis :
> On Tue, Nov 28, 2017 at 10:14 AM, Paolo Pisati
> wrote:
>> On Mon, Nov 27, 2017 at 7:33 PM, Jim Davis wrote:
>>>
>>> With this patch applied to the 4.14 kernel source, and running make
>>> snap-pkg on a Ubuntu 16.04 VM with the latest 16.04 kernel config
On Tue, Nov 28, 2017 at 10:14 AM, Paolo Pisati
wrote:
> On Mon, Nov 27, 2017 at 7:33 PM, Jim Davis wrote:
>>
>> With this patch applied to the 4.14 kernel source, and running make
>> snap-pkg on a Ubuntu 16.04 VM with the latest 16.04 kernel
On Tue, Nov 28, 2017 at 10:14 AM, Paolo Pisati
wrote:
> On Mon, Nov 27, 2017 at 7:33 PM, Jim Davis wrote:
>>
>> With this patch applied to the 4.14 kernel source, and running make
>> snap-pkg on a Ubuntu 16.04 VM with the latest 16.04 kernel config
>> file, I ran into
>>
>> Traceback (most
On Mon, Nov 27, 2017 at 7:33 PM, Jim Davis wrote:
>
> With this patch applied to the 4.14 kernel source, and running make
> snap-pkg on a Ubuntu 16.04 VM with the latest 16.04 kernel config
> file, I ran into
>
> Traceback (most recent call last):
> File
On Mon, Nov 27, 2017 at 7:33 PM, Jim Davis wrote:
>
> With this patch applied to the 4.14 kernel source, and running make
> snap-pkg on a Ubuntu 16.04 VM with the latest 16.04 kernel config
> file, I ran into
>
> Traceback (most recent call last):
> File "/usr/lib/python3.5/shutil.py", line
On Mon, Nov 27, 2017 at 4:07 AM, Paolo Pisati
wrote:
> Following in footsteps of other targets like 'deb-pkg, 'rpm-pkg' and
> 'tar-pkg',
> this patch adds a 'snap-pkg' target for the creation of a Linux kernel snap
> package using the kbuild infrastructure.
With this
On Mon, Nov 27, 2017 at 4:07 AM, Paolo Pisati
wrote:
> Following in footsteps of other targets like 'deb-pkg, 'rpm-pkg' and
> 'tar-pkg',
> this patch adds a 'snap-pkg' target for the creation of a Linux kernel snap
> package using the kbuild infrastructure.
With this patch applied to the 4.14
Following in footsteps of other targets like 'deb-pkg, 'rpm-pkg' and 'tar-pkg',
this patch adds a 'snap-pkg' target for the creation of a Linux kernel snap
package using the kbuild infrastructure.
A snap, in its general form, is a self contained, sandboxed, universal package
and it is intended to
Following in footsteps of other targets like 'deb-pkg, 'rpm-pkg' and 'tar-pkg',
this patch adds a 'snap-pkg' target for the creation of a Linux kernel snap
package using the kbuild infrastructure.
A snap, in its general form, is a self contained, sandboxed, universal package
and it is intended to
32 matches
Mail list logo