Hi,
cc:ing the bug and thus leaving some more context…
On Montag, 21. Dezember 2015, Vagrant Cascadian wrote:
> On 2015-12-21, Holger Levsen wrote:
> >> For now, relying on the fact that there are different actual kernels on
> >> various builds (4.x vs. 3.x) will hopefully be good enough to
Hi,
On Donnerstag, 3. Dezember 2015, Vagrant Cascadian wrote:
> Filed against libc-bin:
> https://bugs.debian.org/806911
> Aurelian Jarno filed a patch upstream to support using the uname26
> personality:
> https://sourceware.org/ml/libc-alpha/2015-12/msg00028.html
ok, cool, thanks!
> So
On 2015-12-21, Holger Levsen wrote:
> On Donnerstag, 3. Dezember 2015, Vagrant Cascadian wrote:
>> Filed against libc-bin:
>> https://bugs.debian.org/806911
>> Aurelian Jarno filed a patch upstream to support using the uname26
>> personality:
>>
Hi,
thanks Vagrant for catching and reporting this…!
On Mittwoch, 2. Dezember 2015, Vagrant Cascadian wrote:
> I suspect this is also an issue with amd64, though it shows up when
> trying to install build-deps:
> https://reproducible.debian.net/unstable/amd64/index_last_24h.html
yeah :/ it's
On 2015-12-01, Reiner Herrmann wrote:
> On Tue, Dec 01, 2015 at 02:13:07PM -0800, Vagrant Cascadian wrote:
>> Hey, I think all of the second builds on armhf are failing to set up the
>> build environment:
>>
>>
>>
On Tue, Dec 01, 2015 at 02:13:07PM -0800, Vagrant Cascadian wrote:
> Hey, I think all of the second builds on armhf are failing to set up the
> build environment:
>
> https://reproducible.debian.net/logs/unstable/armhf/gb_0.3.2-1.build2.log.gz
>
> I: Installing the build-deps
> I: user
Hi there!
To be clear, I'm in Athens atm and I don't really have time now to look
better at this, but:
On Tue, Dec 01, 2015 at 02:13:07PM -0800, Vagrant Cascadian wrote:
> Hey, I think all of the second builds on armhf are failing to set up the
> build environment:
>
>