Great, thanks Hlib! Security Ack is in.
MIR ack was with conditions Required TODOs: 1. The package has not documented how to refresh vendored code. Please document it. It was not mentioned, but I see it in debian/README.Debian in the most recent version. It isn't perfect, but it explaines how to update the whole tree to a new rust coreutils. Furthermore d/rules has a vendor-tarball target which mostly matches https://canonical-ubuntu-project.readthedocs-hosted.com/MIR/mir-rust/ 2. The package does not have autopkgtest. This was discussed in comment #4. Due to the way when rust builds and not linking late the build test is covering more than usual. It was mentioned that a good compromise might be to have gnu coreutils Test-Depends on rust-coreutils - I assume to run the gnu tests of behavior against the partial rust-coreutils system. But I've not seen that in the changelog of src:coreutils I'd ask you to track and add that, but would not consider it blocking for 25.10 (but early 26.04 please) 3. Please address the translation issue. Explained in comment #4 , I think there is nothing more we can do there in a hurry. It is and will be transalated, but not in a compatible format. 4a. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1097827 False positive 4b. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1107270 Fixed in https://bugs.launchpad.net/ubuntu/+source/rust- coreutils/+bug/2112445 aling with various other similar "oh we need to fix this remaining mismatch of behavior" 5. There quite a few open Ubuntu bugs, please address them https://bugs.launchpad.net/ubuntu/+source/rust-coreutils/+bugs Until addressed mitigated by a mix and match with GNU coreutils as explained in comment #5 6. Review upstream issues and assess which of them are likely to cause problems. and We can't consider it done, but uploads like https://bugs.launchpad.net/ubuntu/+source/rust-coreutils/+bug/2112445 do exactly that. As long as you are willing and comitted to continue on that this is no more gating. Getting it into 25.10 is our chance to know what else is nice to have or very important. I think the recommended todo will continue to be true for a while which said "Address as many as possible of the upstream bugs triaged in (6)." Just the same applies for some topics out of the discussions by the security review. I think thereby the remaining aspects of #2,#5,#6,#7 are all on the "recommended level". Those are all about "more testing" (2) and Fixing more bugs (5,6,7) to make it replace coreutils with less friction. I highly encourage you follow up on these, but as mentioned getting it into the questing release will open up more feedback and allow us to fill and prioritize the queues for #5 #6 #7 better. This is hereby ready for promotion (with the big ask to continue on this more intense than usual, allocate time for it I'm sure it will be needed). It is in component mismatches already - setting state accordingly. I'll leave the actual promotion move to Seb in case there is more to coordinate. ** Changed in: rust-coreutils (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2111815 Title: [MIR] rust-coreutils To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rust-coreutils/+bug/2111815/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
