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

Thread: Plasma Vault in 5.11.0; wrong CryFS & fusermount.

  1. #11
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    27,828
    Blog Entries
    15

    Default Re: Plasma Vault in 5.11.0; wrong CryFS & fusermount.

    On Sat 21 Oct 2017 05:36:01 PM CDT, tannington wrote:

    malcolmlewis;2842505 Wrote:
    > Hi
    > Yes, just for Tumbleweed...



    "nothing provides libcryfs-cli.so()(64bit) needed by
    cryfs-0.9.7-2.1.x86_64"

    possibly the answer lies here (last few posts)
    https://github.com/cryfs/cryfs/issues/159
    but I've only very briefly skimmed through, about to go out


    Hi
    Ahhh, so I use the OBS %cmake macro, looks like I need to drop back to
    standard cmake routine, might look at the CMakeLists a bit further....

    --
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    openSUSE Leap 42.2|GNOME 3.20.2|4.4.87-18.29-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!


  2. #12
    Join Date
    Jun 2017
    Location
    Australia
    Posts
    582

    Default Re: Plasma Vault in 5.11.0; wrong CryFS & fusermount.

    Thanks Paul & Malcolm, once again. Gosh, you blokes are awesome. Yes i would be happy to give it a go, but will hold off a bit longer in anticipation of Malcolm's next build version, heehee.

  3. #13
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    27,828
    Blog Entries
    15

    Default Re: Plasma Vault in 5.11.0; wrong CryFS & fusermount.

    Hi
    It's fixed and built now....
    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. #14
    Join Date
    Jun 2017
    Location
    Australia
    Posts
    582

    Default Re: Plasma Vault in 5.11.0; wrong CryFS & fusermount.

    Excellent, thanks. Vault now works a treat, heehee.

    [Mind you, there was initially a very rude bit of misbehaviour. Once the repo was added & i'd upgraded Fuse, then installed CryFS via your built RPM, i was adjusting my Plasma SystemTray setting to make Vault's widget visible, when plasmashell died an ugly death. Kudos though, it did a really thorough job. My Panel vanished, keyboard stopped responding [but mouse pointer still moved though clicking was dead]. Could not toggle to TTY, could not restart desktop session with Ctrl-Alt-Backspace. Only the usual REISUB method worked. Sigh. Yet again my desire to achieve Uptimes of a week or more was defeated].

    What is the correct / advised management strategy now for my newly-added-to-my-repos-list obs://build.opensuse.org/filesystems repo? At first, after getting Vault working [& recovering from the crash], i thought it best to disable this repo, so as to avoid future possible headaches during later dups. However, trying an exploratory dup then gave this unpleasant output:
    Code:
    sudo zypper -vvv dup
    [sudo] password for root: 
    Verbosity: 3
    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.
    Initialising Target
    Checking whether to refresh metadata for My_openSUSE_Repo
    Checking whether to refresh metadata for Vivaldi
    Checking whether to refresh metadata for Main Repository (NON-OSS)
    Checking whether to refresh metadata for Main Repository (OSS)
    Checking whether to refresh metadata for Main Update Repository
    Checking whether to refresh metadata for Packman Repository
    Loading repository data...
    Reading installed packages...
    Computing distribution upgrade...
    Force resolution: No
    Computing upgrade...
    
    
    Problem: problem with installed package fuse-2.9.7-80.4.x86_64
     Solution 1: install fuse-2.9.5-2.2.x86_64 (with vendor change)
      obs://build.opensuse.org/filesystems  -->  openSUSE
    
    
    Choose the above solution using '1' or cancel using 'c' [1/c] (c): c
    I re-enabled said repo, after which dup was happy... but am i setting myself up for some future headaches with this repo active? Would it be better to again disable it, then lock my Fuse version, then some time in the future when the new Fuse version lands in the standard repos, remove the lock & let dup then change it to the standard repo?

    Btw, as i write this a dup is underway in one of my test TW VMs [in which i'd tested the above methodology to get Vault working, before then doing it in Tower's real TW]. Said VM will end up at TW 20171019, & i noticed this interesting thing in the zypper verbose info at the beginning:
    Code:
    The following application is going to be REMOVED:                                                                                                                              
      Vaults    noarch                                                                                                                                                             
    
    
    The following 1033 packages are going to be upgraded:
    
    
    plasma-vault                            5.11.0-1.1 -> 5.11.1-1.1                                          x86_64  openSUSE-Tumbleweed-Oss      openSUSE
    plasma-vault-lang                       5.11.0-1.1 -> 5.11.1-1.1                                          noarch  openSUSE-Tumbleweed-Oss      openSUSE
    
    
    So even though Plasma 5.11.1 itself has not landed in TW yet, Vault does already get the upgrade.

  5. #15
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    27,828
    Blog Entries
    15

    Default Re: Plasma Vault in 5.11.0; wrong CryFS & fusermount.

    Hi
    The version I built didn't need the updated fuse, so you could use the default Tumbleweed version... I would suggest removing the repo and dup back to the defaults and see how it goes.
    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!

  6. #16
    Join Date
    Sep 2013
    Location
    Norfolk, UK
    Posts
    1,389

    Default Re: Plasma Vault in 5.11.0; wrong CryFS & fusermount.

    Quote Originally Posted by GooeyGirl View Post
    Excellent, thanks. Vault now works a treat, heehee.
    You're way ahead of me now ... just about to install Vault and take a look.

    This bug report (it's OK, nothing to panic about) https://bugs.kde.org/show_bug.cgi?id=385444 regarding deleting vaults might be worth a quick read.



    @Malcolm

    Thanks...
    Regards, Paul

    2x Tumbleweed (Snapshot: 20200211) KDE Plasma 5
    2x Leap 15.1 KDE Plasma 5

  7. #17
    Join Date
    Sep 2013
    Location
    Norfolk, UK
    Posts
    1,389

    Default Re: Plasma Vault in 5.11.0; wrong CryFS & fusermount.

    Quote Originally Posted by malcolmlewis View Post
    Hi
    The version I built didn't need the updated fuse, so you could use the default Tumbleweed version... I would suggest removing the repo and dup back to the defaults and see how it goes.
    It seems that Vault itself wants fuse 2.9.7

    http://paste.opensuse.org/view/raw/71c44519


    As an aside, is there a procedure for requesting a package (in this case cryFS) to be added to the "official" TW repositories?
    Regards, Paul

    2x Tumbleweed (Snapshot: 20200211) KDE Plasma 5
    2x Leap 15.1 KDE Plasma 5

  8. #18
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    27,828
    Blog Entries
    15

    Default Re: Plasma Vault in 5.11.0; wrong CryFS & fusermount.

    Quote Originally Posted by tannington View Post
    It seems that Vault itself wants fuse 2.9.7

    http://paste.opensuse.org/view/raw/71c44519


    As an aside, is there a procedure for requesting a package (in this case cryFS) to be added to the "official" TW repositories?
    Hi
    Ahh well that's a vault issue then....

    Yes, find a package and maintainer (no thanks ), then push to filesystems development repo and then submit to Factory.
    https://en.opensuse.org/openSUSE:Factory_submissions
    https://en.opensuse.org/openSUSE:Fac...elopment_model

    Then it will wind up in the next stable release (eg Leap 15), then you also need to maintain there as well;
    https://en.opensuse.org/openSUSEackage_maintenance
    https://en.opensuse.org/openSUSE:Mai...update_process
    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!

  9. #19
    Join Date
    Sep 2013
    Location
    Norfolk, UK
    Posts
    1,389

    Default Re: Plasma Vault in 5.11.0; wrong CryFS & fusermount.

    Quote Originally Posted by malcolmlewis View Post
    Hi
    Ahh well that's a vault issue then....
    Yes, sorry, I wasn't suggesting otherwise. (More as a comment in relation to being able to remove the "filesystems" repo).


    Yes, find a package and maintainer (no thanks ), then push to filesystems development repo and then submit to Factory.
    https://en.opensuse.org/openSUSE:Factory_submissions
    https://en.opensuse.org/openSUSE:Fac...elopment_model

    Then it will wind up in the next stable release (eg Leap 15), then you also need to maintain there as well;
    https://en.opensuse.org/openSUSEackage_maintenance
    https://en.opensuse.org/openSUSE:Mai...update_process
    Thanks for the info... Something for me to think about
    Regards, Paul

    2x Tumbleweed (Snapshot: 20200211) KDE Plasma 5
    2x Leap 15.1 KDE Plasma 5

  10. #20
    Join Date
    Jun 2017
    Location
    Australia
    Posts
    582

    Default Re: Plasma Vault in 5.11.0; wrong CryFS & fusermount.

    Quote Originally Posted by malcolmlewis View Post
    Hi
    The version I built didn't need the updated fuse, so you could use the default Tumbleweed version... I would suggest removing the repo and dup back to the defaults and see how it goes.
    No, it's not CryFS that wants that new Fuse, it's Vault. See my original post, in which i included:

    3. Clicking said <<Vault>> widget & choosing to create a new vault, leads to this next fault:
    Code:
    cryfs: Wrong version installed. The required version is 0.9.6
    fusermount: Wrong version installed. The required version is 2.9.7

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
  •