Electron update!

[limotux]

Trying to update but I get:

[limo@asus ~]$ yay
:: Synchronizing package databases...
 endeavouros is up to date
 core is up to date
 extra is up to date
 community is up to date
 multilib is up to date
:: Searching AUR for updates...
:: Searching databases for updates...
 -> Flagged Out Of Date AUR Packages: python-coloredlogs
:: 1 package to upgrade/install.
1  extra/electron  22.3.13-1 -> 25.1.1-2
==> Packages to exclude: (eg: "1 2 3", "1-3", "^4" or repo name)
 -> Excluding packages may cause partial upgrades and break systems
==> 
Sync Dependency (1): electron-25.1.1-2
:: Synchronizing package databases...
 endeavouros is up to date
 core is up to date
 extra is up to date
 community is up to date
 multilib is up to date
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...
error: failed to prepare transaction (could not satisfy dependencies)
:: installing electron (25.1.1-2) breaks dependency 'electron22' required by code
 -> error installing repo packages
[limo@asus ~]$ 

So, looking for electron I found:

4 extra/electron24 24.5.1-1 (59.2 MiB 207.4 MiB) 
    Build cross platform desktop apps with web technologies
3 extra/electron25 25.1.1-1 (60.4 MiB 212.3 MiB) 
    Build cross platform desktop apps with web technologies
2 extra/electron19 19.1.9-5 (54.8 MiB 176.9 MiB) 
    Build cross platform desktop apps with web technologies
1 extra/electron 25.1.1-2 (60.4 MiB 212.3 MiB) (Installed: 22.3.13-1)
    Build cross platform desktop apps with web technologies
==> Packages to install (eg: 1 2 3, 1-3 or ^4)
==> 

Shouldn’t yay update everything? (which I actually did)
I wonder how/why this happens?
Is it my system? (Started thinking of doing a fresh install despite this misses the point of a rolling release!)

[pycrk]

Hi,
you should update the mirrors and update your system. since you still have the community repo, you didn’t set up your system according to the specifications after the last pacman update, you should do that.

Arch repo migration

There are some upcoming changes to the Arch repos that everyone should be aware of. What is happening Full details are in the link below but the most important note to be aware of is: The [testing] repository will be split into [core-testing] and [extra-testing], the [staging] repository will be split into [core-staging] and [extra-staging]. The [community] repository will be merged into [extra] and will therefore be empty after the migration. https://archlinux.org/news/git-migration-annou…

Edit: not to forget the EnOS and arch keyrings should also be updated, try to do one by one and ask if you get stuck.

[limotux]

Thank you @pycrk

@pycrk

you should update the mirrors and update your system.

@pycrk

and ask if you get stuck.

Well, I just thought and launched the Welcome app, clicked the 5 top left buttons to update repos, mirrors… etc.

Still the same. What I am doing wrong?

[I0F]

Try installing electron22 yourself with this

sudo pacman -S electron22

Then update again.

Code seems to need electron22 but the update wants to replace it with the newest electron package, which is at version 25. If you have electron22 installed on your system it should work.

[limotux]

@I0F

sudo pacman -S electron22

Thanks @I0F

[limo@asus ~]$ sudo pacman -S electron22
resolving dependencies...
looking for conflicting packages...
:: electron22 and electron are in conflict. Remove electron? [y/N] 
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: electron22 and electron are in conflict
[limo@asus ~]$ 
[limo@asus ~]$ 

Maybe I should press “y” instead of the default “N”?

[I0F]

Please post your output of

pacman -Ss electron22

and

pacman -Ss electron

For electron22 it should find this: extra/electron22 22.3.13-2
For electron it should find this somewhere: extra/electron 25.1.1-2

If the versions don’t match, your mirrors are still not up to date.

[limotux]

@I0F

Please post your output of

pacman -Ss electron22

and

pacman -Ss electron

[limo@asus ~]$ pacman -Ss electron22
extra/electron22 22.3.13-2
    Build cross platform desktop apps with web technologies
[limo@asus ~]$ 

[limo@asus ~]$ pacman -Ss electron

extra/asar 3.2.3-1
    Creating Electron app packages
extra/datovka 4.22.1-1
    GUI application for a 'Databox' - an electronic communication interface endorsed by the Czech government
extra/eid-mw 5.1.4-2
    The Belgian e-ID (electronic identity card) viewer and Firefox extension
extra/electron 25.1.1-2 [installed: 22.3.13-1]
    Build cross platform desktop apps with web technologies
extra/electron17 17.4.11-6
    Build cross platform desktop apps with web technologies
extra/electron19 19.1.9-5
    Build cross platform desktop apps with web technologies
extra/electron20 20.3.12-2
    Build cross platform desktop apps with web technologies
extra/electron21 21.4.4-1
    Build cross platform desktop apps with web technologies
extra/electron22 22.3.13-2
    Build cross platform desktop apps with web technologies
extra/electron23 23.3.7-1
    Build cross platform desktop apps with web technologies
extra/electron24 24.5.1-1
    Build cross platform desktop apps with web technologies
extra/electron25 25.1.1-1
    Build cross platform desktop apps with web technologies
extra/emby-theater 3.0.19-3
    An Electron app for Emby
extra/kicad 7.0.5-1
    Electronic schematic and printed circuit board (PCB) design tools
[limo@asus ~]$ 

[pebcak]

What says: pactree -r electron ?

[I0F]

Hmm, this is weird.
What happens if you do
sudo pacman -S electron electron22
and install both again?

[limotux]

@pebcak

pactree -r electron ?

[limo@asus ~]$ pactree -r electron
electron
└─code
[limo@asus ~]$ 

[I0F]

Or just try installing code again.

sudo pacman -S code

It seems code has changed its dependency from electron to electron22.

[limotux]

@I0F

and install both again?

Both? Aren’t they the same?
Doing it anyway!

[pebcak]

Try installing electron22 and say yes to removing electron.

I f you get any breaking dependency, abort the transaction and post it here.

If not, you are good.

[limotux]

I think

@I0F

sudo pacman -S electron electron22

Is done!

==> root: 8408
:: Processing package changes...
(1/2) upgrading electron                                           [------------------------------------] 100%
(2/2) installing electron22                                        [------------------------------------] 100%
Optional dependencies for electron22
    kde-cli-tools: file deletion support (kioclient5) [installed]
    libappindicator-gtk3: StatusNotifierItem support
    pipewire: WebRTC desktop sharing under Wayland [installed]
    qt5-base: enable Qt5 with --enable-features=AllowQt [installed]
    trash-cli: file deletion support (trash-put)
    xdg-utils: open URLs with desktop’s default (xdg-email, xdg-open) [installed]
:: Running post-transaction hooks...
(1/4) Arming ConditionNeedsUpdate...
(2/4) Checking which packages need to be rebuilt
foreign python-coloredlogs
(3/4) Updating the desktop file MIME type cache...
(4/4) Performing snapper post snapshots for the following configurations...
==> root: 8409
[limo@asus ~]$ 

[pycrk]

electron22 is a dependencie for code
https://archlinux.org/packages/extra/x86_64/code/

[I0F]

Does the normal update work now?

[limotux]

@I0F

Hmm, this is weird.
What happens if you do
sudo pacman -S electron electron22
and install both again?

[limo@asus ~]$ yay
:: Synchronizing package databases...
 endeavouros is up to date
 core is up to date
 extra                                   8.3 MiB  3.09 MiB/s 00:03 [------------------------------------] 100%
 community is up to date
 multilib is up to date
:: Searching AUR for updates...
:: Searching databases for updates...
 -> Flagged Out Of Date AUR Packages: python-coloredlogs
 there is nothing to do
[limo@asus ~]$ 

[limotux]

@I0F

Does the normal update work now?

Yes, as per my previous post.
But I wonder why the system didn’t manage automatically!

@limotux

Maybe I should press “y” instead of the default “N”?

I wonder if what I thought of is correct?

[I0F]

I’m still not sure what happened here. electron22 and electron should not be in conflict, because those packages can be installed the same time.

Removing electron could’ve helped, but it still shouldn’t print errors like this.

[limotux]

@I0F

I’m still not sure what happened here.

I assume yay or Pacman should install/upgrade whatever needed by itself.
Maybe I should have answered “y” instead of just “Enter” for the default. If so, I wonder who should change the default? The developer (the package itself) or Arch itself?