** Description changed:

  [Impact]
- We want to provide an easy tool to allow users to refresh signing keys. This 
feature works for deb822 sources, classic sources are TBD.
+ We want to provide an easy tool to allow users to refresh signing keys. This 
feature works for both deb822 sources and classic sources.
  
  [Test plan]
  
  We have multiple test cases:
  
  1. Add a weak PPA, ensure its key is refreshed.
  2. Add a weak private PPA and ensure that it does not fail the process, then 
retry with --login
  3. Add a second private PPA and ensure that we only see a single login 
request with --login
  
+ For 24.04:
+ A. Add a weak PPA as a deb822 (23.10), ensure its key is refreshed.
+ B. Add a superflous key for a deb822 source with Signed-By and observe key 
file deletion.
+ 
  [Where problems could occur]
  The new feature could not work in all cases.
  
  The launchpad login caching could possibly cause some problems, there
  may be bugs there, but our test plan checks for both non-login and login
  cases.

** Description changed:

  [Impact]
  We want to provide an easy tool to allow users to refresh signing keys. This 
feature works for both deb822 sources and classic sources.
  
  [Test plan]
  
- We have multiple test cases:
+ For all releases:
  
  1. Add a weak PPA, ensure its key is refreshed.
  2. Add a weak private PPA and ensure that it does not fail the process, then 
retry with --login
  3. Add a second private PPA and ensure that we only see a single login 
request with --login
  
  For 24.04:
- A. Add a weak PPA as a deb822 (23.10), ensure its key is refreshed.
+ A. Add a weak PPA as a .list (23.10), ensure its key is refreshed.
  B. Add a superflous key for a deb822 source with Signed-By and observe key 
file deletion.
  
  [Where problems could occur]
  The new feature could not work in all cases.
  
  The launchpad login caching could possibly cause some problems, there
  may be bugs there, but our test plan checks for both non-login and login
  cases.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/2077162

Title:
  [FFe/SRU] add-apt-repository --refresh-keys

Status in software-properties package in Ubuntu:
  New

Bug description:
  [Impact]
  We want to provide an easy tool to allow users to refresh signing keys. This 
feature works for both deb822 sources and classic sources.

  [Test plan]

  For all releases:

  1. Add a weak PPA, ensure its key is refreshed.
  2. Add a weak private PPA and ensure that it does not fail the process, then 
retry with --login
  3. Add a second private PPA and ensure that we only see a single login 
request with --login

  For 24.04:
  A. Add a weak PPA as a .list (23.10), ensure its key is refreshed.
  B. Add a superflous key for a deb822 source with Signed-By and observe key 
file deletion.

  [Where problems could occur]
  The new feature could not work in all cases.

  The launchpad login caching could possibly cause some problems, there
  may be bugs there, but our test plan checks for both non-login and
  login cases.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2077162/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to