sts-sponsors team mailing list archive

[Christian Ehrhardt  <2013081@xxxxxxxxxxxxxxxxxx>]

Your changelog missed a bug reference, this is actually released

 simplestreams | 0.1.0-48-gb936edd4-0ubuntu2            | lunar/universe            | all
 simplestreams | 0.1.0-48-gb936edd4-0ubuntu2            | mantic/universe           | all


** Changed in: simplestreams (Ubuntu)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of MAAS
Maintainers, which is subscribed to simplestreams in Ubuntu.
https://bugs.launchpad.net/bugs/2013081

Title:
  Autopkgtest/build fails, because example gpg key is expired

Status in simplestreams package in Ubuntu:
  Fix Released

Bug description:
  Running the autopkgtest fails to build the package. During the build
  process the example gpg key (examples/keys/example.pub and
  examples/keys/example.sec) gets imported. When the example key is used
  to test the package during build time; the build fails, because gpg
  fails to sign something with the expired gpg key.

  How to verify:
  1. Checkout the source tree
  2. import examples/keys/example.pub with gpg --import examples/keys/example.pub
  3. see details about key: gpg --list-keys 198E8D3C27227898CB4D413CA9714A203967536E

  Should display something like this:
  pub   rsa1024 2013-02-26 [SCEA] [expired: 2023-02-24]
        198E8D3C27227898CB4D413CA9714A203967536E
  uid           [ expired] Simple Streams Test User (Test Usage Only. Do Not Import.) <simplestreams@xxxxxxxxxxxxxxxxx>

  4. Note that the key expired at 24.02.2023
  5. (optional) remove key: gpg --delete-keys 198E8D3C27227898CB4D413CA9714A203967536E

  How to fix this:
  Generate a new key upstream or do the key generation dynamically to avoid this problem entirely.

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