Public bug reported:
Binary package hint: emacs23
If you are in a source repository, emacs loads the version control
package for that repository in batch mode. The problem can be
reproduced as follows:
# Create an empty directory.
$ mkdir tmp
$ cd tmp
# Verify there is no
** Changed in: dovecot (Ubuntu)
Status: New = Invalid
--
hostname -f prevents dovecot installation
https://bugs.launchpad.net/bugs/583821
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dovecot in ubuntu.
--
Ubuntu-server-bugs
** Changed in: dovecot (Ubuntu)
Status: New = Invalid
--
hostname -f prevents dovecot installation
https://bugs.launchpad.net/bugs/583821
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
After further review, I don't think the problem is dovecot. It is
either libc6-xen or my hosting provider's kernel.
--
hostname -f prevents dovecot installation
https://bugs.launchpad.net/bugs/583821
You received this bug notification because you are a member of Ubuntu
Server Team, which is
After further review, I don't think the problem is dovecot. It is
either libc6-xen or my hosting provider's kernel.
--
hostname -f prevents dovecot installation
https://bugs.launchpad.net/bugs/583821
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Public bug reported:
In dovecot-common-1:1.2.9-1ubuntu6 (lucid), the postinst script for
dovecot-common calls hostname -f which fails if the computer has a
FQDN of the form example.com (instead of foo.example.com). This
prevents dovecot from installing. The workaround I used was to manually
Public bug reported:
In dovecot-common-1:1.2.9-1ubuntu6 (lucid), the postinst script for
dovecot-common calls hostname -f which fails if the computer has a
FQDN of the form example.com (instead of foo.example.com). This
prevents dovecot from installing. The workaround I used was to manually
Public bug reported:
Binary package hint: metacity
When upgrading to metacity-1.2.30.1-0ubuntu1, the new package installs
without error but metacity does not run when you start X because it
cannot find workspace names using gconf. To trigger this bug, create
more than 16 workspaces before
