Failureto update glibc

[campigenus]

The update of glibc has been failing for the last couple days, any idea when this will be fixed? And hints on fixing the issue myself?

"sh-4.2# pacman -Syu
:: Starting full system upgrade...
resolving dependencies...
looking for inter-conflicts...

Targets (1): glibc-2.16.0-4

Total Installed Size: 33.75 MiB
Net Upgrade Size: 0.10 MiB

Proceed with installation? [Y/n]
(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)
glibc: /lib exists in filesystem
Errors occurred, no packages were upgraded.
"

[WarheadsSE]

pacman -R pcmiatools (probably one of the culprits)
And read up on the issue of glibc-2.16 .. it's all over this forum and upstream.

[campigenus]

I have been reading on the glibc issues, upstream stuff too. Alas, none of the suggested solutions/workarounds does anything for me.
Could this be related to my having fixed the previous "no-boot-flashing-LED" issue by manually linking "/usr/lib/modules"?

"pcmiatools"??

[WarheadsSE]

Which way did you link ?

/lib/modules => /usr/lib/modules or the opposite?

[campigenus]

Came up with the solution on my own, but it ended up being the same as:

"
cd /mnt/wherethepogodiskismounted
cd lib
ln -s ../usr/lib/modules .

"

[WarheadsSE]

Yeah, You're going to need to remove that symlink

[Speed383]

I just rebooted my Plug B01 and it seems glibc installed fine. I did it yesterday and it installed but it wouldn't reboot.

Here is what I did in order:

1. Updated ignoring glibc: $this->bbcode_second_pass_code('', 'pacman -Su --ignore glibc')
2. Removed pcmciautils: $this->bbcode_second_pass_code('', 'pacman -R pcmciautils')
3. Removed oxnas-no pci: $this->bbcode_second_pass_code('', 'pacman -R kernel26-oxnas-nopci')
4. Removed oxnas-pic: $this->bbcode_second_pass_code('', 'pacman -R kernel26-oxnas-pci')
5. Deleted the gmac_copro_firmware from /usr/lib/firmware and copied the one from /lib/firmware to /usr/lib/firmware. ( I did this because I read a post that Warhead specifically said to copy the one from /lib. The one on /usr/lib/firmware may be the same so you might be able to skip this step.)
6. Removed the symlink from /usr/lib/modules to /lib/modules that we linked to install kmod earlier: $this->bbcode_second_pass_code('', 'cd /lib') then $this->bbcode_second_pass_code('', 'unlink modules')
7. Then I ran: $this->bbcode_second_pass_code('', 'grep '^lib/' /var/lib/pacman/local/*/files | grep -v glibc') and $this->bbcode_second_pass_code('', 'find /lib -exec pacman -Qo -- {} +') to make sure that there weren't any other conflicts for glibc.
8. Then update: $this->bbcode_second_pass_code('', 'pacman -Syu')

After that I rebooted and was good to go. I kinda flew through it and didn't take notes because I was actually expecting it to fail since I believe I did the same sequence last night and it bombed. Though it could have been that I was up far too late messing with it.... damn OCD.

[Kamen]

This is interesting. Did you do that off of a clean install of the current root filesystem distributed here (the tarball for the B01 plug), or did you have a previous installation? Has anyone else tried this? Is this a solution or will there be other issues associated with it?
Kamen

[WarheadsSE]

I will be making a new tarball no later than this weekend.

[Kamen]

Thank you, very much, WarheadsSE! No rush, take your time to do a robust fix. It's good to know that there will be a fix. We all appreciate it.
Kamen