Page 2 of 3 FirstFirst 123 LastLast
Results 11 to 20 of 26

Thread: Update issue, LMMS related

  1. #11

    Default Re: Update issue, LMMS related

    Quote Originally Posted by hcvv View Post
    And why repo #6 and #9?

    I also wonder what the real difference is between #7 and #8.
    I have no idea, should I remove some ?

  2. #12
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    27,359

    Default Re: Update issue, LMMS related

    Quote Originally Posted by Gps2010 View Post
    I hope I will remember this, but I typed what the post above that one suggested.

    I probably cant edit the post any-more ?
    I know that most probably you did in this case what was asked for. But we see often enough that people do not copy/paste the command from the thread into the terminal but then type it, making errors. And then others can wonder what happened.

    Also, you first post here started with output without informing about what was done. No idea what you did to get it, except the vague "Update issue".


    And I guess it is not that difficult to remember that you ask for help and thus should provide much information about what you are doing and getting. Others want to see the same things you saw. Not only the part you think is important.

    And no, you can not edit the post anymore. This is to prevent confusing threads. And my remark is for the future as well as in this thread as in others.
    Henk van Velden

  3. #13
    Join Date
    Mar 2011
    Location
    Sauerland
    Posts
    5,015

    Default AW: Re: AW: Update issue, LMMS related

    Quote Originally Posted by Gps2010 View Post
    Thank you, but then what ?

    Reinstall LMMS ?

    Not using LMMS is not an option for me.

    Although I could stop using the version from openSUSE, and use the appimage version instead.
    lmms is in the OSS-Repo:
    https://software.opensuse.org/package/lmms

    Maybe you have to install it once more even also the lmms-vst

    You uppade only with zypper dup?
    Last edited by Sauerland; 24-Sep-2020 at 09:46.

  4. #14

    Default Re: Update issue, LMMS related

    Quote Originally Posted by hcvv View Post
    I know that most probably you did in this case what was asked for. But we see often enough that people do not copy/paste the command from the thread into the terminal but then type it, making errors. And then others can wonder what happened.

    Also, you first post here started with output without informing about what was done. No idea what you did to get it, except the vague "Update issue".


    And I guess it is not that difficult to remember that you ask for help and thus should provide much information about what you are doing and getting. Others want to see the same things you saw. Not only the part you think is important.

    And no, you can not edit the post anymore. This is to prevent confusing threads. And my remark is for the future as well as in this thread as in others.
    Well I remember , it was: zypper dup

  5. #15

    Default Re: AW: Re: AW: Update issue, LMMS related

    Quote Originally Posted by Sauerland View Post
    lmms is in the OSS-Repo:
    https://software.opensuse.org/package/lmms

    Maybe you have to install it once more even also the lmms-vst

    You upgrade only with zypper dup?
    Yes since a month or so, before I once allowed verdor change, then was told I should not have done this ( zypper dup allow vendor change)

    Yes, I have LMMS and LMMS vst installed.


    When you do pick LMMS-vst in YAST, you get the LMMS without vst too. Don't look at me I am not the package maintainer.
    Something about, I hope I recall this right, unnecessary wine dependencies.

    LMMS it self does not need wine, but the vst module it has does.


    Maybe I need to clear some things, when it comes to LMMS I am a bit of an expert.
    Been using it for years now, because most package builders from any Distro, mess it up. ( They don't know that for vst to work with LMMS you need wine )
    This is also why the LMMS devs, tired of all the issues on there forum, made an appimage file.

    I am a member of the LMMS forum too, and kinda of the Linux support guy. That how I know that about every distro package maintainer messes it up.
    LMMS users asking why Vestige in LMMS is not working.


    Because of this I have been trying to compile it myself, but when it comes to LMMS, this is far from simple.

    Then there is Carla, and that's how I ended up talking to our LMMS / Carla package maintainer.
    His name can be seen in my repository list. I helped by testing Carla and LMMS.


    Back to my problem. I will try the option suggested by zypper of removing lmms.
    If it then finishes the update I will try to reinstall LMMS after this.

    If that fails, I will talk to the package maintainer.



    A bit off topic, the music in this vid is made with LMMS. I made both the vid and the music track. ( Blender for the vid, LMMS for the Music)

    https://www.youtube.com/watch?v=RSzceg_jTS0

    Now you will understand why not using LMMS is not an option for me. I can also go back to using the appimage file though.
    When the LMMS dev release a new appimage file, I am the one testing it on openSUSE.
    With LMMS you can make music on your pc. ( like how allot of today hits in the charts are made )

    I will report back.

  6. #16

    Default Re: Update issue, LMMS related

    Code:
    guus@linux-2ls4:~> sudo zypper dup 
    [sudo] password for root: 
    Retrieving repository 'packman' metadata ................................................................................................................................................................................................[done]
    Building repository 'packman' cache .....................................................................................................................................................................................................[done]
    Loading repository data...
    Reading installed packages...
    Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command.
    Computing distribution upgrade...
    
    Problem: libvkd3d1-32bit-1.2-1.1.x86_64 requires libvkd3d-shader.so.1, but this requirement cannot be provided
      not installable providers: libvkd3d-shader1-1.2-1.1.i586[http-download.opensuse.org-3de67a27]
                       libvkd3d-shader1-1.2-1.1.i586[http-download.opensuse.org-9c129f69]
                       libvkd3d-shader1-1.2-1.1.i586[openSUSE_20191112-0]
     Solution 1: Following actions will be done:
      deinstallation of libvkd3d1-32bit-1.1-2.1.x86_64
      deinstallation of wine-mono-5.1.0-2.2.noarch
      deinstallation of lmms-vst-1.2.2-151.11.x86_64
     Solution 2: install libvkd3d-shader1-1.2-1.1.i586 despite the inferior architecture
     Solution 3: keep obsolete libvkd3d1-32bit-1.1-2.1.x86_64
     Solution 4: break libvkd3d1-32bit-1.2-1.1.x86_64 by ignoring some of its dependencies
    
    Choose from above solutions by number or cancel [1/2/3/4/c/d/?] (c): 1
    
    Resolving dependencies...
    Computing distribution upgrade...
    2 Problems:
    Problem: wine-32bit-5.17-1.2.x86_64 requires libvkd3d.so.1, but this requirement cannot be provided
    Problem: wine-32bit-5.17-1.2.x86_64 requires libvkd3d.so.1, but this requirement cannot be provided
    
    Problem: wine-32bit-5.17-1.2.x86_64 requires libvkd3d.so.1, but this requirement cannot be provided
      deleted providers: libvkd3d1-32bit-1.1-2.1.x86_64
    not installable providers: libvkd3d1-1.2-1.1.i586[http-download.opensuse.org-3de67a27]
                       libvkd3d1-32bit-1.2-1.1.x86_64[http-download.opensuse.org-3de67a27]
                       libvkd3d1-1.2-1.1.i586[http-download.opensuse.org-9c129f69]
                       libvkd3d1-32bit-1.2-1.1.x86_64[http-download.opensuse.org-9c129f69]
                       libvkd3d1-1.2-1.1.i586[openSUSE_20191112-0]
                       libvkd3d1-32bit-1.2-1.1.x86_64[openSUSE_20191112-0]
     Solution 1: deinstallation of wine-32bit-5.17-1.2.x86_64
     Solution 2: install libvkd3d1-1.2-1.1.i586 despite the inferior architecture
     Solution 3: keep libvkd3d1-32bit-1.1-2.1.x86_64
     Solution 4: break wine-32bit-5.17-1.2.x86_64 by ignoring some of its dependencies
    
    Choose from above solutions by number or skip, retry or cancel [1/2/3/4/s/r/c/d/?] (c):
    I think its time to talk to our package builder?

  7. #17

    Default Re: Update issue, LMMS related

    I am starting to wonder, if the person , who tried to hi jack my topic , maybe does have the same problem.

    It also seem to complain about a not full filled dependency of wine.

  8. #18

    Default Re: Update issue, LMMS related

    I have been looking in YAST, this does seem to confirm why zypper is not happy, but it also confuses me.

    When I search for libvkd3d.so.1, yast finds nothing.
    When I however check the box , RPM requires in YAST, wine pops up.

    Gonna contact the LMMS maintainer.

  9. #19
    Join Date
    Jul 2020
    Posts
    6

    Default Re: Update issue, LMMS related

    Hello,

    It would appear I share the same basic problem.
    I'm not using LMMS, but I am using wine to run some games and the latest Tumbleweed updates are giving me the same basic problem with zypper being unable to work out the dependencies.

    I don't know if I'm doing something wrong or if it's a packaging problem or bug so I've started a thread here asking for advice:
    https://forums.opensuse.org/showthre...not-be-provide

    I'm going to hold off from changing things for the time being.

  10. #20

    Default Re: Update issue, LMMS related

    After I uninstall lmms I still have the same zypper dup problem, I use zypper dup --no-allow-vendor-change but the problem still occurs with plain zypper dup. It appears as if the problem lies with the libvkd3d1-32bit rpm not having a libvkd3d-shader1-32bit package available. This is most probably caused by an error in that packages baselibs.conf which facilitates the creation of the 32bit libraries. I'll have a look later on

Page 2 of 3 FirstFirst 123 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
  •