Hi, The ci.debian.net nodes are managed with chef, and during the weekend I realized that it was not in testing. There was an RC bug against chef (FTBFS, 3 tests broken by an update to the test framework, package just worked nevertheless) and ruby-cheffish (broken by openssl 1.1.1). I fixed both, and uploaded ruby-cheffish Saturday night and chef Sunday morning. ruby-cheffish migrated to testing before the freeze, but chef didn't even though they have a pathological circular build dependency, so ruby-cheffish can't be built in buster at the moment: The following packages have unmet dependencies: builddeps:ruby-cheffish : Depends: chef but it is not installable E: Unable to correct problems, you have held broken packages.' Maybe this a bug in britney; it should have migrated either both or none of them, but not one without the other. This needs to be fixed somehow. I would very much prefer to have chef migrate, since 1) that would make my life maintaining ci.debian.net much easier and 2) it will save a lot of Debian users the pain of not having chef in stable. OTOH I realize chef was fixed too late, so if it's unacceptable to have it in buster, ruby-cheffish needs to be removed. Thanks in advance.
Attachment:
signature.asc
Description: PGP signature