Skip to content

Allow to map 2 projects to the same package #2009

@JoseExposito

Description

@JoseExposito

I'm trying to fully automate mesa releases (https://src.fedoraproject.org/rpms/mesa) with Packit.

Packit is triggered when a new release is found by release-monitoring.org, however, release-monitoring.org only picks the latest update.

My use case is:

  • I'd like to target mesa 26.x in Rawhide
  • I'd like to target mesa 25.x in Fedora 43 and 44

Since release-monitoring.org only picks the latest version (26.x) only Rawhide is updated by Packit.

I tried to create a new release-monitoring project for mesa 25.x:
https://release-monitoring.org/project/388363/

This would allow Packit to update all versions. However, it is not possible to map it to Fedora's mesa: "Could not edit the mapping of mesa on Fedora, there is already a package mesa on Fedora as part of the project mesa."

Would it be possible to remove this restriction so Packit can pick all updates?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions