On Thu, Oct 24, 2024 at 09:36:04PM +0100, Otto Kekäläinen wrote: > 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?
What's the problem here? You can simply assume that a NMU wasn't committed but if you really need to check you can look at the tags and/or debian/changelog? > 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 If gbp import-dsc works then I don't think there is a better way. I thought you are asking about repos that have changes committed into them since the previous maintainer upload, but I don't think there is an automated way to update those. -- WBR, wRAR
signature.asc
Description: PGP signature
