László Böszörményi (GCS) wrote:
> Found this, seems to be solvable. But next time I'll do test builds
> on several architectures before upload.
In the past I've found it easier to upload protobuf to experimental
first when testing FTBFS fixes, or just new upstream releases. There's
always the
Hi,
On Fri, Nov 25, 2016 at 4:05 PM, lumin wrote:
> It is now present in unstable. However the buildd status seems bad.
Yes, seen that. :(
> ppc64el due to segfault during python2 test.
Do you know any reason why it may happen?
> kfreebsd-* had never compiled protobuf
On Thu, 2016-11-24 at 20:39 +0100, László Böszörményi (GCS) wrote:
> Your changes seem to be correct. I plan to upload the attached diff
> in some hours if you don't mind.
It is now present in unstable. However the buildd status seems bad.
ppc64el due to segfault during python2 test.
kfreebsd-*
On Thu, 2016-11-24 at 20:39 +0100, László Böszörményi (GCS) wrote:
>
> Your changes seem to be correct. I plan to upload the attached diff
> in some hours if you don't mind.
I see it in the NEW queue, thank you!
Hi,
On Thu, Nov 24, 2016 at 4:01 PM, lumin wrote:
> On Thu, 2016-11-24 at 14:37 +, Gianfranco Costamagna wrote:
>> I don't think it was a bad upload, because I used DoM to build and
>> test it.
>
> Thank you for confirmation. I checked the package at DoM and
> it is
5 matches
Mail list logo