Fix issues for reivew.

[junaruga]

Hi,
I could pass the review for the ticket https://bugzilla.redhat.com/show_bug.cgi?id=1326504#c35 .
This is the updated version. I wish you merge it.

By the way, I requested to create the htslib repository and branches.
https://bugzilla.redhat.com/show_bug.cgi?id=1326504#c35 .

But it was declined, because I am not the creator of the bugzilla ticket.
https://pagure.io/releng/fedora-scm-requests/issue/17763#comment-602780

So, I need to ask you to request the repository.
See https://bugzilla.redhat.com/show_bug.cgi?id=1326504#c35 review process document. This is what you need to do.

Thank you.

[SamStudio8]

Thanks Jun!

[junaruga]

Hi Sam, I am asking Fedora to get a "sponsor" role for my account to be a sponsor of you.
But I am not sure that I can get it.
https://pagure.io/packager-sponsors/issue/402

To create the repository on Fedora, I like you to get a sponsor from someone.

Here the documents.

• https://fedoraproject.org/wiki/Package_Review_Process

  If you have not yet been sponsored, request sponsorship by raising an issue at https://pagure.io/packager-sponsors/

• https://fedoraproject.org/wiki/How_to_get_sponsored_into_the_packager_group

[SamStudio8]

Hi Jun! Thanks for the help, if you are already a package author previously, I don't mind if you would like to be the official maintainer as it means we could bypass having to wait for sponsorship.

…

On Wed, Oct 9, 2019 at 11:17 AM Jun Aruga ***@***.***> wrote: Hi Sam, I am asking Fedora to get a "sponsor" role for my account to be a sponsor of you. But I am not sure that I can get it. https://pagure.io/packager-sponsors/issue/402 To create the repository on Fedora, I like you to get a sponsor from someone. Here the documents. - https://fedoraproject.org/wiki/Package_Review_Process If you have not yet been sponsored, request sponsorship by raising an issue at https://pagure.io/packager-sponsors/ - https://fedoraproject.org/wiki/How_to_get_sponsored_into_the_packager_group — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#4?email_source=notifications&email_token=AAIN6OTYNEVT5A6PCDE4Q7DQNWVUDA5CNFSM4I6GRVUKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAXMWOY#issuecomment-539937595>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAIN6OQDJKVGBQNKJUESSUDQNWVUDANCNFSM4I6GRVUA> .

[junaruga]

Sure, okay. I will open own review request, closing current ticket like

https://bugzilla.redhat.com/show_bug.cgi?id=1326504#c37
alternatively create your own review request and close this bug as duplicate and block this bug as FE-DEADREVIEW. If Sam request the package, he will be the maintainer and not you.

[SamStudio8]

Great. I think this makes the most sense. I am happy to help with future maintenance but this means we won't have to go through the sponsor process.

…

On Wed, Oct 9, 2019 at 11:31 AM Jun Aruga ***@***.***> wrote: Sure, okay. I open own review request, closing current ticket like https://bugzilla.redhat.com/show_bug.cgi?id=1326504#c37 alternatively create your own review request and close this bug as duplicate and block this bug as FE-DEADREVIEW. If Sam request the package, he will be the maintainer and not you. — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#4?email_source=notifications&email_token=AAIN6ORZNSMDAQQVTJRBNL3QNWXG5A5CNFSM4I6GRVUKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAXNZDY#issuecomment-539942031>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAIN6OSCI6ZKZFBIV5XGSODQNWXG5ANCNFSM4I6GRVUA> .