Robie, your response to the others was unhelpful. This is NOT a "local configuration problem", but rather an endemic problem with mythbuntu. Based on info on the Internet regarding past releases, this appears to be a result of mythbuntu's configuration making changes to smb.conf, which results in the update failing. It happens on ALL mythbuntu systems with SMB - so it is not unique to the other repoters' systems. It would be more helpful for the Ubuntu folks and the mythbuntu folks to put their heads together and find out what causes this on ALL mythbuntu systems with SMB when they try to upgrade. In the meantime, the workaround seems to be to not include samba in the GUI driven automatic update process, and the update it using "apt-get upgrade", though I have not yet tried that. See http://ubuntuforums.org/showthread.php?t=1881553 .
-- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1185250 Title: package samba 2:3.6.3-2ubuntu2.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1185250/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
