Please fast-migrate fontconfig 2.13.0-5 into green
Closed, ResolvedPublic

Description

Hi Matthias,
Please "fast-migrate" src:fontconfig 2.13.0-5 into green. This is part of the solution to T433.
Many thanks!

mak added a comment.May 16 2018, 10:58 PM

The system doesn't seem to know that revision yet, I'll bump the packages urgency in advance.

In T434#7672, @mak wrote:

The system doesn't seem to know that revision yet, I'll bump the packages urgency in advance.

Would that be because it is not yet in buster?

Just wondering if there is a better way to get both packages into green ASAP as it is essentially making machines unbootable.

mak added a comment.May 17 2018, 12:47 AM

Would that be because it is not yet in buster?

Oh yeah, that is most certainly the reason ^^
I can sync the package from unstable though.

mak closed this task as "Resolved".May 17 2018, 3:26 AM

Done, if the package can migrate, it should migrate instantly.
Its status can be monitored at http://software.pureos.net/package/source/landing/fontconfig

chris.lamb reopened this task as "Open".EditedMay 17 2018, 6:57 AM

Unfortunately a few hours on http://software.pureos.net/package/source/landing/fontconfig is not showing -5 as being in landing or green. There is no reason why it shouldn't migrate if -4 is already there (no change of dependencies AFAICT). Can you help?

It's in landing now at least. Curious why it hasn't actually migrated given that the excuses mention that the priority was elevated?

d3vid added a comment.May 17 2018, 1:00 PM

This package has arrived in green (got it via apt even though http://software.pureos.net/package/source/green/fontconfig still lists -4).

mak closed this task as "Resolved".May 17 2018, 1:03 PM

@chris.lamb Be patient ;-) Migrating a completely new package taes at least two dinstall runs, so a few hours was just not enough time ^^
@d3vid The website takes a few minutes to update after a new package has been published, so you might have caight the new package immediately after it was migrated, but before it was actually registered in the database as being in green as well.

Add Comment