[Solved] Help With Update

Hello,

I have been using Netrunner for six months (first experience with Linux). I picked this distro after watching videos and reading about the various trypes of distros out there. It seemed to offer a learning experience as well as enough preinstalled content for a novice such as myself to get started. I have learned quite a bit and got tons of windows games and other things intalled/wroking without having to post a question somewhere, but now i find myself stumped. Currently I am trying to update my rolling release to match 2014.09, but I am running into issues. After consulting the readme and typing the commands specified commands, I see this:

[color=#1E90FF][slingshot@Slingshot ~]$ sudo rm -R /var/lib/pacman/local/bash-4.3.024-1
[sudo] password for slingshot:
rm: cannot remove ‘/var/lib/pacman/local/bash-4.3.024-1’: No such file or directory
[slingshot@Slingshot ~]$ sudo pacman -Sy bash
:: Synchronizing package databases…
blueshell is up to date
core is up to date
extra is up to date
community is up to date
multilib is up to date
:: The following packages should be upgraded first :
manjaro-system pacman
:: Do you want to cancel the current operation
:: and upgrade these packages now? [Y/n] y

resolving dependencies…
looking for inter-conflicts…

Packages (3): bash-4.3.030-1 manjaro-system-20141014-1 pacman-4.1.2-7

Total Installed Size: 11.19 MiB
Net Upgrade Size: 6.18 MiB

:: Proceed with installation? [Y/n] y
(3/3) checking keys in keyring [###################################] 100%
(3/3) checking package integrity [###################################] 100%
(3/3) loading package files [###################################] 100%
(3/3) checking for file conflicts [###################################] 100%
error: failed to commit transaction (conflicting files)
bash: /usr/bin/bash exists in filesystem
bash: /usr/bin/bashbug exists in filesystem
bash: /usr/bin/sh exists in filesystem
bash: /usr/share/doc/bash/CHANGES exists in filesystem
bash: /usr/share/doc/bash/COMPAT exists in filesystem
bash: /usr/share/doc/bash/FAQ exists in filesystem
bash: /usr/share/doc/bash/INTRO exists in filesystem
bash: /usr/share/doc/bash/NEWS exists in filesystem
bash: /usr/share/doc/bash/POSIX exists in filesystem
bash: /usr/share/doc/bash/RBASH exists in filesystem
bash: /usr/share/doc/bash/README exists in filesystem
bash: /usr/share/doc/bash/bash.html exists in filesystem
bash: /usr/share/doc/bash/bashref.html exists in filesystem
bash: /usr/share/info/bash.info.gz exists in filesystem
bash: /usr/share/locale/af/LC_MESSAGES/bash.mo exists in filesystem
bash: /usr/share/locale/bg/LC_MESSAGES/bash.mo exists in filesystem
bash: /usr/share/locale/ca/LC_MESSAGES/bash.mo exists in filesystem
bash: /usr/share/locale/cs/LC_MESSAGES/bash.mo exists in filesystem
bash: /usr/share/locale/da/LC_MESSAGES/bash.mo exists in filesystem
bash: /usr/share/locale/de/LC_MESSAGES/bash.mo exists in filesystem
bash: /usr/share/locale/el/LC_MESSAGES/bash.mo exists in filesystem
bash: /usr/share/locale/en@boldquot/LC_MESSAGES/bash.mo exists in filesystem
bash: /usr/share/locale/en@quot/LC_MESSAGES/bash.mo exists in filesystem
bash: /usr/share/locale/eo/LC_MESSAGES/bash.mo exists in filesystem
bash: /usr/share/locale/es/LC_MESSAGES/bash.mo exists in filesystem
bash: /usr/share/locale/et/LC_MESSAGES/bash.mo exists in filesystem
bash: /usr/share/locale/fi/LC_MESSAGES/bash.mo exists in filesystem
bash: /usr/share/locale/fr/LC_MESSAGES/bash.mo exists in filesystem
bash: /usr/share/locale/ga/LC_MESSAGES/bash.mo exists in filesystem
bash: /usr/share/locale/gl/LC_MESSAGES/bash.mo exists in filesystem
bash: /usr/share/locale/hr/LC_MESSAGES/bash.mo exists in filesystem
bash: /usr/share/locale/hu/LC_MESSAGES/bash.mo exists in filesystem
bash: /usr/share/locale/id/LC_MESSAGES/bash.mo exists in filesystem
bash: /usr/share/locale/it/LC_MESSAGES/bash.mo exists in filesystem
bash: /usr/share/locale/ja/LC_MESSAGES/bash.mo exists in filesystem
bash: /usr/share/locale/lt/LC_MESSAGES/bash.mo exists in filesystem
bash: /usr/share/locale/nl/LC_MESSAGES/bash.mo exists in filesystem
bash: /usr/share/locale/pl/LC_MESSAGES/bash.mo exists in filesystem
bash: /usr/share/locale/pt_BR/LC_MESSAGES/bash.mo exists in filesystem
bash: /usr/share/locale/ro/LC_MESSAGES/bash.mo exists in filesystem
bash: /usr/share/locale/ru/LC_MESSAGES/bash.mo exists in filesystem
bash: /usr/share/locale/sk/LC_MESSAGES/bash.mo exists in filesystem
bash: /usr/share/locale/sl/LC_MESSAGES/bash.mo exists in filesystem
bash: /usr/share/locale/sr/LC_MESSAGES/bash.mo exists in filesystem
bash: /usr/share/locale/sv/LC_MESSAGES/bash.mo exists in filesystem
bash: /usr/share/locale/tr/LC_MESSAGES/bash.mo exists in filesystem
bash: /usr/share/locale/uk/LC_MESSAGES/bash.mo exists in filesystem
bash: /usr/share/locale/vi/LC_MESSAGES/bash.mo exists in filesystem
bash: /usr/share/locale/zh_CN/LC_MESSAGES/bash.mo exists in filesystem
bash: /usr/share/locale/zh_TW/LC_MESSAGES/bash.mo exists in filesystem
bash: /usr/share/man/man1/bash.1.gz exists in filesystem
bash: /usr/share/man/man1/bashbug.1.gz exists in filesystem
Errors occurred, no packages were upgraded.[/color]

Addtional info: Using Kernel 3.14.21-1 and have also tried commands sudo pacman -S manjaro-system pacman,
sudo pacman -Syu.

There is a possibility i did manage to upgrade and this error just means im an idiot.

This is all you should need to update the system, including bash:

sudo pacman -Syyu

However, after manjaro-system and pacman are updated, you will need to run it a second time like this:

sudo pacman -Su

Thanks for the reply. Gave a shot with sudo pacman -Syyu and received the same error message as above.

OK then:

sudo pacman-mirrors -g
sudo pacman -Syy
sudo pacman -S bash --force
sudo pacman -S manjaro-system pacman
sudo pacman -Su

Problem Solved. The second set of commands did the trick, but not all of them (sudo pacman -S manjaro-system pacman).

So I entered these
sudo pacman-mirrors -g
sudo pacman -Syy
sudo pacman -S bash --force

then once bash installed i could enter

sudo pacman -Syyu
sudo pacman -Su

I think the original problem was because i failed to keep up with updates as they were released.

Yes, this is very possible.
I’m very glad to hear that you were able to get it updated.
[hr]
PS. May I suggest that you should keep an eye out here on the forums as I usually make a post shortly after each update-pack is released.

Will do and thanks.