-
Notifications
You must be signed in to change notification settings - Fork 278
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
[regression] pkg lock and unlock complains about already locked or unlocked #2059
Comments
I cannot reproduce that here |
Can you try again? Still an issue here:
|
Hello, i can reproduce it aswell.
|
A lazy guess: is multiple repos sometimes a factor?
|
I only see this:
|
GDB is your friend, look at this:
When you set a package locked it immediately shows up in the search results. I suggest that the lock field has 3 states: 0: unlocked And to iterate the database two times. When you lock all lock fields should go to 2 first and if you see 1 output a warning. Then iterate again and change 2->1 Same for going to unlocked. locked = 2 can be treated as locked though. Or just skip the warning for already locked/unlocked packages! @bapt : Any comments? |
no I would prefer that we fix the regression, this is caused by the following commit ade813b |
Thank you for fixing! |
Likewise: thank you, @bapt. For other readers: cross-reference FreeBSD bug 267629 – ports-mgmt/pkg, ports-mgmt/pkg-devel: already locked, or already unlocked, after using pkg-lock(8) to lock or unlock. |
Reproduction:
The text was updated successfully, but these errors were encountered: