From: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Xen-devel <xen-devel@lists.xenproject.org>,
Anthony PERARD <anthony.perard@vates.tech>,
Stefano Stabellini <sstabellini@kernel.org>,
Michal Orzel <michal.orzel@amd.com>,
Doug Goldstein <cardoe@cardoe.com>
Subject: Re: [PATCH 1/3] Rework rootfs generation to make a cpio archive
Date: Fri, 11 Apr 2025 13:47:09 +0200 [thread overview]
Message-ID: <Z_kBPfXvxDozbMNk@mail-itl> (raw)
In-Reply-To: <7dd33457-f748-45b5-b885-eb451bdab9e9@citrix.com>
[-- Attachment #1: Type: text/plain, Size: 907 bytes --]
On Fri, Apr 11, 2025 at 12:33:50PM +0100, Andrew Cooper wrote:
> On 11/04/2025 12:09 pm, Andrew Cooper wrote:
> > On 11/04/2025 12:06 pm, Marek Marczykowski-Górecki wrote:
> >> On Fri, Apr 11, 2025 at 11:52:15AM +0100, Andrew Cooper wrote:
> >>> + find $PATHS | cpio -o -H newc | gzip > "${COPYDIR}/rootfs.cpio.gz"
> >>> +
> >>> + # Print the contents for the build log
> >>> + zcat "${COPYDIR}/rootfs.cpio.gz" | cpio -tv
> >> add 'v' to cpio above instead?
> > Oh, of course. There's another instance of this pattern in argo, which
> > I'll fix up too.
>
> Apparently not.
> https://gitlab.com/xen-project/hardware/test-artifacts/-/jobs/9695952322
>
> I expect the -v is getting swallowed by the pipe.
Great, busybox's cpio prints it to stdout instead of stderr (as normal
cpio do)...
--
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-04-11 11:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-11 10:52 [PATCH TEST-ARTEFACTS 0/3] Rootfs generation (ARM and x86) Andrew Cooper
2025-04-11 10:52 ` [PATCH 1/3] Rework rootfs generation to make a cpio archive Andrew Cooper
2025-04-11 11:06 ` Marek Marczykowski-Górecki
2025-04-11 11:09 ` Andrew Cooper
2025-04-11 11:33 ` Andrew Cooper
2025-04-11 11:47 ` Marek Marczykowski-Górecki [this message]
2025-04-11 12:25 ` Frediano Ziglio
2025-04-11 12:39 ` Andrew Cooper
2025-04-11 15:53 ` Denis Mukhin
2025-04-11 17:50 ` Andrew Cooper
2025-04-11 18:26 ` Denis Mukhin
2025-04-11 18:36 ` Denis Mukhin
2025-04-11 10:52 ` [PATCH 2/3] Shrink the rootfs substantially Andrew Cooper
2025-04-11 12:35 ` Frediano Ziglio
2025-04-11 10:52 ` [PATCH 3/3] Provide an ARM64 rootfs too Andrew Cooper
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=Z_kBPfXvxDozbMNk@mail-itl \
--to=marmarek@invisiblethingslab.com \
--cc=andrew.cooper3@citrix.com \
--cc=anthony.perard@vates.tech \
--cc=cardoe@cardoe.com \
--cc=michal.orzel@amd.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.