public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: Ferry Toth <fntoth@gmail.com>, openembedded-core@lists.openembedded.org
Cc: Xavier Berger <xavier.berger@bio-logic.net>
Subject: Re: [PATCH v1 1/2] gpg-sign: Add parameters to gpg signature function
Date: Thu, 24 Mar 2022 08:12:44 +0000	[thread overview]
Message-ID: <e2b6066a69cf7933b0618a66b7e1b3589ff6da5c.camel@linuxfoundation.org> (raw)
In-Reply-To: <fe0f9ee8-e3d0-1681-af93-fa97019b8a0c@gmail.com>

On Wed, 2022-03-23 at 19:34 +0100, Ferry Toth wrote:
> Hi Richard,
> 
> I forgot to add a cover letter, sorry for that. The 2 patches  together 
> implement DEB repository signing.
> 
> This is necessary since Gatesgarth |apt| (1.8.2) has become more strict 
> and doesn’t allow unsigned repositories by default.
> 
> It is possible to override this behavior |but||| is more work then to 
> enable signed DEB repositories. These patches makes DEB a first class 
> citizen as IPK and RPM.
> 
> Patches have been in use in meta-intel-edison since Gatesgarth, see 
> https://edison-fw.github.io/meta-intel-edison/5.0-Creating-a-deb-repository.html\

What puzzles me is that we can build root filesystems using apt, we test this on
the autobuilder. Saying repositories are broken since gatesgarth therefore seems
confusing in the commit message.

I guess we must configure apt to override that during the rootfs process and
likely an end user with a remote feed could do the same, possibly with a warning
from apt?

I'm also worried that there isn't any automated testing of this change. The
reason I worry is that since we don't show any testing failures right now, there
is clearly a hole in our automated testing coverage and there is no guarantee
that this feature will keep working. It is these smaller corner case issues
which tend to make or break the project's experience as if a feature is present,
people expect it to work. Can we improve the testing situation?

Cheers,

Richard




  reply	other threads:[~2022-03-24  8:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-22 21:19 [PATCH v1 1/2] gpg-sign: Add parameters to gpg signature function Ferry Toth
2022-03-22 21:19 ` [PATCH v1 2/2] package_manager: sign DEB package feeds Ferry Toth
2022-03-23 18:34 ` [PATCH v1 1/2] gpg-sign: Add parameters to gpg signature function Ferry Toth
2022-03-24  8:12   ` Richard Purdie [this message]
2022-03-24 11:23     ` Ferry Toth
2022-03-24 12:03       ` Richard Purdie
2022-03-24 15:36         ` Ferry Toth
2022-03-24 22:11           ` Ferry Toth
2022-03-24 22:20             ` Richard Purdie
2022-03-28 14:04               ` Ferry Toth
2022-03-25 11:28             ` Ferry Toth
2022-03-25 11:51               ` [OE-core] " Alexander Kanavin
2022-03-25 21:57                 ` Ferry Toth

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=e2b6066a69cf7933b0618a66b7e1b3589ff6da5c.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=fntoth@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=xavier.berger@bio-logic.net \
    /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