Spec URL: https://raw.githubusercontent.com/tylerfanelli/rust-asn1-rs-derive_candidate/refs/heads/master/rust-asn1-rs-derive.spec SRPM URL: https://github.com/tylerfanelli/rust-asn1-rs-derive_candidate/raw/refs/heads/master/rust-asn1-rs-derive-0.5.1-1.fc42.src.rpm Description: Derive macros for rust-asn1-rs crate Fedora Account System Username: tfanelli
Copr build: https://copr.fedorainfracloud.org/coprs/build/8184261 (succeeded) Review template: https://download.copr.fedorainfracloud.org/results/@fedora-review/fedora-review-2322184-rust-asn1-rs-derive/fedora-rawhide-x86_64/08184261-rust-asn1-rs-derive/fedora-review/review.txt Please take a look if any issues were found. --- This comment was created by the fedora-review-service https://github.com/FrostyX/fedora-review-service If you want to trigger a new Copr build, add a comment containing new Spec and SRPM URLs or [fedora-review-service-build] string.
*** Bug 2322185 has been marked as a duplicate of this bug. ***
Hi Fabio, I've submitted all required information and the build succeeded, I just need approval to continue with the new package process. For the future, am I able to do this process on my own, without the approval of anyone else? I only ask because I have to introduce a few more packages and don't want to interrupt others if not necessary.
> For the future, am I able to do this process on my own, without the approval of anyone else? No, all new packages need approval by a second person. To some degree, I really wonder how you got to be a packager without knowing these basics 😅 Additionally, in this case, a request for this package was already submitted elsewhere, so I'll close this one as a duplicate. *** This bug has been marked as a duplicate of bug 2312632 ***
(In reply to Fabio Valentini from comment #4) > > For the future, am I able to do this process on my own, without the approval of anyone else? > > No, all new packages need approval by a second person. > To some degree, I really wonder how you got to be a packager without knowing > these basics 😅 Lame and unhelpful comment. Not everyone lives and breaths fedora policy and packaging. I think it's reasonable for someone who rarely submits new packages to ask if there's a simpler process they are missing, especially considering how much you've helped streamline the rust package process with rust2rpm
I apologize for yesterday's quip - it was indeed not helpful. I guess the NEEDINFO request for me threw me off - at least in Fedora, it's only used for really important actions and many contributors perceive it as "aggressive nagging". Just CCing me on this bug would have sufficed to get my attention. > I think it's reasonable for someone who rarely submits new packages to ask > if there's a simpler process they are missing, especially considering how much > you've helped streamline the rust package process with rust2rpm I'm happy that you perceive it as streamlined. But no, there are usually no shortcuts you can take for adding a new package to Fedora - with some small exceptions, see https://docs.fedoraproject.org/en-US/packaging-guidelines/ReviewGuidelines/#_package_review_process wrt/ Rust packages, the only relevant exception is usually the one for "compat" packages, i.e. for providing more than one version of a crate that is already packaged.