On Sun, Nov 29, 2015 at 07:25:32PM +0100, Michael Banck wrote: > > Even if your package is not directly to blame, I think it is important > > to know how this happened and ensure that it will be fixed. > > I think the reason is that testing now has gfortran-5.2, and the elpa > package in testing has not been rebuilt with it since. There was an > elpa upload recently, but as it FTBFS on a few arches, it hasn't > migrated yet.
But we have Depends, Build-Depends, sonames, and all that. Is this a transition that we did wrong? Or maybe this is a bug in the script that makes packages to propagate to testing? (it used to be called britney if I remember well). > So hrm, not exactly sure what to do about it. The options are basically two: * Do nothing, i.e. keep the bug open until the problem it's fixed. * Clone/reassign/retitle as appropriate.
