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
pkg(8) infinite loop with multiple repos containing different versions of pkg #1303
Comments
Also experienced this, your workaround worked perfectly. |
Worked for me today. Thanks. |
I think I first encountered this bug around 1.5.4. Any pointers to the piece of code causing this issue? |
not sure if i'm just adding noise, but FTR i have encountered this issue today with 1.6.1_1, so it's definitely not resolved yet. and yes, the workaround still works, too, thanks! |
ditto. However given there's no bugzilla report should I add one for this, and refer the workaround + github issue to make it a bit more discoverable? |
any news about this? I see even someone provided patch.. |
andrejzverev: It appears to have been fixed on 2015.11.18, 26 days before your question. |
@dlangille nope, one part of fix was committed on 24 Dec, yes. But loop still exist in case on multirepo. |
This is happening to me now on 10.2-RELEASE-p9 with pkg 1.6.2 I have a snapshot of the system if anyone wishes it for debugging. |
The bug just happened to me again. The infinite loop happens reproducibly on 1.6.2 when If it helps: when running |
should be totlaly fixed since pkg 1.7.2 |
Bug is reproduced with pkg-1.8.6. FreeBSD repo and my local repo contains pkg-1.8.7.
|
As @alxrem said this is happening to me too, if you have pkg package on both repositories (Say official FreeBSD and custom Poudriere repository) when you do:
It will run on an infinite loop, the fix (In my case) was to specify the custom Poudriere repository:
Hope it helps someone! |
@bapt do you think this will get fixed? I'm adding more info because we are stumbling with this every now and then (Generating tons of pkg processes and network activity when running in multiple machines/jails):
Would love to provide more information/debug if needed. Thanks! |
Little more information, this is for every package we want to upgrade. If we don't use the
|
I am having the same issue as @amontalban , debug throws the exact message. |
I just saw the same thing on a system that had pkg 1.12.0 installed, which was pointing to multiple repos that all were serving version 1.13.2. The workaround of using |
I experienced the same issue when upgrading pkg: 1.17.1 -> 1.17.5 Is rhis going to be fixed? |
|
Hmmm..... at the point I ran this, the desktop repo still had pkg-1.5.5 (hadn't finished building) whereas the server repo had pkg-1.5.6
Workaround was simply
pkg install -r server pkg
and then continue with pkg upgrade.The text was updated successfully, but these errors were encountered: