Notices by Yann Büchau :nixos: (nobodyinperson@fosstodon.org)

@dckc @joeyh @cwebber I made an overview here, but not overly in-depth:

https://tube.tchncs.de/w/p/4as7A1ZDo7FDqydwVrUbtv?playlistPosition=5&resume=true

@publicvoit @AngryAnt @raboof Well if you need any kind of dependency, a simple `python ./myscript.py` won't work on any distribution. Poetry or uv can ease that step of specifying and fetching dependencies, and work identically across distros. The only difference on #NixOS is that you will need to run everything from within an fhsUserEnv, e.g. execute my `fhs` command here before:

https://gitlab.com/nobodyinperson/nixconfig/-/blob/main/modules/fhs.nix?ref_type=heads

This is how I do it.

@publicvoit @AngryAnt @raboof Same for NixOS. If a venv does the job for you, use my linked fhs command as the one thing to execute before doing anything Python, then do whatever venv stuff you need to do. If you don't need external system dependencies, do you really need nix?

Why exactly does my :nixos: #NixOS want to rebuilt my :linux: #Linux kernel if I use #rsync from nixpkgs-master? 😅

🍿

> git annex assist
...
symlinkPointsToGitDir: symlink target points to git dir
remote: fatal: fsck error in pack objects
error: remote unpack failed: unpack-objects abnormal exit

IIUC, :git: #git implemented something that uselessly breaks :gitannex: #gitAnnex / :datalad: #DataLad compatibility on the remote side, amazing! 🤦

https://github.com/git/git/commit/a33fea0886cfa016d313d2bd66bdd08615bffbc9

Initial report:

https://git-annex.branchable.com/forum/Strange_symlinkPointsToGitDir_error/#comment-12ed3e72e46de9b086da51455f20b26b

@joeyh @mih @chrysn

@SReyCoyrehourcq @khinsen It's true that the #Python ecosystem moves quickly and one can not rely on an analysis to still work *exactly the same* in a couple of months when executed with the then-latest versions. But that's not just the case for Python! Relying on backwards-compatibility of any software stack is not enough and a very poor choice in the first place. As suggested in the README, using something like :guix: #guix or :nixos: #nix or at least containers is necessary.

@freemo For one, the beta and the non-beta store messages in different places IIUC, they are independent. Copying or restoring stuff around does not help. Signal desktop seems to be very fragile in that regard. It is also a security feature to not transfer old messages upon fresh pairing. All in all you're lucky if you can keep your message history and this is what I intend to so.

@freemo *-beta you mean. As I mentioned, I can't use the non-beta, because with that I'll lose all my messages again amd have to re-pair.

So apparently :nixos: #NixOS removed signal-desktop-beta from nixpkgs within a release and one even can't use an old, pinned nixpkgs version to still get it because of super cryptic errors in nixos-rebuild? 🤔

(must use the beta because otherwise no old messages and have to pair again...)

UPDATE: I forgot a {} after the import 🤦♂️

@libreoffice Of course, I know, sorry for ranting. I guess I'll just replace the ✅ with ✓ and be done with it...

Keep up the good work! 💪

Oh please @libreoffice PLEASE fix the bug that makes emojis disappear when exporting or printing to PDF 😩

For how many years (decades?) has this existed now?

Can't just be me, same problem across distros for me.

(Of course, I highly value your work maintaining an open source office suite, but this one really hits hard every time 🥲)

#LibreOffice #bug #emoji #PDF