On 2023-09-27, Holger Levsen wrote:
> On Wed, Sep 20, 2023 at 12:25:36PM +, Holger Levsen wrote:
>> so I've powercycled the machine and also disabled the armhf workers now.
>> (under the (weak) assumption that this bug is mostly trigged when running
>> diffoscope on 32bit .debs...)
Most
hi,
On Wed, Sep 20, 2023 at 12:25:36PM +, Holger Levsen wrote:
> so I've powercycled the machine and also disabled the armhf workers now.
> (under the (weak) assumption that this bug is mostly trigged when running
> diffoscope on 32bit .debs...)
so on Sep 23rd I made diffoscope run under
On Wed, Sep 20, 2023 at 12:25:36PM +, Holger Levsen wrote:
> so I've powercycled the machine and also disabled the armhf workers now.a
this didnt really help:
mosh last connect some 50m ago:
13 109 19:00:30 up 6:41, 3 users, load average: 151.64, 205.31, 156.09
10 112 19:01:00 up
hi,
from #debian-reproducible just now:
and there we go again, first mosh connection lost after disabling i386
workers.
* | h01ger sighs. at least i was hopeful for a few hours
while running diffoscope on an armhf deb
so I've powercycled the machine and also disabled the armhf
package: diffoscope
version: 240
severity: important
x-debbugs-cc: reproducible-bui...@lists.alioth.debian.org
hi,
On Tue, Sep 05, 2023 at 10:05:58PM +0200, FC Stegerman wrote:
> It worked (and was probably needed) before as the "--" was interpreted
> by schroot, not diffoscope. So the solution
5 matches
Mail list logo
