Hi, Quoting Hector Oron (2015-08-28 12:55:13) > It is rather tricky to check that, as you need quite a long list of > packages from experimental, then one needs to verify the build-dep > chain is correct, as using other solvers seemed to lead to bogus > packages being pulled in. <URL: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=693921#52 > > > If you have ideas for robust test cases, feel free to post them. since multiple packages are able to provide the same package name and since there are dependency alternatives (A|B), there exist multiple solutions for most dependency satisfaction questions. If all constraints are honored then they are all correct. The bug you quote mentions "bogus" packages drawn in by aptitude. Either aptitude is not respecting build and binary dependencies correctly in which case, these packages are indeed "bogus" (but then this is an aptitude bug), or the metadata is incorrectly expressing that these extra packages can be part of the solution. Which of these problems are you concerned about? As with this specific "bogus" package problem, aspcud "should" not have this problem because it optimizes the solution by the given optimization criterea. As far as this optimization criterea is concerned there is no "bogus" packages (if we assume that there is no bug in aspcud). In that case, are you concerned about the right optimization criterea? Or about dependency relationships that could lead to solutions that you might call "bogus"? Or about a bug in aspcud? It is extremely hard to compare solutions because in most cases, the solution found by apt will be different from the one found by aptitude or dose3. Would it be sufficient for you if I picked a snapshot, rebuilt all packages in experimental with the apt resolver and then rebuild those that fail with apt with the aptitude as well as with the aspcud resolver and then compare the results from the aptitude to the aspcud resolver? And by compare I mean: make sure that there is no FTBFS with the aspcud resolver where there is none with the aptitude resolver? Thanks! cheers, josch
Attachment:
signature.asc
Description: signature