Thank you for your insight. Ultimately, the goal is to get package A into Factory (from P). I already maintain a handful of packages on Factory and a few other packages in devel projects. Today, the owner of B on Q added me as a maintainer of Q, which allows me to submit B to Factory as you mentioned, although it will not be too useful until A is added to P (if accepted!). Just before my initial email on this list, I already submitted A to P where it has not been reviewed yet (I explained in the request that A depended on B in Q). On 5/16/23 21:13, Ben Greiner wrote:
Am 16.05.23 um 13:27 schrieb Michael Pujos:
I want to submit package A from my home project to devel project P. package A depends on package B that is only found in devel project Q. In my home project, B was simply a link to Q, allowing A to build. How does it work when submitting A to P, for A to find B when built in P ?
Make sure that B is submitted from Q to Factory. A will only be built in P as soon as B is in Tumbleweed. Wait until then before you submit A to P. But if you have control over A in P or can convince the maintainer, submit it at the same time to Factory (even though it does not build in P) and tell dimstar to put it into the same staging project as B. If the latter does not happen, the staging of A will just be unresolvable and sit there until B is accepted in its own staging.
Or, if you have full control over Q: Add P to the repository paths of Q/meta