Hi all,
After quite some time, I was finally able to work again on the package,
and I've got some questions:
- I'm not sure why, but I guess when I've imported 0.2.9 into git, I
forgot to do 'git push --all', instead I did 'git push', if I remember
correctly.
If I'm now building the package, I get:
dpkg-source: info: local changes detected, the modified files are:
ruby-mail-gpg-0.2.9/History.txt
ruby-mail-gpg-0.2.9/lib/mail/gpg/version.rb
ruby-mail-gpg-0.2.9/test/test_helper.rb
Later I fixed the upstream and pristine-tar branches manually,
however, it seems, this wasn't correct. dpkg-sources gives me the
advice to use dpkg-source --commit, which I didn't use, because it's
obviously not the correct way to do in this situation.
If I switch to the gbp export-dir, and do:
wget https://github.com/jkraemer/mail-gpg/archive/0.2.9.tar.gz -O ruby-mail-gpg_0.2.9.orig.tar.gz
dpkg-source is happy and the build succeeds.
I guess there is something wrong in either the upstream or
pristine-tar branches, but I can't figure out what on my own.
- Also, I've got a question about the Maintainer: and Uploaders: fields
in debian/control, because of lintian errors:
- If I put the team name and email into Maintainer:, lintian exits
with error because this doesn't match debian/changelog. According to
lintian, this is a NMU upload then, with the version number being
incorrect. Also this should then be reflected in the changelog.
- I've tried to put both the team name and myself into Maintainer:,
but it seems the field is just single, not accepting multiple
values.
- I've tried to put the team into Maintainer: and myself into
Changed-By:, but this didn't made lintian happy either.
- So, for now, I put myself into Maintainer:, and the team into
Uploaders:, which is not correct as well I think, because up until
now I'm not sure who will do the upload.
- So, again, I'm not sure how to deal with this.
Any input appreciated, thanks in advance and for your work!
All the best,
Georg
Attachment:
signature.asc
Description: Digital signature