During regular software updates in Ubuntu Linux distros, you may encounter a situation where some packages have been kept back and are not updated. This could lead to disparities in the version of packages across different systems.
Jupyter Notebook is a web application used to produce computational documents, commonly called “notebooks” which can contain human-readable text, executable code, charts, and more. When used together with Python and libraries like pandas and Matplotlib, Jupyter notebooks are an excellent tool we can use for presentations and data analysis.
If you are familiar with Python, you surely used pip: the Python package installer. With pip, we can install packages “globally” or in virtual environments. Virtual environments are mainly used to install dependencies of specific projects, so to develop them in isolation. We usually install packages, “globally”, instead, when want to access the utilities they provide from anywhere. By using pipx we can get the best of both approaches: we can install each application in its own virtual environment, and, at the same time, access it globally.
Debian, also known as “the universal operating system”, is one of the oldest Linux distributions. At any point in time there are always three main Debian releases: stable, testing and unstable. The “stable” release represents the official Debian release: it is rock solid, ready for production, and contains packages which doesn’t change much. The “testing” release contains packages which are on their road to be accepted into stable, and finally, the “unstable” release is the one with the most updated versions of software, used for the distribution development.
RPM is the acronym for Red Hat Package Manager: we use it to reference both the software package format and the low-level package manager used by the Red Hat family of distributions. Since version 4.12 of the latter it is possible to declare packages “weak dependencies”, which are installed by default, but not strictly required.
In case you are wondering when a software package was installed on your Linux system, the information is stored by the package manager and can be accessed via the command line. This can come in handy for a number of reasons, such as when troubleshooting issues that started on a certain date, to see if any packages installed at that time could be causing the problem. In this tutorial, you will learn how to show the installation date for a software package on all major Linux distributions.
Software installation packages for Linux systems will sometimes come in the form of an RPM file. These are files intended for installation on RHEL-based Linux distributions like Red Hat Enterprise Linux, Fedora, CentOS, etc. On Ubuntu, the equivalent packages are DEB files. However, it is possible to convert RPM files to DEB and install them on Ubuntu Linux.
Homebrew (or just “Brew”) is a package manager that is well known as the go-to package management tool for MacOS, but it also works on Linux systems. It has been providing Apple users with a means of installing Linux packages on their devices for many years now, and the development has since expanded it into a tool for Linux as well. Homebrew is free and open source, and its big catalog of installable software has made it an attractive supplement to built in package managers such as apt and dnf on some systems.
Vim is definitely one of the most venerated text editors in the Unix world. Although its learning curve can be pretty steep when accustomed to more traditional text editors, its usage can dramatically improve productivity. A lot of plugins are available for the editor; almost always their source code is hosted on Github or similar platforms based on Git. To manage such plugins, several third-party plugin managers were developed in time, such as Pathogen or Vim-Plug, but since version 8 of the editor, a native way to manage plugins was introduced.