Error message when a core-dev ack is needed used to be more explicit

[Olivier Tilloy]

I just tried to publish a silo of mine which had packaging changes, and got back the following message from the train:

    "Can't publish: osomon not authorized to upload webbrowser-app"

IIRC, in previous versions of the dashboard the message was more explicit, along the lines of "need a core-dev ack for packaging changes".

Can we get the previous message back?

[Robert Bruce Park (robru)]

Strange bug coming from you, because you never had permission to publish until I changed it to the way it is. So you never did a publish and got the message "needs ACK". Only when trainguards were publishing for you would you have seen the "needs ACK" message.

This change happened because the train is now forcing proper archive upload permissions, at least when there's no packaging diff (it used to just be honor system, which is why only blessed trainguards could do it).

I'm not really sure why this matters, whether it says "not authorized" or "needs ACK" either way you need to go get a core dev to ACK it. It means the same thing.

[Olivier Tilloy (osomon)]

I didn’t say that I was ever able to publish myself :)
But now I am (thanks for this useful functionality!), and I find the error message not very clear. It’s really not a big deal, but if possible it would be helpful to know the exact reason why I need a core-dev ack.

[Olivier Tilloy (osomon)]

If not easily "fixable", feel free to mark invalid, I can live with the error message as it is today.