On Thu, May 19, 2016 at 02:52:27PM +1000, Jonathon Love wrote:
> so the advice i received regarding the name was that i must get it renamed
> upstream[1]. i don't think this will be possible because:
>
> - upstream is an established package, present in PYPI and macports
> - the developer is MIA
hi,
so the advice i received regarding the name was that i must get it
renamed upstream[1]. i don't think this will be possible because:
- upstream is an established package, present in PYPI and macports
- the developer is MIA
(additionally, the official Protocol Buffers 3 supports Python 3
umh, you force pushed everything, master, upstream and pristine-tar
branches. WHY? what did you do?
oh, sorry, i never intended for you to look at that repo, assuming you'd
look at the debian-mentors one.
And still it doesn't build, if that was meant to fix it.
Without thinking of it I alrea
On Tue, May 17, 2016 at 01:07:05PM +1000, Jonathon Love wrote:
> thanks for the review, and sorry for the embarrassing "does not build"
> situation. i was packaging on ubuntu, and my experience has been that if it
> works there, it will work on debian - but apparently not, i'll be more
> careful in
hi matt,
thanks for the review, and sorry for the embarrassing "does not build"
situation. i was packaging on ubuntu, and my experience has been that if
it works there, it will work on debian - but apparently not, i'll be
more careful in future.
i'm actually writing to ask your advice about
5 matches
Mail list logo
