[Solved] Ebuild downloading old tar.gz

Nima0908 · n00b Joined: 24 Feb 2025 Posts: 44

Hello,
i recently updated SuperSlicer with some fixes to work on gentoo, and the source compiles fine, but when i use my custom ebuild to download and build it from my repo, it fails in a place where it would without the fixes i applied. I already copied the link out of the ebuild and downloaded the tarball manually, but there its fine and has the updated cmake. Does somebody know how to fix it. Here is the cmake (its not finished yet, some deps may be missing):

Hu · Administrator Joined: 06 Mar 2007 Posts: 23811

If you unpack the tar file downloaded by the ebuild, are your fixes present? Since you named the tar file from $P, if your ebuild has the same name as the ::gentoo package, then your ebuild may be reusing the tar file downloaded by the ::gentoo ebuild, which would be from the original (bad) upstream.

Genone · Posted: Wed Sep 17, 2025 9:10 am Post subject:

a) Verify that portage is really using your ebuild (e.g. add an elog statement in src_unpack)
b) I would recommend to use a different filename for the tarball than the original ebuild as that will very likely lead to problems and confusion otherwise.

logrusx · Advocate Joined: 22 Feb 2018 Posts: 3239

If portage finds a file with the same name in the dstfiles cache, it uses it. You need to delete it and regenerate the manifest.

Also you can apply your fixes in the tempdir and use ebuild command to compile the sources. Once you're finished with the fixes, you can apply them in the dist file. Have in mind that certain amount of work has already been done in the tempdir and your changes might not be picked up.

Best Regards,
Georgi

Nima0908 · n00b Joined: 24 Feb 2025 Posts: 44

Sorry for the late answer, i had lots to do last weak. Cleaning the distfile cach fixed it (i completely forgot i have to do that).
Thank you very much for your help