[SM-Grimoire-Bugs] [Bug 15291] New: upgrading from old libusb to libusb + libusb-compat fails

bugzilla-daemon at bugs.sourcemage.org bugzilla-daemon at bugs.sourcemage.org
Sun Jul 12 07:50:06 EDT 2009


http://bugs.sourcemage.org/show_bug.cgi?id=15291

           Summary: upgrading from old libusb to libusb + libusb-compat
                    fails
           Product: Codex
           Version: stable-rc grimoire
          Platform: x86
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P3
         Component: libs
        AssignedTo: sm-grimoire-bugs at lists.ibiblio.org
        ReportedBy: wich at sourcemage.org



Remko van der Vossen <wich at sourcemage.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
               Flag|                            |must_fix_before_release+


The old version of libusb provided libusb-0.1.so.4, the new version provides
libusb-1.0.so.0, with libusb-compat providing libusb-0.1.so.4. The problem here
is that gnupg optionally depends on libusb, linking to libusb-0.1.so.4.

The sequence of events is:

@ libusb-0.1.so.4 exists
@ all ok
> cast libusb
- libusb and libusb-compat are queued
- libusb is cast successfully
@ libusb-0.1.so.4 has been removed, libusb-1.0.so.0 is installed
@ gpg binary now fails
- libusb-compat is cast
- hash verification of libusb-compat is initiated
- hash verification fails, since gpg fails

Obviously the cast now gives an error message that the has can not be verified
and prompts whether to abort. Aborting however will lead any subsequent hash
verifications to fail for any spell.

What would be a good way to resolve this?

-- 
Configure bugmail: http://bugs.sourcemage.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the SM-Grimoire-Bugs mailing list