Did you re-export the backup after applying the patch?
IIRC it fixes the backup/export phase not the restore/import phase so
unless you re-created the dumps it wouldn't have actually done anything.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Public bug reported:
Hi,
I've just performed an upgrade of our LDAP server on Ubuntu 10.04.4 LTS
to Ubuntu 12.04 (I acknowledge this upgrade path is not officially
supported yet).
The incompatible database upgrading process in the preinst/postinst
files failed in the following scenario.
We
(If requested I can provide a suitable debdiff for the proposed fix)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/1003854
Title:
Database upgrade/migration fails with nested db
I'd like to double check this again before confirming hardy PAM is ok
with usernames of this length but unfortunately I seem to have
lost/deleted the test VM where I had this issue setup.
I'll re-create the VM and re-test this issue just to be sure (give me a
couple of days or so depending on
** Description changed:
vsftpd has a max username length of 32, this is too small for a virtual
hosting environment where the username is a user's e-mail address (if
they have a long domain name etc...)
This issue was patched in FC10 via their patch system and has been
pulled into
Just spotted a slight error in my debdiff. I made my debdiff against
2.0.6-1ubuntu1, failing to notice the -ubuntu1.1 in hardy-updates.
I'll submit an updated patch/debdiff later today against -ubuntu1.1 if
someone else doesn't do so before hand.
TESTING NOTE: Please note that although the
This bug is more than likely a duplicate of: #209447
Can the OP or Chris provide echo $SSH_AUTH_SOCK so we can confirm gnome-
keyring-daemon is infact being used?
--
ssh-agent does not expire key
https://bugs.launchpad.net/bugs/252200
You received this bug notification because you are a member
*** This bug is a duplicate of bug 209447 ***
https://bugs.launchpad.net/bugs/209447
That's certainly gnome-keyring's socket.
I'm going to go ahead mark this bug a duplicate, for a work around
please see bug: #209447.
The work around involves resetting your ssh-agent back to the standard
