[Group.of.nepali.translators] [Bug 1959876] Re: xenial/linux-hwe: 4.15.0-169.177~16.04.1 -proposed tracker

2022-02-10 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow/regression-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/verification-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/regression-testing
   Status: Confirmed => Triaged

** Changed in: kernel-sru-workflow/verification-testing
   Status: Confirmed => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  built:
route-entry: 1
  delta:
promote-to-proposed:
- meta
- main
- signed
sru-review:
- main
- meta
- signed
  issue: KSRU-1050
  kernel-stable-master-bug: 1959877
  packages:
main: linux-hwe
meta: linux-meta-hwe
signed: linux-signed-hwe
- phase: Promote to Proposed
- phase-changed: Thursday, 10. February 2022 21:42 UTC
+ phase: Testing
+ phase-changed: Thursday, 10. February 2022 22:47 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Pending -- packages copying to Proposed (main:P
- meta:P signed:P)
+   regression-testing: Ongoing -- testing in progress
  synthetic:
:promote-to-as-proposed: Invalid
  variant: debs
  versions:
main: 4.15.0-169.177~16.04.1
meta: 4.15.0.169.161
signed: 4.15.0-169.177~16.04.1
  versions-clamp:
self: 4.15.0-169.177~16.04.1

-- 
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/1959876

Title:
  xenial/linux-hwe: 4.15.0-169.177~16.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow boot-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Triaged
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow sru-review series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-hwe source package in Xenial:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  built:
route-entry: 1
  delta:
promote-to-proposed:
- meta
- main
- signed
sru-review:
- main
- meta
- signed
  issue: KSRU-1050
  kernel-stable-master-bug: 1959877
  packages:
main: linux-hwe
meta: linux-meta-hwe
signed: linux-signed-hwe
  phase: Testing
  phase-changed: Thursday, 10. February 2022 22:47 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
  synthetic:
:promote-to-as-proposed: Invalid
  variant: debs
  versions:
main: 4.15.0-169.177~16.04.1
meta: 4.15.0.169.161
signed: 4.15.0-169.177~16.04.1
  versions-clamp:
self: 4.15.0-169.177~16.04.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1959876/+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


[Group.of.nepali.translators] [Bug 1959876] Re: xenial/linux-hwe: 4.15.0-169.177~16.04.1 -proposed tracker

2022-02-10 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/promote-signing-to-proposed
   Status: New => Invalid

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: In Progress => Fix Committed

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  built:
route-entry: 1
  delta:
promote-to-proposed:
- meta
- main
- signed
sru-review:
- main
- meta
- signed
  issue: KSRU-1050
  kernel-stable-master-bug: 1959877
  packages:
main: linux-hwe
meta: linux-meta-hwe
signed: linux-signed-hwe
- phase: Ready for Promote to Proposed
- phase-changed: Thursday, 10. February 2022 18:12 UTC
+ phase: Promote to Proposed
+ phase-changed: Thursday, 10. February 2022 21:42 UTC
  reason:
-   promote-to-proposed: Pending -- ready for review
+   promote-to-proposed: Pending -- packages copying to Signing (main:P
+ meta:P signed:B)
  synthetic:
:promote-to-as-proposed: Invalid
  variant: debs
  versions:
main: 4.15.0-169.177~16.04.1
meta: 4.15.0.169.161
signed: 4.15.0-169.177~16.04.1
  versions-clamp:
self: 4.15.0-169.177~16.04.1

-- 
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/1959876

Title:
  xenial/linux-hwe: 4.15.0-169.177~16.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow boot-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow sru-review series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-hwe source package in Xenial:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  built:
route-entry: 1
  delta:
promote-to-proposed:
- meta
- main
- signed
sru-review:
- main
- meta
- signed
  issue: KSRU-1050
  kernel-stable-master-bug: 1959877
  packages:
main: linux-hwe
meta: linux-meta-hwe
signed: linux-signed-hwe
  phase: Promote to Proposed
  phase-changed: Thursday, 10. February 2022 21:42 UTC
  reason:
promote-to-proposed: Ongoing -- packages copying to Signing
  (signed:B)
  synthetic:
:promote-to-as-proposed: Invalid
  variant: debs
  versions:
main: 4.15.0-169.177~16.04.1
meta: 4.15.0.169.161
signed: 4.15.0-169.177~16.04.1
  versions-clamp:
self: 4.15.0-169.177~16.04.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1959876/+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


[Group.of.nepali.translators] [Bug 1531184] Re: [SRU] dnsmasq doesn't start on boot because its interface isn't up yet

2022-02-10 Thread Sergio Durigan Junior
Xenial has reached end of standard support.

** Changed in: dnsmasq (Ubuntu Xenial)
   Status: Confirmed => Won't Fix

-- 
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/1531184

Title:
  [SRU] dnsmasq doesn't start on boot because its interface isn't up yet

Status in One Hundred Papercuts:
  Confirmed
Status in dnsmasq package in Ubuntu:
  Confirmed
Status in dnsmasq source package in Xenial:
  Won't Fix
Status in dnsmasq source package in Bionic:
  Confirmed
Status in dnsmasq package in Debian:
  New

Bug description:
  [Impact]
  dnsmasq will fail to respond on network devices that weren't up when its
  service started, thus not binding as expected.

  [Test Case]
  TBD

  [Regression Potential]
  The fix is just configuring the order of service startup, so is unlikely to 
create any regressions.  Things to watch would be service related misbehaviors 
and general availability of the dnsmasq functionality.

  [Fix]
  Straightforward packaging fix to the service to make it delay startup
  until after the network is online.

  https://bugs.debian.org/cgi-
  bin/bugreport.cgi?att=1;bug=774970;filename=774970-network-
  online.debdiff;msg=22

  [Discussion]

  [Original Report]
  My dnsmasq instance uses "interface=br-vz0" and the interface br-vz0 is 
managed manually in /etc/network/interfaces.

  During boot, dnsmasq is started before br-vz0 is created and this
  causes dnsmasq to exit:

  Jan  5 08:56:16 simon-laptop dnsmasq[1008]: dnsmasq: unknown interface br-vz0
  Jan  5 08:56:16 simon-laptop dnsmasq[1008]: unknown interface br-vz0
  Jan  5 08:56:16 simon-laptop dnsmasq[1008]: FAILED to start up
  Jan  5 08:56:17 simon-laptop NetworkManager[937]:   NetworkManager 
(version 1.0.4) is starting...
  ...
  Jan  5 08:56:18 simon-laptop NetworkManager[937]: 
interface-parser: parsing file /etc/network/interfaces
  ...
  Jan  5 08:56:18 simon-laptop NetworkManager[937]:   found bridge ports 
none for br-vz0
  Jan  5 08:56:18 simon-laptop NetworkManager[937]:   adding bridge port 
none to eni_ifaces
  Jan  5 08:56:18 simon-laptop NetworkManager[937]:   management mode: 
unmanaged

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: dnsmasq 2.75-1
  ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3
  Uname: Linux 4.3.0-5-generic x86_64
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jan  5 09:53:30 2016
  PackageArchitecture: all
  SourcePackage: dnsmasq
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1531184/+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


[Group.of.nepali.translators] [Bug 1888000] Re: Bionic/Xenial minimal cloud image: failed to apply load kernel module

2022-02-10 Thread Sergio Durigan Junior
Xenial has reached end of standard support.

** Changed in: open-iscsi (Ubuntu Xenial)
   Status: Triaged => Won't Fix

** Changed in: linux (Ubuntu Xenial)
   Status: New => Won't Fix

-- 
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/1888000

Title:
  Bionic/Xenial minimal cloud image: failed to apply load kernel module

Status in linux package in Ubuntu:
  Confirmed
Status in open-iscsi package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Won't Fix
Status in open-iscsi source package in Xenial:
  Won't Fix
Status in linux source package in Bionic:
  New
Status in open-iscsi source package in Bionic:
  Triaged

Bug description:
  Overview
  ---
  It appears the Bionic and Xenial minimal images have always shipped with a 
failing systemd unit: "systemd-modules-load.service" with the error "Failed to 
find module 'ib_iser'"

  Expected results
  ---
  $ sudo systemctl list-units --failed --no-legend
  # Return no failed units

  Actual results
  ---
  $ sudo systemctl list-units --failed --no-legend
  systemd-sysctl.service loaded failed failed Apply Kernel Variables
  # cloud-config.service may show up failing to setup the timezone...

  From the journal:
  Jul 17 17:48:27 ubuntu systemd-modules-load[98]: Module 'iscsi_tcp' is builtin
  Jul 17 17:48:27 ubuntu systemd-modules-load[98]: Failed to find module 
'ib_iser'
  Jul 17 17:48:27 ubuntu systemd-sysctl[106]: Couldn't write '176' to 
'kernel/sysrq', ignoring: No such file or directory
  Jul 17 17:48:27 ubuntu systemd-sysctl[106]: Couldn't write 'fq_codel' to 
'net/core/default_qdisc', ignoring: No such file or directory

  Steps to reproduce
  ---
  $ wget 
https://cloud-images.ubuntu.com/daily/server/minimal/releases/bionic/release/ubuntu-18.04-minimal-cloudimg-amd64.img
  $ multipass launch file:///$(pwd)/ubuntu-18.04-minimal-cloudimg-amd64.img 
--name=bionic-minimal
  $ multipass exec bionic-minimal -- sudo systemctl list-units --failed 
--no-legend

  
  ---
  ProblemType: Bug
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser': 
'fuser'
  CRDA: N/A
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lspci: Error: [Errno 2] No such file or directory: 'lspci': 'lspci'
  Lsusb: Error: [Errno 2] No such file or directory: 'lsusb': 'lsusb'
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  Package: linux (not installed)
  PciMultimedia:

  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1069-kvm 
root=PARTUUID=ffb7214d-c783-45ed-b736-278d4ee0cac0 ro console=tty1 console=ttyS0
  ProcVersionSignature: User Name 4.15.0-1069.70-kvm 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-1069-kvm N/A
   linux-backports-modules-4.15.0-1069-kvm  N/A
   linux-firmware   N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.15.0-1069-kvm x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.10.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-bionic
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-bionic
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888000/+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


[Group.of.nepali.translators] [Bug 1877442] Re: Broken SQL CONCAT function behaviour in 5.7.30-0ubuntu0.18.04.1

2022-02-10 Thread Sergio Durigan Junior
Xenial has reached end of standard support.

** Changed in: mysql-5.7 (Ubuntu Xenial)
   Status: Triaged => Won't Fix

-- 
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/1877442

Title:
  Broken SQL CONCAT function behaviour in 5.7.30-0ubuntu0.18.04.1

Status in mysql-5.7 package in Ubuntu:
  Triaged
Status in mysql-8.0 package in Ubuntu:
  Triaged
Status in mysql-5.7 source package in Xenial:
  Won't Fix
Status in mysql-8.0 source package in Xenial:
  Invalid
Status in mysql-5.7 source package in Bionic:
  Triaged
Status in mysql-8.0 source package in Bionic:
  Invalid
Status in mysql-5.7 source package in Eoan:
  Invalid
Status in mysql-8.0 source package in Eoan:
  Won't Fix
Status in mysql-5.7 source package in Focal:
  Invalid
Status in mysql-8.0 source package in Focal:
  Triaged

Bug description:
  [Impact]
  This is a regression in MySQL 5.7.30 (does not affect 8.0 which is in focal 
and development release, nor 5.7.29). The CONCAT function has inconsistent 
behavior depending on whether or not the result is assigned to a variable, 
which is leading to a crash in slurmdbd.

  Since it's limited to 5.7.30, the bug only affects stable releases
  Bionic and Xenial.

  [Test Case]
  - Start up MySQL Server 5.7.30
  - Connect to it with the mysql cli (with default install of the server, "sudo 
mysql" will connect to the MySQL root user)
  - Run the following two queries:
* SELECT CONCAT('');
* SET @var = ""; SELECT @var := CONCAT('');
  They should give the same output, but the second one returns NULL instead of 
an empty string when using 5.7.30.

  [Regression Potential]
  The patch changes fairly low-level code, which can always carry some risk. 

  [Other info]
  This bug is fixed in the next upstream release of MySQL (5.7.31), so the 
patch would only be needed until that is picked.

  --- ORIGINAL DESCRIPTION ---
  Hi,

  Yesterday we upgraded from 5.7.29-0ubuntu0.18.04.1 to
  5.7.30-0ubuntu0.18.04.1 (via unattended-upgrade) on Ubuntu 18.04 and
  slurmdbd (https://packages.ubuntu.com/bionic/admin/slurmdbd) started
  segfaulting.

  Upon inspection, the slurmdbd crash is caused by a change of behaviour
  of the SQL CONCAT function. The new behaviour seems wrong.

  Calling
  SELECT CONCAT('');
  will result in an empty string as expected however if the result is assigned 
to a variable with:
  SET @var = ""; SELECT @var := CONCAT('');
  the variable will be NULL instead of an empty string.

  It seems that when the output of CONCAT is assigned to a variable; if
  CONCAT should have returned an empty string, it will set the variable
  to NULL instead.

  SLURM itself crashes because it uses a stored procedure which relies
  on the output of CONCAT to be an empty string rather than a NULL
  variable and tries to dereference the pointer.

  I wasn’t able to get hold of 5.7.29-0ubuntu0.18.04.1 via APT so I
  tested on 5.7.21-1ubuntu1. On 5.7.21, the variable was correctly set
  to an empty string. I have also tried on 20.04 and the behaviour is
  correct as well. So the problem seems to be present only in the
  version 5.7.30-0ubuntu0.18.04.1.

  I think that the behaviour was introduced in the 5.7 branch by this commit:
  
https://github.com/mysql/mysql-server/commit/addb2aab601d98e685eccae545f79d120561ad9b
  but I am not entirely sure.

  This bug is a bit annoying because it makes SLURM with accounting
  enabled completely unusable. However downgrading MySQL to
  5.7.29-0ubuntu0.18.04.1 temporarily fixed the problem.

  I have attached a log file with examples to reproduce the bug.

  Thank you very much.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1877442/+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


[Group.of.nepali.translators] [Bug 1466926] Re: reload apache2 with mpm_event cause scoreboard is full

2022-02-10 Thread Sergio Durigan Junior
Xenial has reached its end of standard support.

** Changed in: apache2 (Ubuntu Xenial)
   Status: Triaged => Won't Fix

-- 
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/1466926

Title:
  reload apache2  with mpm_event cause  scoreboard is full

Status in apache2 package in Ubuntu:
  Fix Released
Status in apache2 source package in Trusty:
  Won't Fix
Status in apache2 source package in Xenial:
  Won't Fix
Status in apache2 source package in Zesty:
  Fix Released

Bug description:
  [Impact]

   * apache2 reload can fill up the scorecard with graceful reastarting
     workers to an amount that it is unable to serve more requests.

   * Backport fix from upstream to avoid the issue

  [Test Case]

   * In comment #8 I outlined some steps to fill up the scorecard with
     Gracefully stopping processes. But that never triggered the reported
     bug of eventually breaking new requests for me (It is still good to
     verify some busy tests on this part of the apache code)
     -> Therefore one of the reporters of the bug tested the ppa quite a
    while on his main machines that formerly were affected by the issue.
     -> no clear "do this then X happens" test case steps
   * Perform arbitrary additional functional tests on the package to make sure 
no regressions are visible

  [Regression Potential]

   * It is a rather complex code change in the mpm event handling.
     Only the first change is to code, the other two are for the
     documentation to match.
     We tested some apache benchmarks to check the effect, but found neither
     a positive nor negative impact in general (other than the bug being
     resolved). Yet if people rely on very specific behavior of the mpm
     handling that might change a bit.
     It will change for the good of it, but always remember xkcd.com/1172

     TL;DR: IMHO it clearly has a ">none" regression potential on the mpm
     event handling

  [Other Info]

   * Since this is hard to test we had a 2+ week test on the ppa, see
     comments c#8 - c#15

   * It clearly is a fix for some (e.g. the reporter of the bug), but I'd
     understand if the SRU Team would rate it as feature and deny it for an
     SRU - depends on the POV, certainly worth to be reviewed at least.

  

  On the clean install Ubuntu 14.04 with Apache without almost any
  client load the Apache server with the command "service apache2
  reload" itself allocates slots marked with "Gracefully finishing" for
  which rejects new connections.

  For full rejection of new requests is sufficient to perform 4x command
  "service apache2 reload".

  Ubuntu 14.04.2 LTS
  Apache 2.4.7-ubuntu4.4 (mpm_event)
  Kernel 2.16.0-30-generic

  Reproduce problem:
  #
  1/ service apache2 start
  __W_
  ___.
  ..

  2/ service apache2 reload

  .GGG
  GGG__W__
  __

  3/ service apache2 reload

  ___W_GGG
  GGG__...
  ..

  4/ service apache2 reload

  
  G___
  W_

  5/ service apache2 reload -> Server Apache not responding
  With logs in apache error log file:
  ... [mpm_event:error] [pid 9381:tid 1234563234] AH00485: scoreboard is full, 
not at MaxRequestWorkers
  ...
  #

  My workaround was change to  MPM module  from "mpm_event" to
  "mpm_worker".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1466926/+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


[Group.of.nepali.translators] [Bug 1789527] Re: Galera agent doesn't work when grastate.dat contains safe_to_bootstrap

2022-02-10 Thread Sergio Durigan Junior
Xenial has reached its end of standard support.

** Changed in: resource-agents (Ubuntu Xenial)
   Status: Confirmed => Won't Fix

-- 
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/1789527

Title:
  Galera agent doesn't work when grastate.dat contains safe_to_bootstrap

Status in resource-agents package in Ubuntu:
  Fix Released
Status in resource-agents source package in Trusty:
  Won't Fix
Status in resource-agents source package in Xenial:
  Won't Fix
Status in resource-agents source package in Bionic:
  Fix Released

Bug description:
  Galera resource agent is not able to put mysql up and master even if
  safe_to_bootstrap flag in grastate.dat is set to 1.

  * res_percona_promote_0 on 09fde2-2 'unknown error' (1): call=1373,
  status=complete, exitreason='MySQL server failed to start (pid=2432)
  (rc=0), please check your installation',

  
  The resource agent is not able to handle safe_to_bootstrap feature in galera: 
http://galeracluster.com/2016/11/introducing-the-safe-to-bootstrap-feature-in-galera-cluster/

  I use percona cluster database which uses the same galera mechanism
  for clustering.

  Packages I use in Xenial:

  resource-agents   3.9.7-1
  percona-xtradb-cluster-server-5.6 5.6.37-26.21-0ubuntu0.16.04.2
  pacemaker 1.1.14-2ubuntu1.4
  corosync  2.3.5-3ubuntu2.1

  A workaround exist in : 
https://github.com/ClusterLabs/resource-agents/issues/915
  A fix also exist but it was not addressed to xenial package: 
https://github.com/ClusterLabs/resource-agents/pull/1022

  Is it possible to add this fix on the recent package of resource-
  agents in Xenial ?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resource-agents/+bug/1789527/+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


[Group.of.nepali.translators] [Bug 1633485] Re: Backport login throttling plugin to 5.6 and 5.7

2022-02-10 Thread Sergio Durigan Junior
Trusty has reached its end of standard support.

** Changed in: mysql-5.6 (Ubuntu Trusty)
   Status: Triaged => Won't Fix

-- 
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/1633485

Title:
  Backport login throttling plugin to 5.6 and 5.7

Status in mysql-5.6 package in Ubuntu:
  Invalid
Status in mysql-5.7 package in Ubuntu:
  Fix Released
Status in mysql-5.6 source package in Precise:
  Invalid
Status in mysql-5.7 source package in Precise:
  Invalid
Status in mysql-5.6 source package in Trusty:
  Won't Fix
Status in mysql-5.7 source package in Trusty:
  Invalid
Status in mysql-5.6 source package in Xenial:
  Invalid
Status in mysql-5.7 source package in Xenial:
  Fix Released
Status in mysql-5.6 source package in Yakkety:
  Invalid
Status in mysql-5.7 source package in Yakkety:
  Invalid

Bug description:
  In MySQL 8.0 we (Oracle) are adding a plugin to rate-limit/throttle
  login attempts in order to stop brute-force attacks.

  Since this is a security mechanism that has been requested by users,
  we would also like to backport this plugin to MySQL 5.6 and 5.7.

  After consulting with Robie Basak (racb), we understand this change to
  be allowed in Ubuntu under the SRU process (Sect. 2.2,
  https://wiki.ubuntu.com/StableReleaseUpdates), but if there are any
  comments or objections, we'd like to hear them now.

  
  Impact
  ==

  This functionality is implemented in a plugin. The plugin is not
  loaded, and the functionality will not be activated unless the DBA
  explicitly activates it.

  
  Regression potential
  

  The potential for regression is considered low for the following
  reasons:

   - The new functionality is in a plugin that 1) is not loaded by
 default, and 2) can be unloaded if it causes problems.

   - The change does not introduce new SQL syntax, and no existing
 syntax is affected.

   - The plugin is new, so it's not used by any other packages in
 Ubuntu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1633485/+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


[Group.of.nepali.translators] [Bug 1745185] Re: If apt-get upgrade is run on mysql server when the server is disabled, the upgrade fails.

2022-02-10 Thread Sergio Durigan Junior
Xenial has reached its end of standard support.

** Changed in: mysql-5.7 (Ubuntu Xenial)
   Status: Triaged => Won't Fix

-- 
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/1745185

Title:
  If apt-get upgrade is run on mysql server when the server is disabled,
  the upgrade fails.

Status in mysql-5.7 package in Ubuntu:
  Invalid
Status in mysql-5.7 source package in Xenial:
  Won't Fix

Bug description:
  Since I only use the mysql server for development, I tend to keep the server 
disabled with systemctl. If mysql server is upgraded while the service is 
disabled, apt-get fails. To remedy this, I must run "systemctl enable mysqld" 
before "apt-get upgrade". Since I found a work around, it isn't a big deal, but 
a less experienced user may have trouble diagnosing this. Possible solutions 
are:
  1) Better error message
  2) If the server must be running for upgrade, the upgrade could start it. 
Maybe prompting first.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1745185/+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


[Group.of.nepali.translators] [Bug 1828496] Re: service haproxy reload sometimes fails to pick up new TLS certificates

2022-02-10 Thread Sergio Durigan Junior
Xenial has reached its end of standard support.

** Changed in: haproxy (Ubuntu Xenial)
   Status: Confirmed => Won't Fix

-- 
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/1828496

Title:
  service haproxy reload sometimes fails to pick up new TLS certificates

Status in haproxy package in Ubuntu:
  Confirmed
Status in haproxy source package in Xenial:
  Won't Fix
Status in haproxy source package in Bionic:
  Confirmed

Bug description:
  I suspect this is the same thing reported on StackOverflow:

  "I had this same issue where even after reloading the config, haproxy
  would randomly serve old certs. After looking around for many days the
  issue was that "reload" operation created a new process without
  killing the old one. Confirm this by "ps aux | grep haproxy"."

  https://stackoverflow.com/questions/46040504/haproxy-wont-recognize-
  new-certificate

  In our setup, we automate Let's Encrypt certificate renewals, and a
  fresh certificate will trigger a reload of the service. But
  occasionally this reload doesn't seem to do anything.

  Will update with details next time it happens, and hopefully confirm
  the multiple process theory.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1828496/+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


[Group.of.nepali.translators] [Bug 1052449] Re: corosync hangs due to missing pacemaker shutdown scripts

2022-02-10 Thread Sergio Durigan Junior
Trusty has reached its end of standard support, so this bug will not be
fixed for that release.

** Changed in: pacemaker (Ubuntu Trusty)
   Status: Triaged => Won't Fix

-- 
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/1052449

Title:
  corosync hangs due to missing pacemaker shutdown scripts

Status in pacemaker package in Ubuntu:
  Fix Released
Status in pacemaker source package in Precise:
  Won't Fix
Status in pacemaker source package in Trusty:
  Won't Fix
Status in pacemaker source package in Xenial:
  Fix Released

Bug description:
  The pacemaker package installs the right init script but doesn't link
  it to the according runlevels. If corosync is activated and started on
  the system this leads to a hanging shutdown / reboot because corosync
  only ends if pacemaker is stopped beforehand. In addition to this the
  pacemaker daemon has to start after corosync but has to stop before
  corosync.

  A possible solution would be to link the init script accordingly an
  enable it throug /etc/default/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1052449/+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


[Group.of.nepali.translators] [Bug 1589531] Re: HA_VARRUN has trailing slash

2022-02-10 Thread Sergio Durigan Junior
Xenial has reached its end of standard support.

** Changed in: resource-agents (Ubuntu Xenial)
   Status: Confirmed => Won't Fix

-- 
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/1589531

Title:
  HA_VARRUN has trailing slash

Status in resource-agents package in Ubuntu:
  Fix Released
Status in resource-agents source package in Xenial:
  Won't Fix
Status in resource-agents source package in Bionic:
  Fix Released
Status in resource-agents source package in Eoan:
  Fix Released

Bug description:
  Because HA_VARRUN contains a trailing slash a check in ocf_mkstatedir
  if $path starts with /var/run/ fails.

  This is a bug in 3.9.7-1 on Xenial.

  Fix in upstream:
  
https://github.com/ClusterLabs/resource-agents/commit/571f8dd928b168eef36f79316a5198df9cbdbdca

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resource-agents/+bug/1589531/+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


[Group.of.nepali.translators] [Bug 1732150] Re: Unbound behaviour changes (wrong) when domain-insecure is set for a stub zone with multiple stub-addr(s)

2022-02-10 Thread Sergio Durigan Junior
Xenial and Trusty have reached end of standard support.

** Changed in: unbound (Ubuntu Trusty)
   Status: Triaged => Won't Fix

** Changed in: unbound (Ubuntu Xenial)
   Status: Triaged => Won't Fix

-- 
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/1732150

Title:
  Unbound behaviour changes (wrong) when domain-insecure is set for a
  stub zone with multiple stub-addr(s)

Status in Unbound - Caching DNS Resolver:
  Unknown
Status in unbound package in Ubuntu:
  Fix Released
Status in unbound source package in Trusty:
  Won't Fix
Status in unbound source package in Xenial:
  Won't Fix
Status in unbound source package in Bionic:
  Incomplete

Bug description:
  [Impact]

   * DNSSEC setup with domain-insecure set fail to work.
 The lookup will process all available servers leading to a very long 
 lookup time.

   * Backport upstream fix to stop checking for further trust points in that 
 case.

  [Test Case]

   * TBD: Waiting for the bug reporter to provide the initial steps that we 
 migth refine

  [Regression Potential]

   * The change will make it stop iterating for further DNSSEC records in 
 certain configuration cases (domain-insecure). But this is just what 
 the respective configuration is meant to do (see 
 http://manpages.ubuntu.com/manpages/bionic/man5/unbound.conf.5.html)
 So it should speed up certain cases were so far it still iterated
 through servers, but giving that up early is just what it shoudl be per 
 config.
 I can think of a slight behavior change due to being faster now, but 
 the end result should not change due to this. With that background I 
 could think of two regressions:
   a) the faster lookup makes automation wonder
   b) there would be a condition we (and upstream) missed which would 
  change the actual lookup return
 Given that the code was not reverted upstream for quite a while I'd 
 think the latter is only theoretical, and the former should be of low 
 risk.

  [Other Info]
   
   * n/a

  
  ---

  Unbound contains a bug when domain-insecure is set for a (stub) zone.
  This bug is fixed, see https://www.nlnetlabs.nl/bugs-
  script/show_bug.cgi?id=2882. Can you please backport this to the
  Trusty package?

  With regards,
  Richard Arends

To manage notifications about this bug go to:
https://bugs.launchpad.net/unbound/+bug/1732150/+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


[Group.of.nepali.translators] [Bug 1959876] Re: xenial/linux-hwe: 4.15.0-169.177~16.04.1 -proposed tracker

2022-02-10 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/boot-testing
   Status: In Progress => Fix Released

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Confirmed

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  built:
route-entry: 1
  delta:
+   promote-to-proposed:
+   - meta
+   - main
+   - signed
sru-review:
- main
- meta
- signed
  issue: KSRU-1050
  kernel-stable-master-bug: 1959877
  packages:
main: linux-hwe
meta: linux-meta-hwe
signed: linux-signed-hwe
- phase: Testing
- phase-changed: Thursday, 10. February 2022 16:07 UTC
+ phase: Ready for Promote to Proposed
+ phase-changed: Thursday, 10. February 2022 18:12 UTC
  reason:
-   boot-testing: Ongoing -- testing in progress
+   promote-to-proposed: Pending -- ready for review
  synthetic:
:promote-to-as-proposed: Invalid
  variant: debs
  versions:
main: 4.15.0-169.177~16.04.1
meta: 4.15.0.169.161
signed: 4.15.0-169.177~16.04.1
  versions-clamp:
self: 4.15.0-169.177~16.04.1

-- 
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/1959876

Title:
  xenial/linux-hwe: 4.15.0-169.177~16.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow boot-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow sru-review series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-hwe source package in Xenial:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  built:
route-entry: 1
  delta:
promote-to-proposed:
- meta
- main
- signed
sru-review:
- main
- meta
- signed
  issue: KSRU-1050
  kernel-stable-master-bug: 1959877
  packages:
main: linux-hwe
meta: linux-meta-hwe
signed: linux-signed-hwe
  phase: Ready for Promote to Proposed
  phase-changed: Thursday, 10. February 2022 18:12 UTC
  reason:
promote-to-proposed: Pending -- ready for review
  synthetic:
:promote-to-as-proposed: Invalid
  variant: debs
  versions:
main: 4.15.0-169.177~16.04.1
meta: 4.15.0.169.161
signed: 4.15.0-169.177~16.04.1
  versions-clamp:
self: 4.15.0-169.177~16.04.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1959876/+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


[Group.of.nepali.translators] [Bug 1959876] Re: xenial/linux-hwe: 4.15.0-169.177~16.04.1 -proposed tracker

2022-02-10 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow/boot-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/boot-testing
   Status: Confirmed => Triaged

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
+ boot-testing-requested: true
  built:
route-entry: 1
  delta:
sru-review:
- main
- meta
- signed
  issue: KSRU-1050
  kernel-stable-master-bug: 1959877
  packages:
main: linux-hwe
meta: linux-meta-hwe
signed: linux-signed-hwe
- phase: Packaging
- phase-changed: Thursday, 10. February 2022 08:36 UTC
+ phase: Testing
+ phase-changed: Thursday, 10. February 2022 16:07 UTC
  reason:
-   :prepare-packages: Pending -- building in ppa (meta:P signed:P)
-   prepare-package-meta: Ongoing -- meta package not yet fully built
-   prepare-package-signed: Ongoing -- signed package not yet fully
- built
+   boot-testing: Ongoing -- testing in progress
  synthetic:
:promote-to-as-proposed: Invalid
  variant: debs
  versions:
main: 4.15.0-169.177~16.04.1
meta: 4.15.0.169.161
signed: 4.15.0-169.177~16.04.1
  versions-clamp:
self: 4.15.0-169.177~16.04.1

-- 
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/1959876

Title:
  xenial/linux-hwe: 4.15.0-169.177~16.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow boot-testing series:
  Triaged
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow sru-review series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-hwe source package in Xenial:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  built:
route-entry: 1
  delta:
sru-review:
- main
- meta
- signed
  issue: KSRU-1050
  kernel-stable-master-bug: 1959877
  packages:
main: linux-hwe
meta: linux-meta-hwe
signed: linux-signed-hwe
  phase: Testing
  phase-changed: Thursday, 10. February 2022 16:07 UTC
  reason:
boot-testing: Ongoing -- testing in progress
  synthetic:
:promote-to-as-proposed: Invalid
  variant: debs
  versions:
main: 4.15.0-169.177~16.04.1
meta: 4.15.0.169.161
signed: 4.15.0-169.177~16.04.1
  versions-clamp:
self: 4.15.0-169.177~16.04.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1959876/+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


[Group.of.nepali.translators] [Bug 1959876] Re: xenial/linux-hwe: 4.15.0-169.177~16.04.1 -proposed tracker

2022-02-10 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/prepare-package
   Status: Fix Committed => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  built:
route-entry: 1
  delta:
sru-review:
- main
- meta
- signed
  issue: KSRU-1050
  kernel-stable-master-bug: 1959877
  packages:
main: linux-hwe
meta: linux-meta-hwe
signed: linux-signed-hwe
  phase: Packaging
  phase-changed: Thursday, 10. February 2022 08:36 UTC
  reason:
-   :prepare-packages: Pending -- building in ppa (main:P meta:D
- signed:D)
-   prepare-package: Ongoing -- main package not yet fully built
+   :prepare-packages: Ongoing -- building in ppa (meta:B signed:B)
prepare-package-meta: Ongoing -- meta package not yet fully built
prepare-package-signed: Ongoing -- signed package not yet fully
  built
  synthetic:
:promote-to-as-proposed: Invalid
  variant: debs
  versions:
main: 4.15.0-169.177~16.04.1
meta: 4.15.0.169.161
signed: 4.15.0-169.177~16.04.1
  versions-clamp:
self: 4.15.0-169.177~16.04.1

-- 
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/1959876

Title:
  xenial/linux-hwe: 4.15.0-169.177~16.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow boot-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Committed
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Committed
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow sru-review series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-hwe source package in Xenial:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  built:
route-entry: 1
  delta:
sru-review:
- main
- meta
- signed
  issue: KSRU-1050
  kernel-stable-master-bug: 1959877
  packages:
main: linux-hwe
meta: linux-meta-hwe
signed: linux-signed-hwe
  phase: Packaging
  phase-changed: Thursday, 10. February 2022 08:36 UTC
  reason:
:prepare-packages: Pending -- building in ppa (meta:B signed:P)
prepare-package-meta: Ongoing -- meta package not yet fully built
prepare-package-signed: Ongoing -- signed package not yet fully
  built
  synthetic:
:promote-to-as-proposed: Invalid
  variant: debs
  versions:
main: 4.15.0-169.177~16.04.1
meta: 4.15.0.169.161
signed: 4.15.0-169.177~16.04.1
  versions-clamp:
self: 4.15.0-169.177~16.04.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1959876/+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


[Group.of.nepali.translators] [Bug 1959876] Re: xenial/linux-hwe: 4.15.0-169.177~16.04.1 -proposed tracker

2022-02-10 Thread Andy Whitcroft
** Changed in: kernel-sru-workflow/sru-review
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/sru-review
 Assignee: (unassigned) => Andy Whitcroft (apw)

** Changed in: kernel-sru-workflow/sru-review
   Status: In Progress => 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/1959876

Title:
  xenial/linux-hwe: 4.15.0-169.177~16.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow boot-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Committed
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Committed
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Committed
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow sru-review series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-hwe source package in Xenial:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  built:
route-entry: 1
  delta:
sru-review:
- main
- meta
- signed
  issue: KSRU-1050
  kernel-stable-master-bug: 1959877
  packages:
main: linux-hwe
meta: linux-meta-hwe
signed: linux-signed-hwe
  phase: Packaging
  phase-changed: Thursday, 10. February 2022 08:36 UTC
  reason:
:prepare-packages: Ongoing -- building in ppa (main:B meta:D
  signed:D)
prepare-package: Ongoing -- main package not yet fully built
prepare-package-meta: Ongoing -- meta package not yet fully built
prepare-package-signed: Ongoing -- signed package not yet fully
  built
  synthetic:
:promote-to-as-proposed: Invalid
  variant: debs
  versions:
main: 4.15.0-169.177~16.04.1
meta: 4.15.0.169.161
signed: 4.15.0-169.177~16.04.1
  versions-clamp:
self: 4.15.0-169.177~16.04.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1959876/+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


[Group.of.nepali.translators] [Bug 1958556] Re: [SRU] ubuntu-advantage-tools (27.5 -> 27.6) Xenial, Bionic, Focal, Impish

2022-02-10 Thread Launchpad Bug Tracker
This bug was fixed in the package ubuntu-advantage-tools - 27.6~18.04.1

---
ubuntu-advantage-tools (27.6~18.04.1) bionic; urgency=medium

  * Backport new upstream release: (LP: #1958556) to bionic

 -- Lucas Moura   Thu, 20 Jan 2022 18:02:22
-0300

** Changed in: ubuntu-advantage-tools (Ubuntu Xenial)
   Status: Fix Committed => 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/1958556

Title:
  [SRU] ubuntu-advantage-tools (27.5 -> 27.6) Xenial, Bionic, Focal,
  Impish

Status in ubuntu-advantage-tools package in Ubuntu:
  Fix Released
Status in ubuntu-advantage-tools source package in Xenial:
  Fix Released
Status in ubuntu-advantage-tools source package in Bionic:
  Fix Released
Status in ubuntu-advantage-tools source package in Focal:
  Fix Released
Status in ubuntu-advantage-tools source package in Impish:
  Fix Released

Bug description:
  [Impact]
  The main focus of this release is to allow focal cloud users to enable FIPS 
services on their machines. Furthermore, we are also performing some small 
fixes in the code:

  * Fixing how apt and motd messages are updated after some ua operations
  * Disable the license check job after attach/auto-attach operations.

  Additionally, we are now making our logs word readable

  We have spent a lot time debugging our logs to see if are leaking any
  credentials there, but we are now sure that we have redacted all of
  the private information

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/UbuntuAdvantageToolsUpdates

  The ubuntu-advantage-tools team will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug.
  ubuntu-advantage-tools team members will not mark ‘verification-done’
  until this has happened.

  Integration test artifacts are attached to the bug.

  [Regression Potential]
  Most of the changes are adding new things and the integration tests make sure 
that the existing functionality is preserved.

  However, by making the logs world readable, we could be still leaking
  some credentials there which would be now readable be every user on
  the machine.

  [Discussion]
  Even though the focus of this release is on allowing FIPS services on Focal 
machines, the major change of this release is making the logs world readable.

  The reason for making the logs world readable is that we don't have
  any major reason keep it readable by only sudo users. Also, this will
  also allow for non-root users to more easily open bugs that affect the
  package.

  We have performed several tests on different scenarios to verify that
  the logs are not leaking, but even though we have tested it multiple
  times, we could still have a blind spot on that work.

  If we do have those leaks, this means that user on the machine can try
  to use the leaked credentials on other machines. This will not affect
  the machines already attached to an UA subscription.

  If the team has any reservations about this work, we can better
  discuss a better path moving forward here.

  [Changelog]

    * d/tools.postinst:
  - make log files world readable
    * New upstream release 27.6
  - cli: only go for resources on explicit help calls
  - fips:
    + allow enabling FIPS on focal clouds
    + update prompt messages
  - jobs: disable jobs after attach/auto-attach
  - message: fix how apt and motd messages are updated after ua commands

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1958556/+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


[Group.of.nepali.translators] [Bug 1958556] Re: [SRU] ubuntu-advantage-tools (27.5 -> 27.6) Xenial, Bionic, Focal, Impish

2022-02-10 Thread Launchpad Bug Tracker
This bug was fixed in the package ubuntu-advantage-tools - 27.6~20.04.1

---
ubuntu-advantage-tools (27.6~20.04.1) focal; urgency=medium

  * Backport new upstream release: (LP: #1958556) to focal

 -- Lucas Moura   Thu, 20 Jan 2022 18:02:27
-0300

** Changed in: ubuntu-advantage-tools (Ubuntu Focal)
   Status: Fix Committed => Fix Released

** Changed in: ubuntu-advantage-tools (Ubuntu Bionic)
   Status: Fix Committed => 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/1958556

Title:
  [SRU] ubuntu-advantage-tools (27.5 -> 27.6) Xenial, Bionic, Focal,
  Impish

Status in ubuntu-advantage-tools package in Ubuntu:
  Fix Released
Status in ubuntu-advantage-tools source package in Xenial:
  Fix Released
Status in ubuntu-advantage-tools source package in Bionic:
  Fix Released
Status in ubuntu-advantage-tools source package in Focal:
  Fix Released
Status in ubuntu-advantage-tools source package in Impish:
  Fix Released

Bug description:
  [Impact]
  The main focus of this release is to allow focal cloud users to enable FIPS 
services on their machines. Furthermore, we are also performing some small 
fixes in the code:

  * Fixing how apt and motd messages are updated after some ua operations
  * Disable the license check job after attach/auto-attach operations.

  Additionally, we are now making our logs word readable

  We have spent a lot time debugging our logs to see if are leaking any
  credentials there, but we are now sure that we have redacted all of
  the private information

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/UbuntuAdvantageToolsUpdates

  The ubuntu-advantage-tools team will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug.
  ubuntu-advantage-tools team members will not mark ‘verification-done’
  until this has happened.

  Integration test artifacts are attached to the bug.

  [Regression Potential]
  Most of the changes are adding new things and the integration tests make sure 
that the existing functionality is preserved.

  However, by making the logs world readable, we could be still leaking
  some credentials there which would be now readable be every user on
  the machine.

  [Discussion]
  Even though the focus of this release is on allowing FIPS services on Focal 
machines, the major change of this release is making the logs world readable.

  The reason for making the logs world readable is that we don't have
  any major reason keep it readable by only sudo users. Also, this will
  also allow for non-root users to more easily open bugs that affect the
  package.

  We have performed several tests on different scenarios to verify that
  the logs are not leaking, but even though we have tested it multiple
  times, we could still have a blind spot on that work.

  If we do have those leaks, this means that user on the machine can try
  to use the leaked credentials on other machines. This will not affect
  the machines already attached to an UA subscription.

  If the team has any reservations about this work, we can better
  discuss a better path moving forward here.

  [Changelog]

    * d/tools.postinst:
  - make log files world readable
    * New upstream release 27.6
  - cli: only go for resources on explicit help calls
  - fips:
    + allow enabling FIPS on focal clouds
    + update prompt messages
  - jobs: disable jobs after attach/auto-attach
  - message: fix how apt and motd messages are updated after ua commands

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1958556/+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


[Group.of.nepali.translators] [Bug 1958556] Re: [SRU] ubuntu-advantage-tools (27.5 -> 27.6) Xenial, Bionic, Focal, Impish

2022-02-10 Thread Launchpad Bug Tracker
This bug was fixed in the package ubuntu-advantage-tools - 27.6~21.10.1

---
ubuntu-advantage-tools (27.6~21.10.1) impish; urgency=medium

  * Backport new upstream release: (LP: #1958556) to impish

 -- Lucas Moura   Thu, 20 Jan 2022 18:02:36
-0300

** Changed in: ubuntu-advantage-tools (Ubuntu Impish)
   Status: Fix Committed => 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/1958556

Title:
  [SRU] ubuntu-advantage-tools (27.5 -> 27.6) Xenial, Bionic, Focal,
  Impish

Status in ubuntu-advantage-tools package in Ubuntu:
  Fix Released
Status in ubuntu-advantage-tools source package in Xenial:
  Fix Released
Status in ubuntu-advantage-tools source package in Bionic:
  Fix Released
Status in ubuntu-advantage-tools source package in Focal:
  Fix Released
Status in ubuntu-advantage-tools source package in Impish:
  Fix Released

Bug description:
  [Impact]
  The main focus of this release is to allow focal cloud users to enable FIPS 
services on their machines. Furthermore, we are also performing some small 
fixes in the code:

  * Fixing how apt and motd messages are updated after some ua operations
  * Disable the license check job after attach/auto-attach operations.

  Additionally, we are now making our logs word readable

  We have spent a lot time debugging our logs to see if are leaking any
  credentials there, but we are now sure that we have redacted all of
  the private information

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/UbuntuAdvantageToolsUpdates

  The ubuntu-advantage-tools team will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug.
  ubuntu-advantage-tools team members will not mark ‘verification-done’
  until this has happened.

  Integration test artifacts are attached to the bug.

  [Regression Potential]
  Most of the changes are adding new things and the integration tests make sure 
that the existing functionality is preserved.

  However, by making the logs world readable, we could be still leaking
  some credentials there which would be now readable be every user on
  the machine.

  [Discussion]
  Even though the focus of this release is on allowing FIPS services on Focal 
machines, the major change of this release is making the logs world readable.

  The reason for making the logs world readable is that we don't have
  any major reason keep it readable by only sudo users. Also, this will
  also allow for non-root users to more easily open bugs that affect the
  package.

  We have performed several tests on different scenarios to verify that
  the logs are not leaking, but even though we have tested it multiple
  times, we could still have a blind spot on that work.

  If we do have those leaks, this means that user on the machine can try
  to use the leaked credentials on other machines. This will not affect
  the machines already attached to an UA subscription.

  If the team has any reservations about this work, we can better
  discuss a better path moving forward here.

  [Changelog]

    * d/tools.postinst:
  - make log files world readable
    * New upstream release 27.6
  - cli: only go for resources on explicit help calls
  - fips:
    + allow enabling FIPS on focal clouds
    + update prompt messages
  - jobs: disable jobs after attach/auto-attach
  - message: fix how apt and motd messages are updated after ua commands

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1958556/+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


[Group.of.nepali.translators] [Bug 1959876] Re: xenial/linux-hwe: 4.15.0-169.177~16.04.1 -proposed tracker

2022-02-10 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/promote-to-security
   Status: New => Invalid

** Changed in: kernel-sru-workflow/security-signoff
   Status: New => Invalid

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  issue: KSRU-1050
  kernel-stable-master-bug: 1959877
  packages:
main: linux-hwe
meta: linux-meta-hwe
signed: linux-signed-hwe
- phase: Ready for Packaging
- phase-changed: Wednesday, 09. February 2022 17:22 UTC
+ phase: Packaging
+ phase-changed: Thursday, 10. February 2022 08:36 UTC
  reason:
-   :prepare-packages: Pending -b Debs ready to be cranked
-   prepare-package: Pending -- version not specified
+   :prepare-packages: 'Ongoing -b Being cranked by: smb'
+   prepare-package: Pending -- tag not published and package not
+ uploaded
+   prepare-package-meta: Pending -- tag not published and package not
+ uploaded
+   prepare-package-signed: Pending -- tag not published and package not
+ uploaded
+ synthetic:
+   :promote-to-as-proposed: Invalid
  variant: debs
+ versions-clamp:
+   self: 4.15.0-169.177~16.04.1

-- 
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/1959876

Title:
  xenial/linux-hwe: 4.15.0-169.177~16.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow boot-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow sru-review series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-hwe source package in Xenial:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  issue: KSRU-1050
  kernel-stable-master-bug: 1959877
  packages:
main: linux-hwe
meta: linux-meta-hwe
signed: linux-signed-hwe
  phase: Packaging
  phase-changed: Thursday, 10. February 2022 08:36 UTC
  reason:
:prepare-packages: 'Ongoing -b Being cranked by: smb'
prepare-package: Pending -- tag not published and package not
  uploaded
prepare-package-meta: Pending -- tag not published and package not
  uploaded
prepare-package-signed: Pending -- tag not published and package not
  uploaded
  synthetic:
:promote-to-as-proposed: Invalid
  variant: debs
  versions-clamp:
self: 4.15.0-169.177~16.04.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1959876/+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