This bug was fixed in the package liblinear - 1.8+dfsg-2
Sponsored for Jackson Doak (noskcaj)
---
liblinear (1.8+dfsg-2) unstable; urgency=low
* debian/control:
- Demoted liblinear1's Recommends for liblinear-tools to Suggests, so
packages depending only on the library
This bug was fixed in the package python-django-piston - 0.2.3-2
Sponsored for Andrew Starr-Bochicchio (andrewsomething)
---
python-django-piston (0.2.3-2) unstable; urgency=low
* Team upload.
[ Jakub Wilk ]
* Use canonical URIs for Vcs-* fields.
* Remove DM-Upload-Allowed;
I experienced this failure these days and my unittest always failed at case
neutron.tests.unit.ml2.drivers.cisco.nexus.test_cisco_mech.TestCiscoBasicGet.test_single_get_admin.
After debugging, I found this bug is caused by ml2 type_drivers entry points
not found.
way to reproduce:
1. cd neutron
how do I install this fix?
seems like the build failed?
https://launchpad.net/ubuntu/+source/nova/1:2014.1-0ubuntu1.1/+build/6050434
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
I have done clean install of the server and yes, Windows VM freezes with hyperv
before as well as after reinstall. I'm have reverted my servers to 12.04.4
until this is solved.
Krzysiek
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
** Changed in: ceilometer (Ubuntu)
Status: New = Invalid
** Changed in: cinder (Ubuntu)
Status: New = Invalid
** Changed in: glance (Ubuntu)
Status: New = Invalid
** Changed in: heat (Ubuntu)
Status: New = Invalid
** Changed in: horizon (Ubuntu)
Status: New =
Public bug reported:
Line 107 in /var/lib/dpkg/info/samba-common.postinst fails if smb.conf is not
owned by samba and because of set -e breaks the configuration of the package.
Thats the line:
ucfr samba-common $CONFIG
it should be something like that:
ucfr samba-common $CONFIG || true
in
When will it be released? Any ETA?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to drbd8 in Ubuntu.
https://bugs.launchpad.net/bugs/1314289
Title:
[Precise/regression] drbd 8.4.x backport breaks existing clusters
To manage
** Branch linked: lp:ubuntu/python-django-piston
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-django-piston in Ubuntu.
https://bugs.launchpad.net/bugs/1185012
Title:
Piston subclass of HttpResponse fails with Django 1.5
** Branch linked: lp:ubuntu/python-django-piston
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-django-piston in Ubuntu.
https://bugs.launchpad.net/bugs/1184219
Title:
Piston Django 1.5 incompatibility with simplejson 2.2
** Patch added:
0001-Fix-bug-8882-Broken-processing-of-U-with-vfs_full_au.patch
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1307682/+attachment/4132495/+files/0001-Fix-bug-8882-Broken-processing-of-U-with-vfs_full_au.patch
** Tags added: patch patch-accepted-upstream
--
You
** Tags removed: verification-donee
** Tags added: verification-done
--
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/1275656
Title:
open-vm-dkms 2011.12.20-562307-0ubuntu1:
Public bug reported:
Could we get an updated package for Nut 2.7.2? It's already in Debian
(https://packages.debian.org/sid/nut).
** Affects: nut (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
Tested with environment variable set and saw no issues.
** 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 drbd8 in Ubuntu.
https://bugs.launchpad.net/bugs/1314598
** Summary changed:
- [SRU] packaging for openstack icehouse 2014.1.1 release
+ [SRU] icehouse 2014.1.1 point release
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1328134
Title:
Public bug reported:
strongSwan's charon AppArmor profile is so restrictive it doesn't allow
for smartcards.
** Affects: strongswan (Ubuntu)
Importance: Medium
Assignee: Jonathan Davies (jpds)
Status: In Progress
--
You received this bug notification because you are a member
** Changed in: strongswan (Ubuntu)
Status: New = In Progress
** Changed in: strongswan (Ubuntu)
Importance: Undecided = Medium
** Changed in: strongswan (Ubuntu)
Assignee: (unassigned) = Jonathan Davies (jpds)
--
You received this bug notification because you are a member of
** Changed in: qemu (Ubuntu)
Status: Confirmed = Won't Fix
** Changed in: libvirt (Ubuntu)
Status: Confirmed = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
Bug for obsolete Ubuntu release 9.10, thus closing.
** Changed in: ldns (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ldns in Ubuntu.
https://bugs.launchpad.net/bugs/665187
Title:
ldns-keygen
** Tags added: unittest
** Package changed: neutron (Ubuntu) = neutron
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to neutron in Ubuntu.
https://bugs.launchpad.net/bugs/1204456
Title:
neutron ml2 plugin test failures
To manage
Public bug reported:
As seen here: http://d-jenkins.ubuntu-ci:8080/view/MAAS/job/utopic-adt-
maas/74/console
Setting up maas-dns (1.6+bzr2367+2423+279-0ubuntu1) ...
Traceback (most recent call last):
File /usr/bin/django-admin, line 5, in module
management.execute_from_command_line()
Source package ready at: http://people.canonical.com/~jpds/s5.1.3/
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to strongswan in Ubuntu.
https://bugs.launchpad.net/bugs/1330504
Title:
strongSwan 5.1.3
To manage notifications about
I am using the code of Andreas in #12 now in a productive environment.
So far without any problems. Could someone assign the bug to the package
maintainer? It seems like I have not the option to do that here. Thank
you, Chris.
--
You received this bug notification because you are a member of
Public bug reported:
There's a new version of strongSwan out: 5.1.3.
** Affects: strongswan (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to strongswan in Ubuntu.
You have been subscribed to a public bug:
We have an Ubuntu server (64-bit) that host multiple virtual machines
(mostly Linux).
The server is managed remotely using virt-manager.
Both machines (client and server) were recently upgraded from 13.10 to
14.04.
I noticed that shutting down the VM
As Serge said, you are missing required rules in your libvirtd profile. This
probably happened during upgrade and you like have a
/etc/apparmor.d/usr.sbin.libvirtd.dpkg-new file. If you add these rules to the
profile then do:
$ sudo apparmor_parser -r /etc/apparmor.d/usr.sbin.libvirtd
things
Looks like this is a problem with python-django-piston's packaging:
Result of `apt-cache show python-django-piston` in trusty:
http://paste.ubuntu.com/7653328/ and in utopic:
http://paste.ubuntu.com/7653329/
Note the difference in 'Depends':
Trusty:
Depends: python (= 2.7), python ( 2.8),
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: maas (Ubuntu)
Status: New = Confirmed
--
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/1271188
This bug was fixed in the package drbd8 - 2:8.4.3-0ubuntu0.12.04.2
---
drbd8 (2:8.4.3-0ubuntu0.12.04.2) precise-proposed; urgency=low
* d/p/ubuntu-fix-drbdsetup-legacy-path.patch
Test kernel module version and run the legacy drbdsetup early if
it is lower than 8.4. Also do
The release of the is package was dependent upon another bug being fixed
by this version being verified, that verification has now happened.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to drbd8 in Ubuntu.
This bug was fixed in the package drbd8 - 2:8.4.3-0ubuntu0.12.04.2
---
drbd8 (2:8.4.3-0ubuntu0.12.04.2) precise-proposed; urgency=low
* d/p/ubuntu-fix-drbdsetup-legacy-path.patch
Test kernel module version and run the legacy drbdsetup early if
it is lower than 8.4. Also do
The verification of the Stable Release Update for drbd8 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
The verification of the Stable Release Update for drbd8 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
*** This bug is a duplicate of bug 1315888 ***
https://bugs.launchpad.net/bugs/1315888
** This bug has been marked a duplicate of bug 1315888
Zlib functions (gzopen etc.) are undefined while gzopen64 etc. exist
--
You received this bug notification because you are a member of Ubuntu
** Changed in: corosync (Ubuntu)
Status: New = Invalid
** Changed in: pacemaker (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to corosync in Ubuntu.
https://bugs.launchpad.net/bugs/1327222
I found out that not the cluster stack itself was causing the issues but
the tool that I used to configure the cluster: LCMC. Although LCMC has
been working flawlessly for me on older versions of corosync/pacemaker,
it seems as it hasn't been updated to work with corosync 2.3.x and
pacemaker 1.1x.
Public bug reported:
This bug has been reported on many versions of Ubuntu. I've gone through many
fix guides. Nothing works. Here's the problem.
___
1) apt-get purge php-pear
2) rm -rf ~/.pearrc /etc/pear.conf /usr/share/php/
/usr/share/doc/php5-common/PEAR (required to purge all things
** Tags added: ci
--
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/1330498
Title:
maas package missing dependency on python-decorator
To manage notifications about this bug go to:
I ran `sudo tdbbackup *.tdb` in /var/lib/samba and my join is persisting
even with multiple reboots.
--
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/1291951
Title:
winbind loose
Public bug reported:
In the Add New Virtual Hardware dialog virt-manager let's you create a
filesystem passthrough with the Proxy type. That's very useful for
safely sharing data owned by a user. However the process fails to
complete with an error:
Error adding device: unsupported configuration:
Thanks for reporting this bug. Given the lkml.org fix, I assume this is
in fact a kernel bug, so assigning it as such.
This is presumably fix-released in utopic, but SRU-able to precise and
trusty's backport kernels. I'm not clearn on how that process works, so
leaving it like this.
** Also
The feature that I would like in maas to address this is the ability for
the user to provide installer config (in addition to user-data). This
installer config would be passed wholesale through maas to curtin (or
d-i). .
This would allow either
a.) the user to provide curtin-config without
This bug was fixed in the package walinuxagent - 2.0.5-0ubuntu2~12.04.0
---
walinuxagent (2.0.5-0ubuntu2~12.04.0) precise; urgency=medium
* Backport from 14.10 development version to 12.04 (LP: #1321427).
* Use 12.04 appropriate dependencies and standards version.
* Dropped
The verification of the Stable Release Update for walinuxagent 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
This bug was fixed in the package walinuxagent - 2.0.5-0ubuntu2~12.04.0
---
walinuxagent (2.0.5-0ubuntu2~12.04.0) precise; urgency=medium
* Backport from 14.10 development version to 12.04 (LP: #1321427).
* Use 12.04 appropriate dependencies and standards version.
* Dropped
This bug was fixed in the package walinuxagent - 2.0.5-0ubuntu2~14.04.0
---
walinuxagent (2.0.5-0ubuntu2~14.04.0) trusty; urgency=medium
* Straight backport to 14.04 (LP: #1321427).
* Use 14.04 appropriate dependencies.
-- Ben Howard ben.how...@ubuntu.com Mon, 26 May 2014
The verification of the Stable Release Update for cunit 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
This bug was fixed in the package cunit - 2.1-0.dfsg-9build1
---
cunit (2.1-0.dfsg-9build1) precise-proposed; urgency=medium
* No change rebuild so we can actually publish this into updates and
override it to main... (LP: #1275656)
-- Stephane Graber stgra...@ubuntu.com Wed,
** Changed in: open-vm-tools (Ubuntu Trusty)
Status: Fix Committed = In Progress
--
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/1275656
Title:
open-vm-dkms
** Branch linked: lp:~rcj/ubuntu/trusty/open-vm-tools/trusty-proposed
--
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/1275656
Title:
open-vm-dkms 2011.12.20-562307-0ubuntu1:
Confirming this issue on trusty with juju 1.18.4. br0 is not created.
--
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/1271144
Title:
br0 not brought up by cloud-init script with
I have fixed an issue infinity found in the trusty-proposed package.
There was a problem with the package relationships between the new and
transitional packages. The latest revision in this branch has a fix for
those relationships; namely the transitional package depends on the new
package, while
So, my nodes don't have eth0, but p1p1, if that makes any difference.
I've noticed that br0 was not configured, so I manually added it to
/etc/network/interfaces. After I brought up the interface, I've deployed
a charm within LXC container.
Nodes are deployed by MAAS.
So, obviously, this is
So, my nodes don't have eth0, but p1p1, if that makes any difference.
This is most likely the key; the MAAS provider code assumes it's dealing
with eth0. Thanks for the information.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
This is also blocking a precise - trusty migration for me.
Would it be possible / feasible to provide a pc-1.0-precise machine
type in qemu for trusty and an updated libvirt for precise that allows
you to change the machine attribute on the type element for migration,
so I could specify a
55 matches
Mail list logo
