Hi, On Tue, Dec 13, 2022 at 03:00:09PM +0100, Roland Mas wrote: > Le 29/11/2022 à 17:19, Guido Günther a écrit : > > Hi, > > On Tue, Apr 26, 2022 at 03:11:42PM +0200, Roland Mas wrote: > > > Package: git-buildpackage > > > Version: 0.9.22 > > > Severity: wishlist > > > > > > There are cases where "gbp import-orig --uscan" exits with a no-op > > > although a new upstream version should be available: > > > - a new repack level in d/watch; > > > - new subcomponents in d/watch; > > > > > > In both cases, the new "upstream" part of the version number is > > > actually increased (either with +dfsgX or +~csX.Y.Z if using > > > subcomponents), but to get there you have to perform the ugly trick of > > > setting the latest version number in d/changelog to 0, then running > > > gbp import-orig --uscan, then changing the version number back to its > > > previous value. > > > > > > I think a "gbp import-orig --uscan --force" option would be a nice > > > addition; it should be a simple matter of running uscan with -ddd. > > Does giving the version explicitly do the trick for you? > > > > gbp import-orig --uscan --upstream-version=0.23.0~rc1 > > > That trick works, thanks. I still think a --force option would be nice, but > I can live with that workaround.
Great that this works for you! I'm not objecting to a `--force` option it's just unlikely that I get to add something like this soon. Cheers, -- Guido > > Thank you! > > Roland. >
