[Errno 104] Connection reset by peer when uploading orig.tar.gz
For the last month or so I have been getting
[Errno 104] Connection reset by peer
errors when while dput is uploading the *.orig.tar.gz file.
Here is the terminal output from the last time I tried it:
epier@epier2:
Checking signature on .changes
gpg: Signature made Thu 10 Jan 2019 09:20:47 AM HST using RSA key ID 36984E33
gpg: Good signature from "Edward Pier <email address hidden>"
Good signature on /home/epier/
Checking signature on .dsc
gpg: Signature made Thu 10 Jan 2019 09:20:47 AM HST using RSA key ID 36984E33
gpg: Good signature from "Edward Pier <email address hidden>"
Good signature on /home/epier/
Package includes an .orig.tar.gz file although the debian revision suggests
that it might not be required. Multiple uploads of the .orig.tar.gz may be
rejected by the upload queue management software.
Uploading to ppa (via ftp to ppa.launchpad.net):
Uploading vipa_2.
Uploading vipa_2.
The last time it worked was on 2018-11-29. Here is the terminal output then:
Checking signature on .changes
Good signature on /home/epier/
Checking signature on .dsc
Good signature on /home/epier/
Package includes an .orig.tar.gz file although the debian revision suggests
that it might not be required. Multiple uploads of the .orig.tar.gz may be
rejected by the upload queue management software.
Uploading to ppa (via ftp to ppa.launchpad.net):
Uploading vipa_2.
Uploading vipa_2.
Uploading vipa_2.
Uploading vipa_2.
Successfully uploaded packages.
I get the error every time I do a dput upload. Nothing changed in my code or in my upload procedures on 11/30 the day it stopped working.
Let me know if there is any more information I can give you to help resolve this.
Question information
- Language:
- English Edit question
- Status:
- Expired
- Assignee:
- No assignee Edit question
- Last query:
- Last reply: