Hi,
I occasionally run into the situation that a package has been NMU'd or
otherwise updated directly into the Debian repositories,
bypassing/ignoring that a packaging git repository existed. I was
wondering what techniques other DDs use to
1) detect that the git packaging repository was bypassed/diverged?
2) bring the git repository back in sync with minimal effort?
So far, I have settled on having the deb-src for Debian sid configured
on my laptop (even though it is not running sid) and then inside the
git packaging checkout directory run for example:
gbp import-dsc --verbose --pristine-tar apt:j4-dmenu-desktop/sid
This will both check if there are any newer uploads than what git
knows about, and if needed, also download, apply and commit the
uploads using the uploader as the git author. The result of this
particular example is visible in
https://salsa.debian.org/otto/j4-dmenu-desktop/-/commit/62ea4cd6df973138e3a452b09250510da5279db4
I wanted to check if anyone knows any better techniques or mechanisms
than trying to remember to run this command manually before working on
a package?
- Otto
