Description of problem: I can't make hubic run on Mageia6 (or with the mono version available on Mageia6). hubic is an executable that allow the synchronization between Hubic/OVH servers and a local directory. It is started the following : exec mono <full path to the local hubic dir>/hubiC.exe main-loop Version-Release number of selected component (if applicable): Mageia6 Mono 4.2.4 How reproducible: Always in Mageia6. It was working fine in Mageia5, at least till the beginning of July. I don't know if an update of some package could have broken this software before I've updated everything to Mageia6 Steps to Reproduce: As root : 1) Get the file hubiC-Linux-2.1.0.53-linux.tar.gz and uncompress it (https://hubic.com/fr/telechargements). 2) make install 3) dbus-launch --csh-syntax (or --sh-syntax) 4) setenv DBUS_SESSION_BUS_ADDRESS 'unix:abstract=/tmp/dbus-mYr656STqn,guid=681d6a4c2306df38e8b5915359aad300' 5) set DBUS_SESSION_BUS_PID=21346 Steps 3), 4) and 5) were not necessary in Mageia5 (or they were done automatically at boot). I couldn't make it work the same way in Mageia6. Normal user : 6) hubic main-loop & You need an Hubic account to be able to do the next step : 7) hubic login <username> <Path to your directory to be synchronized> Password [Error] Timeout. Command failed: System.InvalidOperationException: Cannot log in. This is the same issue as described here : https://forums.linuxmint.com/viewtopic.php?f=63&t=249567&sid=929cf6944bddc3851050337e2f98cd1f and they solved it by installing a ca-certificates-mono package. This package seems available only to Debian and Ubuntu people. Is it possible to get this package as well ? I'm not sure this will solve the issue but we need to try. The workaround is to do the synchronization manually, using the (bad) web interface (or probably using Windows). Regards. Xuo.
Assigning to all packagers collectively, like any package request. We obsoleted ca-certificates, because we use rootcerts nowadays, I don't know what that means, if anything, for ca-certificates-mono. Even if there's no objection against packaging ca-certificates-mono, then it'll still need to be packaged for cauldron, first, after which a backport request can be made to make it available for Mga6.
CC: (none) => jani.valimaa, marja11Severity: minor => enhancementVersion: 6 => CauldronSource RPM: (none) => ca-certificates-mono
Assignee: bugsquad => pkg-bugs
CA certificates are handled very differently in Debian than the RedHat family, and ca-certificates from Fedora is not the same as what you're talking about here. Packaging something from Debian isn't the solution. It may be that a configuration in your software needs to be adapted for RedHat-type distros.
Status: NEW => RESOLVEDResolution: (none) => INVALID