New answers tagged

0

At last I solved it with the following configuration: package name is thunder-buildout-prod debian/oooctl.service as in question in debian/rules: %: dh $@ --with bash-completion --with systemd --with python2 override_dh_systemd_enable: dh_systemd_enable -p thunder-buildout-prod debian/oooctl.service override_dh_systemd_start: dh_systemd_start ...


6

You aren't building a deb from source here. You can read the documentation provided on the link you posted, but I will summarize here. The commands you will have to do will be as follows: git clone https://www.github.com/KDE/kdenlive cd kdenlive mkdir build cd build cmake .. -DCMAKE_INSTALL_PREFIX=/usr/bin make -j4 sudo make install This will: Gather ...


0

Seems the best answer is a working example Configuration files conf/distributions Codename: trusty Components: main universe Architectures: amd64 #Update: test1 Pull: pull1 Codename: vivid Suite: production Components: universe Architectures: amd64 Update: update1 conf/updates Name: test1 Suite: trusty Method: http://archive.ubuntu.com/ubuntu/ ...


1

As it happens, dh can not possibly be used to package a Qt programme in the traditional way presented in most guides and tutorials out there. More specifically, the rules file must be informed of which snippets it must use to include in the final Makefile. One way of achieving this is using the cdbs package: sudo apt-get install cdbs Then the rules file ...


1

Here's solution that worked: 1. Install midnight commander (sudo apt-get install mc) 2. Run it as root and navigate to the directory the package lies. 3. Enter the package (by taping [enter]), enter the directory CONTENTS and copy all the directories that have been removed manually back to theirs place. 4. Reinstall the package (just to be sure everything is ...


0

You have left the virtualbox package in a half-installed/half-uninstalled state. Manually deleting packages you have installed using a package manager is very bad and most often lead to scenarios like this one. To proceed you have to find all installed virtualbox-packages using dpkg -l | grep virtualbox. Now purge each package with dpkg -P ..., replace ... ...


0

I had the same problem as you and the only way to resolve it was to use dpkg. Thus, all packages that were already downloaded were installed and Ubuntu did not ask to download them again. I hope it helps you. With regard to the 32-bit libraries, Ubuntu installs to ensure compatibility with other programs or processes that may need them. I also think it's a ...



Top 50 recent answers are included