Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Handle multiply mapped anitya projects. #39

Merged
merged 3 commits into from Mar 28, 2015
Merged

Conversation

ralphbean
Copy link
Contributor

It is possible for an anitya project to be mapped to two or more Fedora
packages. In these cases we will now check the monitoring flag of each
one of those packages (not just whichever one appears first in the
list) and then file bugs for each of those packages that do want
bugs to be filed.

Fixes #33.

It is possible for an anitya project to be mapped to two or more Fedora
packages.  In these cases we will now check the monitoring flag of *each*
one of those packages (not just whichever one appears first in the
list) and then file bugs for each of those packages that **do** want
bugs to be filed.

Fixes #33.
@tyll requested this in #34:  sometimes, a project exists on
release-monitoring.org *and* the package exists in Fedora.. but there is
no mapping between the two.  When a user establishes that mapping
between them, the-new-hotness should respond by filing a bug if
necessary.

If the project in question has **no** version information at the time
this message arrives, the we force a new check in anitya and bail..
waiting on the next message from that to arrive.

Fixes #34.
@ralphbean
Copy link
Contributor Author

4cef2de also fixes #34.

@pypingou
Copy link
Member

👍 for me

@ralphbean
Copy link
Contributor Author

Thanks so much, @pypingou!

ralphbean added a commit that referenced this pull request Mar 28, 2015
Handle multiply mapped anitya projects.
@ralphbean ralphbean merged commit dc53423 into develop Mar 28, 2015
@ralphbean ralphbean deleted the feature/multiply-mapped branch March 28, 2015 11:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants