Page 1 of 2 12 LastLast
Results 1 to 10 of 13

Thread: Update of python failed, not sure what to do

  1. #1

    Default Update of python failed, not sure what to do

    Updating system, and the following error occurred, not sure what to do: I tried the retry option, but same issue.
    Any help appreciated!

    thanks!
    JOhn KIbert

    Code:
    ..>cut
    
    (  1/155) Installing: xine-ui-0.99.9-51.3.x86_64 .......................................................................................................................................[done]
    Additional rpm output:
    Unknown media type in type 'all/all'
    Unknown media type in type 'all/allfiles'
    
    
    (  2/155) Installing: handbrake-cli-1.0.7-1.7.x86_64 ...................................................................................................................................[done]
    (  3/155) Installing: handbrake-gtk-1.0.7-1.7.x86_64 ...................................................................................................................................[done]
    (  4/155) Installing: handbrake-gtk-lang-1.0.7-1.7.noarch ..............................................................................................................................[done]
    (  5/155) Installing: libreoffice-branding-upstream-5.3.2.1-1.3.noarch .................................................................................................................[done]
    (  6/155) Installing: libreoffice-icon-theme-galaxy-5.3.2.1-1.3.noarch .................................................................................................................[done]
    (  7/155) Installing: linux-glibc-devel-4.10-1.1.noarch ................................................................................................................................[done]
    (  8/155) Installing: python-rpm-macros-1.0.git.1490791775.6e5b01c-1.1.noarch ..........................................................................................................[done]
    (  9/155) Installing: python3-idna-2.5-1.1.noarch ......................................................................................................................................[done]
    ( 10/155) Installing: python3-nose-1.3.7-5.1.noarch ....................................................................................................................................[done]
    Additional rpm output:
    update-alternatives: error: alternative link /usr/share/man/man1/nosetests.1.gz is already managed by nosetests.1 (slave of nosetests)
    warning: %post(python3-nose-1.3.7-5.1.noarch) scriptlet failed, exit status 2
    
    ....... cut>
    
    
    
    ( 75/155) Installing: kernel-default-4.10.9-1.5.x86_64 .................................................................................................................................[done]
    Additional rpm output:
    Creating initrd: /boot/initrd-4.10.9-1-default
    dracut: Executing: /usr/bin/dracut --logfile /var/log/YaST2/mkinitrd.log --force /boot/initrd-4.10.9-1-default 4.10.9-1-default
    dracut: dracut module 'systemd-bootchart' will not be installed, because command '/usr/lib/systemd/systemd-bootchart' could not be found!
    dracut: *** Including module: bash ***
    dracut: *** Including module: systemd ***
    dracut: *** Including module: warpclock ***
    dracut: *** Including module: systemd-initrd ***
    dracut: *** Including module: i18n ***
    dracut: *** Including module: drm ***
    dracut: *** Including module: plymouth ***
    dracut: *** Including module: kernel-modules ***
    dracut: *** Including module: resume ***
    dracut: *** Including module: rootfs-block ***
    dracut: *** Including module: terminfo ***
    dracut: *** Including module: udev-rules ***
    dracut: Skipping udev rule: 40-redhat.rules
    dracut: Skipping udev rule: 50-firmware.rules
    dracut: Skipping udev rule: 50-udev.rules
    dracut: Skipping udev rule: 91-permissions.rules
    
    
    ( 76/155) Installing: python3-tornado-4.4.2-1.3.x86_64 ................................................................................................................................[error]
    Installation of python3-tornado-4.4.2-1.3.x86_64 failed:
    Error: Subprocess failed. Error: RPM failed: error: unpacking of archive failed on file /usr/lib64/python3.6/site-packages/tornado-4.4.2-py3.6.egg-info: cpio: rename
    error: python3-tornado-4.4.2-1.3.x86_64: install failed
    error: python3-tornado-4.4.2-1.2.x86_64: erase skipped

  2. #2

    Default Re: Update of python failed, not sure what to do

    Have the same problem. Also tried to abort, reboot and then do a "zypper dup" again. Ended up with the same error.

  3. #3

    Default Re: Update of python failed, not sure what to do

    I would up accidentally aborting by trying to copy/paste (ctrl C oops)the whole terminal window into notepad. I am really just hoping a bootable system right now.

  4. #4
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    25,261

    Default Re: Update of python failed, not sure what to do

    Cutting part of the output also removed the command used. Now we have only the vague description: Updating system, ....

    BTW, when you have large output (to large for posting here), there is http://paste.opensuse.org
    Henk van Velden

  5. #5
    Join Date
    Jun 2008
    Location
    San Diego, Ca, USA
    Posts
    11,382
    Blog Entries
    2

    Default Re: Update of python failed, not sure what to do

    Errors:
    xine-ui
    Likely problems with MIME types. If xine isn't critical to what you do, you can wait for the next update which <may> fix the problem, else explore the many solutions posted on the Internet which generally involve removing and replacing definitions.

    broken update-alternatives link for a MAN page
    Unless you intend to look up that MAN page, you can probably ignore it for now

    broken pyton3-nose scriptlet
    Unless you do something dependent on that scriptlet, you can probably ignore for now

    Python3-tornado
    Do you already have it installed and is being updated? I assume your existing installed version should be running fine (Python3 tornado is a python webserver). Keep an eye out if anything seems broken using a python webserver, else you can ignore for now (but maybe report to bugzilla, this seems to be the biggest of the errors you posted because the entire package couldn't be unpacked).

    I assume that all these errors are re-producible and my impression is that they shouldn't happened due to some unique setup, so they should already be noticed, but you can still submit formal bugs for any or all of them if you wish at https://bugzilla.opensuse.org

    IMO,
    TSU
    Beginner Wiki Quickstart - https://en.opensuse.org/User:Tsu2/Quickstart_Wiki
    Solved a problem recently? Create a wiki page for future personal reference!
    Learn something new?
    Attended a computing event?
    Post and Share!

  6. #6

    Default Re: Update of python failed, not sure what to do

    The cutoff command was zypper dup --no-allow-vendor-change

    Here is the exact output :

    http://paste.opensuse.org/66333728

    Another odd thing the just occurred to me is the accepting of the key: it never seems permanent.

    thanks

  7. #7
    Join Date
    Jun 2008
    Location
    San Diego, Ca, USA
    Posts
    11,382
    Blog Entries
    2

    Default Re: Update of python failed, not sure what to do

    Quote Originally Posted by kilbert View Post
    The cutoff command was zypper dup --no-allow-vendor-change

    Here is the exact output :

    http://paste.opensuse.org/66333728

    Another odd thing the just occurred to me is the accepting of the key: it never seems permanent.

    thanks
    Why are you specifying "no-allow-vendor-change" ?
    Especially in a rolling release, applications might be introduced with one vendor version, then when considered stable moved to OSS (or similar development path).

    Try running a "zypper dup" without any flags unless you have a specific reason to completely block <all> vendor changes.
    If you have a specific application that you want to never change, you can install a block to blacklist that app from changing.

    TSU
    Beginner Wiki Quickstart - https://en.opensuse.org/User:Tsu2/Quickstart_Wiki
    Solved a problem recently? Create a wiki page for future personal reference!
    Learn something new?
    Attended a computing event?
    Post and Share!

  8. #8
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    25,261

    Default Re: Update of python failed, not sure what to do

    Quote Originally Posted by tsu2 View Post
    Why are you specifying "no-allow-vendor-change" ?
    Because that is the recommended way to keep Tumbleweed up to date here on the forums in many threads.
    Henk van Velden

  9. #9
    Join Date
    Jun 2008
    Location
    San Diego, Ca, USA
    Posts
    11,382
    Blog Entries
    2

    Default Re: Update of python failed, not sure what to do

    Quote Originally Posted by hcvv View Post
    Because that is the recommended way to keep Tumbleweed up to date here on the forums in many threads.
    OK,
    After thinking about that a bit,
    I can see how that might help stabilize by declining bleeding edge versions in favor of what is in the OSS.

    Although I don't rely on TW to do most of my work,
    I haven't yet run into a problem by accepting all updates, but it's inarguably a riskier policy (knock on wood).

    TSU
    Beginner Wiki Quickstart - https://en.opensuse.org/User:Tsu2/Quickstart_Wiki
    Solved a problem recently? Create a wiki page for future personal reference!
    Learn something new?
    Attended a computing event?
    Post and Share!

  10. #10

    Default Re: Update of python failed, not sure what to do

    The main (and actually only) problem is this:
    Quote Originally Posted by kilbert View Post
    Code:
    Installation of python3-tornado-4.4.2-1.3.x86_64 failed:
    Error: Subprocess failed. Error: RPM failed: error: unpacking of archive failed on file /usr/lib64/python3.6/site-packages/tornado-4.4.2-py3.6.egg-info: cpio: rename
    For some reason, rpm cannot create the corresponging file ( /usr/lib64/python3.6/site-packages/tornado-4.4.2-py3.6.egg-info ) on your hard disk.

    There may be several reasons for this...
    But one particular possible cause is that this was installed as symlink before and is now an actual file.

    To circumvent this problem, uninstall the original package and then reinstall the new one:
    Code:
    sudo rpm -e --nodeps python3-tornado
    sudo zypper in python3-tornado
    (the --nodeps is only necessary if another package requires it)

    Or just delete the offending "file" before updating, the update will of course recreate it anyway.

    If this is an official package, you may want to consider filing a bug report in that case.

Page 1 of 2 12 LastLast

Posting Permissions

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