https://bugzilla.redhat.com/show_bug.cgi?id=2049400 --- Comment #18 from Dominik Wombacher <dominik@xxxxxxxxxxxx> --- (In reply to Nikola Forró from comment #17) > > I would suggest to sync with David Duncan, he's the main admin of the > dist-git repo and can give you access, then you can proceed with the import. > In my opinion it makes no sense to import the originally approved files > first. Agree. I had a call with David. We going to update aws-c-common to the latest version. It's a dependency to update aws-c-cal. In parallel, we have to sort out the package group sponsor topic for me. Otherwise he can't add me as co-maintainer. When that's done I will import aws-c-cal in an updated version. I don't expect fundamental changes with the package. It should still be pretty close to what was approved. -- You are receiving this mail because: You are always notified about changes to this product and component You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2049400 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-spam&short_desc=Report%20of%20Bug%202049400%23c18 -- _______________________________________________ package-review mailing list -- package-review@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to package-review-leave@xxxxxxxxxxxxxxxxxxxxxxx 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/package-review@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
