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

Commits on Mar 28, 2015

  1. Handle multiply mapped anitya projects.

    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.
    ralphbean committed Mar 28, 2015
    Configuration menu
    Copy the full SHA
    a9eba18 View commit details
    Browse the repository at this point in the history
  2. Demote this error message.

    ralphbean committed Mar 28, 2015
    Configuration menu
    Copy the full SHA
    3630273 View commit details
    Browse the repository at this point in the history
  3. Handle newly-mapped packages from anitya.

    @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 committed Mar 28, 2015
    Configuration menu
    Copy the full SHA
    4cef2de View commit details
    Browse the repository at this point in the history