[Bug 1179065] Re: Update to 6.25
** Changed in: nmap (Debian) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nmap in Ubuntu. https://bugs.launchpad.net/bugs/1179065 Title: Update to 6.25 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nmap/+bug/1179065/+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
[Bug 1095757] Re: Please update krb5 to new upstream release =1.10.2
** Changed in: krb5 (Debian) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1095757 Title: Please update krb5 to new upstream release =1.10.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1095757/+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
[Bug 998918] Re: openvpn openssl.cnf file missing
I spent a little time debugging this. I don't think it is a matter of a missing config file. When you 'source vars', one of the things that happens is this: # This variable should point to # the openssl.cnf file included # with easy-rsa. export KEY_CONFIG=`$EASY_RSA/whichopensslcnf $EASY_RSA` If you look at whichopensslcnf, you see that the first section includes logic for determining the correct config file to used based on the OpenSSL version installed on the system. On my system (12.04 lts), 'openssl version' produces the following output: # openssl version OpenSSL 1.0.1 14 Mar 2012 Which, presumably, should generate a match in this code in whichopensslcnf: elif $OPENSSL version | grep -E 1\.0\.([[:digit:]][[:alnum:]]) /dev/null; then cnf=$1/openssl-1.0.0.cnf else cnf=$1/openssl.cnf fi Instead it is falling through to the default value (tested by running the grep command on its own) , which results in the output noted by others above. One workaround is to symlink openssl.cnf to the appropriate config file mentioned above. The solution is to fix the pattern matching... -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvpn in Ubuntu. https://bugs.launchpad.net/bugs/998918 Title: openvpn openssl.cnf file missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvpn/+bug/998918/+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
[Bug 1083719] Re: open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build
** Branch linked: lp:~n-muench/ubuntu/precise/open-vm-tools/open-vm- tools.raring-precise.backport -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to open-vm-tools in Ubuntu. https://bugs.launchpad.net/bugs/1083719 Title: open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1083719/+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
[Bug 1083719] Re: open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build
I've started work on the Raring backport. It should give support through 3.7 (3.8 with the patches). There's still stuff to downgrade back to what it looked like for Precise -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to open-vm-tools in Ubuntu. https://bugs.launchpad.net/bugs/1083719 Title: open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1083719/+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
[Bug 1134036] Re: Failure when using ssh with a locale that is not configured on the server
No, I never saw this sort of message at all. I concur with falling back to a C locale though, because as it stands package installation of Postgres just *hangs*. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1134036 Title: Failure when using ssh with a locale that is not configured on the server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1134036/+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
[Bug 1184457] [NEW] Stores user configuration outside of $XDG_CONFIG_HOME
Public bug reported: Juju stores user configuration in ~/.juju. Ideally this would be stored alongside the rest of the user-local configuration, in $XDG_CONFIG_HOME/juju (this will almost always be $HOME/.config/juju). I've not yet checked whether juju stores any cache data in ~/.juju; if it does, that would ideally be in $XDG_CACHE_HOME. Using the XDG basedir spec directories makes it easier to determine what files are precious and what may be discarded, and so is useful for backup programs or users poking around trying to do manual backups or the like. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: juju-core 1.10.0.1-0ubuntu1~ubuntu13.04.1 Uname: Linux 3.7.10-linode49 i686 ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 Date: Mon May 27 01:11:37 2013 Dependencies: MarkForUpload: True SourcePackage: juju-core UpgradeStatus: Upgraded to raring on 2013-02-28 (87 days ago) ** Affects: juju-core (Ubuntu) Importance: Wishlist Status: New ** Tags: apport-bug i386 raring -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1184457 Title: Stores user configuration outside of $XDG_CONFIG_HOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1184457/+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
[Bug 1182980] Re: global parameters do not apply to enlistment
** Changed in: maas Status: Triaged = In Progress ** Changed in: maas Assignee: (unassigned) = Julian Edwards (julian-edwards) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1182980 Title: global parameters do not apply to enlistment To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1182980/+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
[Bug 1182980] Re: global parameters do not apply to enlistment
** Branch linked: lp:~julian-edwards/maas/enlistment-kernel-params -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1182980 Title: global parameters do not apply to enlistment To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1182980/+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
