Page MenuHomePhabricator

Upload zuul_2.5.1-wmf10 to apt.wikimedia.org
Closed, ResolvedPublic

Description

A patch I have done to Zuul for T203846 turned out to be absolutely wrong. I thus replaced the patch entirely with a new version:

rCIZUa205e358263e
https://gerrit.wikimedia.org/r/536689

I have build the package and passed it through deb-diff and compared the package content (diffing output of dpkg-deb -c).

The new package is for jessie-wikimedia/main and I have uploaded it at https://people.wikimedia.org/~hashar/debs/zuul_2.5.1-wmf10/

Note: documentation has to how the package is build is at https://www.mediawiki.org/wiki/Continuous_integration/Zuul#new_package . It relies on dh-virtualenv which would fetch missing python modules from Pypi. Has such:

  • .pbuilderrc has to contain USENETWORK=1
  • The build is not reproducible at all

The resulting Debian package has to be carefully examined for differences. Which @hashar done for the package published on people.wikimedia.org

Once uploaded I will take of deploying it to contint1001 and restarting the service.

Event Timeline

Hi @herron, others have pointed me to you for this task since you are on ops clinic duty. The package can't really be rebuild on the SRE box since it requires network access and would vary due to the installation of python dependencies from https://pypi..org/ . It is legacy and a bad practice, but that is predates a lot of changes we have done since (such as using scap, components in apt.wikimedia.org etc).

The doc to build it is https://www.mediawiki.org/wiki/Continuous_integration/Zuul#new_package

The package I have published on people.wikimedia.org has followed that doc and I have carefully compared it with the previous version (extract, run diff, assert that python dependencies have not changed etc). So I guess the one I have build is probably safe enough ;]

Hey @hashar, zuul_2.5.1-wmf10 has been uploaded for jessie-wikimedia:

zuul | 2.5.1-wmf10 | jessie-wikimedia | amd64, source

Aiui there are some thoughts about how to improve how/where this package is maintained and built, and so we might want to capture those for follow up in longer-term tracking tasks if we haven't already.

At any rate, I'll transition this to resolved since the original ask has been done. Please re-open if any follow up is needed. Thanks!

herron claimed this task.