Created attachment 394800 [details] build.log Source files for salome-kernel could not be downloaded. When trying manually via mozilla to access the specified adress, I got 404 error same as the portage error.
Created attachment 394802 [details] emerge --info
If the src location just moved, we could adjust them. Anyway, a look to the download page [1] tells me "You have to login(register) for download link". This shouldn't be the case, as the GPL-2 licensed packages shouldn't be fetch restricted. [1] http://www.salome-platform.org/downloads/previous-versions/salome-v5.1.4
(In reply to Marius Brehler from comment #2) > If the src location just moved, we could adjust them. Anyway, a look to the > download page [1] tells me "You have to login(register) for download link". > This shouldn't be the case, as the GPL-2 licensed packages shouldn't be > fetch restricted. > > [1] http://www.salome-platform.org/downloads/previous-versions/salome-v5.1.4 Yes I aware of the restriction. Should we move the ebuilds/sources to gentoo.distfiles?
We could download the sources via git. Like the Arch way. " git clone git://git.salome-platform.org/modules/${_source}.git " https://aur.archlinux.org/packages/sa/salome-kernel/PKGBUILD I will try to make an ebuild out of this.
Created attachment 403554 [details] ebuild It is a modification of the old 5.1.4 ebuild and the Arch's PKGBUILD.
It configures and compiles good but it fails to install due to some conflicts: * Package 'sci-misc/salome-kernel-7.4.1' has one or more collisions * between symlinks and directories, which is explicitly forbidden by PMS * section 13.4 (see bug #326685): * * /opt/salome-7.4.1/KERNEL/lib * * 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): * * /opt/salome-7.4.1/KERNEL/lib * * Searching all installed packages for file collisions... * * Press Ctrl-C to Stop * * None of the installed packages claim the file(s). * * Package 'sci-misc/salome-kernel-7.4.1' NOT merged since it has one or * more collisions between symlinks and directories, which is explicitly * forbidden by PMS section 13.4 (see bug #326685). If necessary, refer * to your elog messages for the whole content of the above message.
Created attachment 403558 [details] build.log.NEW
You could do a pull request on https://github.com/gentoo-science/sci and we assist with fixing the issues.
WONTFIX because package has been removed
