There are unlikely many to have proposed enabled generally. So based on
the feedback of Simon (thanks!) and the regression testing I did, I am
marking the verification as done,
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because
You have been subscribed to a public bug:
Unfortunately pax is useless since not POSIX conform. The following
command should work, but doesn't:
cd /etc/skel sudo pax -rwLlk -o gid=118 -o uid=118 . /home/test
see http://pubs.opengroup.org/onlinepubs/9699919799/utilities/pax.html
** Affects:
** Package changed: ubuntu = pax (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pax in Ubuntu.
https://bugs.launchpad.net/bugs/1393611
Title:
pax is not POSIX compliant
To manage notifications about this bug go to:
This still happens on Ubuntu 12.04 (up to date with patches) connecting to an
Exchange 2010 server,
using the 'mutt' package, version 1.5.21-5ubuntu2.1. It happens often enough
that mutt is effectively unusable. I can post my configuration on request. The
mutt in package 'mutt-patched', same
For what it's worth: the same problem exists with Cygwin's mutt, so it
looks like this needs to be fixed upstream.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to exim4 in Ubuntu.
https://bugs.launchpad.net/bugs/105736
Title:
mutt -
** Branch linked: lp:tinco-vm-builder/virtio-uuid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vm-builder in Ubuntu.
https://bugs.launchpad.net/bugs/517067
Title:
Using virtio for block devices makes disks and partitions
Incidentally: setting imap_keepalive to a small value does not make any
difference for me.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to exim4 in Ubuntu.
https://bugs.launchpad.net/bugs/105736
Title:
mutt - TLS packet with
Karmic has long since stopped to receive any updates. Marking the Karmic
task for this ticket as Won't Fix.
** Changed in: nbd (Ubuntu Karmic)
Status: New = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nbd in
Looks like Vivid will need to either cherry-pick this, or a merge may be
sufficient
since your message says you picked r1629372, r1629485, r1629519 and Debian
2.4.10-6 reports to have picked everything up to r1632831 but I need to check
this.
The commits mentioned by Alex are in the trunk
Karmic has long since stopped to receive any updates. Marking the Karmic
task for this ticket as Won't Fix.
--
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/513727
Title:
Samba 3.4
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: grub2 (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vm-builder in Ubuntu.
Karmic has long since stopped to receive any updates. Marking the Karmic
task for this ticket as Won't Fix.
--
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/513727
Title:
Samba 3.4
Karmic has long since stopped to receive any updates. Marking the Karmic
task for this ticket as Won't Fix.
** Changed in: samba (Ubuntu Karmic)
Status: New = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in
Karmic has long since stopped to receive any updates. Marking the Karmic
task for this ticket as Won't Fix.
** Changed in: samba (Ubuntu Karmic)
Status: New = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in
You have been subscribed to a public bug:
There is no qemu-kvm for ppc64el:
http://ports.ubuntu.com/ubuntu-ports/pool/main/q/qemu-kvm/
I discovered that after pick Virtual Machine Host in the installer I got the
following error:
Nov 14 14:45:38 in-target: xml-core set to manually installed.
Nov
Karmic has long since stopped to receive any updates. Marking the Karmic
task for this ticket as Won't Fix.
** Changed in: image-store-proxy (Ubuntu Karmic)
Status: New = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
Yes, the new “pax” archive format, and some of the new -o options, are
not supported. This utility is compatible with an older version of
POSIX.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pax in Ubuntu.
Looking at x86. qemu-kvm contains files for SPICE qemu, as you can see:
# dpkg -L qemu-kvm
/.
/usr
/usr/bin
/usr/share
/usr/share/doc
/usr/share/doc/qemu-kvm
/usr/share/doc/qemu-kvm/NEWS.Debian.gz
/usr/share/doc/qemu-kvm/copyright
/usr/bin/kvm-spice
/usr/bin/qemu-system-x86_64-spice
Ubuntu 8.04 (Hardy) is EOL.
** Changed in: radiusclient (Ubuntu Hardy)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to radiusclient in Ubuntu.
https://bugs.launchpad.net/bugs/219299
Title:
FTBFS in
Public bug reported:
Two parts of the juju-core test suite panic or segfault when run with
-compiler gccgo on amd64.
Some examples, in provider/openstack:
ubuntu@go:~/go/src/github.com/juju/juju$ (cd provider/openstack/ go test
./... -compiler gccgo -gocheck.v -v)
3
=== RUN Test
...
PASS:
qemu-kvm does exist for ppc64el:
http://ports.ubuntu.com/pool/main/q/qemu/
qemu-kvm is a different source tree which was used through 12.10.
** Changed in: qemu-kvm (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server
** Branch linked: lp:cloud-init
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1355343
Title:
cloud-init writes sources.list without newline at end of file
To manage
fixed in revno 1033
** Changed in: cloud-init
Status: Confirmed = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1355343
Title:
cloud-init writes
Public bug reported:
This is related to Debian bug 745834 and Launchpad bug 1312854, which
Stefan kindly fixed in http://anonscm.debian.org/cgit/pkg-
apache/apache2.git/commit/?id=804b53b7d5901e47c2751cdf78908ccd9c594c5b
that went into 2.4.10-3 that I merged in 2.4.10-7ubuntu1 that is now
stuck
--- Comment From thierry.fa...@fr.ibm.com 2014-11-18 15:49 EDT---
We have found the issue - On a bare LE system, nodes are name 0, 1 , 16 , 17
and the library search for these nodes for the meminfo file however it search
for nodes 0, 1, 2 for the cpumap file.
On a VM started by qemu, the
Thanks Stefan, I didn't consider that.
I started with a merge of 2.4.10-7 that's now stuck in vivid-proposed
due to bug 1393832 which I've just filed. I could re-merge 2.4.10-8
though, and then continue with the SRU - no need to block the SRU on
this.
--
You received this bug notification
--- Comment on attachment From thierry.fa...@fr.ibm.com 2014-11-18 15:55
EDT---
Please have a test
** Attachment added: new libnuma.so with fix
https://bugs.launchpad.net/bugs/1358835/+attachment/4263037/+files/libnuma1_2.0.9%7Erc5-1ubuntu2_ppc64el.deb
--
You received this bug
Theres probably a charm bug here as well as after discussion it turns
out upgrading the hacluster charm also updates the pacemaker package
with the security update; this is not intended behaviour.
** Also affects: hacluster (Juju Charms Collection)
Importance: Undecided
Status: New
--
Hello Jorge, or anyone else affected,
Accepted nova into trusty-proposed. The package will build now and be
available at
http://launchpad.net/ubuntu/+source/nova/1:2014.1.3-0ubuntu2 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
I tried building 1.17.21 from Debian on Vivid, downgrading to that, and
I still get the same (different) behaviour on Vivid. So it seems that it
isn't directly a dpkg version difference, but perhaps something else
different in Ubuntu (or dpkg configuration?) that is causing this
difference in
--- Comment on attachment From thierry.fa...@fr.ibm.com 2014-11-18 15:55
EDT---
Please have a test
** Attachment added: new libnuma.so with fix
https://bugs.launchpad.net/bugs/1358835/+attachment/4263072/+files/libnuma1_2.0.9%7Erc5-1ubuntu2_ppc64el.deb
--
You received this bug
--- Comment From thierry.fa...@fr.ibm.com 2014-11-18 16:45 EDT---
Sent patch to the community:
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to numactl in Ubuntu.
https://bugs.launchpad.net/bugs/1358835
Title:
Hello Haw, or anyone else affected,
Accepted pollen into utopic-proposed. The package will build now and be
available at http://launchpad.net/ubuntu/+source/pollen/4.13-0ubuntu1 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Marking verification-failed due to comment #2.
** Tags removed: verification-needed
** Tags added: verification-failed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pollen in Ubuntu.
https://bugs.launchpad.net/bugs/1386052
Title:
Linked Vivid branch, Edited bug description for SRU. Attached Trusty
patch.
** Tags added: cts
** Branch linked: lp:~niedbalski/ubuntu/vivid/squid3/fix-pinger-icmp
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid3 in Ubuntu.
** Branch linked: lp:ubuntu/utopic-proposed/pollen
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pollen in Ubuntu.
https://bugs.launchpad.net/bugs/1386052
Title:
pollen fails to log everytime rsyslog package is upgraded or daemon
** Description changed:
+ [Description]
+
+ Malformed ICMP packets were accepted into processing with undefined
+ and potentially nasty results.
+
+ Both sets of flaws can result in pinger segmentation fault and halting
+ the Squid functionality relying on pinger for correct operation.
+
+ A
Marked as affecting the kernel given tha last few commits - thank you
for the information.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
** Description changed:
[Description]
Malformed ICMP packets were accepted into processing with undefined
and potentially nasty results.
Both sets of flaws can result in pinger segmentation fault and halting
the Squid functionality relying on pinger for correct operation.
A
This bug is missing log files that will aid in diagnosing the problem.
From a terminal window please run:
apport-collect 1379340
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a
Fix proposed to branch: master
Review: https://review.openstack.org/135382
** Changed in: nova
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
** Patch added: lp1384943_fix_icmp_trusty.debdiff
https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1384943/+attachment/4263140/+files/lp1384943_fix_icmp_trusty.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid3 in
** Summary changed:
- Pinger crashes with segfault in libc
+ [sru] Pinger crashes with segfault in libc
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid3 in Ubuntu.
https://bugs.launchpad.net/bugs/1384943
Title:
[SRU] Pinger
** Summary changed:
- [sru] Pinger crashes with segfault in libc
+ [SRU] Pinger crashes with segfault in libc
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid3 in Ubuntu.
https://bugs.launchpad.net/bugs/1384943
Title:
[SRU]
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: squid3 (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid3 in Ubuntu.
--- Comment on attachment From thierry.fa...@fr.ibm.com 2014-11-18 15:55
EDT---
Please have a test
** Attachment added: new libnuma.so with fix
https://bugs.launchpad.net/bugs/1358835/+attachment/4263182/+files/libnuma1_2.0.9%7Erc5-1ubuntu2_ppc64el.deb
--
You received this bug
--- Comment From t...@us.ibm.com 2014-11-18 19:13 EDT---
Hi,
Are you sure the fix is in the new libnuma.so.1?
I copied it to our node and re-tested it. I didn't see any difference.
The test still failed.
root@c656f2n01:/usr/lib/powerpc64le-linux-gnu# sum libnuma.so.1
libnuma.so.1.orig
Public bug reported:
[Description]
In versions of ipmitool earlier than 1.8.14, setting the boot device to
PXE does not work correctly. (You have to reboot within 60 seconds for
it to apply - and that only works for some corner cases.)
With this patch, bootflag options can be set or cleared
** Patch added: lp1393918_bootflags_trusty.diff
https://bugs.launchpad.net/ubuntu/+source/ipmitool/+bug/1393918/+attachment/4263201/+files/lp1393918_bootflags_trusty.diff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ipmitool in
** Branch linked: lp:ubuntu/squid3
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid3 in Ubuntu.
https://bugs.launchpad.net/bugs/1384943
Title:
[SRU] Pinger crashes with segfault in libc
To manage notifications about this bug
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ipmitool (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ipmitool in Ubuntu.
** Also affects: squid3 (Ubuntu Trusty)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid3 in Ubuntu.
https://bugs.launchpad.net/bugs/1384943
Title:
[SRU] Pinger crashes with segfault
Public bug reported:
Versions:
Ubuntu 14.04.1 LTS
postfix:amd64 2.11.0-1
postfix-ldap:amd64 2.11.0-1
libldap-2.4-2:amd64 2.4.31-1+nmu2ubuntu8
libgnutls26:amd64 2.12.23-12ubuntu2.1
libp11-kit0:amd64 0.18.3-2ubuntu1 (works)
libp11-kit0:amd64
Hi
I have the same problem but I'm on Ubuntu 14.04, our DFS is on Windows
2008 R2. Do you still have this problem like me?
--
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/738968
Title:
** Branch linked: lp:ubuntu/ipmitool
** Tags added: cts
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ipmitool in Ubuntu.
https://bugs.launchpad.net/bugs/1393918
Title:
[SRU] Add ability to set BMC boot flag valid bit clearing to
** Also affects: ipmitool (Ubuntu Trusty)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ipmitool in Ubuntu.
https://bugs.launchpad.net/bugs/1393918
Title:
[SRU] Add ability to set BMC
Private bug reported:
The overall upgrade completed, but these failed.
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: apache2 2.2.22-1ubuntu1.7
ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
Uname: Linux 3.13.0-39-generic i686
Apache2ConfdDirListing:
** Changed in: qemu (Ubuntu)
Assignee: (unassigned) = Chris J Arges (arges)
** Changed in: qemu (Ubuntu)
Status: New = In Progress
** Also affects: qemu (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Trusty)
Importance: Undecided
Hi, could you provide the exact command used to launch qemu to produce this
error? If using libvirt, you can find this in /var/log/libvirt/qemu/name.log
if using virsh for example.
Thanks,
--chris
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
** Description changed:
juju-core 1.20.11 is proposed for release upstream.
We're now in a position to have this enter trusty-proposed and vivid-
proposed, but it should not land in trusty-updates or vivid until
upstream passes QA on our proposed binaries, published 1.20.11 tools in
Vivid testing is complete. It is suitable for local development and for
deploying to clouds.
Trusty testing is blocked by the missing juju-local package for 14.14.
The vivid local package can be forced to install, but it depends on
juju-core = 1.20.11-0ubuntu1, but the trusty backport is
Thanks Curtis!
i386 is blocked on Trusty binNEW. I've asked Steve to review this for
us, but I'm not sure when he'll be able to get to it.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is a bug assignee.
https://bugs.launchpad.net/bugs/1386144
Julian: The patch I submitted fixed my problem (see #13 above).
Unfortunately I don't have time tonight to try to reproduce the
situation, and indeed I may not be able to (I'm not sure I have access
to the server anymore). But I can definitely confirm that it was still
fixed in LinuxMint 13
Reading the upstream bug associated with #1381743, I wonder if it might
be related?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to postfix in Ubuntu.
https://bugs.launchpad.net/bugs/1393923
Title:
postfix (2.11.0-1) does not LDAP
** Attachment added: ThreadStacktrace.txt
https://bugs.launchpad.net/bugs/1393110/+attachment/4263481/+files/ThreadStacktrace.txt
** Attachment removed: CoreDump.gz
https://bugs.launchpad.net/bugs/1393110/+attachment/4261567/+files/CoreDump.gz
** Changed in: celery (Ubuntu)
** Attachment added: Stacktrace.txt
https://bugs.launchpad.net/bugs/1393110/+attachment/4263479/+files/Stacktrace.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to celery in Ubuntu.
https://bugs.launchpad.net/bugs/1393110
Title:
** Attachment added: StacktraceSource.txt
https://bugs.launchpad.net/bugs/1393110/+attachment/4263480/+files/StacktraceSource.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to celery in Ubuntu.
StacktraceTop:
amqp_pool_alloc (pool=0x2467720, amount=38693072) at
/build/buildd/librabbitmq-0.4.1/librabbitmq/amqp_mem.c:164
PyDict_ToAMQTable (conn=0x2467720, src=0x7ffcc724e280) at
Modules/_librabbitmq/connection.c:228
PyRabbitMQ_Connection_queue_declare (self=0x7ffcc72c89e0,
68 matches
Mail list logo
