Summary: | perl-core/ExtUtils-Manifest-1.630.0-r1: file collisions... perl-core/ExtUtils-MakeMaker-7.40.0:0::gentoo | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Toralf Förster <toralf> |
Component: | [OLD] Development | Assignee: | Gentoo Perl team <perl> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | bkohler, rose, whissi |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 539996 | ||
Bug Blocks: |
Description
Toralf Förster
2015-02-27 17:43:30 UTC
Ah. I was wondering when bug #539996 would become an actual problem =) ExtUtils::Manifest is one of EUMMs "Bundled" libraries which normally gets installed in bootstrap environments ( CPAN ). Gentoo presently foolishly fix "The bundled libraries" like this: # remove all the bundled distributions pushd "${D}" find ".${VENDOR_LIB}" -mindepth 1 -maxdepth 1 -not -name "ExtUtils" -exec rm -rfv {} \+ Which would make perfect sense as long as ExtUtils::Manifest was not a bundled library :p 27 Feb 2015; Andreas K. Huettel <dilfridge@gentoo.org> +ExtUtils-MakeMaker-7.40.0-r1.ebuild: Fix bug 539996 and bug 541544 *** Bug 541630 has been marked as a duplicate of this bug. *** This fix isn't great, if I try to upgrade to ExtUtils-MakeMaker-7.40.0-r1 to get the fix, it pulls ExtUtils-Manifest-1.700.0 as a dep which collides with the currently installed ExtUtils-MakeMaker-7.40.0. # emerge -1av perl-core/ExtUtils-MakeMaker These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild N ] perl-core/ExtUtils-Manifest-1.700.0::gentoo 0 KiB [ebuild U ] virtual/perl-ExtUtils-Manifest-1.700.0::gentoo [1.630.0-r1::gentoo] 0 KiB [blocks b ] >perl-core/ExtUtils-Manifest-1.630.0-r999 (">perl-core/ExtUtils-Manifest-1.630.0-r999" is blocking virtual/perl-ExtUtils-Manifest-1.630.0-r1) [ebuild U ] perl-core/ExtUtils-MakeMaker-7.40.0-r1::gentoo [7.40.0::gentoo] 0 KiB [ebuild N ] perl-core/CPAN-Meta-2.143.240::gentoo USE="{-test}" 0 KiB [ebuild U ] virtual/perl-CPAN-Meta-2.143.240::gentoo [2.140.640::gentoo] 0 KiB [blocks b ] >perl-core/CPAN-Meta-2.140.640-r999 (">perl-core/CPAN-Meta-2.140.640-r999" is blocking virtual/perl-CPAN-Meta-2.140.640) Total: 5 packages (3 upgrades, 2 new), Size of downloads: 0 KiB Conflict: 2 blocks Would you like to merge these packages? [Yes/No] y >>> Verifying ebuild manifests >>> Emerging (1 of 5) perl-core/ExtUtils-Manifest-1.700.0::gentoo >>> Installing (1 of 5) perl-core/ExtUtils-Manifest-1.700.0::gentoo >>> Failed to install perl-core/ExtUtils-Manifest-1.700.0, Log file: >>> '/mnt/btr/var-tmp/portage/perl-core/ExtUtils-Manifest-1.700.0/temp/build.log' >>> Jobs: 0 of 5 complete, 1 failed Load avg: 0.14, 0.14, 0.10 * Package: perl-core/ExtUtils-Manifest-1.700.0 * Repository: gentoo * Maintainer: perl@gentoo.org * USE: abi_x86_64 amd64 elibc_glibc kernel_linux userland_GNU * FEATURES: preserve-libs sandbox userpriv usersandbox >>> Unpacking source... >>> Unpacking ExtUtils-Manifest-1.70.tar.gz to /mnt/btr/var-tmp/portage/perl-core/ExtUtils-Manifest-1.700.0/work >>> Source unpacked in /mnt/btr/var-tmp/portage/perl-core/ExtUtils-Manifest-1.700.0/work >>> Preparing source in /mnt/btr/var-tmp/portage/perl-core/ExtUtils-Manifest-1.700.0/work/ExtUtils-Manifest-1.70 ... >>> Source prepared. >>> Configuring source in /mnt/btr/var-tmp/portage/perl-core/ExtUtils-Manifest-1.700.0/work/ExtUtils-Manifest-1.70 ... * Using ExtUtils::MakeMaker * perl Makefile.PL PREFIX=/usr INSTALLDIRS=vendor INSTALLMAN3DIR=none DESTDIR=/mnt/btr/var-tmp/portage/perl-core/ExtUtils-Manifest-1.700.0/image/ Checking if your kit is complete... Looks good Generating a Unix-style Makefile Writing Makefile for ExtUtils::Manifest Writing MYMETA.yml and MYMETA.json >>> Source configured. >>> Compiling source in /mnt/btr/var-tmp/portage/perl-core/ExtUtils-Manifest-1.700.0/work/ExtUtils-Manifest-1.70 ... * emake OTHERLDFLAGS=-Wl,-O1 -Wl,--as-needed make -j5 'OTHERLDFLAGS=-Wl,-O1 -Wl,--as-needed' cp lib/ExtUtils/Manifest.pm blib/lib/ExtUtils/Manifest.pm cp lib/ExtUtils/MANIFEST.SKIP blib/lib/ExtUtils/MANIFEST.SKIP >>> Source compiled. >>> Test phase [not enabled]: perl-core/ExtUtils-Manifest-1.700.0 >>> Install ExtUtils-Manifest-1.700.0 into /mnt/btr/var-tmp/portage/perl-core/ExtUtils-Manifest-1.700.0/image/ category perl-core make -j5 pure_install Installing /mnt/btr/var-tmp/portage/perl-core/ExtUtils-Manifest-1.700.0/image/usr/lib64/perl5/vendor_perl/5.20.2/ExtUtils/Manifest.pm Installing /mnt/btr/var-tmp/portage/perl-core/ExtUtils-Manifest-1.700.0/image/usr/lib64/perl5/vendor_perl/5.20.2/ExtUtils/MANIFEST.SKIP >>> Completed installing ExtUtils-Manifest-1.700.0 into /mnt/btr/var-tmp/portage/perl-core/ExtUtils-Manifest-1.700.0/image/ ecompressdir: bzip2 -9 /usr/share/doc * checking 4 files for package collisions * This package will overwrite one or more files that may belong to other * packages (see list below). You can use a command such as `portageq * owners / <filename>` to identify the installed package that owns a * file. If portageq reports that only one package owns a file then do * NOT file a bug report. A bug report is only useful if it identifies at * least two or more packages that are known to install the same file(s). * If a collision occurs and you can not explain where the file came from * then you should simply ignore the collision since there is not enough * information to determine if a real problem exists. Please do NOT file * a bug report at http://bugs.gentoo.org unless you report exactly which * two packages install the same file(s). See * http://wiki.gentoo.org/wiki/Knowledge_Base:Blockers for tips on how to * solve the problem. And once again, please do NOT file a bug report * unless you have completely understood the above message. * * Detected file collision(s): * * /usr/lib64/perl5/vendor_perl/5.20.2/ExtUtils/Manifest.pm * /usr/lib64/perl5/vendor_perl/5.20.2/ExtUtils/MANIFEST.SKIP * * Searching all installed packages for file collisions... * * Press Ctrl-C to Stop * * perl-core/ExtUtils-MakeMaker-7.40.0:0::gentoo * /usr/lib64/perl5/vendor_perl/5.20.2/ExtUtils/MANIFEST.SKIP * /usr/lib64/perl5/vendor_perl/5.20.2/ExtUtils/Manifest.pm * * Package 'perl-core/ExtUtils-Manifest-1.700.0' NOT merged due to file * collisions. If necessary, refer to your elog messages for the whole * content of the above message. * GNU info directory index is up-to-date. I agree with Ben, this isn't fixed. Users have to manually unmerge "perl-core/ExtUtils-MakeMaker" to solve the blocking/file collision problem. OK I've additionally added a blocker on perl-core/ExtUtils-MakeMaker in 7.40.0 This should give Portage enough information to sort out the update sequence. |