Hi,
at https://tracker.debian.org/pkg/cssutils I don't see,
why the package does not migrate. Some package depend on
cssutils and will be removed from testing soon...
Any idea what's wrong with cssutils?
TIA & Cheers
On Thu, Feb 06, 2020 at 12:00:36PM +0100, Martin wrote:
> at https://tracker.debian.org/pkg/cssutils I don't see,
> why the package does not migrate. Some package depend on
> cssutils and will be removed from testing soon...
>
> Any idea what's wrong with cssutils?
https://release.debian.org/brit
Quoting Mattia Rizzolo :
I reckon the way forward is to fix those two FTBFS in calibre.
If calibre gets removed from testing on 2020-02-16, the reason
for non-migration of cssutils and removing depending packages
from testing, e.g. gajim, vanishes. Will this work out due to
britneys wisdom? Or
On Thu, Feb 06, 2020 at 12:29:08PM +0100, Martin wrote:
> If calibre gets removed from testing on 2020-02-16, the reason
> for non-migration of cssutils and removing depending packages
> from testing, e.g. gajim, vanishes. Will this work out due to
> britneys wisdom? Or should calibre better remove
Quoting Mattia Rizzolo :
Given that the whole stack of packages is scheduled to get out on
2020-02-16, it's more likely that everything will be removed, and then
cssutils will migrate back (and with it everything that will be suitable
to migrate back into testing) at the next britney run.
That'
> If fixing those FTBFS is not on the table, I think you could just let it
> be, and have it go out and then back in. Tricks like pinging the bug to
> delay the autorm will likely backfire since it might very well be that
> very same bug that is also removing calibre. At the same time,
> botherin
Hi Nicholas,
thanks for your email.
On Thu, 06 Feb 2020, Nicholas D Steeves wrote:
> It doesn't look like these test failures on non-x86 will go away by
> themselves, though. Somebody will have to figure out what's wrong
> and fix them eventually.
Forwarded upstream
https://bugs.laun
7 matches
Mail list logo
