<niksnut>
well, messing with the bootloader is *especially* something that shouldn't be done on the stable branch :p
<niksnut>
because it's the one thing we can't recover from
<niksnut>
if it goes wrong
<ekleog>
OTOH looks like it's not changing anything for people without the option set
<domenkozar[m]>
the only part that changes the bootloader runtime is `[-configurationLimit:]` which I've shown in the PR that if you substitute with 0, it's a noop
<domenkozar[m]>
can also be made a bit more explicit
<domenkozar[m]>
I'd prefer not to maintain a fork until september but I'm open to alternatives
init_6 has joined #nixos-dev
Jackneill has quit [Ping timeout: 245 seconds]
Jackneill has joined #nixos-dev
johanot has quit [Quit: WeeChat 2.4]
Jackneill has quit [Ping timeout: 258 seconds]
Jackneill has joined #nixos-dev
<manveru>
domenkozar[m]: i'd love that for my rpi too :)
<gchristensen>
I think it is a good idea too, we'll definitely need to get samueldr and sphalerite to look at it and weigh in w.r.t. backports, and maybe give it a few weeks on unstable before backporting
<niksnut>
yeah a bit of soak time on master is a good idea
<jtojnar>
I will just revert the latter, since the former is superior
<worldofpeace>
that's pretty common with python packages, it moves so quick in nixpkgs
<ekleog>
do we really want to have files specialized for python2 support?
<ekleog>
like, python2 countdown is going to be over in a few months, not supporting peripheral packages like scikit over there would make sense to me (now, the work has already been done, so I'm not debating that, just wondering whether I should care about python2)
<gchristensen>
we won't be able to just drop py2 at the EoL unfortunately
<gchristensen>
so I think it is premature to start being too aggressive about cutting it away
<ekleog>
definitely not, but we might be able to start phasing it out :)
<ekleog>
like, not trying to keep support for packages whose latest version doesn't support python2 and which aren't needed for our own code to work
<ekleog>
that said I guess timokau[m] will have a different view on the matter?
<ekleog>
(my own view being, for the time being, “well… to drop py2 we need to start somewhere”)
cjpbirkbeck has joined #nixos-dev
Guanin has left #nixos-dev ["Leaving"]
Guanin has joined #nixos-dev
Guanin is now known as Amarandus
<jtojnar>
worldofpeace: what do you think about the discource announcement?
<worldofpeace>
Maybe there should be a development announcements section?
<jtojnar>
worldofpeace: yeah, just wanted to suggest that
<jtojnar>
zimbatm^
orivej has joined #nixos-dev
<worldofpeace>
Or maybe there should be development highlights each month, with important notices to maintainers too.
<jtojnar>
that feels like too much work
<jtojnar>
important changes announce list where people can just post something like a PR link with short description is lower effort
<worldofpeace>
that's pretty much what I meant
<jtojnar>
highlights mean that some curator produces them (like nixos-weekly), I would prefer something more organic where anyone can post and things are immediately published
<jtojnar>
s/mean/mean to me/
<samueldr>
yeah, a discourse category "just so you know I did ______"
pie_ has joined #nixos-dev
<samueldr>
that also may help RMs figuring out changes for the next release's release notes
<worldofpeace>
yeah and discourse already would work perfect for that
pie_ has quit [Remote host closed the connection]
pie_ has joined #nixos-dev
pie_ has quit [Remote host closed the connection]
pie_ has joined #nixos-dev
<worldofpeace>
samueldr: getting release notes together for a nixos release sounds like a lot of work
<samueldr>
it's not as bad as it looks, it's mostly a long winded effort to comb through commits/PRs rather than a complicated task requiring thinking
<samueldr>
and with git, checking the history of only one of the base folder at a time makes it easier, check lib for changes, check pkgs for notable changes, check nixos for notable changes
<samueldr>
with --merges-only and --no-merges (iirc) it also makes it easier to understand
<worldofpeace>
I thought thinking was easy for humans and sorting was for machines :P
<worldofpeace>
but I guess we adapt
<samueldr>
just enough thinking so it's harder for machines :), though I think I also grepped away version bumps
<worldofpeace>
is the `merges-only` part documented?
<samueldr>
in our docs, no, I think there's no tips for figuring out the release notes
<samueldr>
it's `--merges` and `--no-merges` for git log, tig also respects those parameters
<worldofpeace>
just asking because there might be a potential future release manager mentally acclimatizing 😸
* gchristensen
perks up
<worldofpeace>
but they're pretty unsure how they'll handle it
<timokau[m]>
ekleog: I'll do a little happy dance as soon as python2 dies
<timokau[m]>
I don't have a very strong opinion on weather or not we want to keep py2 support for scikitlearn. Just by default I try not to unnecessarily break things for people
<ekleog>
'k )
<ekleog>
:)*
<timokau[m]>
gchristensen: That question may be naive, but why won't we be able to drop support at EOL?
<gchristensen>
because it is impossible, far too many very important things depend on py2
<gchristensen>
effectively no (widely used) distro is able to do this
<timokau[m]>
Hm, that sounds like we'll never get rid of python2 :/
<timokau[m]>
Do you have examples for Very Important Things that still only support py2?
<gchristensen>
I feel quite sick right now, so I'm not going to go looking too hard
<samueldr>
could python2 be isolated, so that it doesn't hold back things incompatible with it in the infra, while allowing to use it as a dependency for those important bits in the time?
<timokau[m]>
Doesn't matter if you don't know anything f the top of your head, just idle curiosity :)
<gchristensen>
samueldr: that might be
<samueldr>
some kind of pkgs.__warrantyVoidIfUsed.python2 :)
<niksnut>
meta.broken?
<samueldr>
wouldn't that make transitive users broken too?
<niksnut>
yes
alp has quit [Ping timeout: 258 seconds]
alp has joined #nixos-dev
Drakonis has joined #nixos-dev
pie_ has quit [Remote host closed the connection]
cjpbirkbeck has quit [Quit: Quitting now.]
pie_ has joined #nixos-dev
Drakonis has quit [Read error: Connection reset by peer]
pie_ has quit [Ping timeout: 268 seconds]
pie_ has joined #nixos-dev
matthewbauer has joined #nixos-dev
<matthewbauer>
niksnut: Would it be possible to integrate `nix-bundle` functionality into Nix? Right now it still uses the old-style Nix commands, but I wonder if it deserves its own commands
<{^_^}>
matthewbauer/nix-bundle#47 (by haslersn, 1 day ago, open): Make CLI similar to nix build
<niksnut>
matthewbauer: I think that would be pretty cool
<tilpner>
niksnut: What about other subcommands, like generators for expression (node, cabal, cargo -> nix)? guix integrated those too
<niksnut>
could be, but they'd have to be written in C++ (or maybe rust in the future)
<niksnut>
what dependencies would be needed for nix bundle?
<qyliss>
I wouldn't like that I think. The best way to generate those expressions changes very regularly, and experimentation and there not being one "blessed" way is pretty important.
<niksnut>
yeah
<ekleog>
OTOH, having one “blessed” way is a good way to say “this is supported” -- personally, with the plethora of python to nix things, I'm completely lost
<ekleog>
The “blessed” way can still evolve, it's not set in stone
<ekleog>
so long as the overall API is fixed, that is
<qyliss>
turnaround time is way bigger with stuff in Nix core, and it's hard enough to experiment with new stuff as it is.
<qyliss>
As a Bundix maintainer, it would be a lot more difficult for me to iterate on Ruby packaging if I had to go through Nix
<ekleog>
You wouldn't have to go through nix
<ekleog>
you could maintain bundix, and there to be a nix way that'd be updated once in a while to the latest bundix
<ekleog>
now, forcing things to be written in C++/rust is unfortunate, OTOH, and would likely kill such attempts anyway
<samueldr>
nixos:trunk-combined, Too many heap sections: Increase MAXHINCR or MAX_HEAP_SECTS ~ 14:27 UTC
averell has quit [Excess Flood]
averell has joined #nixos-dev
das_j has quit [Quit: "Bye!";]
pie_ has quit [Ping timeout: 244 seconds]
das_j has joined #nixos-dev
tilpner has quit [Quit: WeeChat 2.4]
<gchristensen>
I propose we give flokli merge rights
<gchristensen>
oh he already has it (thought he didn't)
<andi->
hu? I think that has been the case since february
<andi->
or longer
<samueldr>
I guess no one objects then :)
<gchristensen>
:P
<flokli>
:-D
<flokli>
thanks for the reassurement, I guess ;-)
pie_ has joined #nixos-dev
pie_ has quit [Remote host closed the connection]
pie_ has joined #nixos-dev
pie_ has quit [Remote host closed the connection]
pie_ has joined #nixos-dev
alp has quit [Ping timeout: 259 seconds]
Amarandus has quit [Remote host closed the connection]
Synthetica has quit [Quit: Connection closed for inactivity]