Skip to content
This repository has been archived by the owner on Jan 14, 2021. It is now read-only.

Orphaned package bugs assigned to former POC #411

Open
voxik opened this issue Feb 6, 2017 · 1 comment
Open

Orphaned package bugs assigned to former POC #411

voxik opened this issue Feb 6, 2017 · 1 comment

Comments

@voxik
Copy link
Contributor

voxik commented Feb 6, 2017

Not sure if this is the right place, but anyway ... I used to be maintainer of rubygem-linode [1], but I recently orphaned that package. However, the newly created bug by the-new-hotness [2] was assigned to me. Is this bug in PkgDb, new-hotness, bugzilla?

Actually I tried the "Reset Assignee to default for component" but it does not appear to change anything, so I suppose the PkgDb does not inform Bugzilla about the change of ownership correctly, since the new owner should be "orphan owner" user?

@pypingou
Copy link
Member

pypingou commented Feb 6, 2017

Hm I guess something went wrong in the sync with bz :s

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants