Re: NSLS-II Debian Repository in 2018

[Anton Derbenev <aaderbenev@gmail.com>]

Hello Ralph, Martin,

thanks for your comments and insights. I get a bit jealous every time I see "bottom-to-top" setups with CIs, push triggering, automatic testing and such - that is until I imagine something goes wrong and, say, a malformed input just drags a trace through the entire setup. Even if that doesn't break production right away, cleaning things up may be troublesome. That of course can be prevented by proper tuning and maintenance of the delivery mechanism, and it is great when there is an appropriate effort put into that.

What different in the "FRIB version numbers" is that upload comes before distribution - doesn't it mean that a recent upload for, say, jessie will sort as newer when compared to an older upload for stretch? And the system will consider it to be newer if it sees both.

As Ralph noted, the deployment part is not always a fluent connection - especially with all the legacy we have in place. Having 'bleeding edge' builds with git-hash-derived versioning would open up even more questions about what to do with that further... perhaps eventually we may get to that.

Anton.