Your /usr/bin/python symlink is incorrect. It needs to point to Python
2, as per PEP 394. Otherwise system scripts will fail, because they
expect to find Python 2 there, not Python 3. Have you changed this by
hand?
So this looks like a local configuration problem, rather than a bug in
Ubuntu.
Thank you for your report.
This is something that upstream would need to do, not Ubuntu developers.
So it really belongs in upstream's bug tracker or some kind of
communication upstream, not here. If you want to see this done, you
should speak to upstream.
Since there's nothing we can do for
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
I understand that you have a single use case here, and that you expect this to
just work on 14.04. From the point of view of fixing it though, there are a few
different changes required, which need to be treated
So I think it's a valid concern that this was broken, but the conclusion
is that there's nothing that we can do about it since the choice is to
leave users vulnerable or to break this edge case. Won't Fix seems
appropriate.
** Changed in: bsd-mailx (Ubuntu)
Status: New = Won't Fix
--
You
I find it disconcerting that a security update completely removes
functionality that has been available and expected for many years
without providing a proper compatibility layer. Is this really the way
to do this?
What do you suggest instead?
--
You received this bug notification because you
Relevant links:
http://www.ubuntu.com/usn/usn-2455-1/
http://people.canonical.com/~ubuntu-security/cve/2014/CVE-2014-7844.html
** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7844
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
in this bug.
Landscape team QA: ?TODO
** Affects: juju-core (Ubuntu)
Importance: Undecided
Assignee: Robie Basak (racb)
Status: New
** Affects: juju-core (Ubuntu Trusty)
Importance: Undecided
Assignee: Robie Basak (racb)
Status: New
** Tags: block-proposed
(I had already run my test case on every release prior to preparing my
fix, and verified that they all said Affected. I saw no need to do
this again as the existing packages haven't changed)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
Thank you Simon for your verification.
I have verified all releases (Lucid, Precise, Trusty, Utopic). For
Lucid, I used a VM, as I couldn't get LXC networking to work with it.
For the others, I used LXC.
In each VM or container, I enabled proposed, installed spamassassin, ran
my test case and
Uploaded a fix for Vivid. I'll prepare an SRU for the stable releases
tomorrow.
** Changed in: spamassassin (Ubuntu)
Status: Triaged = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
Blueprint changed by Robie Basak:
Work items changed:
Work items:
NTP on by default (from elmo): TODO
evaluate dpdk (http://dpdk.org/) for inclusion: TODO
update haproxy to latest: DONE
update corosync to latest: TODO
MySQL cleanup in Debian and 5.6 transition: INPROGRESS
Move from
** Attachment added: Test case script
https://bugs.launchpad.net/ubuntu/+source/spamassassin/+bug/1412830/+attachment/4306621/+files/test.sh
** Description changed:
+ [Test Case]
+
+ Run test.sh (attached). This reads testcase (attached) and will print
+ whether spamassassin is affected,
Pierre-Andre has had to unexpectedly be out this week, so I'll take care
of this.
** Changed in: spamassassin (Ubuntu)
Assignee: Kick In (kick-d) = Robie Basak (racb)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report
** Attachment added: Test case email
https://bugs.launchpad.net/ubuntu/+source/spamassassin/+bug/1412830/+attachment/4306620/+files/testcase
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
Lucid)
Assignee: (unassigned) = Robie Basak (racb)
** Changed in: spamassassin (Ubuntu Utopic)
Assignee: (unassigned) = Robie Basak (racb)
** Changed in: spamassassin (Ubuntu Utopic)
Importance: Undecided = Critical
** Changed in: spamassassin (Ubuntu Precise)
Assignee: (unassigned
Uploaded SRUs for Lucid, Precise, Trusty and Utopic. Now awaiting review
from the SRU team.
** Description changed:
+ [Impact]
+
+ spamassassin users have a regression in behaviour in the last month or
+ so. The AHBL DNS check is now returning a false positive. This causes
+ mail to be more
Liam independently investigated and asked me to sync this package over
the weekend. I just verified this and found this bug, so closing this
bug also at the same time.
I can't mark you both as the sponsoree, so I've named Liam as he
initally led me here. I hope that's OK, Jackson. Did you mean to
From log:
Jan 23 08:16:06 kmsubuntu named[6624]: loading configuration from
'/etc/bind/named.conf'
Jan 23 08:16:06 kmsubuntu named[6624]: /etc/bind/named.conf.options:16: missing
';' before '}'
Jan 23 08:16:06 kmsubuntu named[6624]: loading configuration: failure
Jan 23 08:16:06 kmsubuntu
Thank you for your report.
This looks like a local configuration problem, rather than a bug in
Ubuntu.
You can find pointers to get help for this sort of problem here:
http://www.ubuntu.com/support/community
Since we use this bug tracker to track bugs in Ubuntu, rather than
configuration
Done in ubuntu.vivid seed rev 2308.
** Changed in: ldap-auth-client (Ubuntu)
Status: Confirmed = Fix Committed
** Changed in: libnss-ldap (Ubuntu)
Status: Confirmed = Fix Committed
** Changed in: libpam-ldap (Ubuntu)
Status: Confirmed = Fix Committed
--
You received this
** Also affects: python-urllib3 (Ubuntu Trusty)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-urllib3 in Ubuntu.
https://bugs.launchpad.net/bugs/1412545
Title:
proxy isn't used
I believe that sa-update will update the rules correctly in
/var/lib/spamassassin, so after running this users should not be getting
a false positive. Please could someone confirm?
If this is true, I'm not sure whether the right thing to do is an SRU to
disable it for users who don't run
15:37 rbasak ScottK: can I have an opinion from you on bug 1412830 please?
sa-update or SRU?
15:37 ubottu bug 1412830 in spamassassin (Ubuntu) [AHBL] spamassassin is
returning false positives by default [Critical,Confirmed]
https://launchpad.net/bugs/1412830
15:37 ScottK Looking
15:38 ScottK
** Description changed:
[SRU justification]
The version of the library in the archive for Utopic and Trusty has been
built prior to a change in glibc that removes an expected symbol. Rebuild of
the libnss-ldap library with the current source package will render the library
unusable and may
Uploaded to Trusty and Utopic with minor changes as discussed with Louis
on IRC.
Note that I've looked at the patches, but they're too in depth for me to
follow really. Superficially they look fine, and Debian have also
included them so they're in Vivid, and so I think this is sufficient
provided
Please don't change the bug status without an explanation. I marked this
bug as Invalid and I explained why. Leaving it as Confirmed just sets
false expectations to other readers that this bug might be fixed some
day, when it won't be.
--
You received this bug notification because you are a
Blueprint changed by Robie Basak:
Work items changed:
Work items:
NTP on by default (from elmo): TODO
evaluate dpdk (http://dpdk.org/) for inclusion: TODO
- update haproxy to latest: INPROGRESS
+ update haproxy to latest: DONE
update corosync to latest: TODO
MySQL cleanup in Debian
Blueprint changed by Robie Basak:
Work items changed:
Work items:
NTP on by default (from elmo): TODO
evaluate dpdk (http://dpdk.org/) for inclusion: TODO
update haproxy to latest: INPROGRESS
update corosync to latest: TODO
- MySQL cleanup in Debian and 5.6 transition: TODO
+ MySQL
Blueprint changed by Robie Basak:
Work items changed:
Work items:
NTP on by default (from elmo): TODO
evaluate dpdk (http://dpdk.org/) for inclusion: TODO
- update haproxy and corosync to latest: TODO
+ update haproxy to latest: INPROGRESS
+ update corosync to latest: TODO
MySQL cleanup
Update. I've added a dep8 smoke test to juju-quickstart in Vivid, but it
is failing due to a proxy error - something to do with the environment
it runs in: https://jenkins.qa.ubuntu.com/job/vivid-adt-juju-
quickstart/ARCH=amd64,label=adt/lastBuild/
I'll need to investigate this next, but I'm
Public bug reported:
On Vivid:
juju-quickstart 1.4.2-0ubuntu1
juju-core 1.20.11-0ubuntu1 (installed by juju-quickstart)
Steps to reproduce:
sudo apt-get install juju-quickstart on a Vivid cloud image.
Run juju-quickstart as the ubuntu user
Choose to bootstrap a local environment
Presumably this is related to the DHCP client via dhclient and dhclient-
script, so presumably should be a task on isc-dhcp?
I see code in dhclient-script that sets the MTU based on the DHCP
option, but it doesn't have any special behaviour for br0. So I'm
wondering if this code is being used at
** Changed in: bind9 (Ubuntu)
Status: New = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/1405075
Title:
Sync bind9 1:9.9.5.dfsg-7 (main) from Debian unstable
This bug was fixed in the package bind9 - 1:9.9.5.dfsg-8
Sponsored for Artur Rona (ari-tczew)
---
bind9 (1:9.9.5.dfsg-8) unstable; urgency=medium
* Launch rndc command in the background in networking scripts to avoid a
hang in named from bringing down the entire network
Verified libgo5 4.9.1-0ubuntu1 was used using arm64 and ppc64el build
logs. I presume a full SRU verification of the original failure case
isn't needed here because this SRU is an MRE.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification
Verified that dbus now correctly appears in dependencies for juju-local
and juju-local-kvm in trusty-proposed. My LXC cloud image already has
dbus installed, but I think it's trivial enough to consider verified.
** Tags removed: verification-needed
** Tags added: verification-done
--
You
** 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
Scott,
Thank you for all the work you've put into postfix and clamav on Ubuntu.
On Fri, Dec 12, 2014 at 02:29:38PM -0500, Scott Kitterman wrote:
I do think that for the Ubuntu Server community, it's important that
the work be done and I'd be glad to help bring someone up to speed on
what
** Changed in: libnss-ldap (Ubuntu)
Importance: Undecided = High
** Changed in: libnss-ldap (Ubuntu)
Status: New = Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Is Ubuntu the place to offer such fixes?
It should go to Debian in the first instance, assuming that Debian is
also affected - in Ubuntu, we try to keep the packaging in sync with
Debian.
** Changed in: puppet
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
It may be running before hostname resolution is available.
Then isn't something else broken that causes puppet to be started before
hostname resolution is available? What is on your system that causes
hostname
Thank you for taking the time to file this bug and helping to make
Ubuntu better.
I cannot reproduce this on Trusty. Additionally, I don't see that the
openssh-server or openssh-client binary packages pull in gcrypt at all.
Are you sure this isn't some PAM module that uses gcrypt that ssh is
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Sounds like this is a wishlist item that needs to go upstream in the
first instance.
** Package changed: cloud-init (Ubuntu) = cloud-init
--
You received this bug notification because you are a member of Ubuntu
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Has this patch gone upstream at all, please? We'd prefer to not have to
maintain patches indefinitely.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Thanks Norvald. I've subscribed the SRU team to this bug for their
attention. Since this type of request is quite unusual we don't really
have an existing process for it, so please chase this up with me if you
don't get a response soon and I can follow up.
--
You received this bug notification
What is it trying to look up? Itself, or something else? I'd expect a
self-lookup to always succeed.
If for some reason it does need to hit the network in the typical case,
then I agree that a timeout may make sense. In this case, I suggest
going to upstream to implement proper retry
** Tags added: upgrade-software-version
--
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/1395098
Title:
[Utopic] OpenLDAP version is outdated
To manage notifications about this bug
2.4.10-8ubuntu1 is now in vivid-proposed and should fix this bug for
Vivid and for future releases, but it won't land in Vivid itself until
bug 1393832 is fixed. I'd like to focus on this SRU before working on
that bug.
Alex, could you please verify that the bug is fixed in vivid-proposed
for
i386 now accepted into trusty-proposed. Thanks Steve!
--
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
Title:
juju-core 1.20.11 is not packaged in Ubuntu
To manage notifications about this
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
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
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
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
Thanks Alex. I'm sorry I've been slow. I'm still not back at work as
normal but I'll try to look at this now.
Just to log what I've seen so far:
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
Thanks Dean! Note quite verification-done yet though - we have a couple
of other verifications we need to do first (tracked in bug whiteboard).
** Tags removed: verification-done
** Tags added: verification-needed
--
You received this bug notification because you are a member of Ubuntu
Server
** 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
* Provide a new, debian specific, default landing page.
Does this need making into an Ubuntu-specific page like in bug 1288690?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
On Thu, Oct 30, 2014 at 10:09:53PM +, Serge Hallyn wrote:
Does this seem sensible? Any suggestions/alternatives are
appreciated.
Is it possible to have a lowest common denominator LTS machine type
that is long term stable and doesn't need to change or be deprecated
between releases? Or is
Any chance this can now be backported to Trusty? The impact is pretty
severe.
It sounds like a good candidate, though I haven't reviewed the patch
yet. I'm away at the moment, so if somebody else wants to work on this
in the meantime, please feel free. The process is documented at
: (unassigned) = Robie Basak (racb)
** Changed in: juju-core (Ubuntu Trusty)
Status: New = In Progress
--
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/1343301
Title:
juju-local
Uploaded to vivid-proposed and trusty-proposed. Vivid is ready for
testing now. Trusty is pending SRU team approval.
--
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
Title:
juju-core 1.20.11
** Package changed: juju-quickstart (Ubuntu) = juju-quickstart
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-quickstart in Ubuntu.
https://bugs.launchpad.net/bugs/1385407
Title:
juju-quickstart destroys existing AWS
Public bug reported:
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
their stable
= Triaged
** Changed in: juju-core (Ubuntu)
Importance: Undecided = High
** Changed in: juju-core (Ubuntu Trusty)
Importance: Undecided = High
** Changed in: juju-core (Ubuntu)
Assignee: (unassigned) = Robie Basak (racb)
** Changed in: juju-core (Ubuntu Trusty)
Assignee: (unassigned
Can you provide steps to reproduce, please? Does it occur on Utopic or
on the latest upstream PHP release? If there has been an upstream fix,
identifying it so that we can cherry-pick it would be great.
Given the memory corruption, this may well be a security issue.
Please note that php5-fpm is
Blueprint changed by Robie Basak:
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
You shouldn't be using juju-mongodb for anything but Juju. AIUI, the
security team don't support it for security updates for any other
purpose.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mongodb in Ubuntu.
Although that was the plan, it occurs to me that juju-mongodb never
entered main. So perhaps I am mistaken.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mongodb in Ubuntu.
https://bugs.launchpad.net/bugs/1381967
Title:
mongodb
I'd like to seed ntp in both server and cloud-image in Vivid. Servers
should maintain the correct time by default. Please make any objections
now.
Right now, ntpdate is seeded in minimal. It makes little sense to have
both ntpdate and ntp installed.
So is there some mechanism I can use to have
I should add some more related links:
Debian making NTP happen by default too is being discussed in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731594. openntpd was
suggested, but this effort seems to have languished, and in Ubuntu we
have ntp in main, not openntpd.
An ntpdate issue in
** Information type changed from Public to Public Security
** Tags added: poodle
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to haproxy in Ubuntu.
https://bugs.launchpad.net/bugs/1383704
Title:
Can't switch off SSLv3 cipher groups
** Tags added: poodle
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dovecot in Ubuntu.
https://bugs.launchpad.net/bugs/1381537
Title:
Dovecot version in precise too old to switch off SSLv3 protocol for
poodle fix
To manage
** Tags added: poodle
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1383379
Title:
nginx default config has SSLv3 enabled, makes sites using default
config options vulnerable to
Thanks Ante. Though this is a regular update, not a security one.
** Summary changed:
- Security update breaks pacemaker in 14.04
+ SRU breaks pacemaker in 14.04
** Tags added: regression-update
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Public bug reported:
[Impact]
maas-cluster-controller cannot be installed on a non-Intel system at
all. So, for example, a ppc64el cluster cannot be managed by a MAAS that
is running on ppc64el.
If we drop the dependency on syslinux-common for non-Intel
architectures, then this would work
Thank you for the patch!
Unfortunately using rsync's internal zlib violates policy section 4.13
(see in particular footnote 31 for rationale):
http://people.canonical.com/~cjwatson/ubuntu-policy/policy.html/ch-
source.html#s-embeddedfiles
For example: if a security vulnerability were found in
** Changed in: maas (Ubuntu)
Status: New = Triaged
--
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/1382250
Title:
If IP address of interface doesn't match cluster UI, DHCP fails
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information.
Example: no versions of anything reported, and you haven't stated what
release your report relates to.
If you
Thank you for your report.
This looks like a local configuration problem, rather than a bug in
Ubuntu.
Your supplied XML contains on_poweroffdestroy/on_poweroff. Your VM
got destroyed on shutdown because this is what you requested.
You can find pointers to get help for this sort of problem
*** This bug is a duplicate of bug 1348972 ***
https://bugs.launchpad.net/bugs/1348972
** This bug has been marked a duplicate of bug 1348972
Default address space limit is too small for some PAM modules
--
You received this bug notification because you are a member of Ubuntu
Server
I had a quick discussion with mdeslaur (security team) on #ubuntu-
hardened.
He's not prepared to push changes which just turn SSLv3 off, since that
would break clients. But he is prepared to sponsor security patches that
add it as an option, so that users can opt to turn SSLv3 off after
they've
** Changed in: munin (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to munin in Ubuntu.
https://bugs.launchpad.net/bugs/1381939
Title:
Error in cron logrotate 'gzip: stdin: file size changed
Fix waiting in Utopic unapproved.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-greenlet in Ubuntu.
https://bugs.launchpad.net/bugs/1379297
Title:
python-greenlet ftbfs on ARM32
To manage notifications about this bug go
Thanks. Looks like 2.0.3 is tagged upstream but not yet released.
It would be easiest to fix this in Debian and then sync (looks like a
bugfix only release, with test suite additions, so it seems pretty
safe).
But to make Utopic before release, we need to cherry-pick the fix, or
pull in 2.0.3
Hopefully 12.04 and wheezy both get pygrub updates to support 14.04
domUs.
A backport[0] or SRU[1] is probably suitable here (I'm not sure which).
Volunteers welcome. For a first step, we need to understand what version
of pygrub is needed, or what patch needs to be backported.
[0]
** Changed in: cloud-init (Ubuntu)
Importance: Undecided = Medium
--
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/1379080
Title:
update-grub-legacy-ec2 fails to detect xen
** Changed in: irqbalance (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to irqbalance in Ubuntu.
https://bugs.launchpad.net/bugs/1379065
Title:
Ubuntu 14.04.1: irqbalance not working
To
Public bug reported:
Symbols file mismatch: https://launchpad.net/ubuntu/+archive/test-
rebuild-20140914/+build/6371580/+files/buildlog_ubuntu-
utopic-i386.libecap_0.2.0-1ubuntu4_FAILEDTOBUILD.txt.gz
The attached patch fixes it, but I'm not comfortable uploading since I
don't see how I can
** Changed in: libecap (Ubuntu)
Status: Triaged = In Progress
** Changed in: libecap (Ubuntu)
Assignee: (unassigned) = Robie Basak (racb)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libecap in Ubuntu.
https
Public bug reported:
The latest libelf removed DW_TAG_mutable_type in upstream commit
af1e6ed9b4c0160a6a5c6f59d9443ae4f6f20a14, causing an FTBFS on Utopic
(Trusty still builds).
** Affects: dwarves-dfsg (Ubuntu)
Importance: Undecided
Assignee: Robie Basak (racb)
Status
13:53 rbasak doko: sorry, I'm still not comfortable with this. I don't really
follow the bigger picture of how to determine that these symbols really aren't n
eeded.
13:53 rbasak The package includes all the headers, which makes it
awkward.
13:54 rbasak doko: if you're happy with my diff, then
** Bug watch added: Debian Bug tracker #764484
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764484
** Also affects: dwarves-dfsg (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764484
Importance: Unknown
Status: Unknown
--
You received this bug notification
** Changed in: apache2 (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
https://bugs.launchpad.net/bugs/1377827
Title:
Apache reload fails silenty when not run as sudo
To
Thank you for the note, Brandon. This should be very useful to other
users.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in Ubuntu.
https://bugs.launchpad.net/bugs/1273225
Title:
php5enmod - priority is not set by argument
** Summary changed:
- service slapd stop fails
+ Reading /proc/$(pidof slapd)/exe fails inside a docker container
--
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/1376548
Title:
Assuming this affects 1.18.4 in Trusty, adding a task to track that.
** Also affects: juju-core (Ubuntu)
Importance: Undecided
Status: New
** Also affects: juju-core (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: juju-core (Ubuntu)
Status: New = Fix
Upload blocked by bug 1374335. juju-quickstart 1.4.4 needs python-
websocket = 0.18 and python-jujuclient = 0.18.4.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-quickstart in Ubuntu.
https://bugs.launchpad.net/bugs/1359938
Upload blocked by bug 1374335. juju-quickstart 1.4.4 needs python-
websocket = 0.18 and python-jujuclient = 0.18.4.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-quickstart in Ubuntu.
https://bugs.launchpad.net/bugs/1359944
juju-quickstart also needs python-websocket = 0.18 and python-
jujuclient = 0.18.4 in bug 1359938 and bug 1359944.
** Also affects: juju-quickstart (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
From #juju on Freenode:
11:04 frankban rbasak: I think we need to bump the version of the
dependencies. unfortunately the expected topic version of websocket-
client includes backward incompatible changes, so we needed to reflect
those changes
[...]
11:17 frankban rbasak: the public API of
1301 - 1400 of 3424 matches
Mail list logo
