[question] correct usage of build_policy = "never"

Conan version 1.44.0 OS: Windows 11

We created a conanfile.py which only contains a package step to be created with conan export-pkg instead of conan create. As it doesn’t use the exports_sources to copy files into the conan cache, I assumed it makes sense to disable the possibility to rebuild a package. Therefore we set the build_policy = "never" So that it isn’t possibly to attempt to recreate the conan package only from the conanfile, as this wouldn’t work anyway. Then I get the error message: ERROR: No package matching '[package name]' pattern found. this message also appears with conan create.

So my questions:

• is there anything I need to do, to get rid of this message, but keeping the build_policy = "never"
• Is my understanding correct of the purpose of the build_policy = "never"? Does it make sense in this case?

• I’ve read the CONTRIBUTING guide.

[memsharded]

Ok, I have been able to track this. It is an unfortunate UX bug, due to sharing the core code with other commands. But, it has no effect at all, it is just an incorrect message, but the command is working fine, the package is correctly created, etc.

I have checked it, and this is already fixed in 2.0, and it would be quite dirty to try to fix it in 1.X, so I vote to consider this bug closed in 2.0.

[memsharded]

I have been able to reproduce it. Thanks for reporting, we will have a look.

At least, it seems the package is being created, it is just an error message.