lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Wed, 6 Dec 2017 19:14:26 +0100
From:   Paolo Pisati <>
To:     Masahiro Yamada <>
Cc:     Jim Davis <>,
        Michal Marek <>,
        Behan Webster <>,
        Matthias Kaehlcke <>,
        Vinícius Tinti <>,
        linux-kbuild <>,
        linux-kernel <>
Subject: Re: [PATCH v3] scripts/package: snap-pkg target

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, because "plugin: kernel" needs to know
> the kernel-build system internal.

Well, in this case, i had to fix the 'kernel-with-firmware' option to
skip the 'firmware_install' step since
we took it by default - let's say that in the future the
'modules_install' target is removed or change name,
then i'll have to patch snapcraft.

Wrt updating from -edge, i told you to take it from there because snap
packages land there more often and more quickly
compared to the canonicaldeb  archive, so from a developer perspective
it's easier&quicker to iterate over it, but sooner
or later (e.g. once snapcraft 2.36.1 reaches the snap -stable
channel), it will be copied to the deb archive too -
IOW, you would get using apt-get only too.

Powered by blists - more mailing lists