[Bug 1839216] [NEW] xenial VM hangs copying block device

[LaMont Jones]

Public bug reported:

With a Xenial kernel running in a VM (32 cores and 65536 MB RAM), the
following script hangs in the dd command:

==
#!/bin/bash
dd if=/dev/zero of=in.bin bs=1 seek=6442506751 count=1
cp in.bin out.bin
IN=$(losetup --show -f in.bin)
OUT=$(losetup --show -f out.bin)
typeset -i i=1
while true; do
  echo $i $(date)
  dd if=$IN of=$OUT bs=128k
  i=i+1
done
==

The trace (sorry, I don't have the exact kernel version... I found this 
mid-June 2019) looks like:
# cat /proc/5230/stack 
[<0>] io_schedule+0x16/0x40
[<0>] wbt_wait+0x234/0x390
[<0>] blk_mq_make_request+0x103/0x590
[<0>] generic_make_request+0x122/0x2f0
[<0>] submit_bio+0x73/0x150
[<0>] submit_bh_wbc+0x17a/0x1b0
[<0>] __block_write_full_page+0x15b/0x400
[<0>] block_write_full_page+0x10c/0x130
[<0>] blkdev_writepage+0x18/0x20
[<0>] __writepage+0x1d/0x50
[<0>] write_cache_pages+0x228/0x4b0
[<0>] generic_writepages+0x5c/0x90
[<0>] blkdev_writepages+0x2f/0x40
[<0>] do_writepages+0x1f/0x70
[<0>] __filemap_fdatawrite_range+0xc6/0x100
[<0>] filemap_write_and_wait+0x31/0x90
[<0>] __blkdev_put+0x7a/0x210
[<0>] blkdev_put+0x4c/0xd0
[<0>] blkdev_close+0x34/0x70
[<0>] __fput+0xea/0x220
[<0>] fput+0xe/0x10
[<0>] task_work_run+0x9a/0xc0
[<0>] exit_to_usermode_loop+0xce/0xd0
[<0>] do_syscall_64+0x116/0x150
[<0>] entry_SYSCALL_64_after_hwframe+0x42/0xb7
[<0>] 0x

If we have used strace on the process, we find that dd is inside
"close(1)" as it closes the output file.

I don't know if this would reproduce on actual hardware, as I don't have
a machine that large to play with.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1839216

Title:
  xenial VM hangs copying block device

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839216/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Kernel-packages] [Bug 1839216] [NEW] xenial VM hangs copying block device

[LaMont Jones]

Public bug reported:

With a Xenial kernel running in a VM (32 cores and 65536 MB RAM), the
following script hangs in the dd command:

==
#!/bin/bash
dd if=/dev/zero of=in.bin bs=1 seek=6442506751 count=1
cp in.bin out.bin
IN=$(losetup --show -f in.bin)
OUT=$(losetup --show -f out.bin)
typeset -i i=1
while true; do
  echo $i $(date)
  dd if=$IN of=$OUT bs=128k
  i=i+1
done
==

The trace (sorry, I don't have the exact kernel version... I found this 
mid-June 2019) looks like:
# cat /proc/5230/stack 
[<0>] io_schedule+0x16/0x40
[<0>] wbt_wait+0x234/0x390
[<0>] blk_mq_make_request+0x103/0x590
[<0>] generic_make_request+0x122/0x2f0
[<0>] submit_bio+0x73/0x150
[<0>] submit_bh_wbc+0x17a/0x1b0
[<0>] __block_write_full_page+0x15b/0x400
[<0>] block_write_full_page+0x10c/0x130
[<0>] blkdev_writepage+0x18/0x20
[<0>] __writepage+0x1d/0x50
[<0>] write_cache_pages+0x228/0x4b0
[<0>] generic_writepages+0x5c/0x90
[<0>] blkdev_writepages+0x2f/0x40
[<0>] do_writepages+0x1f/0x70
[<0>] __filemap_fdatawrite_range+0xc6/0x100
[<0>] filemap_write_and_wait+0x31/0x90
[<0>] __blkdev_put+0x7a/0x210
[<0>] blkdev_put+0x4c/0xd0
[<0>] blkdev_close+0x34/0x70
[<0>] __fput+0xea/0x220
[<0>] fput+0xe/0x10
[<0>] task_work_run+0x9a/0xc0
[<0>] exit_to_usermode_loop+0xce/0xd0
[<0>] do_syscall_64+0x116/0x150
[<0>] entry_SYSCALL_64_after_hwframe+0x42/0xb7
[<0>] 0x

If we have used strace on the process, we find that dd is inside
"close(1)" as it closes the output file.

I don't know if this would reproduce on actual hardware, as I don't have
a machine that large to play with.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1839216

Title:
  xenial VM hangs copying block device

Status in linux package in Ubuntu:
  New

Bug description:
  With a Xenial kernel running in a VM (32 cores and 65536 MB RAM), the
  following script hangs in the dd command:

  
==
  #!/bin/bash
  dd if=/dev/zero of=in.bin bs=1 seek=6442506751 count=1
  cp in.bin out.bin
  IN=$(losetup --show -f in.bin)
  OUT=$(losetup --show -f out.bin)
  typeset -i i=1
  while true; do
echo $i $(date)
dd if=$IN of=$OUT bs=128k
i=i+1
  done
  
==

  The trace (sorry, I don't have the exact kernel version... I found this 
mid-June 2019) looks like:
  # cat /proc/5230/stack 
  [<0>] io_schedule+0x16/0x40
  [<0>] wbt_wait+0x234/0x390
  [<0>] blk_mq_make_request+0x103/0x590
  [<0>] generic_make_request+0x122/0x2f0
  [<0>] submit_bio+0x73/0x150
  [<0>] submit_bh_wbc+0x17a/0x1b0
  [<0>] __block_write_full_page+0x15b/0x400
  [<0>] block_write_full_page+0x10c/0x130
  [<0>] blkdev_writepage+0x18/0x20
  [<0>] __writepage+0x1d/0x50
  [<0>] write_cache_pages+0x228/0x4b0
  [<0>] generic_writepages+0x5c/0x90
  [<0>] blkdev_writepages+0x2f/0x40
  [<0>] do_writepages+0x1f/0x70
  [<0>] __filemap_fdatawrite_range+0xc6/0x100
  [<0>] filemap_write_and_wait+0x31/0x90
  [<0>] __blkdev_put+0x7a/0x210
  [<0>] blkdev_put+0x4c/0xd0
  [<0>] blkdev_close+0x34/0x70
  [<0>] __fput+0xea/0x220
  [<0>] fput+0xe/0x10
  [<0>] task_work_run+0x9a/0xc0
  [<0>] exit_to_usermode_loop+0xce/0xd0
  [<0>] do_syscall_64+0x116/0x150
  [<0>] entry_SYSCALL_64_after_hwframe+0x42/0xb7
  [<0>] 0x

  If we have used strace on the process, we find that dd is inside
  "close(1)" as it closes the output file.

  I don't know if this would reproduce on actual hardware, as I don't
  have a machine that large to play with.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839216/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Bug 1090593] Re: D.ROOT-SERVERS.NET changing January 3rd 2013

[LaMont Jones]

Precise reached EOL some time ago.  Marking this "won't fix"

** Changed in: bind9 (Ubuntu Precise)
   Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1090593

Title:
   D.ROOT-SERVERS.NET changing January 3rd 2013

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1090593/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1553176] Re: BIND ignores nanoseconds field in timestamps, fails to load newer versions of zones on reload

[LaMont Jones]

** Changed in: maas/1.9
 Assignee: LaMont Jones (lamont) => (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1553176

Title:
  BIND ignores nanoseconds field in timestamps, fails to load newer
  versions of zones on reload

To manage notifications about this bug go to:
https://bugs.launchpad.net/bind/+bug/1553176/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: bind9 shipping outdated root hint file (etc.)

[LaMont Jones]

On Tue, Aug 08, 2017 at 04:47:27PM -0400, Chris Lamb wrote:
> It was just mentioned "en passant" in a conversation at DebConf that
> bind9 is shipping a root hint file from 2003.

The version of db.root in stretch is from Feb 17, 2016.  I suspect that the
comment originates from the fact that I've never done any backports to
stable releases, nor do I particularly want to do so.  Others have been
doing that.

> I had a quick glance at the bug list and saw it was a little larger
> than I would have liked for what is clearly a critical piece and
> infrastructure. :)
> 
> Lamont, can you comment? Anyone interested in helping out here…?

There are a couple of people who are working with me on it, as per the
control file in the package.  Many of the bugs are more minor, or asking
for upstream development, or asking when some feature will be backported
to a stable release.  I tend to not close those bugs out of hand, so the
bug list is both accurate and overstating.

lamont

Bug#857465: Postfix-3.1.4 reintroduces bug 214741

[LaMont Jones]

tags 857465 + wontfix
--

I believe that the postinst does the best it can at getting the FQDN into
main.cf -- this doesn't do much for the upgrade path though.

I agree with upstream that postfix should not be calling gethostbyname
at runtime -- if this is happening in a fresh install, then I'm interested
in the configuration of the host that led to this, so that we can make that
path work better.

lamont

On Sat, May 20, 2017 at 12:29:15PM +0100, James Cowgill wrote:
> On 11/03/17 16:32, Herwig Burgert wrote:
> > Package: postfix
> > 
> > Version: 3.1.4-4
> > 
> > Description:
> > 
> > postfix-3.1.4 currently part of the upcoming release of strech
> > reintroduces bug 214741 which was fixed for postfix-2.11.3 (jessie). -
> > Fetch the correct FQDN for myhostname.
> > For details on this bug see:
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=214741.
> 
> FWIW, this was also broken for me when I setup my new postfix server
> (postfix was convinced my domain was "localdomain"). I gave up and
> hardcoded the correct mydomain in main.cf.
> 
> James
> 
> 

[Touch-packages] [Bug 1683911] [NEW] ifup places illegally named variables into the environment

[LaMont Jones]

Public bug reported:

When dhclient brings up interface eth0.55, the environment passed to scripts 
includes:
IFUPDOWN_eth0=parent-lock
IFUPDOWN_eth0.55=post-up
IFACE=eth0.55
LOGICAL=eth0.55
ADDRFAM=inet
METHOD=dhcp
MODE=start
PHASE=post-up
VERBOSITY=0
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

IFUPDOWN_eth0.55 is not a valid name for an environment variable.

** Affects: ifupdown (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1683911

Title:
  ifup places illegally named variables into the environment

Status in ifupdown package in Ubuntu:
  New

Bug description:
  When dhclient brings up interface eth0.55, the environment passed to scripts 
includes:
  IFUPDOWN_eth0=parent-lock
  IFUPDOWN_eth0.55=post-up
  IFACE=eth0.55
  LOGICAL=eth0.55
  ADDRFAM=inet
  METHOD=dhcp
  MODE=start
  PHASE=post-up
  VERBOSITY=0
  PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

  IFUPDOWN_eth0.55 is not a valid name for an environment variable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1683911/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Bug 1683911] [NEW] ifup places illegally named variables into the environment

[LaMont Jones]

Public bug reported:

When dhclient brings up interface eth0.55, the environment passed to scripts 
includes:
IFUPDOWN_eth0=parent-lock
IFUPDOWN_eth0.55=post-up
IFACE=eth0.55
LOGICAL=eth0.55
ADDRFAM=inet
METHOD=dhcp
MODE=start
PHASE=post-up
VERBOSITY=0
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

IFUPDOWN_eth0.55 is not a valid name for an environment variable.

** Affects: ifupdown (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1683911

Title:
  ifup places illegally named variables into the environment

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1683911/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Touch-packages] [Bug 1408106] Re: attach_disconnected not sufficient for overlayfs

[LaMont Jones]

This bug causes maas testing to fail (at least the ntp test, because of
overlayfs and apparmor and ntp having a profile.) See
https://bugs.launchpad.net/maas/+bug/1677336

Hardware testing is a requirement for MAAS 2.2.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1408106

Title:
  attach_disconnected not sufficient for overlayfs

Status in AppArmor:
  In Progress
Status in MAAS:
  New
Status in apparmor package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Triaged

Bug description:
  With the following use of overlayfs, we get a disconnected path:

  $ cat ./profile
  #include 
  profile foo {
    #include 

    capability sys_admin,
    capability sys_chroot,
    mount,
    pivot_root,
  }

  $ cat ./overlay.c
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 

  int main(int argc, char* argv[]) {
  int i = 0;
  int len = 0;
  int ret = 0;
  char* options;

  if (geteuid())
  unshare(CLONE_NEWUSER);
  unshare(CLONE_NEWNS);

  for (i = 1; i < argc; i++) {
  if (i == 1) {
  len = strlen(argv[i]) + strlen("upperdir=,lowerdir=/") + 2;
  options = alloca(len);
  ret = snprintf(options, len, "upperdir=%s,lowerdir=/", argv[i]);
  }
  else {
  len = strlen(argv[i]) + strlen("upperdir=,lowerdir=/mnt") + 2;
  options = alloca(len);
  ret = snprintf(options, len, "upperdir=%s,lowerdir=/mnt", 
argv[i]);
  }

  mount("overlayfs", "/mnt", "overlayfs", MS_MGC_VAL, options);
  }

  chdir("/mnt");
  pivot_root(".", ".");
  chroot(".");

  chdir("/");
  execl("/bin/bash", "/bin/bash", NULL);
  }

  $ sudo apparmor_parser -r ./profile && aa-exec -p foo -- ./a.out /tmp
  [255]
  ...
  Dec 12 14:31:38 localhost kernel: [57278.040216] audit: type=1400 
audit(1418387498.613:712): apparmor="DENIED" operation="exec" info="Failed name 
lookup - disconnected path" error=-13 profile="foo" name="/bin/bash" pid=18255 
comm="a.out" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0

  With the above, the expectation was for the denial to be /mnt/bin/bash. There 
are three ways forward:
  1. the correct solution is to patch overlayfs to properly track the loopback, 
but this will take a while, may ultimately be unachievable. UPDATE: upstream is 
currently working on this and Ubuntu will engage with them
  2. we could rely on the fact that overlayfs creates a private unshared 
submount, and provide a way to not mediate the path when that is present, and 
tagged. This would take a bit of time, and might be the preferred method over 1 
longer term
  3. we could extend attach_disconnected so that we can define the attach root. 
Eg, we can use profile foo (attach_disconnected=/mnt) {} such that '/bin/bash' 
maps to '/mnt/bin/bash'. UPDATE: THIS IS NOT VIABLE

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1408106/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1408106] Re: attach_disconnected not sufficient for overlayfs

[LaMont Jones]

This bug causes maas testing to fail (at least the ntp test, because of
overlayfs and apparmor and ntp having a profile.) See
https://bugs.launchpad.net/maas/+bug/1677336

Hardware testing is a requirement for MAAS 2.2.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1408106

Title:
  attach_disconnected not sufficient for overlayfs

Status in AppArmor:
  In Progress
Status in MAAS:
  New
Status in apparmor package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Triaged

Bug description:
  With the following use of overlayfs, we get a disconnected path:

  $ cat ./profile
  #include 
  profile foo {
    #include 

    capability sys_admin,
    capability sys_chroot,
    mount,
    pivot_root,
  }

  $ cat ./overlay.c
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 

  int main(int argc, char* argv[]) {
  int i = 0;
  int len = 0;
  int ret = 0;
  char* options;

  if (geteuid())
  unshare(CLONE_NEWUSER);
  unshare(CLONE_NEWNS);

  for (i = 1; i < argc; i++) {
  if (i == 1) {
  len = strlen(argv[i]) + strlen("upperdir=,lowerdir=/") + 2;
  options = alloca(len);
  ret = snprintf(options, len, "upperdir=%s,lowerdir=/", argv[i]);
  }
  else {
  len = strlen(argv[i]) + strlen("upperdir=,lowerdir=/mnt") + 2;
  options = alloca(len);
  ret = snprintf(options, len, "upperdir=%s,lowerdir=/mnt", 
argv[i]);
  }

  mount("overlayfs", "/mnt", "overlayfs", MS_MGC_VAL, options);
  }

  chdir("/mnt");
  pivot_root(".", ".");
  chroot(".");

  chdir("/");
  execl("/bin/bash", "/bin/bash", NULL);
  }

  $ sudo apparmor_parser -r ./profile && aa-exec -p foo -- ./a.out /tmp
  [255]
  ...
  Dec 12 14:31:38 localhost kernel: [57278.040216] audit: type=1400 
audit(1418387498.613:712): apparmor="DENIED" operation="exec" info="Failed name 
lookup - disconnected path" error=-13 profile="foo" name="/bin/bash" pid=18255 
comm="a.out" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0

  With the above, the expectation was for the denial to be /mnt/bin/bash. There 
are three ways forward:
  1. the correct solution is to patch overlayfs to properly track the loopback, 
but this will take a while, may ultimately be unachievable. UPDATE: upstream is 
currently working on this and Ubuntu will engage with them
  2. we could rely on the fact that overlayfs creates a private unshared 
submount, and provide a way to not mediate the path when that is present, and 
tagged. This would take a bit of time, and might be the preferred method over 1 
longer term
  3. we could extend attach_disconnected so that we can define the attach root. 
Eg, we can use profile foo (attach_disconnected=/mnt) {} such that '/bin/bash' 
maps to '/mnt/bin/bash'. UPDATE: THIS IS NOT VIABLE

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1408106/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Bug 1408106] Re: attach_disconnected not sufficient for overlayfs

[LaMont Jones]

This bug causes maas testing to fail (at least the ntp test, because of
overlayfs and apparmor and ntp having a profile.) See
https://bugs.launchpad.net/maas/+bug/1677336

Hardware testing is a requirement for MAAS 2.2.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1408106

Title:
  attach_disconnected not sufficient for overlayfs

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1408106/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1408106] Re: attach_disconnected not sufficient for overlayfs

[LaMont Jones]

** Also affects: maas
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1408106

Title:
  attach_disconnected not sufficient for overlayfs

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1408106/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Kernel-packages] [Bug 1408106] Re: attach_disconnected not sufficient for overlayfs

[LaMont Jones]

** Also affects: maas
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1408106

Title:
  attach_disconnected not sufficient for overlayfs

Status in AppArmor:
  In Progress
Status in MAAS:
  New
Status in apparmor package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Triaged

Bug description:
  With the following use of overlayfs, we get a disconnected path:

  $ cat ./profile
  #include 
  profile foo {
    #include 

    capability sys_admin,
    capability sys_chroot,
    mount,
    pivot_root,
  }

  $ cat ./overlay.c
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 

  int main(int argc, char* argv[]) {
  int i = 0;
  int len = 0;
  int ret = 0;
  char* options;

  if (geteuid())
  unshare(CLONE_NEWUSER);
  unshare(CLONE_NEWNS);

  for (i = 1; i < argc; i++) {
  if (i == 1) {
  len = strlen(argv[i]) + strlen("upperdir=,lowerdir=/") + 2;
  options = alloca(len);
  ret = snprintf(options, len, "upperdir=%s,lowerdir=/", argv[i]);
  }
  else {
  len = strlen(argv[i]) + strlen("upperdir=,lowerdir=/mnt") + 2;
  options = alloca(len);
  ret = snprintf(options, len, "upperdir=%s,lowerdir=/mnt", 
argv[i]);
  }

  mount("overlayfs", "/mnt", "overlayfs", MS_MGC_VAL, options);
  }

  chdir("/mnt");
  pivot_root(".", ".");
  chroot(".");

  chdir("/");
  execl("/bin/bash", "/bin/bash", NULL);
  }

  $ sudo apparmor_parser -r ./profile && aa-exec -p foo -- ./a.out /tmp
  [255]
  ...
  Dec 12 14:31:38 localhost kernel: [57278.040216] audit: type=1400 
audit(1418387498.613:712): apparmor="DENIED" operation="exec" info="Failed name 
lookup - disconnected path" error=-13 profile="foo" name="/bin/bash" pid=18255 
comm="a.out" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0

  With the above, the expectation was for the denial to be /mnt/bin/bash. There 
are three ways forward:
  1. the correct solution is to patch overlayfs to properly track the loopback, 
but this will take a while, may ultimately be unachievable. UPDATE: upstream is 
currently working on this and Ubuntu will engage with them
  2. we could rely on the fact that overlayfs creates a private unshared 
submount, and provide a way to not mediate the path when that is present, and 
tagged. This would take a bit of time, and might be the preferred method over 1 
longer term
  3. we could extend attach_disconnected so that we can define the attach root. 
Eg, we can use profile foo (attach_disconnected=/mnt) {} such that '/bin/bash' 
maps to '/mnt/bin/bash'. UPDATE: THIS IS NOT VIABLE

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1408106/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1408106] Re: attach_disconnected not sufficient for overlayfs

[LaMont Jones]

** Also affects: maas
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1408106

Title:
  attach_disconnected not sufficient for overlayfs

Status in AppArmor:
  In Progress
Status in MAAS:
  New
Status in apparmor package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Triaged

Bug description:
  With the following use of overlayfs, we get a disconnected path:

  $ cat ./profile
  #include 
  profile foo {
    #include 

    capability sys_admin,
    capability sys_chroot,
    mount,
    pivot_root,
  }

  $ cat ./overlay.c
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 

  int main(int argc, char* argv[]) {
  int i = 0;
  int len = 0;
  int ret = 0;
  char* options;

  if (geteuid())
  unshare(CLONE_NEWUSER);
  unshare(CLONE_NEWNS);

  for (i = 1; i < argc; i++) {
  if (i == 1) {
  len = strlen(argv[i]) + strlen("upperdir=,lowerdir=/") + 2;
  options = alloca(len);
  ret = snprintf(options, len, "upperdir=%s,lowerdir=/", argv[i]);
  }
  else {
  len = strlen(argv[i]) + strlen("upperdir=,lowerdir=/mnt") + 2;
  options = alloca(len);
  ret = snprintf(options, len, "upperdir=%s,lowerdir=/mnt", 
argv[i]);
  }

  mount("overlayfs", "/mnt", "overlayfs", MS_MGC_VAL, options);
  }

  chdir("/mnt");
  pivot_root(".", ".");
  chroot(".");

  chdir("/");
  execl("/bin/bash", "/bin/bash", NULL);
  }

  $ sudo apparmor_parser -r ./profile && aa-exec -p foo -- ./a.out /tmp
  [255]
  ...
  Dec 12 14:31:38 localhost kernel: [57278.040216] audit: type=1400 
audit(1418387498.613:712): apparmor="DENIED" operation="exec" info="Failed name 
lookup - disconnected path" error=-13 profile="foo" name="/bin/bash" pid=18255 
comm="a.out" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0

  With the above, the expectation was for the denial to be /mnt/bin/bash. There 
are three ways forward:
  1. the correct solution is to patch overlayfs to properly track the loopback, 
but this will take a while, may ultimately be unachievable. UPDATE: upstream is 
currently working on this and Ubuntu will engage with them
  2. we could rely on the fact that overlayfs creates a private unshared 
submount, and provide a way to not mediate the path when that is present, and 
tagged. This would take a bit of time, and might be the preferred method over 1 
longer term
  3. we could extend attach_disconnected so that we can define the attach root. 
Eg, we can use profile foo (attach_disconnected=/mnt) {} such that '/bin/bash' 
maps to '/mnt/bin/bash'. UPDATE: THIS IS NOT VIABLE

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1408106/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Re: maas hooks/triggers for dns (de-)registration

[LaMont Jones]

On Wed, Mar 29, 2017 at 03:36:19PM +0200, Patrizio Bassi wrote:
> 2017-03-29 15:18 GMT+02:00 Andres Rodriguez 
> :
> 
> > Hi Patrizio,
> >
> > I have an external dns providing name resolution for bare metal machines
> >> and everything works fine.
> >> Basically we have a subnet 10.10.xxx.xxx/16 allocated where first
> >> addresses are statically registered in the dns server, while the others are
> >> "assigned" (meaning, without any hostname association) to maas so it can
> >> dynamically use them.
> >>
> >
> > Does this mean that your machines in MAAS share the same hostname as those
> > in your upstream DNS server? Are you configuring MAAS DNS to point to the
> > upstream DNS (Under the Settings page). This would allow MAAS to use your
> > upstream DNS server to resolve for domains names MAAS doesn't know about.
> >
> 
> Dear Andres,
> 
> MAAS is configured like this:
> 1) under global settings it has the upstream DNS (Infoblox) to resolve
> hostnames it doesn't know, this dns list is passed to maas-deployed
> machines too
> 2) the upstream DNS has some (read: first 50s) ips/hostnames already
> configured in the network 10.x.x.x we are using
> 3) under DNS settings MAAS has the domain configured as not Authoritative.
> in the Subnet network, infact i reserved the first 50 ips not to be used by
> MAAS (statically allocated in our upstream dns)
> 4) when MAAS commissions a machine or a juju container it can allocate
> ip/hostname  without problems but, as it's not authoritative and as our
> clients are pointing to upstream dns, we do need to notify upstream server
> to add new entry (and remove when it's gone)

The better solution would be to have the infoblox DNS delegate a zone to
MAAS and slave it.  Even if that means using an RFC2317 network.  (MAAS
will happily work with that.)  Then the entries get added and removed
for you, and the slave zone (since you added the NS RR pointing at
it...) will get notified and refresh.

MAAS really needs to be authoritative for the netblock that it's
managing.  That reality drove the DNS design, not the other way around.

lamont

-- 
Maas-devel mailing list
Maas-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/maas-devel

[Bug 1673253] Re: "Screen Display" icon is missing from System Settings

[LaMont Jones]

I can confirm that downgrading from 15.04.0+17.04.20170314-0ubuntu1 to
15.04.0+17.04.20170213-0ubuntu1 makes the Display Icon return.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1673253

Title:
  "Screen Display" icon is missing from System Settings

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1673253/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Desktop-packages] [Bug 1673253] Re: "Screen Display" icon is missing from System Settings

[LaMont Jones]

I can confirm that downgrading from 15.04.0+17.04.20170314-0ubuntu1 to
15.04.0+17.04.20170213-0ubuntu1 makes the Display Icon return.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1673253

Title:
  "Screen Display" icon is missing from System Settings

Status in unity-control-center package in Ubuntu:
  Fix Committed

Bug description:
  After shoving in a new Nvidia GeForce 8400GS (and trying the
  proprietary drivers out), the Screen Display icon is completely
  missing from the Systems Settings on my machine.

  I'd kinda like it back. :/  Please let me know what other info you may
  need.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: unity-control-center 15.04.0+17.04.20170314-0ubuntu1
  ProcVersionSignature: Ubuntu 
4.4.0-14.30~lp1543683LatestXenialWithRevert-generic 4.4.5
  Uname: Linux 4.4.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Wed Mar 15 14:35:38 2017
  InstallationDate: Installed on 2014-09-22 (905 days ago)
  InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  SourcePackage: unity-control-center
  UpgradeStatus: Upgraded to zesty on 2014-11-14 (852 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1673253/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Bug 1673253] [NEW] "Screen Display" icon is missing from System Settings

[LaMont Jones]

Public bug reported:

After shoving in a new Nvidia GeForce 8400GS (and trying the proprietary
drivers out), the Screen Display icon is completely missing from the
Systems Settings on my machine.

I'd kinda like it back. :/  Please let me know what other info you may
need.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: unity-control-center 15.04.0+17.04.20170314-0ubuntu1
ProcVersionSignature: Ubuntu 
4.4.0-14.30~lp1543683LatestXenialWithRevert-generic 4.4.5
Uname: Linux 4.4.0-14-generic x86_64
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity:Unity7
Date: Wed Mar 15 14:35:38 2017
InstallationDate: Installed on 2014-09-22 (905 days ago)
InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
SourcePackage: unity-control-center
UpgradeStatus: Upgraded to zesty on 2014-11-14 (852 days ago)

** Affects: unity-control-center (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug zesty

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1673253

Title:
  "Screen Display" icon is missing from System Settings

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1673253/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Desktop-packages] [Bug 1673253] [NEW] "Screen Display" icon is missing from System Settings

[LaMont Jones]

Public bug reported:

After shoving in a new Nvidia GeForce 8400GS (and trying the proprietary
drivers out), the Screen Display icon is completely missing from the
Systems Settings on my machine.

I'd kinda like it back. :/  Please let me know what other info you may
need.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: unity-control-center 15.04.0+17.04.20170314-0ubuntu1
ProcVersionSignature: Ubuntu 
4.4.0-14.30~lp1543683LatestXenialWithRevert-generic 4.4.5
Uname: Linux 4.4.0-14-generic x86_64
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity:Unity7
Date: Wed Mar 15 14:35:38 2017
InstallationDate: Installed on 2014-09-22 (905 days ago)
InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
SourcePackage: unity-control-center
UpgradeStatus: Upgraded to zesty on 2014-11-14 (852 days ago)

** Affects: unity-control-center (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug zesty

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1673253

Title:
  "Screen Display" icon is missing from System Settings

Status in unity-control-center package in Ubuntu:
  New

Bug description:
  After shoving in a new Nvidia GeForce 8400GS (and trying the
  proprietary drivers out), the Screen Display icon is completely
  missing from the Systems Settings on my machine.

  I'd kinda like it back. :/  Please let me know what other info you may
  need.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: unity-control-center 15.04.0+17.04.20170314-0ubuntu1
  ProcVersionSignature: Ubuntu 
4.4.0-14.30~lp1543683LatestXenialWithRevert-generic 4.4.5
  Uname: Linux 4.4.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Wed Mar 15 14:35:38 2017
  InstallationDate: Installed on 2014-09-22 (905 days ago)
  InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  SourcePackage: unity-control-center
  UpgradeStatus: Upgraded to zesty on 2014-11-14 (852 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1673253/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Bug 1661691] Re: TERM=xterm enables mouse mode in vi, breaks pasting with middle mouse

[LaMont Jones]

Also true when TERM=screen -- I suspect it doesn't care what terminal
you're using, if it can grab mouse events, it does.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1661691

Title:
  TERM=xterm enables mouse mode in vi, breaks pasting with middle mouse

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1661691/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Touch-packages] [Bug 1661691] Re: TERM=xterm enables mouse mode in vi, breaks pasting with middle mouse

[LaMont Jones]

Also true when TERM=screen -- I suspect it doesn't care what terminal
you're using, if it can grab mouse events, it does.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/1661691

Title:
  TERM=xterm enables mouse mode in vi, breaks pasting with middle mouse

Status in vim package in Ubuntu:
  Confirmed

Bug description:
  I quite often have the following work flow:

  a.) lxc launch ubuntu-daily:zesty z1
  b.) lxc exec z1 /bin/bash
  c.) % vi foo.txt
  d.) paste some thing from my X buffer (hit middle mouse button).

  Somewhere between yakkety (2:7.4.1829-1ubuntu2.1) and zesty
  (2:8.0.0095-1ubuntu2) this behavior changed.

  Previously this all worked fine.

  Now, in zesty, however an attempt to paste results in a vi error message:
   E353: Nothing in register "

  to fix this, you can first disable the mouse 'a' [1]

   : set mouse-=a

  
  I'm not sure what is enabling this, because /usr/share/vim/vimrc has the line
  set mouse=a commented out.

  --
  [1] 
http://www.varesano.net/blog/fabio/disable%20vim%20automatic%20visual%20mode%20using%20mouse

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: vim-nox 2:8.0.0095-1ubuntu2
  ProcVersionSignature: Ubuntu 4.9.0-12.13-generic 4.9.2
  Uname: Linux 4.9.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb  3 12:14:20 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (561 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  SourcePackage: vim
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1661691/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1661691] Re: TERM=xterm enables mouse mode in vi, breaks pasting with middle mouse

[LaMont Jones]

A very unexpected, and totally unwelcome change to vim.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/1661691

Title:
  TERM=xterm enables mouse mode in vi, breaks pasting with middle mouse

Status in vim package in Ubuntu:
  Confirmed

Bug description:
  I quite often have the following work flow:

  a.) lxc launch ubuntu-daily:zesty z1
  b.) lxc exec z1 /bin/bash
  c.) % vi foo.txt
  d.) paste some thing from my X buffer (hit middle mouse button).

  Somewhere between yakkety (2:7.4.1829-1ubuntu2.1) and zesty
  (2:8.0.0095-1ubuntu2) this behavior changed.

  Previously this all worked fine.

  Now, in zesty, however an attempt to paste results in a vi error message:
   E353: Nothing in register "

  to fix this, you can first disable the mouse 'a' [1]

   : set mouse-=a

  
  I'm not sure what is enabling this, because /usr/share/vim/vimrc has the line
  set mouse=a commented out.

  --
  [1] 
http://www.varesano.net/blog/fabio/disable%20vim%20automatic%20visual%20mode%20using%20mouse

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: vim-nox 2:8.0.0095-1ubuntu2
  ProcVersionSignature: Ubuntu 4.9.0-12.13-generic 4.9.2
  Uname: Linux 4.9.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb  3 12:14:20 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (561 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  SourcePackage: vim
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1661691/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Bug 1661691] Re: TERM=xterm enables mouse mode in vi, breaks pasting with middle mouse

[LaMont Jones]

A very unexpected, and totally unwelcome change to vim.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1661691

Title:
  TERM=xterm enables mouse mode in vi, breaks pasting with middle mouse

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1661691/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Touch-packages] [Bug 1640147] Re: [2.1] rsyslog is flooded with "no link-local IPv6 address for $IFACE" on commissioning

[LaMont Jones]

** Changed in: maas/2.1
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1640147

Title:
  [2.1] rsyslog is flooded with "no link-local IPv6 address for $IFACE"
  on commissioning

Status in MAAS:
  Fix Committed
Status in MAAS 2.1 series:
  In Progress
Status in isc-dhcp package in Ubuntu:
  Invalid

Bug description:
  When commissioning, /var/log/maas/rsyslog/ is flooded with the
  repeated messages below with over 30,000 lines.

  
  Nov  8 11:57:54 bunyip dhclient[4734]: no link-local IPv6 address for enp4s0f0
  Nov  8 11:57:54 bunyip dhclient[4734]: 
  Nov  8 11:57:54 bunyip dhclient[4734]: If you think you have received this 
message due to a bug rather
  Nov  8 11:57:54 bunyip dhclient[4734]: than a configuration issue please read 
the section on submitting
  Nov  8 11:57:54 bunyip dhclient[4734]: bugs on either our web page at 
www.isc.org or in the README file
  Nov  8 11:57:54 bunyip dhclient[4734]: before submitting a bug.  These pages 
explain the proper
  Nov  8 11:57:54 bunyip dhclient[4734]: process and the information we find 
helpful for debugging..
  Nov  8 11:57:54 bunyip dhclient[4734]: 
  Nov  8 11:57:54 bunyip dhclient[4734]: exiting.
  

  $ wc -l /var/log/maas/rsyslog/bunyip/2016-11-08/messages
  39278 /var/log/maas/rsyslog/bunyip/2016-11-08/messages

  It would be nice to suppress those lines if those could be safely
  ignored. It would make troubleshooting easier when something wrong
  happened on commissioning.

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1640147/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Bug 1640147] Re: [2.1] rsyslog is flooded with "no link-local IPv6 address for $IFACE" on commissioning

[LaMont Jones]

** Changed in: maas/2.1
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1640147

Title:
  [2.1] rsyslog is flooded with "no link-local IPv6 address for $IFACE"
  on commissioning

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1640147/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1640147] Re: [2.1] rsyslog is flooded with "no link-local IPv6 address for $IFACE" on commissioning

[LaMont Jones]

** Also affects: maas/2.1
   Importance: Undecided
   Status: New

** Changed in: maas/2.1
Milestone: None => 2.1.4

** Changed in: maas/2.1
 Assignee: (unassigned) => LaMont Jones (lamont)

** Changed in: maas
 Assignee: (unassigned) => LaMont Jones (lamont)

** Changed in: maas
   Status: Triaged => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1640147

Title:
  [2.1] rsyslog is flooded with "no link-local IPv6 address for $IFACE"
  on commissioning

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1640147/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Touch-packages] [Bug 1640147] Re: [2.1] rsyslog is flooded with "no link-local IPv6 address for $IFACE" on commissioning

[LaMont Jones]

** Also affects: maas/2.1
   Importance: Undecided
   Status: New

** Changed in: maas/2.1
Milestone: None => 2.1.4

** Changed in: maas/2.1
 Assignee: (unassigned) => LaMont Jones (lamont)

** Changed in: maas
 Assignee: (unassigned) => LaMont Jones (lamont)

** Changed in: maas
   Status: Triaged => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1640147

Title:
  [2.1] rsyslog is flooded with "no link-local IPv6 address for $IFACE"
  on commissioning

Status in MAAS:
  Fix Committed
Status in MAAS 2.1 series:
  New
Status in isc-dhcp package in Ubuntu:
  Invalid

Bug description:
  When commissioning, /var/log/maas/rsyslog/ is flooded with the
  repeated messages below with over 30,000 lines.

  
  Nov  8 11:57:54 bunyip dhclient[4734]: no link-local IPv6 address for enp4s0f0
  Nov  8 11:57:54 bunyip dhclient[4734]: 
  Nov  8 11:57:54 bunyip dhclient[4734]: If you think you have received this 
message due to a bug rather
  Nov  8 11:57:54 bunyip dhclient[4734]: than a configuration issue please read 
the section on submitting
  Nov  8 11:57:54 bunyip dhclient[4734]: bugs on either our web page at 
www.isc.org or in the README file
  Nov  8 11:57:54 bunyip dhclient[4734]: before submitting a bug.  These pages 
explain the proper
  Nov  8 11:57:54 bunyip dhclient[4734]: process and the information we find 
helpful for debugging..
  Nov  8 11:57:54 bunyip dhclient[4734]: 
  Nov  8 11:57:54 bunyip dhclient[4734]: exiting.
  

  $ wc -l /var/log/maas/rsyslog/bunyip/2016-11-08/messages
  39278 /var/log/maas/rsyslog/bunyip/2016-11-08/messages

  It would be nice to suppress those lines if those could be safely
  ignored. It would make troubleshooting easier when something wrong
  happened on commissioning.

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1640147/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1640147] Re: [2.1] rsyslog is flooded with "no link-local IPv6 address for $IFACE" on commissioning

[LaMont Jones]

The loop of output is caused by maas trying to get an ipv6 address in a
loop, even though the interface clearly does not support ipv6. (If it
did, there would be a link-local address.)

** Changed in: isc-dhcp (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1640147

Title:
  [2.1] rsyslog is flooded with "no link-local IPv6 address for $IFACE"
  on commissioning

Status in MAAS:
  Triaged
Status in isc-dhcp package in Ubuntu:
  Invalid

Bug description:
  When commissioning, /var/log/maas/rsyslog/ is flooded with the
  repeated messages below with over 30,000 lines.

  
  Nov  8 11:57:54 bunyip dhclient[4734]: no link-local IPv6 address for enp4s0f0
  Nov  8 11:57:54 bunyip dhclient[4734]: 
  Nov  8 11:57:54 bunyip dhclient[4734]: If you think you have received this 
message due to a bug rather
  Nov  8 11:57:54 bunyip dhclient[4734]: than a configuration issue please read 
the section on submitting
  Nov  8 11:57:54 bunyip dhclient[4734]: bugs on either our web page at 
www.isc.org or in the README file
  Nov  8 11:57:54 bunyip dhclient[4734]: before submitting a bug.  These pages 
explain the proper
  Nov  8 11:57:54 bunyip dhclient[4734]: process and the information we find 
helpful for debugging..
  Nov  8 11:57:54 bunyip dhclient[4734]: 
  Nov  8 11:57:54 bunyip dhclient[4734]: exiting.
  

  $ wc -l /var/log/maas/rsyslog/bunyip/2016-11-08/messages
  39278 /var/log/maas/rsyslog/bunyip/2016-11-08/messages

  It would be nice to suppress those lines if those could be safely
  ignored. It would make troubleshooting easier when something wrong
  happened on commissioning.

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1640147/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Bug 1640147] Re: [2.1] rsyslog is flooded with "no link-local IPv6 address for $IFACE" on commissioning

[LaMont Jones]

The loop of output is caused by maas trying to get an ipv6 address in a
loop, even though the interface clearly does not support ipv6. (If it
did, there would be a link-local address.)

** Changed in: isc-dhcp (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1640147

Title:
  [2.1] rsyslog is flooded with "no link-local IPv6 address for $IFACE"
  on commissioning

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1640147/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Touch-packages] [Bug 1640147] Re: [2.1] rsyslog is flooded with "no link-local IPv6 address for $IFACE" on commissioning

[LaMont Jones]

tl;dr: dhclient -6 should be less spam-chatty in the presence of no ipv6
support.

If dhclient logged that as one message, instead of 9 messages, then
syslog would compress the output.

The easiest way that I've seen to reproduce this is to boot with
ipv6.disable=true on the kernel command line.

Nobuto: do you have ipv6 disabled via the kernel command line?  (This is
known to cause various issues for a number of daemons.)

** Also affects: isc-dhcp (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1640147

Title:
  [2.1] rsyslog is flooded with "no link-local IPv6 address for $IFACE"
  on commissioning

Status in MAAS:
  Triaged
Status in isc-dhcp package in Ubuntu:
  New

Bug description:
  When commissioning, /var/log/maas/rsyslog/ is flooded with the
  repeated messages below with over 30,000 lines.

  
  Nov  8 11:57:54 bunyip dhclient[4734]: no link-local IPv6 address for enp4s0f0
  Nov  8 11:57:54 bunyip dhclient[4734]: 
  Nov  8 11:57:54 bunyip dhclient[4734]: If you think you have received this 
message due to a bug rather
  Nov  8 11:57:54 bunyip dhclient[4734]: than a configuration issue please read 
the section on submitting
  Nov  8 11:57:54 bunyip dhclient[4734]: bugs on either our web page at 
www.isc.org or in the README file
  Nov  8 11:57:54 bunyip dhclient[4734]: before submitting a bug.  These pages 
explain the proper
  Nov  8 11:57:54 bunyip dhclient[4734]: process and the information we find 
helpful for debugging..
  Nov  8 11:57:54 bunyip dhclient[4734]: 
  Nov  8 11:57:54 bunyip dhclient[4734]: exiting.
  

  $ wc -l /var/log/maas/rsyslog/bunyip/2016-11-08/messages
  39278 /var/log/maas/rsyslog/bunyip/2016-11-08/messages

  It would be nice to suppress those lines if those could be safely
  ignored. It would make troubleshooting easier when something wrong
  happened on commissioning.

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1640147/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Bug 1640147] Re: [2.1] rsyslog is flooded with "no link-local IPv6 address for $IFACE" on commissioning

[LaMont Jones]

tl;dr: dhclient -6 should be less spam-chatty in the presence of no ipv6
support.

If dhclient logged that as one message, instead of 9 messages, then
syslog would compress the output.

The easiest way that I've seen to reproduce this is to boot with
ipv6.disable=true on the kernel command line.

Nobuto: do you have ipv6 disabled via the kernel command line?  (This is
known to cause various issues for a number of daemons.)

** Also affects: isc-dhcp (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1640147

Title:
  [2.1] rsyslog is flooded with "no link-local IPv6 address for $IFACE"
  on commissioning

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1640147/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1645912] Re: freeipmi ipmi-config --checkout lacks support for ipv6 lan parameters

[LaMont Jones]

** Also affects: maas/2.1
   Importance: Undecided
   Status: New

** Tags added: maas-ipv6

** Changed in: maas/2.1
Milestone: None => 2.1.4

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1645912

Title:
  freeipmi ipmi-config --checkout lacks support for ipv6 lan parameters

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1645912/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1645912] Re: freeipmi ipmi-config --checkout lacks support for ipv6 lan parameters

[LaMont Jones]

Confirmed freeipmi-tools on xenial and yakkety.

** Tags removed: verification-needed
** Tags added: verification-done

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1645912

Title:
  freeipmi ipmi-config --checkout lacks support for ipv6 lan parameters

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1645912/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1553176] Re: BIND ignores nanoseconds field in timestamps, fails to load newer versions of zones on reload

[LaMont Jones]

Verified trusty using the same test as found in
http://paste.ubuntu.com/23921176/

** Tags removed: verification-needed
** Tags added: verification-done

** Changed in: bind9 (Ubuntu Trusty)
Milestone: None => trusty-updates

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1553176

Title:
  BIND ignores nanoseconds field in timestamps, fails to load newer
  versions of zones on reload

To manage notifications about this bug go to:
https://bugs.launchpad.net/bind/+bug/1553176/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[ubuntu/trusty-proposed] bind9 1:9.9.5.dfsg-3ubuntu0.12 (Accepted)

[LaMont Jones]

bind9 (1:9.9.5.dfsg-3ubuntu0.12) trusty; urgency=medium

  * Backport (70_precise_mtime.diff) 18b87b2a58d422fe4d3073540bf89b5a812ed2e5
to trusty. LP: #1553176

Date: Fri, 03 Feb 2017 13:13:21 -0700
Changed-By: LaMont Jones <lam...@canonical.com>
Maintainer: Ubuntu Developers <ubuntu-devel-disc...@lists.ubuntu.com>
https://launchpad.net/ubuntu/+source/bind9/1:9.9.5.dfsg-3ubuntu0.12
Format: 1.8
Date: Fri, 03 Feb 2017 13:13:21 -0700
Source: bind9
Binary: bind9 bind9utils bind9-doc host bind9-host libbind-dev libbind9-90 
libdns100 libisc95 liblwres90 libisccc90 libisccfg90 dnsutils lwresd
Architecture: source
Version: 1:9.9.5.dfsg-3ubuntu0.12
Distribution: trusty
Urgency: medium
Maintainer: Ubuntu Developers <ubuntu-devel-disc...@lists.ubuntu.com>
Changed-By: LaMont Jones <lam...@canonical.com>
Description:
 bind9  - Internet Domain Name Server
 bind9-doc  - Documentation for BIND
 bind9-host - Version of 'host' bundled with BIND 9.X
 bind9utils - Utilities for BIND
 dnsutils   - Clients provided with BIND
 host   - Transitional package
 libbind-dev - Static Libraries and Headers used by BIND
 libbind9-90 - BIND9 Shared Library used by BIND
 libdns100  - DNS Shared Library used by BIND
 libisc95   - ISC Shared Library used by BIND
 libisccc90 - Command Channel Library used by BIND
 libisccfg90 - Config File Handling Library used by BIND
 liblwres90 - Lightweight Resolver Library used by BIND
 lwresd - Lightweight Resolver Daemon
Launchpad-Bugs-Fixed: 1553176
Changes:
 bind9 (1:9.9.5.dfsg-3ubuntu0.12) trusty; urgency=medium
 .
   * Backport (70_precise_mtime.diff) 18b87b2a58d422fe4d3073540bf89b5a812ed2e5
 to trusty. LP: #1553176
Checksums-Sha1:
 2c64dc185c9837c1cc80a436abfe352146f1e7f0 2844 bind9_9.9.5.dfsg-3ubuntu0.12.dsc
 ea05323d1d799fae970a7124debe297ef71f2cd0 7877309 bind9_9.9.5.dfsg.orig.tar.gz
 c212ca1816529594ec34c33d6755baad879491d2 194064 
bind9_9.9.5.dfsg-3ubuntu0.12.diff.gz
Checksums-Sha256:
 cd80ef9c0420a7b2d38dc5daad138d9be0600a533d02ec390e18468aff222703 2844 
bind9_9.9.5.dfsg-3ubuntu0.12.dsc
 8108e01d5b501642d986beae7dfff9650b5bf54d87677275a8aaf4f0bcb008e6 7877309 
bind9_9.9.5.dfsg.orig.tar.gz
 329b9bd699b2689202dc0be0b0afdf4ed8f2c21554fde8556a46d1c65b55b209 194064 
bind9_9.9.5.dfsg-3ubuntu0.12.diff.gz
Files:
 b661b189b6e8c048ba7c872e9d064ea7 2844 net optional 
bind9_9.9.5.dfsg-3ubuntu0.12.dsc
 e3b03e1cd273d708cbfbd862297646ce 7877309 net optional 
bind9_9.9.5.dfsg.orig.tar.gz
 863b860264ec169c1f305a7f15156bd6 194064 net optional 
bind9_9.9.5.dfsg-3ubuntu0.12.diff.gz
Original-Maintainer: LaMont Jones <lam...@debian.org>
-- 
Trusty-changes mailing list
Trusty-changes@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/trusty-changes

[Group.of.nepali.translators] [Bug 1553176] Re: BIND ignores nanoseconds field in timestamps, fails to load newer versions of zones on reload

[LaMont Jones]

** Description changed:

  Since 2.6, linux has supported nanosecond granular time in stat(2)
  returns.  BIND has a comment in the code that it might use it, but
  continues to ignore it.
  
  As of 9.9.3b2, named checks the time of (at least) zone files on disk
  (expanding to include include files in 9.10.0a2).  Because the check is
  only done to a granularity of seconds, changing the zone file twice in
  the same second can cause BIND to decide that it need not reload the
  zone, even though it is out of date.
  
  [Impact]
  
-  * If a zone file is changed (generally by automated processes) more
+  * If a zone file is changed (generally by automated processes) more
  than once in a second, bind9 happily thinks it has already loaded the
  zone.  A trivial demonstration of the bug can be seen at
- paste.ubuntu.com/23921121/
+ paste.ubuntu.com/23921121/ -- http://paste.ubuntu.com/23921176/ is the
+ same test with the fixed code.  Making this a test case is somewhat
+ problematic in that it needs to make sure that they happen inside of the
+ same second.
  
-  * MAAS is exactly the sort of use case that hits this bug.
+  * MAAS is exactly the sort of use case that hits this bug.
  
-  * The upload changes BIND's utility function to actual use the
+  * The upload changes BIND's utility function to actual use the
  st_mtim.tv_nsec instead of '0'.
  
  [Test Case]
  
-  * See the pastebin above.  (Change a zone file and reload it, and then
+  * See the pastebin above.  (Change a zone file and reload it, and then
  do it again less than a second later.)
  
  [Regression Potential]
  
-  * Ignoring the whole "rebuilds sometimes break things", the most likely
+  * Ignoring the whole "rebuilds sometimes break things", the most likely
  regression would be one where something was either relying on BIND not
  reloading the dozone (unlikely), or otherwise relying on the modify time
  on a zone file to some arbitrary value.
  
  [Other Info]
  
-   This bug was fixed in 1:9.10.3.dfsg.P2-5, which landed in xenial March
+   This bug was fixed in 1:9.10.3.dfsg.P2-5, which landed in xenial March
  2016.

** Also affects: bind9 (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: bind9 (Ubuntu Xenial)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1553176

Title:
  BIND ignores nanoseconds field in timestamps, fails to load newer
  versions of zones on reload

Status in BIND:
  Fix Released
Status in MAAS:
  Fix Released
Status in bind9 package in Ubuntu:
  Confirmed
Status in bind9 source package in Xenial:
  Fix Released

Bug description:
  Since 2.6, linux has supported nanosecond granular time in stat(2)
  returns.  BIND has a comment in the code that it might use it, but
  continues to ignore it.

  As of 9.9.3b2, named checks the time of (at least) zone files on disk
  (expanding to include include files in 9.10.0a2).  Because the check
  is only done to a granularity of seconds, changing the zone file twice
  in the same second can cause BIND to decide that it need not reload
  the zone, even though it is out of date.

  [Impact]

   * If a zone file is changed (generally by automated processes) more
  than once in a second, bind9 happily thinks it has already loaded the
  zone.  A trivial demonstration of the bug can be seen at
  paste.ubuntu.com/23921121/ -- http://paste.ubuntu.com/23921176/ is the
  same test with the fixed code.  Making this a test case is somewhat
  problematic in that it needs to make sure that they happen inside of
  the same second.

   * MAAS is exactly the sort of use case that hits this bug.

   * The upload changes BIND's utility function to actual use the
  st_mtim.tv_nsec instead of '0'.

  [Test Case]

   * See the pastebin above.  (Change a zone file and reload it, and
  then do it again less than a second later.)

  [Regression Potential]

   * Ignoring the whole "rebuilds sometimes break things", the most
  likely regression would be one where something was either relying on
  BIND not reloading the dozone (unlikely), or otherwise relying on the
  modify time on a zone file to some arbitrary value.

  [Other Info]

    This bug was fixed in 1:9.10.3.dfsg.P2-5, which landed in xenial
  March 2016.

To manage notifications about this bug go to:
https://bugs.launchpad.net/bind/+bug/1553176/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Bug 1553176] Re: BIND ignores nanoseconds field in timestamps, fails to load newer versions of zones on reload

[LaMont Jones]

** Description changed:

  Since 2.6, linux has supported nanosecond granular time in stat(2)
  returns.  BIND has a comment in the code that it might use it, but
  continues to ignore it.
  
  As of 9.9.3b2, named checks the time of (at least) zone files on disk
  (expanding to include include files in 9.10.0a2).  Because the check is
  only done to a granularity of seconds, changing the zone file twice in
  the same second can cause BIND to decide that it need not reload the
  zone, even though it is out of date.
  
  [Impact]
  
-  * If a zone file is changed (generally by automated processes) more
+  * If a zone file is changed (generally by automated processes) more
  than once in a second, bind9 happily thinks it has already loaded the
  zone.  A trivial demonstration of the bug can be seen at
- paste.ubuntu.com/23921121/
+ paste.ubuntu.com/23921121/ -- http://paste.ubuntu.com/23921176/ is the
+ same test with the fixed code.  Making this a test case is somewhat
+ problematic in that it needs to make sure that they happen inside of the
+ same second.
  
-  * MAAS is exactly the sort of use case that hits this bug.
+  * MAAS is exactly the sort of use case that hits this bug.
  
-  * The upload changes BIND's utility function to actual use the
+  * The upload changes BIND's utility function to actual use the
  st_mtim.tv_nsec instead of '0'.
  
  [Test Case]
  
-  * See the pastebin above.  (Change a zone file and reload it, and then
+  * See the pastebin above.  (Change a zone file and reload it, and then
  do it again less than a second later.)
  
  [Regression Potential]
  
-  * Ignoring the whole "rebuilds sometimes break things", the most likely
+  * Ignoring the whole "rebuilds sometimes break things", the most likely
  regression would be one where something was either relying on BIND not
  reloading the dozone (unlikely), or otherwise relying on the modify time
  on a zone file to some arbitrary value.
  
  [Other Info]
  
-   This bug was fixed in 1:9.10.3.dfsg.P2-5, which landed in xenial March
+   This bug was fixed in 1:9.10.3.dfsg.P2-5, which landed in xenial March
  2016.

** Also affects: bind9 (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: bind9 (Ubuntu Xenial)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1553176

Title:
  BIND ignores nanoseconds field in timestamps, fails to load newer
  versions of zones on reload

To manage notifications about this bug go to:
https://bugs.launchpad.net/bind/+bug/1553176/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1553176] Re: BIND ignores nanoseconds field in timestamps, fails to load newer versions of zones on reload

[LaMont Jones]

** Description changed:

  Since 2.6, linux has supported nanosecond granular time in stat(2)
  returns.  BIND has a comment in the code that it might use it, but
  continues to ignore it.
  
  As of 9.9.3b2, named checks the time of (at least) zone files on disk
  (expanding to include include files in 9.10.0a2).  Because the check is
  only done to a granularity of seconds, changing the zone file twice in
  the same second can cause BIND to decide that it need not reload the
  zone, even though it is out of date.
+ 
+ [Impact]
+ 
+  * If a zone file is changed (generally by automated processes) more
+ than once in a second, bind9 happily thinks it has already loaded the
+ zone.  A trivial demonstration of the bug can be seen at
+ paste.ubuntu.com/23921121/
+ 
+  * MAAS is exactly the sort of use case that hits this bug.
+ 
+  * The upload changes BIND's utility function to actual use the
+ st_mtim.tv_nsec instead of '0'.
+ 
+ [Test Case]
+ 
+  * See the pastebin above.  (Change a zone file and reload it, and then
+ do it again less than a second later.)
+ 
+ [Regression Potential]
+ 
+  * Ignoring the whole "rebuilds sometimes break things", the most likely
+ regression would be one where something was either relying on BIND not
+ reloading the dozone (unlikely), or otherwise relying on the modify time
+ on a zone file to some arbitrary value.
+ 
+ [Other Info]
+ 
+   This bug was fixed in 1:9.10.3.dfsg.P2-5, which landed in xenial March
+ 2016.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1553176

Title:
  BIND ignores nanoseconds field in timestamps, fails to load newer
  versions of zones on reload

To manage notifications about this bug go to:
https://bugs.launchpad.net/bind/+bug/1553176/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[ubuntu/yakkety-proposed] freeipmi 1.4.11-1.1ubuntu3~0.16.10 (Accepted)

[LaMont Jones]

freeipmi (1.4.11-1.1ubuntu3~0.16.10) yakkety; urgency=medium

  * Backport to yakkety.
Add ipv6 ipmi-discovery. LP: #1645912.  See also:

https://github.com/chu11/freeipmi-mirror/pull/12/commits/32721f88cd37aa4ca1564c243669f96628089986

Date: Thu, 26 Jan 2017 09:43:29 -0700
Changed-By: LaMont Jones <lam...@canonical.com>
Maintainer: Ubuntu Developers <ubuntu-devel-disc...@lists.ubuntu.com>
https://launchpad.net/ubuntu/+source/freeipmi/1.4.11-1.1ubuntu3~0.16.10
Format: 1.8
Date: Thu, 26 Jan 2017 09:43:29 -0700
Source: freeipmi
Binary: freeipmi-common freeipmi-tools freeipmi-bmc-watchdog 
freeipmi-ipmidetect freeipmi-ipmiseld libfreeipmi16 libfreeipmi-dev 
libipmidetect0 libipmidetect-dev libipmimonitoring5a libipmimonitoring-dev 
libipmiconsole2 libipmiconsole-dev freeipmi
Architecture: source
Version: 1.4.11-1.1ubuntu3~0.16.10
Distribution: yakkety
Urgency: medium
Maintainer: Ubuntu Developers <ubuntu-devel-disc...@lists.ubuntu.com>
Changed-By: LaMont Jones <lam...@canonical.com>
Description:
 freeipmi   - GNU implementation of the IPMI protocol
 freeipmi-bmc-watchdog - GNU implementation of the IPMI protocol - BMC watchdog
 freeipmi-common - GNU implementation of the IPMI protocol - common files
 freeipmi-ipmidetect - GNU IPMI - IPMI node detection tool
 freeipmi-ipmiseld - GNU IPMI - IPMI node detection tool
 freeipmi-tools - GNU implementation of the IPMI protocol - tools
 libfreeipmi-dev - GNU IPMI - development package
 libfreeipmi16 - GNU IPMI - libraries
 libipmiconsole-dev - GNU IPMI - ipmiconsole development package
 libipmiconsole2 - GNU IPMI - Serial-over-Lan library
 libipmidetect-dev - GNU IPMI - ipmidetect development package
 libipmidetect0 - GNU IPMI - IPMI node detection library
 libipmimonitoring-dev - GNU IPMI - ipmimonitoring development package
 libipmimonitoring5a - GNU IPMI - Sensor monitoring library
Launchpad-Bugs-Fixed: 1645912
Changes:
 freeipmi (1.4.11-1.1ubuntu3~0.16.10) yakkety; urgency=medium
 .
   * Backport to yakkety.
 Add ipv6 ipmi-discovery. LP: #1645912.  See also:
 
https://github.com/chu11/freeipmi-mirror/pull/12/commits/32721f88cd37aa4ca1564c243669f96628089986
Checksums-Sha1:
 2db591a9dcfb7ed9e527eaff395f65a5a792c8f2 2379 
freeipmi_1.4.11-1.1ubuntu3~0.16.10.dsc
 2223bae3e9137b7fc50ccd09e9ddb8077a3c0832 35236 
freeipmi_1.4.11-1.1ubuntu3~0.16.10.debian.tar.xz
Checksums-Sha256:
 b1c78cbb504cc0d223eb7fd9ecf8127bb92f7df4714f027ae4b88a4d54f1d92d 2379 
freeipmi_1.4.11-1.1ubuntu3~0.16.10.dsc
 440343ec1f2b2e24d0c4dda58ed37967f2fd74f01896b58563e23588b87acc09 35236 
freeipmi_1.4.11-1.1ubuntu3~0.16.10.debian.tar.xz
Files:
 9f083acdcbc7386eb0fb83db40b64d0c 2379 admin extra 
freeipmi_1.4.11-1.1ubuntu3~0.16.10.dsc
 5360787912c6c8cdbccb9a8d9a3ae4a2 35236 admin extra 
freeipmi_1.4.11-1.1ubuntu3~0.16.10.debian.tar.xz
Original-Maintainer: Debian FreeIPMI Maintainers 
<pkg-freeipmi-de...@lists.alioth.debian.org>
-- 
Yakkety-changes mailing list
Yakkety-changes@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/yakkety-changes

[ubuntu/xenial-proposed] freeipmi 1.4.11-1.1ubuntu3~0.16.04 (Accepted)

[LaMont Jones]

freeipmi (1.4.11-1.1ubuntu3~0.16.04) xenial; urgency=medium

  * Backport to xenial.
Add ipv6 ipmi-discovery. LP: #1645912.  See also:

https://github.com/chu11/freeipmi-mirror/pull/12/commits/32721f88cd37aa4ca1564c243669f96628089986

Date: Thu, 26 Jan 2017 09:43:29 -0700
Changed-By: LaMont Jones <lam...@canonical.com>
Maintainer: Ubuntu Developers <ubuntu-devel-disc...@lists.ubuntu.com>
https://launchpad.net/ubuntu/+source/freeipmi/1.4.11-1.1ubuntu3~0.16.04
Format: 1.8
Date: Thu, 26 Jan 2017 09:43:29 -0700
Source: freeipmi
Binary: freeipmi-common freeipmi-tools freeipmi-bmc-watchdog 
freeipmi-ipmidetect freeipmi-ipmiseld libfreeipmi16 libfreeipmi-dev 
libipmidetect0 libipmidetect-dev libipmimonitoring5a libipmimonitoring-dev 
libipmiconsole2 libipmiconsole-dev freeipmi
Architecture: source
Version: 1.4.11-1.1ubuntu3~0.16.04
Distribution: xenial
Urgency: medium
Maintainer: Ubuntu Developers <ubuntu-devel-disc...@lists.ubuntu.com>
Changed-By: LaMont Jones <lam...@canonical.com>
Description:
 freeipmi   - GNU implementation of the IPMI protocol
 freeipmi-bmc-watchdog - GNU implementation of the IPMI protocol - BMC watchdog
 freeipmi-common - GNU implementation of the IPMI protocol - common files
 freeipmi-ipmidetect - GNU IPMI - IPMI node detection tool
 freeipmi-ipmiseld - GNU IPMI - IPMI node detection tool
 freeipmi-tools - GNU implementation of the IPMI protocol - tools
 libfreeipmi-dev - GNU IPMI - development package
 libfreeipmi16 - GNU IPMI - libraries
 libipmiconsole-dev - GNU IPMI - ipmiconsole development package
 libipmiconsole2 - GNU IPMI - Serial-over-Lan library
 libipmidetect-dev - GNU IPMI - ipmidetect development package
 libipmidetect0 - GNU IPMI - IPMI node detection library
 libipmimonitoring-dev - GNU IPMI - ipmimonitoring development package
 libipmimonitoring5a - GNU IPMI - Sensor monitoring library
Launchpad-Bugs-Fixed: 1645912
Changes:
 freeipmi (1.4.11-1.1ubuntu3~0.16.04) xenial; urgency=medium
 .
   * Backport to xenial.
 Add ipv6 ipmi-discovery. LP: #1645912.  See also:
 
https://github.com/chu11/freeipmi-mirror/pull/12/commits/32721f88cd37aa4ca1564c243669f96628089986
Checksums-Sha1:
 bf42d861a9337b7e62e46ed45d70b1cead432729 2379 
freeipmi_1.4.11-1.1ubuntu3~0.16.04.dsc
 fadb313ad45bdbe6d7f21dfc3b105ea79f2880f7 35240 
freeipmi_1.4.11-1.1ubuntu3~0.16.04.debian.tar.xz
Checksums-Sha256:
 841b28bd3355f88218d67e1cea4f5d36df17daf31821671572ccb241f0e912e5 2379 
freeipmi_1.4.11-1.1ubuntu3~0.16.04.dsc
 860f4921a4ad9c4026ab686c30a03cfd8e55b281e182ff2f0aa95d742d16a280 35240 
freeipmi_1.4.11-1.1ubuntu3~0.16.04.debian.tar.xz
Files:
 7e8f74a72c99adc5ca34437ea872316b 2379 admin extra 
freeipmi_1.4.11-1.1ubuntu3~0.16.04.dsc
 dea294f8bb4f089c47751de7045de87f 35240 admin extra 
freeipmi_1.4.11-1.1ubuntu3~0.16.04.debian.tar.xz
Original-Maintainer: Debian FreeIPMI Maintainers 
<pkg-freeipmi-de...@lists.alioth.debian.org>
-- 
Xenial-changes mailing list
Xenial-changes@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/xenial-changes

[Bug 1645912] Re: freeipmi ipmi-config --checkout lacks support for ipv6 lan parameters

[LaMont Jones]

Package verified in zesty.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1645912

Title:
  freeipmi ipmi-config --checkout lacks support for ipv6 lan parameters

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1645912/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1645912] Re: freeipmi ipmi-config --checkout lacks support for ipv6 lan parameters

[LaMont Jones]

** Changed in: freeipmi (Ubuntu)
Milestone: None => ubuntu-17.04

** Also affects: freeipmi (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: freeipmi (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: maas
Milestone: None => 2.2.0

** Description changed:

  See also https://github.com/chu11/freeipmi-mirror/issues/8 and
  https://github.com/chu11/freeipmi-mirror/issues/12 -- freeipmi needs to
  successfully discover the ipv6 address of a hosts BMC.
  
  [Impact]
  
-  * Machines with BMCs configured to use IPv6 addresses, ipmi-config
-(silently) fails to show those values.
+  * Machines with BMCs configured to use IPv6 addresses, ipmi-config
+    (silently) fails to show those values.
  
-  * MAAS 2.2 supports IPv6 BMC addresses, and depends on ipmi-config
-finding the IPv6 address of the BMC.
+  * MAAS 2.2 supports IPv6 BMC addresses, and depends on ipmi-config
+    finding the IPv6 address of the BMC.
  
-  * This upload is a backport of an upstream work-in-progress to add IPv6
-configuration parameters to ipmi-config.  While the eventual upstream
-source may differ slightly as the branch lands, this delivers the
-information for use.  ANYONE USING THIS CODE NEEDS TO BE PREPARED TO
-CHANGE TO MATCH THE ACTUAL DELIVERY WHEN 1.6 LANDS.
+  * This upload is a backport of an upstream work-in-progress to add IPv6
+    configuration parameters to ipmi-config.  While the eventual upstream
+    source may differ slightly as the branch lands, this delivers the
+    information for use.  ANYONE USING THIS CODE NEEDS TO BE PREPARED TO
+    CHANGE TO MATCH THE ACTUAL DELIVERY WHEN 1.6 LANDS.
  
  [Test Case]
  
-  * Start with an HP DL360 Proliant Gen9 (iLO4 is required) with an IPv6
-address configured on the iLO.  Try to get ipmi-config to give you
-that address.
+  * Start with an HP DL360 Proliant Gen9 (iLO4 is required) with an IPv6
+    address configured on the iLO.  Try to get ipmi-config to give you
+    that address.
  
-  * This upload introduces the Lan6_Conf section (which may change when
-1.6 finally arrives.)  The following displays the IPv6 Addresses of
-the BMC:
-   ipmi-config --checkout --category=core --section=Lan6_Conf
+  * This upload introduces the Lan6_Conf section (which may change when
+    1.6 finally arrives.)  The following displays the IPv6 Addresses of
+    the BMC:
+   ipmi-config --checkout --category=core --section=Lan6_Conf
  
  [Regression Potential]
  
-  * Scripting that uses --checkout and no section/key-pair specification
-will now see the additional Lan6_Conf section, which has the potential
-to confuse said script.
+  * Scripting that uses --checkout and no section/key-pair specification
+    will now see the additional Lan6_Conf section, which has the potential
+    to confuse said script.
  
-  * If upstream changes the presentation of the data, anyone who has
-adopted this pre-release of same may see differences.  The section is
-clearly marked as subject to change in 1.6, and missing in 1.5.  (If
-Ubuntu syncs 1.5, MAAS is committed to porting this change forward.
-Upstream has committed to the feature being present in 1.6.)
+  * If upstream changes the presentation of the data, anyone who has
+    adopted this pre-release of same may see differences.  The section is
+    clearly marked as subject to change in 1.6, and missing in 1.5.  (If
+    Ubuntu syncs 1.5, MAAS is committed to porting this change forward.
+    Upstream has committed to the feature being present in 1.6.)
  
  [Other Info]
+ 
+ Once the changes are available, MAAS will need to change to use the new
+ Lan6_Conf section.

** Changed in: freeipmi (Ubuntu Xenial)
Milestone: None => xenial-updates

** Changed in: freeipmi (Ubuntu Yakkety)
Milestone: None => yakkety-updates

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1645912

Title:
  freeipmi ipmi-config --checkout lacks support for ipv6 lan parameters

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1645912/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1645912] Re: freeipmi ipmi-config --checkout lacks support for ipv6 lan parameters

[LaMont Jones]

** Description changed:

  See also https://github.com/chu11/freeipmi-mirror/issues/8 and
  https://github.com/chu11/freeipmi-mirror/issues/12 -- freeipmi needs to
  successfully discover the ipv6 address of a hosts BMC.
+ 
+ [Impact]
+ 
+  * Machines with BMCs configured to use IPv6 addresses, ipmi-config
+(silently) fails to show those values.
+ 
+  * MAAS 2.2 supports IPv6 BMC addresses, and depends on ipmi-config
+finding the IPv6 address of the BMC.
+ 
+  * This upload is a backport of an upstream work-in-progress to add IPv6
+configuration parameters to ipmi-config.  While the eventual upstream
+source may differ slightly as the branch lands, this delivers the
+information for use.  ANYONE USING THIS CODE NEEDS TO BE PREPARED TO
+CHANGE TO MATCH THE ACTUAL DELIVERY WHEN 1.6 LANDS.
+ 
+ [Test Case]
+ 
+  * Start with an HP DL360 Proliant Gen9 (iLO4 is required) with an IPv6
+address configured on the iLO.  Try to get ipmi-config to give you
+that address.
+ 
+  * This upload introduces the Lan6_Conf section (which may change when
+1.6 finally arrives.)  The following displays the IPv6 Addresses of
+the BMC:
+   ipmi-config --checkout --category=core --section=Lan6_Conf
+ 
+ [Regression Potential]
+ 
+  * Scripting that uses --checkout and no section/key-pair specification
+will now see the additional Lan6_Conf section, which has the potential
+to confuse said script.
+ 
+  * If upstream changes the presentation of the data, anyone who has
+adopted this pre-release of same may see differences.  The section is
+clearly marked as subject to change in 1.6, and missing in 1.5.  (If
+Ubuntu syncs 1.5, MAAS is committed to porting this change forward.
+Upstream has committed to the feature being present in 1.6.)
+ 
+ [Other Info]

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1645912

Title:
  freeipmi ipmi-config --checkout lacks support for ipv6 lan parameters

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1645912/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1645912] Re: freeipmi ipmi-config --checkout lacks support for ipv6 lan parameters

[LaMont Jones]

** Summary changed:

- freeipmi ipmi-config (and discovery) lacks ipv6 support
+ freeipmi ipmi-config --checkout lacks support for ipv6 lan parameters

** Description changed:

- See also https://github.com/chu11/freeipmi-mirror/issues/8 -- freeipmi
- needs to successfully discover the ipv6 address of a hosts BMC.
+ See also https://github.com/chu11/freeipmi-mirror/issues/8 and
+ https://github.com/chu11/freeipmi-mirror/issues/12 -- freeipmi needs to
+ successfully discover the ipv6 address of a hosts BMC.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1645912

Title:
  freeipmi ipmi-config --checkout lacks support for ipv6 lan parameters

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1645912/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1658750] Re: fails to add search directive to resolv.conf

[LaMont Jones]

Note that while there is no DOMAINSEARCH, DNSDOMAIN needs to translate
into something (domain or search directive), and only one of those will
be honored by the resolver (they overwrite each other, per the
specification).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1658750

Title:
  fails to add search directive to resolv.conf

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1658750/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1658750] [NEW] fails to add search directive to resolv.conf

[LaMont Jones]

Public bug reported:

When open-iscsi creates /etc/resolv.conf, it fails to add the domain
name to resolv.conf:

See also http://askubuntu.com/questions/873701/maas-node-unable-to-
resolve-its-own-hostname/874005

ubuntu@resolve:~$ cat /run/net-ens3.conf 
DEVICE='ens3'
PROTO='dhcp'
IPV4ADDR='172.18.145.5'
IPV4BROADCAST='172.18.147.255'
IPV4NETMASK='255.255.252.0'
IPV4GATEWAY='172.18.144.1'
IPV4DNS0='192.168.133.18'
IPV4DNS1='0.0.0.0'
HOSTNAME=''
DNSDOMAIN='maas.example.com'
NISDOMAIN=''
ROOTSERVER='172.18.144.1'
ROOTPATH=''
filename='pxelinux.0'
UPTIME='8'
DHCPLEASETIME='600'
DOMAINSEARCH=''
ubuntu@resolve:~$ cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 192.168.133.18
ubuntu@resolve:~$ dpkg -l open-iscsi | cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version   Architecture Description
+++-==-=--=
ii  open-iscsi 2.0.873+git0.3b4b4500-14ubuntu3.3 amd64iSCSI 
initiator tools

** Affects: open-iscsi (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1658750

Title:
  fails to add search directive to resolv.conf

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1658750/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Bug#820974: bind9 crypto issue

[LaMont Jones]

On Fri, Jan 20, 2017 at 02:35:16PM +0100, Arturo Borrero Gonzalez wrote:
> I believe this is a serious bug, since it affects the most common way
> to deploy bind9 server which is in a chroot.
> In my opinion, we should probably not release stable stretch with
> bind9 in this state.
> 
> This is what I get in systemctl status:
> 
> ene 19 13:38:04 named[1020]: ENGINE_by_id failed (crypto failure)

Can you provide a named.conf that reproduces the issue?

thanks,
lamont

Bug#820974: bind9 crypto issue

[LaMont Jones]

On Fri, Jan 20, 2017 at 02:35:16PM +0100, Arturo Borrero Gonzalez wrote:
> I believe this is a serious bug, since it affects the most common way
> to deploy bind9 server which is in a chroot.
> In my opinion, we should probably not release stable stretch with
> bind9 in this state.
> 
> This is what I get in systemctl status:
> 
> ene 19 13:38:04 named[1020]: ENGINE_by_id failed (crypto failure)

Can you provide a named.conf that reproduces the issue?

thanks,
lamont

Bug#851489: Updated Russian debconf translation

[LaMont Jones]

On Sun, Jan 15, 2017 at 06:09:35PM +0300, Sergey Alyoshin wrote:
> Package: postfix
> Version: 3.1.3-6
> Priority: wishlist
> Tags: l10n patch

This file is unchanged from one that landed in the source tree on the 9th..
Was that intentional?

lamont

[Bug 1655049] Re: [2.1] netaddr raises IndexError when looking up some OUI registrations

[LaMont Jones]

The actual source of the issue seems to be that netaddr indexes a file
that it doesn't own (from ieee-data package), and then assumes that it
won't change underneath it (either because of an ieee-data update, or a
netaddr update in the case of a running process), which results in
various exceptions and other errors from the code.  I believe that a
fresh bug is being filed against python-netaddr on the issue.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1655049

Title:
  [2.1] netaddr raises IndexError when looking up some OUI registrations

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1655049/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1655049] Re: [2.1] netaddr raises IndexError when looking up some OUI registrations

[LaMont Jones]

Interesting point.  Here is what I see:

[xenial]
ii  ieee-data   20150531.1   all  OUI and IAB listings
ii  python3-netaddr 0.7.18-1 all  manipulation of various common 
netwo
% python3
Python 3.5.2 (default, Nov 17 2016, 17:05:23) 
[GCC 5.4.0 20160609] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import netaddr
>>> netaddr.EUI('00:22:59:11:22:33').oui.registration().org
'Guangzhou New Postcom Equipment Co.,Ltd.'


[zesty]
ii  ieee-data 20160613.1all   OUI and IAB listings
ii  python3-netaddr   0.7.18-2  all   manipulation of various 
common network 
% python3
Python 3.5.2+ (default, Dec 13 2016, 14:16:35) 
[GCC 6.2.1 20161212] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import netaddr
>>> netaddr.EUI('00:22:59:11:22:33').oui.registration().org
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/netaddr/eui/__init__.py", line 478, in 
oui
return OUI(self.value >> 24)
  File "/usr/lib/python3/dist-packages/netaddr/eui/__init__.py", line 98, in 
__init__
self._parse_data(data, offset, size)
  File "/usr/lib/python3/dist-packages/netaddr/eui/__init__.py", line 145, in 
_parse_data
record['org'] = line.split(None, 2)[2]
IndexError: list index out of range
>>> 

That is netaddr is not sufficiently hardened against the newer ieee-
data.  While it's conceivable that the actual bug is in ieee-data, it
would seem that hardening the code to better deal with it would be good.

The entry that breaks reads:
00-22-59   (hex)Guangzhou New Postcom Equipment Co.,Ltd.
002259 (base 16)Guangzhou New Postcom Equipment Co.,Ltd.
No.3¡¡Guangpuxi Road,Guangzhou Science 
City,
Guangzhou  Guangdong  510663
CN
while the same entry in the working file is:
  00-22-59   (hex)  Guangzhou New Postcom Equipment Co.,Ltd.
  002259 (base 16)  Guangzhou New Postcom Equipment Co.,Ltd.
No.3¡¡Guangpuxi Road,Guangzhou Science 
City,
Guangzhou Guangdong 510663
CHINA
(Note the leading pair of spaces...)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1655049

Title:
  [2.1] netaddr raises IndexError when looking up some OUI registrations

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1655049/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1628761] Re: [2.1] netaddr assumes MAC OUI is ascii

[LaMont Jones]

Likewise, as of 0.7.18-2, the mac prefixes 00:22:59, 00:23:89, and
5c:15:15 generate IndexError, because unicode is treated as ascii.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1628761

Title:
  [2.1] netaddr assumes MAC OUI is ascii

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1628761/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1655049] Re: List index out of range on main page and nodes page

[LaMont Jones]

MAAS was incomplete in the workaround for Bug#1628761.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1655049

Title:
  List index out of range on main page and nodes page

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1655049/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1655049] Re: List index out of range on main page and nodes page

[LaMont Jones]

I found some that exhibit the issue (00-22-59, 00-23-89) for starters.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1655049

Title:
  List index out of range on main page and nodes page

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1655049/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1655049] Re: List index out of range on main page and nodes page

[LaMont Jones]

Can you provide the first 3 octets of one of the bad MACs?  If you're
not sure which one, the following is sure to catch it:

sudo maas-region dbshell
select distinct substring(cast(mac_address as varchar) for 8) from 
maasserver_interface;

This would appear to be a bug in the python3-netaddr, which MAAS should
probably armor itself against.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1655049

Title:
  List index out of range on main page and nodes page

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1655049/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Accepted postfix 3.1.4-3 (source) into unstable

[LaMont Jones]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 09 Jan 2017 07:25:22 -0700
Source: postfix
Binary: postfix postfix-ldap postfix-lmdb postfix-cdb postfix-pcre 
postfix-mysql postfix-pgsql postfix-sqlite postfix-doc
Architecture: source
Version: 3.1.4-3
Distribution: unstable
Urgency: medium
Maintainer: LaMont Jones <lam...@debian.org>
Changed-By: LaMont Jones <lam...@debian.org>
Description:
 postfix- High-performance mail transport agent
 postfix-cdb - CDB map support for Postfix
 postfix-doc - Documentation for Postfix
 postfix-ldap - LDAP map support for Postfix
 postfix-lmdb - LMDB map support for Postfix
 postfix-mysql - MySQL map support for Postfix
 postfix-pcre - PCRE map support for Postfix
 postfix-pgsql - PostgreSQL map support for Postfix
 postfix-sqlite - SQLite map support for Postfix
Closes: 848686 850426 850430 850551 850573 850598 850616
Changes:
 postfix (3.1.4-3) unstable; urgency=medium
 .
   [LaMont Jones]
 .
   * Use the lmtp binary for lmtp, make it a hardlink instead of a symlink.
 Closes: #850430, #850426  LP: #1654453
 .
   [Scott Kitterman]
 .
   * Update multi-instance instructions to have new instances start on boot.
   * Juggle lmtp and qmgr symlinks so it builds
 .
   [Daniel Shahaf]
 .
   * Allow postfix variable interpolation in control scripts. (Accepted with
 changes.).  Closes: #848686
 .
   [localization folks]
 .
   * l10n: Updated Russian debconf translations. (Sergey Alyoshin)
   * l10n: Updated French debconf translations.  Closes: #850573 (jean-pierre
 giraud)
   * l10n: Updated Portuguese debconf translations.  Closes: #850616 (Miguel
 Figueiredo)
   * l10n: Updated Catalan debconf translations.  Closes: #850551 (Innocent De
 Marchi)
   * l10n: Updated Turkish debconf translations.  Closes: #850598 (Atila KOÇ)
Checksums-Sha1:
 e472f6eb433e270758b4912f08a4391aada854f7 2642 postfix_3.1.4-3.dsc
 0c87b291e67e40be8acc44bffcd9507263df6476 190620 postfix_3.1.4-3.debian.tar.xz
Checksums-Sha256:
 9a27aff403520328b267475d6d32b53aa04e7749d04c1d69865c3f99385fd5bf 2642 
postfix_3.1.4-3.dsc
 0fead39569f9224685dd4582bdb1d26b07953792b424855edd9d2fd6c00d82e2 190620 
postfix_3.1.4-3.debian.tar.xz
Files:
 66f4a6e636ae6c42842e61a404b55d7b 2642 mail extra postfix_3.1.4-3.dsc
 f0b4e557bfa9230d8ba901d4e108b870 190620 mail extra 
postfix_3.1.4-3.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIVAwUBWHOeRNVHlGMnADo/AQhgWg//XFGHUKHax5+pCFRD0uej2Q4MdfFHPafd
PP0K311Tgf2gwQrNH3NkNATixUczALWRUxhm8dHaNynCtl1kSau9KkVrooPttI7O
ei4aV0sa1QOo++XkEtJDoETVLF4F7yXNV7PeXrUpeahcYXsrxID2OCdrlTwInvDS
6gkld7QczZBEdwzCDxvb2yJKed/zTCotGmj/YiWxpg57eW7h1x3/ytLVLzyEl3nd
wA3ASa8LTYopH9VhuGpP/D/wBXPopMO/PshsBV3IHEi5XJotI7ZmKFqXNefuVNTF
jqcTPw488XN2ZxgEisM/dGxPGzRxDBIgMsAFPEaxyVtX4JFMBiIF/xnoV2eqcPFD
HF/Jmjy9uoExv6W5m+Ia7mcBq3kBmm/N8b+bFlcTxGM+Yzy2H8Y7KOIXDJo7x4cL
/Uv5TjkHpTbWIe/fuJ6NkSKyrOFLEMqfGOrbIGLLmFuTpKr1uprwtetM2O3YsiME
ihNpbVIuhptjX9Sx5l1zaDJ/A2UxZJMZRE13bN2vtgbPyEvX7+yLA98tbKezvZmf
fDVmqb9d8xLGsAgPxv1LD1nmbgJ4Jbre+q3Q2nhHjm3uBn/9dzckV0eBRuh5hr82
jOcKlA960TWWJJoz0dDhNj80fLXlMdM2NiKiLgEvrpEvLmA0+guAWGAQSj9P7RGW
0NUjKdC4OjE=
=o+SJ
-END PGP SIGNATURE-

[Bug 1654453] Re: LMTP delivery to Dovecot stops working in 3.1.4-1

[LaMont Jones]

There is a new test version in the ppa.  This one built. :/

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1654453

Title:
  LMTP delivery to Dovecot stops working in 3.1.4-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1654453/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1654453] Re: LMTP delivery to Dovecot stops working in 3.1.4-1

[LaMont Jones]

@mamarley - A postfix package with the fix (for testing) is in
ppa:lamont/postfix -- can you confirm that the bug is fixed with that
version?

thanks

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1654453

Title:
  LMTP delivery to Dovecot stops working in 3.1.4-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1654453/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1654453] Re: LMTP delivery to Dovecot stops working in 3.1.4-1

[LaMont Jones]

3.1.4-3 should be uploaded this weekend, with the fix.

** Changed in: postfix (Ubuntu)
   Status: Confirmed => Fix Committed

** Bug watch added: Debian Bug tracker #850430
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850430

** Also affects: postfix (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850430
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1654453

Title:
  LMTP delivery to Dovecot stops working in 3.1.4-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1654453/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1654453] Re: LMTP delivery to Dovecot stops working in 3.1.4-1

[LaMont Jones]

On Sat, Jan 07, 2017 at 01:26:41PM -, Michael Marley wrote:
> I just upgraded and still have exactly the same problem as before.

During the upgrade, did it say that it was changing master.cf as below?

In master.cf:
  using smtp binary for lmtp service (symlink removed)

In either case, please send me unredacted (other than any passwords) master.cf
and /var/log/apt/term.log from the upgrade?

lamont

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1654453

Title:
  LMTP delivery to Dovecot stops working in 3.1.4-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1654453/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Accepted postfix 3.1.4-2 (source) into unstable

[LaMont Jones]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 06 Jan 2017 08:41:36 -0700
Source: postfix
Binary: postfix postfix-ldap postfix-lmdb postfix-cdb postfix-pcre 
postfix-mysql postfix-pgsql postfix-sqlite postfix-doc
Architecture: source
Version: 3.1.4-2
Distribution: unstable
Urgency: medium
Maintainer: LaMont Jones <lam...@debian.org>
Changed-By: LaMont Jones <lam...@debian.org>
Description:
 postfix- High-performance mail transport agent
 postfix-cdb - CDB map support for Postfix
 postfix-doc - Documentation for Postfix
 postfix-ldap - LDAP map support for Postfix
 postfix-lmdb - LMDB map support for Postfix
 postfix-mysql - MySQL map support for Postfix
 postfix-pcre - PCRE map support for Postfix
 postfix-pgsql - PostgreSQL map support for Postfix
 postfix-sqlite - SQLite map support for Postfix
Closes: 850400 850430
Changes:
 postfix (3.1.4-2) unstable; urgency=medium
 .
   * Update postfix Suggestions.
   * Update postfix-sqlite postinst/prerm to reflect that addmap is idempotent.
   * Restore so.1.0.1 symlinks for map libraries and change how new entries are
 added.  Closes: #850400
   * Be more aggressive in retiring usage of lmtp binary.  Closes: #850430
 LP: #1654453
   * Check symlinks separately in postfix-script, to allow library symlinks.
 This will go away once the symlinks are dropped again.
Checksums-Sha1:
 fb98c9eb602d2db24ebe173d9511c1327dd144f4 2642 postfix_3.1.4-2.dsc
 4eabc4bb1b80593a3f76096097fbabcdd5169867 188800 postfix_3.1.4-2.debian.tar.xz
Checksums-Sha256:
 2cba260c9248417d2ff2e2e6f9b7901a1ef35bc1989989f151ee4d3c710474ab 2642 
postfix_3.1.4-2.dsc
 95375d84d3b8637019e99c0cde70fa09e09f014be7f4d001572759dfaeba0b17 188800 
postfix_3.1.4-2.debian.tar.xz
Files:
 33d559c822b6bf06010079fd1bc62cb6 2642 mail extra postfix_3.1.4-2.dsc
 a08b7114de32c8c23ad2ccc89ad9cb4a 188800 mail extra 
postfix_3.1.4-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIVAwUBWG/F4dVHlGMnADo/AQjZ6A//arn3fDrUKQeFVVPUco05tNCA9IHJvjP6
+zqwNH/vqaGt8lgCVxrnCCcDOtFOEvm/eGZ0VCwIKgdAxMUJCU5gN1t28T6M/QIn
J8lvVdzKpbtWpsLlGqwr6y2tpKLQFKpdl8lNhRnbi5YDXsqYWzPRlNzRLbUhRR3q
vqRAUedaWtHo6KbZauosdYUr81VKyxhtiDaJ+t/U0FhsYwZSe9FPoI9vBj22JFzc
ay4eBpWJ8DL7zuGl/75PwHRNSmXG6OxS3/O8JWtagQge+yIhO4pD9z/fiB6YuFv8
uAdvqVrPM1P4VKKfrzaTdIk7YSDnfz42olJE3SvoLdIb+w9arMdE5bBk/BxvYcLt
LkF/4aH14y/gFvruLiZPh5MPsLUyYOpKubMVQg/rdCIBhDyThGNYxvnqf1kZ2vJX
PCoBypZIp1p6q59UcPQ7H8wWXDfk6rO2EvI73qg4AYoSd28KmCuBbuWyfoVSVxJD
7VCUx07ca7VuPIeqDWHHpXNQ7JezIT6G0VzpkbJ3c9PrjTMSlRhap51D54GSs/jh
kj/vNvOGhtd/pCknxWDK8jI185NzF80c3HX5zzrl8Bf0tn5H/VtVg3H6lKCvDj6X
nuWsJhq8u7O5OVMK4MGu+mmZsT1scKoKBAh8SZ5XVvWKT2mzLoA9v2mRWuVulvwB
kxnIYpKuNTk=
=dRB1
-END PGP SIGNATURE-

[Bug 1654453] Re: LMTP delivery to Dovecot stops working in 3.1.4-1

[LaMont Jones]

Based on the reported contents of the line, I'm assuming that's the case
and uploading 3.1.4-2.  If that doesn't fix it, please reopen this bug.

** Changed in: postfix (Ubuntu)
   Importance: Undecided => Critical

** 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1654453

Title:
  LMTP delivery to Dovecot stops working in 3.1.4-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1654453/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1654453] Re: LMTP delivery to Dovecot stops working in 3.1.4-1

[LaMont Jones]

Is it possible that there is trailing whitespace on the lmtp line in
master.cf?  That would explain the issue.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1654453

Title:
  LMTP delivery to Dovecot stops working in 3.1.4-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1654453/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Bug#850430: postfix 3.1.4-1 breaks on lmtp interface

[LaMont Jones]

On Fri, Jan 06, 2017 at 03:22:34PM +0100, Thomas Leuxner wrote:
> $ grep lmtp /etc/postfix/master.cf
> lmtp  unix  -   -   y   -   -   lmtp

Is there by any chance any trailing whitespace on that line?

lamont

Bug#850430: postfix 3.1.4-1 breaks on lmtp interface

[LaMont Jones]

On Fri, Jan 06, 2017 at 03:22:34PM +0100, Thomas Leuxner wrote:
> $ grep lmtp /etc/postfix/master.cf
> lmtp  unix  -   -   y   -   -   lmtp

Is there by any chance any trailing whitespace on that line?

lamont

Accepted postfix 3.1.4-1 (source) into unstable

[LaMont Jones]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 04 Jan 2017 17:55:06 -0700
Source: postfix
Binary: postfix postfix-ldap postfix-lmdb postfix-cdb postfix-pcre 
postfix-mysql postfix-pgsql postfix-sqlite postfix-doc
Architecture: source
Version: 3.1.4-1
Distribution: unstable
Urgency: medium
Maintainer: LaMont Jones <lam...@debian.org>
Changed-By: LaMont Jones <lam...@debian.org>
Description:
 postfix- High-performance mail transport agent
 postfix-cdb - CDB map support for Postfix
 postfix-doc - Documentation for Postfix
 postfix-ldap - LDAP map support for Postfix
 postfix-lmdb - LMDB map support for Postfix
 postfix-mysql - MySQL map support for Postfix
 postfix-pcre - PCRE map support for Postfix
 postfix-pgsql - PostgreSQL map support for Postfix
 postfix-sqlite - SQLite map support for Postfix
Closes: 589188 794038 822291 832576 836306 844277 849584 849778 849919 849920 
849964 850049 850086
Changes:
 postfix (3.1.4-1) unstable; urgency=medium
 .
   [Wietse Venema]
 .
   * New Upstream 3.1.4
 .
   [Scott Kitterman]
 .
   * For systems using systemd (and only systems using systemd) and not
 configured for local only use, add service override file to start after
 network-online.target and systemd-resolved.service to ensure the network
 is fully up and name services are available.  Closes: #822291, #836306,
 #844277  LP: #1649453
   * Remove postfix-dev: The postfix headers are not public interfaces and not
 suitable for third-party development
   * Stop setting artificial soname for postfix share libs - upstream does not
 promise any ABI stability and in Debian exact version depends keep needed
 packages in sync - Resolves most symlink related issues with postfix check
   * Do not choke on dangling symlinks in ca-certificates.  LP: #1305232
   * Stop shipping lmtp symlink and have master.cf/master.cf.proto lmtp
 services us smtp - they are the same since postfix 2.1.  Closes: #832576
   * Remove debian/*.files - no longer needed
   * Split postfix-files into postfix-files.d snippets for each postfix-*
 binary to enable postfix set-permissions to have the potential to work
 (additional file naming issues still to be resolved)
   * Install /etc/postfix/makedefs.out so users can see how the package was
 built
   * Add /etc/postfix/dynamicmaps.cf.d and postfix-files.d to directories
 shipped by postfix
   * Exclude Postfix license files from postfix-files - not needed in Debian
 since we ship the licenses in debian/copyright
   * Update debian/patches/05_debian_defaults.diff to comment out files in
 postfix-files that Debian does not ship in /etc/postfix
   * Add debian/patches/05_debian_manpage_differences.diff to align
 postfix-files to Debian man page naming/compression
   * Add debian/patches/05_debian_readme_differences.diff to align
 postfix-files to Debian README file naming/compression.  Closes: #589188
 LP: #274108
   * Add OVERVIEW to README files shipped in postfix-doc
   * Moved install of map type so files inside the loop used to create their
 postfix-files.d snippets to simplify debian/rules
   * Added postfix.NEWS entry to describe the demise of the smtp -> lmtp symlink
   * Move man 5 *_tables man pages to their respective binary packages and add
 appropriate breaks/replaces
   * Remove ancient check for kernels before 2.6.  Closes: #794038
   * Remove service file override on purge
   * Do not attempt to use postmulti is /etc/postfix/main.cf does not exist -
 it will fail
   * Add NEWS item and documentation about how to us postfix service files.
 Closes: #849584
 .
   [LaMont Jones]
 .
   * Make lmtp warning be a debconf question, instead of a NEWS item.
   * Allow libmysqlclient-dev to satisfy build-deps, to make backporting easier.
   * Better permissions for /etc/postfix/postfix-files.d, et al.
   * Default to compatibility_level=2 on fresh installs.
   * Various lint cleanup in templates.
   * re-refresh po files for neatness.
   * Various message cleanup in postinst, for consistency.
 .
   [localization folks]
 .
   * l10n: Updated Japanese debconf translations.  Closes: #849919 (Kenshi Muto)
   * l10n: Updated Slovak debconf translations.  Closes: #849778 (helix84)
   * l10n: Updated Basque debconf translation.  Closes: #850049 (Dooteo)
   * l10n: Updated Swedish debconf translations.  Closes: #849920 (Martin Bagge)
   * l10n: Updated Danish debconf translations.  Closes: #849964 (Joe Dalton)
   * l10n: Updated Indonesian debconf translations. (Surya Fajri)
   * l10n: Updated Brazilian Portuguese debconf translations. (Uesli)
   * l10n: Updated Brazilian Portuguese debconf translations.  Closes: #850086
 (Marcelo Santana)
   * l10n: Updated German debconf translations. (Markus Hiereth)
   * l10n: Updated Brazilian Portuguese debconf translations.  Closes: #850086
 (Marcelo Santana)
   * l10n: Updated German debconf translations. (Markus Hiereth)

[Touch-packages] [Bug 1632808] Re: Consider supporting IPv6 autoconf in configure_networking

[LaMont Jones]

I am also not aware of anyone in the MAAS space who _wants_ autoconf for
ipv6 networks.  I am aware of at least one who wants it OFF for their
networks.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1632808

Title:
  Consider supporting IPv6 autoconf in configure_networking

Status in MAAS:
  Triaged
Status in initramfs-tools package in Ubuntu:
  Triaged

Bug description:
  Because DHCPv6 only does addresses, and not routes,
  configure_networking needs to wait for the kernel to process a router-
  advertisement before returning claiming an IPv6 config (since all it
  will have is a /128 and no routes, making for a pretty useless network
  stack.)  See Bug #1609898 for context.

  (The syntax for ip= should probably also be extended to allow SLAAC
  configuration.  If the user said "dhcp", then we should insist on
  getting our answer from DHCP.)

  On the bright side, iscsi retries, so after 1 or more failures to
  connect, the router-advertisement comes in and the connect succeeds.

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1632808/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1632808] Re: Consider supporting IPv6 autoconf in configure_networking

[LaMont Jones]

And leaving it triaged for MAAS, since once initramfs-tools supports it,
MAAS will need to propagate that to the UI.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1632808

Title:
  Consider supporting IPv6 autoconf in configure_networking

Status in MAAS:
  Triaged
Status in initramfs-tools package in Ubuntu:
  Triaged

Bug description:
  Because DHCPv6 only does addresses, and not routes,
  configure_networking needs to wait for the kernel to process a router-
  advertisement before returning claiming an IPv6 config (since all it
  will have is a /128 and no routes, making for a pretty useless network
  stack.)  See Bug #1609898 for context.

  (The syntax for ip= should probably also be extended to allow SLAAC
  configuration.  If the user said "dhcp", then we should insist on
  getting our answer from DHCP.)

  On the bright side, iscsi retries, so after 1 or more failures to
  connect, the router-advertisement comes in and the connect succeeds.

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1632808/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Bug 1632808] Re: Consider supporting IPv6 autoconf in configure_networking

[LaMont Jones]

And leaving it triaged for MAAS, since once initramfs-tools supports it,
MAAS will need to propagate that to the UI.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1632808

Title:
  Consider supporting IPv6 autoconf in configure_networking

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1632808/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1632480] Re: Latest Yakkety grub timesout when attempting to UEFI boot over IPv6

[LaMont Jones]

I am not able to reproduce this.  Is this still an issue for the machine
in question?

** Changed in: grub2 (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1632480

Title:
  Latest Yakkety grub timesout when attempting to UEFI boot over IPv6

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1632480/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Touch-packages] [Bug 1632808] Re: configure_networking exits without any ipv6 routes

[LaMont Jones]

Converting this to be the bug for ip6=stateless (or ip6=autoconf?), as
the rest of it was solved with 1621507.

** Changed in: maas
   Status: New => Fix Released

** Summary changed:

- configure_networking exits without any ipv6 routes
+ Consider supporting IPv6 autoconf in configure_networking

** Changed in: maas
   Status: Fix Released => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1632808

Title:
  Consider supporting IPv6 autoconf in configure_networking

Status in MAAS:
  Triaged
Status in initramfs-tools package in Ubuntu:
  Triaged

Bug description:
  Because DHCPv6 only does addresses, and not routes,
  configure_networking needs to wait for the kernel to process a router-
  advertisement before returning claiming an IPv6 config (since all it
  will have is a /128 and no routes, making for a pretty useless network
  stack.)  See Bug #1609898 for context.

  (The syntax for ip= should probably also be extended to allow SLAAC
  configuration.  If the user said "dhcp", then we should insist on
  getting our answer from DHCP.)

  On the bright side, iscsi retries, so after 1 or more failures to
  connect, the router-advertisement comes in and the connect succeeds.

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1632808/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Bug 1632808] Re: Consider supporting IPv6 autoconf in configure_networking

[LaMont Jones]

I am also not aware of anyone in the MAAS space who _wants_ autoconf for
ipv6 networks.  I am aware of at least one who wants it OFF for their
networks.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1632808

Title:
  Consider supporting IPv6 autoconf in configure_networking

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1632808/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1632808] Re: configure_networking exits without any ipv6 routes

[LaMont Jones]

Converting this to be the bug for ip6=stateless (or ip6=autoconf?), as
the rest of it was solved with 1621507.

** Changed in: maas
   Status: New => Fix Released

** Summary changed:

- configure_networking exits without any ipv6 routes
+ Consider supporting IPv6 autoconf in configure_networking

** Changed in: maas
   Status: Fix Released => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1632808

Title:
  Consider supporting IPv6 autoconf in configure_networking

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1632808/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Yahoo-eng-team] [Bug 1639930] Re: initramfs network configuration ignored if only ip6= on kernel command line

[LaMont Jones]

No maas changes were required here, since it always specifies both ip=
and ip6=

** Changed in: maas
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1639930

Title:
  initramfs network configuration ignored if only ip6= on kernel command
  line

Status in cloud-init:
  Fix Released
Status in MAAS:
  Fix Released
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Fix Released
Status in cloud-init source package in Yakkety:
  In Progress

Bug description:
  === Begin SRU Template ===
  [Impact]
  On a system booted with both ip6= and ip= on the kernel command line
  cloud-init will raise an exception and fail to process user-data and
  have its normal affect on boot.

  That is because cloud-init previously raised an exception when more
  than one file in /run/net*.conf declared the same DEVICE.  Changes to
  isc-dhcp and initramfs-tools have changed their behavior and cloud-init
  has to adjust to allow DEVICE6= and DEVICE= in separate files.

  [Test Case]
  Boot a system on a network with both ipv4 and ipv6 dhcp servers,
  and pass kernel command line with:
    ip=dhcp ip6=dhcp

  [Regression Potential]
  Regression seems unlikely as this is relaxing a check.  Where previously
  an exception would have been raised, cloud-init will now go on.

  So it seems most likely, something that didn't work before (due to raised
  exception) would now still not work, but with failures.  That is not
  expected, but that would likely be where regressions were found.

  === End SRU Template ===

  In changes made under bug 1621615 (specifically a1cdebdea), we now
  expect that there may be a 'ip6=' argument on the kernel command line.
  The changes made did not test the case where there is 'ip6=' and no
  'ip='.

  The code currently will return with no network configuration found if
  there is only ip6=...

  Related bugs:
   * bug 1621615: network not configured when ipv6 netbooted into cloud-init
   * bug 1621507: initramfs-tools configure_networking() fails to dhcp IPv6 
addresses
   * bug 1635716: Can't bring up a machine on a dual network (ipv4 and ipv6)

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1639930/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1639930] Re: initramfs network configuration ignored if only ip6= on kernel command line

[LaMont Jones]

No maas changes were required here, since it always specifies both ip=
and ip6=

** Changed in: maas
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1639930

Title:
  initramfs network configuration ignored if only ip6= on kernel command
  line

Status in cloud-init:
  Fix Released
Status in MAAS:
  Fix Released
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Fix Released
Status in cloud-init source package in Yakkety:
  In Progress

Bug description:
  === Begin SRU Template ===
  [Impact]
  On a system booted with both ip6= and ip= on the kernel command line
  cloud-init will raise an exception and fail to process user-data and
  have its normal affect on boot.

  That is because cloud-init previously raised an exception when more
  than one file in /run/net*.conf declared the same DEVICE.  Changes to
  isc-dhcp and initramfs-tools have changed their behavior and cloud-init
  has to adjust to allow DEVICE6= and DEVICE= in separate files.

  [Test Case]
  Boot a system on a network with both ipv4 and ipv6 dhcp servers,
  and pass kernel command line with:
    ip=dhcp ip6=dhcp

  [Regression Potential]
  Regression seems unlikely as this is relaxing a check.  Where previously
  an exception would have been raised, cloud-init will now go on.

  So it seems most likely, something that didn't work before (due to raised
  exception) would now still not work, but with failures.  That is not
  expected, but that would likely be where regressions were found.

  === End SRU Template ===

  In changes made under bug 1621615 (specifically a1cdebdea), we now
  expect that there may be a 'ip6=' argument on the kernel command line.
  The changes made did not test the case where there is 'ip6=' and no
  'ip='.

  The code currently will return with no network configuration found if
  there is only ip6=...

  Related bugs:
   * bug 1621615: network not configured when ipv6 netbooted into cloud-init
   * bug 1621507: initramfs-tools configure_networking() fails to dhcp IPv6 
addresses
   * bug 1635716: Can't bring up a machine on a dual network (ipv4 and ipv6)

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1639930/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Bug 1639930] Re: initramfs network configuration ignored if only ip6= on kernel command line

[LaMont Jones]

No maas changes were required here, since it always specifies both ip=
and ip6=

** Changed in: maas
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1639930

Title:
  initramfs network configuration ignored if only ip6= on kernel command
  line

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1639930/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1618543] Re: freeipmi lacks IPv6 support

[LaMont Jones]

No maas changes were needed here.

** Changed in: maas
   Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1618543

Title:
  freeipmi lacks IPv6 support

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1618543/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Group.of.nepali.translators] [Bug 1618543] Re: freeipmi lacks IPv6 support

[LaMont Jones]

No maas changes were needed here.

** Changed in: maas
   Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1618543

Title:
  freeipmi lacks IPv6 support

Status in MAAS:
  Fix Released
Status in freeipmi package in Ubuntu:
  Fix Released
Status in freeipmi source package in Xenial:
  Fix Released
Status in freeipmi source package in Yakkety:
  Fix Released

Bug description:
  ipmipower in 1.4.11 and 1.5 lack ipv6 support.  This is in-plan for
  1.6 from upstream.

  See also related bug 1645912.

  The -h argument to ipmipower needs to be extended to accept
  [ip:v6::addr]:port type syntax, and the processing of the hostnames
  needs to take into account ipv6 addresses as well.

  [Impact]

   * If a BMC has only IPv6 addresses, then ipmipower cannot discover
  it.

   * MAAS needs to be able to do just that.

  [Test Case]

   * To reproduce / verify the bug, configure a BMC with an IPv6 address, and
     try to talk to it.

  [Regression Potential]

   * If a BMC has both IPv6 and IPv4 addresses in the DNS, and the hostname
     is used to control it, then this change will cause ipmipower to try
     IPv6 first, where it used to completely ignore IPv6 in the DNS.  We
     believe this to be the correct behavior and that it does not affect
     the current installed base.  (IPv6 BMC addresses are not a thing that
     we have been able to find anywhere.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1618543/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Bug 1229458] Re: grubnetx64.efi tftp client does not work over ipv6

[LaMont Jones]

Verified that both IPv4 pxeboot and IPv6 uefi boot cleanly into MAAS.

** Tags removed: verification-needed
** Tags added: verification-done

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1229458

Title:
  grubnetx64.efi tftp client does not work over ipv6

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1229458/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

REVISED: postfix 3.1.3-6: Please update debconf PO translation for the package postfix

[LaMont Jones]

Hi,

[Right after I sent the last email, review found that one more template
was needed.  Please do the translations based on this email, not the
earlier one.]

You are noted as the last translator of the debconf translation for
postfix. The English template has been changed, and now some messages
are marked "fuzzy" in your translation or are missing.
I would be grateful if you could take the time and update it.
Please send the updated file to me, or submit it as a wishlist bug
against postfix.

The deadline for receiving the updated translation is
Sun, 08 Jan 2017 17:00:00 -0700.

Thanks in advance,

#
# Catalan translation for postfix package.
# Copyright (C) 2012 LaMont Jones.
# This file is distributed under the same license as the postfix package.
#
# Jordà Polo <jo...@ettin.org>, 2006, 2007, 2008, 2012.
#
msgid ""
msgstr ""
"Project-Id-Version: 2.9.1-5\n"
"Report-Msgid-Bugs-To: post...@packages.debian.org\n"
"POT-Creation-Date: 2016-12-30 20:42+\n"
"PO-Revision-Date: 2012-06-03 09:34+0200\n"
"Last-Translator: Jordà Polo <jo...@ettin.org>\n"
"Language-Team: Catalan <debian-l10n-catalan@lists.debian.org>\n"
"Language: ca\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"

#. Type: boolean
#. Description
#: ../templates:1001
msgid "Add a 'mydomain' entry in main.cf for upgrade?"
msgstr ""
"Voleu afegir l'entrada «mydomain» al fitxer main.cf per a l'actualització?"

#. Type: boolean
#. Description
#: ../templates:1001
msgid ""
"Postfix version 2.3.3-2 and later require changes in main.cf. Specifically, "
"mydomain must be specified, since hostname(1) is not a fully qualified "
"domain name (FQDN)."
msgstr ""
"A partir de la versió 2.3.3-2 de Postfix es requereixen canvis a main.cf. "
"Més concretament, s'ha d'especificar «mydomain», ja que hostname(2) no és un "
"nom de domini completament qualificat (FQDN)."

#. Type: boolean
#. Description
#: ../templates:1001
msgid ""
"Failure to fix this will result in a broken mailer. Decline this option to "
"abort the upgrade, giving you the opportunity to add this configuration "
"yourself. Accept this option to automatically set mydomain based on the FQDN "
"of the machine."
msgstr ""
"Si es produeix una fallada en aquest punt, el funcionament de "
"l'administrador de correu pot veure's interromput. Declineu aquesta opció si "
"voleu avortar l'actualització i afegir aquesta configuració manualment. "
"Accepteu si preferiu que s'estableixi «mydomain» automàticament a partir de "
"l'FQDN de la màquina."

#. Type: boolean
#. Description
#: ../templates:2001
#, fuzzy
#| msgid "Correct retry entry in master.cf for upgrade?"
msgid "Set smtpd_relay_restrictions in main.cf for upgrade?"
msgstr ""
"Voleu esmenar l'entrada «retry» al fitxer master.cf per a l'actualització?"

#. Type: boolean
#. Description
#: ../templates:2001
msgid ""
"Postfix version 2.10 adds smtpd_relay_restrictions, to separate relaying "
"restrictions from recipient restrictions, and you have a non-default value "
"for smtpd_recipient_restrictions."
msgstr ""

#. Type: boolean
#. Description
#: ../templates:2001
msgid ""
"Failure to do this may result in deferred or bounced mail after the "
"upgrade.  Accept this option to set smtpd_relay_restrictions equal to "
"smtpd_recipient_restrictions."
msgstr ""

#. Type: boolean
#. Description
#: ../templates:3001
msgid "Update configuration to avoid compatibility warnings?"
msgstr ""

#. Type: boolean
#. Description
#: ../templates:3001
msgid ""
"This upgrade of postfix changes some default values in the configuration. As "
"part of this upgrade, the following will be changed: (1) chrooted components "
"will be changed from '-' to 'y' in master.cf, and (2) myhostname will be set "
"to a fully-qualified domain name if it is not already such.  The install "
"will be aborted if you do not allow the change."
msgstr ""

#. Type: boolean
#. Description
#: ../templates:4001
msgid "Update master.cf for merged lmtp/smtp binary?"
msgstr ""

#. Type: boolean
#. Description
#: ../templates:4001
msgid ""
"This upgrade of postfix drops the \"lmtp\" symlink, and your configuration "
"(master.cf) refers to it: lmtp was merged into smtp long ago.  The install "
"will be aborted if you do not allow the change."
msgstr ""

#. Type: boolean
#. Descript

REVISED: postfix 3.1.3-6: Please update debconf PO translation for the package postfix

[LaMont Jones]

Hi,

[Right after I sent the last email, review found that one more template
was needed.  Please do the translations based on this email, not the
earlier one.]

You are noted as the last translator of the debconf translation for
postfix. The English template has been changed, and now some messages
are marked "fuzzy" in your translation or are missing.
I would be grateful if you could take the time and update it.
Please send the updated file to me, or submit it as a wishlist bug
against postfix.

The deadline for receiving the updated translation is
Sun, 08 Jan 2017 17:00:00 -0700.

Thanks in advance,

#
#Translators, if you are not familiar with the PO format, gettext
#documentation is worth reading, especially sections dedicated to
#this format, e.g. by running:
# info -n '(gettext)PO Files'
# info -n '(gettext)Header Entry'
#
#Some information specific to po-debconf are available at
#/usr/share/doc/po-debconf/README-trans
# or http://www.debian.org/intl/l10n/po-debconf/README-trans
#
#Developers do not need to manually edit POT or PO files.
#
msgid ""
msgstr ""
"Project-Id-Version: postfix 3.0.4-3\n"
"Report-Msgid-Bugs-To: post...@packages.debian.org\n"
"POT-Creation-Date: 2016-12-30 20:42+\n"
"PO-Revision-Date: 2016-02-28 21:23+0900\n"
"Last-Translator: Kenshi Muto \n"
"Language-Team: Japanese \n"
"Language: ja\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"

#. Type: boolean
#. Description
#: ../templates:1001
msgid "Add a 'mydomain' entry in main.cf for upgrade?"
msgstr "更新のために master.cf に mydomain エントリを追加しますか?"

#. Type: boolean
#. Description
#: ../templates:1001
msgid ""
"Postfix version 2.3.3-2 and later require changes in main.cf. Specifically, "
"mydomain must be specified, since hostname(1) is not a fully qualified "
"domain name (FQDN)."
msgstr ""
"Postfix バージョン 2.3.3-2 以降では、main.cf の変更を必要とします。特に、"
"hostname(1) が完全修飾ドメイン名 (FQDN) ではなくなったので、 mydomain を指定"
"する必要があります。"

#. Type: boolean
#. Description
#: ../templates:1001
msgid ""
"Failure to fix this will result in a broken mailer. Decline this option to "
"abort the upgrade, giving you the opportunity to add this configuration "
"yourself. Accept this option to automatically set mydomain based on the FQDN "
"of the machine."
msgstr ""
"これを修正するのに失敗すると、壊れたメーラとなってしまいます。更新を中止する"
"にはこの選択肢に「いいえ」とし、この設定をあなた自身で追加します。この選択肢"
"で「はい」と答えれば、自動的にマシンの FQDN に基き mydomain を設定します。"

#. Type: boolean
#. Description
#: ../templates:2001
msgid "Set smtpd_relay_restrictions in main.cf for upgrade?"
msgstr "更新のために master.cf の smtpd_relay_restrictions を設定しますか?"

#. Type: boolean
#. Description
#: ../templates:2001
msgid ""
"Postfix version 2.10 adds smtpd_relay_restrictions, to separate relaying "
"restrictions from recipient restrictions, and you have a non-default value "
"for smtpd_recipient_restrictions."
msgstr ""
"Postfix バージョン 2.10 では、リレー制限を受信者制限から分離するために "
"smtpd_relay_restrictions が追加されました。そして今、"
"smtpd_recipient_restrictions にはデフォルトではない値が設定されています。"

#. Type: boolean
#. Description
#: ../templates:2001
msgid ""
"Failure to do this may result in deferred or bounced mail after the "
"upgrade.  Accept this option to set smtpd_relay_restrictions equal to "
"smtpd_recipient_restrictions."
msgstr ""
"これは、更新後に、メールを遅延または返却してしまう結果となる恐れがあります。"
"smtpd_relay_restrictions を smtpd_recipient_restrictions と等価になるよう設定"
"するには、この選択肢を選んでください。"

#. Type: boolean
#. Description
#: ../templates:3001
msgid "Update configuration to avoid compatibility warnings?"
msgstr ""

#. Type: boolean
#. Description
#: ../templates:3001
msgid ""
"This upgrade of postfix changes some default values in the configuration. As "
"part of this upgrade, the following will be changed: (1) chrooted components "
"will be changed from '-' to 'y' in master.cf, and (2) myhostname will be set "
"to a fully-qualified domain name if it is not already such.  The install "
"will be aborted if you do not allow the change."
msgstr ""

#. Type: boolean
#. Description
#: ../templates:4001
msgid "Update master.cf for merged lmtp/smtp binary?"
msgstr ""

#. Type: boolean
#. Description
#: ../templates:4001
#, fuzzy
#| msgid ""
#| "This upgrade of postfix changes where daemons are located, and your "
#| "postfix configuration explicitly specifies the old location.  The install "
#| "will be aborted if you do not allow the change."
msgid ""
"This upgrade of postfix drops the \"lmtp\" symlink, and your configuration "
"(master.cf) refers to it: lmtp was merged into smtp long ago.  The install "
"will be aborted if you do not allow the change."
msgstr ""
"postfix の今回の更新ではデーモンの置かれる位置が変更されていますが、現状の "
"postfix 設定では以前の位置を明示的に指定しています。この変更を受け入れない場"
"合はインストールを中止します。"

#. Type: boolean
#. Description
#: ../templates:5001
#, fuzzy
#| msgid "Update main.cf for daemon_directory change"
msgid "Update main.cf for daemon_directory change?"
msgstr "daemon_directory の変更に伴い 

REVISED: postfix 3.1.3-6: Please update debconf PO translation for the package postfix

[LaMont Jones]

Hi,

[Right after I sent the last email, review found that one more template
was needed.  Please do the translations based on this email, not the
earlier one.]

You are noted as the last translator of the debconf translation for
postfix. The English template has been changed, and now some messages
are marked "fuzzy" in your translation or are missing.
I would be grateful if you could take the time and update it.
Please send the updated file to me, or submit it as a wishlist bug
against postfix.

The deadline for receiving the updated translation is
Sun, 08 Jan 2017 17:00:00 -0700.

Thanks in advance,

# Translation of postfix debconf templates to German
# Copyright (C) Helge Kreutzmann , 2006-2008, 2012, 2014, 2016.
# This file is distributed under the same license as the postfix package.
#
msgid ""
msgstr ""
"Project-Id-Version: postfix 3.0.3-2\n"
"Report-Msgid-Bugs-To: post...@packages.debian.org\n"
"POT-Creation-Date: 2016-12-30 20:42+\n"
"PO-Revision-Date: 2016-02-27 10:56+0100\n"
"Last-Translator: Helge Kreutzmann \n"
"Language-Team: de \n"
"Language: de\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=iso-8859-15\n"
"Content-Transfer-Encoding: 8bit\n"

#. Type: boolean
#. Description
#: ../templates:1001
msgid "Add a 'mydomain' entry in main.cf for upgrade?"
msgstr "Einen »mydomain«-Eintrag in main.cf beim Upgrade hinzufügen?"

#. Type: boolean
#. Description
#: ../templates:1001
msgid ""
"Postfix version 2.3.3-2 and later require changes in main.cf. Specifically, "
"mydomain must be specified, since hostname(1) is not a fully qualified "
"domain name (FQDN)."
msgstr ""
"Postfix, Version 2.3.3-2 und neuer, benötigt Änderungen in der main.cf. "
"Insbesondere muss »mydomain« angegeben werden, da hostname(1) kein voll-"
"qualifizierter Domain-Name (FQDN) ist."

#. Type: boolean
#. Description
#: ../templates:1001
msgid ""
"Failure to fix this will result in a broken mailer. Decline this option to "
"abort the upgrade, giving you the opportunity to add this configuration "
"yourself. Accept this option to automatically set mydomain based on the FQDN "
"of the machine."
msgstr ""
"Wenn Sie dies nicht korrigieren, wird Ihr E-Mail-Server unbrauchbar. "
"Verneinen Sie, um das Upgrade abzubrechen und diese Änderung selbst "
"vorzunehmen. Akzeptieren Sie, um, basierend auf dem FQDN, mydomain "
"automatisch zu setzen."

#. Type: boolean
#. Description
#: ../templates:2001
msgid "Set smtpd_relay_restrictions in main.cf for upgrade?"
msgstr "smtpd_relay_restrictions in main.cf für das Upgrade setzen?"

#. Type: boolean
#. Description
#: ../templates:2001
msgid ""
"Postfix version 2.10 adds smtpd_relay_restrictions, to separate relaying "
"restrictions from recipient restrictions, and you have a non-default value "
"for smtpd_recipient_restrictions."
msgstr ""
"Postfix Version 2.10 fügt smtpd_relay_restrictions hinzu, um Weiterleitungs-"
"von Empfänger-Beschränkungen zu trennen. Bei Ihnen liegt eine von der "
"Vorgabe abweichende smtpd_recipient_restrictions vor."

#. Type: boolean
#. Description
#: ../templates:2001
msgid ""
"Failure to do this may result in deferred or bounced mail after the "
"upgrade.  Accept this option to set smtpd_relay_restrictions equal to "
"smtpd_recipient_restrictions."
msgstr ""
"Wird dies nicht vorgenommen, kann nach dem Upgrade E-Mail verzögert oder "
"abgelehnt (»bounced«) werden. Aktzeptieren Sie diese Option, um "
"smtpd_relay_restrictions identisch zu smtpd_recipient_restrictions zu setzen."

#. Type: boolean
#. Description
#: ../templates:3001
msgid "Update configuration to avoid compatibility warnings?"
msgstr ""

#. Type: boolean
#. Description
#: ../templates:3001
msgid ""
"This upgrade of postfix changes some default values in the configuration. As "
"part of this upgrade, the following will be changed: (1) chrooted components "
"will be changed from '-' to 'y' in master.cf, and (2) myhostname will be set "
"to a fully-qualified domain name if it is not already such.  The install "
"will be aborted if you do not allow the change."
msgstr ""

#. Type: boolean
#. Description
#: ../templates:4001
msgid "Update master.cf for merged lmtp/smtp binary?"
msgstr ""

#. Type: boolean
#. Description
#: ../templates:4001
#, fuzzy
#| msgid ""
#| "This upgrade of postfix changes where daemons are located, and your "
#| "postfix configuration explicitly specifies the old location.  The install "
#| "will be aborted if you do not allow the change."
msgid ""
"This upgrade of postfix drops the \"lmtp\" symlink, and your configuration "
"(master.cf) refers to it: lmtp was merged into smtp long ago.  The install "
"will be aborted if you do not allow the change."
msgstr ""
"Dieses Upgrade von Postfix ändert den Speicherort der Daemons. Ihre Postfix-"
"Konfiguration spezifiziert explizit den alten Ort. Die Installation wird "
"abbrechen, falls Sie der Änderung nicht zustimmen."

#. Type: boolean
#. 

REVISED: postfix 3.1.3-6: Please update debconf PO translation for the package postfix

[LaMont Jones]

Hi,

[Right after I sent the last email, review found that one more template
was needed.  Please do the translations based on this email, not the
earlier one.]

You are noted as the last translator of the debconf translation for
postfix. The English template has been changed, and now some messages
are marked "fuzzy" in your translation or are missing.
I would be grateful if you could take the time and update it.
Please send the updated file to me, or submit it as a wishlist bug
against postfix.

The deadline for receiving the updated translation is
Sun, 08 Jan 2017 17:00:00 -0700.

Thanks in advance,

# Danish translation postfix.
# Copyright (C) 2013 postfix & nedenstående oversættere.
# This file is distributed under the same license as the postfix package.
# Joe Hansen , 2010, 2012, 2013.
#
msgid ""
msgstr ""
"Project-Id-Version: postfix\n"
"Report-Msgid-Bugs-To: post...@packages.debian.org\n"
"POT-Creation-Date: 2016-12-30 20:42+\n"
"PO-Revision-Date: 2013-03-26 19:21+0100\n"
"Last-Translator: Joe Hansen \n"
"Language-Team: Danish \n"
"Language: da\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"

#. Type: boolean
#. Description
#: ../templates:1001
msgid "Add a 'mydomain' entry in main.cf for upgrade?"
msgstr "Tilføj et punkt »mydomain« i main.cf for opgradering?"

#. Type: boolean
#. Description
#: ../templates:1001
msgid ""
"Postfix version 2.3.3-2 and later require changes in main.cf. Specifically, "
"mydomain must be specified, since hostname(1) is not a fully qualified "
"domain name (FQDN)."
msgstr ""
"Postfix version 2.3.3-2 og senere kræver ændringer i main.cf. Specifikt skal "
"mydomain angives, da hostname(1) ikke er et fuldt kvalificeret domænenavn "
"(FQDN)."

#. Type: boolean
#. Description
#: ../templates:1001
msgid ""
"Failure to fix this will result in a broken mailer. Decline this option to "
"abort the upgrade, giving you the opportunity to add this configuration "
"yourself. Accept this option to automatically set mydomain based on the FQDN "
"of the machine."
msgstr ""
"Manglende rettelse af dette vil resultere i en ødelagt sender. Afslå denne "
"indstilling for at afbryde opgraderingen, hvilket giver dig mulighed for "
"selv at tilføje denne konfiguration. Accepter denne indstilling for "
"automatisk at angive mydomain baseret på FQDN'en på denne maskine."

#. Type: boolean
#. Description
#: ../templates:2001
msgid "Set smtpd_relay_restrictions in main.cf for upgrade?"
msgstr "Sæt smtpd_relay_restrictions i main.cf for opgradering?"

#. Type: boolean
#. Description
#: ../templates:2001
msgid ""
"Postfix version 2.10 adds smtpd_relay_restrictions, to separate relaying "
"restrictions from recipient restrictions, and you have a non-default value "
"for smtpd_recipient_restrictions."
msgstr ""
"Postfix version 2.10 tilføjer smtpd_relay_restrictions, for at adskille "
"»relaying«-restriktioner fra modtagerbegrænsninge, og du har en værdi der "
"ikke er standard for smtpd_recipient_restrictions."

#. Type: boolean
#. Description
#: ../templates:2001
msgid ""
"Failure to do this may result in deferred or bounced mail after the "
"upgrade.  Accept this option to set smtpd_relay_restrictions equal to "
"smtpd_recipient_restrictions."
msgstr ""
"Hvis dette ikke gøres kan resultatet være afvist til tilbagesendt post efter "
"opgraderingen. Accepter denne indstilling for at sætte "
"smtpd_relay_restrictions lig smtpd_recipient_restrictions."

#. Type: boolean
#. Description
#: ../templates:3001
msgid "Update configuration to avoid compatibility warnings?"
msgstr ""

#. Type: boolean
#. Description
#: ../templates:3001
msgid ""
"This upgrade of postfix changes some default values in the configuration. As "
"part of this upgrade, the following will be changed: (1) chrooted components "
"will be changed from '-' to 'y' in master.cf, and (2) myhostname will be set "
"to a fully-qualified domain name if it is not already such.  The install "
"will be aborted if you do not allow the change."
msgstr ""

#. Type: boolean
#. Description
#: ../templates:4001
msgid "Update master.cf for merged lmtp/smtp binary?"
msgstr ""

#. Type: boolean
#. Description
#: ../templates:4001
msgid ""
"This upgrade of postfix drops the \"lmtp\" symlink, and your configuration "
"(master.cf) refers to it: lmtp was merged into smtp long ago.  The install "
"will be aborted if you do not allow the change."
msgstr ""

#. Type: boolean
#. Description
#: ../templates:5001
msgid "Update main.cf for daemon_directory change?"
msgstr ""

#. Type: boolean
#. Description
#: ../templates:5001
msgid ""
"This upgrade of postfix changes where daemons are located, and your postfix "
"configuration explicitly specifies the old location.  The install will be "
"aborted if you do not allow the change."
msgstr ""

#. Type: boolean
#. Description
#: ../templates:6001
msgid "Update dynamicmaps.cf for 

REVISED: postfix 3.1.3-6: Please update debconf PO translation for the package postfix

[LaMont Jones]

Hi,

[Right after I sent the last email, review found that one more template
was needed.  Please do the translations based on this email, not the
earlier one.]

You are noted as the last translator of the debconf translation for
postfix. The English template has been changed, and now some messages
are marked "fuzzy" in your translation or are missing.
I would be grateful if you could take the time and update it.
Please send the updated file to me, or submit it as a wishlist bug
against postfix.

The deadline for receiving the updated translation is
Sun, 08 Jan 2017 17:00:00 -0700.

Thanks in advance,

# Brazilian Portuguese translation of postfix.
# Copyright (C) 2016 THE postfix'S COPYRIGHT HOLDER
# This file is distributed under the same license as the postfix package.
# André Luís Lopes , -2004.
# Marcelo Gomes de Santana , 2013-2016.
#
msgid ""
msgstr ""
"Project-Id-Version: postfix 3.0.4-3\n"
"Report-Msgid-Bugs-To: post...@packages.debian.org\n"
"POT-Creation-Date: 2016-12-30 20:42+\n"
"PO-Revision-Date: 2016-02-27 02:28-0300\n"
"Last-Translator: Marcelo Gomes de Santana \n"
"Language-Team: Brazilian Portuguese \n"
"Language: pt_BR\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"

#. Type: boolean
#. Description
#: ../templates:1001
msgid "Add a 'mydomain' entry in main.cf for upgrade?"
msgstr "Adicionar uma entrada \"mydomain\" ao main.cf para atualização?"

#. Type: boolean
#. Description
#: ../templates:1001
msgid ""
"Postfix version 2.3.3-2 and later require changes in main.cf. Specifically, "
"mydomain must be specified, since hostname(1) is not a fully qualified "
"domain name (FQDN)."
msgstr ""
"A versão 2.3.3-2 e posterior do Postfix requer mudanças no main.cf. "
"Especificamente, o mydomain deve ser definido, uma vez que o hostname(1) não "
"é um nome de domínio completamente qualificado (FQDN)."

#. Type: boolean
#. Description
#: ../templates:1001
msgid ""
"Failure to fix this will result in a broken mailer. Decline this option to "
"abort the upgrade, giving you the opportunity to add this configuration "
"yourself. Accept this option to automatically set mydomain based on the FQDN "
"of the machine."
msgstr ""
"Caso isso não seja corrigido, resultará em um servidor de e-mail quebrado. "
"Não aceite esta opção para cancelar a atualização, o que lhe dará a "
"oportunidade de adicionar a configuração manualmente. Aceite esta opção para "
"definir automaticamente o mydomain baseado no nome de domínio completamente "
"qualificado (FQDN) da máquina."

#. Type: boolean
#. Description
#: ../templates:2001
msgid "Set smtpd_relay_restrictions in main.cf for upgrade?"
msgstr "Definir smtpd_relay_restrictions no main.cf para atualização?"

#. Type: boolean
#. Description
#: ../templates:2001
msgid ""
"Postfix version 2.10 adds smtpd_relay_restrictions, to separate relaying "
"restrictions from recipient restrictions, and you have a non-default value "
"for smtpd_recipient_restrictions."
msgstr ""
"A versão 2.10 do Postfix adiciona smtpd_relay_restrictions, para separar as "
"restrições de retransmissão das restrições de destinatário, e você tem um "
"valor fora do padrão para smtpd_recipient_restrictions."

#. Type: boolean
#. Description
#: ../templates:2001
msgid ""
"Failure to do this may result in deferred or bounced mail after the "
"upgrade.  Accept this option to set smtpd_relay_restrictions equal to "
"smtpd_recipient_restrictions."
msgstr ""
"Caso isto falhe, pode resultar em mensagem deferida ou devolvida após a "
"atualização. Aceite esta opção para definir smtpd_relay_restrictions igual a "
"smtpd_recipient_restrictions."

#. Type: boolean
#. Description
#: ../templates:3001
msgid "Update configuration to avoid compatibility warnings?"
msgstr ""

#. Type: boolean
#. Description
#: ../templates:3001
msgid ""
"This upgrade of postfix changes some default values in the configuration. As "
"part of this upgrade, the following will be changed: (1) chrooted components "
"will be changed from '-' to 'y' in master.cf, and (2) myhostname will be set "
"to a fully-qualified domain name if it is not already such.  The install "
"will be aborted if you do not allow the change."
msgstr ""

#. Type: boolean
#. Description
#: ../templates:4001
msgid "Update master.cf for merged lmtp/smtp binary?"
msgstr ""

#. Type: boolean
#. Description
#: ../templates:4001
#, fuzzy
#| msgid ""
#| "This upgrade of postfix changes where daemons are located, and your "
#| "postfix configuration explicitly specifies the old location.  The install "
#| "will be aborted if you do not allow the change."
msgid ""
"This upgrade of postfix drops the \"lmtp\" symlink, and your configuration "
"(master.cf) refers to it: lmtp was merged into smtp long ago.  The install "
"will be aborted if you do not allow the change."
msgstr ""
"Esta atualização do 

REVISED: postfix 3.1.3-6: Please update debconf PO translation for the package postfix

[LaMont Jones]

Hi,

[Right after I sent the last email, review found that one more template
was needed.  Please do the translations based on this email, not the
earlier one.]

You are noted as the last translator of the debconf translation for
postfix. The English template has been changed, and now some messages
are marked "fuzzy" in your translation or are missing.
I would be grateful if you could take the time and update it.
Please send the updated file to me, or submit it as a wishlist bug
against postfix.

The deadline for receiving the updated translation is
Sun, 08 Jan 2017 17:00:00 -0700.

Thanks in advance,

# SOME DESCRIPTIVE TITLE.
# Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER
# This file is distributed under the same license as the PACKAGE package.
# Atila KOÇ , 2012, 2014, 2016.
#
msgid ""
msgstr ""
"Project-Id-Version: postfix\n"
"Report-Msgid-Bugs-To: post...@packages.debian.org\n"
"POT-Creation-Date: 2016-12-30 20:42+\n"
"PO-Revision-Date: 2016-03-03 10:03+0200\n"
"Last-Translator: Atila KOÇ \n"
"Language-Team: Turkish \n"
"Language: tr\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: Poedit 1.5.4\n"

#. Type: boolean
#. Description
#: ../templates:1001
msgid "Add a 'mydomain' entry in main.cf for upgrade?"
msgstr "Yükseltme için main.cf dosyasına bir 'mydomain' girdisi eklensin mi?"

#. Type: boolean
#. Description
#: ../templates:1001
msgid ""
"Postfix version 2.3.3-2 and later require changes in main.cf. Specifically, "
"mydomain must be specified, since hostname(1) is not a fully qualified "
"domain name (FQDN)."
msgstr ""
"Postfix'in 2.3.3-2 ve sonraki sürümleri main.cf dosyasında değişiklikler "
"yapılmasını gerektirir. hostname(1) tam tanımlanmış alan adı (FQDN) "
"olmadığından 'mydomain' girdisi özellikle tanımlanmalıdır."

#. Type: boolean
#. Description
#: ../templates:1001
msgid ""
"Failure to fix this will result in a broken mailer. Decline this option to "
"abort the upgrade, giving you the opportunity to add this configuration "
"yourself. Accept this option to automatically set mydomain based on the FQDN "
"of the machine."
msgstr ""
"Bu sorunun giderilememesi çalışmayan bir posta sunucusu ile sonuçlanacaktır. "
"Bu seçeneği geri çevirip yükseltmeden vazgeçer ve bu yapılandırmayı elle "
"yürütürsünüz ya da bu seçeneği seçer ve 'mydomain' girdisinin bu makinenin "
"FQDN'sine göre belirlenmesine izin verirsiniz."

#. Type: boolean
#. Description
#: ../templates:2001
msgid "Set smtpd_relay_restrictions in main.cf for upgrade?"
msgstr ""
"Yükseltme için main.cf dosyasındaki 'smtpd_relay_restrictions' girdisi "
"ayarlansın mı?"

#. Type: boolean
#. Description
#: ../templates:2001
msgid ""
"Postfix version 2.10 adds smtpd_relay_restrictions, to separate relaying "
"restrictions from recipient restrictions, and you have a non-default value "
"for smtpd_recipient_restrictions."
msgstr ""
"Aktarım kısıtlamalarını alıcı kısıtlamalarından ayırmak için, Postfix 2.10 "
"sürümüne 'smtpd_relay_restrictions' girdisi eklenmiştir ve sizin girdiniz "
"öntanımlı değerden farklıdır."

#. Type: boolean
#. Description
#: ../templates:2001
msgid ""
"Failure to do this may result in deferred or bounced mail after the "
"upgrade.  Accept this option to set smtpd_relay_restrictions equal to "
"smtpd_recipient_restrictions."
msgstr ""
"'smtpd_relay_restrictions' girdisini 'smtpd_recipient_restrictions' girdisi "
"ile aynı yapmak için bu seçeneği kabul edin. Aksi durumda, yükseltme "
"sonrasında geciken ya da geri dönen postalar olabilir."

#. Type: boolean
#. Description
#: ../templates:3001
msgid "Update configuration to avoid compatibility warnings?"
msgstr ""

#. Type: boolean
#. Description
#: ../templates:3001
msgid ""
"This upgrade of postfix changes some default values in the configuration. As "
"part of this upgrade, the following will be changed: (1) chrooted components "
"will be changed from '-' to 'y' in master.cf, and (2) myhostname will be set "
"to a fully-qualified domain name if it is not already such.  The install "
"will be aborted if you do not allow the change."
msgstr ""

#. Type: boolean
#. Description
#: ../templates:4001
msgid "Update master.cf for merged lmtp/smtp binary?"
msgstr ""

#. Type: boolean
#. Description
#: ../templates:4001
#, fuzzy
#| msgid ""
#| "This upgrade of postfix changes where daemons are located, and your "
#| "postfix configuration explicitly specifies the old location.  The install "
#| "will be aborted if you do not allow the change."
msgid ""
"This upgrade of postfix drops the \"lmtp\" symlink, and your configuration "
"(master.cf) refers to it: lmtp was merged into smtp long ago.  The install "
"will be aborted if you do not allow the change."
msgstr ""
"Postfix'in bu yükseltmesi alan adlarının saklandığı konumu değiştiriyor ve "
"sizin Postfix yapılandırmanız eski konumu gösteriyor. 

REVISED: postfix 3.1.3-6: Please update debconf PO translation for the package postfix

[LaMont Jones]

Hi,

[Right after I sent the last email, review found that one more template
was needed.  Please do the translations based on this email, not the
earlier one.]

You are noted as the last translator of the debconf translation for
postfix. The English template has been changed, and now some messages
are marked "fuzzy" in your translation or are missing.
I would be grateful if you could take the time and update it.
Please send the updated file to me, or submit it as a wishlist bug
against postfix.

The deadline for receiving the updated translation is
Sun, 08 Jan 2017 17:00:00 -0700.

Thanks in advance,

# postfix debconf templates
# Copyright (C) 2007-2012 Tommi Vainikainen.
# This file is distributed under the same license as the package.
# Tommi Vainikainen , 2007-2012.
#
msgid ""
msgstr ""
"Project-Id-Version: postfix debconf templates\n"
"Report-Msgid-Bugs-To: post...@packages.debian.org\n"
"POT-Creation-Date: 2016-12-30 20:42+\n"
"PO-Revision-Date: 2012-06-05 11:43+0300\n"
"Last-Translator: Tommi Vainikainen \n"
"Language-Team: Finnish \n"
"Language: fi\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"

#. Type: boolean
#. Description
#: ../templates:1001
msgid "Add a 'mydomain' entry in main.cf for upgrade?"
msgstr "Lisää ”mydomain”-kenttä main.cf:ään päivitettäessä?"

#. Type: boolean
#. Description
#: ../templates:1001
msgid ""
"Postfix version 2.3.3-2 and later require changes in main.cf. Specifically, "
"mydomain must be specified, since hostname(1) is not a fully qualified "
"domain name (FQDN)."
msgstr ""
"Postfix versiosta 2.3.3-2 alkaen vaatii muutoksen main.cf:ään. Erityisesti "
"mydomain pitää määritellä, koska hostname(1) ei ole täydellinen "
"toimialuenimi (FQDN)."

#. Type: boolean
#. Description
#: ../templates:1001
msgid ""
"Failure to fix this will result in a broken mailer. Decline this option to "
"abort the upgrade, giving you the opportunity to add this configuration "
"yourself. Accept this option to automatically set mydomain based on the FQDN "
"of the machine."
msgstr ""
"Tämän korjaamisen epäonnistuessa postipalvelin ei toimi. Kieltäytymällä "
"tästä valinnasta keskeytyy päivitys, ja sinulle annetaan mahdollisuus lisätä "
"tämä asetus itse. Hyväksymällä tämän valinnan mydomain asetetaan "
"automaattisesti tämän tietokoneen FQDN:ksi."

#. Type: boolean
#. Description
#: ../templates:2001
#, fuzzy
#| msgid "Correct retry entry in master.cf for upgrade?"
msgid "Set smtpd_relay_restrictions in main.cf for upgrade?"
msgstr "Korjaa retry-tietue master.cf:ssä päivitettäessä?"

#. Type: boolean
#. Description
#: ../templates:2001
msgid ""
"Postfix version 2.10 adds smtpd_relay_restrictions, to separate relaying "
"restrictions from recipient restrictions, and you have a non-default value "
"for smtpd_recipient_restrictions."
msgstr ""

#. Type: boolean
#. Description
#: ../templates:2001
msgid ""
"Failure to do this may result in deferred or bounced mail after the "
"upgrade.  Accept this option to set smtpd_relay_restrictions equal to "
"smtpd_recipient_restrictions."
msgstr ""

#. Type: boolean
#. Description
#: ../templates:3001
msgid "Update configuration to avoid compatibility warnings?"
msgstr ""

#. Type: boolean
#. Description
#: ../templates:3001
msgid ""
"This upgrade of postfix changes some default values in the configuration. As "
"part of this upgrade, the following will be changed: (1) chrooted components "
"will be changed from '-' to 'y' in master.cf, and (2) myhostname will be set "
"to a fully-qualified domain name if it is not already such.  The install "
"will be aborted if you do not allow the change."
msgstr ""

#. Type: boolean
#. Description
#: ../templates:4001
msgid "Update master.cf for merged lmtp/smtp binary?"
msgstr ""

#. Type: boolean
#. Description
#: ../templates:4001
msgid ""
"This upgrade of postfix drops the \"lmtp\" symlink, and your configuration "
"(master.cf) refers to it: lmtp was merged into smtp long ago.  The install "
"will be aborted if you do not allow the change."
msgstr ""

#. Type: boolean
#. Description
#: ../templates:5001
msgid "Update main.cf for daemon_directory change?"
msgstr ""

#. Type: boolean
#. Description
#: ../templates:5001
msgid ""
"This upgrade of postfix changes where daemons are located, and your postfix "
"configuration explicitly specifies the old location.  The install will be "
"aborted if you do not allow the change."
msgstr ""

#. Type: boolean
#. Description
#: ../templates:6001
msgid "Update dynamicmaps.cf for 3.0?"
msgstr ""

#. Type: boolean
#. Description
#: ../templates:6001
#, fuzzy
#| msgid ""
#| "Postfix version 2.9 adds sqlite support to maps, but your dynamicmaps.cf "
#| "does not reflect that.  Accept this option to add support for sqlite maps."
msgid ""
"Postfix version 3.0 changes how dynamic maps are delivered, and your "
"dynamicmaps.cf does not reflect 

REVISED: postfix 3.1.3-6: Please update debconf PO translation for the package postfix

[LaMont Jones]

Hi,

[Right after I sent the last email, review found that one more template
was needed.  Please do the translations based on this email, not the
earlier one.]

You are noted as the last translator of the debconf translation for
postfix. The English template has been changed, and now some messages
are marked "fuzzy" in your translation or are missing.
I would be grateful if you could take the time and update it.
Please send the updated file to me, or submit it as a wishlist bug
against postfix.

The deadline for receiving the updated translation is
Sun, 08 Jan 2017 17:00:00 -0700.

Thanks in advance,

# Translation of postfix debconf templates to French
# Copyright (C) 2007  Michel Grentzinger 
# This file is distributed under the same license as the postfix package.
#
#
# Michel Grentzinger , 2007-2008.
# Christian Perrier , 2008, 2012, 2013, 2016.
msgid ""
msgstr ""
"Project-Id-Version: \n"
"Report-Msgid-Bugs-To: post...@packages.debian.org\n"
"POT-Creation-Date: 2016-12-30 20:42+\n"
"PO-Revision-Date: 2016-02-26 18:49+0100\n"
"Last-Translator: Christian Perrier \n"
"Language-Team: French \n"
"Language: fr\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: Lokalize 2.0\n"
"Plural-Forms: nplurals=2; plural=(n > 1);\n"

#. Type: boolean
#. Description
#: ../templates:1001
msgid "Add a 'mydomain' entry in main.cf for upgrade?"
msgstr ""
"Faut-il ajouter une entrée « mydomain » dans main.cf pour la mise à jour ?"

#. Type: boolean
#. Description
#: ../templates:1001
msgid ""
"Postfix version 2.3.3-2 and later require changes in main.cf. Specifically, "
"mydomain must be specified, since hostname(1) is not a fully qualified "
"domain name (FQDN)."
msgstr ""
"À partir de la version 2.3.3-2, Postfix nécessite des modifications du "
"fichier main.cf. En particulier, « mydomain » doit être indiqué puisque "
"hostname(1) n'est pas un nom de domaine complètement qualifié (FQDN)."

#. Type: boolean
#. Description
#: ../templates:1001
msgid ""
"Failure to fix this will result in a broken mailer. Decline this option to "
"abort the upgrade, giving you the opportunity to add this configuration "
"yourself. Accept this option to automatically set mydomain based on the FQDN "
"of the machine."
msgstr ""
"Si vous ne faites pas cette correction, le serveur de courriels ne "
"fonctionnera pas. Si vous refusez cette option, la mise à jour sera "
"interrompue, ce qui vous donnera la possibilité de faire vous-même cette "
"configuration. Choisissez cette option pour définir automatiquement "
"« mydomain » en fonction du nom de domaine complètement qualifié de la "
"machine."

#. Type: boolean
#. Description
#: ../templates:2001
msgid "Set smtpd_relay_restrictions in main.cf for upgrade?"
msgstr ""
"Faut-il établir des restrictions sur le relais SMTP dans le fichier master."
"cf à la mise à jour ?"

#. Type: boolean
#. Description
#: ../templates:2001
msgid ""
"Postfix version 2.10 adds smtpd_relay_restrictions, to separate relaying "
"restrictions from recipient restrictions, and you have a non-default value "
"for smtpd_recipient_restrictions."
msgstr ""
"La version 2.10 de Postfix met en œuvre des restrictions pour le relais SMTP "
"(« smtpd_relay_restrictions ») et sépare les restrictions de relais des "
"restrictions de destinataire (« recipient restrictions »). Or, la valeur de "
"« smtpd_recipient_restrictions » n'est actuellement pas la valeur par défaut."

#. Type: boolean
#. Description
#: ../templates:2001
msgid ""
"Failure to do this may result in deferred or bounced mail after the "
"upgrade.  Accept this option to set smtpd_relay_restrictions equal to "
"smtpd_recipient_restrictions."
msgstr ""
"Si vous ne choisissez pas cette option, il existe un risque que des "
"courriers soient différés ou rejetés après la mise à jour. En la "
"choisissant, la valeur de « smtpd_relay_restrictions » sera positionnée "
"comme égale à celle de « smtpd_recipient_restrictions »."

#. Type: boolean
#. Description
#: ../templates:3001
msgid "Update configuration to avoid compatibility warnings?"
msgstr ""

#. Type: boolean
#. Description
#: ../templates:3001
msgid ""
"This upgrade of postfix changes some default values in the configuration. As "
"part of this upgrade, the following will be changed: (1) chrooted components "
"will be changed from '-' to 'y' in master.cf, and (2) myhostname will be set "
"to a fully-qualified domain name if it is not already such.  The install "
"will be aborted if you do not allow the change."
msgstr ""

#. Type: boolean
#. Description
#: ../templates:4001
msgid "Update master.cf for merged lmtp/smtp binary?"
msgstr ""

#. Type: boolean
#. Description
#: ../templates:4001
#, fuzzy
#| msgid ""
#| "This upgrade of postfix changes where daemons are located, and your "
#| "postfix configuration explicitly specifies 

REVISED: postfix 3.1.3-6: Please update debconf PO translation for the package postfix

[LaMont Jones]

Hi,

[Right after I sent the last email, review found that one more template
was needed.  Please do the translations based on this email, not the
earlier one.]

You are noted as the last translator of the debconf translation for
postfix. The English template has been changed, and now some messages
are marked "fuzzy" in your translation or are missing.
I would be grateful if you could take the time and update it.
Please send the updated file to me, or submit it as a wishlist bug
against postfix.

The deadline for receiving the updated translation is
Sun, 08 Jan 2017 17:00:00 -0700.

Thanks in advance,

# Italian translation of the postfix debconf template
# This file is distributed under the same license as the postfix package
# Cristian Rigamonti , 2004, 2012.
# Dario , 2016.
msgid ""
msgstr ""
"Project-Id-Version: postfix 2.9.1-2\n"
"Report-Msgid-Bugs-To: post...@packages.debian.org\n"
"POT-Creation-Date: 2016-12-30 20:42+\n"
"PO-Revision-Date: 2016-03-04 23:04+0100\n"
"Last-Translator: Cristian Rigamonti \n"
"Language-Team: Italian \n"
"Language: it\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"

#. Type: boolean
#. Description
#: ../templates:1001
msgid "Add a 'mydomain' entry in main.cf for upgrade?"
msgstr "Aggiungere una voce «mydomain» a main.cf per l'aggiornamento?"

#. Type: boolean
#. Description
#: ../templates:1001
msgid ""
"Postfix version 2.3.3-2 and later require changes in main.cf. Specifically, "
"mydomain must be specified, since hostname(1) is not a fully qualified "
"domain name (FQDN)."
msgstr ""
"Postfix a partire dalla versione 2.3.3-2 richiede delle modifiche in main."
"cf. In particolare, mydomain deve essere specificato, visto che hostname(1) "
"non è un nome di dominio pienamente qualificato (FQDN)."

#. Type: boolean
#. Description
#: ../templates:1001
msgid ""
"Failure to fix this will result in a broken mailer. Decline this option to "
"abort the upgrade, giving you the opportunity to add this configuration "
"yourself. Accept this option to automatically set mydomain based on the FQDN "
"of the machine."
msgstr ""
"Se non si corregge questa impostazione, il programma sarà inutilizzabile. "
"Rifiutando questa proposta, l'aggiornamento verrà annullato e si potrà "
"eseguire manualmente la modifica alla configurazione. Accettando la proposta "
"il valore di mydomain sarà impostato automaticamente al FQDN del sistema."

#. Type: boolean
#. Description
#: ../templates:2001
msgid "Set smtpd_relay_restrictions in main.cf for upgrade?"
msgstr "Impostare smtpd_relay_restrictions nel main.cf per l'aggiornamento?"

#. Type: boolean
#. Description
#: ../templates:2001
msgid ""
"Postfix version 2.10 adds smtpd_relay_restrictions, to separate relaying "
"restrictions from recipient restrictions, and you have a non-default value "
"for smtpd_recipient_restrictions."
msgstr ""
"Postfix versione 2.10 aggiunge il parametro smtpd_relay_restrictions per "
"separare le restrizioni relative all'inoltro da quelle relative ai "
"destinatari, ed è impostato un valore non predefinito per "
"smtpd_recipient_restrictions."

#. Type: boolean
#. Description
#: ../templates:2001
msgid ""
"Failure to do this may result in deferred or bounced mail after the "
"upgrade.  Accept this option to set smtpd_relay_restrictions equal to "
"smtpd_recipient_restrictions."
msgstr ""
"Se questo non viene fatto, dopo l'aggiornamento si potrebbe avere posta in "
"ritardo o restituita. Accettare questa opzione per impostare il parametro "
"smtpd_recipient_restrictions uguale a smtpd_relay_restrictions."

#. Type: boolean
#. Description
#: ../templates:3001
msgid "Update configuration to avoid compatibility warnings?"
msgstr ""

#. Type: boolean
#. Description
#: ../templates:3001
msgid ""
"This upgrade of postfix changes some default values in the configuration. As "
"part of this upgrade, the following will be changed: (1) chrooted components "
"will be changed from '-' to 'y' in master.cf, and (2) myhostname will be set "
"to a fully-qualified domain name if it is not already such.  The install "
"will be aborted if you do not allow the change."
msgstr ""

#. Type: boolean
#. Description
#: ../templates:4001
msgid "Update master.cf for merged lmtp/smtp binary?"
msgstr ""

#. Type: boolean
#. Description
#: ../templates:4001
msgid ""
"This upgrade of postfix drops the \"lmtp\" symlink, and your configuration "
"(master.cf) refers to it: lmtp was merged into smtp long ago.  The install "
"will be aborted if you do not allow the change."
msgstr ""

#. Type: boolean
#. Description
#: ../templates:5001
msgid "Update main.cf for daemon_directory change?"
msgstr ""

#. Type: boolean
#. Description
#: ../templates:5001
msgid ""
"This upgrade of postfix changes where daemons are located, and your postfix "
"configuration explicitly specifies the old location.  The install will 

postfix 3.1.3-6: Please update debconf PO translation for the package postfix

[LaMont Jones]

Hi,

You are noted as the last translator of the debconf translation for
postfix. The English template has been changed, and now some messages
are marked "fuzzy" in your translation or are missing.
I would be grateful if you could take the time and update it.
Please send the updated file to me, or submit it as a wishlist bug
against postfix.

The deadline for receiving the updated translation is
Sun, 08 Jan 2017 17:00:00 -0700.

Thanks in advance,
lamont

#
# Catalan translation for postfix package.
# Copyright (C) 2012 LaMont Jones.
# This file is distributed under the same license as the postfix package.
#
# Jordà Polo <jo...@ettin.org>, 2006, 2007, 2008, 2012.
#
msgid ""
msgstr ""
"Project-Id-Version: 2.9.1-5\n"
"Report-Msgid-Bugs-To: post...@packages.debian.org\n"
"POT-Creation-Date: 2016-07-29 01:18-0400\n"
"PO-Revision-Date: 2012-06-03 09:34+0200\n"
"Last-Translator: Jordà Polo <jo...@ettin.org>\n"
"Language-Team: Catalan <debian-l10n-catalan@lists.debian.org>\n"
"Language: ca\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"

#. Type: boolean
#. Description
#: ../templates:1001
msgid "Add a 'mydomain' entry in main.cf for upgrade?"
msgstr ""
"Voleu afegir l'entrada «mydomain» al fitxer main.cf per a l'actualització?"

#. Type: boolean
#. Description
#: ../templates:1001
msgid ""
"Postfix version 2.3.3-2 and later require changes in main.cf. Specifically, "
"mydomain must be specified, since hostname(1) is not a fully qualified "
"domain name (FQDN)."
msgstr ""
"A partir de la versió 2.3.3-2 de Postfix es requereixen canvis a main.cf. "
"Més concretament, s'ha d'especificar «mydomain», ja que hostname(2) no és un "
"nom de domini completament qualificat (FQDN)."

#. Type: boolean
#. Description
#: ../templates:1001
msgid ""
"Failure to fix this will result in a broken mailer. Decline this option to "
"abort the upgrade, giving you the opportunity to add this configuration "
"yourself. Accept this option to automatically set mydomain based on the FQDN "
"of the machine."
msgstr ""
"Si es produeix una fallada en aquest punt, el funcionament de "
"l'administrador de correu pot veure's interromput. Declineu aquesta opció si "
"voleu avortar l'actualització i afegir aquesta configuració manualment. "
"Accepteu si preferiu que s'estableixi «mydomain» automàticament a partir de "
"l'FQDN de la màquina."

#. Type: boolean
#. Description
#: ../templates:2001
#, fuzzy
#| msgid "Correct retry entry in master.cf for upgrade?"
msgid "Set smtpd_relay_restrictions in main.cf for upgrade?"
msgstr ""
"Voleu esmenar l'entrada «retry» al fitxer master.cf per a l'actualització?"

#. Type: boolean
#. Description
#: ../templates:2001
msgid ""
"Postfix version 2.10 adds smtpd_relay_restrictions, to separate relaying "
"restrictions from recipient restrictions, and you have a non-default value "
"for smtpd_recipient_restrictions."
msgstr ""

#. Type: boolean
#. Description
#: ../templates:2001
msgid ""
"Failure to do this may result in deferred or bounced mail after the "
"upgrade.  Accept this option to set smtpd_relay_restrictions equal to "
"smtpd_recipient_restrictions."
msgstr ""

#. Type: boolean
#. Description
#: ../templates:3001
msgid "Update configuration to avoid compatibility warnings"
msgstr ""

#. Type: boolean
#. Description
#: ../templates:3001
msgid ""
"This upgrade of postfix changes some default values in the configuration. As "
"part of this upgrade, the following will be changed: (1) chrooted components "
"will be changed from '-' to 'y' in master.cf, and (2) myhostname will be set "
"to a fully-qualified domain name if it is not already such.  The install "
"will be aborted if you do not allow the change."
msgstr ""

#. Type: boolean
#. Description
#: ../templates:4001
msgid "Update main.cf for daemon_directory change"
msgstr ""

#. Type: boolean
#. Description
#: ../templates:4001
msgid ""
"This upgrade of postfix changes where daemons are located, and your postfix "
"configuration explicitly specifies the old location.  The install will be "
"aborted if you do not allow the change."
msgstr ""

#. Type: boolean
#. Description
#: ../templates:5001
#, fuzzy
#| msgid "Correct dynamicmaps.cf for upgrade?"
msgid "Update dynamicmaps.cf for 3.0"
msgstr "Voleu esmenar dynam

postfix 3.1.3-6: Please update debconf PO translation for the package postfix

[LaMont Jones]

Hi,

You are noted as the last translator of the debconf translation for
postfix. The English template has been changed, and now some messages
are marked "fuzzy" in your translation or are missing.
I would be grateful if you could take the time and update it.
Please send the updated file to me, or submit it as a wishlist bug
against postfix.

The deadline for receiving the updated translation is
Sun, 08 Jan 2017 17:00:00 -0700.

Thanks in advance,
lamont

# Translation of Postfix PO file to Russian
# Yuriy Talakan' , 2005.
# Yuriy Talakan' , 2007.
# Vladimir Zhbanov , 2012.
# Sergey Alyoshin , 2007, 2008, 2013, 2016.
#
msgid ""
msgstr ""
"Project-Id-Version: postfix_3.0.3-2_ru\n"
"Report-Msgid-Bugs-To: post...@packages.debian.org\n"
"POT-Creation-Date: 2016-07-29 01:18-0400\n"
"PO-Revision-Date: 2016-02-22 21:20+0300\n"
"Last-Translator: Sergey Alyoshin \n"
"Language-Team: Russian \n"
"Language: ru\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms:  nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"

#. Type: boolean
#. Description
#: ../templates:1001
msgid "Add a 'mydomain' entry in main.cf for upgrade?"
msgstr "Добавить запись 'mydomain' в main.cf для обновления?"

#. Type: boolean
#. Description
#: ../templates:1001
msgid ""
"Postfix version 2.3.3-2 and later require changes in main.cf. Specifically, "
"mydomain must be specified, since hostname(1) is not a fully qualified "
"domain name (FQDN)."
msgstr ""
"Для Postfix версии 2.3.3-2 и выше требуются изменения в main.cf. А именно, "
"необходимо задать mydomain, поскольку hostname(1) не является полностью "
"определённым именем домена (FQDN)."

#. Type: boolean
#. Description
#: ../templates:1001
msgid ""
"Failure to fix this will result in a broken mailer. Decline this option to "
"abort the upgrade, giving you the opportunity to add this configuration "
"yourself. Accept this option to automatically set mydomain based on the FQDN "
"of the machine."
msgstr ""
"При невозможности исправления почтовая программа окажется неработоспособной. "
"В случае отказа обновление будет прервано, что даст вам возможность добавить "
"эту настройку самостоятельно. В случае согласия mydomain будет определён по "
"FQDN машины и установлен автоматически."

#. Type: boolean
#. Description
#: ../templates:2001
msgid "Set smtpd_relay_restrictions in main.cf for upgrade?"
msgstr "Задать запись 'smtpd_relay_restriction' в master.cf для обновления?"

#. Type: boolean
#. Description
#: ../templates:2001
msgid ""
"Postfix version 2.10 adds smtpd_relay_restrictions, to separate relaying "
"restrictions from recipient restrictions, and you have a non-default value "
"for smtpd_recipient_restrictions."
msgstr ""
"В Postfix версии 2.10 добавлена запись smtpd_relay_restrictions, для "
"разделения ограничений ретрансляции (smtpd_relay_restrictions) и ограничений "
"получателя (smtpd_recipient_restrictions). Ваше значение "
"smtpd_recipient_restrictions не является значением по умолчанию."

#. Type: boolean
#. Description
#: ../templates:2001
msgid ""
"Failure to do this may result in deferred or bounced mail after the "
"upgrade.  Accept this option to set smtpd_relay_restrictions equal to "
"smtpd_recipient_restrictions."
msgstr ""
"Невозможность выполнения этого может привести к задержке или возвращению "
"писем после обновления. В случае согласия будет задана запись "
"'smtpd_relay_restrictions' эквивалентная 'smtpd_recipient_restrictions'."

#. Type: boolean
#. Description
#: ../templates:3001
msgid "Update configuration to avoid compatibility warnings"
msgstr ""

#. Type: boolean
#. Description
#: ../templates:3001
msgid ""
"This upgrade of postfix changes some default values in the configuration. As "
"part of this upgrade, the following will be changed: (1) chrooted components "
"will be changed from '-' to 'y' in master.cf, and (2) myhostname will be set "
"to a fully-qualified domain name if it is not already such.  The install "
"will be aborted if you do not allow the change."
msgstr ""

#. Type: boolean
#. Description
#: ../templates:4001
msgid "Update main.cf for daemon_directory change"
msgstr ""

#. Type: boolean
#. Description
#: ../templates:4001
msgid ""
"This upgrade of postfix changes where daemons are located, and your postfix "
"configuration explicitly specifies the old location.  The install will be "
"aborted if you do not allow the change."
msgstr ""

#. Type: boolean
#. Description
#: ../templates:5001
msgid "Update dynamicmaps.cf for 3.0"
msgstr "Обновить dynamicmaps.cf для версии 3.0"

#. Type: boolean
#. Description
#: ../templates:5001
msgid ""
"Postfix version 3.0 changes how dynamic maps are delivered, and your "
"dynamicmaps.cf does not reflect that.  Accept this option to convert "

postfix 3.1.3-6: Please update debconf PO translation for the package postfix

[LaMont Jones]

Hi,

You are noted as the last translator of the debconf translation for
postfix. The English template has been changed, and now some messages
are marked "fuzzy" in your translation or are missing.
I would be grateful if you could take the time and update it.
Please send the updated file to me, or submit it as a wishlist bug
against postfix.

The deadline for receiving the updated translation is
Sun, 08 Jan 2017 17:00:00 -0700.

Thanks in advance,
lamont

# SOME DESCRIPTIVE TITLE.
# Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER
# This file is distributed under the same license as the PACKAGE package.
# Atila KOÇ , 2012, 2014, 2016.
#
msgid ""
msgstr ""
"Project-Id-Version: postfix\n"
"Report-Msgid-Bugs-To: post...@packages.debian.org\n"
"POT-Creation-Date: 2016-07-29 01:18-0400\n"
"PO-Revision-Date: 2016-03-03 10:03+0200\n"
"Last-Translator: Atila KOÇ \n"
"Language-Team: Turkish \n"
"Language: tr\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: Poedit 1.5.4\n"

#. Type: boolean
#. Description
#: ../templates:1001
msgid "Add a 'mydomain' entry in main.cf for upgrade?"
msgstr "Yükseltme için main.cf dosyasına bir 'mydomain' girdisi eklensin mi?"

#. Type: boolean
#. Description
#: ../templates:1001
msgid ""
"Postfix version 2.3.3-2 and later require changes in main.cf. Specifically, "
"mydomain must be specified, since hostname(1) is not a fully qualified "
"domain name (FQDN)."
msgstr ""
"Postfix'in 2.3.3-2 ve sonraki sürümleri main.cf dosyasında değişiklikler "
"yapılmasını gerektirir. hostname(1) tam tanımlanmış alan adı (FQDN) "
"olmadığından 'mydomain' girdisi özellikle tanımlanmalıdır."

#. Type: boolean
#. Description
#: ../templates:1001
msgid ""
"Failure to fix this will result in a broken mailer. Decline this option to "
"abort the upgrade, giving you the opportunity to add this configuration "
"yourself. Accept this option to automatically set mydomain based on the FQDN "
"of the machine."
msgstr ""
"Bu sorunun giderilememesi çalışmayan bir posta sunucusu ile sonuçlanacaktır. "
"Bu seçeneği geri çevirip yükseltmeden vazgeçer ve bu yapılandırmayı elle "
"yürütürsünüz ya da bu seçeneği seçer ve 'mydomain' girdisinin bu makinenin "
"FQDN'sine göre belirlenmesine izin verirsiniz."

#. Type: boolean
#. Description
#: ../templates:2001
msgid "Set smtpd_relay_restrictions in main.cf for upgrade?"
msgstr ""
"Yükseltme için main.cf dosyasındaki 'smtpd_relay_restrictions' girdisi "
"ayarlansın mı?"

#. Type: boolean
#. Description
#: ../templates:2001
msgid ""
"Postfix version 2.10 adds smtpd_relay_restrictions, to separate relaying "
"restrictions from recipient restrictions, and you have a non-default value "
"for smtpd_recipient_restrictions."
msgstr ""
"Aktarım kısıtlamalarını alıcı kısıtlamalarından ayırmak için, Postfix 2.10 "
"sürümüne 'smtpd_relay_restrictions' girdisi eklenmiştir ve sizin girdiniz "
"öntanımlı değerden farklıdır."

#. Type: boolean
#. Description
#: ../templates:2001
msgid ""
"Failure to do this may result in deferred or bounced mail after the "
"upgrade.  Accept this option to set smtpd_relay_restrictions equal to "
"smtpd_recipient_restrictions."
msgstr ""
"'smtpd_relay_restrictions' girdisini 'smtpd_recipient_restrictions' girdisi "
"ile aynı yapmak için bu seçeneği kabul edin. Aksi durumda, yükseltme "
"sonrasında geciken ya da geri dönen postalar olabilir."

#. Type: boolean
#. Description
#: ../templates:3001
msgid "Update configuration to avoid compatibility warnings"
msgstr ""

#. Type: boolean
#. Description
#: ../templates:3001
msgid ""
"This upgrade of postfix changes some default values in the configuration. As "
"part of this upgrade, the following will be changed: (1) chrooted components "
"will be changed from '-' to 'y' in master.cf, and (2) myhostname will be set "
"to a fully-qualified domain name if it is not already such.  The install "
"will be aborted if you do not allow the change."
msgstr ""

#. Type: boolean
#. Description
#: ../templates:4001
msgid "Update main.cf for daemon_directory change"
msgstr ""
"main.cf dosyası 'daemon_directory' girdisi değişikliği için güncellensin mi?"

#. Type: boolean
#. Description
#: ../templates:4001
msgid ""
"This upgrade of postfix changes where daemons are located, and your postfix "
"configuration explicitly specifies the old location.  The install will be "
"aborted if you do not allow the change."
msgstr ""
"Postfix'in bu yükseltmesi alan adlarının saklandığı konumu değiştiriyor ve "
"sizin Postfix yapılandırmanız eski konumu gösteriyor. Değişikliğe izin "
"vermezseniz, kurulumdan çıkılacaktır."

#. Type: boolean
#. Description
#: ../templates:5001
msgid "Update dynamicmaps.cf for 3.0"
msgstr "dynamicmaps.cf dosyası 3.0 sürümü için güncellensin mi?"

#. Type: boolean
#. Description
#: ../templates:5001
msgid ""
"Postfix version 3.0 changes how dynamic 

postfix 3.1.3-6: Please update debconf PO translation for the package postfix

[LaMont Jones]

Hi,

You are noted as the last translator of the debconf translation for
postfix. The English template has been changed, and now some messages
are marked "fuzzy" in your translation or are missing.
I would be grateful if you could take the time and update it.
Please send the updated file to me, or submit it as a wishlist bug
against postfix.

The deadline for receiving the updated translation is
Sun, 08 Jan 2017 17:00:00 -0700.

Thanks in advance,
lamont

# Italian translation of the postfix debconf template
# This file is distributed under the same license as the postfix package
# Cristian Rigamonti , 2004, 2012.
# Dario , 2016.
msgid ""
msgstr ""
"Project-Id-Version: postfix 2.9.1-2\n"
"Report-Msgid-Bugs-To: post...@packages.debian.org\n"
"POT-Creation-Date: 2016-07-29 01:18-0400\n"
"PO-Revision-Date: 2016-03-04 23:04+0100\n"
"Last-Translator: Cristian Rigamonti \n"
"Language-Team: Italian \n"
"Language: it\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"

#. Type: boolean
#. Description
#: ../templates:1001
msgid "Add a 'mydomain' entry in main.cf for upgrade?"
msgstr "Aggiungere una voce «mydomain» a main.cf per l'aggiornamento?"

#. Type: boolean
#. Description
#: ../templates:1001
msgid ""
"Postfix version 2.3.3-2 and later require changes in main.cf. Specifically, "
"mydomain must be specified, since hostname(1) is not a fully qualified "
"domain name (FQDN)."
msgstr ""
"Postfix a partire dalla versione 2.3.3-2 richiede delle modifiche in main."
"cf. In particolare, mydomain deve essere specificato, visto che hostname(1) "
"non è un nome di dominio pienamente qualificato (FQDN)."

#. Type: boolean
#. Description
#: ../templates:1001
msgid ""
"Failure to fix this will result in a broken mailer. Decline this option to "
"abort the upgrade, giving you the opportunity to add this configuration "
"yourself. Accept this option to automatically set mydomain based on the FQDN "
"of the machine."
msgstr ""
"Se non si corregge questa impostazione, il programma sarà inutilizzabile. "
"Rifiutando questa proposta, l'aggiornamento verrà annullato e si potrà "
"eseguire manualmente la modifica alla configurazione. Accettando la proposta "
"il valore di mydomain sarà impostato automaticamente al FQDN del sistema."

#. Type: boolean
#. Description
#: ../templates:2001
msgid "Set smtpd_relay_restrictions in main.cf for upgrade?"
msgstr "Impostare smtpd_relay_restrictions nel main.cf per l'aggiornamento?"

#. Type: boolean
#. Description
#: ../templates:2001
msgid ""
"Postfix version 2.10 adds smtpd_relay_restrictions, to separate relaying "
"restrictions from recipient restrictions, and you have a non-default value "
"for smtpd_recipient_restrictions."
msgstr ""
"Postfix versione 2.10 aggiunge il parametro smtpd_relay_restrictions per "
"separare le restrizioni relative all'inoltro da quelle relative ai "
"destinatari, ed è impostato un valore non predefinito per "
"smtpd_recipient_restrictions."

#. Type: boolean
#. Description
#: ../templates:2001
msgid ""
"Failure to do this may result in deferred or bounced mail after the "
"upgrade.  Accept this option to set smtpd_relay_restrictions equal to "
"smtpd_recipient_restrictions."
msgstr ""
"Se questo non viene fatto, dopo l'aggiornamento si potrebbe avere posta in "
"ritardo o restituita. Accettare questa opzione per impostare il parametro "
"smtpd_recipient_restrictions uguale a smtpd_relay_restrictions."

#. Type: boolean
#. Description
#: ../templates:3001
msgid "Update configuration to avoid compatibility warnings"
msgstr ""

#. Type: boolean
#. Description
#: ../templates:3001
msgid ""
"This upgrade of postfix changes some default values in the configuration. As "
"part of this upgrade, the following will be changed: (1) chrooted components "
"will be changed from '-' to 'y' in master.cf, and (2) myhostname will be set "
"to a fully-qualified domain name if it is not already such.  The install "
"will be aborted if you do not allow the change."
msgstr ""

#. Type: boolean
#. Description
#: ../templates:4001
msgid "Update main.cf for daemon_directory change"
msgstr ""

#. Type: boolean
#. Description
#: ../templates:4001
msgid ""
"This upgrade of postfix changes where daemons are located, and your postfix "
"configuration explicitly specifies the old location.  The install will be "
"aborted if you do not allow the change."
msgstr ""

#. Type: boolean
#. Description
#: ../templates:5001
msgid "Update dynamicmaps.cf for 3.0"
msgstr "Aggiornamento dynamicmaps.cf per 3.0"

#. Type: boolean
#. Description
#: ../templates:5001
msgid ""
"Postfix version 3.0 changes how dynamic maps are delivered, and your "
"dynamicmaps.cf does not reflect that.  Accept this option to convert "
"dynamicmaps.cf to the version required for 3.0."
msgstr ""
"Postfix versione 3.0 cambia il modo in cui le mappe dinamiche vengono "
"recapitate, 

postfix 3.1.3-6: Please update debconf PO translation for the package postfix

[LaMont Jones]

Hi,

You are noted as the last translator of the debconf translation for
postfix. The English template has been changed, and now some messages
are marked "fuzzy" in your translation or are missing.
I would be grateful if you could take the time and update it.
Please send the updated file to me, or submit it as a wishlist bug
against postfix.

The deadline for receiving the updated translation is
Sun, 08 Jan 2017 17:00:00 -0700.

Thanks in advance,
lamont

# Translation of postfix debconf templates to French
# Copyright (C) 2007  Michel Grentzinger 
# This file is distributed under the same license as the postfix package.
#
#
# Michel Grentzinger , 2007-2008.
# Christian Perrier , 2008, 2012, 2013, 2016.
msgid ""
msgstr ""
"Project-Id-Version: \n"
"Report-Msgid-Bugs-To: post...@packages.debian.org\n"
"POT-Creation-Date: 2016-07-29 01:18-0400\n"
"PO-Revision-Date: 2016-02-26 18:49+0100\n"
"Last-Translator: Christian Perrier \n"
"Language-Team: French \n"
"Language: fr\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: Lokalize 2.0\n"
"Plural-Forms: nplurals=2; plural=(n > 1);\n"

#. Type: boolean
#. Description
#: ../templates:1001
msgid "Add a 'mydomain' entry in main.cf for upgrade?"
msgstr ""
"Faut-il ajouter une entrée « mydomain » dans main.cf pour la mise à jour ?"

#. Type: boolean
#. Description
#: ../templates:1001
msgid ""
"Postfix version 2.3.3-2 and later require changes in main.cf. Specifically, "
"mydomain must be specified, since hostname(1) is not a fully qualified "
"domain name (FQDN)."
msgstr ""
"À partir de la version 2.3.3-2, Postfix nécessite des modifications du "
"fichier main.cf. En particulier, « mydomain » doit être indiqué puisque "
"hostname(1) n'est pas un nom de domaine complètement qualifié (FQDN)."

#. Type: boolean
#. Description
#: ../templates:1001
msgid ""
"Failure to fix this will result in a broken mailer. Decline this option to "
"abort the upgrade, giving you the opportunity to add this configuration "
"yourself. Accept this option to automatically set mydomain based on the FQDN "
"of the machine."
msgstr ""
"Si vous ne faites pas cette correction, le serveur de courriels ne "
"fonctionnera pas. Si vous refusez cette option, la mise à jour sera "
"interrompue, ce qui vous donnera la possibilité de faire vous-même cette "
"configuration. Choisissez cette option pour définir automatiquement "
"« mydomain » en fonction du nom de domaine complètement qualifié de la "
"machine."

#. Type: boolean
#. Description
#: ../templates:2001
msgid "Set smtpd_relay_restrictions in main.cf for upgrade?"
msgstr ""
"Faut-il établir des restrictions sur le relais SMTP dans le fichier master."
"cf à la mise à jour ?"

#. Type: boolean
#. Description
#: ../templates:2001
msgid ""
"Postfix version 2.10 adds smtpd_relay_restrictions, to separate relaying "
"restrictions from recipient restrictions, and you have a non-default value "
"for smtpd_recipient_restrictions."
msgstr ""
"La version 2.10 de Postfix met en œuvre des restrictions pour le relais SMTP "
"(« smtpd_relay_restrictions ») et sépare les restrictions de relais des "
"restrictions de destinataire (« recipient restrictions »). Or, la valeur de "
"« smtpd_recipient_restrictions » n'est actuellement pas la valeur par défaut."

#. Type: boolean
#. Description
#: ../templates:2001
msgid ""
"Failure to do this may result in deferred or bounced mail after the "
"upgrade.  Accept this option to set smtpd_relay_restrictions equal to "
"smtpd_recipient_restrictions."
msgstr ""
"Si vous ne choisissez pas cette option, il existe un risque que des "
"courriers soient différés ou rejetés après la mise à jour. En la "
"choisissant, la valeur de « smtpd_relay_restrictions » sera positionnée "
"comme égale à celle de « smtpd_recipient_restrictions »."

#. Type: boolean
#. Description
#: ../templates:3001
msgid "Update configuration to avoid compatibility warnings"
msgstr ""

#. Type: boolean
#. Description
#: ../templates:3001
msgid ""
"This upgrade of postfix changes some default values in the configuration. As "
"part of this upgrade, the following will be changed: (1) chrooted components "
"will be changed from '-' to 'y' in master.cf, and (2) myhostname will be set "
"to a fully-qualified domain name if it is not already such.  The install "
"will be aborted if you do not allow the change."
msgstr ""

#. Type: boolean
#. Description
#: ../templates:4001
msgid "Update main.cf for daemon_directory change"
msgstr "Mise à jour de main.cf pour modifier « daemon_directory » ?"

#. Type: boolean
#. Description
#: ../templates:4001
msgid ""
"This upgrade of postfix changes where daemons are located, and your postfix "
"configuration explicitly specifies the old location.  The install will be "
"aborted if you do not allow the change."
msgstr ""
"Lors de cette 

postfix 3.1.3-6: Please update debconf PO translation for the package postfix

[LaMont Jones]

Hi,

You are noted as the last translator of the debconf translation for
postfix. The English template has been changed, and now some messages
are marked "fuzzy" in your translation or are missing.
I would be grateful if you could take the time and update it.
Please send the updated file to me, or submit it as a wishlist bug
against postfix.

The deadline for receiving the updated translation is
Sun, 08 Jan 2017 17:00:00 -0700.

Thanks in advance,
lamont

# Brazilian Portuguese translation of postfix.
# Copyright (C) 2016 THE postfix'S COPYRIGHT HOLDER
# This file is distributed under the same license as the postfix package.
# André Luís Lopes , -2004.
# Marcelo Gomes de Santana , 2013-2016.
#
msgid ""
msgstr ""
"Project-Id-Version: postfix 3.0.4-3\n"
"Report-Msgid-Bugs-To: post...@packages.debian.org\n"
"POT-Creation-Date: 2016-07-29 01:18-0400\n"
"PO-Revision-Date: 2016-02-27 02:28-0300\n"
"Last-Translator: Marcelo Gomes de Santana \n"
"Language-Team: Brazilian Portuguese \n"
"Language: pt_BR\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"

#. Type: boolean
#. Description
#: ../templates:1001
msgid "Add a 'mydomain' entry in main.cf for upgrade?"
msgstr "Adicionar uma entrada \"mydomain\" ao main.cf para atualização?"

#. Type: boolean
#. Description
#: ../templates:1001
msgid ""
"Postfix version 2.3.3-2 and later require changes in main.cf. Specifically, "
"mydomain must be specified, since hostname(1) is not a fully qualified "
"domain name (FQDN)."
msgstr ""
"A versão 2.3.3-2 e posterior do Postfix requer mudanças no main.cf. "
"Especificamente, o mydomain deve ser definido, uma vez que o hostname(1) não "
"é um nome de domínio completamente qualificado (FQDN)."

#. Type: boolean
#. Description
#: ../templates:1001
msgid ""
"Failure to fix this will result in a broken mailer. Decline this option to "
"abort the upgrade, giving you the opportunity to add this configuration "
"yourself. Accept this option to automatically set mydomain based on the FQDN "
"of the machine."
msgstr ""
"Caso isso não seja corrigido, resultará em um servidor de e-mail quebrado. "
"Não aceite esta opção para cancelar a atualização, o que lhe dará a "
"oportunidade de adicionar a configuração manualmente. Aceite esta opção para "
"definir automaticamente o mydomain baseado no nome de domínio completamente "
"qualificado (FQDN) da máquina."

#. Type: boolean
#. Description
#: ../templates:2001
msgid "Set smtpd_relay_restrictions in main.cf for upgrade?"
msgstr "Definir smtpd_relay_restrictions no main.cf para atualização?"

#. Type: boolean
#. Description
#: ../templates:2001
msgid ""
"Postfix version 2.10 adds smtpd_relay_restrictions, to separate relaying "
"restrictions from recipient restrictions, and you have a non-default value "
"for smtpd_recipient_restrictions."
msgstr ""
"A versão 2.10 do Postfix adiciona smtpd_relay_restrictions, para separar as "
"restrições de retransmissão das restrições de destinatário, e você tem um "
"valor fora do padrão para smtpd_recipient_restrictions."

#. Type: boolean
#. Description
#: ../templates:2001
msgid ""
"Failure to do this may result in deferred or bounced mail after the "
"upgrade.  Accept this option to set smtpd_relay_restrictions equal to "
"smtpd_recipient_restrictions."
msgstr ""
"Caso isto falhe, pode resultar em mensagem deferida ou devolvida após a "
"atualização. Aceite esta opção para definir smtpd_relay_restrictions igual a "
"smtpd_recipient_restrictions."

#. Type: boolean
#. Description
#: ../templates:3001
msgid "Update configuration to avoid compatibility warnings"
msgstr ""

#. Type: boolean
#. Description
#: ../templates:3001
msgid ""
"This upgrade of postfix changes some default values in the configuration. As "
"part of this upgrade, the following will be changed: (1) chrooted components "
"will be changed from '-' to 'y' in master.cf, and (2) myhostname will be set "
"to a fully-qualified domain name if it is not already such.  The install "
"will be aborted if you do not allow the change."
msgstr ""

#. Type: boolean
#. Description
#: ../templates:4001
msgid "Update main.cf for daemon_directory change"
msgstr "Atualizar o main.cf para a mudança daemon_directory?"

#. Type: boolean
#. Description
#: ../templates:4001
msgid ""
"This upgrade of postfix changes where daemons are located, and your postfix "
"configuration explicitly specifies the old location.  The install will be "
"aborted if you do not allow the change."
msgstr ""
"Esta atualização do postfix muda a localização dos daemons, e sua "
"configuração do postfix especifica explicitamente a antiga localização. A "
"instalação será cancelada caso você não permita a mudança."

#. Type: boolean
#. Description
#: ../templates:5001
msgid "Update dynamicmaps.cf for 3.0"
msgstr "Atualizar o dynamicmaps.cf para 3.0?"

#. Type: boolean

postfix 3.1.3-6: Please update debconf PO translation for the package postfix

[LaMont Jones]

Hi,

You are noted as the last translator of the debconf translation for
postfix. The English template has been changed, and now some messages
are marked "fuzzy" in your translation or are missing.
I would be grateful if you could take the time and update it.
Please send the updated file to me, or submit it as a wishlist bug
against postfix.

The deadline for receiving the updated translation is
Sun, 08 Jan 2017 17:00:00 -0700.

Thanks in advance,
lamont

# Translation of postfix debconf templates to German
# Copyright (C) Helge Kreutzmann , 2006-2008, 2012, 2014, 2016.
# This file is distributed under the same license as the postfix package.
#
msgid ""
msgstr ""
"Project-Id-Version: postfix 3.0.3-2\n"
"Report-Msgid-Bugs-To: post...@packages.debian.org\n"
"POT-Creation-Date: 2016-07-29 01:18-0400\n"
"PO-Revision-Date: 2016-02-27 10:56+0100\n"
"Last-Translator: Helge Kreutzmann \n"
"Language-Team: de \n"
"Language: de\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=iso-8859-15\n"
"Content-Transfer-Encoding: 8bit\n"

#. Type: boolean
#. Description
#: ../templates:1001
msgid "Add a 'mydomain' entry in main.cf for upgrade?"
msgstr "Einen »mydomain«-Eintrag in main.cf beim Upgrade hinzufügen?"

#. Type: boolean
#. Description
#: ../templates:1001
msgid ""
"Postfix version 2.3.3-2 and later require changes in main.cf. Specifically, "
"mydomain must be specified, since hostname(1) is not a fully qualified "
"domain name (FQDN)."
msgstr ""
"Postfix, Version 2.3.3-2 und neuer, benötigt Änderungen in der main.cf. "
"Insbesondere muss »mydomain« angegeben werden, da hostname(1) kein voll-"
"qualifizierter Domain-Name (FQDN) ist."

#. Type: boolean
#. Description
#: ../templates:1001
msgid ""
"Failure to fix this will result in a broken mailer. Decline this option to "
"abort the upgrade, giving you the opportunity to add this configuration "
"yourself. Accept this option to automatically set mydomain based on the FQDN "
"of the machine."
msgstr ""
"Wenn Sie dies nicht korrigieren, wird Ihr E-Mail-Server unbrauchbar. "
"Verneinen Sie, um das Upgrade abzubrechen und diese Änderung selbst "
"vorzunehmen. Akzeptieren Sie, um, basierend auf dem FQDN, mydomain "
"automatisch zu setzen."

#. Type: boolean
#. Description
#: ../templates:2001
msgid "Set smtpd_relay_restrictions in main.cf for upgrade?"
msgstr "smtpd_relay_restrictions in main.cf für das Upgrade setzen?"

#. Type: boolean
#. Description
#: ../templates:2001
msgid ""
"Postfix version 2.10 adds smtpd_relay_restrictions, to separate relaying "
"restrictions from recipient restrictions, and you have a non-default value "
"for smtpd_recipient_restrictions."
msgstr ""
"Postfix Version 2.10 fügt smtpd_relay_restrictions hinzu, um Weiterleitungs-"
"von Empfänger-Beschränkungen zu trennen. Bei Ihnen liegt eine von der "
"Vorgabe abweichende smtpd_recipient_restrictions vor."

#. Type: boolean
#. Description
#: ../templates:2001
msgid ""
"Failure to do this may result in deferred or bounced mail after the "
"upgrade.  Accept this option to set smtpd_relay_restrictions equal to "
"smtpd_recipient_restrictions."
msgstr ""
"Wird dies nicht vorgenommen, kann nach dem Upgrade E-Mail verzögert oder "
"abgelehnt (»bounced«) werden. Aktzeptieren Sie diese Option, um "
"smtpd_relay_restrictions identisch zu smtpd_recipient_restrictions zu setzen."

#. Type: boolean
#. Description
#: ../templates:3001
msgid "Update configuration to avoid compatibility warnings"
msgstr ""

#. Type: boolean
#. Description
#: ../templates:3001
msgid ""
"This upgrade of postfix changes some default values in the configuration. As "
"part of this upgrade, the following will be changed: (1) chrooted components "
"will be changed from '-' to 'y' in master.cf, and (2) myhostname will be set "
"to a fully-qualified domain name if it is not already such.  The install "
"will be aborted if you do not allow the change."
msgstr ""

#. Type: boolean
#. Description
#: ../templates:4001
msgid "Update main.cf for daemon_directory change"
msgstr "main.cf für daemon_directory-Änderungen aktualisieren"

#. Type: boolean
#. Description
#: ../templates:4001
msgid ""
"This upgrade of postfix changes where daemons are located, and your postfix "
"configuration explicitly specifies the old location.  The install will be "
"aborted if you do not allow the change."
msgstr ""
"Dieses Upgrade von Postfix ändert den Speicherort der Daemons. Ihre Postfix-"
"Konfiguration spezifiziert explizit den alten Ort. Die Installation wird "
"abbrechen, falls Sie der Änderung nicht zustimmen."

#. Type: boolean
#. Description
#: ../templates:5001
msgid "Update dynamicmaps.cf for 3.0"
msgstr "dynamicmaps.cf für 3.0 aktualisieren"

#. Type: boolean
#. Description
#: ../templates:5001
msgid ""
"Postfix version 3.0 changes how dynamic maps are delivered, and your "
"dynamicmaps.cf does not reflect that.  Accept this option to convert "

postfix 3.1.3-6: Please update debconf PO translation for the package postfix

[LaMont Jones]

Hi,

You are noted as the last translator of the debconf translation for
postfix. The English template has been changed, and now some messages
are marked "fuzzy" in your translation or are missing.
I would be grateful if you could take the time and update it.
Please send the updated file to me, or submit it as a wishlist bug
against postfix.

The deadline for receiving the updated translation is
Sun, 08 Jan 2017 17:00:00 -0700.

Thanks in advance,
lamont

#
#Translators, if you are not familiar with the PO format, gettext
#documentation is worth reading, especially sections dedicated to
#this format, e.g. by running:
# info -n '(gettext)PO Files'
# info -n '(gettext)Header Entry'
#
#Some information specific to po-debconf are available at
#/usr/share/doc/po-debconf/README-trans
# or http://www.debian.org/intl/l10n/po-debconf/README-trans
#
#Developers do not need to manually edit POT or PO files.
#
msgid ""
msgstr ""
"Project-Id-Version: postfix 3.0.4-3\n"
"Report-Msgid-Bugs-To: post...@packages.debian.org\n"
"POT-Creation-Date: 2016-07-29 01:18-0400\n"
"PO-Revision-Date: 2016-02-28 21:23+0900\n"
"Last-Translator: Kenshi Muto \n"
"Language-Team: Japanese \n"
"Language: ja\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"

#. Type: boolean
#. Description
#: ../templates:1001
msgid "Add a 'mydomain' entry in main.cf for upgrade?"
msgstr "更新のために master.cf に mydomain エントリを追加しますか?"

#. Type: boolean
#. Description
#: ../templates:1001
msgid ""
"Postfix version 2.3.3-2 and later require changes in main.cf. Specifically, "
"mydomain must be specified, since hostname(1) is not a fully qualified "
"domain name (FQDN)."
msgstr ""
"Postfix バージョン 2.3.3-2 以降では、main.cf の変更を必要とします。特に、"
"hostname(1) が完全修飾ドメイン名 (FQDN) ではなくなったので、 mydomain を指定"
"する必要があります。"

#. Type: boolean
#. Description
#: ../templates:1001
msgid ""
"Failure to fix this will result in a broken mailer. Decline this option to "
"abort the upgrade, giving you the opportunity to add this configuration "
"yourself. Accept this option to automatically set mydomain based on the FQDN "
"of the machine."
msgstr ""
"これを修正するのに失敗すると、壊れたメーラとなってしまいます。更新を中止する"
"にはこの選択肢に「いいえ」とし、この設定をあなた自身で追加します。この選択肢"
"で「はい」と答えれば、自動的にマシンの FQDN に基き mydomain を設定します。"

#. Type: boolean
#. Description
#: ../templates:2001
msgid "Set smtpd_relay_restrictions in main.cf for upgrade?"
msgstr "更新のために master.cf の smtpd_relay_restrictions を設定しますか?"

#. Type: boolean
#. Description
#: ../templates:2001
msgid ""
"Postfix version 2.10 adds smtpd_relay_restrictions, to separate relaying "
"restrictions from recipient restrictions, and you have a non-default value "
"for smtpd_recipient_restrictions."
msgstr ""
"Postfix バージョン 2.10 では、リレー制限を受信者制限から分離するために "
"smtpd_relay_restrictions が追加されました。そして今、"
"smtpd_recipient_restrictions にはデフォルトではない値が設定されています。"

#. Type: boolean
#. Description
#: ../templates:2001
msgid ""
"Failure to do this may result in deferred or bounced mail after the "
"upgrade.  Accept this option to set smtpd_relay_restrictions equal to "
"smtpd_recipient_restrictions."
msgstr ""
"これは、更新後に、メールを遅延または返却してしまう結果となる恐れがあります。"
"smtpd_relay_restrictions を smtpd_recipient_restrictions と等価になるよう設定"
"するには、この選択肢を選んでください。"

#. Type: boolean
#. Description
#: ../templates:3001
msgid "Update configuration to avoid compatibility warnings"
msgstr ""

#. Type: boolean
#. Description
#: ../templates:3001
msgid ""
"This upgrade of postfix changes some default values in the configuration. As "
"part of this upgrade, the following will be changed: (1) chrooted components "
"will be changed from '-' to 'y' in master.cf, and (2) myhostname will be set "
"to a fully-qualified domain name if it is not already such.  The install "
"will be aborted if you do not allow the change."
msgstr ""

#. Type: boolean
#. Description
#: ../templates:4001
msgid "Update main.cf for daemon_directory change"
msgstr "daemon_directory の変更に伴い main.cf を更新します"

#. Type: boolean
#. Description
#: ../templates:4001
msgid ""
"This upgrade of postfix changes where daemons are located, and your postfix "
"configuration explicitly specifies the old location.  The install will be "
"aborted if you do not allow the change."
msgstr ""
"postfix の今回の更新ではデーモンの置かれる位置が変更されていますが、現状の "
"postfix 設定では以前の位置を明示的に指定しています。この変更を受け入れない場"
"合はインストールを中止します。"

#. Type: boolean
#. Description
#: ../templates:5001
msgid "Update dynamicmaps.cf for 3.0"
msgstr "dynamicmaps.cf を 3.0 用に更新します"

#. Type: boolean
#. Description
#: ../templates:5001
msgid ""
"Postfix version 3.0 changes how dynamic maps are delivered, and your "
"dynamicmaps.cf does not reflect that.  Accept this option to convert "
"dynamicmaps.cf to the version required for 3.0."
msgstr ""
"Postfix バージョン 3.0 では動的割り当ての設定に変更がありますが、現状の "
"dynamicmaps.cf はその変更を反映した形式になっていません。この選択を受け入れる"
"と、dynamicmaps.cf を 3.0 で要求される形式に変換します。"

#. Type: boolean
#. 

[Bug 1645912] Re: freeipmi ipmi-config (and discovery) lacks ipv6 support

[LaMont Jones]

** Also affects: maas
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1645912

Title:
  freeipmi ipmi-config (and discovery) lacks ipv6 support

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1645912/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Touch-packages] [Bug 1629972] Re: networking stop incorrectly disconnects from (network) root filesystem

[LaMont Jones]

Verification was done by using MAAS to enlist, commission, and deploy
xenial (with the fix) on a machine.  Previously, it failed to shut down,
because the root disk got unmounted.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1629972

Title:
  networking stop incorrectly disconnects from (network) root filesystem

Status in MAAS:
  Triaged
Status in ifupdown package in Ubuntu:
  Fix Released
Status in ifupdown source package in Xenial:
  Fix Committed
Status in ifupdown source package in Yakkety:
  Fix Released
Status in ifupdown package in Debian:
  New

Bug description:
  === Begin SRU Template ===
  [Impact]
  The systemd networking.service unit will bring down the loopback device (lo)
  when it is stopped.  This behavior differs from the behavior in other
  Ubuntu releases (upstart's networking.conf), where 'lo' is not taken down.

  The problem that was seen was that iscsi root over ipv6 would hang on
  shutdown.  

  [Test Case]
  Test is fairly simple and can be demonstrated in lxc container.
  The key is really that the lo device should not have its link set down
  after stopping networking.service.  So, below:
out=$(ip address show dev lo up); [ -n "$out" ] && echo "$out" || echo empty

  should not show 'empty', but should have LOOPBACK,UP,LOWER in its
  output.

  $ release=yakkety; name=y1
  $ lxc launch ubuntu-daily:$release $name
  $ sleep 10
  $ lxc exec $name /bin/bash

  ## show only things that are up (note output has LOOPBACK,UP,LOWER_UP)
  % ip link show dev lo
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00

  % ip address show dev lo up
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
 valid_lft forever preferred_lft forever

  ## Stop the service and show lo link is down (no 'UP' or 'LOWER_UP').
  % systemctl stop networking.service
  % ip link show dev lo
  1: lo:  mtu 65536 qdisc noqueue state DOWN mode DEFAULT group 
default qlen 1
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  % out=$(ip address show dev lo up); [ -n "$out" ] && echo "$out" || echo empty
  empty

  ## Now enable proposed, install update, reboot and show.
  % rel=$(lsb_release -sc)
  % echo "deb http://archive.ubuntu.com/ubuntu $rel-proposed main" |
  sudo tee /etc/apt/sources.list.d/proposed.list
  % sudo apt update -qy && sudo apt install -qy ifupdown  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  % ip address show dev lo up
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
 valid_lft forever preferred_lft forever
  % systemctl stop networking.service
  % ip link show dev lo
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  % out=$(ip address show dev lo up); [ -n "$out" ] && echo "$out" || echo empty
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
 valid_lft forever preferred_lft forever

  
  [Regression Potential]
  Should be pretty low.  zesty and  yakkety-proposed have this.
  Taking down 'lo' is often cause of problems, and never the solution to
  problems as far as I'm aware.

  [Other Info]

  === End SRU Template ===

  With the switch to systemd, all support for iscsi root (and other)
  filesystems disappeared, since shutdown yanks the rug out from under
  us.

  Rather than just relying on /etc/iscsi/iscsi.initramfs (which d-i
  creates..), the DEV check should be expanded to include iscsi devices,
  and networking.service ExecStop should honor those checks.

  Related bugs:
    * bug 1229458: grub2 needed changes
    * bug 1621615: network not configured when ipv6 netbooted into cloud-init
    * bug 1621507: ipv6 network boot does not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1629972/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Bug 1629972] Re: networking stop incorrectly disconnects from (network) root filesystem

[LaMont Jones]

Verification was done by using MAAS to enlist, commission, and deploy
xenial (with the fix) on a machine.  Previously, it failed to shut down,
because the root disk got unmounted.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1629972

Title:
  networking stop incorrectly disconnects from (network) root filesystem

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1629972/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1629972] Re: networking stop incorrectly disconnects from (network) root filesystem

[LaMont Jones]

** Tags removed: verification-needed
** Tags added: verification-done

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1629972

Title:
  networking stop incorrectly disconnects from (network) root filesystem

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1629972/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs