nemos-team team mailing list archive

[Steve Langasek <2043448@xxxxxxxxxxxxxxxxxx>]

Hi, this hasn't been accepted yet from the Ubuntu NEW queue.  When I
look at this package I'm puzzled.  If this is a snakeoil key that
everyone has access to the private part of, why does it need to be in
the archive?  I guess that might be because you want the artifacts from
the other packages named to be signed by it consistently so that (for
dev purposes only) the hardware can have the single public key enrolled
and consume them directly, without having to do local re-signing.  Do I
have that right?

** Changed in: ubuntu
       Status: In Progress => Incomplete

-- 
You received this bug notification because you are a member of NemOS
Team, which is a bug assignee.
https://bugs.launchpad.net/bugs/2043448

Title:
  [needs-packaging] nemos-dev-key

Status in Ubuntu:
  Incomplete

Bug description:
  [needs-packaging] nemos-dev-key (1.3)
  For Erlangen project, we have to provide a nemos-dev-key to the customer via Ubuntu archive (universe).
  The nemos-dev-key will be used for arm-trusted-firmware-s32, optee-os-s32, and optee-test-s32

  URL: https://launchpad.net/~nemos-team/+archive/ubuntu/archive-staging/+packages
  Source code: https://code.launchpad.net/~nemos-team/nemos/+git/nemos-dev-key/+ref/ubuntu/devel
  License: https://git.launchpad.net/~nemos-team/nemos/+git/nemos-dev-key/tree/debian/copyright
  Notes: The nemos-dev-key [Noble]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2043448/+subscriptions