FTP Transport doesn't implement put_*_non_atomic
Bug #75422 reported by
John A Meinel
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Confirmed
|
Wishlist
|
Unassigned | ||
Breezy |
Won't Fix
|
Wishlist
|
Unassigned |
Bug Description
The FTP transport doesn't implement put_*_non_atomic, which means that push over ftp is slower than it needs to be. (It requires an additional rename for each file)
Also, it means it creates temporary files, which have longer path names. Which *might* be causing problems on Windows where there is a limited amount of path space available by default.
Related branches
lp:~jelmer/brz/no-more-ftp
- Vincent Ladeuil: Approve
- Martin Packman: Approve
-
Diff: 1510 lines (+17/-1308)16 files modifiedbreezy/help_topics/en/authentication.txt (+3/-3)
breezy/lockdir.py (+0/-3)
breezy/plugins/git/tests/test_dir.py (+1/-1)
breezy/plugins/upload/__init__.py (+1/-1)
breezy/plugins/upload/tests/test_upload.py (+1/-25)
breezy/tests/__init__.py (+0/-6)
breezy/tests/blackbox/test_help.py (+0/-2)
breezy/tests/ftp_server/__init__.py (+0/-82)
breezy/tests/ftp_server/pyftpdlib_based.py (+0/-223)
breezy/tests/test_ftp_transport.py (+0/-151)
breezy/tests/test_http.py (+2/-2)
breezy/tests/test_smart_transport.py (+1/-1)
breezy/tests/transport_util.py (+8/-19)
breezy/transport/__init__.py (+0/-23)
breezy/transport/ftp/__init__.py (+0/-638)
breezy/transport/ftp/_gssapi.py (+0/-128)
Changed in bzr: | |
importance: | Undecided → Wishlist |
status: | Unconfirmed → Confirmed |
tags: | added: check-for-breezy |
Changed in brz: | |
status: | New → Triaged |
importance: | Undecided → Wishlist |
tags: |
added: ftp removed: check-for-breezy |
Changed in brz: | |
status: | Triaged → Fix Released |
milestone: | none → 3.0.0 |
status: | Fix Released → Won't Fix |
To post a comment you must log in.