Results 1 to 6 of 6

Thread: Cockpit experimental package seems broken

  1. #1

    Default Cockpit experimental package seems broken

    Please bare with me. I'm a long time Slackware ( 2002 ) user and more recently ( past 5 years ) have been mostly using FreeBSD at work with Mac as a desktop. I'm giving SUSE a try as an at home server, mostly for support of some newer sys admin technologies ( snappy and cockpit ), while also keeping rock solid stability I'm used to, hopefully.

    I'm running openSUSE Leap 15

    I'm currently trying to install cockpit experimental package - https://software.opensuse.org/package/cockpit
    I can into an issue while using the one click installer. There was a warning:

    "nothing provides storaged >= 2.1.1 needed by cockpit-storaged-0.79-1.284.noarch"

    Conflict resolution gives me two options which I suspect will fail due to the nature of the software - don't install, don't install cockpit-storaged.

    Through some research I found that storaged is now named udisks, as of 2.6.4. On the github, under the legacy branch, there is a link in the readme to tarball releases, the earliest one being the last one named storaged. Too good to be true, this did not resolve the error.

    Through a little deeper dive, I found that users of CentOS had an identical issue, udisks being available and/or installed, but the package requiring - erroneously - storaged. https://github.com/cockpit-project/cockpit/issues/9159 https://github.com/cockpit-project/c...595bebf728ee8c

    I'm hoping this is a similar case for openSUSE as my experience with the OS so far has been positive.

    Where might I find something similar in the YaST package system where I might be able to tell the package to use udrives instead of the old name of storaged? I'm not very familiar with packaging systems in Slackware, RedHat/CentOS, or SUSE.

    [edit]
    As I pressed the submit button I noticed the links I posted were titled CentOS but were for the official package itself. I'm hoping this is the right place for this.

  2. #2
    Join Date
    Jun 2008
    Location
    San Diego, Ca, USA
    Posts
    10,942
    Blog Entries
    2

    Default Re: Cockpit experimental package seems broken

    First FYI I posted the methods I use to find a missing file, library, etc in this other Forum thread
    https://forums.opensuse.org/showthre...08#post2868808

    Also,
    Package names may be varied and have no relationship to whether a dependency is filled...
    It's the individual files within the package that are important, and you can list a package's contents with the following
    Code:
    rpm -ql packagename 
    If a file name is <still> not what is required but you know or want to test whether the file might fill a need using a different name, then the next step is to create a symlink in a specific location (and name) pointing to the file that should fill the need.

    HTH,
    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!

  3. #3
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    26,524
    Blog Entries
    15

    Default Re: Cockpit experimental package seems broken

    Hi
    Since it's not built for Leap 15, I'm guessing your 1-click installed the factory version which is not compatible and failing too, plus it's a way out of date version (un-maintained project perhaps).
    https://build.opensuse.org/package/s...ockpit/cockpit

    The latest cockpit release is 169...
    https://github.com/cockpit-project/cockpit/releases
    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!

  4. #4
    Join Date
    Nov 2013
    Location
    Kamloops, BC, Canada
    Posts
    3,974

    Default Re: Cockpit experimental package seems broken

    Quote Originally Posted by WrinkledCheese View Post
    Please bare with me.
    ... uh, no. I do not skinny dip with strangers.
    -Gerry Makaro
    Fraser-Bell Info Tech
    Solving Tech Mysteries since the Olden Days!
    ~~
    If I helped you, consider clicking the Star at the bottom left of my post.

  5. #5

    Default Re: Cockpit experimental package seems broken

    Quote Originally Posted by Fraser_Bell View Post
    ... uh, no. I do not skinny dip with strangers.
    We'll just have to have a drink first.

    I resorted to my Slackware roots and installed from GitHub, manually resolving dependencies, using yast and npm where applicable. Now I just have to figure out how to run the thing. Their docs rely completely on: "there's a package for these distros, use those."

    Actually the docs look pretty good. There's just no "here's an out of the box solution not using one of these other distros"

  6. #6
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    26,524
    Blog Entries
    15

    Default Re: Cockpit experimental package seems broken

    On Thu 14 Jun 2018 10:16:03 PM CDT, WrinkledCheese wrote:

    Fraser_Bell;2869587 Wrote:
    > ... uh, no. I do not skinny dip with *strangers*.


    We'll just have to have a drink first.

    I resorted to my Slackware roots and installed from GitHub, manually
    resolving dependencies, using yast and npm where applicable. Now I just
    have to figure out how to run the thing. Their docs rely completely on:
    "there's a package for these distros, use those."


    Hi
    There is a lot....!!! have a look at the spec file for all the
    details....
    https://build.opensuse.org/package/v....spec?expand=1

    --
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SLES 15 | GNOME Shell 3.26.2 | 4.12.14-23-default
    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
  •