Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix package :data visibility so it's compatible with cacerts() #44

Merged
merged 2 commits into from
May 4, 2024

Conversation

lazcamus
Copy link
Contributor

set package :data visibility to public so it can be used in a call to cacerts()

I stuck a quick check into examples/apt tests to verify that it behaves as expected.

@lazcamus
Copy link
Contributor Author

The bullseye.lock.json diff has a spaces vs tabs change that was unintentional ... the diff looks sane with whitespace ignored

I'm not sure if this is a byproduct of another change and the lock file never got regenerated, or maybe my environment is somehow creeping in?

@thesayyn
Copy link
Collaborator

thesayyn commented May 1, 2024

Yeah, we should be ignoring the lockfiles from formatter. Feel free to revert those lockfile changes.

@lazcamus
Copy link
Contributor Author

lazcamus commented May 2, 2024

@thesayyn lockfile is reverted ... though it'll have a legit change if you re-gen it b/c I added a package

@thesayyn
Copy link
Collaborator

thesayyn commented May 2, 2024

that's true, sorry, you can regen it.

@lazcamus lazcamus force-pushed the cacerts-perm-fix branch from 27582f5 to 54335a1 Compare May 4, 2024 18:39
@lazcamus
Copy link
Contributor Author

lazcamus commented May 4, 2024

that's true, sorry, you can regen it.

regenned the lockfile and rebased on main so the PR should be current

oddly, the spurious whitespace diff I was seeing before is no longer occurring 🤷

@thesayyn thesayyn merged commit 490e5ac into GoogleContainerTools:main May 4, 2024
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants