From: Paolo Pisati <paolo.pisati@canonical.com>
To: Jim Davis <jim.epost@gmail.com>
Cc: "Masahiro Yamada" <yamada.masahiro@socionext.com>,
"Michal Marek" <michal.lkml@markovi.net>,
"Behan Webster" <behanw@converseincode.com>,
"Matthias Kaehlcke" <mka@chromium.org>,
"Vinícius Tinti" <viniciustinti@gmail.com>,
linux-kbuild <linux-kbuild@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3] scripts/package: snap-pkg target
Date: Wed, 29 Nov 2017 18:03:07 +0100 [thread overview]
Message-ID: <CAMsH0TSJuWLs-pDUyaop5g-LLvG1XuwsaUAap8LnF0NAKJGLKA@mail.gmail.com> (raw)
In-Reply-To: <CA+r1ZhgFQS6EEzazw0YZXhYqm+WN3mp69mGyaeNpX36WZLABrA@mail.gmail.com>
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-storeaccount@canonical.com
description: |
Snapcraft aims to make upstream developers' lives easier and as such is not a
single toolset, but instead is a collection of tools that enable the natural
workflow of an upstream to be extended with a simple release step into Snappy
enabled system.
snap-id: vMTKRaLjnOJQetI78HjntT37VuoyssFE
commands:
- snapcraft
tracking: edge
installed: 2.35+git26.0474d85 (864) 53MB classic
refreshed: 2017-11-29 09:54:04 +0100 CET
channels:
stable: 2.35 (794) 53MB classic
candidate: ↑
beta: ↑
edge: 2.35+git26.0474d85 (864) 53MB classic
On Tue, Nov 28, 2017 at 8:35 PM, Jim Davis <jim.epost@gmail.com> wrote:
> On Tue, Nov 28, 2017 at 10:14 AM, Paolo Pisati
> <paolo.pisati@canonical.com> wrote:
>> On Mon, Nov 27, 2017 at 7:33 PM, Jim Davis <jim.epost@gmail.com> 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 538, in move
>>> os.rename(src, real_dst)
>>> FileNotFoundError: [Errno 2] No such file or directory:
>>> '/home/jim/linux/snap/parts/kernel/install/lib/firmware' ->
>>> '/home/jim/linux/snap/parts/kernel/install/firmware'
>>>
>>> What did I miss?
>>
>> You need a recent version of snapcraft, i landed a fix for that last week.
>>
>> $ snap install --classic --edge snapcraft
>>
>> or refresh it, in case you already installed via snaps:
>>
>> $ snap refresh --edge snapcraft
>>
>> and then 'make snap-pkg' again.
>> Beware of $PATH in case you have the snap and deb version installed.
>
> Ok, after updating and setting ~/snapcraft/bin/snapcraft ahead of
> /usr/bin in my $PATH, the build completed. Oddly both
> /usr/bin/snapcraft --version and ~/snapcraft/bin/snapcraft --version
> return 2.34, though the build failed with /usr/bin/snapcraft.
>
> --
> Jim
--
bye,
p.
prev parent reply other threads:[~2017-11-29 17:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20171114123834.xsjiy2ynvott4gae@brain>
2017-11-27 11:07 ` [PATCH v3] scripts/package: snap-pkg target Paolo Pisati
2017-11-27 18:33 ` Jim Davis
2017-11-28 17:14 ` Paolo Pisati
2017-11-28 19:35 ` Jim Davis
2017-11-29 7:33 ` Masahiro Yamada
2017-11-29 17:05 ` Paolo Pisati
2017-11-30 23:15 ` Jim Davis
2017-12-05 11:43 ` Paolo Pisati
2017-12-05 21:23 ` Jim Davis
2017-12-06 10:36 ` Masahiro Yamada
2017-12-06 18:14 ` Paolo Pisati
2017-12-07 15:31 ` Masahiro Yamada
2017-12-12 15:08 ` Masahiro Yamada
2017-12-01 12:03 ` Riku Voipio
2017-12-05 11:31 ` Paolo Pisati
2017-11-29 17:03 ` Paolo Pisati [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAMsH0TSJuWLs-pDUyaop5g-LLvG1XuwsaUAap8LnF0NAKJGLKA@mail.gmail.com \
--to=paolo.pisati@canonical.com \
--cc=behanw@converseincode.com \
--cc=jim.epost@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.lkml@markovi.net \
--cc=mka@chromium.org \
--cc=viniciustinti@gmail.com \
--cc=yamada.masahiro@socionext.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).