[Bug 2089690] Re: [MIR] rust-sequoia-sq

[Lukas Märdian]

** Description changed:

  TBD
  
- Foundations should probably make a case for replacing GnuPG with Sequoia
- in "main", filing corresponding MIRs for the needed sequoia components.
+ Foundations should probably make a case for replacing GnuPG with Sequoia in "main", filing corresponding MIRs for the needed sequoia components. This due to "gnupg2" currently pulling in transitive dependencies on "rust-sequoia-chameleon-gnupg" and "rust-sequoia-sq", introducing a component-mismatch:
+ https://ubuntu-archive-team.ubuntu.com/component-mismatches-proposed.svg
  
  MIR team usually likes to see some kind of transition plan, how to get
  rid of the older alternative (GPG) when a new one is introduced. Or
  technical solutions, such as a package split to ship only binary
  packages in main that are non-duplicates, even though the source package
  of two components might have some overlap.
  
  See https://github.com/canonical/ubuntu-mir/blob/main/vendoring/Rust.md
  for vendoring Rust dependencies.

** Description changed:

  TBD
  
- Foundations should probably make a case for replacing GnuPG with Sequoia in "main", filing corresponding MIRs for the needed sequoia components. This due to "gnupg2" currently pulling in transitive dependencies on "rust-sequoia-chameleon-gnupg" and "rust-sequoia-sq", introducing a component-mismatch:
+ Foundations should probably make a case for replacing GnuPG with Sequoia in "main", filing corresponding MIRs for the needed sequoia components. This due to "gnupg2" as of 2.4.4-2ubuntu19 is pulling in transitive dependencies on "rust-sequoia-chameleon-gnupg" and "rust-sequoia-sq", introducing a component-mismatch:
  https://ubuntu-archive-team.ubuntu.com/component-mismatches-proposed.svg
  
  MIR team usually likes to see some kind of transition plan, how to get
  rid of the older alternative (GPG) when a new one is introduced. Or
  technical solutions, such as a package split to ship only binary
  packages in main that are non-duplicates, even though the source package
  of two components might have some overlap.
  
  See https://github.com/canonical/ubuntu-mir/blob/main/vendoring/Rust.md
  for vendoring Rust dependencies.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to gnupg2 in Ubuntu.
https://bugs.launchpad.net/bugs/2089690

Title:
  [MIR] rust-sequoia-sq

Status in gnupg2 package in Ubuntu:
  New
Status in rust-sequoia-chameleon-gnupg package in Ubuntu:
  New
Status in rust-sequoia-sq package in Ubuntu:
  Incomplete

Bug description:
  TBD

  Foundations should probably make a case for replacing GnuPG with Sequoia in "main", filing corresponding MIRs for the needed sequoia components. This due to "gnupg2" as of 2.4.4-2ubuntu19 is pulling in transitive dependencies on "rust-sequoia-chameleon-gnupg" and "rust-sequoia-sq", introducing a component-mismatch:
  https://ubuntu-archive-team.ubuntu.com/component-mismatches-proposed.svg

  MIR team usually likes to see some kind of transition plan, how to get
  rid of the older alternative (GPG) when a new one is introduced. Or
  technical solutions, such as a package split to ship only binary
  packages in main that are non-duplicates, even though the source
  package of two components might have some overlap.

  See https://github.com/canonical/ubuntu-
  mir/blob/main/vendoring/Rust.md for vendoring Rust dependencies.

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