Hi Konstantin, On Tue Mar 11, 2025 at 7:34 PM CET, Konstantin Ryabitsev wrote: > On Mon, Mar 10, 2025 at 05:31:32PM +0100, Antonin Godard wrote: >> > And now I noticed you used b4, so I really do not get how the tags can >> > be missing here. :/ >> >> Sorry, that's totally my fault here, I forgot to run 'b4 trailers -u' before >> sending... :/ And I don't think it's part of the prep checks? > > Mostly, because there's no clear picture of how this would work reliably. All > other checks are on a "ran since modifications to the series" basis, but this > one would have to be time-based. > > Should it check if the trailer updates have been run in the past XX minutes > (and how long should that XX be?). Had some thoughts about this the past few days. What about checking if it was run at least once between vX and vX+1? Maybe during the `b4 send` command? In case it wasn't run, give a hint/warning to the user before proceeding? This could also be enforced with an b4 config option like b4.force-trailers-update - either set by the user or the project configuration. Not so sure about this one though... Now if I were to speak for myself, I would love to have an option that just fetches the new trailers during `b4 send` and errors out / warns me about it if there's anything new that isn't part of my series. Which could be also ignored with --ignore-trailer-errors or something like that, in any case. Antonin -- Antonin Godard, Bootlin Embedded Linux and Kernel engineering https://bootlin.com
