samueldr changed the topic of #nixos-dev to: #nixos-dev NixOS Development (#nixos for questions) | NixOS 19.09 is released! https://discourse.nixos.org/t/nixos-19-09-release/4306 | https://hydra.nixos.org/jobset/nixos/trunk-combined https://channels.nix.gsc.io/graph.html | https://r13y.com | 19.09 RMs: disasm, sphalerite | https://logs.nix.samueldr.com/nixos-dev
__monty__ has quit [Quit: leaving]
justanotheruser has joined #nixos-dev
<jtojnar> regarding fonts, we might need to switch to cairo master
<jtojnar> there are some hinting issues apparently
<worldofpeace> Jan Tojnar: I believe this is what arch linux has done to "workaround" this.
<worldofpeace> I'd say it'd totally be fine for unstable
<samueldr> this statement scares me: will this change be reverted when cutting the next stable?
<worldofpeace> tbh, cairo needs to get to it and make a release :D
<samueldr> I don't think it's fair to put unfinished/unreleased/unstable stuff in our unstable, our unstable I think means more "software will update from under your feet" than "things will break"
<samueldr> not singling this out, but I've seen the same sentiment recently of feeling it's fine to dump unstable stuff in unstable
<samueldr> unstable is more nextstable than unstable
<worldofpeace> Well, in this case an upgrade to the newest usable version of a package also incurred some changes needed in another, one which hasn't slated a release with those commits. I'm not sure which commits in cairo we could backport, but that would be probably better than updating to an unreleased version. I think I agree in unstable, users will see maintainers updating their packages to the newest usable versions, but
<worldofpeace> causing things to break on purpose isn't great like you said. But at the same time we're using unstable to identify bugs and issues before they reach users in a stable release. So in same cases, if the releases line up, I think it would be appropriate to update to a released development version.
<worldofpeace> We probably need docs on "What the development version of NixOS, nixos-unstable, is and isn't"
<samueldr> anyone handy with perl? trying to fix a cross-compilation issue the right way and it's not making sense
<samueldr> Undefined subroutine &File::Temp::mktemp called at inc/Devel/CheckLib.pm line 236.
<samueldr> which is baffling me since https://perldoc.perl.org/File/Temp.html#MKTEMP-FUNCTIONS
orivej has quit [Ping timeout: 276 seconds]
<samueldr> and funnily enough the only reason it cross-compiled (seemingly) successfully beforehand is because the failure condition was ignored
das_j has quit [Remote host closed the connection]
Scriptkiddi has quit [Remote host closed the connection]
das_j has joined #nixos-dev
Scriptkiddi has joined #nixos-dev
<samueldr> furthering my confusion, it seems to only happen with the perl used for cross-compilation
<samueldr> #75132 is a work-around, with a full explanation of the situation, if you have a better solution it's obviously going to be better than patching the check out
<{^_^}> https://github.com/NixOS/nixpkgs/pull/75132 (by samueldr, 1 minute ago, open): perlPackages.XMLParser: Work around cross-compilation regression
<samueldr> btw, just saying that I hate the workaround, it's ugly...
<samueldr> though I think the checking code is... way more worse
phreedom has joined #nixos-dev
phreedom has quit [Ping timeout: 260 seconds]
phreedom has joined #nixos-dev
phreedom has quit [Ping timeout: 260 seconds]
phreedom has joined #nixos-dev
orivej has joined #nixos-dev
<{^_^}> firing: RootPartitionLowDiskSpace: https://status.nixos.org/prometheus/alerts
<{^_^}> resolved: RootPartitionLowDiskSpace: https://status.nixos.org/prometheus/alerts
roberth has quit [Quit: killed]
nh2[m] has quit [Quit: killed]
abbradar[m] has quit [Quit: killed]
timokau[m] has quit [Quit: killed]
dtz has quit [Quit: killed]
bennofs[m] has quit [Quit: killed]
aanderse has quit [Quit: killed]
worldofpeace has quit [Quit: killed]
Nyanloutre[m] has quit [Quit: killed]
Ox4A6F has quit [Quit: killed]
ma27[m] has quit [Quit: killed]
arcnmx has quit [Quit: killed]
atopuzov[m] has quit [Quit: killed]
jtojnar has quit [Quit: killed]
thefloweringash has quit [Quit: killed]
alienpirate5 has quit [Quit: killed]
rycee has quit [Quit: killed]
rnhmjoj has quit [Quit: killed]
jonge[m] has quit [Read error: Connection reset by peer]
Ox4A6F has joined #nixos-dev
<fpletz> somebody around to verify that the firefox 71 bump breaks indexedDB? since the bump was already backported to 19.09 we should revert asap
<srhb> fpletz: I can check. How to reproduce? Just build release-19.09 version and try to change settings?
<fpletz> srhb: try with 0322870203ccdb671701cfd69b1c369be1333d37, that is on 19.09 and has already been built on hydra
<srhb> On it :)
<fpletz> I had problems with stylish but many extensions should have problems
<srhb> multi account containers seem to work. Trying stylish
<fpletz> also if you use riot (matrix) in firefox, that should also be broken
<srhb> riot seems to work..
<srhb> "JavaScript error: resource://services-common/kinto-offline-client.js, line 603: Error: IndexedDB list() The operation failed for reasons unrelated to the database itself and not covered by any other error code."
<srhb> But I can't seem to find any misbehaviour in the UI, and things seem to work just fine.
<fpletz> in riot, for instance encrypted channels can't be viewed because the crypto keys can't be fetched
<srhb> OK, think I can confirm the bug. I am unable to alter the lock time in my bitwarden extension
<srhb> It just revers silently
<gchristensen> adisbladis: join -borg? :)
<srhb> fpletz: Revert sounds prudent :)
<fpletz> srhb: yup, that's the issue, thanks!
<srhb> Sure thing!
orivej has quit [Ping timeout: 250 seconds]
* gchristensen pokes adisbladis
Ericson2314 has joined #nixos-dev
abbradar[m] has joined #nixos-dev
aanderse has joined #nixos-dev
alienpirate5 has joined #nixos-dev
arcnmx has joined #nixos-dev
atopuzov[m] has joined #nixos-dev
bennofs[m] has joined #nixos-dev
domenkozar[m] has joined #nixos-dev
dtz has joined #nixos-dev
jonge[m] has joined #nixos-dev
roberth has joined #nixos-dev
rnhmjoj has joined #nixos-dev
nh2[m] has joined #nixos-dev
jtojnar has joined #nixos-dev
Nyanloutre[m] has joined #nixos-dev
layus[m] has joined #nixos-dev
ma27[m] has joined #nixos-dev
rycee has joined #nixos-dev
timokau[m] has joined #nixos-dev
thefloweringash has joined #nixos-dev
vaibhavsagar has joined #nixos-dev
yegortimoshenko has joined #nixos-dev
worldofpeace has joined #nixos-dev
<adisbladis> gchristensen: Joined :)
obadz has quit [Quit: WeeChat 2.6]
obadz has joined #nixos-dev
NinjaTrappeur has quit [Quit: WeeChat 2.6]
NinjaTrappeur has joined #nixos-dev
janneke_ has joined #nixos-dev
janneke has quit [Ping timeout: 252 seconds]
prusnak has joined #nixos-dev
ryantm has quit [Ping timeout: 276 seconds]
ryantm has joined #nixos-dev
cbarrett has quit []
cbarrett has joined #nixos-dev
orivej has joined #nixos-dev
justanotheruser has quit [Ping timeout: 276 seconds]
justanotheruser has joined #nixos-dev
<andi-> srhb: fpletz: did you create an issue?
<fpletz> andi-: I have a patch :> https://github.com/NixOS/nixpkgs/pull/75169
<{^_^}> #75169 (by fpletz, 1 hour ago, open): firefox: fix indexedDB for 71.0
<andi-> fpletz: nice, that really looks like a compiler bug o.O
<fpletz> andi-: I'm not sure if both changes to dom/localstorage/ActorsParent.cpp are needed, I just search for ternary operator usage that looked suspicious
<fpletz> that fixes the issue, though, and shouldn't change any behaviour (other than what the broken compilers produce of course :>)
<fpletz> seems like only clang7+ works at the momemt, and that behaviour seems to be only a recent addition to the standard (2017)... not a good idea for firefox to rely on that so soon I guess
<{^_^}> firing: ChannelUpdateStuck: https://status.nixos.org/prometheus/alerts
<{^_^}> resolved: ChannelUpdateStuck: https://status.nixos.org/prometheus/alerts
<{^_^}> nixos-channel-scripts#28 (by grahamc, 3 weeks ago, merged): mirror-nixos-branch.pl: exit 0 if the channel would go back in time
<andi-> fpletz: interesting, I know that they are at least compiling with GCC as well was with Clang (last time I checked). I was thinking of moving the derivation to clang a while ago since then we could use plto IIRC
justan0theruser has joined #nixos-dev
justanotheruser has quit [Ping timeout: 250 seconds]
prusnak has quit [Quit: Connection closed for inactivity]
<{^_^}> firing: ChannelUpdateStuck: https://status.nixos.org/prometheus/alerts
<gchristensen> oh the deploy failed.
justan0theruser is now known as justanotheruser
prusnak has joined #nixos-dev