On 4/3/19 7:10 PM, Andreas Beckmann wrote: > On 2019-04-03 17:27, Thomas Goirand wrote: >> Weird, I couldn't reproduce. Could it be my setup with >> --build-dep-resolver=aspcud? > > Likely. I'd guess my build pulled a package from sid due to > insufficiently versioned B-D. > > Andreas
Hi Andreas, When I look into my build log, I can see that it took python3-castellan 1.2.2-1, while yours took 0.19.0-1. So I replaced aspcud by aptitude, and then I saw the same issue you reported. Lesson learned: I'll use aptitude from now on, as it looks like it does a better job at taking the right (expected) dependencies. After bumping castellan to 1.2.2, built succeeds. Uploading and filing a bug upstream... Thanks for all of your valuable bug reports, Cheers, Thomas Goirand (zigo)
