As I said, please give us exact steps to reproduce, preferably verified
on a fresh installation. Until then this bug correctly remains both
Incomplete and unconfirmed and so nobody will be working on fixing it.
--
You received this bug notification because you are a member of Ubuntu
Server Team,
5.5 superceded in = Vivid = Won't Fix. Fixed in 5.6. Could be SRU'd if
bundled in with some other updates, so no objection to bug tasks for
specific stable releases.
** Changed in: mysql-5.5 (Ubuntu)
Status: Triaged = Won't Fix
--
You received this bug notification because you are a
** Also affects: juju-core (Ubuntu Trusty)
Importance: Undecided
Status: New
--
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/1469744
Title:
[needs-packaging] 1.22.6 is
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 your reply. I think this bug needs further investigation
in comparing the Ubuntu packaged versions to upstream versions to figure
out if and where the gap appears.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ruby1.9.1
Uploaded; now awaiting SRU team review.
** Changed in: grub2 (Ubuntu Precise)
Status: Triaged = In Progress
** Changed in: grub2 (Ubuntu Trusty)
Status: Triaged = In Progress
** Changed in: grub2 (Ubuntu Utopic)
Status: Triaged = In Progress
** Changed in: grub2 (Ubuntu
In relation to the mongodb task, AFAICT the error is still coming from
inside Juju code. How can this be exercised independent of Juju, please?
Is the current version of mongo in Wily affected, or is it fixed there?
** Changed in: mongodb (Ubuntu)
Status: New = Incomplete
--
You received
** Changed in: mysql-5.6 (Ubuntu)
Importance: Undecided = High
--
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/1468984
Title:
hash.h not packaged but required by sql_common.h
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
SRU from Ryan Harper sponsored and uploaded. Thanks! Now awaiting review
from the SRU team.
** Changed in: samba (Ubuntu Trusty)
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
** Changed in: rsync (Ubuntu)
Assignee: (unassigned) = Ryan Harper (raharper)
** Also affects: rsync (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: rsync (Ubuntu)
Status: Confirmed = Fix Released
** Changed in: rsync (Ubuntu Trusty)
Status: New =
This bug also affects vsftpd functionality. When SMB password
synchronisation is selected in pam-auth-update, vsftpd can not
authenticate users and segfaults with OOPS message.
This sounds like bug 1348972 in vsftpd and I don't think a fix to this
samba bug will affect it.
--
You received this
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
I know that years ago gem install was horribly insecure, but I believe
this has been improved upstream? So is this a bug in Ubuntu's packaging,
or is it that it is fixed in a newer upstream (and/or Ubuntu)
** Also affects: docker.io (Ubuntu Vivid)
Importance: Undecided
Status: New
--
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/1466550
Title:
docker lxc driver fails
To
Believed fixed in Wily, but still affects Vivid.
** Also affects: docker.io (Ubuntu Vivid)
Importance: Undecided
Status: New
** Changed in: docker.io (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
Thank you for your report.
What is /repo/config/etc/php.ini please? Is it something you have
created and symlinked from /etc/php? Do you have multiple symlinks
pointing to the same location?
Once you've replied, please change the bug status back to New.
** Changed in: php5 (Ubuntu)
Thank you for your report.
etckeeper can use bzr, git, mercurial or darcs, and requires only one of
these to be installed. If you already have git installed (for example),
then the dependency is fulfilled and bzr will not be installed.
On Ubuntu etckeeper currently defaults to bzr, so in this
** Changed in: php5 (Ubuntu)
Status: New = Incomplete
--
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/1465326
Title:
package php5-fpm 5.6.4+dfsg-4ubuntu6 failed to
Marking Won't Fix for the SRU tasks as the current position is that we
have no intention of SRUing this.
** Changed in: rpcbind (Ubuntu Precise)
Status: New = Won't Fix
** Changed in: rpcbind (Ubuntu Trusty)
Status: New = Won't Fix
** Changed in: rpcbind (Ubuntu Utopic)
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
This report should probably be verified upstream and then sent there, as
it doesn't make sense for Ubuntu to diverge from other distributions on
this.
** Tags added: needs-upstream-report
** Changed in: iproute2
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Your report says that you originally installed from Ubuntu-Kylin 14.04
LTS Trusty Tahr - Release i386 (20140417.1), yet I see mentions of
apache2.2-bin 2.2.14-5ubuntu8.15 which did not ship with 14.04. So it
seems
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
I just looked into this, prompted by Chuck Peters on the ubuntu-server
list.
It seems to me that this is a security-related feature made upstream in
a newer release of exim4. To use it, every individual sysadmin would
need to manually configure the tls_verify_cert_hostnames setting to a
list of
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
** Changed in: rsync (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to rsync in Ubuntu.
https://bugs.launchpad.net/bugs/1467281
Title:
rsync ignores -x for dmsetup managed mountpoints
To
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Please attach the error from /var/log/mysql/error.log after the actual
fail-to-start failure. The logs automatically attached don't contain the
failure as they have rotated out since you first had a problem as far
Since we are already building with SASL, marking this bug Invalid.
If you actually intended to report a problem with SASL support in some
existing release, then please describe in detail, rename this bug and
reopen it accordingly. You may find it helpful to read How to report
bugs effectively
Build logs:
From Trusty:
Configuration summary for libmemcached version 1.0.8
* Installation prefix: /usr
* System type: pc-linux-gnu
* Host CPU: x86_64
* C Compiler:gcc (Ubuntu/Linaro 4.8.2-10ubuntu1) 4.8.2
* Assertions
** Also affects: openssh via
https://bugzilla.mindrot.org/show_bug.cgi?id=2365
Importance: Unknown
Status: Unknown
** Description changed:
This is a regression from the version of the client in 14.04 compared to
13.10. I'm connecting to 12.04.4 for a server.
Expected
I presume this is fixed with the current MySQL 5.5 and 5.6 packages in
= Trusty? Marking this bug closed accordingly. If it is still a problem
then please do reopen.
** Changed in: mysql-dfsg-5.1 (Ubuntu)
Status: Triaged = Invalid
--
You received this bug notification because you are a
As 5.1 doesn't exist, I don't know if Invalid, Won't Fix or Fix Released
is appropriate. I don't suppose it really matters - just reopen for
attention again if there's still a problem.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Probably not suitable for sync but it is a valid bug in that memcached
needs updating in Ubuntu, so let's track that.
** Summary changed:
- Please sync with 1.4.24 Debian sid package
+ Please merge with latest upstream from Debian
** Changed in: memcached (Ubuntu)
Status: Incomplete =
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
** Also affects: irqbalance (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: irqbalance (Ubuntu Trusty)
Status: New = Won't Fix
** Changed in: irqbalance (Ubuntu Trusty)
Status: Won't Fix = Triaged
** Changed in: irqbalance (Ubuntu)
Status: Triaged
Uploaded, with one minor change agreed with Manoj on IRC: on not finding
/proc/device-tree/model, no warning is printed, as this is the common
case on Intel (and I want to avoid risking alarming users via eg.
logcheck).
I'll leave it to the SRU team to decide on whether it's OK to fix Trusty
** Also affects: golang-blackfriday (Ubuntu)
Importance: Undecided
Status: New
** Also affects: go-md2man (Ubuntu)
Importance: Undecided
Status: New
** Also affects: golang-context (Ubuntu)
Importance: Undecided
Status: New
** Also affects: golang-dbus (Ubuntu)
** Also affects: openldap (Ubuntu Utopic)
Importance: Undecided
Status: New
** Also affects: openldap (Ubuntu Vivid)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openldap in
Upstream says With pep8 1.5 you achieve it adding # noqa on the last
line of the docstring. and 1.5 is in Wily.
** Changed in: pep8 (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pep8 in
** Changed in: nmap (Ubuntu)
Importance: Undecided = Low
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nmap in Ubuntu.
https://bugs.launchpad.net/bugs/1464888
Title:
manpage examples are missing
To manage notifications about
This is fixed in mysql-5.6.
** Changed in: mysql-5.6 (Ubuntu)
Status: Triaged = Fix Released
--
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/1362393
Title:
default my.cnf
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
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
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
From log:
Aborting downgrade from (at least) 10.0 to 5.6.
If are sure you want to downgrade to 5.6, remove the file
/var/lib/mysql/debian-*.flag and try installing again.
dpkg: error processing archive
/var/cache/apt/archives/mysql-server-5.6_5.6.19-0ubuntu0.14.04.1_amd64.deb
(--unpack):
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.ubun
tu.com/support/community
Since we use this bug tracker to track bugs in Ubuntu, rather than configuration
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
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
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
It should be asked trough a popup question, not left hidden in the
installation logs.
It is a critical debconf prompt. If synaptic did not present it to you,
then that's either a bug in synaptic or you have synaptic configured to
hide critical prompts from you.
** Changed in: mysql-5.6 (Ubuntu)
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
** Changed in: mysql-5.6 (Ubuntu)
Importance: Undecided = Low
--
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/1419581
Title:
A little typo
To manage notifications about this
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
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
Marking Importance: Wishlist based on the corresponding Debian bug. If
there are specific issues causing real problems for users, then please
use separate bugs to help us track the actual issues and assess their
importance individually and objectively. It's buggy isn't particularly
helpful on its
Thank you for your report.
This looks like a local configuration problem, rather than a bug in
Ubuntu, since you have manually deleted /etc/apache2/mods-
available/php5.conf and php5.load. Under these circumstances libapache2
-mod-php5 cannot be expected to work correctly.
You can find pointers
Thank you for taking the time for reporting this bug and helping to make
Ubuntu better.
With the default GracefulShutdownTimeout, Apache should still shut down
after all existing requests have been served, and the reload should
still occur. Based on that description, I don't yet see a bug in the
From log:
Setting up libapache2-mod-php5 (5.5.9+dfsg-1ubuntu4.7) ...
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
Not
** Patch added:
0003-Add-W3C-BSD-3-clause-for-src-golang.org-x-net-html-c.patch
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1462001/+attachment/4412117/+files/0003-Add-W3C-BSD-3-clause-for-src-golang.org-x-net-html-c.patch
--
You received this bug notification because you are a
Your branch looks good, thanks. I found some minor issues for which I'll
attach fixes, and three upstream licensing issues. Two just need
reporting upstream and don't need to block an upload in Ubuntu. The
third is a Canonical upstream with possibly an error in license choice -
if upstream can
** Patch added: 0002-Bump-copyright-date-range.patch
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1462001/+attachment/4412116/+files/0002-Bump-copyright-date-range.patch
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Technically we want upgrade-software-version, not needs-packaging.
** Tags removed: needs-packaging
** Tags added: upgrade-software-version
** Changed in: juju-core (Ubuntu)
Importance: Wishlist = Medium
** Changed in: juju-core (Ubuntu)
Status: New = Triaged
--
You received this
OK thanks Anton. Marking Incomplete for now.
** Changed in: php5 (Ubuntu)
Status: New = Incomplete
--
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/1442797
Title:
add patches to
There is currently no mechanism for a package maintainer script to
automatically detect that you added additional ports and apply this
change to the new configuration file in a major upstream release update.
If you have a customised configuration file, then when you upgrade you
should get a
Marking Invalid based on Amos' response - thanks. It's either that or
Fix Released; I'm not sure. Whichever way this bug does not need to
remain open.
** Changed in: squid3 (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
*** This bug is a duplicate of bug 1370602 ***
https://bugs.launchpad.net/bugs/1370602
** This bug has been marked a duplicate of bug 1370602
package squid3 3.3.8-1ubuntu6.1 failed to install/upgrade: Unterprozess
installiertes post-installation-Skript gab den Fehlerwert 1 zurück
--
You
*** This bug is a duplicate of bug 1370602 ***
https://bugs.launchpad.net/bugs/1370602
** This bug has been marked a duplicate of bug 1370602
package squid3 3.3.8-1ubuntu6.1 failed to install/upgrade: Unterprozess
installiertes post-installation-Skript gab den Fehlerwert 1 zurück
--
You
*** This bug is a duplicate of bug 1370602 ***
https://bugs.launchpad.net/bugs/1370602
** This bug has been marked a duplicate of bug 1370602
package squid3 3.3.8-1ubuntu6.1 failed to install/upgrade: Unterprozess
installiertes post-installation-Skript gab den Fehlerwert 1 zurück
--
You
Thank you for your report.
This looks like a local configuration problem, rather than a bug in
Ubuntu, since you had previously modified squid.conf and these
customisations needed to be updated in the upgrade.
You can find pointers to get help for this sort of problem here:
*** This bug is a duplicate of bug 1370602 ***
https://bugs.launchpad.net/bugs/1370602
** This bug has been marked a duplicate of bug 1370602
package squid3 3.3.8-1ubuntu6.1 failed to install/upgrade: Unterprozess
installiertes post-installation-Skript gab den Fehlerwert 1 zurück
--
You
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
I don't think this is a valid bug in Ubuntu since you're trying to build
differently from the way that Ubuntu does it. Certainly not in 12.04
anyway, which is an old (but still supported) release. I don't think
*** This bug is a duplicate of bug 1370602 ***
https://bugs.launchpad.net/bugs/1370602
** This bug has been marked a duplicate of bug 1370602
package squid3 3.3.8-1ubuntu6.1 failed to install/upgrade: Unterprozess
installiertes post-installation-Skript gab den Fehlerwert 1 zurück
--
You
Thank you for your report.
This looks like a local configuration problem, rather than a bug in
Ubuntu. You appear to have a customised squid.conf with syntax errors.
You can find pointers to get help for this sort of problem here:
http://www.ubuntu.com/support/community
Since we use this bug
** Package changed: squid3 (Ubuntu) = grub2 (Ubuntu)
--
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/1334803
Title:
package squid3 3.3.8-1ubuntu6 failed to install/upgrade:
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Is this bug fixed in upstream release 3.4.8? If so, then I will be
fixing the development release of Ubuntu shortly.
If someone can prepare backports, please follow the steps at
*** This bug is a duplicate of bug 1370602 ***
https://bugs.launchpad.net/bugs/1370602
** This bug has been marked a duplicate of bug 1370602
package squid3 3.3.8-1ubuntu6.1 failed to install/upgrade: Unterprozess
installiertes post-installation-Skript gab den Fehlerwert 1 zurück
--
You
*** This bug is a duplicate of bug 1370602 ***
https://bugs.launchpad.net/bugs/1370602
** This bug is no longer a duplicate of bug 1241957
package squid3 3.3.8-1ubuntu3 failed to install/upgrade: ErrorMessage:
subprocess installed post-installation script returned error exit status 1
**
*** This bug is a duplicate of bug 1370602 ***
https://bugs.launchpad.net/bugs/1370602
** This bug is no longer a duplicate of bug 1241957
package squid3 3.3.8-1ubuntu3 failed to install/upgrade: ErrorMessage:
subprocess installed post-installation script returned error exit status 1
**
Marking as Invalid as it sounds like this was a local configuration
problem and not a bug in Ubuntu.
** Changed in: squid3 (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid3 in Ubuntu.
Thank you for your report.
This looks like a local configuration problem, rather than a bug in
Ubuntu. You seem to have deleted your squid configuration, so it cannot
be expected to restart successfully.
You can find pointers to get help for this sort of problem here:
I haven't treated this as a priority to be fixed because I presume that
SMP squid has very few active users. Only three people have marked
themselves as affected by this bug in over a year.
If someone can prepare a fix and test that it works for all use cases,
including for non-SMP squid users on
That's fine, but we need to take care to avoid regressing existing users
not affected by this bug, and we need a test case to exercise the bug to
verify that it is fixed before issuing the update. Please see my link
above if you can assist with this.
--
You received this bug notification because
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Which upstream releases are affected, please? Is it just 2.4.40, and
thus just Wily? Or are 2.4.28 and/or 2.4.31 affected as well?
** Summary changed:
- Requesting ITS#8003 inclusion in 2.4.40 package
+
Thanks Igor.
I'll set this back to Invalid again, since Igor confirms that the issue
is in the client. I have no current intention of symlinking pt-bz to pt-
br in packaging in Ubuntu unless upstream decide to do it also, so I
think the correct status for the Ubuntu task is Invalid.
** Changed
Based on the Debian bug I believe this was fixed in 15.04.
If you need a fix for an existing stable release, please comment with a
justification against https://wiki.ubuntu.com/StableReleaseUpdates#When
and complete steps 1 through 4 in
https://wiki.ubuntu.com/StableReleaseUpdates#Procedure - and
Thank you for your report.
As you have modified your apache2 configuration, 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
Thank you for your report.
This looks like a local configuration problem, rather than a bug in
Ubuntu.
Specifically, you have deleted /etc/apache2/mods-available/wsgi.conf and
wsgi.load, so apache2 cannot be expected to start.
You can find pointers to get help for this sort of problem here:
** Changed in: mysql-5.6 (Ubuntu)
Importance: Undecided = Medium
--
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/1460346
Title:
Innotop broken
To manage notifications about
Thank you for your report.
This looks like a local configuration problem, rather than a bug in
Ubuntu.
Specifically, as you have deleted /etc/apache2/mods-available/php5.conf
and php5.load, apache2 cannot be expected to start.
You can find pointers to get help for this sort of problem here:
@km
Thank you for reporting back. Does this mean that it was a problem
specific to customisations you had made to your system, or is this a
problem that would apply to all users? If the latter, do you now
understand how I might be able to reproduce the issue?
--
You received this bug
** Changed in: keepalived (Ubuntu)
Status: New = Triaged
** Changed in: keepalived (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keepalived in Ubuntu.
From log:
May 29 20:01:48 mail named[1196]: loading configuration from
'/etc/bind/named.conf'
May 29 20:01:48 mail named[1196]: /etc/bind/named.conf:13: unknown option
'forwarders'
May 29 20:01:48 mail named[1196]: loading configuration: failure
May 29 20:01:48 mail named[1196]: exiting (due to
Thank you for your report.
This looks like a local configuration problem, rather than a bug in
Ubuntu.
Specifically you have modified your bind9 configuration in named.conf
and named.conf.local, and it appears that your modifications contain
syntax errors.
You can find pointers to get help for
Thanks Stig. Looks like we want to cherry-pick relevant changes between
3.7.2-1 and 3.7.2-4.
** Changed in: puppet (Ubuntu)
Status: Confirmed = Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
Thanks. Upstream says this was fixed in 3.4.5, which we don't have in
Ubuntu yet. So this bug remains valid in Ubuntu.
** Tags removed: needs-upstream-report
** Changed in: squid3 (Ubuntu)
Status: New = Triaged
--
You received this bug notification because you are a member of Ubuntu
If it has the old usr.sbin.mysqld (and an uninstalled dist file) you
have hit the bug
By uninstalled dist file, do you mean usr.sbin.mysqld.dpkg-dist? I
expect your scenario to occur if the user previously modifies the
apparmor profile. In this case, on upgrade, the user should be prompted
to
** Tags added: upgrade-software-version
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keepalived in Ubuntu.
https://bugs.launchpad.net/bugs/1460120
Title:
Please merge from debian unstable 1.2.13-1
To manage notifications about
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
If this also affects upstream, it should be reported there if it is not
already. We can cherry-pick a fix in Ubuntu but I'd prefer to do that
only after an upstream commit lands so we don't end up maintaining
21:53 rbasak pitti: see bug 1458630. We deliberately moved apparmor-
profile-load into init-system-helpers because it isn't necessarily
upstart-specific. So I'm not sure why you say Temporarily? In any case
the Breaks/Replaces needs to continue to be present.
** Changed in: init-system-helpers
This should have been fixed by:
init-system-helpers (1.22ubuntu7) vivid; urgency=medium
* Declare Breaks/Replaces against both upstart and upstart-bin since
/lib/init/apparmor-profile-load briefly appeared in both packages
(LP: #1439988).
-- Robie Basak robie.ba...@ubuntu.com Tue
As I said, I see no issue with updating the squidguard package 15.04
with a reversion of the patch I mentioned above, if as I understand the
package is broken in 15.04 today and reverting the patch does actually
fix the issue. Someone just needs to check this works, perform SRU
verification, etc.
801 - 900 of 3231 matches
Mail list logo
