On 2018/05/16 13:37, Harald Dunkel wrote: > On 5/16/18 1:07 PM, Stuart Henderson wrote: > > > > You can't create a syspatch from it. > > I am talking about a *private* syspatch. Something that I can > revert later to gain access to the official syspatches again. > That should be possible.
Oh. In that case, see /usr/src/distrib/syspatch/README, but you're not going to like it. > > > > If you can get it tested as a patch on a self-built -stable kernel > > and we can get it committed then there's a *chance* it might be > > errata worthy in which case you could go back to syspatches instead. > > > > Thats the interesting part. How can I "go back to syspatches"? AFAIR, > when I built stable on 6.1, then it was installed as part as the build > procedure. My system appeared to be "contaminated" to syspatch and it > refused to touch it on further updates. There was no way back. > > It would be nice if this had been fixed. There might be quicker ways, but this ought to work, syspatch -R do an "upgrade" install of the release syspatch
