[SOLVED] error: could not open file /var/lib/pacman/local/qt-4.5.2-4/
Hi all,
So there I was, running pacman -Syu on all my Arch machines, and I get to my desktop PC at work, and half way through X decides to crash and kick me back to the CLI. Fair enough
Now when I try and use pacman, I get a whole bunch of errors about a missing 'depends' directory:
root ~ # pacman -S amarok
resolving dependencies...
error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
looking for inter-conflicts...
error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
error: could not open file /var/lib/pacman/local/qt-4.5.2-4/depends: No such file or directory
It still asks me to continue with installing the new package, but I'd rather get this fixed first in case it buggers it up worse
Last edited by fukawi2 (2009-07-30 05:44:25)
Once again my saviour Allan -- I had to -Sf it due to file already existing, but seems to be good now
Similar Messages
-
I am trying to install Arch but when I type "pacstrap /mnt base base-devel" I keep on getting this error "error could not open file /var/lib/pacman/sync/core.db unrecognized archive format".
I have tried:
# rm -R /var/lib/pacman/sync/
# pacman -Syuf
I have also tried pacman -Syy with no luck.
What more is there to do besides installing ubuntu?
Last edited by johane (2012-08-11 08:22:07)johane wrote:
I am trying to install Arch but when I type "pacstrap /mnt base base-devel" I keep on getting this error "error could not open file /var/lib/pacman/sync/core.db unrecognized archive format".
I have tried:
# rm -R /var/lib/pacman/sync/
Pacstrap was telling you it couldn't open a file, so you just deleted the entire directory tree? Did it appear to be downloading the database files correctly before this? Did you try running pacstrap again after you deleted everything?
And then you tried to run pacman with the -f (force) option? What happened? "no luck" doesn't tell us anything.
What more is there to do besides installing ubuntu?
There are many things you can do. You can give us more information about what you did and what happened. Did you follow all the steps in the Beginners Guide up to the pacstrap step? Did you get any errors or warnings before that step? Are you sure you had a working network connection? Did you interrupt the pacstrap process at any time? Did you try running it again after you deleted /var/lib/pacman/sync?
Did you check the sha1sum of the iso you downloaded before you put it on a usb stick?
https://wiki.archlinux.org/index.php/Be … oaded_file
How did you put it on the usb stick?
When you got the error, did you do
ls /var/lib/pacman/sync
to see what (if anything) was there?
Last edited by 2ManyDogs (2012-08-06 23:38:27) -
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... -
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) -
Fatal error : can not open file 'msvcrt.lib'
Hello dudes !
I am using windows and jdk1.6. I want to develop one application using JNI. As steps for JNI, i have created Helloworld java class and compiled it, then created header file using jnh. After that i have created HelloWorld.c file.
To build dll file, i am executing the below command
"cl -Ic:\java\include -Ic:\java\include\win32 -MD -LD HelloWorld.c -FeHelloWorld.dll".
Command giving the output as follows:
HelloWorld.c
Microsoft (R) Incremental Linker Version 8.00.50727.42
Copyright (C) Microsoft Corporation. All rights reserved.
/dll
/implib:HelloWorld.lib
/out:HelloWorld.dll
HelloWorld.obj
LINK : fatal error LNK1104: cannot open file 'MSVCRT.lib'
Can anybody say why it is giving this problem.
Also i tried giving the msvcrt.lib path as the value for -MD option,
cl -Ic:\java\include -Ic:\java\include\win32 -MD"c:\Microsoft Visual Studio 8\VC\lib" -LD HelloWorld.c -FeHelloWorld.dll
Then it is giving "can not open file LIBCMT.lib" .
Note : ...\VC\lib and ....\VC\include are added in the path.
Can anybody tell the solution for this ?
Thanks in advance!!Hi,
I was with the same problem. You have set the your VCC environment.
Path, Include and Lib.
In your directory VCC (2003 toolkit), you have a .bat file (vcvars32.bat)
Run the bat, or copy and past this command in your command prompt.
In my compilation, I run the code, wihtout -MD and -LF. In your, just:
cl -Ic:\java\include -Ic:\java\include\win32 HelloWorld.c -FeHelloWorld.dll
thanks,
Fabio Pinheiro
Brasil. -
[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) -
Heya Arch Forums,
So it's my first time installing and I've made it to the point were I'm ready to install X11.
When I run "pacman -S xorg-server xorg-xinit xorg-server-utils" my console returns the following errors:
error: could not open file /var/lib/pacman/sync/testing.db: Unrecognized archive format
error: could not open file /var/lib/pacman/sync/multilib.db: Unrecognized archive format
error: could not open file /var/lib/pacman/sync/core.db: Unrecognized archive format
error: could not open file /var/lib/pacman/sync/extra.db: Unrecognized archive format
error: could not open file /var/lib/pacman/sync/community-testing.db: Unrecognized archive format
error: could not open file /var/lib/pacman/sync/community.db: Unrecognized archive format
error: could not open file /var/lib/pacman/sync/testing.db: Unrecognized archive format
These errors repeat again followed by:
error: target not found: xorg-twm
I'm in Canada, so I've only set my mirror list to use "Server = http://mirror.csclub.uwaterloo.ca/archlinux/$repo/os/$arch"
Also, in my /etc/pacman.conf all SigLevel's are = Never.
Thanks for any replies.skunktrader wrote:Did you run pacman -Syu before attempting to install new packages?
Thanks for the quick reply
Yes, however pacman -Syu as well as pacman -Syyu return the same errors. -
DART: Could not open file c:\datafile.txt on application server
We are running data extracts on DART (t-code FTW1A).
However we get error:
Could not open file c:\datafile.txt on application server ####.
We verified that c:\datafile is existing and accessible.
Please help tell why? Pints guaranteed. Thanks!Hi,
Are you able to see the file from AL11 or using report RSWATCH0. Also please check below thread it may help you.
File not created in application server
Thanks,
Sushil -
I can't use bigpkg anymore, because it expects everything in /var/lib/pacman/local/ to be a directory:
https://aur.archlinux.org/packages/bigpkg/ -> http://allanmcrae.com/scripts/bigpkg
Here are the important lines:
LOCAL_DB_PATH="/var/lib/pacman/local"
file = LOCAL_DB_PATH + "/" + dir + "/desc"
f = open(file, "r")
After running 'pacman-db-upgrade', /var/lib/pacman/local/ALPM_DB_VERSION was placed there
$ pacman -Qo /var/lib/pacman/local/ALPM_DB_VERSION
error: No package owns /var/lib/pacman/local/ALPM_DB_VERSION
$ cat /var/lib/pacman/local/ALPM_DB_VERSION
9
$ bigpkg
Traceback (most recent call last):
File "/usr/bin/bigpkg", line 83, in <module>
parse_package_info(pkg, dir)
File "/usr/bin/bigpkg", line 51, in parse_package_info
f = open(file, "r")
NotADirectoryError: [Errno 20] Not a directory: '/var/lib/pacman/local/ALPM_DB_VERSION/desc'
I can remove that file and make bigpkg work again, but it breaks pacman:
error: failed to initialize alpm library
(database is incorrect version: /var/lib/pacman/)
error: try running pacman-db-upgrade
Is it a bug? If not, can someone please fix bigpkg? I don't speak python, so I can't do it myself :-(
Last edited by karol (2015-01-16 18:50:59)progandy wrote:
I believe you can use bigpkg if you patch it like this:
for dir in os.listdir(LOCAL_DB_PATH):
try:
pkg = dir[0:dir.rindex("-",0,dir.rindex("-"))]
pkg_list.append(pkg)
parse_package_info(pkg, dir)
except ValueError:
pass
Can you post a diff? I have no idea where to put it.
bigpkg complains
$ /usr/bin/bigpkg_patched
Traceback (most recent call last):
File "/usr/bin/bigpkg_patched", line 53, in <module>
pkg_list.append(pkg)
NameError: name 'pkg_list' is not defined
if I try to use the part you posted before the line that says
pkg_list = []
but I still have problems with
file = LOCAL_DB_PATH + "/" + dir + "/desc"
f = open(file, "r") -
I am geting this error when I enter the "java" command:
"Error: could not open `C:\Program Files\Java\j2re1.4.0_01\lib\i386\jvm.cfg'"
I have configured the PATH variable (Windows 2000) and "javac" works. I cannot, however, get my programs to run because of the error every time I type "java". Also, I did not install my JDK / SDK to the directory in which the computer is looking for the "java" cammand (ie. it is not in 'Program Files'...). If anyone can help, it would be greatly appreciated. Thank you.Try using the -cp switch on the command line. For example:java -cp . MyProgramIf this corrects the problem, you need to set the classpath variable
as well as the path.
Mark -
I am using Adobe Acrobat 9 Standard version in Windows 8.1 and when I try to create a .pdf file, I receive the following error message "Acrobat could not open "file name.log" because it is either not a supported file type or because the file has been damaged. To create a PDF document, go to the source application then print the document to .pdf" I am going to the source application and printing the document to .pdf yet it's saving the file as a .log file. After reinstalling the software, I initially didn't encounter this problem but on my second and third attempts to convert files to .pdf format, this error message reappeared. How do I resolve this problem?
I have a similar problem which i did not have before...and it exists only in some powerpoint files which i want to print as a pdf file...and i get the same message as above.
the log says the bellow details...what's the problem and how can i resolve it? thanks.
%%[ ProductName: Distiller ]%%
%%[Page: 1]%%
%%[Page: 2]%%
Cambria not found, using Courier.
%%[ Error: invalidfont; OffendingCommand: show ]%%
Stack:
%%[ Flushing: rest of job (to end-of-file) will be ignored ]%% -
Error message Could not open file....on application server
Hi Experts,
we are using 3.1 production server which has four application servers, after harware upgrdation we are facing connectivity problem with datastage.
daily the infospkoes and abap programs are faling with the message "Could not open file........on application server".
when we trigger manually on one server then it gets success, means we are facing problem with other 3 appliction servers. we do not know how to go about this issue.Hi,
This is error RSBO214 and can be due to upper/lower case letters within your destination path.
Maybe you have changed the path in transaction SE16?
In case you change the destination manually, you have to make sure that that the directory exists and that the authorizations are set up correctly for the extraction user.
Rgds,
Colum -
Entourage error 'could not open that feature end of file reached
When opening Entourage I received the error 'Could not open that feature. End of file reached' I tried Utility and rebuild. when attempting to rebuild a pane came up stating 'preparing to rebuild 0 of 0' and the pane has been stuck there for 8 hours. Every other office product works though. any ideas?
Contact Microsoft for support. That's not an Apple product.
-
Gerring Error -"Could not open command file"
Hi All,
I'm using Business Object Data services XI 4.0 .When I executes the job it given an error -"Could not open command file "
so if anyone know the solution then please let me know.
Thanks
Rajeev kumar
SAP-BODI DeveloperThe -compat=4 (and the default -compat=5) compilation modes are not related to the compiler version. All compiler versions from 5.0 (1998) through 5.10 (2009) have these options. The C++ Migration Guide
[http://docs.sun.com/app/docs/doc/819-5266]
explains the differences in detail between -compat=4 and -compat=5, with examples of how to make old code compatible with standard C++.
There is no compiler version 7. Perhaps you are thinking of the Sun Studio release. There is a Sun Studio 7 (containing C++ 5.4), but it is End Of Life, no longer available for purchase, and is not supported on Solaris 10. The recent releases are these:
Sun Studio 11, C++ 5.8, supports Solaris 8, 9, 10
Sun Studio 12, C++ 5.9, supports Solaris 9, 10, Open Solaris, Linux
Sun Studio 12 update 1, C++ 5.10, supports Solaris 10, Open Solaris, Linux
(Sun Studio 12 update 1 should be released next week. Watch this forum for an announcement.)
Please run the command
CC -V
to find out your compiler version.
When compiling on Solaris, 32-bit compilation is the default. You don't get 64-bit compilation unless you ask for it, via the -xarch option on older compilers, or the -m64 option on current compilers. -
Photoshop cse 5 error "Could not open scratch file because disk is not available" using Maverick
I am getting the following error:
"Could not open scratch file because disk is not available"
I am using Adobe Photoshop CS5 on the Mac Operating System "Maverick". The application is currently loaded on an external bootable drive. I created an external bootable drive using "Disk Utilities". I've changed the directory /private/ to 777 using the following command "chmod -R 777 /private/". I have created the external bootable drive in the event that my current internal drive crashes. I would just then have to swap the drives out. I created the external bootable drive using DYNEX SATA Hard drive enclosure.
Photoshop General DiscussionI searched around and found the answer. My question was to specific. Jim Olvera had the same problem and this was the solution with the help of Adobe Support.
OS X Mavericks. I was able to resolve it after a chat discussion with Adobe support. It is indeed a permissions issue apparently, but not one that can be resolved with Disk Utility. I was able to change to another scratch disk by holding down "Command + Option" as I launched Photoshop, and that did it. Still can't use the previous disk as a scratch, though, even though permissions have been repaired.
JO
Thank you for your suggestion, but I could not even get to the point where "Photoshop" would even open up.
Thank you everyone!
Maybe you are looking for
-
Passing a parameter to a Web start app
Hi, I'm having trouble getting a single integer value into my web start application. I understand how you do this with a JNLP however I need a different value for this integer depending on a PHP script. With applets it was fairly simple but with web
-
Hi everyone, I am working on implementing FSCM Dispute Managment module. I have some questions regarding the new standard content provided by SAP for this: Earlier I have seen clients using the Stanadard InfoSet 0DPM_I0 for all the Dispute's reportin
-
Adobe flash plugin crashes when I open Frontierville in Facebook
9 out of ten times that I open Frontierville in Facebook I get an error that says "Adobe Flash plugin has crashed". I have reinstalled the plugin numerous times. I cleared my cache. Finaly, after 2 days of this I uninstalled and reinstalled both Fire
-
/* Session6B07.java */ /* Evaluates compatibility for a dating agency */ import java.util.*; public class Session6B07 public static void main(String[] args) /* Description ...... Prompt for and read both ages IF both ages are valid
-
Unable to block Non-Corprate machine access to CORP wireless network
Hello everyone I am facing this problem right now , I created rule 1 for host authentication and rule 2 for user authentication ,but seems I am unable to block non-corprate machine * IPAD or smart phone* to access CORP wireless net