Details
(None) Description
Running a valid release job of release:apt-repo produces the following for the mender-client 2.5.1-build4 job:
reprepro --keepunreferencedfiles include experimental $change_file || true Skipping inclusion of 'mender-client' '2.5.1-build4-1' in 'experimental|main|arm64', as it has already '2.6.0-build1-1'. Deleting files just added to the pool but not used. (to avoid use --keepunusednewfiles next time) deleting and forgetting pool/main/m/mender-client/mender-client_2.5.1-build4-1_arm64.deb
I have not spent any real time researching the topic, but a quick google search rendered me this:
3.1) Can I have two versions of a package in the same distribution? ------------------------------------------------------------------- Sorry, this is not possible right now, as reprepro heavily optimizes at only having one version of a package in a suite-type-component-architecture quadruple. You can have different versions in different architectures and/or components within the same suite. (Even different versions of a architecture all package in different architectures of the same suite). But within the same architecture and the same component of a distribution it is not possible.
So it seems to be a limitation in the reprepo tool.
Acceptance criteria:
- mender-docs: add a note that installing the repo would always pull the latest
- Tip on how to “pin” a given version once installed, using "dpkg --set-selections" or "apt-mark hold"
- mender-dist-packages: only update APT repo on latest tags
- mender-dist-packages: publish packages for not latest tags directly on the pool