um... but lucid is still in LTS, and this problem is still present
there. It doesn't particularly matter to me whether this bug exists in
precise, especially since if there is no mysql-cluster package in
precise, I won't be deploying precise for this application.
What is the appropriate way for
Public bug reported:
The mysql-cluster-client-5.1 package (part of mysql-cluster-7.0), at
least the Lucid release, is missing some packaging metadata. The
package contains the libmysqlclient16 shared library:
# dpkg -L mysql-cluster-client-5.1 | grep libmysqlclient
** Branch linked: lp:~shuff/ubuntu/lucid/mysql-cluster-7.0/fix-
for-929779
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/929779
Title:
mysql-cluster-client-5.1 package should provide
*** This bug is a duplicate of bug 660379 ***
https://bugs.launchpad.net/bugs/660379
** This bug has been marked a duplicate of bug 660379
Make mysql-cluster depend on libmysqlclient16 from mysql-5.1 (rather than
conflict)
--
You received this bug notification because you are a member
** Branch linked: lp:~shuff/ubuntu/precise/net-snmp/fix-for-701944
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to net-snmp in Ubuntu.
https://bugs.launchpad.net/bugs/701944
Title:
snmpd postinst fails if user cannot be deleted
To
** Branch linked: lp:~shuff/ubuntu/precise/net-snmp/fix-for-701944
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/701944
Title:
snmpd postinst fails if user cannot be deleted
To manage
asac: This bug still affects 8.04.4 LTS systems, on which the current
version of git-core is 1.5.4.3-1ubuntu2.1. That version of git is old
enough that it does *not* link against libcurl, but rather calls the
curl executable from a shell script, and thus it seems to me that the
git-core package
another confirmed fix in lucid (non-EC2) for 1.5.8-2ubuntu2.3, on a
system that had previously exhibited the issue.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to facter in Ubuntu.
https://bugs.launchpad.net/bugs/885998
Title:
another confirmed fix in lucid (non-EC2) for 1.5.8-2ubuntu2.3, on a
system that had previously exhibited the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/885998
Title:
facter upgrade
I can confirm that rolling back to facter_1.5.6-2ubuntu2 resolves the
issue on 10.04 LTS.
I'm using puppet 2.6.1-0ubuntu2 from the lucid-backports repo.
In addition, I see the following traceback using facter_1.5.6-2ubuntu2.2
when running `facter --debug`:
# facter --debug
I can confirm that rolling back to facter_1.5.6-2ubuntu2 resolves the
issue on 10.04 LTS.
I'm using puppet 2.6.1-0ubuntu2 from the lucid-backports repo.
In addition, I see the following traceback using facter_1.5.6-2ubuntu2.2
when running `facter --debug`:
# facter --debug
11 matches
Mail list logo
