<samueldr>
I *think* there may be other issues, as I had a weird one where the partitions didn't show up after settling after partitioning one time
<samueldr>
but I assume this is unrelated, and I have really no way of testing :/
<samueldr>
7 minutes and a half per successful test run
<samueldr>
forcing ${builtins.currentTime} in the script and a while could allow one to run the test a lot of times over
<samueldr>
but since it happened only once, and the `until` loop didn't end up catching any of that, which happened before the check, I guess it's a non-issue
<samueldr>
a once in a blue moon thing
abathur has joined #nixos-dev
maljub019 has joined #nixos-dev
maljub01 has quit [Ping timeout: 260 seconds]
maljub019 is now known as maljub01
<hexa->
we *clap* have *clap* a *clap* grub2 *clap* maintainer
<lukegb>
it takes 1h45m to compile with 2 cores :(
<lukegb>
(and about 10m with $MANY)
<lukegb>
this just makes me want gchristensen's Magic Scheduler proposal :p
<gchristensen>
=)
<samueldr>
what can we do to make this a thing, as a community?
<gchristensen>
the danger of "mostly works" is, uh, I haven't prioritized it
<gchristensen>
good question
bennofs_ has quit [Ping timeout: 240 seconds]
hexa- has quit [Quit: WeeChat 2.9]
hexa- has joined #nixos-dev
orivej has quit [Ping timeout: 252 seconds]
cole-h has quit [Quit: Goodbye]
cole-h has joined #nixos-dev
jonringer has quit [Remote host closed the connection]
abathur has quit [Quit: abathur]
tomberek has quit [Quit: Connection closed]
justanotheruser has quit [Ping timeout: 260 seconds]
tomberek has joined #nixos-dev
abathur has joined #nixos-dev
pmy has quit [Ping timeout: 252 seconds]
AlwaysLivid has quit [Remote host closed the connection]
AlwaysLivid has joined #nixos-dev
bennofs__ has quit [Read error: Connection reset by peer]
bennofs_ has joined #nixos-dev
<rajivr>
There is a patch that is currently in the staging branch (https://github.com/NixOS/nixpkgs/pull/117914) that I was hoping to see land in unstable. I need it because mobile-nixos uses unstable, and I would like to use mobile-nixos cache for my cross-compilation work.
<rajivr>
samueldr: Thanks for the quick reply! :-) How to go from staging to staging next for this PR?
<rajivr>
In RFC26 it says - "staging-next is branched from staging"
<samueldr>
once a staging-next stabilisation round is done, and that staging-next is merged into master, the current state of staging becomes staging-next
<samueldr>
you can build Mobile NixOS against staging or staging-next, or even a git branch with your required fixes
<samueldr>
I'd even accept contributions clearly stating they need a fix not yet in master, maybe only waiting for the thing to land in master to merge the contribution :)
<rajivr>
I see. Thanks. Is there some way to track the "staging-next" stabilization round?
<samueldr>
yes
<rajivr>
My main motivation for seeing this land in "master" and "nixpkgs-unstable", is to use the cross-compilation tools. Mobile-nixos is not my primary target. I am experimenting on Xilinx ZynqMP and Raspberry Pi (aarch64, armv6l)
<rajivr>
But I am learning a lot from your work on Mobile NixOS, so thank you again! :-)
<samueldr>
that's why I couldn't find the open PR :)
<samueldr>
so in ~1-2 weeks depending on your luck it should be merged hopefully :)
<rajivr>
I see. Thanks! :-)
<aaronjanse>
Mic92 Bet
<aaronjanse>
But I need to focus on exams, then I can add more LSP features
<Mic92>
aaronjanse: Makes sense. The MVP would just take nix-instantiate and convert its error message to what github actions expect as a format and print that to terminal. Does not need to be superfancy to be useful.
<aaronjanse>
Oh I already have a partial Nix evaluator written in Rust to do this
<aaronjanse>
It's needed for my hover feature and autocomplete for stuff like `with pkgs; <type here>`
<aaronjanse>
(my screenshot utility hides my cursor etc :-/)
<Mic92>
aaronjanse: yes. nice. I find this more useful than the nixos option in emacs, that I disabled for speed-reason.
<aaronjanse>
Right now it caches evaluation across document edits, so `pkgs` isn't re-evaluated as you type in that list
<aaronjanse>
Furthermore, as you type and hover more, it'll populate that cache with more evaluated info
<aaronjanse>
Mic92: Oh and it also has goto, so if you click on `vim` it'll go to `vim =` in the big package list in nixpkgs. Then you can click on the path there to the derivation. It's also pretty fun for exploring stuff like the GCC bootstrap
<domenkozar[m]>
are there some heavy flakes users here that would have time/energy to review a proposal for changing one design decision in flakes?
<ma27[m]>
domenkozar: using it for quite a bit of (personal only) stuff (and contributed a bit to it). Can't promise that I'll have the time for a thorough review, but if you can share a link, I'm happy to look at it (asynchronously though) :)
jpo has quit [Ping timeout: 260 seconds]
jdnixx-M has quit [Quit: Bridge terminating on SIGTERM]
ky0ko1 has quit [Quit: Bridge terminating on SIGTERM]
<domenkozar[m]>
PMed :)
jonringer has joined #nixos-dev
jonringer has quit [Remote host closed the connection]
<domenkozar[m]>
trying to check if ofborg has a darwin builder now
<hexa->
the hardware is allocated, it is not yet configured
<domenkozar[m]>
I guess I'm writing a github actions tomorrow to build things from nixpkgs
<domenkozar[m]>
thanks hexa-
<gchristensen>
hm?
<domenkozar[m]>
something like @github build git
<gchristensen>
:( ah
<gchristensen>
maybe I can get the time today to setup the new machine and beat you to it
<domenkozar[m]>
that would be awesome
<domenkozar[m]>
I only want to get stuff done
<gchristensen>
though like I've said in the past I'm not opposed to moving away from ofborg where the alternatives are viable and give very strong/clear signals
tomberek has quit [Quit: Connection closed]
<sterni>
domenkozar[m]: would that mean building on github actions?
pmy has joined #nixos-dev
rajivr has quit [Quit: Connection closed for inactivity]
_ris has quit []
<domenkozar[m]>
Yes
<sterni>
hmm, I wonder if this will really work out if you accidentally hit a larger rebuild
AkechiShiro has joined #nixos-dev
Synthetica has joined #nixos-dev
<domenkozar[m]>
afaik ofborg also has a timeout
<sterni>
my impression has been that the machines doing ofborg builds are much faster than the github action containers (?)
<sterni>
builds could be half feasible though
<sterni>
eval on github actions is certainly impossible
<gchristensen>
the machines doing build are fairly generously allocated
<domenkozar[m]>
sterni: github will allow bigger machines in a few months
<domenkozar[m]>
either way, you can host your own agents with it and have a fraction of complexity
ris has joined #nixos-dev
<Mic92>
we also have github actions runner packaged now.
<Mic92>
If they come with nix pre-installed that would also make the jobs run faster.
<sterni>
that's cool
Jackneill has quit [Read error: Connection reset by peer]
bennofs_ has quit [Read error: Connection reset by peer]
bennofs_ has joined #nixos-dev
Guest80259 is now known as LinuxHackerman
LinuxHackerman is now known as Guest80427
Guest80427 has joined #nixos-dev
Guest80427 has quit [Changing host]
Jackneill has joined #nixos-dev
Guest80427 is now known as LinuxHackerman
justanotheruser has quit [Ping timeout: 245 seconds]
<lukegb>
iirc it's something along the lines of in general we don't want python modules using aliased versions of things, because then there's the possibility of ending up with multiple different versions of the same package in your pythonpath, which causes explosions
<lukegb>
python applications requiring specific versions is fine, though
<lukegb>
(because they're leaves)
<ivan>
ah I see thanks
<lukegb>
judging by the date on the commit and the tags I think it was late in the runup to 20.09 which might explain why it was merged in a hurry