https://bugzilla.redhat.com/show_bug.cgi?id=2388375



--- Comment #41 from Akiyoshi Kurita <[email protected]> ---
Spec URL:
https://raw.githubusercontent.com/redadmin-k/gshogi-fedora44/refs/heads/main/gshogi.spec
SRPM URL:
https://github.com/redadmin-k/gshogi-fedora44/raw/refs/heads/main/gshogi-0.5.1%5E20250818.git7c4bd90-2.fc44.src.rpm

Dear Cristian Le,

First of all, I would like to thank you again for your continuous and patient
reviews.
As a beginner, I have truly benefited from your detailed feedback, and the
quality of this RPM package has undoubtedly improved thanks to your guidance. I
really appreciate the time and effort you have dedicated to helping me.

I have prepared the updated Spec and SRPM above.
The Copr build succeeded successfully:
https://copr.fedorainfracloud.org/coprs/build/9441986

The only reported issue is an “Upstream MD5sum check error”, which is a known
false positive with GitHub auto-generated tarballs (their compression can vary,
causing checksum mismatches even for the same commit). This is expected and not
an actual issue with the package.

I kindly ask for your review once again at your convenience.
Thank you very much for your time and support.

Best regards,
Akiyoshi Kurita


-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are always notified about changes to this product and component
https://bugzilla.redhat.com/show_bug.cgi?id=2388375

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-spam&short_desc=Report%20of%20Bug%202388375%23c41

-- 
_______________________________________________
package-review mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to