gobolinux / Recipes

The GoboLinux recipes repository
107 stars 30 forks source link

CoreUtils 9.5 #227

Closed sage-etcher closed 4 months ago

sage-etcher commented 4 months ago

While running the test-suites, between the non-root and root tests, 4 failed. comparing the failed tests of the new version, 9.5, and the old version, 8.31:

would also like to note, when testing, version 8.31 also had 4 failed tests in total.

After installing, I'd used ldd and readlink (this very rough script) to find runtime dependencies, and added them to the Dependencies file.

Nuc1eoN commented 4 months ago

It builds fine for me :+1: Good work on researching and providing the new i18n-1.patch aswell. Merging.

BTW failing test is not so important for us at this point. Mostly we just disable tests in the recipe (as well as often problematic stuff like docbook/documentation). But still, thank you for pointing it out!

Nuc1eoN commented 4 months ago

I just tried to Compile Coreutils 9.5 on a fresh GoboLinux system and it failed. CoreUtils was missing a header file /sys/capability.h

The problem turned out to be unexpected: Even though /sys/capability.h is part of LibCap which is installed on GoboLinux 017 by default, the file is not to be found not under /System/Index/include/sys/*.

So I did a quick SymlinkProgram LibCap and lo and behold - that fixed it. For some reason it was not properly Symlinked. I had this problem before with some program, however I cannot remember whether it was LibCap. So I am leaving it here for future reference :)

sage-etcher commented 4 months ago

This's quite peculiar?

I tried to replicate the issue, setup a fresh install w/ known issues and fixes applied, tried to compile the package, and it all worked fine. After the compile I checked capabilitiy.h, and it was installed properly by Installer. I couldn't say why the issue occurred.

Is your ISO fine? if non-vm, is the boot media reliable?

Nuc1eoN commented 4 months ago

Hm weird, I cannot tell at this point. Let's just see whether we stumble on it again in the future. Maybe it was some user error on my part :)