I think we should always add unresponsive maintainer in cc while reporting ticket.

I don't see any important issue to be fixed for xsd package, all I see maintainer is not building for epel7 branch which if requested any provenpackager can build.

Also, I see latest upstream release is already packaged in Fedora.

So either we can orphan this package or just grant access to epel7 branch for required users.

Replying to [comment:1 pnemade]:

I think we should always add unresponsive maintainer in cc while reporting ticket.[[BR]]

I added his mail in cc, but i think it's still useless because he does not reply since months.

I don't see any important issue to be fixed for xsd package, all I see maintainer is not building for epel7 branch which if requested any provenpackager can build.

Also, I see latest upstream release is already packaged in Fedora.[[BR]]

The package needs updates from point of view of packaging, and it will need in future probably.

So either we can orphan this package or just grant access to epel7 branch for required users.[[BR]]

In future should we update it just on EPEL7?

I already said we can orphan xsd package totally if other people also thinks. My only concern is as follows->
It happens that some maintainer just don't want to maintain package for EPEL but only for Fedora. It may happen with anyone that he will not consider or just grant EPEL access to co-maintainers but that should not be taken that we should start filing unresponsive requests and get forcefully packages orphaned.

Is there any other cases of this maintainer's packages where he has not responded? If there are cases then count my +1 to orphan all his packages.

Replying to [comment:4 pnemade]:

I already said we can orphan xsd package totally if other people also thinks. My only concern is as follows->
It happens that some maintainer just don't want to maintain package for EPEL but only for Fedora. It may happen with anyone that he will not consider or just grant EPEL access to co-maintainers but that should not be taken that we should start filing unresponsive requests and get forcefully packages orphaned.

I agree, would be sufficient make known this to the others. :)
I don't want to force nothing, i wish to point out that i have a package blocked since weeks because of this missing package on EPEL7 and i don't know how to unblock that issue.

Is there any other cases of this maintainer's packages where he has not responded? If there are cases then count my +1 to orphan all his packages.

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

In others packages he is a co-maintainer, so he has not unique responsabilities.

Hi!

Thank you for adding me to the CC.

I do not have an EPEL box to test on so help with EPEL builds is appreciated.

I have granted commit access on xsd to sagitter@ Please discuss the details of other changes you plan to make to the packaging beforehand.

Thank you

Anttix.

Replying to [comment:6 anttix]:

Hi!

Thank you for adding me to the CC.

Hi anttix.
Nice to meet you.

I do not have an EPEL box to test on so help with EPEL builds is appreciated.

I have granted commit access on xsd to sagitter@ Please discuss the details of other changes you plan to make to the packaging beforehand.

Thanks. I made some modifications on your SPEC file; i will open a bugzilla ticket to talk about them and for a new package review before to commit a new packaging release.

Thank you

Anttix.

Antonio

Replying to [comment:6 anttix]:

Hi!

Thank you for adding me to the CC.

Hi anttix.
Nice to meet you.

I do not have an EPEL box to test on so help with EPEL builds is appreciated.

I have granted commit access on xsd to sagitter@ Please discuss the details of other changes you plan to make to the packaging beforehand.

Thanks. I made some modifications on your SPEC file; i will open a bugzilla ticket to talk about them and for a new package review before to commit a new packaging release.

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

Thank you

Anttix.

Antonio

Hi sagitter,

I see you have become co-maintainer now for xsd package and there is an epel7 branch also available. If there is nothing left to be done here then we can resolve this ticket.

Replying to [comment:9 pnemade]:

Hi sagitter,

I see you have become co-maintainer now for xsd package and there is an epel7 branch also available. If there is nothing left to be done here then we can resolve this ticket.

Hi,

we can close this ticket.
Thanks.