*** This bug is a duplicate of bug 523812 ***
https://bugs.launchpad.net/bugs/523812
I've now had 0.99.20 running fully stable for 24 hours. My ospfd issues have
gone and everything appears to be much more stable. It seems a lot of ospfd
issues were patched upstream at 0.99.18+
For
Public bug reported:
Dialog selections:
select configure database for keystone with dbconfig-common
select sqlite3
dpkg output:
-
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
keystone
0
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keystone in Ubuntu.
https://bugs.launchpad.net/bugs/944684
Title:
Error installing keystone selecting dbconfig-common and sqlite3 as the
backend
To manage notifications about this
First clean keystone install.
** Branch linked: lp:~openstack-ubuntu-packagers/keystone/ubuntu
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keystone in Ubuntu.
https://bugs.launchpad.net/bugs/944684
Title:
Error installing
Thanks for this bug report. Today, keystone should have a major change,
which has been held back until now. The 'upstream' of keystone has
performed a rewrite, which should land today.
I'd be interested if you could try to reproduce this after it is
uploaded.
Thanks.
** Changed in: keystone
** Changed in: keystone (Ubuntu)
Status: New = Triaged
** Changed in: openstack-dashboard (Ubuntu)
Status: New = Triaged
** Changed in: keystone (Ubuntu)
Assignee: (unassigned) = Chuck Short (zulcss)
** Changed in: openstack-dashboard (Ubuntu)
Assignee: (unassigned) =
It looks like this patch is already applied in Precise, based on a
visual inspection of /usr/lib/ruby/1.8/facter/util/processor.rb.
On a Pandaboard freshly installed with a Precise armhf netinst today:
root@panda0:~# facter processorcount
2
root@panda0:~# facter processor0 processor1
processor0
This will be fixed in today's upload.
** Changed in: python-keystoneclient (Ubuntu)
Status: Confirmed = In Progress
** Changed in: openstack-dashboard (Ubuntu)
Status: Triaged = In Progress
** Changed in: keystone (Ubuntu)
Status: Triaged = In Progress
--
You received
rbasak lamont: can I mark the bug Fix Released for precise, or would you like
to check further first?
lamont 'tever - if it's returning good facts, I'm happy
** Changed in: facter (Ubuntu Precise)
Status: Triaged = Fix Released
** Changed in: facter (Ubuntu Precise)
Assignee: Robie
Blueprint changed by Clemens Kalb:
Whiteboard changed:
Status: 5.4 has not released yet, though it is in final rc stages.
Debian has not been tracking the RC's, nor have we been able to devote
enough resources to that in Ubuntu. Given the proximity to feature
freeze and low priority given
This bug was fixed in the package lxc - 0.7.5-3ubuntu31
---
lxc (0.7.5-3ubuntu31) precise; urgency=low
* 0050-clone-lvm-sizes: make lxc-clone with lvm snapshots create a
snapshot of the same size as the original. (LP: #939765)
* run our dnsmasq as user 'lxc-dnsmasq' (LP:
This bug was fixed in the package lxc - 0.7.5-3ubuntu31
---
lxc (0.7.5-3ubuntu31) precise; urgency=low
* 0050-clone-lvm-sizes: make lxc-clone with lvm snapshots create a
snapshot of the same size as the original. (LP: #939765)
* run our dnsmasq as user 'lxc-dnsmasq' (LP:
This bug was fixed in the package lxc - 0.7.5-3ubuntu31
---
lxc (0.7.5-3ubuntu31) precise; urgency=low
* 0050-clone-lvm-sizes: make lxc-clone with lvm snapshots create a
snapshot of the same size as the original. (LP: #939765)
* run our dnsmasq as user 'lxc-dnsmasq' (LP:
This bug was fixed in the package lxc - 0.7.5-3ubuntu31
---
lxc (0.7.5-3ubuntu31) precise; urgency=low
* 0050-clone-lvm-sizes: make lxc-clone with lvm snapshots create a
snapshot of the same size as the original. (LP: #939765)
* run our dnsmasq as user 'lxc-dnsmasq' (LP:
This bug was fixed in the package lxc - 0.7.5-3ubuntu31
---
lxc (0.7.5-3ubuntu31) precise; urgency=low
* 0050-clone-lvm-sizes: make lxc-clone with lvm snapshots create a
snapshot of the same size as the original. (LP: #939765)
* run our dnsmasq as user 'lxc-dnsmasq' (LP:
This bug was fixed in the package lxc - 0.7.5-3ubuntu31
---
lxc (0.7.5-3ubuntu31) precise; urgency=low
* 0050-clone-lvm-sizes: make lxc-clone with lvm snapshots create a
snapshot of the same size as the original. (LP: #939765)
* run our dnsmasq as user 'lxc-dnsmasq' (LP:
This bug was fixed in the package lxc - 0.7.5-3ubuntu31
---
lxc (0.7.5-3ubuntu31) precise; urgency=low
* 0050-clone-lvm-sizes: make lxc-clone with lvm snapshots create a
snapshot of the same size as the original. (LP: #939765)
* run our dnsmasq as user 'lxc-dnsmasq' (LP:
Attached Fix.
** Patch added: Patch
https://bugs.launchpad.net/ubuntu/+source/amavisd-new/+bug/930916/+attachment/2801291/+files/amavisd-new_2.6.5-0ubuntu4.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to amavisd-new in
Thanks Vibhav for your work on this.
Can you verify that in your patch you replaced the old debian/amavisd-
new.init with the new debian/amavisd-new.init? Because the changes in
the attached patch are rather large.
--
You received this bug notification because you are a member of Ubuntu
Server
Public bug reported:
Please sync puppet 2.7.11-1 (main) from Debian sid (main)
Explanation of the Ubuntu delta and why it can be dropped:
* Use maintscript support in dh_installdeb rather than writing out
dpkg-maintscript-helper commands by hand. We now simply Pre-Depend on a
new
This bug was fixed in the package keystone - 2012.1~e4-0ubuntu1
---
keystone (2012.1~e4-0ubuntu1) precise; urgency=low
[ Chuck Short ]
* New upstream release.
* debian/keystone.upstart: Update for ksl.
* debian/control: Add python-keystoneclient as dependency.
*
This bug was fixed in the package keystone - 2012.1~e4-0ubuntu1
---
keystone (2012.1~e4-0ubuntu1) precise; urgency=low
[ Chuck Short ]
* New upstream release.
* debian/keystone.upstart: Update for ksl.
* debian/control: Add python-keystoneclient as dependency.
*
This bug was fixed in the package python-keystoneclient -
2012.1~e4-0ubuntu1
---
python-keystoneclient (2012.1~e4-0ubuntu1) precise; urgency=low
* New upstream release.
* debian/disbale-argparse.patch: Dropped.
* debian/control: dont conflict on keystone. (LP: #934064)
*
** Branch linked: lp:ubuntu/python-keystoneclient
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keystone in Ubuntu.
https://bugs.launchpad.net/bugs/934064
Title:
Installing openstack-dashboard on Precise removes Keystone package
This bug was fixed in the package nova - 2012.1~e4-0ubuntu1
---
nova (2012.1~e4-0ubuntu1) precise; urgency=low
[ Adam Gandleman ]
* debian/patches/libvirt-use-console-pipe.patch: Refreshed.
* debain/nova-volume.upstart.in: Ensure lock directory is created
(LP: #940780)
*
Thanks Dave,
Installing works now, but removing throws an error:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
keystone
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
After this operation,
Also dpkg-reconfigure keystone and using sqlite3 throws the following
error:
Traceback (most recent call last):
File /usr/bin/keystone-manage, line 28, in module
cli.main(argv=sys.argv, config_files=config_files)
File /usr/lib/python2.7/dist-packages/keystone/cli.py, line 147, in main
keystone:
Installed: 2012.1~e4-0ubuntu1
Candidate: 2012.1~e4-0ubuntu1
Version table:
*** 2012.1~e4-0ubuntu1 0
500 http://archive.ubuntu.com/ubuntu/ precise/universe amd64 Packages
100 /var/lib/dpkg/status
--
You received this bug notification because you are a member of
Blueprint changed by Clint Byrum:
Whiteboard changed:
- Status: 5.4 has not released yet, though it is in final rc stages.
- Debian has not been tracking the RC's, nor have we been able to devote
- enough resources to that in Ubuntu. Given the proximity to feature
- freeze and low priority given
For info, keystone packages after 2012.1~e4-0ubuntu1 (after the prior
review), is based on whole new upstream code. Upstream rewrote this
project from scratch. Apologies for the doubling of work.
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Server Team,
This bug was fixed in the package lxc - 0.7.5-0ubuntu8.5
---
lxc (0.7.5-0ubuntu8.5) oneiric-proposed; urgency=low
* lxcguest.lxcguest.upstart: emit the net-device-up IFACE=lo event, so
that any upstart jobs waiting on it (esp rc-sysinit before oneiric) will
proceed. (LP:
This bug was fixed in the package lxc - 0.7.5-0ubuntu8.5
---
lxc (0.7.5-0ubuntu8.5) oneiric-proposed; urgency=low
* lxcguest.lxcguest.upstart: emit the net-device-up IFACE=lo event, so
that any upstart jobs waiting on it (esp rc-sysinit before oneiric) will
proceed. (LP:
This bug was fixed in the package linux - 3.2.0-18.28
---
linux (3.2.0-18.28) precise; urgency=low
[ Andy Whitcroft ]
* ubuntu: AUFS -- adapt to the new changelog handling
* ubuntu: AUFS -- sort out the relative header paths
* ubuntu: AUFS -- update to
Public bug reported:
Precise 3D 32-Bit up-to-date
What you expected to happen:
When right clicking a folder and selecting these sharing options:
* Share this folder
* Allow others to create and delete...
* Guest access
+ Modify Share
+ Adding the needed permissions by conforming that option in
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/945117
Title:
can't edit files in my public guest allow rw folder
To manage notifications about this bug go to:
Public bug reported:
$ lintian nova-ajax-console-proxy_2012.1~e4-0ubuntu1_all.deb:
W: nova-ajax-console-proxy: syntax-error-in-debian-changelog line 77 badly
formatted trailer line
W: nova-ajax-console-proxy: spelling-error-in-changelog dont don't
W: nova-ajax-console-proxy:
Public bug reported:
Because of the current ssh approach used in lxc-start-ephemeral in lieu
of lxc-attach, you need a password or key in the ubuntu account to
connect. If you want to do this with automation, you can use a key. If
you want to use this with another user and that user's key, you
** Branch linked: lp:~benji/ubuntu/precise/lxc/bug-945183
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/945183
Title:
lxc-start-ephemeral is difficult to use with non-ubuntu accounts
** Changed in: lxc (Ubuntu)
Status: New = Confirmed
** 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 Ubuntu.
https://bugs.launchpad.net/bugs/945183
Title:
This bug was fixed in the package lxc - 0.7.5-3ubuntu32
---
lxc (0.7.5-3ubuntu32) precise; urgency=low
* add user (-u) and key (-S) to lxc-start-ephemeral. (LP: #945183)
-- benji benji.y...@canonical.com Fri, 02 Mar 2012 17:20:46 -0500
** Changed in: lxc (Ubuntu)
Maarten - thanks for submitting this patch. As I mentioned in the merge
review, I believe this should go through debian (see
http://www.debian.org/Bugs/Reporting). If you do so, you can mark this
bug as 'also affecting' the debian bug # you opened.
If you prefer, please let me know and I'll
** Branch linked: lp:ubuntu/389-ds-base
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/27463
Title:
[needs-packaging] 389 Directory Server for Ubuntu
To manage notifications about
mterry, thanks for the review. I fixed the test suite, it now runs on
build, and added a -V to dh_makeshlibs.
** Changed in: log4cxx (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to netty in
Public bug reported:
I am using GPSD to connect to my GPS receiever (Garmin 18 LVC).
/etc/default/gpsd:
START_DAEMON=true
GPSD_OPTIONS=-n -b
BAUDRATE=4800
DEVICES=/dev/ttyS5
USBAUTO=false
GPSD_SOCKET=/var/run/gpsd.sock
The daemon works and i get data using: gpsd -n -b -N -D2 /dev/ttyS5
This is on 12.04 server Beta 1 :-)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/945264
Title:
NTP not receiving PPS signal
To manage notifications about this bug go to:
*** This bug is a duplicate of bug 693594 ***
https://bugs.launchpad.net/bugs/693594
I'm marking this a duplicate of #693594 but if you come across this here
are some Workarounds/Fixes:
1)do not move all tasks into a default cgroup
comment CREATE_DEFAULT=yes out and uncomment
Hi
I've been looking at cgroup bugs and I suspect that you have a
multicore/hypterthreaded system which is experiencing a symptom of
https://bugs.launchpad.net/ubuntu/+source/libcgroup/+bug/693594 could
you try giving the default group some realtime priority (e.g echo 95
| sudo tee
Public bug reported:
Error in preinst:
Selecting previously unselected package keystone.
Unpacking keystone (from .../keystone_2012.1~e4-0ubuntu1_all.deb) ...
adduser: The group `keystone' does not exist.
id: keystone: No such user
chown: invalid user: `keystone:keystone'
dpkg: error processing
** Branch linked: lp:~gandelman-a/ubuntu/precise/keystone/lp945299
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keystone in Ubuntu.
https://bugs.launchpad.net/bugs/945299
Title:
keystone_2012.1~e4-0ubuntu1_all fails to install
[Expired for samba (Ubuntu) because there has been no activity for 60
days.]
** Changed in: samba (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
Blueprint changed by Timo Aaltonen:
Whiteboard changed:
Rather fine-grained task list below. Uploading full 389ds stack is not
necessary (hence status isn't BLOCKED), though not a whole lot of work
after the prereqs are already done.
Work items (precise-alpha-2):
[tjaalton] package
I have verified the patch again.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to amavisd-new in Ubuntu.
https://bugs.launchpad.net/bugs/930916
Title:
amavis start-stop script fails to stop amavisd
To manage notifications about this
52 matches
Mail list logo
