mbrgm has quit [Ping timeout: 248 seconds]
mbrgm has joined #nixos-dev
aminechikhaoui has quit [Read error: Connection reset by peer]
aminechikhaoui has joined #nixos-dev
stqism has quit [Quit: Like 3 fire emojis lit rn 🔥🔥🔥]
stqism has joined #nixos-dev
stqism has quit [Client Quit]
stqism has joined #nixos-dev
stqism has quit [Client Quit]
stqism has joined #nixos-dev
stqism has quit [Client Quit]
pie___ has quit [Ping timeout: 248 seconds]
stqism has joined #nixos-dev
stqism has quit [Quit: Like 3 fire emojis lit rn 🔥🔥🔥]
stqism has joined #nixos-dev
stqism has quit [Client Quit]
stqism has joined #nixos-dev
mbrgm has quit [Ping timeout: 248 seconds]
mbrgm has joined #nixos-dev
<adisbladis[m]> dtz: I'm very hopeful to use it for containers in the future :)
JosW has joined #nixos-dev
aminechikhaoui has quit [Ping timeout: 240 seconds]
pie___ has joined #nixos-dev
aminechikhaoui has joined #nixos-dev
<Profpatsch> What’s the best workflow to do backports?
<Profpatsch> Create a PR against the stable branches?
yegortimoshenko has quit [Ping timeout: 255 seconds]
yegortimoshenko has joined #nixos-dev
<sphalerite> gchristensen: Oracle, in a strange and extremely uncharacteristic but welcome move, have decided they'll finally accept the GPLv2 and dtrace can be mainlined in linux
vcunat has joined #nixos-dev
vcunat has quit [Client Quit]
vcunat has joined #nixos-dev
yegortimoshenko has quit [Remote host closed the connection]
yegortimoshenko has joined #nixos-dev
ma27 has joined #nixos-dev
ma271 has joined #nixos-dev
ma27 has quit [Remote host closed the connection]
vcunat has quit [Quit: Leaving.]
orivej has joined #nixos-dev
jtojnar has quit [Ping timeout: 256 seconds]
ma271 has quit [Ping timeout: 276 seconds]
ma272 has joined #nixos-dev
orivej has quit [Ping timeout: 276 seconds]
<gchristensen> Whoa
pie___ has quit [Ping timeout: 255 seconds]
jtojnar has joined #nixos-dev
taktoa has joined #nixos-dev
jtojnar has quit [Quit: jtojnar]
jtojnar has joined #nixos-dev
<shlevy> zfs next?
jtojnar has quit [Quit: jtojnar]
jtojnar has joined #nixos-dev
<shlevy> Are we planning on getting gcc 7.3 in 18.03?
<shlevy> Would be nice to have the full spectre variant 2 fix
<Dezgeg> wouldn't that be also accomplished by compiling just the relevant packages (JITs, etc.) with GCC 7 or do I remember wrong?
<Dezgeg> anyway here's the tracking ticket: https://github.com/NixOS/nixpkgs/issues/31747
<shlevy> Dezgeg: Sure but it's a pain and opt-in
<shlevy> Thanks for the link
<niksnut> tbh I think we should just merge the gcc-7 branch
<shlevy> \o/
<niksnut> only way to get people to fix build problems...
<shlevy> :shipit"
<shlevy> I'll let you do it though :D
<niksnut> nah, it's up to the release managers
<Dezgeg> let's get the systemd upgrade to master first though :)
<shlevy> Who's the release manager this round?
<sphalerite_> shlevy: GPL zfs would be amazing
orivej has joined #nixos-dev
goibhniu1 is now known as goibhniu
orivej has quit [Ping timeout: 248 seconds]
pie___ has joined #nixos-dev
<sphalerite_> gchristensen (and anyone else): would building one rust package (say, ripgrep) with ofborg for https://github.com/NixOS/nixpkgs/pull/34968 make sense?
pie__ has joined #nixos-dev
<sphalerite_> or should it just be merged into staging and see from there?
pie___ has quit [Ping timeout: 240 seconds]
<gchristensen> Go for it
pie___ has joined #nixos-dev
pie__ has quit [Ping timeout: 240 seconds]
<LnL> if that rebuilds rustc it will probably timeout
pie___ has quit [Ping timeout: 248 seconds]
<gchristensen> true
<gchristensen> I've been reading up on a research paper about a scheduling algo called TAGS for handling variable duration builds
<gchristensen> to support long builds without hampering short builds
<gchristensen> the gist of it is if a build times out, punt it to a queue which supports longer builds
<LnL> interesting, do you have a link?
* gchristensen scrounges
<gchristensen> short and pretty readable
<LnL> cool, the project I work on is loosely related to ofborg in certain aspects :)
<gchristensen> nice! :D:
<gchristensen> we'll talk more later. gotta go
Lisanna has quit [Quit: Lisanna]
jtojnar has quit [Quit: jtojnar]
Lisanna has joined #nixos-dev
pie_ has joined #nixos-dev
zarel has joined #nixos-dev
orivej has joined #nixos-dev
contrapumpkin has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
jtojnar has joined #nixos-dev
ma272 has quit [Ping timeout: 276 seconds]
ma272 has joined #nixos-dev
taktoa has quit [Remote host closed the connection]
JosW has quit [Quit: Konversation terminated!]
zarel has quit [Quit: Leaving]
vcunat has joined #nixos-dev
<vcunat> LnL: this room?
<LnL> hi
<vcunat> It's close to midnight here, but I can be here for a while.
<LnL> same here :)
<LnL> so I have a fix for pysqlite
<vcunat> Riht, still very few nix* devs are outside Europe.
<LnL> what do you want to do, merge staging^ and apply the fixes to master?
<vcunat> x86_64-linux diff looks good
<vcunat> aarch64-linux as well, except for 3.3k queued jobs
<vcunat> darwin... hard to say if some other error is hiding among those pysqlite failures
<gchristensen> the UScentric nix devs are growing!
<vcunat> Is that your doing?
<LnL> there are some new failures because of the clang update, but nothing major
<vcunat> I truste aarch64 will be OK.
<gchristensen> I don't know if it is mine
<vcunat> For darwin, it can't be worse than ~2.7k failures.
<vcunat> LnL: if you trust it will be bearable to handle Darwin on master, we can e.g. wait till morning for better aarch64 confidence and merge then.
<vcunat> bearable in terms of errors
<vcunat> 2.7k darwin builds will probably be cleared by Hydra in one day.
<vcunat> (and master has preference before the other mass rebuilds running now)
<LnL> yeah, I think it will be ok if the builders are healthy
<vcunat> Actually, will the fix cause many rebuilds on other platforms?
<vcunat> Maybe we could temporarily conditionalize it if it's many.
<LnL> ah right, didn't look at that
<vcunat> Is it in a branch already, or will you check the rebuiluds?
<LnL> checking, think I'll have remove some of my cleanup
<LnL> that only rebuilds for darwin
<vcunat> confirmed
<LnL> the pkgconfig weirdness wasn't the problem aparently
<vcunat> I'll re-check aarch64 status in the morning and (most likely) merge this.
<vcunat> That's weird.
<vcunat> So all that is still in the log?
<LnL> yeah, but we add -L flags so it still finds sqlite
<vcunat> Oh, it's in log even on Linux :-D
<vcunat> Well, those flags aren't blockers, but would better be fixed later.
<LnL> yeah, I can push my cleanup to staging after
<vcunat> Well, you can merge all this to staging now.
<vcunat> It was just master I was concerned about.
<LnL> but there's another rebuild on staging now
<vcunat> yes
<vcunat> I plan to merge #35021 to master directly in any case to avoid that rebuild.
<vcunat> But that doesn't conflict with also merging stuff to staging.
<LnL> oh you're talking about the cleanup?
<vcunat> Yes, I assume the cleanup will depend on this commit (to avoid conflicts) and go to staging.
<Dezgeg> I would just merge the almost-built one (79e7f7a) now before it gets further out of sync with master :)
<LnL> yeah, that's the plan
<vcunat> 2b851d14d9f directly, instead of the parent
<vcunat> (i.e. PR #35021)
<vcunat> Though I'm not sure what you mean by "out of sync".
<Dezgeg> well the staging commit that's built in staging is already like, 10 hours old
<vcunat> That doesn't feel very long to me :-)
pie__ has joined #nixos-dev
pie_ has quit [Ping timeout: 268 seconds]
ma272 has quit [Ping timeout: 276 seconds]
<vcunat> Maybe I'm just too old comparatively.
ma272 has joined #nixos-dev