Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | podman-compose: switch to main branch | Bruce Ashfield | 2024-07-10 | 1 | -1/+1 |
| | | | | | | | | | | | | | The upstream project has made the "interesting" decision to delete the stable branch and move to "main" for recent releases. So rather than being able to simply switch for our updates, we have to switch to main on all releases that had podman-compose recipes using the stable branch. Luckily, the commit hashes haven't changed, so we only have to modify the branch in the SRC_URI. Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> | ||||
* | podman-compose: switch 1.0.3 to stable branch | Bruce Ashfield | 2022-06-01 | 1 | -2/+2 |
| | | | | | | | | | It looks like 'devel' in podman compose gets rewritten, so our 1.0.3 commit is no longer on that branch, breaking fetches. Moving to stable and changing the commit to avoid the issue. Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> | ||||
* | podman-compose: update to 1.0.3 | Bruce Ashfield | 2022-03-21 | 1 | -0/+15 |
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> |