*** This bug is a duplicate of bug 69051 ***
** This bug has been marked a duplicate of bug 69051
Debconf not updating gui when ucf is used and detect a conffile-change
--
Strange upgrade behaviour from Dapper to Edgy
https://launchpad.net/bugs/67133
--
ubuntu-bugs mailing list
ubuntu-bugs@
this from a duplicate:
"Other packages are able to show their diff in update-manager correctly
without using the terminal. This should be changed in nfs-kernel-server
as well."
so it might be nfs-utils which needs fixing, after all.
--
Strange upgrade behaviour from Dapper to Edgy
https://launc
hardly nfs-utils's fault
** Changed in: nfs-utils (Ubuntu)
Sourcepackagename: nfs-utils => update-manager
--
Strange upgrade behaviour from Dapper to Edgy
https://launchpad.net/bugs/67133
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-
As Philipp wrote in his comment:
https://bugs.launchpad.net/distros/ubuntu/+source/nfs-
utils/+bug/67133/comments/1
** Changed in: nfs-utils (Ubuntu)
Status: Unconfirmed => Confirmed
--
Strange upgrade behaviour from Dapper to Edgy
https://launchpad.net/bugs/67133
--
ubuntu-bugs mailin
Please note... after killing the particular debconf step, the upgrade
continued to my surprise (but I ran into other errors which I will
report separately).
--
Strange upgrade behaviour from Dapper to Edgy
https://launchpad.net/bugs/67133
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Attachment added: "dist-upgrade_term.log"
http://librarian.launchpad.net/4938502/term.log
--
Strange upgrade behaviour from Dapper to Edgy
https://launchpad.net/bugs/67133
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I'm attaching the dist-upgrade log file, as advised in the error
message.
** Attachment added: "dist-upgrade_main.log"
http://librarian.launchpad.net/4938501/main.log
--
Strange upgrade behaviour from Dapper to Edgy
https://launchpad.net/bugs/67133
--
ubuntu-bugs mailing list
ubuntu-bugs@li
I can confirm this issue. I was thrown completely off track here. I
didn't guess that I had to press 'q' at all. Also, when I clicked on the
terminal widget (to look at the differences) and then clicked on the
'Modified configuration file dialog' again, the rendering of that dialog
became quirky (n
