The third-party repository story is clearly defined how it should work: For providers:
For single package repositories, a single .deb should be provided that contains the program, the key in trusted.gpg.d, and a sources.list.d snippet. For multi-package repositories, a .deb should be provided that contains the sources.list.d snippet, and the key in trusted.gpg.d. This config deb should be shipped in that archive, so the archive key can be rotated. It could be named myrepo-config, for example. The key shall have the same name as the sources.list.d snippet (e.g. myrepo.gpg and myrepo.list) For users: Single package: User installs and is done Multi-package: User installs config package, than uses apt update and apt install to install the packages. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835645 Title: apt sources should be able to understand release variables To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1835645/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
