On Sat, Nov 12, 2022 at 08:06:56AM +, stefa...@debian.org wrote:
> Hi Faidon (2022.11.11_22:25:52_+)
> > I don't mind having an NMU, though, whether targeted or for the new
> > upstream version itself.
>
> Sure, happy to NMU a new upstream version, too. I'll 0-day NMU that.
>
> [...]
>
> >
Hi Faidon (2022.11.11_22:25:52_+)
> I don't mind having an NMU, though, whether targeted or for the new
> upstream version itself.
Sure, happy to NMU a new upstream version, too. I'll 0-day NMU that.
I'm afraid this specific bug isn't fixed there, yet, so we still need to
carry a patch. But i
On Fri, Nov 11, 2022 at 11:56:18PM +0200, Stefano Rivera wrote:
> I've prepared an NMU for python-maxminddb (versioned as 2.0.3-1.1) and
> uploaded it to DELAYED/2. Please feel free to tell me if I
> should delay it longer.
Thank you so much Stefano! I've been meaning to update to the latest
upstr
Control: tags 1022449 + patch
Control: tags 1022449 + pending
Dear maintainer,
I've prepared an NMU for python-maxminddb (versioned as 2.0.3-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Regards.
SR
diff -Nru python-maxminddb-2.0.3/debian/changelog
4 matches
Mail list logo