Hello Gregory, or anyone else affected,
Accepted rpcbind into trusty-proposed. The package will build now and be
available at
http://launchpad.net/ubuntu/+source/rpcbind/0.2.1-2ubuntu2.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https:/
** Description changed:
- Received an upgrade notice. I executed the upgrade procedures which
- indicated 529 packages need to be installed. Upgrade requesrted that I
- install the DVD. of the ISO file I had downloaded. Upgrade did not
- complete and failed to reboot. I had to use "recovery mode"
I confirm this bug in the rpcbind package.
This is an issue specific to upgrades from precise; no fix is needed for
utopic. (A wrong fix is included via Debian; I have reopened Debian bug
#734903 with regards to this.)
** Also affects: rpcbind (Ubuntu Trusty)
Importance: Undecided
Stat
Now a few months since report: Any fix in sight ?
We got another report for this issue here too:
http://www.joomlapolis.com/forum/154-advanced-members-support/226150-workaround-found-reappearance-of-older-qabort-pclpclziplibphp--missing-zlib-extensionsq-error-cb-191
--
You received this bug noti
Seems to me that the issue is not that the MTU isn't being honoured, but
that the MTU should be checked *before* TSO assembly and not *after*.
Assembly should happen outside the VM if the VM has enabled it on the
interface internally, and clearly the incoming segments (not packets, at
this point) m
I'm also seeing a SEGV (not a SIGILL) when testing the version of QEMU
that shipped in trusty. So, we might just consider this bug fixed and
track this segfault issue separately.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in U
Using 2.1+dfsg-2ubuntu2 from utopic within a trusty ubuntu core:
# /usr/bin/qemu-aarch64-static -d unimp /usr/bin/java
host mmap_min_addr=0x1
Reserved 0x12000 bytes of guest address space
Relocating guest address space from 0x0040 to 0x40
guest_base 0x0
startend
** Changed in: samba (Ubuntu Trusty)
Milestone: ubuntu-14.04.1 => ubuntu-14.04.2
--
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/1257186
Title:
memory leakage messages
To manage n
FYI the ppc64el build failed (tests)
https://launchpad.net/ubuntu/+source/strongswan/5.1.3-0ubuntu1/+build/6260486
--
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:
s
multipathd does not act upon udev changes -- its very easy to see when
running udev monitor and multipathd -v9 -d and then attaching new disks.
by the looks of it, support for monitoring events by libudev was only added in
2013, far later than 0.4.9
everything seems to exist in 0.5, and none of i
This bug was fixed in the package qemu - 2.1+dfsg-2ubuntu2
---
qemu (2.1+dfsg-2ubuntu2) utopic; urgency=medium
* reload kvm_intel if needed to set the nested=Y flag (LP: #1324174)
-- Serge HallynMon, 11 Aug 2014 12:58:50 -0500
** Changed in: qemu (Ubuntu)
Status: Triage
Comparing build logs looks good. Comparing binaries looks good. Changes
look fine (excepting the two minor issues I mentioned). The test suites
pass during the build. ACK with my changes (uploading now).
** Changed in: strongswan (Ubuntu)
Status: Triaged => Fix Committed
--
You received t
** Changed in: nagios-plugins (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nagios-plugins in Ubuntu.
https://bugs.launchpad.net/bugs/1273484
Title:
nagios-plugins renamed to monitoring-p
Two entries were missing from the changelog:
* debian/libstrongswan.install: install new acert.* files
* debian/usr.lib.ipsec.stroke: add capability dac_override
I'm still going through the package, but will simply add these as part
of the sponsoring process.
--
You received this bug notificatio
** Also affects: qemu (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: qemu (Ubuntu Trusty)
Status: New => Confirmed
** Changed in: qemu (Ubuntu Trusty)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
S
This bug was fixed in the package linux - 3.16.0-7.12
---
linux (3.16.0-7.12) utopic; urgency=low
[ Andy Whitcroft ]
* rebase to v3.16 final
* [Config] d-i -- add virtio_scsi to virtio-modules
- LP: #1342000
[ dann frazier ]
* [Packaging] Fix 'printchanges' to work wi
Blueprint changed by Serge Hallyn:
Work items changed:
Work items for ubuntu-14.06:
[serge-hallyn] convert libvirt to cgmanager (4d): DONE
[racb] Early cycle merge report: POSTPONED
[serge-hallyn] merge qemu: DONE
Work items for ubuntu-14.07:
[serge-hallyn] cgmanager package into de
As far as I know, everyone who has experienced this has been using a
thinkpad. I've first experienced this myself last week, on a new
thinkpad running utopic.
Two curious things I noticed, beside this being a thinkpad:
1. I could not start the VM with the bad image at all. Until I rebooted.
The
Public bug reported:
This happens on Utopic. Trusty is fine. Steps to reproduce:
sudo lxc-create -t ubuntu-cloud -n utopic -- -F -s daily -r utopic
sudo lxc-start-ephemeral -o trusty -n test -d
sudo lxc-attach -n test -- login -f root
Examine /etc/apt/sources.list inside the host. For example, "
Hi Martin,
when you get this, I assume that is with the standard trusty or utopic
package?
I ask because the subject says 'ppa' - i'd like to remove that.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.la
OK, so I think we should stick to 5.5. in Utopic then. I'll mark
Won't Fix to reflect this for now, but feel free to change this bug into
one to update to 5.5., or file a new bug for that, or whatever.
Also unsubscribing ~ubuntu-sponsors as we have nothing to upload now.
** Changed in: php5 (Ubun
** Changed in: qemu (Ubuntu)
Status: New => Invalid
--
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/1342000
Title:
UBUNTU14.10-LE:liz:Ubuntu installation failing on virtio-scsi d
** Changed in: qemu (Ubuntu)
Importance: High => Medium
--
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/1129571
Title:
libreoffice armhf FTBFS
To manage notifications about this bug
*** This bug is a duplicate of bug 1292234 ***
https://bugs.launchpad.net/bugs/1292234
** This bug has been marked a duplicate of bug 1292234
qcow2 image corruption in trusty (qemu 1.7 and 2.0 candidate)
--
You received this bug notification because you are a member of Ubuntu
Server Team,
I don't see a /etc/init/serial.conf in my trusty or utopic hosts. Is
that only intalled on ppc hosts?
** No longer affects: qemu (Ubuntu)
--
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/
No, that won't work as it's the emulator in which the build is running.
You should however be able to install the ppa's qemu on a local host,
install a standard ubuntu server vm, apt-get install ubuntu-dev-tools,
copy the package sources over to the vm, and build the packages inside
the vm.
--
Y
How can I use your one? I have no possibility to tweak the host system,
I'm not an lp admin, do you think I can try to add your ppa as
dependency and it will work?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://
I have a similar problem, the metering service print this error even when you
delete a router.
I think that the namespace is deleted but the service does not notice
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to neutron in Ubuntu.
htt
** Changed in: docker.io (Ubuntu Trusty)
Assignee: Adam Conrad (adconrad) => (unassigned)
** Changed in: docker.io (Ubuntu)
Status: Fix Released => Invalid
** Changed in: docker.io (Ubuntu Trusty)
Status: Confirmed => Invalid
--
You received this bug notification because you
(Note, the patches being tested are the ones from this thread:
https://lists.nongnu.org/archive/html/qemu-devel/2014-07/msg03160.html )
--
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/1291
Yes, it's the same bug or same class of bugs where qemu is being
stricter than the kernel, for better or worse.
--
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/1317090
Title:
qemu fails
Are these new failures using the qem upackage in ppa:serge-hallyn/qemu-
user-thread, or using the stock trusty qemu package?
--
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/1350435
Title:
@med hopefully soon - but I have only just finishing reviewing and
uploading for Corey.
In the meantime all the pkgs have been built here as well:
https://launchpad.net/~james-page/+archive/ubuntu/icehouse/+packages
** Changed in: ceilometer (Ubuntu)
Status: New => Invalid
** Changed
Public bug reported:
I don't know if this is specific for php5-curl or that it occurs with
all php modules. When I install this module I see that first the apache
server is reloaded and then the module is set-up. Shouldn't the order be
reversed? Wasn't it the idea that Apache is reloaded automatic
** Branch linked: lp:~ubuntu-server-dev/keystone/icehouse
--
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/1354159
Title:
[SRU] icehouse 2014.1.2 point release
To manage notifications a
** Branch linked: lp:~ubuntu-server-dev/neutron/icehouse
--
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/1185019
Title:
rootwrap sudoers configuration does not follow packaging guidelin
Quoting Matt Mullins (mokom...@gmail.com):
> That's awesome. I just got a chance to test it out, and with a couple
> hiccups (below), I seem to have successfully migrated a guest from a
> precise host to a new trusty one.
>
> It looks like qemu failed to build in Serge's PPA due to the spice that
** Branch linked: lp:~ubuntu-server-dev/neutron/icehouse
--
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/1354159
Title:
[SRU] icehouse 2014.1.2 point release
To manage notifications ab
@jamespage when will this hit t-proposed?
--
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/1354159
Title:
[SRU] icehouse 2014.1.2 point release
To manage notifications about this bug go
Will appear in Ubuntu-3.16.0-7.12
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Committed
--
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/1342000
Title:
UBUNTU14.10-L
** Branch linked: lp:~ubuntu-server-dev/nova/icehouse
--
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/1219658
Title:
Wrong image size using rbd backend for libvirt
To manage notificati
** Branch linked: lp:~ubuntu-server-dev/cinder/icehouse
** Branch linked: lp:~ubuntu-server-dev/glance/icehouse
** Branch linked: lp:~ubuntu-server-dev/nova/icehouse
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
http
the patch removes the warning but still, something isn't right --
multipathd does not show the devices that shoul've been created by the
udev rule. we're gathering more information and will update soon.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
** Branch linked: lp:~ubuntu-server-dev/cinder/icehouse
--
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/1185019
Title:
rootwrap sudoers configuration does not follow packaging guideline
Trove is not covered under the MRE for OpenStack yet.
** Changed in: openstack-trove (Ubuntu)
Status: New => Won't Fix
** Changed in: openstack-trove (Ubuntu Trusty)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team, whic
** Branch linked: lp:~ubuntu-server-dev/horizon/icehouse
--
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/1354159
Title:
[SRU] icehouse 2014.1.2 point release
To manage notifications ab
** Branch linked: lp:~ubuntu-server-dev/trove/icehouse
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openstack-trove in Ubuntu.
https://bugs.launchpad.net/bugs/1347567
Title:
trove unit tests disabled
To manage notifications about
** Branch linked: lp:~ubuntu-server-dev/trove/icehouse
--
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/1354159
Title:
[SRU] icehouse 2014.1.2 point release
To manage notifications abou
** Branch linked: lp:~ubuntu-server-dev/ceilometer/icehouse
--
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/1354159
Title:
[SRU] icehouse 2014.1.2 point release
To manage notifications
** Branch linked: lp:~corey.bryant/keystone/2014.1.2
--
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/1354159
Title:
[SRU] icehouse 2014.1.2 point release
To manage notifications about
This is supported via the glance-simplestreams-sync charm.
** Changed in: glance (Juju Charms Collection)
Status: Triaged => Invalid
** No longer affects: glance (Ubuntu Trusty)
** Changed in: glance (Ubuntu)
Status: Invalid => Triaged
--
You received this bug notification becaus
** Changed in: ldns (Debian)
Status: Unknown => Fix Released
--
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/1354699
Title:
libldns.pc (pkg-config description) installed in wrong
Public bug reported:
Please sync nose 1.3.3-2 (main) from Debian unstable (main)
Changelog entries since current utopic version 1.3.3-1:
nose (1.3.3-2) unstable; urgency=low
* Add patch to make sure we call super constructor for LazySuite. Without
this, tests fail under Python3.4 as _remo
** Changed in: openldap (Ubuntu)
Status: New => Triaged
--
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/1347954
Title:
build slapd-sha2 module for strong passwords
To manage
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Reproduced on Trusty but not on Utopic. It looks like this was fixed in
Debian (1.6.17-2).
Since this is fixed in the development release, I'm marking this as Fix
Released.
If you need a fix for an existing stabl
Maybe related https://bugs.launchpad.net/txamqp/+bug/1023327
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to txamqp in Ubuntu.
https://bugs.launchpad.net/bugs/1355056
Title:
Error for send big message
To manage notifications about t
Public bug reported:
Run simple client for send big message:
Output:
$ ./tx-err_big_semd.py
Connected to broker.
Authenticated. Ready to receive messages
Message max length: 131072
Sending message: len=262144 prop: {}
Unhandled Error
Traceback (most recent call last):
File "/usr/lib/python2.7/d
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
I tried to reproduce this by installing the apache2 package on a fresh
Utopic system, which gave me version 2.4.10-1ubuntu1. This gave me no
mention of umask; neither in /etc/apache2/envvars, nor in
/etc/init.d/apa
Hey, sorry for the delay. Unfortunately no, reverting this commit
doesn't help (as suggested in the upstream bug).
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to tmux in Ubuntu.
https://bugs.launchpad.net/bugs/1350810
Title:
Shift-F
My personal suggestion would be to stick with 5.5. in utopic.
You can use master-5.5 branch for that.
People can always use PPAs to update to 5.6 when it's ready (f.e. my
ppa:ondrej/php5-5.6).
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscrib
60 matches
Mail list logo
