Bug#835170: [Pkg-protobuf-devel] Bug#835170: transition: protobuf

[Dmitry Smirnov]

On Wednesday, 24 August 2016 1:28:32 AM AEST Sebastiaan Couwenberg wrote:
> On 08/23/16 16:45, Dmitry Smirnov wrote:
> > On Tuesday, 23 August 2016 11:32:10 AM AEST Sebastiaan Couwenberg wrote:
> >> protobuf (3.0.0-1) FTBFS pretty much everywhere. :-(
> >> 
> >> Using -Werror may be a bit much based on the buildlogs.
> > 
> > I think it may not be the problem in this particular case...
> 
> I disagree. A patch is for this issue (reported by Aaron M. Ucko in
> #835266) is available. Adding -Wno-error=misleading-indentation whenever
> -Werror is used solves the FTBFS in my i386 sid chroot.

Thank you very much for patch. I will upload it shortly.
Unfortunately I'm still unable to reproduce FTBFS in clean pbuilder 
environment...

-- 
Regards,
 Dmitry Smirnov.

---

Belief means not wanting to know what is true.
-- Friedrich Nietzsche


signature.asc
Description: This is a digitally signed message part.

Bug#835170: [Pkg-protobuf-devel] Bug#835170: transition: protobuf

[Robert Edmonds]

Dmitry Smirnov wrote:
> On Tuesday, 23 August 2016 8:51:23 PM AEST Adam D. Barratt wrote:
> > That's not an excuse for causing disruption in unstable.
> 
> I'm not sure when it is OK to cause disruption in unstable. For example
> uploading new GCC seems to cause a lot of problems despite attempts to
> mitigate FTBFS.

It's a very easy rule for protobuf, since protobuf has a non-trivial set
of reverse build-dependencies: every ABI bump for protobuf needs a
corresponding, coordinated ABI transition.

For previous protobuf transitions (2.5.0, 2.6.0), please review #726165
and #760343. It's not as simple as just uploading a new release to
unstable. Probably it should have been uploaded to experimental first,
to check that the package would build and pass its test suite on all
architectures. (E.g., see #572923 for an example of
architecture-specific breakage in protobuf.)

> Also do you have a clue why protobuf FTBFS on build servers? I'm unable to
> reproduce the problem...

I built it on amd64 in an up-to-date sid pbuilder chroot and it failed
in the same manner as it did on all the buildd's.

-- 
Robert Edmonds
edmo...@debian.org