Conversation
|
Will this leave us in the 'never ran upgrade' position? |
|
More like a "Only run upgrade manually" situation - the problem is that automatic upgrade of all software on the machine has big implications, and often creates complex problems. This upgrade has causes issues in Travis with mongodb, rsyslog, and postgres, and they are annoyingly complex issues (like upgrade seems to re-install the postgres version that we expressly uninstalled, then try and start it, which fails because an older version is running or something crazy like that) |
|
Basically, if a human is there to understand what to do when apt-get upgrade fails and dpkg starts refusing to do anything more, then sure you can upgrade. Otherwise....it's a PITA |
|
Travis build - not yet started as of this commit. |
|
This one was actually scheduled correctly on the main queue. I think a lot of them were (see here) they just were not hyperlinked from the pull requests because travis didn't have write permission on the organization |
|
whoops- thanks @hamiltont |
|
So travis finished, and the only two differences from the latest full build on master are
I'm hoping to merge this, thoughts? |
|
As an added bonus, this drops about 2 hours off the total travis build time :-P |
|
|
|
Sadly, I have confirmed that So the only test affected by this PR appears to be nodejs, which now passes. |
Toolset: Do not apt-get upgrade
Increases stability of our scripts by avoiding unexpected upgrades
Fixes #1369
Fixes #1139