[Python-modules-team] Bug#943509: python-django: FTBFS due to failed tests: failures=7, skipped=891, expected failures=4

[Paul Gevers]

Hi,

On Sat, 26 Oct 2019 19:17:01 +0100 "Chris Lamb" <lamby at debian.org> wrote:
> Hi László,
> 
> > But you mean plural packages? I knew only python-django. I meant
> > sure, it's a FTBFS in experimental where […]
> 
> I see what you mean now, thanks. I assumed it affected more packages
> and was more severe than just python-django from the description, but
> I admittedly had done no specific searching.
> 
> > In short, I don't get the importance of filing a FTBFS bug for a beta 
> > release in experimental.
> 
> Hah, well my defense I did not file this bug and indeed deliberately
> did not file any issue in Debian for this very reason when I first
> noticed it, prefering to file a bug upstream first (there have been
> similar short-term issues in other database backends in the past).
> 
> I would be perfectly happy with downgrading this to important and thus
> non-RC.
> 
> >  Yeah, you are British. :)
> 
> Don't quite follow that... :)

Can we please move this bug forward? python-django *in sid* has been
failing to build from source since the beginning of November. It's FTBFS
is hampering CVE fixes from reaching testing users and is hampering the
python 2 removal effort.

@python-django maintainers what does this mean for the functionality of
python-django in bullseye? Is it "only" the test that fails and can that
thus be temporarily disabled?

Paul

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/python-modules-team/attachments/20191229/4919d9cc/attachment-0001.sig>