Pacman - Upgrade Fail (Can't Satisfy Dependencies)

ARM
1

Hi folks,

I’ve got a new pinephone running KDE-Plasma on 5.18.0-1-MANJARO-ARM aarch64. Fresh out of the box, KDE Discover indicates 622 packages need upgrade. In fact, I’m getting dependency failures even when trying to install single packages from there, so I figure we need to run the upgrade. However, attempting to run from there returns this error:

Dependency resolution failed:
kcoreaddons <- kdav2, kcoreaddons <- kimap2, ki18n <- kirigami-addons, kcontacts <- kpeoplesink, kpeople <- kpeoplesink, kcontacts <- sink, kcalendarcore <- sink: could not satisfy dependencies

Moving to the terminal, I try the following:

pacman-mirrors -f 5 && pacman -Syu

This is where the fun begins. There now comes a 72-item-long series of queries re: whether I’d like to replace a package with another version, e.g.:

Replace appstream-qt with extra/appstream-qt5? [Y/n]

Then it asks me to pick a provider for dbus-units, and a few more y/n dependency resolution queries, and finally fails with unresolvable package conflict. Here’s the last lines of the output:

resolving dependencies...
:: There are 2 providers available for dbus-units:
:: Repository core
   1) dbus-broker-units  2) dbus-daemon-units

Enter a number (default=1): 1
looking for conflicting packages...
warning: removing 'libgpiod' from target list because it conflicts with 'libgpiod1'
:: kitemmodels5 and kitemmodels are in conflict. Remove kitemmodels? [y/N] n
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: kitemmodels5 and kitemmodels are in conflict (kitemmodels<5.111)

As you can see, I answered no there. I’ve tried it both ways. I should also say that I’ve run pacman -Syyu after adjusting mirrors, and the problem is the same.

Any help would be greatly appreciated :slight_smile:

2

Can you use pamac upgrade ?

1 Like
3

Ah, hadn’t tried that. Thanks for the suggestion. Trying now…

Ok, it didn’t work, and the error at the end is very similar:

sudo pamac upgrade
Preparing...
Synchronizing package databases...
Choose a provider for dbus-units:
1:  dbus-broker-units  35-2       core
2:  dbus-daemon-units  1.14.10-2  core

Enter a number (default=1): 1

Resolving dependencies...
Choose a provider for dbus-units:
1:  dbus-broker-units  35-2       core
2:  dbus-daemon-units  1.14.10-2  core

Enter a number (default=1): 2

Checking inter-conflicts...
Warning: removing 'libgpiod' from target list because it conflicts with 'libgpiod1'
Error: Failed to prepare transaction:
could not satisfy dependencies:
- removing kcoreaddons breaks dependency 'kcoreaddons' required by kdav2
- removing ki18n breaks dependency 'ki18n' required by kirigami-addons
- removing kcontacts breaks dependency 'kcontacts' required by kpeoplesink
- removing kpeople breaks dependency 'kpeople' required by kpeoplesink
- removing kcalendarcore breaks dependency 'kcalendarcore' required by sink
4

I don’t own a Pipephone and i have not the slighest clue about ARM stuff.

But this version number looks pretty outdated, is it possible that you installed your Pipephone with a really old .ISO?

I hope i remember correctly here, but i think kpeople on my Desktop was a orphan after my switch from Plasma5 to Plasma6 (6month ago).

This tells me that you may have a outdated version and its better to use a brand new iso for a fresh install.

1 Like
5

I was wondering the same. Tried to use mhwd to see where we’re at and hopefully fix it that way, but evidently arm does it some other way (no mhwd).

Anyways, yeah, good note. I’ll try it and report back.

*edit to mention that this is what came installed on the phone, brand new yesterday

1 Like
6

I wouldn’t be surprised if the (pre-installed) .iso isn’t refreshed in the last second before shipping :wink:

And since Manjaro is a rolling distro, this may lead to a regression to use a stoneage iso :crazy_face:

btw. i still don’t use a Smartphone till today and i evade it on all possible ways, but if my government forced me to use it, i would prefer to buy a Pipephone with this cool Hardware Switches instead a Spyphone.

1 Like
7

I finally got round to this. I’m now running an iso downloaded today. inxi -S shows the kernel is 6.1.0-rc8-1-MANJARO-ARM. So, fingers crossed, I tried the same sequence of steps, and here’s how it went:

  • first KDE Discover: Same problem as before
  • then pacman-mirrors -f 10 && pacman -Syyu: Same problem as before
  • finally pamac update: Same problem as before
8

I saw that ARM Area isn’t regularly updated… i have no idea whats going on there.

The Topic is from 12/2022 and showed Beta 14 Release.

Where a Pipephone user facing the same problem as you… with no feedback from other’s :frowning:

But the Beta 16 (03/2023) which is also kind old for my understanding, but showed a much newer release date as Beta 14… probably will work better.

1 Like
9

So you just acquired a pinephone?

Just for the sake of clarification - Is this the standard edition or the Pro edition?

Did you flash it yourself or did it come with the OS installed?

If you flashed it yourself - then you should create a new image - do not download a prebuilt image (unless it is a Manjaro Arm CI build) and reflash the phone.

10

Likely you need to remove libgpiod1

11

Yeah, I was initially trying to get the OS that came preinstalled working before trying another. Wanted to do a fair comparison, you know.

Then @Kobald suggested I try the latest arm image, so that’s what I did. Unfortunately, it had the same problem.

@Lolix: Good thought. But, libgpiod1 is not installed. It’s trying to upgrade libgpiod amongst the deps of the upgrade. Also seems that libgpiod is required by eg25-manager, which is the daemon for the modem. Call me a coward, but I’m hesitant to start pulling this thread out of the sweater

12

Looking at upstream compatibility with libgpiod 2.x have been fixed a month ago Compatibility with libgpiod 2.0 (#45) · Issues · Mobian / eg25-manager · GitLab

and Alpine Linux is building against libgpiod 2.x

Also Pine64-Arch

Manjaro-ARM pkgbuild need an update

1 Like
13

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.