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
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
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!
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
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
On Sun, 2018-02-25 at 17:30 +, Chris Lamb wrote:
> 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
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?
On Sun, 2018-02-25 at 14:55 +, Chris Lamb wrote:
> Hi Stefan,
>
> > According to bug report #850534, it should be fixed by version
> > 3.2.6-2,
> > but obviously that version is not available for Debian stable.
>
> Actually… not so obvious! This should have been fixed in stable
> via
Hi Stefan,
> According to bug report #850534, it should be fixed by version 3.2.6-2,
> but obviously that version is not available for Debian stable.
Actually… not so obvious! This should have been fixed in stable
via #857746.
Emilio, you unblocked this in:
https://bugs.debian.org/857746#10
Hi Stefan,
> According to bug report #850534, it should be fixed by version 3.2.6-2,
> but obviously that version is not available for Debian stable.
Actually… not so obvious! This should have been fixed in stable
via #857746.
Emilio, you unblocked this in:
https://bugs.debian.org/857746#10
Package: redis-server
Version: 3:3.2.6-1
Followup-For: Bug #880474
According to bug report #850534, it should be fixed by version 3.2.6-2,
but obviously that version is not available for Debian stable.
-- System Information:
Debian Release: 9.3
APT prefers stable-updates
APT policy: (500,
Hi!
On Mon, 2017-11-20 at 07:48:18 +, Chris Lamb wrote:
> > redis-server: Unknown lvalue 'RunTimeDirectory' in section 'Service'
>
> Hm, so this was added for #846350. Not quite clear what I should have
> done - clearly a "Depends" would be wrong, but "Breaks" doesn't seem
> that sensible
severity 880474 minor
tags 880474 + wontfix
thanks
Hi Russell,
> > Sorry for replying earlier but I seemingly did not receive this bug report
> > by mail and have just seen it via my QA page.
>
> Maybe a DMARC issue. No big deal.
Ah well, please be assured its just an impassive mail server
On Monday, 20 November 2017 7:48:18 AM AEDT Chris Lamb wrote:
> Sorry for replying earlier but I seemingly did not receive this bug report
> by mail and have just seen it via my QA page.
Maybe a DMARC issue. No big deal.
> > redis-server: Unknown lvalue 'RunTimeDirectory' in section 'Service'
>
Hi,
Sorry for replying earlier but I seemingly did not receive this bug report by
mail and have just seen it via my QA page.
> redis-server: Unknown lvalue 'RunTimeDirectory' in section 'Service'
Hm, so this was added for #846350. Not quite clear what I should have
done - clearly a "Depends"
Package: redis-server
Version: 3:3.2.6-1
Severity: normal
[ 10.306287] systemd[1]: [/lib/systemd/system/redis-server.service:14]
Unknown lvalue 'RunTimeDirectory' in section 'Service'
I get the above in the kernel message log at boot. It seems that this version
of redis-server has a service
16 matches
Mail list logo
