It seems that only the main admin can edit the owners (they have displayed the "edit" button), is that expected? E.g. checking rubygem-puma [1], where I have admin bit, I cannot edit the BZ assignee, while for rubygem-tilt [2] as a main admin, I can. Vít [1] https://src.fedoraproject.org/rpms/rubygem-puma/ [2] https://src.fedoraproject.org/rpms/rubygem-tilt Dne 04. 05. 20 v 17:13 Pierre-Yves Chibon napsal(a): > Good Morning Everyone, > > You may remember the email below from a little while ago. > > Well, we just wanted to let you know that this is now running in production and > the data present in the fedora-scm-requests repo has been migrated and that git > repo has been cleared of a large number of files. > > Let us know if you run into any problems or have any questions with this. > > > Happy packaging! > > Pierre > > > > On Tue, Mar 17, 2020 at 11:58:40AM +0100, Pierre-Yves Chibon wrote: >> Good Morning Everyone, >> >> A little while ago[1], we integrated anitya in dist-git itself, allowing to >> stop using fedora-scm-request's[2] git repository to store this information. >> >> However, this git repository is still being used to store bugzilla overrides >> (i.e.: default assignee on bugzilla ticket when they differ from the point of >> contact (main admin) of the package in dist-git). >> >> Together with Karsten Hopp we worked on integrating this functionality on >> pagure-dist-git[3], thus allowing to get rid entirely of the git repository at >> fedora-scm-request[2]. >> >> This work has been deployed in staging today. We would very much appreciate if >> you could take a few minute of your time and see if it works to your >> liking: https://src.stg.fedoraproject.org/ >> >> The overrides information from production has been migrated yesterday to the >> staging dist-git, so what you see in the UI reflects the current state of the >> overrides in production as of yesterday. >> >> Here is an example with an override: >> https://src.stg.fedoraproject.org/rpms/0ad >> >> >> One note: in the rpms namespace, the UI will always show you the default >> assignee for Fedora and Fedora EPEL, regardless of whether the package is in >> EPEL. >> This is a shortcoming we are aware of and will be looking at fixing in the near >> future but potentially after it has reached production. >> >> >> Thank you for your understanding and help testing this, >> Pierre >> >> >> [1] https://lists.fedoraproject.org/archives/list/devel-announce@xxxxxxxxxxxxxxxxxxxxxxx/message/UWVJBV3RBVCW2IW5Z47QJTBO5T5KDGNJ/ >> [2] https://pagure.io/releng/fedora-scm-requests >> [3] https://pagure.io/pagure-dist-git/ > _______________________________________________ > devel-announce mailing list -- devel-announce@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to devel-announce-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/devel-announce@xxxxxxxxxxxxxxxxxxxxxxx > _______________________________________________ > devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to devel-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/devel@xxxxxxxxxxxxxxxxxxxxxxx _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-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/devel@xxxxxxxxxxxxxxxxxxxxxxx
