<thoughtpolice>
Ugh. I think I've asked this before but, if I want to change the version scheme of a package (I didn't choose the original one), but e.g. lib.versionLessThan is invalid for the new scheme -- is there anyway to fix this? IIRC the issue is something like 'nix-env -u' won't properly upgrade when it thinks the new build is "less than" the old one
<thoughtpolice>
Or is it just stuck that way forever
<thoughtpolice>
Namely, I want to change something like "2018.08.08" to "0.8pre<revCount>_<sha256>", closer to the traditional scheme we use
* samueldr
has epochs in mind, but that might be an archlinux thing
<samueldr>
not unix epoch, but something that was used to fix that issue
matthewbauer has joined #nixos-dev
<matthewbauer>
anyone willing to merge staging into master?
<{^_^}>
#45042 (by kirelagin, 6 weeks ago, open): dyld: Symbol not found: ___CFObjCIsCollectable
<domenkozar>
is impure security the way to go? :)
<LnL>
I don't know much about the libsecurity packages
<LnL>
but using the Security framework is fine if we can't update and it also works on older versions
goibhniu has quit [Ping timeout: 252 seconds]
<Mic92>
LnL: I will upgrade alacritty also on master based on my own fork, so we can have this version in 18.09 as well - This will be a simple merge conflict when merging staging -> master.
<samueldr>
yeah, the issue is still open for comment if anyone has reasons *not* to go forward with parted
<samueldr>
(my experience is limited in the area, I always use cfdisk to partition)
jtojnar has quit [Remote host closed the connection]
init_6 has quit []
goibhniu has quit [Ping timeout: 252 seconds]
sir_guy_carleton has quit [Quit: WeeChat 2.0]
<Mic92>
one more pr for hacktoberfest
<Mic92>
well, I have not even upstreamed the nixpkgs stuff I did for my server.
sir_guy_carleton has joined #nixos-dev
<ekleog>
zimbatm: can we re-enable the issues on the RFCs repository? I think having a way to host discussions on pre-RFCs (like Rust) would help, as writing a RFC just to host a discussion isn't really convenient :)
<zimbatm>
how about posting them on discourse instead?
<zimbatm>
I agree that the RFC discussion is a bit unwieldy
<zimbatm>
I've been ready the one about GPG signing for 30min now
<ekleog>
well, I'm thinking about splitting current RFC discussion, and was thinking it'd make sense to keep it into the RFC repository to minimize the context switchs people have
<gchristensen>
those comments are _so_ long :P
* ekleog
pleads guilty
<ekleog>
anyway… time to sleep here, will let you decide on whether to turn on issues, add a pre-RFC section to discourse, do nothing or anything else :)
<ekleog>
'night!
<{^_^}>
Night!
jtojnar has joined #nixos-dev
sir_guy_carleton has quit [Quit: WeeChat 2.0]
jtojnar has quit [Remote host closed the connection]
sir_guy_carleton has joined #nixos-dev
<zimbatm>
I don't have admin on the repo so that solves the question :p