Historical bug tracker for the Pacman package manager.
The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacman/-/issues
This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.
The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacman/-/issues
This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.
FS#924 - Pacman upgrade borkage
|
DetailsI'm hoping this is a temporary issue, but I got a whole bunch of nonsense when I went to do a pacman update today. It also offerred to upgrade Pacman (to a version from testing) and I hoped that would work. However, the same problems persist (so at least I can not blame it on the new Pacman, as I would happily roll back to avoid these issues).
System-wise I am running a regularly-updated Arch install (installed with 0.6-base, have upgraded since then) which has been up for a few days now and this is the first time Pacman has failed in such a manner. Here is a log of my last Pacman session (also posted in the "Pacman" forum): I don't know what's going on but something is seriously a-bork: [code] 03:02:59 <+delysid|~> sudo pacman -Syu :: Synchronizing package databases... gnustep [/var/abs/gnustep.repo/] 100% LOCAL testing [################] 100% 1K 4.8K/s 00:00:00 current [################] 100% 39K 51.5K/s 00:00:00 extra [################] 100% 136K 223.0K/s 00:00:00 unstable [################] 100% 1K 5.7K/s 00:00:00 error: could not cwd to /tur/bfinch/: 550 /tur/bfinch/: No such file or directory failed to synchronize bfinch error: anonymous login failed Control socket read failed: Success failed to synchronize contrasutra error: anonymous login failed Control socket read failed: Success failed to synchronize deepfreeze error: anonymous login failed Control socket read failed: Success failed to synchronize dp error: anonymous login failed Control socket read failed: Success failed to synchronize hapy error: anonymous login failed Control socket read failed: Success failed to synchronize kritoke error: anonymous login failed Control socket read failed: Success failed to synchronize roberto error: anonymous login failed Control socket read failed: Success failed to synchronize staging error: anonymous login failed Control socket read failed: Success failed to synchronize twm error: anonymous login failed Control socket read failed: Success failed to synchronize whatah error: anonymous login failed Control socket read failed: Success failed to synchronize xentac error: anonymous login failed Control socket read failed: Success failed to synchronize brice error: anonymous login failed Control socket read failed: Success failed to synchronize tpowa :: j2re-1.5.0_beta1-1: local version is newer :: j2sdk-1.5.0_beta1-2: local version is newer :: mplayer-1.0pre3.2-1: ignoring package upgrade (1.0pre4-1) :: prelink-20021002-2: local version is newer :: Above packages will be skipped. To manually upgrade use 'pacman -S <pkg>' Targets: binutils-2.15-1t1 cvsup-16.1h-2t1 glibc-2.3.3-1t1 initscripts-0.6-9 iputils-021109-1t1 rhythmbox-0.8.3-1 sox-12.17.4-3 Proceed with upgrade? [Y/n] y :: Retrieving packages from testing... error: anonymous login failed Control socket read failed: Success error: failed to retrieve some files from testing :: Retrieving packages from current... error: anonymous login failed Control socket read failed: Success initscripts-0.6-9 [################] 100% 7K 3.5K/s 00:00:02 :: Retrieving packages from extra... error: anonymous login failed Control socket read failed: Success rhythmbox-0.8.3-1 [################] 100% 1206K 67.4K/s 00:00:17 sox-12.17.4-3 [################] 100% 238K 56.7K/s 00:00:04 [/code] After downloading those files it does not install them (presumably because it was unable to download some dependencies). I haven't seen any other posts about this so perhaps this problem just arose? |
This task depends upon
Comment by Jan de Groot (JGC) -
Saturday, 22 May 2004, 12:23 GMT
This doesn't look like a bug to me. Pacman is a little bit verbose, but in fact the tur mirror looks unreachable, causing all these errors.