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@lists.fedorapro... [2] https://pagure.io/releng/fedora-scm-requests [3] https://pagure.io/pagure-dist-git/ _______________________________________________ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-leave@lists.fedoraproject.org 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@lists.fedorapro...
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.
https://src.fedoraproject.org/rpms/setroubleshoot - main admin - plautrba@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1814223 - Assignee Petr Lautrbach
but
https://src.stg.fedoraproject.org/rpms/setroubleshoot -
Bugzilla Assignee: Fedora: dwalsh EPEL: dwalsh
On Tue, Mar 17, 2020 at 01:17:13PM +0100, Petr Lautrbach wrote:
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.
https://src.fedoraproject.org/rpms/setroubleshoot - main admin - plautrba@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1814223 - Assignee Petr Lautrbach
but
https://src.stg.fedoraproject.org/rpms/setroubleshoot -
Bugzilla Assignee: Fedora: dwalsh EPEL: dwalsh
This is because the main maintainer of the package in staging is still dwalsh and there is no overrides that I can see in fedora-scm-requests. In production, you can see the main admin is plautrba, so once we move this to production, plautrba will show as default assignee for both Fedora and EPEL.
Pierre
On 17. 03. 20 11:58, Pierre-Yves Chibon wrote:
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].
Thank You both \o/
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/
1. Can you make the usernames clickable please?
2. I don't understand how to update the information, I can only understand how to read it.
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.
When the data does not reflect the state of the fedora-scm-requests repo, should we report it as a bug? Example:
https://pagure.io/releng/fedora-scm-requests/blob/master/f/rpms/python-tox https://src.stg.fedoraproject.org/rpms/python-tox
On Tue, Mar 17, 2020 at 01:23:59PM +0100, Miro Hrončok wrote:
On 17. 03. 20 11:58, Pierre-Yves Chibon wrote:
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].
Thank You both \o/
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/
- Can you make the usernames clickable please?
That should be doable, to http://src.stg.fedoraproject.org/user/<name> I guess?
- I don't understand how to update the information, I can only understand
how to read it.
If you are logged in and on a package where you have admin rights, there should be an "update" button underneath, clicking it makes a pop-up (a modal) appear, in which you can update the settings.
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.
When the data does not reflect the state of the fedora-scm-requests repo, should we report it as a bug? Example:
https://pagure.io/releng/fedora-scm-requests/blob/master/f/rpms/python-tox https://src.stg.fedoraproject.org/rpms/python-tox
Reporting here should be enough, I'll check this.
Thanks! :)
Pierre
On 17. 03. 20 14:14, Pierre-Yves Chibon wrote:
On Tue, Mar 17, 2020 at 01:23:59PM +0100, Miro Hrončok wrote:
On 17. 03. 20 11:58, Pierre-Yves Chibon wrote:
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].
Thank You both \o/
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/
- Can you make the usernames clickable please?
That should be doable, to http://src.stg.fedoraproject.org/user/<name> I guess?
I guess so. Plus extra care for groups.
- I don't understand how to update the information, I can only understand
how to read it.
If you are logged in and on a package where you have admin rights, there should be an "update" button underneath, clicking it makes a pop-up (a modal) appear, in which you can update the settings.
It appears you need to be main admin to do this. Is that intended?
The fields seem to have no validation:
https://src.stg.fedoraproject.org/rpms/python-pip
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.
When the data does not reflect the state of the fedora-scm-requests repo, should we report it as a bug? Example:
https://pagure.io/releng/fedora-scm-requests/blob/master/f/rpms/python-tox https://src.stg.fedoraproject.org/rpms/python-tox
Reporting here should be enough, I'll check this.
OK. Thanks.
On Tue, Mar 17, 2020 at 02:26:18PM +0100, Miro Hrončok wrote:
On 17. 03. 20 14:14, Pierre-Yves Chibon wrote:
On Tue, Mar 17, 2020 at 01:23:59PM +0100, Miro Hrončok wrote:
On 17. 03. 20 11:58, Pierre-Yves Chibon wrote:
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].
Thank You both \o/
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/
- Can you make the usernames clickable please?
That should be doable, to http://src.stg.fedoraproject.org/user/<name> I guess?
I guess so. Plus extra care for groups.
- I don't understand how to update the information, I can only understand
how to read it.
If you are logged in and on a package where you have admin rights, there should be an "update" button underneath, clicking it makes a pop-up (a modal) appear, in which you can update the settings.
It appears you need to be main admin to do this. Is that intended?
Reading the code it is definitely intended: https://pagure.io/pagure-dist-git/blob/master/f/pagure_distgit/plugin.py#_41... but I guess we could relax this to all project admins.
The fields seem to have no validation:
That is indeed correct for the moment.
Pierre
On 17. 03. 20 14:45, Pierre-Yves Chibon wrote:
If you are logged in and on a package where you have admin rights, there should be an "update" button underneath, clicking it makes a pop-up (a modal) appear, in which you can update the settings.
It appears you need to be main admin to do this. Is that intended?
Reading the code it is definitely intended: https://pagure.io/pagure-dist-git/blob/master/f/pagure_distgit/plugin.py#_41... but I guess we could relax this to all project admins.
May I suggest that members of the cvsadmin group should be able to change this as well?
I can change the main admin but not the bugizlla assignee which is kinda weird.
I am able to get the thing done by making myself the main admin, doing it and giving the package back to the original owner, but it feels silly and overcomplicated.
Should I file a ticket at https://pagure.io/pagure-dist-git/ ?
On Wed, Apr 08, 2020 at 11:56:01AM +0200, Miro Hrončok wrote:
On 17. 03. 20 14:45, Pierre-Yves Chibon wrote:
If you are logged in and on a package where you have admin rights, there should be an "update" button underneath, clicking it makes a pop-up (a modal) appear, in which you can update the settings.
It appears you need to be main admin to do this. Is that intended?
Reading the code it is definitely intended: https://pagure.io/pagure-dist-git/blob/master/f/pagure_distgit/plugin.py#_41... but I guess we could relax this to all project admins.
May I suggest that members of the cvsadmin group should be able to change this as well?
I can change the main admin but not the bugizlla assignee which is kinda weird.
I am able to get the thing done by making myself the main admin, doing it and giving the package back to the original owner, but it feels silly and overcomplicated.
That is a good point
Should I file a ticket at https://pagure.io/pagure-dist-git/ ?
Please yes :)
Pierre
On Tue, Mar 17, 2020 at 02:26:18PM +0100, Miro Hrončok wrote:
On 17. 03. 20 14:14, Pierre-Yves Chibon wrote:
On Tue, Mar 17, 2020 at 01:23:59PM +0100, Miro Hrončok wrote:
On 17. 03. 20 11:58, Pierre-Yves Chibon wrote:
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].
Thank You both \o/
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/
- Can you make the usernames clickable please?
That should be doable, to http://src.stg.fedoraproject.org/user/<name> I guess?
I guess so. Plus extra care for groups.
- I don't understand how to update the information, I can only understand
how to read it.
If you are logged in and on a package where you have admin rights, there should be an "update" button underneath, clicking it makes a pop-up (a modal) appear, in which you can update the settings.
It appears you need to be main admin to do this. Is that intended?
The fields seem to have no validation:
This has been addressed and the new code deployed in staging.
If there are no other issues found/reported, I would like to look at pushing this to production next week.
Thanks for your feedback!
Pierre
On Tue, Mar 17, 2020 at 02:14:46PM +0100, Pierre-Yves Chibon wrote:
If you are logged in and on a package where you have admin rights, there should be an "update" button underneath, clicking it makes a pop-up (a modal) appear, in which you can update the settings.
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.
When the data does not reflect the state of the fedora-scm-requests repo, should we report it as a bug? Example:
https://pagure.io/releng/fedora-scm-requests/blob/master/f/rpms/python-tox https://src.stg.fedoraproject.org/rpms/python-tox
Reporting here should be enough, I'll check this.
Ok, so pebkac on this one. I kept doing a git pull that was showing my git repo as up to date, except that it was pulling from my fork... Pulling from the right (upstream) repo did bring the override info for python-tox and the script is re-running right now.
Sorry for the inconvenience,
Pierre
Dne 17. 03. 20 v 11:58 Pierre-Yves Chibon napsal(a):
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].
Am I supposed to be able to modify the owners?
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.
Packages coming from RHEL are the same I assume. I just asking, because there is difference in not being in EPEL and being in EPEL transitively from RHEL.
Vít
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@lists.fedorapro... [2] https://pagure.io/releng/fedora-scm-requests [3] https://pagure.io/pagure-dist-git/
On Tue, Mar 17, 2020 at 01:25:03PM +0100, Vít Ondruch wrote:
Dne 17. 03. 20 v 11:58 Pierre-Yves Chibon napsal(a):
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].
Am I supposed to be able to modify the owners?
Yes and your comment as well as Miro's makes me wonder if something isn't working as it should.
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.
Packages coming from RHEL are the same I assume. I just asking, because there is difference in not being in EPEL and being in EPEL transitively from RHEL.
I am not quite following you here, what I meant is that the UI always displays Fedora and EPEL for the rpms namespace, even, for example, for the kernel which is definitely not in EPEL. I am not sure I'm clearer, so I must be missing something here, sorry.
Pierre
Dne 17. 03. 20 v 14:24 Pierre-Yves Chibon napsal(a):
On Tue, Mar 17, 2020 at 01:25:03PM +0100, Vít Ondruch wrote:
Dne 17. 03. 20 v 11:58 Pierre-Yves Chibon napsal(a):
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].
Am I supposed to be able to modify the owners?
Yes and your comment as well as Miro's makes me wonder if something isn't working as it should.
The "Update" together with the icon is probably not intuitive. I thought that the button will refresh the fields or something.
Also, the UX differs from the "monitoring status", where there is popup.
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.
Packages coming from RHEL are the same I assume. I just asking, because there is difference in not being in EPEL and being in EPEL transitively from RHEL.
I am not quite following you here, what I meant is that the UI always displays Fedora and EPEL for the rpms namespace, even, for example, for the kernel which is definitely not in EPEL. I am not sure I'm clearer, so I must be missing something here, sorry.
If package might be in EPEL, but it is not, because nobody have imported it seems to be different case then Kernel, which can't be in EPEL. These two should be distinguished.
Vít
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@lists.fedorapro... [2] https://pagure.io/releng/fedora-scm-requests [3] https://pagure.io/pagure-dist-git/
_______________________________________________ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-leave@lists.fedoraproject.org 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@lists.fedorapro...
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@lists.fedorapro... [2] https://pagure.io/releng/fedora-scm-requests [3] https://pagure.io/pagure-dist-git/
devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-leave@lists.fedoraproject.org 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@lists.fedorapro... _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-leave@lists.fedoraproject.org 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@lists.fedoraproject.org
And since I am asking questions like this, how does it work for group owned packages (if there are any, can't find any example ATM, but there used to be, right?)?
Vít
Dne 04. 05. 20 v 19:02 Vít Ondruch napsal(a):
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@lists.fedorapro... [2] https://pagure.io/releng/fedora-scm-requests [3] https://pagure.io/pagure-dist-git/
devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-leave@lists.fedoraproject.org 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@lists.fedorapro... _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-leave@lists.fedoraproject.org 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@lists.fedoraproject.org
devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-leave@lists.fedoraproject.org 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@lists.fedoraproject.org
On Mon, May 04, 2020 at 07:02:35PM +0200, Vít Ondruch wrote:
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.
Miro has asked for cvsadmin to be able to edit the bugzilla overrides and the simplest solution to this request was to allow all project admins to change them. I have a patch (already merged) that I'm thinking to apply on the current release to make this available sooner.
Pierre
I also wonder what happened to rubygem-slop [1], because it says it is retired, while it should be only orphaned [2].
Vít
[1] https://src.fedoraproject.org/rpms/rubygem-slop
[2] https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/...
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@lists.fedorapro... [2] https://pagure.io/releng/fedora-scm-requests [3] https://pagure.io/pagure-dist-git/
devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-leave@lists.fedoraproject.org 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@lists.fedorapro... _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-leave@lists.fedoraproject.org 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@lists.fedoraproject.org
There is very likely more packages like this:
https://src.fedoraproject.org/rpms/nodejs-tern-cordovajs
Vít
Dne 05. 05. 20 v 8:53 Vít Ondruch napsal(a):
I also wonder what happened to rubygem-slop [1], because it says it is retired, while it should be only orphaned [2].
Vít
[1] https://src.fedoraproject.org/rpms/rubygem-slop
[2] https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/...
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@lists.fedorapro... [2] https://pagure.io/releng/fedora-scm-requests [3] https://pagure.io/pagure-dist-git/
devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-leave@lists.fedoraproject.org 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@lists.fedorapro... _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-leave@lists.fedoraproject.org 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@lists.fedoraproject.org
devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-leave@lists.fedoraproject.org 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@lists.fedoraproject.org
On Tue, May 05, 2020 at 08:53:27AM +0200, Vít Ondruch wrote:
I also wonder what happened to rubygem-slop [1], because it says it is retired, while it should be only orphaned [2].
Looks like some debugging slipped it way to the release and introduced a bug, thanks for catching this, it has been fixed.
Pierre
devel@lists.stg.fedoraproject.org
-
Miro Hrončok -
Petr Lautrbach -
Pierre-Yves Chibon -
Vít Ondruch