Tag Info

New answers tagged

0

You can achieve what you aim for, by creating two meta packages (that only contain dependencies) that provide a virtual package (that exists to declare some functionality that some other package can provide). So: Package: nvidia-dependencies-340 Provides: nvidia-dependencies Depends: nvidia-340 (>=340.29), nvidia-340-uvm (>=340.29), nvidia-340-dev ...


1

It may not be possible in a fully general sense, but if your deb came from Debian or Ubuntu directly (i.e., not a third-party deb), then it is required to be reproducible by autobuilders which do something like the following: Start with a bare system- all Essential: yes or Priority: Required packages, plus build-essential, and any extra dependencies of ...


1

Use this command instead of dpkg-buildpackage -us -uc and all is fine: DEB_BUILD_OPTIONS=nocheck dpkg-buildpackage -rfakeroot -us -uc -b Tests are disabled and there are only built binary packages.


0

I feel to guess an anwser, still feel free to add your own anwser. I've learned there is a /var/lib/dpkg/available database, as raw‑text. I checked for python3 (to go on with the same example as in the question) it says Provides: python3-profiler: there is no python3:any. So may be the anwser is: there is not always a direct match between a requirements ...


2

python3:any (>= 3.3.2-2~) is not a virtual package, it's a substitution string created by the ${python3:Depends} pattern and filled by dh_python3 when called from dh_gencontrol when the package was built. Take a look at the debian/control file of the apturl source package: Package: apturl-common Architecture: any Depends: ${python3:Depends}, ...


1

I'm not sure if there's a better way, but at the very least you could remove the signature "manually" with ar: ar d "$yourpackage.deb" _gpgbuilder (or additional things besides _gpgbuilder if you accomplished having "three signatures" by giving role names other than "builder"). This works because .deb files, at the outermost layer, are essentially just ...


0

For embedded signatures, you can open the .deb file with file-roller, and remove the embedded signature file. You can also use ar with ar d package.deb _gpgbuilder. For detached signatures, you can just open the xul-ext-ubufox_3.0-0ubuntu0.14.10.1.dsc file in a text editor, and should be able to remove the extra signature blocks from the bottom of the file. ...


1

QT assistant is packaged as part of qttools5-dev-tools, you will also want qt5-doc for the QT5 SDK documentation. To install run the following command: sudo apt-get install qt5-doc qttools5-dev-tools To launch you can run this command from a terminal: /usr/lib/x86_64-linux-gnu/qt5/bin/assistant You may want to create a desktop file to make it ...


-1

You should follow these steps, may work for you. 1) .deb file install in root path only so root path command: sudo su 2) then find the your your .deb file in which folder 3) using ls command show the particular folder files. 4) then find your .deb package file. 5) deb package command as dpkg -i ./your_file_name then Enter 6) may be work for you. I am ...


1

if you want to list liblucene (liblucene++0) relevant packages run: apt-cache search liblucene or: apt-cache search liblucene++0* if you want to check package liblucene++0 run: apt-cache policy liblucene++0


2

Generally, <name>_<version>.orig.tar.xz or <name>_<version>.orig.tar.gz is the source archive, as released by the project. It's simply renamed to fit the vagaries of the Debian packaging system. Usually, for packaging purposes, you need to unpack <name>_<version>.orig.tar.xz in the current folder and then place the ...



Top 50 recent answers are included