On Fri, 2019-02-01 at 10:42 +0100, Yves-Alexis Perez wrote:
> On Fri, 2019-02-01 at 03:20 +0000, Ben Hutchings wrote:
> > As there isn't much time left before the point release, I am inclined
> > to make one more upload based on 4.9.144 that just fixes the ceph
> > regression and any other known recent regressions.
> >
> > Does anyone want to argue for updating further?
>
> Hi,
>
> I'm usually in favor of updating, but here we have a large delta between
> proposed-updates and current (.150/.153). There are 319 commits between .144
> and .150 (and 431 for .153) which would be nice to have since they likely fix
> quite some stuff (although they might as well introduce regression and we
> don't have a lot of time to test it).
>
>
> If we go for .144 + ceph fix, how do we handle the git part (since stretch is
> already at .150)? We create a stretch-9.8 branch or something?
I don't think the d-k-prerelease and d-k-tag scripts will accept that.
What I did for 4.9.144-2 was to move my local stretch branch around:
- Check out the stretch branch
- Check that I have no commits to push
- Reset to the new branch point: git reset --hard debian/4.9.144-1
- Commit my changes and tag
- Reset to upstream: git reset --hard salsa/stretch
- Merge the new tag: git merge debian/4.9.144-2
> In any case, I'd say we try to upload .153 (or .154) to proposed-updates just
> after the point release.
Yes, absolutely.
Ben.
--
Ben Hutchings
Life is what happens to you while you're busy making other plans.
- John Lennon
Attachment:
signature.asc
Description: This is a digitally signed message part