Results 1 to 6 of 6

Thread: Getting past the Python dependency problem during zypper dup

  1. #1

    Default Getting past the Python dependency problem during zypper dup

    Is there a way around the Python dependency problem when updating Tumbleweed?

    When I use Debian Sid, and, dependencies are waiting for solution, I can use the "--solver=aspcud" during DU.(apt-get --solver-aspcuid dist-upgrade) to get past the problem.

    Right now I have 4 problems when updating.
    4 Problems:
    Problem: python3-wxPython-4.0.1-2.3.x86_64 requires python(abi) = 3.6, but this requirement cannot be provided
    Problem: python3-tqdm-4.28.1-1.1.noarch requires python(abi) = 3.6, but this requirement cannot be provided
    Problem: eric-19.01-1.3.noarch requires python(abi) = 3.7, but this requirement cannot be provided
    Problem: hplip-3.18.6-1.4.x86_64 requires python(abi) = 3.7, but this requirement cannot be provided

    Problem: python3-wxPython-4.0.1-2.3.x86_64 requires python(abi) = 3.6, but this requirement cannot be provided
    deleted providers: python3-base-3.6.5-3.3.x86_64
    Solution 1: deinstallation of python3-wxPython-4.0.1-2.3.x86_64
    Solution 2: keep obsolete python3-base-3.6.5-3.3.x86_64
    Solution 3: break python3-wxPython-4.0.1-2.3.x86_64 by ignoring some of its dependencies

    Does using Solution 1, 2 or 3 make any sense at this time? I've already passed by 3 updates. Should I lock the packages using zypper addlock, or should I just wait until all the python packages are rebuilt? Or, am I missing something?

    Thanks in advance, I've been using Tumbleweed for quite a while and never had to skip 3 updates before, and, I couldn't find solutions on the mailing list or here in the forums.

    Tom

  2. #2
    Join Date
    Jun 2008
    Location
    Groningen, Netherlands
    Posts
    19,090
    Blog Entries
    14

    Default Re: Getting past the Python dependency problem during zypper dup

    Any additional repos involved?
    Code:
    zypper lr -d
    ° Appreciate my reply? Click the star and let me know why.

    ° Perfection is not gonna happen. No way.

    https://en.opensuse.org/openSUSE:Board#Members
    http://en.opensuse.org/User:Knurpht
    http://nl.opensuse.org/Gebruiker:Knurpht

  3. #3

    Default Re: Getting past the Python dependency problem during zypper dup

    zypper lr -d
    # | Alias | Name | Enabled | GPG Check | Refresh | Priority | Type | URI | Service
    ---+---------------------------+-----------------------------+---------+-----------+---------+----------+--------+---------------------------------------------------------------------+--------
    1 | Packman | Packman | Yes | (r ) Yes | Yes | 99 | rpm-md | http://ftp.gwdg.de/pub/linux/misc/pa...SE_Tumbleweed/ |
    2 | google-chrome-beta | google-chrome-beta | Yes | (r ) Yes | Yes | 99 | rpm-md | http://dl.google.com/linux/chrome/rpm/stable/x86_64 |
    3 | http-ftp.gwdg.de-166c2f25 | Packman Repository | Yes | (r ) Yes | Yes | 99 | rpm-md | http://ftp.gwdg.de/pub/linux/packman...SE_Tumbleweed/ |
    4 | libdvdcss | libdvdcss | No | ---- | ---- | 99 | rpm-md | http://opensuse-guide.org/repo/openSUSE_Tumbleweed/ |
    5 | openSUSE-20171114-0 | openSUSE-20171114-0 | No | ---- | ---- | 99 | yast2 | hd:///?device=/dev/disk/by-id/usb-Patriot_Memory_AEC46D2B-0:0-part2 |
    6 | repo-debug | openSUSE-Tumbleweed-Debug | No | ---- | ---- | 99 | NONE | http://download.opensuse.org/debug/tumbleweed/repo/oss/ |
    7 | repo-non-oss | openSUSE-Tumbleweed-Non-Oss | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/tumbleweed/repo/non-oss/ |
    8 | repo-oss | openSUSE-Tumbleweed-Oss | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/tumbleweed/repo/oss/ |
    9 | repo-source | openSUSE-Tumbleweed-Source | No | ---- | ---- | 99 | NONE | http://download.opensuse.org/source/...weed/repo/oss/ |
    10 | repo-update | openSUSE-Tumbleweed-Update | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/tumbleweed/ |
    11 | x86_64 | google-chrome-beta | No | ---- | ---- | 99 | rpm-md | http://dl.google.com/linux/chrome/rpm/stable/x86_64 |
    12 | x86_64_1 | google-talkplugin | Yes | (r ) Yes | Yes | 99 | rpm-md | http://dl.google.com/linux/talkplugin/rpm/stable/x86_64

  4. #4
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    25,464
    Blog Entries
    15

    Default Re: Getting past the Python dependency problem during zypper dup

    Quote Originally Posted by GoinEasy9 View Post
    Is there a way around the Python dependency problem when updating Tumbleweed?

    When I use Debian Sid, and, dependencies are waiting for solution, I can use the "--solver=aspcud" during DU.(apt-get --solver-aspcuid dist-upgrade) to get past the problem.

    Right now I have 4 problems when updating.
    4 Problems:
    Problem: python3-wxPython-4.0.1-2.3.x86_64 requires python(abi) = 3.6, but this requirement cannot be provided
    Problem: python3-tqdm-4.28.1-1.1.noarch requires python(abi) = 3.6, but this requirement cannot be provided
    Problem: eric-19.01-1.3.noarch requires python(abi) = 3.7, but this requirement cannot be provided
    Problem: hplip-3.18.6-1.4.x86_64 requires python(abi) = 3.7, but this requirement cannot be provided

    Problem: python3-wxPython-4.0.1-2.3.x86_64 requires python(abi) = 3.6, but this requirement cannot be provided
    deleted providers: python3-base-3.6.5-3.3.x86_64
    Solution 1: deinstallation of python3-wxPython-4.0.1-2.3.x86_64
    Solution 2: keep obsolete python3-base-3.6.5-3.3.x86_64
    Solution 3: break python3-wxPython-4.0.1-2.3.x86_64 by ignoring some of its dependencies

    Does using Solution 1, 2 or 3 make any sense at this time? I've already passed by 3 updates. Should I lock the packages using zypper addlock, or should I just wait until all the python packages are rebuilt? Or, am I missing something?

    Thanks in advance, I've been using Tumbleweed for quite a while and never had to skip 3 updates before, and, I couldn't find solutions on the mailing list or here in the forums.

    Tom
    Hi
    So python3-wxPython has been fixed in the development repo, but not made it through to Factory... since there are delays in the next snapshot consider a manual download of the package and install....

    https://build.opensuse.org/package/s...ython-wxPython

    https://build.opensuse.org/package/s...ython-wxPython

    https://download.opensuse.org/reposi...0.1.x86_64.rpm

    Once it's fixed and published, you can switch back on a zypper dup.
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

  5. #5

    Default Re: Getting past the Python dependency problem during zypper dup

    Thank you for the quick replies.

    Both python3-wxPython and eric updates seem to have succeeded. Thanks for the links to the build service.

    hplip is still waiting for a Tumbleweed update. This might be a candidate for a hold.

    I can't find python3-tqdm on the build service, although python-tqdm is there. I'm not familiar enough with python to know if that's a replacement or not. I'm still looking.

    Thanks again. I'm almost there.

  6. #6
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    25,464
    Blog Entries
    15

    Default Re: Getting past the Python dependency problem during zypper dup

    Quote Originally Posted by GoinEasy9 View Post
    Thank you for the quick replies.

    Both python3-wxPython and eric updates seem to have succeeded. Thanks for the links to the build service.

    hplip is still waiting for a Tumbleweed update. This might be a candidate for a hold.

    I can't find python3-tqdm on the build service, although python-tqdm is there. I'm not familiar enough with python to know if that's a replacement or not. I'm still looking.

    Thanks again. I'm almost there.
    Hi
    It's there and under details, ABI 3.7
    https://build.opensuse.org/package/b...-tqdm/standard

    https://build.opensuse.org/package/b...1.2.noarch.rpm

    Likely some further dependency in the above.

    Many python packages are single spec now and build both python2 and python3 rpms at the same time, no need to maintain two packages like in the past....
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •