Hi Steve, You said: ~~~~~~~~~~~~~~~~~~~~~~~~~ Picking and choosing specific versions of packages from the archive as INPUT into the ISO, as opposed to taking the most recent version of packages at the time the ISO is built, would simply enable bad practices (omitting security updates) and lure users into not feeding back into Ubuntu information about SRU regressions that should be addressed for all users, not on a per-customer basis. ~~~~~~~~~~~~~~~~~~~~~~~~~
But this is exactly what they want, so we must provide them some kind of solution where they can cook their own ISO with packages and versions that are currently used by them in the multitude of deployments at their own customers In the real world, customers don't have the latest version of packages, but instead they have a snapshot of versions captured at some point time in the past, and when they publish a certain release of their product to their customer, then these versions must be kept intact, because all the development and testing was based on these specific versions, you can't just tell them to upgrade to the latest and greatest, when they spent months to test their solutions on this snapshot of package versions. This is Telco world, they can't just jump from one day to another with package version, as I said it takes a lot of time to do a thorough testing before they release a product to their customer -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923590 Title: Telco Customer needs Minimal ISO with customizable set and versions of packages To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1923590/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
