Bug 454953 - imapsync doesn't work with current perl-mail-imapclient
imapsync doesn't work with current perl-mail-imapclient
Status: CLOSED NEXTRELEASE
Product: Fedora
Classification: Fedora
Component: imapsync (Show other bugs)
9
All Linux
low Severity medium
: ---
: ---
Assigned To: Marek Mahut
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-07-10 21:00 EDT by Lev Novikov
Modified: 2008-09-10 03:15 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-09-10 03:15:48 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Lev Novikov 2008-07-10 21:00:37 EDT
Description of problem:
imapsync doesn't work with current perl-mail-imapclient

Version-Release number of selected component (if applicable):
imapsync-1.252-2 (and 1.255)
perl-Mail-IMAPClient-3.05-1

Steps to Reproduce:
1. yum install imapsync
2. run imapsync (without any parameters)
  
Actual results:

Subroutine Authuser redefined at /usr/bin/imapsync line 2564.
imapsync needs perl lib Mail::IMAPClient release 2.2.9 exactly, future imapsync
release may suppoort 3.0.x, but sorry not now. See file BUG_IMAPClient_3.xx


Additional info:
when i build from source.rpm and install old version of perl-Mail-IMAPClient (2.2.9)
imapsync run correctly without any problem
Comment 1 Pavel Alexeev 2008-07-13 20:38:49 EDT
In my spec (it in my repository http://hubbitus.net.ru/rpm/Fedora8/imapsync/
with additional patches) I just using:
BuildRequires:>perl(Mail::IMAPClient) < 2.99
Requires:><--->perl(Mail::IMAPClient) < 2.99
Comment 2 Pavel Alexeev 2008-07-13 20:40:07 EDT
Excuse me (I can not edit comment?):

BuildRequires: perl(Mail::IMAPClient) < 2.99
Requires:      perl(Mail::IMAPClient) < 2.99
Comment 3 Lubomir Rintel 2008-08-08 05:09:55 EDT
Actually, imapsync works with Mail::IMAPClient >= 3, there are just two known bugs (see BUG_IMAPClient_3.xx), albeit quite serious (at least the ssl one:)

BUGS found with Mail-IMAPClient-3.05/

1) --ssl* bugs. 

   30 timeout.

2) --expunge2 does not expunge anything.

Nevertheless, I've changed the code to fall back to override the Authuser function only with older IMAPClients, so permanent errors are hopefully gone. I've done no testing at all, so I'll appreciate any feedback. Thanks!
Comment 4 Lubomir Rintel 2008-08-08 05:11:26 EDT
fc10 build is here [1], please let me know if you need package for f9 as well, unless you are able rebuild it yourself:

[1] http://koji.fedoraproject.org/koji/buildinfo?buildID=58990
Comment 5 Rick Richardson 2008-08-11 10:49:57 EDT
$ gmail-backup 
Subroutine Authuser redefined at /usr/bin/imapsync line 2557.
imapsync needs perl lib Mail::IMAPClient release 2.2.9 exactly, future imapsync release may suppoort 3.0.x, but sorry not now. See file BUG_IMAPClient_3.xx
# Looks like your test died before it could output anything.

Latest update from fc9.
Comment 6 Lubomir Rintel 2008-08-11 13:18:26 EDT
Rick: Try the package from comment #4 and please report if it works for you.
Comment 7 Lev Novikov 2008-08-12 10:41:10 EDT
Package from comment #4 works for me
Comment 8 Lubomir Rintel 2008-08-15 04:51:44 EDT
Lev: Thanks for the feedback.

The package had been commited into Fedora 9 branch, but the build is pending the resolution of some infrastructure trouble now.

I'd appreciate if anyone else that can test here tried the new package from comment #4 so we can check how severe are the known bugs of this release before we push it.

Thanks!
Comment 9 Fedora Update System 2008-08-24 10:56:18 EDT
imapsync-1.255-3.fc9 has been submitted as an update for Fedora 9.
http://admin.fedoraproject.org/updates/imapsync-1.255-3.fc9
Comment 10 Fedora Update System 2008-09-10 03:15:45 EDT
imapsync-1.255-3.fc9 has been pushed to the Fedora 9 stable repository.  If problems still persist, please make note of it in this bug report.

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