I've committed code to dissociate quirks from the pkg update-cache. It is actually fairly transparent: it just handles quirks like other packages (it can have dependencies!)
If you don't update, quirks may not install properly, along with the future updatedb. If you're running snapshots, hopefully this will trickle down on all architectures SOON (within a week or two). I do intend to commit the actual split in a week or so. Technically, this makes it much easier for people to test quirks changes WITHOUT having to rebuild a full ports tree and create the updatedb, since it's going to be a separate package (and quirks depends on it). Also technically: I added an @option updatedb to tag the actual package that contains the updatedb near the end of 2023. I've waited a few weeks before actually adding @option updatedb to quirks (this is current, right, so you're supposed to update). The actual split is going to be way more silent: if your base snapshot is not uptodate, all that's gonna happen is that you're going to lose quirks+updatedb for a few updates... It's not a big change, so I'm taking my time, but it's definitely helpful for developers who want to test things. Kudoes to the guy (sorry, didn't note down your name) who brought that specific issue to my attention. Very soon, your problem will be solved !