[Bug 795336] [NEW] dovecot-postfix always overwrites main.cf

2011-06-09 Thread Tim White
Public bug reported: Binary package hint: dovecot-postfix Every upgrade of dovecot-postfix overwrites the main.cf postfix configuration file removing some of the users customisations. It is expected on initial install for this to occur (although a warning even then would be good), however

[Bug 795336] Re: dovecot-postfix always overwrites main.cf

2011-06-09 Thread Tim White
-- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dovecot in Ubuntu. https://bugs.launchpad.net/bugs/795336 Title: dovecot-postfix always overwrites main.cf To manage notifications about this bug go to:

[Bug 715056] Re: invalid ssl-certificates in /etc/postfix/main.cf after security upgrade

2011-06-10 Thread Tim White
Lucid-proposed works great. Thanks for the quick bugfix. How soon before we'll see it in Lucid-updates? Thanks -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dovecot in Ubuntu. https://bugs.launchpad.net/bugs/715056 Title: invalid

[Bug 663672] [NEW] won't mount NFS mounts with space in the name

2010-10-19 Thread Tim White
Public bug reported: Binary package hint: autofs5 Using the auto.net file to mount NFS mounts on the local network. One of the machines (a NAS) has a number of similarly named exports with spaces in the name. autonfs appears to only see the name upto the first space. The awk script in

[Bug 663672] Re: won't mount NFS mounts with space in the name

2010-10-20 Thread Tim White
From my poking around, it appears the bug will be in both this package, and nfs-common. showmount's output doesn't allow for parsing as it uses spaces to separate the fields (exportname and the ipaddress of who can mount it). Ideally it needs to use a : between the fields not whitespace. If

[Bug 663672] Re: won't mount NFS mounts with space in the name

2010-10-21 Thread Tim White
apport information ** Tags added: apport-collected ** Description changed: Binary package hint: autofs5 Using the auto.net file to mount NFS mounts on the local network. One of the machines (a NAS) has a number of similarly named exports with spaces in the name. autonfs appears to

[Bug 663672] Re: won't mount NFS mounts with space in the name

2010-10-21 Thread Tim White
/etc/auto.master ** Attachment added: auto.master https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/663672/+attachment/1705842/+files/auto.master -- won't mount NFS mounts with space in the name https://bugs.launchpad.net/bugs/663672 You received this bug notification because you are a

[Bug 663672] Re: won't mount NFS mounts with space in the name

2010-10-21 Thread Tim White
Original auto.net that is packaged with ubuntu. This file fails when NFS share has spaces in them. ** Attachment added: auto.net.original https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/663672/+attachment/1705843/+files/auto.net.original -- won't mount NFS mounts with space in the

[Bug 663672] Re: won't mount NFS mounts with space in the name

2010-10-21 Thread Tim White
A workaround (certainly not a solution) is to put a grep -v in the pipeline between the SHOWMOUNT and the awk that prints it in the expected format for autofs. Using this, I was able to filter out the 3 mounts with spaces in them so that I can continue using autofs. A proper solution appears to be