| 29 Nov 2022 |
 Artturin | would be better if the move and .flatten were not there | 17:36:58 |
| Artturin | i think | 17:43:51 |
| 30 Nov 2022 |
 cole-h | I would be very unhappy to merge that (not that I don't appreciate your work and that this issue exists).
I don't want to hard-code a specific python version that will have to be kept in sync. It also carries the possibility of being incorrect when e.g. targeting a staging after 3.11 has merged into it. Or even a previous release that only has 3.10 but not 3.11 and we bump the alias to 3.11 in Nixpkgs and ofborg.
I don't have any better ideas at the moment, though... | 00:06:48 |
| Artturin | Have it as a passthru attribute in python3 and then get it in ofborg perhaps | 01:42:57 |
| 1 Dec 2022 |
|  hexa changed their display name from hexa to hexa (22.11 now). | 13:09:00 |
| hexa changed their display name from hexa (22.11 now) to hexa. | 14:38:48 |
| 2 Dec 2022 |
 Sandro | The log viewer should somehow separate logs for each package. It is usually quite hard to find the build failure for dependencies of the changed package. | 20:10:06 |
| cole-h | I have very little experience with javascript and web development as a whole, so you're welcome to file an issue at https://github.com/samueldr/ofborg-viewer (some day, I'll figure out how to transfer that to the ofborg org), but I at least will likely never attempt to fix that. | 20:11:47 |
| Artturin | https://github.com/NixOS/ofborg/pull/625 | 20:41:43 |
| Artturin | supersedes https://github.com/NixOS/ofborg/pull/615 | 20:42:21 |
| cole-h | How does --force handle files that aren't affected by the checkout (i.e. dirty files, but not the ones that might prevent checking it out)? | 20:43:24 |
