Hi Chris, On Sat, Oct 26, 2019 at 2:48 PM Chris Lamb <la...@debian.org> wrote:
> Not quite sure what you mean by bad. It's "bad" in that it's causing > an FTBFS in other packages, but I don't think that's quite what you > meant here. :) > Yeah, you are British. :) But you mean plural packages? I knew only python-django. I meant sure, it's a FTBFS in experimental where people expect failures and maintainers follow it more closely. Doesn't upload the package to Sid before all issues are solved. What are the surroundings? Do you need a clean compile soon because you are testing some important bugfix / alternative compilation method, an upstream release which adds a long awaited feature (users are expecting that soon), etc? It's a beta of Django and even a RC release might be far away. I've doubts SQLite3 upstream will do a minor updated release. I think the new SQLite3 stable upstream release can be a month away. Should I upload a Fossil snapshot of that to experimental immediately? In short, I don't get the importance of filing a FTBFS bug for a beta release in experimental. Regards, Laszlo/GCS
