Re: libnftnl for jessie-backports
Hi Arturo,
On Tue, Apr 28, 2015 at 7:37 AM, Arturo Borrero Gonzalez
<arturo.borrero.glez@gmail.com> wrote:
> Hi there!
>
> I plan to include and maintain nftables in jessie-backports.
> The first step is libnftnl, which i'm sending now.
>
> I've uploaded the package to mentors.d.n [0]. Would you like to review
> and upload?
Your mentors.d.n package includes an orig tarball that's different
than the one already in the archive, which is not allowed for the same
upstream version of any given package. I've gone ahead and replaced
that orig tarball with the one already present in the archive, then
uploaded your package. Thanks for your work!
> The package was build this way:
> % dpkg-buildpackage -tc -sa
It doesn't matter now since I'm building and uploading the package
myself, but once you're a DM and you start uploading your own packages
to backports, you may want to take note of the (recommended, but not
mandatory) rule [1]:
"It is recommended to 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). It helps others to
follow the changes introduced with the backport (by reading the
changes mailinglist)."
Also, unless you're already calling dpkg-buildpackage inside a clean
jessie chroot, do note that you should be building packages in a clean
environment, and that's easiest to do with tools like
pbuilder/cowbuilder/sbuild. I'm sure you're already aware of this
however. :)
Regards,
Vincent
[1] http://backports.debian.org/Contribute/
Reply to: