Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1893506 - Two NodeJS package conflicts blocking system-upgrade from F32->F33
Summary: Two NodeJS package conflicts blocking system-upgrade from F32->F33
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: nodejs-grunt
Version: 32
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Orphan Owner
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 1864885
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-11-01 06:15 UTC by Benji Wiebe
Modified: 2021-05-25 16:57 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: ---
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-05-25 16:57:52 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Benji Wiebe 2020-11-01 06:15:36 UTC 
Description of problem:
I can't do a system-upgrade from F32 -> F33 due to broken dependencies.

Version-Release number of selected component (if applicable):
Fedora 32

How reproducible:
Always

Steps to Reproduce:
1. Attempt to upgrade with 'dnf system-upgrade --releasever=33 download'


Actual results:
'dnf system-upgrade' fails with the following error messages:
------------------------------------------------
Error:
 Problem 1: package nodejs-grunt-1.0.4-4.fc33.noarch requires (npm(rimraf) >= 2.0 with npm(rimraf) < 3), but none of the providers can be installed
  - package nodejs-grunt-cli-1.2.0-9.fc32.noarch requires npm(grunt), but none of the providers can be installed
  - nodejs-rimraf-2.6.1-7.fc32.noarch does not belong to a distupgrade repository
  - nodejs-grunt-1.0.4-3.fc32.noarch does not belong to a distupgrade repository
  - problem with installed package nodejs-grunt-cli-1.2.0-9.fc32.noarch
 Problem 2: package nodejs-request-2.67.0-15.fc32.noarch requires (npm(http-signature) >= 0.10.0 with npm(http-signature) < 0.11), but none of the providers can be installed
  - package nodejs-http-signature-0.10.0-16.fc32.noarch requires (npm(asn1) >= 0.1.11 with npm(asn1) < 0.2), but none of the providers can be installed
  - nodejs-asn1-0.1.11-15.fc32.noarch does not belong to a distupgrade repository
  - problem with installed package nodejs-request-2.67.0-15.fc32.noarch
(try to add '--skip-broken' to skip uninstallable packages)
------------------------------------------------

Expected results:
'dnf system-upgrade' should successfully resolve dependencies and download packages.


Additional info:
Comment 1 Robin Rainton 2021-01-30 07:41:39 UTC 
This isn't just an upgrade problem. Trying to install rimraf in FC33 is broken:

# dnf install nodejs-rimraf.noarch
Last metadata expiration check: 0:09:20 ago on Sat 30 Jan 2021 08:30:46 CET.
Error: 
 Problem: package nodejs-rimraf-3.0.2-1.fc33.noarch requires npm(glob), but none of the providers can be installed
  - conflicting requests
  - nothing provides (npm(inherits) >= 2 with npm(inherits) < 3) needed by nodejs-glob-6.0.4-9.fc32.noarch
(try to add '--skip-broken' to skip uninstallable packages)
Comment 2 Robin Rainton 2021-01-30 07:44:32 UTC 
See: https://bugzilla.redhat.com/show_bug.cgi?id=1864885
Comment 3 Fedora Program Management 2021-04-29 16:43:00 UTC 
This message is a reminder that Fedora 32 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '32'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 32 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 4 Ben Cotton 2021-05-25 16:57:52 UTC 
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.
Note You need to log in before you can comment on or make changes to this bug.