I believe I found a workaround for the original issue I emailed about. If
we add a prefix the the names of the packages then we can get around the
Anitya name/homepage uniqueness. I did a test with the ninesixty project
by prefixing each Anitya project name with either "Drupal 6: " or "Drupal
7: ". If we do that then everything can be monitored and we will not have
to go to the Anitya project details to figure out if it is for Drupal 6 or
Drupal 7. I will try to make these name (and homepages fixes) tomorrow.
The base drupal6 issue remains though.
Sorry for all of the emails!
On Sun, Feb 22, 2015 at 12:46 AM, Shawn Iwinski <shawn.iwinski(a)gmail.com>
wrote:
Another issue for the base drupal6 package:
https://github.com/fedora-infra/anitya/issues/88
Unless anyone disagrees, I will try to find time tomorrow to fix the
drupal7-* pkgs in Anitya instead of the same project drupal6-* ones as I
feel it it more important to monitor the drupal7-* releases.
On Sat, Feb 21, 2015 at 11:59 PM, Shawn Iwinski <shawn.iwinski(a)gmail.com>
wrote:
> Only one of drupal7-* and drupal6-* pkgs that are the same Drupal project
> will be monitored by the new upstream release monitoring (Anitya). See
>
https://github.com/fedora-infra/anitya/issues/80 for the issue. See my
> comment in that issue for how same-Drupal-project pkgs are set up right now
> in Anitya.
>