pacman stopped working

yowwww · 2005-01-26 07:48:59

I've looked at the log for pacman and I'm not really too sure how I could repair this. When I open a term and type in a pacman command, it starts off sounding like it is going to work (old box, I can hear it churning), but then it doesn't do anything). The rest of the system works fine afaict. Here is the relevant info from /var/log/pacman.log:

[01/24/05 05:09] starting full system upgrade
[01/24/05 05:09] installed glibc (2.3.4-2)
[01/24/05 05:09] installed ncurses (5.4-1)
[01/24/05 05:09] installed readline (5.0-1)
[01/24/05 05:09] installed bash (3.0-3)
[01/24/05 05:09] installed freetype1 (1.3.1-2)
[01/24/05 05:09] installed expat (1.95.8-1)
[01/24/05 05:09] installed zlib (1.2.2-1)
[01/24/05 05:09] installed freetype2 (2.1.9-2)
[01/24/05 05:09] warning: /etc/fonts/local.conf saved as /etc/fonts/local.conf.pacorig
[01/24/05 05:09] installed fontconfig (2.2.3-1)
[01/24/05 05:10] installed binutils (2.15-1)
[01/24/05 05:10] installed gcc (3.4.3-1)
[01/24/05 05:10] installed libpng (1.2.7-1)
[01/24/05 05:11] installed xorg (11R6.8.1-1)
[01/24/05 05:12] installed libjpeg (6b-3)
[01/24/05 05:12] installed libtiff (3.7.1-2)
[01/24/05 05:12] installed pkgconfig (0.15.0-1)
[01/24/05 05:12] installed glib2 (2.6.1-1)
[01/24/05 05:12] installed atk (1.9.0-1)
[01/24/05 05:12] installed pango (1.8.0-1)
[01/24/05 05:12] installed gtk2 (2.6.1-2)
[01/24/05 05:12] upgraded vte (0.11.11-2 -> 0.11.11-3)
[01/25/05 03:21] synchronizing package lists
[01/25/05 03:31] starting full system upgrade
[01/25/05 03:32] could not extract lib/ld-2.3.3.so: Text file busy
[01/25/05 03:32] errors occurred while installing glibc
[01/25/05 03:32] installed glibc (2.3.4-2)
[01/25/05 03:32] installed freetype1 (1.3.1-2)
[01/25/05 03:32] installed expat (1.95.8-1)
[01/25/05 03:32] installed zlib (1.2.2-1)
[01/25/05 03:32] installed freetype2 (2.1.9-2)
[01/25/05 03:32] installed fontconfig (2.2.3-1)
[01/25/05 03:33] installed binutils (2.15-1)
[01/25/05 03:33] could not extract usr/bin/i686-pc-linux-gnu-g++: File exists
[01/25/05 03:33] could not extract usr/bin/i686-pc-linux-gnu-c++: File exists
[01/25/05 03:33] could not extract usr/bin/i686-pc-linux-gnu-gcc-3.4.3: File exists
[01/25/05 03:33] could not extract usr/bin/i686-pc-linux-gnu-gcc: File exists
[01/25/05 03:33] errors occurred while installing gcc
[01/25/05 03:33] installed gcc (3.4.3-1)
[01/25/05 03:33] installed libpng (1.2.7-1)
[01/25/05 03:34] installed xorg (11R6.8.1-1)
[01/25/05 03:34] installed pkgconfig (0.15.0-1)
[01/25/05 03:34] installed glib2 (2.6.1-1)
[01/25/05 03:34] installed gettext (0.14.1-2)
[01/25/05 03:34] installed popt (1.7-2)
[01/25/05 03:34] installed desktop-file-utils (0.10-1)
[01/25/05 03:35] upgraded openoffice2 (1.9.65-1 -> 1.9.69-1)
[01/25/05 03:37] could not extract lib/ld-2.3.3.so: Text file busy
[01/25/05 03:37] errors occurred while installing glibc
[01/25/05 03:37] installed glibc (2.3.4-2)
[01/25/05 03:37] installed ed (0.2-2)
[01/25/05 03:37] installed openoffice2-spell-en (20040623-1)

I was getting some looping for a while in terms of it wanting to install packages that were already installed and I also got a message saying that libz.so was too small. I just copied over those libs from another Arch box which seemed to fix the issue at the time. However, now, after continuing the upgrade, more problems exist. I will try some more things to see if I can correct. This install was originated from the 0.6 iso long ago and has been running perfectly till just yesterday.

I would rather not re-install so if anyone has any ideas, it would be appreciated.

TIA

sarah31 · 2005-01-27 17:23:13

Th ething that comes to mind is the must be an issue with your zlib install... mind you with pacman not working I am not sure how to rectify it. Per haps you could download the pacman source and install it from source to see if that fixes anything.

Also that error for glibc part of your instal worries me too. but then it says it installed

yowwww · 2005-01-27 17:56:16

thanks for your response.

There are a few things in the log that worry me too. I did try downloading the pacman package and extracting it to the / directory but it still doesnt work. I think I am going to try using abs and just go through almost all the packages in the list until something hopefully works and corrects it.

edit: abs didn't work unfortunately, it just sits there as does pacman. So I am relegated to compiling from source...

I'm going to make a list here in hopes that I can eventually post something that worked

zlib - done
gcc - failed:

make[1]: *** No rule to make target `gnu/java/security/provider/DSAParameters.d'.  Stop.
make[1]: Leaving directory `/home/ctm/gcc-3.4.3/i686-pc-linux-gnu/libjava'
make: *** [all-target-libjava] Error 2

sarah31 · 2005-01-27 18:42:39

you should give glibc a shot too.

sorry about taking so long to get back to you but I wasn't really able to properly process your post yesterday. I read it and just drew a blank on suggestions. I got a bit more sleep last night though and was able to think up some sort of response.

phrakture · 2005-01-27 19:00:47

could it be network issues?
does pacman output anything at all?

yowwww · 2005-01-28 06:02:02

It's not a network issue because everything else seems to work fine. I updated my previous post with the indication that building gcc failed. I will try glibc next. Thanks for the suggestions.

abs can update, but makepkg does not work, I just get this:

[root@celly glibc]# makepkg -fic
==> Making package: glibc  (Fri Jan 28 01:03:49 EST 2005)
==> Checking Runtime Dependencies...

and it just sits there. So I have been trying to compile things from source. I am using the sources posted on the Arch site so I am trying to keep things are cohesive as possible.

cactus · 2005-01-28 06:12:59

try manually downloading the tarballs for zlib and pacman.
create a temp directory
untar the two tarballs there.
copy the files to where they are supposed to be...
note: the directory structure will be obvious..

then try running update with pacman again.

yowwww · 2005-01-28 06:20:51

As mentioned in a previous post, I did try that with pacman. I also tried that with zlib and it made no difference.

cactus · 2005-01-28 06:30:14

[01/25/05 03:37] could not extract lib/ld-2.3.3.so: Text file busy
[01/25/05 03:37] errors occurred while installing glibc

(eliott@hermes ~)$ pacman -Qo /lib/ld-2.3.3.so
/lib/ld-2.3.3.so is owned by glibc 2.3.4-2

Try the same with glibc. It looks like it borked the upgrade for some reason.

yowwww · 2005-01-28 06:48:02

ok, I'm trying to do gcc again now and I will try glibc after that.
Thanks for the input

edit -- glibc is a mess to compile, hopefully I don't end up at that point.

phrakture · 2005-01-28 15:24:18

is your pacman database screwed up? /var/lib/pacman ?

yowwww · 2005-01-28 17:58:13

well, gcc failed again with that same java error.

phrakture - im not sure how you mean by 'screwed up'. Here is what is in that directory:

current  extra  local  testing  unstable

other than that, i'm not sure what determines if it is screwed up or not, could you be more specific?

cactus · 2005-01-28 21:32:55

ok. clarification.
Are you trying to recompile gcc and glibc?

I was just talking about extracting the packman package tarballs in a temp dir, and moving the binary files to where they should go (overwriting the existing ones).
Since the package is already installed, there should be no issue with needing to update the package database, and no "requirements" causing problems....

Simply dismiss the above if this is actually what you did, and chalk it up to me not understanding you.

phrakture · 2005-01-28 21:39:22

cactus wrote:

ok. clarification.
Are you trying to recompile gcc and glibc?
I was just talking about extracting the packman package tarballs in a temp dir, and moving the binary files to where they should go (overwriting the existing ones).
Since the package is already installed, there should be no issue with needing to update the package database, and no "requirements" causing problems....
Simply dismiss the above if this is actually what you did, and chalk it up to me not understanding you.

yeah, I'd agree with this...
download from archlinux.org the pkg files for glibc and gcc.
run pacman -A <file> and see if that installs (could be downloading isn't working).
if that fails still, then untar the packages and move the files where they need to go.

yowwww · 2005-01-29 05:19:40

To clarify, pacman does not work in any way shape or form so it is not an option for me to use it. I was actually trying to compile glibc and gcc from source. I will attempt to unpack the packages to their appropriate directories and see if that makes any diffference. The reason why I was discouraged with that option was because I did start out doing it with other packages and it made no difference. I have not tried doing that with gcc and glibc though, so I will try that and post back. Sorry if I wasnt clear before. There are a lot of different methods to try here so it is hard to keep track and use the correct syntax. Thanks for the continued input.

edit: OK, none of that made any difference. I am starting to really consider just reinstalling my root partition. I would just need to back up files in the / dir such as fstab and smb.conf mainly since I have a separate /home and /boot.

unless there are any other suggestions, maybe a reinstall of the / would be best anyway.

update - I reinstalled the / partition and all is well again. It got to the point where it was just the easiest thing to do and it gave me a chance to try out the final Arch 0.7 cd for the first time. Peculiar that DevFS is still default, but otherwise, it was solid.

cactus · 2005-01-29 05:57:11

after doing the overwriting, have you rebooted? The inodes might not be being released if something is using them.

yowwww · 2005-01-29 18:18:05

yes, I did reboot, it made no difference. It's working fine now since reinstalling the / though. Thanks to everyone who offered help on this situation

Xentac · 2005-01-30 22:57:02

You say pacman doesn't work, but does pacman.static? It's statically compiled so anything short of glibc being hosed shouldn't stop it from working.

Benedict_White · 2005-01-30 23:09:43

If you want to make a package, with makepkg, and can't seem to get makepkg to download a file, download it manually and place it in /var/cache/pacman/src/ and don't unpack it. Makepkg will get it from there.

Xentac · 2005-01-31 02:36:06

Benedict_White wrote:

If you want to make a package, with makepkg, and can't seem to get makepkg to download a file, download it manually and place it in /var/cache/pacman/src/ and don't unpack it. Makepkg will get it from there.

Makepkg freezes resolving dependencies, which it calls pacman to do.

Benedict_White · 2005-01-31 09:22:55

Rename the directory in which your package database is located, and see if that forces pacman to cleanly get a new copy.

I think it is /var/lib/pacman/

Then do a pacman -Syu and see what happens.

scarecrow · 2005-01-31 12:55:45

IMHO if you make a fresh 0.7 installation (which is what you already did) you should avoid installing devfsd completely right from the start (untich the package from the BASE list)... this should give you much less worries later.
The system installs and runs fine with just udev installed- unless of course you want to use 2.4.X kernels.

Arch Linux

#1 2005-01-26 07:48:59

pacman stopped working

#2 2005-01-27 17:23:13

Re: pacman stopped working

#3 2005-01-27 17:56:16

Re: pacman stopped working

#4 2005-01-27 18:42:39

Re: pacman stopped working

#5 2005-01-27 19:00:47

Re: pacman stopped working

#6 2005-01-28 06:02:02

Re: pacman stopped working

#7 2005-01-28 06:12:59

Re: pacman stopped working

#8 2005-01-28 06:20:51

Re: pacman stopped working

#9 2005-01-28 06:30:14

Re: pacman stopped working

#10 2005-01-28 06:48:02

Re: pacman stopped working

#11 2005-01-28 15:24:18

Re: pacman stopped working

#12 2005-01-28 17:58:13

Re: pacman stopped working

#13 2005-01-28 21:32:55

Re: pacman stopped working

#14 2005-01-28 21:39:22

Re: pacman stopped working

#15 2005-01-29 05:19:40

Re: pacman stopped working

#16 2005-01-29 05:57:11

Re: pacman stopped working

#17 2005-01-29 18:18:05

Re: pacman stopped working

#18 2005-01-30 22:57:02

Re: pacman stopped working

#19 2005-01-30 23:09:43

Re: pacman stopped working

#20 2005-01-31 02:36:06

Re: pacman stopped working

#21 2005-01-31 09:22:55

Re: pacman stopped working

#22 2005-01-31 12:55:45

Re: pacman stopped working

Board footer