Recent searches
Search options
@FrostyX@fosstodon.org
In case you are asked to backport some upstream commit into an RPM package (as a patch) and don't know how to do it, here is my workflow.
@FrostyX That was a great video. Thanks for sharing!
@FrostyX I was looking at https://spacepub.space/videos/watch/9cad106a-1a43-4a38-a18a-dfcece394051 (by @drewdevault) yesterday and it feels similar. Using ultra complicated tools for something simple. If instead of creating fake git repo and fiddling with git tools you just curl those patches from their URLs (+ .patch) and use something simple like quilt, your life would be easier. Yes, I am at SUSE and we love our quilt here. And concerning patch metadata in SPEC file: https://en.opensuse.org/openSUSE:Packaging_Patches_guidelines and a snippet in your $EDITOR.
@mcepl I never heard of quilt, I need to take a look at that. Thank you.
The reason why I go through the temporary git repo step is that rpmbuild is very pedantic about the patch context and simply downloading .patch from GitHub and using it in spec often fails because of line numbers or something not being 100% same. Does quilt help with something like this?
Also, you nailed it perfectly with the ultra-complicated thing for something that should be simple.
That's what I think as well, and that's why the bit gloomy vibe of my video 
Every documentation I read only mentioned using an existing patch in a spec file, never generating it. Leaving me with the impression that it is a trivial step. But when I tried to do it, it never was.