From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Current 'next' won't build
Date: Sat, 08 Jun 2019 11:21:23 +0100 [thread overview]
Message-ID: <98AEC0A0-509B-4434-8865-A715A03CBDE8@ipfire.org> (raw)
In-Reply-To: <de22197f-6779-053e-4e7f-25535e79f37e@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 793 bytes --]
For which architecture is this?
> On 8 Jun 2019, at 11:20, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
>
> Hi,
>
> today building current 'next' failed with the following error:
>
> ***SNIP***
> ...
> # Compress root filesystem
> # Reason for this tar+untar+tar is removing of entries listed two or
> more in src/ROOTFILES
> tar -c --exclude='#*' --exclude='proc/*' --exclude='dev/pts/*'
> --exclude='tmp/ROOTFILES' \
> -C / --files-from=/tmp/ROOTFILES -f /ipfire.tar
>
> tar: You may not specify more than one '-Acdtrux', '--delete' or
> '--test-label' option
>
> Try 'tar --help' or 'tar --usage' for more information.
> make: *** [cdrom:158: /usr/src/log/cdrom] Error 2
> ***SNAP***
>
> Can anyone confirm?
>
> Best,
> Matthias
next prev parent reply other threads:[~2019-06-08 10:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-08 10:20 Matthias Fischer
2019-06-08 10:21 ` Michael Tremer [this message]
2019-06-08 10:33 ` Matthias Fischer
2019-06-08 10:35 ` Michael Tremer
2019-06-08 11:38 ` Matthias Fischer
-- strict thread matches above, loose matches on Subject: below --
2018-12-23 9:59 Matthias Fischer
2018-12-25 8:22 ` Michael Tremer
2018-04-29 11:53 Matthias Fischer
2018-04-29 12:08 ` Peter Müller
2017-10-18 2:39 Matthias Fischer
2017-10-18 2:39 ` Michael Tremer
2017-10-18 13:56 ` Matthias Fischer
2017-10-18 14:22 ` Matthias Fischer
2017-10-18 14:50 ` Michael Tremer
2017-10-18 15:54 ` Matthias Fischer
2017-10-18 17:03 ` Matthias Fischer
2017-10-18 17:42 ` Michael Tremer
2017-10-19 14:00 ` Matthias Fischer
2017-10-19 19:10 ` Matthias Fischer
2017-10-23 14:22 ` 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=98AEC0A0-509B-4434-8865-A715A03CBDE8@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