Bug 466602 - recent changes to libusb break pilot-link syncing
Summary: recent changes to libusb break pilot-link syncing
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: libusb
Version: 10
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jindrich Novy
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-10-11 04:50 UTC by James Ralston
Modified: 2013-07-02 23:32 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-12-18 06:33:18 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description James Ralston 2008-10-11 04:50:32 UTC
Bug 456811 contains a suggested patch to libusb. The libusb maintainer included the patch in libusb-0.1.12-17.

Unfortunately, this patch completely breaks pilot-link's ability to sync with at least Palm TX devices, and possibly other devices.

For now, I've asked the libusb maintainer to revert the patch.

Could you please ask the upstream pilot-link developers to inspect the patch in bug 456811?  Specifically: does upstream think the patch bogus?  Or is pilot-link using libusb incorrectly, and the patch breaks pilot-link's incorrect behavior? Or some combination of both?

Versions of pilot-link that the patch in bug 456811 breaks:

pilot-link-0.12.3-14
pilot-link-0.12.3-18

Comment 1 Bug Zapper 2008-11-26 03:46:43 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle.
Changing version to '10'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 2 Ivana Varekova 2009-04-20 10:02:27 UTC
Hello, the patch could be reviewed by libusb guys - they should be the best persons who are relevant to check this code. I'm reassignig this bug to jnovy.

Comment 3 Bug Zapper 2009-11-18 08:33:43 UTC
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '10'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 10's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 10 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 4 Bug Zapper 2009-12-18 06:33:18 UTC
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.