| 17 Aug 2025 |
 emily | none; it'd need to skip Hydra entirely | 22:43:26 |
| emily | so hydraPlatforms on the root jobs that lead to it | 22:43:31 |
| emily | * so hydraPlatforms = [ ]; on the root jobs that lead to it | 22:43:39 |
| emily | (are those images actually entirely FOSS?) | 22:43:55 |
| emily | (because meta.license would be another route…) | 22:44:03 |
 Morgan (@numinit) | Gotcha, pretty sure I tried applying the toplevel meta, but something may not be taking. Thanks for the heads up | 22:59:15 |
| Morgan (@numinit) | Will get that fixed | 22:59:26 |
| emily | I will be putting up some Android-related PRs soon :) | 23:21:56 |
| emily | (nothing exciting - LLVM clean-up) | 23:22:05 |
| emily | but yeah the weird thing about hydraPlatforms is that anything else can still pull it in | 23:22:39 |
| emily | @numinit:matrix.org it looks like those system images include GMS btw? which I'm pretty sure is non-free | 23:25:20 |
| Morgan (@numinit) | yeah, that is likely | 23:25:37 |
| Morgan (@numinit) | The intent was to mark all of them | 23:25:51 |
| Morgan (@numinit) | they are certainly locked behind unfree for composing a SDK | 23:26:14 |
| emily | I got them through building the emulator | 23:27:29 |
| Morgan (@numinit) | ah, makes sense, yeah we should absolutely propagate that down | 23:28:03 |
| emily | you can just set meta.license on the fetchers | 23:29:34 |
| emily | and it'll do the trick for you | 23:29:42 |
| Morgan (@numinit) | yep yep, should work | 23:30:47 |
| 18 Aug 2025 |
 Vladimír Čunát | If you set an unfree license, you won't need hydraPlatforms. Moreover it will apply transitively (exclude anything depending on this from Hydra builds). | 05:54:04 |
| Morgan (@numinit) | Yep, did it that way, making its way through backports. | 06:51:51 |
|  @blastboomstrice:4d2.org left the room. | 14:03:16 |
|  knownasred changed their display name from redblueflame to knownasred. | 14:26:06 |
| 20 Aug 2025 |
|  @federicodschonborn:matrix.org changed their profile picture. | 01:07:25 |
 Winter | why do only some Hydra builds show the "build dependencies" tab? | 17:13:11 |
 dgrig | I'm following the breadcrumbs here, might be completely off, but:
[% IF drvAvailable %]
[% INCLUDE makeLazyTab tabName="tabs-build-deps" uri=c.uri_for('/build' build.id 'build-deps') callback="makeTreeCollapsible" %]
[% END %]
&&
[% IF drvAvailable %]<li class="nav-item"><a class="nav-link" href="#tabs-build-deps" data-toggle="tab">Build Dependencies</a></li>[% END %]
in https://github.com/NixOS/hydra/blob/0d2a030661fb1a6ba3f5cb83c627a72b562ebe74/src/root/build.tt#L469-L471
While drvAvailable is defined as:
$c->stash->{drvAvailable} = $MACHINE_LOCAL_STORE->isValidPath($build->drvpath);
So, since MACHINE_LOCAL_STORE seems to be local indeed, this tab will only exist if the derivation is available on mimas?
| 17:42:27 |
| 21 Aug 2025 |
|  sinan changed their profile picture. | 02:27:02 |
| sinan | 02:27:05 |
 Tristan Ross | HW team is likely going to be able to get remote hardware which could be usable for RISC-V support. What sort of requirements are necessary in terms of access, performance, storage, etc? | 15:37:34 |
 K900 | How much hardware? | 15:40:50 |
