Indeed let us re-check after the security ack.
Slyon is unavailable, as agreed in the MIR meeting I'll have a look at the open 
tasks:

# Notes
#0 - rpds-py will replace pyrsistent, which is going to be demoted from "main"

OK
the only thing in main holding it is python3-jsonschema which is hereby changed.
pyrsistent would go to auto-demotions then.

#1 - I'm requesting security review, due to parsing untrusted (user) source code
     in vendor/proc-macro2 and for tracking the vendored crates

OK
Was approved

Required TODOs:
#2 - The package should make use of "XS-Vendored-Sources-Rust", either via
     dh-cargo or manually, see:
     https://wiki.ubuntu.com/RustCodeInMain#Rust_vendored_sources_tracking
     => compare to "mdevctl" or "gnome-snapshot"

OK
Was done in 0.20.0-0ubuntu3

Recommended TODOs:
#3 - The package should get a team bug subscriber before being promoted

OK
Done in comment 10

#4 - Consider if dropping non-linux stuff from vendor/libc is feasible
(probably not..)

Not done, but was only optional

#5 - Diverging from Debian, using a -0ubuntuX version is not ideal, but there's
     not a lot we can do about it other than slowly tring to get the rust-*-dev
     packages into main, one by one.

For now diverging which is ok.

So other than the long term general sentiment of maybe being time to
revisit the rust rules (years have passed, could be better) this is
perfectly fine. => Approving, as it shows in mismatches state is Fix
committed.

** Changed in: rpds-py (Ubuntu)
       Status: New => Fix Committed

** Changed in: rpds-py (Ubuntu)
     Assignee: Christian Ehrhardt  (paelzer) => (unassigned)

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

Title:
  [MIR] rpds-py

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rpds-py/+bug/2072621/+subscriptions


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

Reply via email to