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

jobs variable reset only works when upgrading format from 2.0 -> 2.2, not 2.0 -> 2.1 -> 2.2 #5816

Closed
dra27 opened this issue Jan 31, 2024 · 1 comment · Fixed by #5904
Closed

Comments

@dra27
Copy link
Member

dra27 commented Jan 31, 2024

When upgrading from a 2.0 root directly to 2.2, one gets:

[NOTE] The 'jobs' option was reset, its value was 255 and its new value will vary according to the current number of cores on your machine. You can restore the fixed
       value using:
           opam option jobs=255 --global

If the root has already been upgraded to 2.1, this check is skipped (and the old, fixed value, persists).

Not clear on the impact - it just probably just means a lot of users have a hard-coded wrong opam 2.1 value.

@kit-ty-kate kit-ty-kate added this to For RC in Opam 2.2.0 Feb 5, 2024
@rjbou
Copy link
Collaborator

rjbou commented Feb 5, 2024

linked to #5284

@kit-ty-kate kit-ty-kate moved this from For RC to For beta3 in Opam 2.2.0 Apr 8, 2024
Opam 2.2.0 automation moved this from For beta3 to Done May 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Opam 2.2.0
  
Done
Development

Successfully merging a pull request may close this issue.

3 participants