From Kolab, To Youhttps://git.kolab.org/phame/blog/feed/1/2019-03-27T18:05:42+00:00by the Senior Solutions ArchitectOBS Signatures Fixedhttps://git.kolab.org/phame/post/view/11/vanmeeuwen (Jeroen van Meeuwen)2019-03-27T18:05:42+00:002019-03-27T18:05:42+00:00

Recent reports have shown how our upgrading of the OBS had caused previous fixes to get lost again.

I'm happy to report another series of out-of-bound patches has seemed to resolve the problem.

The crux of the issue seems to be OBS's assumption to use those hashes considered valid only under such specific circumstances, that upstream has not yet realized any of the downstream scenarios, and that therefore downstream patching is required. However, we also required an upgrade of the OBS over 'enhanced dependencies'.

Upgrading Phabricator, September 2015 Editionhttps://git.kolab.org/phame/post/view/5/vanmeeuwen (Jeroen van Meeuwen)2015-09-08T10:45:51+00:002015-09-08T10:52:28+00:00

I'm planning to upgrade Phabricator on git.kolab.org this weekend (12-13 September).

As you may be aware, Phabricator consists of various components, including:

  • arcanist,
  • libphutil,
  • phabricator,
  • the sprint extension.

In order to achieve this, I will need to;

  1. shut down the web server,
  2. shut down the SSH server,
  3. shut down the phabricator daemons,
  4. shut down the notification server,
  5. record the current revision for arcanist, libphutil, phabricator and the sprint extension,
  6. export the MySQL database,
  7. pull in the changes for arcanist, libphutil, phabricator and the sprint extension,
  8. run the upgrade procedure for Phabricator's storage,
  9. start the phabricator daemons,
  10. start the notification server,
  11. start the webserver,
  12. test if the web interface works as expected;
    • if not, roll back all the changes and re-import the aforementioned export,
  13. start the SSH server,
  14. test if the SSH server works as expected,
    • if not, roll back all the changes and re-import the aforementioned export.

This is quite the checklist -- and I'm omitting the parts where I actually test stuff -- but it is necessary to ensure the platform continues to work as well as it does -- and hopefully better.

As a secondary attempt, should the first one (that follows each respective master branch) fail, I plan on executing the same checklist again but with the stable branches.