I just learned upstream git now has tags, like: Notes Backport: bugfix I just tested 18 bugfixes since release of systemd-208 by hand saving them to /etc/portage/patches... (There may be a git command to automate this lenghtly procedure?) They flawlessly patched during the ebuilds epatch_user. My machine rebooted well and runs without issues! I could provide a "cat" of these files as one patch, but there might be a better handling through a special git command by Gentoo maintainers? Reproducible: Always
(In reply to Ulenrich from comment #0) > I just learned upstream git now has tags, like: > > Notes > Backport: bugfix Maybe it's more useful to set that tag as a USE flag in systemd-9999.ebuild (along with other tags), or hard-code it in a separate systemd-208.9999.ebuild?
Well, those are git notes. I don't see a problem making git fetch those but I don't really see where to go from there. We'd have to move forward from the release tag and check whether the future commits have the note... I can't think of any easy enough way of doing this.
There was a HEADS-UP announcement about it: --- Why? -- Well, we want to be nice to downstream. So far the inofficial place where we tracked backport-worthy commits was the fedora packaging git, but that's not fair to other distributions and was very focussed on the Fedora branching points. ... What do the notes you add mean? -- Currently we know three different annotations in the notes: Backport: bugfix Backport: documentation Backport: security The first marks important bug fixes, the second important documentation fixes, and the last one security fixes. So far I have not used the latter annotation though. We might add more annotation types later on. I want to nominate a commit as backport-worthy! --- I only found bugfix yet. I would have liked an additional info what release it fixes (fix207, fix208). But that does not happen. Surely it fixes the last release. The most easy fixes and the most in numbers will be in the first week after a release - I guess.
(In reply to Jeroen Roovers from comment #1) > systemd-208.9999.ebuild? That way the normal user won't get it. And an advanced user - like me? - could easily get it himself. The very best would be some sort of "stable" upstream release 10 days after a normal release, eg: 208.1 This not happening I would prefer a normal revision release at about 2 weeks after a release. Then further bugfixes will be available for the Gentoo~unstable user after a 2 more weeks period through the next normal upstream release ...
The systemd.ebuild has an enabled "epatch_user" It is possible to advertise single hotpatches in the forums. Downloading and saving them in /etc/portage/patches/.. this would serve as playing ground to prove validity of the bugfixes and will reward active users.
@mgorny, thanks for releasing these bugfixes And the wave of incoming bugfixes related to Systemd-208 seems to be over now.
