#gitannex
TIL: #gitAnnex can be limited in bandwidth: `git config remote.REMOTENAME.annex-bwlimit-download "1MiB"`
Same goes for `annex-bwlimit-upload` and global limits are also possible (see `man git-annex`).
And here another one: #gitAnnex is notorious for making many commits in the background to the branches synced/<yourbranch>, synced/git-annex and git-annex. These have a perfectly valid technical reason and make git annex as awesome as it is, but in a #forgejo dashboard feed, these are massively confusing as they mask the really important changes. With a little bit of template massaging, these can be filtered out. Probably better to make this configurable somehow (checkbox? 
), but this is a workable solution for now.
It's very useful if you self-host the #FOSS tools you need, because then you can fix little issues you have here and there on your own.
For example, we use #forgejoAneksajo (#forgejo with #gitAnnex support) to sync and collaborate on code and data. We often have long filenames, which are unfortunately obstructed by forgejo's gigantic commit message column 
But a bit of #CSS later and that's fixed so we can more easily browse through our multicopter flight plots 
Heyy #gitAnnex quality people, do you have a quality tutorial to follow for archiving photographs? I am not satisfied with just creating a repo on an external drive because then I can't easily browse the archived photographs, and I am struggling to make an exported directory repo...
Registrations are now re-opened for #distribits2025, taking place 23-24 October! https://www.distribits.live/news/2025-registration-open/
Join us in person (spots are limited) or remotely - sign up now at https://www.distribits.live/.
Please note:
The call for contributions is closed
The #hackathon is full, but you can ask to join the waitlist in your registration form
@datalad #gitannex #distributed #data #opendata #rdm #tech #open_source_software #conference
@umphy 
#gitAnnex and 
#dataLad organize the data and sync it to our own 
#forgejoAneksajo instance. You can instantly see if everything is there and worked. A great workflow!
AG Umweltphysik Uni Tübingen@umphy I spent the last two weeks migrating and curating all the 
#NixOS configurations for the sensor packages to flakes. Previously, I hand-rolled the pinning, and it involved a lot of manual scripting, which is now gone, what a relief! 
I had to drop #gitAnnex though for tracking assets I want to deploy on the copters. Unfortunately, flakes don't like git annex. 
But there is workarounds for many things.
Beim #TagDerDigitalenFreiheit vom @ctt in #Tübingen am 26./27.07. gibts von mir einen Vortrag, wie man alles Mögliche mit 
#git trackt: Code, Zeit, Notizen, Fotos, Medien, etc.
@musicmatze @chrysn And Re: 'repo is tracked': git annex meticulously maintains a hidden git tree of the files in an export to speed up (imports and) exports. And exports can now also just hold the raw tree of annex/objects, so they can keep old files as well and have become pretty snappy. They just lack (history of) metadata.
How to remove a special remote in #gitAnnex ?
@nobodyinperson
Importing all our photos (stored in git-annex) into #Immich (which doesn't use git-annex) I'm being bitten hard by #gitAnnex not really caring about file timestamps - many files end up at the date I last did some big git annex get or whatever 
Kind of expected though. Luckily, most files have a rather sensible timestamp, so I wrote some #Python that queries Immich and set timestamps from filenames. Very finnicky, but it worked.
I need a #gitAnnex specialist: I try to `git annex move ./* --to somewhere` but that command tries to lock `otherhost`, which is unavailable.
The `annex-cost` of that `otherhost` is _higher_ than costs of other remotes that are indeed available.
What do I do?
Our fleet of #multicopters is growing as we prepare for our part in the #TeamX¹ campaign in 
#Austria next month.
We'll provide valuable in-situ #temperature, #humidity, #wind and #turbulence measurements with our custom meteorological PARASITE system on multiple copters in parallel across the Inn valley. This data will help with understanding wind shear in mountainous regions and eventually improve
#mountainWeather forecasts.
Our PARASITEs carry several atmospheric sensors and we derive the turbulent 3D wind vector from the copter movements. @nobodyinperson suggested to name them like #BugsLife characters 
. He put a nicely customized 
#NixOS in there to stay in control of the software, integrate it all and sync data e.g. to a #forgejoAneksajo instance (#forgejo with #gitAnnex support), our own or the one of @fzj_rdm during the VITAL campaign last year.
#Austria #Österreich #Inntal #Innsbruck #meteorology
The preliminary #distribits2025 schedule is now available: https://www.distribits.live/news/2025-distribits-schedule/.
You can expect to hear talks about federated data management across disciplines, deep dives into #gitAnnex and special remotes,
how to make your analysis pipelines #FAIR from beginning to end (and tools you can use to make it happen),
and so much more.
If you missed the registration deadline but would still like to participate, stay tuned - we will be able to accommodate late registrations soon.
There is now also a #gitAnnex wheel on PyPi that should run on any system with GLIBC 2.17+. This should work on CentOS7 (released more than 10 years ago).
If you have access to such a machine, please consider giving it a try.
Thanks!
Is there a tool to set up #GitAnnex to calculate archive unpackings yet? Something™ could look at a repo's .zip / .tar.gz files, check whether any file in the repo is also in there, and annotate it as computed / computable. (I'm not aiming to restore the zip files from the content –that'd be pristine-tar territory. I'd already be happy if the compute path would be there so that the single files don't need to be in the archive).
Yay, @joeyh made it so #gitAnnex pushes the current branch first (not the git-annex or synced/* branches). This is awesome when you want to push-to-create a local repo to your @forgejo or #GitLab instance. Previously, `git annex assist` et al. would result in e.g. synced/main (or worse: synced/git-annex) being used as the default branch on the forge, which is never what you want.
As of version https://pypi.org/project/git-annex/10.20250520b7 the #gitAnnex wheel is now tested and confirmed to be functional after a
`uv tool install git-annex`
on Linux (tested with Ubuntu 22.04 and 24.04), Windows (tested with 2022 and 2025), and Mac (tested with 13(intel), 14(arm), 15(arm)).
https://github.com/psychoinformatics-de/git-annex-wheel/actions/workflows/test-pypi-wheel.yaml