[SOLVED] Pacman 4 Update Not Working: Conflicting Files

VaustMortifera · 2013-09-29 04:28:41

So, I'm trying to update my computer, and it gives me:

:: The following packages should be upgraded first :
    pacman
:: Do you want to cancel the current operation
:: and upgrade these packages now? [Y/n] y

After entering "y," it attempts to update, but it gives out an error.

resolving dependencies...
looking for inter-conflicts...

Targets (7): bash-4.2.045-5  filesystem-2013.05-2  glibc-2.18-3
             libarchive-3.1.2-2  linux-api-headers-3.10.6-1  lzo2-2.06-1
             pacman-4.1.2-1

Total Installed Size:   49.56 MiB
Net Upgrade Size:       -2.78 MiB

Proceed with installation? [Y/n] y
(7/7) checking package integrity                   [######################] 100%
(7/7) loading package files                        [######################] 100%
(7/7) checking for file conflicts                  [######################] 100%
error: failed to commit transaction (conflicting files)
filesystem: /bin exists in filesystem
filesystem: /sbin exists in filesystem
filesystem: /usr/sbin exists in filesystem
Errors occurred, no packages were upgraded.

I tried looking in the wiki, but I didn't find anything that would help. None of the current threads seemed to have the same problems I am, so I'm asking here.

I'm really needing pacman updated so that I can update my wireless driver and be able to connect to the Internet without needing to plug an ethernet cable in every single time.

Thanks.

Edit: It has been about 6 months to a year since I have actually used my computer due to a wiring problem in the power connector. I have finally gotten my computer back up and running after dismantling most of it and putting it back together, and my wireless has not been working since.

Last edited by VaustMortifera (2013-09-29 17:33:21)

henk · 2013-09-29 04:45:23

Take a look at https://bbs.archlinux.org/viewtopic.php?id=164312. There is a big difference between six months and a year.
If it is really a year, you missed the migration to systemd completely.

WonderWoofy · 2013-09-29 05:06:47

You probably want to go to the news and check all that out. It might actually be the case that resintalling is easier since there have been so many big changes to Arch in the past year. On top of that, we also recently lost the Arch Rollback Machine, meaning that trying to do incremental updates from there to get up to speed is not impossible.

Scimmia · 2013-09-29 06:56:51

It's it's 6 months, just follow the upgrade procedure on the front page news. If it's a year, forget it, just reinstall.

VaustMortifera · 2013-09-29 17:32:12

Thanks for the advice. I think I may just need to do a reinstall at this point.

I'm actually thinking about switching back to Ubuntu until I get a better grasp of Arch, but either way, I need to get a LiveCD made or something.

Thanks again, and I'll get to work on the reinstall.

karol · 2013-09-29 17:42:23

There's no shame in trying something out and realizing you may not have what it takes (I'm not talking specifically about Arch Linux, just generally about life and evrything) or you're looking for something different.
Good luck and have fun :-)

cfr · 2013-09-30 01:00:15

WonderWoofy wrote:

You probably want to go to the news and check all that out. It might actually be the case that resintalling is easier since there have been so many big changes to Arch in the past year. On top of that, we also recently lost the Arch Rollback Machine, meaning that trying to do incremental updates from there to get up to speed is not impossible.

I don't think this is what you meant to say?

WonderWoofy · 2013-09-30 01:40:44

I guess what I was trying to get at is that if the installation is super out of date, it might require going through each news post one at a time. So say if it was a year ago, there would be filesystem packages that you would need to get through the updates that would no longer be available anywhere now that the ARM is gone (or at least the old ARM). If it was a bit over a year ago, you risk running into the /lib → /usr/lib merge, which would require upgrading just past that before moving further as well.

So I guess I just wasn't very clear in what i was trying to get at here…

cfr · 2013-09-30 20:26:40

Oh. I thought 'not' was just a typo for 'now'.

Arch Linux

#1 2013-09-29 04:28:41

[SOLVED] Pacman 4 Update Not Working: Conflicting Files

#2 2013-09-29 04:45:23

Re: [SOLVED] Pacman 4 Update Not Working: Conflicting Files

#3 2013-09-29 05:06:47

Re: [SOLVED] Pacman 4 Update Not Working: Conflicting Files

#4 2013-09-29 06:56:51

Re: [SOLVED] Pacman 4 Update Not Working: Conflicting Files

#5 2013-09-29 17:32:12

Re: [SOLVED] Pacman 4 Update Not Working: Conflicting Files

#6 2013-09-29 17:42:23

Re: [SOLVED] Pacman 4 Update Not Working: Conflicting Files

#7 2013-09-30 01:00:15

Re: [SOLVED] Pacman 4 Update Not Working: Conflicting Files

#8 2013-09-30 01:40:44

Re: [SOLVED] Pacman 4 Update Not Working: Conflicting Files

#9 2013-09-30 20:26:40

Re: [SOLVED] Pacman 4 Update Not Working: Conflicting Files

Board footer