** Changed in: qemu
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1714750
Title:
2.10.0 cannot be installed on case-insensitive file system
Status in Q
We updated our u-boot sources to v2019.01 in QEMU commit
f2a3b549e357041f86d7e, and we removed the scripts/make-release
workaround in commit 082c0543baa6f23770, so all the loose ends I
mentioned in comment #18 are now fixed and will be in QEMU 4.0.
** Changed in: qemu
Status: New => Fix Co
Somebody re-reported this which reminded me that we forgot to tidy up the loose
ends here.
Current status:
* this is fixed in upstream u-boot with their commit 610eec7f0593574
(committed October 2017, and in u-boot release v2017.11 and later)
* in QEMU's release process we put in a workaround i
Hurray!
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1714750
Title:
2.10.0 cannot be installed on case-insensitive file system
Status in QEMU:
New
Bug description:
The https://download.qemu.
Update: Sam Protsenko has kindly written and submitted a u-boot patch which
resolves the filename clash:
https://lists.denx.de/pipermail/u-boot/2017-September/307910.html
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.l
Thanks for taking care of that @ubuntu-weilnetz
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1714750
Title:
2.10.0 cannot be installed on case-insensitive file system
Status in QEMU:
New
Bug d
See https://lists.denx.de/pipermail/u-boot/2017-September/304728.html.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1714750
Title:
2.10.0 cannot be installed on case-insensitive file system
Statu
Am 04.09.2017 um 17:11 schrieb Peter Maydell:
> Yes, it's awkward for users who are on OSX (or Windows, I assume).
Windows users who want to extract the tarball would have the same
problem. I don't think that there are many users who do that.
Nevertheless I have just sent an e-mail to the u-boot
>Thanks for putting the workaround into the homebrew packaging in the
meantime.
You're welcome. I have now shipped the 2.10.0 binaries.
>if this bug had been reported for one of the 2.10.x release candidates
it would maybe have been a release blocker
We should add a `devel` spec to the qemu form
Yes, it's awkward for users who are on OSX (or Windows, I assume). But
the 2.10.0 release is already out and we can't change it -- if this bug
had been reported for one of the 2.10.x release candidates it would
maybe have been a release blocker. As it is we have to wait for a 2.10.1
release (and we
I mean in that every user is going to have to figure this out
individually until it's fixed.
In any case it will not be a problem for our Homebrew users, as I will do this:
```
diff --git a/Formula/qemu.rb b/Formula/qemu.rb
index 16a54af167..db0e68d103 100644
--- a/Formula/qemu.rb
+++ b/Formula/qe
Eh? That command line is not particularly slow, especially compared to
the time it takes to download the tarball in the first place.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1714750
Title:
2.1
Right. The issue is that solution is O(n) not O(1).
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1714750
Title:
2.10.0 cannot be installed on case-insensitive file system
Status in QEMU:
New
B
There is a simple workaround: use
tar xf qemu-2.10.0.tar.xz --exclude qemu-2.10.0/roms/u-boot/scripts/Kconfig
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1714750
Title:
2.10.0 cannot be install
I agree. But it's not really tenable in the interim for the 2.9.0
tarball not to be able to even be unpacked on macOS.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1714750
Title:
2.10.0 cannot be
Yes, but that's not how we ship them today. (We're actually considering
having the ROM blob sources be in an entirely separate tarball from the
QEMU sources, for unrelated reasons).
We should fix this bug by:
(1) getting u-boot to fix it upstream
(2) moving to a fixed u-boot
--
You received th
>we don't actually build them, we just ship them for license compliance
reasons.
Would you be in compliance with the license if the u-boot sources were
themselves in a tarball inside your qemu tarball?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is sub
Hmm I'll try some magic tar invocations.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1714750
Title:
2.10.0 cannot be installed on case-insensitive file system
Status in QEMU:
New
Bug descript
I don't think it would be wise to downgrade u-boot. You can always just
skip unpacking the u-boot sources -- we don't actually build them, we
just ship them for license compliance reasons.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEM
The offending commit is
https://github.com/u-boot/u-boot/commit/61304dbec36dc445bbe7d2c19b4da0695861e0a8
so it should be possible to downgrade u-boot until it gets fixed
upstream, no?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
ht
That's apparently a problem with U-Boot. Could you please report this
issue to the U-Boot project instead (see
https://github.com/u-boot/u-boot)? We only include the u-boot sources in
the QEMU tarballs, but we do not maintain them in the QEMU project, so
we can not fix this issue here for you, sorr
21 matches
Mail list logo
