Bug#857746: Bug#880474: Bug#857746: Bug#880474: redis-server: Unknown lvalue 'RunTimeDirectory' in section 'Service'
Hi Adam, > > Best case scenario for me is that I upload what I proposed in > > #857746; I mean, it was seemingly approved before and the issues are > > still outstanding. > > There isn't necessarily a 1:1 mapping between changes that would be > approved for an unblock during freeze and changes that are likely to > get ACKed for a stable update. Oh hilariously I did not spot p-u vs. freeze unblock. This bug is a trainwreck of confusion :) > I've repurposed the unblock as a p-u request. Which way we go with the > exact changes will depend on someone looking over the diff with a > stable update perspective. (You are, of course, completely right that this would not necessarily or automatically qualify for stretch via p-u..) Best wishes, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#857746: Bug#880474: Bug#857746: Bug#880474: redis-server: Unknown lvalue 'RunTimeDirectory' in section 'Service'
retitle 857746 pu: package redis/3:3.2.6-1
tags 857746 = stretch
user release.debian@packages.debian.org
usertags 857746 = pu
thanks
Hi,
On Sun, 2018-02-25 at 18:14 +, Chris Lamb wrote:
> Hi Adam,
>
> > Ah, I think I got confused by the bugs - I meant #880474. I assumed
> > that you were looking at getting the service fix included, rather
> > than
> > the whole of the upstream releases.
> >
> > Before we both get any more confused, which of the above were you
> > actually requesting?
>
> Good idea! So, I want to fix #880474 ("Unknown lvalue
> 'RunTimeDirectory' in section 'Service'") in stretch.
>
> The real "confusion" is I had already fixed, uploaded and had
> unblocked this via #857746 yet this new version never actually hit
> stretch. (!)
As I explained, that's because there was an RC bug affecting the
version that was unblocked, that I assume no-one noticed at the time.
> Best case scenario for me is that I upload what I proposed in
> #857746; I mean, it was seemingly approved before and the issues are
> still outstanding.
There isn't necessarily a 1:1 mapping between changes that would be
approved for an unblock during freeze and changes that are likely to
get ACKed for a stable update.
I've repurposed the unblock as a p-u request. Which way we go with the
exact changes will depend on someone looking over the diff with a
stable update perspective.
Hopefully that won't be too long, but we are also in the week before
the p-u freeze for the 9.4 point release, which is generally fairly
busy.
Regards,
Adam
Bug#857746: Bug#880474: Bug#857746: Bug#880474: redis-server: Unknown lvalue 'RunTimeDirectory' in section 'Service'
Hi Adam,
> Ah, I think I got confused by the bugs - I meant #880474. I assumed
> that you were looking at getting the service fix included, rather than
> the whole of the upstream releases.
>
> Before we both get any more confused, which of the above were you
> actually requesting?
Good idea! So, I want to fix #880474 ("Unknown lvalue 'RunTimeDirectory'
in section 'Service'") in stretch.
The real "confusion" is I had already fixed, uploaded and had unblocked
this via #857746 yet this new version never actually hit stretch. (!)
Best case scenario for me is that I upload what I proposed in #857746;
I mean, it was seemingly approved before and the issues are still
outstanding.
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
Bug#857746: Bug#880474: Bug#857746: Bug#880474: redis-server: Unknown lvalue 'RunTimeDirectory' in section 'Service'
On Sun, 2018-02-25 at 17:54 +, Chris Lamb wrote: > Hi Adam, > > > > Do I need to re-upload? > > > > If you want to fix #857746 in stretch (which I assume is the > > overall > > goal) then yes, that'll need to go through proposed-updates with a > > release.d.o p-u bug > > I don't quite follow I'm afraid - I would simply be re-filing #857746 > with the exact same content? > > (If so, couldn't I reopen and re-upload? Mostly trying to understand > the process here and/or ensure I'm not missing anything, rather than > shortcut or bypass anything...) > Ah, I think I got confused by the bugs - I meant #880474. I assumed that you were looking at getting the service fix included, rather than the whole of the upstream releases. Before we both get any more confused, which of the above were you actually requesting? Regards, Adam
Bug#857746: Bug#880474: Bug#857746: Bug#880474: redis-server: Unknown lvalue 'RunTimeDirectory' in section 'Service'
Hi Adam, > > Do I need to re-upload? > > If you want to fix #857746 in stretch (which I assume is the overall > goal) then yes, that'll need to go through proposed-updates with a > release.d.o p-u bug I don't quite follow I'm afraid - I would simply be re-filing #857746 with the exact same content? (If so, couldn't I reopen and re-upload? Mostly trying to understand the process here and/or ensure I'm not missing anything, rather than shortcut or bypass anything...) Thank you for your patience. :) Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#857746: Bug#880474: Bug#857746: Bug#880474: redis-server: Unknown lvalue 'RunTimeDirectory' in section 'Service'
Hi Adam, > > What am I missing? :) > #857855, which was RC at the time and (at least according to the > metadata) a regression relative to the package that was already in > stretch. Huh, okay. Can you recommend the best way forward at this point? Mark the bug as notfound in the stretch version? Do I need to re-upload? I'm a little lost, alas :) Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
