[tahoe-lafs-trac-stream] [Tahoe-LAFS] #3856: sFTP integration test failures

[Tahoe-LAFS]

#3856: sFTP integration test failures
----------------------------------------+-----------------------
     Reporter:  meejah                  |      Owner:  itamarst
         Type:  defect                  |     Status:  closed
     Priority:  major                   |  Milestone:  undecided
    Component:  code-frontend-ftp-sftp  |    Version:  n/a
   Resolution:  fixed                   |   Keywords:
Launchpad Bug:                          |
----------------------------------------+-----------------------
Changes (by exarkun):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 For reference, the fix landed via https://github.com/tahoe-lafs/tahoe-
 lafs/pull/1169 in https://github.com/tahoe-lafs/tahoe-
 lafs/commit/4cdbf7fb0cb1a462f4edf6ed93a74dc6f4df0499

 To the question of whether this ticket should be open or closed: one
 ticket, one PR.

 As you say, the problem is solved: the SFTP integration tests no longer
 fail because of this Paramiko regression.  I don't even know that removing
 the pin is sensible after Paramiko fixes the issue.  The most obvious
 thing that does is open us up to future regressions.

 Maybe we want to revisit the pin in a month or a year or something and
 move it to a newer version if there is some interesting reason to do so.
 The same probably applies to all of our dependencies.  Do we want to track
 that work with a ticket or some other way?  A ticket sounds kind of nice
 but I'm not convinced it would actually remind anyone to do anything in,
 say, six months.  More likely it will just get lost in the pile.

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/3856#comment:5>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage