#9324 Bugzilla assignee sync script assigns some bugs to orphan by accident
Closed: Fixed a month ago by mohanboddu. Opened 3 months ago by churchyard.

See for example https://bugzilla.redhat.com/show_bug.cgi?id=1699483#c2 -- this seems to be a mistake because https://src.fedoraproject.org/modules/maven still says it is owned by @mizdebsk.


@zlopez you've been working on this code-base recently, do you remember seeing this?

This is not limited to modules:

https://bugzilla.redhat.com/show_bug.cgi?id=1742427#c2

https://src.fedoraproject.org/rpms/python2-django1.11

That project is retired in rawhide and the bug is a rawhide bug, so that one looks fine actually

That project is retired in rawhide and the bug is a rawhide bug

So if anything, I suggest it should be closed, not assigned to orphan. The package is not orphaned. This is confusing :/

This is not limited to modules:

https://bugzilla.redhat.com/show_bug.cgi?id=1742427#c2

https://src.fedoraproject.org/rpms/python2-django1.11

That project is retired in rawhide and the bug is a rawhide bug, so that one looks fine actually

This is how it should work, the retired packages are still updated, but not created.

Metadata Update from @zlopez:
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: dev, medium-gain, medium-trouble

3 months ago

When testing the new distgit_bugzilla_sync toddler. I tried to check the modules/maven project and the script is consider it retired, because there is no active branch in PDC.

Here is the project info updated by the active branch query from PDC:

{'namespace': 'modules', 'name': 'maven', 'poc': 'mizdebsk', 'epelpoc': 'mizdebsk', 'watchers': ['mizdebsk'], 'summary': None, 'branches': [['master', False], ['f27', False], ['f28', False], ['3.5', False], ['f29', False], ['3.6', False]], 'products': ['Fedora Modules'], 'products_poc': {'Fedora Modules': 'orphan'}, 'products_retired': {'Fedora Modules': True}}

It sounds like the script is doing what it should do.

@mohanboddu @humaton is it expected that the master branch of a module can be inactive?

Is there anything to left do here?

It seems to me that the script is doing what it should.

It sounds like the script is doing what it should do.

@mohanboddu @humaton is it expected that the master branch of a module can be inactive?

Yes, modules are allowed to use any branch they want, they can retire master and work on the stream branches.

We discussed this further and basically the outcome of the discussion was that the script behaves as expected but PDC needs to be adjusted so not all branches are EOL'd.

Metadata Update from @pingou:
- Issue untagged with: dev
- Issue tagged with: releng

2 months ago

@humaton @mohanboddu could you update the PDC entries for these components?

The script is working as expected and as long as the maintainer of the maven module didn't request us to extend the EOL in PDC, we are not going to update it since we dont know if he is still willing to maintain it or not.

Closing this ticket.

Metadata Update from @mohanboddu:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

a month ago

Login to comment on this ticket.

Metadata