[Group.of.nepali.translators] [Bug 1856369] [NEW] [SRU] Add riscv64 support to cputable for xenial

[Adam Conrad]

Public bug reported:

[ Justification ]
Much like we did for arm64 in 
https://launchpad.net/ubuntu/+source/dpkg/1.16.1.2ubuntu7.1 and for ppc64el in 
https://launchpad.net/ubuntu/+source/dpkg/1.16.1.2ubuntu7.2, we need to add 
riscv64 support for xenial (and up) so dpkg running on LP infrastructure 
machines can understand the new arch.

[ Regression Potential ]
This is effectively a 1-line addition to a lookup table (and a twiddle of a 
testsuite to match), so the regression potential is basically nil.

[ Test Case ]
Check that the output of "dpkg-architecture -ariscv64" matches the output of 
same on bionic and up.

** Affects: dpkg (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: dpkg (Ubuntu Xenial)
 Importance: Undecided
 Assignee: Adam Conrad (adconrad)
 Status: In Progress

** Affects: dpkg (Ubuntu Bionic)
 Importance: Undecided
 Status: Fix Released

** Affects: dpkg (Ubuntu Eoan)
 Importance: Undecided
 Status: Fix Released

** Affects: dpkg (Ubuntu Focal)
 Importance: Undecided
 Status: Fix Released

** Also affects: dpkg (Ubuntu Focal)
   Importance: Undecided
   Status: New

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

** Also affects: dpkg (Ubuntu Eoan)
   Importance: Undecided
   Status: New

** Also affects: dpkg (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: dpkg (Ubuntu Bionic)
   Status: New => Fix Released

** Changed in: dpkg (Ubuntu Eoan)
   Status: New => Fix Released

** Changed in: dpkg (Ubuntu Focal)
   Status: New => Fix Released

** Changed in: dpkg (Ubuntu Xenial)
 Assignee: (unassigned) => Adam Conrad (adconrad)

** Changed in: dpkg (Ubuntu Xenial)
   Status: New => In Progress

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

Title:
  [SRU] Add riscv64 support to cputable for xenial

Status in dpkg package in Ubuntu:
  Fix Released
Status in dpkg source package in Xenial:
  In Progress
Status in dpkg source package in Bionic:
  Fix Released
Status in dpkg source package in Eoan:
  Fix Released
Status in dpkg source package in Focal:
  Fix Released

Bug description:
  [ Justification ]
  Much like we did for arm64 in 
https://launchpad.net/ubuntu/+source/dpkg/1.16.1.2ubuntu7.1 and for ppc64el in 
https://launchpad.net/ubuntu/+source/dpkg/1.16.1.2ubuntu7.2, we need to add 
riscv64 support for xenial (and up) so dpkg running on LP infrastructure 
machines can understand the new arch.

  [ Regression Potential ]
  This is effectively a 1-line addition to a lookup table (and a twiddle of a 
testsuite to match), so the regression potential is basically nil.

  [ Test Case ]
  Check that the output of "dpkg-architecture -ariscv64" matches the output of 
same on bionic and up.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1856369/+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 1844155] Re: arm64: sigaltstack fails with MINSIGSTKSZ for 32-bit processes

[Adam Conrad]

With previous xenial kernels:

XFAIL: nptl/tst-signal6
XFAIL: nptl/tst-thread-exit-clobber
XFAIL: signal/tst-minsigstksz-1
XFAIL: signal/tst-minsigstksz-2
XFAIL: signal/tst-minsigstksz-3
XFAIL: signal/tst-minsigstksz-3a
XFAIL: signal/tst-minsigstksz-4
XFAIL: support/tst-xsigstack

With the kernel in xenial-proposed:

XPASS: nptl/tst-signal6
XPASS: nptl/tst-thread-exit-clobber
XPASS: signal/tst-minsigstksz-1
XPASS: signal/tst-minsigstksz-2
XPASS: signal/tst-minsigstksz-3
XPASS: signal/tst-minsigstksz-3a
XPASS: signal/tst-minsigstksz-4
XPASS: support/tst-xsigstack

I declare this a resounding success and will adjust the tags
accordingly.

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

** Changed in: linux (Ubuntu)
   Status: Confirmed => 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/1844155

Title:
  arm64: sigaltstack fails with MINSIGSTKSZ for 32-bit processes

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed
Status in linux package in Debian:
  Fix Released

Bug description:
  [Impact]

  The arm64 kernel allows one to run aarch32 processes on an aarch64
  processor, using the standard 32/64-bit syscall compatibility. However
  this compat layer does not correctly validate the arguments of the
  sigaltstack syscall which can result in process failures.

  [Test Case]

  The simple reproducer from https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=904385 triggers a memory allocation error with
  the current Xenial 4.4 kernel.

  [Fix]

  Backport the following two upstream commits:
  24951465cbd2 arm64: compat: Provide definition for COMPAT_SIGMINSTKSZ
  22839869f21a signal: Introduce COMPAT_SIGMINSTKSZ for use in 
compat_sys_sigaltstack

  With these two commits, the reproducer no longer fails.

  [Regression Potential]

  Low. the modifications are trivial and the two patches have been in
  upstream for quite a while.

  [Original Description]

  This seems to have been fixed in 4.15 (finally), but is still an issue
  in the 4.4 kernel used on our builders, and possibly others as well
  (needs investigation).

  The original Debian bug report linked has more info, as well as the
  patchset on lkml at https://lkml.org/lkml/2018/7/25/409

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1844155/+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 1840686] Re: Xenial images won't reboot if disk size is > 2TB when using GPT

[Adam Conrad]

** Package changed: grub (Ubuntu) => grub2 (Ubuntu)

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

Title:
  Xenial images won't reboot if disk size is > 2TB when using GPT

Status in cloud-init:
  Won't Fix
Status in grub2 package in Ubuntu:
  Fix Released
Status in grub2-signed package in Ubuntu:
  Fix Released
Status in grub2 source package in Xenial:
  In Progress

Bug description:
  [Impact]

  On Xenial images which use GPT instead of MBR to enable efi based
  booting, there is an issue where after booting an instance that has a
  disk size of 2049 GB or higher, we hang on the next subsequent boot
  (Logs indicate it hanging on "Booting Hard Disk 0").

  This is a problem in grub2 where the system would become unbootable
  after ext* online resize if no resize_inode was created at ext* format
  time.

  [Test Case]

  To reproduce:

  1) Create an image with a disk size of 3072 GB using a serial that has
  GPT:

  gcloud compute instances create test-3072-xenial --image daily-
  ubuntu-1604-xenial-v20190731 --image-project ubuntu-os-cloud-devel
  --boot-disk-size 3072

  2) Reboot the instance

  The instance will hang on reboot and you cannot connect. If you go to
  GCP console and select Logs > Serial port 1 (console), you will see
  the boot process has stopped at "Booting Hard Disk 0".

  I have built a test package, which is available here:

  https://launchpad.net/~mruffell/+archive/ubuntu/lp1840686-test

  If you do step 1) but do not reboot, and instead add the PPA, install
  the new grub like so:

  1) gcloud compute instances create test-3072-xenial --image 
daily-ubuntu-1604-xenial-v20190731 --image-project ubuntu-os-cloud-devel 
--boot-disk-size 3072
  2) sudo add-apt-repository ppa:mruffell/lp1840686-test
  3) sudo apt-get update
  4) sudo apt remove grub-common grub-efi-amd64 grub-efi-amd64-bin 
grub-efi-amd64-signed grub-pc-bin grub2-common
  5) sudo apt install grub-common grub-efi-amd64 grub-efi-amd64-bin grub-pc-bin 
grub2-common
  6) sudo grub-install /dev/sda
  7) sudo reboot

  The instance will boot successfully and you will be able to connect.

  Note, we must use "daily-ubuntu-1604-xenial-v20190731" as the image,
  as it is enabled for GPT and efi. GCP was reverted back to MBR and
  bios booting because of this bug, so the latest images will not
  reproduce the problem.

  [Regression Potential]

  Grub is a core package and every care must be taken in order to not
  introduce any regressions.

  The commit is present in B, D, E and F, and is considered well tested
  and widely adopted by the community.

  The commit comes with its own testcase, to test the ext4_metabg fix.

  The changes are localised to ext* based filesystems, although since
  they are the most popular family of filesystems used by the community,
  this does not reduce risk of breakage by much.

  If a regression were to happen, a regression would have a large
  impact, and in the worst case, can lead to unbootable systems and data
  loss for users who are not technical enough to reinstall grub from a
  working package inside the broken system chroot.

  [Other Info]

  In comment #4, Sultan identifies the fix as:

  commit e20aa39ea4298011ba716087713cff26c6c52006
  Author: Vladimir Serbinenko 
  Date:   Mon Feb 16 20:53:26 2015 +0100
  Subject: ext2: Support META_BG.

  This commit is from upstream grub2, and can be found here:

  
https://git.savannah.gnu.org/cgit/grub.git/commit/?id=e20aa39ea4298011ba716087713cff26c6c52006

  Looking at when this was merged:

  $ git describe --contains e20aa39ea4298011ba716087713cff26c6c52006
  2.02-beta3~429

  This commit is present in B, D, E and F, leaving X as the only version
  needing an SRU.

  The commit cleanly cherry picks to X, because the delta from
  2.02~beta2-36ubuntu3.22 to 2.02-beta3~429 is small.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1840686/+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 1754671] Re: Full-tunnel VPN DNS leakage regression

[Adam Conrad]

The original bug report was about a regression in 16.04 with the dnsmasq
integration.  While I'm glad this got the ball rolling on the bionic
networkd integration, let's not forget that we broke xenial?  Added a
xenial task for network-manager accordingly.

** Also affects: network-manager (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

** Changed in: systemd (Ubuntu Xenial)
   Status: New => Invalid

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

Title:
  Full-tunnel VPN DNS leakage regression

Status in NetworkManager:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  New
Status in systemd source package in Xenial:
  Invalid
Status in network-manager source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Triaged

Bug description:
  [Impact]
  When using a VPN the DNS requests might still be sent to a DNS server outside 
the VPN when they should not

  [Test case]
  1) Set up a VPN with split tunneling:
a) Configure VPN normally (set up remote host, any ports and options needed 
for the VPN to work)
b) Under the IPv4 tab: enable "Use this connection only for the resources 
on its network".
c) Under the IPv6 tab: enable "Use this connection only for the resources 
on its network".

  2) Connect to the VPN.

  3) Run 'systemd-resolve --status'; note the DNS servers configured:
a) For the VPN; under a separate link (probably tun0), note down the IP of 
the DNS server(s). Also note the name of the interface (link).
b) For the "main" connection; under the link for your ethernet or wireless 
devices (wl*, en*, whatever it may be), note down the IP of the DNS server(s). 
Also note the name of the interface (link).

  4) In a separate terminal, run 'sudo tcpdump -ni 
  port 53'; let it run.

  5) In a separate terminal, run 'sudo tcpdump -ni 
  port 53'; let it run.

  6) In yet another terminal, issue name resolution requests using dig:
a) For a name known to be reachable via the public network:
   'dig www.yahoo.com'
b) For a name known to be reachable only via the VPN:
   'dig '

  7) Check the output of each terminal running tcpdump. When requesting
  the public name, traffic can go through either. When requesting the
  "private" name (behind the VPN), traffic should only be going through
  the interface for the VPN. Additionally, ensure the IP receiving the
  requests for the VPN name is indeed the IP address noted above for the
  VPN's DNS server.

  If you see no traffic showing in tcpdump output when requesting a
  name, it may be because it is cached by systemd-resolved. Use a
  different name you have not tried before.

  
  [Regression potential]
  The code change the handling of DNS servers when using a VPN, we should check 
that name resolution still work whne using a VPN in different configurations

  -

  In 16.04 the NetworkManager package used to carry this patch:
  
http://bazaar.launchpad.net/~network-manager/network-manager/ubuntu/view/head:/debian/patches/Filter-DNS-servers-to-add-to-dnsmasq-based-on-availa.patch

  It fixed the DNS setup so that when I'm on the VPN, I am not sending
  unencrypted DNS queries to the (potentially hostile) local
  nameservers.

  This patch disappeared in an update. I think it was present in
  1.2.2-0ubuntu0.16.04.4 but was dropped some time later.

  This security bug exists upstream too: 
https://bugzilla.gnome.org/show_bug.cgi?id=746422
  It's not a *regression* there though, as they didn't fix it yet 
(unfortunately!)

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1754671/+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 1822270] Re: Debconf readline frontend does not show options

[Adam Conrad]

** Changed in: debconf (Ubuntu Eoan)
   Status: Confirmed => 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/1822270

Title:
  Debconf readline frontend does not show options

Status in debconf package in Ubuntu:
  Fix Released
Status in debconf source package in Xenial:
  Confirmed
Status in debconf source package in Bionic:
  Confirmed
Status in debconf source package in Cosmic:
  Confirmed
Status in debconf source package in Disco:
  Confirmed
Status in debconf source package in Eoan:
  Fix Released
Status in debconf package in Debian:
  Fix Committed

Bug description:
  [Impact]
  debconf prompts the user for input before displaying options

  [Description]
  When upgrading packages with apt or dpkg, debconf scripts are ran through 
'run-parts' with the '--report' flag. This causes script output to be handled 
through pipes set up by run-parts, and buffers output from maintainer scripts 
nicely for formatting.

  If debconf makes use of the readline frontend, any prompts will bypass
  the run-parts buffers and be displayed directly to /dev/tty. This
  generally causes the prompt to be displayed before the user gets any
  of the available options for it, and printing will block until the
  user inputs a valid option.

  Upstream commit: https://salsa.debian.org/pkg-
  debconf/debconf/commit/48c5ce38cfd5

  [Test Case]
  1) Deploy a VM through e.g. uvt-kvm
  $ uvt-kvm create disco release=disco

  2) Remove the whiptail package to force the readline frontend in debconf
  root@disco:~# apt remove --purge whiptail -y

  3) Install grub-legacy-ec2 and prepare /boot/grub/menu.lst for an upgrade 
through run-parts
  root@disco:~# apt update && apt install -y grub-legacy-ec2
  root@disco:~# rm -f /boot/grub/menu.lst*
  root@disco:~# touch -d "4 years ago" /boot/grub/menu.lst

  4) Invoke run-parts as in a kernel upgrade (kernel version doesn't matter, we 
just need it to think menu.lst needs an upgrade)
  root@disco:~# run-parts --exit-on-error --arg=5.0.0 /etc/kernel/postinst.d 
--report
  ...
  /etc/kernel/postinst.d/x-grub-legacy-ec2:
  debconf: unable to initialize frontend: Dialog
  debconf: (No usable dialog-like program is installed, so the dialog based 
frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 
76.)
  debconf: falling back to frontend: Readline
  Searching for GRUB installation directory ... found: /boot/grub
  Searching for default file ... found: /boot/grub/default
  Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst
  Searching for splash image ... none found, skipping ...
  What would you like to do about menu.lst?

  The "What would you like to do about menu.lst?" prompt will block
  until the user enter a valid option, even though it's being displayed
  before the available options.

  [Regression Potential]
  We could hit regressions if changing debconf's printing to /dev/tty is 
expected by other programs. The changes are needed only in the readline 
frontend, so that would minimize impact of any possible regressions. The fixes 
will be thoroughly tested with autopkgtest and use-case scenarios.

  # # # #

  [Original Description]
  When upgrading the kernel on a recent Bionic minimal image, the user is 
prompted to resolve a conflict in the file /boot/grub/menu.lst.

  The minimal images do not have dialog/whiptail installed, so debconf
  falls back to using the readline frontend.

  The user sees the prompt: "What would you like to do about menu.lst?"
  but is not presented with the list of options to choose from.

  If a valid option is typed in, debconf will continue processing
  correctly and the list of options  appears on the screen. See also
  https://pastebin.ubuntu.com/p/8xvSn88SKG/

  STEPS TO REPRODUCE:

  Launch the minimal Bionic image with serial 20190212 http://cloud-
  images.ubuntu.com/minimal/releases/bionic/release-20190212/ubuntu-18.04
  -minimal-cloudimg-amd64.img

  for example via multipass and run `apt-get update` and `apt-get dist-
  upgrade`.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1822270/+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 1800610] Re: [SRU] minimize number of manually installed packages

[Adam Conrad]

I initially marked this Won't Fix for xenial, as there will be no more
desktop or server images produced for xenial, but if this also has
benefit on cloud images, we might want to look into it for that.

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

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

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

Title:
  [SRU] minimize number of manually installed packages

Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in livecd-rootfs source package in Xenial:
  Triaged
Status in livecd-rootfs source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  Releases prior to cosmic mark almost all packages manually installed, meaning 
that obsolete packages are not autoremoved when they should. We fixed this in 
cosmic, in trunk r1695, by including a new script that marks as automatically 
installed all dependencies of manually-installed metapackages.

  [Test case]
  Run a build and check in the log that some packages are visited by the script 
in more than one iterations. 

  [Regression potential]
  First of all, this does not change existing installations; only new ones. The 
change can cause packages to be autoremoved that were not autoremoved before 
after performing a package management operation, or dependency change in 
packages.

  The change is essentially safe: Since we only mark dependencies of
  packages in the section "metapackages", and since those receive
  special treatment by apt:

  1. removal due to dependencies/conflicts: the manual bit transfers from the 
meta to its deps
  2. explicit removal (apt remove meta): meta and its dependencies are removed

  It is not possible to accidentally uninstall the entire metapackage
  with its dependencies.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1800610/+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 1648873] Re: Ubuntu 16.10 netboot install fails with "Oops: Exception in kernel mode, sig: 5 [#1] " (lpfc)

[Adam Conrad]

** Changed in: debian-installer (Ubuntu Xenial)
   Status: New => Fix Released

** Changed in: debian-installer (Ubuntu Yakkety)
   Status: New => Fix Released

** Changed in: debian-installer (Ubuntu)
   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/1648873

Title:
  Ubuntu 16.10 netboot install fails with "Oops: Exception in kernel
  mode, sig: 5 [#1] " (lpfc)

Status in debian-installer package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in debian-installer source package in Xenial:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in debian-installer source package in Yakkety:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  == Comment: #33 - Mauricio Faria De Oliveira - 2016-12-09 06:49:57 ==

  Hi Canonical,

  Can you please apply this patch [1] to 16.10 and 16.04.x HWE (4.8) ?
  It's fixes a regression introduced in 4.8.

  As you can see, it's in the SCSI maintainer (James Bottomley)'s
  'fixes' branch, but didn't make 4.9-rc8 (maybe he considered it late
  for this one).

  We have installer, boot, and post-boot problems due to this one.
  It'd be good if the netboot images for 16.04.x HWE kernel can get it too.

  Thank you,

  [1] scsi: lpfc: fix oops/BUG in lpfc_sli_ringtxcmpl_put() 
  
http://git.kernel.org/cgit/linux/kernel/git/jejb/scsi.git/commit/?h=fixes=2319f847a8910cff1d46c9b66aa1dd7cc3e836a9

  Historical context:

  == Comment: #0 - HARSHA THYAGARAJA - 2016-11-21 02:39:35 ==
  ---Problem Description---
  Ubuntu 16.10 netboot install fails with "Oops: Exception in kernel mode. " 
(kernel: 4.8.0-27)
   
  Machine Type = Power8 baremetal  
   
  ---boot type---
  QEMU direct boot kernel/initrd
   
  ---Kernel cmdline used to launch install---
  On a Power8 server,  Using kernel and initrd images, 

  netcfg/disable_dhcp=true netcfg/confirm_static=true 
netcfg/choose_interface=98:BE:94:00:4C:68 netcfg/get_ipaddress=9.47.67.159/20 
netcfg/get_gateway=9.47.79.254 netcfg/get_nameservers=
   
  ---Install repository type---
  Internet repository
   
  ---Install repository Location---
  
http://ports.ubuntu.com/ubuntu-ports/dists/yakkety/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/
   
  ---Point of failure---
  Other failure during installation (stage 1)

  == Comment: #1 - HARSHA THYAGARAJA - 2016-11-21 02:41:54 ==
  The netboot install fails and Call traces are seen at the Disk detection step.

  == Comment: #8 - Mauricio Faria De Oliveira - 2016-11-21 15:58:25 ==
  Finally got it.

  The assembly offset/code + the trap signal is due to this BUG_ON(),
  and the second condition triggered the trap.

  Checking why piocb is not NULL but piocb->vport is NULL.
  This might have happened in the lpfc_linkdown_port() path, in the stack trace.

  Would need a more readable console log (ie, dmesg, as requested in
  comments 5, 3) to help understanding it.

  --

  static int
  lpfc_sli_ringtxcmpl_put(struct lpfc_hba *phba, struct lpfc_sli_ring *pring,
  struct lpfc_iocbq *piocb)
  {
  lockdep_assert_held(>hbalock);

  BUG_ON(!piocb || !piocb->vport);
  <...>
  }

  [  226.147886] NIP [db7324c0]
  lpfc_sli_ringtxcmpl_put+0x48/0x120 [lpfc]

  0x2478 + 0x48 = 0x24c0 (tdnei; trap doubleword not equal immediate)

  2478 :
  <...>
  2498:   78 2b bf 7c mr  r31,r5 // r31 is *piocb (r5 is the 
3rd function parameter)
  249c:   78 1b 7d 7c mr  r29,r3
  24a0:   78 23 9e 7c mr  r30,r4
  24a4:   01 00 00 48 bl  24a4  
// probably converted at module load time to the call lockdep_assert_held()
  24a8:   00 00 00 60 nop
  24ac:   00 00 bf 2f cmpdi   cr7,r31,0 // compare piocb with 0. 
checking for NULL.
  24b0:   70 00 9e 41 beq cr7,2520 
 // if equal to zero, branch out. done w/ the  
former part of the OR check.
  24b4:   e8 00 3f e9 ld  r9,232(r31) // an offset of piocb. 
probably piocb->vport in the bug_on
  24b8:   74 00 29 7d cntlzd  r9,r9 // count leading zeroes. if r59 
is null (0), leading zeroes is 64 (binary: 0100_, bit 6 is 1, and 6 LSbs 
[bits 5-0] are 0)
  24bc:   82 d1 29 79 rldicl  r9,r9,58,6 // rotate left 58 (ie, 
those 6 LSbs are now MSbs, and that bit 6 from 64 was rotated in the register 
and is now bit 0, the LSb), now AND the 6 MSbs w/ 0-bits, and the all lower 
bits with 1-bits (ie, save the LSb). 
  24c0:   00 00 09 0b tdnei   r9,0 // trap if not equal to zero. 
(ie, the whole r9 was zero, with 64 leading/consecutive zeroes, then bit 6 is 
1, it becomes bit 0.. and since bit 0 is now 1, r9 is thus non-zero, and the 
trap triggers.)this 

[Group.of.nepali.translators] [Bug 1812313] Re: SKX Gold 6129, Platinum 8168 cpu frequency throttling issue during the benchmark

[Adam Conrad]

** Also affects: glibc (Ubuntu)
   Importance: Undecided
   Status: New

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

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

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

** Changed in: glibc (Ubuntu Xenial)
 Assignee: (unassigned) => Adam Conrad (adconrad)

** Changed in: glibc (Ubuntu Xenial)
   Status: New => In Progress

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

Title:
  SKX Gold 6129,Platinum 8168  cpu frequency throttling issue during the
  benchmark

Status in GLibC:
  Fix Released
Status in intel:
  Fix Committed
Status in glibc package in Ubuntu:
  Fix Released
Status in glibc source package in Xenial:
  In Progress

Bug description:
  Description:

  This is a known issue. Glibc fix is available:
  glibc 2.23 branch more than a year ago:
  
https://sourceware.org/git/?p=glibc.git;a=shortlog;h=refs/heads/release/2.23/master
  The specific commit for glibc 2.23 is
  
https://sourceware.org/git/?p=glibc.git;a=commit;h=26d289bb92b6d1125536644f607c73617463477d

  
  History:
  in Ubuntu 16.04.5 ,If the benchmark tools is dynamic linked, and in the 
main loop, there are external function call to the dynamic lib, like dhrystone, 
whetstone, sysbench… During the benchmark running, CPU core max frequency is 
always 2.2Ghz(Gold 6129 , max turbo should be 3.3Ghz). Even the test is single 
thread test, we got the same result. In our lab, we found with our Gold 6129 
chipset, cpu is always at 1.5Ghz while benchmarking. 
  In Ubuntu 18.04.1 (glibc 2.27),everything works fine. No freq limit. Try 
to upgrade the glibc on Ubuntu 16.04.5 from 2.23 to 2.27, the Gold 6129 works 
fine, can reach 3.3Ghz. There is the same issue on Platinum 8168, on Ubuntu 
16.04.5(glibc2.23),  cpu max frequency during benchmark is about 3Ghz（Platinum 
8168 ,1~2 cores max turbo should be 3.7Ghz). Xeon Gold 6129 and Platinum 8168 
are major Skylake platform

  Target Release: 16.04.5

To manage notifications about this bug go to:
https://bugs.launchpad.net/glibc/+bug/1812313/+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 1571403] Re: lz4 fails to run the tests on s390x (glibc-2.23 related?)

[Adam Conrad]

** Changed in: glibc (Ubuntu)
   Status: New => Invalid

** Changed in: glibc (Ubuntu Xenial)
   Status: New => Invalid

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

Title:
  lz4 fails to run the tests on s390x (glibc-2.23 related?)

Status in glibc package in Ubuntu:
  Invalid
Status in lz4 package in Ubuntu:
  Fix Released
Status in glibc source package in Xenial:
  Invalid
Status in lz4 source package in Xenial:
  Confirmed

Bug description:
  seen in the test rebuild:

  https://launchpad.net/ubuntu/+archive/test-
  rebuild-20160401/+build/9483622

  60658   
  60679   
  60698   
  60724   *** Error in `./fuzzer': double free or corruption (!prev): 
0x02aa181a4090 ***
  === Backtrace: =
  /lib/s390x-linux-gnu/libc.so.6(+0x791ba)[0x3ffaf7791ba]
  /lib/s390x-linux-gnu/libc.so.6(+0x7f62e)[0x3ffaf77f62e]
  /lib/s390x-linux-gnu/libc.so.6(+0x80010)[0x3ffaf780010]
  ./fuzzer(+0xed86)[0x2aa1490ed86]
  ./fuzzer(main+0x15c)[0x2aa14900e84]
  /lib/s390x-linux-gnu/libc.so.6(__libc_start_main+0x10e)[0x3ffaf722ece]
  ./fuzzer(+0x145c)[0x2aa1490145c]
  === Memory map: 
  2aa1490-2aa14914000 r-xp  fc:00 1443097  
/<>/programs/fuzzer
  2aa14914000-2aa14915000 r--p 00013000 fc:00 1443097  
/<>/programs/fuzzer
  2aa14915000-2aa14916000 rw-p 00014000 fc:00 1443097  
/<>/programs/fuzzer
  2aa1815f000-2aa1820d000 rw-p  00:00 0
[heap]
  3ffa800-3ffa8021000 rw-p  00:00 0 
  3ffa8021000-3ffac00 ---p  00:00 0 
  3ffaf68-3ffaf69 r-xp  fc:00 1180835  
/lib/s390x-linux-gnu/libgcc_s.so.1
  3ffaf69-3ffaf691000 rw-p f000 fc:00 1180835  
/lib/s390x-linux-gnu/libgcc_s.so.1
  3ffaf70-3ffaf885000 r-xp  fc:00 1183401  
/lib/s390x-linux-gnu/libc-2.23.so
  3ffaf885000-3ffaf889000 r--p 00184000 fc:00 1183401  
/lib/s390x-linux-gnu/libc-2.23.so
  3ffaf889000-3ffaf88b000 rw-p 00188000 fc:00 1183401  
/lib/s390x-linux-gnu/libc-2.23.so
  3ffaf88b000-3ffaf88f000 rw-p  00:00 0 
  3ffaf98-3ffaf9a4000 r-xp  fc:00 1183402  
/lib/s390x-linux-gnu/ld-2.23.so
  3ffaf9a4000-3ffaf9a5000 r--p 00023000 fc:00 1183402  
/lib/s390x-linux-gnu/ld-2.23.so
  3ffaf9a5000-3ffaf9a7000 rw-p 00024000 fc:00 1183402  
/lib/s390x-linux-gnu/ld-2.23.so
  3ffaf9f5000-3ffaf9fe000 rw-p  00:00 0 
  3ffaf9fe000-3ffafa0 r-xp  00:00 0
[vdso]
  3ffefabc000-3ffefb8 rw-p  00:00 0
[stack]
  All unit tests completed successfully 

60747 /  60747   - all tests completed successfully 
  compression ratio: 55.197%
  HC compression ratio: 51.173%
  ratio with dict: 44.457%
  Makefile:277: recipe for target 'test-fuzzer' failed
  make[3]: *** [test-fuzzer] Aborted
  make[3]: Leaving directory '/<>/programs'
  Makefile:98: recipe for target 'test' failed
  make[2]: *** [test] Error 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1571403/+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 1756209] Re: i386 implementation of memmove broken since glibc 2.21

[Adam Conrad]

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

** Changed in: glibc (Ubuntu)
   Status: Confirmed => 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/1756209

Title:
  i386 implementation of memmove broken since glibc 2.21

Status in glibc package in Ubuntu:
  Fix Released
Status in glibc source package in Xenial:
  New
Status in glibc source package in Bionic:
  Confirmed

Bug description:
  In glibc 2.21 they optimized i386 memcpy:

  https://sourceware.org/ml/libc-alpha/2015-02/msg00119.html

  The implementation contained a bug which causes memmove to break when
  crossing the 2GB threshold.

  This has been filed with glibc here (filed by someone else, but I have
  requested an update from them as well):

  https://sourceware.org/bugzilla/show_bug.cgi?id=22644

  Unfortunately they have not yet taken action on this bug, however I
  want to bring it to your attention in the hope that it can be patched
  into all current Ubuntu releases as soon as possible. I hope this is
  not improper procedure. Both myself and another (see comment 1 in the
  glibc bug report) have tested the patch provided in the above glibc
  bug report and it does appear to fix the problem, however I don't know
  what the procedure is for getting it properly confirmed/tested and
  merged into Ubuntu.

  As requested in the guidelines:

  1) We are using:
  Description:Ubuntu 16.04.4 LTS
  Release:16.04

  2)
  libc6:i386:
Installed: 2.23-0ubuntu10

  However as stated above this has been present since libc6:i386 2.21
  and affects Ubuntu 15.04 onward. (I have actually tested this as well.
  15.04 conveniently used both glibc 2.19 and 2.21 so it was a good test
  platform when I was initially attempting to track down the problem.)

  3) What we expected to happen:
  memmove should move data within the entire valid address space without 
segfaulting or corrupting memory.

  4) What happened instead:
  When memmove attempts to move data crossing the 2GB threshold it either 
segfaults or causes memory corruption.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1756209/+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 1807448] [NEW] [SRU] Patch power9-001.diff breaks IFUNC on ELFv1

[Adam Conrad]

Public bug reported:

[ SRU Justification ]
As per comment #4 in 
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1655181 the undefined 
weak fix should not have been backported because it breaks IFUNC on ELFv1, and 
can't be fixed without a much larger backport from 2.27.  This patch breaks 
glibc builds on PPC64 ELFv1.

See also https://sourceware.org/bugzilla/show_bug.cgi?id=20472

I will be pushing this upload via the ubuntu-security-proposed PPA, as
this regression also exists in security and if we ever want to do a
glibc security update, we need the fix there as well.

[ Test Case ]
See that glibc now builds on powerpc in xenial, when it didn't with the 
previous version.

[ Regression Potential ]
We lived fine without this patch before, and will do again in the future.  
Removing it fixes ELFv1 glibc builds (and presumably anything else that uses 
IFUNC), but should have no other obvious impact.

** Affects: binutils (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: binutils (Ubuntu Xenial)
 Importance: Undecided
 Assignee: Adam Conrad (adconrad)
 Status: In Progress

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

** Changed in: binutils (Ubuntu)
   Status: New => Invalid

** Changed in: binutils (Ubuntu Xenial)
 Assignee: (unassigned) => Adam Conrad (adconrad)

** Changed in: binutils (Ubuntu Xenial)
   Status: New => In Progress

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

Title:
  [SRU] Patch power9-001.diff breaks IFUNC on ELFv1

Status in binutils package in Ubuntu:
  Invalid
Status in binutils source package in Xenial:
  In Progress

Bug description:
  [ SRU Justification ]
  As per comment #4 in 
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1655181 the undefined 
weak fix should not have been backported because it breaks IFUNC on ELFv1, and 
can't be fixed without a much larger backport from 2.27.  This patch breaks 
glibc builds on PPC64 ELFv1.

  See also https://sourceware.org/bugzilla/show_bug.cgi?id=20472

  I will be pushing this upload via the ubuntu-security-proposed PPA, as
  this regression also exists in security and if we ever want to do a
  glibc security update, we need the fix there as well.

  [ Test Case ]
  See that glibc now builds on powerpc in xenial, when it didn't with the 
previous version.

  [ Regression Potential ]
  We lived fine without this patch before, and will do again in the future.  
Removing it fixes ELFv1 glibc builds (and presumably anything else that uses 
IFUNC), but should have no other obvious impact.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1807448/+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 1800656] Re: Add Ubuntu 19.04 Disco Dingo

[Adam Conrad]

Precise is taken care of via the ESM archive.

** Changed in: distro-info-data (Ubuntu Precise)
   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/1800656

Title:
  Add Ubuntu 19.04 Disco Dingo

Status in distro-info-data package in Ubuntu:
  New
Status in distro-info-data source package in Precise:
  Fix Released
Status in distro-info-data source package in Trusty:
  Fix Committed
Status in distro-info-data source package in Xenial:
  Fix Committed
Status in distro-info-data source package in Bionic:
  Fix Committed
Status in distro-info-data source package in Cosmic:
  Fix Committed
Status in distro-info-data source package in Disco:
  New

Bug description:
  We have a name, at last

  == SRU Impact ==

  Several tools rely on distro-info to tell them which releases are available.
  This package just contains data, with no format changes.

  == Regression Potential ==

  Minimal, if we are only adding new entries. We do this every release.

  == Test Case ==
  "ubuntu-distro-info -d" should return "disco" not an error that the data is 
out of date.

  "ubuntu-distro-info -df" should name the release in full: Ubuntu 19.04
  "Disco Dingo"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/distro-info-data/+bug/1800656/+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 1799773] Re: Accelerate the build: Drop unused checksum generation

[Adam Conrad]

** Also affects: livecd-rootfs (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: livecd-rootfs (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: livecd-rootfs (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Changed in: livecd-rootfs (Ubuntu Cosmic)
   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/1799773

Title:
  Accelerate the build: Drop unused checksum generation

Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in livecd-rootfs source package in Xenial:
  New
Status in livecd-rootfs source package in Bionic:
  New
Status in livecd-rootfs source package in Cosmic:
  Fix Released

Bug description:
  [Impact]

   * Image builds take time
   * Some of the time is spent computing checksums
   * Those checksums are never used
   * Time and energy is wasted
   * build/(md5|sha256)sum.txt is not used by livecd-rootfs and not exposed by 
launchpad-buildd

  [Test Case]

   * Build images
   * Disable checksums
   * Build images
   * Ensure image deliverables are unchanged

  [Regression Potential]

   * Someone was using the checksums outside of launchpad-buildd; because 
launchpad-buildd doesn't present those artifacts
   * The checksums are included beside the squashfs in live-build ISOs but none 
of our projects use live-build to build ISOs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1799773/+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 1779815] Please test proposed package

[Adam Conrad]

Hello bugproxy, or anyone else affected,

Accepted debian-installer into xenial-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/debian-
installer/20101020ubuntu451.25 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: debian-installer (Ubuntu)
   Status: Confirmed => 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/1779815

Title:
  [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI
  based SAS/md raid device

Status in The Ubuntu-power-systems project:
  In Progress
Status in debian-installer package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Committed
Status in debian-installer source package in Xenial:
  Fix Committed
Status in systemd source package in Xenial:
  Fix Committed
Status in debian-installer source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  == Comment: #0 - ABDUL HALEEM  - 2018-07-02 03:55:33 ==
  ---Problem Description---
  Ubuntu 18.04.01 ppc64el installer does not detect LSI3008  base SAS disks / 
MD RAID devices 

  Used 20101020ubuntu543 version to install
  
http://ports.ubuntu.com/ubuntu-ports/dists/bionic/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/

  Contact Information = abdha...@in.ibm.com 
   
  ---uname output---
  Linux ltc-boston21 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 
2018 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = BostonLC
   
  ---boot type---
  Network boot
   

  Installer fails to detect the LSI SAS disks / RAID MD device

  ===console error log===

?? [!!] Partition disks ???
? ?
? Note that all data on the disk you select will be erased, but not   ?
? before you have confirmed that you really want to make the changes. ?
? ?
? Select disk to partition:   ?
? ?
? /dev/nvme0n1 - 491.5 GB NVMe Device ?
? /dev/nvme1n1 - 98.3 GB NVMe Device  ?
? ?
??
? ?
???



   moves;  selects;  activates buttons

  
  To make sure it detects the disks I had to 
  
  
  Detect disks-->Guided partitioning--> Guided - use entire disk 

  
?? [!!] Partition disks ???
? ?
? Note that all data on the disk you select will be erased, but not   ?
? before you have confirmed that you really want to make the changes. ?
? ?
? Select disk to partition:   ?
? ?
?  /dev/nvme0n1 - 491.5 GB NVMe Device?
?  /dev/nvme1n1 - 98.3 GB NVMe Device ?
?  SCSI3 (0,0,0) (sda) - 4.0 TB SEAGATE ST4000NM0075  ?
?  SCSI3 (1,0,0) (sdb) - 199.9 GB LSI Logical Volume  ?
?  SCSI3 (0,2,0) (sdc) - 2.0 TB ATA ST2000NM0125-1YZ  ?
? ?
??
? 

[Group.of.nepali.translators] [Bug 1692876] Re: ubuntu-server ARM64 ISOs lack partition table with EFI System Partition

[Adam Conrad]

** Changed in: ubuntu-cdimage
   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/1692876

Title:
  ubuntu-server ARM64 ISOs lack partition table with EFI System
  Partition

Status in Ubuntu CD Images:
  Fix Released
Status in debian-installer package in Ubuntu:
  Fix Released
Status in debian-installer source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  On some arm64/efi platforms, the firmware will not be able to boot from an 
ISO dd'd to a USB stick.

  [Test Case]
  My test is to attach the ISO as an "HD/USB Image" to a Cavium CRB1S w/ AMI 
UEFI firmware using the BMC's Virtual Media. Note that the BMC requires that 
the file be renamed with a ".img" suffix.

  [Regression Risk]
  For d-i, this is aligning the xorriso boot options with the same ones now 
used to build the server ISO. Regression risk has been mitigated by testing on 
real hardware connected as both CD and disk images.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1692876/+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 1781036] Re: bionic amd64 netboot.tar.gz - bad permission on uncompressed file

[Adam Conrad]

** Also affects: debian-installer (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: debian-installer (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

Title:
  bionic amd64 netboot.tar.gz - bad permission on uncompressed file

Status in debian-installer package in Ubuntu:
  New
Status in debian-installer source package in Xenial:
  New
Status in debian-installer source package in Bionic:
  New

Bug description:
  I find that the permission on a file is not correct.

  Unpacking the tarball
  http://be.archive.ubuntu.com/ubuntu/dists/bionic/main/installer-
  amd64/current/images/netboot/netboot.tar.gz to prepare my TFTP server,
  I found that the permission on the file .../ubuntu-
  installer/amd64/linux is 600 instead of 644.

  This prevents the process to perform a PXE installation.

  FYI:
  TZ=utc ls -n ./netboot.tar.gz 
  -rw-r--r-- 1 xxx xxx 54820328 avr 25 21:23 ./netboot.tar.gz

  sha256sum ./netboot.tar.gz 
  5fe1e599ed7266abb39364b21c07870866b37f655d603c3b2191394a3e85ff39  
./netboot.tar.gz

  TZ=utc ls -n ./ubuntu-installer/amd64/linux 
  -rw--- 1 xxx xxx 8249080 avr 25 20:10 ./ubuntu-installer/amd64/linux

  sha256sum ./linux 
  beeab595bb361fa38f9eadac4bedff6082c2f7f06cb97507103a4316a291c0f5  ./linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1781036/+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 1779815] Re: [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI based SAS/md raid device

[Adam Conrad]

I've uploaded a fixed systemd to cosmic and bionic for this (xenial will
follow when I sort out the best way to backport the fix).  dannf should
be in a position to test this once a new d-i is built using the new
udev-udeb.

** Also affects: debian-installer (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: debian-installer (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

** Also affects: systemd (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux (Ubuntu Bionic)
   Status: New => Invalid

** Changed in: systemd (Ubuntu)
 Assignee: (unassigned) => Adam Conrad (adconrad)

** Changed in: systemd (Ubuntu Xenial)
 Assignee: (unassigned) => Adam Conrad (adconrad)

** Changed in: systemd (Ubuntu Bionic)
 Assignee: (unassigned) => Adam Conrad (adconrad)

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

Title:
  [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI
  based SAS/md raid device

Status in The Ubuntu-power-systems project:
  Triaged
Status in debian-installer package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  New
Status in debian-installer source package in Xenial:
  New
Status in linux source package in Xenial:
  Invalid
Status in systemd source package in Xenial:
  New
Status in debian-installer source package in Bionic:
  New
Status in linux source package in Bionic:
  Invalid
Status in systemd source package in Bionic:
  New

Bug description:
  == Comment: #0 - ABDUL HALEEM  - 2018-07-02 03:55:33 ==
  ---Problem Description---
  Ubuntu 18.04.01 ppc64el installer does not detect LSI3008  base SAS disks / 
MD RAID devices 

  Used 20101020ubuntu543 version to install
  
http://ports.ubuntu.com/ubuntu-ports/dists/bionic/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/

  Contact Information = abdha...@in.ibm.com 
   
  ---uname output---
  Linux ltc-boston21 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 
2018 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = BostonLC
   
  ---boot type---
  Network boot
   

  Installer fails to detect the LSI SAS disks / RAID MD device

  ===console error log===

?? [!!] Partition disks ???
? ?
? Note that all data on the disk you select will be erased, but not   ?
? before you have confirmed that you really want to make the changes. ?
? ?
? Select disk to partition:   ?
? ?
? /dev/nvme0n1 - 491.5 GB NVMe Device ?
? /dev/nvme1n1 - 98.3 GB NVMe Device  ?
? ?
??
? ?
???



   moves;  selects;  activates buttons

  
  To make sure it detects the disks I had to 
  
  
  Detect disks-->Guided partitioning--> Guided - use entire disk 

  
?? [!!] Partition disks ???
? ?
? Note that all data on the disk you select will be erased, but not   ?
? before you have confirmed that you really want to make the changes. ?
? ?
? Select disk to partition:   ?
? ?
?  /dev/nvme0n1 - 491.5 GB NVMe Device?
?  /dev/nvme1n1 - 98.3 GB NVMe Device ?
?  SCSI3 (0,0,0) (sda) - 4.0 TB SEAGATE ST4000NM0075  ?
?  SCSI3 (1,0,0) (sdb) - 199.9 GB LSI Logical Volume  ?
?  SCSI3 (0,2,0) (sdc) - 2.0 TB

[Group.of.nepali.translators] [Bug 1766727] Re: initramfs-tools exception during pm.DoInstall with do-release-upgrade from 16.04 to 18.04

[Adam Conrad]

** Changed in: initramfs-tools (Ubuntu Xenial)
   Status: New => Invalid

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

Title:
  initramfs-tools exception during pm.DoInstall with  do-release-upgrade
  from 16.04 to 18.04

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Committed
Status in s390-tools package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Invalid
Status in initramfs-tools source package in Xenial:
  Invalid
Status in linux source package in Xenial:
  New
Status in s390-tools source package in Xenial:
  Fix Released
Status in ubuntu-release-upgrader source package in Xenial:
  Invalid
Status in initramfs-tools source package in Bionic:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in s390-tools source package in Bionic:
  Fix Released
Status in ubuntu-release-upgrader source package in Bionic:
  Invalid

Bug description:
  [Impact]
  Upgrades of linux-image-generic-hwe-16.04-edge will fail to configure because 
the post-update script for zipl will fail.

  [Test Case]
  Upgrade linux-image-generic-hwe-16.04-edge from xenial to xenial-proposed on 
s390x.

  [Regression]
  zipl update on s390x might fail, causing the system to be unbootable.

  
  

  Upgrading from 16.04 to 18.04 using 'do-release-upgrade -d' results
  in:

  Errors were encountered while processing:
   initramfs-tools
  Exception during pm.DoInstall():  E:Sub-process /usr/bin/dpkg returned an 
error code (1)

  Could not install the upgrades

  The upgrade has aborted. Your system could be in an unusable state. A
  recovery will run now (dpkg --configure -a).

  ---

  Processing triggers for systemd (237-3ubuntu10) ...
  Processing triggers for initramfs-tools (0.130ubuntu3) ...
  update-initramfs: Generating /boot/initrd.img-4.4.0-121-generic
  Using config file '/etc/zipl.conf'
  Error: Ramdisk file '/boot/initrd.img' in section 'ubuntu': No such file or 
directory
  run-parts: /etc/initramfs/post-update.d//zz-zipl exited with return code 1
  dpkg: error processing package initramfs-tools (--configure):
   installed initramfs-tools package post-installation script subprocess 
returned error exit status 1
  Processing triggers for ca-certificates (20180409) ...
  Updating certificates in /etc/ssl/certs...
  0 added, 0 removed; done.
  Running hooks in /etc/ca-certificates/update.d...
  done.
  Processing triggers for dictionaries-common (1.27.2) ...
  Processing triggers for linux-image-4.15.0-19-generic (4.15.0-19.20) ...
  /etc/kernel/postinst.d/initramfs-tools:
  update-initramfs: Generating /boot/initrd.img-4.15.0-19-generic
  Using config file '/etc/zipl.conf'
  Building bootmap in '/boot'
  Building menu 'menu'
  Adding #1: IPL section 'ubuntu' (default)
  Adding #2: IPL section 'old'
  Preparing boot device: dasdb (0104).
  Done.
  /etc/kernel/postinst.d/zz-zipl:
  Using config file '/etc/zipl.conf'
  Building bootmap in '/boot'
  Building menu 'menu'
  Adding #1: IPL section 'ubuntu' (default)
  Adding #2: IPL section 'old'
  Preparing boot device: dasdb (0104).
  Done.
  Processing triggers for sgml-base (1.29) ...
  Processing triggers for resolvconf (1.79ubuntu10) ...
  Processing triggers for ureadahead (0.100.0-20) ...
  Errors were encountered while processing:
   initramfs-tools
  Log ended: 2018-04-24  13:12:40
  ---
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: s390x
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.15.0-19.20-generic 4.15.17
  Tags:  bionic
  Uname: Linux 4.15.0-19-generic s390x
  UpgradeStatus: Upgraded to bionic on 2018-04-24 (0 days ago)
  UserGroups: adm cdrom cpacfstats dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1766727/+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 1770004] Re: Update distro-info-data for cosmic

[Adam Conrad]

** Changed in: distro-info-data (Ubuntu Trusty)
   Status: New => Fix Released

** Changed in: distro-info-data (Ubuntu Xenial)
   Status: New => Fix Released

** Changed in: distro-info-data (Ubuntu Artful)
   Status: New => Fix Released

** Changed in: distro-info-data (Ubuntu Bionic)
   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/1770004

Title:
  Update distro-info-data for cosmic

Status in distro-info-data package in Ubuntu:
  Fix Released
Status in distro-info-data source package in Precise:
  Fix Released
Status in distro-info-data source package in Trusty:
  Fix Released
Status in distro-info-data source package in Xenial:
  Fix Released
Status in distro-info-data source package in Artful:
  Fix Released
Status in distro-info-data source package in Bionic:
  Fix Released

Bug description:
  distro-info-data needs updating in all stable series' to include
  cosmic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/distro-info-data/+bug/1770004/+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 1769992] Re: Add Ubuntu 18.10 - Cosmic Cuttlefish

[Adam Conrad]

Released to the precise ESM archive.

** Changed in: distro-info-data (Ubuntu Precise)
   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/1769992

Title:
  Add Ubuntu 18.10 - Cosmic Cuttlefish

Status in distro-info-data package in Ubuntu:
  Fix Released
Status in distro-info-data source package in Precise:
  Fix Released
Status in distro-info-data source package in Trusty:
  New
Status in distro-info-data source package in Xenial:
  New
Status in distro-info-data source package in Artful:
  New
Status in distro-info-data source package in Bionic:
  New
Status in distro-info-data source package in Cosmic:
  Fix Released

Bug description:
  We have a name (it took a while)

  == SRU Impact ==

  Several tools rely on distro-info to tell them which releases are available.
  This package just contains data, with no format changes.

  == Regression Potential ==

  Minimal, if we are only adding new entries. We do this every release.

  == Test Case ==
  "ubuntu-distro-info -d" should return "cosmic" not an error that the data is 
out of date.

  "ubuntu-distro-info -df" should name the release in full: Ubuntu 18.10
  "Cosmic Cuttlefish"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/distro-info-data/+bug/1769992/+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 1770004] Re: Update distro-info-data for cosmic

[Adam Conrad]

Released to the precise ESM archive.

** Changed in: distro-info-data (Ubuntu Precise)
   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/1770004

Title:
  Update distro-info-data for cosmic

Status in distro-info-data package in Ubuntu:
  Fix Released
Status in distro-info-data source package in Precise:
  Fix Released
Status in distro-info-data source package in Trusty:
  New
Status in distro-info-data source package in Xenial:
  New
Status in distro-info-data source package in Artful:
  New
Status in distro-info-data source package in Bionic:
  New

Bug description:
  distro-info-data needs updating in all stable series' to include
  cosmic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/distro-info-data/+bug/1770004/+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 1770004] [NEW] Update distro-info-data for cosmic

[Adam Conrad]

Public bug reported:

distro-info-data needs updating in all stable series' to include cosmic.

** Affects: distro-info-data (Ubuntu)
 Importance: Undecided
 Assignee: Adam Conrad (adconrad)
 Status: Fix Released

** Affects: distro-info-data (Ubuntu Precise)
 Importance: Undecided
 Assignee: Adam Conrad (adconrad)
 Status: New

** Affects: distro-info-data (Ubuntu Trusty)
 Importance: Undecided
 Assignee: Adam Conrad (adconrad)
 Status: New

** Affects: distro-info-data (Ubuntu Xenial)
 Importance: Undecided
 Assignee: Adam Conrad (adconrad)
 Status: New

** Affects: distro-info-data (Ubuntu Artful)
 Importance: Undecided
 Assignee: Adam Conrad (adconrad)
 Status: New

** Affects: distro-info-data (Ubuntu Bionic)
 Importance: Undecided
 Assignee: Adam Conrad (adconrad)
 Status: New

** Changed in: distro-info-data (Ubuntu)
 Assignee: (unassigned) => Adam Conrad (adconrad)

** Also affects: distro-info-data (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: distro-info-data (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: distro-info-data (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: distro-info-data (Ubuntu Precise)
   Importance: Undecided
   Status: New

** Also affects: distro-info-data (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Changed in: distro-info-data (Ubuntu Precise)
 Assignee: (unassigned) => Adam Conrad (adconrad)

** Changed in: distro-info-data (Ubuntu Trusty)
 Assignee: (unassigned) => Adam Conrad (adconrad)

** Changed in: distro-info-data (Ubuntu Xenial)
 Assignee: (unassigned) => Adam Conrad (adconrad)

** Changed in: distro-info-data (Ubuntu Artful)
 Assignee: (unassigned) => Adam Conrad (adconrad)

** Changed in: distro-info-data (Ubuntu Bionic)
 Assignee: (unassigned) => Adam Conrad (adconrad)

** Changed in: distro-info-data (Ubuntu)
   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/1770004

Title:
  Update distro-info-data for cosmic

Status in distro-info-data package in Ubuntu:
  Fix Released
Status in distro-info-data source package in Precise:
  New
Status in distro-info-data source package in Trusty:
  New
Status in distro-info-data source package in Xenial:
  New
Status in distro-info-data source package in Artful:
  New
Status in distro-info-data source package in Bionic:
  New

Bug description:
  distro-info-data needs updating in all stable series' to include
  cosmic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/distro-info-data/+bug/1770004/+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 1577413] Re: dpkg crashes if given -i directory as parameter

[Adam Conrad]

dpkg (1.18.4ubuntu1.3) xenial; urgency=medium

  * Use ohshit() instead of internerr() for unhandled dpkg-split exit
codes. (i.e. do not abort). Closes: #812679, LP: #1601998

 -- Brian Murray   Fri, 20 Oct 2017 16:14:06 -0700


** Changed in: dpkg (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/1577413

Title:
  dpkg crashes if given -i directory as parameter

Status in dpkg package in Ubuntu:
  Fix Released
Status in dpkg source package in Xenial:
  Fix Released

Bug description:
  $ sudo dpkg -i /tmp
  [sudo] password for user: 
  dpkg-split: error: error reading /tmp: Is a directory
  dpkg:../../src/unpack.c:123:deb_reassemble: internal error: unexpected exit 
status 2 from dpkg-split

  Aborted (core dumped)

  
  Installing a directory is of course an error from user, but dpkg should 
detect it and not crash.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: dpkg 1.18.4ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Mon May  2 17:14:01 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-02-12 (445 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: dpkg
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1577413/+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 1730647] Re: on s390x one should alway be able to manipulate z devices

[Adam Conrad]

** Changed in: ubuntu-meta (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/1730647

Title:
  on s390x one should alway be able to manipulate z devices

Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-meta source package in Xenial:
  Fix Committed
Status in ubuntu-meta source package in Zesty:
  Fix Committed
Status in ubuntu-meta source package in Artful:
  Fix Committed
Status in ubuntu-meta source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * Currently s390-tools is not installed as part of the server seed,
  which leads to inconsistencies between manually installed systems with
  d-i and systems originating from cloud images - containers, cloud
  images, maas. d-i installs s390-tools, whilst the rest do not.
  However, s390-tools ship tooling to inspect, list, operate on z
  specific devices and should always be available across all of ubuntu,
  including containers, maas, etc. Hence seeding it to server seed.

  [Test Case]

   * s390x containers have s390-tools package installed
   * s390x cloud images have s390-tools package installed
   * s390x maas images have s390-tools package installed

  [Regression Potential]

   * This is calling ubuntu-meta update script only
   * The only other changes are those that have been introduced in other srus.
   * s390-tools is in main

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1730647/+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 1682102] Please test proposed package

[Adam Conrad]

Hello Dimitri, or anyone else affected,

Accepted libseccomp into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/libseccomp/2.3.1-2.1ubuntu2~16.04.1
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: libseccomp (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  libseccomp should support GA and HWE kernels

Status in libseccomp package in Ubuntu:
  Invalid
Status in libseccomp source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

  out of date libseccomp w.r.t. custom and hwe kernels provides sub-par 
userspace protection, which is otherwise available on the running kernel and 
hardware combination.
  This results in subpar security of systems running new architectures (s390x & 
ppc64el) and newer hwe/custom kernels.

  * Version 2.3.1 - April 20, 2016
  - Fixed a problem with 32-bit x86 socket syscalls on some systems
  - Fixed problems with ipc syscalls on 32-bit x86
  - Fixed problems with socket and ipc syscalls on s390 and s390x

  * Version 2.3.0 - February 29, 2016
  - Added support for the s390 and s390x architectures
  - Added support for the ppc, ppc64, and ppc64le architectures
  - Update the internal syscall tables to match the Linux 4.5-rcX releases
  - Filter generation for both multiplexed and direct socket syscalls on x86
  - Support for the musl libc implementation
  - Additions to the API to enable runtime version checking of the library
  - Enable the use of seccomp() instead of prctl() on supported systems
  - Added additional tests to the regression test suite

  There is no ABI/API break

  There are no packaging changes, apart from dropping patches included
  in this upstream release and updating new symbols.

  Doing wholesome update is safer and carries less risk, than
  individually cherrypicking effectively all of the above.

  This is a backport to an LTS release under the banner of safe
  introduction of new features and new hardware support.

  It is expected that container technologies will take advantage of the
  newly available libseccomp.

  This may need to be uploaded as a security update.

  Currently, s390x support in xenial libssecomp is incomplete. And there
  are v4.5+ syscall tables missing as used by hwe kernels and some
  custom kernels.

  [Testcase]
  Validate that all main contianer technologies are operational and do not 
regress, e.g.:
   - lxc
   - lxd
   - docker
   - snapd

  [Regression Potential]
  Userspace components may detect at runtime newly available libseccomp, and 
thus restrict user-space processes more than previously done. This may lead to 
a change of restrictions applied on the user sapce processes, and result in 
previously unexpected denials / errors returned.

  
  [Proposed Update available in bileto PPA]
  https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/2981

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1682102/+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 1717382] Re: [Bug] Glibc: performance improvement patches

[Adam Conrad]

** Also affects: glibc (Ubuntu Artful)
   Importance: Undecided
   Status: Fix Released

** Changed in: glibc (Ubuntu Artful)
 Assignee: (unassigned) => Adam Conrad (adconrad)

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

Title:
  [Bug] Glibc: performance improvement patches

Status in GLibC:
  Fix Released
Status in intel:
  New
Status in glibc package in Ubuntu:
  Fix Released
Status in glibc source package in Xenial:
  New
Status in glibc source package in Zesty:
  New
Status in glibc source package in Artful:
  Fix Released

Bug description:
  Description:

  Intel’s new request – for performance related patches that need to be
  picked up as part of one the Ubuntu 16.04 LTS family releases and
  Ubuntu 17.10:

  Glibc 2.23 needs the first 2 patches on hjl/pr21258/2.23 branch:
  
https://sourceware.org/git/gitweb.cgi?p=glibc.git;a=shortlog;h=refs/heads/hjl/pr21258/2.23
  Patches: Address transition penalty when SSE instructions are mixed with 
256-bit AVX or 512-bit AVX512 load instructions.

  Target Release: TBD

To manage notifications about this bug go to:
https://bugs.launchpad.net/glibc/+bug/1717382/+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 1708486] Re: linux-hwe-edge: 4.11.0-13.19~16.04.1 -proposed tracker

[Adam Conrad]

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

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

** Changed in: linux-hwe-edge (Ubuntu Xenial)
   Status: Confirmed => Fix Released

** Changed in: kernel-sru-workflow/upload-to-ppa
   Status: New => Fix Released

** Changed in: kernel-sru-workflow/promote-to-security
   Status: New => Fix Released

** Changed in: kernel-sru-workflow/promote-to-security
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Adam Conrad 
(adconrad)

** Changed in: kernel-sru-workflow/promote-to-updates
   Status: New => Fix Released

** Changed in: kernel-sru-workflow/promote-to-updates
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Adam Conrad 
(adconrad)

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

Title:
  linux-hwe-edge: 4.11.0-13.19~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 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-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Invalid
Status in linux-hwe-edge package in Ubuntu:
  Invalid
Status in linux-hwe-edge source package in Xenial:
  Fix Released

Bug description:
  This bug is for tracking the 4.11.0-13.19~16.04.1 upload package. This
  bug will contain status and testing results related to that upload.

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

  -- swm properties --
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1708486/+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 1708486] Re: linux-hwe-edge: 4.11.0-13.19~16.04.1 -proposed tracker

[Adam Conrad]

** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => Invalid

** Changed in: kernel-sru-workflow/certification-testing
   Status: Confirmed => Invalid

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

Title:
  linux-hwe-edge: 4.11.0-13.19~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 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-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-hwe-edge package in Ubuntu:
  Invalid
Status in linux-hwe-edge source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the 4.11.0-13.19~16.04.1 upload package. This
  bug will contain status and testing results related to that upload.

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

  -- swm properties --
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1708486/+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 1686183] Re: Ship ubuntu-advantage in ubuntu-minimal

[Adam Conrad]

** Changed in: ubuntu-advantage-tools (Ubuntu Yakkety)
   Status: New => Won't Fix

** Changed in: ubuntu-meta (Ubuntu Yakkety)
   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/1686183

Title:
  Ship ubuntu-advantage in ubuntu-minimal

Status in ubuntu-advantage-tools package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  New
Status in ubuntu-advantage-tools source package in Precise:
  Fix Released
Status in ubuntu-meta source package in Precise:
  Fix Released
Status in ubuntu-advantage-tools source package in Trusty:
  Fix Committed
Status in ubuntu-meta source package in Trusty:
  New
Status in ubuntu-advantage-tools source package in Xenial:
  New
Status in ubuntu-meta source package in Xenial:
  New
Status in ubuntu-advantage-tools source package in Yakkety:
  Won't Fix
Status in ubuntu-meta source package in Yakkety:
  Won't Fix
Status in ubuntu-advantage-tools source package in Zesty:
  New
Status in ubuntu-meta source package in Zesty:
  New
Status in ubuntu-advantage-tools source package in Artful:
  New
Status in ubuntu-meta source package in Artful:
  New

Bug description:
  The ubuntu-advantage-tools package is a bit odd as it was first landed
  in precise to support the ESM effort inside canonical. [0]  In order
  to bring this package up to date across other series in ubuntu, it has
  been recommended by the Ubuntu Foundations team to land into trusty
  next, then forward-port pocket-copy to all supported series until we
  get to the devel release.

  The version here:

  https://github.com/CanonicalLtd/ubuntu-advantage-
  script/releases/tag/v2

  ... has all on-disk bits correctly working, for all series, but no-ops
  on any release other than precise (ESM is only for "unsupported" LTS
  releases as it were).  This is a request to land ubuntu-advantage-
  tools into trusty, then pocket-copy it to supported series of ubuntu
  once that is finished.

  [Impact]

   * Allow ubuntu-advantage users to access the extended security
  maintenance script with a simple command line tool.  This script needs
  to hit precise machines and be easy for ubuntu-advantage customers to
  enable, thus basefiles was chosen as a home.

  [Test Case]

   * Run ubuntu-advantage, it should print out help
   * Run sudo ubuntu-advantage enable  (without sudo it will warn you), 
but you need to be an ubuntu-advantage customer to get that token.  In the end, 
the script simply adds and removes an /etc/apt/sources.list.d entry.
   * you can contact me (d...@canonical.com) if you would like a token for test 
purposes.

  [Regression Potential]

   * Low, this is a new script, not included in any automated startup
  paths.

  [Other Info]

   * http://blog.dustinkirkland.com/2017/03/ubuntu-1204-esm.html

  [0] https://insights.ubuntu.com/2017/03/14/introducing-ubuntu-12-04
  -esm-extended-security-maintenance/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1686183/+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 1646585] Re: oem-config replaces /etc/resolv.conf symlink with a hard file

[Adam Conrad]

Hello Newton, or anyone else affected,

Accepted ubiquity into xenial-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/ubiquity/2.21.63.4
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: netcfg (Ubuntu Yakkety)
   Status: Fix Committed => Won't Fix

** Changed in: ubiquity (Ubuntu Xenial)
   Status: Triaged => Fix Committed

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

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

Title:
  oem-config replaces /etc/resolv.conf symlink with a hard file

Status in Nvidia:
  New
Status in netcfg package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in netcfg source package in Xenial:
  Fix Released
Status in ubiquity source package in Xenial:
  Fix Committed
Status in netcfg source package in Yakkety:
  Won't Fix
Status in netcfg source package in Zesty:
  Fix Released
Status in ubiquity source package in Zesty:
  Fix Released

Bug description:
  [Impact]
  This breaks oem-config installs because after running oem-config-firstboot, 
/etc/resolv.conf's symlink might be replaced by a regular file.

  [Test case]
  The DGX server install process uses oem-config to setup certain settings.  We 
are seeing that oem-config-firstboot is replacing the /etc/resolv.conf symlink 
to /run/resolvconf/resolv.conf with a hard file at /etc/resolv.conf.

  This was confirmed by booting in single user mode after a fresh
  install, and seeing the symlink is still there.  Then go thru oem-
  config-firstboot, and find that the symlink is no longer there when
  that is done.

  We have to run "sudo dpkg-reconfigure resolvconf" to restore that
  symlink.

  [Regression potential]
  This may regress by failing to recognize a case where resolvconf is not in 
use, or triggering a false-positive (resolvconf is not in use, by an install is 
tricked into thinking it is and removes resolv.conf). Corruption of 
/etc/resolv.conf or /run/resolvconf/resolv.conf should be considered as 
possible regressions from this SRU.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nvidia/+bug/1646585/+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 1690083] Re: [SRU] 2.26.10

[Adam Conrad]

** Changed in: snapd (Ubuntu Xenial)
   Status: Fix Released => Fix Committed

** Changed in: snapd (Ubuntu Yakkety)
   Status: Fix Committed => 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/1690083

Title:
  [SRU] 2.26.10

Status in snapd package in Ubuntu:
  Fix Released
Status in snapd source package in Trusty:
  Fix Committed
Status in snapd source package in Xenial:
  Fix Committed
Status in snapd source package in Yakkety:
  Won't Fix
Status in snapd source package in Zesty:
  Fix Committed

Bug description:
  This is a new version of snapd.

  The changelog for 2.26.8 is available here
  
https://github.com/snapcore/snapd/blob/2.26.8/packaging/ubuntu-16.04/changelog,
  the raw git changelog is available here:
  https://github.com/snapcore/snapd/commits/2.26.8 (note that the debian
  changelog is auto-generated from the merges of the git commits so
  there is usually no need to look at the raw git commits).

  The snappy team released a new 2.26.8 release that we want SRU into
  xenial. The new process described in
  https://wiki.ubuntu.com/SnapdUpdates was used and we have done
  integration-tests on the snappy images, autopkgtests on classic and
  unit tests.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1690083/+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 1694697] Re: build-depends keeps OR flag if end of or group is ignored

[Adam Conrad]

Hello Julian, or anyone else affected,

Accepted apt into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/1.2.24 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: apt (Ubuntu Yakkety)
   Status: In Progress => Won't Fix

** Changed in: apt (Ubuntu Xenial)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-xenial

** Changed in: apt (Ubuntu Zesty)
   Status: In Progress => Fix Committed

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

Title:
  build-depends keeps OR flag if end of or group is ignored

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Trusty:
  New
Status in apt source package in Xenial:
  Fix Committed
Status in apt source package in Yakkety:
  Won't Fix
Status in apt source package in Zesty:
  Fix Committed

Bug description:
  [Impact]
  If the last alternative(s) of an Or group is ignored, because it does
  not match an architecture list, we would end up keeping the or flag,
  effectively making the next AND an OR.

  For example, when parsing (on amd64):

  debhelper (>= 9), libnacl-dev [amd64] | libnacl-dev [i386]
   => debhelper (>= 9), libnacl-dev |

  Which can cause python-apt and apt-get build-dep to crash.

  Even worse:

   debhelper (>= 9), libnacl-dev [amd64] | libnacl-dev [i386], foobar
    => debhelper (>= 9), libnacl-dev [amd64] | foobar

  [Test case]
  On amd64:

  cat > segv.dsc  << EOF
  Format: 3.0 (native)
  Source: foobar
  Binary: foobar
  Architecture: all
  Version: 1
  Maintainer: Joe Sixpack 
  Build-Depends: build-essential [amd64] | build-essential [fancy]
  Standards-Version: 3.9.8
  EOF
  cat > failure.dsc  << EOF
  Format: 3.0 (native)
  Source: foobar
  Binary: foobar
  Architecture: all
  Version: 1
  Maintainer: Joe Sixpack 
  Build-Depends: build-essential [amd64] | build-essential [fancy], 
a-non-existing-package
  Standards-Version: 3.9.8
  EOF

  (1) apt-get build-dep -s ./segv.dsc should succeed instead of crash
  (2) apt-get build-dep -s ./failure.dsc should complain about "Depends: 
a-non-existing-package but it is not installable" instead of succeeding.

  This is the same test as run by CI and autopkgtests, so if they pass
  the tests passed. You can also run apt-get build-dep -s dq for a real
  life example that should not segfault.

  [Regression Potential]
  apt-get build-dep and friends can now fail where they succeeded previously 
for packages that employ architecture-limited alternatives in their build 
depends, as in the second example given above, because now additional packages 
need to be installed (which is correct, though).

  [Other info]
  By setting the previous alternatives Or flag to the current Or flag
  if the current alternative is ignored, we solve the issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1694697/+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 1686470] Re: Apt updates that are uniformly spread across all timezones, with predictable application windows

[Adam Conrad]

Hello Dimitri, or anyone else affected,

Accepted apt into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/1.2.24 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: apt (Ubuntu Xenial)
   Status: In Progress => Fix Committed

** Changed in: apt (Ubuntu Yakkety)
   Status: In Progress => Won't Fix

** Tags added: verification-needed verification-needed-xenial

** Changed in: unattended-upgrades (Ubuntu Yakkety)
   Status: Triaged => Won't Fix

** Changed in: apt (Ubuntu Zesty)
   Status: In Progress => Fix Committed

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

Title:
  Apt updates that are uniformly spread across all timezones, with
  predictable application windows

Status in apt package in Ubuntu:
  Fix Released
Status in unattended-upgrades package in Ubuntu:
  Triaged
Status in apt source package in Xenial:
  Fix Committed
Status in unattended-upgrades source package in Xenial:
  Triaged
Status in apt source package in Yakkety:
  Won't Fix
Status in unattended-upgrades source package in Yakkety:
  Won't Fix
Status in apt source package in Zesty:
  Fix Committed
Status in unattended-upgrades source package in Zesty:
  Triaged
Status in apt source package in Artful:
  Fix Released
Status in unattended-upgrades source package in Artful:
  Triaged
Status in apt package in Debian:
  Fix Released
Status in unattended-upgrades package in Debian:
  Fix Committed

Bug description:
  [ Impact ]

   * unattended-upgrades are enabled by default in Ubuntu 16.04 and
  later

   * Currently the following three things happen as a monolithic event:
     - metadata updates: apt update
     - download of updates: apt upgrade --download-only
     - application of updates: apt upgrade

   * For the long running instances, all of the above happens at random
     times throughout the day.

   * If systems were poweredoff / suspended, this happens on boot /
  resume

   * End-users would like to have predictable timing, and control over when
     the updates happen.

  Considering all of the above, the following new behavior is proposed
  which should address all concerns in question. It combines all the
  desired properties from both end-user and mirror perspectives.

  [ Proposed Default Behavior ]

   * Decouple unattended-upgrades application, from apt update

   * apt update:
     - shall be a systemd timer based unit, triggered every 12h with a
   random delay of 12h, therefore executed randomly twice a day.
     - if unattened-upgrades (default on), or download-upgreadaeble-packages
   are enabled, it should result in updates being downloaded aka
   `apt upgrade --download-only`

   * unattended-upgrades:
     - shall be a separate systemd timer based unit triggered at 6am local
   time with a random delay of 1h, therefore executed between 6am and
   7am local time.

   * On boot / resume:
     - if we have missed one, or more, apt update timers,
   apt update / download upgrades / unattended-upgrade will happen in
   sequence. This may result in mirror spikes, but we do want to secure
   cold/stale-booted systems as soon as possible.

  [Test Case]

   * Run system for more than 24h, and check that apt updates were
     automatically executed twice.

   * Check that unattended upgrades were triggered to be applied at
     6am..7am window, if any.

   * Poweroff the machine over the period when apt-get update was
     scheduled, poweron and observe that apt-get update / download / 
 unattended upgrade are all performed on boot.

  [Regression Potential]

   * The newly proposed behavior is a mix of Pre-xenial behavior of "do
     everything at 6am..6:30am window" and the xenial+ behavior of "do 
 everything at random times throughout the day". If there are specific 
 deployments that rely on the previous types of behaviour they will be 
 able to adjust manually the systemd timers with the overrides to be 
 executed exactly as they wish; or match the 

[Group.of.nepali.translators] [Bug 1672710] Re: apt fails to verify keys when Dir has space, and set via cmdline

[Adam Conrad]

Hello Dimitri, or anyone else affected,

Accepted apt into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/1.2.24 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Tags added: verification-needed-xenial

** Changed in: apt (Ubuntu Yakkety)
   Status: Fix Committed => 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/1672710

Title:
  apt fails to verify keys when Dir has space, and set via cmdline

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Fix Committed
Status in apt source package in Yakkety:
  Won't Fix

Bug description:
  When Dir has a space, and it is set via APT_CONFIG file, keys are found and 
validated correctly.
  When Dir is set without a space via cmdline, keys are found and validated 
correctly.
  When Dir is set with a space via cmdline, keys are not found and repositories 
are not verified.

  [Test case]
  Please see attached reproducer, which works on xenial system (gpg1) but not 
on zesty system (gpg2)

  $ bash reproducer.sh
  ++ mktemp -d
  + tmpdir=/tmp/tmp.sFipy6h5yL
  + pushd /tmp/tmp.sFipy6h5yL
  /tmp/tmp.sFipy6h5yL ~
  + mkdir 'Sub Dir'
  + pushd 'Sub Dir'
  /tmp/tmp.sFipy6h5yL/Sub Dir /tmp/tmp.sFipy6h5yL ~
  + mkdir -p etc/apt/apt.conf.d
  + mkdir -p etc/apt/trusted.gpg.d
  + mkdir -p etc/apt/preferences.d
  + mkdir -p var/lib/apt/lists/partial
  + mkdir -p var/lib/dpkg
  + touch var/lib/dpkg/status
  + cp /etc/apt/trusted.gpg.d/ubuntu-keyring-2012-archive.gpg 
etc/apt/trusted.gpg.d/
  + echo 'deb http://archive.ubuntu.com/ubuntu/ trusty main'
  + echo 'Dir "/tmp/tmp.sFipy6h5yL/Sub Dir";'
  + export APT_CONFIG=/tmp/tmp.sFipy6h5yL/apt.conf
  + APT_CONFIG=/tmp/tmp.sFipy6h5yL/apt.conf
  + cat /tmp/tmp.sFipy6h5yL/apt.conf
  Dir "/tmp/tmp.sFipy6h5yL/Sub Dir";
  + :
  + : == list available keys ==
  + apt-key list
  /tmp/tmp.sFipy6h5yL/Sub 
Dir/etc/apt/trusted.gpg.d/ubuntu-keyring-2012-archive.gpg
  
-
  pub   rsa4096 2012-05-11 [SC]
    790B C727 7767 219C 42C8  6F93 3B4F E6AC C0B2 1F32
  uid   [ unknown] Ubuntu Archive Automatic Signing Key (2012) 


  + :
  + : == update with environ APT_CONFIG setting the Dir variable ==
  + apt update
  Ign:1 http://archive.ubuntu.com/ubuntu trusty InRelease
  Get:2 http://archive.ubuntu.com/ubuntu trusty Release [58.5 kB]
  Get:3 http://archive.ubuntu.com/ubuntu trusty Release.gpg [933 B]
  Get:4 http://archive.ubuntu.com/ubuntu trusty/main amd64 Packages [1,350 kB]
  Fetched 1,410 kB in 0s (1,959 kB/s)
  Reading package lists... Done
  Building dependency tree... Done
  All packages are up to date.
  + unset APT_CONFIG
  + :
  + : == update with cmdline Dir option setting Dir to relative pwd ==
  + apt -o Dir=./ update
  Ign:1 http://archive.ubuntu.com/ubuntu trusty InRelease
  Hit:2 http://archive.ubuntu.com/ubuntu trusty Release
  Reading package lists... Done
  Building dependency tree... Done
  All packages are up to date.
  + :
  + : == update with cmdline Dir option setting Dir to absolute pwd with space 
==
  + apt -o 'Dir=/tmp/tmp.sFipy6h5yL/Sub Dir' update
  Ign:1 http://archive.ubuntu.com/ubuntu trusty InRelease
  Hit:2 http://archive.ubuntu.com/ubuntu trusty Release
  Err:3 http://archive.ubuntu.com/ubuntu trusty Release.gpg
    The following signatures couldn't be verified because the public key is not 
available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32
  Reading package lists... Done
  Building dependency tree... Done
  All packages are up to date.
  W: An error occurred during the signature verification. The repository is not 
updated and the previous index files will be used. GPG error: 
http://archive.ubuntu.com/ubuntu trusty Release: The following signatures 
couldn't be verified because the public key is not available: NO_PUBKEY 
40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32
  W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/trusty/Release.gpg  
The 

[Group.of.nepali.translators] [Bug 1623418] Re: gcc-as-needed.diff patch broke mpx support in GCC

[Adam Conrad]

** Changed in: binutils (Ubuntu Yakkety)
   Status: Fix Committed => Won't Fix

** Changed in: gcc-5 (Ubuntu Yakkety)
   Status: New => Won't Fix

** Changed in: gcc-6 (Ubuntu Yakkety)
   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/1623418

Title:
  gcc-as-needed.diff patch broke mpx support in GCC

Status in gcc:
  Unknown
Status in binutils package in Ubuntu:
  Fix Released
Status in gcc-5 package in Ubuntu:
  Fix Released
Status in gcc-6 package in Ubuntu:
  Fix Released
Status in binutils source package in Xenial:
  Fix Released
Status in gcc-5 source package in Xenial:
  New
Status in binutils source package in Yakkety:
  Won't Fix
Status in gcc-5 source package in Yakkety:
  Won't Fix
Status in gcc-6 source package in Yakkety:
  Won't Fix

Bug description:
  [SRU Justification]
  gcc-5 from Ubuntu is configured with MPX support, but it is broken due
  to always-added linker option "-as-needed".

  [Test case]
  1. Pass -mmpx to gcc when building an arbitrary project on x86.
  2. Verify with ldd that the resulting executable is not linked against 
libmpx.so because the -as-needed flag has discarded the mpx library from being 
linked in.
  3. Install binutils and gcc-5 from -proposed.
  4. Rebuild the target, again with -mmpx.
  5. Verify with ldd that the new executable is linked against libmpx.so.
  6. Verify that there are no regressions in the binutils testsuite on any 
architectures, by manually checking the results in the build log.

  [Regression potential]
  This binutils patch implements new --push-state / --pop-state options which 
will not be used in the common case, only when -mmpx is passed.  When these 
flags are not in use, which is the default, it should have no effect on the 
behavior of the toolchain, so risk of regression is minimal.


  Here is the GCC upstream bug & fix

  https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77267

  https://gcc.gnu.org/viewcvs/gcc?view=revision=240057

  Would it be possible to backport this fix to Ubuntu gcc-5 build?

To manage notifications about this bug go to:
https://bugs.launchpad.net/gcc/+bug/1623418/+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 1687981] Re: Backport packages for 16.04.3 HWE stack

[Adam Conrad]

** Changed in: xfonts-utils (Ubuntu)
   Status: New => Invalid

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

Title:
  Backport packages for 16.04.3 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in libinput package in Ubuntu:
  Invalid
Status in libwacom package in Ubuntu:
  Invalid
Status in libxfont package in Ubuntu:
  Invalid
Status in libxfont2 package in Ubuntu:
  Invalid
Status in llvm-toolchain-4.0 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in virtualbox-hwe package in Ubuntu:
  Fix Released
Status in vulkan package in Ubuntu:
  Invalid
Status in wayland package in Ubuntu:
  Invalid
Status in x11proto-core package in Ubuntu:
  Invalid
Status in xfonts-utils package in Ubuntu:
  Invalid
Status in xorg-hwe-16.04 package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in xorg-server-hwe-16.04 package in Ubuntu:
  Invalid
Status in libclc source package in Xenial:
  Fix Released
Status in libdrm source package in Xenial:
  Fix Released
Status in libinput source package in Xenial:
  Fix Released
Status in libwacom source package in Xenial:
  Fix Released
Status in libxfont source package in Xenial:
  Fix Released
Status in libxfont2 source package in Xenial:
  Fix Released
Status in llvm-toolchain-4.0 source package in Xenial:
  Fix Released
Status in mesa source package in Xenial:
  Fix Released
Status in vulkan source package in Xenial:
  Fix Released
Status in wayland source package in Xenial:
  Fix Released
Status in x11proto-core source package in Xenial:
  Fix Released
Status in xfonts-utils source package in Xenial:
  Fix Released
Status in xorg-hwe-16.04 source package in Xenial:
  Fix Released
Status in xorg-server source package in Xenial:
  Invalid
Status in xorg-server-hwe-16.04 source package in Xenial:
  Fix Released

Bug description:
  [Impact]

  *** hwe-16.04 refresh for 16.04.3 ***

  Revert changes to use debhelper10.

  xorg-server-hwe-16.04 needs updates
  - wayland 1.11 (but zesty has 1.12 which mesa needs so backport that)
  - x11proto-core 7.0.31
  - libxfont-dev 2.0.1, which also means backporting libxfont1 (NEW)

  x-x-i-libinput will not replace -evdev in x-x-i-all-hwe-16.04 because the 
unity mouse config doesn't work with -libinput.
  x-x-i-libinput needs newer libinput, which in turn needs libwacom update.

  Mesa needs llvm-4.0 and libclc, libdrm, wayland updates.

  [Test case]

  upgrade from/to stock & old hwe stack, test desktop usage

  [Regression potential]

  zesty hasn't blown up

  [Other information]

  build order:
  1. x11proto-core, libdrm, libxfont, libxfont1, libwacom, llvm-toolchain-4.0, 
vulkan, wayland
  2. libclc, libinput, xorg-server (build-dep libxfont1-dev)
  3. mesa, xorg-server-hwe-16.04
  4. drivers
  5. xorg-hwe-16.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1687981/+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 1696710] Re: Ubuntu 16.04.02: depmod: WARNING: needs unknown symbol .TOC.

[Adam Conrad]

Ahh yes, and we already had that patch in yakkety and zesty, it was just
never backported to xenial.

** Changed in: kmod (Ubuntu)
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Adam Conrad 
(adconrad)

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

** Changed in: kmod (Ubuntu)
   Status: New => Invalid

** Changed in: kmod (Ubuntu Xenial)
 Assignee: (unassigned) => Adam Conrad (adconrad)

** Changed in: kmod (Ubuntu Xenial)
   Status: New => In Progress

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

Title:
  Ubuntu 16.04.02: depmod: WARNING:  needs unknown symbol
  .TOC.

Status in The Ubuntu-power-systems project:
  New
Status in kmod package in Ubuntu:
  Invalid
Status in kmod source package in Xenial:
  In Progress

Bug description:
  == Comment: #0 - Douglas Miller <dougm...@us.ibm.com> - 2017-01-24 07:59:54 ==
  ---Problem Description---
  depmod does not handle .TOC symbol on powerpc platforms
   
  Contact Information = Douglas Miller <dougm...@linux.vnet.ibm.com> 
   
  ---uname output---
  Linux p8le03 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:40:06 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = other 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Compile kernel, during modules_install target the messages appear. PPC64 
modules have a .TOC symbol which is required. It may be the only symbol with a 
period in the name, and so tools that restrict symbols based on a pattern may 
neglect to include .TOC.
   
  Userspace tool common name: depmod 
   
  The userspace tool has the following bit modes: 64 

  Userspace rpm: libkmod2:ppc64el

  Userspace tool obtained from project website:  na 
   
  *Additional Instructions for Douglas Miller <dougm...@linux.vnet.ibm.com>:
  -Attach ltrace and strace of userspace application.

  == Comment: #3 - Douglas Miller <dougm...@us.ibm.com> - 2017-01-24 08:12:58 ==
  kmod package:

  # dpkg --list |grep kmod
  ii  kmod   22-1ubuntu4
 ppc64el  tools for managing Linux kernel modules
  ii  libkmod2:ppc64el   22-1ubuntu4
 ppc64el  libkmod shared library

  == Comment: #7 - Douglas Miller <dougm...@us.ibm.com> - 2017-06-07 16:20:38 ==
   I was doing a build of upstream origin/master on Ubuntu 16.04.2 fresh 
install and still getting these messages. In the "make modules_install" output 
I see:

  ...
DEPMOD  4.12.0-rc4
  depmod: WARNING: 
/lib/modules/4.12.0-rc4/kernel/arch/powerpc/kernel/rtas_flash.ko needs unknown 
symb
  ol .TOC.
  ...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1696710/+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 1687981] Re: Backport packages for 16.04.3 HWE stack

[Adam Conrad]

Hello Timo, or anyone else affected,

Accepted virtualbox-hwe into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/virtualbox-
hwe/5.0.40-dfsg-0ubuntu1.16.04.1~16.04.3 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Tags added: verification-needed

** Also affects: virtualbox-hwe (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Backport packages for 16.04.3 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in libinput package in Ubuntu:
  Invalid
Status in libwacom package in Ubuntu:
  Invalid
Status in libxfont package in Ubuntu:
  Invalid
Status in libxfont2 package in Ubuntu:
  Invalid
Status in llvm-toolchain-4.0 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in virtualbox-hwe package in Ubuntu:
  New
Status in vulkan package in Ubuntu:
  Invalid
Status in wayland package in Ubuntu:
  Invalid
Status in x11proto-core package in Ubuntu:
  Invalid
Status in xfonts-utils package in Ubuntu:
  New
Status in xorg-hwe-16.04 package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in xorg-server-hwe-16.04 package in Ubuntu:
  Invalid
Status in libclc source package in Xenial:
  Fix Committed
Status in libdrm source package in Xenial:
  Fix Committed
Status in libinput source package in Xenial:
  Fix Committed
Status in libwacom source package in Xenial:
  Fix Committed
Status in libxfont source package in Xenial:
  Fix Committed
Status in libxfont2 source package in Xenial:
  Fix Committed
Status in llvm-toolchain-4.0 source package in Xenial:
  Fix Committed
Status in mesa source package in Xenial:
  Fix Committed
Status in vulkan source package in Xenial:
  Fix Committed
Status in wayland source package in Xenial:
  Fix Committed
Status in x11proto-core source package in Xenial:
  Fix Committed
Status in xfonts-utils source package in Xenial:
  Fix Committed
Status in xorg-hwe-16.04 source package in Xenial:
  New
Status in xorg-server source package in Xenial:
  Invalid
Status in xorg-server-hwe-16.04 source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

  *** hwe-16.04 refresh for 16.04.3 ***

  Revert changes to use debhelper10.

  xorg-server-hwe-16.04 needs updates
  - wayland 1.11 (but zesty has 1.12 which mesa needs so backport that)
  - x11proto-core 7.0.31
  - libxfont-dev 2.0.1, which also means backporting libxfont1 (NEW)

  x-x-i-libinput will not replace -evdev in x-x-i-all-hwe-16.04 because the 
unity mouse config doesn't work with -libinput.
  x-x-i-libinput needs newer libinput, which in turn needs libwacom update.

  Mesa needs llvm-4.0 and libclc, libdrm, wayland updates.

  [Test case]

  upgrade from/to stock & old hwe stack, test desktop usage

  [Regression potential]

  zesty hasn't blown up

  [Other information]

  build order:
  1. x11proto-core, libdrm, libxfont, libxfont1, libwacom, llvm-toolchain-4.0, 
vulkan, wayland
  2. libclc, libinput, xorg-server (build-dep libxfont1-dev)
  3. mesa, xorg-server-hwe-16.04
  4. drivers
  5. xorg-hwe-16.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1687981/+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 1704774] Re: xtables-addons 2.10-1ubuntu0.1 ADT test failure with linux-hwe 4.10.0-27.30~16.04.2

[Adam Conrad]

Hello Andy, or anyone else affected,

Accepted xtables-addons into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/xtables-
addons/2.12-0.1~16.04.1 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: xtables-addons (Ubuntu Xenial)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-xenial

** Changed in: xtables-addons (Ubuntu)
   Status: New => Invalid

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

Title:
  xtables-addons 2.10-1ubuntu0.1 ADT test failure with linux-hwe
  4.10.0-27.30~16.04.2

Status in xtables-addons package in Ubuntu:
  Invalid
Status in xtables-addons source package in Xenial:
  Fix Committed

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/x/xtables-addons/20170710_033319_81aa5@/log.gz
  armhf: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/armhf/x/xtables-addons/20170710_033556_81aa5@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/x/xtables-addons/20170710_033230_81aa5@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/x/xtables-addons/20170710_033456_81aa5@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/x/xtables-addons/20170710_033059_81aa5@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xtables-addons/+bug/1704774/+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 1704280] Re: dm-writeboost 2.1.1-1ubuntu1 ADT test failure with linux-hwe 4.10.0-27.30~16.04.2

[Adam Conrad]

Hello Andy, or anyone else affected,

Accepted dm-writeboost into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/dm-
writeboost/2.2.6-1~16.04.1 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: dm-writeboost (Ubuntu Xenial)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-xenial

** Changed in: dm-writeboost (Ubuntu)
   Status: New => Invalid

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

Title:
  dm-writeboost 2.1.1-1ubuntu1 ADT test failure with linux-hwe
  4.10.0-27.30~16.04.2

Status in dm-writeboost package in Ubuntu:
  Invalid
Status in dm-writeboost source package in Xenial:
  Fix Committed

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/d/dm-writeboost/20170710_033146_b2be1@/log.gz
  armhf: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/armhf/d/dm-writeboost/20170710_033525_b2be1@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/d/dm-writeboost/20170710_033208_b2be1@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/d/dm-writeboost/20170710_033322_b2be1@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/d/dm-writeboost/20170710_033100_b2be1@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dm-writeboost/+bug/1704280/+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 1684034] Re: Some Dell and Lenovo systems do not work after BIOS Capsule Update

[Adam Conrad]

Yakkety is EOL in a week, so there's closing the Yakkety tasks given
that no one has uploaded a package yet (which would likely take a week
or more to get through the verification pipe).

** Changed in: fwupdate (Ubuntu Yakkety)
   Status: In Progress => Won't Fix

** Changed in: fwupdate-signed (Ubuntu Yakkety)
   Status: In Progress => 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/1684034

Title:
  Some Dell and Lenovo systems do not work after BIOS Capsule Update

Status in fwupdate package in Ubuntu:
  Fix Released
Status in fwupdate-signed package in Ubuntu:
  Fix Released
Status in fwupdate source package in Xenial:
  Fix Committed
Status in fwupdate-signed source package in Xenial:
  Fix Committed
Status in fwupdate source package in Yakkety:
  Won't Fix
Status in fwupdate-signed source package in Yakkety:
  Won't Fix
Status in fwupdate source package in Zesty:
  Fix Released
Status in fwupdate-signed source package in Zesty:
  Fix Released

Bug description:
  [Impact]
  This bug is found on Ubuntu 16.04 with fwupdate 0.5-2ubuntu4, but not found 
on Ubuntu 17.04 with fwupdate 9-1.

  The newer version of capsule flashing tools in Ubuntu 17.04 supports
  the reset type from some querycapsuleinfo call：

  
https://github.com/rhinstaller/fwupdate/commit/f1cc489783d2054e90fa6bebc3732e7ea8bb3722

  [Test Case]

  == fwupdate ==
  On a system with a capsule update available, perform capsule update using 
fwupdate.  Verify the system works properly after the update.

  == efivar ==
  We avoided the upgrade of efivar so we don't need to validate its 
reverse-dependencies.

  [Regression Potential]
  Any vendors that relied upon the previous functionality (hardcoded to warm 
reset rather than querying for reset types) may have problems.  This is 
actually a BIOS
  problem in those situations.

  It's unlikely that this should happen though because querying for
  reset types more closely aligns to the implementations that other OSes
  use when applying capsule updates.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fwupdate/+bug/1684034/+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 1704013] Re: xenial myth and mate livefses fail to build due to libgles1-mesa

[Adam Conrad]

** Also affects: livecd-rootfs (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: livecd-rootfs (Ubuntu)
   Status: New => Invalid

** Changed in: livecd-rootfs (Ubuntu Xenial)
 Assignee: (unassigned) => Adam Conrad (adconrad)

** Changed in: livecd-rootfs (Ubuntu Xenial)
   Status: New => In Progress

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

Title:
  xenial myth and mate livefses fail to build due to libgles1-mesa

Status in livecd-rootfs package in Ubuntu:
  Invalid
Status in livecd-rootfs source package in Xenial:
  In Progress

Bug description:
  [ SRU Justification ]
  The mesa update in -proposed removed libgles1-mesa, which should be fine, as 
everything in xenial depends on libgles2-mesa except for two packages, both of 
which were fixed in updates.  However, because task-based installation pulls in 
tasks from the release pocket, myth and mate accidentally attempt to install 
libgles1-mesa during the livefs build, and it's no longer installable.

  [ Proposed Fix ]
  Add libgles1-mesa to the task filter to remove it from the list of packages 
to install.

  [ Regression Potential ]
  Zip.

  [ Test Case ]
  See if mate and myth livefses build in proposed with this change.  Make sure 
manifests look sane.  Profit.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1704013/+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 1687981] Re: Backport packages for 16.04.3 HWE stack

[Adam Conrad]

Hello Timo, or anyone else affected,

Accepted libinput into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/libinput/1.6.3-1ubuntu1~16.04.1 in
a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: libinput (Ubuntu Xenial)
   Status: New => Fix Committed

** Changed in: mesa (Ubuntu Xenial)
   Status: New => Fix Committed

** Changed in: mesa (Ubuntu)
   Status: New => Invalid

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

Title:
  Backport packages for 16.04.3 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in libinput package in Ubuntu:
  Invalid
Status in libwacom package in Ubuntu:
  Invalid
Status in libxfont package in Ubuntu:
  Invalid
Status in libxfont2 package in Ubuntu:
  Invalid
Status in llvm-toolchain-4.0 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in vulkan package in Ubuntu:
  Invalid
Status in wayland package in Ubuntu:
  Invalid
Status in x11proto-core package in Ubuntu:
  Invalid
Status in xfonts-utils package in Ubuntu:
  New
Status in xorg-hwe-16.04 package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in xorg-server-hwe-16.04 package in Ubuntu:
  Invalid
Status in libclc source package in Xenial:
  Fix Committed
Status in libdrm source package in Xenial:
  Fix Committed
Status in libinput source package in Xenial:
  Fix Committed
Status in libwacom source package in Xenial:
  Fix Committed
Status in libxfont source package in Xenial:
  Fix Committed
Status in libxfont2 source package in Xenial:
  Fix Committed
Status in llvm-toolchain-4.0 source package in Xenial:
  Fix Committed
Status in mesa source package in Xenial:
  Fix Committed
Status in vulkan source package in Xenial:
  Fix Committed
Status in wayland source package in Xenial:
  Fix Committed
Status in x11proto-core source package in Xenial:
  Fix Committed
Status in xfonts-utils source package in Xenial:
  Fix Committed
Status in xorg-hwe-16.04 source package in Xenial:
  New
Status in xorg-server source package in Xenial:
  Invalid
Status in xorg-server-hwe-16.04 source package in Xenial:
  New

Bug description:
  [Impact]

  *** hwe-16.04 refresh for 16.04.3 ***

  Revert changes to use debhelper10.

  xorg-server-hwe-16.04 needs updates
  - wayland 1.11 (but zesty has 1.12 which mesa needs so backport that)
  - x11proto-core 7.0.31
  - libxfont-dev 2.0.1, which also means backporting libxfont1 (NEW)

  x-x-i-libinput will not replace -evdev in x-x-i-all-hwe-16.04 because the 
unity mouse config doesn't work with -libinput.
  x-x-i-libinput needs newer libinput, which in turn needs libwacom update.

  Mesa needs llvm-4.0 and libclc, libdrm, wayland updates.

  [Test case]

  upgrade from/to stock & old hwe stack, test desktop usage

  [Regression potential]

  zesty hasn't blown up

  [Other information]

  build order:
  1. x11proto-core, libdrm, libxfont, libxfont1, libwacom, llvm-toolchain-4.0, 
vulkan, wayland
  2. libclc, libinput, xorg-server (build-dep libxfont1-dev)
  3. mesa, xorg-server-hwe-16.04
  4. drivers
  5. xorg-hwe-16.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1687981/+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 1693226] Re: Break the conflicts with click the optparser

[Adam Conrad]

** Also affects: click (Ubuntu Artful)
   Importance: Undecided
 Assignee: Sergio Schvezov (sergiusens)
   Status: Fix Released

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

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

Title:
  Break the conflicts with click the optparser

Status in click package in Ubuntu:
  Fix Released
Status in click source package in Xenial:
  New
Status in click source package in Yakkety:
  New
Status in click source package in Zesty:
  New
Status in click source package in Artful:
  Fix Released

Bug description:
  [Impact]

   * python-click and python-click-package conflict as they use the same
 python package for its implementation.

   * Since python-click-package is an implementation detail for the click 
 package and python3-click is a package meant to be used in other
 implementations it makes sense to break the conflict by moving the
 package name for python-click-package to a different name

   * snapcraft has moved from docopt to python3-click, users that have click
 installed don't have an upgrade path.his bug.

  [Test Case]

   * Where snapcraft 2.30 is present:
 
 - apt install click
 - Install snapcraft << 2.30
 - update to snapcraft >= 2.30
 - the upgrade should not be held on any package.
 - click and snapcraft commands should work.

  * Install python3-click and click should be possible. The click command
should keep working and python3 -c 'from click import group' shall work.

  
  [Regression Potential] 

   * Users depending on click from python-click-package will be importing an
 unexpected click in any scripts they may have.

  [Other Info]
   
   * While unfortunate, click as a technology is deprecated and not used
 anymore. This resolution path was discussed with slangasek and apw prior
 to any work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/click/+bug/1693226/+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 1673247] Re: package snapd 2.23.1 failed to install/upgrade: trying to overwrite '/etc/apparmor.d/usr.lib.snapd.snap-confine', which is also in package snap-confine

[Adam Conrad]

** Also affects: dpkg (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Also affects: snapd (Ubuntu Zesty)
   Importance: Undecided
   Status: New

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

Title:
  package snapd 2.23.1 failed to install/upgrade: trying to overwrite
  '/etc/apparmor.d/usr.lib.snapd.snap-confine', which is also in package
  snap-confine 2.23.1

Status in dpkg package in Ubuntu:
  In Progress
Status in snapd package in Ubuntu:
  In Progress
Status in dpkg source package in Trusty:
  Confirmed
Status in snapd source package in Trusty:
  In Progress
Status in dpkg source package in Xenial:
  Confirmed
Status in snapd source package in Xenial:
  Confirmed
Status in dpkg source package in Yakkety:
  Confirmed
Status in snapd source package in Yakkety:
  Confirmed
Status in dpkg source package in Zesty:
  New
Status in snapd source package in Zesty:
  New

Bug description:
  When the ubuntu installer runs it has an option to download updates during 
the install. When this happens snapd/snap-confine 2.22.6 are installed on 
/target. The upgrade brings in snapd/snap-confine 2.23.1 which has a conffile 
in /etc/apparmor.d/usr.lib.snapd.snap-confine. The snapd packages declares a 
breaks/replaces: snapd-confine (<< 2.23) which works correctly on regular 
upgrades. However it does fail on upgrades with the "--root=/target" that is 
used by ubiquity. After a bit of debugging it turns out the reason is that
  src/archives.c:tarobject() has a check for obsolete conffiles in the block
  around "Is the file an obsolete conffile ...". There is a stat() here that
  checks that the conff->name and the fnamevb are the same file. This check
  fails to take the instdir into account and therefore the loop does not 
  continue but falls through to the "does_replace()" checks.

  
  
  Snap 2.23.1 fails to upgrade from 2.21.

  Known facts:
  - reporters (and apport) indicate it fails during the install via the live-cd
  - not reproducible so far on an already installed system
  - breaks/replaces of snapd are correct
  - When adding "xenial-proposed" to apt-setup in ubiquity and installing

  Cause:
  - when ubiquity runs it uses "dpkg --root=/target --unpack ..." - however 
when doing the conffile checking dpkg does not handle the "--root" parameter 
correctly and checks something against "/" instead of "/target".

  -
  I really don't know what else to add...

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: snapd 2.23.1
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  Uname: Linux 4.8.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CasperVersion: 1.376.2
  Date: Wed Mar 15 16:03:33 2017
  DuplicateSignature:
   package:snapd:2.23.1
   Unpacking snapd (2.23.1) over (2.21) ...
   dpkg: error processing archive 
/target/var/cache/apt/archives/snapd_2.23.1_amd64.deb (--unpack):
    trying to overwrite '/etc/apparmor.d/usr.lib.snapd.snap-confine', which is 
also in package snap-confine 2.23.1
  ErrorMessage: trying to overwrite 
'/etc/apparmor.d/usr.lib.snapd.snap-confine', which is also in package 
snap-confine 2.23.1
  LiveMediaBuild: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: snapd
  Title: package snapd 2.23.1 failed to install/upgrade: trying to overwrite 
'/etc/apparmor.d/usr.lib.snapd.snap-confine', which is also in package 
snap-confine 2.23.1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1673247/+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 1688606] Please test proposed package

[Adam Conrad]

Hello Scott, or anyone else affected,

Accepted cloud-initramfs-tools into yakkety-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/cloud-initramfs-tools/0.30ubuntu1.2 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: cloud-initramfs-tools (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  SRU cloud-initramfs-rooturl to archive

Status in maas-images:
  Triaged
Status in cloud-initramfs-tools package in Ubuntu:
  Invalid
Status in cloud-initramfs-tools source package in Trusty:
  Fix Committed
Status in cloud-initramfs-tools source package in Xenial:
  Fix Committed
Status in cloud-initramfs-tools source package in Yakkety:
  Fix Committed

Bug description:
  === Begin SRU Template ===
  [Impact]
  MAAS has an interest in booting entirely ephemerally without iscsi root.
  The package cloud-initramfs-rooturl supports booting with root coming
  from a url.
    root=http:///squashfs

  This function will be used to pxe boot into a RAM only system with no
  dependency on the network.

  [Test Case]
  See the attached prepare-1688606.sh.  That script automates
  everything here making this much easier to test.

  1. make sure squashfs module is in the initramfs
     squashfs module is not automatically added to initramfs in precise.
     Just ensure that it is there.

     $ [ "$(lsb_release -sc)" = "precise" ] &&
    echo "manual_add_modules squashfs" |
   sudo tee /etc/initramfs-tools/hooks/squashfs

  2. install cloud-initramfs-rooturl
     sudo apt-get update
     sudo apt-get install cloud-initramfs-rooturl

  3. collect the kernel and newly generated initramfs

     sudo cat /boot/vmlinu?-$(uname -r) > kernel
     cp /boot/initrd.img-$(uname -r) initrd

  4. Download a squashfs image or a .tar.xz image

     rel="xenial"
     burl="http://cloud-images.ubuntu.com/daily/server;
     file="$rel-server-cloudimg-amd64-root.tar.xz"
     file="$rel-server-cloudimg-amd64.squashfs"
     wget "$burl/$rel/current/$file" -O "$file"

  5. run a web server
     python -m SimpleHTTPServer  &

  6. create a seed disk for cloud-init.

     $ cat > my-user-data < my-meta-data
     $ cloud-localds seed.img my-user-data my-meta-data

  7. Boot a vm using the kernel, initrd and url.

     cmdline="root=http://10.0.2.2:/$file console=ttyS0 -v "
     cmdline="${cmdline} overlayroot=tmpfs"

     qemu-system-x86_64 -enable-kvm \
    -device virtio-net-pci,netdev=net00 \
    -netdev type=user,id=net00 \
    -drive if=virtio,file=seed.img \
    -m 1G -nographic \
    -kernel kernel -initrd initrd \
    -append "root=$cmdline"

  [Regression Potential]
  Low.  This is adding a package previously not present.

  [Other Info]
  Related bugs:
   * bug 1689557: replace iscsi usage in ephemeral image with rooturl
   * bug 1689642: cloud-initramfs-rooturl should manual_add_modules squashfs 

  === End SRU Template ===

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas-images/+bug/1688606/+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 1685055] Re: Update to add Artful

[Adam Conrad]

** Changed in: distro-info-data (Ubuntu Artful)
   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/1685055

Title:
  Update to add Artful

Status in distro-info-data package in Ubuntu:
  Fix Released
Status in distro-info-data source package in Trusty:
  Fix Committed
Status in distro-info-data source package in Xenial:
  Fix Committed
Status in distro-info-data source package in Yakkety:
  Fix Committed
Status in distro-info-data source package in Zesty:
  Fix Committed
Status in distro-info-data source package in Artful:
  Fix Released

Bug description:
  SRU verification:

  "ubuntu-distro-info -d" should succeed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/distro-info-data/+bug/1685055/+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 1676380] Re: Update to cups-daemon 2.1.3-4ubuntu0.2 results in maintainer script failures

[Adam Conrad]

So, if old prerm is failing on a bad unit, then new prerm is attempted.
New prerm should be written in a way that it skips/ignores the failure.

** Changed in: cups (Ubuntu)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

** Changed in: cups (Ubuntu)
   Status: Fix Released => Confirmed

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

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

Title:
  Update to cups-daemon 2.1.3-4ubuntu0.2 results in maintainer script
  failures

Status in cups package in Ubuntu:
  Confirmed
Status in cups source package in Xenial:
  New

Bug description:
  Even though LP: #1642966 states that this is now fixed, the very
  update that was SRU'ed in that bug-report caused this error just now.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.10.0-13.15~16.04.2-generic 4.10.1
  Uname: Linux 4.10.0-13-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CupsErrorLog:

  Date: Mon Mar 27 12:53:31 2017
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2017-03-15 (11 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Lpstat: device for iP5200R: usb://Canon/iP5200R?serial=9045C0
  MachineType: Dell Inc. Precision 5520
  Papersize: a4
  PpdFiles: iP5200R: Canon iP5200R series - CUPS+Gutenprint v5.2.11
  ProcCmdline: BOOT_IMAGE=/vmlinuz-4.10.0-13-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi_rev_override vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-13-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi_rev_override vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new 
pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.3
  dmi.board.name: 06X96V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.3:bd01/18/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn06X96V:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.name: Precision 5520
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1676380/+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 1506427] Re: Using calendar with keys might cause Indicator-datetime to crash unity-panel-service

[Adam Conrad]

** Also affects: ido (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Changed in: ido (Ubuntu Trusty)
   Status: New => Fix Committed

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

Title:
  Using calendar with keys might cause Indicator-datetime to crash
  unity-panel-service

Status in ido package in Ubuntu:
  Fix Released
Status in ido source package in Trusty:
  Fix Committed
Status in ido source package in Xenial:
  Fix Released
Status in ido source package in Yakkety:
  Fix Released

Bug description:
  [Impact] 
  Unity panel service crashes (removing indicators from panel) when calendar 
menu is opened and there are some key presses.

  [Test Case]
  This is a quite random bug that is not easy to reproduce, it happens 
sometimes that you open the indicator-datetime and after a keypress the panel 
crashes.

  [Regression Potential]
  Nothing expected, but calendar item in datetime might behave differently on 
key-presses.
  Although the fix is quite safe since we're just ensuring that we disconnect 
from parent widget signals on menuitem destruction.

  ===

  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity.  This problem was most recently seen with version
  7.3.2+15.10.20151002.2-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/74901303bee889a2ca807616ea267069ad252435
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ido/+bug/1506427/+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 1679252] Re: Cloud images for non-Intel architectures are configured with security repos that don't work

[Adam Conrad]

Hello Dan, or anyone else affected,

Accepted livecd-rootfs into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/livecd-
rootfs/2.408.10 in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** No longer affects: livecd-rootfs

** Changed in: livecd-rootfs (Ubuntu)
   Status: Confirmed => Fix Released

** Changed in: livecd-rootfs (Ubuntu Xenial)
   Status: New => Fix Committed

** Tags added: verification-needed

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

Title:
  Cloud images for non-Intel architectures are configured with security
  repos that don't work

Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in livecd-rootfs source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

  Users who don't get a fresh sources.list written out on first boot
  (e.g. Docker users) can't install updates from xenial-security on non-
  Intel architectures.

  [Test Case]

  Run an ubuntu-cpc livefs build for a non-Intel architecture, unpack
  one of the produced root tarballs, chroot in to it and perform an
  `apt-get update`.  You should see no errors.

  [Regression Potential]

  This change modifies the sources that apt will use for updates, so the
  biggest risk for regression is that the fix is malformed and systems
  become un-updateable (either partially or fully).  The test above
  should catch this.

  [Original Report]

  In the fix for bug 1513529, we[0] modified livecd-rootfs to write out
  a sources.list that matches the sources.list in Ubuntu Server
  installed from an ISO.  We (presumably) compared to an Intel
  installation, and hard-coded security.ubuntu.com as a repo in
  sources.list.

  Unfortunately, packages for non-Intel architectures aren't published
  to security.ubuntu.com; they are instead published at
  http://ports.ubuntu.com/ubuntu-ports/.  That should be the URL that we
  configure as the source for $SUITE-security.

  [0] Well, *ahem*, _I_.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1679252/+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 1679252] Re: Cloud images for non-Intel architectures are configured with security repos that don't work

[Adam Conrad]

** Also affects: livecd-rootfs (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

Title:
  Cloud images for non-Intel architectures are configured with security
  repos that don't work

Status in livecd-rootfs:
  New
Status in livecd-rootfs package in Ubuntu:
  Confirmed
Status in livecd-rootfs source package in Xenial:
  New

Bug description:
  [Impact]

  Users who don't get a fresh sources.list written out on first boot
  (e.g. Docker users) can't install updates from xenial-security on non-
  Intel architectures.

  [Test Case]

  Run an ubuntu-cpc livefs build for a non-Intel architecture, unpack
  one of the produced root tarballs, chroot in to it and perform an
  `apt-get update`.  You should see no errors.

  [Regression Potential]

  This change modifies the sources that apt will use for updates, so the
  biggest risk for regression is that the fix is malformed and systems
  become un-updateable (either partially or fully).  The test above
  should catch this.

  [Original Report]

  In the fix for bug 1513529, we[0] modified livecd-rootfs to write out
  a sources.list that matches the sources.list in Ubuntu Server
  installed from an ISO.  We (presumably) compared to an Intel
  installation, and hard-coded security.ubuntu.com as a repo in
  sources.list.

  Unfortunately, packages for non-Intel architectures aren't published
  to security.ubuntu.com; they are instead published at
  http://ports.ubuntu.com/ubuntu-ports/.  That should be the URL that we
  configure as the source for $SUITE-security.

  [0] Well, *ahem*, _I_.

To manage notifications about this bug go to:
https://bugs.launchpad.net/livecd-rootfs/+bug/1679252/+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 1678042] Re: removal of priority changed packages breaks builds of the core snap

[Adam Conrad]

** Also affects: live-build (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: live-build (Ubuntu)
 Assignee: Andy Whitcroft (apw) => Adam Conrad (adconrad)

** Changed in: live-build (Ubuntu Xenial)
 Assignee: (unassigned) => Adam Conrad (adconrad)

** Changed in: live-build (Ubuntu Xenial)
   Importance: Undecided => Critical

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

Title:
  removal of priority changed packages breaks builds of the core snap

Status in live-build package in Ubuntu:
  New
Status in live-build source package in Xenial:
  New

Bug description:
  the fix for bug 1668847 seems to cause a removal of systemd-sysv (and
  installation of upstart) in the ubuntu core snap builds, which makes
  teh build fail now.

  a log of the last successful build of the core snap:
  
https://launchpadlibrarian.net/313520770/buildlog_snap_ubuntu_xenial_amd64_core_BUILDING.txt.gz

  a log of a current failing build:
  
https://launchpadlibrarian.net/313704330/buildlog_snap_ubuntu_xenial_amd64_core_BUILDING.txt.gz

  it removes locales properly but then tries to also remove systemd-sysv
  in the lb_chroot_archives step

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/live-build/+bug/1678042/+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 1674532] Re: Ubuntu 14.04 broken during PXE boot

[Adam Conrad]

** Changed in: glibc (Ubuntu Yakkety)
   Status: New => Invalid

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

** Changed in: glibc (Ubuntu Xenial)
   Status: New => Confirmed

** Changed in: eglibc (Ubuntu Precise)
 Assignee: (unassigned) => Steve Beattie (sbeattie)

** Changed in: eglibc (Ubuntu Trusty)
 Assignee: (unassigned) => Steve Beattie (sbeattie)

** Changed in: glibc (Ubuntu Xenial)
 Assignee: (unassigned) => Steve Beattie (sbeattie)

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

Title:
  Ubuntu 14.04 broken during PXE boot

Status in eglibc package in Ubuntu:
  Invalid
Status in glibc package in Ubuntu:
  Fix Committed
Status in eglibc source package in Precise:
  Confirmed
Status in glibc source package in Precise:
  Invalid
Status in eglibc source package in Trusty:
  Confirmed
Status in glibc source package in Trusty:
  Invalid
Status in eglibc source package in Xenial:
  Invalid
Status in glibc source package in Xenial:
  Confirmed
Status in eglibc source package in Yakkety:
  Invalid
Status in glibc source package in Yakkety:
  Invalid

Bug description:
  After installing the libc6_2.19-0ubuntu6.10_amd64_udeb package during
  the automated install of ubuntu 14.04.5, the system was suddenly
  unable to resolve hostnames via dns. Installing -0ubuntu6.9 resolved
  the issue. Reinstalling -ubuntu6.10 broke the system again.

  I note that -ubuntu6.10 was recently added to the archive.

  I am currently unable to install Ubuntu 14.04.5.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1674532/+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 1674532] Re: Ubuntu 14.04 broken during PXE boot

[Adam Conrad]

** Also affects: glibc (Ubuntu)
   Importance: Undecided
   Status: New

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

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

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

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

** Also affects: glibc (Ubuntu Precise)
   Importance: Undecided
   Status: New

** Also affects: eglibc (Ubuntu Precise)
   Importance: Undecided
   Status: New

** Also affects: glibc (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: eglibc (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Changed in: eglibc (Ubuntu)
   Status: Confirmed => Invalid

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

** Changed in: eglibc (Ubuntu Precise)
   Status: New => Confirmed

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

** Changed in: eglibc (Ubuntu Trusty)
   Status: New => Confirmed

** Changed in: eglibc (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: eglibc (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: glibc (Ubuntu Precise)
   Status: New => Invalid

** Changed in: glibc (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: glibc (Ubuntu)
 Assignee: (unassigned) => Adam Conrad (adconrad)

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

Title:
  Ubuntu 14.04 broken during PXE boot

Status in eglibc package in Ubuntu:
  Invalid
Status in glibc package in Ubuntu:
  Fix Committed
Status in eglibc source package in Precise:
  Confirmed
Status in glibc source package in Precise:
  Invalid
Status in eglibc source package in Trusty:
  Confirmed
Status in glibc source package in Trusty:
  Invalid
Status in eglibc source package in Xenial:
  Invalid
Status in glibc source package in Xenial:
  New
Status in eglibc source package in Yakkety:
  Invalid
Status in glibc source package in Yakkety:
  New

Bug description:
  After installing the libc6_2.19-0ubuntu6.10_amd64_udeb package during
  the automated install of ubuntu 14.04.5, the system was suddenly
  unable to resolve hostnames via dns. Installing -0ubuntu6.9 resolved
  the issue. Reinstalling -ubuntu6.10 broke the system again.

  I note that -ubuntu6.10 was recently added to the archive.

  I am currently unable to install Ubuntu 14.04.5.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1674532/+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 1625222] Re: d-i is missing usb support for platforms that use the xhci-platform driver

[Adam Conrad]

** Also affects: debian-installer (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: debian-installer (Ubuntu Xenial)
   Status: New => Fix Released

** Changed in: debian-installer (Ubuntu Zesty)
   Status: New => Fix Released

** Changed in: debian-installer (Ubuntu Yakkety)
 Assignee: (unassigned) => Adam Conrad (adconrad)

** Changed in: debian-installer (Ubuntu Trusty)
 Assignee: (unassigned) => Adam Conrad (adconrad)

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

Title:
  d-i is missing usb support for platforms that use the xhci-platform
  driver

Status in debian-installer package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in debian-installer source package in Trusty:
  New
Status in linux source package in Trusty:
  Invalid
Status in debian-installer source package in Xenial:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in debian-installer source package in Yakkety:
  New
Status in linux source package in Yakkety:
  Fix Released
Status in debian-installer source package in Zesty:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

Bug description:
  [Impact]
  Any platform that gets usb support from the xhci-platform driver does not 
have usb enabled in d-i.

  [Test Case]
  Boot into d-i and attempt to use a usb device, i.e. keyboard.

  [Regression Risk]
  Extremely low as this is a driver that is already present in the kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1625222/+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 1625222] Re: d-i is missing usb support for platforms that use the xhci-platform driver

[Adam Conrad]

** Also affects: debian-installer (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  d-i is missing usb support for platforms that use the xhci-platform
  driver

Status in debian-installer package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in debian-installer source package in Trusty:
  New
Status in linux source package in Trusty:
  Invalid
Status in debian-installer source package in Xenial:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in debian-installer source package in Yakkety:
  New
Status in linux source package in Yakkety:
  Fix Released
Status in debian-installer source package in Zesty:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

Bug description:
  [Impact]
  Any platform that gets usb support from the xhci-platform driver does not 
have usb enabled in d-i.

  [Test Case]
  Boot into d-i and attempt to use a usb device, i.e. keyboard.

  [Regression Risk]
  Extremely low as this is a driver that is already present in the kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1625222/+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 1638306] Re: [SRU] zypper binary shipped w/ Ubuntu Xenial requires rebuild (relocation error)

[Adam Conrad]

Hello Markus, or anyone else affected,

Accepted zypper into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/zypper/1.12.4-1build0.1 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: zypper (Ubuntu Xenial)
   Status: New => Fix Committed

** Tags added: verification-needed

** Changed in: zypper (Ubuntu)
   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/1638306

Title:
  [SRU] zypper binary shipped w/ Ubuntu Xenial requires rebuild
  (relocation error)

Status in zypper package in Ubuntu:
  Fix Released
Status in zypper source package in Xenial:
  Fix Committed

Bug description:
  [IMPACT]
  zypper is not usable at all.
  $ zypper -V
  zypper: relocation error: zypper: symbol 
_ZN4zypp5CpeId11NoThrowType13lastMalformedE, version ZYPP_plain not defined in 
file libzypp.so.1503 with link time reference

  [TEST CASE]
  * run: zypper -V

  [Regression Potential]
  None

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zypper/+bug/1638306/+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 1662116] Re: open-vm-tools 2:10.0.7-3227872-2ubuntu1 ADT test failure with linux-hwe 4.8.0-37.39~16.04.2

[Adam Conrad]

Hello Andy, or anyone else affected,

Accepted open-vm-tools into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/open-vm-
tools/2:10.0.7-3227872-5ubuntu1~16.04.1 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Also affects: open-vm-tools (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: open-vm-tools (Ubuntu)
   Status: In Progress => Fix Released

** Changed in: open-vm-tools (Ubuntu Xenial)
 Assignee: (unassigned) => Andy Whitcroft (apw)

** Changed in: open-vm-tools (Ubuntu Xenial)
   Status: New => Fix Committed

** Tags added: verification-needed

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

Title:
  open-vm-tools 2:10.0.7-3227872-2ubuntu1 ADT test failure with linux-
  hwe 4.8.0-37.39~16.04.2

Status in open-vm-tools package in Ubuntu:
  Fix Released
Status in open-vm-tools source package in Xenial:
  Fix Committed

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial-canonical-kernel-team-unstable/xenial/amd64/o/open-vm-tools/20170205_185226_c750f@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial-canonical-kernel-team-unstable/xenial/i386/o/open-vm-tools/20170205_185956_c750f@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1662116/+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 1553176] Re: BIND ignores nanoseconds field in timestamps, fails to load newer versions of zones on reload

[Adam Conrad]

Hello LaMont, or anyone else affected,

Accepted bind9 into trusty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/bind9/1:9.9.5.dfsg-
3ubuntu0.12 in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: bind9 (Ubuntu Trusty)
   Status: New => Fix Committed

** Tags added: verification-needed

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

** Changed in: bind9 (Ubuntu Trusty)
 Assignee: (unassigned) => LaMont Jones (lamont)

-- 
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:
  Fix Released
Status in bind9 source package in Trusty:
  Fix Committed
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

[Group.of.nepali.translators] [Bug 1566352] Re: AWSCLI doesn't support S3 in eu-central-1

[Adam Conrad]

Hello psl, or anyone else affected,

Accepted awscli into yakkety-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/awscli/1.11.13-1~16.10.0 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

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

** Changed in: awscli (Ubuntu)
   Status: Confirmed => Fix Released

** Changed in: awscli (Ubuntu Yakkety)
   Status: New => Fix Committed

** Tags added: verification-needed

** Changed in: awscli (Ubuntu Xenial)
   Status: New => Fix Committed

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

Title:
  AWSCLI doesn't support S3 in eu-central-1

Status in awscli package in Ubuntu:
  Fix Released
Status in awscli source package in Xenial:
  Fix Committed
Status in awscli source package in Yakkety:
  Fix Committed

Bug description:
  Ubuntu 14.04.4
  awscli 1.2.9-2

  AWS S3 in EU (eu-central-1) changed authorization method to AWS4-HMAC-
  SHA256. This is not supported in awscli 1.2.9-2. Such S3 bucket cannot
  be used with awscli. Authorization method AWS4-HMAC-SHA256 is used in
  all new AWS regions. This problem is addresses in newer awscli
  release.

  HOW to test it:

  $ aws  s3 ls s3://some-eu-central-1-bucket

  A client error (InvalidRequest) occurred when calling the ListObjects
  operation: The authorization mechanism you have provided is not
  supported. Please use AWS4-HMAC-SHA256.

  INFO:
  
http://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4-authenticating-requests.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/awscli/+bug/1566352/+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 1642730] Re: [SRU] Backport awscli 1.11.13-1 (universe) from Debian unstable (main)

[Adam Conrad]

** Also affects: python-botocore (Ubuntu)
   Importance: Undecided
   Status: New

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

** Changed in: python-botocore (Ubuntu)
   Status: New => Fix Released

** Also affects: python-s3transfer (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: python-s3transfer (Ubuntu)
   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/1642730

Title:
  [SRU] Backport awscli 1.11.13-1 (universe) from Debian unstable (main)

Status in awscli package in Ubuntu:
  Fix Released
Status in python-botocore package in Ubuntu:
  Fix Released
Status in python-s3transfer package in Ubuntu:
  Fix Released
Status in awscli source package in Xenial:
  New
Status in python-botocore source package in Xenial:
  New
Status in python-s3transfer source package in Xenial:
  Fix Committed
Status in awscli source package in Yakkety:
  New
Status in python-botocore source package in Yakkety:
  New
Status in python-s3transfer source package in Yakkety:
  New

Bug description:
  Please sync awscli 1.11.13-1 (universe) from Debian unstable (main)

  [Impact]

   * The Amazon EC2 "Elastic Network Adapter" ('ENA') driver has recently been
 SRU'd into most supported Ubuntu kernels (>= Trusty) via LP: #1635721.
 However, to actually enable the ENA hardware on an EC2 instance requires
 use of an 'awscli' userspace command:

  aws ec2 modify-instance-attribute --ena-support ...

 as documented here:
 
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/enhanced-networking-ena.html

 The "modify-instance-attribute --ena-support" feature first appears in
 the latest Debian (or Zesty) version of awscli and its dependencies.  We
 need the feature for Xenial and Yakkety.

   * This set of three packages sync'ed from Debian is required, and
 work fine in Xenial and Yakkety (a solution for trusty is t.b.d).
 Note that Zesty already carries these exact package versions:

awscli (1.11.13-1)
python-botocore (1.4.70-1)
python-s3transfer (0.1.9-1)

   * As a bonus this will also resolve an unrelated bug report:
   LP: #1566352 "AWSCLI doesn't support S3 in eu-central-1"

  [Test Case]

   * Simple test: Check whether modify-instance-attribute mentions the feature:
 $ aws ec2 modify-instance-attribute help | grep ena-support
[--ena-support | --no-ena-support]  <-- yes
{no output} <-- no

   * Full test: Launch an x1.32xlarge large instance with Ubuntu kernel version
 >= xenial (4.4.0-47.68) or trusty (3.13.0-102.149), then follow AWS doc
 url above to enable and verify --ena-support.

  [Regression Potential]

   * Updating awscli and python-botocore could possibly introduce regressions
 in the myriad features they provide, but we believe these packages to be
 backwards-compatible and well-tested upstream.  The newer versions are
 known to be widely used by Ubuntu users (e.g. installed from upstreams'
 github).  Any regressions would likely be reported to us (very quickly)
 by AWS users.

   * python-s3transfer is new as of Zesty so no regression potential is
 expected for X and Y (the new awscli package depends on python-s3transfer).

   * These packages (both old and new versions) have no Ubuntu-specific
 divergence from Debian, so updating them all (X, Y, Z, and Debian)
 to the same modern upstream baseline seems robust and safe.

  Changelog entries since current xenial version 1.10.1-1:

  awscli (1.11.13-1) unstable; urgency=medium

* New upstream version 1.11.13 (Closes: #819451)
* debian/patches: Refresh patches.

   -- TANIGUCHI Takaki   Thu, 10 Nov 2016 19:50:29
  +0900

  awscli (1.11.7-2) unstable; urgency=medium

* debian/control: add python3-s3tranfert to B-D. (Closes: #841064)

   -- TANIGUCHI Takaki   Sun, 23 Oct 2016 21:31:02
  +0900

  awscli (1.11.7-1) unstable; urgency=medium

* debian/control: Update Vcs-* to new git repository.
* New upstream version 1.11.7

   -- TANIGUCHI Takaki   Thu, 20 Oct 2016 16:29:01
  +0900

  awscli (1.11.2-1) unstable; urgency=medium

* New upstream release
* Bump Standards-Version to 3.9.8 
* debian/rules: Change to library style layout.
* debian/links: link from doc direcotory.
* debian/control: Move to under DPMT.

   -- TANIGUCHI Takaki   Sun, 16 Oct 2016 19:05:50
  +0900

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : 

[Group.of.nepali.translators] [Bug 1648873] Re: Ubuntu 16.10 netboot install fails with "Oops: Exception in kernel mode, sig: 5 [#1] " (lpfc)

[Adam Conrad]

** Also affects: debian-installer (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: debian-installer (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

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

** Also affects: debian-installer (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

** Changed in: debian-installer (Ubuntu Xenial)
 Assignee: (unassigned) => Adam Conrad (adconrad)

** Changed in: debian-installer (Ubuntu Yakkety)
 Assignee: (unassigned) => Adam Conrad (adconrad)

** Changed in: linux (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: debian-installer (Ubuntu)
 Assignee: (unassigned) => Adam Conrad (adconrad)

** Changed in: linux (Ubuntu Yakkety)
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

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

Title:
  Ubuntu 16.10 netboot install fails with "Oops: Exception in kernel
  mode, sig: 5 [#1] " (lpfc)

Status in debian-installer package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Triaged
Status in debian-installer source package in Xenial:
  New
Status in linux source package in Xenial:
  Invalid
Status in debian-installer source package in Yakkety:
  New
Status in linux source package in Yakkety:
  New

Bug description:
  == Comment: #33 - Mauricio Faria De Oliveira - 2016-12-09 06:49:57 ==

  Hi Canonical,

  Can you please apply this patch [1] to 16.10 and 16.04.x HWE (4.8) ?
  It's fixes a regression introduced in 4.8.

  As you can see, it's in the SCSI maintainer (James Bottomley)'s
  'fixes' branch, but didn't make 4.9-rc8 (maybe he considered it late
  for this one).

  We have installer, boot, and post-boot problems due to this one.
  It'd be good if the netboot images for 16.04.x HWE kernel can get it too.

  Thank you,

  [1] scsi: lpfc: fix oops/BUG in lpfc_sli_ringtxcmpl_put() 
  
http://git.kernel.org/cgit/linux/kernel/git/jejb/scsi.git/commit/?h=fixes=2319f847a8910cff1d46c9b66aa1dd7cc3e836a9

  Historical context:

  == Comment: #0 - HARSHA THYAGARAJA - 2016-11-21 02:39:35 ==
  ---Problem Description---
  Ubuntu 16.10 netboot install fails with "Oops: Exception in kernel mode. " 
(kernel: 4.8.0-27)
   
  Machine Type = Power8 baremetal  
   
  ---boot type---
  QEMU direct boot kernel/initrd
   
  ---Kernel cmdline used to launch install---
  On a Power8 server,  Using kernel and initrd images, 

  netcfg/disable_dhcp=true netcfg/confirm_static=true 
netcfg/choose_interface=98:BE:94:00:4C:68 netcfg/get_ipaddress=9.47.67.159/20 
netcfg/get_gateway=9.47.79.254 netcfg/get_nameservers=
   
  ---Install repository type---
  Internet repository
   
  ---Install repository Location---
  
http://ports.ubuntu.com/ubuntu-ports/dists/yakkety/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/
   
  ---Point of failure---
  Other failure during installation (stage 1)

  == Comment: #1 - HARSHA THYAGARAJA - 2016-11-21 02:41:54 ==
  The netboot install fails and Call traces are seen at the Disk detection step.

  == Comment: #8 - Mauricio Faria De Oliveira - 2016-11-21 15:58:25 ==
  Finally got it.

  The assembly offset/code + the trap signal is due to this BUG_ON(),
  and the second condition triggered the trap.

  Checking why piocb is not NULL but piocb->vport is NULL.
  This might have happened in the lpfc_linkdown_port() path, in the stack trace.

  Would need a more readable console log (ie, dmesg, as requested in
  comments 5, 3) to help understanding it.

  --

  static int
  lpfc_sli_ringtxcmpl_put(struct lpfc_hba *phba, struct lpfc_sli_ring *pring,
  struct lpfc_iocbq *piocb)
  {
  lockdep_assert_held(>hbalock);

  BUG_ON(!piocb || !piocb->vport);
  <...>
  }

  [  226.147886] NIP [db7324c0]
  lpfc_sli_ringtxcmpl_put+0x48/0x120 [lpfc]

  0x2478 + 0x48 = 0x24c0 (tdnei; trap doubleword not equal immediate)

  2478 :
  <...>
  2498:   78 2b bf 7c mr  r31,r5 // r31 is *piocb (r5 is the 
3rd function parameter)
  249c:   78 1b 7d 7c mr  r29,r3
  24a0:   78 23 9e 7c mr  r30,r4
  24a4:   01 00 00 48 bl  24a4 <lpfc_sli_ringtxcmpl_put+0x2c> 
// probably converted at module load time to the call lockdep_assert_held()
  24a8:   00 00 00 60 nop
  24ac:   00 00 bf 2f cmpdi   cr7,r31,0 // compare piocb with 0. 
checking for NULL.
  24b0:   70 00 9e 41 beq cr7,2520 
<lpfc_sli_ringtxcmpl_put+0xa8> // if equal to zero, branch out. done w/ the  
former part of the OR check.
  24b4:   e8 00 3f e9 ld  r9,

[Group.of.nepali.translators] [Bug 1640518] Re: MongoDB Memory corruption

[Adam Conrad]

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

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

** Changed in: glibc (Ubuntu)
 Assignee: Taco Screen team (taco-screen-team) => Adam Conrad (adconrad)

** Changed in: glibc (Ubuntu Xenial)
 Assignee: (unassigned) => Adam Conrad (adconrad)

** Changed in: glibc (Ubuntu Yakkety)
 Assignee: (unassigned) => Adam Conrad (adconrad)

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

Title:
  MongoDB Memory corruption

Status in GLibC:
  Unknown
Status in glibc package in Ubuntu:
  New
Status in glibc source package in Xenial:
  New
Status in glibc source package in Yakkety:
  New

Bug description:
  == Comment: #0 - Calvin L. Sze <calv...@us.ibm.com> - 2016-11-01 23:09:10 ==
  Team has changed to the Bare-metal Ubuntu 16.4.  The problem still exists, so 
it is not related to the virtualization. 

  Since the bug is complicated to reproduce,  Could we use sets of tools
  to collect the data when this happens?

  
  ---Problem Description---
  MongoDB has memory corruption issues which only occurred on Ubuntu 16.04, it 
doesn't occur on Ubuntu 15.
   
  Contact Information =Calvin Sze/Austin/IBM
   
  ---uname output---
  Linux master 4.4.0-36-generic #55-Ubuntu SMP Thu Aug 11 18:00:57 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = Model: 2.1 (pvr 004b 0201) Model name: 
   POWER8E (raw), altivec supported 
   
  ---System Hang---
   the system is still alive
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Unfortunately, not very easily. I had a test case that I was running on 
ubuntu1604-ppc-dev.pic.build.10gen.cc and -ppc-dev.pic.build.10gen.cc. I 
understand these to be two VMs running on the same physical host.

  About 3.5% of the test runs on ubuntu1604-ppc-dev.pic.build.10gen.cc
  would fail, but all of the runs on the other machine passed.
  Originally, this failure manifested as the GCC stack protector (from
  -fstack-protector-strong) claiming stack corruption.

  Hoping to be able to see the data that was being written and
  corrupting the stack, I manually injected a guard region into the
  stack of the failing functions as follows:


  
  +namespace {
  +
  +class Canary {
  +public:
  +
  +static constexpr size_t kSize = 1024;
  +
  +explicit Canary(volatile unsigned char* const t) noexcept : _t(t) {
  +::memset(const_cast(_t), kBits, kSize);
  +}
  +
  +~Canary() {
  +_verify();
  +}
  +
  +private:
  +static constexpr uint8_t kBits = 0xCD;
  +static constexpr size_t kChecksum = kSize * size_t(kBits);
  +
  +void _verify() const noexcept {
  +invariant(std::accumulate(&_t[0], &_t[kSize], 0UL) == kChecksum);
  +}
  +
  +const volatile unsigned char* const _t;
  +};
  +
  +}  // namespace
  +

   Status bsonExtractField(const BSONObj& object, StringData fieldName, 
BSONElement* outElement) {
  +
  +volatile unsigned char* const cookie = static_cast(alloca(Canary::kSize));
  +const Canary c(cookie);
  + 

  When running with this, the invariant would sometimes fire. Examining
  the stack cookie under the debugger would show two consecutive bytes,
  always at an offset ending 0x...e, written as either 0 0, or 0 1,
  somewhere at random within the middle of the cookie.

  This indicated that it was not a conventional stack smash, where we
  were writing past the end of a contiguous buffer. Instead it appeared
  that either the currently running thread had reached up some arbitrary
  and random amount on the stack and done either two one-byte writes, or
  an unaligned 2-byte write. Another possibility was that a local
  variable had been transferred to another thread, which had written to
  it.

  However, while looking at the code to find such a thing, I realized
  that there was another possibility, which was that the bytes had never
  been written correctly in the first place. I changed the stack canary
  constructor to be:


  +explicit Canary(volatile unsigned char* const t) noexcept : _t(t) {
  +::memset(const_cast(_t), kBits, kSize);
  +_verify();
  +}  

  So that immediately after writing the byte pattern to the stack
  buffer, we verified the contents we wrote. Amazingly, this *failed*,
  with the same corruption as seen before. This means that either
  between the time we called memset to write the bytes and when we read
  them back, something either overwrote the stack cookie region, or that
  the bytes were never written correctly by memset, or that memset wrote
  the bytes, but the underlying physical memory never took the write.



   
  Stack trace output:
   no
   
  Oops output:
   no
   
 

[Group.of.nepali.translators] [Bug 1642390] [NEW] Disable lock-elision in glibc pending upstream changes

[Adam Conrad]

Public bug reported:

[ SRU Justification ]
A long thread on debian-devel[1] has pointed out that hardware lock elision 
behaves differently (arguably, more correctly) in the face of incorrect pthread 
usage, especially where double-unlocks are concerned.  While this isn't itself 
a bug, it's quite true that we have no way of knowing right now just how many 
third party sources are buggy, and as people are upgrading to hardware that 
supports this feature, more software may crash in the future.

The long-term goal should be to try to ferret out all the bad actors
here, fix them, and re-enable hardware lock elision as the default, but
the sane conservative choice seems to be to just disable the feature
entirely for now, while we (the glibc upstream community) work on making
lock elision a per-process opt-in.

[1] https://lists.debian.org/debian-devel/2016/11/msg00210.html

[ Proposed Fix ]
This SRU will disable lock elision entirely, thus avoiding the problematic 
codepaths.  A future SRU will re-enable building those codepaths, but in such a 
way that they're disabled by default with a per-process environment twiddle to 
enable it on demand.

[ Regression Potential ]
There's a potential for performance regressions, however given that most x86 
users are only just now upgrading to hardware that supports this feature, the 
status quo is that this codepath is dead to most users.  As for s390x and PPC, 
we've had requests to disable lock elision by default on both arches (entirely 
on s390x, conditionally on PPC), and those requests will be somewhat satisfied 
by this SRU, and cleaned up in the future SRU where we integrate the 
upstream-concensus patch to allow it to be conditionally re-enabled.

[ Testing ]
autopkgtest regressions will be our guide here on if this SRU is causing any 
issues.

** Affects: glibc (Ubuntu)
 Importance: Undecided
 Assignee: Adam Conrad (adconrad)
 Status: New

** Affects: glibc (Ubuntu Xenial)
 Importance: Undecided
 Assignee: Adam Conrad (adconrad)
 Status: New

** Affects: glibc (Ubuntu Yakkety)
 Importance: Undecided
 Assignee: Adam Conrad (adconrad)
 Status: New

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

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

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

Title:
  Disable lock-elision in glibc pending upstream changes

Status in glibc package in Ubuntu:
  New
Status in glibc source package in Xenial:
  New
Status in glibc source package in Yakkety:
  New

Bug description:
  [ SRU Justification ]
  A long thread on debian-devel[1] has pointed out that hardware lock elision 
behaves differently (arguably, more correctly) in the face of incorrect pthread 
usage, especially where double-unlocks are concerned.  While this isn't itself 
a bug, it's quite true that we have no way of knowing right now just how many 
third party sources are buggy, and as people are upgrading to hardware that 
supports this feature, more software may crash in the future.

  The long-term goal should be to try to ferret out all the bad actors
  here, fix them, and re-enable hardware lock elision as the default,
  but the sane conservative choice seems to be to just disable the
  feature entirely for now, while we (the glibc upstream community) work
  on making lock elision a per-process opt-in.

  [1] https://lists.debian.org/debian-devel/2016/11/msg00210.html

  [ Proposed Fix ]
  This SRU will disable lock elision entirely, thus avoiding the problematic 
codepaths.  A future SRU will re-enable building those codepaths, but in such a 
way that they're disabled by default with a per-process environment twiddle to 
enable it on demand.

  [ Regression Potential ]
  There's a potential for performance regressions, however given that most x86 
users are only just now upgrading to hardware that supports this feature, the 
status quo is that this codepath is dead to most users.  As for s390x and PPC, 
we've had requests to disable lock elision by default on both arches (entirely 
on s390x, conditionally on PPC), and those requests will be somewhat satisfied 
by this SRU, and cleaned up in the future SRU where we integrate the 
upstream-concensus patch to allow it to be conditionally re-enabled.

  [ Testing ]
  autopkgtest regressions will be our guide here on if this SRU is causing any 
issues.

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

[Group.of.nepali.translators] [Bug 1631474] Re: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option

[Adam Conrad]

** Also affects: initramfs-tools (Ubuntu Yakkety)
   Importance: High
 Assignee: Dave Chiluk (chiluk)
   Status: In Progress

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

Title:
  No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot
  option

Status in initramfs-tools package in Ubuntu:
  In Progress
Status in initramfs-tools source package in Xenial:
  Confirmed
Status in initramfs-tools source package in Yakkety:
  In Progress

Bug description:
  [Impact]

   * 0.122ubuntu8.3 of initramfs-tools no longer correctly processed
  ip=dhcp or ip=:eth0:dhcp

   * Regression-updates

   * The fix better parses the ip= command line argument.

  [Test Case]

   * Create a machine that boots using an nfsroot.

   * Use ip=:eth0:dhcp on the kernel command line.  To set up
     networking.

   * Discover that the device never comes up because, networking is not
  configured correctly.

  [Regression Potential]

   * Regressions potential is limited to machines using
  ip={""|*|on|any|dhcp} on the kernel command line.  As this is
  already broken regression potential is minimal.  This is common on
  machines that use nfsroot or otherwise pxe boot.

  [Other Info]

   * There are a number of other issues in this code base that are not solved 
by this fix.
   * The networking configuration does not strictly follow the kernel 
documentation as described 
https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt . This 
should be fixed.

  Original Bug Description Follows==

  initramfs-tools 0.122ubuntu8.3 introduced a serious regression where
  networking is not initialized when the boot option "ip=dhcp" is
  provided. We are seeing this problem in AWS, but cannot confirm if
  this issue is specific to AWS or will occur with different hardware or
  in different environments.

  Removing "ip=dhcp" from the boot options with 0.122ubuntu8.3 results
  in networking being configured.

  The issue does not occur with 0.122ubuntu8.2 or previous versions when
  "ip=dhcp" is set.

  AWS has no console so debugging is not a trivial task. I do have a
  console log with some output, and will update this bug shortly with
  it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+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 1598212] Re: /etc/os-release: Please specify VERSION_CODENAME

[Adam Conrad]

** Also affects: base-files (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

Title:
  /etc/os-release: Please specify VERSION_CODENAME

Status in base-files package in Ubuntu:
  New
Status in base-files source package in Xenial:
  New
Status in base-files package in Debian:
  New

Bug description:
  The os-release specification was updated in systemd > 230 to also
  include a VERSION_CODENAME parameter:
  
https://github.com/systemd/systemd/commit/646b997c118e261c5ececc434dd40d0dbdbac4d8

  Please replace the custom UBUNTU_CODENAME parameter by
  VERSION_CODENAME in yakkety and add VERSION_CODENAME to /etc/os-
  release to all stable releases.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1598212/+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 1612120] Re: $SNAP_USER_DATA is no longer created by snap-confine but is not yet created by snapd

[Adam Conrad]

** Also affects: snap-confine (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: snap-confine (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: snap-confine (Ubuntu Xenial)
   Status: New => Fix Committed

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

Title:
  $SNAP_USER_DATA is no longer created by snap-confine but is not yet
  created by snapd

Status in Snappy Launcher:
  Fix Committed
Status in snap-confine package in Ubuntu:
  New
Status in snap-confine source package in Xenial:
  Fix Committed

Bug description:
  We've noticed that the code that creates the $SNAP_USER_DATA directory
  has now been removed from snap-confine for the past few releases but
  the corresponding code in snapd, that depends on snap-exec, is not yet
  active. This has lead to some snaps that rely on it to have no way to
  create per-user data directories.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snap-confine/+bug/1612120/+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 1606640] [NEW] a typo in 481-1 broke lesspipe ddeb support

[Adam Conrad]

Public bug reported:

[ SRU Justification ]
Due to the bug, "less foo.ddeb" now gives you binary goop, instead of executing 
dpkg.

[ Test Case ]
Make sure the output of "less foo.ddeb" is similar to "less foo.deb", rather 
than a binary dump.

[ Regression Potential ]
nil, it's a 1-char fix.

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

** Affects: less (Ubuntu Xenial)
 Importance: Undecided
 Status: New

** Affects: less (Debian)
 Importance: Unknown
 Status: Unknown

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

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

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

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

Title:
  a typo in 481-1 broke lesspipe ddeb support

Status in less package in Ubuntu:
  New
Status in less source package in Xenial:
  New
Status in less package in Debian:
  Unknown

Bug description:
  [ SRU Justification ]
  Due to the bug, "less foo.ddeb" now gives you binary goop, instead of 
executing dpkg.

  [ Test Case ]
  Make sure the output of "less foo.ddeb" is similar to "less foo.deb", rather 
than a binary dump.

  [ Regression Potential ]
  nil, it's a 1-char fix.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/less/+bug/1606640/+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 1597365] Re: errinjct tool error while running EEH tests (powerpc-utils)

[Adam Conrad]

Our librtas 2.0.0 contains a cherrypick of the errinjct fixes, and I'm
uploading powerpc-utils 1.3.2 right now.

Will cherrypick the ppc-utils fixes to xenial after that.

** Also affects: powerpc-utils (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

Title:
  errinjct tool error while running EEH tests (powerpc-utils)

Status in powerpc-utils package in Ubuntu:
  Triaged
Status in powerpc-utils source package in Xenial:
  New

Bug description:
  == Comment: #0 - Manvanthara B. Puttashankar - 2016-06-29 01:40:42 ==
  ---Problem Description---
  errinjct tool error while running EEH tests (powerpc-utils)

  ---uname output---
  Linux ltciofvtr-s822l2-lp3 4.4.0-24-generic #43-Ubuntu SMP Wed Jun 8 19:25:36 
UTC 2016 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = s822l 
   
  ---Steps to Reproduce---
   errinjct tool needs to pick two patch to address the below error

  
  errinjct eeh -v -f 6 -s net/eth1 -a 0xde00 -m 0xFF80
  Injecting an ioa-bus-error with the following data:

  BUS ADDR: de00
  ADDR MASK:ff80
  CONFIG ADDR:  90
  PHB UNIT_ID:  8002135
  FUNCTION: 6
  Store to PCI Memory Address Space - inject an Adress Parity Error
  errinjct: Could not open RTAS error injection facility
  errinjct: librtas returned an unknown error code (-50331649) for function 
ioa-bus-error

  Parent bug: Bug 121866 : EEH via errinjct tool fails with librtas
  error in Ubuntu 16.04 (Shiner-T & Grand Canyon)

  errinjct issues will be solved with multiple patches 1 librtas + 2
  errijnct.

  Based on suggestion from developer in Bug 121866 reporting this
  specific issue to powerpc-utils package , two patch needs to be picked
  by canonical.

  Note: have verified the powerpc-utils for 16.04.01 , the patch hasn't
  gone into yet.

  upstream patch fix link: 
https://github.com/nfont/powerpc-utils/tree/next/src/errinjct
   
  Userspace tool common name: errinjct 
   
  The userspace tool has the following bit modes: ppc64le 

  Userspace rpm: powerpc-utils

  
  == Comment: #1 - Manvanthara B. Puttashankar  - 
2016-06-29 01:48:02 ==
  commits to be picked up

  
  commit 386a07c4dc6c09d35116dc6064f7a83d76f4415b
  Author: Nathan Fontenot 
  Date:   Tue May 24 16:32:39 2016 -0400

  errinjct: Correct read_file() error checking
  
  When reading files from syfs the file length returned from a stat()
  call does not always match the actual length of the file. The read_file()
  routine should be checking for an error return from the read() call
  instead of checking that the amount read matches the file length returned
  from a stat() call.
  
  Signed-off-by: Nathan Fontenot 

  commit 42b83884bfb51c0c8b23bf2949157430f8468caa
  Author: Nathan Fontenot 
  Date:   Tue May 24 16:31:37 2016 -0400

  errinjct: Recognize -5 return from rtas
  
  Update the errinjct command to recognize the rturn code of -5 from
  rtas indicating that PCI error injection is not enabled.
  
  Signed-off-by: Nathan Fontenot 

  
  commit ab848a8d5cc4c4b9f5faef1b31be3982fb7d4bf2
  Author: Nathan Fontenot 
  Date:   Tue May 24 16:30:33 2016 -0400

  errinjct: Correct config_addr parsing
  
  A recent patch (commit id: ccc9c72cec2a4) to move the errinjct function to
  using a common read_file() routine did not correctly update the
  get_config_addr_from_reg() function. This patch corrects this to return 
the
  proper config address.
  
  Signed-off-by: Nathan Fontenot 

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/powerpc-utils/+bug/1597365/+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 1599191] Re: [LTCTest][Opal][OP820] update_flash -d option is throwing /usr/sbin/update_flash_nv: 595: [: x47: unexpected operator

[Adam Conrad]

** Package changed: powerpc-ibm-utils (Ubuntu) => powerpc-utils (Ubuntu)

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

Title:
  [LTCTest][Opal][OP820] update_flash -d option is throwing
  /usr/sbin/update_flash_nv: 595: [: x47: unexpected operator

Status in powerpc-utils package in Ubuntu:
  Fix Released
Status in powerpc-utils source package in Xenial:
  Fix Released

Bug description:
  [SRU Justification]
  On an OpenPower system, '/usr/sbin/update_flash_nv -d' will print a 
gratuitous error message, and will not correctly report failures to query the 
firmware version.

  [Test case]
  1. On an OpenPower system (as determined by the presence of the file 
/proc/device-tree/bmc), run 'sudo update_flash_nv -d'.  Observe that an error 
message is printed before the version information.
  2. Install powerpc-utils from xenial-proposed.
  3. Run 'sudo update_flash_nv -d' again.  Verify that no error message is 
printed.

  [Regression potential]
  Minimal.  This is a targeted, one-line fix for a bashism in a shell script.

  ---Problem Description---
  update_flash -d option is throwing [: x47: unexpected operator message

  ---uname output---
  Linux ltc-garri2 4.4.0-30-generic #49-Ubuntu SMP Fri Jul 1 10:00:36 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = P8

  ---Steps to Reproduce---
   Install a P8 8335-GTB Hardware with Ubuntu 16.04.1 OS.
  Then execute the below command to check the version of the firmware installed 
on the machine.

  root@ltc-garri2:~# update_flash -d

  /usr/sbin/update_flash_nv: 595: [: x47: unexpected operator
  Firmware version:
   Product Name  : OpenPOWER Firmware
   Product Version   : IBM-garrison-ibm-OP8_v1.9_2.1
   Product Extra :op-build-dcacfac
   Product Extra :buildroot-bc248fa
   Product Extra :skiboot-5f25590
   Product Extra :hostboot-4c63029-6034fa6
   Product Extra :linux-4.4.9-openpower2-ebc7b6d
   Product Extra :petitboot-v1.1.1-fc477ec
   Product Extra :garrison-xml-b453a81
   Product Extra :occ-19a3ebc
   Product Extra :hostboot-binar
  root@ltc-garri2:~# echo $?
  0

  root@ltc-garri2:~# which update_flash
  /usr/sbin/update_flash

  root@ltc-garri2:~# dpkg -S /usr/sbin/update_flash
  powerpc-ibm-utils: /usr/sbin/update_flash
  root@ltc-garri2:~# dpkg --list | grep powerpc-ibm-utils
  ii  powerpc-ibm-utils  1.3.1-2 
ppc64el  utilities for maintenance of IBM PowerPC platforms

  Userspace tool common name: /usr/sbin/update_flash

  The userspace tool has the following bit modes: 64-bit

  Userspace package: powerpc-ibm-utils

  Below upstream patch fixes this issue:

  commit c3269d4e3d4882fd931d1df6aece0bec86fb6734
  Author: Vasant Hegde 
  Date:   Thu Jun 30 10:26:58 2016 -0400

  update_flash: Fix bashism issue in
  opp_display_current_fw_version()

  Ubuntu uses dash, not bash. We hit below warning on Ubuntu system.

  root@abc:/sys/firmware/devicetree/base/ibm,opal/sensors# update_flash -d
  /usr/sbin/update_flash_nv: 595: [: x43: unexpected operator
  Firmware version:
  
  

  == is a bashism. Replace it with =.

  Fixes: 767e3dd7 (update_flash: Add support for OpenPower system)
  Signed-off-by: Vasant Hegde 

  -Vasant

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/powerpc-utils/+bug/1599191/+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 1602035] Re: Maps app no longer works because MapQuest disabled access

[Adam Conrad]

** Also affects: livecd-rootfs (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: livecd-rootfs (Ubuntu)
   Status: New => Invalid

** Changed in: livecd-rootfs (Ubuntu Xenial)
 Assignee: (unassigned) => Adam Conrad (adconrad)

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

Title:
  Maps app no longer works because MapQuest disabled access

Status in Gnome Maps:
  Confirmed
Status in Ubuntu GNOME:
  Triaged
Status in gnome-maps package in Ubuntu:
  Triaged
Status in libchamplain package in Ubuntu:
  Triaged
Status in livecd-rootfs package in Ubuntu:
  Invalid
Status in ubuntu-gnome-meta package in Ubuntu:
  Fix Released
Status in gnome-maps source package in Trusty:
  Triaged
Status in gnome-maps source package in Wily:
  Triaged
Status in gnome-maps source package in Xenial:
  Triaged
Status in libchamplain source package in Xenial:
  Triaged
Status in livecd-rootfs source package in Xenial:
  New
Status in ubuntu-gnome-meta source package in Xenial:
  Fix Released
Status in gnome-maps package in Debian:
  Confirmed
Status in gnome-maps package in Fedora:
  Unknown

Bug description:
  As of today, MapQuest has disabled their free map tile feed. This
  means the Maps app no longer displays anything except a warning
  pointing to

  http://devblog.mapquest.com/2016/06/15/modernization-of-mapquest-
  results-in-changes-to-open-tile-access/

  Screenshot attached.

  [Impact]
  GNOME Maps is included by default in Ubuntu GNOME 15.10 and 16.04. The app 
currently is useless.

  Triaged as "High" because it "prevents the application or any
  dependencies from functioning correctly at all".
  https://wiki.ubuntu.com/Bugs/Importance

  This also breaks libchamplain (a library for embedding maps into your
  app). Once a fix is released, apps using libchamplain will likely need
  to be patched to use a different map provider.

  [Test Case]
  Install gnome-maps. Open the Maps app. Do you see maps?

  Note that maps are cached so you may not notice the feed has been
  disabled unless you try viewing a specific area at a close enough zoom
  that you have not viewed recently.

  [Regression Potential]
  No Stable Release Update is ready yet for this issue.

  https://mail.gnome.org/archives/desktop-devel-
  list/2016-July/msg3.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-maps/+bug/1602035/+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 1604441] Re: D-I on 16.04.1 breaks on usb probe and networking setup on secureboot

[Adam Conrad]

** Also affects: debian-installer (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: debian-installer (Ubuntu)
 Assignee: Mathieu Trudel-Lapierre (cyphermox) => Adam Conrad (adconrad)

** Changed in: debian-installer (Ubuntu Xenial)
 Assignee: (unassigned) => Adam Conrad (adconrad)

** Also affects: debian-installer (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

Title:
  D-I on 16.04.1 breaks on usb probe and networking setup on secureboot

Status in debian-installer package in Ubuntu:
  New
Status in debian-installer source package in Trusty:
  New
Status in debian-installer source package in Xenial:
  New

Bug description:
  On both netboot mini.iso and ubuntu server the installer fails probing
  usb and then fails to setup networking, for netboot this means you can
  not continue the install.

  Only happen on Securebot with just uefi it works fine.

  This is a critical fix required for 16.04.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1604441/+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 1604178] Re: arm64 server ISOs are now available

[Adam Conrad]

Hello dann, or anyone else affected,

Accepted installation-guide into xenial-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source
/installation-guide/20160121ubuntu2.2 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Also affects: installation-guide (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: installation-guide (Ubuntu Xenial)
   Status: New => Fix Committed

** Tags added: verification-needed

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

Title:
  arm64 server ISOs are now available

Status in installation-guide package in Ubuntu:
  Invalid
Status in installation-guide source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  In 20160121ubuntu2.1, I replaced the text that describes CD-ROM installation 
as the recommended install method for arm64 w/ a note saying CD-ROMs won't be 
available until 16.04.1. 16.04.1 is now imminent, and ISOs now exist, so it is 
now reasonable to revert that change.

  [Test Case]
  (Text Update)

  [Regression Risk]
  Minimal; just docs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/installation-guide/+bug/1604178/+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 1599219] Re: SRU: spl-linux: xenial: apply fix Fix do_div() types in condvar:timeout

[Adam Conrad]

** Also affects: spl-linux (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

Title:
  SRU: spl-linux: xenial: apply fix Fix do_div() types in
  condvar:timeout

Status in spl-linux package in Ubuntu:
  New
Status in spl-linux source package in Xenial:
  New

Bug description:
  [SRU JUSTIFICATION][XENIAL]

  The do_div() macro expects unsigned types and this is detected in
  powerpc implementation of do_div(). Make whole_delta and remain_delta 
unsigned.

  [FIX]
  Upstream spl fix 2a552736b7fc2bcb810cc520abd2ff9e229a9904 ("Fix do_div() 
types in condvar:timeout"), https://github.com/zfsonlinux/spl.git

  [TEST CASE]
  Must pass zfs regression tests.

  [REGRESSION POTENTIAL]
  Minimal, this touches the spl splat test module, so it's fix to the spl tests 
rather than core spl module.

  

  spl 0.6.5.7 has the following do_div fix that should be SRU'd to spl-
  linux 0.6.5.6 for Xenial:

  [PATCH] Fix do_div() types in condvar:timeout

  The do_div() macro expects unsigned types and this is detected in
  powerpc implementation of do_div().

  Signed-off-by: Brian Behlendorf 
  Closes #516

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/spl-linux/+bug/1599219/+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 1599221] Re: SRU: spl-linux: backport dep8 adt fixes from Yakkety

[Adam Conrad]

** Also affects: spl-linux (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

Title:
  SRU: spl-linux: backport dep8 adt fixes from Yakkety

Status in spl-linux package in Ubuntu:
  In Progress
Status in spl-linux source package in Xenial:
  New

Bug description:
  [SRU JUSTIFICATION][XENIAL]
  Since Xenial is an LTS, it makes sense to backport fixes to the adt testing 
that have landed in Yakkety in 0.6.5.7-0ubuntu4 and 0.6.5.7-0ubuntu3

  [FIX]
  Merge of adt test changes from Yakkety 0.6.5.7-0ubuntu4 and 0.6.5.7-0ubuntu3

  [REGRESSION POTENTAL]
  Will not break core spl functionality.  Any regressions in the tests will 
break the testing and not spl per se.

  ---

  Backport dep8 adt fix from Yakkety; namely:

  Add isolation-machine to tests/control
  Also restrict spl tests to 64 bit systems as that all we support for ZFS

  This is an amalgamation of two debian/tests sets of changes from
  0.6.5.7-0ubuntu4 and 0.6.5.7-0ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/spl-linux/+bug/1599221/+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 1597466] Re: dpkg giving warning about '/etc/lsb-release' version number not starting with a digit when there is no apparent problem in the file

[Adam Conrad]

** Changed in: ubuntu-gnome
   Status: Confirmed => Invalid

** Package changed: dpkg (Ubuntu) => ubuntu-gnome-default-settings
(Ubuntu)

** Also affects: ubuntu-gnome-default-settings (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

Title:
  dpkg giving warning about '/etc/lsb-release' version number not
  starting with a digit when there is no apparent problem in the file

Status in Ubuntu GNOME:
  Invalid
Status in ubuntu-gnome-default-settings package in Ubuntu:
  Confirmed
Status in ubuntu-gnome-default-settings source package in Xenial:
  New

Bug description:
  I have recently noticed (though I believe that during the upgrade from Ubuntu 
GNOME 15.10 to 16.04 I spotted the message when it got to the point of updating 
the '/etc/lsb-release' file) that sometimes 
  during an 'apt-get dist-upgrade' operation or similar that dpkg outputs this 
warning:

  dpkg: warning: version '/etc/lsb-release' has bad syntax: version
  number does not start with a digit

  The contents of my 'lsb-release' file is:

  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=16.04
  DISTRIB_CODENAME=xenial
  DISTRIB_DESCRIPTION="Ubuntu 16.04 LTS"

  So I assume that this is a dpkg bug as this was the standard file and
  I don't see any problems in it (I have also compared it to the one on
  14.04 and it is in the same format).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1597466/+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 1577413] Re: dpkg crashes if given -i directory as parameter

[Adam Conrad]

This seems to be fixed in yakkety, but I can reproduce it in xenial.

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

** Changed in: dpkg (Ubuntu)
   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/1577413

Title:
  dpkg crashes if given -i directory as parameter

Status in dpkg package in Ubuntu:
  Fix Released
Status in dpkg source package in Xenial:
  New

Bug description:
  $ sudo dpkg -i /tmp
  [sudo] password for user: 
  dpkg-split: error: error reading /tmp: Is a directory
  dpkg:../../src/unpack.c:123:deb_reassemble: internal error: unexpected exit 
status 2 from dpkg-split

  Aborted (core dumped)

  
  Installing a directory is of course an error from user, but dpkg should 
detect it and not crash.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: dpkg 1.18.4ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Mon May  2 17:14:01 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-02-12 (445 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: dpkg
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1577413/+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 1595882] Re: linux-snapdragon: 4.4.0-1019.22 -proposed tracker

[Adam Conrad]

** Changed in: kernel-sru-workflow/upload-to-ppa
   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/1595882

Title:
  linux-snapdragon: 4.4.0-1019.22 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-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 promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-snapdragon package in Ubuntu:
  Fix Released
Status in linux-snapdragon source package in Xenial:
  Fix Released

Bug description:
  This bug is for tracking the 4.4.0-1019.22 upload package. This bug
  will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1595874
  phase: Released
  proposed-announcement-sent: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1595882/+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 1595881] Re: linux-raspi2: 4.4.0-1016.22 -proposed tracker

[Adam Conrad]

** Changed in: kernel-sru-workflow/upload-to-ppa
   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/1595881

Title:
  linux-raspi2: 4.4.0-1016.22 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-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 promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Xenial:
  Fix Released

Bug description:
  This bug is for tracking the 4.4.0-1016.22 upload package. This bug
  will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1595874
  phase: Released
  proposed-announcement-sent: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1595881/+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 1594906] Re: linux: 4.4.0-27.46 -proposed tracker

[Adam Conrad]

** Changed in: linux (Ubuntu)
   Status: Invalid => New

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

Title:
  linux: 4.4.0-27.46 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
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-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  New
Status in linux source package in Xenial:
  New

Bug description:
  This bug is for tracking the 4.4.0-27.46 upload package. This bug will
  contain status and testing results related to that upload.

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

  -- swm properties --
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1594906/+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 1574897] Re: Upgrading to 16.04 disables Python3?

[Adam Conrad]

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

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

Title:
  Upgrading to 16.04 disables Python3?

Status in vim package in Ubuntu:
  Confirmed
Status in vim source package in Xenial:
  New

Bug description:
  Since I ran a do-release-upgrade last week from 15.10 to 16.04,
  starting Vim now produces this warning I haven't seen before:

  ~/D/abc ❯❯❯ vim   
 develop ✭
  You need vim compiled with Python 2.6, 2.7 or 3.2 and later support
  for Powerline to work. Please consult the documentation for more
  details.
  Press ENTER or type command to continue

  Then had a look at the included features of Vim:

  /e/alternatives ❯❯❯ vim --version
  VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Apr 08 2016 11:38:28)
  Included patches: 1-1689
  Modified by pkg-vim-maintain...@lists.alioth.debian.org
  Compiled by pkg-vim-maintain...@lists.alioth.debian.org
  Huge version without GUI.  Features included (+) or not (-):
  +acl +farsi   +mouse_netterm   +tag_binary
  +arabic  +file_in_path+mouse_sgr   +tag_old_static
  +autocmd +find_in_path-mouse_sysmouse  -tag_any_white
  -balloon_eval+float   +mouse_urxvt -tcl
  -browse  +folding +mouse_xterm +terminfo
  ++builtin_terms  -footer  +multi_byte  +termresponse
  +byte_offset +fork()  +multi_lang  +textobjects
  +channel +gettext -mzscheme+timers
  +cindent -hangul_input+netbeans_intg   +title
  -clientserver+iconv   +packages-toolbar
  -clipboard   +insert_expand   +path_extra  +user_commands
  +cmdline_compl   +job -perl+vertsplit
  +cmdline_hist+jumplist+persistent_undo +virtualedit
  +cmdline_info+keymap  +postscript  +visual
  +comments+langmap +printer +visualextra
  +conceal +libcall +profile +viminfo
  +cryptv  +linebreak   -python  +vreplace
  +cscope  +lispindent  -python3 +wildignore
  +cursorbind  +listcmds+quickfix+wildmenu
  +cursorshape +localmap+reltime +windows
  +dialog_con  -lua +rightleft   +writebackup
  +diff+menu-ruby-X11
  +digraphs+mksession   +scrollbind  -xfontset
  -dnd +modify_fname+signs   -xim
  -ebcdic  +mouse   +smartindent -xsmp
  +emacs_tags  -mouseshape  +startuptime -xterm_clipboard
  +eval+mouse_dec   +statusline  -xterm_save
  +ex_extra+mouse_gpm   -sun_workshop-xpm
  +extra_search-mouse_jsbterm   +syntax  
 system vimrc file: "$VIM/vimrc"
   user vimrc file: "$HOME/.vimrc"
   2nd user vimrc file: "~/.vim/vimrc"
user exrc file: "$HOME/.exrc"
fall-back for $VIM: "/usr/share/vim"
  Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H   -Wdate-time  -g -O2 -fPIE 
-fstack-protector-strong -Wformat -Werror=format-security -U_FORTIFY_SOURCE 
-D_FORTIFY_SOURCE=1  
  Linking: gcc   -Wl,-Bsymbolic-functions -fPIE -pie -Wl,-z,relro -Wl,-z,now 
-Wl,--as-needed -o vim-lm -ltinfo -lnsl  -lselinux -lacl -lattr -lgpm 
-ldl

  I see, there is -python and -python3

  But all news and documentation say the Vim in Xenial 16.04 comes with
  Python3 enabled. I am confused? A bug?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1574897/+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 1582431] Re: linux: 4.4.0-23.41 -proposed tracker

[Adam Conrad]

** Changed in: kernel-sru-workflow/promote-to-security
   Status: Confirmed => Fix Released

** Changed in: kernel-sru-workflow/promote-to-updates
   Status: Confirmed => Fix Released

** Changed in: kernel-sru-workflow
   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/1582431

Title:
  linux: 4.4.0-23.41 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-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-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released

Bug description:
  This bug is for tracking the 4.4.0-23.41 upload package. This bug will
  contain status and testing results related to that upload.

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

  -- swm properties --
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1582431/+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 1582679] Re: linux-snapdragon: 4.4.0-1014.16 -proposed tracker

[Adam Conrad]

** Changed in: kernel-sru-workflow/promote-to-security
   Status: Confirmed => Fix Released

** Changed in: kernel-sru-workflow/promote-to-updates
   Status: Confirmed => Fix Released

** Changed in: kernel-sru-workflow
   Status: In Progress => Fix Released

** Changed in: kernel-sru-workflow/upload-to-ppa
   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/1582679

Title:
  linux-snapdragon: 4.4.0-1014.16 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-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 promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-snapdragon package in Ubuntu:
  Fix Released
Status in linux-snapdragon source package in Xenial:
  Fix Released

Bug description:
  This bug is for tracking the 4.4.0-1014.16 upload package. This bug
  will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1582431
  phase: Promoted to proposed
  proposed-announcement-sent: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1582679/+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 1582847] Re: linux-raspi2: 4.4.0-1011.14 -proposed tracker

[Adam Conrad]

** Changed in: kernel-sru-workflow/promote-to-security
   Status: Confirmed => Fix Released

** Changed in: kernel-sru-workflow/promote-to-updates
   Status: Confirmed => Fix Released

** Changed in: kernel-sru-workflow
   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/1582847

Title:
  linux-raspi2: 4.4.0-1011.14 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
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 promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-raspi2 package in Ubuntu:
  Fix Released
Status in linux-raspi2 source package in Xenial:
  Fix Released

Bug description:
  This bug is for tracking the 4.4.0-1011.14 upload package. This bug
  will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1582431
  phase: Promoted to proposed
  proposed-announcement-sent: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1582847/+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 1578022] Re: dmidecode fails to output smibios 3.0 info

[Adam Conrad]

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

** Also affects: dmidecode (Ubuntu Yakkety)
   Importance: Medium
 Assignee: Colin Ian King (colin-king)
   Status: Incomplete

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

Title:
  dmidecode fails to output smibios 3.0 info

Status in dmidecode package in Ubuntu:
  Incomplete
Status in dmidecode source package in Xenial:
  New
Status in dmidecode source package in Yakkety:
  Incomplete

Bug description:
  Ubuntu 16.04, dmidecode 3.0-2 can display smibios 2.8 but not smibios
  3.0. Rhel 7.2 can display smibios 3.0 on the same system without a
  problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dmidecode/+bug/1578022/+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 1579082] Re: minor changes to satisfy MIR request

[Adam Conrad]

Hello Colin, or anyone else affected,

Accepted zfs-linux into xenial-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/zfs-
linux/0.6.5.6-0ubuntu9 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Also affects: zfs-linux (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: zfs-linux (Ubuntu Xenial)
   Status: New => Fix Committed

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

Title:
  minor changes to satisfy MIR request

Status in zfs-linux package in Ubuntu:
  In Progress
Status in zfs-linux source package in Xenial:
  Fix Committed

Bug description:
  [SRU][XENIAL]

  This SRU contains a few minor fixes to satisfy the outstanding issues
  to complete the MIR filed for ZFS linux bug 1532198

  [FIXES]

  The outstanding fixes that need to be applied to the package were:
  https://bugs.launchpad.net/ubuntu/+source/zfs-
  linux/+bug/1532198/comments/4

  "- zfs-zed Replaces zfsutils-linux without a version constraint. Is
  that correct? I assumed a file moved from one package to another, in
  which case there should be a version."

  DONE: zfs-zed, add Replaces: zfsutils-linux (<< 0.6.3)

  "- I like the dep8 tests

  So I'd say add a bug subscriber..."

  DONE: canonical-kernel-team and colin-king

  "... fix the Replaces line, ..."

  DONE: zfs-zed, add Replaces: zfsutils-linux (<< 0.6.3)

  "... address the init script lintian errors ...",

  DONE:  the initscripts will never be used, so we proposed to just add
  lintian ignores for these currently. When Debian accepts their zfs
  package we will rebase from this and will get init scripts from there.

  "... and fix the sudoers file ...",

  DONE: remove root ALL=(ALL) ALL from debian/tree/zfsutils-
  linux/etc/sudoers.d/zfs

  [REGRESSION POTENTAL]
  No actual change to the zfs code per se, more final changes to the packaging, 
regression potential minimal to zero.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1579082/+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 1581186] [NEW] mtr 0.86 doesn't respect terminal colors

[Adam Conrad]

Public bug reported:

[ SRU Justification ]
mtr 0.86 added more colours to the curses output, but this broke how it blends 
in with dark terminals with non-standard colours, and light terminals in 
general.

While this is purely cosmetic, it's pretty ugly compared to mtr 0.85,
and the fix is trivial and trivially verified as correct (or, more
correct than 0.86) on several different terminal colour schemes.  As a
man who uses mtr daily, it's been driving me mildly nuts.

[ Solution ]
Two commits upstream fix this, so it's a little more readable again on light 
terminals, and doesn't mess with non-standard terminals:

63a1f1493bfbaf7e55eb7e20b3791fc8b14cf92d
7571201cf7a3394e0dcd2b037aba1836089cc084

[ Test Case ]
Run old and new mtr on a variety of terminal schemes (default gnome-terminal, 
inverted gnome-terminal, default and inverted xterm, etc) to see if it's (a) as 
readable or more than before, (b) now shows sanely default bg colours, (c) 
works correctly with transparent backgrounds.

The first point is somewhat subjective, though a quick test here shows
that on "xterm -rv", the bold text has switched from some barely-
readable grey-on-white to something approaching black-on-white, so I
think this is moving in a winning direction.

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

** Affects: mtr (Ubuntu Xenial)
 Importance: Undecided
 Status: New

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

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

Title:
  mtr 0.86 doesn't respect terminal colors

Status in mtr package in Ubuntu:
  New
Status in mtr source package in Xenial:
  New

Bug description:
  [ SRU Justification ]
  mtr 0.86 added more colours to the curses output, but this broke how it 
blends in with dark terminals with non-standard colours, and light terminals in 
general.

  While this is purely cosmetic, it's pretty ugly compared to mtr 0.85,
  and the fix is trivial and trivially verified as correct (or, more
  correct than 0.86) on several different terminal colour schemes.  As a
  man who uses mtr daily, it's been driving me mildly nuts.

  [ Solution ]
  Two commits upstream fix this, so it's a little more readable again on light 
terminals, and doesn't mess with non-standard terminals:

  63a1f1493bfbaf7e55eb7e20b3791fc8b14cf92d
  7571201cf7a3394e0dcd2b037aba1836089cc084

  [ Test Case ]
  Run old and new mtr on a variety of terminal schemes (default gnome-terminal, 
inverted gnome-terminal, default and inverted xterm, etc) to see if it's (a) as 
readable or more than before, (b) now shows sanely default bg colours, (c) 
works correctly with transparent backgrounds.

  The first point is somewhat subjective, though a quick test here shows
  that on "xterm -rv", the bold text has switched from some barely-
  readable grey-on-white to something approaching black-on-white, so I
  think this is moving in a winning direction.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mtr/+bug/1581186/+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 1571174] Re: package squid3 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[Adam Conrad]

** Also affects: dpkg (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: dpkg (Ubuntu)
   Status: New => Invalid

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

Title:
  package squid3 failed to install/upgrade: dependency problems -
  leaving triggers unprocessed

Status in dpkg package in Ubuntu:
  Invalid
Status in squid3 package in Ubuntu:
  Invalid
Status in dpkg source package in Xenial:
  New
Status in squid3 source package in Xenial:
  In Progress

Bug description:
  During an upgrade from 15.10 to 16.04, upgrading squid3 erred out...

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: squid3 3.3.8-1ubuntu16.2
  ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4
  Uname: Linux 4.2.0-34-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  Date: Sat Apr 16 05:33:51 2016
  DuplicateSignature: package:squid3:3.3.8-1ubuntu16.2:dependency problems - 
leaving triggers unprocessed
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2015-12-07 (131 days ago)
  InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: squid3
  Title: package squid3 3.3.8-1ubuntu16.2 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to xenial on 2016-04-16 (0 days ago)
  modified.conffile..etc.apparmor.d.usr.sbin.squid3: [deleted]
  modified.conffile..etc.init.d.squid3: [deleted]
  modified.conffile..etc.init.squid3.conf: [deleted]
  modified.conffile..etc.logrotate.d.squid3: [deleted]
  modified.conffile..etc.resolvconf.update.libc.d.squid3: [deleted]
  modified.conffile..etc.squid3.errorpage.css: [deleted]
  modified.conffile..etc.squid3.msntauth.conf: [deleted]
  modified.conffile..etc.squid3.squid.conf: [deleted]
  modified.conffile..etc.ufw.applications.d.squid3: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1571174/+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 1579036] Re: add dep8 tests for the scripts/check.sh SPL/SPLAT tests

[Adam Conrad]

Hello Colin, or anyone else affected,

Accepted spl-linux into xenial-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/spl-
linux/0.6.5.6-0ubuntu3 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Also affects: spl-linux (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: spl-linux (Ubuntu Xenial)
   Status: New => Fix Committed

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

Title:
  add dep8 tests for the scripts/check.sh SPL/SPLAT tests

Status in spl-linux package in Ubuntu:
  In Progress
Status in spl-linux source package in Xenial:
  Fix Committed

Bug description:
  [SRU Justification][XENIAL]

  Add dep8 SPL/SPLAT regression tests from the spl source to sanity
  check that the SPL driver module is behaving sanely.

  This SRU is to fix issues found in the MIR review,
  https://bugs.launchpad.net/ubuntu/+source/spl-
  linux/+bug/1569294/comments/2

  [FIX]
  Modified version of the scripts/check.sh added to the dep8 test directory

  [TESTCASE]
  adt-run spl-linux_0.6.5.6-0ubuntu3.dsc --- qemu --ram-size 4096 
adt-xenial-amd64-cloud.img

  ..with the tests we now get the spl splat checks running by adt:

  Loading splat
  -- Running SPLAT Tests 
--
  kmem:kmem_alloc   Pass
  kmem:kmem_zalloc  Pass
  kmem:vmem_alloc   Pass
  kmem:vmem_zalloc  Pass
  kmem:slab_small   Pass
  kmem:slab_large   Pass
  kmem:slab_align   Pass
  kmem:slab_reapPass
  kmem:slab_age Pass
  kmem:slab_lockPass
     taskq:single   Pass
     taskq:multiple Pass
     taskq:system   Pass
     taskq:wait Pass
     taskq:frontPass
     taskq:recurse  Pass
     taskq:contention   Pass
     taskq:delayPass
     taskq:cancel   Pass
     taskq:dynamic  Pass
  krng:freq Pass
     mutex:tryenter Pass
     mutex:race Pass
     mutex:ownedPass
     mutex:ownerPass
   condvar:signal1  Pass
   condvar:broadcast1   Pass
   condvar:signal2  Pass
   condvar:broadcast2   Pass
   condvar:timeout  Pass
    thread:create   Pass
    thread:exit Pass
    thread:tsd  Pass
    rwlock:N-rd/1-wrPass
    rwlock:0-rd/N-wrPass
    rwlock:held Pass
    rwlock:tryenter Pass
    rwlock:rw_downgrade Pass
    rwlock:rw_tryupgradePass
  time:time1Pass
  time:time2Pass
     vnode:vn_open  Pass
     vnode:vn_openatPass
     vnode:vn_rdwr  Pass
     vnode:vn_getattr   Pass
     vnode:vn_sync  Pass
  kobj:open Pass
  kobj:size/readPass
    atomic:64-bit   Pass
  list:create/destroy   Pass
  list:ins/rm head  Pass
  list:ins/rm tail  Pass
  list:insert_after Pass
  list:insert_beforePass
  list:remove   Pass
  list:active   Pass
   

[Group.of.nepali.translators] [Bug 1580952] Re: [SRU] Update apt/xenial to 1.2.12

[Adam Conrad]

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

** Changed in: apt (Ubuntu)
   Status: New => Invalid

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

Title:
  [SRU] Update apt/xenial to 1.2.12

Status in apt package in Ubuntu:
  Invalid
Status in apt source package in Xenial:
  New

Bug description:
  Since the version in xenial, we released two more new bug fix releases
  upstream. We'd like to get this into xenial under the "New upstream
  microreleases" rule.

  [Impact]
  Most visible for xenial users:
  -> AppStream now updates even if some repositories failed to be fetched (see 
#1562733 for reference)

  -> Third-party repositories will no longer print "Unknown public key"
  type errors when a new key was added (and another key was successfully
  used to verify the repo). This happen(s/ed) on the Chrome
  repositories, for example, and leads users to manually receive keys
  from the key server which weakens their security.

  The rest are other bugfixes. Full changelogs:

  apt (1.2.11) unstable; urgency=medium

    [ David Kalnischkies ]
    * ensure transaction states are changed only once
  -> more sanity checks
    * stop handling items in doomed transactions.
  Thanks to Barr Detwix & Vincent Lefevre for log files (Closes: 817240)
  -> fixes a lot of "E: Unpatched file  doesn't exist (anymore)!" that happen 
sometimes
    * do not require non-broken systems in 'upgrade'
  -> allows people to fix their broken system in upgrade
    * detect compressed status files on extension again
  -> regression from 1.1, single flag changed
    * recheck Pre-Depends satisfaction in SmartConfigure (LP: #1569099)
  -> already in xenial
    * fix Alt-Filename handling of file method
  -> off-by-one error when removing file extensions to get uncompressed filename
    * allow uncompressed files to be empty in store again
  -> this caused failures when fetching empty files
    * silently skip acquire of empty index files
  -> clean up of the above
    * ensure outdated files are dropped without lists-cleanup
  -> ensures proper cleanup

    [ Kelemen Gábor ]
    * Hungarian program translation update (Closes: 820638)

   -- Julian Andres Klode   Mon, 25 Apr 2016 15:23:49
  +0200

  apt (1.2.12) unstable; urgency=medium

    [ Patrick Cable ]
    * refactored no_proxy code to work regardless of where https proxy is set
  -> no_proxy should really work for all ways to set an https proxy (actually 
LP: #1575877)

    [ James McCoy ]
    * deb822: Restore support for -{Add,Remove}
  -> Adds - in front of Add and Remove strings...

    [ David Kalnischkies ]
    * don't show NO_PUBKEY warning if repo is signed by another key
  (Closes: 618445)
  -> this helps the DSA->RSA key transitions, at it gets rid of the unkown 
public key warnings on the Chrome repository
    * allow redirection for items without a space in the desc again
  -> small bug fix
    * don't sent uninstallable rc-only versions via EDSP
  -> Fixes EDSP/CUDF solvers to not try to install package versions in 
config-file state
    * respect user pinning in M-A:same version (un)screwing
  -> used the wrong function get a candidate version

    [ Julian Andres Klode ]
    * update: Run Post-Invoke-Success if not all sources failed
  -> This fixes the problem with AppStream not being updated because a mirror 
failed (see #1562733)
    * debian/gbp.conf: Set debian-branch to 1.2.y
  -> Build infrastructure

    [ Frans Spiesschaert ]
    * Dutch program translation update (Closes: 823976)

   -- Julian Andres Klode   Wed, 11 May 2016 10:56:53
  +0200

  [Regression Potential]
  APT has a very thorough regression test suite and the releases have passed 
our upstream CI system on travis, and autopkgtests on Debian unstable and 
Ubuntu xenial; so there's no huge regression potential.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1580952/+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 1578759] Re: linux-snapdragon: 4.4.0-1013.14 -proposed tracker

[Adam Conrad]

** Changed in: kernel-sru-workflow/automated-testing
   Status: Confirmed => Invalid

** Changed in: kernel-sru-workflow/certification-testing
   Status: Confirmed => Invalid

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

** Changed in: kernel-sru-workflow/security-signoff
   Status: Confirmed => Fix Released

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

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

Title:
  linux-snapdragon: 4.4.0-1013.14 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
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:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Invalid
Status in linux-snapdragon package in Ubuntu:
  New
Status in linux-snapdragon source package in Xenial:
  Fix Released

Bug description:
  This bug is for tracking the 4.4.0-1013.14 upload package. This bug
  will contain status and testing results related to that upload.

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

  -- swm properties --
  phase: Promoted to proposed
  proposed-announcement-sent: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1578759/+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 1578721] Re: linux: 4.4.0-22.39 -proposed tracker

[Adam Conrad]

** Changed in: kernel-sru-workflow/promote-to-security
   Status: New => Fix Released

** Changed in: kernel-sru-workflow/promote-to-security
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Adam Conrad 
(adconrad)

** Changed in: kernel-sru-workflow/promote-to-updates
   Status: New => Fix Released

** Changed in: kernel-sru-workflow/promote-to-updates
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Adam Conrad 
(adconrad)

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

Title:
  linux: 4.4.0-22.39 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
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:
  Invalid
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Invalid
Status in linux package in Ubuntu:
  New
Status in linux source package in Xenial:
  Fix Released

Bug description:
  This bug is for tracking the 4.4.0-22.39 upload package. This bug will
  contain status and testing results related to that upload.

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

  -- swm properties --
  phase: Promoted to proposed
  proposed-announcement-sent: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1578721/+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 1578741] Re: linux-raspi2: 4.4.0-1010.12 -proposed tracker

[Adam Conrad]

** Changed in: kernel-sru-workflow/promote-to-security
   Status: New => Fix Released

** Changed in: kernel-sru-workflow/promote-to-security
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Adam Conrad 
(adconrad)

** Changed in: kernel-sru-workflow/promote-to-updates
   Status: New => Fix Released

** Changed in: kernel-sru-workflow/promote-to-updates
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Adam Conrad 
(adconrad)

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

Title:
  linux-raspi2: 4.4.0-1010.12 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
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:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Invalid
Status in linux-raspi2 package in Ubuntu:
  New
Status in linux-raspi2 source package in Xenial:
  Fix Released

Bug description:
  This bug is for tracking the 4.4.0-1010.12 upload package. This bug
  will contain status and testing results related to that upload.

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

  -- swm properties --
  phase: Promoted to proposed
  proposed-announcement-sent: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1578741/+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 1578721] Re: linux: 4.4.0-22.39 -proposed tracker

[Adam Conrad]

** Changed in: kernel-sru-workflow/automated-testing
   Status: Confirmed => Invalid

** Changed in: kernel-sru-workflow/certification-testing
   Status: Confirmed => Invalid

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

** Changed in: kernel-sru-workflow/security-signoff
   Status: Confirmed => Fix Released

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

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

Title:
  linux: 4.4.0-22.39 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
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:
  Invalid
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Invalid
Status in linux package in Ubuntu:
  New
Status in linux source package in Xenial:
  Fix Released

Bug description:
  This bug is for tracking the 4.4.0-22.39 upload package. This bug will
  contain status and testing results related to that upload.

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

  -- swm properties --
  phase: Promoted to proposed
  proposed-announcement-sent: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1578721/+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 1572416] Re: do-release-upgrade crashes in Greek locale

[Adam Conrad]

** Changed in: ubuntu-release-upgrader (Ubuntu Xenial)
   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/1572416

Title:
  do-release-upgrade crashes in Greek locale

Status in ubuntu-release-upgrader package in Ubuntu:
  In Progress
Status in ubuntu-release-upgrader source package in Xenial:
  Fix Released
Status in ubuntu-release-upgrader source package in Yakkety:
  Fix Committed

Bug description:
  [SRU Justification]
  Wrong translations and wrong behavior of upgrader

  [Regression potential]
  Code changes are specific to an input function used at one specific point in 
the upgrader and should be very testable.

  [Test case]
  1. On Ubuntu 14.04, get a root shell in a terminal.
  2. Run 'apt install language-pack-el'
  3. Run 'LANG=el_GR.UTF-8 do-release-upgrade -d'
  4. Confirm that the upgrader is shown in Greek.
  5. When prompted whether or not to upgrade, confirm that the Continue prompt 
shows 'Συνἑχεια [yN]' instead of the expected 'Συνἑχεια [νΟ]'.
  6. Type 'y' and see that the input is ignored and the prompt 
redisplayed.
  7. Hit '' and see that the input is ignored and the prompt redisplayed.
  8. Type (or cut and paste) 'ν' and confirm that the 
upgrader crashes.
  9. Reset the environment by running sudo mv /etc/apt/sources.list.distUpgrade 
/etc/apt/sources.list
  10. Run 'LANG=el_GR.UTF-8 do-release-upgrade -p'
  11. Confirm that the upgrader is shown in Greek.
  12. When prompted whether or not to upgrade, confirm that the Continue prompt 
shows 'Συνἑχεια [νΟ]'.
  13. Type (or cut and paste) 'ν' and confirm that the 
upgrade cancels cleanly.
  14. Run 'LANG=el_GR.UTF-8 do-release-upgrade -p' again.
  15. Confirm that the upgrader is shown in Greek.
  16. Type (or cut and paste) 'ν' and confirm that the upgrade proceeds.

  I tried `do-release-upgrade -d` on an up to date 14.04 system, with
  Greek locale=el_GR.UTF-8.

  I got notified that some packages are no longer supported by Canonical, and 
then I got this prompt:
  Continue [yN] λεπτομέρειες [λ]

  λεπτομέρειες means details.

  I tried pressing [λ] and I got the (hopefully attached) crash. If it's
  not attached, I also uploaded it to http://paste.ubuntu.com/15941779/.

  Then it restarted the upgrade process and it got to the same prompt. At that 
point, [λ] worked and showed me the no-longer supported packages,
  but y/n didn't work at all, so I couldn't continue.

  I pressed Ctrl+C to abort the upgrade process,
  but now `do-release-upgrade -d` tells me there's no new distribution 
available to upgrade to, possibly because it's checking my just-broken 
sources.list...

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: ubuntu-release-upgrader-core 1:0.220.8
  ProcVersionSignature: Ubuntu 3.13.0-85.129-generic 3.13.11-ckt36
  Uname: Linux 3.13.0-85-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CrashDB: ubuntu
  Date: Wed Apr 20 08:52:43 2016
  InstallationDate: Installed on 2015-01-29 (446 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64+mac 
(20140722.2)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=el
   TERM=xterm
   PATH=(custom, no user)
   LANG=el_GR.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to trusty on 2016-04-20 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1572416/+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 1572284] Re: linux-snapdragon: 4.4.0-1012.12 -proposed tracker

[Adam Conrad]

** Changed in: kernel-development-workflow
   Status: In Progress => Fix Released

** Changed in: kernel-development-workflow/automated-testing
   Status: Confirmed => Fix Released

** Changed in: kernel-development-workflow/promote-to-release
   Status: New => Fix Released

** Changed in: kernel-development-workflow/regression-testing
   Status: Confirmed => 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/1572284

Title:
  linux-snapdragon: 4.4.0-1012.12 -proposed tracker

Status in Kernel Development Workflow:
  Fix Released
Status in Kernel Development Workflow automated-testing series:
  Fix Released
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  Fix Released
Status in Kernel Development Workflow regression-testing series:
  Fix Released
Status in linux-snapdragon package in Ubuntu:
  Fix Released
Status in linux-snapdragon source package in Xenial:
  Fix Released

Bug description:
  This bug is for tracking the 4.4.0-1012.12 upload package. This bug
  will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-Prepare-package-start:Tuesday, 19. April 2016 19:06 UTC
  -- swm properties --
  phase: Promoted to proposed
  proposed-announcement-sent: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1572284/+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 1573817] Re: linux: 4.4.0-22.38 -proposed tracker

[Adam Conrad]

** Changed in: linux (Ubuntu)
   Status: New => Invalid

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

Title:
  linux: 4.4.0-22.38 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Confirmed
Status in Kernel Development Workflow prepare-package-meta series:
  Confirmed
Status in Kernel Development Workflow prepare-package-signed series:
  Confirmed
Status in Kernel Development Workflow promote-to-proposed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

Bug description:
  This bug is for tracking the 4.4.0-22.38 upload package. This bug will
  contain status and testing results related to that upload.

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

  kernel-phase:Packaging
  kernel-phase-changed:Friday, 22. April 2016 22:01 UTC

  -- swm properties --
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1573817/+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 1561750] Re: linux-raspi2: 4.4.0-1006.7 -proposed tracker

[Adam Conrad]

*** This bug is a duplicate of bug 1572273 ***
https://bugs.launchpad.net/bugs/1572273

** This bug is no longer a duplicate of bug 1564430
   linux-raspi2: 4.4.0-1007.8 -proposed tracker
** This bug has been marked a duplicate of bug 1572273
   linux-raspi2: 4.4.0-1009.10 -proposed tracker

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

Title:
  linux-raspi2: 4.4.0-1006.7 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Incomplete
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux-raspi2 package in Ubuntu:
  New
Status in linux-raspi2 source package in Xenial:
  New

Bug description:
  This bug is for tracking the 4.4.0-1006.7 upload package. This bug
  will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-Prepare-package-start:Thursday, 24. March 2016 22:18 UTC
  kernel-phase-changed:Thursday, 24. March 2016 22:18 UTC
  kernel-phase:Prepare

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1561750/+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 1559264] Re: linux-raspi2: 4.4.0-1005.6 -proposed tracker

[Adam Conrad]

*** This bug is a duplicate of bug 1572273 ***
https://bugs.launchpad.net/bugs/1572273

** This bug is no longer a duplicate of bug 1564430
   linux-raspi2: 4.4.0-1007.8 -proposed tracker
** This bug has been marked a duplicate of bug 1572273
   linux-raspi2: 4.4.0-1009.10 -proposed tracker

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

Title:
  linux-raspi2: 4.4.0-1005.6 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Fix Released
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux-raspi2 package in Ubuntu:
  New
Status in linux-raspi2 source package in Xenial:
  New

Bug description:
  This bug is for tracking the 4.4.0-1005.6 upload package. This bug
  will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-Prepare-package-start:Friday, 18. March 2016 19:07 UTC
  kernel-phase-changed:Friday, 18. March 2016 19:07 UTC
  kernel-phase:Prepare
  kernel-stable-Promote-to-proposed-end:Monday, 21. March 2016 09:13 UTC
  proposed-announcement-sent:True

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1559264/+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 1570348] Re: linux: 4.4.0-19.35 -proposed tracker

[Adam Conrad]

*** This bug is a duplicate of bug 1571791 ***
https://bugs.launchpad.net/bugs/1571791

** This bug is no longer a duplicate of bug 1571069
   linux: 4.4.0-20.36 -proposed tracker
** This bug has been marked a duplicate of bug 1571791
   linux: 4.4.0-21.37 -proposed tracker

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

Title:
  linux: 4.4.0-19.35 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  New
Status in linux source package in Xenial:
  New

Bug description:
  This bug is for tracking the 4.4.0-19.35 upload package. This bug will
  contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-Prepare-package-start:Thursday, 14. April 2016 12:11 UTC
  -- swm properties --
  phase: Promoted to proposed
  proposed-announcement-sent: true

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