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

update rootlesskit to 1.0.1 #5773

Merged
merged 1 commit into from
Jul 21, 2022
Merged

Conversation

dirkmueller
Copy link
Contributor

@dirkmueller dirkmueller commented Jun 28, 2022

This avoids an issue with u-root 7.0.0 which has been pulled:

$ go list -u -m all
$ go list -m: github.com/u-root/[email protected]+incompatible: retracted by module author: Published v7 too early (before migrating to go modules)

Proposed Changes

This enables outdated-dependency check to work again and not fail on a retracted module.

Types of Changes

Bugfix

Verification

CI passes

Linked Issues

  • TBD

User-Facing Change

Bumped rootlesskit to v1.0.1

Further Comments

@dirkmueller dirkmueller requested a review from a team as a code owner June 28, 2022 13:05
go.mod Outdated
@@ -104,7 +104,7 @@ require (
github.com/rancher/wharfie v0.5.1
github.com/rancher/wrangler v1.0.0
github.com/robfig/cron/v3 v3.0.1
github.com/rootless-containers/rootlesskit v0.14.5
github.com/rootless-containers/rootlesskit v0.14.6
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Any reason not to use v1.0.1?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

from a "what makes sense" perspective going with newest makes most sense, but it is a much larger jump. pushed now.

Copy link
Member

@brandond brandond left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If Akihiro thinks we should go to v1.0.1 then I'm liable to agree.

@dirkmueller dirkmueller requested a review from brandond June 29, 2022 11:30
@dirkmueller dirkmueller changed the title update rootlesskit to 0.14.6 update rootlesskit to 1.0.1 Jun 29, 2022
@dirkmueller
Copy link
Contributor Author

so it looks like 1.0.1 is failing on the arm architecture. going back to 0.14.6 to confirm

@AkihiroSuda
Copy link
Contributor

so it looks like 1.0.1 is failing on the arm architecture. going back to 0.14.6 to confirm

What was the error?

@dirkmueller dirkmueller changed the title update rootlesskit to 1.0.1 update rootlesskit to 0.14.6 Jun 30, 2022
@brandond
Copy link
Member

I think the failure with 1.0.1 was just a CI flake. Your other PR for 1.x.x seems to be passing at the moment.

@dirkmueller
Copy link
Contributor Author

I think the failure with 1.0.1 was just a CI flake. Your other PR for 1.x.x seems to be passing at the moment.

the other PR is using 1.0.0, not 1.0.1, which passes. 1.0.1 still fails.

@dirkmueller dirkmueller changed the title update rootlesskit to 0.14.6 update rootlesskit to 1.0.0 Jul 4, 2022
@brandond
Copy link
Member

brandond commented Jul 5, 2022

I'm a little confused, you appear to be updating both this PR and #5788 - which one would you like to move forward with?

This avoids an issue with u-root 7.0.0 which has been retracted by the
author:

  $ go list -u -m all
  $ go list -m: github.com/u-root/[email protected]+incompatible: retracted by module author: Published v7 too early (before migrating to go modules)

Signed-off-by: Dirk Müller <[email protected]>
@dirkmueller
Copy link
Contributor Author

I'm a little confused, you appear to be updating both this PR and #5788 - which one would you like to move forward with?

the other one was just for testing the CI. You were right, the previous failure appeared to be a CI fluke, so this is good to go.

@brandond brandond changed the title update rootlesskit to 1.0.0 update rootlesskit to 1.0.1 Jul 21, 2022
@brandond brandond merged commit 93ca992 into k3s-io:master Jul 21, 2022
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.

4 participants