Le 12/01/2016 17:09, Marcelo Santana a écrit :
On Tue, 12 Jan 2016 07:25:57 +0100
Christian PERRIER wrote:
Hello Marcelo,
Hello Christian,
Everything seems fine and I think you can push your changes to alioth.
Done.
Thanks a lot for your work, again.
Thank you for your support. :-)
On Tue, 12 Jan 2016 07:25:57 +0100
Christian PERRIER wrote:
> Hello Marcelo,
Hello Christian,
> Everything seems fine and I think you can push your changes to alioth.
Done.
> Thanks a lot for your work, again.
Thank you for your support. :-)
Kind regards,
--
Marcelo Santana (aka msantana
Quoting Marcelo Santana (marc...@msantana.eng.br):
> I just finished the changes that you proposed. Please could you take a
> look at my git repository [1] before I push them to the pkg-running
> repository?
>
> [1]https://git.msantana.eng.br/pytrainer.git
Hello Marcelo,
Everything seems fine
On Sun, 3 Jan 2016 20:05:27 +0100
Christian PERRIER wrote:
> Hello Marcelo,
Hello Christian,
[...]
> Indeed, what would help me would be:
>
> 1) cut the packaging QA commit
> (6c0f66469f49feff4a7e43bce502d6672e3ec1e9) in on commit per each
> individual change so that I can apply the patches i
On Mon, 4 Jan 2016 05:52:02 +0100
Christian PERRIER wrote:
Hello Christian,
[...]
> Here you go : your alioth account can now push to the git
> repository
Thank you so much. Soon as I finish the changes I'll ask you to take a
look before I push them to pkg-running repository.
> And now's
Quoting Marcelo Santana (marc...@msantana.eng.br):
> Idem.
>
> > I can of course do both 1) and 2) but I don't really know when...:-)
> >
> > Giving you commit access to the packaging git repository is certainly
> > something I'd be happy to do if you're OK with this. I'd then just
> > need the
On Sun, 3 Jan 2016 20:05:27 +0100
Christian PERRIER wrote:
[...]
> Hello Marcelo,
Hello Christian,
> Roughly looking at the changes, I'm OK with all of them, including the
> packaging QA.
>
> Thanks a lot for your work, which seems great.
Thanks for your quick reply. It is a pleasure to be
Quoting Marcelo Santana (marc...@msantana.eng.br):
> Hi there,
>
> I believe this bug was fixed by this commit[1] submitted to the
> upstream repository. As far as I know it was caused by the last upgrade
> to perl 5.22 occurred on Debian testing.
>
> [1]https://github.com/pytrainer/pytrainer/com
Quoting Marcelo Santana (marc...@msantana.eng.br):
> Hi there,
>
> I believe this bug was fixed by this commit[1] submitted to the
> upstream repository. As far as I know it was caused by the last upgrade
> to perl 5.22 occurred on Debian testing.
>
> [1]https://github.com/pytrainer/pytrainer/com
Hi there,
I believe this bug was fixed by this commit[1] submitted to the
upstream repository. As far as I know it was caused by the last upgrade
to perl 5.22 occurred on Debian testing.
[1]https://github.com/pytrainer/pytrainer/commit/fcc8f3361d4ff25559cb87a375fbbfc1192ca334
I've made some test
Hi Johannes,
Thanks for the info, please find my comments inline.
2013/11/3 Johannes Rohr :
> On Do, Okt 31, 2013 at 12:38:13 +0100, David García Granda wrote:
>> Hi,
>>
>> Pytrainer tries to validate every xml document before import and
>> unfortunately xml 1.0 is not supported. Some questions t
please note a similar bug report at
https://code.google.com/p/osmtracker-android/issues/detail?id=232
Obviously, the OSM Tracker dev holds that the speed extension is legit
and should be supported.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscr
On Do, Okt 31, 2013 at 12:38:13 +0100, David García Granda wrote:
> Hi,
>
> Pytrainer tries to validate every xml document before import and
> unfortunately xml 1.0 is not supported. Some questions trying to find
> root cause:
>
> 1.- Does gpx file validate?
>
> $ xmllint --noout --schema
Her
Hi,
Pytrainer tries to validate every xml document before import and
unfortunately xml 1.0 is not supported. Some questions trying to find
root cause:
1.- Does gpx file validate?
$ xmllint --noout --schema
2.- Did you Johannes change some packages on your local installation
in last weeks?
3.
Package: pytrainer
Version: 1.10.1-2
Severity: normal
As of today, pytrainer no longer imports gpx files generated by OSM Tracker. (I
last tried a couple of weeks back, it always used to work flawlessly.)
Here is what I see on the console:
running pytrainer from egg installation
data_path: /us
15 matches
Mail list logo
