I wrote rdopkg to automate boring and repetitive tasks related to RPM packaging of OpenStack *client projects and it grown to contain quite a lot of white automagic to make packagers' lives easier.
rdopkg contains functionality to easily keep RPM packages up to date with upstream while managing downstream patches in git patches branches (as opposed to plain .patch files). It can easily manage downstream patches and even rebase package distgit to new upstream release. It also contains utilities for managing python requirements.txt files and much more we need to package OpenStack into RDO/Fedora.
This workshop is for RPM packagers. If you maintain an RPM package that carries some patches, rdopkg will probably save you a lots of time and pain. I'll show you what conventions you need to follow in your dist-git and howto setup your repo in order for rdopkg to work.
I'll demonstrate basic packaging tasks with rdopkg, especially managing patches and rebasing a package to a new upstream version. I'll provide real life examples of rdopkg-managed packages from RDO. Based on your interest, I can also dive into more fancy functionality rdopkg provides such advanced python requirements.txt management or whatever you're interested in.
I'll also talk about how rpkg/fedpkg sucks and why I plot to create an ultimate RPM packaging framework called pwnpkg and finally give the world fedpkg it deserves. Join me in the glorious packaging revolution! :)