You are not logged in.

#1 2011-11-11 21:57:02

fsckd
Forum Moderator
Registered: 2009-06-15
Posts: 3,646

Common Problems and Issues

These are some of the common issues that new Arch users experience.

Your issue may already be known and workarounds exist. Please check the front page Arch news, Announcements list and other mailing lists. Also do search the fine wiki and forums.

Good luck.

1. File not found

If you encounter errors trying to install an application, such as, "error: failed retrieving file 'foobar.pkg.tar.xz' from extra: Not Found", this invariably means one of two things: either your local database is out-of-date and needs to be resynced with a 'pacman -Syyu', or your mirror is out of date and you need to choose one that is up-to-date.

Arch is a rolling release distribution and you need to ensure that pacman is aware of the latest versions of software. If in doubt, go to the Package Database at http://www.archlinux.org/packages/ and check what the current version of 'foobar' is in the repos.

You can always check how up-to-date your mirror is here: http://www.archlinux.org/mirrors/status/
and generate a new mirror list with reflector: https://wiki.archlinux.org/index.php/Reflector

2. FILENAME exists in Filesystem

Pacman gives an error similar to,

error: failed to commit transaction (conflicting files)
foobar: /path/to/file exists in filesystem

This is because pacman has detected a file conflict. Pacman will not blindly overwrite files and instead aborts. As a user, you must figure out what is causing the conflict and act accordingly. See
the wiki for possible solutions.

3. error: failed to commit transaction (invalid or corrupted package)

There are two ways to interpret this message: the signature for the package is invalid, so check your keyring is up-to-date and that you are synching with an up-to-date mirror, or the package was only partially downloaded and is indeed corrupt. If the latter, delete it manually from your cache, resynch your local database and reinstall the package with -Syyu $package.

4. pacman-key hangs

If the command pacman-key --init takes a long time to finish it is because your system does not have enough entropy. The process should normally take no more than a few minutes. See the wiki article on pacman-key. That article also includes information for when operating over ssh.

5. Downgrading packages

A guide to downgrading packages can be found on the wiki.

6. When will $package be in the repos?

When it is ready.

If you find this answer unsatisfactory, you can always build your own package using ABS or asp.


aur S & M :: forum rules :: Community Ethos
Resources for Women, POC, LGBT*, and allies

Offline

Board footer

Powered by FluxBB