[elbe-users] Project build was not successful

[Kurt Kanzenbach]

Hi Ralf,

On Tue, Oct 22, 2019 at 05:13:09PM +0200, Ralf Schlatterbeck wrote:
> I'm trying to build a project that previously succeeded with Debian
> Stretch now with buster (and after an ELBE upgrade, I'm running
> 12.0+deb10+build781). ELBE is latest for debian stretch (so, yes, my
> build-system is still stretch).
>
> The build fails, I'm running
> elbe control --build-bin build $(cat elbe.prj)
>
> stderr says:
> Project build was not successful, current status: build_failed
>
> The last line of stdout says
> [INFO] Build finished with Error
>
> A nand.img seems to be created (but my Makefile doesn't retrieve it due
> to the error). I see no obvious failure in the whole build, just one
> traceback from a missing copyright file for a self-made package
> somewhere in the middle of a *long* log:
>
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/dist-packages/elbepack/efilesystem.py", line 148, in write_licenses
>     with io.open(copyright_fname, "rb") as lic:
> IOError: [Errno 2] No such file or directory: '/var/cache/elbe/386249c2-bb65-42eb-b6d4-a6daa6a3eb08/chroot/usr/share/doc/iptna/copyright'
>
> Is it possible this makes the whole build fail?

Yes, it does. The reason is, that the error handling has
changed. Whenever an error is encountered the build result is also
marked as failed.

However, there are some changes to license extraction code. Can you
retry with Elbe v12.1?

Thanks,
Kurt
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.linutronix.de/pipermail/elbe-users/attachments/20191023/55df5652/attachment.sig>