You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is this the intended behaviour? I guess I was using it wrong, but I think the cli is not very forgiving here, where could I have learned about the correct order of commands?
Edit: In case this matters, I'm using ostree from the debian testing repo on arm64
ostree admin init-fs implies creating the ostree repo, which is always in bare mode for sysroots (since the goal is to share hardlinks). ostree init is idempotent but will confusingly not error out if the requested mode isn't of the type of the existing repo. But anyway, you normally cannot switch from one repo mode to another after it's been created.
Hi,
I was observing something that did not seem logical to me, I'm not sure if this is a bug but I don't really understand what ostree is doing here.
Given this example cli session:
I do get a file with the name
*.file
despite using the modearchive
which should result in getting a*.filez
file.Out of curiosity, I swapped the order of the
init-fs
and theinit
call, which does give me the*.filez
file as expected.Is this the intended behaviour? I guess I was using it wrong, but I think the cli is not very forgiving here, where could I have learned about the correct order of commands?
Edit: In case this matters, I'm using ostree from the debian testing repo on arm64
The text was updated successfully, but these errors were encountered: