FS#76066 - [qemu] 7.1.0-5 Empty firmware files in hppa,sparc,alpha,and s390 packages

Attached to Project: Arch Linux
Opened by Doug Johnson (dougvj) - Friday, 30 September 2022, 00:19 GMT
Last edited by David Runge (dvzrv) - Friday, 30 September 2022, 19:31 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Anatol Pomozov (anatolik)
David Runge (dvzrv)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Description:

These firmware files under `/usr/share/qemu` are empty files:

```
$ ls -lah /usr/share/qemu/{s390-*,palcode-clipper,openbios-sparc*,hppa-*}
-rw-r--r-- 1 root root 0 Sep 11 11:49 /usr/share/qemu/hppa-firmware.img
-rw-r--r-- 1 root root 0 Sep 11 11:49 /usr/share/qemu/openbios-sparc32
-rw-r--r-- 1 root root 0 Sep 11 11:49 /usr/share/qemu/openbios-sparc64
-rw-r--r-- 1 root root 0 Sep 11 11:49 /usr/share/qemu/palcode-clipper
-rw-r--r-- 1 root root 0 Sep 11 11:49 /usr/share/qemu/s390-ccw.img
-rw-r--r-- 1 root root 0 Sep 11 11:49 /usr/share/qemu/s390-netboot.img
```

This results in such messages as:

```
$ qemu-system-alpha
qemu-system-alpha: could not load palcode '/usr/bin/../share/qemu/palcode-clipper'
```

```
$ qemu-system-hppa
qemu-system-hppa: could not load firmware '/usr/bin/../share/qemu/hppa-firmware.img'
```

Etc.

I Confirmed the files exist in the qemu-common prefix in the PKGBUILD before splitting but I am not sure what causes them to truncate.

This task depends upon

Closed by  David Runge (dvzrv)
Friday, 30 September 2022, 19:31 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed with qemu 7.1.0-6
Comment by David Runge (dvzrv) - Friday, 30 September 2022, 07:16 GMT
@dougvj: Thanks for the ticket.

I guess stripping the packages was not a good idea after all. I'll see if I can split them out further or anything.
Comment by David Runge (dvzrv) - Friday, 30 September 2022, 09:29 GMT
Please check whether qemu 7.1.0-6 in [testing] fixes your issue.
Comment by Doug Johnson (dougvj) - Friday, 30 September 2022, 19:22 GMT
This is resolved in 7.1.0-6, thanks for the quick turnaround.
Comment by David Runge (dvzrv) - Friday, 30 September 2022, 19:31 GMT
Thansk for testing! :)

Loading...