Overview
Request 1121011 revoked
- Add reproducible-slof-date.patch to make slof.bin reproducible (boo#1047218)
- Add reproducible-sphinx.patch to make sphinx output reproducible (boo#1102408)
both are not yet upstream, but the slof patch is submitted
and sphinx needs to get patched to get rid of this workaround.
- Created by bmwiedemann
- In state revoked
- 8 package maintainers
Loading...
Request History
bmwiedemann created request
- Add reproducible-slof-date.patch to make slof.bin reproducible (boo#1047218)
- Add reproducible-sphinx.patch to make sphinx output reproducible (boo#1102408)
both are not yet upstream, but the slof patch is submitted
and sphinx needs to get patched to get rid of this workaround.
bmwiedemann revoked request
1/3 part is already merged,
https://github.com/openSUSE/qemu/pull/44 sends part2 and mentions part 3 (slof update)
Thanks for the contribution. However, the development of the QEMU package happens in git (as I've tried to document in README.PACKAGING). I can see about integrating the patches in the repositories, as soon as I get to that. More important, are you planning to submit the patches to the upstream project(s) too?
The first patch is submitted at https://gitlab.com/qemu-project/SLOF/-/merge_requests/1 and https://lists.ozlabs.org/pipermail/slof/2023-October/002900.html
and the other is rather a safe workaround for an issue in sphinx that I still need to debug deeper, so ideally we can drop it after the underlying bug is fixed.
Would be nice if you could add these to git.
Hi @bmwiedemann ! So, the SLOF one, since it's submitted upstream, I guess we'll get it from there (if we can wait). If it's urgent, we can shortcut it in.
The Sphinx one, I'm fine taking it as a downstream workaround only, for now. What I was asking was if we could come up with an MR (to https://gitlab.suse.de/virtualization/qemu/-/tree/factory?ref_type=heads) or a PR (to https://github.com/openSUSE/qemu/commits/factory) with these patches as commits. :-)
I can take the patches and turn them into that myself, but I'd like them to have a proper subject, changelog, tags, etc (and while I can pick these up from the submission for the SLOF one, I wouldn't know what to write for the Sphinx one...)
So, can you send the MR/PR yourself? Or at least send me something to use as subject and changelog of the second one?
Also, about SLOF, which one do I pick up (if I'm the one doing it), the one on the ML or the one in gitlab?
For Sphinx:
It's reviewed in slof, but does not seem to be upstream yet.
@bmwiedemann are you planning to ping this?
https://lists.ozlabs.org/pipermail/slof/2023-October/002900.html
It was already pinged https://lists.ozlabs.org/pipermail/slof/2023-November/002901.html
@aginies, @ccrane, @charlesa, @claudiofontana, @dfaggioli, @dirkmueller, @jfehlig, @lin_ma, @lizhang, @lyan, @mhocko, @mlatimer, @mseben, @olh, @vulyanov: review reminder