Reprepro Release Recipe

Montuer has a continuously developed release recipe dedicated for reprepro, a decentralized deb package distributions.

The objective is simple: to quickly and steadily upstream the built .deb packages in a consistent, secured, and seamlessly easy manner.

All users has to do is to issue this command:

1

monteur release

Resources

This recipe is built and maintained based on the following resources:

• Debian Reprepro Setup Specification - https://wiki.debian.org/DebianRepository/SetupWithReprepro

• Monteur Release Data Structure - https://monteur.zoralab.com/en/ci-jobs/release/

One-Time Setup

Reprepro requires a ONE-TIME (1) setup to meet its minimal requirements. This 3rd-party software ONLY works on linux operating system. Its specifications is available at https://wiki.debian.org/DebianRepository/SetupWithReprepro.

The first thing to do is to create a persistent data directory for it to house its workspace and configuration data. All you need to do is:

1. Create the conf/distributions file in your data directory (.DataDir). The content of the file is as such:

   1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26

   Origin: monteur.zoralab.com/releases/deb Label: ZORALab's Monteur Deb Package (Main Branch) Codename: main Suite: stable Architectures: amd64 Components: stable Description: software manufacturing automation tool in one single app. SignWith: [email protected] Origin: monteur.zoralab.com/releases/deb Label: ZORALab's Monteur Deb Package (Staging) Codename: staging Suite: unstable Architectures: amd64 Components: unstable Description: software manufacturing automation tool in one single app. SignWith: [email protected] Origin: monteur.zoralab.com/releases/deb Label: ZORALab's Monteur Deb Package (Next) Codename: next Suite: experimental Architectures: amd64 Components: experimental Description: software manufacturing automation tool in one single app. SignWith: [email protected]

• Origin

  1. The distribution URI where users source the packages from (and added into /etc/apt/source.list.d) directory.

• Label

  1. Name of the package series.

• Codename

  1. controlled field.

  2. When in doubts, denotes it to your branch name.

• Suite

  1. Debian distribution suite. Please refer to the operating system manuals for compliant names.

  2. When in doubts, sticks to stable, unstable, or experimental.

• Architectures

  1. Supported CPU architectures separated by space ( ). Example: amd64 arm64 i386.

  2. Please refers to operating system manuals for accepted values or refer to Debian MultiArch Specification.

• Components

  1. Distribution components.

  2. When in doubt, keep it to the same as Suite.

• Description

  1. Abstract of the package.

  2. When in doubt, use your App.Abstract data.

• SignWith

  1. Your GPG signing key ID.

The above shall make your user to add your sources.List in the following pattern:

1
2
3
4

deb https://{{- .Origin }} {{ .Codename }} {{ .Components }}

# example above:
deb https://monteur.zoralab.com/releases/deb main stable

1
2
3
4
5
6

{{ .AppName }}/{{- .Suite }} {{ .PkgVersion }} {{ .PkgArch }}
  {{ .Description }}

# example above:
monteur/stable 0.0.1 amd64
  software manufacturing automation tool in one single app.

Recipe File

Here are all the Monteur Release CI Job recipe files for operating Reprepro semi-autonomously. They are sorted by the latest version first, at the top.

Please read through its requiremnets and changes before procuring.

Epilogue

That's all for Monteur's Release CI Job handling Reprepro release distribution system. If you have any question, please feel free to raise your question at our Issues Section.