You can configure apt via apt.conf files.
Here is a command I use on my server (as root):
cat > /etc/apt/apt.conf.d/01norecommend << EOF
To see if apt reads this, enter this in command line (as root or regular user):
apt-config dump | grep Recommends
According to the IRC channel for Debian, jessie-updates is now not supported:
Oldstable: Debian Jessie, jessie-updates and jessie-backports REMOVED 2019-03-24
Your solution is either to upgrade to Stretch, or update your /etc/apt/sources.list to the following:
deb http://archive.debian.org/debian/ jessie main
deb-src http://archive.debian.org/debian/ ...
In short: apt-get install does everything that is needed that your system can successfully execute the new installed software application.
From the manpage:
All packages required by the package(s) specified for installation
will also be retrieved and installed.
Those packages are stored on a repository in the network ...
You probably changed the file permissions on your /tmp folder, check with
ls -lad /tmp
The normal settings for /tmp are 1777, which ls shows as drwxrwxrwt. That is: wide open, except that only the owner of a file can remove it (that's what this extra t bit means for a directory).
If the settings are wrong, you can restore them with:
chmod 1777 /tmp
I would ...
No, apt is Debian specific. apt uses dpkg to install .deb files (which are binary files that are specific to Debian).
Red Hat based Linux distributions uses the rpm package management system. You can use yum to retrieve and install rpms on Red Hat distributions:
yum search som-package-name
yum install some-package-name
If you want to install an rpm that ...
There is a MySQL server running, but we failed in our attempts to stop it.
Stop it yourself and try again!
I had this problem yesterday when the mariadb 10.1 server package failed to update and install correctly. In the end deleting the following symbolic link may have fixed the problem.
lrwxrwxrwx 1 root ...
Updated 2016-07-27: a wheezy-backports is now available for Git 1.9.1. Instructions still applies to install a more recent version or for Jessie.
When a newer version of a backport package isn't available, you have two options:
Ask the package maintainers to prepare a backport. It's not guaranteed to work but some maintainers are positive about making ...
You can find the description of remove, autoremove, purge, clean and autoclean, as well as the syntax in the manpages for apt-get: man apt-get.
If you are still unsure after reading it though (I was) the best way to clarify it is to try it out.
Below is an example of a full dependency tree for vim:
You can get it with:
apt-rdepends -d vim > vim.dot
You can use my Launchpad PPA, currently it gives you git 1.8.0.
Git is available for the following Ubuntu distributions:
Ubuntu 12.10 (Quantal)
Ubuntu 12.04 (Precise)
Ubuntu 11.10 (Oneiric)
Ubuntu 11.04 (Natty)
Ubuntu 10.10 (Maverick)
Ubuntu 10.04 (Lucid)
To install my git repository follow the instructions at: Git Packages for Ubuntu • A Virtual Home
There is a project out there that claims to support apt style repositories (as well as the apt-get command) on RPM based distros. It is called apt-rpm and is used as the default package manager on a few distros, though not on RHEL/Fedora.
It seems not to be really maintained since ~2008; it may have incremental patches or fixes since then, but ...
Short answer: It is possible that you actually do not want to do this.
Why is that?
There has been a lot of discussion on this particular functionality. One such is in this (duplicate)bug report and the one it is linked to.
Discussion at the bug report also explains that "--ignore-missing" only applies if the there is an issue downloading a package that ...
Solved by doing a docker system prune(?!). Is it the image that was in a bad state? Was it a problem caused by not having enough disk space?
Maybe something to consider if you're having the problem inside a docker.
Is falling back to lower-level tool such as dpkg an option?
dpkg --remove foo bar libperl-dev
dpkg: warning: ignoring request to remove foo which isn't installed
dpkg: warning: ignoring request to remove bar which isn't installed
(Reading database ... 169132 files and directories currently installed.)
Removing libperl-dev ...
To remove packages config ...
This feature is provided by the command-not-found( Its function is to suggest alternatives and corrections in case of mistyping etc. ) package. Ubuntu installs it by default.
how does it work?
The way it works is through the command_not_found_handle() function in bash. bash provides a hook which is basically a function that is invoked when a command is ...
Apparently git on a Linux system refers to GNU Interactive Tools. The command to download the Git version control system on Ubuntu is:
sudo apt-get install git-core git-doc
If you want or need additional tools (including GUI and Web access), you can:
sudo apt-get install gitweb git-gui gitk git-email git-svn
I faced a similar issue recently with ubuntu 16.04.3 LTS, what worked for me is as following -
First you need to create an empty file, as following :-
adminuser@sandbox:~$ sudo touch /var/lib/dpkg/status
Now run update & upgrade :-
adminuser@sandbox:~$ sudo apt update && sudo apt upgrade
Probable you may end up seeing something like this --
I have no idea if it is still relevant for you to get help on this, but here is a summary of the things one could do to help in such situation
(from here at Appuals (appuals.com)) :
Method 1: Use the -f parameter (I know you already did that, but I gather everything here altogether)
sudo apt-get install -f
sudo dpkg --configure -a
sudo apt-get install -f
I use apt-get remove --purge (aka apt-get purge) for the dependency following with a list of packages. To handle packages that don't exist I filter out packages that are not installed with the following script.
for pkgToRemove in $(echo $pkgToRemoveListFull); do
$(dpkg --status $pkgToRemove &...
You can still use the Git PPA for Ubuntu Precise by telling apt to build from the latest source it finds there. The distributions are similar enough that this should work just fine.
I used it with success on Raspbian (which is based on wheezy) to get packages for armhf, but it should work for any architecture.
First add the GPG key for the PPA:
If you want to upgrade a specific package in Debian 7 (Wheezy), you have the option to use backports by simply adding to your /etc/apt/sources.list the following lines:
deb http://cloudfront.debian.net/debian wheezy-backports main
deb-src http://cloudfront.debian.net/debian wheezy-backports main
Then, for installing/upgrading git, run the commands:
apt is a Debian only application that was inherited by ubuntu. Having it work on AIX would be akin to trying to run yum on Ubuntu. There is no reason whatsoever this command would work
Unfortunately, it looks like AIX systems don't have a repository for its package manager at all - you will need to obtain AIX packages (which seem to be RPMs) or compile ...
Oh man, you are definitely going to have a very bad time.
You come from Ubuntu. Here you don't have sudo, but you may have su. Check it and if you do have it, this problem is solved.
AIX not having Advanced Packaging Tool framework support is not easily solvable. Take into account that if you ran fedora or CentOS you would not also have those, and you ...
At the root of an apt respository there is a Release file, which contains hashes of the various Contents, Release, and Packages files. The Packages files in turn have hashes of the individual .deb package files. At the same location as the root Release file, there is a Release.gpg file, which contains a GPG digital signature of the Release file, made with a ...