Public bug reported:
See Debian bug #510495 - when vlans are configured, snmpd leaks memory.
Definitely observed in 5.4.1~dfsg-4ubuntu4.4.
** Affects: net-snmp (Ubuntu)
Importance: Undecided
Status: New
** Affects: net-snmp (Debian)
Importance: Unknown
Status:
An SRU into existing releases makes good sense. The change is very
minimal, with the biggest risk being that somepoint after the current
operator of D stops using the IP address, said address gets assigned to
someone who decides that giving out the wrong answers would be a thing
to do. I don't
I've uploaded SRU-able versions of the package to my personal ppa. See
https://launchpad.net/~lamont/+archive/ppa/+packages
--
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/1090593
What is the value for smtp_tls_CApath in your configuration?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to postfix in Ubuntu.
https://bugs.launchpad.net/bugs/1139159
Title:
Postfix does not restart properly when using SSL
To
Finally saw what was meant there. Confirmed, doing the mkdir
${dest_dir}.NEW will be unconditional (inside that box) as of 2.10.0-1
** Changed in: postfix (Ubuntu)
Status: New = Confirmed
** Changed in: postfix (Ubuntu)
Assignee: (unassigned) = LaMont Jones (lamont)
** Changed
Public bug reported:
I need to run tftpd from xinetd, and that support was dropped when the
init script was converted to upstart.
Please restore the ability to run tftpd from xinetd.
** Affects: tftp-hpa (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug
Public bug reported:
Postfix 2.10 provides improved controls for reducing the risk of open relays.
Also, we want to continue to offer the latest postfix to LTS users via
backports and we need to get it into raring to do this.
Attached is the upstream diff of the HISTORY file.
** Affects:
If approved, please sync 2.10.0-2 from debian.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to postfix in Ubuntu.
https://bugs.launchpad.net/bugs/1155730
Title:
postfix 2.10 for raring
To manage notifications about this bug go to:
Fred - was that on a fresh install, or what version were you upgrading
from?
thanks,
lamont
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to postfix in Ubuntu.
https://bugs.launchpad.net/bugs/1155730
Title:
postfix 2.10 for raring
Fixed in 2.10.0-3
** Changed in: postfix (Ubuntu)
Importance: Undecided = High
** Changed in: postfix (Ubuntu)
Status: Confirmed = Fix Committed
** Changed in: postfix (Ubuntu)
Status: Fix Committed = Won't Fix
** Changed in: postfix (Ubuntu)
Status: Won't Fix = Fix
This is actually a bug in the ubuntu server settings. Servers should
not have ipv6 privacy on by default, and postfix should honor what the
admin has set.
I'll revisit this and either close it with a reference to the other bug,
or reassign it, as appropriate.
--
You received this bug
Public bug reported:
During an upgrade to raring (from quantal), the prerm script tries to
use things that are not defined. There are broken Dependencies in the
package.
Preparing to replace python-novaclient 1:2.9.0-0ubuntu1 (using
.../python-novaclient_1%3a2.11.1-0ubuntu1_all.deb) ...
Public bug reported:
After I created a thousand new flavors (to enable some automation), with
IDs 1000-1999, nova flavor-list now displays flavor 1, followed by
1000-1998, and then stops.
Flavors 1999 and 2-6 are still valid and usable, just absent from the
output of flavor-list (flavor-show is
** Tags added: prodstack
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1166455
Title:
nova flavor-list only shows 1000 flavors
To manage notifications about this bug go to:
Public bug reported:
The setup:
- grizzly rc2 upgraded to grizzly (1:2013.1-0ubuntu1~cloud0), running on
precise.
- fresh install configured based on what appears to be a folsom howto
Starting nova-network results in the following in the nova-network log:
...
2013-04-10 08:59:18.788 WARNING
This is specifically caused by having non-default
smtp_recipient_restrictions, which changed behavior in 2.10, and postfix
needs to know how you want to proceed. The answer to the question can
be preseeded if you so desire. There is no bug here.
--
You received this bug notification because
** Patch added: patch for 1.5.8
https://bugs.launchpad.net/ubuntu/+source/facter/+bug/911812/+attachment/2657118/+files/processor.diff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to facter in Ubuntu.
Public bug reported:
/proc/cpuinfo is architecture specific, and the facter code does not
correctly handle it.
** Affects: facter (Ubuntu)
Importance: Undecided
Status: New
** Affects: facter (Ubuntu Lucid)
Importance: Undecided
Status: New
** Affects: facter
I have tried to reproduce this on both Lucid and Precise, and in neither
case does it reproduce for me.
** Changed in: postfix (Ubuntu)
Status: Confirmed = Won't Fix
** Changed in: postfix (Ubuntu)
Status: Won't Fix = Incomplete
--
You received this bug notification because you
** Changed in: postfix (Ubuntu)
Status: New = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to postfix in Ubuntu.
https://bugs.launchpad.net/bugs/859658
Title:
Add SSMTP entry
To manage notifications about this
** Changed in: postfix (Ubuntu)
Status: Confirmed = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to postfix in Ubuntu.
https://bugs.launchpad.net/bugs/774500
Title:
postfix build does not have documented support
** Changed in: bind9 (Ubuntu Precise)
Assignee: (unassigned) = LaMont Jones (lamont)
--
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/920202
Title:
bind9 fails to start on precise
** Changed in: bind9 (Ubuntu Precise)
Status: Triaged = 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/920202
Title:
bind9 fails to start on precise after clean
Public bug reported:
Package fails to configure because of missing dnsmasq. Either it needs
a Depends, or it needs to check before trying to run it.
lamont
--
dpkg --configure --pending
Setting up lxc (0.7.5-3ubuntu19) ...
* Starting Linux Containers
It turns out that I had diverted dnsmasq in my hatred of it. Not a
vaild bug.
** Changed in: lxc (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
** 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/933723
Title:
resolvconf creating bogus resolv.conf file
To manage
** Changed in: bind9 (Ubuntu)
Status: Triaged = 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/681536
Title:
/usr/share/bind9/bind9-default.md5sum should be in
This sounds like 933723 will fix it.
--
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/437783
Title:
bind9 failed to start : resolvconf: Error: /etc/resolv.conf must be a
symlink
To
** Summary changed:
- rndc-confgen does nothing
+ rndc-confgen is silent during key genration
--
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/697609
Title:
rndc-confgen is silent
** Changed in: bind9 (Ubuntu)
Status: Confirmed = 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/929563
Title:
apparmor profile does not include local overrides
The next upload of bind9 will default to not enabling resolvconf, since
there is no way for it to guarantee that it can resolve addresses and is
not behind some egress-filtering firewall.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
The wording was ambiguous, though correct, given that the postinst only
appends an entry. I've updated the text to be less ambiguous.
** Changed in: postfix (Ubuntu)
Status: New = Fix Committed
** Changed in: postfix (Ubuntu)
Assignee: (unassigned) = LaMont Jones (lamont)
--
You
I don't suppose that /var/spool/postfix has a core file in it? if so,
that would be wonderful to have
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to postfix in Ubuntu.
https://bugs.launchpad.net/bugs/970921
Title:
Postfix 2.9.1
Will be in 2.9.1-3
** Changed in: postfix (Ubuntu)
Status: New = Fix Committed
** Changed in: postfix (Ubuntu)
Assignee: (unassigned) = LaMont Jones (lamont)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to postfix
I am unable to reproduce this, but I also lack the mysql setup to really
test this well.
Try this:
# cp /lib/x86_64-linux-gnu/libgcc_s.so.1
/var/spool/postfix/lib/x86_64-linux-gnu/libgcc_s.so.1
and see if the problem goes away, (you may need to repeat that if strace
gives you yet a different
I will be in -3, with a changelog entry that is a bit vague about this
bug.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to postfix in Ubuntu.
https://bugs.launchpad.net/bugs/970921
Title:
Postfix 2.9.1 Crashing with Signal 6 -
fixed in 2.9.1-3
** Changed in: postfix (Ubuntu)
Status: Incomplete = Fix Committed
** Changed in: postfix (Ubuntu)
Assignee: (unassigned) = LaMont Jones (lamont)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to postfix
apparently, it's spelled 'chmod', not 'chown' :(
** Changed in: bind9 (Ubuntu)
Status: New = Fix Committed
** Changed in: bind9 (Ubuntu)
Assignee: (unassigned) = LaMont Jones (lamont)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
Bad code from 2007, I believe that simply making sure that the queue
directory is non-null before copying will fix it.
** Changed in: postfix (Ubuntu)
Status: Confirmed = Fix Committed
** Changed in: postfix (Ubuntu)
Assignee: (unassigned) = LaMont Jones (lamont)
--
You received
Fixed in 2.9.1-5
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to postfix in Ubuntu.
https://bugs.launchpad.net/bugs/980682
Title:
postconf can't open main.cf with the result that /etc/resolvconf
/update-libc.d/postfix fails trying
*** This bug is a duplicate of bug 980682 ***
https://bugs.launchpad.net/bugs/980682
** This bug has been marked a duplicate of bug 980682
postconf can't open main.cf with the result that
/etc/resolvconf/update-libc.d/postfix fails trying to copy /etc/resolv.conf
onto itself
--
You
Public bug reported:
For a variety of reasons, I wound up needing to change the IP address of
a MAAS server. Doing what it said to do at install time (dpkg
--reconfigure maas) was insufficient, and I eventually just reinstalled
the machine as the final fallback solution to fixing the config to
Public bug reported:
If a node failed to commission, and I wish simply to remove it from maas
completely, there is no way to do that from the UI, since the remove
node button is greyed out at that stage. I believe that the failed
state is the same way.
** Affects: maas
Importance:
Public bug reported:
When viewing /MAAS/nodes, it is sometimes useful to sort by hostname
(which may have actually been assigned to something other than the
nodename based on MAC address, as it was in our case). Today that can
only be done by cut-n-paste piped into sort, which is suboptimal.
**
Public bug reported:
dpkg --configure -a
Setting up nova-common (2012.1-0ubuntu2.1) ...
chmod: cannot access `/etc/sudoers.d/nova_sudoers': No such file or directory
dpkg: error processing nova-common (--configure):
subprocess installed post-installation script returned error exit status 1
dpkg:
** Also affects: postfix (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671235
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to postfix in Ubuntu.
Public bug reported:
There does not seem to be a CLI, nor does the python api appear to
provide a way (other than iteration) to find all of the tenants to which
a user belongs. I basically want the rough equivalent of the following
sql:
SELECT tenant.* FROM tenant,user_tenant_membership WHERE
Public bug reported:
ifup -a with lots of new interfaces exposes a race condition in the init
script:
lamont
---
ssh start/running, process 9328
Set name-type for VLAN subsystem. Should be visible in /proc/net/vlan/config
cat: /var/run/sshd.pid: No such file or directory
ERROR: List of
Public bug reported:
Nova uses dnsmasq to answer questions about name - IP resolution for
instances. By default, it does nothing about things where there is no
answer.
This causes dnsmasq to forward the query (for which it should be
authoritative) off to the nameserver found in resolv.conf. If
As discussed in IRC:
If the domain I assign to nova is its own (which I believe it should
be), then it should be authoritative for that zone. As in it shouldn't
go asking the upstream resolver to give it answers for things that are
delegated to it. This is also true of the reverse zone for the
I suspect that the issue here is that the config file was modified
(values set) during install, and then the file changed outside of
debconf later, and then installed again, resulting in postfix honoring
the debconf values it had been told to enforce.
There are several values that postfix expects
** Changed in: postfix (Ubuntu)
Milestone: None = ubuntu-11.10-beta-1
** Changed in: postfix (Ubuntu)
Assignee: (unassigned) = LaMont Jones (lamont)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to postfix in Ubuntu.
https
** Changed in: postfix (Ubuntu)
Status: Confirmed = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to postfix in Ubuntu.
https://bugs.launchpad.net/bugs/530323
Title:
resolvconf update script should not produce
** Changed in: postfix (Ubuntu)
Assignee: (unassigned) = LaMont Jones (lamont)
** Changed in: postfix (Ubuntu)
Status: Confirmed = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to postfix in Ubuntu.
https
** Changed in: postfix (Ubuntu)
Assignee: (unassigned) = LaMont Jones (lamont)
** Changed in: postfix (Ubuntu)
Status: Confirmed = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to postfix in Ubuntu.
https
Lacking a /var/cache/postfix directory, I suppose this belongs in
/var/lib/postfix. It certainly doesn't belong in /var/spool/postfix.
** Changed in: postfix (Ubuntu)
Assignee: (unassigned) = LaMont Jones (lamont)
Status: Confirmed = Fix Committed
--
default main.cf.tls causes
-9 includes more apparmor changes that need to be there for the profile
to be correct. Please sync.
bind9 (1:9.4.2-9) unstable; urgency=low
* apparmor: allow subdirs in {/etc,/var/cache,/var/lib}/bind
* apparmor: make profile match README.Debian
-- LaMont Jones [EMAIL PROTECTED] Tue, 01
Will be in 1:9.4.2-10 and 1:9.5.0~b2-3
** Changed in: bind9 (Ubuntu)
Assignee: (unassigned) = LaMont Jones (lamont)
Status: In Progress = Fix Committed
--
apparmor profile should be in complain for feisty and gutsy upgrades
https://bugs.launchpad.net/bugs/204658
You received
And, as noted in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=291148
, this really needs a complete specification, and should probably be
supported via some new code in start-stop-daemon.
** Changed in: bind9 (Ubuntu)
Status: New = Incomplete
--
status function for init scripts
When investigating the issue we noticed there was an updated version of
ISC DNS Bind that was not incorporated into the most recent Ubuntu 6.06
DNS Bind package.
If you mean bind 9.4.2, that is in 8.04/hardy. However any security
fixes that are found in 9.4.2 should have also been
Russian translation. Closes: #479776
[LaMont Jones]
* meta: fix changelog
* finish cherrypick of 2.5.2~rc2 fixes.
* lintian: don't depend on a -1 version of a package
* meta: fix MySQL/PostgreSQL spelling
* doc-base: change to Network/Communication
[Rudy Godoy Guillén]
* l10n
** Changed in: postfix (Ubuntu)
Status: New = Incomplete
--
Upgrade to 8.04
https://bugs.launchpad.net/bugs/225608
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to postfix in ubuntu.
--
Ubuntu-server-bugs mailing list
: (unassigned) = LaMont Jones (lamont)
Status: New = Invalid
--
Bind9 (8.04) not returning 'ad' flag when dnssec is enabled
https://bugs.launchpad.net/bugs/242956
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in ubuntu
9.5.0 is in intrepid
** Changed in: bind9 (Ubuntu)
Status: Fix Committed = Fix Released
--
bind9 does not support gssapi updates
https://bugs.launchpad.net/bugs/158197
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in
** Changed in: bind9 (Ubuntu)
Assignee: (unassigned) = LaMont Jones (lamont)
Status: Incomplete = Fix Committed
--
status function for init scripts
https://bugs.launchpad.net/bugs/203169
You received this bug notification because you are a member of Ubuntu
Server Team, which
:
bind9 (1:9.5.0.dfsg.P2-1) unstable; urgency=low
[LaMont Jones]
* default to using resolvconf if it is installed
* fix sonames and dependencies. Closes: #149259, #492418
* Do not build-depend libcap2-dev on non-linux. Closes: #493392
* drop unused query-loc manpage. Closes: #492564
) unstable; urgency=low
[Wietse Venema]
* New upstream release:
- Bugfix: dangling pointer in vstring_sprintf_prepend()
- Harden delivery to symlink destinations. CVE-2008-2936
-- LaMont Jones [EMAIL PROTECTED] Wed, 13 Aug 2008 21:21:10 -0600
postfix (2.5.3-1) unstable; urgency=low
** Summary changed:
- Please sync postfix 2.5.2-2 (main) from Debian unstable (main).
+ Please sync postfix 2.5.4-1 (main) from Debian incoming/unstable (main).
--
Please sync postfix 2.5.4-1 (main) from Debian incoming/unstable (main).
https://bugs.launchpad.net/bugs/257893
You received this
It's CVE-2008-2936, and fixed in:
2.2.10-1ubuntu0.2 (dapper)
2.3.8-2ubuntu0.1 (feisty)
2.4.5-3ubuntu1.1 (gutsy)
2.5.1-2ubuntu1 (hardy)
2.5.4-1 (intrepid)
None of these have hit the archive, see also
https://bugs.edge.launchpad.net/ubuntu/+source/postfix/+bug/257893
I'd expect to see the
** Changed in: bind9 (Ubuntu)
Assignee: (unassigned) = LaMont Jones (lamont)
Status: New = Fix Committed
--
dig compiled without -DDIG_SIGCHASE!
https://bugs.launchpad.net/bugs/257682
You received this bug notification because you are a member of Ubuntu
Server Team, which
fixed in 1:9.3.2-2ubuntu1.5, 1:9.3.4-2ubuntu2.3, 1:9.4.1-P1-3ubuntu2,
1:9.4.2-10ubuntu0.1, and 1:9.5.0.dfsg.P1-1
** Changed in: bind9 (Ubuntu)
Status: Fix Committed = Fix Released
--
[CVE-2008-1447] Randomize DNS query source ports to prevent cache poisoning
** Changed in: postfix (Ubuntu)
Status: Confirmed = Fix Committed
--
default postfix config creates backscatter
https://bugs.launchpad.net/bugs/242383
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to postfix in ubuntu.
--
I would love details for how to reproduce this bug. tagged
unreproducible in debian. :-(
--
dpkg-reconfigure postfix partly broken
https://bugs.launchpad.net/bugs/251433
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to postfix in ubuntu.
I cannot find any version of the manpage that includes that text. What
version of bind9 are you looking at?
** Changed in: bind9 (Ubuntu)
Assignee: (unassigned) = LaMont Jones (lamont)
Status: New = Incomplete
--
misleading man page category phrase
https://bugs.launchpad.net/bugs
** Changed in: postfix (Ubuntu)
Assignee: Scott Kitterman (kitterman) = LaMont Jones (lamont)
Status: In Progress = Fix Committed
--
Please add a script to allow filter services to be programatically added to
master.cf
https://bugs.launchpad.net/bugs/247332
You received this bug
is included in debian.
Changelog since current intrepid version 2.5.4-1ubuntu2:
postfix (2.5.5-1) unstable; urgency=low
[Wietse Venema]
* local file descriptor leak with 2.6 kernels and epoll.
-- LaMont Jones [EMAIL PROTECTED] Tue, 02 Sep 2008 07:20:37 -0600
postfix (2.5.4-2) unstable
*** This bug is a duplicate of bug 56235 ***
https://bugs.launchpad.net/bugs/56235
** This bug has been marked a duplicate of bug 56235
Postfix fails to start at boot time
--
postfix upgrade does not replace /etc/postfix/postfix-script
https://bugs.launchpad.net/bugs/265004
You received
The package does not deliver anything in /etc/libexec/postfix, nor does
it set any variables equal to that in main.cf.
The configuration is incorrect, and, based on the bug report, created by
you.
Unless you can show me how installing the package resulted in this
configuration, we'll have to
newaliases: warning: valid_hostname: misplaced delimiter: angel-
desktop.hsd1.wa.comcast.net.
newaliases: fatal: file /etc/postfix/main.cf: parameter myhostname: bad
parameter value: angel-desktop.hsd1.wa.comcast.net.
I rather expect that the issue here is maybe a trailing dot?
--
package
This is because postfix set-permissions assumes that all of the postfix
packages are installed, and they aren't.
There should be no reason to run postfix set-permissions on an ubuntu
machine.
--
postfix set-permissons fails
https://bugs.launchpad.net/bugs/274108
You received this bug
The SIGCHASE code is limited to the dig and host commands, and (as far
as I can tell), any regression would be limited to failures when using
the sigchase options (which currently just say invalid option
+sigchase, so they wouldn't particularly be regressions as much as
continued bugs.) The code
also, yes, there are soname changes. The only consumers of the affected
libraries are packages from the bind9 source, so this is also a non-
issue.
lamont
--
SRU for bind9 to 9.4.2.dfsg.P2 on hardy
https://bugs.launchpad.net/bugs/279316
You received this bug notification because you are a
speaking with my hppa-port lead hat, I agree that having the archive
debootstrappable for intrepid would be good.
please approve this upload.
thanks,
lamont
--
build failure on hppa
https://bugs.launchpad.net/bugs/288908
You received this bug notification because you are a member of Ubuntu
, I expect that postfix wasn't even
starting before the upgrade.
** Changed in: postfix (Ubuntu)
Assignee: (unassigned) = LaMont Jones (lamont)
Status: Incomplete = Invalid
--
package update-manager 1:0.93.32 failed to install/upgrade: ErrorMessage:
SystemError in cache.commit(): E:Sub
I have added the fix into ubuntu as well, will be in the next upload.
** Changed in: bind9 (Ubuntu)
Importance: Undecided = Medium
** Changed in: bind9 (Ubuntu)
Status: Confirmed = In Progress
--
[intrepid] bind9/named IPv6 unusable
https://bugs.launchpad.net/bugs/249824
You received
** Changed in: bind9 (Ubuntu)
Status: In Progress = Fix Committed
--
[intrepid] bind9/named IPv6 unusable
https://bugs.launchpad.net/bugs/249824
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in ubuntu.
--
** Changed in: bind9 (Ubuntu)
Assignee: (unassigned) = LaMont Jones (lamont)
Status: In Progress = Fix Committed
--
named bind9 apparmor profile error
https://bugs.launchpad.net/bugs/289060
You received this bug notification because you are a member of Ubuntu
Server Team, which
** Changed in: bind9 (Ubuntu)
Status: New = Fix Committed
--
apparmor error when logging to /var/log/named/
https://bugs.launchpad.net/bugs/294935
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in ubuntu.
--
** Changed in: bind9 (Ubuntu)
Importance: Undecided = Wishlist
--
Prints error messages to stdout
https://bugs.launchpad.net/bugs/300226
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in ubuntu.
--
Ubuntu-server-bugs mailing
** Changed in: bind9 (Ubuntu)
Assignee: (unassigned) = LaMont Jones (lamont)
Status: New = Fix Committed
--
apparmor exception missing for keytab
https://bugs.launchpad.net/bugs/277370
You received this bug notification because you are a member of Ubuntu
Server Team, which
Fixed in 1:9.9.3.dfsg.P2-3
** Changed in: bind9 (Ubuntu)
Status: Confirmed = Fix Released
** Also affects: bind9 (Ubuntu Precise)
Importance: Undecided
Status: New
** Changed in: bind9 (Ubuntu Precise)
Status: New = Confirmed
** Changed in: bind9 (Ubuntu Precise)
/var/tmp/* rw,
I would much rather have named using some more protected directory, like
maybe /var/cache/bind or some such. Otherwise I don't have any issue
with this.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in
This will be in 1:9.9.3.dfsg.P2-4
** Changed in: bind9 (Ubuntu)
Status: Confirmed = 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/1092243
Title:
*** This bug is a duplicate of bug 1099458 ***
https://bugs.launchpad.net/bugs/1099458
** Summary changed:
- /etc/init.d/bind9.dpkg-dist file is left over after lucid to precise main and
universe upgrades
+ /etc/init.d/bind9.dpkg-dist file is left over after upgrade
** This bug has been
** Bug watch added: Debian Bug tracker #701704
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701704
** Also affects: bind9 (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701704
Importance: Unknown
Status: Unknown
--
You received this bug notification because
** Changed in: bind9 (Ubuntu)
Status: Triaged = 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/834901
Title:
Apparmor profile blocks geoip db access
To manage
** Summary changed:
- /etc/init.d/bind9.dpkg-dist file is left over after quantal to raring server
upgrades
+ /etc/init.d/bind9.dpkg-dist file is left over after upgrade
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in
** Changed in: bind9 (Ubuntu)
Status: Confirmed = 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/1115168
Title:
add --enable-filter- compilation option
To
Postfix delivers no /usr/bin/mail, nor any mail user agent.
** Package changed: postfix (Ubuntu) = bsd-mailx (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bsd-mailx in Ubuntu.
https://bugs.launchpad.net/bugs/1222179
Title:
Fixed in 2.10.2-1
** Changed in: postfix (Ubuntu Saucy)
Status: Triaged = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to postfix in Ubuntu.
https://bugs.launchpad.net/bugs/1222180
Title:
postfix package
1 - 100 of 208 matches
Mail list logo
