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
Hi,
something like
... lfsmake2 socat ...
is missing in 'make.sh'.
'socat' wasn't built.
HTH, Matthias
On 04.11.2020 21:35, smooky@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
Hi Matthias.
Does that mean I should have included the customized make.sh with the patch? I didn't do that with lshw and ncdu either, but everything seems to work.
best regards
Marcel Follert
-----Ursprüngliche Nachricht----- Von: Matthias Fischer matthias.fischer@ipfire.org Gesendet: Mittwoch, 4. November 2020 22:17 An: smooky@v16.de; development@lists.ipfire.org Betreff: Re: AW: [PATCH] First Patch from me. Hope this Ok so. Socat, filan and procan.
Hi,
something like
... lfsmake2 socat ...
is missing in 'make.sh'.
'socat' wasn't built.
HTH, Matthias
On 04.11.2020 21:35, smooky@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
On 04.11.2020 23:04, smooky@v16.de wrote:
Hi Matthias.
Hi,
Does that mean I should have included the customized make.sh with the patch?
Exactly. ;-)
I didn't do that with lshw and ncdu either, but everything seems to work.
Both exist in 'make.sh' - no need to add. They were both added by MT (2020-09-21).
=> https://git.ipfire.org/?p=ipfire-2.x.git;a=blob;f=make.sh;h=9ddfd4c07bcf6f1f...
Added by MT: => https://git.ipfire.org/?p=ipfire-2.x.git;a=commit;f=make.sh;h=4d275bcd1f8638...
...and: => https://git.ipfire.org/?p=ipfire-2.x.git;a=commit;f=make.sh;h=76c5f3e0d96525...
If you add a *new* package to the distribution, an appropriate lfsmake2 ... -line must be added to 'make.sh' or nothing will be compiled.
Best, Matthas
best regards
Marcel Follert
-----Ursprüngliche Nachricht----- Von: Matthias Fischer matthias.fischer@ipfire.org Gesendet: Mittwoch, 4. November 2020 22:17 An: smooky@v16.de; development@lists.ipfire.org Betreff: Re: AW: [PATCH] First Patch from me. Hope this Ok so. Socat, filan and procan.
Hi,
something like
... lfsmake2 socat ...
is missing in 'make.sh'.
'socat' wasn't built.
HTH, Matthias
On 04.11.2020 21:35, smooky@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
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@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
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@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@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
-
Matthias Fischer -
Michael Tremer -
smooky＠v16.de