Closed iainbryson closed 5 years ago
Thanks for reporting this, I will try to have a fix asap. I think I should go back to just picking the executables from the p4 repo. Switching to yum, means the repo can break in the future. :disappointed: You can see here that it built when I first pushed to git, but it doesn't any longer :disappointed:
They have versioned packages too, that seems like a better choice for this kind of usage.
On May 31, 2019, at 9:48 PM, Amit Bakshi notifications@github.com wrote:
Thanks for reporting this, I will try to have a fix asap. I think I should go back to just picking the executables from the p4 repo. Switching to yum, means the repo can break in the future. 😞 You can see here https://hub.docker.com/r/ambakshi/perforce-swarm that it built when I first pushed to git, but it doesn't any longer 😞
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/ambakshi/docker-perforce/issues/12?email_source=notifications&email_token=AALVZX6HKWGCRZGD7TPPQE3PYF6JTA5CNFSM4HRXNVO2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWWGVAA#issuecomment-497838720, or mute the thread https://github.com/notifications/unsubscribe-auth/AALVZXYCRQERRZMRGJK75CLPYF6JTANCNFSM4HRXNVOQ.
Hey, this should be fixed now using versioned packages :)
Simple clone now fails: