Jeoren,
Thanks! I was able to get this working with your hints, but there
were some snags:
On 8/2/26 12:50 AM, Jeroen Ploemen wrote:
On Sat, 1 Aug 2026 19:17:52 -0600
Antonio Russo <[email protected]> wrote:
Hello,
Also, when I upload the new version, I will need to upload a new
source tar. Can I make it using
git archive -- ':(exclude)debian'
or is there some reason I must/should use another tool, like uscan?
You can use the normal tooling for creating or pulling in the orig
tarball, e.g. gbp or uscan, as if you were dealing with an actual new
upstream release. With just uscan, you'll probably have to manually
rename the new orig tarball to dfsg2; gbp asks what you want the
upstream version to be, providing the maintainer with the opportunity
to add the extra "2".
Unfortunately, gbp refuses to work because "package is up to date, nothing to
do."
This can be worked around by sneaking a "--force" into gbp's deb/uscan.py
call to uscan, and forcing a False return value in _parse_uptodate. Maybe
these should be incorporated into a "--force" flag?
Best,
Antonio Russo
