'build_debug_symbols' argument for the `build` XMLRPC command is fine.
DDEBs are published in the DEBUG (purpose) archive for a distribution and will be published with:
`./scripts/publish-distro.py --primary-debug` (completely separate repo using NMAF)
once we create the needed DEBUG archive (well remembered).
The new archive flag (for controlling ddeb generation) will come later, for now 'build_debug_symbols' should be hardcoded as True only for building sources in the ubuntu PRIMARY archive (and the security ppa ...).
Regarding propagating changes to `pkg-create-dbgsym` to old series, I guess we can shelve the new version directly in the chroots instead submitting it via SRU (which it won't pass, I believe).
Hi Willian,
Super-thanks for working on this task.
'build_ debug_symbols' argument for the `build` XMLRPC command is fine.
DDEBs are published in the DEBUG (purpose) archive for a distribution and will be published with:
`./scripts/ publish- distro. py --primary-debug` (completely separate repo using NMAF)
once we create the needed DEBUG archive (well remembered).
The new archive flag (for controlling ddeb generation) will come later, for now 'build_ debug_symbols' should be hardcoded as True only for building sources in the ubuntu PRIMARY archive (and the security ppa ...).
Regarding propagating changes to `pkg-create-dbgsym` to old series, I guess we can shelve the new version directly in the chroots instead submitting it via SRU (which it won't pass, I believe).