dev-util/seer-9999 install fails [RESOLVED]

[Progman3K]

Hi,

The install phase fails with the following:

Code: Select all

>>> Install dev-util/seer-9999 into /var/tmp/portage/dev-util/seer-9999/image
 * Source directory (CMAKE_USE_DIR): "/var/tmp/portage/dev-util/seer-9999/work/seer-9999/src"
 * Build directory  (BUILD_DIR):     "/var/tmp/portage/dev-util/seer-9999/work/seer-9999/src_build"
ninja -v -l0 -j24 install
[0/1] cd /var/tmp/portage/dev-util/seer-9999/work/seer-9999/src_build && /usr/bin/cmake -P cmake_install.cmake
-- Install configuration: "RelWithDebInfo"
-- Installing: /var/tmp/portage/dev-util/seer-9999/image/usr/bin/seergdb
 * ERROR: dev-util/seer-9999::gentoo failed (install phase):
 *   !!! newins: resources/seergdb_32x32.png does not exist

Log at
https://paste2.net/sqn28978


The ~2.6 version does install properly.

Thank you

[rab0171610]

The 9999 version should really be for testing. This is a live ebuild that installs code from upstream that may be a work in progress. Commits sometimes break things and are rolled back later. You should expect this kind of breakage if you are going to install the 9999 versions.

The ebuild in question contains this installation directive:

Code: Select all

src_install() {
	cmake_src_install

	domenu resources/seergdb.desktop

	local size
	for size in 32 64 128 256 512 ; do
		newicon -s ${size} resources/seergdb_${size}x${size}.png seergdb.png
	done
}

The problem is the main github source code for seer no longer contains those icons that are prefixed with the seergdb_ prefix in the src/resources directory.
You can maintain your own ebuild and alter this or you can keep the version that works, 2.6. The code from the main branch has never been packaged by the devs and released into a known working release.
Or, you can detail here why you need the 9999 version. The last release, v2.6, was October 7, 2025. That was not so long ago. Are there features that have been added or commits that were made that you are wanting to test?
I do not know exactly what the procedure for testing 9999 versions of ebuilds, but I assume you can also file a bug report so the ebuild maintainers are aware that changes have been made upstream in the source code that currently break the 9999 version of the ebuild.
The problem is that the omission of the icons may have been intentional or it may be fixed tomorrow. Without digging into the most recent commits on Github, I would not know. The "main" branches are staging areas usually where developers collaborate and make frequent commits that sometimes are reverted or modified before the next release. What is broken today might work tomorrow and vice versa.
So unless you have compelling reasons to install the 9999 version, you should save yourself the headaches and stick with the version that works.
(To clarify, the version of code that is installed by the 9999 ebuild is from the main branch which is currently in the v2.7 development cycle.)
https://wiki.gentoo.org/wiki/Live_ebuilds

[Progman3K]

Thank you for the clarification, rab0171610.

That makes lots of sense.

I wanted the latest version for no particular reason than to be on the bleeding edge.

Yes, the 2.6 version is completely adequate, so I'll stick with that.

Marking this resolved for the reasons you outlined, mainly that it could change state at any moment.

Thanks again, rab0171610!