** Changed in: irqbalance (Ubuntu)
Status: Incomplete => Invalid
** Converted to question:
https://answers.launchpad.net/ubuntu/+source/irqbalance/+question/273167
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to irqbalance
Horizon is affected because as long as cinderclient <1.4.0, if the user
is logged in with admin permissions, the user lists all cinderbackup
resources instead of the ones of his own tenant, with the reisk of
tampering with ressources from another tenant/user.
** Also affects: horizon
This can be a security issue, because openstack admins may not be aware
that they are seeing other users' cinder backup ressources and can
delete them.
** Information type changed from Public to Public Security
--
You received this bug notification because you are a member of Ubuntu
Server
Yes, Ubuntu version is 14.04. Somehow I didnt notice to use apport-bug,
although I read wiki. I will use it in future.
Here apport-bug's report:
ProblemType: Bug
ApportVersion: 2.14.1-0ubuntu3.17
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Oct 27 09:10:33 2015
Dependencies:
adduser
Public bug reported:
///
ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: nginx-core 1.9.3-1ubuntu1
ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3
Uname: Linux 4.2.0-17-generic x86_64
ApportVersion: 2.19.1-0ubuntu3
Architecture: amd64
Date: Tue Oct 27 17:08:01 2015
ErrorMessage:
*** This bug is a duplicate of bug 344878 ***
https://bugs.launchpad.net/bugs/344878
I found this problem before but i have fixed this easily. There are many
tool available for long path error. I have used Long path tool and it
works great. You can try it. It is easy to fix this error using
You have been subscribed to a public bug by Robie Basak (racb):
https://github.com/hercules-team/augeas/issues/191
Augaes 1.3 can't read certain ssl.conf files, such as one of the ones Let's
Encrypt uses: https://github.com/letsencrypt/letsencrypt/issues/981
versions 1.2 and 1.4 of augaes don't
So, there's still no fix for 12.04 in the standard repos? I mean,
Precise is called "LTS" after all.
--
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/1504781
Title:
lxc-test-ubuntu hangs
Hi Marc,
please check comment #33 from Serge. He explained that formally lxc in precise
is not covered by lts.
However a very special case as a LTS update in main in precise (kernel) did
break unrelated software (lxc) which is a clear regression.
And then not having that other software not in
Not a bug. If you read the systemctl output for the NGINX service or
read the service logs, you will get the information about why your
installation failed: NGINX could not bind to port 80. Check what's
bound to port 80, and turn that service off temporarily while you
install nginx.
** Changed
--- Comment From manju...@in.ibm.com 2015-10-27 09:53 EDT---
Issue is fixed with new build, which has multipath-tools - 0.5.0-7ubuntu7:
root@pearlp5:~# uname -r
4.2.0-16-generic
root@pearlp5:~# dpkg -l |grep -i multipath-tools
ii multipath-tools0.5.0-7ubuntu7
** Also affects: augeas (Ubuntu Wily)
Importance: Undecided
Status: New
** Also affects: augeas (Ubuntu Vivid)
Importance: Undecided
Status: New
** Changed in: augeas (Ubuntu)
Status: New => Triaged
** Changed in: augeas (Ubuntu Vivid)
Status: New => Triaged
** Attachment added: "asterisk_11.7.0~dfsg-1ubuntu1_amd64.build"
https://bugs.launchpad.net/ubuntu/+source/asterisk/+bug/1510099/+attachment/4506523/+files/asterisk_11.7.0%7Edfsg-1ubuntu1_amd64.build
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
This bug was fixed in the package mysql-5.6 - 5.6.27-0ubuntu0.14.04.1
---
mysql-5.6 (5.6.27-0ubuntu0.14.04.1) trusty-security; urgency=medium
* SECURITY UPDATE: Update to 5.6.27 to fix security issues (LP: #1508441)
-
Hi,
I tested this with clean install of Ubuntu 14.04
mkdir src
cd src
sudo apt-get build-dep asterisk
apt-get source asterisk
cd asterisk-11.7.0~dfsg
./configure
make
[CC] res_mutestream.c -> res_mutestream.o
[LD] res_mutestream.o -> res_mutestream.so
[CC] res_odbc.c -> res_odbc.o
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
We can't bump augeas in Vivid and Wily as they are already released, but
it looks like it should be fairly easy to cherry-pick just this fix
without regressing existing users. Is this accurate?
In this case, if
Importance: High because I think it's important to the Ubuntu Server
Team to help ensure that Let's Encrypt works well on Ubuntu. Find me
(rbasak) in #ubuntu-server on Freenode during UK working hours if you
need any help.
** Changed in: augeas (Ubuntu)
Importance: Undecided => High
** Tags
I'm attaching the trio of commits to fix the bug in a single patch,
rebased on top of the upstream 1.3.0 release. Hopefully somebody can
use this as the basis of a patch against the package itself.
Locally it seems to resolve parsing of the ssl.conf file at
Public bug reported:
None
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: mysql-server-5.5 5.5.46-0ubuntu0.14.04.2 [modified:
usr/share/mysql/errmsg-utf8.txt]
ProcVersionSignature: Ubuntu 3.16.0-51.69~14.04.1-generic 3.16.7-ckt17
Uname: Linux 3.16.0-51-generic x86_64
ApportVersion:
With regards to manual regression testing for a stable update, I'd
suggest running "augtool print /files/etc/apache2" (with Apache, mod_ssl
and optionally, other Apache modules installed) to check if any files
that used to parse now fail in any way. Hopefully the number of errors
will be reduced.
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
I am unable to reproduce and successfully test built asterisk 1:11.7.0
~dfsg-1ubuntu1 on Trusty using sbuild. Could it be some issue with your
build environment? See my build log attached.
I'm marking this
** Changed in: ipmitool (Ubuntu)
Assignee: (unassigned) => Taco Screen team (taco-screen-team)
--
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/1509896
Title:
IPMI USB SCSI
The attachment "Patch against upstream release-1.3.0" 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
Hey Stéphane,
I agree that hardcoding the phablet user is not the best way to go about
this. This is really only needed for The Future in which devices use a
kernel that supports unprivileged containers. I think at this juncture,
going about the way where members of a lxc-net group
This bug was fixed in the package augeas - 1.3.0-0ubuntu2
---
augeas (1.3.0-0ubuntu2) xenial; urgency=medium
* Fix parsing of Apache httpd ssl.conf files by cherry-picking three
commits from upstream (LP: #1510318):
- d/p/Httpd-Do-not-pass-empty-as-body-to-section.patch
Public bug reported:
Juju 1.25.0 adds a payload management for charms. The Juju team want
this version of Juju in Xenial and Wily.
[SRU Information]
juju-core has a stable release exception in
https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions,
including for major version
I created a branch for xenial. This is just a forward port of the wily
branch. Only the changelog differs.
** Branch linked: lp:~sinzui/ubuntu/xenial/juju-core/xenial-1.24.7
** Description changed:
Juju 1.24.7 addresses changes happening in AWS and MAAS. AWS deprecated
the m1* instance
Hi
I got a similar error in Ubuntu 15.10, I'll try to upload the crash logs.
--
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/913809
Title:
smbd crashed with SIGABRT in
** Changed in: canonical-devices-system-image
Milestone: ww46-2015 => backlog
--
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/1475751
Title:
need phablet support for mods to
** Changed in: netcf (Ubuntu Xenial)
Status: Triaged => Fix Released
** Changed in: virt-manager (Ubuntu Xenial)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to netcf in Ubuntu.
Thanks - haven't tested, but it certainly makes sense.
status: confirmed
importance: high
** Changed in: lxc (Ubuntu)
Importance: Undecided => High
** Changed in: lxc (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server
I have the same problem with OpenVPN 2.3.8.
The status of the tap interface when calling the up script seems to b seems to
be different from it's status after the initialization of the connection.
** Changed in: openvpn (Ubuntu)
Status: New => Confirmed
--
You received this bug
** Changed in: lsb (Ubuntu)
Importance: Undecided => High
** Changed in: lsb (Ubuntu Utopic)
Importance: Undecided => High
--
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/1273462
Thanks, I've merged this upstream. I may push a new version to xenial
in a few days.
** Changed in: vmbuilder
Status: Invalid => Fix Released
** No longer affects: ubuntu-vm-builder (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
> or just manually grab the .deb files from Xenial and install it on
Wily if you like - that should work
I should add that if you do this you should manually downgrade back to
packages from Wily later, to make sure that you receive any future
security updates.
--
You received this bug
** 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 the bug report.
https://bugs.launchpad.net/bugs/1481388
Title:
NTP : Use-after-free in routing socket code after
I'm also interested by an update of the lxc package for precise.
The attached patch is working for me (add "/dev/pts/ptmx -> /dev/ptmx"
instead of "/dev/pts/ptmx/ -> /dev/ptmx/"). Note that keeping the
previous rule is required for not breaking old kernels.
** Patch added:
I'm trying to come up with a brief test case to SRU this to wily, but
i don't seem to get an error when I do:
sudo ifconfig eth0:0 192.168.99.1 up
sudo ncftool list
sudo ncftool dumpxml eth0:0
Or, at least, no different results than with the patch applied. Can you
show
ifconfig -a
output for
Hi Richard, were you able to test the proposed package? Thanks
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to seabios in Ubuntu.
https://bugs.launchpad.net/bugs/1404396
Title:
[regression] vgabios -> seabios breaks (my) 16-bit
Eric, I've been running the proposed version on many systems and haven't
found any regression. Do you think this would be ready to move on to
-updates now?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
*** This bug is a duplicate of bug 1468611 ***
https://bugs.launchpad.net/bugs/1468611
@paugnu
which ubuntu release are you on and what is your dnsmasq version? (dpkg
-l dnsmasq) Do you have bind installed?
Does creating /etc/dnsmasq.conf fix without having to clear out
/etc/dnsmasq.d/lxc
** Changed in: ipmitool (Ubuntu)
Assignee: Taco Screen team (taco-screen-team) => Mathieu Trudel-Lapierre
(mathieu-tl)
** Changed in: ipmitool (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Public bug reported:
During commissioning the node boots and stops as cloud-init:
[CLOUDINIT] cc_rightscale_userdata.py[DEBUG]: Failed to get raw userdata
in module rightscale_userdata
logs: http://paste.ubuntu.com/12982617/
** Affects: cloud-init (Ubuntu)
Importance: Undecided
** Also affects: lxc (Ubuntu)
Importance: Undecided
Status: New
** Changed in: juju-core
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
I seem to have forgotten. I'll test it today, for sure.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to seabios in Ubuntu.
https://bugs.launchpad.net/bugs/1404396
Title:
[regression] vgabios -> seabios breaks (my) 16-bit
Public bug reported:
automatic error reporting
ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: mysql-server-5.6 5.6.27-0ubuntu1
ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3
Uname: Linux 4.2.0-17-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.19.1-0ubuntu3
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1510671
Title:
package mysql-server-5.6 5.6.27-0ubuntu1 failed to install/upgrade:
Currently looking at updatin lxc package to have lxc-net run After
=network-online.target which should ensure that ifup on auto interfaces
has run, meaning ethX interfaces will have obtained and IP and at that
point then lxc-net can check if something is squating on 10.0.3.X
network and switch to
Complete Pastebin: http://paste.ubuntu.com/12982743/
--
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/1510693
Title:
Cloud-Init 0.7.5 does not work with MAAS 1.9.0 (beta1+bzr4417)
My juju-core 1.25.0 package is based on 1.24.6-0ubuntu3. 1.25.0 contains 16
dependencies changes:
* 2 new go packages, github.com/juju/deputy and gopkg.in/juju/environschema.v1
* 13 update go packages that are unique to juju-core
* 1 package, github.com/juju/loggo, is newer than the the dh-golang
The deb.diff is from 1.24.6-0ubuntu3. I updated the copyright files for
the new revisions. I also reviewed all the dates of the copyrights of the
sources and found changes maybe should have been in the 1.24.6-0ubuntu3
package. Like my concurrent packages for juju-core 1.24.7 I removed the .pc/
dir
The diff of the juju-core 1.25.0 package is from 1.24.6-0ubuntu3. It is
196702 lines long. There are 623 new files, 109 removed files. Most of the
removes are really moves to new locations or other go packages.
** Patch added: "juju-core diff from 1.24.6"
The 1.24.6-0ubuntu3 package in both wily and xenial use:
golang-go-dbus-dev
golang-go.crypto-dev
golang-go.net-dev
golang-juju-loggo-dev
There are/were inompatabilities with some of the other -dev packakages in
wily. The Juju QA team are working on updating packages in Debian to so that
the they
** Patch added: "patch from my vivid git branch"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1457639/+attachment/4507008/+files/aio-strengthen-memory-barriers-for-bottom-half-sched.patch
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Public bug reported:
A common name for bridge interfaces is 'br0'. Currently, the pre-up and
post-down scripts do not support those, so the interaface fails to
autocreate.
Seen on trusty (1.9-3ubuntu10) and confirmed as not fixed on xenial
(1.9-3.2ubuntu1)
** Affects: vlan (Ubuntu)
Public bug reported:
If trying to use a package that relies on python-vm-builder on ppc64el,
it will fail as ppc64el is not in the list of valid architectures
supported by vm-builder (even though ppc64el is a supported Ubuntu
architecture).
** Affects: vm-builder (Ubuntu)
Importance:
On 28/10/15 08:42, dann frazier wrote:
> Sorry for the additional post - I just noticed that @Haw was asking
> about trusty.
>
> As I recall, the issue fixed by the patch I provided was introduced in
> vivid, and was fixed before wily. In other words, only vivid should be
> impacted. I'm
** Branch linked: lp:~sinzui/ubuntu/wily/juju-core/xenial-1.25.0
--
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/1510565
Title:
[needs-packaging] Juju 1.25.0 is not in xenial and
Good evening Chris,
This bug has been brought to my attention by someone in the community.
Unfortunately, I never had a confirmation from him if the fix solve his
issue or not... but as state in comment #5 & #11, I've been able to
reproduce the problem and make sure it addressed the situation.
Public bug reported:
---
ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: cgmanager 0.36-2ubuntu5
ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7
Uname: Linux 3.19.0-31-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.17.2-0ubuntu1.5
AptOrdering:
cgmanager:
Apparently the kernel is now fixed so that we should be able to use the
upstream fix. I'm going to try to get that into the trusty package
rather than keep tweakng this separate patch.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
@Serge: I identified the patch that fixes this - see comment #2.
--
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/1457639
Title:
qemu-img qcow2 conversion hangs on large core systems
Sorry for the additional post - I just noticed that @Haw was asking
about trusty.
As I recall, the issue fixed by the patch I provided was introduced in
vivid, and was fixed before wily. In other words, only vivid should be
impacted. I'm surprised to hear that it impacts trusty.
--
You received
Has anyone who was able to reproduce the original crash tested the
packages from trusty-proposed (or precise or vivid) to check that the
crash is actually fixed?
It's good that it doesn't seem to regress anything, but we also want to
know whether it *fixes* anything :)
--
You received this bug
*** This is an automated message ***
This bug is tagged needs-packaging which identifies it as a request for
a new package in Ubuntu. As a part of the managing needs-packaging bug
reports specification,
https://wiki.ubuntu.com/QATeam/Specs/NeedsPackagingBugs, all needs-
packaging bug reports
** Changed in: docker.io (Ubuntu)
Importance: Undecided => High
--
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/1488668
Title:
ftbfs on wily-ppc64el
To manage notifications about
** Branch linked: lp:byobu
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to byobu in Ubuntu.
https://bugs.launchpad.net/bugs/1503418
Title:
[SRU] [REGRESSION] launching byobu from unity uses the terminal icon
rather than the
** Changed in: docker.io (Ubuntu)
Importance: Undecided => Wishlist
--
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/1488669
Title:
consider building with golang-go on wily-arm64
To
Ceph 0.94.4 is out with important bug fixes, released oct 19. Will it
appear in vivid/wily soon?
v0.94.4 Hammer released
This Hammer point fixes several important bugs in Hammer, as well as
fixing interoperability issues that are required before an upgrade to
Infernalis. That is, all users of
I can confirm that the proposed package fixes the issue. I tested before
the change by rebooting the guest using the stock SeaBIOS, and it was
broken. I installed seabios-1.7.4-4ubuntu1 from trusty-proposed and
rebooted the guest. It works now.
** Tags removed: verification-needed
** Tags added:
** Changed in: byobu (Ubuntu)
Status: Invalid => In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to byobu in Ubuntu.
https://bugs.launchpad.net/bugs/1503418
Title:
[REGRESSION] launching byobu from unity uses the
*** This bug is a duplicate of bug 1503418 ***
https://bugs.launchpad.net/bugs/1503418
Yep. Definitely a bug in 15.10 Wily. This is a duplicate of
https://bugs.launchpad.net/ubuntu/+source/byobu/+bug/1503418
** Changed in: byobu (Ubuntu)
Status: Fix Released => Confirmed
** This
Public bug reported:
Closed unexpectely while install updates
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: mysql-server-core-5.6 5.6.24-2+deb.sury.org~precise+2
ProcVersionSignature: Ubuntu 3.13.0-66.108-generic 3.13.11-ckt27
Uname: Linux 3.13.0-66-generic x86_64
ApportVersion:
This bug was fixed in the package byobu - 5.98-0ubuntu1
---
byobu (5.98-0ubuntu1) xenial; urgency=medium
[ Dustin Kirkland ]
* usr/bin/vigpg:
- specify stdin for input file
* usr/bin/vigpg:
- get vigpg working with the new release of gpg in wily
- clean up encrypted
** No longer affects: qemu (Ubuntu Trusty)
--
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/1457639
Title:
qemu-img qcow2 conversion hangs on large core systems
To manage notifications
** Changed in: samba (Ubuntu Trusty)
Importance: Undecided => High
** Bug watch added: Samba Bugzilla #10896
https://bugzilla.samba.org/show_bug.cgi?id=10896
** Also affects: samba via
https://bugzilla.samba.org/show_bug.cgi?id=10896
Importance: Unknown
Status: Unknown
--
** Also affects: byobu (Ubuntu Wily)
Importance: Undecided
Status: New
** Also affects: bamf (Ubuntu Wily)
Importance: Undecided
Status: New
** Changed in: byobu (Ubuntu Wily)
Status: New => In Progress
** Changed in: byobu (Ubuntu Wily)
Importance: Undecided =>
This SRU has been shadowed by a security update and needs to be re-
merged.
** Changed in: ntp (Ubuntu Precise)
Status: Fix Committed => In Progress
** Changed in: ntp (Ubuntu Trusty)
Status: Fix Committed => In Progress
** Changed in: ntp (Ubuntu Vivid)
Status: Fix
Since this report concerns a possible security risk, an incomplete
security advisory task has been added while the core security reviewers
for the affected project or projects confirm the bug and discuss the
scope of any vulnerability along with potential solutions.
** Also affects: ossa
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mysql-5.6 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.6 in Ubuntu.
** Changed in: lightdm
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1478087
Title:
Add libaudit support
To manage notifications
Good evening Mathew,
Does it mean I need to re-do the debdiffs ?
--
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/1481388
Title:
NTP : Use-after-free in routing socket code after
I think it is probably necessary to rebase the debdiffs on the new
versions in case there are any confilcts. There were a lot of changes as
you can see here http://www.ubuntu.com/usn/usn-2783-1/ .
I don't have direct knowledge of the code though.
--
You received this bug notification because
Thanks Dominic. I've uploaded this to Xenial, which as it is for the
development release I don't have to worry as much about regressing
existing users.
Can someone confirm that the problem with letsencrypt is fixed with
Xenial, please (or just manually grab the .deb files from Xenial and
install
@stefan-huehner - sorry, I'm losing track. is what you are asking for
just a lxc update to precise-proposed with the new apparmor allow rule
that jj suggested?
If so, in comment #33 I was trying to encourage a debdiff to be posted
by someone who could best test it. I'll then sponsor it into the
That's not the correct way build from a Debian or Ubuntu source package.
Use "debian/rules build" or "dpkg-buildpackage". See the documentation.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to asterisk in Ubuntu.
** Attachment added: "asterisk-build.txt"
https://bugs.launchpad.net/ubuntu/+source/asterisk/+bug/1510099/+attachment/4506607/+files/asterisk-build.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to asterisk in Ubuntu.
87 matches
Mail list logo
