On 10/19/2010 05:26 PM, intrigeri wrote:
> Jameson Rollins wrote (19 Oct 2010 13:46:09 GMT) :
>> but maybe we can find some other ways to reduce entropy consumption
>
> I don't know if this would be considered good-practice, or even
> allowed by the Debian policy, but build-depending on haveged wo
Jameson Rollins wrote (19 Oct 2010 13:46:09 GMT) :
> but maybe we can find some other ways to reduce entropy consumption
I don't know if this would be considered good-practice, or even
allowed by the Debian policy, but build-depending on haveged would
probably fix the test suite entropy problems.
On Tue, 19 Oct 2010 15:34:10 +0200, Alexander Reichle-Schmehl
wrote:
> Am 19.10.2010 15:28, schrieb Alexander Reichle-Schmehl:
>
> > [..] The bad news
> > is, that in all of the the 8 failed builds, it always stopped at a
> > different point. I copied the full build logs of the failed builds to
Hi!
Am 19.10.2010 15:28, schrieb Alexander Reichle-Schmehl:
> [..] The bad news
> is, that in all of the the 8 failed builds, it always stopped at a
> different point. I copied the full build logs of the failed builds to
> http://people.debian.org/~tolimar/tmp/ ; I could make anything out of the
Hi!
Am 19.10.2010 10:42, schrieb Alexander Reichle-Schmehl:
>>> I can reproduce this bug in about 3/4 of the build tests using
>>> monkeysphere 0.31-1 and a simple pbuilder with a minimal configuration:
>> Hi, Alexander. New versions of this package have been uploaded that
>> claim to fix this i
Hi Jameson!
Am 18.10.2010 16:50, schrieb Jameson Rollins:
> On Mon, 18 Oct 2010 11:30:56 +0200, Alexander Reichle-Schmehl
> wrote:
>> I can reproduce this bug in about 3/4 of the build tests using
>> monkeysphere 0.31-1 and a simple pbuilder with a minimal configuration:
> Hi, Alexander. New ve
On Mon, 18 Oct 2010 11:30:56 +0200, Alexander Reichle-Schmehl
wrote:
> I can reproduce this bug in about 3/4 of the build tests using
> monkeysphere 0.31-1 and a simple pbuilder with a minimal configuration:
Hi, Alexander. New versions of this package have been uploaded that
claim to fix this i
Hi!
Am 15.10.2010 18:30, schrieb Jameson Rollins:
> Lucas, Alexander (or anyone who is encountering this bug, for that
> matter): can you please describe in detail exactly what commands and
> environments you're using produce this error? If you are using
> pbuilder, can you please describe in de
On Fri, 15 Oct 2010 16:22:41 +0200, Alexander Reichle-Schmehl
wrote:
> That is quite a strange bug; I could reproduce it simply by running
> pbuilder on the package multiple times. And while I'm using ntp
> according to the logs it hasn't been active.
Lucas, Alexander (or anyone who is encounte
Hi!
* Lucas Nussbaum [100810 17:20]:
> > > > Lucas and jrollins, can you please tell what time-changing software is
> > > > running on your build environments if any? This 1s offset looks like
> > > > the various ntp daemons adjustment process.
> > > None.
> > Lucas, is your build environment us
On 10/08/10 at 10:43 -0400, Jameson Rollins wrote:
> On Tue, 10 Aug 2010 16:06:09 +0200, Lucas Nussbaum
> wrote:
> > > Lucas and jrollins, can you please tell what time-changing software is
> > > running on your build environments if any? This 1s offset looks like
> > > the various ntp daemons ad
On Tue, 10 Aug 2010 16:06:09 +0200, Lucas Nussbaum
wrote:
> > Lucas and jrollins, can you please tell what time-changing software is
> > running on your build environments if any? This 1s offset looks like
> > the various ntp daemons adjustment process.
>
> None.
Lucas, is your build environmen
On 10/08/10 at 11:56 +0200, intrigeri wrote:
> Hi,
>
> > On 02/08/10 at 12:25 -0400, Daniel Kahn Gillmor wrote:
> >> This time warp error message seems problematic to me. jrollins, do you
> >> see this time warp report when you build?
> >>
> >> Lucas, is it possible that your rebuild environment
On Tue, 10 Aug 2010 11:56:03 +0200, intrigeri wrote:
> Lucas and jrollins, can you please tell what time-changing software is
> running on your build environments if any? This 1s offset looks like
> the various ntp daemons adjustment process.
As I mentioned before, I have never encountered this t
Hi,
> On 02/08/10 at 12:25 -0400, Daniel Kahn Gillmor wrote:
>> This time warp error message seems problematic to me. jrollins, do you
>> see this time warp report when you build?
>>
>> Lucas, is it possible that your rebuild environment has clock problems?
Lucas and jrollins, can you please te
On 02/08/10 at 12:25 -0400, Daniel Kahn Gillmor wrote:
> tags 591118 + unreproducible
> thanks
>
> On 08/02/2010 08:20 AM, Jameson Rollins wrote:
> > Hey, dkg et. al. It looks like this FTBFS is due to one of the keytrans
> > tests failing: "test working with two primary keys". I don't see this
tags 591118 + unreproducible
thanks
On 08/02/2010 08:20 AM, Jameson Rollins wrote:
> Hey, dkg et. al. It looks like this FTBFS is due to one of the keytrans
> tests failing: "test working with two primary keys". I don't see this
> failure when I run the tests on my own system. Has anyone else b
Source: monkeysphere
Version: 0.31-1
Severity: serious
Tags: squeeze sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20100731 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part:
> make[1]: Entering dire
18 matches
Mail list logo
