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

Thread: Packman broken?

  1. #1

    Default Packman broken?

    Having trouble doing "zypper dup" today.

    Code:
    File './Multimedia/i586/nvidia-settings-270.41.06-0.pm.1.1.i586.rpm' not found on medium 'http://packman.inode.at/suse/openSUSE_11.4/'
    Abort, retry, ignore? [a/r/i/?] (a): i
    and

    Code:
    Retrieving package python-sip-4.12.2-58.1.i586 (2/221), 48.0 KiB (102.0 KiB unpacked)
    Retrieving: python-sip-4.12.2-58.1.i586.rpm [done]
    Digest verification failed for python-sip-4.12.2-58.1.i586.rpm. Expected d60d4a5138b5cdf909fe3d16cd1cf3f8a09d679b6a554e68869215e64b101eaa, found 589097aca5511a4107bd94caf9c2f202c9c30d17d9ee2599c8b58bd8ad682b4b. Continue? [yes/no] (no): yes
    Package python-sip-4.12.2-58.1 seems to be corrupted during transfer. Do you want to retry retrieval?
    Abort, retry, ignore? [a/r/i] (a): r
    Retrieving package python-sip-4.12.2-58.1.i586 (2/221), 48.0 KiB (102.0 KiB unpacked)
    Retrieving: python-sip-4.12.2-58.1.i586.rpm [done]
    Digest verification failed for python-sip-4.12.2-58.1.i586.rpm. Expected d60d4a5138b5cdf909fe3d16cd1cf3f8a09d679b6a554e68869215e64b101eaa, found 589097aca5511a4107bd94caf9c2f202c9c30d17d9ee2599c8b58bd8ad682b4b. Continue? [yes/no] (no): yes
    Package python-sip-4.12.2-58.1 seems to be corrupted during transfer. Do you want to retry retrieval?
    Abort, retry, ignore? [a/r/i] (a): i

    Anyone else experiencing this too?

  2. #2
    Join Date
    Jun 2008
    Location
    Ardrishaig, Argyll. Scotland UK - GMT/BST
    Posts
    36,858
    Blog Entries
    20

    Default Re: Packman broken?

    These packages are nothing to do with Packman

    Please post result of

    Code:
    zypper lr -d
    Tumbleweed_KDE
    My Articles Was I any help? If yes: Click the star below

  3. #3

    Default Re: Packman broken?

    I was about to ask the same thing. packman (unixheads) fails to refresh for me.
    http://www.downforeveryoneorjustme.c....unixheads.com

  4. #4

    Default Re: Packman broken?

    True, looking closer the python package is not from Packman, but the nvidia-settings is. I noticed Packman has version 1.2 of said package available, but the 1.1 version is missing.



    Code:
    1 | KDE46                     | KDE46                        | Yes     | No      |   99     | rpm-md | Index of /MIRRORS/opensuse/repositories/KDE:/Distro:/Factory/openSUSE_11.4 |        
     2 | Nvidia                    | Nvidia                       | Yes     | No      |   99     | rpm-md | http://download.nvidia.com/opensuse/11.4/                                               |        
     3 | download.opensuse.org-oss | Main Repository (Sources)    | Yes     | No      |   99     | yast2  | Index of /source/distribution/11.4/repo/oss                         |        
     4 | google-chrome             | google-chrome                | Yes     | No      |   99     | rpm-md | http://dl.google.com/linux/chrome/rpm/stable/i386                                       |        
     5 | openSUSE-11.4-Non-Oss     | openSUSE-11.4-Non-Oss        | Yes     | No      |  120     | yast2  | Index of /distribution/11.4/repo/non-oss                            |        
     6 | openSUSE-11.4-Oss         | openSUSE-11.4-Oss            | Yes     | No      |  120     | yast2  | Index of /distribution/11.4/repo/oss                                |        
     7 | openSUSE-11.4-Update      | openSUSE-11.4-Update         | Yes     | No      |   99     | rpm-md | Index of /update/11.4                                               |        
     8 | packman.inode.at-suse     | Packman Repository           | Yes     | No      |   98     | rpm-md | Index of /suse/openSUSE_11.4/                                             |        
     9 | server:monitoring         | server:monitoring            | Yes     | No      |   99     | rpm-md | Index of /repositories/server:/monitoring/openSUSE_11.4           |        
    10 | virtualbox-11.4           | VirtualBox for openSUSE 11.4 | Yes     | No      |   99     | rpm-md | Index of /virtualbox/rpm/opensuse/11.4/

  5. #5

    Default Re: Packman broken?

    But your packman mirror is responding. Only the US site is down.

  6. #6
    Join Date
    Jun 2008
    Location
    Ardrishaig, Argyll. Scotland UK - GMT/BST
    Posts
    36,858
    Blog Entries
    20

    Default Re: Packman broken?

    Easy to switch repos and try switching refresh ON in your repos
    Packman Layout Explained
    Tumbleweed_KDE
    My Articles Was I any help? If yes: Click the star below

  7. #7

    Default Re: Packman broken?

    Yep, that's what I did.

  8. #8
    Join Date
    Feb 2010
    Location
    Upstate New York, USA
    Posts
    487

    Default Re: Packman broken?

    Quote Originally Posted by caf4926 View Post
    Easy to switch repos and try switching refresh ON in your repos
    Packman Layout Explained
    As mentioned earlier, only the US site is down. The base domain, Unixheads, stuff that matters, reports that the mirror server is down, however, last updated message was from 12.05.2011.

    Switching to the Austria/Germany repositories, followed by a refesh, resolves the problem. The access problem is exacerbated by the inability to "Skip Autorefresh" in YAST. It appears that DNS resolution is NOT handled by a server in Sweden, resulting in a very long "timeout" (twice) to terminate YAST and switch repositories.
    Lap: Gateway NV79, i5-430, 4GB, 2 x 500GB HD, Intel GMA HD
    openSUSE Leap 15.2 x64 + Ubuntu 18.04 LTS, Windows 7

    Test:: openSUSE 15.3, KDE Plasma, Windows/XP/SP3 guest.

  9. #9

    Default Re: Packman broken?

    What do you mean by inability to "Skip Autorefresh"? If autorefresh is disabled for some repos, YaST won't try to access them. I have been doing security updates yesterday and today on several machines without changing the packman mirror - because autorefresh was off for this repo.

  10. #10
    Join Date
    Feb 2010
    Location
    Upstate New York, USA
    Posts
    487

    Default Re: Packman broken?

    Quote Originally Posted by please_try_again View Post
    What do you mean by inability to "Skip Autorefresh"? If autorefresh is disabled for some repos, YaST won't try to access them. I have been doing security updates yesterday and today on several machines without changing the packman mirror - because autorefresh was off for this repo.
    Learning something here !

    All my repositories are (now were) set to Autorefresh. When I checked for updates, YAST sat, then timed out on Packman. <sigh>

    Thanks for the assist!
    Lap: Gateway NV79, i5-430, 4GB, 2 x 500GB HD, Intel GMA HD
    openSUSE Leap 15.2 x64 + Ubuntu 18.04 LTS, Windows 7

    Test:: openSUSE 15.3, KDE Plasma, Windows/XP/SP3 guest.

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
  •