<aanderse>
anyone get blurays playing on nixos (or linux in general?)
<aanderse>
ah...
<aanderse>
gchristensen
* aanderse
waves
<aanderse>
wb
<infinisil>
aanderse: I have ripped blurays before with makemkv
<aanderse>
infinisil: ever tried with kodi?
<infinisil>
Nope
<aanderse>
makemkv much work?
<infinisil>
Yup, works pretty well, I did buy a license even
<infinisil>
Because of bluray being bluray, I'm not sure if a libre and gratis version can even exist
drakonis has joined #nixos-dev
<aanderse>
well vlc doesn't want to play blurays
<aanderse>
"This Blu-ray Disc needs a library for ACCS decoding, and your system does not have it."
<aanderse>
and that was after adding libaacs + libbdplus to the buildInputs of vlc
<clever>
aanderse: check the build log to see if configure actually enabled it
<clever>
`nix log /nix/store/qjz3c2pnzpyiki9vaas6q2gh7bvg8hs3-vlc-3.0.6` with a random build from unstable reveals: checking for libbluray >= 0.6.2... yes
<clever>
CC access/liblibbluray_plugin_la-bluray.lo
<aanderse>
clever: from what i'm reading i need libbluray, libaacs, and libbdplus
<clever>
at least on my version, it appears to be compiling something bluray based
<clever>
aacs and bdplus dont appear in my build logs
<aanderse>
yeah they aren't in the nixpkgs build
<clever>
`nix edit nixpkgs.vlc` reveals fairly few --enable flags, so i would guess that most just auto-enable, based on finding deps
<clever>
81 # Most of the libraries are auto-detected so we don't need to set a bunch of
<clever>
a comment even confirms that
<aanderse>
mhm, which makes me wonder why adding to buildInputs is not making it work
<clever>
i dont see the configure script making any attempt to search for it
<clever>
which makes me wonder, maybe libbluray is what needs it?
<ivan>
yorick: I thought about what might satisfy nixpkgs, which might be a patch from a systemd PR that isn't closed, which would probably have to be a rethinking of how systemd uses 256-color codes, and there's another one of those (gray) that probably has to be dealt with
<ivan>
there's a guy contributing to systemd adding this stuff and I don't want to engage and become a systemd developer
<ivan>
in conclusion someone else will have to go care while I just rebuild everything in my hydra to fix a yellow color
<qyliss>
I'm not sure such a function should be written in Nix
<qyliss>
What do you plan on reading kernel configs in Nix for?
ris has joined #nixos-dev
psyanticy has quit [Quit: Connection closed for inactivity]
phreedom has quit [Ping timeout: 260 seconds]
<samueldr>
nixos has a few checks
<samueldr>
nixos/modules/system/boot/kernel.nix
phreedom has joined #nixos-dev
<samueldr>
though I think it's all internal~ish, system.requiredKernelConfig is where the checks end up
<qyliss>
Could we accomplish the same goal by removing the ability to set raw string kernel config?
<qyliss>
It feels a bit backward to be parsing config rather than generating it
<samueldr>
I'm not 100% sure of what I'll assert, but I think this ends up checking the .config after going through the configure script, meaning that default answers for unsanwered questions are known
<samueldr>
at least, that was my high level understanding at one point
<qyliss>
If we mandate certain things, we could just set them explicitly though?
FRidh has quit [Quit: Konversation terminated!]
<samueldr>
AFAIUI some combinations can disable and hide options form the config step from the kernel, but I'm not too sure about that
<samueldr>
I just know that saying "CONFIG_X_Y_Z=y" is not always enough for it to be enabled :/
<samueldr>
(when done outside the usual nixos config script)
<samueldr>
which makes me think: this would break with a given .config kernel configuration
<samueldr>
which AFAIUI this currently works with
<qyliss>
wait, but how do we read that file from Nix anyway? wouldn't that be IFD?
<qyliss>
Or am I misunderstanding when this runs
<samueldr>
I believe it's an option
<samueldr>
sorry, I'm not confident enough to say more authoratively about those bits :/
<worldofpeace>
TRACKER_VERBOSITY can be used to make it complain louder
<worldofpeace>
ohh, do we need tracker-with-miners package?
* ekleog
would need some way of easily identifying nixpkgs committers, to know when a PR I'm falling on via triage already has someone taking care of it or not
<ekleog>
currently I'm just going to the org team's page, but that's kind of slow
evanjs- has joined #nixos-dev
evanjs- has quit [Client Quit]
<samueldr>
I'll ask here, the message got lost on #nixos; anyone knows the location of the travis-ci setup information? or is that not public?
<samueldr>
though the reason to ask is that it may be useful for someone else than me who I'm lightly helping in automating a nix on non-NixOS setup with salt, and the install script has not been good to them
Synthetica has quit [Quit: Connection closed for inactivity]
evanjs- has joined #nixos-dev
<ivan>
I'm surprised to see we don't have reversePatches :-)
<fpletz>
ivan: fetchpatch has a revert parameter that you can set to true :)
<ivan>
fpletz: oh, awesome, thanks
<jtojnar>
hmm, GitHub’s saved replies are useful for pasting ,libraries, if only the list of replies could be stored in the repo and synced with {^_^}