1. Install Deb Packages In Puppy Linux

Install Deb Packages In Puppy Linux

Debian releases live install images for CDs, DVDs and USB thumb drives, for the i386 and amd64 architectures, and with a choice of desktop environments. These Debian Live images allow the user to boot from a removable media and run Debian without affecting the contents of their computer. Linux games deb free download. Dpki can install a local.deb file via the command line like the dpkg command. Click Mark to allow the installation of the additional package(s).

Puppy Linux is an operating system and family of light-weight Linux distributions that focus on ease of use^[4] and minimal memory footprint. The entire system can be run from random-access memory with current versions generally taking up about 210 MB,^[5] allowing the boot medium to be removed after the operating system has started. Applications such as AbiWord, Gnumeric and MPlayer are included, along with a choice of lightweight web browsers and a utility for downloading other packages. The distribution was originally developed by Barry Kauler and other members of the community, until Kauler retired in 2013.^[6] The tool Woof can build a Puppy Linux distribution from the binary packages of other Linux distributions.^[7]

• 1History

History[edit]

Barry Kauler started Puppy Linux in response to a trend of other distributions becoming stricter on system requirements over time. His own distribution, with an emphasis on speed and efficiency and being lightweight, started from 'Boot disk HOWTO' and gradually included components file-by-file until Puppy Linux was completed.^{[8][clarification needed]} Puppy Linux started as Vector Linux based until it became a fully independent distribution.^[9]

Release versions[edit]

Puppy 0 is the initial release of Puppy Linux. It has no unionfs, extreme minimal persistence support, and has no package manager or ability to install applications.^[10]

Puppy 1 series will run comfortably on very dated hardware, such as a Pentium computer with at least 32 MB RAM. For newer systems, the USB keydrive version might be better (although if USB device booting is not directly supported in the BIOS, the Puppy floppy boot disk can be used to kick-start it). It is possible to run Puppy Linux with Windows 9x/Windows Me. It is also possible, if the BIOS does not support booting from USB drive, to boot from the CD and keep user state on a USB keydrive; this will be saved on shutdown and read from the USB device on bootup.^[11][12]

Puppy 2 uses the Mozilla-based SeaMonkey as its Internet suite (primarily a web browser and e-mail client).^[13]

Puppy 3 features Slackware 12 compatibility.^[14] This is accomplished by the inclusion of almost all the dependencies needed for the installation of Slackware packages. However, Puppy Linux is not a Slackware-based distribution.^[15][16]

Puppy 4 is built from scratch using the T2 SDE^[17] and no longer features native Slackware 12 compatibility^[18] in order to reduce the size and include newer package versions than those found in 3. To compensate for this, an optional 'compatibility collection' of packages was created that restores some of the lost compatibility.^{[18][19][20][21]}

Puppy 4.2 features changes to the user interface and backend, upgraded packages, language and character support, new in-house software and optimizations, while still keeping the ISO image size under 100 MB.^[22]

Puppy 5 is based on a project called Woof^[23] which is designed to assemble a Puppy Linux distribution from the packages of other Linux distributions. Woof includes some binaries and software derived from Ubuntu, Debian, Slackware, T2 SDE, or Arch repositories. Puppy 5 came with a stripped down version of the Midori browser to be used for reading help files and a choice of web browsers to be installed, including Chromium, Firefox, SeaMonkey Internet Suite, Iron and Opera.^{[24][25][26][27][28][29][30][31][32][33][34][35]}

Puppy 6 is built from Ubuntu 14.04 'Trusty Tahr' packages, has binary compatibility with Ubuntu 14.04 and access to the Ubuntu package repositories. Tahrpup is built from the woof-CE build system, forked from Barry Kauler's Woof late last year after he announced his retirement from Puppy development. It is built from the latest testing branch, incorporates all the latest woof-CE features and is released in PAE and noPAE ISOs, with the option to switch kernels.^[36]

Puppy 7 is built from Ubuntu 16.04 Xenial Xerus packages, has binary compatibility with Ubuntu 16.04 and access to the Ubuntu package repositories. Tahrpup is built from the woof-CE build system, forked from Barry Kauler's Woof. It is built from the latest testing branch, incorporates all the latest woof-CE features and is released in PAE and noPAE ISOs, with the option to switch kernels. It has a new UI, a new kernel update for greater hardware compatibility, redesign Puppy Package Manager, some bugfixes and base packages inclusion into the woof structure.^[37]

Puppy 8 is built from Ubuntu Bionic Beaver 18.04.2 packages, has binary compatibility with Ubuntu 18.04.2 and access to the Ubuntu package repositories. BionicPup is built from the woof-CE build system, forked from Barry Kauler's Woof. It is built from the latest testing branch, and incorporates all the latest woof-CE features.^[38]

Features[edit]

Puppy Linux is a complete operating system bundled with a collection of applications suited to general use tasks. It can be used as a rescue disk,^[39] a demonstration system that leaves the previous installation unaltered, as an accommodation for a system with a blank or missing hard drive, or for using modern software on legacy computers.^[40]

Puppy's compact size allows it to boot from any media that the computer can support. It can function as a live USB for flash devices or other USB mediums, a CD, an internal hard disk drive, an SD card, a Zip drive or LS-120/240 SuperDisk, through PXE, and through a floppy boot disk that chainloads the data from other storage media. It has also been ported to ARM and can run on a single board computer such as the Raspberry Pi.^[41]

Puppy Linux features built-in tools which can be used to create bootable USB drives, create new Puppy CDs, or remaster a new live CD with different packages.^[42][43] It also uses a sophisticated write-caching system with the purpose of extending the life of live USB flash drives.^[44]

Puppy Linux includes the ability to use a normal persistent updating environment on a write-once multisession CD/DVD that does not require a rewritable disc; this is a unique feature that sets it apart from other Linux distributions.^[45] While other distributions offer live CD versions of their operating systems, none offer a similar feature.

Puppy's bootloader does not mount hard drives or connect to the network automatically. This ensures that a bug or even unknowingly incompatible software won't corrupt the contents of such devices.^{[46][better source needed]}

Puppy Linux offers a session save on shutdown. Since Puppy Linux fundamentally runs in RAM, any files and configurations made or changed in a session would disappear otherwise. This feature enables the user to either save the contents to a writable storage medium, or write the file system to the same CD containing Puppy, if 'multisession' was used to create the booted CD and if the disc drive supports burning. This applies to CD-Rs as well as CD-RWs and DVDs.

It is also possible to save all files to an external hard drive, USB stick, or even a floppy disk instead of the root file system. Puppy can also be installed to a hard disk.^[47]

User interface[edit]

The default window manager in most Puppy releases is JWM.^[48]

Packages of the IceWM desktop, Fluxbox and Enlightenment are also available via Puppy's PetGet package (application) management system (see below). Some derivative distributions, called puplets, come with default window managers other than JWM.^[49]

When the operating system boots, everything in the Puppy package uncompresses into a RAM area, the 'ramdisk'. The PC needs to have at least 128 MB of RAM (with no more than 8 MB shared video) for all of Puppy to load into the ramdisk. However, it is possible for it to run on a PC with only about 48 MB of RAM because part of the system can be kept on the hard drive, or less effectively, left on the CD.

Puppy is fairly full-featured for a system that runs entirely in a ramdisk, when booted as Live system or from a 'frugal' installation. However, Puppy also supports the 'full' installation mode, which enables Puppy to run from a hard drive partition, without a ramdisk. Applications were chosen that met various constraints, size in particular. Because one of the aims of the distribution is to be extremely easy to set up, there are many wizards that guide the user through a wide variety of common tasks.^{[50][citation needed]}

Package and distribution management[edit]

Puppy Linux's package manager, Puppy Package Manager, installs packages in PET (Puppy Enhanced Tarball) format by default but it also accepts packages from other distros (such as .deb, .rpm, .txz, and .tgz packages) or by using third-party tools to convert packages from other distros to PET packages. Puppy Package Manager can also trim the software bloat of a package to reduce the disk space used.^[51]

Building the distribution[edit]

On earlier releases of Puppy Linux, Puppy Unleashed was used to create Puppy ISO images. It consists of more than 500 packages that are put together according to the user's needs. However, on later versions starting with Puppy Linux version 5.0, it was replaced by Woof. It is an advanced tool for creating Puppy installations. It requires an Internet connection and some knowledge of Linux to use. It is able to download the binary source packages from another Linux distribution and process them into Puppy Linux packages by just defining the name of that Linux distro.^[52] It is equipped with a simpler version control named Bones on earlier releases but on later versions of woof, Fossil version control is used.^[53]

Puppy also comes with a remastering tool that takes a 'snapshot' of the current system and lets the user create a live CD from it, and an additional remastering tool that is able to remove installed components.^{[citation needed]}

Puppy Linux uses the T2 SDE build scripts to build the base binary packages.^{[citation needed]}

Official variants[edit]

Because of the relative ease with which the Woof tool and the remaster tool can be used to build variants of Puppy Linux, there are many variants available.^[7][54] Variants of Puppy Linux are known as puplets.

After Barry Kauler reduced his involvement with the Puppy Project, he designed two new distributions within the same Puppy Linux family, Quirky and Wary.

Quirky – An embedded, less-stable distro with all files contained in an initramfs built into the kernel. It has simple module loading management but fewer drivers are included.^[55][56][57] It is used for experimental purposes.

Racy – A variant of puppy optimized for newer PCs.^[58]

Wary – A Puppy variant targeted at users with old hardware. It uses an older Linux kernel, which has long-term support and the newest applications.^[59]

Easy – A puppy variant in which the init script is completely rewritten and which uses originally developed application containers aside the conventional package management.^[60]

Reception[edit]

DistroWatch reviewer Rober Storey concluded about Puppy 5.2.5 in April 2011: 'A lot of people like Puppy — it's in the top 10 of the DistroWatch page-hit ranking. I enjoy Puppy too, and it's what I run exclusively on my netbook. Maybe the only thing wrong with Puppy is that users' expectations tend to exceed the developer's intentions.'^[61]

In a detailed review of Puppy Linux in May 2011 Howard Fosdick of OS News addressed the root user issue, 'In theory this could be a problem — but in practice it presents no downside. I've never heard of a single Puppy user suffering a problem due to this.' Fosdick concluded 'I like Puppy because it's the lightest Linux distro I've found that is still suitable for end users. Install it on an old P-III or P-IV computer and your family or friends will use it just as effectively for common tasks as any expensive new machine.'^[62]

In December 2011 Jesse Smith, writing in DistroWatch, reviewed Puppy 5.3.0 Slacko Puppy. He praised its simplicity, flexibility and clear explanations, while noting the limitations of running as root. He concluded 'I would also like to see an option added during the boot process which would give the user the choice of running in unprivileged mode as opposed to running as root. Always being the administrator has its advantages for convenience, but it means that the user is always one careless click away from deleting their files and one exploit away from a compromised operating system. As a live CD it's hard to beat Puppy Linux for both performance and functional software. It has minimal hardware requirements and is very flexible. It's a great distro as long as you don't push it too far out of its niche.'^[30]

In December 2011 Howard Fosdick reviewed the versions of Puppy Linux then available. He concluded, 'Puppy's diversity and flexibility make it a great community-driven system for computer enthusiasts, hobbyists, and tinkerers. They also make for a somewhat disorderly world. You might have to read a bit to figure out which Puppy release or Puplet is for you. Puppy's online documentation is extensive but can be confusing. It's not always clear which docs pertain to which releases. Most users rely on the active, friendly forum for support.' He also noted 'Those of us who enjoy computers sometimes forget that many view them with disdain. What's wrong with it now? Why do I have to buy a new one every four years? Why on earth do they change the interface in every release? Can't it just work? Puppy is a great solution for these folks. It's up-to-date, free, and easy to use. And now, it supports free applications from the Ubuntu, Slackware, or Puppy repositories. Now that's user-friendly.'^[63]

See also[edit]

References[edit]

1. ^'Puppy Time Line pre-Puppy Version 1 (2003-2005)'. PuppyLinux. Retrieved 2012-05-06.
2. ^'DistroWatch Puppy Linux'. 2019-04-11. Retrieved 2019-04-12.
3. ^'Puppy Linux Blog - Powered by SJPPLOG_NG'. puppylinux.com. Retrieved 21 January 2018.
4. ^Fosdick, Howard (October 8, 2007). 'An in-depth look at Puppy Linux'. DesktopLinux. Archived from the original on January 16, 2013. Retrieved August 19, 2016.
5. ^Kauler, Barry (2008). 'Official Puppy Linux Website'. Archived from the original on December 11, 2015. Retrieved July 13, 2016.Cite uses deprecated parameter dead-url= (help)
6. ^Kauler, Barry. 'TahrPup 6.0'. Bkhome.org. Retrieved 2013-08-04.
7. ^ ^ab'Announcement and release notes for Lucid Puppy 5.0'.
8. ^'Interview: Barry Kauler, Puppy Linux'. DistroWatch Weekly. DistroWatch. November 14, 2005. Retrieved 2016-08-19.
9. ^'Puppy Linux History'. puppylinux.com. Retrieved 26 August 2016.
10. ^'Puppy Linux History'. puppylinux.com. Retrieved 2016-08-16.
11. ^'Pupsave file'. PuppyLinux.com.
12. ^'Featured Distribution of the Week: Puppy Linux'. DistroWatch.com. 3 October 2005. Retrieved 24 March 2019.
13. ^'Taking Puppy for a short walk - Tux Machines'. www.tuxmachines.org. Retrieved 24 March 2019.
14. ^Kauler, Barry. 'Puppy 3.00 Released (Updated to 3.01)'. Archived from the original on November 8, 2007.Cite uses deprecated parameter deadurl= (help)
15. ^Kauler, Barry. 'Puppy Linux release notes v3.00'.
16. ^Linton, Susan (8 October 2007). 'First look at Puppy Linux 3.00'. DistroWatch.com. Retrieved 24 March 2019.
17. ^Kauler, Barry. 'Puppy Linux release notes 4.00'.
18. ^ ^abKauler, Barry. 'package management'.
19. ^'Puppy Linux 4.3 and Woof [LWN.net]'. lwn.net. Retrieved 24 March 2019.
20. ^Smith, Jesse (24 August 2009). 'First look at Puppy Linux 4.2.1'. DistroWatch.com. Retrieved 24 March 2019.
21. ^'Puppy Linux - revisited - Absolutely stunning!'. www.dedoimedo.com. Retrieved 24 March 2019.
22. ^Kauler, Barry. 'Puppy Linux 4.2'. Archived from the original on 3 January 2010. Retrieved 6 April 2011.Cite uses deprecated parameter deadurl= (help)
23. ^Kauler, Barry (9 February 2009). 'Woof: the 'Puppy builder''. Puppy developer pages. Retrieved 2009-02-13.
24. ^Puppy Linux (May 2016). 'Index of /puppylinux/Lucid_Puppy'. Retrieved May 14, 2016.
25. ^Puppy Linux (May 2016). 'Index of /puppylinux/pet-packages-lucid/'. Retrieved May 14, 2016.
26. ^Smith, Jesse (7 April 2014). 'First Impressions of Slacko Puppy 5.7'. distrowatch.com. Retrieved 24 March 2019.
27. ^Review of Precise Puppy: Puppy Linux With Ubuntu Favor, MakeTechEasier.
28. ^'Precise Puppy Is a Fast, Furious Distro - Reviews - LinuxInsider'. www.linuxinsider.com. Retrieved 24 March 2019.
29. ^Smith, Jesse (24 December 2014). 'First look at Puppy Linux 5.4 'Slacko''. DistroWatch.com. Retrieved 24 March 2019.
30. ^ ^abSmith, Jesse (12 December 2011). 'Review: Puppy Linux 5.3 'Slacko''. DistroWatch. Retrieved 12 December 2011.
31. ^'Puppy Linux: Top Dog of the Lightweight Distros – OSnews'. www.osnews.com. Retrieved 24 March 2019.
32. ^Storey, Robert (18 April 2014). 'Puppy Linux 5.2.5 - taking a bite out of bloat'. DistroWatch.com. Retrieved 24 March 2019.
33. ^Noyes, Katherine (11 January 2011). 'For an Old or Slow PC, Try Puppy Linux 5.2'. PCWorld. Retrieved 24 March 2019.
34. ^'Puppy Linux 5 Lucid Puppy - Nothing but praise'. www.dedoimedo.com. Retrieved 24 March 2019.
35. ^Michael Reed (May 21, 2010). 'Puppy Linux 5.0 'Lucid Puppy' Released'. Linux Journal. Retrieved 27 March 2019.
36. ^Kauler, Barry (May 2013). 'Announcement and release notes for Tahrpup 6.0 CE'. iBiblio.org. Retrieved May 14, 2016.
37. ^Kauler, Barry. 'Puppy Linux Release Announcement'. distro.ibiblio.org. Retrieved 2017-12-10.
38. ^CMS, Bludit. 'BionicPup 32 bit and 64 bit released'. blog.puppylinux.com. Retrieved 24 March 2019.
39. ^'Taking Puppy Linux for a Walk'.
40. ^'Reviving old computer'.
41. ^'ARM'. PuppyLinux. May 29, 2013. Retrieved August 12, 2013.
42. ^'Make your own Puppy-CD'. Archived from the original on October 13, 2008. Retrieved August 19, 2016.Cite uses deprecated parameter dead-url= (help)
43. ^'Remastering'. Puppy Linux Wiki. Retrieved August 19, 2016.
44. ^Kauler, Barry (September 9, 2006). 'How Puppy Works'. Archived from the original on August 19, 2016. Retrieved August 19, 2016.Cite uses deprecated parameter dead-url= (help)
45. ^'Puppy Multisession DVD/CD'.
46. ^'AutoFS'. Archived from the original on 2010-08-14.Cite uses deprecated parameter dead-url= (help)
47. ^Eckstein, Keith (July 2010). 'And they call it Puppy Love…'. Archived from the original on July 11, 2010. Retrieved 9 July 2010.Cite uses deprecated parameter deadurl= (help)
48. ^'JWM'. PuppyLinux.org.
49. ^'IceWM'. PupWeb.org.
50. ^'AboutPuppy - Puppy Linux'. Archived from the original on 2008-06-21. Retrieved 2008-08-02.
51. ^Kauler, Barry (October 2009). 'Package management'. Retrieved 23 January 2011.
52. ^Barry Kauler (March 2010). 'Woof: the 'Puppy builder''.
53. ^Barry Kauler (March 2010). 'Bones: version control'.
54. ^'PuppyLinux: Puplets'.
55. ^'Quirky'. bkhome.org. Retrieved 24 March 2019.
56. ^'DistroWatch.com: Quirky'. distrowatch.com. Retrieved 24 March 2019.
57. ^'Quirky Linux Gets More Pep Out of Puppy - Reviews - LinuxInsider'. www.linuxinsider.com. Retrieved 24 March 2019.
58. ^'Puppy Linux Community - Home'. Puppylinux.org. Retrieved 2012-04-12.
59. ^Kauler, Barry. 'Wary Puppy Linux'. bkhome.org. Retrieved 26 August 2016.
60. ^Kauler, Barry. 'How Easy Linux works'. barryk.org. Retrieved 21 March 2017.
61. ^Storey, Robert (April 2011). 'Puppy Linux 5.2.5 - taking a bite out of bloat'. DistroWatch. Retrieved 23 April 2011.
62. ^Fosdick, Howard (May 2011). 'Puppy Linux: Top Dog of the Lightweight Distros'. OS News. Retrieved 17 May 2011.
63. ^Fosdick, Howard (17 December 2011). 'Puppy Has A Litter'. OS News. Retrieved 17 December 2011.

External links[edit]

• Puppy Linux at DistroWatch

How do I install a .deb file via the command line?

10 Answers

Packages are manually installed via the dpkg command (Debian Package Management System). dpkg is the backend to commands like apt-get and aptitude, which in turn are the backend for GUI install apps like the Software Center and Synaptic.

Something along the lines of:

dpkg -->apt-get, aptitude --> Synaptic, Software Center

But of course the easiest ways to install a package would be, first, the GUI apps (Synaptic, Software Center, etc.), followed by the terminal commands apt-get and aptitude that add a very nice user friendly approach to the backend dpkg, including but not limited to packaged dependencies, control over what is installed, needs update, not installed, broken packages, etc. Lastly the dpkg command which is the base for all of them.

Since dpkg is the base, you can use it to install packaged directly from the command line.

Install a package

For example if the package file is called askubuntu_2.0.deb then you should do sudo dpkg -i askubuntu_2.0.deb. If dpkg reports an error due to dependency problems, you can run sudo apt-get install -f to download the missing dependencies and configure everything. If that reports an error, you'll have to sort out the dependencies yourself by following for example How do I resolve unmet dependencies after adding a PPA?.

Remove a package

For example if the package is called askubuntu then you should do sudo dpkg -r askubuntu.

Reconfigure an existing package

This is useful when you need to reconfigure something related to said package. Some useful examples it the keyboard-configuration when you want to enable the Ctrl+Alt+Backspace in order to reset the X server, so you would the following:

Another great one is when you need to set the Timezone for a server or your local testing computer, so you use use the tzdata package:

Debian (.deb) packages are the packages that are used in Ubuntu. You can install any .deb package in your system. .deb files can generally be installed from your file manager (Nautilus) merely by clicking on them, since file associations with the default installer is already set in Ubuntu. These instructions are for those who wish to install packages from the command-line terminal (Terminal).

To install a downloaded Debian (Ubuntu) package (.deb): Open Terminal and type

To remove a Debian (Ubuntu) package (.deb):

To Reconfigure/Repair an installed Debian (Ubuntu) package (.deb):

My favourite is GDebi, available from both terminal/shell or graphical desktop.

I usually associate .deb files with GDebi as it is fast and efficient - especially compared to Ubuntu Software Center. One of the main feature of GDebi is it resolves dependencies and installs them.

For command-line run sudo gdebi <package.deb> to install a single deb file.

Are you looking for all dpkg commands? click this link to have a read.

There are two actions, they are dpkg-query and dpkg-deb.

Install a package

Remove a package

Remove a package and its configuration files

List all installed packages.

You can pipe the command to less (a pager) so you can more easily scroll the content:

Check if the package is installed or not

Check if the package is installed or not, and if it is, launch it:

See whether a package is installed or not

And this will show the location where the package will be installed.Here -S (capital S) to search whether the package was installed or not.

Install a *.deb package from a specified location

Here -R is recursive. (Recursively handle all regular files matching the pattern *.deb found at specified directories and all of its subdirectories).

Show package details

Here -p (lowercase p) will show the package info:

View the content of a package

Use -c (lowercase c) to show the content:

Extract the *.deb package file

Use -x (lowercase x) to extract:

Extract and display the filenames contained in a package

Use -X (uppercase X) to display the content with extraction.

Display information about a package

Here -I stands for information:

Reconfigure an already installed package

dpkg-reconfigure reconfigures packages after they already have been installed. Pass it the name(s) of a package or packages to reconfigure. It will ask configuration questions, much like when the package was first installed.

This will reconfigure postfix the same way as when you installed it for the first time.

Need to know more about dpkg commands? Have a look at the manual page:

While dpkg -i indeed installs the package, it doesn't do any automatic dependency resolution, meanwhile there are two other alternatives, using gdebi, or the apt-get tool. To use the later just use:

Even if you are on the directory with the package you need to give a path using ./ at the start:

A handy tip when installing a program like Libreoffice which has multiple .deb files in a folder is to use.

Here's the best way to install a .deb file on Ubuntu on the command-line:

If you don't have gdebi installed already, install it using sudo apt install gdebi-core.

gdebi will look for all the dependencies of the .deb file, and will install them before attempting to install the .deb file. I find this much preferable than sudo dpkg -i skype.deb && sudo apt install -f. The latter is much too eager to remove dependencies in certain situations. For instance, when I tried to install Skype, it attempted to remove 96 (!) packages, including packages like compiz and unity! gdebi gave a much clearer error message:

(Here is the solution to that particular issue, by the way.)

Create your own script installer debInstaller as the following:

Make the script executable with

Then move it to some dirs in your PATH or add the current directory to your PATH.

I'm going to move it to /usr/bin

Now you can install any .deb package using the command:

The added value of this method is the solving the dependencies problem, since mostly you'll face some problems when you install a .deb with dpkg -i due to dependencies error, so you have to use apt-get install -f to solve it, this script will do the job for you, but here I used apt-get --yes --fix-broken install to automatically solve these errors without user intervention.

Aqua aquarius full album download. To install deb files, open Terminal and type:

The second line is to fix broken packages if the installation fails, then, install again to complete the installation.

Another approach is to use gdebi tool to install deb files.

There are many tools to install a deb packageI personally use built-in package installer dpkg

If you are logged as rootchange the directory to location of deb package

if you are not logged as root

To make sure that package installed correctly and didn't have any broken dependencies

If there are any broken dependencies

protected by Community♦Feb 20 '14 at 20:57

Thank you for your interest in this question. Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?

Not the answer you're looking for? Browse other questions tagged command-linesoftware-installationdpkgdeb or ask your own question.