Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#67806 - [npm] The package npm-6.14.8-1-any.pkg.tar.zst has the previous version

Attached to Project: Community Packages
Opened by Axel Navarro (navarroaxel) - Wednesday, 02 September 2020, 14:31 GMT
Last edited by Felix Yan (felixonmars) - Tuesday, 27 October 2020, 22:27 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Felix Yan (felixonmars)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 9
Private No

Details

Description:
The npm package is still outdated.
The npm package content is for 6.14.7 but the package version is 6.14.8.


Additional info:
* npm 6.14.8-1


Steps to reproduce:
* pacman -Syu npm
* npm -v
The output is 6.14.7
* pacman -Qi npm
The output is Version: 6.14.8-1
* cat /usr/lib/node_modules/npm/package.json
The output has "version": "6.14.7"
* xdg-open /var/cache/pacman/pkg/npm-6.14.8-1-any.pkg.tar.zst
The file /usr/lib/node_modules/npm/package.json inside the .tar.zst has the value "version": "6.14.7"
This task depends upon

Closed by  Felix Yan (felixonmars)
Tuesday, 27 October 2020, 22:27 GMT
Reason for closing:  Fixed
Additional comments about closing:  6.14.8-2
Comment by Doug Newgard (Scimmia) - Wednesday, 02 September 2020, 14:48 GMT
Checksum has changed as well. I'd guess upstream screwed up, then retagged the release.
Comment by Mark Blakeney (bulletmark) - Wednesday, 09 September 2020, 22:55 GMT
I just used current PKGBUILD and it builds 6.14.8 correctly so can the pkgrel be bumped please?
Comment by Hexhu (hexhu) - Tuesday, 27 October 2020, 02:02 GMT
+1, a rebuild is clearly needed

Loading...