-
Notifications
You must be signed in to change notification settings - Fork 54
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
Allow to change channel priority #343
Comments
Hi @beenje indeed, we need to figure out how to do all of this. |
Unfortunately, I don't think that would help with our workflow :-( |
Any update on this for channel-specific matchspecs? |
No updates yet, sadly. I think our thoughts are to extend the options:
channels: [...]
mirrors: ... (or from global configuration)
channel_priority: strict/lax
target_platforms: ... ? should probably be a map? do we need this?
compilers:
cxx: gcc 12.3
c: co
linux-64:
cxx: bla
variant_configuration:
boost_cpp:
- 1.4.5
- 1.6.5
bla: ...
...
|
This is a blocker for my work using |
I had seen in the discord that I could work around this by using the channel pin in the I created a PR adding a |
Thanks @tl-hbk ! |
Ive tested the new cli argument and couldnt get it to work, im curious if others had time to test it and made it work. |
It worked splendid for me. Although, my previous channel_priority was |
Ive tried again today and this is definitely not working. Maybe because im using 3 channels |
I actually can reproduce the channel_priority not working for solving test
phases. It only appears to apply in build phases.
|
Could you help me reproduce it? I'm unable to get it to not solve both with the tests running with the initial build |
I have a basic reproduction: build.sh
run_test.sh
recipe.yaml schema_version: 1
package:
name: problem_reproduction
version: 0
source:
path: .
build:
noarch: generic
tests:
- requirements:
run:
- python <=3.6
- protobuf
script: run_test.sh Create the override channel:
Run:
Observe the output:
|
Thanks I was able to replicate the issue. I'll create another PR to fix it |
It looks like part of my change was reverted during a pretty big refactoring 2c7f0e9#diff-be833857e8bbf63e2cbb12410f1e722789c4dce3d8c1dde47a79af89e52c71dcL201 2c7f0e9#diff-b1a35a68f14e696205874893c07fd24fdb88882b47c23cc0e0c80a30c7d53759R521 After changing it to |
Happy to test again on the next release |
It looks like channel priority is set to strict mode when testing with rattler-build.
This is an issue for us as we have 2 internal channels: the default one for stable packages and a "dev" one for testing.
When building a dev package we pass the "dev" channel and usually want the most recent version of some dependencies to be installed. That could come from the dev or stable channel.
I haven't seen a way to configure the channel priority. It would be great to have a flag or another way to change that.
The text was updated successfully, but these errors were encountered: