Tag Info

Hot answers tagged

101

I run apt-cache policy <package name>: $ apt-cache policy wajig wajig: Installed: 2.01 Candidate: 2.01 Version table: *** 2.1 0 100 /var/lib/dpkg/status 2.0.47 0 500 file:/home/wena/.repo_bin/ squeeze/main i386 Packages 500 ftp://ftp.is.co.za/debian/ squeeze/main i386 Packages That means that there are three wajig ...


74

apt-file search filename or apt-file search /path/to/file To install apt-file, use: sudo apt-get install apt-file You will need to update its database before you can use it: sudo apt-file update


68

(Debian/Ubuntu) Discover what package a file belongs to: dpkg -S /usr/bin/ls 'dpkg -S' just matches the string you supply it, so just using 'ls' as an argument matches any file from any package that has 'ls' anywhere in the filename. So usually it's a good idea to use an absolute path. You can see in the second example that 12 thousand ...


40

These tools all install software into your system, but are working on different levels. ./configure && make install Running ./configure && make install builds and installs the libraries or executables directly from the source code. The make install step basically just copies the final files into your system. Many sources come with a ...


31

$ apt-get install libgstreamer0.10-dev libgstreamer-plugins-base0.10-dev which you could have found by doing a search for gstreamer-app-0.10.pc in package contents on packages.ubuntu.com or with apt-file search, or by running the whole configuration process within auto-apt run.


29

Package gzip has priority "required", meaning it must always be installed for the system to work properly. Probably aptitude is therefore refusing to remove it. What output did you get from the remove command? BTW: Why do you want to remove gzip? Doing so is a really bad idea... Edit: If you see gzip consuming a lot of CPU, that's because some other ...


25

I used to use Macports because: It is generally more up to date Macports seems to be more common / popular Everyone else I work with uses it When I did my own research on this topic when I got my MBP last fall, Macports seemed to be most commonly recommended for reason #1 above, hence reason #2 (and probably reason #3). Compiling every package doesn't ...


24

On any Debian based machine, this is one common way to duplicate a package set. On the old machine: dpkg --get-selections "*" > my_favorite_packages Copy the file my_favorite_packages to the new machine (a thumb drive is a good option, but scp also works fine). Then run this sequence (with root privileges): apt-get update dpkg --set-selections < ...


22

Look at the Open Source Watershed page. OpenSourceWatershed is a project aimed at understanding the relationship between distributions (downstream) and the individual software components (upstream). It is the basis for a larger study of distributions and their evolution. It is distrology. In the future, more distro oriented statistics will be available. ...


21

or dpkg --print-architecture


20

user@host:~$ dpkg-query -S /bin/bash bash: /bin/bash Where bash is the package name.


18

The confirmation dialog will not only appear when you would install packages you didn't ask for, but also in the following cases: Installing packages that you didn't specifically want to install Removal of essential packages Changing a held package (a held package is one you want to keep in the version currently installed) You can override it with one of ...


18

apt-get source package Will get you two or three files: "original" tarball (sometimes modified, but rarely... the only change is often the file name) -- named *.orig.tar.gz, the debian changes in form of *.diff.gz file, and some metadata. Sometimes the .diff.gz file is missing: this means that package is built only for debian/ubuntu, to handle some ...


16

There are two main systems for unix software on OS X: MacPorts and Fink Fink is akin to (and iirc based on) the Debian/Ubunutu apt system: it delivers pre-compiled binaries. MacPorts is related to the older BSD Ports collections: rather than pre-built binaries, it containers pointers to the original source + patches required to make that source work on your ...


16

There are several utilites in Debian which perform this task; check this page for a description. I'll mention two of them, apt-file and dlocate. apt-file searches its internal cache, thus allowing you to not install all the packages you want to search. Search is performed by launching apt-file search file.name. dlocate is a fast alternative to dpkg -L (the ...


15

Aha! Apparently, the proper apt command is not apt-cache info, but instead, apt-cache showpkg. $ apt-cache showpkg linux-generic Package: linux-generic Versions: 2.6.31.19.32 (/var/lib/apt/lists/us.archive.ubuntu.com_ubuntu_dists_karmic-updates_main_binary-amd64_Packages) ...


13

dpkg-architecture -qDEB_HOST_ARCH


13

You don't have to pick between the two. MacPorts installs software to /opt/local. Fink installs to /sw. Both leave the Darwin base system untouched, and the two can co-exist peacefully. Fink's binary packages are great, but they aren't always up-to-date. I tend to use Fink when they've got an up-to-date package, and I build from MacPorts if they don't. ...


13

i wasn't reading carefully when i tried to uninstall it. this is what it says WARNING: Performing this action will probably cause your system to break! Do NOT continue unless you know EXACTLY what you are doing! To continue, type the phrase "I am aware that this is a very bad idea": Abort.


13

Just as an addendum apt-cache madison package will list the versions available from all your sources. apt-cache madison vim vim | 2:7.3.547-1 | http://debian.mirrors.tds.net/debian/ unstable/main amd64 Packages vim | 2:7.3.429-2 | http://debian.mirrors.tds.net/debian/ testing/main amd64 Packages vim | 2:7.3.429-2 | ...


12

I recommend HomeBrew - http://mxcl.github.com/homebrew/


10

$sudo apt-get update This will update the list of available packages from the server.


10

Look at these files, '/var/log/installer/initial-status.gz' -- your primary installation this file date would be your installation date (i think) '/var/log/dpkg.log' update timeline (this is what you want) '/var/log/apt/term.log' -- things apt updated on your system '/var/cache/apt/archives/' will contain the deb packages downloaded for installation ...


10

The apt-cache search command will return all packages that have name in the package name or description: apt-cache search name Once you have a package name, you can get more detailed information on the package using the apt-cache show and apt-cache showpkg commands. apt-cache show package_name apt-cache showpkg package_name


9

I believe Allmyapps might be somewhat similar to Ninite. In addition, the best application update-checker I know is SUMo.


9

aptitude can do what are you looking for and much more, actually. aptitude search '?installed ?not(?automatic)' Or shorter: aptitude search '~i!~M' will list all the packages installed manually. None of the dependent (i.e., like mysql-data, or *-common, that are installed automatically) packages will be listed. If you want just package names, use -F ...


9

It depends on how much you trust the dependancy tracker. While almost always correct, there are times when you would want a dependancy to remain, particularly when you are a developer or power user installing software that is not in the repository. If you always install software through apt-get, without exception, and trust all the dependancies to be ...


9

You should use the equivs package to generate meta-packages that provide these dependencies, and then use dpkg to install these packages. Installing equivs and reading its documentation should be enough, but this guide for Ubuntu is quite extensive and should apply to other APT systems as well. Also, if you feel that a package should be able to be ...


9

They will not coexist well together. The Apple gcc looks in /usr/local for some things. This means that a macports compile could find something the porter did not expect. See macports mail lists and bugs for examples of things found in /usr/local.


9

I gave another answer on a similar question: Homebrew will cause problems when building software from source if it is installed in /usr/local. This is the default, which is a bad choice as this path is in the default search path of compilers and other tools. Therefore builds from other packaging software might pick up the wrong dependency, using ...



Only top voted, non community-wiki answers of a minimum length are eligible