Skip to content

Instantly share code, notes, and snippets.

@lrlna
Last active July 29, 2020 08:12
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save lrlna/0b824cd89a5887b80eab0d6783cbe598 to your computer and use it in GitHub Desktop.
Save lrlna/0b824cd89a5887b80eab0d6783cbe598 to your computer and use it in GitHub Desktop.
Requirements for Apt uploads

Package Requirements for Apt

  • Changelog file to live in DEBIAN/changelog. changelog file can be added to mongosh repo root. pkg-deb can then copy it over to its internal DEBIAN dir. Format should be as follows:
package (version) distribution(s); urgency=urgency
  [optional blank line(s), stripped]
  * change details
  more change details
  [blank line(s), included in output of dpkg-parsechangelog]
  * even more change details
  [optional blank line(s), stripped]
-- maintainer name <email address>[two spaces]  date
  • Package needs to be tested for Debian standards.
  • Package needs to have a control file with essential information about the package, like version, maintainer, desciption.
  • Maintainer field allows only for one maintainer. Use team as a maintainer.
  • Description/ProductDescription needs to be adjusted to Debian standards.
  • Update to a more eloquent description before sending to mentors.debian.net, so it'll be easier to find a sponsor.
  • Package needs to have LICENSE files of all 3rd party packages being used. This might need to be generated in build by looking at all package.json in ./packages and extracting LICENSE files from all packages in dependencies.
  • Package should have a readme. pkg-deb should copy over mongosh readme from root into DEBIAN/README.

Uploading Package to Apt

Instructions on Publishing a Package and adding it to mentors.debian.net.

Uploading to mentors.debian.net can be done via FTP, which means we can automate this process from our build.

Every package uploaded needs a mentor, or a sponsor, that is a member of the Debian Community who will verify and approve your package added to the Debian repository.

Verification of our package will have to happen with every patch release. That is, we are unable to be the ones uploading the pacakge, the sponsor uploads the package.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment