Bug 77914
| Summary: | On load: No available connection provider, plugins probably missing | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Need Real Name <morten> |
| Component: | tora | Assignee: | Mihai Ibanescu <mihai.ibanescu> |
| Status: | CLOSED RAWHIDE | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 8.0 | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2002-12-03 13:11:13 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Need Real Name
2002-11-15 09:01:01 UTC
up2date can only be trusted if you are using packages built from Red Hat source RPMs. That way, the files are put in the proper place and can be updated properly. This bug may need to go to up2date, since up2date should check to see if the Packager of the currently installed package is indeed a Red Hat package. If it isn't, the user can opt to force an upgrade or to ignore the upgrade altogether. No an up2date issue. I get the exact same problem if I install the official RPM from scratch. Please note that 1.2.4 < 1.2.6.1, this is the reason why up2date offered to upgrade the package. If you want up2date to ignore the newer (but not Oracle-enabled) tora, you may add tora to up2date's skiplist. I am not exactly sure I understand the bug report. Was tora-1.3.6.1 working before, you installed 1.2.4, then you re-installed 1.3.6.1 and it doesn't work anymore? 1.3.6.1 never worked for me and always gives the same error message (see summary). The outcome is the same, regardless if I upgrade from 1.2.4 or install on a 'clean' machine. 1.2.4 from globecom works nicely. Okay, I'll try to schedule some time to work on the tora package this week.tora works like a charm on my machine (but it's a custom build for 7.3). Here's the fix: Install qt-ODBC and/or qt-PostgreSQL qt-MySQL; make sure you remove .tora* in your home directory (they seem to be versioned, or at least that's what I think). Then you'll start seeing the mysql and postgresql connection providers. I would be really grateful if you downloaded the newer tora 1.3.8 rpms from: ftp://people.redhat.com/misa/fixes/tora and run those instead, since I'm trying to test the packaging on this one. I've updated the package's description too. It installed nicely, but failed to execute: [oracle@dellbert oracle]$ tora tora: relocation error: tora: undefined symbol: static_QUType_varptr Yupp, my bad. Can you please try it now? Please make sure you rpm -e tora before attempting to install the 3.8.0 packages. Thanks a lot. I installed ftp://people.redhat.com/misa/fixes/tora/tora-1.3.8-3.8.0.i386.rpm but I still get the same (original) error: "No available connection provider, plugins probably missing" Have you run: rm -rf ~/.tora* and installed qt-ODBC, qt-PostgreSQL and qt-MySQL? I forgot to remove .tora* (duh!). Works fine now. Yeah, not sure why those files are versioned and have to be changed - makes upgrades a PITA. If that's okay with you, I'm going to close this bug as RAWHIDE - there is a fix available out there. |