Bug 243845 - [NEW PORT] mail/py-imapclient: Pythonic and complete IMAP client library
Summary: [NEW PORT] mail/py-imapclient: Pythonic and complete IMAP client library
Status: Closed DUPLICATE of bug 250806
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-ports-bugs (Nobody)
URL:
Keywords: feature, needs-qa
Depends on:
Blocks: 243847 243844
  Show dependency tree / graph
 
Reported: 2020-02-03 13:28 UTC by ml
Modified: 2021-04-08 14:50 UTC (History)
2 users (show)

See Also:

Attachments
SHAR archive (2.05 KB, text/plain)
2020-02-03 13:28 UTC, ml 		no flags Details
py-imapclient.diff (2.61 KB, patch)
2020-07-07 12:26 UTC, Li-Wen Hsu 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description ml 2020-02-03 13:28:03 UTC 
Created attachment 211318 [details]
SHAR archive

Easy-to-use, Pythonic and complete IMAP client library.

WWW: https://github.com/mjs/imapclient
Comment 1 Li-Wen Hsu freebsd_committer freebsd_triage 2020-07-07 12:26:01 UTC 
Created attachment 216286 [details]
py-imapclient.diff

I've updated the patch for some cleanups and making the (case of the) name consistency. Can you check it?
Comment 2 ml 2020-07-13 07:48:18 UTC 
Very fine for me.

However #243844 and #243847 should be updated consequently.
Those are currently broken, though, until upstream solves some compatibility problem, which arrived meanwhile.
Comment 3 Li-Wen Hsu freebsd_committer freebsd_triage 2020-07-13 13:42:21 UTC 
(In reply to ml from comment #2)
If renaming is the only issue, I can take care when detailing with bug 243844 and bug 243847.  However, do you mean that test two ports cannot run correctly at the moment?  If so, we have better to wait until the issues have been solved.
Comment 4 ml 2020-07-13 14:14:50 UTC 
Exactly: they worked ATM when I submitted them; however things have changed in the meanwhile (both upstream and in our port tree, with newer version of dependencies) and I'm waiting for upstream to solve a couple of incompatibilities before I can upgrade my ports.

If you want to rename imapclient in their dependencies in the meantime, feel free and go ahead.

Thanks.
Comment 5 ml 2021-01-05 19:24:31 UTC 
#243844 should be ok now.
While that should solve #243847, other compatibility issues arose in the meantime for that port.
Comment 6 ml 2021-04-08 14:50:02 UTC 

*** This bug has been marked as a duplicate of bug 250806 ***