Bug#1010207: import-orig: please provide a --force option
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. >
Bug#1010207: import-orig: please provide a --force option
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. Thank you! Roland.
Bug#1010207: import-orig: please provide a --force option
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 Cheers, -- Guido
Bug#1010207: import-orig: please provide a --force option
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. Thanks, Roland. -- System Information: Debian Release: 11.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-13-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_WARN Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages git-buildpackage depends on: ii devscripts 2.21.7~bpo11+1 ii git1:2.30.2-1 ii man-db 2.9.4-2 ii python33.9.2-3 ii python3-dateutil 2.8.1-6 ii python3-pkg-resources 52.0.0-4 ii sensible-utils 0.0.14 Versions of packages git-buildpackage recommends: ii cowbuilder0.89 ii pbuilder 0.231 ii pristine-tar 1.49 ii python3-requests 2.25.1+dfsg-2 Versions of packages git-buildpackage suggests: pn python3-notify2 ii sudo 1.9.5p2-3 ii unzip6.0-26 -- no debconf information
