** Description changed:

  The rust-pyo3 transition is stuck in questing-proposed because rust-
  breezyshim is using a feature from rustc 1.86 named "trait upcasting
  coercion".
  
  Solution 0
  ----------
  Switch the default rustc for Ubuntu 25.10 from rustc-1.85 to rustc-1.86. This 
would require a Feature Freeze Exception and I don't think Foundations is 
interested in this proposal.
  
  Solution 1
  ----------
  Build breezyshim and rdepends with the non-default rustc 1.86 which is 
available in Ubuntu 25.10. I'm not sure how to do this. I think Julian did 
something like this once. I'm not sure if it's practical?
  
  Solution 2
  ----------
  Either use an older version of breezyshim that is both compatible with 
rust-pyo3 0.25 but doesn't use the rustc 1.86 code or replace the rustc 1.86 
code with code compatible with rustc 1.85.
  
  I spent some time working on this. With the time I want to spend on this
  and my very basic rust skills, I wasn't able to get this to work.
  
  Solution 2
  ----------
  Remove rust-breezyshim from Ubuntu. This would also require removing its 
reverse dependencies:
  rust-debian-analyzer
  rust-ognibuild
  rust-upstream-ontologist
  silver-platter
  lintian-brush
  
  lintian-brush is a useful tool for improving .deb packages so I am
  reluctant to choose this option.
  
  Solution 3
  ----------
  Remove the incomplete rust-pyo3 transition from questing-proposed. Remove 
these packages from questing-proposed only:
  
  rust-breezyshim
  rust-deb822-derive
  rust-deb822-fast
  rust-deb822-lossless
  rust-debian-control
  rust-debian-copyright
  rust-debversion
  rust-dep3
  rust-jiter
  rust-launchpadlib
  rust-lexical-parse-float
  rust-lexical-parse-integer
  rust-lexical-util
  rust-pyo3
  rust-pyo3-async-runtimes
  rust-pyo3-async-runtimes-macros
  rust-pyo3-build-config
  rust-pyo3-ffi
  rust-pyo3-filelike
  rust-pyo3-log
  rust-pyo3-macros
  rust-pyo3-macros-backend
  rust-pythonize
  rust-r-description
  rust-wadl
  
  Then for the 26.04 development cycle, someone needs to make sure these
  packages come back into -proposed.
  
  References
  ----------
  
https://launchpad.net/ubuntu/+source/rust-breezyshim/0.6.4-1ubuntu1/+latestbuild/amd64
  https://github.com/rust-lang/lang-team/issues/98
  
+ Other Info
+ ----------
+ Earlier this year, Archive Admins removed the tree-sitter transition from 
plucky-proposed and plucky NEW since it was after Feature Freeze and it was 
decided it was better to not complete the transition and try to keep -proposed 
as uncluttered as possible.
+ 
  Conclusion
  ----------
  I recommend Solution 3.
  
  Handling this issue is helpful to reduce time spent on +1 maintenance by
  people trying to get this stack to migrate out of questing-proposed.

** Description changed:

  The rust-pyo3 transition is stuck in questing-proposed because rust-
- breezyshim is using a feature from rustc 1.86 named "trait upcasting
- coercion".
+ breezyshim fails to build because it is using a feature from rustc 1.86
+ named "trait upcasting coercion".
  
  Solution 0
  ----------
  Switch the default rustc for Ubuntu 25.10 from rustc-1.85 to rustc-1.86. This 
would require a Feature Freeze Exception and I don't think Foundations is 
interested in this proposal.
  
  Solution 1
  ----------
  Build breezyshim and rdepends with the non-default rustc 1.86 which is 
available in Ubuntu 25.10. I'm not sure how to do this. I think Julian did 
something like this once. I'm not sure if it's practical?
  
  Solution 2
  ----------
  Either use an older version of breezyshim that is both compatible with 
rust-pyo3 0.25 but doesn't use the rustc 1.86 code or replace the rustc 1.86 
code with code compatible with rustc 1.85.
  
  I spent some time working on this. With the time I want to spend on this
  and my very basic rust skills, I wasn't able to get this to work.
  
  Solution 2
  ----------
  Remove rust-breezyshim from Ubuntu. This would also require removing its 
reverse dependencies:
  rust-debian-analyzer
  rust-ognibuild
  rust-upstream-ontologist
  silver-platter
  lintian-brush
  
  lintian-brush is a useful tool for improving .deb packages so I am
  reluctant to choose this option.
  
  Solution 3
  ----------
  Remove the incomplete rust-pyo3 transition from questing-proposed. Remove 
these packages from questing-proposed only:
  
  rust-breezyshim
  rust-deb822-derive
  rust-deb822-fast
  rust-deb822-lossless
  rust-debian-control
  rust-debian-copyright
  rust-debversion
  rust-dep3
  rust-jiter
  rust-launchpadlib
  rust-lexical-parse-float
  rust-lexical-parse-integer
  rust-lexical-util
  rust-pyo3
  rust-pyo3-async-runtimes
  rust-pyo3-async-runtimes-macros
  rust-pyo3-build-config
  rust-pyo3-ffi
  rust-pyo3-filelike
  rust-pyo3-log
  rust-pyo3-macros
  rust-pyo3-macros-backend
  rust-pythonize
  rust-r-description
  rust-wadl
  
  Then for the 26.04 development cycle, someone needs to make sure these
  packages come back into -proposed.
  
  References
  ----------
  
https://launchpad.net/ubuntu/+source/rust-breezyshim/0.6.4-1ubuntu1/+latestbuild/amd64
  https://github.com/rust-lang/lang-team/issues/98
  
  Other Info
  ----------
  Earlier this year, Archive Admins removed the tree-sitter transition from 
plucky-proposed and plucky NEW since it was after Feature Freeze and it was 
decided it was better to not complete the transition and try to keep -proposed 
as uncluttered as possible.
  
  Conclusion
  ----------
  I recommend Solution 3.
  
  Handling this issue is helpful to reduce time spent on +1 maintenance by
  people trying to get this stack to migrate out of questing-proposed.

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

Title:
  Remove incomplete rust-pyo3 transition from questing-proposed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rust-pyo3/+bug/2122135/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to