I think this has been indirectly fixed when we added proper syncing of the updates directory. dpkg deals correctly with no disk space. An update file only appears after having been written to in a temporary file and renamed. Thus you should never see the #padding in an update file.
Thus marking as fix released. If it persists, it means a filesystem bug more than a dpkg bug.
I think this has been indirectly fixed when we added proper syncing of the updates directory. dpkg deals correctly with no disk space. An update file only appears after having been written to in a temporary file and renamed. Thus you should never see the #padding in an update file.
Thus marking as fix released. If it persists, it means a filesystem bug more than a dpkg bug.