Guido Günther <a...@sigxcpu.org> writes:
[...] >> git-dch only increases the version found in debian/changelog or uses the >> “--new-version” command line option for native packages. > > Should this read non-native packages? No, the sentence was not very clear, I try to say: “we can bump version number of native package only with the --new-version option”. >> I wonder if the limitation[1] of using upstream-tag to non native >> packages could not be removed. > > [1] links to the whole dch.py script which doesn't unconfuse me. I > assume you want to see the changelog updated for _native_ packages as > well? We currently only do this for _non_native_ packages. Sorry, I pointed the line 466, where “guess_version_from_upstream()” was called, here the link is opened with the focus on the line 466. > Both of these won't work since we need to pass in options.debian_tag in > the native case. I'm not sure to understand this, I proposed to use “options.upstream_tag” in native case too. My use case is to bump version number, for example in the case of git-buildpackage: - now is at 0.6.13 - next call to “git-dch -a -R” will do 0.6.14 - we must call “git-dch -N 0.7.0” to bump version to 0.7.0, here I want to use “options.upstream_tag” to avoid passing “-N” > Since we now have GitVfs we don't need to know if it's native or not > upfront but can handle all the details in > DebianGitRepository.debian_version_from_upstream. > > Does this make sense? It looks to me. Regards. -- Daniel Dehennin Récupérer ma clef GPG: gpg --recv-keys 0xCC1E9E5B7A6FE2DF Fingerprint: 3E69 014E 5C23 50E8 9ED6 2AAD CC1E 9E5B 7A6F E2DF
signature.asc
Description: PGP signature
