sync issueshttps://gitlab.cern.ch/unpacked/sync/-/issues2023-07-20T14:20:48+02:00https://gitlab.cern.ch/unpacked/sync/-/issues/12I can't edit the file recype.yaml2023-07-20T14:20:48+02:00Gianfranco VecchioI can't edit the file recype.yamlHi,
when I try to edit the recype.yaml file I get this error:
"Someone edited the file the same time you did. Please check out the file and make sure your changes will not unintentionally remove theirs."
Thank youHi,
when I try to edit the recype.yaml file I get this error:
"Someone edited the file the same time you did. Please check out the file and make sure your changes will not unintentionally remove theirs."
Thank youhttps://gitlab.cern.ch/unpacked/sync/-/issues/10Can't edit the recipe.yaml file2022-11-17T15:54:02+01:00Alessandra FortiCan't edit the recipe.yaml fileIt says
"Someone edited the file the same time you did. Please check out the file and make sure your changes will not unintentionally remove theirs. "
but this has been going on all day and I cannot believe it takes so long to add a l...It says
"Someone edited the file the same time you did. Please check out the file and make sure your changes will not unintentionally remove theirs. "
but this has been going on all day and I cannot believe it takes so long to add a line.
can you help?
thankshttps://gitlab.cern.ch/unpacked/sync/-/issues/7Remove Old/Nonexistent Images2020-05-29T20:29:52+02:00Alexx PerloffRemove Old/Nonexistent ImagesWe have asked that [1] be synchronized and this is working beautifully. However, it seems that the system is not removing old images, which have been removed from DockerHub. For example, we previously had the tag latest-gpu-py3-singulari...We have asked that [1] be synchronized and this is working beautifully. However, it seems that the system is not removing old images, which have been removed from DockerHub. For example, we previously had the tag latest-gpu-py3-singularity, but this image was removed from DockerHub. I still see the folder in CVMFS, but of course not in DockerHub. Is it part of the system design that it will remove non-existent images or is this beyond its current capabilities? This would be a desirable feature. If it's not part of the plan, how else might we remove these old images?
[1]
https://gitlab.cern.ch/unpacked/sync/-/blob/master/recipe.yaml#L62https://gitlab.cern.ch/unpacked/sync/-/issues/5sync all tags newer than X2020-04-20T19:49:45+02:00Lukas Alexander Heinrichsync all tags newer than XHi,
we'd like to sync https://hub.docker.com/r/ucatlas/analysisbase/tags
but don't need all historical tags. At the same time it would be
nice to have auto-syncing of any new tags
(the images have significant overlap with the atlas/a...Hi,
we'd like to sync https://hub.docker.com/r/ucatlas/analysisbase/tags
but don't need all historical tags. At the same time it would be
nice to have auto-syncing of any new tags
(the images have significant overlap with the atlas/analysisbase ones since they
are built on top of them so would also be interesting to see whether the de-duping on the
file-level works0https://gitlab.cern.ch/unpacked/sync/-/issues/3Remove `:` from paths2020-06-03T21:46:10+02:00Dan GuestRemove `:` from pathsThis is a minor nitpick but if it's possible it might be desirable to remove `:` from paths. It's easy enough to work around by quoting the path but it could get confusing / ugly if people write more complicated scripts.This is a minor nitpick but if it's possible it might be desirable to remove `:` from paths. It's easy enough to work around by quoting the path but it could get confusing / ugly if people write more complicated scripts.