Subject: Need help for aport patch workflow

From: Faustin Lammler <[email-masked]>
Date: Thu, 7 Aug 2025 14:54:54 +0200

Hi!
I am trying to bump mariadb version 11.4.7 > 11.4.8 and I am struggling
with the patch process.

Can someone point me to the correct workflow? I did not found any
documentation on how to do that on the wiki nor on the aport repository.

As far as I understand the process, the approach would be:
1/ abuild bump mariadb-11.4.8
2/ abuild fetch && abuild unpack
3/ edit patch in src/mariadb...
4/ generate updated patch
5/ abuild checksum
6/ abuild prepare
...

The step 4/ is the one that I am struggling with. If there is no better
way than to edit files and to manually go trough all patches with `diff
-up` then I will do it, but there might be something much more
efficient?

Thanks a lot for your help.

-- 
Faustin

---

From: Konstantin Kulikov <[email-masked]>
Date: Fri, 8 Aug 2025 16:28:25 +0300

I only did that once or twice, but I find it helpful to have a git history
available, so I'd just grab a repo, checkout a tag and then test patches
there.
The problem is
1. patch may apply cleanly and produce correct results - nice
2. patch may apply cleanly and produce wrong results due to something else
changing - bleh
3. patch may not apply at all - investigate history and fix, problem may
have been fixed in a different way
4. patch merged upstream as is - nice

I don't think this is automatable, although tests help..