Package from AUR failed to install after doing many steps, how to rm?

trusktr · 2010-02-27 10:37:41

How can I see what files have been left on my hard drive after a package failed to install. I can't pacman -Rsu the package because it didnt install, but now i got some other packages that i don't need then. and probably some other stuff while the package was being extracted..

How can i prevent from leaving a messy trail?

Runiq · 2010-02-27 10:52:12

If the package is from the AUR, you should have gotten an archive like $pkgname-$pkgver-$pkgrel-$arch.pkg.tar.gz (example: libetc-0.4-2-x86_64.pkg.tar.gz). You can see what files are in that archive with:

$ tar -tf libetc-0.4-2-x86_64.pkg.tar.gz
.PKGINFO
.INSTALL
usr/
usr/lib/
usr/lib/libetc.so.0
usr/lib/libetc.so
usr/lib/libetc.so.0.4

The PKGINFO and INSTALL files are for the package database while the the rest of the files are from the package.

Last edited by Runiq (2010-02-27 10:52:36)

trusktr · 2010-02-27 11:42:07

I used yaourt to attempt to install it. oooh, i see. So I can see what files were being extracted, then do a search for them to see if they are indeed on my system? gotcha!

I'm a total newb and have never dealt with the tar command, .pkginfo, or .install files before, hehe.

I will check this out in a lil bit!

trusktr · 2010-02-27 11:46:42

Hey, can tar unzip .zip files by the way?

Runiq · 2010-02-27 12:13:12

I don't think so, but there's unzip (which unzips .zips), p7zip (which unzips a lot more), and xarchiver (frontend to several archive formats, GTK+). These are all in the repos.

Oh, and regarding tar, there's always the manpages

loafer · 2010-02-27 12:22:45

trusktr wrote:

but now i got some other packages that i don't need

If it also installed some now unwanted dependencies you can always check what they are by looking at /var/log/pacman.log.

Runiq · 2010-02-27 12:37:50

loafer wrote:

trusktr wrote:
but now i got some other packages that i don't need
If it also installed some now unwanted dependencies you can always check what they are by looking at /var/log/pacman.log.

Whoops, sorry, I didn't see that part of the post.

These packages were probably installed as dependencies (if you were using the -s switch to makepkg) and hence can be displayed with pacman -Qdt. (This command lists those dependencies that don't have any package that actually depends on them).

By the way, if you want to remove unneeded dependencies after (successfully or unsuccessfully) building a package with makepkg, try makepkg -r (or makepkg -sr, to also install dependencies automatically before building).

Gen2ly · 2010-02-27 20:38:16

What do you mean a package failed to install, trusktr? If I get your meaning, pacman installed some of the files and then stopped??? If this is what you mean, I personally have never seen this before. Pacman checks before it installs if their are file conflicts, and then after than it's the simple matter of just copying files to their correct places. Perhaps if you can give some better details... if this is the case, this most certainly be reported as a bug as this definitely shouldn't happen.

loafer · 2010-02-27 20:49:23

It looks like yaourt started to build the package, called pacman which installed the deps and then the PKGBUILD failed for some reason.

Gen2ly · 2010-02-27 21:12:52

Ahhhhh... yeah, ok that makes more sense.

trusktr · 2010-02-28 19:39:38

Yeah gen2ly, i was using yaourt to get a package from AUR.

I was able to uninstall the extra packages that were uninstalled, but is it possible that when the PKGBUILD failed that it left some random files somewhere? That's what I trully want to know. The other dependancies i have already removed.

Hey thanks for the info on unzip, Runiq! unzip works miracles!!!! I installed it, and now the front end "File Roller" AKA "Archive Manager" in Gnome can suddenly handle .zip files! It's awesome! no need for p7zip or xarchiver.

Every newbie or windows transferee should know about it!

But anyways, is it possible the failed PKGBUILD left files somewhere?

Runiq · 2010-02-28 19:54:49

It leaves files in the build directory – namely, the sources that were needed to build the package in question (continuing my example above: libetc-0.4.tar.gz) as well as "src" and "pkg" directories that contain the sources to be built and the content of the package to be built, respectively. However, unless you give the -i switch (which installs a package right after successfully building it), the files aren't installed anywhere in your file system, so you're safe if you just delete the pkg and src directories.

Edit: trusktr, I hereby command you to read this.

Last edited by Runiq (2010-02-28 19:58:53)

Arch Linux

#1 2010-02-27 10:37:41

Package from AUR failed to install after doing many steps, how to rm?

#2 2010-02-27 10:52:12

Re: Package from AUR failed to install after doing many steps, how to rm?

#3 2010-02-27 11:42:07

Re: Package from AUR failed to install after doing many steps, how to rm?

#4 2010-02-27 11:46:42

Re: Package from AUR failed to install after doing many steps, how to rm?

#5 2010-02-27 12:13:12

Re: Package from AUR failed to install after doing many steps, how to rm?

#6 2010-02-27 12:22:45

Re: Package from AUR failed to install after doing many steps, how to rm?

#7 2010-02-27 12:37:50

Re: Package from AUR failed to install after doing many steps, how to rm?

#8 2010-02-27 20:38:16

Re: Package from AUR failed to install after doing many steps, how to rm?

#9 2010-02-27 20:49:23

Re: Package from AUR failed to install after doing many steps, how to rm?

#10 2010-02-27 21:12:52

Re: Package from AUR failed to install after doing many steps, how to rm?

#11 2010-02-28 19:39:38

Re: Package from AUR failed to install after doing many steps, how to rm?

#12 2010-02-28 19:54:49

Re: Package from AUR failed to install after doing many steps, how to rm?

Board footer