Your message dated Tue, 11 Nov 2014 18:32:08 +0100
with message-id <[email protected]>
and subject line Re: Bug#768696: libsecret: FTBFS in jessie: tests timeout
has caused the Debian Bug report #768696,
regarding libsecret: FTBFS in jessie: tests timeout
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 [email protected]
immediately.)
--
768696: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768696
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: libsecret
Version: 0.18-1
Severity: serious
Tags: jessie sid
User: [email protected]
Usertags: qa-ftbfs-20141108 qa-ftbfs
Justification: FTBFS in jessie on amd64
Hi,
During a rebuild of all packages in jessie (in a jessie chroot, not a
sid chroot), your package failed to build on amd64.
Relevant part (hopefully):
> make[1]: *** Waiting for unfinished jobs....
> make[1]: *** wait: No child processes. Stop.
> make: *** wait: No child processes. Stop.
> make: *** Waiting for unfinished jobs....
> make: *** wait: No child processes. Stop.
> make[5]: *** [check-TESTS] Terminated
> make[4]: *** [check-am] Terminated
> make[3]: *** [check-recursive] Terminated
> semop(2): encountered an error: Invalid argument
> make[2]: *** [check] Terminated
> Makefile:2216: recipe for target 'check-TESTS' failed
> Makefile:2569: recipe for target 'check-am' failed
> Makefile:1996: recipe for target 'check-recursive' failed
> Makefile:2572: recipe for target 'check' failed
> E: Caught signal ‘Terminated’: terminating immediately
> Build killed with signal TERM after 60 minutes of inactivity
The full build log is available from:
http://aws-logs.debian.net/ftbfs-logs/2014/11/08/libsecret_0.18-1_jessie.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 ---
On 10/11/14 at 18:59 +0100, Emilio Pozuelo Monfort wrote:
> Control: tags -1 unreproducible
> Control: severity -1 important
>
> On 09/11/14 08:16, Lucas Nussbaum wrote:
> > Source: libsecret
> > Version: 0.18-1
> > Severity: serious
> > Tags: jessie sid
> > User: [email protected]
> > Usertags: qa-ftbfs-20141108 qa-ftbfs
> > Justification: FTBFS in jessie on amd64
> >
> > Hi,
> >
> > During a rebuild of all packages in jessie (in a jessie chroot, not a
> > sid chroot), your package failed to build on amd64.
> >
> > Relevant part (hopefully):
> >> make[1]: *** Waiting for unfinished jobs....
> >> make[1]: *** wait: No child processes. Stop.
> >> make: *** wait: No child processes. Stop.
> >> make: *** Waiting for unfinished jobs....
> >> make: *** wait: No child processes. Stop.
> >> make[5]: *** [check-TESTS] Terminated
> >> make[4]: *** [check-am] Terminated
> >> make[3]: *** [check-recursive] Terminated
> >> semop(2): encountered an error: Invalid argument
> >> make[2]: *** [check] Terminated
> >> Makefile:2216: recipe for target 'check-TESTS' failed
> >> Makefile:2569: recipe for target 'check-am' failed
> >> Makefile:1996: recipe for target 'check-recursive' failed
> >> Makefile:2572: recipe for target 'check' failed
> >> E: Caught signal ‘Terminated’: terminating immediately
> >> Build killed with signal TERM after 60 minutes of inactivity
> >
> > The full build log is available from:
> >
> > http://aws-logs.debian.net/ftbfs-logs/2014/11/08/libsecret_0.18-1_jessie.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.
>
> I can't reproduce this, either in a jessie or in a sid chroot. I'm thus
> lowering
> the severity.
I tried again, and couldn't reproduce it. So closing.
Lucas
--- End Message ---
