Very simple bug.
/var/lib/dpkg/info/tftpd-hpa.postrm try deluser 'nobody'.
Change username in /etc/default/tftpd-hpa from 'nobody' to 'foo' and repeat
install/purge.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to tftp-hpa in Ubuntu.
I managed to upgrade from Lucid to Maverick, and there didn't seem to be
a problem upgrading. Marking Fix Released.
** Changed in: server-papercuts
Status: Triaged = Fix Released
** Changed in: tftp-hpa (Ubuntu)
Status: Confirmed = Fix Released
--
package tftpd-hpa 0.43-1ubuntu2
** Changed in: server-papercuts
Milestone: maverick-alpha-3 = maverick-beta
--
package tftpd-hpa 0.43-1ubuntu2 failed to install/upgrade: subprocess new
pre-removal script returned error exit status 1
https://bugs.launchpad.net/bugs/147520
You received this bug notification because you are
This seems to be an issue with the removal of the old one, not the
installation of the new one - during the upgrade process. Adding as a
server papercut, as at the very least confirmation needs to be done if
it is fixed in the current development version, and then SRU if
applicable to a prior
same error for me when trying to update from karmic to lucid
package tftpd-hpa 0.49-1 failed to install/upgrade:
--
package tftpd-hpa 0.43-1ubuntu2 failed to install/upgrade: subprocess new
pre-removal script returned error exit status 1
https://bugs.launchpad.net/bugs/147520
You received this
** Changed in: tftp-hpa (Ubuntu)
Status: Invalid = Confirmed
--
package tftpd-hpa 0.43-1ubuntu2 failed to install/upgrade: subprocess new
pre-removal script returned error exit status 1
https://bugs.launchpad.net/bugs/147520
You received this bug notification because you are a member of
This seems to have caused my upgrade to fail as well. I set the bug to
confirmed because I just experienced it upgrading from 9.10 to 10.04.
I'll try the workaround above. See also: Bug #550064
--
package tftpd-hpa 0.43-1ubuntu2 failed to install/upgrade: subprocess new
pre-removal script
This bug report is being closed due to your last comment regarding this
being fixed with an update. For future reference you can manage the
status of your own bugs by clicking on the current status in the yellow
line and then choosing a new status in the revealed drop down box. You
can learn more
