Very interesting.

The build should actually abort if this happens.

Could someone please investigate why this isn’t happening?

In the meantime, I will merge the patch by Marcel to add the package to the build process. Sorry, I must have overlooked that before.

-Michael

> On 4 Nov 2020, at 21:19, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
> 
> Addition:
> 
> See also in '_build.packages.log':
> 
> ...
> Nov  3 12:11:21: Building socat socat-1.7.3.4.tar.gz checksum OK
> + cd /usr/src/lfs
> + make -f socat LFS_BASEDIR=/usr/src dist
> '/usr/src/config/rootfiles/packages//socat' ->
> '/tmp/package-socat/ROOTFILES'
> tar: usr/bin/filan: Cannot stat: No such file or directory
> tar: usr/bin/procan: Cannot stat: No such file or directory
> tar: usr/bin/socat: Cannot stat: No such file or directory
> tar: Exiting with failure status due to previous errors
> tar: *: Cannot stat: No such file or directory
> tar: Exiting with failure status due to previous errors
> ...
> 
> On 04.11.2020 21:35, smooky(a)v16.de wrote:
>> Hey all.
>> 
>> Does anyone happen to have an idea why the socat package offered by Pakfire
>> does not contain any program data? 
>> It only contains the install.sh, uninstall.sh, update.sh, ROOTFILES and an
>> empty .tar.xz archive. 
>> Seen here
>> https://mirror1.ipfire.org/pakfire2/2.25-x86_64/paks/socat-1.7.3.4-1.ipfire.
>> The .tar.xz archive is filled with my locally created version.
>> 
>> best regards
>> 
>> Marcel Follert
>> 
>> 
>