* Detected file collision(s): * * /usr/share/man/man1/ros.1.bz2 * /usr/bin/ros * * Searching all installed packages for file collisions... * * Press Ctrl-C to Stop * * net-libs/librouteros-1.1.2:0::gentoo * /usr/bin/ros * /usr/share/man/man1/ros.1.bz2 * * Package 'dev-lisp/roswell-19.3.10.97' NOT merged due to file ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_desktop_plasma-test-20190802-201521 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-9.1.0 * Available Python interpreters, in order of preference: [1] python3.6 (fallback) [2] python2.7 (fallback) Available Rust versions: [1] rust-1.36.0 * java-config: The following VMs are available for generation-2: *) IcedTea JDK 3.12.0 [icedtea-bin-8] Available Java Virtual Machines: [1] icedtea-bin-8 system-vm emerge -qpvO dev-lisp/roswell --- Invalid atom in /etc/portage/package.accept_keywords/00unstable: sys-libs/glibc-2.30
Created attachment 586160 [details] emerge-info.txt
Created attachment 586162 [details] dev-lisp:roswell-19.3.10.97:20190808-014731.log
Created attachment 586164 [details] emerge-history.txt
Created attachment 586166 [details] etc.portage.tbz2
Created attachment 586168 [details] logs.tbz2
This is because those files are installed by both packages. To be honest I am not sure what is the best way to solve this problem... Do you have any idea?
A man page collision wouldve been doable with a soft blocker. Since the binary file collides, I think hard blocker is needed in roswell. Well, it doesnt seem like librouteros is exactly a popular package.
I understood. Changing the binary to another name (roswell maybe) during installation is also an option.
(In reply to Danny from comment #8) > Changing the binary to another name (roswell maybe) during installation is > also an option. Let's avoid that, it messes with the integrity of docs and man pages etc. I don't think this will hit many people so I'd say a hard blocker is best option here.
(In reply to Joonas Niilola from comment #9) > (In reply to Danny from comment #8) > > Changing the binary to another name (roswell maybe) during installation is > > also an option. > > Let's avoid that, it messes with the integrity of docs and man pages etc. I > don't think this will hit many people so I'd say a hard blocker is best > option here. You are right. I have already submitted a PR that adds a blocker to Roswell.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f67e0f91e4a5ab3114a19fd1a26cd5683f23361b commit f67e0f91e4a5ab3114a19fd1a26cd5683f23361b Author: YUE Daian <sheepduke@gmail.com> AuthorDate: 2019-08-10 03:21:52 +0000 Commit: Joonas Niilola <juippis@gentoo.org> CommitDate: 2019-08-10 12:14:55 +0000 dev-lisp/roswell: fix fill collision with libroutersos Bug: https://bugs.gentoo.org/691754 Signed-off-by: YUE Daian <sheepduke@gmail.com> Closes: https://github.com/gentoo/gentoo/pull/12664 Signed-off-by: Joonas Niilola <juippis@gentoo.org> dev-lisp/roswell/roswell-19.3.10.97.ebuild | 2 ++ 1 file changed, 2 insertions(+)
Fixed. Only one of the two packages can be installed at the same time.
