* Detected file collision(s): * * /usr/bin/ebb * /usr/bin/dvipdfm * /usr/bin/dvipdft * * Searching all installed packages for file collisions... * * Press Ctrl-C to Stop * * app-text/texlive-core-2014-r4:0::gentoo * /usr/bin/dvipdfm * /usr/bin/dvipdft * /usr/bin/ebb * * Package 'app-text/dvipdfm-0.13.2d-r1' NOT merged due to file * collisions. If necessary, refer to your elog messages for the whole * content of the above message. ----------------------------------------------------------------- This is an stable amd64 chroot image (named amd64-kde-stable_20150802-105405) at a hardened host acting as a tinderbox. Portage 2.2.20 (python 3.4.1-final-0, default/linux/amd64/13.0/desktop/kde, gcc-4.8.4, glibc-2.20-r2, 4.0.8-hardened x86_64) ================================================================= System uname: Linux-4.0.8-hardened-x86_64-Intel-R-_Core-TM-_i7-3770_CPU_@_3.40GHz-with-gentoo-2.2 KiB Mem: 16164692 total, 2727592 free KiB Swap: 0 total, 0 free
$ portageq metadata / ebuild app-text/texlive-core-2014-r4 RDEPEND | grep dvipdfm ... !app-text/dvipdfm ... guess you have a problem
Created attachment 408268 [details] emerge log The tinderbox basically runs qsearch --all --name-only | sort --random-sort | xargs -n 1 emerge -1 I attached /mnt/qa/tinderbox/amd64-kde-stable_20150802-105405/var/log/emerge.log So does the tinderbox made some "forbidden" things ?
What I mean is, there are just few unmerges made till now which should not affect the texlive packages, or ? : tfoerste@t44 ~/tmp $ grep -e unmerge -e dvipdfm emerge.log 1438506169: >>> unmerge success: dev-libs/openssl-1.0.1p 1438506686: >>> unmerge success: net-misc/openssh-6.9_p1-r2 1438507886: >>> unmerge success: dev-libs/expat-2.1.0-r4 1438507971: >>> unmerge success: dev-libs/libffi-3.0.13-r1 1438508263: >>> unmerge success: sys-libs/zlib-1.2.8-r1 1438508823: >>> unmerge success: app-arch/unzip-6.0-r3 1438510299: >>> unmerge success: sys-libs/db-4.8.30-r2 1438511703: >>> unmerge success: dev-libs/libpcre-8.36 1438512585: >>> unmerge success: sys-apps/groff-1.22.2 1438512802: >>> unmerge success: dev-libs/glib-2.42.2 1438514300: >>> unmerge success: dev-libs/libxml2-2.9.2-r1 1438515077: >>> unmerge success: dev-lang/python-2.7.9-r1 1438515733: >>> unmerge success: sys-apps/util-linux-2.25.2-r2 1438515828: >>> unmerge success: sys-fs/udev-216 1438516318: >>> unmerge success: dev-lang/python-3.4.1 1438516553: >>> unmerge success: sys-libs/ncurses-5.9-r3 1438520292: >>> unmerge success: sys-process/psmisc-22.21-r2 1438530235: >>> unmerge success: sys-auth/pambase-20150213 1438624904: *** emerge --tree --oneshot --accept-restrict=-fetch --quiet-build=y --update --nospinner --accept-properties=-interactive app-text/dvipdfm 1438624908: >>> emerge (1 of 1) app-text/dvipdfm-0.13.2d-r1 to / 1438624908: === (1 of 1) Cleaning (app-text/dvipdfm-0.13.2d-r1::/usr/portage/app-text/dvipdfm/dvipdfm-0.13.2d-r1.ebuild) 1438624908: === (1 of 1) Compiling/Merging (app-text/dvipdfm-0.13.2d-r1::/usr/portage/app-text/dvipdfm/dvipdfm-0.13.2d-r1.ebuild) 1438624923: === (1 of 1) Merging (app-text/dvipdfm-0.13.2d-r1::/usr/portage/app-text/dvipdfm/dvipdfm-0.13.2d-r1.ebuild) 1438634713: >>> unmerge success: sys-power/upower-0.99.2-r1 1438648224: >>> unmerge success: media-sound/cdtool-2.1.8-r1 1438678547: >>> unmerge success: sys-power/upower-pm-utils-0.9.23-r2 1438678625: >>> unmerge success: sys-power/upower-0.99.2-r1 1438678674: >>> unmerge success: net-im/telepathy-mission-control-5.16.3 1438678727: >>> unmerge success: mate-base/mate-session-manager-1.8.1-r1 1438678750: *** emerge --quiet-build=y --accept-restrict=-fetch --tree --accept-properties=-interactive --nospinner --unmerge =gnome-extra/gnome-power-manager-3.14.1 1438678762: >>> unmerge success: gnome-extra/gnome-power-manager-3.14.1 1438678890: >>> unmerge success: app-crypt/gnupg-2.0.26-r3
For completeness: @world is clean : # MAKEOPTS=-j4 emerge -uDb @world These are the packages that would be merged, in reverse order: Calculating dependencies .. ... done! Nothing to merge; quitting. and portage doesn't hesitate to install it: # emerge -1up app-text/dvipdfm These are the packages that would be merged, in reverse order: Calculating dependencies . ... done! [ebuild N ] app-text/dvipdfm-0.13.2d-r1
(In reply to Alexis Ballier from comment #1) > $ portageq metadata / ebuild app-text/texlive-core-2014-r4 RDEPEND | grep > dvipdfm > ... !app-text/dvipdfm ... That's not enough, you need !app-text/texlive-core in RDEPEND of dvipdfm ebuilds. Otherwise, depending on package merge order, a collision can still happen.
(In reply to Alexandre Rostovtsev from comment #5) > (In reply to Alexis Ballier from comment #1) > > $ portageq metadata / ebuild app-text/texlive-core-2014-r4 RDEPEND | grep > > dvipdfm > > ... !app-text/dvipdfm ... > > That's not enough, you need !app-text/texlive-core in RDEPEND of dvipdfm > ebuilds. Otherwise, depending on package merge order, a collision can still > happen. How so ? blocker means tl-core can't be installed with dvipdfm. Merge order doesn't change anything in this relation and stating that dvipdfm can't be installed with tl-core doesn't add any information. However, it does add a possible source for bugs and less flexibility since we don't have ranged dependencies: imagine tl-core-0 doesn't provide dvipdfm, tl-core-1 to 5 bundle it because of some intricate relation with the other tl stuff, with tl-core-6 the bug is fixed and dvipdfm ebuild is recommended. Good luck maintaining proper blockers in dvipdfm ebuild :)
dvipdfm was last-rited and removed in commit 54577498873ba6ae4dd13a744569fc783a63cacb.
