Dependence issue of PlayOnLinux

English Applications
#1

When installing the PlayOnLinux, zypper shows the following dependence error:

#####~> sudo zypper in PlayOnLinux
[sudo] password for root: 
Loading repository data...
Reading installed packages...
Resolving package dependencies...

Problem: nothing provides 'dbus-1-python' needed by the to be installed PlayOnLinux-4.4.0-bp154.1.108.noarch
 Solution 1: do not install PlayOnLinux-4.4.0-bp154.1.108.noarch
 Solution 2: break PlayOnLinux-4.4.0-bp154.1.108.noarch by ignoring some of its dependencies

And I find that the package ‘dbus-1-python’ does not exit in the offical repositories.

#####~> zypper se dbus-1-python
Loading repository data...
Reading installed packages...
No matching items found.

Is it a bug?
I am on KDE.
And here is my repo

#  | Alias                       | Name             | Enabled | GPG Check | Refresh | Priority | Type   | URI                                                                         | Service
---+-----------------------------+------------------+---------+-----------+---------+----------+--------+-----------------------------------------------------------------------------+--------
 1 | openSUSE-Leap-15.4-1        | openSUSE-Leap--> | No      | ----      | ----    |   99     | rpm-md | hd:/?device=/dev/disk/by-id/usb-_USB_FLASH_DRIVE_0702328E2C0C6B26-0:0-part2 | 
 2 | packman                     | Packman          | Yes     | (r ) Yes  | Yes     |   90     | rpm-md | https://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Leap_15.4/         | 
 3 | repo-backports-debug-update | Update reposit-> | No      | ----      | ----    |   99     | NONE   | http://download.opensuse.org/update/leap/15.4/backports_debug/              | 
 4 | repo-backports-update       | Update reposit-> | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/update/leap/15.4/backports/                    | 
 5 | repo-debug                  | Debug Repository | No      | ----      | ----    |   99     | NONE   | http://download.opensuse.org/debug/distribution/leap/15.4/repo/oss/         | 
 6 | repo-debug-non-oss          | Debug Reposito-> | No      | ----      | ----    |   99     | NONE   | http://download.opensuse.org/debug/distribution/leap/15.4/repo/non-oss/     | 
 7 | repo-debug-update           | Update Reposit-> | No      | ----      | ----    |   99     | NONE   | http://download.opensuse.org/debug/update/leap/15.4/oss/                    | 
 8 | repo-debug-update-non-oss   | Update Reposit-> | No      | ----      | ----    |   99     | NONE   | http://download.opensuse.org/debug/update/leap/15.4/non-oss/                | 
 9 | repo-non-oss                | Non-OSS Reposi-> | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/distribution/leap/15.4/repo/non-oss/           | 
10 | repo-oss                    | Main Repository  | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/distribution/leap/15.4/repo/oss/               | 
11 | repo-sle-debug-update       | Update reposit-> | No      | ----      | ----    |   99     | NONE   | http://download.opensuse.org/debug/update/leap/15.4/sle/                    | 
12 | repo-sle-update             | Update reposit-> | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/update/leap/15.4/sle/                          | 
13 | repo-source                 | Source Reposit-> | No      | ----      | ----    |   99     | NONE   | http://download.opensuse.org/source/distribution/leap/15.4/repo/oss/        | 
14 | repo-update                 | Main Update Re-> | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/update/leap/15.4/oss/                          | 
15 | repo-update-non-oss         | Update Reposit-> | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/update/leap/15.4/non-oss/                      |
#2

@ddtty I suspect Leap 15.4 needs a maintenance update to avoid that, it should be python3 Show games:tools / PlayOnLinux - openSUSE Build Service doesn’t exhibit the error…

#3

Yes but, the package “python3-dbus-python” provides ‘dbus-1-python3’.

> zypper search --provides dbus-1-python

#4

Thank you both for the reply.

Indeed, I have ‘python3-dbus-python’ installed.
But it provides ‘dbus-1-python3’ instead of ‘dbus-1-python’

Information for package python3-dbus-python:
--------------------------------------------
Repository     : Main Repository
Name           : python3-dbus-python
Version        : 1.2.16-6.3.1
Arch           : x86_64
Vendor         : SUSE LLC <https://www.suse.com/>
Installed Size : 469.3 KiB
Installed      : Yes (automatically)
Status         : up-to-date
Source package : python-dbus-python-1.2.16-6.3.1.src
Upstream URL   : https://www.freedesktop.org/wiki/Software/DBusBindings/
Summary        : Python bindings for D-Bus
Description    : 
    D-Bus python bindings for use with python programs.
Provides       : [3]
    dbus-1-python3 = 1.2.16
    python3-dbus-python = 1.2.16-6.3.1
    python3-dbus-python(x86-64) = 1.2.16-6.3.1

Hoping there will be the patch to fix this issue.

#5

There won’t be unless you report it. Or you can wait until someone reports it (apparently you are the first to try this package though :slight_smile: )

#6

Where should I report to?
Bugzilla?

#7

Yes, all bugs are going to bugzilla.

#8

@ddtty no patch needed, just needs an update to the spec file… MR created for you: Request 1058012: Incident PlayOnLinux - openSUSE Build Service

1 Like
#9

Have you asked yourself why zypper could not find it then?

zypper search performs partial match.

#10

Given, the original error, it’s clear that the package displaying the error isn’t compatible with the current openSUSE Python packages.

  • Meaning that, the OpenQA associated with the package isn’t testing everything that it should do …
#11

@ddtty the Maintenance Request was accepted, not sure how long it will take to get to the update repository now…

#12

Is there a chance that, someone will take a look at the OpenQA tests?

#13

@dcurtisfra Anyone can, and change? I’m surprised the MR was accepted considering the Maintenance folks are on holiday until next week…

#14

@ddtty the Maintenance Request was accepted, not sure how long it will take to get to the update repository now…

I have been aware of that.
Many thanks for your help.