Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-104877

Make nodejsXY-devel packages explicitly conflict with each other

Linking RHIVOS CVEs to...Migration: Automation ...Sync from "Extern...XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • rhel-10.1
    • nodejs22
    • None
    • nodejs-devel-explicit-conflict
    • Hide

      Any and all nodejs{XY}-devel packages have an explicit conflict with any other.

      Affected packages in Fedora Rawhide: nodejs20-devel nodejs-devel nodejs24-devel
      Affected packages in c10s / RHEL 10.1: nodejs-devel nodejs24-devel

      Show
      Any and all nodejs{XY}-devel packages have an explicit conflict with any other. Affected packages in Fedora Rawhide: nodejs20-devel nodejs-devel nodejs24-devel Affected packages in c10s / RHEL 10.1: nodejs-devel nodejs24-devel
    • 0% To Do, 0% In Progress, 100% Done
    • rhel-pt-ruby-nodejs
    • False
    • Hide

      None

      Show
      None
    • Unspecified
    • Unspecified
    • Unspecified

      The nodejs(XY)-devel packages are not designed to be installed in parallel; however, they are lacking the Conflicts: declaration to make this explicit.


      The experimental -bin packages suffer from similar problem, and we should probably come up with a way to specify this sort of thing in a sane way than to just list all the other streams (and then forgetting to update the lists once a new stream is introduced).

      This epic is created so that the changes are propagated to all the -devel packages as well.

              nodejs-maint nodejs-maint
              jstanek@redhat.com Jan Stanek
              nodejs-maint nodejs-maint
              rhel-nodejs-qe bot rhel-nodejs-qe bot
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: