Re: [PATCH] rules: fix empty COMMITCOUNT/AUTORELEASE

2021-01-29 Thread Ilya Lipnitskiy
On Fri, Jan 29, 2021 at 10:23 AM Paul Spooren wrote: > > On Fri, Jan 29, 2021 at 10:43, Petr Štetiar wrote: > > I guess, that the actual error from that dump.txt file would be more > > useful in > > this case :) > > Sorry, it was late: > Makefile:48: *** Package/px5g-wolfssl is missing the

Re: [PATCH] rules: fix empty COMMITCOUNT/AUTORELEASE

2021-01-29 Thread Paul Spooren
On Fri, Jan 29, 2021 at 10:43, Petr Štetiar wrote: I guess, that the actual error from that dump.txt file would be more useful in this case :) Sorry, it was late: Makefile:48: *** Package/px5g-wolfssl is missing the VERSION field. Stop. VERSION is defined as PKG_VERSION-PKG_RELEASE, or

Re: [PATCH] rules: fix empty COMMITCOUNT/AUTORELEASE

2021-01-29 Thread Petr Štetiar
Paul Spooren [2021-01-28 23:25:57]: Hi, > ERROR: please fix package/utils/px5g-wolfssl/Makefile - \ > see logs/package/utils/px5g-wolfssl/dump.txt for details I guess, that the actual error from that dump.txt file would be more useful in this case :) Cheers, Petr

[PATCH] rules: fix empty COMMITCOUNT/AUTORELEASE

2021-01-29 Thread Paul Spooren
Packages that are in-tree only often lack a PKG_VERSION and only use the PKG_RELEASE to mark changes. Using COMMITCOUNT/AUTORELEASE variables causes an issue as both variables are empty during the metadata DUMP phase. Instead of leaving these variables empty and causing an error message like