From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] First Patch from me. Hope this Ok so. Socat, filan and procan.
Date: Fri, 06 Nov 2020 10:24:41 +0000 [thread overview]
Message-ID: <8F4A2F11-08BB-4FC5-B027-87732A29CE06@ipfire.org> (raw)
In-Reply-To: <d16f6998-367b-b3af-d056-42655410cabf@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1540 bytes --]
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
>>
>>
>
next prev parent reply other threads:[~2020-11-06 10:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200729212025.28443-1-user@router.home.v16.de>
2020-11-04 20:35 ` AW: " smooky
2020-11-04 21:16 ` Matthias Fischer
2020-11-04 22:04 ` AW: " smooky
2020-11-05 6:38 ` Matthias Fischer
2020-11-04 21:19 ` Matthias Fischer
2020-11-06 10:24 ` Michael Tremer [this message]
2020-08-03 14:05 smooky
2020-08-04 9:34 ` Michael Tremer
-- strict thread matches above, loose matches on Subject: below --
2020-07-30 22:22 smooky
2020-08-03 11:57 ` Michael Tremer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8F4A2F11-08BB-4FC5-B027-87732A29CE06@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox