ngativ wrote:abveritas wrote:pacman was rebuild, but not part of a .db for this update, it is fixed for x86_64 (-4 is not up for i686 yet).It is me or pacman doesn't recognize my ccr install anymore neither?Forget it! i just received a pacman update that fixed it
In my shell script I am using the zip command to zip the log files. The zip file is password protected. But there is a dicey.
I want the output as:
1) All files should be zipped including sub-directories' files
2) All files (individually) should be Password protected (may be common or different)
3) User should feed the password as input just once.
You are obviously using [kde-unstable], so I will move the post.Please paste a complete output of "pacman -Syu". The above paste says nothing.These kind of issues are usually fixed by doing a "sudo pacman -Syyu".
abveritas wrote:SpiderOaks last promo was sigining up with the code WORLDBACKUPDAY, but seems this one expired.@abveritas Thank you very much for the information. Since I am a current SpiderOak user hopefully they will allow me to go up to 5gb instead of previous limit of 2gb even though the 5gb promotion has expired.
abveritas wrote:Mentioning you just got an amarok update, indictaes that your updates have not been correct. Or updating once very 3 months with a rolling relaese, not the best plan either. Do you use pacman -Syu solely for updates? Before installing ANY package ever, do you always pacman -Syu first? Checked if your mirror is syncing correctly?I get the updates as soon as t
2ManyDogs wrote:senorsmile wrote:I have found the rngd in aur. However, since I can't run pacman yet, I can't install anything. The wiki says to run haveged before, but I can't install that either until I run the key init.Arch wiki wrote:Initializing the keyringTo set up the pacman keyring use:pacman-key --initFor this initialization entropy is required.
Thanks for the reply, abveritas. System is fixed now. Here's how I got into -- and out of -- this mess:Initially, I ran: pacman -Syu --ignore filesystem && pacman -S filesystem --force && pacman -S chakra-initThe chakra-init sync failed due to conflicts -- I don't recall conflict descriptions.
We have a Windows 7 machine (but in the near future we may use a Windows Server one) which we use for showing a screensaver on a big display. The host is in the company domain, we log to the machine with a domain account, and we set the screensaver timeout to 1 minute.