Hi, Quoting Benjamin Drung (2026-06-25 11:10:37) > I thought about it. We should handle security.ubuntu.com separately. It might > be useful to use resolute-security from the mirror that you specified and > have security.ubuntu.com as fallback. So > > ``` > mmdebstrap --suites="%s %s-updates %s-security" resolute resolute.tar > http://my.mirror.example/ubuntu > ``` > > would create: > > ``` > deb [signed-by="/usr/share/keyrings/ubuntu-archive-keyring.gpg"] > http://my.mirror.example/ubuntu resolute main > deb [signed-by="/usr/share/keyrings/ubuntu-archive-keyring.gpg"] > http://my.mirror.example/ubuntu resolute-updates main > deb [signed-by="/usr/share/keyrings/ubuntu-archive-keyring.gpg"] > http://my.mirror.example/ubuntu resolute-security main > deb [signed-by="/usr/share/keyrings/ubuntu-archive-keyring.gpg"] > http://security.ubuntu.com/ubuntu resolute-security main > ``` > > What do you think?
is the main purpose of the --suites option with %s placeholders you propose to add security mirrors? If yes, I am in the process of overhauling the way in which mmdebstrap selects default suites and mirrors for distributions including Debian ports and Debian derivatives. If mmdebstrap would automatically add security and updates suites for a Ubuntu stable release, which use-case for the --suites option would remain and would the remaining use-case warrant a new option? Thanks! cheers, josch
signature.asc
Description: signature
