HI Jazz! Thanks for taking the time to file this bug report.
I notice the paths in your errors say /usr/lib/php5/20090626+lfs
The official packages do not have the '+lfs' in them. Is it possible you
have a leftover config file (probably /etc/php5/conf.d/pdo_pgsql.ini)
that has the wrong path in i
Looks like autofs needs to do 'stop on deconfiguring-networking'. That
will ensure that the main process is completely stopped before the
network is shutdown. I wonder if we should also consider raising the
'kill timeout' above 5 seconds, as it may take longer than that to
unmount a lot of mounts,
JazZ, this is extremely confusing.
Can you install php5-cli and run 'php -i | grep extension_dir' ?
On my 12.04 system, it shows:
extension_dir => /usr/lib/php5/20090626 => /usr/lib/php5/20090626
If that shows the same, can you place a file in your webroot with the
content 'https://bugs.launchp
Excerpts from JazZ's message of Sat May 05 16:10:33 UTC 2012:
> When i do 'php -i | grep extension_dir', I got:
>
> PHP Warning: PHP Startup: Unable to load dynamic library
> '/usr/lib/php5/20090626+lfs/pdo_mysql.so' -
> /usr/lib/php5/20090626+lfs/pdo_mysql.so: undefined symbol: pdo_parse_para
Excerpts from Ondřej Surý's message of Sat May 05 18:40:58 UTC 2012:
> Clint,
>
> +lfs is arch dependent.
OOH! Thanks, will note that for the future. :)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in Ubuntu.
https://b
Public bug reported:
The template lxc-ubuntu-cloud uses ubuntu-cloudimg-query, which is in
the cloud-utils package. So, lxc should depend on cloud-utils.
** Affects: lxc (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ub
Blueprint changed by Clint Byrum:
Whiteboard changed:
Discussion Topics:
What issues lead to the packages being removed from precise?
How do we ensure that these don't re-occur to ensure the long term viability
of chef as part of Ubuntu?
+ - Maintaining chef in Debian will help
We need to fix this in precise and quantal. It should arrive via the
merge from Debian in quantal, but we'll need to get the fix (thanks for
the debdiff!) included in 12.04 as well.
** Changed in: ntp (Ubuntu)
Status: New => Triaged
** Changed in: ntp (Ubuntu)
Importance: Undecided => H
Excerpts from Daniel Hahler's message of Tue May 15 08:53:06 UTC 2012:
> For what it's worth, this does not happen with the squid-deb-proxy
> package (which uses squid with an optimized config) - at least after
> several boot processes.
>
> The init/start script is different, for example, it uses
** Description changed:
+ == SRU Justifcation ==
+
+ === Impact ===
+ This bug can cause juju's local provider to fill up the local disk very
rapidly after a reboot.
+
+ === Test Case ===
+ 1. Create a local environment in ~/.juju/environments.yaml, something like
this:
+
+ environments:
+
** Changed in: juju (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
https://bugs.launchpad.net/bugs/958312
Title:
Change zk logging configuration
To manage notification
** Changed in: juju
Importance: Undecided => High
** Also affects: juju (Ubuntu)
Importance: Undecided
Status: New
** Also affects: juju (Ubuntu Precise)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team
** Description changed:
+ == SRU Justification ==
+
+ === Impact ===
+ Charms written in shell, which is the bulk of charms, cannot make use of the
output of this command. Also charms written using the documentation as a guide
will not work because the docs say it works this way.
+
+ === Test
** Description changed:
+ == SRU Justification ==
+
+ === Impact ===
+
+ This causes some charms to have to add complex output control logic for
+ calling juju-log.
+
+ === Test Case ===
+
+ 1. juju bootstrap
+ 2. juju deploy --repository /usr/share/doc/juju/examples local:mysql
+ 3. juju debu
Public bug reported:
Pretty sure this was just EC2 returning something unexpected. This was
while talking to us-west-2. Repeating the same operation immediately
afterward produced no errors.
$ juju terminate-machine 28
2012-05-16 17:36:14,878 INFO Connecting to environment...
2012-05-16 17:36:15,
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to txaws in Ubuntu.
https://bugs.launchpad.net/bugs/1000504
Title:
KeyError raised when txaws encountered unexpected code
To manage notifications about this bug go to:
https://bugs.launchp
Blueprint changed by Clint Byrum:
Work items set to:
Work items:
Author and communicate proposed release plan to juju mailing list: TODO
(Placeholder) Implement testing plan after discussion: TODO
(Placeholder) Implement release plan after discussion: TODO
(Placeholder) Verify Launchpad can
Blueprint changed by Clint Byrum:
Definition Status: Discussion => Drafting
--
Clarifying Charm Store policy around Ubuntu Releases
https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-juju-charms-release-policy
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.
Blueprint changed by Clint Byrum:
Whiteboard set to:
python two more milestones before maint:
galapagos we'll try the process above
honolulu
What are the options for 12.10 release to allow the go and juju ports to coexist
v2.0.0 go port
use alternatives?
use completely separate namespace?
Blueprint changed by Clint Byrum:
Work items set to:
Work items:
implement this versioning scheme in go juju: TODO
create spec to allow charms to depend on juju versions: TODO
juju to warn on invalid metadata: TODO
--
Juju Formal Release Process
https://blueprints.launchpad.net/ubuntu/+spec
Blueprint changed by Clint Byrum:
Whiteboard set to:
Glance has supported ceph as a a backend storage for the past couple of
releases of openstack. We should make it as easy as possible for users
to use ceph with glance. This could be an alternative for users who do
not want to setup for a full
Blueprint changed by Clint Byrum:
Work items changed:
Work items:
- [clint-fewbar] Maintainer idea was almost universally accepted: TODO
[negronjl] Promulgate should run "charm proof": TODO
- [clint-fewbar] update charm tools to support maintainer : TODO
- [clint-fewbar] assign main
Blueprint changed by Clint Byrum:
Definition Status: Discussion => Obsolete
--
Juju upstart integration
https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-juju-upstart-integration
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings
Blueprint changed by Clint Byrum:
Work items changed:
Work items:
- [clint-fewbar] Maintainer idea was almost universally accepted: TODO
- [clint-fewbar] update charm tools to support maintainer : TODO
- [clint-fewbar] assign maintainers to existing charms, everyone who committed
to the charm
Hi mcguire.
Which release of Ubuntu do the updated packages solve the problem on for
you? There are fixes available for natty, oneiric, and precise.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libnss-ldap in Ubuntu.
https:
** Changed in: emacs23 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pep8 in Ubuntu.
https://bugs.launchpad.net/bugs/741381
Title:
pep8 crashes, integrated with emacs when in python-mode
To m
Hello ShaolinTiger, or anyone else affected,
Accepted munin into precise-proposed. The package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in adva
Hello Malcolm, or anyone else affected,
Accepted munin into precise-proposed. The package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** Tags added: verification-done verification-done-precise
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libnss-ldap in Ubuntu.
https://bugs.launchpad.net/bugs/423252
Title:
NSS using LDAP+SSL breaks setuid applications like su, su
** Also affects: txaws
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to txaws in Ubuntu.
https://bugs.launchpad.net/bugs/1000504
Title:
KeyError raised when txaws encountered unexpected code
Blueprint changed by Clint Byrum:
Work items changed:
Work items:
implement this versioning scheme in go juju: TODO
create spec to allow charms to depend on juju versions: TODO
+ implement charm versioning in python: TODO
+ implement charm versioning in go: TODO
juju to warn on invalid
Blueprint changed by Clint Byrum:
Definition Status: Discussion => Review
--
Juju Formal Release Process
https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-juju-release-process
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscr
1.1 just landed in quantal with this fix, closing bug as Fix Released.
** Changed in: pep8 (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pep8 in Ubuntu.
https://bugs.launchpad.net/bugs/
** Also affects: juju (Ubuntu)
Importance: Undecided
Status: New
** Changed in: juju (Ubuntu)
Status: New => Triaged
** Changed in: juju (Ubuntu)
Importance: Undecided => Medium
** Also affects: juju (Ubuntu Precise)
Importance: Undecided
Status: New
** Description
** Description changed:
- juju-origin in environments.yaml needs to accept 'distro-proposed', or
- environments.yaml needs to accept some other option that will allow
- directing juju to install the version of juju from the -proposed pocket.
+ [Impact]
+ Users will not be able to test any proposed
The EC2 provider verifies all certs now if ssl-hostname-verification:
true is in the environment configuration.
** Changed in: juju (Ubuntu Precise)
Status: In Progress => Fix Released
** Changed in: juju (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notifi
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to munin in Ubuntu.
https://bugs.launchpad.net/bugs/598385
Title:
[SRU] munin plugin exim_mailqueue has incorrect grap
This was in fact fixed quite a while ago during the precise dev cycle.
** Changed in: juju (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: juju (Ubuntu Precise)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ub
Excerpts from James Page's message of 2012-05-24 13:56:30 UTC:
> I think this bug warrants some attention as I just triage a load more
> from 12.04.
>
> I would propose changing the upstart configuration of nmbd:
>
> NMBD_DISABLED=`testparm -s --parameter-name='disable netbios'
> 2>/dev/null ||
Hello Stéphane, or anyone else affected,
Accepted lxc into precise-proposed. The package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
Hello Andrey, or anyone else affected,
Accepted lxc into precise-proposed. The package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
**
Hello Robert, or anyone else affected,
Accepted lxc into precise-proposed. The package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
**
Hello martin, or anyone else affected,
Accepted mcollective into precise-proposed. The package will build now
and be available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in adva
Hello Jean-Baptiste, or anyone else affected,
Accepted lxc into precise-proposed. The package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advan
Hello Gary, or anyone else affected,
Accepted lxc into precise-proposed. The package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** T
Setting Importance to Medium. 5 year old bug that has only one reporter,
so the scope of the impact seems fairly limited.
** Changed in: keepalived (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribe
*** This bug is a duplicate of bug 958312 ***
https://bugs.launchpad.net/bugs/958312
Hi Victor.
There is an SRU in precise-proposed that fixes this. bug #958312
Could you follow the directions in the comments of that bug to enable
proposed, and then verify that it is fixed for you? Marking t
Hi xcitchx. It looks like bind is giving errors during its startup. Can
you look in /var/log/syslog for any errors from 'named' or 'bind'? You
might also want to try just running the daemon to see if it prints
anything out.
** Changed in: bind9 (Ubuntu)
Status: New => Incomplete
** Changed
*** This bug is a duplicate of bug 545790 ***
https://bugs.launchpad.net/bugs/545790
ErrorMessage: error writing "": Success
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
SourcePackage: krb5
Title: package libgssrpc4 1.10 + dfsg ~ beta1-2ubuntu0.1 failed to insta
alex, this is somewhat surprising to hear, as up until 12.04, NIS was
actually quite broken on bootup for most users due to many race
conditions in the way it started up. In 12.04, the startup was moved to
being managed by upstart jobs, and this fixed the problem for many users
(in fact we have upd
*** This bug is a duplicate of bug 545790 ***
https://bugs.launchpad.net/bugs/545790
** This bug has been marked a duplicate of bug 545790
package PACKAGE failed to install/upgrade: error writing to '': Success
--
You received this bug notification because you are a member of Ubuntu
Serve
*** This bug is a duplicate of bug 545790 ***
https://bugs.launchpad.net/bugs/545790
** This bug has been marked a duplicate of bug 545790
package PACKAGE failed to install/upgrade: error writing to '': Success
--
You received this bug notification because you are a member of Ubuntu
Serve
Hi Thomas.
been b
autofs5 starts when runlevel 2 is reached.
This means that it starts after any network connections that are
configured in /etc/network/interfaces have been brought up. That would
include DNS configurations of any kind that a server would have.
If, however, you have configured y
*** This bug is a duplicate of bug 442941 ***
https://bugs.launchpad.net/bugs/442941
Hi Kevin, great report, and great suggestion on the apport stuff. This
actually is a duplicate report of a known bug that is pretty much
unrelated to samba. However, it would be awesome if you opened that
sugg
** Changed in: mcollective (Ubuntu)
Status: New => Triaged
** Changed in: mcollective (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mcollective in Ubuntu.
https://bugs.launchpad.net/
This is happening because populating the cache in /var/cache/lxc/... Is
not protected by a lock file or random temp names. The former approach
would be preferrable, since if we tell the system to create 3 at a time,
we don't want 3 concurrent debootstraps, we want 1 and the other 2
processes waitin
Doh, just behind you Serge. Ok, that makes sense. :)
** Changed in: lxc (Ubuntu)
Status: New => Triaged
** Changed in: lxc (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubunt
Hello Stéphane, or anyone else affected,
Accepted lxc into precise-proposed. The package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
(Ubuntu)
Assignee: (unassigned) => Clint Byrum (clint-fewbar)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to zookeeper in Ubuntu.
https://bugs.launchpad.net/bugs/1007433
Title:
zookeeperd not running after installation of zookeeper
er
2) the upstart job should be reporting the failure, not 'start/running'
** Changed in: zookeeper (Ubuntu)
Status: In Progress => Triaged
** Changed in: zookeeper (Ubuntu)
Assignee: Clint Byrum (clint-fewbar) => (unassigned)
** Also affects: dpkg (Ubuntu)
Importance
After bootstrapping with the version of juju in proposed, and setting
'juju-origin: proposed', my bootstrap node started up, with this:
juju:
Installed: 0.5+bzr531-0ubuntu1.1
Candidate: 0.5+bzr531-0ubuntu1.1
Version table:
*** 0.5+bzr531-0ubuntu1.1 0
500 http://us-west-2.ec2.archiv
Verified working in precise-proposed:
root@ip-10-244-15-92:/var/lib/juju/units/mysql-0/charm# relation-ids
db:0
db:1
root@ip-10-244-15-92:/var/lib/juju/units/mysql-0/charm# apt-cache policy juju
juju:
Installed: 0.5+bzr531-0ubuntu1.1
Candidate: 0.5+bzr531-0ubuntu1.1
Version table:
*** 0.5+b
Verified working in precise-proposed
root@ip-10-244-15-92:/var/lib/juju/units/mysql-0/charm# apt-cache policy juju
juju:
Installed: 0.5+bzr531-0ubuntu1.1
Candidate: 0.5+bzr531-0ubuntu1.1
Version table:
*** 0.5+bzr531-0ubuntu1.1 0
500 http://us-west-2.ec2.archive.ubuntu.com/ubuntu/
Cannot test this one as it is blocked on upstream bug #1007657. A fix is
pending, and will need to be pushed into precise-proposed before this
can be verified.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
https://bugs
Excerpts from Raphaël Hertzog's message of 2012-06-02 06:25:02 UTC:
> Clint, where do you see a *circular* dependency? The dependencies that
> you show are not circular.
>
> Also the ordering of package installation is decided by apt and not
> dpkg, so this is an apt bug if any.
>
I don't necess
** Also affects: juju (Ubuntu)
Importance: Undecided
Status: New
** Changed in: juju (Ubuntu)
Status: New => Triaged
** Changed in: juju (Ubuntu)
Importance: Undecided => Low
** Also affects: juju (Ubuntu Precise)
Importance: Undecided
Status: New
** Changed in: ju
** Description changed:
- maas-server must be specified as "http://maas.example.com:80/";;
- "http://maas.example.com/"; is not enough. I would expect to be able to
- omit the port specification when using the scheme's default port.
+ [Test Case]
+ 1. setup MaaS listening on port 80
+ 2. setup a j
Adding lucid task. This actually has to be fixed in lucid and oneiric so
that mysql-5.1 -> 5.5 transitions go properly. Also adding mysql-5.1
since it will have to be rebuilt.
** Also affects: apparmor (Ubuntu Lucid)
Importance: Undecided
Status: New
** Also affects: mysql-5.5 (Ubuntu L
dh_apparmor was in debhelper until precise, so oneiric/lucid apparmor is
unaffected, but adding debhelper tasks instead
** Also affects: debhelper (Ubuntu)
Importance: Undecided
Status: New
** Changed in: apparmor (Ubuntu Oneiric)
Status: Confirmed => Invalid
** Changed in: appa
dh_apparmor was added after lucid, so the code is directly in lucid's
mysql-server-5.1.postrm
** Also affects: mysql-dfsg-5.1 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: debhelper (Ubuntu Lucid)
Status: New => Invalid
** Changed in: debhelper (Ubuntu Oneiric)
** Changed in: debhelper (Ubuntu Oneiric)
Importance: Undecided => High
** Changed in: debhelper (Ubuntu Oneiric)
Status: Triaged => In Progress
** Changed in: debhelper (Ubuntu Oneiric)
Assignee: (unassigned) => Clint Byrum (clint-fewbar)
** Tags added: luci
** Description changed:
+ [Test case]
+ Apparmor:
+ 1.Install dh-apparmor
+ 2. Build a package which build-depends on it (such as mysql-5.5)
+ 3. Extract debs which have dh_apparmor run on them into a dir in tmp with
dpkg -e file.deb /tmp/foo
+ 4. Verify that the postrm has conditional logic to n
** Description changed:
+ MySQL 5.1 and 5.5 must be rebuilt with the updated debhelper/apparmor
+ and so cannot be verified until those fixes are complete.
+
[Test case]
Apparmor:
1.Install dh-apparmor
2. Build a package which build-depends on it (such as mysql-5.5)
3. Extract debs whic
** Description changed:
MySQL 5.1 and 5.5 must be rebuilt with the updated debhelper/apparmor
and so cannot be verified until those fixes are complete.
+
+ Also for clarity sake, there has been a lot of shuffling of this bug
+ around multiple packages for various reasons. This bug is fixed in
** Changed in: mysql-dfsg-5.1 (Ubuntu Lucid)
Status: Triaged => In Progress
** Changed in: mysql-dfsg-5.1 (Ubuntu Lucid)
Assignee: (unassigned) => Clint Byrum (clint-fewbar)
** Changed in: mysql-5.5 (Ubuntu Lucid)
Status: Triaged => Invalid
** Changed in: mysql-5.
I'm a little concerned about how deep inside the core of Apache this
change is. I think its probably, as you say, a corner case if it causes
somebody issues, but we should make sure it actually works as we think
it does by testing some of those corner cases.
** Changed in: apache2 (Ubuntu Precise)
Hello Christoph_vW, or anyone else affected,
Accepted apache2 into precise-proposed. The package will build now and
be available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in ad
Hello Christoph_vW, or anyone else affected,
Accepted modsecurity-apache into precise-proposed. The package will
build now and be available in a few hours. Please test and give feedback
here. See https://wiki.ubuntu.com/Testing/EnableProposed for
documentation how to enable and use -proposed. Than
** Changed in: juju
Milestone: galapagos => honolulu
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
https://bugs.launchpad.net/bugs/955576
Title:
'local:' services not started on reboot
To manage notifications a
Only 'juju bootstrap' prints the message now, which I think is less
confusing since you actually asked it to do something.
** Summary changed:
- 'juju' with no arguments gives confusing message
+ 'juju bootstrap' with no arguments gives confusing message
** Changed in: juju
Importance: Medium
** Changed in: juju
Milestone: galapagos => honolulu
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
https://bugs.launchpad.net/bugs/802117
Title:
juju ssh/scp commands cause spurious key errors, should use a
di
Hi Adriene, thanks for reporting this issue!
Even though this is a "system" file, it is controlled by files in user
home directories (~/.juju/environments.yaml) and so I don't think we can
purge the upstart jobs.
I do think we can add a check to the upstart job's pre-start for juju,
and if it is
This does indeed look to be Invalid in libnss-ldap. Its worth taking a
look at in glibc though as perhaps there is some work to resolve this in
NSS's design, so opening a bug task against eglibc.
** Changed in: libnss-ldap (Ubuntu)
Status: Incomplete => Invalid
** Also affects: eglibc (Ubu
I'm going to move this back to 'Confirmed' so we can take a look at this
in the next sweep for bugs in krb5. There are 3 affected, so its likely
the problem is at least worth a look.
** Changed in: krb5 (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because
*** This bug is a duplicate of bug 1006553 ***
https://bugs.launchpad.net/bugs/1006553
Hi Adrien, this is a duplicate of bug #1006553 , which will be fixed by
not starting the agents on reboot (since the lxc containers and
zookeeper are not also resurrected).
** This bug has been marked a dup
** Also affects: juju (Ubuntu)
Importance: Undecided
Status: New
** Also affects: juju (Ubuntu Precise)
Importance: Undecided
Status: New
** Changed in: juju (Ubuntu)
Status: New => Triaged
** Changed in: juju (Ubuntu Precise)
Status: New => Triaged
--
You rec
r541 released to Quantal, marking Fix Released
** Changed in: juju (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
https://bugs.launchpad.net/bugs/1007657
Title:
propos
Nathan, you must have a modified /etc/mysql/my.cnf then. log_error is
not set in any of the 5.5 packages for precise or quantal, so there
should actually be no error log being written. I have a fix committed to
the packaging branch for that (bug #1014732) .. and this log rotate will
also be fixed.
** Description changed:
+ [Test Case]
+ 1. install juju from precise-proposed
+ 2. create a local environment in ~/.juju/environments.yaml, with juju-origin:
proposed
+ 3. juju bootstrap -e local-env-name
+ 4. juju deploy -e local-env-name wordpress
+- broken version will fail during the mast
Whoops, r542 has the actual fix.
** Changed in: juju (Ubuntu)
Status: Fix Released => Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
https://bugs.launchpad.net/bugs/1007657
Title:
proposed origin does
r542 has been uploaded to Debian unstable. Just awaiting sync.
** Changed in: juju (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
https://bugs.launchpad.net/bugs/1007657
** Changed in: juju (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
https://bugs.launchpad.net/bugs/1007657
Title:
proposed origin does not work with local provide
I'm adding an upstart task. I'm wondering if its even valid for upstart
to log these at the default log priority. Perhaps they should be dropped
to 'info' level. Killing a process as part of stopping the job is a
perfectly normal situation and doesn't really seem to warrant logs. The
only time I th
Here is the patch I have come up with, very simple, but I'm not sure of
the full ramifications:
** Patch added: "ignore-sighup-early.patch"
https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/978356/+attachment/3196698/+files/ignore-sighup-early.patch
** Tags added: patch
--
You received
** Also affects: dnsmasq (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: squid3 (Ubuntu Precise)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubunt
** Description changed:
+ [ Test case ]
+ This is difficult to test as it is a race condition, however there are
multiple users affected.
+
+ 1. install squid3 on a system which has a system level network connection
+ 2. reboot
+ 3. on bootup, check to see if squid3 is running (service squid3 st
** Changed in: dnsmasq (Ubuntu Precise)
Status: New => Invalid
** Bug watch added: Squid Bugzilla #3574
http://bugs.squid-cache.org/show_bug.cgi?id=3574
** Also affects: squid via
http://bugs.squid-cache.org/show_bug.cgi?id=3574
Importance: Unknown
Status: Unknown
--
You
Works in precise-proposed:
# apt-get install python-ceph
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following package was automatically installed and is no longer required:
libapt-inst1.3
Use 'apt-get autoremove' to remove them.
The follow
Thanks for getting back to us, closing the report as Invalid.
** Changed in: mysql-5.5 (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.5 in Ubuntu.
https://bugs.launchpad.net/bugs/1
** Summary changed:
- Please sync rabbitmq-server 2.8.2 from Debian
+ Please merge rabbitmq-server 2.8.2 from Debian
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to rabbitmq-server in Ubuntu.
https://bugs.launchpad.net/bugs/1004373
Ti
1 - 100 of 2248 matches
Mail list logo
