All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Cole Robinson <crobinso@redhat.com>
Cc: qemu-devel@nongnu.org, deller@gmx.de
Subject: Re: [PATCH] roms: re-remove execute bit from hppa-firmware*
Date: Mon, 19 May 2025 14:45:23 +0100	[thread overview]
Message-ID: <aCs183hjzXVafV6B@redhat.com> (raw)
In-Reply-To: <52d0edfbb9b2f63a866f0065a721f3a95da6f8ba.1747590860.git.crobinso@redhat.com>

On Sun, May 18, 2025 at 01:54:20PM -0400, Cole Robinson wrote:
> This was fixed in c9d77526bddba0803a1fa982fb59ec98057150f9 for
> 9.2.0 but regressed in db34be329162cf6b06192703065e6c1010dbe3c5 in
> 10.0.0
> 
> When the bit is present, rpmbuild complains about missing ELF build-id
> 
> Signed-off-by: Cole Robinson <crobinso@redhat.com>
> ---
>  pc-bios/hppa-firmware.img   | Bin
>  pc-bios/hppa-firmware64.img | Bin
>  2 files changed, 0 insertions(+), 0 deletions(-)
>  mode change 100755 => 100644 pc-bios/hppa-firmware.img
>  mode change 100755 => 100644 pc-bios/hppa-firmware64.img

Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>

Though given the back & forth, I wonder if we wouldn't be better off
changing meson.build rules instead to mode 0644 for all blobs ?

  install_data(blobs,
               install_dir: qemu_datadir,
	       install_mode: 0644)

...assuming none actually need execute bits set.

With regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|



  reply	other threads:[~2025-05-19 13:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-18 17:54 [PATCH] roms: re-remove execute bit from hppa-firmware* Cole Robinson
2025-05-19 13:45 ` Daniel P. Berrangé [this message]
2025-05-25  0:26   ` Helge Deller
2025-07-15  6:04 ` Philippe Mathieu-Daudé

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=aCs183hjzXVafV6B@redhat.com \
    --to=berrange@redhat.com \
    --cc=crobinso@redhat.com \
    --cc=deller@gmx.de \
    --cc=qemu-devel@nongnu.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.