[Testing Update] 2018-05-05 - RT-Kernels, Nvidia 390xx, Firefox Dev, MHWD

update
testing

#7

I had to remove libmozjs-52.so.0 on two different machines, as stated in the Wiki, but all OK after reboot. KDE edition.


#8

#9

…done,done, all fine.


#10

Could we make a transition package, that removes this file in case it’s there, owned by nobody? Because thats again a showstopper for normal people.

EDIT: :joy:


#11

Even applying fix js52 and it is “broken”. Looks like fix is incomplete.


error: failed to commit transaction (conflicting files)
js52: /usr/lib/libmozjs-52.so.0 exists in filesystem
Errors occurred, no packages were upgraded.

Maybe because I’m using firefox nightly from AUR?


#12

My Linux Manjaro_KDE_VM 4.16.7-1-MANJARO #1 SMP PREEMPT Wed May 2 19:14:22 UTC 2018 x86_64 GNU/Linux update was successful but not uneventful:

  1. The same need for sudo rm /usr/lib/libmozjs-52.so.0 per Wiki, & as other Testers also reported.
  2. A repeat of this annoyance… [Testing Update] 2018-05-01 - BFQ Scheduler (v4.16, v4.17), Vulkan, Hyper, & so today i had to repeat this earlier advice [Testing Update] 2018-05-01 - BFQ Scheduler (v4.16, v4.17), Vulkan, Hyper . As i also enquired in that prior thread, given i don’t use/need/want Samba, can i remove it somehow please [avoiding the potential mess implied by [Testing Update] 2018-05-01 - BFQ Scheduler (v4.16, v4.17), Vulkan, Hyper]?

[Stable Review] 2018-05-05 - Kernels, Plasma5, Nvidia, Mesa, GlibC, Firefox, Deepin
#13

lib32-libaio is not update but libaio is, so i can’t install the update because of broken dependencies.


#14

after removing the said lib everything went fine! thx


#16

Hi everyone .
Little problem with js52 too:

(1/1) mise à jour de manjaro-system                [######################] 100%
==> Fix js52 upgrade ...

erreur : la validation de la transaction a échoué (conflit de fichiers)
js52 : /usr/lib/libmozjs-52.so.0 est déjà présent dans le système de fichiers
Des erreurs se sont produites, aucun paquet n’a été mis à jour.

I solved with:

[steph@manjaro ~]$ sudo mv /usr/lib/libmozjs-52.so.0 /usr/lib/libmozjs-52.so.0.old
[sudo] Mot de passe de steph : 
[steph@manjaro ~]$ sudo pacman -Su
...........
..........
### update ok###
sudo rm /usr/lib/libmozjs-52.so.0.old

I hope it could help.


#17

I got an error with yay:

==> Error: Could not find all required packages:
    pacman>=4.2

It would be because manjaro-system has a contradiction in package info:

Provides        : pacman=4.1.2
Depends On      : pacman>=4.2

I bypassed this error by using pacman.


#18

An official workaround will be better I think. Anyway, looks like next stable update will be big and late.


#19

Install went fine after removing requested file.


#20

After running from

sudo rm /usr/lib/libmozjs-52.so.0

ran update without problems.


#21

Looks like proposed workaround is not working at all :frowning:


#22

Late to update this time and the workaround did not work for me either:

(1/1) upgrading manjaro-system                     [######################] 100%
==> Fix js52 upgrade ...
:: Running post-transaction hooks...
(1/2) Checking for orphaned packages...
(2/2) Arming ConditionNeedsUpdate...
:: Starting full system upgrade...
[...]
error: failed to commit transaction (conflicting files)
js52: /usr/lib/libmozjs-52.so.0 exists in filesystem
Errors occurred, no packages were upgraded.

I noted that the old libmozjs-52.so.0 was a symlink to libmozjs-52.so, whereas after finishing the update (following manual intervention) now libmozjs-52.so is a symlink to libmozjs-52.so.0.

I am also worried that lib32-libaio 0.3.110-1 (not updated) lists its dependency as libaio=0.3.110 since libaio is now at 0.3.111-1.

That said it did not cause me any immediate problems on updating.


#23

Thx, update went well!


#24

There is a new about js52 on Archlinux.org.

https://www.archlinux.org/news/js52-5273-2-upgrade-requires-intervention/


#25

Published on may 4th, 2018. The same for archlinux.fr -> https://archlinux.fr/news/la-mise-a-jour-de-js52-52-7-3-2-requiert-une-intervention-manuelle


#26

#27

Workaround on js52 didnt work here either. Removed js52 and updated without other issues. So far no other problems. Thanks to everyone for posting the js52 information. Regards.