EPEL破包：我如何到达EPEL维修人员？

我和npm EPEL包有同样的更新问题，最后看到错误信息。

我的解决scheme是删除'npm'包并再次安装。 这在我的服务器上没有问题，因为npm只是nodejs的包pipe理器。 安装的npm包，把手和更less，留在服务器上:-)

 [root@somewhere yum.repos.d] # yum update Loaded plugins: fastestmirror, priorities Loading mirror speeds from cached hostfile epel/metalink | 23 kB 00:00 * epel: ftp.uni-koeln.de base | 3.7 kB 00:00 extras | 3.4 kB 00:00 updates | 3.4 kB 00:00 Setting up Update Process Resolving Dependencies --> Running transaction check ---> Package npm.noarch 0:1.2.17-5.el6 will be updated ---> Package npm.noarch 0:1.3.3-1.el6 will be an update --> Finished Dependency Resolution Dependencies Resolved ================================================================================================================================================================================== Package Arch Version Repository Size ================================================================================================================================================================================== Updating: npm noarch 1.3.3-1.el6 epel 351 k Transaction Summary ================================================================================================================================================================================== Upgrade 1 Package(s) Total download size: 351 k Is this ok [y/N]: y Downloading Packages: npm-1.3.3-1.el6.noarch.rpm | 351 kB 00:00 Running rpm_check_debug Running Transaction Test Transaction Test Succeeded Running Transaction Updating : npm-1.3.3-1.el6.noarch 1/2 Error unpacking rpm package npm-1.3.3-1.el6.noarch error: unpacking of archive failed on file /usr/lib/node_modules/npm/man: cpio: rename Verifying : npm-1.3.3-1.el6.noarch 1/2 npm-1.2.17-5.el6.noarch was supposed to be removed but is not! Verifying : npm-1.2.17-5.el6.noarch 2/2 Failed: npm.noarch 0:1.2.17-5.el6 npm.noarch 0:1.3.3-1.el6 Complete! [root@somewhere yum.repos.d]# yum remove npm Loaded plugins: fastestmirror, priorities Setting up Remove Process Resolving Dependencies --> Running transaction check ---> Package npm.noarch 0:1.2.17-5.el6 will be erased --> Finished Dependency Resolution base | 3.7 kB 00:00 epel/metalink | 23 kB 00:00 extras | 3.4 kB 00:00 updates | 3.4 kB 00:00 Dependencies Resolved ================================================================================================================================================================================== Package Arch Version Repository Size ================================================================================================================================================================================== Removing: npm noarch 1.2.17-5.el6 @epel 951 k Transaction Summary ================================================================================================================================================================================== Remove 1 Package(s) Installed size: 951 k Is this ok [y/N]: y Downloading Packages: Running rpm_check_debug Running Transaction Test Transaction Test Succeeded Running Transaction Erasing : npm-1.2.17-5.el6.noarch 1/1 Verifying : npm-1.2.17-5.el6.noarch 1/1 Removed: npm.noarch 0:1.2.17-5.el6 Complete! [root@somewhere yum.repos.d]# yum install npm Loaded plugins: fastestmirror, priorities Loading mirror speeds from cached hostfile epel/metalink | 23 kB 00:00 * epel: ftp.uni-koeln.de base | 3.7 kB 00:00 extras | 3.4 kB 00:00 updates | 3.4 kB 00:00 Setting up Install Process Resolving Dependencies --> Running transaction check ---> Package npm.noarch 0:1.3.3-1.el6 will be installed --> Finished Dependency Resolution Dependencies Resolved ================================================================================================================================================================================== Package Arch Version Repository Size ================================================================================================================================================================================== Installing: npm noarch 1.3.3-1.el6 epel 351 k Transaction Summary ================================================================================================================================================================================== Install 1 Package(s) Total download size: 351 k Installed size: 1.3 M Is this ok [y/N]: y Downloading Packages: npm-1.3.3-1.el6.noarch.rpm | 351 kB 00:00 Running rpm_check_debug Running Transaction Test Transaction Test Succeeded Running Transaction Installing : npm-1.3.3-1.el6.noarch 1/1 Verifying : npm-1.3.3-1.el6.noarch 1/1 Installed: npm.noarch 0:1.3.3-1.el6 Complete! [root@somewhere yum.repos.d] # /usr/bin/lessc lessc: no input files usage: lessc [option option=parameter ...] <source> [destination] If source is set to `-' (dash or hyphen-minus), input is read from stdin. options: -h, --help Print help (this message) and exit. --include-path Set include paths. Separated by `:'. Use `;' on Windows. --no-color Disable colorized output. -s, --silent Suppress output of error messages. --strict-imports Force evaluation of imports. --verbose Be verbose. -v, --version Print version number and exit. -x, --compress Compress output by removing some whitespaces. --yui-compress Compress output using ycssmin -O0, -O1, -O2 Set the parser's optimization level. The lower the number, the less nodes it will create in the tree. This could matter for debugging, or if you want to access the individual nodes in the tree. --line-numbers=TYPE Outputs filename and line numbers. TYPE can be either 'comments', which will output the debug info within comments, 'mediaquery' that will output the information within a fake media query which is compatible with the SASS format, and 'all' which will do both. -rp, --rootpath Set rootpath for url rewriting in relative imports and urls. Works with or withour the relative-urls option. -ru, --relative-urls re-write relative urls to the base less file. 

实际上，对我来说，RepoForge的libmodplug软件包可能会干扰某些方面。 我不能肯定地说，没有手动跟踪依赖链接，但我会尝试删除当前安装的libmodplug包或repoforge（rf）存储库定义并重新发出更新命令。 根据该testing的结果采取进一步的行动（或不行）。

约翰有你的答案，我想; 您可能与另一个第三方存储库的软件包发生冲突。

关于您关于EPEL的问题： EPEL FAQ告诉您在哪里可以findEPEL软件包的支持或文件错误报告：

我在哪里可以find帮助或报告问题？

您可以在epel-devel-list或#epel Freenode IRC频道中find帮助或讨论问题。 通过bugzilla向EPEL报告问题。