qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Helge Deller <deller@gmx.de>
To: "Daniel P. Berrangé" <berrange@redhat.com>,
	"Cole Robinson" <crobinso@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH] roms: re-remove execute bit from hppa-firmware*
Date: Sun, 25 May 2025 02:26:35 +0200	[thread overview]
Message-ID: <9cdae9a0-c82f-4238-9eef-792e51eaa535@gmx.de> (raw)
In-Reply-To: <aCs183hjzXVafV6B@redhat.com>

On 5/19/25 15:45, Daniel P. Berrangé wrote:
> 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>

Acked-by: Helge Deller <deller@gmx.de>


> 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.

yes, please.

Helge


  reply	other threads:[~2025-05-25  0:27 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é
2025-05-25  0:26   ` Helge Deller [this message]
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=9cdae9a0-c82f-4238-9eef-792e51eaa535@gmx.de \
    --to=deller@gmx.de \
    --cc=berrange@redhat.com \
    --cc=crobinso@redhat.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).