From: Masahiro Yamada <yamada.masahiro@socionext.com>
To: Jim Davis <jim.epost@gmail.com>,
Paolo Pisati <paolo.pisati@canonical.com>
Cc: "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 16:33:03 +0900 [thread overview]
Message-ID: <CAK7LNARNfOzuR72U6Co0GYt7=7V4u8TmTUQAsB8R7H_5QYQ_5A@mail.gmail.com> (raw)
In-Reply-To: <CA+r1ZhgFQS6EEzazw0YZXhYqm+WN3mp69mGyaeNpX36WZLABrA@mail.gmail.com>
2017-11-29 4:35 GMT+09:00 Jim Davis <jim.epost@gmail.com>:
> 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
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
Worked for me too,
after updating snapcraft.
Is it really impossible to check the snapcraft version?
What is the minimum version? 2.35 ?
--
Best Regards
Masahiro Yamada
next prev parent reply other threads:[~2017-11-29 7:33 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 [this message]
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
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='CAK7LNARNfOzuR72U6Co0GYt7=7V4u8TmTUQAsB8R7H_5QYQ_5A@mail.gmail.com' \
--to=yamada.masahiro@socionext.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=paolo.pisati@canonical.com \
--cc=viniciustinti@gmail.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).