nough to be useful...
Keep on reproducibilitizing!
live well,
vagrant
From ff8da4f3ef9674503da93e38be565c3a7837c7d2 Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian
Date: Sat, 9 Apr 2016 16:43:31 -0700
Subject: [PATCH] Disable download of package descripts by setting apt.conf
languages to none. Th
So, basically, nevermind, apparently pbuilder already does this
automatically:
< mapreri> I added acquire::languages="none" 6/7 months ago, i think
< mapreri> vagrantc: since pbuilder 0.216, 26 august 2015
And looks like the builders are using 0.223~bpo8+1, and I checked the
config on one of the
Doing some sql queires and a bit of eyeball heuristics, I've determined
the packages listed below frequently FTBFS due to timeout on armhf.
I was hoping we could drop blacklisting altogether as the build network
grew, but I'm not sure that's realistic with the current infrastructure.
Please black
On 2016-04-17, Steven Chamberlain wrote:
> I was wondering what is the performance of various armhf boards, for
> package building. Of course, the reproducible-builds team have a lot of
> stats already. Below I'm sharing the query I used and the results in
> case anyone else is interested in this
I think bpi0's SSD may be in a very bad state. It's one of the oldest
nodes, so it's no huge surprise to see disk failures there...
I do have an extra SSD on hand to replace it with, but it will mean a
clean re-install and then jenkins setup code run, so probably best to
suspend scheduling jobs re
On 2016-05-04, Holger Levsen wrote:
> On Tue, May 03, 2016 at 11:35:07PM -0700, Vagrant Cascadian wrote:
>> I think bpi0's SSD may be in a very bad state. It's one of the oldest
>> nodes, so it's no huge surprise to see disk failures there...
Yup, disk seemed to be
The following packages FTBFS on armhf between 18 hours and 18 hours and
5 minutes since May 1st, and have no builds marked "unreproducible" or
"reproducible". Please blacklist them on armhf for all suites:
activemq
aptdaemon
commons-math3
docbook-defguide
doc-linux-fr
eclipse
gcc-5
Three new build nodes ready to be added to the build network:
odu3a-armhf-rb.debian.net:
Odroid-U3, exynos4122 quad-core (cortex-a9), 2GB ram, ~60GB USB2 SSD
ssh port: 2243
ssh fingerprints:
256 96:13:3b:ec:45:72:45:bc:c7:78:29:73:56:81:4e:ae
/etc/ssh/ssh_host_ecdsa_key.pub (ECDSA)
2048 e3:08:75:
On 2016-06-02, Holger Levsen wrote:
> Hi Vagrant,
>
> On Sun, May 29, 2016 at 09:13:20AM -0700, Vagrant Cascadian wrote:
>> odu3a-armhf-rb.debian.net:
>> cb3a-armhf-rb.debian.net:
>
> those I can reach nicely…
Yay!
>> opi2c-armhf-rb.debian.net:
>> ssh port
On 2016-06-02, Holger Levsen wrote:
> opi2c already has too little diskspace, from
>
> https://jenkins.debian.net/view/reproducible/view/Debian_setup_armhf/job/reproducible_setup_schroot_experimental_armhf_opi2c/1/console
>
> tee: /tmp/schroot-create-8VxOVXtl: No space left on device
Sorry about
Well, I've been debugging why u-boot stopped building reprodicbly, and
it appears to be that the recent fix that really switches armhf to build
with it_CH.UTF-8 locale actually breaks u-boot reproducibility.
So, just for comparison, I also tested with other locales, including
some with non-latin "
Reassign jobs for ff2b-armhf-rb to other nodes, as it is down for the
forseeable future.
Available in the ff2b-reassign branch:
https://anonscm.debian.org/git/users/vagrant/jenkins.debian.net.git
---
job-cfg/reproducible.yaml | 9 +++--
1 file changed, 3 insertions(+), 6 deletions(-)
dif
On 2016-06-10, Holger Levsen wrote:
> On Thu, Jun 09, 2016 at 01:31:39PM -0700, Vagrant Cascadian wrote:
>> Reassign jobs for ff2b-armhf-rb to other nodes, as it is down for the
>> forseeable future.
>
> thanks for the patch, before I apply something similar I have a
>
On 2016-06-11, Holger Levsen wrote:
> On Fri, Jun 10, 2016 at 09:18:40AM -0700, Vagrant Cascadian wrote:
>> > thanks for the patch, before I apply something similar I have a
>> > question: does that mean ff2b is gone *forever*?
>>
>> Not 100% sure just yet; it
On 2016-06-11, Holger Levsen wrote:
> This shall give us some more time+ease while deciding if/when to remove
> all ff2b and opi2c related jobs…
Both should be back online now! So no need to rearrange the jobs
anymore.
Whew.
live well,
vagrant
signature.asc
Description: PGP signature
__
consistant regardless of the
build environment.
Thanks to HW42 for debugging the issue:
https://lists.alioth.debian.org/pipermail/reproducible-builds/Week-of-Mon-20160606/005722.html
For more information about reproducible builds:
https://reproducible-builds.org/
Signed-off-by: Vagrant
: Vagrant Cascadian
---
tools/default_image.c | 14 +-
tools/fit_image.c | 6 --
tools/imagetool.c | 20
tools/imagetool.h | 16
4 files changed, 41 insertions(+), 15 deletions(-)
diff --git a/tools/default_image.c b/tools
On 2016-07-10, Otto Kekäläinen wrote:
> Diffs reveal that the issue is expressed in products that stem from
> storage/tokudb/*. We are not able to poinpoint what it is exactly, and
> we are not even able to reproduce the unreproducible build.
>
> Here's what we've done in a sid amd64 VM:
>
> ==
On 2016-07-27, Ceridwen wrote:
> For most of the variations I've done so far, I've been either
> depending on external utilities or had POSIX-compliant ways to execute
> them. The rest of the variations pose more problems.
...
> 5. kernel: While `uname` is in the POSIX standard, mechanisms for
> a
On 2016-07-25, Jonathan McDowell wrote:
> I propose instead a Buildinfo.xz (or gz or whatever) file, which is
> single text file with containing all of the buildinfo information that
> corresponds to the Packages list. What is lost by this approach are the
> OpenPGP signatures that .buildinfo files
On 2016-08-11, Chris Lamb wrote:
> +--- ddd-3.3.12.orig/ddd/config-info
> ddd-3.3.12/ddd/config-info
> +@@ -59,6 +59,10 @@ esac
> + month=`date '+%m'`
> + day=`date '+%d'`
> + date=${year}-${month}-${day}
> ++if [ -n "${SOURCE_DATE_EPOCH}" ]
> ++then
> ++date=`date --utc --date="@${SOURCE_
New armhf board up and ready for configuration.
Thanks to Nvidia for the donation, and to Martin Michlmayr and Eric
Brower for making the arrangements!
jtk1a-armhf-rb.debian.net:
Jetson-TK1, nvidia tegra-k1 (cortex-a15) quad-core, 2GB ram
ssh port: 2246
ssh fingerprints:
256 ec:8e:dc:22:dd:69:d0:
opi2a is back! Not sure how to rearrange build jobs off the top of my
head, but we've got several cores just sittle idle again. :)
For some reason, systemd wasn't starting consistantly, hanging on
systemd-logind. Oddly, it worked well enough to still run build jobs,
but restarting daemons and upgr
Hi, Just heard about the SCALE CfP this weekend, and it's due *today*,
so am working on re-doing the talk I did at SeaGL, but could use help on
the long description. I've put up a pad for this with links to my SeaGL
slides:
https://pad.riseup.net/p/1Q5KsaDJnnis
If anyone could help extending th
Retrying without the diff, since that got moderated...
Using lazy unmount *might* allow the disorderfs filesystems to unmount
if a file descriptor is held open but later releases... worst case is it
shouldn't make anything worse.
available in "lazy-unmount" branch at:
https://anonscm.debian.or
git
live well,
vagrant
commit 351a85c7713ef9fece0df76959bbe7fe0bb3fde3
Author: Vagrant Cascadian
Date: Tue Nov 15 11:11:46 2016 -0800
Do a lazy unmount of disorderfs.
---
hosts/bbx15-armhf-rb/etc/pbuilder/rebuild-hooks/B01_cleanup | 2 +-
hosts/bbx15-armhf-rb/etc/pbuilde
On 2016-12-07, Jonathan McDowell wrote:
> On Tue, Dec 06, 2016 at 09:24:20PM +, Holger Levsen wrote:
>> On Mon, Nov 14, 2016 at 02:57:00PM +, Ximin Luo wrote:
>> > This email is a summary of some discussions that happened after the
>> > last post to bug #763822, plus some more of my own tho
On 2016-12-06, Axel Beckert wrote:
> Holger Levsen wrote:
>> On Tue, Dec 06, 2016 at 09:24:50AM -0800, Martin Michlmayr wrote:
>> > I heard from a Linaro contact that LeMaker wasn't able to fix the PCIE
>> > issue and was going to produce the board without, but that update is
>> > from October and
On 2017-01-16, Santiago Vila wrote:
> Before I use this rationale more times in some discussions out there, I'd
> like to be sure that there is a consensus.
>
> What's the definition of reproducible? It is more like A or more like B?
I don't know if you're aware of the recently created:
https:/
Another arm board ready to be configured for the build farm!
p64b-armhf-rb.debian.net:
Pine64+, Allwinner A64 (cortex-a53) quad-core, 2GB ram
ssh port: 2247
ssh fingerprints:
2048 19:26:31:fa:7b:ff:96:ae:14:20:b8:25:36:59:37:df
/etc/ssh/ssh_host_rsa_key.pub (RSA)
256 74:1d:59:57:c7:3b:c9:ad:a7:09
On 2017-02-13, Chris Lamb wrote:
> Mattia Rizzolo wrote:
>> Then, if the unblock is accepted, I'd say we should either freeze
>> diffoscope development […]
>
> Strongly against this. :)
>
>> or stop uploading to unstable
>
> We can always upload to experimental to keep release momentum. Or just
> k
On 2017-02-13, Mattia Rizzolo wrote:
> On Mon, Feb 13, 2017 at 01:32:55PM -0800, Vagrant Cascadian wrote:
>> The other obvious option is to not ship a version in stretch and rely on
>> stretch-backports, if diffoscope development hasn't yet settled down
>> enough (will it
Yet Another arm board ready to be configured for the build farm!
p64c-armhf-rb.debian.net:
Pine64+, Allwinner A64 (cortex-a53) quad-core, 2GB ram
ssh port: 2248
ssh fingerprints:
2048 7e:11:62:84:b2:e8:cd:2b:52:f5:41:c1:98:bf:7a:d2 (RSA)
256 83:48:b1:c2:11:45:5c:51:9d:67:d1:58:0a:95:3d:33 (ECDSA)
On 2017-02-16, Holger Levsen wrote:
> On Mon, Feb 06, 2017 at 01:39:47PM -0800, Vagrant Cascadian wrote:
> linux-image-4.10.0-rc6-arm64-unsigned (4.10~rc6-1~exp1) wird eingerichtet ...
> /etc/kernel/postinst.d/initramfs-tools:
> update-initramfs: Generating /boot/initrd.img-4.10.0-rc6
On 2017-02-19, Guillem Jover wrote:
>> * .buildinfo files are not generated when creating source-only uploads
>
> Fixed. Now always generated.
On a related note, is it currently possible to create a .buildinfo with
both the source and binary, but a corresponding .changes with only the
source?
Thi
Package: trydiffoscope
Version: 64
Severity: important
I haven't been able to use trydiffoscope for some weeks now, getting
tracebacks like the following:
$ date > a
$ # wait a bit...
$ date > b
$ trydiffoscope a b
Traceback (most recent call last):
File "/usr/bin/trydiffoscope", li
rant
From c55c67da65ed37bd4268005fbdede27767b1331b Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian
Date: Mon, 24 Apr 2017 10:21:21 -0700
Subject: [PATCH 1/2] Add support for .dtb (device tree blob) files.
---
diffoscope/comparators/__init__.py | 1 +
diffoscope/comparators/dtb.py
Control: tag 861109 pending
On 2017-04-24, Chris Lamb wrote:
> Thanks for implementing this. :) I'd just check two things:
>
> a) Unused subprocess import in test_dtb.py
Tested that it works without; committed and pushed.
> b) Whether the tests pass with jessie's device-tree-compiler
>
On 2017-05-26, Chris Lamb wrote:
>> jtx1a-armhf-rb.debian.net:
>> Jetson-tx1, quad-core (big.LITTLE Cortex-A53/A57), ~3.5GB ram,
>
> Hm? _Approximately_ 3.5GB ram? :)
I think the kernel is overly agressive reserving some ram(there was a
recent thread about it on one of the kernel lists), and with
On 2017-06-02, Holger Levsen wrote:
> On Fri, May 26, 2017 at 01:56:54PM -0700, Vagrant Cascadian wrote:
>> Got one old machine freshly reinstalled after a disk failure (rpi2c),
>> and three newly readied machines (ff64a, jtx1a, odc2a) that are arm64
>> capable, but configured
On 2017-06-03, Holger Levsen wrote:
> On Fri, Jun 02, 2017 at 08:46:14AM -0700, Vagrant Cascadian wrote:
>> > < h01ger> | odc2a is faster than jtx1a (also io wise, but both are
>> > rather fine…)
>> > < h01ger> | odc2a takes ages to gener
On 2017-06-03, Holger Levsen wrote:
> On Sat, Jun 03, 2017 at 09:27:38AM -0700, Vagrant Cascadian wrote:
>> On a related note, I haven't noticed any builds on ff64a or jtx1a... did
>> all their partner machines happen to be marked as disabled?
>
> there was a problem wi
On 2017-06-19, Holger Levsen wrote:
> On Mon, Jun 19, 2017 at 09:37:20AM +, Holger Levsen wrote:
>> so I've upgraded profitbricks-build2-i386 to stretch last night and so far it
>> *seems* everything went well and continues to go well.
>
> except that - if I'm not mistaken - there are no amd64
On 2017-06-19, Holger Levsen wrote:
> so I've upgraded profitbricks-build2-i386 to stretch last night and so far it
> *seems* everything went well and continues to go well.
Very exciting!
> after the amd64 nodes, I would like to upgrade the armhf nodes, possible on
> Wednesday.
For armhf, it mi
On 2017-06-19, Holger Levsen wrote:
> On Mon, Jun 19, 2017 at 06:38:06AM -0700, Vagrant Cascadian wrote:
>> > except that - if I'm not mistaken - there are no amd64 kernels for Debian
>> > i386
>> > anymore. Is that correct, or am I blind?
>> I think t
On 2017-06-21, Ian Jackson wrote:
> Daniel Kahn Gillmor writes ("Re: source-only builds and .buildinfo"):
>> On Tue 2017-06-20 18:10:49 +0100, Ian Jackson wrote:
>> > A .buildinfo file is not useful for a source-only upload which is
>> > veried to be identical to the intended source as present in t
On 2017-07-13, Mattia Rizzolo wrote:
> During the last IRC meeting we agreed on sending a "short" report to dda
> as a first step for our NMU campaign.
>
> I drafted it, and it ended up a lot longer than what I'd have liked. So
> please read it, and do any kind of rewriting/re-arrengemente you fee
Two new machines ready for incorporation into the armhf build network.
Thanks to Nvidia, Debian and Freegeek for the donations that
made this expansion phase possible!
jtk1b-armhf-rb.debian.net:
Jetson-TK1, nvidia tegra-k1 (cortex-a15) quad-core, 2GB ram
ssh port: 2252
ssh fingerprints:
256 MD5:6
.debian.net.git/
https://anonscm.debian.org/cgit/users/vagrant/jenkins.debian.net.git/commit/?h=new-armhf-jtk1b-jtx1b
Hopefully it's everything needed to deploy to the new machines.
Thanks for working on Debian's jenkins infrastructure!
live well,
vagrant
On 2017-07-13, Vagrant C
On 2017-08-16, Ximin Luo wrote:
> It looks like the GCC reviewer that looked at my patch this time
> around, really doesn't like environment variables. They seem to be
> happy to support the variable (including the syntax) as a command-line
> flag however.
> The original patch fixed ~1800 packages
On 2017-09-02, Holger Levsen wrote:
> On Fri, Sep 01, 2017 at 04:51:55PM +0200, Guillem Jover wrote:
>> > during discussing #844431 it became clear, that some information about the
>> > running kernel should be included in .buildinfo files, as this can affect
>> > the
>> > build.
>>
>> It is actu
Package: jenkins.debian.org
Severity: normal
Tags: patch
X-Debbugs-Cc: reproducible-builds@lists.alioth.debian.org
One new machine ready for incorporation into the armhf build network,
and one old one ready to be reactivated.
Welcome back jtk1a-armhf-rb.debian.net. Specs and fingerprints are
unch
On 2017-09-18, Axel Beckert wrote:
> Control: retitle -1 zsh: FTBFS with noatime mounts (e.g. on reproducible
> builds armhf nodes)
...
> We still see this issue with reproducible builds on armhf in unstable as
> well as stretch:
> https://tests.reproducible-builds.org/debian/rb-pkg/stretch/armhf/
On 2017-09-18, Russ Allbery wrote:
> Daniel Kahn Gillmor writes:
>> On Sun 2017-09-17 16:26:25 -0700, Russ Allbery wrote:
>
>>> I personally lean towards 2, which is consistent with what's in Policy
>>> right now, but I can see definite merits in 3. I believe the
>>> reproducible builds project i
On 2017-09-18, Vagrant Cascadian wrote:
> On 2017-09-18, Russ Allbery wrote:
>> Daniel Kahn Gillmor writes:
>>> On Sun 2017-09-17 16:26:25 -0700, Russ Allbery wrote:
>>> Does everything in policy need to be rigorously testable? or is it ok
>>> to have Policy
Package: jenkins.debian.org
Severity: normal
Tags: patch
X-Debbugs-Cc: reproducible-builds@lists.alioth.debian.org
Welcome back ff64a-armhf-rb.debian.net. Specs and fingerprints are
unchanged.
With the 4.14-rc1 kernel, the firefly-rk3399 boards have working cpufreq
support, and so the CPU can run
Package: jenkins.debian.org
Severity: normal
X-Debbugs-Cc: reproducible-builds@lists.alioth.debian.org
cbxi4a-armhf-rb.debian.net had a critical disk failure.
It's been reinstalled, so the ssh keys have changed:
256 SHA256:C8nL+YAOEhjWYH2tkeoP00sfiWi4bI2ZlI400idPBqU root@cbxi4a (ECDSA)
256 SHA25
On 2017-09-24, Mattia Rizzolo wrote:
> On Sun, Sep 24, 2017 at 07:14:22PM +0100, Chris Lamb wrote:
>> Naturally, please let know if there are other things like this.
>
> What I was about, is that the sentence implies that what's *right after*
> is all the changelog of the release, which is not righ
Package: jenkins.debian.org
Severity: normal
X-Debbugs-Cc: reproducible-builds@lists.alioth.debian.org
odxu4-armhf-rb.debian.net had a critical disk failure.
It's been reinstalled, so the ssh keys have changed:
256 SHA256:qdZCQDO2crGdXaDopH9OP5qen3XHml3Y68/BsEmmP8I root@odxu4a (ECDSA)
256 SHA256
On 2017-11-04, Holger Levsen wrote:
> On Mon, Oct 30, 2017 at 06:21:39PM +0100, Georg Faerber wrote:
>> @dkg: It seems, there is still a bug / race in dirmngr, which leads to
>> errors like "can't connect to '127.0.0.1': no IP address for host" and
>> in turn "marking host '127.0.0.1' as dead". See
On 2017-12-26, Ximin Luo wrote:
> This week's blog post draft is now available for review:
>
> https://reproducible.alioth.debian.org/blog/drafts/139/
The links to some of alioth's git repositories (maybe only jenkins
related ones) are apparently not valid at the moment; I'm assuming this
is due t
Control: affects 892539 diffoscope
On 2018-03-21, Matthias Klose wrote:
> pdftk still still depends on GCJ, and is likely to be removed when gcj is
> removed. Please stop build-depending on pdftk.
FWIW, there's a reference to a fork of pdftk that doesn't require gcj:
https://bugs.debian.org/89
On 2015-08-25, Andreas Bießmann wrote:
> On 07/28/2015 05:00 PM, Tom Rini wrote:
>> On Sun, Jul 26, 2015 at 06:48:15PM +0200, Paul Kocialkowski wrote:
>>> In order to achieve reproducible builds in U-Boot, timestamps that are
>>> defined
>>> at build-time have to be somewhat eliminated. The SOURCE
On 2015-07-26, Paul Kocialkowski wrote:
> In order to achieve reproducible builds in U-Boot, timestamps that are defined
> at build-time have to be somewhat eliminated. The SOURCE_DATE_EPOCH
> environment
> variable allows setting a fixed value for those timestamps.
...
> However, some other devic
On 2015-09-28, Paul Kocialkowski wrote:
> Le jeudi 24 septembre 2015 à 09:05 -0700, Vagrant Cascadian a écrit :
>> I think the use of "time = mktime(time_universal);" is where the problem
>> lies:
>
> […]
>
>> According to the mktime manpage:
>>
>&
I have another machine ready to add a few more cpu cycles to the armhf
rebuilds... Currently stress-testing it with some parallel u-boot and
linux builds, and it seems to be holding up at a load of 8-10; if those
work out ok, I'd say it's ready.
odxu4-armhf-rb.debian.net:
Odroid-XU4, exynos5422 qu
On 2015-11-09, Holger Levsen wrote:
> thanks a lot for this new node. I've set it up and included in the machinery
> now
That was fast... yay!
> btw, how will you attach the sdd?
> http://archlinuxarm.org/platforms/armv7/samsung/odroid-xu4 only speaks about
> sd-cards as far as I could see.
US
And another one!
wbd0-armhf-rb.debian.net:
Wandboard-Dual, imx6 dual-core, 1GB ram, ~60GB USB2 SATA spinning disk
ssh port: 2223
ssh fingerprints:
256 d9:50:c6:3b:f8:1d:38:ac:97:ea:62:ea:37:cd:98:ed
/etc/ssh/ssh_host_ecdsa_key.pub (ECDSA)
2048 48:4c:9c:b4:b7:41:76:6f:36:0d:eb:b5:83:bf:66:4c
/etc
And another!
rpi2b-armhf-rb.debian.net:
Raspberry PI 2B, broadcom(?) quad-core, 1GB ram, ~60GB USB3 SATA SSD
ssh port: 2230
ssh fingerprints:
256 42:3a:92:86:e8:a9:db:2f:1e:86:9b:f2:07:fa:87:97
/etc/ssh/ssh_host_ecdsa_key.pub (ECDSA)
2048 d1:a8:26:2a:0a:c9:1b:67:0d:c9:48:95:23:4b:9f:31
/etc/ssh/
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 script /srv/workspace/pbuilder/5651/tmp/hooks/D01_modify_environment
starting
FATA
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:
>>
>>
>> https://reproducible.debian.net/logs/unstab
On 2015-12-01, Vagrant Cascadian wrote:
> Also saw this message on an amd64/experimental build, although much
> later in the build environment setup:
>
>
> https://reproducible.debian.net/logs/experimental/amd64/python-letsencrypt_0.0.0.dev20151123-1.build2.log.gz
>
> T
Package: libc-bin
Version: 2.21-1
Severity: normal
X-Debbugs-Cc: reproducible-builds@lists.alioth.debian.org
Apparently, when run with "setarch uname26" or "linux64 --uname-2.6",
ldconfig segfaults.
setarch uname26 ldconfig
FATAL: kernel too old
Segmentation fault
libc-bin version 2.19-22
affects 806911 qa.debian.org
thanks
On 2015-12-03, Holger Levsen wrote:
> 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.debi
Please (add to the growing) blacklist on armhf: vxl qtbase-opensource-src
Both hit the 12 hour timeout at least once, and armhf is slow enough,
and hasn't neared 100% enough to keep building these...
live well,
vagrant
signature.asc
Description: PGP signature
_
On 2015-12-03, Holger Levsen wrote:
> On Donnerstag, 3. Dezember 2015, Vagrant Cascadian wrote:
>> Both hit the 12 hour timeout at least once, and armhf is slow enough,
>> and hasn't neared 100% enough to keep building these...
>
> no need to justify things, I assume
It might not come online for real until Sunday evening (just need to
move it into place with all the others), but figured I'd announce it
now:
odc1-armhf-rb.debian.net:
Odroid-C1+, quad-core Amlogic (meson8b? cortex-a5), 1GB ram, ~60GB USB3 SATA SSD
ssh port: 2231
ssh fingerprints:
256 9e:09:96:a8
On 2015-12-05, Vagrant Cascadian wrote:
> It might not come online for real until Sunday evening (just need to
> move it into place with all the others), but figured I'd announce it
> now:
>
> odc1-armhf-rb.debian.net:
...
> This is the first one running an older version of
This proposal outlines how to double or triple the current capacity of
the armhf reproducible build network by purchasing a variety of boards
and related equipment.
The current armhf reproducible build network is barely keeping up with
the demand, and it currently only supports "unstable". It woul
r of the process, or
other functions that run outside of reproducible_build.sh that need to
know those variables.
live well,
vagrant
commit 200c45bbb5768dce5649b05ad599c85c6bb14b50
Author: Vagrant Cascadian
Date: Fri Dec 18 15:02:32 2015 -0800
Implement support for build pools, and add an ex
On 2015-12-18, Holger Levsen wrote:
> Hi Vagrant,
>
> On Samstag, 19. Dezember 2015, Vagrant Cascadian wrote:
>> Patch below! No idea if it works, given that I don't have a spare
>> jenkins.debian.net or build network to test on, but hopefully it
>> demonstrat
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:
>> https://sou
On 2015-12-21, Holger Levsen wrote:
> On Samstag, 19. Dezember 2015, Vagrant Cascadian wrote:
>> I didn't spend any time really figuring out which nodes to add to the
>> example 16th build job, so that might need some adjusting.
>
> put some 4cores in one pool, and 2core
Ok, got the first of the armhf build network upgrade plan machines up
and running, awaiting integration into the network...
odxu4b-armhf-rb.debian.net:
Odroid-XU4, exynos5422 quad-core, 2GB ram, ~60GB USB3 SATA SSD
ssh port: 2232
ssh fingerprints:
256 71:38:c6:43:9c:85:aa:08:1f:e1:1c:8f:d0:a3:77:d
On 2015-12-25, Vagrant Cascadian wrote:
> Have been working a bit on two firefly boards, but need to
> sort out issues with MMC and USB, but at least u-boot is able to boot a
> debian kernel (built with a few config options added)...
Well, today was productive! Figured out the kernel o
Got a second Raspberry PI 2 set up, awaiting configuration...
rpi2c-armhf-rb.debian.net:
Raspberry PI 2B, broadcom(?) quad-core, 1GB ram, ~60GB USB3 SATA SSD
ssh port: 2235
ssh fingerprints:
256 85:c9:4c:6a:99:6a:d0:61:26:4b:00:2d:19:0c:67:a2
/etc/ssh/ssh_host_ecdsa_key.pub (ECDSA)
2048 39:da:ca:
On 2016-01-01, Holger Levsen wrote:
> On Mittwoch, 30. Dezember 2015, Vagrant Cascadian wrote:
>> Got a second Raspberry PI 2 set up, awaiting configuration...
>> rpi2c-armhf-rb.debian.net:
>
> I've set it up now and am in the process of integrating it into the jenkins
Two more quad-core systems ready to join the fun!
ff2b-armhf-rb.debian.net:
Firefly, rockchip rk3288 (cortex-a12(?)) quad-core, 2GB ram, ~60GB USB2 SATA SSD
ssh port: 2237
ssh fingerprints:
256 ca:65:9c:9c:df:6e:8c:b8:00:10:dc:f0:71:b0:57:ab
/etc/ssh/ssh_host_ecdsa_key.pub (ECDSA)
2048 cd:d8:b6:
On 2016-01-05, Holger Levsen wrote:
> On Dienstag, 5. Januar 2016, Vagrant Cascadian wrote:
>> Two more quad-core systems ready to join the fun!
>
> awesome, thanks a lot!
>
> I'm setting them up right now, pbuilder/schroot/maintenance jobs are
> basically
> t
This one has been rather finicky, but appears to be working now...
opi2b-armhf-rb.debian.net:
OrangePi Plus2, Allwinner H3 (cortex-a7) quad-core, 2GB ram, ~60GB USB2 SATA SSD
ssh port: 2238
ssh fingerprints:
256 3e:b4:a4:f3:3a:c1:ba:75:3a:4b:4f:c6:80:e6:04:5b
/etc/ssh/ssh_host_ecdsa_key.pub (ECDS
On 2016-01-14, Holger Levsen wrote:
> On Mittwoch, 13. Januar 2016, Vagrant Cascadian wrote:
>> opi2b-armhf-rb.debian.net:
>> OrangePi Plus2, Allwinner H3 (cortex-a7) quad-core, 2GB ram, ~60GB USB2
>> SATA SSD ssh port: 2238
>
> thanks, added to the jenkins setup. Once
Here's another board, in theory with more ram, but in practice...
cbxi4a-armhf-rb.debian.net:
Cubox-i4x4, imx6 quad-core, 2GB ram, ~60GB SATA SSD
ssh port: 2239
ssh fingerprints:
256 dc:9a:85:0a:d5:85:72:26:9b:5b:b8:89:24:8a:fb:46
/etc/ssh/ssh_host_ecdsa_key.pub (ECDSA)
2048 c1:dd:a6:c8:bf:26:a5:
On 2016-02-02, Holger Levsen wrote:
> thanks for setting it up, but:
>
> jenkins@jenkins:~$ ssh -v -p 2239 cbxi4a-armhf-rb.debian.net
> OpenSSH_6.7p1 Debian-5+deb8u1, OpenSSL 1.0.1k 8 Jan 2015
> debug1: Reading configuration data /etc/ssh/ssh_config
> debug1: /etc/ssh/ssh_config line 19: Applying o
On 2016-02-01, Vagrant Cascadian wrote:
> cbxi4a-armhf-rb.debian.net:
> Cubox-i4x4, imx6 quad-core, 2GB ram, ~60GB SATA SSD
Upgraded cbxi4a to 3.8GB of ram!
And added another node to join it:
cbxi4b-armhf-rb.debian.net:
Cubox-i4x4, imx6 quad-core, 3.8GB ram, ~60GB SATA SSD
ssh port: 22
On 2016-02-04, Holger Levsen wrote:
> I'd like to add proper licencing to the presentations in
> git.debian.org/git/reproducible/presentations.git and you in the to: headers
> of the mail are a git commiter to this repository, so I would like you to
> (re-)licence your contributions under the fo
This new board recognizes all 4GB of ram, yay!
ff4a-armhf-rb.debian.net:
Firefly-RK3288, quad-core rockchip 3288 (A12/A17?), 4GB ram
ssh port: 2241
ssh fingerprints:
2048 87:3e:d4:f7:00:65:bd:39:ea:47:81:16:55:d6:cf:66
/etc/ssh/ssh_host_rsa_key.pub (RSA)
256 b8:a5:af:69:6a:76:03:9a:e3:77:82:a3:d9
On 2016-03-03, Vagrant Cascadian wrote:
> I need to do some more testing with the BeagleBoard-X15 board to get
> support in the kernel and debian-installer, and try to enable eSATA
> support, but should be ready real soon now...
Well, got eSATA working finally, so decided to run with i
On 2016-03-05, Holger Levsen wrote:
> On Donnerstag, 3. März 2016, Vagrant Cascadian wrote:
>> This new board recognizes all 4GB of ram, yay!
>>
>> ff4a-armhf-rb.debian.net:
>> Firefly-RK3288, quad-core rockchip 3288 (A12/A17?), 4GB ram
>
> yay indeed & a
On 2016-03-06, Holger Levsen wrote:
> On Sonntag, 6. März 2016, Axel Beckert wrote:
>> I now wonder if a bunch of Raspberry Pi 3 -- since they have 64-bit
>> CPUs (IIRC an Allwinner A53T) -- would make us able to check
>> reproducible-builds for Debian arm64, too.
I got the impression it was anoth
Cc'ed correct debian-arm address...
On 2016-03-06, Holger Levsen wrote:
> On Sonntag, 6. März 2016, Axel Beckert wrote:
>> I now wonder if a bunch of Raspberry Pi 3 -- since they have 64-bit
>> CPUs (IIRC an Allwinner A53T) -- would make us able to check
>> reproducible-builds for Debian arm64, to
1 - 100 of 116 matches
Mail list logo