[SOLVED] pacman replies - No such file

i cant install amarok right now.
pacman -S amarok
No such file “amarok-2.4.1-1-x86_64.pkg.tar.xz”.
warning: failed to retrieve some files from extra
error: failed to commit transaction (error invoking external downloader)
Errors occurred, no packages were upgraded.
i have tried various transfer commands as well in the pacman.conf
#XferCommand = /usr/bin/wget --passive-ftp -c -O %o %u
#MY EDIT
#XferCommand = /usr/bin/wget -c --passive-ftp -c %u
#XferCommand = /usr/bin/curl %u > %o
i tried about 15 different mirrors as well. 
what am i doing wrong?
Last edited by wolfdogg (2011-07-05 23:04:17)

thank you for the replies.
falconindy wrote:If you switch mirrors, you need to forcefully update your sync DBs with 'pacman -Syy'. Failing to do this will lead to attempts to download the same missing files.
your right, thanks its working now! i forgot about this, (to re sync pacman -Syy after switching mirrors)
first i received a message that the file doesnt exist, thats understandable if its using the old pacman database before the -Syy resync
Connecting to mirror.rit.edu|129.21.171.98|:21... connected.
Logging in as anonymous ... Logged in!
==> SYST ... done.    ==> PWD ... done.
==> TYPE I ... done.  ==> CWD (1) /archlinux/extra/os/x86_64 ... done.
==> SIZE amarok-2.4.1-1-x86_64.pkg.tar.xz ... done.
==> PASV ... done.    ==> RETR amarok-2.4.1-1-x86_64.pkg.tar.xz ...
No such file “amarok-2.4.1-1-x86_64.pkg.tar.xz”.
why is it if i switch mirrors, even though i can see the machine its connecting to is the new mirror, the file isnt found, it must be because the old database list from the old mirror tells it that it doesnt exist, so it doesnt even bother looking right? 
but for some reason the next time i tried i got a 404 error, which is confusing to me because when you see a 404, that means that the server responded that the file doesnt exist.  i think this is the one i was going off off to make my assumption.  i didnt notice the first one until i detailed this out.  i only noticed the 404.
Connecting to mirrors.kernel.org|149.20.20.135|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2011-07-02 13:20:52 ERROR 404: Not Found.
Last edited by wolfdogg (2011-07-02 20:51:23)

Similar Messages

  • Pacman Error: No such file or directory, please help

    This morning I decided to make a package using the ABS and I noticed this error when executing Pacman.
    error: /var/lib/pacman/local/pacman-2.9.8-1/desc: No such file or directory
    Consequently, the custom package (Gaim Beta 4) kept complaining about dependancies, when I knew those packages were installed in the system. I did some searching around and it appeared that my local database may be currupted? At any rate, one of the posters suggested to forcefully reinstall the offending package, which I did. Upon doing so, it appeared that I had found a solution. However, after installing another package, the error appeared again. Repeating the process resolves the error, but only once before it occurs again.
    Upon further searching, another poster suggested that I should remove the offending directory, and then reinstall the package. When I attempt to remove the directory, I get a kernel panic and my entire system freezes. Since there is so much output, I've take a photo of the error (X just freezes).
    I apologise for the dodgy flash, but you can see the output. If anyone could offer any suggestions/assistance, I'd appreciate it.
    Cheers,
    Tate
    EDIT: If it helps, I'm using the latest 2.6.18 stock Arch Kernel and LVM2 with ReiserFS.

    try this:
    cd /var/lib/pacman/local
    mv pacman-2.9.8-1 pacman-2.9.8-1.old
    pacman -Sf pacman
    verify /var/lib/pacman/local/pacman-2.9.8-1 folder exists
    verify that following files are in folder:  depends, desc, files, install
    verify pacman -Syu works
    rm -rf /var/lib/pacman/local/pacman-2.9.8-1.old

  • [SOLVED] Pacman - could not open file

    After being forced to downgrade my firmware in this thread I get the following error in pacman...
    :: Starting full system upgrade...
    resolving dependencies...
    [b]error: could not open file /var/lib/pacman/local/linux-firmware-20120227-2/desc: No such file or directory[/b]
    looking for inter-conflicts...
    Any idea how I stop this?
    Last edited by Swarfega (2012-05-17 09:03:10)

    Yeah thanks.  Just done that and get the following
    [root@xv5-ln01 andrewp]# pacman -S linux-firmware
    warning: linux-firmware-20120227-2 is up to date -- reinstalling
    resolving dependencies...
    looking for inter-conflicts...
    error: could not open file /var/lib/pacman/local/linux-firmware-20120227-2/desc: No such file or directory
    Targets (1): linux-firmware-20120227-2
    Total Installed Size: 38.73 MiB
    Proceed with installation? [Y/n] y
    (1/1) checking package integrity [###########################################################################] 100%
    (1/1) loading package files [###########################################################################] 100%
    (1/1) checking for file conflicts [###########################################################################] 100%
    error: failed to commit transaction (conflicting files)
    linux-firmware: /usr/lib/firmware/GPL-3 exists in filesystem
    linux-firmware: /usr/lib/firmware/TDA7706_OM_v2.5.1_boot.txt exists in filesystem
    linux-firmware: /usr/lib/firmware/TDA7706_OM_v3.0.2_boot.txt exists in filesystem
    linux-firmware: /usr/lib/firmware/agere_ap_fw.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/agere_sta_fw.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/ar7010.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/ar7010_1_1.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/ar9170-1.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/ar9170-2.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/ar9271.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/ath3k-1.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/atmsar11.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/bnx2x-e1-4.8.53.0.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/bnx2x-e1-5.2.13.0.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/bnx2x-e1-5.2.7.0.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/bnx2x-e1h-4.8.53.0.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/bnx2x-e1h-5.2.13.0.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/bnx2x-e1h-5.2.7.0.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/dvb-fe-xc5000-1.6.114.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/dvb-usb-dib0700-1.20.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/dvb-usb-terratec-h5-drxk.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/emi62/bitstream.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/emi62/loader.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/emi62/midi.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/ene-ub6250/ms_init.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/ene-ub6250/ms_rdwr.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/ene-ub6250/msp_rdwr.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/ene-ub6250/sd_init1.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/ene-ub6250/sd_init2.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/ene-ub6250/sd_rdwr.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/ess/maestro3_assp_kernel.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/ess/maestro3_assp_minisrc.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/f2255usb.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/htc_7010.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/htc_9271.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/i2400m-fw-usb-1.4.sbcf exists in filesystem
    linux-firmware: /usr/lib/firmware/i2400m-fw-usb-1.5.sbcf exists in filesystem
    linux-firmware: /usr/lib/firmware/i6050-fw-usb-1.5.sbcf exists in filesystem
    linux-firmware: /usr/lib/firmware/intelliport2.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/isci/Makefile exists in filesystem
    linux-firmware: /usr/lib/firmware/isci/README exists in filesystem
    linux-firmware: /usr/lib/firmware/isci/create_fw.c exists in filesystem
    linux-firmware: /usr/lib/firmware/isci/create_fw.h exists in filesystem
    linux-firmware: /usr/lib/firmware/isci/isci_firmware.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/isci/probe_roms.h exists in filesystem
    linux-firmware: /usr/lib/firmware/iwlwifi-100-5.ucode exists in filesystem
    linux-firmware: /usr/lib/firmware/iwlwifi-1000-3.ucode exists in filesystem
    linux-firmware: /usr/lib/firmware/iwlwifi-1000-5.ucode exists in filesystem
    linux-firmware: /usr/lib/firmware/iwlwifi-105-6.ucode exists in filesystem
    linux-firmware: /usr/lib/firmware/iwlwifi-135-6.ucode exists in filesystem
    linux-firmware: /usr/lib/firmware/iwlwifi-2000-6.ucode exists in filesystem
    linux-firmware: /usr/lib/firmware/iwlwifi-2030-6.ucode exists in filesystem
    linux-firmware: /usr/lib/firmware/iwlwifi-3945-2.ucode exists in filesystem
    linux-firmware: /usr/lib/firmware/iwlwifi-4965-2.ucode exists in filesystem
    linux-firmware: /usr/lib/firmware/iwlwifi-5000-1.ucode exists in filesystem
    linux-firmware: /usr/lib/firmware/iwlwifi-5000-2.ucode exists in filesystem
    linux-firmware: /usr/lib/firmware/iwlwifi-5000-5.ucode exists in filesystem
    linux-firmware: /usr/lib/firmware/iwlwifi-5150-2.ucode exists in filesystem
    linux-firmware: /usr/lib/firmware/iwlwifi-6000-4.ucode exists in filesystem
    linux-firmware: /usr/lib/firmware/iwlwifi-6000g2a-5.ucode exists in filesystem
    linux-firmware: /usr/lib/firmware/iwlwifi-6000g2b-5.ucode exists in filesystem
    linux-firmware: /usr/lib/firmware/iwlwifi-6000g2b-6.ucode exists in filesystem
    linux-firmware: /usr/lib/firmware/iwlwifi-6050-4.ucode exists in filesystem
    linux-firmware: /usr/lib/firmware/iwlwifi-6050-5.ucode exists in filesystem
    linux-firmware: /usr/lib/firmware/kaweth/new_code.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/kaweth/new_code_fix.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/kaweth/trigger_code.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/kaweth/trigger_code_fix.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/keyspan/mpr.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/keyspan/usa18x.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/keyspan/usa19.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/keyspan/usa19qi.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/keyspan/usa19qw.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/keyspan/usa19w.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/keyspan/usa28.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/keyspan/usa28x.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/keyspan/usa28xa.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/keyspan/usa28xb.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/keyspan/usa49w.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/keyspan/usa49wlc.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/keyspan_pda/Makefile exists in filesystem
    linux-firmware: /usr/lib/firmware/keyspan_pda/keyspan_pda.S exists in filesystem
    linux-firmware: /usr/lib/firmware/keyspan_pda/keyspan_pda.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/keyspan_pda/xircom_pgs.S exists in filesystem
    linux-firmware: /usr/lib/firmware/keyspan_pda/xircom_pgs.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/korg/k1212.dsp exists in filesystem
    linux-firmware: /usr/lib/firmware/lbtf_usb.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/lgs8g75.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/libertas/cf8381.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/libertas/cf8381_helper.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/libertas/cf8385.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/libertas/cf8385_helper.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/libertas/gspi8682.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/libertas/gspi8682_helper.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/libertas/gspi8686_v9.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/libertas/gspi8686_v9_helper.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/libertas/gspi8688.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/libertas/gspi8688_helper.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/libertas/lbtf_sdio.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/libertas/sd8385.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/libertas/sd8385_helper.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/libertas/sd8682.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/libertas/sd8682_helper.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/libertas/sd8686_v8.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/libertas/sd8686_v8_helper.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/libertas/sd8686_v9.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/libertas/sd8686_v9_helper.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/libertas/sd8688.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/libertas/sd8688_helper.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/libertas/usb8388_olpc.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/libertas/usb8388_v5.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/libertas/usb8388_v9.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/libertas/usb8682.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/matrox/g200_warp.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/matrox/g400_warp.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/mrvl/sd8787_uapsta.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/mts_cdma.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/mts_edge.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/mts_gsm.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/mts_mt9234mu.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/mts_mt9234zba.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/mwl8335_duplex.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/mwl8k/fmimage_8366.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/mwl8k/fmimage_8366_ap-1.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/mwl8k/fmimage_8366_ap-2.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/mwl8k/fmimage_8687.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/mwl8k/helper_8366.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/mwl8k/helper_8687.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/myri10ge_eth_z8e.dat exists in filesystem
    linux-firmware: /usr/lib/firmware/myri10ge_ethp_z8e.dat exists in filesystem
    linux-firmware: /usr/lib/firmware/myri10ge_rss_eth_z8e.dat exists in filesystem
    linux-firmware: /usr/lib/firmware/myri10ge_rss_ethp_z8e.dat exists in filesystem
    linux-firmware: /usr/lib/firmware/myricom/lanai.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/ositech/Xilinx7OD.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/phanfw.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/ql2100_fw.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/ql2200_fw.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/ql2300_fw.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/ql2322_fw.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/ql2400_fw.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/ql2500_fw.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/qlogic/1040.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/qlogic/12160.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/qlogic/1280.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/qlogic/isp1000.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/qlogic/sd7220.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/r128/r128_cce.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/radeon/BARTS_mc.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/radeon/BARTS_me.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/radeon/BARTS_pfp.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/radeon/BTC_rlc.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/radeon/CAICOS_mc.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/radeon/CAICOS_me.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/radeon/CAICOS_pfp.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/radeon/CAYMAN_mc.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/radeon/CAYMAN_me.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/radeon/CAYMAN_pfp.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/radeon/CAYMAN_rlc.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/radeon/CEDAR_me.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/radeon/CEDAR_pfp.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/radeon/CEDAR_rlc.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/radeon/CYPRESS_me.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/radeon/CYPRESS_pfp.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/radeon/CYPRESS_rlc.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/radeon/JUNIPER_me.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/radeon/JUNIPER_pfp.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/radeon/JUNIPER_rlc.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/radeon/PALM_me.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/radeon/PALM_pfp.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/radeon/R100_cp.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/radeon/R200_cp.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/radeon/R300_cp.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/radeon/R420_cp.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/radeon/R520_cp.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/radeon/R600_me.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/radeon/R600_pfp.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/radeon/R600_rlc.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/radeon/R700_rlc.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/radeon/REDWOOD_me.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/radeon/REDWOOD_pfp.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/radeon/REDWOOD_rlc.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/radeon/RS600_cp.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/radeon/RS690_cp.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/radeon/RS780_me.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/radeon/RS780_pfp.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/radeon/RV610_me.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/radeon/RV610_pfp.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/radeon/RV620_me.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/radeon/RV620_pfp.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/radeon/RV630_me.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/radeon/RV630_pfp.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/radeon/RV635_me.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/radeon/RV635_pfp.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/radeon/RV670_me.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/radeon/RV670_pfp.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/radeon/RV710_me.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/radeon/RV710_pfp.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/radeon/RV730_me.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/radeon/RV730_pfp.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/radeon/RV770_me.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/radeon/RV770_pfp.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/radeon/SUMO2_me.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/radeon/SUMO2_pfp.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/radeon/SUMO_me.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/radeon/SUMO_pfp.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/radeon/SUMO_rlc.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/radeon/TURKS_mc.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/radeon/TURKS_me.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/radeon/TURKS_pfp.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/rt2561.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/rt2561s.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/rt2661.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/rt2860.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/rt2870.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/rt3070.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/rt3071.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/rt3090.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/rt73.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/rtl_nic/rtl8105e-1.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/rtl_nic/rtl8168d-1.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/rtl_nic/rtl8168d-2.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/rtl_nic/rtl8168e-1.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/rtl_nic/rtl8168e-2.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/rtl_nic/rtl8168e-3.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/rtl_nic/rtl8168f-1.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/rtl_nic/rtl8168f-2.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/rtl_nic/rtl8402-1.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/rtl_nic/rtl8411-1.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/rtlwifi/rtl8192cfw.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/rtlwifi/rtl8192cufw.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/rtlwifi/rtl8192defw.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/rtlwifi/rtl8192sefw.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/rtlwifi/rtl8712u.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/s2250.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/s2250_loader.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/sb16/alaw_main.csp exists in filesystem
    linux-firmware: /usr/lib/firmware/sb16/ima_adpcm_capture.csp exists in filesystem
    linux-firmware: /usr/lib/firmware/sb16/ima_adpcm_init.csp exists in filesystem
    linux-firmware: /usr/lib/firmware/sb16/ima_adpcm_playback.csp exists in filesystem
    linux-firmware: /usr/lib/firmware/sb16/mulaw_main.csp exists in filesystem
    linux-firmware: /usr/lib/firmware/slicoss/gbdownload.sys exists in filesystem
    linux-firmware: /usr/lib/firmware/slicoss/gbrcvucode.sys exists in filesystem
    linux-firmware: /usr/lib/firmware/slicoss/oasisdbgdownload.sys exists in filesystem
    linux-firmware: /usr/lib/firmware/slicoss/oasisdownload.sys exists in filesystem
    linux-firmware: /usr/lib/firmware/slicoss/oasisrcvucode.sys exists in filesystem
    linux-firmware: /usr/lib/firmware/sun/cassini.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/sxg/saharadbgdownloadB.sys exists in filesystem
    linux-firmware: /usr/lib/firmware/sxg/saharadownloadB.sys exists in filesystem
    linux-firmware: /usr/lib/firmware/tehuti/bdx.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/ti-connectivity/TIInit_7.2.31.bts exists in filesystem
    linux-firmware: /usr/lib/firmware/ti-connectivity/wl1271-fw-2.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/ti-connectivity/wl1271-fw-ap.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/ti-connectivity/wl1271-fw.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/ti-connectivity/wl1271-nvs.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/ti-connectivity/wl127x-fw-3.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/ti-connectivity/wl127x-fw-plt-3.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/ti-connectivity/wl127x-nvs.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/ti-connectivity/wl128x-fw-3.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/ti-connectivity/wl128x-fw-ap.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/ti-connectivity/wl128x-fw-plt-3.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/ti-connectivity/wl128x-fw.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/ti-connectivity/wl128x-nvs.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/ti-connectivity/wl12xx-nvs.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/ti_3410.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/ti_5052.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/tigon/tg3.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/tigon/tg3_tso.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/tigon/tg3_tso5.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/tlg2300_firmware.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/tr_smctr.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/ttusb-budget/dspbootcode.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/ueagle-atm/930-fpga.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/ueagle-atm/CMV4p.bin.v2 exists in filesystem
    linux-firmware: /usr/lib/firmware/ueagle-atm/CMV9i.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/ueagle-atm/CMV9p.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/ueagle-atm/CMVei.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/ueagle-atm/CMVeiWO.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/ueagle-atm/CMVep.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/ueagle-atm/CMVepES.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/ueagle-atm/CMVepES03.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/ueagle-atm/CMVepFR.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/ueagle-atm/CMVepFR04.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/ueagle-atm/CMVepFR10.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/ueagle-atm/CMVepIT.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/ueagle-atm/CMVepWO.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/ueagle-atm/DSP4p.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/ueagle-atm/DSP9i.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/ueagle-atm/DSP9p.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/ueagle-atm/DSPei.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/ueagle-atm/DSPep.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/ueagle-atm/adi930.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/ueagle-atm/eagleI.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/ueagle-atm/eagleII.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/ueagle-atm/eagleIII.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/ueagle-atm/eagleIV.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/usbdux/Makefile_dux exists in filesystem
    linux-firmware: /usr/lib/firmware/usbdux/README.dux exists in filesystem
    linux-firmware: /usr/lib/firmware/usbdux/fx2-include.asm exists in filesystem
    linux-firmware: /usr/lib/firmware/usbdux/usbdux_firmware.asm exists in filesystem
    linux-firmware: /usr/lib/firmware/usbdux/usbduxfast_firmware.asm exists in filesystem
    linux-firmware: /usr/lib/firmware/usbdux/usbduxsigma_firmware.asm exists in filesystem
    linux-firmware: /usr/lib/firmware/usbdux_firmware.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/usbduxfast_firmware.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/usbduxsigma_firmware.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/v4l-cx231xx-avcore-01.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/v4l-cx23418-apu.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/v4l-cx23418-cpu.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/v4l-cx23418-dig.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/v4l-cx23885-avcore-01.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/v4l-cx23885-enc.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/v4l-cx25840.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/vicam/firmware.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/vntwusb.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/vxge/X3fw-pxe.ncf exists in filesystem
    linux-firmware: /usr/lib/firmware/vxge/X3fw.ncf exists in filesystem
    linux-firmware: /usr/lib/firmware/whiteheat.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/whiteheat_loader.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/yam/1200.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/yam/9600.bin exists in filesystem
    linux-firmware: /usr/lib/firmware/yamaha/ds1_ctrl.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/yamaha/ds1_dsp.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/yamaha/ds1e_ctrl.fw exists in filesystem
    linux-firmware: /usr/lib/firmware/yamaha/yss225_registers.bin exists in filesystem
    linux-firmware: /usr/share/licenses/linux-firmware/LICENCE.Marvell exists in filesystem
    linux-firmware: /usr/share/licenses/linux-firmware/LICENCE.OLPC exists in filesystem
    linux-firmware: /usr/share/licenses/linux-firmware/LICENCE.agere exists in filesystem
    linux-firmware: /usr/share/licenses/linux-firmware/LICENCE.atheros_firmware exists in filesystem
    linux-firmware: /usr/share/licenses/linux-firmware/LICENCE.broadcom_bcm43xx exists in filesystem
    linux-firmware: /usr/share/licenses/linux-firmware/LICENCE.chelsio_firmware exists in filesystem
    linux-firmware: /usr/share/licenses/linux-firmware/LICENCE.ene_firmware exists in filesystem
    linux-firmware: /usr/share/licenses/linux-firmware/LICENCE.i2400m exists in filesystem
    linux-firmware: /usr/share/licenses/linux-firmware/LICENCE.iwlwifi_firmware exists in filesystem
    linux-firmware: /usr/share/licenses/linux-firmware/LICENCE.mwl8335 exists in filesystem
    linux-firmware: /usr/share/licenses/linux-firmware/LICENCE.myri10ge_firmware exists in filesystem
    linux-firmware: /usr/share/licenses/linux-firmware/LICENCE.phanfw exists in filesystem
    linux-firmware: /usr/share/licenses/linux-firmware/LICENCE.qla2xxx exists in filesystem
    linux-firmware: /usr/share/licenses/linux-firmware/LICENCE.ralink-firmware.txt exists in filesystem
    linux-firmware: /usr/share/licenses/linux-firmware/LICENCE.rtlwifi_firmware.txt exists in filesystem
    linux-firmware: /usr/share/licenses/linux-firmware/LICENCE.tda7706-firmware.txt exists in filesystem
    linux-firmware: /usr/share/licenses/linux-firmware/LICENCE.ti-connectivity exists in filesystem
    linux-firmware: /usr/share/licenses/linux-firmware/LICENCE.ueagle-atm4-firmware exists in filesystem
    linux-firmware: /usr/share/licenses/linux-firmware/LICENCE.via_vt6656 exists in filesystem
    linux-firmware: /usr/share/licenses/linux-firmware/LICENCE.xc5000 exists in filesystem
    linux-firmware: /usr/share/licenses/linux-firmware/LICENSE.dib0700 exists in filesystem
    linux-firmware: /usr/share/licenses/linux-firmware/LICENSE.radeon_rlc exists in filesystem
    linux-firmware: /usr/share/licenses/linux-firmware/WHENCE exists in filesystem
    Errors occurred, no packages were upgraded.
    Last edited by Swarfega (2012-05-17 08:59:31)

  • [SOLVED] Pacman error: failed retrieving file : No address record

    I just installed Arch on a x86 laptop using the cd as the package source. I wanted to do a net install, but when I attempted to (regardless of the mirror) I got many responses from pacman in tty7 of "No address record". This happened despite having a network connection and being able to ping any site from the cli.
    After installing, I am still having the same problem. The laptop is plugged in via ethernet, and I can ping any site I want, but a call to pacman -Syyu just returns numerous errors such as
    error: failed retrieving file 'core.db' from mirror.rit.edu : No address record
    And just as a test, I was getting replies when pinging mirror.rit.edu.
    Last edited by process91 (2011-11-18 18:21:17)

    Try the following steps:
    1 - Set the VirtualBox Networking option to NAT
    2 -  Start the arch machine in the VirtualBox
    3 -  Edit /etc/rc.conf as a dynamic IP:
    HOSTNAME="arch"
    interface=eth0
    address=
    netmask=
    broadcast=
    gateway=
    4 - Run dhcpcd
    5 -  Try to ping a couple of sites, or your router
    If you still can't ping or anything, I suggest you start a new thread specifically about your problem. Include the output from "ipconfig -a". You're not going to get much help from posting in a thread marked "[SOLVED]".
    Last edited by process91 (2012-01-18 07:21:14)

  • "No such file or directory" when pacman -S.[solved

    161245/home/riwa/hacking/python/projects# pacman_all -S gftp
    error: /var/lib/pacman/local/libxfce4util-4.2.3.2-3/desc: No such file or directory
    error: /var/lib/pacman/local/libxfce4util-4.2.3.2-3/desc: No such file or directory
    error: /var/lib/pacman/local/libxfce4util-4.2.3.2-3/desc: No such file or directory
    Targets: gftp-2.0.18-1
    Total Package Size: 0.9 MB
    Proceed with upgrade? [Y/n] Y
    I get (at least I think so) the file after a while but don't seem to be able to update anymore. For maybie three days I've done -Syu once a day without a single download except bitmaps-stream-vera (or similiar). It also consumes a lot of time. I've read through my pacman.conf but can't find anything referring to the path above. What can cause this?

    There's a problem with your local db. Remove the broken entry:
    # rm -r /var/lib/pacman/local/libxfce4util-4.2.3.2-3
    and reinstall libxfce4util.

  • [SOLVED] Error : sys\stat.h: No such file or directory

    I get "...sys\stat.h: No such file or directory" error when compiling a simple C program. i have been searching for a while on web and see people writing "# pacman -S base-devel" i have that already and some more packages like glib ...
    These are the includes i am using :
    #include <stdio.h>
    #include <stdlib.h>
    #include <io.h>
    #include <fcntl.h>
    #include <sys\stat.h>
    // here is when i use the libraries sys/stats.h
    struct stat stbuf;
    stat(argv[2], &stbuf);
    int infSize = stbuf.size;
    This is the output of the command "gcc -o copy copy.c" :
    copy.c:3:16: error: io.h: No such file or directory
    copy.c:5:22: error: sys\stat.h: No such file or directory
    copy.c: In function 'main':
    copy.c:35: error: storage size of 'stbuf' isn't known
    Either i am missing any package needed or the gcc compiler is missing any lib directory. But i dont know which one is it.
    Any ideas are apreciated. Thanks you
    EDIT : The error was actually on #Include <io.h> , but i dunno why it conflicted with #include <sys\stat.h>.
    Anyway Problem Solved.
    Last edited by puzzled (2008-10-05 17:07:03)

    If you're not sure if you have the SDKs, can you confirm you have the files under /Developer? Check for /Developer/SDKs/MacOSX10.4u.sdk/usr/X11R6/include/X11
    I don't remember having to do anything special to get gcc to find these files.
    From what I've noted, the usual trigger seems to be that the X11SDK.pkg package wasn't installed.
    Typical PATH export is:
    export PATH="/bin:/sbin:/usr/bin:/usr/sbin"
    If you're working with Fink, there's a call to the following needed:
    . /sw/bin/init.sh
    See http://finkproject.org/doc/users-guide/install.php
    But I'd first make sure the X11 SDK was installed. I'd guess that is missing.

  • [SOLVED]Pacman systemd missing file

    Everytime when I run pacman I get this error:
    error: could not open file /var/lib/pacman/local/systemd-217-8/desc: No such file or directory
    I think i messed up something when upgrading system.
    Can you help me to solve this issue?
    Thanks
    Last edited by Arch3R (2014-11-29 19:14:08)

    Just reinstall systemd:
    pacman -S systemd
    select yes if it prompts due to it already being installed.
    You might also want to run `pacman -Qk` to see if any other packages have been damaged.
    EDIT: I just did some silly trial and error and deleted that file from my system (probably would have been smarter to move/rename it).  Reinstalling systemd failed due to a conflicting file error as all the files for the package are there, but the pacman database doesn't realize they belong to that package.  In this case I used --force with the single specific package:
    pacman -S --force systemd
    Note that this use of --force is an apparent necessity to fix this specific problem.  This does not support using it when uncertain why something fails - I knew why it was failing.
    Last edited by Trilby (2014-11-29 19:01:55)

  • [SOLVED] Pacman "config file could not be read" error during Arch ins

    I've been attempting to get Arch setup for a while now, and after having some trouble with partitions, my wireless connecting, and setting up repos and mirrors, which the Wiki helped me solve, I've hit a bigger bump.  While updating the system using pacman as the Beginners Guide says to do, I get errors when I try to continue the update process as follows :
    btw: I'm typing this on a laptop next to my computer
    [root@McArch~]# pacman -Syu
    error: config file /etc/pacman.d/core could not be read
    error: config file /etc/pacman.d/extra could not be read
    error: config file /etc/pacman.d/community could not be read
    :: Synchronizing package databases . . .
    error: failed to updated core (unexpected error)
    error: failed to updated extra (unexpected error)
    error: failed to updated community (unexpected error)
    error: failed to synchronize any databases
    Any tips as to whats going on?  I've tried to created said files, and even insert mirrors into the file, like in the /etc/pacman.d/mirrorlist file but this doesn't seem to help
    Last edited by Windfinder (2008-09-29 20:43:29)

    Glad you got it working.
    I'm not sure what happened in your install but I just finished using an old 2007.08 iso and pacman first starts out with /etc/pacman.d/core, etc/pacman.d/extra, /etc/pacman.d/community ... etc., but I never had your problem when I did the #pacman -Syu after initial install reboot.  The pacman update removes the above mentioned repos and replaces them with a single /etc/pacman.d/mirrorlist.  You must have messed up an initial config file somehow as I couldn't get the same errors you got.  It looks like you had your /etc/pacman.conf file messed up somehow and when you pointed it to the mirrorlist it could finally work properly.  I'll just include my /etc/pacman.conf file and /etc/pacman.d/mirrorlist so you can compare.  NB*  these are from my x86_64 so for 32 bit machines i686 would replace x86_64 in the files.
    # /etc/pacman.conf
    # See the pacman.conf(5) manpage for option and repository directives
    # GENERAL OPTIONS
    [options]
    # The following paths are commented out with their default values listed.
    # If you wish to use different paths, uncomment and update the paths.
    #RootDir = /
    #DBPath = /var/lib/pacman/
    #CacheDir = /var/cache/pacman/pkg/
    #LogFile = /var/log/pacman.log
    HoldPkg = pacman glibc
    # If upgrades are available for these packages they will be asked for first
    SyncFirst = pacman
    #XferCommand = /usr/bin/wget --passive-ftp -c -O %o %u
    #XferCommand = /usr/bin/curl %u > %o
    # Pacman won't upgrade packages listed in IgnorePkg and members of IgnoreGroup
    #IgnorePkg =
    #IgnoreGroup =
    #NoUpgrade =
    #NoExtract =
    # Misc options (all disabled by default)
    #NoPassiveFtp
    #UseSyslog
    #ShowSize
    #UseDelta
    #TotalDownload
    # REPOSITORIES
    # - can be defined here or included from another file
    # - pacman will search repositories in the order defined here
    # - local/custom mirrors can be added here or in separate files
    # - repositories listed first will take precedence when packages
    # have identical names, regardless of version number
    # - URLs will have $repo replaced by the name of the current repo
    # Repository entries are of the format:
    # [repo-name]
    # Server = ServerName
    # Include = IncludePath
    # The header [repo-name] is crucial - it must be present and
    # uncommented to enable the repo.
    # Testing is disabled by default. To enable, uncomment the following
    # two lines. You can add preferred servers immediately after the header,
    # and they will be used before the default mirrors.
    #[testing]
    #Include = /etc/pacman.d/mirrorlist
    [core]
    # Add your preferred servers here, they will be used first
    Include = /etc/pacman.d/mirrorlist
    [extra]
    # Add your preferred servers here, they will be used first
    Include = /etc/pacman.d/mirrorlist
    [community]
    # Add your preferred servers here, they will be used first
    Include = /etc/pacman.d/mirrorlist
    # An example of a custom package repository. See the pacman manpage for
    # tips on creating your own repositories.
    #[custom]
    #Server = file:///home/custompkgs
    /etc/pacman.d/mirrorlist
    # Arch Linux repository mirrorlist
    # North America
    # - United States
    Server = http://mirror.neotuli.net/arch/$repo/os/x86_64
    Server = http://holmes.umflint.edu/archlinux/$repo/os/x86_64
    Server = http://archlinux.unixheads.org/$repo/os/x86_64
    Server = ftp://ftp.archlinux.org/$repo/os/x86_64
    Server = ftp://locke.suu.edu/linux/dist/archlinux/$repo/os/x86_64
    Server = ftp://ftp.gtlib.gatech.edu/pub/linux/distributions/archlinux/$repo/os/x86_64
    Server = ftp://mirror.cs.vt.edu/pub/ArchLinux/$repo/os/x86_64
    Server = http://mirrors.easynews.com/linux/archlinux/$repo/os/x86_64
    Server = ftp://ftp.ibiblio.org/pub/linux/distributions/archlinux/$repo/os/x86_64
    Server = http://mirror.rit.edu/archlinux/$repo/os/x86_64
    Server = http://mirror.umoss.org/archlinux/$repo/os/x86_64
    # - Canada
    Server = ftp://mirror.csclub.uwaterloo.ca/archlinux/$repo/os/@carch
    Well it was an interesting way to kill 30+ minutes.

  • [SOLVED]fail to build package: no such file or directory error

    EDIT1: read my last post
    I'm getting an error while installing pacman-color from the aur repository. I'm still a newbie so my only guess is to make such directory? why should I have to do that? anyone help?
    ==> Validating source files with md5sums...
        pacman-3.4.2.tar.gz ... Passed
        pacman-color-3.4.2-1.patch ... Passed
        color.conf ... Passed
    ==> Extracting Sources...
    ==> Removing existing pkg/ directory...
    ==> Starting build()...
    /tmp/yaourt-tmp-root/aur-pacman-color/./PKGBUILD: line 21: cd: pacman-3.4.2: No such file or directory
        Aborting...
    ==> ERROR: Makepkg was unable to build pacman-color.
    Last edited by aluser (2011-01-21 04:48:16)

    Here once again a failed attempt after removing pacman-color. I am beginning to think that maybe running yaourt as sudo is probably a bad idea. I think that may have had something to do with it.
    archuser@archws ~ % sudo yaourt -S abiword-light <11:54>
    Password:
    ==> Downloading abiword-light PKGBUILD from AUR...
    x PKGBUILD
    Comment by: mango on Thu, 25 Mar 2010 21:53:12 +0000
    ./configure --prefix=/usr \
    --disable-spell \
    --disable-print
    Comment by: chessboxing on Wed, 19 May 2010 14:33:51 +0000
    doesn't want to build
    rule 23: make: command not found
    == ERROR: Build Failed.
    Aborting...
    Eventhough I Had to install flex psiconv, it didn't help.
    Its a minefield man.
    Comment by: sHyLoCk on Wed, 02 Jun 2010 13:54:43 +0000
    http://aur.archlinux.org/packages.php?ID=37738
    Comment by: zenny on Thu, 02 Sep 2010 05:59:05 +0000
    Quite confusing statements. Below sHyLoCk recommends http://aur.archlinux.org/packages.php?ID=37738 on June 2 2010 and on June 27 he declares his recommended package obsolet and ask a TU to delete! The problem with the sHyLoCk package is there is not page setup option. So I installed this package, it has got the page setup menu, but once I click the option, the application dies with the following output (Maybe helpful to debug for the maintainer, I am not an expert):
    (abiword:32455): Gtk-CRITICAL **: gtk_label_set_text: assertion `GTK_IS_LABEL (label)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_label_set_text: assertion `GTK_IS_LABEL (label)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_label_get_label: assertion `GTK_IS_LABEL (label)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_label_set_markup: assertion `GTK_IS_LABEL (label)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_label_set_text: assertion `GTK_IS_LABEL (label)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_label_set_text: assertion `GTK_IS_LABEL (label)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_label_set_text: assertion `GTK_IS_LABEL (label)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_label_set_text: assertion `GTK_IS_LABEL (label)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_label_get_label: assertion `GTK_IS_LABEL (label)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_label_set_markup: assertion `GTK_IS_LABEL (label)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_container_foreach: assertion `GTK_IS_CONTAINER (container)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_label_set_text: assertion `GTK_IS_LABEL (label)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_label_set_text: assertion `GTK_IS_LABEL (label)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_label_set_text: assertion `GTK_IS_LABEL (label)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_label_get_label: assertion `GTK_IS_LABEL (label)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_label_set_markup: assertion `GTK_IS_LABEL (label)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_label_set_text: assertion `GTK_IS_LABEL (label)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_label_set_text: assertion `GTK_IS_LABEL (label)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_label_set_text: assertion `GTK_IS_LABEL (label)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_label_set_text: assertion `GTK_IS_LABEL (label)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_label_get_label: assertion `GTK_IS_LABEL (label)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_label_set_markup: assertion `GTK_IS_LABEL (label)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_container_foreach: assertion `GTK_IS_CONTAINER (container)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_label_set_text: assertion `GTK_IS_LABEL (label)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_container_foreach: assertion `GTK_IS_CONTAINER (container)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_label_set_text: assertion `GTK_IS_LABEL (label)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_label_get_label: assertion `GTK_IS_LABEL (label)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_label_set_markup: assertion `GTK_IS_LABEL (label)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_label_set_text: assertion `GTK_IS_LABEL (label)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_label_set_text: assertion `GTK_IS_LABEL (label)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_label_set_text: assertion `GTK_IS_LABEL (label)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_label_set_text: assertion `GTK_IS_LABEL (label)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_label_set_text: assertion `GTK_IS_LABEL (label)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_label_set_text: assertion `GTK_IS_LABEL (label)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_label_set_text: assertion `GTK_IS_LABEL (label)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_label_set_text: assertion `GTK_IS_LABEL (label)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_label_set_text: assertion `GTK_IS_LABEL (label)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_spin_button_set_value: assertion `GTK_IS_SPIN_BUTTON (spin_button)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_spin_button_set_value: assertion `GTK_IS_SPIN_BUTTON (spin_button)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_spin_button_set_value: assertion `GTK_IS_SPIN_BUTTON (spin_button)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_spin_button_set_value: assertion `GTK_IS_SPIN_BUTTON (spin_button)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_spin_button_set_value: assertion `GTK_IS_SPIN_BUTTON (spin_button)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_spin_button_set_value: assertion `GTK_IS_SPIN_BUTTON (spin_button)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_spin_button_set_value: assertion `GTK_IS_SPIN_BUTTON (spin_button)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_spin_button_set_value: assertion `GTK_IS_SPIN_BUTTON (spin_button)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_spin_button_set_value: assertion `GTK_IS_SPIN_BUTTON (spin_button)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_combo_box_set_model: assertion `GTK_IS_COMBO_BOX (combo_box)' failed
    (abiword:32455): GLib-GObject-WARNING **: invalid (NULL) pointer instance
    (abiword:32455): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_combo_box_set_model: assertion `GTK_IS_COMBO_BOX (combo_box)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_cell_layout_clear: assertion `GTK_IS_CELL_LAYOUT (cell_layout)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_cell_layout_pack_start: assertion `GTK_IS_CELL_LAYOUT (cell_layout)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_cell_layout_set_attributes: assertion `GTK_IS_CELL_LAYOUT (cell_layout)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_combo_box_get_model: assertion `GTK_IS_COMBO_BOX (combo_box)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_list_store_append: assertion `GTK_IS_LIST_STORE (list_store)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_list_store_set_valist: assertion `GTK_IS_LIST_STORE (list_store)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_combo_box_get_model: assertion `GTK_IS_COMBO_BOX (combo_box)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_list_store_append: assertion `GTK_IS_LIST_STORE (list_store)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_list_store_set_valist: assertion `GTK_IS_LIST_STORE (list_store)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_combo_box_get_model: assertion `GTK_IS_COMBO_BOX (combo_box)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_list_store_append: assertion `GTK_IS_LIST_STORE (list_store)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_list_store_set_valist: assertion `GTK_IS_LIST_STORE (list_store)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_combo_box_get_model: assertion `GTK_IS_COMBO_BOX (combo_box)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_tree_model_get_iter_first: assertion `GTK_IS_TREE_MODEL (tree_model)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_combo_box_set_model: assertion `GTK_IS_COMBO_BOX (combo_box)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_cell_layout_clear: assertion `GTK_IS_CELL_LAYOUT (cell_layout)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_cell_layout_pack_start: assertion `GTK_IS_CELL_LAYOUT (cell_layout)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_cell_layout_set_attributes: assertion `GTK_IS_CELL_LAYOUT (cell_layout)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_combo_box_get_model: assertion `GTK_IS_COMBO_BOX (combo_box)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_list_store_append: assertion `GTK_IS_LIST_STORE (list_store)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_list_store_set_valist: assertion `GTK_IS_LIST_STORE (list_store)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_combo_box_get_model: assertion `GTK_IS_COMBO_BOX (combo_box)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_list_store_append: assertion `GTK_IS_LIST_STORE (list_store)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_list_store_set_valist: assertion `GTK_IS_LIST_STORE (list_store)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_combo_box_get_model: assertion `GTK_IS_COMBO_BOX (combo_box)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_list_store_append: assertion `GTK_IS_LIST_STORE (list_store)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_list_store_set_valist: assertion `GTK_IS_LIST_STORE (list_store)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_combo_box_get_model: assertion `GTK_IS_COMBO_BOX (combo_box)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_tree_model_get_iter_first: assertion `GTK_IS_TREE_MODEL (tree_model)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_widget_get_colormap: assertion `GTK_IS_WIDGET (widget)' failed
    (abiword:32455): Gdk-CRITICAL **: gdk_pixmap_colormap_create_from_xpm_d: assertion `drawable != NULL || colormap != NULL' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_image_set_from_pixmap: assertion `mask == NULL || GDK_IS_PIXMAP (mask)' failed
    (abiword:32455): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
    (abiword:32455): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_box_pack: assertion `GTK_IS_BOX (box)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_toggle_button_set_active: assertion `GTK_IS_TOGGLE_BUTTON (toggle_button)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_widget_get_colormap: assertion `GTK_IS_WIDGET (widget)' failed
    (abiword:32455): Gdk-CRITICAL **: gdk_pixmap_colormap_create_from_xpm_d: assertion `drawable != NULL || colormap != NULL' failed
    Aborted
    First Submitted: Wed, 15 Apr 2009 17:01:46 +0000
    abiword-light 2.8.6-2 : A fully-featured word processor without some gnome dependencies
    ( Unsupported package: Potentially dangerous ! )
    ==> Edit PKGBUILD ? [Y/n] ("A" to abort)
    ==> ------------------------------------
    ==> n
    ==> abiword-light dependencies:
    - fribidi>=0.10.9 (already installed)
    - wv>=1.2.4 (already installed)
    - libglade>=2.0 (already installed)
    - pkgconfig (already installed)
    ==> Continue building abiword-light ? [Y/n]
    ==> ---------------------------------------
    ==>
    ==> Building and installing package
    ==> WARNING: Building package as root is dangerous.
    Please run yaourt as a non-privileged user.
    ==> Making package: abiword-light 2.8.6-2 (Fri Jan 21 11:54:35 JST 2011)
    ==> Checking Runtime Dependencies...
    ==> Checking Buildtime Dependencies...
    ==> Retrieving Sources...
    -> Downloading abiword-2.8.6.tar.gz...
    --2011-01-21 11:54:35-- http://www.abisource.com/downloads/abiword/2.8.6/source/abiword-2.8.6.tar.gz
    Resolving www.abisource.com... 130.89.149.216
    Connecting to www.abisource.com|130.89.149.216|:80... connected.
    HTTP request sent, awaiting response... 200 OK
    Length: 9218827 (8.8M) [application/x-gzip]
    Saving to: "abiword-2.8.6.tar.gz.part"
    100%[=======================================>] 9,218,827 414K/s in 28s
    2011-01-21 11:55:04 (325 KB/s) - "abiword-2.8.6.tar.gz.part" saved [9218827/9218827]
    ==> Validating source files with md5sums...
    abiword-2.8.6.tar.gz ... Passed
    ==> Extracting Sources...
    ==> Starting build()...
    /tmp/yaourt-tmp-root/aur-abiword-light/./PKGBUILD: line 16: cd: /tmp/yaourt-tmp-root/aur-abiword-light/src/abiword-2.8.6/: No such file or directory
    Aborting...
    ==> ERROR: Makepkg was unable to build abiword-light.
    ==> Restart building abiword-light ? [y/N]
    ==> --------------------------------------
    ==> archuser@archws ~ % <11:find /usr/{bin,lib} -type f -size 0
    /usr/lib/python3.1/tkinter/test/__init__.py
    /usr/lib/python3.1/tkinter/test/test_ttk/__init__.py
    /usr/lib/python3.1/tkinter/test/test_tkinter/__init__.py
    /usr/lib/python3.1/test/nullcert.pem
    /usr/lib/python3.1/site-packages/ranger/gui/__init__.py
    /usr/lib/python3.1/email/mime/__init__.py
    /usr/lib/python3.1/email/test/__init__.py
    /usr/lib/python3.1/urllib/__init__.py
    /usr/lib/python3.1/sqlite3/test/__init__.py
    /usr/lib/python3.1/pydoc_data/__init__.py
    /usr/lib/python3.1/lib2to3/tests/data/fixers/myfixes/__init__.py
    /usr/lib/python2.7/test/nullcert.pem
    /usr/lib/python2.7/site-packages/git_remote_helpers/git/__init__.py
    /usr/lib/python2.7/site-packages/OpenGL/GL/MESAX/__init__.py
    /usr/lib/python2.7/site-packages/OpenGL/GL/VERSION/__init__.py
    /usr/lib/python2.7/site-packages/OpenGL/GLU/EXT/__init__.py
    /usr/lib/python2.7/site-packages/OpenGL/AGL/__init__.py
    /usr/lib/python2.7/site-packages/pychess/__init__.py
    /usr/lib/python2.7/site-packages/pychess/widgets/__init__.py
    /usr/lib/python2.7/site-packages/pychess/Utils/__init__.py
    /usr/lib/python2.7/site-packages/pychess/Utils/lutils/__init__.py
    /usr/lib/python2.7/site-packages/pychess/ic/__init__.py
    /usr/lib/python2.7/site-packages/pychess/ic/managers/__init__.py
    /usr/lib/python2.7/site-packages/pychess/System/__init__.py
    /usr/lib/python2.7/site-packages/pychess/Players/__init__.py
    /usr/lib/python2.7/site-packages/pychess/gfx/__init__.py
    /usr/lib/python2.7/site-packages/xml2po/modes/__init__.py
    /usr/lib/python2.7/site-packages/numpy/distutils/tests/gen_ext/__init__.py
    /usr/lib/python2.7/site-packages/numpy/distutils/tests/f2py_ext/__init__.py
    /usr/lib/python2.7/site-packages/numpy/distutils/tests/pyrex_ext/__init__.py
    /usr/lib/python2.7/site-packages/numpy/distutils/tests/swig_ext/__init__.py
    /usr/lib/python2.7/site-packages/numpy/distutils/tests/f2py_f90_ext/__init__.py
    /usr/lib/python2.7/site-packages/bzrlib/util/__init__.py
    /usr/lib/python2.7/site-packages/bzrlib/util/configobj/__init__.py
    /usr/lib/python2.7/site-packages/pygame/tests/util/build_page/libs/build_client/__init__.py
    /usr/lib/python2.7/site-packages/pygame/tests/util/build_page/libs/build_client/test_fixtures/BUILD_LINK_FAILED
    /usr/lib/python2.7/site-packages/pygame/tests/util/build_page/libs/build_client/test_fixtures/BUILD_FAILED_EXCEPTION
    /usr/lib/python2.7/site-packages/pygame/tests/util/build_page/libs/build_client/test_fixtures/BUILD_FAILED_UNPARSEABLE
    /usr/lib/python2.7/site-packages/pygame/tests/util/build_page/libs/build_client/test_fixtures/TESTS_FAILED
    /usr/lib/python2.7/site-packages/pygame/tests/util/build_page/libs/build_client/test_fixtures/BUILD_FAILED
    /usr/lib/python2.7/site-packages/pygame/tests/util/build_page/libs/build_client/test_fixtures/TESTS_INVALID
    /usr/lib/python2.7/site-packages/pygame/tests/util/build_page/libs/build_client/test_fixtures/BUILD_FAILED_UNKNOWN
    /usr/lib/python2.7/site-packages/pygame/examples/__init__.py
    /usr/lib/python2.7/site-packages/gtk-2.0/egg/__init__.py
    /usr/lib/python2.7/site-packages/gtk-2.0/gi/overrides/__init__.py
    /usr/lib/python2.7/site-packages/sonata/__init__.py
    /usr/lib/python2.7/site-packages/sonata/plugins/__init__.py
    /usr/lib/python2.7/email/mime/__init__.py
    /usr/lib/python2.7/email/test/__init__.py
    /usr/lib/python2.7/sqlite3/test/__init__.py
    /usr/lib/python2.7/pydoc_data/__init__.py
    /usr/lib/python2.7/bsddb/test/__init__.py
    /usr/lib/python2.7/lib-tk/test/test_ttk/__init__.py
    /usr/lib/python2.7/lib-tk/test/test_tkinter/__init__.py
    /usr/lib/python2.7/lib2to3/tests/data/fixers/myfixes/__init__.py
    /usr/lib/purple-2/perl/auto/Purple/Purple.bs
    /usr/lib/perl5/vendor_perl/auto/HTML/Parser/Parser.bs
    /usr/lib/perl5/vendor_perl/auto/XML/Parser/Expat/Expat.bs
    /usr/lib/perl5/vendor_perl/auto/Crypt/SSLeay/SSLeay.bs
    /usr/lib/perl5/vendor_perl/auto/Irssi/Irssi.bs
    /usr/lib/perl5/vendor_perl/auto/Irssi/UI/UI.bs
    /usr/lib/perl5/vendor_perl/auto/Irssi/Irc/Irc.bs
    /usr/lib/perl5/vendor_perl/auto/Irssi/TextUI/TextUI.bs
    /usr/lib/pidgin/perl/auto/Pidgin/Pidgin.bs
    /usr/lib/firefox-3.6/.autoreg
    archuser@archws ~ %
    Last edited by aluser (2011-01-21 03:02:22)

  • [SOLVED] zsh: Failed to execute operation: No such file or directory

    I recently ordered a chromebook (acer c720) and have successfully replaced ChromeOS with Arch Linux. Things were going great the past 2 days but all of a sudden whenever I try to use tab completion on zsh (does not happen in bash or any other shell I've tested) I receive the message:
    Failed to execute operation: No such file or directory
    My .zprofile is:
    emulate sh -c 'source /etc/profile'
    #[[ -f ~/.zshrc ]] && . ~/.zshrc
    if [[ -z $DISPLAY ]] && [[ $(tty) = /dev/tty1 ]]; then
    startx
    fi
    My .zshenv is:
    export PATH=/home/zach/.bin:$PATH
    export EDITOR=nano
    export BROWSER=firefox
    [[ $(tty) = /dev/tty1 ]] && xrdb merge /home/zach/.config/xresources
    My .zshrc is:
    #source ~/.zshenv
    # Lines configured by zsh-newuser-install
    HISTFILE=~/.histfile
    HISTSIZE=100000
    SAVEHIST=100000
    HISTCONTROL=ignoredups
    setopt appendhistory autocd extendedglob nomatch
    bindkey -e
    # End of lines configured by zsh-newuser-install
    # The following lines were added by compinstall
    zstyle :compinstall filename '/home/zach/.zshrc'
    autoload -Uz compinit
    compinit
    # End of lines added by compinstall
    PS1=$'\e[1;36m%~\e[0m >>\e[1;36m>\e[0m%] '
    #Begin Aliases
    alias edit='$EDITOR'
    alias sedit='sudo $EDITOR'
    alias pacman='sudo pacman'
    # Listing
    alias ls='ls --color=auto --group-directories-first'
    alias lsl='ls --color=auto --group-directories-first -l'
    alias lsa='ls --color=auto --group-directories-first -al'
    alias lsp='ls --color=auto --group-directories-first -alp'
    # Moving/Copying
    alias cp='cp -r'
    alias rm='rm -r'
    alias ...='cd ../..'
    alias ....='cd ../../..'
    alias bd='cd -'
    alias mkdir='mkdir -p'
    # System
    alias systemctl='sudo systemctl'
    alias journalctl='sudo journalctl'
    alias cronedit='EDITOR=nano crontab -e'
    alias reload-daemons='sudo systemctl daemon-reload'
    alias enable='sudo systemctl enable'
    alias disable='sudo systemctl disable'
    alias start='sudo systemctl start'
    alias stop='sudo systemctl stop'
    Is there something I'm missing or not considering? The tab completion still works, it just displays that message every time inline and it's really annoying. Also I searched google, the wiki, and the forums for any information regarding this and either my search-fu isn't strong enough or it's not showing up elsewhere.
    Last edited by revoltorb (2014-09-13 14:05:44)

    Rename the "enable" and "disable" aliases. They are zsh hash table operators.

  • Pacman issue - error: .. : No such file or directory.

    It seems I have my first issue, and it's with Pacman. I get this error everytime I sync the database or install a package, even though everything seems to go fine.
    error: /var/lib/pacman/extra/flite-1.3-2/desc: No such file or directory
    I don't know what flite is but it won't install it as it doesn't exist even though there is a directory called "flite-1.3-2" and it's empty. I've tried removing the directory but synching the database doesn't put it back. Also I've used 'pacman -Scc' to clear cache but still no joy.

    archuser wrote:
    It seems I have my first issue, and it's with Pacman. I get this error everytime I sync the database or install a package, even though everything seems to go fine.
    error: /var/lib/pacman/extra/flite-1.3-2/desc: No such file or directory
    I don't know what flite is but it won't install it as it doesn't exist even though there is a directory called "flite-1.3-2" and it's empty. I've tried removing the directory but synching the database doesn't put it back. Also I've used 'pacman -Scc' to clear cache but still no joy.
    delete the directory /var/lib/pacman/extra and run pacman -Sy to restore. I believe if you delete just the flite directory it won't restore with Sy.

  • [solved] ArchCK boot: /bin/sh: No such file or directory

    I am getting some weird errors on my arch install.
    I chrooted to my install, mounted tmp, and "pacman -Syu"'d.  I'm using the archck kernel in extra.  Now when I try to boot, I get the following errors:
    mount: Mounting none on /proc failed: Device or resource busy.
    mknod: /dev/null: File exists.
    mount: Mounting /dev/root on /new_root failed: No such device or address
    pivot_root: pivot_root: No such file or directory
    chroot: cannot execute /bin/sh: No such file or directory
    Kernel panic - not syncing: Attempted to kill init!
    I really don't know what to do with this.  Any help?  I think it has to do with how I am using mkinitramfs in a chrooted filesystem.  I'm not sure thogh.  And yes, all my paths in configs are right.

    Ok, it seems that your initramfs image doesn't contain all the necesary modules to access your boot partition. To boot, use
    mkinitramfs full
    to create an image with all the modules, it should be named initramfs26-full.img or something similar. Configure your bootloader accordingly. It shoudl boot.
    After that you should tweak your mkinitramfs.conf file so it includes only the modules you need, so you don't need ot use the "full" image.

  • [SOLVED] startx - open /dev/fb0: No such file or directory

    Hej,
    it was a long time since I've boot my Arch Linux. So I did all the updates. After rebooting my X was broken. He said that some Modules are missing: sis, vga and fbdev. So I've installed them with pacman. But now he sais the following when I try to start X with 'startx':
    (EE) open dev/fb0: No such file or directory
    So, anyone knows about what to do now?
    And I'm also wondering if it was right, that Arch dont use a xorg.conf?
    Thanks
    neb.anch
    Last edited by neb.anch (2008-07-18 10:57:31)

    neb.anch:  xorg-server-1.4.2-2 with a similar card is working fine over here, try https://belug.de/~lutz/pub/v5535/sis_vg … .04.tar.gz and extract the sis_drv.so into your /usr/lib/xrog/modules/drivers
    Although a poster who gave that link to a newer/unoffcial driver for the said SIS card is still strugling, but the driver worked fine for both my Debian and Archlinx.

  • [SOLVED]Pacman error: could not open file /var/.../portaudio

    Anyone got any insight?
    Any pacman or AUR-helper operation I try to do results in many repititions of this error.
    [marcus@ARCH ~]$ packer -Syu
    Password:
    :: Synchronizing package databases...
    core is up to date
    extra 450.4K 401.0K/s 00:00:01 [##########################################] 100%
    error: failed retrieving file 'community.db.tar.gz' from mirrors.easynews.com#####-------------] 68%
    community 372.7K 997.9K/s 00:00:00 [##########################################] 100%
    :: Starting full system upgrade...
    error: could not open file /var/lib/pacman/sync/community/portaudio-19_20071207-2/desc: No such file or directory
    error: could not open file /var/lib/pacman/sync/community/portaudio-19_20071207-2/desc: No such file or directory
    error: could not open file /var/lib/pacman/sync/community/portaudio-19_20071207-2/desc: No such file or directory
    error: could not open file /var/lib/pacman/sync/community/portaudio-19_20071207-2/desc: No such file or directory
    error: could not open file /var/lib/pacman/sync/community/portaudio-19_20071207-2/desc: No such file or directory
    [snip many repeats of same error]
    [marcus@ARCH ~]$ packer portaudio
    0 error: could not open file /desc: could not open file /var/lib/pacman/sync/community/portaudio-19_20071207-2/desc: No such file or directory
    1 community/desc: 19_20071207-2error: could not open file /var/lib/pacman/sync/community/portaudio-19_20071207-2/desc: No such file or directory
    error: could not open file /var/lib/pacman/sync/community/portaudio-19_20071207-2/desc: No such file or directory
    2 aur/haskell-portaudio 0.0.1-2
    Haskell bindings for the PortAudio library.
    3 aur/mingw32-portaudio 19_20071207-1
    A free, cross-platform, open source, audio I/O library (mingw32)
    4 aur/portaudio-svn 1384-3
    PortAudio is a free, cross platform, open-source, audio I/O library.
    5 aur/pyaudio 0.2.3-3
    Python bindings for PortAudio, the cross-platform audio I/O library
    6 aur/portaudio_v18 pa_snapshot_v18-3
    A free, cross-platform, open source, audio I/O library
    Type numbers to install. Separate each number with a space.
    Numbers: 1
    error: could not open file /var/lib/pacman/sync/community/portaudio-19_20071207-2/depends: No such file or directory
    desc: package not found, searching for group...
    error: could not open file /var/lib/pacman/sync/community/portaudio-19_20071207-2/desc: No such file or directory
    error: 'desc:': not found in sync db
    Last edited by Skripka (2010-05-11 18:21:11)

    hokasch wrote:looks like that mirror has some problem, switch to another one for the time being
    That mirror does have a problem...but switching to a different mirror returns the same mystery local error.  PS-I haven't had portaudio installed on my system in at least 6 months, and pacman has started returning errors about it this morning
    Last edited by Skripka (2010-05-11 18:15:33)

  • [SOLVED] pacman error: could not open file /var/lib ...

    the actual error is
    error: could not open file /var/lib/pacman/sync/community/fonteditfs-1.2-2/desc: No such file or directory
    removing that folder fixed it. i dont know if it was a coding mistake or just my box did something stupid today :S
    any thoughts?
    Last edited by eldragon (2010-04-20 17:25:18)

    geniuz wrote:
    I don't know if this error occured during an update of right after you've invoked pacman, but in any way synchronizing pacman I think should fix the issue. This is something you might have tried before deleting the file, but then again I don't know when the error occured. If it occured immediately deleting the file would probably be the easiest solution. I would've done the same.
    If you've synchronized pacman after you've removed the file all should be well now, maybe something indeed went wrong during an update (maybe your mirror went down or something, you never know).
    yes, the error apperared right after syncing the databases. the update went as expected...

Maybe you are looking for

  • I got a new computer how do i put the songs from my ipod to my itunes?

    Help i got a new computer how do i put the songs from my ipod to my itunes?

  • Hd partition won't unmount

    I have a MacBook pro that I am trying to install mountain lion on.  Long story short it tells me I have errors on my hard drive that need fixing first.  I can now only reboot to the os x install/time machine back up /disc utility.   I don't have a ba

  • X201s does not initiate hibernation on Fn+F12 just goes to login window

    Hi! I have an X201s system on Windows 7 64-bit. Hibernation worked when I bought the machine factory-installed. I recently reinstalled the system from original recovery media then installed all updates through Microsoft and Lenovo update, then instal

  • Name of Sender Problem

    Hello, I began sending media files of various projects at work, from my mobile phone under another provider (gmail) to my work email (Outlook). Ever since I did that, every email I now recieve in outlook, weither it be from my boss, coworkers, or any

  • Option of creating a DIR from Asset master not available

    hi I have one document type for which object link is Asset master ( ANLA, Screen no: 225). In customizing for create document, option selected is Use transaction to create document. Now When I go to Asset master -> extra -> Document data , there I ge