Jim Fehlig wrote:
Cristian Morales Vega wrote:
Could someone explain me why we have the factory-maintainer's auto-revoke?
We have perl-Sys-Virt failing for 26 days because it requires libvirt
= 1.0.0. The thing is that libvirt 1.0.0 is packaged in the
Virtualization project, and it was submitted to Factory in the request #140771. The request got rejected because it removed patches without saying so in the changelog. No problem with that, but apparently the request was "auto-revoked"?? Why do we have that? We want the request creator to see the request rejected so he can fix any problem an resubmit. From my understanding of this auto-revoke thing, isn't it just hiding problems?
One could then start making questions about why the request was created by "factory-maintainer" (and not by jfehlig, who did the package update). And how factory-maintainer *auto* revoked its *own* request and then forgot about it. But that probably would just confuse me... So could somebody just explain me what's the purpose of this auto-revoke feature? Am I misunderstanding it or it's really just hiding problems?
Sorry I didn't notice this. I've rather neglected factory prior to and through the holidays. But I've been working on libvirt 1.0.1 for factory and will submit it within a few days after resolving a few remaining issues.
Ok, I've submitted libvirt 1.0.1 to Factory - SR#147454 Regards, Jim -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org