On Mon, 29 Dec 2014, Vasudev Kamath wrote:
> I've included mv_conffile change you suggested and changes
> reflected back in git. And piuparts test shows no obsolete files left
> back which is good :).
Hmm, did you rewrite the history of the git repo? Pulling into master
suddently gives merge conflicts?
And, I *THINK* the version number in
debian/maintscript
is wrong... You put
1:4.4.4r2-6~
for the release that will be -5.
man dpkg-maintscript-helper tells me that
For example, for a conffile removed in version 2.0-1 of a pack‐
age, prior-version should be set to 2.0-1~. This will cause the
which would mean that we have to set it to
...-5~
The version is defined as:
prior-version
Defines the latest version of the package whose upgrade should
trigger the operation. It is important to calculate prior-ver‐
with -6~ we would mean that an
upgrade -5 -> -6
would also trigger the action, right?
All the best
Norbert
------------------------------------------------------------------------
PREINING, Norbert http://www.preining.info
JAIST, Japan TeX Live & Debian Developer
GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
------------------------------------------------------------------------
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
