Sigyn has quit [Quit: People always have such a hard time believing that robots could do bad things.]
Sigyn has joined #nixos-dev
ajs124 has joined #nixos-dev
ajs124 has left #nixos-dev [#nixos-dev]
ajs124 has joined #nixos-dev
ajs124 has left #nixos-dev [#nixos-dev]
ajs124 has joined #nixos-dev
ajs124 has left #nixos-dev [#nixos-dev]
ajs124 has joined #nixos-dev
ajs124 has left #nixos-dev [#nixos-dev]
Sigyn has left #nixos-dev ["Highly illogical"]
Zer000 has joined #nixos-dev
init_6 has quit []
ma27 has quit [Remote host closed the connection]
ma27 has joined #nixos-dev
andi- has quit [Ping timeout: 258 seconds]
johanot has quit [Quit: WeeChat 2.4]
andi- has joined #nixos-dev
andi- has quit [Excess Flood]
andi- has joined #nixos-dev
andi- has quit [Ping timeout: 268 seconds]
drakonis1 has joined #nixos-dev
andi- has joined #nixos-dev
andi- has quit [Ping timeout: 250 seconds]
phreedom has quit [Remote host closed the connection]
phreedom_ has joined #nixos-dev
andi- has joined #nixos-dev
<genesis>
is there a way to add option like --prefix PATH : ${gettext}/bin with wrapGAppsHook ?
<genesis>
gappsWrapperArgs ; hard to find :/
<srhb>
genesis: You may want to pose these questions to #nixos which is higher traffic, and intended for use for development as well, just not wide-ranging project-wide discussions as this channel is. :)
<genesis>
srhb : i tried two time, and btw domenkozar is here i wonder if he stills interesting about maintain poedit
<genesis>
i've finished the update.
<genesis>
seems only one derivation based on wxGTK29 :)
andi- has quit [Ping timeout: 255 seconds]
MichaelRaskin has joined #nixos-dev
andi- has joined #nixos-dev
ajs124 has joined #nixos-dev
lassulus has quit [Ping timeout: 245 seconds]
lassulus_ has joined #nixos-dev
lassulus_ is now known as lassulus
drakonis has quit [Quit: WeeChat 2.3]
drakonis1 is now known as drakonis
<infinisil>
Hey, #57656 wants to add a patch to patchelf for fixing an issue. The patchelf we use in nixpkgs is apparently ancient, there hasn't been a release in over 3 years. What do you think about this? Specificall the discussion in the PR
<samueldr>
the good thing with your good implementation is that it's all self-contained; so it's not a dealbreaker for usage with 19.03 to use it out-of-tree
<samueldr>
which also makes me say: holding off will only affect discoverability for 6 months
<samueldr>
(users which want to use it for 19.03 can do it trivially AFAICT)
<gchristensen>
IMO its up to the RMs
<samueldr>
and it is
<niksnut>
I'm not against it
<samueldr>
new feature: -1, tests +1, we're at zero, self-contained, with no global effects without actively using it, +1, I think it's good
<infinisil>
niksnut: samueldr: Nice, a patchelf release would be awesome :)
orivej has quit [Ping timeout: 255 seconds]
<aszlig>
okay, then last chance for opposition, otherwise i'll merge tonight =)
<samueldr>
and as far as RM vote, +1 from me, 0 from sphalerite, BDFL (is he?) niksnut "not -1" I think it'll be right
<aszlig>
k, i'll merge as soon as i'm properly awake, thanks for the input :-)
<gchristensen>
niksnut: ^ if you grep this channel's log for "nixos:.*OOM" you'll find several reports like this from samueldr
<samueldr>
(and note that both problems probably are individual and require different care)
<samueldr>
I've been keeping the eval logs when re-queuing evals just in case, hydra doesn't show failed evaluation logs, if it keeps them, once re-queued
<samueldr>
(does it even keep logs from evals that aren't the latest?)
<infinisil>
gchristensen: Do you know what happened with evaluation in #57315?
<samueldr>
niksnut: do you want someone to do the PR+update in nixpkgs, and on the patchelf web page?
<gchristensen>
infinisil: if failing to publish logs in this one case is the only regression in the massive refactor I did, I will be delighted.
<niksnut>
I've updated the webpage
<infinisil>
niksnut: Nice! One thing missing yet is a GitHub release
<samueldr>
pushing the tag would implicitly make one
<niksnut>
done
jtojnar has joined #nixos-dev
<infinisil>
niksnut++
<{^_^}>
niksnut's karma got increased to 4
<gchristensen>
infinisil: {^_^} might should have a carve-out on niksnut's karma
<infinisil>
samueldr: Want to make the patchelf update PR?
<flokli>
thanks niksnut :-)
<gchristensen>
niksnut++
<{^_^}>
niksnut's karma got increased to 5
<flokli>
niksnut++
<{^_^}>
niksnut's karma got increased to 6
<flokli>
the patchelf bump PR could probably also point patchelfUnstable to patchelf, and change derivations currently using patchelfUnstable to use patchelf
<samueldr>
would it be a bad end-user experience for zfs to be in the LTS installers, but not part of the new kernel installers?
<samueldr>
this, in turn, makes it a less reliable resource when users are faced with extremely new hardware that has issues with the LTS
<samueldr>
and in aarch64 land, sd images (and isos) with the latest kernels should probably always be kept green, as hardware support is always improving, sometimes making the difference between works and not
<samueldr>
sphalerite: ^ opinions?
<samueldr>
to reiterate: the idea would be to keep the zfs supported filesystem only for the main release, which has the latest LTS kernel, while on new_kernel (which are using _latest) zfs wouldn't be supported