I ran into the same problem for a while. There’s been multiple reports about
this breakage recently in the alias. Keith gave a recommendation a week ago.
But it didn’t work for me either. Until the real solution/fix is available, I
figured out a workaround myself and it is good enough for me. I changed the
rules file to use python3 instead of python2 because that is where the error
is. Again, this is not a fix, just my hack to workaround the problem.
diff --git a/build-root/deb/debian/rules b/build-root/deb/debian/rules
index 4ecd38f..66ac3e2 100755
--- a/build-root/deb/debian/rules
+++ b/build-root/deb/debian/rules
@@ -18,7 +18,7 @@ include /usr/share/dpkg/default.mk
# main packaging script based on dh7 syntax
%:
- dh $@ --with dkms --with systemd,python2
+ dh $@ --with dkms --with systemd,python3
override_dh_install:
dh_install --exclude .git
Steven
From: <[email protected]<mailto:[email protected]>> on
behalf of "Pravin Ajagekar (pajageka)"
<[email protected]<mailto:[email protected]>>
Date: Thursday, December 1, 2016 at 11:01 PM
To: "[email protected]<mailto:[email protected]>"
<[email protected]<mailto:[email protected]>>
Subject: [vpp-dev] Error while building a Debian package for VPP
Hi,
I am following steps on “VPP/Build, install, and test images” WiKi page to
install VPP.
While executing “vagrant up” I got below error.
*******************************************************
==> default: update-alternatives: using /usr/bin/emacs24-x to provide
/usr/bin/emacs (emacs) in auto mode
==> default: Install emacsen-common for emacs24
==> default: emacsen-common: Handling install of emacsen flavor emacs24
==> default: Wrote /etc/emacs24/site-start.d/00debian-vars.elc
==> default: Wrote /usr/share/emacs24/site-lisp/debian-startup.elc
==> default: Setting up emacs (45.0ubuntu1) ...
==> default: Processing triggers for libc-bin (2.19-0ubuntu6.9) ...
==> default: Processing triggers for libgdk-pixbuf2.0-0:amd64
(2.30.7-0ubuntu1.6) ...
==> default: Errors were encountered while processing:
==> default: sudo
==> default: E: Sub-process /usr/bin/dpkg returned an error code (1)
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.
root@pndevucs47:~/source/vpp/build-root/vagrant#
*******************************************************
I ignored above error and went on to build Debian package. While executing
“make V=0 PLATFORM=vpp TAG=vpp install-deb” am getting below error.
*******************************************************
make[3]: Leaving directory
`/vpp/build-root/build-vpp-native/plugins/flowperpkt-plugin'
make[3]: Entering directory `/vpp/build-root/build-vpp-native/plugins'
make[4]: Entering directory `/vpp/build-root/build-vpp-native/plugins'
make[4]: Nothing to be done for `install-exec-am'.
make[4]: Nothing to be done for `install-data-am'.
make[4]: Leaving directory `/vpp/build-root/build-vpp-native/plugins'
make[3]: Leaving directory `/vpp/build-root/build-vpp-native/plugins'
make[2]: Leaving directory `/vpp/build-root/build-vpp-native/plugins'
make[1]: Leaving directory `/vpp/build-root'
dpkg-buildpackage: source package vpp
dpkg-buildpackage: source version 17.01-rc0~144-g7be864a
dpkg-buildpackage: source distribution unstable
dpkg-buildpackage: source changed by Dave Barach
<[email protected]<mailto:[email protected]>>
dpkg-buildpackage: host architecture amd64
dpkg-source --before-build deb
fakeroot debian/rules clean
make[1]: Entering directory `/vpp/build-root/deb'
dh clean --with dkms --with systemd,python2
dh_testdir
dh_auto_clean
dh_clean
make[1]: Leaving directory `/vpp/build-root/deb'
debian/rules build
make[1]: Entering directory `/vpp/build-root/deb'
dh build --with dkms --with systemd,python2
dh_testdir
dh_auto_configure
dh_auto_build
dh_auto_test
make[1]: Leaving directory `/vpp/build-root/deb'
fakeroot debian/rules binary
make[1]: Entering directory `/vpp/build-root/deb'
dh binary --with dkms --with systemd,python2
dh_testroot
dh_prep
dh_auto_install
debian/rules override_dh_install
make[2]: Entering directory `/vpp/build-root/deb'
dh_install --exclude .git
make[2]: Leaving directory `/vpp/build-root/deb'
dh_installdocs
dh_installchangelogs
debian/rules override_dh_dkms
make[2]: Entering directory `/vpp/build-root/deb'
dh_dkms -pvpp-dpdk-dkms
make[2]: Leaving directory `/vpp/build-root/deb'
dh_systemd_enable
dh_python2
Traceback (most recent call last):
File "/usr/share/python/dh_python2", line 718, in <module>
main()
File "/usr/share/python/dh_python2", line 609, in main
fix_locations(package)
File "/usr/share/python/dh_python2", line 94, in fix_locations
os.renames(srcdir, dstdir)
File "/usr/lib/python2.7/os.py", line 199, in renames
rename(old, new)
OSError: [Errno 17] File exists
make[1]: *** [binary] Error 1
make[1]: Leaving directory `/vpp/build-root/deb'
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
make: *** [install-deb] Error 1
vagrant@localhost:/vpp/build-root$
*******************************************************
# vagrant -v
Vagrant 1.9.0
# vboxmanage --version
4.3.36_Ubuntur105129
# uname -a
Linux pndevucs47 3.16.0-30-generic #40~14.04.1-Ubuntu SMP Thu Jan 15 17:43:14
UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
#
Can I ignore first error during “vagrant up”?
If no then how to resolve it.
If yes then how to resolve second error.
Any help is greatly appreciated.
Thanks,
Pravin Ajagekar
_______________________________________________
vpp-dev mailing list
[email protected]
https://lists.fd.io/mailman/listinfo/vpp-dev