[solved] lm_sensors and lib32-lm_sensors upgrade fails

-thc · Yesterday 05:42:09

Trying to upgrade lm_sensors and lib32-lm_sensors from 3.6.0.r41.g31d1f125-3 to 3.6.2-1 fails with

(2/2) checking for file conflicts                                                                         [##############################################################] 100%
error: failed to commit transaction (conflicting files)
/usr/share/zsh/site-functions/_sensors exists in both 'lm_sensors' and 'lib32-lm_sensors'
/usr/share/zsh/site-functions/_sensors-detect exists in both 'lm_sensors' and 'lib32-lm_sensors'
Errors occurred, no packages were upgraded.

Last edited by -thc (Yesterday 12:37:29)

lucasm · Yesterday 05:56:45

I'm having this exact same issue at the same time go figure. Hoping someone here can help, google wasnt too helpful. ):

Yujiro Hanma · Yesterday 05:57:50

It is a packaging issue most probably, should be rectified pretty soon.

Beru · Yesterday 06:12:14

It does, indeed, seem to be a packaging issue with lib32-lm_sensors

See relevant issues on the issue tracker here and here.

In the interim you can checkout the PKGBUILD and edit it.

Change its pkgrel to 1.2. Then, for the following line:

rm -r "${pkgdir}"/usr/{bin,sbin,include,man}

...change it to:

rm -r "${pkgdir}"/usr/{bin,sbin,include,man,share}

In order to remove the newly added zsh keybindings that are breaking the build.

Last edited by Beru (Yesterday 06:18:18)

rug4ru · Yesterday 06:29:58

Had the same issue.
Maybe its a bad solution, but it worked for me.
At first I manually upgraded lm_sensors by "pacman -S lm_sensors", then I renamed conflicting files and did "pacman -Syu" again, and it worked.
Diff between files didnt show anything.
P.S. Using the same file in two different packages looks not very clever for me.

Last edited by rug4ru (Yesterday 07:11:30)

ibk · Yesterday 06:47:17

Same issue here.

SimonJ · Yesterday 07:11:50

rug4ru wrote:

At first I upgraded lm_sensors by "pacman -S lm_sensors", then I renamed conflicting files and did "pacman -Syu" again.
It worked for me. Diff between files didnt show anything.
Using the same file in two different packages looks not very clever for me.

Isn't this the wrong way round? lm_sensors should have these files, so you will need to correct this for next upgrade?

Oops, nvm, I see the command change would achieve the same, you are right.

Last edited by SimonJ (Yesterday 07:19:44)

GreenTuxer · Yesterday 07:12:24

I have the same issue. I don't want to rename the files, I prefer to wait for a fixed package or an official solution.

rug4ru · Yesterday 07:18:04

SimonJ wrote:

rug4ru wrote:
At first I upgraded lm_sensors by "pacman -S lm_sensors", then I renamed conflicting files and did "pacman -Syu" again.
It worked for me. Diff between files didnt show anything.
Using the same file in two different packages looks not very clever for me.
Isn't this the wrong way round? lm_sensors should have these files, so you will need to correct this for next upgrade?
Oops, nvm, I see the command change would achieve the same, you are right.

It has the same files after lib32-lm_sensors upgrade on their places, but if something goes wrong, you can rename files back

Last edited by rug4ru (Yesterday 07:19:47)

lucasm · Yesterday 07:18:23

rug4ru wrote:

Had the same issue.
Maybe its a bad solution, but it worked for me.
At first I manually upgraded lm_sensors by "pacman -S lm_sensors", then I renamed conflicting files and did "pacman -Syu" again, and it worked.
Diff between files didnt show anything.
P.S. Using the same file in two different packages looks not very clever for me.

Thanks man this worked for me. I appreciate it! I was confused at first because when the error very first appeared for me, i couldnt find those files. And now they are there after updating lm_sensors *headscratcher

CyrIng · Yesterday 07:40:27

Had forced successfully the update

pacman -Syyuu

SometimesYes · Yesterday 07:42:03

rug4ru wrote:

Had the same issue.
Maybe its a bad solution, but it worked for me.
At first I manually upgraded lm_sensors by "pacman -S lm_sensors", then I renamed conflicting files and did "pacman -Syu" again, and it worked.
Diff between files didnt show anything.
P.S. Using the same file in two different packages looks not very clever for me.

This worked for me! After running the proposed workaround, I rebooted and ran

nvidia-inst

After yet another reboot my GUI started working again.

rug4ru · Yesterday 08:11:17

This issue may be not relevant anymore.
After I did workaround with file renaming "lib32-lm_sensors" has been updated, and -Syu upgraded it with no errors

rug4ru · Yesterday 08:12:57

CyrIng wrote:

Had forced successfully the update
pacman -Syyuu

Afaik yy is really unsafe and not recommended to use, is it?

marko3 · Yesterday 08:21:24

I did it like this:

sudo pacman -Suy --overwrite '/usr/share/zsh/site-functions/_sensors' --overwrite '/usr/share/zsh/site-functions/_sensors-detect'

mpan · Yesterday 08:33:40

lib32-lm_sensors has been updated to fix the issue. Wait for it to be available on your mirror.

If that was not fixed already, upgrading these packages could have been postponed temporarily. The update doesn’t introduce any new .so version. That would introduce a partial update and partial updates are unsupported. But nobody is going to mind it being a part of temporarily circumventing a packaging issue, if you are always clear and open about this being the case.

CyrIng wrote:

Had forced successfully the update
pacman -Syyuu

This isn’t a solution. You were simply lucky that the package has been fixed and that your mirror updated it. It would work equally with plain -Syu.

Don’t use `-Syyuu` blindly in hope that it magically fixes anything. It is only helpful in a very few, very specific situations. In most cases it only causes unneeded load on the volunteer-donated infrastructure.

GreenTuxer · Yesterday 09:22:48

I confirm, the updated package fixes the issue.

rug4ru · Yesterday 09:45:24

Issue is solved, I suppose.

Arch Linux

#1 Yesterday 05:42:09

[solved] lm_sensors and lib32-lm_sensors upgrade fails

#2 Yesterday 05:56:45

Re: [solved] lm_sensors and lib32-lm_sensors upgrade fails

#3 Yesterday 05:57:50

Re: [solved] lm_sensors and lib32-lm_sensors upgrade fails

#4 Yesterday 06:12:14

Re: [solved] lm_sensors and lib32-lm_sensors upgrade fails

#5 Yesterday 06:29:58

Re: [solved] lm_sensors and lib32-lm_sensors upgrade fails

#6 Yesterday 06:47:17

Re: [solved] lm_sensors and lib32-lm_sensors upgrade fails

#7 Yesterday 07:11:50

Re: [solved] lm_sensors and lib32-lm_sensors upgrade fails

#8 Yesterday 07:12:24

Re: [solved] lm_sensors and lib32-lm_sensors upgrade fails

#9 Yesterday 07:18:04

Re: [solved] lm_sensors and lib32-lm_sensors upgrade fails

#10 Yesterday 07:18:23

Re: [solved] lm_sensors and lib32-lm_sensors upgrade fails

#11 Yesterday 07:40:27

Re: [solved] lm_sensors and lib32-lm_sensors upgrade fails

#12 Yesterday 07:42:03

Re: [solved] lm_sensors and lib32-lm_sensors upgrade fails

#13 Yesterday 08:11:17

Re: [solved] lm_sensors and lib32-lm_sensors upgrade fails

#14 Yesterday 08:12:57

Re: [solved] lm_sensors and lib32-lm_sensors upgrade fails

#15 Yesterday 08:21:24

Re: [solved] lm_sensors and lib32-lm_sensors upgrade fails

#16 Yesterday 08:33:40

Re: [solved] lm_sensors and lib32-lm_sensors upgrade fails

#17 Yesterday 09:22:48

Re: [solved] lm_sensors and lib32-lm_sensors upgrade fails

#18 Yesterday 09:45:24

Re: [solved] lm_sensors and lib32-lm_sensors upgrade fails

Board footer