Andrej Z.
Andrej Z.
I'm sure if is done for 1.3 and later, can you confirm?
This is bad, i hope it will be fixed someday. As workaround you can explicitly give pkg hint which repo must be used. ``` pkg install -r reponame package ```
You can try with pkg 1.6. It should work as expected.
this still defect for pkg 1.3?
@bapt ?
I'm sure I missed the idea. But what a difference with `pkg delete -n pkgname`, since solver will remove all depends recursive on `pkgname`?
3a) Without quite mode my scripts read lot of 1% 2% 3% ... 100% of progress. 3b) Mostly pkg made for people. People like reading and controlling such tools :-)...
What behavior do you expect? Message about what package locked and cannot be upgraded?
Em, i'm not sure, but how you did create repo with with two packages with same pkgname? I thought what pkgname is unique key
Less pain to implement this via external perl (for example) script :-)