$
tar xvf set_7.4.5.orig.tar.gz
[...]
social-engineer-toolkit-7.4.5/src/wireless/wifiattack.py
$
cp -a set-7.4.4/debian social-engineer-toolkit-7.4.5/debian
$
cd social-engineer-toolkit-7.4.5
$
dch -v 7.4.5-0buxy1 ”New upstream release”
That’s it. You can now build the updated package.
Depending on the kind of changes that the new upstream version introduces, you may also need
to change build dependencies and run-time dependencies, and install new files. Those are much
more involved operations that are not covered by this book.
9.1.4. Starting the Build
When all the needed changes have been applied to the sources, you can start generating the actual
binary package or
.deb
file. The whole process is managed by the
dpkg-buildpackage
command
and it looks like this:
$
dpkg-buildpackage -us -uc -b
dpkg-buildpackage: source package libfreefare
dpkg-buildpackage: source version 0.4.0-2buxy1
dpkg-buildpackage: source distribution UNRELEASED
dpkg-buildpackage: source changed by Raphael Hertzog
dpkg-buildpackage: host architecture amd64
[...]
dh_builddeb
dpkg-deb: building package ’libfreefare0-dbgsym’ in ’../libfreefare0-dbgsym_0.4.0-2buxy1_amd64.deb’.
dpkg-deb: building package ’libfreefare0’ in ’../libfreefare0_0.4.0-2buxy1_amd64.deb’.
dpkg-deb: building package ’libfreefare-dev’ in ’../libfreefare-dev_0.4.0-2buxy1_amd64.deb’.
dpkg-deb: building package ’libfreefare-bin-dbgsym’ in ’../libfreefare-bin-dbgsym_0.4.0-2buxy1_amd64.deb’.
dpkg-deb: building package ’libfreefare-bin’ in ’../libfreefare-bin_0.4.0-2buxy1_amd64.deb’.
dpkg-deb: building package ’libfreefare-doc’ in ’../libfreefare-doc_0.4.0-2buxy1_all.deb’.
dpkg-genchanges -b >../libfreefare_0.4.0-2buxy1_amd64.changes
dpkg-genchanges: binary-only upload (no source code included)
dpkg-source --after-build libfreefare-0.4.0
dpkg-buildpackage: binary-only upload (no source included)
The -us -uc options disable signatures on some of the generated files (
.dsc
,
.changes
) because this
operation will fail if you do not have a GnuPG key associated with the identity you have put in the
changelog
file. The -b option asks for a “binary-only build.” In this case, the source package (
.dsc
)
will not be created, only the binary (
.deb
) packages will. Use this option to avoid failures during
the source package build: if you haven’t properly recorded your changes in the patch management
system, it might complain and interrupt the build process.
As suggested by
dpkg-deb
’s messages, the generated binary packages are now available in the
parent directory (the one that hosts the directory of the source package). You can install them
with
dpkg -i
or
apt install
.
$ sudo apt install ../libfreefare0_0.4.0-2buxy1_amd64.deb \
