May 25 2020
09:53 AM JT-Cave: pcw_home, is it possible to connect a 7i84 and 7i85s to a 7i76E?
10:03 AM JT-Cave: nevermind on the first question, found the 7i76e_7i76x1_7i85sx2d.bit file
10:38 AM pcw_home: yes made a 5i25+7i76_7I89 bitfile when you asked a week or so ago
10:42 AM pcw_home: http://freeby.mesanet.com/5i25_7i76_7i89.bit
10:53 AM JT-Cave: thanks
10:54 AM JT-Cave: the guy finally placed the order lol
07:22 PM cerna: To the buildbot: Is there any reason (or is it an error) for master branch to build the precise RIP (1200.rip-lucid-i386, 1201.rip-lucid-rtai-i386, 1202.rip-lucid-amd64) but not the debian packages (4003.deb-lucid-i386, 4004.deb-lucid-amd64, 4006.deb-lucid-rtai-i386)? And similarly the 2.7 branch (4040.deb-buster-rtpreempt-i386, 4041.deb-buster-rtpreempt-amd64, 4042.deb-buster-rtpreempt-rpi4) - but building the RIP
07:22 PM cerna: versions?
07:47 PM jepler: if any build that 0000.checkin depends on fails, the packaging builds are not started. Perhaps I misunderstand the question, but if you're looking at cases where there are at least some failures that's why
07:48 PM jepler: RIP & test, then generate debian source packages, then build them
08:03 PM cerna: It actually doesn't fail, like for the latest deddd4e4ddb3a0197deb815ffd58d82e59afda3a, it just is never started on lucid deb builders - http://buildbot.linuxcnc.org/dists/lucid/ - the last is from February. But it is still tested on RIP. It seems like inconsistency to me.
08:52 PM jepler: http://buildbot.linuxcnc.org/buildbot/builders/1200.rip-lucid-i386/builds/6839/steps/platform-is-supported
08:52 PM jepler: so for instance this lucid build didn't occur since the branch is not supported there