> APT answer: Handwave! You don't need it. You can just have multiple distributions! It is because of how we sign things - we sign collections!
This is not true at all. If you need to distribute multiple versions of the same package then all you need to do is provide multiple versions of the same package. Just get your act straight, learn how to package software, create your packages so that you can deploy them simultaneously without breaking downstream software, and you're set.
This is not apt's limitation, though.
That's true, but multiple versions of the same package is not the same as multiple versions of the same software. Debian and Ubuntu have access to multiple minor version releases of GCC and they can all coexist side by side.
The way Debian works around this is by doing "<name>-<version>" as the package name. This is a valid approach, though it makes package name discovery a bit more difficult at times...
As for multiple versions of packages in the repo, "createrepo"/"createrepo_c" (for RPM repositories) does not care.
And for Debian, "dpkg-scanpackages" can be made to not care too, using the "--multiversion" switch: https://www.mankier.com/1/dpkg-scanpackages#--multiversion
This is somewhat at your peril, as I've observed APT getting confused when it parses metadata from repositories produced by dpkg-scanpackages that allows multiple versions in the repository.
However, reprepro does not support this at all, so most deployments with semi-large Debian repositories will not have this option available to them anyway.
It seems there is a significant semantics gap between how deb packages work and what's supposed to be a package version.
In deb packages, package versions are lexicograhically ordered descriptions of a version ID that is used to guide autoupgrades.
If a packager wishes that multiple minor version releases should be present in a system then he should build his packages to reflect that, which is exactly how Python packages, and specially some libraries, do. For example, python packages are independent at the major version level but GCC packages are independent at the minor version level.
Not in a system. In a repo. Standard debian tools ( not hacked, not outside the tree, not outside the debian main tree ) do not support this.
If you have a repo with <packagename>-<packageversion> and add a package <packagename>-<packageversion1> where packageversion1 is higher than the package version, the previous version gets deleted from the repo.
Can it be worked around? Sure, you can:
a) have multiple repos. If you want to keep up to a hundred versions, you can just create a hundred repos.
b) you can redefine the meaning of a package name and incorporate the version into the name of the package.
(b) Sounds like a good solution. Except if the org decided to use something like .deb for distribution of artifacts it is probably the org that uses other software. Let's say it uses puppet, which supports Debian package management out of the box, except that now you need to change how puppet uses version numbers because as we started embedding the version name into the package name "nginx-1.99.22" and "nginx-1.99.23" became two different packages not two different versions of the same package.
This goes on and on.
That's the semantic gap I've mentioned.
Your statement is patently wrong, as deb packages do enable distributions such as Debian and other Debian-based distros such as Ubuntu to provide multiple major, minor, and even point releases through their official repos to be installed and run side-by-side .
Take, for example, GCC. Debian provides official deb packages for multiple major and minor release versions of GCC, and they are quite able to coexist in the very same system.
All it takes for someone to build deb packages for multiple versions of a software package is to get to know deb, build their packages so that they can coexist, and set their package and version names accordingly.
Through multiple repos. Not through one repo. That's why testing packages live in a separate repo. That's why security packages live in a separate repo. That's why updates live in a separate repo.
If you are using careful versioning on packaging avoiding the <packagename>-<version> as the convention you are breaking other tools, including the tools that are distributed with Debian. Puppets' package { "nginx": ensure => installed } will not work if you decided to allow nginx to have multiple versions using "nginx-1.99" as a special package name.
Wrong. The official debian package repository hosts projects which provide multiple major and even minor versions of the same software package to be installed independently and to coexist side-by-side.
Seriously, you should get to know debian and its packaging system before making any assertion about them. You can simply browse debian's package list and search for software packages such as GCC to quickly acknowledge that your assertion is simply wrong.
I have provided the challenge in another reply:
I have in a repo:
package: nginx version: 1.99.77
I need to add to the repo:
package: nginx version: 1.99.78
Both of the versions must remain in the repo. Packages must be signed. Repo must be signed. The name of the package cannot change and neither can the version number. Both of the packages must be installable using a flag that specifies a version number passed to one of the standard Debian package install tools (the tool must be in "main" collection )
What is a tool that can be used that is listed https://wiki.debian.org/DebianRepository/Setup as existing in the "main" part of the Debian? For half a point, you can use any tool listed in the wiki.
Everything else is the hand waving.
I want to have
nginx-1.99.77 nginx-1.99.78 nginx-1.99.78ehjkhk-1
in the same repo. It is not possible.
<thispackage>-<this-version>-<this-patchlevel>.architecture
The package name is <thispackage>
I need to add to the repo <thispackage>-<this-version>-<that-patchlevel>.architecture
Packages are signed and repo will be signed. At the end I should be able to install the package using the select the specific version flag without adding another repo.
I use aptly and rely on this everyday.
* gopher://jdebp.info:70/1/Repository/debian/dists/stable/
1) It is not listed in the debian wiki
2) To access the "methods" i need to install a gopher client
That's pretty much a definition of the "handwave! Workaround!"
P.S. I have implemented a workaround. It works. It is just not a solution. I should not need to assign people to resign the packages with our own keys and create utilities that would duplicate Debian tools to provide a nominal access to regular required functionality by a large organization that has packages with hundreds of dependencies and could have 5-20 versions of the apps in different production/test/validation/qa environments. Joe Random Engineer expects that his knowledge of how apt-get works, how dpkg works and how puppet works to be portable.
I'm just not going to laboriously re-type it all into Hacker News when you can just go to the published repository and see it all explicitly laid out right there in the repository itself, with the exact scripts and commands that get run to produce the very repository that you are seeing -- quite the opposite of either handwaving or workarounds.
You could get to it with an FTP or an HTTP client, too. But that would just leave you with the raw files in no particular order, rather than the annotated and organized GOPHER listings. A value-added bonus for the GOPHER version, as I said.
You don't actually have any justification at all for your claim that this is somehow impossible with Debian repositories, given that people like me are doing it with a few simple scripts and even publishing them for the world to see; and clearly neither handwaving nor workarounds for anything are required.
Second of all, you still have not provided a link to the doc that someone can read without installing a gopher client. Come on, you said you already have it!
not going to argue with the rest of your flame (others already did) but the answer to this one is
apt install debsums
Here's are some low level gems:
1. I have installed package X. I want to validate that the files that are listed in a manifest for package X have not changed on a host.
APT answer: Handwave! This is not a valid question. If you are asking this question you already lost.
2. I want to have more than one version of a package in a distribution.
APT answer: Handwave! You don't need it. You can just have multiple distributions! It is because of how we sign things - we sign collections!
3. I want to have a complicated policy where some packages are signed, some are not signed, and some are signed with specific keys.
APT answer: Handwave! You should have all or nothing policy! Nothing policy, actually, because we mostly just sign collections, rather than the individual packages
https://wiki.debian.org/SecureApt