How to install deb package arch

Arch Linux

You are not logged in.

#1 2010-12-13 23:57:27

I want to install the Adobe Connect 8 Add-in which can be found under the following link.

Please tell me that it is possible. I would really appreciate if someone can tell me how I can install this properly.

Last edited by Archie_Enthusiasm (2010-12-14 19:50:48)

#2 2010-12-14 00:33:04

You can do something with community/deb2targz, I’m not sure of the exact steps though. Ideally, you (or a generous bystander) should make a PKGBUILD.

#3 2010-12-14 01:57:44

There are lots of examples in aur of PKGBUILDs that converts deb to pkg.tar.gz

Evil #archlinux@libera.chat channel op and general support dude.
. files on github, Screenshots, Random pics and the rest

#4 2010-12-14 09:48:32

I do not have any experience with building aur pkg. Can someone please make the pkg build for this add-in? It is very important for me because I need to share my desktop screen with this add-in.

Thanks I am waiting for any kind of responses.

#5 2010-12-14 12:41:07

Have you tried making a PKGBUILD? Try it, at least once.

#6 2010-12-14 13:42:35

thanks for the responses. but the problem is that I am relatively new to arch linux. Since I had one serious problem with my nvidia driver because of an unsupported binary, I only use official arch linux repos for installing the application. I really (please understand this) do not want to take risk doing stuff on my own for this. My lap should be working tomorrow. Otherwise I will miss my presentation with adobe connect which would be very pity for me.

I am still looking for your responses.

Thanks in advance

EDIT: I found this from the community forum

Is this correct?

Last edited by Archie_Enthusiasm (2010-12-14 13:49:11)

#7 2010-12-14 14:13:31

thanks for the responses. but the problem is that I am relatively new to arch linux. Since I had one serious problem with my nvidia driver because of an unsupported binary, I only use official arch linux repos for installing the application. I really (please understand this) do not want to take risk doing stuff on my own for this. My lap should be working tomorrow. Otherwise I will miss my presentation with adobe connect which would be very pity for me.

The better solution is to actually try things out, and learn while doing so. Nobody is going to just give you the right answer, that’s not how the distro works. In the case of what you’re trying to do, YMMV, so even more there’ll be no ‘right answer’ to point you to.

Allan-Volunteer on the (topic being discussed) mailn lists. You never get the people who matters attention on the forums.
jasonwryan-Installing Arch is a measure of your literacy. Maintaining Arch is a measure of your diligence. Contributing to Arch is a measure of your competence.
Griemak-Bleeding edge, not bleeding flat. Edge denotes falls will occur from time to time. Bring your own parachute.

SYNOPSIS

dpkg-deb packs, unpacks and provides information about Debian archives.

Use dpkg to install and remove packages from your system.

You can also invoke dpkg-deb by calling dpkg with whatever options you want to pass to dpkg-deb. dpkg will spot that you wanted dpkg-deb and run it for you.

For most commands taking an input archive argument, the archive can be read from standard input if the archive name is given as a single minus character («—»); otherwise lack of support will be documented in their respective command description.

COMMANDS

Unless you specify —nocheck, dpkg-deb will read DEBIAN/control and parse it. It will check the file for syntax errors and other problems, and display the name of the binary package being built. dpkg-deb will also check the permissions of the maintainer scripts and other files found in the DEBIAN control information directory.

If no archive is specified then dpkg-deb will write the package into the file binary-directory.deb.

If the archive to be created already exists it will be overwritten.

If the second argument is a directory then dpkg-deb will write to the file directory/package_version_arch.deb. When a target directory is specified, rather than a file, the —nocheck option may not be used (since dpkg-deb needs to read and parse the package control file to determine which filename to use).

If no control-file-names are specified then it will print a summary of the contents of the package as well as its control file.

If any control-file-names are specified then dpkg-deb will print them in the order they were specified; if any of the components weren’t present it will print an error message to stderr about each one and exit with status 2.

-W, —show archive Provides information about a binary package archive in the format specified by the —showformat argument. The default format displays the package’s name and version on one line, separated by a tabulator. -f, —field archive [control-field-name. ] Extracts control file information from a binary package archive.

If no control-field-names are specified then it will print the whole control file.

If any are specified then dpkg-deb will print their contents, in the order in which they appear in the control file. If more than one control-field-name is specified then dpkg-deb will precede each with its field name (and a colon and space).

No errors are reported for fields requested but not found.

-c, —contents archive Lists the contents of the filesystem tree archive portion of the package archive. It is currently produced in the format generated by tar‘s verbose listing. -x, —extract archive directory Extracts the filesystem tree from a package archive into the specified directory.

Note that extracting a package to the root directory will not result in a correct installation! Use dpkg to install packages.

directory (but not its parents) will be created if necessary, and its permissions modified to match the contents of the package.

-X, —vextract archive directory Is like —extract (-x) with —verbose (-v) which prints a listing of the files extracted as it goes. -R, —raw-extract archive directory Extracts the filesystem tree from a package archive into a specified directory, and the control information files into a DEBIAN subdirectory of the specified directory (since dpkg 1.16.1).

The target directory (but not its parents) will be created if necessary.

The input archive is not (currently) processed sequentially, so reading it from standard input («—») is not supported.

—ctrl-tarfile archive Extracts the control data from a binary package and sends it to standard output in tar format (since dpkg 1.17.14). Together with tar(1) this can be used to extract a particular control file from a package archive. The input archive will always be processed sequentially. —fsys-tarfile archive Extracts the filesystem tree data from a binary package and sends it to standard output in tar format. Together with tar(1) this can be used to extract a particular file from a package archive. The input archive will always be processed sequentially. -e, —control archive [directory] Extracts the control information files from a package archive into the specified directory.

If no directory is specified then a subdirectory DEBIAN in the current directory is used.

The target directory (but not its parents) will be created if necessary.

-?, —help Show the usage message and exit. —version Show the version and exit.

OPTIONS

The string may reference any status field using the “$<field-name>” form, a list of the valid fields can be easily produced using -I on the same package. A complete explanation of the formatting options (including escape sequences and field tabbing) can be found in the explanation of the —showformat option in dpkg-query(1).

The default for this field is “$\t$\n”.

-zcompress-level Specify which compression level to use on the compressor backend, when building a package (default is 9 for gzip, 6 for xz). The accepted values are 0-9 with: 0 being mapped to compressor none for gzip. Before dpkg 1.16.2 level 0 was equivalent to compressor none for all compressors. -Scompress-strategy Specify which compression strategy to use on the compressor backend, when building a package (since dpkg 1.16.2). Allowed values are none (since dpkg 1.16.4), filtered, huffman, rle and fixed for gzip (since dpkg 1.17.0) and extreme for xz. -Zcompress-type Specify which compression type to use when building a package. Allowed values are gzip, xz (since dpkg 1.15.6), and none (default is xz). —[no-]uniform-compression Specify that the same compression parameters should be used for all archive members (i.e. control.tar and data.tar; since dpkg 1.17.6). Otherwise only the data.tar member will use those parameters. The only supported compression types allowed to be uniformly used are none, gzip and xz. The —no-uniform-compression option disables uniform compression (since dpkg 1.19.0). Uniform compression is the default (since dpkg 1.19.0). —threads-max=threads Sets the maximum number of threads allowed for compressors that support multi-threaded operations (since dpkg 1.21.9). —root-owner-group Set the owner and group for each entry in the filesystem tree data to root with id 0 (since dpkg 1.19.0).

Note: This option can be useful for rootless builds (see rootless-builds.txt), but should not be used when the entries have an owner or group that is not root. Support for these will be added later in the form of a meta manifest.

—deb-format=format Set the archive format version used when building (since dpkg 1.17.0). Allowed values are 2.0 for the new format, and 0.939000 for the old one (default is 2.0).

The old archive format is less easily parsed by non-Debian tools and is now obsolete; its only use is when building packages to be parsed by versions of dpkg older than 0.93.76 (September 1995), which was released as i386 a.out only.

EXIT STATUS

ENVIRONMENT

The —threads-max option overrides this value.

DPKG_COLORS Sets the color mode (since dpkg 1.18.5). The currently accepted values are: auto (default), always and never. TMPDIR If set, dpkg-deb will use it as the directory in which to create temporary files and directories. SOURCE_DATE_EPOCH If set, it will be used as the timestamp (as seconds since the epoch) in the deb(5)’s ar(5) container and used to clamp the mtime in the tar(5) file entries.

NOTES

Do not attempt to use just dpkg-deb to install software! You must use dpkg proper to ensure that all the files are correctly placed and the package’s scripts run and its status and contents recorded.

There is no authentication on .deb files; in fact, there isn’t even a straightforward checksum. (Higher level tools like APT support authenticating .deb packages retrieved from a given repository, and most packages nowadays provide an md5sum control file generated by debian/rules. Though this is not directly supported by the lower level tools.)

SEE ALSO

Package name: community/dpkg Version: 1.21.9-1 Upstream: https://tracker.debian.org/pkg/dpkg Licenses: GPL Manuals: /listing/community/dpkg/ Table of contents

Powered by archmanweb, using mandoc for the conversion of manual pages.

The website is available under the terms of the GPL-3.0 license, except for the contents of the manual pages, which have their own license specified in the corresponding Arch Linux package.

Установка пакетов ArchLinux

Все существующие дистрибутивы Linux для того, чтобы осуществлять операции по обновлению ПО и библиотек ОС в основном используют пакетные менеджеры. Пакетный менеджер является ключевой программой, который зачастую и отличает различие одного дистрибутива Linux от другого.

Общее описание технологии

Пакетный менеджер pacman является основным признаком дистрибутива ArchLinux. Archlinux pacman предназначен для установки программ и пакетов в дистрибутиве ArchLinux. pacman оперирует пакетами, которые, как и в случае с другими пакетными менеджерами представляют из себя бинарные архивы, содержащие некоторые данные для установки.

Pacman сам по себе может использоваться не только в ArchLinux и его производных, но и в прочих дистрибутивах. Возможна адаптация pacman для использования RPM, а также пакетов прочего типа, несовместимого со стандартным ArchLinux.

Pacman, как и RPM имеет возможность загрузки части пакета при обновлении. При работе pacman зачастую значительно быстрее обрабатывает транзакции, нежели это делает DPKG или RPM.

История разработки ArchLinux

Первые версии ArchLinux на самом деле являлись просто некоторой сборкой LFS, содержащим набор скриптов для сборки и развертывания дистрибутива. Очень долго, для установки самого дистрибутива pacman вообще не использовался, установочный образ содержал специализированную программу, называемую Arch Install Frimewere (AIF).

Сам по себе, дистрибутив в первых своих версиях содержал примитивную скрипт-сборочную пакетную систему, называемую Arch Build System (ABS). Суть такой примитивной пакетной системы заключался в предоставлении быстрого и удобного метода сборки пакетов из исходного кода. Но это не то, что хотел иметь собственно разработчик Arch Linux. По этой причине была разработана утилита pacman, которая и предназначалась для оперирования с уже собранными бинарными пакетами. ABS затем была переназначена для того, чтобы заниматься сборкой пакетов для pacman.

В дальнейшем, ABS в Archlinux позволил создать пользовательский репозиторий рецептов для сборки пакетов, называемый AUR. Из AUR возможна установка пакетов ArchLinux, которых нет даже в официальных репозиториях.

Установка пакетов в ArchLinux

Установка пакетов ArchLinux, их обновление, а также их удаление как мы уже поняли выше, осуществляются при помощи pacman. Данная утилита достаточно проста. Рассмотрим команды ее синтаксис:

$ sudo pacman [опция]

Вот основные опции программы, которые мы будем использовать:

Это основные опции, которые будут применяться в этой инструкции.

Установка пакетов ArchLinux

Сначала рассмотрим как выполняется установка программ ArchLinux с помощью Pacman из официальных репозиториев, а потом остановимся на пользовательском репозитории AUR. Теперь рассмотрим основные команды pacman archlinux.

Установка пакетов Pacman

Опции для pacman при использовании комбинируются в одну фразу, таким образом, например, для обновления репозиториев и обновления ОС команда будет выглядеть так:

Порядок расстановки опций значения не имеет, за исключением только того, что основной ключ, указывающийся большой буквой должен быть первым.

Установка конкретного пакета:

Удаление конкретного пакета:

Принудительное удаление конкретного пакета, с игнорированием зависимостей:

Поиск пакета в репозиториях:

Получение информации о пакете:

Поиск только среди установленных пакетов:

Просмотр списка всех установленных пакетов:

Просмотр списка файлов пакета:

Установка пакетов из AUR

К сожалению, не все пакеты есть в официальных репозиториях, многие вам придется искать пакеты на стороне. Большинство пакетов уже собраны и подготовлены пользователями в репозитории AUR. Для этого можно использовать пакет pacaur. Его можно установить командой:

Теперь вы можете использовать те же опции что и в утилите pacman в pacaur чтобы пользоваться AUR, например, поиск пакета:

Графический интерфейс Pacman

Для любителей пользоваться графическим интерфейсом вместо терминала в ArchLinux есть утилита pamac. Это простой менеджер приложений, чем-то похожий на стандартный менеджер приложений Ubuntu:

Для установки пакета достаточно открыть для него контекстное меню и нажать «Установить»:

Удаление пакетов выполняется тем же образом.

Выводы

В этой статье мы рассмотрели как выполняется установка пакетов ArchLinux различными способами. А также немного поговорили про историю разработки дистрибутива.

Arch Linux has a huge package repository. You should search for anything you need here first. Despite having such an extensive repository, there is still a chance that you may come across a package that isn’t available. If you can’t find what you are looking for, there is still a good chance that it may be available for Debian, Ubuntu, or Mint.

If you do find what you need but only have the deb package, you may want to try installing that deb package on your Arch system. There are multiple approaches that you could take to install a deb package on Arch Linux:

Use Debtap to Install Deb Package on Arch Linux

The Debtap tool can be used to convert a deb package to an Arch linux package. It can then be installed using pacman.

Download the debtap snapshot: HERE.

Convert the package:

Using Dpkg

Dpkg is actually available for Arch. Apparently it is meant for building packages on Arch that are meant to be installed on another system running Debian or Ubuntu. It isn’t actually meant to be used to install deb packages directly on Arch.

It used to be available from AUR but isn’t there anymore. It looks like it has been moved. You can get dpkg HERE.

Manually Install Deb Package on Arch Linux

To get the ar command you will need to install the binutils package:

Unpack the deb file and then unpack the two tarballs within it:

Check for Existing Arch Packages

Before trying to convert or install a deb package you should first check the repo. If it isn’t there you can also check AUR.

You can check the repo like this:

You can find packages on AUR HERE.

Download snapshot from AUR website and then do the following to build and install it:

You could also use an AUR helper to make things easier.

Use Alien

There is a tool called Alien that can convert from one package format to another. We haven’t verified if this supports converting from Debian to Arch.

How to Install Deb Package in Arch Linux

Deb files are meant for Debian-based distros, but what if you need to install it on Arch Linux? Here’s the fix.

Many non-Debian-based Linux distributions have their own ways of getting around this issue. However, out of all Linux distributions, Arch Linux has the most interesting ways of getting a Debian package working. In this article we outline three ways to accomplish this and discuss which one is best.

Note: the steps below will work for any Arch-based distro.

Content

Installing via the AUR

The AUR is the first place to check when looking for software that isn’t officially supported in Arch Linux. Always check here first. It’s a service that allows anyone to upload a PKGBUILD script, designed to automatically take software from various places, download some or all of the needed dependencies to run them and compile a native Arch Linux package.

When using the AUR, there are two ways to go about it:

1. Use an AUR Helper

For more information about AUR hepers and how to install them, refer to our list of five awesome AUR helpers. Once you have one, just search the AUR, install and go.

Chances are if you’re using Manjaro, Endeavour, Garuda or any of the other Arch-based distros, you’ll have an AUR helper installed. Have a look at your distro’s documentation to check out what is included. Both Garuda and Endeavour use yay.

2. Manual Installing AUR Packages

Another way of getting unofficial packages is by going to the AUR website, using the search bar, and downloading the “snapshot.” This is a less automated process, but it’s worth it if you want more granular control over how packages are made or installed. Instead of instantly installing the package, it’ll spit out a native package you can modify for your own purposes.

This means that if you have a custom personal repository set up, you can easily place these newly-built packages right in the repo for easy installation.

Note: if you just plan to use Arch’s base repositories and the AUR, installing packages with an AUR helper is a much better option than manual builds.

Most (if not all) programs that only come in DEB format will be found in the AUR. Here’s how to compile one as an Arch package from scratch.

in your terminal.

This will download the package’s git repository with a PKGBUILD configuration file for Arch’s powerful makepkg tool.

to navigate to the package’s build directory you just downloaded.

to create the package and install it automatically.

Install via Debtap

If, for some reason, a Deb you need isn’t in the AUR, install Debtap. It’s a program that dismantles a Debian package and makes it into an Arch package that your package manager can “understand.”

Installing Manually

Warning: This method is highly unsafe and should only be used when there is no other option and you already have an advanced understanding of how certain packages work and certain behaviors that Arch expects. For example, some applications (like Plymouth, Virtualbox, etc.) may require hooks into the kernel that can only be done by editing configuration files and re-building the kernel with those hooks. Even more, using this method does not also install the dependencies of your package.

Though this may involve a lot more tedium than previous methods, it’s more platform-independent, meaning you can use this method in many other distributions like Void Linux, Fedora, and openSUSE. I have not tested this in Gentoo and Slackware, so your mileage may vary with them due to how both distros like to handle installing packages.

Debian packages are archives with binaries inside, so no compiling is necessary. To install the files in any Deb package to Arch, first extract it to a folder. Keep in mind that you’ll also need to extract the archive known as “data” inside that folder as well.

For example, to install Google Chrome, you’d first cd into the extracted Deb folder with the extracted contents of “data.tar.xz” inside it.

Then, run the ls command to reveal all of the folders that reside in the data archive inside the Deb package. Keep in mind the names of these folders. cd into each directory and move the contents of these directories to where they belong on the system.

Frequently Asked Questions

1. Why Is Debtap Taking So Long?

In addition to this, the script Debtap converts files with uses only one CPU core, making single-core performance the determining factor that affects how long your system will take to complete the operation. Expect large packages to take up to a few minutes.

2. Can I Use a Graphical Installer After Running Debtap?

3. How does Debtap Compare with the AUR?

Wrapping Up

One of the best things about Arch Linux is how many ways users can install packages – from the AUR, to custom repositories, to decompiling other distributions’ packages so they’ll run. Though this information isn’t new, it’s certainly a good resource for those new to Arch and looking for ways to install their favorite programs.

Our latest tutorials delivered straight to your inbox