* ekleog
thinks updating stable rustc in stable release wouldn't break anything and thus could be done, but… backporting guidelines :p
<sphalerite>
mumble mumble rules guidelines
<ekleog>
(just in case it isn't clear, here I'm grumbling about guidelines not being clear yet :p but I've poked people more than often enough about it, they'll end up hating me ^^)
<ekleog>
andi-: just curious, did you receive this by mail? I'm theoretically subscribed to this ML but didn't receive anything, and it appears to be from > 1 week ago?
<andi->
ekleog: I stumbled upon it while waking up and reading through my RSS feeds ;-)
<andi->
I also saw another update recently that isn't on that list at all.. :/
<ekleog>
oh 'k :) it's weird that the list doesn't appear to actually work :/
<andi->
anyway I'll try to see if 1.29.1 does cause havoc and then I'll probably be out of time for the day
<ekleog>
:D
<ekleog>
andi-++
<{^_^}>
andi-'s karma got increased to 6
<andi->
ekleog: the patch for older stable versions is trivial in this case. I am not sure how it will be with other releases. Do you have experience with that? How much support do old releases receive?
<gchristensen>
some change about rust & nixpkgs changed all the binaries rust created
<gchristensen>
changed the names*
<gchristensen>
this is part of what being in stable means, not breaking stuff really bad like that
<andi->
gchristensen: do you mean recently on master?
<gchristensen>
between 17.09 and 18.03 programs which were foo-bar named became foo_bar named, or visa-versa
<andi->
ahh, I recently changed buildRustCrate (on unstable only) to be in line with what cargo seems to do..
<andi->
Since the old heuristics didn't fit the way cargo works..
<gchristensen>
ah so that might've been our fault? :P
<andi->
it probably was.. I wasn't able to build my nix sec tooling due to some binaries in some crates depending on (older & newer) cargo defaults..
<gchristensen>
ok, then cool
<andi->
In the long run we should rewrite carnix to just use cargo as a lib..
<andi->
There seems to be some interest in the topic.. It recently was discussed in #nixos-de
<gchristensen>
very cool
<andi->
Yeah, it is just that I do not think much will happen besides talk :(
<andi->
Depressing
<gchristensen>
one day, when it is more important to someone
<andi->
apparently ther is already a rust bump to 1.29.0 in the staging branch. The bad thing is that staging hasn't been built since people started to focus on 18.09. So I can drop the bump in 18.09 staging (and backport to 18.03) but leaving unstable/master in an outdated state or I might make people angry about not following the workflow :/
<gchristensen>
andi-: we can change priorities for a bit
<gchristensen>
andi-: no need to be :/, we can find a thing that works :)
<gchristensen>
we're not so mired in process to make this untenable
<gchristensen>
you could even put it in your commit message why you're skipping process
<samueldr>
if the update is already in staging, why wouldn't it be right to backport to 18.03 / 18.09? unless it's expected to break things?
<samueldr>
(to their respective staging branches)
<gchristensen>
yeah! true!
<andi->
Argh, will answer in a few.. Desktops drive finally gave up and I am reinstalling.. EFI behaves strangely.. Grml grml
<samueldr>
grml may help, but why not just the nixos iso?
<andi->
samueldr: I know that one ;-) Why not nixos iso? I try to NEVER use removeable media.. So I am fixing my local netboot first..
<samueldr>
and andi- willingly ignores the joke :)
<gchristensen>
ack
<andi->
back to topic: I didn't check if anything breaks regarding 1.29.x yet so that Is why I was hoping the 1.29.0 upgrade from staging to be done/built already. I am running that rebuild now it will take some time. Blindly porting it to 18.09 thus doesn't sound like a good way. Patching 1.27.1 from 18.03 might be the easier task for now - as that really just changes a line and rebuilds a lot of stuff.