/ Register

Join the community today
Become a Member

Yum update Warnings

Discussion in 'Install & Upgrades or Pre-Install Questions' started by quicksalad, Dec 22, 2023.

Previous Thread Next Thread
Loading...
  1. Dec 22, 2023 #1
    quicksalad

    quicksalad Member

    228
    13
    18
    May 31, 2015
    Ratings:
    +20
    Local Time:
    6:39 AM
    Please fill in any relevant information that applies to you:
    • CentOS Version: CentOS 7 64bit
    • Centmin Mod Version Installed: 124.00stable
    • Nginx Version Installed: 1.24
    • PHP Version Installed: 7.4.33
    • MariaDB MySQL Version Installed: i.e. 10.3.xx
    • When was last time updated Centmin Mod code base ? : No updates available
    Code:
    warning: file /usr/lib/node_modules/npm/tap-snapshots/smoke-tests/index.js.test.cjs: remove failed: No such file or directory
warning: file /usr/lib/node_modules/npm/tap-snapshots/smoke-tests: remove failed: No such file or directory
warning: file /usr/lib/node_modules/npm/tap-snapshots: remove failed: No such file or directory
warning: file /usr/lib/node_modules/npm/node_modules/wcwidth/Readme.md: remove failed: No such file or directory
warning: file /usr/lib/node_modules/npm/node_modules/validate-npm-package-name/index.js: remove failed: No such file or directory
warning: file /usr/lib/node_modules/npm/node_modules/unique-slug/index.js: remove failed: No such file or directory
warning: file /usr/lib/node_modules/npm/node_modules/unique-filename/index.js: remove failed: No such file or directory
warning: file /usr/lib/node_modules/npm/node_modules/unique-filename/coverage/sorter.js: remove failed: No such file or directory
warning: file /usr/lib/node_modules/npm/node_modules/unique-filename/coverage/sort-arrow-sprite.png: remove failed: No such file or directory
....
    The update is complete but I'm seeing above warnings.
     
  2. Dec 22, 2023 #2
    duderuud

    duderuud Premium Member Premium Member

    273
    88
    28
    Dec 5, 2020
    The Netherlands
    Ratings:
    +189
    Local Time:
    3:09 AM
    1.27 x
    10.6
    Not really a big problem I guess :)
     
  3. Dec 23, 2023 #3
    quicksalad

    quicksalad Member

    228
    13
    18
    May 31, 2015
    Ratings:
    +20
    Local Time:
    6:39 AM
    Thanks
    Any idea from what addon is it?
     
  4. Dec 23, 2023 #4
    eva2000

    eva2000 Administrator Staff Member

    55,916
    12,281
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +18,868
    Local Time:
    11:09 AM
    Nginx 1.27.x
    MariaDB 10.x/11.4+
    Looks like you installed some nodes npm packages that conflict with YUM versions

    looks like it's node npm package related. If you installed nodejs via addons/nodejs.sh installer, you don't need YUM npm package in 3rd party EPEL YUM repo

    Code (Text):
    yum -q provides /usr/lib/node_modules/npm/node_modules/unique-slug
1:npm-8.19.4-1.16.20.2.1.el7.x86_64 : Node.js Package Manager
Repo        : epel
Matched from:
Filename    : /usr/lib/node_modules/npm/node_modules/unique-slug
     
  5. Dec 23, 2023 #5
    quicksalad

    quicksalad Member

    228
    13
    18
    May 31, 2015
    Ratings:
    +20
    Local Time:
    6:39 AM
    Thanks @eva2000 I remember installing DO agent and auditd, could that be the trigger? Those are the thing I can recall and the rest is default. Aside from plugins.
     
  6. Dec 23, 2023 #6
    eva2000

    eva2000 Administrator Staff Member

    55,916
    12,281
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +18,868
    Local Time:
    11:09 AM
    Nginx 1.27.x
    MariaDB 10.x/11.4+
    what does checking yum history list report for command
    Code (Text):
    yum -q history list npm
     
  7. Dec 24, 2023 #7
    quicksalad

    quicksalad Member

    228
    13
    18
    May 31, 2015
    Ratings:
    +20
    Local Time:
    6:39 AM
    @eva2000 I'm getting
    Code:
    Bad transaction IDs, or package(s), given
Error: Failed history packages-list
     
  8. Dec 24, 2023 #8
    eva2000

    eva2000 Administrator Staff Member

    55,916
    12,281
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +18,868
    Local Time:
    11:09 AM
    Nginx 1.27.x
    MariaDB 10.x/11.4+
    That just means npm yum package wasn't installed so has no history to list
     
  9. Dec 25, 2023 #9
    quicksalad

    quicksalad Member

    228
    13
    18
    May 31, 2015
    Ratings:
    +20
    Local Time:
    6:39 AM
    non
    @eva2000 Thanks
    maybe because nodejs.x86_64 was listed in all the available updates, prior to yum update
     
Previous Thread Next Thread
Loading...

.