On Thu, 2015-06-04 at 19:45 -0500, Jimmy Berry wrote:
Based on that explanation I am confused how this situation could have arose. As I understand it the following would have had to occur for boost to be updated in tumblweed.
- factory snapshot created - automated tests run against factory snapshot - tests passed and tumbleweed snapshot released
We have two things called 'snapshot' which is what the confusion is. 1) the 'snapshots' of Tumbleweed that are released to the public. That's once packages are checked into Factory, they pass openQA, then we release a snapshot 2) openSUSE:Factory/snapshot (a more static build target compared to openSUSE:Factory/standard). This is totally unrelated to the snapshots above (even though the name might imply). Based on various parameters (the main devel repos being idle, openSUSE:Factory build completed, the right machine/script running), this snapshot is being updated. At the moment, though, the last part is an issue (the machine running the script disappeared on us). As far as I know, this was running on coolo's machine, who happens to have gone on holiday (back next week). This is certainly a script we will be moving to a more central place asap. As coolo will be back soon, we can expect this process to be recovering normal operation as well. Not the help expected for now, but at least this gives some backgrounds what went wrong and we have a plan to correct the situation. -- Dimstar / Dominique Leuenberger <dimstar@opensuse.org>