Created attachment 585352 [details] Broken warzone2100-3.3.0_beta1 ebuild Warzone 2100 version 3.3.0_beta1 was released in February, but has not yet been updated in portage. https://forums.wz2100.net/viewtopic.php?f=1&t=15114 https://sourceforge.net/projects/warzone2100/files/releases/3.3.0/ I have attempted to version bump it myself, but it fails during the install phase. Attached is the ebuild I attempted to create. The following attachments are relevant troubleshooting information.
Created attachment 585354 [details] Output of `emerge --info`
Created attachment 585356 [details] Output of `emerge -pqv`
Created attachment 585358 [details] Build log for ebuild above
Created attachment 585360 [details] warzone2100-3.3.0_beta1.ebuild And that build error exactly is the reason the game hasn't been bumped yet... Attached is a still broken ebuild but bumped to EAPI-7 and with some other improvements.
(In reply to Lars Wendler (Polynomial-C) from comment #4) > Created attachment 585360 [details] > warzone2100-3.3.0_beta1.ebuild > > And that build error exactly is the reason the game hasn't been bumped yet... > > Attached is a still broken ebuild but bumped to EAPI-7 and with some other > improvements. Well at least I can rest tonight knowing I'm not the only one with that issue. I initially tried downgrading the EAPI in an attempt to fix it but to no avail. Some Google-fu also turned up very few results. Is there any explanation as to what causes that error? I've simply never seen it before, nor can I find any logical reason for it to occur, although my knowledge of developing ebuilds is still very limited.
(In reply to 0xC0ncord from comment #5) > > Well at least I can rest tonight knowing I'm not the only one with that > issue. I initially tried downgrading the EAPI in an attempt to fix it but to > no avail. Some Google-fu also turned up very few results. Is there any > explanation as to what causes that error? I've simply never seen it before, > nor can I find any logical reason for it to occur, although my knowledge of > developing ebuilds is still very limited. I have no idea. The "funny" part is, that the po/Makefile.in.in, which the real po/Makefile gets generated from, hasn't changed for three years. So the issue must be coming from somewhere else. But the project also comes with a cmake based build system so I might give that one a try when I have some spare time left.
Alright, found the issue. I'm working on a fix...
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=bd142618d8a708a307bad239bc74d857bae7211a commit bd142618d8a708a307bad239bc74d857bae7211a Author: Lars Wendler <polynomial-c@gentoo.org> AuthorDate: 2019-08-01 03:17:18 +0000 Commit: Lars Wendler <polynomial-c@gentoo.org> CommitDate: 2019-08-01 03:25:55 +0000 games-strategy/warzone2100: Bump to version 3.3.0_beta1 Closes: https://bugs.gentoo.org/691202 Package-Manager: Portage-2.3.69, Repoman-2.3.16 Signed-off-by: Lars Wendler <polynomial-c@gentoo.org> games-strategy/warzone2100/Manifest | 1 + .../warzone2100-3.3.0_beta1-gettext_version.patch | 36 +++++++ .../warzone2100/warzone2100-3.3.0_beta1.ebuild | 115 +++++++++++++++++++++ 3 files changed, 152 insertions(+)
Broken build for me. Tail of build.log: ... test /var/tmp/portage/games-strategy/warzone2100-3.3.0_beta1/work/warzone2100 = /var/tmp/portage/games-strategy/warzone2100-3.3.0_beta1/work/warzone2100 || cp ./doc/*.md doc/ /bin/mkdir -p '/var/tmp/portage/games-strategy/warzone2100-3.3.0_beta1/image/usr/share/doc/warzone2100-3.3.0_beta1' /usr/lib/portage/python3.6/ebuild-helpers/xattr/install -c -m 644 AUTHORS ChangeLog README.md doc/Scripting.md doc/js-globals.md COPYING COPYING.NONGPL COPYING.README '/var/tmp/portage/games-strategy/warzone2100-3.3.0_beta1/image/usr/share/doc/warzone2100-3.3.0_beta1' make[2]: Leaving directory '/var/tmp/portage/games-strategy/warzone2100-3.3.0_beta1/work/warzone2100' make[1]: Leaving directory '/var/tmp/portage/games-strategy/warzone2100-3.3.0_beta1/work/warzone2100' Traceback (most recent call last): File "/usr/lib/portage/python3.6/doins.py", line 611, in <module> sys.exit(main(sys.argv[1:])) File "/usr/lib/portage/python3.6/doins.py", line 602, in main os.path.dirname(source)): File "/usr/lib/portage/python3.6/doins.py", line 450, in _doins return install_runner.install_file(source, os.path.dirname(dest)) File "/usr/lib/portage/python3.6/doins.py", line 386, in install_file return self._ins_runner.run(source, dest_dir) File "/usr/lib/portage/python3.6/doins.py", line 195, in run sstat = os.stat(source) FileNotFoundError: [Errno 2] No such file or directory: b'doc/quickstartguide.html' * ERROR: games-strategy/warzone2100-3.3.0_beta1::gentoo failed (install phase): * dodoc failed *
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=81bc81d28357c3375786d936d3404e9bb210c468 commit 81bc81d28357c3375786d936d3404e9bb210c468 Author: Lars Wendler <polynomial-c@gentoo.org> AuthorDate: 2019-08-06 21:31:56 +0000 Commit: Lars Wendler <polynomial-c@gentoo.org> CommitDate: 2019-08-06 21:32:11 +0000 games-strategy/warzone2100: Added missing app-text/asciidoc to DEPEND Bug: https://bugs.gentoo.org/691202 Package-Manager: Portage-2.3.71, Repoman-2.3.17 Signed-off-by: Lars Wendler <polynomial-c@gentoo.org> games-strategy/warzone2100/warzone2100-3.3.0_beta1.ebuild | 1 + 1 file changed, 1 insertion(+)
