https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/ Issue: dev-lang/nim-1.6.10-r2 fails to compile. Discovered on: amd64 (internal ref: ci)
CC'ing also the author of the commit (86595aa55fdefac85478ee78cea0d18abe525ae3)
Created attachment 846988 [details] build.log build log and emerge --info
I could not reproduce, getting: >: SUCCESS > * Waiting for unfinished jobs ... > [ ok ] > * ./bin/nim compile koch > Hint: used config file '/var/tmp/portage/dev-lang/nim-1.6.10-r2/work/nim-1.6.10/config/nim.cfg' [Conf]
Looks like the file exists but not executable for some reason.
*** Bug 889672 has been marked as a duplicate of this bug. ***
(In reply to Maciej Barć from comment #3) > I could not reproduce, getting: (In reply to Maciej Barć from comment #7) > > *** This bug has been marked as a duplicate of bug 889604 *** At least I am not the only one that hit the bug :)
It is one month later but..., this is my workaround: # emerge -ac nim Calculating dependencies... done! >>> Calculating removal order... >>> These are the packages that would be unmerged: dev-lang/nim selected: 1.6.8 protected: none omitted: none All selected packages: =dev-lang/nim-1.6.8 >>> 'Selected' packages are slated for removal. >>> 'Protected' and 'omitted' packages will not be removed. Would you like to unmerge these packages? [Yes/No] y >>> Waiting 5 seconds before starting... >>> (Control-C to abort)... >>> Unmerging in: 5 4 3 2 1 >>> Unmerging (1 of 1) dev-lang/nim-1.6.8... Packages installed: 1183 Packages in world: 282 Packages in system: 48 Required packages: 1183 Number removed: 1 * GNU info directory index is up-to-date.
(In reply to Emanuel Czirai from comment #7) > It is one month later but..., this is my workaround: > # emerge -ac nim > > Calculating dependencies... done! > >>> Calculating removal order... > > >>> These are the packages that would be unmerged: > > dev-lang/nim > selected: 1.6.8 > protected: none > omitted: none > > All selected packages: =dev-lang/nim-1.6.8 > > >>> 'Selected' packages are slated for removal. > >>> 'Protected' and 'omitted' packages will not be removed. > > Would you like to unmerge these packages? [Yes/No] y > >>> Waiting 5 seconds before starting... > >>> (Control-C to abort)... > >>> Unmerging in: 5 4 3 2 1 > >>> Unmerging (1 of 1) dev-lang/nim-1.6.8... > Packages installed: 1183 > Packages in world: 282 > Packages in system: 48 > Required packages: 1183 > Number removed: 1 > > * GNU info directory index is up-to-date. > It is one month later but..., this is my workaround: > # emerge -ac nim So after you unmerged older nim this version merged correctly?
(In reply to Maciej Barć from comment #8) > (In reply to Emanuel Czirai from comment #7) > > It is one month later but..., this is my workaround: > > # emerge -ac nim > > > > Calculating dependencies... done! > > >>> Calculating removal order... > > > > >>> These are the packages that would be unmerged: > > > > dev-lang/nim > > selected: 1.6.8 > > protected: none > > omitted: none > > > > All selected packages: =dev-lang/nim-1.6.8 > > > > >>> 'Selected' packages are slated for removal. > > >>> 'Protected' and 'omitted' packages will not be removed. > > > > Would you like to unmerge these packages? [Yes/No] y > > >>> Waiting 5 seconds before starting... > > >>> (Control-C to abort)... > > >>> Unmerging in: 5 4 3 2 1 > > >>> Unmerging (1 of 1) dev-lang/nim-1.6.8... > > Packages installed: 1183 > > Packages in world: 282 > > Packages in system: 48 > > Required packages: 1183 > > Number removed: 1 > > > > * GNU info directory index is up-to-date. > > > > It is one month later but..., this is my workaround: > > # emerge -ac nim > > So after you unmerged older nim this version merged correctly? no at all, I simply didn't realize that I didn't need nim at all for anything, thus the @world update that I was in the process of doing succeeded without nim, whilst it previously failed with it. I should've put "workaround" in quotes.
ci has reproduced this issue with version 1.6.12 - Updating summary.
slibtool_tinderbox has reproduced this issue with version 1.6.14-r1 - Updating summary.
*** Bug 928505 has been marked as a duplicate of this bug. ***
