Tag Info

New answers tagged


I was not able to solve it for that way of installing, but this one worked: http://askubuntu.com/a/672018/350308 With one change, his line: https://github.com/libimobiledevice/libimobiledevice.git Should be: git clone https://github.com/libimobiledevice/libimobiledevice.git


If you program is supposed to be called as CLI command, you want to make an entry point using setuptools: http://stackoverflow.com/questions/17401381/debianzing-a-python-program-to-get-a-deb If it's used as a library, you can use the 'import' statement in python to use the code.


Package signing on Ubuntu/Debian systems is rather messy. In theory, signing a deb package makes it possible for the person receiving your package to verify that the package was not modified after you signed it. In reality, signature verification is terribly difficult to setup and is disabled by default. Unless the user does a bunch of setup locally, they ...


bzr builddeb's options include: --strict Refuse to build if there are unknown files in the working tree, --no-strict disables the check. This makes me think it will include only those files which are added to the branch while building a package. Therefore, try adding postinst using bzr add.


I referred this blog and did the trick. solution found from this forum This command got fix my issue. dpkg-buildpackage -b -rfakeroot -us -uc


Use debian/install instead. A debian/install containing: foo /etc/init.d Will cause foo to be copied to /etc/init.d relative to the package build directory.


libois-1.2.0 is an obsolete package and has been replaced in recent versions of Ubuntu by libois-1.3.0. If you need the old version you can still try to install it using sudo dpkg -i <deb_file>. The deb package can still be downloaded from launchpad: amd64 or i386. Example for amd64: sudo dpkg -i libois-1.2.0_1.2.0-2_amd64.deb

Top 50 recent answers are included