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
Where can the treefiles/manifests be found that are used to generate the official ostrees used for Silverblue?
At one point these were (somewhat buried) on pagure but discoverable. Now, they no longer seem to be there and I am unable to find them after looking for many hours. I have located the source manifests/treefiles/compose config repo: https://pagure.io/workstation-ostree-config
Please provide a link to where these are maintained now. I would appreciate if this info was added prominently into documentation somewhere and kept up to date with current locations.
Users should not have to go dumpster diving for this.
The text was updated successfully, but these errors were encountered:
Forgive me for missing it on the organization's page. This is not where I'd expect to find it.
I would suggest adding it to this project's README as this issue tracker pertains (ostensibly) to the contents of those manifests used to build the ostree.
Unfortunately the current state of Fedora project artifacts being scattered amongst github, gitlab and internal tooling creates a very confusing and difficult to navigate situation for users (accessibility issue). It is very odd to find an issue tracker in an SCM system with effectively an empty repository associated to it, tracking issues for something located elsewhere. This is not a normal pattern in the usage of these tools.
Where can the treefiles/manifests be found that are used to generate the official ostrees used for Silverblue?
At one point these were (somewhat buried) on pagure but discoverable. Now, they no longer seem to be there and I am unable to find them after looking for many hours.I have located the source manifests/treefiles/compose config repo: https://pagure.io/workstation-ostree-configPlease provide a link to where these are maintained now.I would appreciate if this info was added prominently into documentation somewhere and kept up to date with current locations.Users should not have to go dumpster diving for this.
The text was updated successfully, but these errors were encountered: