On Mi, Sep 14, 2016 at 12:28:12 +0200, Sebastiaan Couwenberg wrote:
> On 09/13/2016 03:39 PM, Sebastiaan Couwenberg wrote:
> > On 09/13/2016 02:47 PM, Jochen Topf wrote:
> >> I have the same problem as described here
> >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836240
> >> with libosmium.
On 09/13/2016 03:39 PM, Sebastiaan Couwenberg wrote:
> On 09/13/2016 02:47 PM, Jochen Topf wrote:
>> I have the same problem as described here
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836240
>> with libosmium. This is on testing. Do I just have to wait for the fix
>> to arrive in testin
Hi Jochen,
On 09/13/2016 02:47 PM, Jochen Topf wrote:
> I have the same problem as described here
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836240
> with libosmium. This is on testing. Do I just have to wait for the fix
> to arrive in testing? Or can I/we do something to fix this?
Yes,
Hi!
I have the same problem as described here
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836240
with libosmium. This is on testing. Do I just have to wait for the fix
to arrive in testing? Or can I/we do something to fix this?
Jochen
--
Jochen Topf joc...@remote.org http://www.jochentop