For debian packages there is no (technical) restriction to which platform they can be installed, other than maybe dependencies. Sometimes the debian release a package was built for is part of it's version string. What a specific host gets depends primarily on the repositories he has configured. And apt-style repositories are organized in releases. However the support for those releases is not fully implemented in pulp_deb atm. My advice would be that you can sync multiple releases into one pulp_repo and publish them with the `structured` flag. If you want to add selfmade packages, add them to a separate repositories (one for each release) and publish with `simple`.
About deleting old publications: As long as you keep them around, you can roll back your distribution to it in an instant. On Tue, May 19, 2020 at 11:45 AM Dennis Kliban <[email protected]> wrote: > > I am not very familiar with Debian/Ubuntu packages but I can speak for RPMs. > When you list or read a single RPM package[0], you can look at the 'release' > field to determine which distribution it was built for. The release is > usually an integer followed by the platform. e.g. "1.el7" or "3.f24". > > [0] > https://pulp-rpm.readthedocs.io/en/latest/restapi.html#operation/content_rpm_packages_read > > > On Tue, May 19, 2020 at 4:07 AM Christoph Höger > <[email protected]> wrote: >> >> Dear all, >> >> I just finished setting up a prototype apt repository using pulp_deb on >> pulpcore 3.3. Now If I understand the workflow documentation correctly, to >> publish a package one has to do these steps: >> >> 1. Upload content >> 2. Create a new repository version (can be done automatically on upload) >> 3. Create a new publication >> 4. Update the distribution to the new publication >> 5. Delete the old publication (here I am not sure if and when this makes >> sense) >> >> While this is somewhat involved, I guess it will work just fine for a single >> repository. But we support at least two different versions of Ubuntu (and >> similarly Redhat) so I wonder how I would disambiguate these different >> platforms. >> >> In particular, when uploading a package the build job knows it is package >> foo, version x.y for platform Z. Package name and version are obviously >> encoded in the package itself, but I see no way to disambiguate the same >> package for Ubuntu 18.04 and 20.04, like a subfolder or some kind of tag. >> >> Is there a typical way to disambiguate these packages by the platforms they >> were built for? >> >> Thanks, >> >> Christoph >> -- >> Christoph Höger >> >> CeleraOne GmbH >> Usedomer Straße 4 >> 13355 Berlin >> >> Email: [email protected] >> Web: www.celeraone.com >> >> Sitz der Gesellschaft: Berlin >> AG Berlin-Charlottenburg HRB 142747 >> Geschäftsführer: Moritz Hilger, York Walterscheid >> _______________________________________________ >> Pulp-list mailing list >> [email protected] >> https://www.redhat.com/mailman/listinfo/pulp-list > > _______________________________________________ > Pulp-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/pulp-list _______________________________________________ Pulp-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/pulp-list
