Your message dated Thu, 1 Sep 2016 07:40:34 +0200
with message-id <20160901054034.dbnx4r3ixoeyu...@lorien.valinor.li>
and subject line Re: Bug#835778: criu: FTBFS: make[2]: *** No rule to make
target 'images/google/protobuf/descriptor.pb-c.c', needed by
'images/google/protobuf/descriptor.pb-c.d'. Stop.
has caused the Debian Bug report #835778,
regarding criu: FTBFS: make[2]: *** No rule to make target
'images/google/protobuf/descriptor.pb-c.c', needed by
'images/google/protobuf/descriptor.pb-c.d'. Stop.
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
835778: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835778
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: criu
Version: 2.5-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
> make[2]: Entering directory '/<<PKGBUILDDIR>>'
> PBCC images/google/protobuf/descriptor.pb-c.c
> google/protobuf/descriptor.proto:388:3: Expected "required", "optional", or
> "repeated".
> google/protobuf/descriptor.proto:388:12: Expected field name.
> CC images/stats.o
> make[2]: *** No rule to make target
> 'images/google/protobuf/descriptor.pb-c.c', needed by
> 'images/google/protobuf/descriptor.pb-c.d'. Stop.
> make[2]: Leaving directory '/<<PKGBUILDDIR>>'
> Makefile:180: recipe for target 'images/built-in.o' failed
> make[1]: *** [images/built-in.o] Error 2
The full build log is available from:
http://people.debian.org/~lucas/logs/2016/08/28/criu_2.5-2_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Hi Lucas,
On Sun, Aug 28, 2016 at 07:43:55PM +0200, Salvatore Bonaccorso wrote:
> Hi Lucas,
>
> On Sun, Aug 28, 2016 at 12:38:13PM +0200, Lucas Nussbaum wrote:
> > Source: criu
> > Version: 2.5-2
> > Severity: serious
> > Tags: stretch sid
> > User: debian...@lists.debian.org
> > Usertags: qa-ftbfs-20160828 qa-ftbfs
> > Justification: FTBFS on amd64
> >
> > Hi,
> >
> > During a rebuild of all packages in sid, your package failed to build on
> > amd64.
> >
> > Relevant part (hopefully):
> > > make[2]: Entering directory '/<<PKGBUILDDIR>>'
> > > PBCC images/google/protobuf/descriptor.pb-c.c
> > > google/protobuf/descriptor.proto:388:3: Expected "required", "optional",
> > > or "repeated".
> > > google/protobuf/descriptor.proto:388:12: Expected field name.
> > > CC images/stats.o
> > > make[2]: *** No rule to make target
> > > 'images/google/protobuf/descriptor.pb-c.c', needed by
> > > 'images/google/protobuf/descriptor.pb-c.d'. Stop.
> > > make[2]: Leaving directory '/<<PKGBUILDDIR>>'
> > > Makefile:180: recipe for target 'images/built-in.o' failed
> > > make[1]: *** [images/built-in.o] Error 2
>
> Thanks. Since I did not had the FTBFS when I uploaded 2.5-2 some days
> ago my best guess is that it is caused by the new upload of protobuf
> (which unfortunately was started as an uncoordinated transition).
>
> I will try to look into that issue ASAP.
With the recent binNMU of protobuf-c this got resolved.
Regards,
Salvatore
--- End Message ---
