Reduce visibility of package_manager - #469
Conversation
836069a to
3278b5f
Compare
|
@chanseokoh Have you been making other changes to the GCP blob storage used here by chance? a bunch of our CI infra got taken out with 403's a an older version of this par. and sha 256 failures against master |
|
We use these utils to add back in packages that are missing in the distroless, like |
|
@ianoc-stripe maybe try https://storage.googleapis.com/distroless/package_manager_tools/01579c3dd0f9b4397fe4f50769a9caea130b15e7/dpkg_parser.par Or just sync your distroless fork with the master. But note that these binaries can be removed in the future. |
Ah, yeah, this won't work for now, but it will start working again after merging #469 and fixing an intermediate inconsistency. |
|
Thanks for the quick reply! For now i replaced the remote ref with the http_file and updated the sha to the right one, so its unblocked the ci flows. wrt that the binaries can be removed, is this code we should fork/not depend on? |
In principle, any fork of the repo should build successfully. What happened is that, when I prepared #469, I replaced the current dpkg_parser.par binary in order to make the Travis builds to pass. This changed the SHA, but now I find that was a mistake. Once #469 is merged, a new dpkg_parser.par will be built. After that, I will fix master to use the new binary. |
|
Ah thats perfect, @chanseokoh . Thank you. I was just a little concerned if we were depending on something we shouldn't have been here. Appreciate the great work that goes into this! |
Turns out this is unnecessary.
I have confirmed building and publishing all images by