Regarding man pages: siso doesn't change its CLI frequently, so I will choose this man page for now. I will look for how to contribute to the Gerrit Chromium repo afterwards. Hopefully, that's ok.
> Commit 4a19ff16968ee87c112c615288c9e749a61ffeaa touches on several > non-debian/ files, could you back those changes out? Fixed. The source tree now matches the orig tarball. https://salsa.debian.org/mendezr/siso/-/pipelines/1081785 Green builds. Question regarding pipelines in salsa: - I provided a debian/salsa-ci.yml, but I think the team has a different way of triggering pipelines. What is the common procedure for go-team repositories? - Should I keep the extra architecture flags in salsa-ci.yml (arm64, armhf, ppc64el)? Right now, my fork doesn't have available runners. Question on the gbp workflow for +ds packages: I'm creating the orig tarball manually (upstream subtree archive + LICENSE file), importing with gbp import-orig --pristine-tar, and relying on the Salsa CI fallback path (pristine-tar + --git-overlay). Is this the expected workflow, or is there a better approach for packages where the orig tarball is a manual repack? Thanks, Juan
publickey - [email protected] - 0xE697CF1F.asc
Description: application/pgp-keys
signature.asc
Description: OpenPGP digital signature
