:
When using apt-get or some other GUI package management application to install a new package on Ubuntu or Debian Linux the following error message appears:
W:Failed to fetch cdrom://Ubuntu 14.04 LTS _Trusty Tahr_ - Release amd64 (20140416)/dists/trusty/main/binary-amd64/Packages Please use apt-cdrom to make this CD-ROM recognized by APT. apt-get update cannot be used to add new CD-ROMs
When using apt-get suite tools on Debian Linux you may notice a error message similar to the one below:
Traceback (most recent call last): File "/usr/bin/apt-listchanges", line 29, inimport anydbm ImportError: No module named 'anydbm'
Beautiful Soup is a Python package for parsing HTML and XML documents and it resides within a Debian package named python-bs4. However, python-bs4 package is a default package on Debian Linux system for Python 2 version. Therefore, if your intention is to use Python3 as a default environment you will need to also install Python3 and its corresponding version of BS4 python3-bs4. Let’s start by python3 installation:
# apt-get install -y vim python3
After a successful installation of python3 package make sure that python3 is set as default:
# update-alternatives --install /usr/bin/python python /usr/bin/python3.4 2 update-alternatives: using /usr/bin/python3.4 to provide /usr/bin/python (python) in auto mode
Confirm that python 3 is a default version:
# python --version Python 3.4.2
All what remains is to install Beautiful Soup parsing HTML and XML package to match python version 3:
# apt-get install python3-bs4
All done. Test Beautiful Soup parsing HTML and XML with the following example script:
#!/usr/bin/env python3
from urllib.request import urlopen
from bs4 import BeautifulSoup
html = urlopen("http://www.gnu.org")
bsObj = BeautifulSoup(html.read());
print (bsObj.title)
Introduction
How often do you need to install your favorite Linux distribution in a single year either virtually or using real hardware? How frequently it happens that you just want to test new release of certain Linux distribution so you install it on different partition or simply virtually using your current system as a host. How often do you need to deploy a server which is a complete clone of the one you configured yesterday. The installation part of any Linux system today is a very straightforward process. Nonetheless, the hardest and the most tedious part comes with a fine tuning, customization and configuration of your system’s services as well as your own user environment. You can simply copy your custom system configuration files from one system to another but engaging in this concept this task can become quite disorganized, time consuming and most importantly error-prone.
In this article, we are going to take a different approach which involves a creation of a Debian package archive containing all required custom user and configuration files. First part of this article describes a rather simple way on how to create a Debian package archive containing all custom files followed by its installation. In the second part, we will look at the way on how to create our own very basic Debian Repository and use it to deploy a simple website including Apache webserver installation and configuration on a freshly installed Linux system.
In this section, we create and install simple Debian package. The package will accommodate some sample user data to serve as an example.
It took you a while to configure your desktop to have it the way it best suits your needs and convenience. In your custom environment, you may for example include some bash scripts, create several aliases using .bashrc file or changed default behavior of a vim text editor by altering .vimrc file. Furthermore, you may also have customized numerous system configuration files such as /etc/network/interfaces and so on. All this hard work can be saved within a Debian package and installed and removed from any system with a single dpkg command. As a first step we need to create a bare minimum skeleton for a Debian package. This is a fairly simple task as it only involves a single DEBIAN/control file. So let us start by creating a directory named “myenv”. This directory will hold all data for our own version 1.0 Debian package.
$ mkdir myenv
In the next step, we need to create a control file:
$ cd myenv $ mkdir DEBIAN $ vi DEBIAN/control
phpVirtualBox allows you to manage locally or remotely your virtual machines running under VirtualBox via web-based interface. This config will describe an installation and basic configuration of phpVirtualBox on Debian Linux.
First, we need to install apache2 and php support:
# apt-get install libapache2-mod-php5 apache2 unzip wget
Next, we need to download phpVirtualBox. Please update your download link if necessary:
$ wget http://downloads.sourceforge.net/project/phpvirtualbox/phpvirtualbox-4.3-2.zip
Next, we will unzip and move the phpVirtualBoxcode into root directory of our apache2 webserver directory.
# unzip phpvirtualbox-4.3-2.zip # mv phpvirtualbox-4.3-2/ /var/www/html/vbox
Very useful tool to extract files from Debian package archive DEB (*.deb) is ar command. First, let’s download a sample debian package hello_2.10-1_amd64.deb:
$ wget http://ftp.us.debian.org/debian/pool/main/h/hello/hello_2.10-1_amd64.deb
Now, that we have downloaded our sample Debian package we can use ar command to list its content. This can be achieved by t option:
$ ar t hello_2.10-1_amd64.deb debian-binary control.tar.gz data.tar.xz
The typical question after we install a new package on our system is that what are the actual files ware installed and what is their location. This may be even less obvious if the final executable name intended to start your program has slightly different name than the package its self. In the following example we are going to install a dummy package hello using apt-get command:
# apt-get install hello ... (Reading database ... 7528 files and directories currently installed.) Preparing to unpack .../hello_2.9-2+deb8u1_amd64.deb ... Unpacking hello (2.9-2+deb8u1) ... Setting up hello (2.9-2+deb8u1) ...
Using a apt tools may result in a following error:
Traceback (most recent call last): File "/usr/bin/lsb_release", line 28, inimport lsb_release ImportError: No module named 'lsb_release' Traceback (most recent call last): File "/usr/bin/lsb_release", line 28, in import lsb_release ImportError: No module named 'lsb_release'
There are multiple way on how to determine whether a specific package is already installed on your system. The first dpkg command will list all currenlty installed packages on your system:
# dpkg -l
Let’s say you wish to do some changes to nginx source code in
order to add or remove some features before the actual nginx
package installation. In this config we will show how to recompile
nginx package on Debian linux.
First install package building tools:
# apt-get install dpkg-dev
Next, we need to install all nginx build dependencies:
# apt-get build-dep nginx
This short config will describe a installation of s3cmd Command Line S3 tool on Debian. First update your repository:
# apt-get update
Next, install Python package installer pip which will be later used to install s3cmd:
apt-get install python-pip
Using jigdo downloader is a smarter and greener way of downloading data from the Internet mirrors. In comparison to a regular download where you point your browser or wget command to a single mirror URL, jigdo allows for multiple mirrors where the main feature is to re-use a previously download ISO image of a lower version to use as base and thus only new packages not downloaded previously are downloaded.
For this reason using jigdo is often faster way of downloading debian ISO images. To start using you first need to install it on your system:
# apt-get install jigdo-file
Once the jigdo-file package is downloaded your can start using jigdo do download official Debian instillation images. All you need is the URL of the *.jigdo file of the image you intend to download. In the example below we download Debian Jessie KDE iso image. First start jigdo:
$ jigdo-lite Jigsaw Download "lite" Copyright (C) 2001-2005 | jigdo@ Richard Atterer | atterer.net Getting mirror information from /etc/apt/sources.list -----------------------------------------------------------------