[Testing Update] 2020-04-26 - Gnome 3.36.2, Wine 5.7, Firefox, Python

[Drek]

same thing for me

[freggel.doe]

It will update your package database from your mirrors but is a potentially dangerous command that might lead to partial updates if you don't update immediatly after. Better (always) use:

$ sudo pacman -Syyu

[mapmo]

@VoDo

Did pacman -Syyu and the still get the exactly same message as @Vodo, the last time I upgraded was 10 hours ago after the previous issue with gnome-layout-switcher was fixed and everything was fine with my mirror.

[freggel.doe]

Is this related to testing branch and it's current update? If not - you're posting in the wrong place.

Check if your mirror is up to date: https://repo.manjaro.org/

[GaVenga]

@pretzelbrain
@drek
@freggel.doe

Uninstall manjaro-gnome-settings (20200425-1)
update
install manjaro-gnome-settings-19.0 (20200412-3)

[philm]

More or less this is related to gnome-layout-switcher update and the fact that some of you are on versioned settings packages.

gnome-layout-switcher 0.8.7-1 -> 0.8.8.2 requires to downgrade multiple packages

Hello everyone, I received a notification for new upgrades and I was surprised that the new upgrade wanted me to downgrade packages. Take a look at this screenshot: [Screenshot from 2020-04-25 23-28-40] As you can see I have gnome-layout-switcher 0.8.7-1 and the new package version is 0.8.8-2. For some reason the dependencies for the new version are lower than those of the current version. I am not a package expert, but I think that this is weird and I wanted to consult with you before comp…

Check which manjaro-gnome packages are installed on your end:

pacman -Qq | grep manjaro-gnome

Then remove them via

pacman -Rdd

And install the ones without a versioning:

pacman -S manjaro-gnome-assets manjaro-gnome-extension-settings manjaro-gnome-settings

[pretzelbrain]

Sorry, but philm linked to my post, that is why I replied.

I'm on the stable branch, btw.

[pretzelbrain]

@freggel.doe

It will update your package database from your mirrors but is a potentially dangerous command that might lead to partial updates if you don't update immediatly after. Better (always) use:

$ sudo pacman -Syyu

I just did this and it worked, but I had to refuse the 19.0 & 18.0 stuff:

:: Starting full system upgrade...
:: Replace manjaro-gnome-extension-settings with community/manjaro-gnome-extension-settings-18.0? [Y/n] n
:: Replace manjaro-gnome-extension-settings with community/manjaro-gnome-extension-settings-19.0? [Y/n] n
:: Replace manjaro-gnome-settings with community/manjaro-gnome-settings-18.0? [Y/n] n
:: Replace manjaro-gnome-settings with community/manjaro-gnome-settings-19.0? [Y/n] n
resolving dependencies...

[jr29]

and how it works

[mapmo]

I already have the versionless packages

mapmo@Lenovo-L340:~>$ pacman -Qq | grep manjaro-gnome
manjaro-gnome-assets
manjaro-gnome-extension-settings
manjaro-gnome-settings

[philm]

Then update them first:

sudo pacman -Sydd manjaro-gnome-assets manjaro-gnome-extension-settings manjaro-gnome-settings

And try a normal update later

sudo pacman -Su

[zenbum]

$ pacman -Si manjaro-gnome-settings{,-18.0,-19.0}|grep '^Replaces'
Replaces        : manjaro-gnome-settings-19.0
Replaces        : manjaro-gnome-settings
Replaces        : manjaro-gnome-settings

The new package replaces 19.0, but both 18.0 and 19.0 replace the new package. Is there a loop here?

[philm]

Well, in the past it got replaced by the versioned and now it gets replaced again. @Ste74 maybe we should remove the old packages then ...

[Ste74]

At the Moment i can go in front at my PC this afternoon .. if you can do It before go away .. at the Moment my mouse Is this

[jr29]

be careful not to get sunburned

[philm]

A new way of social distancing. If you don't keep the distance meet my friend

[Ste74]

Indeeded more efficient

[mapmo]

There is nothing for updating and even after reinstalling, I still get the dependency conflict messages

[GaVenga]

Mmmh: try - unstall "conflict files"---> update the rest ---> install "conflict files"

[mapmo]

The issue is already fixed and I upgraded successfully