I have reproduced the issue again on a fresh Trusty cloud image. It
reproduces reliably just by removing the ubuntu user first. Exact
reproduction steps below.
Juju requires the machines it provisions to have an ubuntu user.
That's fine, but Juju must not assume that the local user has an
No, I'm saying that whatever QA we're doing on Juju, we must test the
local provider in an environment that specifically does *not* have an
ubuntu user defined. I presume this is not the case, since bug 1328958
slipped through.
** Changed in: juju-core
Status: Incomplete = New
--
You
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
** Changed in: autofs5 (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to autofs5 in Ubuntu.
https://bugs.launchpad.net/bugs/1332203
Title:
autofs5-ldap regularly crashes after long periods of
I came across this on Trusty using ppa:juju/stable :
$ dpkg-query -W juju-core juju-local
juju-core 1.18.4-0ubuntu1~14.04.1~juju1
juju-local 1.18.4-0ubuntu1~14.04.1~juju1
So on Trusty, an ordinary user's desktop will not have an ubuntu user,
and the local environment is completely
My steps to reproduce on a Trusty cloud image (off the top of my head -
let me know if you have any problems):
1. sudo adduser --disabled-password --gecos '' otheruser
2. echo 'otheruser ALL=(ALL) NOPASSWD:ALL'|sudo tee --append /etc/sudoers
3. sudo add-apt-repository ppa:juju/stable
4. sudo
Filed bug 1332820 for test coverage.
--
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/1328958
Title:
Local provider assumes a local ubuntu user exists
To manage notifications
dep8 testing in archive packaging should also test this correctly.
** Also affects: juju-core (Ubuntu)
Importance: Undecided
Status: New
** Changed in: juju-core (Ubuntu)
Status: New = Triaged
** Changed in: juju-core (Ubuntu)
Importance: Undecided = High
** Summary
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
/proc/interrupts exists on all Ubuntu systems. It seems to me that
you're running some kind of modified version of Ubuntu if you don't have
one. I suggest that you take this up with your hosting provider.
Since
Hi,
(I looked to include the nagios-plugins fork in this email also, but was
unable to find a suitable mailing list)
For people following the Ubuntu Server list, note that this relates to
our nagios-plugins source package.
I submitted
** Description changed:
1.18.4 contains essential fixes that need to land in Trusty.
+
+ Changes extracted from bzr for 1.18.1 Trusty (currently in Trusty) to
+ 1.18.4:
+
+
+ revno: 2272 [merge]
+ author: John Arbash Meinel
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
According to the upstream bug, this feature was added by 2.4.9, which is
the version currently in Utopic, so I'm marking this bug as Fix Released
for the current development release of Ubuntu.
Please include
Thanks Kees. Presumably this breaks dynamic updates?
--
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/1331503
Title:
apparmor profile missing link permission
To manage notifications
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
It sounds like this fix is suitable to be backported.
Please see https://wiki.ubuntu.com/StableReleaseUpdates#Procedure for
the process. Are you able to complete these steps, please?
** Summary changed:
- nose
*** 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
Blueprint changed by Robie Basak:
Work items changed:
Work items for ubuntu-14.06:
mongodb 2.6 into Utopic (need to evaluate version of libv8 to include): TODO
address automated testing gaps for PXC: TODO
submit for MRE for PXC 5.5 for 14.04: TODO
+
+ Work items for ubuntu-14.07:
+ [racb
Public bug reported:
https://launchpad.net/ubuntu/+source/juju-
core/1.18.4-0ubuntu1/+build/6076908
All other architectures are OK, including ppc64el. I cannot reproduce on
a porter box. infinity has reproduced and reports that a build on Trusty
is OK, but Utopic fails.
Creating this bug to
Stuck in utopic-proposed due to bug 1329295.
** Changed in: juju-core (Ubuntu)
Status: In Progress = Fix Committed
--
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/1325025
Stuck in utopic-proposed due to bug 1329295.
** Changed in: juju-core (Ubuntu)
Status: In Progress = Fix Committed
--
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/1314686
Stuck in utopic-proposed due to bug 1329295.
** Changed in: juju-core (Ubuntu)
Status: In Progress = Fix Committed
--
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/1321025
Public bug reported:
1.18.4 contains essential fixes that need to land in Trusty.
** Affects: juju-core (Ubuntu)
Importance: High
Assignee: Robie Basak (racb)
Status: Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
Blueprint changed by Robie Basak:
Work items changed:
Work items:
Provide Juju 2.x in Trusty: TODO
+ Land juju-core update in Utopic: TODO
+ Land juju-quickstart update in Utopic: TODO
--
Server team specific Juju work for Utopic
https://blueprints.launchpad.net/ubuntu/+spec/servercloud-u
I mentioned in the Server Security QA session yesterday that I had, for
example, an AppArmor profile for radicale that constrains radicale to
access only the calendar files that it serves.
Since radicale is in universe, this provides some mitigation to a
security update not arriving timely.
Will Ubuntu fix the package, or does it need to be done by the Debian
maintainer?
Whether it needs fixing or not is a matter of debate. Personally, I
agree with you, but this isn't a reason in itself to make a change. I
would prefer to see consensus across Debian and Ubuntu, and am unwilling
to
(also blogged)
As part of the Ubuntu Server team's participation in the [Ubuntu Open
Summit][1], we'll be running two QA sessions this week aimed at Ubuntu
Server users. We want to gather questions from the community both before
and during the event, so that users can get direct and authoritative
Also this is Fix Released as it is presumably fixed in Utopic (the
current development release).
** Changed in: apache2 (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
As upstream has stated that this is a spurious warning, this issue has
only now been reported in Lucid after it has already been out for four
years already, and I don't expect that any new installations will be
*** This bug is a duplicate of bug 1273462 ***
https://bugs.launchpad.net/bugs/1273462
** This bug has been marked a duplicate of bug 1273462
Users can mistakenly run init.d scripts and cause problems if an equivalent
upstart job already exists
--
You received this bug notification
** Changed in: charm-tools (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to charm-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1326477
Title:
charm get doesn't work unless you login to
Blueprint changed by Robie Basak:
Work items changed:
- Work items:
+ Work items for ubuntu-14.06:
+ [racb] Early cycle merge report: TODO
+
+ Work items for ubuntu-14.08:
+ [racb] Late cycle merge report: TODO
+
+ Work items for ubuntu-14.10:
determine ssd caching solution (bcache
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
I specifically tested vsftpd local user login in Trusty by adding a dep8
test that automatically tests this case. You can see the test case here:
http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/trusty/vsftpd
Thanks!
** Also affects: haproxy (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750459
Importance: Unknown
Status: Unknown
** Tags removed: needs-upstream-report
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
** Changed in: juju-core (Ubuntu)
Status: Triaged = In Progress
** Changed in: juju-core (Ubuntu)
Assignee: (unassigned) = Robie Basak (racb)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https
** Changed in: juju-core (Ubuntu)
Status: Triaged = In Progress
** Changed in: juju-core (Ubuntu)
Assignee: (unassigned) = Robie Basak (racb)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https
** Also affects: juju-core (Ubuntu)
Importance: Undecided
Status: New
** Changed in: juju-core (Ubuntu)
Status: New = In Progress
** Changed in: juju-core (Ubuntu)
Assignee: (unassigned) = Robie Basak (racb)
--
You received this bug notification because you are a member
*** This bug is a duplicate of bug 1314740 ***
https://bugs.launchpad.net/bugs/1314740
** This bug has been marked a duplicate of bug 1314740
awk in startup script finds wrong pid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
** Summary changed:
- awk in startup script finds wrong pid
+ init script pid parsing has failure cases
** Tags added: needs-upstream-report
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
Also, I didn't check if the init.d script is provided by packaging or
comes directly from upstream. If it comes directly from upstream, then
sending the patch upstream directly would be best.
** Changed in: haproxy (Ubuntu)
Importance: Undecided = Wishlist
--
You received this bug
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
haproxy in Ubuntu is currently identical to the Debian haproxy package
from which it is derived, so it seems likely to me that Debian will
benefit from this patch, too. I would also like to avoid the additional
** Changed in: maas (Ubuntu)
Importance: Undecided = High
--
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/1325167
Title:
dpkg: ImportError: No module named seamicroclient.v2
To
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Please see the stable release update policy, rationale and procedure
documented at: https://wiki.ubuntu.com/StableReleaseUpdates
In particular, I see changelog entries such as some cosmetics., which
do not appear
Thank you for your report.
This looks like a local configuration problem, rather than a bug in
Ubuntu. Specifically:
Invalid command 'Order', perhaps misspelled or defined by a module not
included in the server configuration
You need to update your Apache configuration to meet the requirements
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
I see that logcheck currently has no delta against Debian. Please could
you check to see if this patch is also relevant to Debian, and if so,
file a bug in Debian if there isn't one there already?
** Changed in:
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. You may find it helpful
to read How to report bugs effectively
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
I presume a workaround is to use sbuild or pbuilder? Assuming that this
is the case, I'll set the Importance to Medium as a workaround is
available.
** Changed in: neutron (Ubuntu)
Importance: Undecided =
Thanks. Marking as Fix Released, as Utopic has 2.4.9.
** Changed in: apache2 (Ubuntu)
Status: New = Fix Released
--
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/1324828
Title:
Blueprint changed by Robie Basak:
Work items changed:
Work items:
determine ssd caching solution (bcache is it): DONE
add scribe (https://github.com/facebook/scribe) to universe: TODO
- add meteor to universe: TODO
+ add meteor (https://github.com/meteor/meteor) to universe: TODO
Blueprint changed by Robie Basak:
Work items changed:
Work items:
determine ssd caching solution (bcache is it): DONE
- add scribe (https://github.com/facebook/scribe) to universe: TODO
- add meteor (https://github.com/meteor/meteor) to universe: TODO
+ [racb] add scribe (https://github.com
Public bug reported:
Late last cycle, a juju-core upload broke juju-quickstart in bug
1306537, but this was not picked up. A dep8 test for juju-quickstart
would be able to automatically test and hold juju-core in -proposed
until juju-quickstart is updated in tandem, should this arise again in
the
Public bug reported:
juju uses distro-info-data to understand what Ubuntu releases exist,
falling back to its own knowledge if it is not available. When we open a
new development release, the version of juju-core that is copied forward
does not know about the release, causing juju-core such as in
(James is out this week)
Looks like chkrootkit has been seeded ever since the start (of server),
under the heading System Administration Tools:
http://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu-
seeds/ubuntu.trusty/revision/448.1.2
Essentially it's in main because it was deemed useful for the
** Package changed: samba4 (Ubuntu) = samba (Ubuntu)
** Changed in: samba (Ubuntu)
Status: New = Triaged
** Changed in: samba (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
I guess that update-rc.d can be run by hand as a workaround? In this
case, setting Importance: Medium as a workaround is available.
** Changed in: pacemaker (Ubuntu)
Importance: Undecided = Medium
--
You
*** This bug is a duplicate of bug 1321369 ***
https://bugs.launchpad.net/bugs/1321369
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
You need to stop smbd and nmbd individually. The samba alias to two
services and confusing interaction with the init.d
I've seen multiple reports involving the samba, smbd and nmbd
services, confusion in their behavior for starting, stopping,
restarting, reloading etc, and in interaction between upstart jobs,
init.d scripts and the service command.
I think these all have the same root cause, which stems from the
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
It's not clear to me if this would be an issue with openssh, lxc or
cloud-init. But I was unable to reproduce your issue.
I had to make a couple of amendments to your instructions.
First, I presume your
Perhaps also include more of your auth.log, as that line appears to be a
red herring?
--
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/1317592
Title:
cannot log into trusty
Thanks Seth. I have no objection. Perhaps we should check on the ubuntu-
server list first? In any case we need a core dev to commit the seed
change, so that will probably be James, so he will be able to confirm
next week.
--
You received this bug notification because you are a member of Ubuntu
Looks like lua wasn't built, because we're trying to build against 5.2,
and it's only looking for 5.1.
https://launchpadlibrarian.net/175043407/buildlog_ubuntu-utopic-
amd64.apache2_2.4.9-1ubuntu1_UPLOADING.txt.gz
checking lua.h usability... no
checking lua.h presence... no
checking for lua.h...
Looks like the regression was in 2.4.4-6ubuntu3. Prior to this, we had:
checking lua.h usability... no
checking lua.h presence... no
checking for lua.h... no
checking for lua.h in /usr/local/include/lua5.1... no
checking for lua.h in /usr/local/include/lua51... no
checking for lua.h in
Public bug reported:
We'd like to support lua 5.2 in main only, and move away from 5.1. But
some upstreams don't yet have support for lua 5.2 yet.
Related: apache bug 1323930 (lua support regression due to failed move
to 5.2) and bug 1262710 (in particular comment 25) for discussion of the
same
Bug 1324062 tracks the missing lua 5.2 support issue.
--
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/1262710
Title:
[MIR] nginx
To manage notifications about this bug go to:
Bug 1324062 tracks the missing lua 5.2 support issue. In the meantime,
I've uploaded a fix by reverting to building against lua 5.1 (as
discussed in #ubuntu-devel just now).
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in
Thank you for your report.
It looks like you have the mail-stack-delivery package installed, which
is designed to alter postfix's configuration as declared in the package
description: This package modifies postfix's configuration to integrate
with dovecot.
If you do not want to have your postfix
Since Ubuntu uses upstart, the correct interface to manage services is
with the service command, not by calling init.d scripts directly.
dovecot in Trusty is managed by an upstart script. This is defined in
/etc/init/dovecot.conf. That /etc/init.d/dovecot doesn't exist is by
design, so I'm
** Changed in: nginx (Ubuntu)
Importance: Undecided = Medium
--
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/1323387
Title:
Auth Request module does not seem to be loaded in the
I think investigation needs to start from a qemu performance
perspective. It may be that uvtool needs to tell libvirt to tell qemu to
do something differently, but in that case I need to know what.
** Project changed: uvtool = qemu
** Project changed: qemu = qemu (Ubuntu)
** Changed in: qemu
** Package changed: libdbi (Ubuntu) = gnucash (Ubuntu)
** Changed in: gnucash (Ubuntu)
Status: Invalid = New
** Summary changed:
- GNUcash crashing because of libdbi
+ GNUcash crashes on close
** Also affects: gnucash via
https://bugzilla.gnome.org/show_bug.cgi?id=728717
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. You may find it helpful
to read How to report bugs effectively
** Bug watch added: Samba Bugzilla #10564
https://bugzilla.samba.org/show_bug.cgi?id=10564
** Also affects: samba via
https://bugzilla.samba.org/show_bug.cgi?id=10564
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
** Changed in: augeas (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to augeas in Ubuntu.
https://bugs.launchpad.net/bugs/1322898
Title:
squid lens fails with current squid syntax
To manage
** Changed in: samba (Ubuntu)
Importance: Undecided = Medium
--
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/1321369
Title:
/etc/init.d/samba starts smbd/nmbd improperly
To manage
*** This bug is a duplicate of bug 1321369 ***
https://bugs.launchpad.net/bugs/1321369
** This bug has been marked a duplicate of bug 1321369
/etc/init.d/samba starts smbd/nmbd improperly
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
I have tested Trusty on i386, and found that installing php-memcache
pulls in php5-common correctly without a problem.
5.5.12+dfsg-2+deb.sury.org~trusty+1 - phpapi-20121212 php5-mhash
Looks like you're using
This bug was fixed in the package mod-wsgi - 3.5-1
Sponsored for Artur Rona (ari-tczew)
---
mod-wsgi (3.5-1) unstable; urgency=high
* New upstream release.
- Fixes CVE-2014-0240: Local privilege escalation when using daemon mode.
* Drop fix_crash_daemon_mode.patch, applied
*** This bug is a security vulnerability ***
Public security bug reported:
check_dhcp is shipped to run suid root by default by upstream, but it is
not packaged as suid root in Debian or Ubuntu.
This issue has no CVE but is listed at
http://osvdb.org/show/osvdb/107070
However, if users mark it
** Package changed: juju (Ubuntu) = juju-website
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
https://bugs.launchpad.net/bugs/1320733
Title:
Broken vagrant download link on juju docs website
To manage
Thanks Charlie and Ondřej. Marking as Incomplete, pending Nick's
response. Nick: if Charlie is correct, please set the bug status to
Invalid. Otherwise, please explain and change the bug status back to
New. Thanks!
** Changed in: php5 (Ubuntu)
Status: New = Incomplete
** Changed in: php5
** Summary changed:
- Document: to use MAAS with virsh, add root to libvirtd group
+ MAAS cluster controller runs as wrong groups
--
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/1319609
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
What are the implications for adding this configure option, please? Why
don't upstream have it enabled by default already? Is this because there
are negative consequences for some proportion of users? If this were
libvirt-bin will pull in libvirtd, which will configure a virbr0, etc.
I'm not sure we want to do that by default. I presume this is the
original rationale for Suggests rather than Recommends or Depends.
I can see that libvirt might be installed on a different machine though,
so perhaps we want
** Also affects: libvirt (Ubuntu)
Importance: Undecided
Status: New
--
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/1319717
Title:
virsh support requires an extra package to
** Changed in: awstats (Ubuntu)
Importance: Undecided = Medium
** Tags added: bitesize
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to awstats in Ubuntu.
https://bugs.launchpad.net/bugs/1320709
Title:
incorrect info in
** Changed in: xen (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to xen in Ubuntu.
https://bugs.launchpad.net/bugs/1321144
Title:
/etc/default/grub.d/xen.cfg only works on english language
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I'm marking this bug as Incomplete.
If indeed this is a local configuration problem, you can find pointers
to
Thanks! I see that 0.11.1~dfsg1-1 has synced to Utopic.
** Changed in: docker.io (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to docker.io in Ubuntu.
https://bugs.launchpad.net/bugs/1314470
Bug 1200255 is related. The same issue happens with the go toolchain. We
ended up specifically not stripping binaries in juju, and I think other
go binaries need to be built this way also.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
Correction. From the upstream bug, is it Unicode that is actually fine,
but non-UTF8 (and thus non-Unicode) paths that are the problem?
** Summary changed:
- Error: Could not set 'file' on ensure: invalid byte sequence in US-ASCII
+ puppet does not correctly handle Unicode filenames in a file
*** This bug is a duplicate of bug 1318660 ***
https://bugs.launchpad.net/bugs/1318660
** This bug has been marked a duplicate of bug 1318660
error msg on install
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
** Summary changed:
- error msg on install
+ trying to overwrite '/usr/lib/python2.7/dist-packages/apiclient/__init__.py',
which is also in package python-googleapi 1.2-2
** Changed in: maas (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are 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: bind9 (Ubuntu)
Importance: Undecided = Medium
--
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/1318396
Title:
localhost reverse ipv6 is missing
To manage
Thank you for your report.
This looks like a local configuration problem, rather than a bug in
Ubuntu, since no package mongodb-10gen ships with Ubuntu itself.
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
** Changed in: openssh (Ubuntu)
Importance: Undecided = Medium
--
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/1316017
Title:
openssh client ignores -o Tunnel=ethernet option,
** Changed in: juju-core (Ubuntu)
Status: New = Triaged
** Changed in: juju-core (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
** Changed in: samba (Ubuntu)
Importance: Undecided = Medium
--
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/1318835
Title:
regression: smbclient authfile parameter no longer works
** Changed in: juju-core (Ubuntu)
Status: New = Triaged
** Changed in: juju-core (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
** Attachment added: trusty.log
https://bugs.launchpad.net/juju-core/+bug/1314686/+attachment/458/+files/trusty.log
--
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/1314686
** Attachment added: utopic-bzr2291.log
https://bugs.launchpad.net/juju-core/+bug/1314686/+attachment/460/+files/utopic-bzr2291.log
** Changed in: juju-core/1.18
Status: Fix Committed = New
--
You received this bug notification because you are a member of Ubuntu
Server Team,
I've failed to get this working on Utopic. The existing dep8 test
(modified just to add distro-info-data as an extra dependency) passes on
Trusty, but fails on Utopic. I've also tried replacing the upstream
tarball with one generated from 1.18 branch bzr revno 2291, and this
also fails on Utopic.
1601 - 1700 of 3424 matches
Mail list logo
