The first method you can try is to reconfigure the package database. Here are a few things you can try (run sudo apt update after each). What I have to do You don't mention the entire apt readout, but one of your packages may be broken. Hi there, I'm using kali linux I still getting this error while trying to download git : Sub-process /usr/bin/dpkg returned an error code (1) For more information, see " Caching your GitHub credentials in Git." You can also store the token in a plain text file that Git can read before every Git will temporarily store yourĬredentials in memory until an expiry interval has passed. Instead of manually entering your PAT for every HTTPS Git operation, you can cache your PAT with a Git client. You can update your credentials in the Keychain to replace your old password with the token. If you are not prompted for your username and password, your credentials may be cached on your computer. If your repository uses an SSH remote URL, you will need to switch the remote from SSH to HTTPS. Personal access tokens can only be used for HTTPS Git operations. Once you have a token, you can enter it instead of your password when performing Git operations over HTTPS.įor example, on the command line you would enter the following: $ git clone Why? The process is described here: Creating a personal access token Using a token on the command line In addition to performing the function of upgrade, this option also intelligently handles changing dependencies with new versions of packages apt-get has a "smart" conflict resolution system, and it will attempt to upgrade the most important packages at the expense of less important ones, if necessary.įirst, you need to create a personal access token (PAT). An update must be performed first so that apt-get knows that new versions of packages are available. New versions of currently installed packages that cannot be upgraded without changing the install status of another package will be left at their current version. Packages currently installed with new versions available are retrieved and upgraded under no circumstances are currently installed packages removed, nor are packages that are not already installed retrieved and installed. Used to install the newest versions of all packages currently installed on the system from the sources enumerated in /etc/apt/sources.list (5). An update should always be performed before an upgrade or dist-upgrade. The indexes of available packages are fetched from the location(s) specified in /etc/apt/sources.list (5). Used to re-synchronize the package index files from their sources. If that doesn't work, then try re-building your sources.list using this tool: Ubuntu Sources List Generator Command Sudo apt -y upgrade & sudo apt autoremove -y Processing triggers for libc-bin (2.23-0ubuntu11). Processing triggers for man-db (2.7.5-1). Selecting previously unselected package libpcre2-8-0:amd64. Done The following additional packages will be installed: git-man libpcre2-8-0 Suggested packages: git-daemon-run | git-daemon-sysvinit git-doc git-el git-email git-gui gitk gitweb git-cvs git-mediawiki git-svn The following NEW packages will be installed: libpcre2-8-0 The following packages will be upgraded: git git-man. Done Building dependency tree Reading state information. $ sudo apt-get install git -yes Reading package lists. $ sudo add-apt-repository ppa:git-core/ppa -yes -update gpg: keyring `/tmp/tmpk8m4os6a/secring.gpg' created gpg: keyring `/tmp/tmpk8m4os6a/pubring.gpg' created gpg: requesting key E1DF1F24 from hkp server gpg: /tmp/tmpk8m4os6a/trustdb.gpg: trustdb created gpg: key E1DF1F24: public key "Launchpad PPA for Ubuntu Git Maintainers" imported gpg: Total number processed: 1 gpg: imported: 1 (RSA: 1) OK
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |