drakonis_ has quit [Remote host closed the connection]
lezed1 has joined #nixos-dev
orivej has quit [Ping timeout: 240 seconds]
orivej has joined #nixos-dev
ckauhaus has joined #nixos-dev
orivej has quit [Ping timeout: 252 seconds]
Mic92_ has joined #nixos-dev
Mic92 has quit [Ping timeout: 264 seconds]
domenkozar has quit [Ping timeout: 268 seconds]
ckauhaus is now known as ckauhaus[away]
pie_ has quit [Ping timeout: 240 seconds]
jtojnar has quit [Ping timeout: 245 seconds]
jtojnar has joined #nixos-dev
<lezed1>
I'm trying to package a daemon that written in Python. I have the executable working when I test in a `nix-shell`, but as soon as I install the package globally, I can no longer run the Python script without encountering errors about imports failing.
<lezed1>
I'm sure there is a proper way to package a python file for global install, I just can't seem to figure it out
__Sander__ has joined #nixos-dev
<srhb>
Is there no prioritization going on for trunk-combined over eg. staging? This evaluation has a successful tested job, but the last jobs have been queued for days: https://hydra.nixos.org/eval/1475822#tabs-unfinished
lassulus_ has joined #nixos-dev
lassulus has quit [Ping timeout: 252 seconds]
lassulus_ is now known as lassulus
lassulus_ has joined #nixos-dev
lassulus has quit [Ping timeout: 246 seconds]
lassulus_ is now known as lassulus
lassulus has quit [Ping timeout: 246 seconds]
lassulus has joined #nixos-dev
lassulus has quit [Ping timeout: 260 seconds]
<gchristensen>
srhb: it is quite possible somebody (with a good reason) prioritized another jobset's jobs first
<gchristensen>
lezed1: #nixos :)
<gchristensen>
#nixos-dev isn't for packaging problems, if you can believe it :)
<srhb>
gchristensen: It just seems like something weird is going on, the entire queue has been mostly empty a few times except for those. Oh well. :)
init_6 has joined #nixos-dev
lassulus_ has joined #nixos-dev
lassulus_ is now known as lassulus
init_6 has quit [Ping timeout: 252 seconds]
init_6 has joined #nixos-dev
orivej has joined #nixos-dev
<samueldr>
hi devs! announcing here too that the branch-off will be no later than 20:00 UTC on september 2
<andi->
\o/
<gchristensen>
time to sneak in all my packages
<gchristensen>
samueldr++
<{^_^}>
samueldr's karma got increased to 16
<samueldr>
no
<samueldr>
thas was a month ago
<gchristensen>
:)
<gchristensen>
I kid.
<gchristensen>
samueldr: can we bump requirements from 1.11 to 2.0?
<LnL>
ah btw, re:nix 2.0 doesn't evaluation of the fallback paths still work even if the language version is bumped?
<srhb>
18.03 already only evaluates with the latest 1.11 versions, not all of them.
<srhb>
(So it makes sense)
<gchristensen>
what does that mean, LnL?
<Dezgeg>
at least the fallback paths used to be hardcoded in bash code
<LnL>
that you can upgrade 1.11 to 2.1 even if you can't evaluate nixpkgs anymore
<gchristensen>
oh in the "your nix is too old" warning
<samueldr>
I haven't really explored the functionalities yet of nix-review, first used it yesterday, and as you could see in my bug report, an outdated version!
<samueldr>
(0.3 vs. 0.5)
<Mic92_>
I think we still have 0.3 in stable?
<Mic92_>
I guess I could backport updates after a while from master.
<samueldr>
I would guess so
<Mic92_>
I use nix-review every day, so it is properly tested.
<Mic92_>
checking previously broken packages on hydra would also help a lot.
<Mic92_>
also blacklisting packages would be helpful.
<Mic92_>
like chromium
<manveru>
seems like asciidoctor fails to build for some reason
<Mic92_>
asciidoctor should better not break
<manveru>
:)
<Mic92_>
either upgrading it or downgrading ruby I would say
<manveru>
we can always pass it the older ruby version
<manveru>
but i think we can also upgrade its gems
<gchristensen>
there is only the security announce list, which we could remove until it is active again
<Mic92_>
would a nixos-weekly style repo work for security too?
<Mic92_>
maybe a security-daily with automation.
<gchristensen>
it is a whole lot of work and we probably shouldn't try to talk about it casually
<gchristensen>
we should talk about it, but not as a tangent to another conversation
<gchristensen>
OfBorg will be undergoing some maintenance very soon and may have a bit of down-time. If you notice problems, please drop by #nixos-borg. Some are to be expected, but please be proactive in reporting them.
ciil has quit [Quit: Lost terminal]
<gchristensen>
Most of the OfBorg infrastruture is now updated. I'm now begining the upgrade procedure for the core of the infrastructure. New messages to ofborg will be lost while it is down. It should only take a few minutes. https://butt.holdings
<gchristensen>
Due to an upstream provider issue, the final piece of maintenance won't be performed today. We're done with today's maintenance and everything should be okay.
drakonis_ has joined #nixos-dev
FRidh has joined #nixos-dev
ckauhaus has quit [Quit: WeeChat 2.0]
pie_ has quit [Ping timeout: 244 seconds]
drakonis_ has quit [Remote host closed the connection]
drakonis_ has joined #nixos-dev
zack_moe_ has joined #nixos-dev
__Sander__ has quit [Quit: Konversation terminated!]
symphorien has joined #nixos-dev
<symphorien>
hello, it is possible to have some opinions on this issue: https://github.com/NixOS/nixpkgs/issues/44465 ? It is easy to solve but needs some "policy decision" about breaking sh256 hashes
<{^_^}>
#44465 (by erictapen, 3 weeks ago, open): buildRustpackage: failed to load source for a dependency on $x
<infinisil>
jtojnar: Holy batman, that section couldn't be less fit for beginners
<jtojnar>
we could still translate it to lojban
<infinisil>
Haha
<infinisil>
Also I didn't know myself there now are 12 (!) ways to specify dependencies..
<infinisil>
Oh and not to mention that those won't always work for runtime deps
<Dezgeg>
yes it's completely nuts, all those cases which are needed in like, <1% of cases should be removed from stdenv and an alternative way figured out
pie_ has joined #nixos-dev
<aminechikhaoui>
wow I was just going to rant about that :D
<Dezgeg>
a really good side effect of removing most of those from stdenv will be that it will hopefully allow removing the parts of code described as "<domenkozar> it's a 3-level for loop that's indexed by different arrays of integers. it's madness :)"
<gchristensen>
oh dear
<jtojnar>
buildstream, for example, decided to disallow cross-compilation
<jtojnar>
(not that I am advocating for that)
init_6 has quit [Ping timeout: 240 seconds]
<FRidh>
Just reading the part from the manual. The part between "The exact rules ... " and "Variables specifying dependencies" should go in an appendix I think.
<gchristensen>
I like this conversation
<FRidh>
There is clearly frustration caused by existing and proposed changes. Even so, I do think it's good some people are looking into this different. I wonder how much effort it is to have a separate stdenv for cross compilation and keeping it compatible with the main stdenv's.