Hi In Wine we depend on libwine-gecko-xxx before it's added to the archive, knowing/hoping/assuming that it will be added to the archive, which has always been true for Debian stable releases, but not for all intermittent Gecko versions that were needed in between (maintainer is in both cases the Wine packaging team, unfortunately afaik every new Gecko upstream release takes a lot of work, especially for reevaluating the copyrights).
Stephen, can you shed some light on the main problem(s) blocking frequent Gecko releases? Let's say, there's some chance that I help. This has the benefit of having the dependency already ready, once Gecko is added to the archive, without the need to reupload Wine. It may also show people more easily where work needs to be done (increasing the people who help from 0 to 0). Rhonda, do you see any flexibility in interpreting the policy for this case? If not, I'll do something like clone -1 -2 retitle -1 wine: doesn't find Gecko in documented place severity -1 important retitle -2 wine: recommends package not in main and commit a fix for -2. Of course this doesn't solve the main problem that the current libwine-gecko (2.40 for current wine, and 2.44 for current wine-development package) is not available in the archive. Greets jre
