Well, I still need to file a MIR for libpwquality, and a separate one
for ding-libs if needed (it got split off sssd some time ago)
and actually, when the new samba is merged ldb will move to main, so
having it here is probably unnecessary
--
You received this bug notification because you are a
Hello Andrea, or anyone else affected,
Accepted lxc into quantal-proposed. The package will build now and be
available at
http://launchpad.net/ubuntu/+source/lxc/0.8.0~rc1-4ubuntu39.12.10.5 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
http
Hello John, or anyone else affected,
Accepted lxc into quantal-proposed. The package will build now and be
available at
http://launchpad.net/ubuntu/+source/lxc/0.8.0~rc1-4ubuntu39.12.10.5 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https:
[Expired for dnsmasq (Ubuntu) because there has been no activity for 60
days.]
** Changed in: dnsmasq (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchp
Hello Andrea, or anyone else affected,
Accepted lxc into quantal-proposed. The package will build now and be
available at
http://launchpad.net/ubuntu/+source/lxc/0.8.0~rc1-4ubuntu39.12.10.4 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
http
Hello John, or anyone else affected,
Accepted lxc into quantal-proposed. The package will build now and be
available at
http://launchpad.net/ubuntu/+source/lxc/0.8.0~rc1-4ubuntu39.12.10.4 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https:
** Branch linked: lp:ubuntu/python-django
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-django in Ubuntu.
https://bugs.launchpad.net/bugs/1231923
Title:
FTBFS: test_instance_is_maintained fails
To manage notifications about
** Branch linked: lp:ubuntu/qemu
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1243403
Title:
Upgrade from qemu 1.0+noroms-0ubuntu14.11 fails
To manage notifications about this bug
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: juju-core (Ubuntu)
Status: New => Confirmed
--
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/bug
The attachment "Patch to /debian/lxc.lxc-net.upstart" seems to be a
patch. If it isn't, please remove the "patch" flag from the attachment,
remove the "patch" tag, and if you are a member of the ~ubuntu-
reviewers, unsubscribe the team.
[This is an automated message performed by a Launchpad user
This bug was fixed in the package simplestreams -
0.1.0~bzr318-0ubuntu1.1
---
simplestreams (0.1.0~bzr318-0ubuntu1.1) saucy-proposed; urgency=low
* fix bug resulting in 'unexpected checksum' most commonly seen
if an http proxy was being used (LP: #1240652)
-- Scott MoserThu
Hello John, or anyone else affected,
Accepted lxc into precise-proposed. The package will build now and be
available at http://launchpad.net/ubuntu/+source/lxc/0.7.5-3ubuntu69 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubunt
Hello Andrea, or anyone else affected,
Accepted lxc into precise-proposed. The package will build now and be
available at http://launchpad.net/ubuntu/+source/lxc/0.7.5-3ubuntu69 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubu
Didier, can you look at this bug again and figure out what needs to
happen next?
** Changed in: ding-libs (Ubuntu)
Assignee: (unassigned) => Didier Roche (didrocks)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
h
Public bug reported:
Setting LXC_DOMAIN=lxc in /etc/default/lxc-net causes the lxc-net init
script to pass -s lxc to the private LXC dnsmasq instance running on the
lxcbr0 interface (on 10.0.3.1, say).
Then, adding server=/lxc/10.0.3.1 to /etc/dnsmasq.conf causes the normal
dnsmasq to forward que
The verification of this Stable Release Update has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression
This bug was fixed in the package lxc - 0.8.0~rc1-4ubuntu39.12.10.3
---
lxc (0.8.0~rc1-4ubuntu39.12.10.3) quantal-proposed; urgency=low
* Add code to postinst to fix any double-migration of /etc/dnsmasq.
(LP: #1157332)
-- Stephane GraberWed, 27 Mar 2013 16:55:17 -0400
** C
Not to mention the change is being SRUed to all release, so they'll get
the change way before they dist-upgrade.
--
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/1244635
Title:
setuid exe
Quoting Seth Arnold (1244...@bugs.launchpad.net):
> Serge, what does " After this version, respect the user's choice." mean?
It means if the user manually chmods /var/lib/lxc to 755, we don't
change it again after this. (Except, see below)
> Does this mean someone upgrading from e.g. 12.04.3 lxc
Serge, what does " After this version, respect the user's choice." mean?
Does this mean someone upgrading from e.g. 12.04.3 lxc packages to 14.04
lxc packages -- skipping this update -- would have the 'unsafe'
permissions?
Or will this check be carried before to e.g. 14.04 lxc packages and only
ex
quantal package looks good.
** 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 lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1157332
Title:
/etc/dnsmasq.d-available
We are looking into backporting 1.0.0~alpha1 to precise-backports which
will contain the needed fix.
--
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/1157332
Title:
/etc/dnsmasq.d-availab
Hello John, or anyone else affected,
Accepted lxc into raring-proposed. The package will build now and be
available at http://launchpad.net/ubuntu/+source/lxc/0.9.0-0ubuntu3.7 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubunt
Hello Andrea, or anyone else affected,
Accepted lxc into raring-proposed. The package will build now and be
available at http://launchpad.net/ubuntu/+source/lxc/0.9.0-0ubuntu3.7 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubu
Hello Andrea, or anyone else affected,
Accepted lxc into precise-proposed. The package will build now and be
available at http://launchpad.net/ubuntu/+source/lxc/0.7.5-3ubuntu68 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubu
Hello John, or anyone else affected,
Accepted lxc into precise-proposed. The package will build now and be
available at http://launchpad.net/ubuntu/+source/lxc/0.7.5-3ubuntu68 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubunt
** Changed in: lxc (Ubuntu Quantal)
Status: New => Fix Committed
** Changed in: lxc (Ubuntu Raring)
Status: New => Fix Committed
** Changed in: lxc (Ubuntu Raring)
Importance: Undecided => Medium
** Changed in: lxc (Ubuntu Quantal)
Importance: Undecided => Medium
** Changed
Could you try setting
devices/system/cpu/cpu0/cpufreq/scaling_governor = performance
in /etc/sysfs.conf?
http://etbe.coker.com.au/2010/03/17/starting-with-kvm/ suggests that kvm
may not like frequency scaling on on that cpu.
** Changed in: linux (Ubuntu)
Status: Invalid => Incomplete
--
This bug was fixed in the package lxc - 1.0.0~alpha2-0ubuntu5
---
lxc (1.0.0~alpha2-0ubuntu5) trusty; urgency=low
[ Serge Hallyn]
* debian/rules and debian/lxc.postinst: set /var/lib/lxc and /var/cache/lxc
to be perms 700. That prevents unprivileged users from running setuid-
This bug was fixed in the package lxc - 1.0.0~alpha2-0ubuntu5
---
lxc (1.0.0~alpha2-0ubuntu5) trusty; urgency=low
[ Serge Hallyn]
* debian/rules and debian/lxc.postinst: set /var/lib/lxc and /var/cache/lxc
to be perms 700. That prevents unprivileged users from running setuid-
Confirming on Precise Pangolin, although with KDE, ssh-askpass and
ksshaskpass. Not solved yet.
If I run ssh-askpass or ksshaskpass from the command line, it prints my
ssh key passphrase to stdout (!), derived from my password wallet.
Running ssh-add from the command line puts my key into the ss
** Description changed:
During instance boot, cloud-init installs packages (if instructed by the
user).
During instance boot, there is no state of the system that the user cares
about.
I'd like to use eatmydata for apt-get install at that point, as it is
dramatically faster than apt-g
Looks like a duplicate of bug 1243187 for the Ubuntu package.
** Also affects: horizon (Ubuntu)
Importance: Undecided
Status: New
** Changed in: horizon
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscri
Probably an apparmor thing.
/etc/apparmor.d/usr.sbin.slapd
--
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/1245921
Title:
postinstaller expects slapd.d to be a directory
To manage
** Changed in: php5 (Ubuntu)
Status: New => Triaged
** Changed in: php5 (Ubuntu)
Importance: Undecided => Medium
** Tags added: bitesize
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in Ubuntu.
https://bugs.launchpad.
Public bug reported:
Related to
https://answers.launchpad.net/ubuntu/+source/openldap/+question/237854
When upgrading slapd, I observed the following:
root@ubuntu:~# apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly insta
I had been considering splitting the lxc apparmor profile loading to its
own upstart job so it would happen sooner, but that will only make the
container start weirdly due to lxc-net not having started. What we need
is a way for lxc-start to know that it shouldn't run yet.
I propose we add a 'lxc
** Changed in: c3p0 (Debian)
Status: New => Confirmed
** Changed in: c3p0 (Debian)
Importance: Undecided => Unknown
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to c3p0 in Ubuntu.
https://bugs.launchpad.net/bugs/1245868
Titl
Problem still exists on 13.10 / amd64. I've dumped /sbin/init with
debugfs, compared it with the one from the package and they are
identical. /sbin/init seems to match 'HOME' and /proc/1/maps does not
match 'init.'
--
You received this bug notification because you are a member of Ubuntu
Server Te
verification-done: we've successfully run installation on the systems
that were previously showing the error.
** 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 curtin
** Changed in: ceilometer (Ubuntu)
Status: Fix Committed => Invalid
** Changed in: cinder (Ubuntu)
Status: Fix Committed => Invalid
** Changed in: glance (Ubuntu)
Status: Fix Committed => Invalid
** Changed in: horizon (Ubuntu)
Status: Fix Committed => Invalid
** Cha
This bug was fixed in the package heat - 2013.2-0ubuntu1
---
heat (2013.2-0ubuntu1) saucy; urgency=low
* New upstream release (LP: #1236462).
-- Chuck ShortThu, 17 Oct 2013 09:30:24 -0400
** Changed in: heat (Ubuntu Saucy)
Status: Fix Committed => Fix Released
--
You
The verification of this Stable Release Update has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression
This bug was fixed in the package ceilometer - 2013.2-0ubuntu1
---
ceilometer (2013.2-0ubuntu1) saucy; urgency=low
* New upstream release (LP: #1236462).
-- Chuck ShortThu, 17 Oct 2013 09:38:31 -0400
** Changed in: cinder (Ubuntu Saucy)
Status: Fix Committed => Fix Rele
This bug was fixed in the package cinder - 1:2013.2-0ubuntu1
---
cinder (1:2013.2-0ubuntu1) saucy; urgency=low
* New upstream release (LP: #1236462).
-- Chuck ShortThu, 17 Oct 2013 10:00:43 -0400
--
You received this bug notification because you are a member of Ubuntu
Server
This bug was fixed in the package keystone - 1:2013.2-0ubuntu1
---
keystone (1:2013.2-0ubuntu1) saucy; urgency=low
* New upstream release (LP: #1236462).
-- Chuck ShortThu, 17 Oct 2013 10:22:54 -0400
** Changed in: keystone (Ubuntu Saucy)
Status: Fix Committed => Fix Re
This bug was fixed in the package nova - 1:2013.2-0ubuntu1
---
nova (1:2013.2-0ubuntu1) saucy; urgency=low
* New upstream release (LP: #1236462).
-- Chuck ShortThu, 17 Oct 2013 11:27:05 -0400
** Changed in: nova (Ubuntu Saucy)
Status: Fix Committed => Fix Released
** C
This bug was fixed in the package glance - 1:2013.2-0ubuntu1
---
glance (1:2013.2-0ubuntu1) saucy; urgency=low
* New upstream release (LP: #1236462).
-- Chuck ShortThu, 17 Oct 2013 10:11:10 -0400
--
You received this bug notification because you are a member of Ubuntu
Server
This bug was fixed in the package horizon - 1:2013.2-0ubuntu1
---
horizon (1:2013.2-0ubuntu1) saucy; urgency=low
* New upstream release (LP: #1236462).
-- Chuck ShortThu, 17 Oct 2013 09:43:46 -0400
** Changed in: ceilometer (Ubuntu Saucy)
Status: Fix Committed => Fix Re
This bug was fixed in the package swift - 1.10.0-0ubuntu1
---
swift (1.10.0-0ubuntu1) saucy; urgency=low
* New upstream release (LP: #1236462).
-- Chuck ShortThu, 17 Oct 2013 10:26:18 -0400
** Changed in: horizon (Ubuntu Saucy)
Status: Fix Committed => Fix Released
--
Public bug reported:
Imported from Debian bug http://bugs.debian.org/725456:
Source: c3p0
Version: 0.9.1.2-8
Severity: serious
>From my pbuilder build log [on amd64]:
...
compile:
jar:
test-init:
[mkdir] Created dir: /tmp/buildd/c3p0-0.9.1.2/build/testclasses
[copy] Copying 47 files
no need to move samba4 in main, we'll need to merge samba 4.0.x from
debian instead
** Package changed: samba4 (Ubuntu) => samba (Ubuntu)
** Changed in: samba (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
This bug was fixed in the package quantum - 1:2013.1.4-0ubuntu1
---
quantum (1:2013.1.4-0ubuntu1) raring-proposed; urgency=low
* Resynchronize with stable/grizzly (c57c0fa) (LP: #1241202):
- [043837e] _retrieve_extra_groups in Nicira plugin incompatible with
oslo.config >=
Public bug reported:
FreeRADIUS 2.1.12 is out of date. The FreeRADIUS maintainers strongly
suggest to upgrade to at least version 2.2.0 because of various
stability fixes as well as CVE-2012-3547 (even though Ubuntu patched
that CVE in 2.1.10).
Considering that 2.2.0 was released in September 201
Seems to actually be a problem with iscsitarget. There is a sysctl.d
file installed with an entry
net.ipv4.tcp_mem=1048576
this entry causes sysctl to error.
Commenting out the line allows procps to upgrade successfully.
** Package changed: procps (Ubuntu) => iscsitarget (Ubuntu)
--
You recei
You have been subscribed to a public bug:
Applying updates on a 12.04.3 server, the procps package failed to
upgrade as the start script errors with error 255 (as seen in syslog).
Purging the package (forcing dependency break) and reinstalling is not
effective.
ProblemType: Bug
DistroRelease: Ubu
** Also affects: cloud-archive
Importance: Undecided
Status: New
** Changed in: cloud-archive
Importance: Undecided => High
** Changed in: cloud-archive
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which i
I've executed the standard three test topologies in the OpenStack QA
Lab:
1) Nova Network, Cinder iSCSI
2) Nova Network, Cinder Ceph
3) Neutron Network, Cinder Ceph
Aside from three test failures due to issues in the Tempest test suite
that we use from OpenStack upstream, all deployments and test
58 matches
Mail list logo
