I was given a backport ACL bit, and have uploaded the package below. I would still appreciate any review from experienced backporters, or comments regarding how to deal with the -v flag (see below) -- to me it seems the documentation on the Contribute-page is incomplete. /Simon Simon Josefsson <simon@josefsson.org> writes: > Hello. > > I have prepared jabberd2 for jessie-backports and have uploaded it to > mentors: > > http://mentors.debian.net/package/jabberd2 > > Packaging is also available via git: > git://anonscm.debian.org/pkg-xmpp/jabberd2.git > > I built the package like this: > gbp buildpackage --git-pbuilder --git-pbuilder-options=--twice > --git-debian-branch=jessie-backports --git-dist=jessie > > It is based on the version that just entered testing. No bpo-specific > changes at all. > > Would you like to review and upload? > > I'm still waiting for my backports ACL to do uploads on my own, but for > my first uploads, I would appreciate review so I understand the process. > > As you can see from mentors, there is a lintian > backports-changes-missing warning related to -v and I'm not sure how to > deal with this. Reading http://backports.debian.org/Contribute/ says: > > Include all changelog entries since the last version on > debian-backports or since stable if it's the first version. You > should do this by passing "-v" to dpkg-buildpackage. Eg: "debuild > -v0.7.5-2", where "0.7.5-2" is the version in stable. If the package > wasn't in stable or backports before you don't have include the > changelog entrys (but you are free to do so). > > However, jabberd2 is not in stable nor debian-backports. What should be > done in that case? It doesn't say, so I didn't do anything. > > Thanks, > /Simon >
Attachment:
signature.asc
Description: PGP signature