FS#68591 - [libretro-dolphin] Package depends on a dependency on community-testing

Attached to Project: Community Packages
Opened by Radio Blah (radiobla_) - Wednesday, 11 November 2020, 18:17 GMT
Last edited by Doug Newgard (Scimmia) - Thursday, 12 November 2020, 03:17 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Maxime Gauduin (Alucryd)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

I'm using the community repository to upgrade libretro and its dependencies.

However, when it tries to upgrade, pacman behaves like the following output:

:: Synchronizing package databases...
core is up to date
extra is up to date
community 5,2 MiB 10,9 MiB/s 00:00 [#####################] 100%
multilib is up to date
:: Starting full system upgrade...
warning: apparmor: ignoring package upgrade (2.13.4-6 => 3.0.0-2)
resolving dependencies...
warning: cannot resolve "libhidapi-hidraw.so", a dependency of "libretro-dolphin"
:: The following package cannot be upgraded due to unresolvable dependencies:
libretro-dolphin

:: Do you want to skip the above package for this upgrade? [y/N]

Somebody in the forums told me that libretro-dolphin seems to be depending on a package that is still on community-testing repository. It might be something to look for.

If you need further information, there is a post on Arch BBS where the issue is being discussed:

https://bbs.archlinux.org/viewtopic.php?id=260686

Additional info:
* package version(s)

Name : libretro-dolphin
Version : 32966-1

* config and/or log files etc.
* link to upstream bug report, if any

Steps to reproduce:

If libretro is installed, the libhidapi-hidraw dependency is missing.

$ sudo pacman -Suy libretro-dolphin


This task depends upon

Closed by  Doug Newgard (Scimmia)
Thursday, 12 November 2020, 03:17 GMT
Reason for closing:  Fixed
Additional comments about closing:  hidapi 0.10.0-2 moved to Community
Comment by Radio Blah (radiobla_) - Wednesday, 11 November 2020, 20:26 GMT
I've just upgraded the package from community repository. The issue seems to be fixed.

Thank you!

Loading...