Hi, > Are there strong reasons for `gbp import-orig --uscan` as 1 step? > > I'm asking because I want to update > https://go-team.pages.debian.net/packaging.html
Doing two commands creates extra work and extra steps to remember. Not only do you need to remember to run both commands, but you also need to pay attention to two sets of error messages and exit codes. It also introduces a point where people can accidentally make mistakes. If you look at the table at https://udd.debian.org/dmd/?team%2Bpkg-go%40tracker.debian.org#details and column "debaudit" you can see large amounts of packages with broken software supply-chain. I believe that if everyone would always run `gbp import-orig --uscan` to import, and always run `gbp tag; gbp push` immediately after upload in the same git directory all those discrepancies would go away. In my opinion the main reason mistakes happen is becaue there are too many commands to remember and to run in the Debian packaging process. In cases where there is an option to simplify, we should simplify. For reference, in https://salsa.debian.org/debian/entr/-/blob/debian/latest/debian/README.source.md I have listed the complete end-to-end workflow I use for all packages I maintain in Debian, both for the Go team and outside of it. The commands always stay the same - if a package is different, it will have a custom config in debian/gbp.conf or debian/watch etc that tools read automatically, but the commands a maintainer needs to remember still stay exactly the same. - Otto
