summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* app-emulation/cri-o: version bump to 1.13.7Zac Medico2019-05-012-0/+113
| | | | | | | Reported-by: Bruce Guenter <bruce@untroubled.org> Closes: https://bugs.gentoo.org/684898 Package-Manager: Portage-2.3.66, Repoman-2.3.12 Signed-off-by: Zac Medico <zmedico@gentoo.org>
* app-emulation/cri-o: disable go build install flagDongsu Park2019-04-292-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | There has been a corner case where `make bin/crio` failed like that: ``` go build runtime/cgo: open /usr/lib/go1.12/pkg/linux_amd64/runtime/cgo.a: permission denied make: *** [Makefile:99: bin/crio] Error 1 ``` The failure happens only under certain circumstances, for example in Jenkins pipelines, where the standard Go runtime path `/usr/lib/go1.12` is not writable for normal users like `jenkins`. On the other hand, the failure is not reproducible when testing locally, nor when testing with the root user who can write to the Go runtime path. What happens is, the standard Go runtime sometime has incorrect timestamps or checksums of `cgo.a`, which makes `go build -i` think that it has to install its own library to the system directory. That's obviously not what the build process should do. Since Go 1.10, it's unnecessary to run `go build` with an `-i` option, because now `go build` command itself maintains a cache of recently build packages. Build speed will not be better by adding an `-i` option. So let's remove `-i` flag from `go build`. That's actually what upstream Go maintainers recommend to do. See: https://github.com/golang/go/issues/24674 Closes: https://github.com/gentoo/gentoo/pull/11863 Package-Manager: Portage-2.3.65, Repoman-2.3.12 Signed-off-by: Dongsu Park <dongsu@kinvolk.io> Signed-off-by: Zac Medico <zmedico@gentoo.org>
* app-emulation/cri-o: remove old version 1.13.0Zac Medico2019-04-292-106/+0
| | | | | Package-Manager: Portage-2.3.65, Repoman-2.3.12 Signed-off-by: Zac Medico <zmedico@gentoo.org>
* app-emulation/cri-o: version bump to 1.13.5Zac Medico2019-04-112-0/+113
| | | | | Package-Manager: Portage-2.3.62, Repoman-2.3.12 Signed-off-by: Zac Medico <zmedico@gentoo.org>
* app-emulation/cri-o: remove old version 1.10.1Zac Medico2019-04-112-106/+0
| | | | | Package-Manager: Portage-2.3.62, Repoman-2.3.12 Signed-off-by: Zac Medico <zmedico@gentoo.org>
* app-emulation/cri-o: HOMEPAGE: use HTTPSMichael Mair-Keimberger2019-02-173-5/+5
| | | | | | Closes: https://github.com/gentoo/gentoo/pull/11087 Signed-off-by: Michael Mair-Keimberger <m.mairkeimberger@gmail.com> Signed-off-by: Zac Medico <zmedico@gentoo.org>
* app-emulation/cri-o: move init script start_pre to startZac Medico2019-01-171-2/+3
| | | | | Package-Manager: Portage-2.3.55, Repoman-2.3.12 Signed-off-by: Zac Medico <zmedico@gentoo.org>
* app-emulation/cri-o: version bump to 1.13.0Dan Molik2019-01-033-1/+107
| | | | | | | | Closes: https://github.com/gentoo/gentoo/pull/10732 Tested-by: Dan Molik <dan@danmolik.com> Package-Manager: Portage-2.3.53, Repoman-2.3.12 Signed-off-by: Dan Molik <dan@danmolik.com> Signed-off-by: Zac Medico <zmedico@gentoo.org>
* app-emulation/cri-o: version bump to 1.10.6Zac Medico2018-12-042-0/+106
| | | | | | | Reported-by: Manuel RĂ¼ger <mrueg@gentoo.org> Closes: https://bugs.gentoo.org/668422 Package-Manager: Portage-2.3.52, Repoman-2.3.12 Signed-off-by: Zac Medico <zmedico@gentoo.org>
* app-emulation/cri-o: add libgpg-error depZac Medico2018-06-041-0/+1
| | | | Package-Manager: Portage-2.3.40, Repoman-2.3.9
* app-emulation/cri-o: new packageZac Medico2018-06-035-0/+177
Package-Manager: Portage-2.3.40, Repoman-2.3.9