*** This bug is a duplicate of bug 545790 ***
https://bugs.launchpad.net/bugs/545790
** This bug is no longer a duplicate of bug 545738
package PACKAGE failed to install/upgrade: error writing to 'standard
output': No such file or directory
** This bug has been marked a duplicate of bug
*** This bug is a duplicate of bug 545738 ***
https://bugs.launchpad.net/bugs/545738
** This bug has been marked a duplicate of bug 545738
package PACKAGE failed to install/upgrade: error writing to 'standard
output': No such file or directory
--
package gcc-4.4-base 4.4.1-4ubuntu6
not a gcc error
** Package changed: gcc-4.4 (Ubuntu) = ubuntu
--
package gcc-4.4-base 4.4.1-4ubuntu6 failed to install/upgrade: error writing to
'standard output': No such file or directory
https://bugs.launchpad.net/bugs/442193
You received this bug notification because you are a member of
** Attachment added: AptOrdering.txt
http://launchpadlibrarian.net/32975375/AptOrdering.txt
** Attachment added: Dmesg.txt
http://launchpadlibrarian.net/32975376/Dmesg.txt
** Attachment added: DpkgTerminalLog.txt
http://launchpadlibrarian.net/32975377/DpkgTerminalLog.txt
--
package
What I did to avoid this, was to go to synaptic and from the down left
corner I chose the option Status and then broken packages. I updated
them and and I anew started the updated process from the icon in the
toolbar.
The next step was to have a new bug for python this time. I closed the
update
