Arch Linux

Marcel-

Member

From: Utrecht, NL

Registered: 2006-12-03

Posts: 266

sysupgrade: No such file or directory

Hi,

When I try to pacman -Syu, I get the following messages and nothing further happens:

:: Synchronizing package databases...
 core                      32.2K  353.5K/s 00:00:00 [#####################################] 100%
 extra                    390.0K  160.8K/s 00:00:02 [#####################################] 100%
 community                362.5K  211.1K/s 00:00:02 [#####################################] 100%
 archlinuxfr               25.3K  184.4K/s 00:00:00 [#####################################] 100%
:: Starting full system upgrade...
resolving dependencies...
ftp://ftp.nluug.nl/pub/metalab/distributions/archlinux/core/os/i686/pciutils-3.1.2-1-i686.pkg.tar.gz
ftp://ftp.nluug.nl/pub/metalab/distributions/archlinux/core/os/i686/binutils-2.19.1-1-i686.pkg.tar.gz
ftp://ftp.nluug.nl/pub/metalab/distributions/archlinux/core/os/i686/device-mapper-1.02.30-1-i686.pkg.tar.gz
.
.
.
ftp://ftp.nluug.nl/pub/metalab/distributions/archlinux/extra/os/i686/xorg-xinit-1.1.1-1-i686.pkg.tar.gz
ftp://ftp.nluug.nl/pub/metalab/distributions/archlinux/extra/os/i686/xterm-241-1-i686.pkg.tar.gz
ftp://ftp.nluug.nl/pub/metalab/distributions/archlinux/community/os/i686/emacs-php-mode-1.5.0-1.pkg.tar.gz
grep: /tmp/yaourt-tmp-mk/sysupgrade: No such file or directory
Checking for package upgrades... 
warning: tetex-3.0-5: ignoring package upgrade (to be replaced by texlive-core-2008.11906-1)
grep: /tmp/yaourt-tmp-mk/sysupgrade: No such file or directory

Problem popped up about a week ago. Anyone?

Mr.Elendig

#archlinux@freenode channel op

From: The intertubes

Registered: 2004-11-07

Posts: 4,092

Re: sysupgrade: No such file or directory

have you aliased pacman to yaourt?

---

Evil #archlinux@libera.chat channel op and general support dude.
. files on github, Screenshots, Random pics and the rest

Marcel-

Member

From: Utrecht, NL

Registered: 2006-12-03

Posts: 266

Re: sysupgrade: No such file or directory

Yes, I did (actually, as 'sudo yaourt'). I just tried doing a yaourt -Syu as root, and it worked. Hope this solves the problem for my usual account, too.