vae :neocat_flag_nb:<p><span>I've been staring at this for too long and can't understand what I'm doing wrong.. Can someone with more brain halp plz? :3<br></span></p><pre><code> environment.systemPackages = with pkgs;
[
...
]
++ lib.mkIf config.someoption.enable [
...
];</code></pre><span><br>Gives me this:<br></span><pre><code>error: expected a list but found a set: { _type = "if"; condition = «thunk»; content = «thunk»; }</code></pre><span><br>I basically copied this from my old config that I </span><i>know</i><span> used to work (though it had been commented out for a few months, so maybe something's changed?)<br><br>Using latest lix, if that matters.<br><br>(bbl, sleep </span>:neocat_flop_sleep:<span>)<br><br></span><a href="https://theshark-smellslike.sparklef.art/tags/nix" rel="nofollow noopener noreferrer" target="_blank">#nix</a> <a href="https://theshark-smellslike.sparklef.art/tags/NixOS" rel="nofollow noopener noreferrer" target="_blank">#NixOS</a><p></p>
Recent searches
Search options
#nix
14 posts14 participants3 posts today
?
WARNING
Apparently some #Nix / #NixOS matrix room(s) have gotten csam spam. I have not verified this claim myself, but honestly, we can all probably just not check matrix for a few days until hopefully things are back to normal.
I do *not* know what utilities #Matrix provides to prevent the proliferation of this information. If you joined the room from a different home server then your server may have synchronized the material to your infrastructure.
I think the safest course of action is not opening a matrix client for a few days...
> Fedora change aims for 99% package reproducibility
Nice, cool. Let's check 
.
> I often see initiatives and articles like this but no mention of #Nix. [...] Should it [Fedora] adopt an alternate package manager to achieve this with less headache?
Ah, yes.
Fixing your existing package manager is *clearly* more of a headache than changing the entire package manager.
Why are so many devs into Nix?
Ron Efroni shares how the Nix community became one of the most supportive and resilient in open source.
Curious what it’s like to use Nix in production? Check out Nix in the Wild, stories from real teams building with Nix.
How does using the #Jolla #JollaC2 (@jolla) with #SailfishOS for about a week as a daily driver now (with my old #iPhone at home as a backup)?
In general, it works much better than I had hoped after my experiences with other alternative #smartphone systems and it indeed is the first (and so far only) system that indeed works quite well. Also at around 285€ (https://commerce.jolla.com/products/jolla-community-phone) it isn't too expensive, so one can simply try it out.
There are a few limitations though:
* I am really missing biometric unlocking
* There is no predictive text input, so typing could be more comfy
* The UX experience sometimes feels strange (but no no-gos for me)
* It is not a snappy and fast device
* Audio quality is so-so
* GPS really needs a GPS signal, so no WIFI-based location
What is great:
* It is a real #Linux, so it has a #terminal, #sshd, you can e.g. use the #Nix package manager etc.
* Android apps are running in a container
* You can have different users to limit data access
Unfortunately there are nearly no high-quality native apps so far and the built-in ones are very basic (e.g. email).
But: The #Android compatibility layer is very good, the system comes with #Fdroid and #AuroraStore (#Google store front-end) pre-installed, so you can easily install practically all official Android apps.
Most apps work very well, some (especially banking) apps do not though as they complain that the system is rooted, so YMMV regarding the apps you need.
In general I am really happy with this system.
And: All the de-ggoglefied Android phones like the #Volla will always still remain just that: A more limited Android. SailfishOS offers a path towards powerful native (#Qt/#QML/#Cplusplus/#Python/you name it) based apps.
I am hoping that Jolla will provide a significantly more powerful device option and that some of the problems above will be solved.
But already now, even with the limitations above, if you are somewhat technically inclined (but without the need to fiddle with a command line unlike with the open mobile Linux distributions), want to get rid of #Google or #Apple for whatever reason, want a #Linux #smartphone, support a #European company from #Finland, this phone is really usable.
commerce.jolla.comJolla C2 Community Phone
I got curious and tried to configure #NixOS to run the #Nix daemon as a non-root user. It *kinda* worked; the deamon starts up, but fork-bombs the system as soon as you try to do anything: https://github.com/gmacon/nix-daemon-rootless
GitHubGitHub - gmacon/nix-daemon-rootlessContribute to gmacon/nix-daemon-rootless development by creating an account on GitHub.
手動建立 Nix 派生項，無需猜測
➤ 探索 Nix 派生項的底層機制與雜湊生成原理
✤ https://bernsteinbear.com/blog/nix-by-hand/
本文深入探討了 Nix 派生項的建立過程，作者為了理解如何手動生成用於 Nix 派生項的雜湊值，進行了一系列實驗和研究。文章詳細解釋了 Nix 的運作原理，包括派生項的概念、ATerm 格式、雜湊演算法以及 Nix 特有的 base32 編碼方式。作者在使用 Docker 環境中逐步拆解了 Nix 派生項的建構步驟，並透過 Python 腳本實現了雜湊值的生成，最終揭示了 Nix 如何確保其可重現性和依賴管理。
+ 這篇文章非常詳細地解釋了 Nix 派生項的建立過程，對於想深入瞭解 Nix 的人來說是個很好的學習資源。
+ 雖然文章內容有點技術性，但作者的講解非常清晰易懂，讓我對 Nix 的運作原理有了更深入的理解。
#Nix #軟體建構 #開發工具
Max Bernstein · Nix derivations by hand, without guessing
More from 
Max B
Nix Derivations, Without Guessing
Max Bernstein · Nix derivations by hand, without guessing
More from Max B
Hey everyone!
#Nix and #NixOS enable declarative systems and reproducible builds — topics that are especially interesting to the systems community.
Next Tuesday (2025-04-15), Cyberus Technology is hosting a Nix #Meetup, and it's open to everyone!
If you're interested in joining, just react to this message with an emoji. 
Cyberus Technology Office, Zwickauer Straße 46
Tue., April 15, 18-22 o'clock
Pizza and drinks included
PlanetNix 2025 talks are now live 
Missed the event? You can now watch the sessions here 
Some highlights:
- Kelsey Hightower and Ron Efroni chat about Nix in a raw, honest fireside chat.
- Aneesh Agrawal shows how Anthropic boosted deploys with nix-sidecar.
- Yannik Sander dives into evaluation performance
And more plus a series of lightning talks!
Big thanks to the Nix community, organizers & volunteers 
Thx to @ivelasq3 for pointing me to this blog post of hers: https://ivelasq.rbind.io/blog/reticulate-data-recreation/
I used it as an example to "port" the code to a rixpress pipeline which you can find here: https://github.com/b-rodrigues/rixpress_demos/tree/master/yanai_lercher_2020
end result is here: https://b-rodrigues.github.io/rixpress_demos/yanai_lercher/index.html
%>% dreamsCreating a dataset from an image using reticulate in R Markdown – %>% dreamsA cool paper used R and Python together — and so can you!
Nix derivations by hand, without guessing https://lobste.rs/s/1ldtix #nix
https://bernsteinbear.com/blog/nix-by-hand/
lobste.rsNix derivations by hand, without guessing | Lobsters
Vimjoyer's April Fools video memed a Determinate #Nix feature into existence: https://www.youtube.com/watch?v=MZUWyrnTUkE
Replied in thread
@janl The purpose is to warn bystanders to invest in technological #complexity that seems to be very attractive for its advanced features without acknowledging the risks or efforts associated.
Its learning curve doesn't even allow for an easy start.
As with so many awesome tools, this is something for specific experts and not for new/occasional/advanced users.
BTDT and I've had my fair share of bad experiences.
Current pain in my setup: #NixOS. Instead of providing an abstraction layer to keep away certain OS setup & maintenance problems for good, I got into so many little & bigger troubles that I try to tell people only to use it when they are ready to invest its required learning effort all the way.
From my point of view, this also holds true for "advanced" file systems like #ZFS, #XFS, ... YMMV.
I have to say, my automatic dependency scanner [1] for #nix packages is already working better than expected!
So far i found unused dependencies in git [2], gst-plugins-bad [3], [4], linux-pam [5], networkmanager [6] and vlc [7]. And i don't plan on stopping! All these unused dependencies cause unnecessary strain on our CI and are trivial to clean up. Some of these dependencies are even old enough to drink!
I will give a talk about the tool at @cccda this Monday in the hopes of getting more people excited for this cleanup work, and to get ideas about improving the tool.
[1] https://github.com/LordGrimmauld/nix-check-deps
[2] https://github.com/NixOS/nixpkgs/pull/391664
[3] https://github.com/NixOS/nixpkgs/pull/394242
[4] https://github.com/NixOS/nixpkgs/pull/394423
[5] https://github.com/NixOS/nixpkgs/pull/396135
[6] https://github.com/NixOS/nixpkgs/pull/395311
[7] https://github.com/NixOS/nixpkgs/pull/391226