 @Eickmeyer seems like a known issue, possibly an apt regression
 which means... um... things broke
 I'm fully aware, I've been reading along.
 👍
 Which is why I'm not sweating it as it's "Someone Else's Problem (tm)."
 lol vorlon said "is this apt in groovy?  do we need to roll back?" so i'm curious whether they're going to call it severe enough to count as needing a rollback
 but if this issue extends to OTHER packages i.e. my packages i'mma be angry as heck
 Literallly nothing we can do but wait. Vorlon already said there's going to be a number of packages that are going to have to be rebuilt due to this regresison.
 It's affecting anything that dropped into -proposed within the past 18 hours or so.
 odd that it's only on amd64 and risc
 i'd expect it to explode global
 I agree. Two completely different architectures with the only thing in common is that they're 64-bit.
 well why not arm64 then too :P
 just sayin
 Exactly. There's no actual logic to it that I can figure out.
 well thats why i'm thinking they may roll back simply because of the severity of impact
 but meh i dunno
 more concerned about this BS in xca
 Well, risc isn't that huge of a deal because it's a new arch still in the process of being introduced, but amd64 has huge implications.
 well amd64 is global
 that's the major thing now
 @Eickmeyer are you rerunning builds?
 @teward001 I was told not to worry about it that all of the FTBFS packages (not just ours) would get rebuilt.
 yep
 vorlon inicated as much though vorlon just fired off the mspdisp builds
 so tyvm to vorlon for those
 Indeed.
 @teward001 How are you feeling today?
[22:28] <Eickmeyer> @OvenWerks: After all this time, mcpdisp is in the seed.