Recent comments posted to this site:
I recently faced with a fail
...
export pixel podcasts/<redacted>.mp3
adb: error: failed to copy '../../.git/annex/objects/17/vK/SHA256E-s57638506--06c92a06db07fa511271e5426c9447cb0fab551d7ba2b9c9d26d3c7e3f975b5c.mp3/SHA256E-s57638506--06c92a06db07fa511271e5426c9447cb0fab551d7ba2b9c9d26d3c7e3f975b5c.mp3' to '/storage/emulated/0/home/media/podcasts/not-related/<redacted>.mp3': remote couldn't create file: Operation not permitted
../../.git/annex/objects/17/vK/SHA256E-s57638506--06c92a06db07...1 file pushed, 0 skipped. 37.0 MB/s (57638506 bytes in 1.487s
adb failed to store file
failed
(recording state in git...)
export: 2 failed
Everything is done as usual on the phone, barring two all other files are succesfully sent. Any clues what might be the cause?
Update: Since I posted this comment, enableremote of an existing webdav special remote has been made to work even if you cannot write to it. So there is no need to use httpalso and no need for a readonly=true.
How feasible would it be to be able to configure the remote so that a git-annex metadata get pushed to the S3 with the objects.
Something like sync-meta=mymetafield
that would set x-amz-meta-mymetafield=
to the value of git-annex metadata -g mymetafield --key theobjectkey
, whenever the data is pushed to the S3.
Thanks!
It seems to be that git has gotten smarter and now actively prevents you from adding a .git
folder (I did this many years ago when before I learned about submodules); I'd like to do something like the following:
bash
git init --separate-git-dir=.gitannex .
git --git-dir=.gitannex annex init
git clone some_repo # A repo I'm pulling from GitHub/wherever and don't want a submodule of as it's not my personal project
git --git-dir=.gitannex add some_repo
Essentially, I can override that .git
folder name, but it still checks for other .git
folders; is there a way to remove this check?
Thank you Joey!
Except for the web special remote, which is a special case. I guess yours special remote also may be a special case, ...
or in the other words, "not that special" after all. I see it just a common enough pattern for use of this new reregisterurl
that in my case it would be easier to just add an option instead of chaining manually reregisterurl
, figure out what key one way or another, call setpresentkey
with 0
. After all it is for a user to announce one way or another.
Anyways, I am ok for now, hopefully would not forget next time I use it to chase with that extra invocation.
You can use git-annex setpresentkey
to tell git-annex that content is not
present in your special remote.
Usually whether or not an url is currently registered with a special remote does not affect whether content is actually stored in it, which is why these are 2 different things. Except for the web special remote, which is a special case. I guess yours special remote also may be a special case, but git-annex doesn't know about it, and so why not use setpresentkey to handle the special case, rather than further complicating reregisterurl with it?
Note that, like git-annex unregisterurl, using this option unregisters an url from a special remote, but it does not mark the content as not present in that special remote.
But then how to mark "not present" in that remote? After git-annex-reregisterurl
I still have [datalad]
remote listed although url now, correctly, associated with web
. I have tried drop
but that didn't work
❯ git annex drop --from datalad images/neurodesk/neurodesk-afni--21.2.00.simg
drop images/neurodesk/neurodesk-afni--21.2.00.simg (from datalad...) (locking smaug...)
Removal of content from urls is not possible
failed
drop: 1 failed
Could there may be option --fully
or --mark-not-present
option to make it 1 invocation operation?