[Group.of.nepali.translators] [Bug 1691520] Re: Wordpress May 2017 security updates

[Launchpad Bug Tracker]

[Expired for wordpress (Ubuntu Xenial) because there has been no
activity for 60 days.]

** Changed in: wordpress (Ubuntu Xenial)
   Status: Incomplete => Expired

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

Title:
  Wordpress May 2017 security updates

Status in wordpress package in Ubuntu:
  Expired
Status in wordpress source package in Xenial:
  Expired
Status in wordpress source package in Yakkety:
  Expired
Status in wordpress source package in Zesty:
  Expired

Bug description:
  Sponsorship
  ---
  git-buildpackage from the ubuntu/* branches at
  https://git.launchpad.net/~jbicha/ubuntu/+source/wordpress/

  Impact
  --
  Update 17.04 from 4.7.3 to 4.7.5
  Update 16.10 from 4.6.1 to 4.6.6
  Update 16.04 LTS from 4.4.2 to 4.4.10

  to fix numerous critical security bugs.

  wordpress 4.7.5-1 was auto-synced from Debian to Ubuntu 17.10 Alpha
  "artful"

  Changes for Ubuntu 17.04
  
  https://wordpress.org/news/2017/04/wordpress-4-7-4/
  https://wordpress.org/news/2017/05/wordpress-4-7-5/

  https://codex.wordpress.org/Version_4.7.4
  https://codex.wordpress.org/Version_4.7.5

  You can change the codex URL to a different version number if you
  really want to see all the individual security fixes.

  The changelog entries were produced by tweaking the changelog from
  https://tracker.debian.org/media/packages/w/wordpress/changelog-4.7.5%2Bdfsg-1

  For Xenial, I also used
  
https://tracker.debian.org/media/packages/w/wordpress/changelog-4.1%2Bdfsg-1%2Bdeb8u13

  and filled in the descriptions for these 2 that didn't apply to the Debian 
security update but apply to Xenial
  https://security-tracker.debian.org/tracker/CVE-2016-6896
  https://security-tracker.debian.org/tracker/CVE-2016-6897

  Testing Done
  
  I have successfully test-built each package.

  Regression Potential
  
  WordPress maintains separate branches to backport security fixes. I suspect 
that the older the branch gets, the more likely it is that something will break.

  WordPress still uses trac/svn, but there's this handy read-only copy
  that is easier to examine:

  https://github.com/WordPress/WordPress/commits/4.4-branch

  WordPress only officially recommends the latest stable series (currently 4.7)
  https://wordpress.org/download/release-archive/

  Other Info
  --
  On one hand, I hope right now no one actually uses the Ubuntu package on a 
live web server. I mean, if they are using the development version of Ubuntu, 
it might actually work but otherwise, it's not really received any security 
support at all.

  Similarly, I guess there's a concern that if we start providing
  security updates, then people will start thinking that Ubuntu's
  'wordpress' package is safe to use, which is fine as long as someone
  from the community will indeed package these updates from now on.
  Otherwise, maybe doing these security updates is not really helping
  anyone?

  WordPress also maintains a 3.8 branch (with a 3.8.21 release this week
  corresponding with 4.7.5) that we could use for Ubuntu 14.04 LTS. I
  could prepare that one too, but I don't think it's worth spending much
  time testing that version.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wordpress/+bug/1691520/+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 1691520] Re: Wordpress May 2017 security updates

[Launchpad Bug Tracker]

[Expired for wordpress (Ubuntu Yakkety) because there has been no
activity for 60 days.]

** Changed in: wordpress (Ubuntu Yakkety)
   Status: Incomplete => Expired

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

Title:
  Wordpress May 2017 security updates

Status in wordpress package in Ubuntu:
  Expired
Status in wordpress source package in Xenial:
  Expired
Status in wordpress source package in Yakkety:
  Expired
Status in wordpress source package in Zesty:
  Expired

Bug description:
  Sponsorship
  ---
  git-buildpackage from the ubuntu/* branches at
  https://git.launchpad.net/~jbicha/ubuntu/+source/wordpress/

  Impact
  --
  Update 17.04 from 4.7.3 to 4.7.5
  Update 16.10 from 4.6.1 to 4.6.6
  Update 16.04 LTS from 4.4.2 to 4.4.10

  to fix numerous critical security bugs.

  wordpress 4.7.5-1 was auto-synced from Debian to Ubuntu 17.10 Alpha
  "artful"

  Changes for Ubuntu 17.04
  
  https://wordpress.org/news/2017/04/wordpress-4-7-4/
  https://wordpress.org/news/2017/05/wordpress-4-7-5/

  https://codex.wordpress.org/Version_4.7.4
  https://codex.wordpress.org/Version_4.7.5

  You can change the codex URL to a different version number if you
  really want to see all the individual security fixes.

  The changelog entries were produced by tweaking the changelog from
  https://tracker.debian.org/media/packages/w/wordpress/changelog-4.7.5%2Bdfsg-1

  For Xenial, I also used
  
https://tracker.debian.org/media/packages/w/wordpress/changelog-4.1%2Bdfsg-1%2Bdeb8u13

  and filled in the descriptions for these 2 that didn't apply to the Debian 
security update but apply to Xenial
  https://security-tracker.debian.org/tracker/CVE-2016-6896
  https://security-tracker.debian.org/tracker/CVE-2016-6897

  Testing Done
  
  I have successfully test-built each package.

  Regression Potential
  
  WordPress maintains separate branches to backport security fixes. I suspect 
that the older the branch gets, the more likely it is that something will break.

  WordPress still uses trac/svn, but there's this handy read-only copy
  that is easier to examine:

  https://github.com/WordPress/WordPress/commits/4.4-branch

  WordPress only officially recommends the latest stable series (currently 4.7)
  https://wordpress.org/download/release-archive/

  Other Info
  --
  On one hand, I hope right now no one actually uses the Ubuntu package on a 
live web server. I mean, if they are using the development version of Ubuntu, 
it might actually work but otherwise, it's not really received any security 
support at all.

  Similarly, I guess there's a concern that if we start providing
  security updates, then people will start thinking that Ubuntu's
  'wordpress' package is safe to use, which is fine as long as someone
  from the community will indeed package these updates from now on.
  Otherwise, maybe doing these security updates is not really helping
  anyone?

  WordPress also maintains a 3.8 branch (with a 3.8.21 release this week
  corresponding with 4.7.5) that we could use for Ubuntu 14.04 LTS. I
  could prepare that one too, but I don't think it's worth spending much
  time testing that version.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wordpress/+bug/1691520/+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 1691520] Re: Wordpress May 2017 security updates

[Launchpad Bug Tracker]

[Expired for wordpress (Ubuntu Zesty) because there has been no activity
for 60 days.]

** Changed in: wordpress (Ubuntu Zesty)
   Status: Incomplete => Expired

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

Title:
  Wordpress May 2017 security updates

Status in wordpress package in Ubuntu:
  Expired
Status in wordpress source package in Xenial:
  Expired
Status in wordpress source package in Yakkety:
  Expired
Status in wordpress source package in Zesty:
  Expired

Bug description:
  Sponsorship
  ---
  git-buildpackage from the ubuntu/* branches at
  https://git.launchpad.net/~jbicha/ubuntu/+source/wordpress/

  Impact
  --
  Update 17.04 from 4.7.3 to 4.7.5
  Update 16.10 from 4.6.1 to 4.6.6
  Update 16.04 LTS from 4.4.2 to 4.4.10

  to fix numerous critical security bugs.

  wordpress 4.7.5-1 was auto-synced from Debian to Ubuntu 17.10 Alpha
  "artful"

  Changes for Ubuntu 17.04
  
  https://wordpress.org/news/2017/04/wordpress-4-7-4/
  https://wordpress.org/news/2017/05/wordpress-4-7-5/

  https://codex.wordpress.org/Version_4.7.4
  https://codex.wordpress.org/Version_4.7.5

  You can change the codex URL to a different version number if you
  really want to see all the individual security fixes.

  The changelog entries were produced by tweaking the changelog from
  https://tracker.debian.org/media/packages/w/wordpress/changelog-4.7.5%2Bdfsg-1

  For Xenial, I also used
  
https://tracker.debian.org/media/packages/w/wordpress/changelog-4.1%2Bdfsg-1%2Bdeb8u13

  and filled in the descriptions for these 2 that didn't apply to the Debian 
security update but apply to Xenial
  https://security-tracker.debian.org/tracker/CVE-2016-6896
  https://security-tracker.debian.org/tracker/CVE-2016-6897

  Testing Done
  
  I have successfully test-built each package.

  Regression Potential
  
  WordPress maintains separate branches to backport security fixes. I suspect 
that the older the branch gets, the more likely it is that something will break.

  WordPress still uses trac/svn, but there's this handy read-only copy
  that is easier to examine:

  https://github.com/WordPress/WordPress/commits/4.4-branch

  WordPress only officially recommends the latest stable series (currently 4.7)
  https://wordpress.org/download/release-archive/

  Other Info
  --
  On one hand, I hope right now no one actually uses the Ubuntu package on a 
live web server. I mean, if they are using the development version of Ubuntu, 
it might actually work but otherwise, it's not really received any security 
support at all.

  Similarly, I guess there's a concern that if we start providing
  security updates, then people will start thinking that Ubuntu's
  'wordpress' package is safe to use, which is fine as long as someone
  from the community will indeed package these updates from now on.
  Otherwise, maybe doing these security updates is not really helping
  anyone?

  WordPress also maintains a 3.8 branch (with a 3.8.21 release this week
  corresponding with 4.7.5) that we could use for Ubuntu 14.04 LTS. I
  could prepare that one too, but I don't think it's worth spending much
  time testing that version.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wordpress/+bug/1691520/+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 1691520] Re: Wordpress May 2017 security updates

[Launchpad Bug Tracker]

[Expired for wordpress (Ubuntu) because there has been no activity for
60 days.]

** Changed in: wordpress (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Wordpress May 2017 security updates

Status in wordpress package in Ubuntu:
  Expired
Status in wordpress source package in Xenial:
  Expired
Status in wordpress source package in Yakkety:
  Expired
Status in wordpress source package in Zesty:
  Expired

Bug description:
  Sponsorship
  ---
  git-buildpackage from the ubuntu/* branches at
  https://git.launchpad.net/~jbicha/ubuntu/+source/wordpress/

  Impact
  --
  Update 17.04 from 4.7.3 to 4.7.5
  Update 16.10 from 4.6.1 to 4.6.6
  Update 16.04 LTS from 4.4.2 to 4.4.10

  to fix numerous critical security bugs.

  wordpress 4.7.5-1 was auto-synced from Debian to Ubuntu 17.10 Alpha
  "artful"

  Changes for Ubuntu 17.04
  
  https://wordpress.org/news/2017/04/wordpress-4-7-4/
  https://wordpress.org/news/2017/05/wordpress-4-7-5/

  https://codex.wordpress.org/Version_4.7.4
  https://codex.wordpress.org/Version_4.7.5

  You can change the codex URL to a different version number if you
  really want to see all the individual security fixes.

  The changelog entries were produced by tweaking the changelog from
  https://tracker.debian.org/media/packages/w/wordpress/changelog-4.7.5%2Bdfsg-1

  For Xenial, I also used
  
https://tracker.debian.org/media/packages/w/wordpress/changelog-4.1%2Bdfsg-1%2Bdeb8u13

  and filled in the descriptions for these 2 that didn't apply to the Debian 
security update but apply to Xenial
  https://security-tracker.debian.org/tracker/CVE-2016-6896
  https://security-tracker.debian.org/tracker/CVE-2016-6897

  Testing Done
  
  I have successfully test-built each package.

  Regression Potential
  
  WordPress maintains separate branches to backport security fixes. I suspect 
that the older the branch gets, the more likely it is that something will break.

  WordPress still uses trac/svn, but there's this handy read-only copy
  that is easier to examine:

  https://github.com/WordPress/WordPress/commits/4.4-branch

  WordPress only officially recommends the latest stable series (currently 4.7)
  https://wordpress.org/download/release-archive/

  Other Info
  --
  On one hand, I hope right now no one actually uses the Ubuntu package on a 
live web server. I mean, if they are using the development version of Ubuntu, 
it might actually work but otherwise, it's not really received any security 
support at all.

  Similarly, I guess there's a concern that if we start providing
  security updates, then people will start thinking that Ubuntu's
  'wordpress' package is safe to use, which is fine as long as someone
  from the community will indeed package these updates from now on.
  Otherwise, maybe doing these security updates is not really helping
  anyone?

  WordPress also maintains a 3.8 branch (with a 3.8.21 release this week
  corresponding with 4.7.5) that we could use for Ubuntu 14.04 LTS. I
  could prepare that one too, but I don't think it's worth spending much
  time testing that version.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wordpress/+bug/1691520/+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 1708315] Re: package virtualbox-guest-utils-hwe 5.0.40-dfsg-0ubuntu1.16.04.1~16.04.3 failed to install/upgrade: subprocess installed post-installation script returne

[LocutusOfBorg]

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

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

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

** Description changed:

-   
- System doesn't allow dkms, or virtual machines built upon dfsg.  I'm not 
interested in mesa or systems  built on X. 
- Linux seems to be about hatred and negativity more than it is about letting 
go of bad things from the past, but seems to revel in the negative and futile, 
more than anything positive and hopeful. 
+ [ Regression Potential ]
+ * None, it has been a mistake in my hwe package creation. It should be an 
easy and simple fix (systemd parses the old init.d string, and when same name 
is detected, it obviously refuses to start
+ 
+ [ test case ]
+ install virtualbox-guest-utils and then install virtualbox-guest-utils-hwe
+ 
+ [ Other info ]
+ 
+ System doesn't allow dkms, or virtual machines built upon dfsg.  I'm not 
interested in mesa or systems  built on X.
+ Linux seems to be about hatred and negativity more than it is about letting 
go of bad things from the past, but seems to revel in the negative and futile, 
more than anything positive and hopeful.
  
  There is a time, I suppose, that rubbing someones face in the past
  nightmare's, has value in a limited way, but at some point, keeping a
  good man down, lacks understanding, as is a maniacle, futile act,that
  helps no one involved, despite there personal prejudice. The reality, is
  just a tragic waste of human worth, and value, accomplishing nothing
  good. In linux,new is effectivlly put away from observvatin, obviously
  ignored and hidden.
  
  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: virtualbox-guest-utils-hwe 5.0.40-dfsg-0ubuntu1.16.04.1~16.04.3
  ProcVersionSignature: Ubuntu 4.4.0-88.111-generic 4.4.76
  Uname: Linux 4.4.0-88-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Wed Aug  2 17:59:01 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-01-10 (204 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
-  dpkg 1.18.4ubuntu1.2
-  apt  1.2.24
+  dpkg 1.18.4ubuntu1.2
+  apt  1.2.24
  SourcePackage: virtualbox-hwe
  Title: package virtualbox-guest-utils-hwe 
5.0.40-dfsg-0ubuntu1.16.04.1~16.04.3 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

** Summary changed:

- package virtualbox-guest-utils-hwe 5.0.40-dfsg-0ubuntu1.16.04.1~16.04.3 
failed to install/upgrade: subprocess installed post-installation script 
returned error exit status 1
+ [SRU]package virtualbox-guest-utils-hwe 5.0.40-dfsg-0ubuntu1.16.04.1~16.04.3 
failed to install/upgrade: subprocess installed post-installation script 
returned error exit status 1

** Changed in: virtualbox-hwe (Ubuntu Xenial)
   Status: New => Fix Committed

** Changed in: virtualbox (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/1708315

Title:
  [SRU]package virtualbox-guest-utils-hwe 5.0.40-dfsg-
  0ubuntu1.16.04.1~16.04.3 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in virtualbox package in Ubuntu:
  Invalid
Status in virtualbox-hwe package in Ubuntu:
  Confirmed
Status in virtualbox source package in Xenial:
  Invalid
Status in virtualbox-hwe source package in Xenial:
  Fix Committed

Bug description:
  [ Regression Potential ]
  * None, it has been a mistake in my hwe package creation. It should be an 
easy and simple fix (systemd parses the old init.d string, and when same name 
is detected, it obviously refuses to start

  [ test case ]
  install virtualbox-guest-utils and then install virtualbox-guest-utils-hwe

  [ Other info ]

  System doesn't allow dkms, or virtual machines built upon dfsg.  I'm not 
interested in mesa or systems  built on X.
  Linux seems to be about hatred and negativity more than it is about letting 
go of bad things from the past, but seems to revel in the negative and futile, 
more than anything positive and hopeful.

  There is a time, I suppose, that rubbing someones face in the past
  nightmare's, has value in a limited way, but at some point, keeping a
  good man down, lacks understanding, as is a maniacle, futile act,that
  helps no one involved, despite there personal prejudice. The reality,
  is just a tragic waste of human worth, and value, accomplishing
  nothing good. In linux,new is effectivlly put away from observvatin,
  obviously ignored and hidden.

  ProblemType: 

[Group.of.nepali.translators] [Bug 1729568] Re: virtualbox-dkms 5.0.40-dfsg-0ubuntu1.16.04.1: virtualbox kernel module failed to build - error: implicit declaration of function ‘set_pages_x’

[LocutusOfBorg]

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

** Summary changed:

- virtualbox-dkms 5.0.40-dfsg-0ubuntu1.16.04.1: virtualbox kernel module failed 
to build - error: implicit declaration of function ‘set_pages_x’
+ [ SRU ]virtualbox-dkms 5.0.40-dfsg-0ubuntu1.16.04.1: virtualbox kernel module 
failed to build - error: implicit declaration of function ‘set_pages_x’

** Description changed:

+ [ Test case ]
+ * Install virtualbox-guest-dkms or virtualbox-dkms on a new hwe linux kernel
+ 
+ [ Regression potential ]
+ * Minimal, this is taken from later kernel modules (usual ifdefs in the 
kernel module)
+ 
+ [ Other info ]
+ * the kernel module needs the usual updates.
  This happened after kernel update to 4.13.0-16-generic
  
  ProblemType: Package
  DKMSBuildLog:
-  DKMS make.log for virtualbox-5.0.40 for kernel 4.13.0-16-generic (x86_64)
-  czw, 2 lis 2017, 11:44:13 CET
-  make: Wejście do katalogu '/usr/src/linux-headers-4.13.0-16-generic'
-AR  /var/lib/dkms/virtualbox/5.0.40/build/built-in.o
-AR  /var/lib/dkms/virtualbox/5.0.40/build/vboxdrv/built-in.o
-CC [M]  /var/lib/dkms/virtualbox/5.0.40/build/vboxdrv/linux/SUPDrv-linux.o
-CC [M]  /var/lib/dkms/virtualbox/5.0.40/build/vboxdrv/SUPDrv.o
-CC [M]  /var/lib/dkms/virtualbox/5.0.40/build/vboxdrv/SUPDrvGip.o
-CC [M]  /var/lib/dkms/virtualbox/5.0.40/build/vboxdrv/SUPDrvSem.o
-CC [M]  /var/lib/dkms/virtualbox/5.0.40/build/vboxdrv/SUPDrvTracer.o
-CC [M]  /var/lib/dkms/virtualbox/5.0.40/build/vboxdrv/SUPLibAll.o
-CC [M]  /var/lib/dkms/virtualbox/5.0.40/build/vboxdrv/r0drv/alloc-r0drv.o
-CC [M]  
/var/lib/dkms/virtualbox/5.0.40/build/vboxdrv/r0drv/initterm-r0drv.o
-CC [M]  /var/lib/dkms/virtualbox/5.0.40/build/vboxdrv/r0drv/memobj-r0drv.o
-CC [M]  
/var/lib/dkms/virtualbox/5.0.40/build/vboxdrv/r0drv/mpnotification-r0drv.o
-CC [M]  
/var/lib/dkms/virtualbox/5.0.40/build/vboxdrv/r0drv/powernotification-r0drv.o
-CC [M]  
/var/lib/dkms/virtualbox/5.0.40/build/vboxdrv/r0drv/linux/assert-r0drv-linux.o
-CC [M]  
/var/lib/dkms/virtualbox/5.0.40/build/vboxdrv/r0drv/linux/alloc-r0drv-linux.o
-  In file included from 
/var/lib/dkms/virtualbox/5.0.40/build/vboxdrv/r0drv/linux/alloc-r0drv-linux.c:31:0:
-  
/var/lib/dkms/virtualbox/5.0.40/build/vboxdrv/r0drv/linux/alloc-r0drv-linux.c: 
In function ‘VBoxHost_RTMemContAlloc’:
-  
/var/lib/dkms/virtualbox/5.0.40/build/vboxdrv/r0drv/linux/the-linux-kernel.h:313:47:
 error: implicit declaration of function ‘set_pages_x’ 
[-Werror=implicit-function-declaration]
-   # define MY_SET_PAGES_EXEC(pPages, cPages)set_pages_x(pPages, cPages)
- ^
-  
/var/lib/dkms/virtualbox/5.0.40/build/vboxdrv/r0drv/linux/alloc-r0drv-linux.c:444:13:
 note: in expansion of macro ‘MY_SET_PAGES_EXEC’
-   MY_SET_PAGES_EXEC([iPage], 1);
-   ^
-  
/var/lib/dkms/virtualbox/5.0.40/build/vboxdrv/r0drv/linux/alloc-r0drv-linux.c: 
In function ‘VBoxHost_RTMemContFree’:
-  
/var/lib/dkms/virtualbox/5.0.40/build/vboxdrv/r0drv/linux/the-linux-kernel.h:314:47:
 error: implicit declaration of function ‘set_pages_nx’ 
[-Werror=implicit-function-declaration]
-   # define MY_SET_PAGES_NOEXEC(pPages, cPages)  set_pages_nx(pPages, cPages)
- ^
-  
/var/lib/dkms/virtualbox/5.0.40/build/vboxdrv/r0drv/linux/alloc-r0drv-linux.c:492:13:
 note: in expansion of macro ‘MY_SET_PAGES_NOEXEC’
-   MY_SET_PAGES_NOEXEC([iPage], 1);
-   ^
-  cc1: some warnings being treated as errors
-  scripts/Makefile.build:302: polecenia dla obiektu 
'/var/lib/dkms/virtualbox/5.0.40/build/vboxdrv/r0drv/linux/alloc-r0drv-linux.o' 
nie powiodły się
-  make[2]: *** 
[/var/lib/dkms/virtualbox/5.0.40/build/vboxdrv/r0drv/linux/alloc-r0drv-linux.o] 
Błąd 1
-  scripts/Makefile.build:575: polecenia dla obiektu 
'/var/lib/dkms/virtualbox/5.0.40/build/vboxdrv' nie powiodły się
-  make[1]: *** [/var/lib/dkms/virtualbox/5.0.40/build/vboxdrv] Błąd 2
-  Makefile:1546: polecenia dla obiektu 
'_module_/var/lib/dkms/virtualbox/5.0.40/build' nie powiodły się
-  make: *** [_module_/var/lib/dkms/virtualbox/5.0.40/build] Błąd 2
-  make: Opuszczenie katalogu '/usr/src/linux-headers-4.13.0-16-generic'
+  DKMS make.log for virtualbox-5.0.40 for kernel 4.13.0-16-generic (x86_64)
+  czw, 2 lis 2017, 11:44:13 CET
+  make: Wejście do katalogu '/usr/src/linux-headers-4.13.0-16-generic'
+    AR  /var/lib/dkms/virtualbox/5.0.40/build/built-in.o
+    AR  /var/lib/dkms/virtualbox/5.0.40/build/vboxdrv/built-in.o
+    CC [M]  /var/lib/dkms/virtualbox/5.0.40/build/vboxdrv/linux/SUPDrv-linux.o
+    CC [M]  /var/lib/dkms/virtualbox/5.0.40/build/vboxdrv/SUPDrv.o
+    CC [M]  /var/lib/dkms/virtualbox/5.0.40/build/vboxdrv/SUPDrvGip.o
+    CC [M]  /var/lib/dkms/virtualbox/5.0.40/build/vboxdrv/SUPDrvSem.o
+    CC [M]  /var/lib/dkms/virtualbox/5.0.40/build/vboxdrv/SUPDrvTracer.o
+    CC [M] 

[Group.of.nepali.translators] [Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

[Launchpad Bug Tracker]

This bug was fixed in the package resolvconf - 1.78ubuntu5

---
resolvconf (1.78ubuntu5) xenial; urgency=medium

  * support reading dns information written by initramfs. (LP: #1711760)

 -- Scott Moser   Mon, 23 Oct 2017 12:44:53 -0400

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

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

Title:
  [2.3] resolv.conf is not set (during commissioning or testing)

Status in MAAS:
  Fix Committed
Status in resolvconf package in Ubuntu:
  Won't Fix
Status in resolvconf source package in Xenial:
  Fix Released

Bug description:
  === Begin SRU Template ===
  [Impact]
  Without this fix applied, dns settings provided to the dhcp response
  in the initramfs are not reflected in the "real root".

  Thus dns resolution does not work. Of most interest was the MAAS use
  case of the 'root=http://<>/squashfs' use case.  MAAS 2.3 uses this for
  the installation environment and also the rescue environment.

  [Test Case]
  There are two tests for this.

  a.) local/non-MAAS test
  Download the test case attached.
  Run it and follow the instructions.
  Login to the guest (ubuntu:password), and inspect /etc/resolv.conf
  without the fix there would be no data in /etc/resolv.conf.  With the
  fix you should see 'nameserver 10.0.2.2' and 'search mydomain.com bar.com'

  b.) MAAS test.
  For the full maas test, you need to build a image stream for maas
  with the fix included in the squashfs image and then import that
  stream to maas and use the rescue environment and verify dns.
  This process is beyond the scope of the SRU template, but is
  described partially in
    
http://bazaar.launchpad.net/~maas-images-maintainers/maas-images/maas-ephemerals/view/head:/README

  [Regression Potential]
  Regression potential should be very low.  There are gates in the code
  to make sure that this code is inactive other than when it is explicitly
  enabled.

  net-interface-handler will exit without doing anything unless:
  a.) there exist files /run/net-$INTERFACE.conf or /run/net6-$INTERFACE.conf
  and these files have non-empty values for a variable mentioned above.
  (These files are written by the initramfs code when 'ip=' is seen).

  b.) this is not a container.

  c.) there is no OPENISCSI_MARKER file (/run/initramfs/open-iscsi.interface)
  if open-iscsi has written this file due to open-iscsi root, then it
  will handle this functionality. resolvconf will get out of the way.

  d.) /proc/cmdline contains cloud-config-url=* or 'rc-initrd-dns'
  This lowers the scope of changes in runtime to cases with where either the
  new flag is seen or cloud-config-url is passed. The MAAS use case will
  contain this flag.

  [Other Info]

  === End SRU Template ===

  Using MAAS 2.3, during commissioning (and likely in the rest of the
  ephemeral environment) we have noticed that resolv.conf is not set
  with the DNS server.

  That said, during the commissioning process, MAAS does not send any
  metadata to cloud-init to configure the network, rather, we expect the
  image to boot from the network via DHCP. So, cloud-init writes:

  ubuntu@manual:~$ cat /etc/network/interfaces.d/50-cloud-init.cfg
  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  auto lo
  iface lo inet loopback

  # control-manual ens3
  iface ens3 inet dhcp
  broadcast 192.168.122.255
  dns-nameservers 192.168.122.2
  gateway 192.168.122.1
  netmask 255.255.255.0

  Which correctly includes the DNS server. However:

  ubuntu@manual:~$ ping google.com
  ping: unknown host google.com

  If restart the interfacE:

  ubuntu@manual:~$ sudo ifdown ens3 && sudo ifup ens3
  ifdown: interface ens3 not configured
  Internet Systems Consortium DHCP Client 4.3.3
  Copyright 2004-2015 Internet Systems Consortium.
  All rights reserved.
  For info, please visit https://www.isc.org/software/dhcp/

  Listening on LPF/ens3/52:54:00:ea:57:31
  Sending on   LPF/ens3/52:54:00:ea:57:31
  Sending on   Socket/fallback
  DHCPDISCOVER on ens3 to 255.255.255.255 port 67 interval 3 (xid=0x14eb0354)
  DHCPDISCOVER on ens3 to 255.255.255.255 port 67 interval 4 (xid=0x14eb0354)
  DHCPREQUEST of 192.168.122.195 on ens3 to 255.255.255.255 port 67 
(xid=0x5403eb14)
  DHCPOFFER of 192.168.122.195 from 192.168.122.2
  DHCPACK of 192.168.122.195 from 192.168.122.2
  Restarting ntp (via systemctl): ntp.service.
  bound to 192.168.122.195 -- renewal in 290 seconds.

  ubuntu@manual:~$ cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc 

[Group.of.nepali.translators] [Bug 1721808] Re: sru curtin 2017-10-06 - 0.1.0~bzr532-0ubuntu1

[Launchpad Bug Tracker]

This bug was fixed in the package curtin - 0.1.0~bzr532-0ubuntu1~16.04.1

---
curtin (0.1.0~bzr532-0ubuntu1~16.04.1) xenial; urgency=medium

  * New upstream snapshot. (LP: #1721808)
- vmtest: fix artful networking
- docs: Trivial doc fix for enabling proposed.
- setup.py: fix to allow installation into a virtualenv
- doc: update documentation on curtin-hooks and non-ubuntu installation.
- reporter: Add journald reporter to send events to journald
- vmtests: add option to tar disk images after test run
- install: ensure iscsi service is running to handle shutdown properly
- mdadm: handle write failures to sysfs entries when stopping mdadm
- vmtest: catch exceptions in curtin-log-print
- iscsi: use curtin storage config to disconnect iscsi targets
- vmtests: bump skip_by_date values out to give cloud-init SRU more time
- vmtest: get info about collected symlinks and then delete them.
- Update network cloud-init related skiptest dates, SRU still pending
- tests: Add CiTestCase common parent for all curtin tests.
- vmtests: Remove force flag for centos curthooks
- tools/jenkins-runner: improve tgtd cleanup logic
- tests: Drop EOL Wily Vivid and Yakkety tests.
- Disable yum plugins when installing packages, update ca-certs for https
- Rename centos_network_curthooks -> centos_apply_network_config.
- tests: in centos_defaults use write_files for grub serial.
- write_files: write files after extract, change write_files signature.
- pass network configuration through to target for ubuntu and centos
- tests: disable yakkety tests.
- tools/launch: automatically pass on proxy settings to curtin
- Add top level 'proxy' to config, deprecate top level http_proxy.
- tools/curtainer: fix to enable deb-src for -proposed.
- Use unshare to put chroot commands in own pid namespace.

 -- Chad Smith   Fri, 06 Oct 2017 10:07:36
-0600

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

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

Title:
  sru curtin 2017-10-06 - 0.1.0~bzr532-0ubuntu1

Status in curtin package in Ubuntu:
  Fix Released
Status in curtin source package in Xenial:
  Fix Released
Status in curtin source package in Zesty:
  Fix Released

Bug description:
  == Begin SRU Template ==
  [Impact]
  This release sports both bug-fixes and new features and we would like to
  make sure all of our supported customers have access to these improvements.
  The notable ones are:

  See the changelog entry below for a full list of changes and bugs.
    - Fixes to support installation of Artful.
  (LP: #1714028, LP: #1718216, LP: #1706744)
    - mdadm: handle write failures to sysfs entries when stopping mdadm
  (LP: #1708052)
    - iscsi: use curtin storage config to disconnect iscsi targets
  (LP: #1713537)
    - network configuration passthrough.  For targets that have
      a sufficient version of cloud-init, network config is now
      passed through to cloud-init rather than being rendered
      by curtin.

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

  Curtin now contains an extensive integration test suite that is ran using
  the SRU package for each releases. These suite has documentation here:
  https://curtin.readthedocs.io/en/latest/topics/integration-testing.html

  In order to avoid regression to existing MAAS product, the MAAS team will
  run their continuous integration test against the curtin that is in
  -proposed. A successful run will be required before the proposed curtin
  can be let into -updates.

  The curtin team will be in charge of attaching the artifacts and console
  output of the appropriate run to the bug. Curtin team members will not
  mark 'verification-done' until this has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned integration tests are attached to this bug.

  [Verification]
  integration tests for xenial:
   * log: see attached curtin-vmtest-x.tar.gz:
   * artifacts: see attached curtin-vmtest-x.log

  integration tests for zesty:
   * log: see attached curtin-vmtest-z.tar.gz:
   * artifacts: see attached curtin-vmtest-z.log

  maas qa tests for xenial:
   * log: see attached maas-xenial-proposed-console.txt
   * artifacts: see attached maas-qa-artifacts-curtin-xenial-proposed.zip

  [Discussion]
  The primary motivation for this fix is support for installation of
  17.10 (Artful) and passthrough networking configuration.

  == End SRU Template ==

  The full changelog with bug references:
    * New upstream snapshot.
  - vmtest: fix artful networking (LP: #1714028, LP: #1718216, LP: #1706744)
     

[Group.of.nepali.translators] [Bug 1721808] Re: sru curtin 2017-10-06 - 0.1.0~bzr532-0ubuntu1

[Launchpad Bug Tracker]

This bug was fixed in the package curtin - 0.1.0~bzr532-0ubuntu1~17.04.1

---
curtin (0.1.0~bzr532-0ubuntu1~17.04.1) zesty; urgency=medium

  * New upstream snapshot. (LP: #1721808)
- vmtest: fix artful networking
- docs: Trivial doc fix for enabling proposed.
- setup.py: fix to allow installation into a virtualenv
- doc: update documentation on curtin-hooks and non-ubuntu installation.
- reporter: Add journald reporter to send events to journald
- vmtests: add option to tar disk images after test run
- install: ensure iscsi service is running to handle shutdown properly
- mdadm: handle write failures to sysfs entries when stopping mdadm
- vmtest: catch exceptions in curtin-log-print
- iscsi: use curtin storage config to disconnect iscsi targets
- vmtests: bump skip_by_date values out to give cloud-init SRU more time
- vmtest: get info about collected symlinks and then delete them.
- Update network cloud-init related skiptest dates, SRU still pending
- tests: Add CiTestCase common parent for all curtin tests.
- vmtests: Remove force flag for centos curthooks
- tools/jenkins-runner: improve tgtd cleanup logic
- tests: Drop EOL Wily Vivid and Yakkety tests.
- Disable yum plugins when installing packages, update ca-certs for https
- Rename centos_network_curthooks -> centos_apply_network_config.
- tests: in centos_defaults use write_files for grub serial.
- write_files: write files after extract, change write_files signature.
- pass network configuration through to target for ubuntu and centos
- tests: disable yakkety tests.
- tools/launch: automatically pass on proxy settings to curtin
- Add top level 'proxy' to config, deprecate top level http_proxy.
- tools/curtainer: fix to enable deb-src for -proposed.
- Use unshare to put chroot commands in own pid namespace.

 -- Chad Smith   Fri, 06 Oct 2017 10:53:10
-0600

** Changed in: curtin (Ubuntu Zesty)
   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/1721808

Title:
  sru curtin 2017-10-06 - 0.1.0~bzr532-0ubuntu1

Status in curtin package in Ubuntu:
  Fix Released
Status in curtin source package in Xenial:
  Fix Released
Status in curtin source package in Zesty:
  Fix Released

Bug description:
  == Begin SRU Template ==
  [Impact]
  This release sports both bug-fixes and new features and we would like to
  make sure all of our supported customers have access to these improvements.
  The notable ones are:

  See the changelog entry below for a full list of changes and bugs.
    - Fixes to support installation of Artful.
  (LP: #1714028, LP: #1718216, LP: #1706744)
    - mdadm: handle write failures to sysfs entries when stopping mdadm
  (LP: #1708052)
    - iscsi: use curtin storage config to disconnect iscsi targets
  (LP: #1713537)
    - network configuration passthrough.  For targets that have
      a sufficient version of cloud-init, network config is now
      passed through to cloud-init rather than being rendered
      by curtin.

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

  Curtin now contains an extensive integration test suite that is ran using
  the SRU package for each releases. These suite has documentation here:
  https://curtin.readthedocs.io/en/latest/topics/integration-testing.html

  In order to avoid regression to existing MAAS product, the MAAS team will
  run their continuous integration test against the curtin that is in
  -proposed. A successful run will be required before the proposed curtin
  can be let into -updates.

  The curtin team will be in charge of attaching the artifacts and console
  output of the appropriate run to the bug. Curtin team members will not
  mark 'verification-done' until this has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned integration tests are attached to this bug.

  [Verification]
  integration tests for xenial:
   * log: see attached curtin-vmtest-x.tar.gz:
   * artifacts: see attached curtin-vmtest-x.log

  integration tests for zesty:
   * log: see attached curtin-vmtest-z.tar.gz:
   * artifacts: see attached curtin-vmtest-z.log

  maas qa tests for xenial:
   * log: see attached maas-xenial-proposed-console.txt
   * artifacts: see attached maas-qa-artifacts-curtin-xenial-proposed.zip

  [Discussion]
  The primary motivation for this fix is support for installation of
  17.10 (Artful) and passthrough networking configuration.

  == End SRU Template ==

  The full changelog with bug references:
    * New upstream snapshot.
  - vmtest: fix artful networking (LP: #1714028, LP: #1718216, LP: #1706744)
  

[Group.of.nepali.translators] [Bug 1730188] Re: linux-image-4.4.0-98 kernel panic

[Joseph Salisbury]

Can you see if this panic is also happening with the kernel in Xenial 
-proposed?  It is available from:
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+build/13668431

** Changed in: linux (Ubuntu)
   Importance: Undecided => High

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

** Changed in: linux (Ubuntu Xenial)
   Importance: Undecided => High

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

** Tags added: kernel-key

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

Title:
  linux-image-4.4.0-98 kernel panic

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Confirmed

Bug description:
  Since updating to linux-image-4.4.0-98-generic 2 days ago, I get a kernel 
panic during boot. With 4.4.0-97 the machine boots fine. Screenshot attached.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jos1929 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=5577332d-7a0a-4c5a-9c10-93a5cd6f5e65
  InstallationDate: Installed on 2013-01-05 (1764 days ago)
  InstallationMedia: This
  Lsusb:
   Bus 002 Device 003: ID 04f2:b34c Chicony Electronics Co., Ltd 
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: wortmann TERRA MOBILE 1512/1712
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-97-generic 
root=UUID=b9e9b26b-d84a-494e-921d-31e5e92726eb ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-97-generic N/A
   linux-backports-modules-4.4.0-97-generic  N/A
   linux-firmware1.157.13
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  xenial
  Uname: Linux 4.4.0-97-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-08-07 (454 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/22/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: TERRA MOBILE 1512/1712
  dmi.board.vendor: Wortmann AG
  dmi.board.version: V3.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Wortmann AG
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/22/2012:svnwortmann:pnTERRAMOBILE1512/1712:pvrNotApplicable:rvnWortmannAG:rnTERRAMOBILE1512/1712:rvrV3.0:cvnWortmannAG:ct10:cvrN/A:
  dmi.product.name: TERRA MOBILE 1512/1712
  dmi.product.version: Not Applicable
  dmi.sys.vendor: wortmann

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730188/+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 1607929] Re: update-manager: missing dependency on libgtk2-perl for debconf frontend

[Steve Langasek]

** Changed in: shim-signed (Ubuntu)
   Status: Triaged => Confirmed

** Changed in: shim-signed (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/1607929

Title:
  update-manager: missing dependency on libgtk2-perl for debconf
  frontend

Status in shim-signed package in Ubuntu:
  Invalid
Status in update-manager package in Ubuntu:
  Fix Released
Status in update-manager source package in Trusty:
  Fix Released
Status in update-manager source package in Xenial:
  Fix Released
Status in update-manager source package in Yakkety:
  Won't Fix
Status in update-manager source package in Zesty:
  Fix Released

Bug description:
  [Impact]
  update-manager is missing a recommends on libgtk2-perl which allows it to 
display debconf prompts. While we've fixed software-properties-gtk and 
gnome-software to depend / recommend libgk2-perl and this will resolve the 
issue for most installations it'd be best to fix update-manager too for all 
releases in case there is some installation situation where libgtk2-perl is 
missing.

  [Test Case]
  1) Uninstall libgtk2-perl - 'sudo apt-get remove libgtk2-perl'
  2) Launch update-manager from a terminal
  3) Observe the following message in the terminal:

  debconf: unable to initialize frontend: Gnome
  debconf: (Can't locate Gtk2.pm in @INC (you may need to install the Gtk2 
module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.24.1 
/usr/local/share/perl/5.24.1 /usr/lib/x86_64-linux-gnu/perl5/5.24 
/usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.24 /usr/share/perl/5.24 
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at 
/usr/share/perl5/Debconf/FrontEnd/Gnome.pm line 91.)
  debconf: falling back to frontend: Dialog

  [Regression Potential]
  None - no really! We are just adding a recommends on another package.

  Original Description
  
  I'm not really sure whether this is a bug; I think the install was hanging 
for a while, with a blank window displaying. I killed the install and it went 
away, but it's certainly plausible that this is due to something local, not a 
bug. Feel free to close this if nobody else is seeing it.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: shim-signed 1.17~14.04.1+0.8-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-85.129-generic 3.13.11-ckt36
  Uname: Linux 3.13.0-85-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  BootEFIContents:
   grub.cfg
   grubx64.efi
   MokManager.efi
   shimx64.efi
  Date: Fri Jul 29 15:45:46 2016
  DuplicateSignature: package:shim-signed:1.17~14.04.1+0.8-0ubuntu2:subprocess 
installed post-installation script was killed by signal (Terminated)
  ErrorMessage: subprocess installed post-installation script was killed by 
signal (Terminated)
  InstallationDate: Installed on 2014-05-23 (798 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.14SourcePackage: shim-signed
  Title: package shim-signed 1.17~14.04.1+0.8-0ubuntu2 failed to 
install/upgrade: subprocess installed post-installation script was killed by 
signal (Terminated)
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1607929/+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 1727732] Re: Add Ubuntu bionic as a supported release

[Launchpad Bug Tracker]

This bug was fixed in the package debootstrap - 1.0.91ubuntu1.1

---
debootstrap (1.0.91ubuntu1.1) artful; urgency=medium

  * Add (Ubuntu) bionic as a symlink to gutsy.  (LP: #1727732)

 -- Andy Whitcroft   Thu, 26 Oct 2017 14:30:19 +0100

** Changed in: debootstrap (Ubuntu Artful)
   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/1727732

Title:
  Add Ubuntu bionic as a supported release

Status in debootstrap package in Ubuntu:
  Fix Released
Status in debootstrap source package in Trusty:
  Fix Committed
Status in debootstrap source package in Xenial:
  Fix Committed
Status in debootstrap source package in Zesty:
  Fix Committed
Status in debootstrap source package in Artful:
  Fix Released

Bug description:
  Add Ubuntu bionic 18.04 LTS to debootstrap.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debootstrap/+bug/1727732/+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 1728971] Re: linux-hwe: 4.10.0-39.43~16.04.1 -proposed tracker

[Brad Figg]

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

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

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

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

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

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

** Description changed:

  This bug is for tracking the  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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1728969
  phase: Uploaded
+ kernel-stable-phase:Promoted to proposed
+ kernel-stable-phase-changed:Monday, 06. November 2017 20:31 UTC

** Description changed:

  This bug is for tracking the  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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1728969
- phase: Uploaded
- kernel-stable-phase:Promoted to proposed
- kernel-stable-phase-changed:Monday, 06. November 2017 20:31 UTC
+ phase: Promoted to proposed
+ proposed-announcement-sent: true
+ proposed-testing-requested: true

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

Title:
  linux-hwe: 4.10.0-39.43~16.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
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:
  Confirmed
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-hwe package in Ubuntu:
  Invalid
Status in linux-hwe source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1728969
  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/1728971/+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 1729280] Re: linux-aws: 4.4.0-1040.49 -proposed tracker

[Brad Figg]

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

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

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

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

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

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

** Description changed:

  This bug is for tracking the  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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1729273
  phase: Uploaded
+ kernel-stable-phase-changed:Monday, 06. November 2017 19:00 UTC
+ kernel-stable-phase:Promoted to proposed

** Description changed:

  This bug is for tracking the  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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1729273
- phase: Uploaded
- kernel-stable-phase-changed:Monday, 06. November 2017 19:00 UTC
- kernel-stable-phase:Promoted to proposed
+ phase: Promoted to proposed
+ proposed-announcement-sent: true
+ proposed-testing-requested: true

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

Title:
  linux-aws: 4.4.0-1040.49 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
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 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:
  Confirmed
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1729273
  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/1729280/+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 1565060] Re: defaults file is ignored

[Seth Arnold]

** Also affects: bind9 (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/1565060

Title:
  defaults file is ignored

Status in bind9 package in Ubuntu:
  Fix Committed
Status in bind9 source package in Xenial:
  Confirmed
Status in bind9 source package in Yakkety:
  Won't Fix
Status in bind9 source package in Zesty:
  New
Status in bind9 package in Debian:
  Fix Committed

Bug description:
  i've just upgraded to 15.10, and have now found that the
  /etc/defaults/bind9 file appears to be ignored.   yet another package
  broken by the adoption of systemd, it would seem.

  >cat /etc/default/bind9 
  # run resolvconf?
  RESOLVCONF=yes

  # startup options for the server
  OPTIONS="-4 -u bind"
  >

  >service bind9 stop
  >

  >service bind9 start
  >

  >ps -aefwww | grep -iF named
  bind  3810 1 17 15:32 ?00:00:01 /usr/sbin/named -f -u bind
  >

  modifying /lib/systemd/system/bind9.service works, but this does not
  seem to offer the same degree of abstraction provided by the files in
  /etc/default/.

  1] >lsb_release -rd
  Description:  Ubuntu 15.10
  Release:  15.10

  2] >apt-cache policy bind9
  bind9:
Installed: 1:9.9.5.dfsg-11ubuntu1.3
Candidate: 1:9.9.5.dfsg-11ubuntu1.3
Version table:
   *** 1:9.9.5.dfsg-11ubuntu1.3 0
  500 http://us.archive.ubuntu.com/ubuntu/ wily-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu/ wily-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:9.9.5.dfsg-11ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages

  3] i expected to be able to be able to make changes in
  /etc/defaults/bind9 and have them honored.

  4] they are not.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1565060/+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 1565060] Re: defaults file is ignored

[Andreas Hasenack]

** Changed in: bind9 (Ubuntu Yakkety)
   Status: Confirmed => Won't Fix

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

Title:
  defaults file is ignored

Status in bind9 package in Ubuntu:
  Fix Committed
Status in bind9 source package in Xenial:
  Confirmed
Status in bind9 source package in Yakkety:
  Won't Fix
Status in bind9 source package in Zesty:
  New
Status in bind9 package in Debian:
  Fix Committed

Bug description:
  i've just upgraded to 15.10, and have now found that the
  /etc/defaults/bind9 file appears to be ignored.   yet another package
  broken by the adoption of systemd, it would seem.

  >cat /etc/default/bind9 
  # run resolvconf?
  RESOLVCONF=yes

  # startup options for the server
  OPTIONS="-4 -u bind"
  >

  >service bind9 stop
  >

  >service bind9 start
  >

  >ps -aefwww | grep -iF named
  bind  3810 1 17 15:32 ?00:00:01 /usr/sbin/named -f -u bind
  >

  modifying /lib/systemd/system/bind9.service works, but this does not
  seem to offer the same degree of abstraction provided by the files in
  /etc/default/.

  1] >lsb_release -rd
  Description:  Ubuntu 15.10
  Release:  15.10

  2] >apt-cache policy bind9
  bind9:
Installed: 1:9.9.5.dfsg-11ubuntu1.3
Candidate: 1:9.9.5.dfsg-11ubuntu1.3
Version table:
   *** 1:9.9.5.dfsg-11ubuntu1.3 0
  500 http://us.archive.ubuntu.com/ubuntu/ wily-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu/ wily-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:9.9.5.dfsg-11ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages

  3] i expected to be able to be able to make changes in
  /etc/defaults/bind9 and have them honored.

  4] they are not.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1565060/+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 1730444] Re: linux-azure-edge: Rebase to Artful Ubuntu-4.13.0-17.20

[Kamal Mostafa]

** Also affects: linux-azure (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/1730444

Title:
  linux-azure-edge: Rebase to Artful Ubuntu-4.13.0-17.20

Status in linux-azure package in Ubuntu:
  Fix Committed
Status in linux-azure source package in Xenial:
  Fix Committed

Bug description:
  SRU Justification:

  Impact: Sync with Artful for fixes and CVEs.
  Fix: Rebase to Ubuntu-4.13.0-17.20.
  Testcase: No new regressions on the regression and ADT tests.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1730444/+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 1693369] Re: 5U84 - ses driver isn't binding right - cannot blink lights on 1 of the 2 5u84

[Manoj Iyer]

** Changed in: ubuntu-power-systems
   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/1693369

Title:
  5U84 - ses driver isn't binding right - cannot blink lights on 1 of
  the 2 5u84

Status in The Ubuntu-power-systems project:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Zesty:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  
  == SRU Justification ==
  This bug is resolved by commit 62e62ffd95539b9220894a7900a619e0f3ef4756.

  Without this patch, the symlink in sysfs which binds a SAS device to an 
enclosure 
  slot does not get created. This makes disk hotplug near impossible on large 
  JBOD disk drawers.

  Commit 62e62ffd95 is also needed in Xenial.  However, Xenial also needed some 
  prereq commits, so it's SRU will be sent separately.

  Commit 62e62ffd95 is in mainline as of 4.13-rc1.

  
  == Fix ==
  commit 62e62ffd95539b9220894a7900a619e0f3ef4756
  Author: Maurizio Lombardi 
  Date:   Tue Jun 27 11:53:27 2017 +0200

  scsi: ses: do not add a device to an enclosure if
  enclosure_add_links() fails.

  == Regression Potential ==
  This patch was also cc'd and applied to upstream stable, so there is 
  upstream confidence in it.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.


  
  This is a request to add the following upstream commit to both Ubuntu 16.04.1 
and 16.04.2:

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/scsi/ses.c?id=9373eba6cfae48911b977d14323032cd5d161aae

  Without this patch, the symlink in sysfs which binds a SAS device to
  an enclosure slot does not get created. This makes disk hotplug near
  impossible on large JBOD disk drawers.

  You should be able to do:

  ls /sys/block/sdb/device/ | grep enclosure

  and see something like:

  enclosure_device:1

  If you cd to this directory, you can then access the SES controls for
  that slot to flash the LED to assist in locating the disk to replace a
  failed disk.

  Currently with 16.04.1 and 16.04.2, these symlinks are not getting
  created.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1693369/+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 1730343] Re: firmware update breaks Ubuntu

[Mario Limonciello]

fixed in unstable via
https://anonscm.debian.org/cgit/uefi/fwupdate.git/commit/?id=7b6d96818db166456bbd9aafb031e7d990e06ef8,
should sync to ubuntu for bionic

** Changed in: fwupdate (Ubuntu Bionic)
   Status: New => Fix Committed

** Also affects: fwupdate-signed (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/1730343

Title:
  firmware update breaks Ubuntu

Status in Fwupd:
  New
Status in fwupd package in Ubuntu:
  Invalid
Status in fwupdate package in Ubuntu:
  Fix Committed
Status in fwupdate-signed package in Ubuntu:
  New
Status in fwupd source package in Xenial:
  Invalid
Status in fwupdate source package in Xenial:
  New
Status in fwupdate-signed source package in Xenial:
  New
Status in fwupd source package in Zesty:
  Invalid
Status in fwupdate source package in Zesty:
  New
Status in fwupdate-signed source package in Zesty:
  New
Status in fwupd source package in Artful:
  Invalid
Status in fwupdate source package in Artful:
  New
Status in fwupdate-signed source package in Artful:
  New
Status in fwupd source package in Bionic:
  Invalid
Status in fwupdate source package in Bionic:
  Fix Committed
Status in fwupdate-signed source package in Bionic:
  New

Bug description:
  Two users have reported that fwupd breaks their Ubuntu installation
  because the "Ubuntu" EFI boot option disappears after an update.

  It might be best to consider turning off firmware updates until this
  issue is fixed.

  Upstream issue: https://github.com/rhboot/fwupdate/issues/86

To manage notifications about this bug go to:
https://bugs.launchpad.net/fwupd/+bug/1730343/+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 1729858] Re: virt-clone fails with: Unknown driver 'iso'

[ChristianEhrhardt]

Hi Jürg,
thanks for using the tool - I rarely do so I appreciate your testing.
Furthermore identifying the fix is nice.

So this went into libvirt in 3.2, so >=Artful is fixed.


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

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

** Changed in: libvirt (Ubuntu Xenial)
   Status: New => Triaged

** Changed in: libvirt (Ubuntu Zesty)
   Status: New => Triaged

** Changed in: libvirt (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/1729858

Title:
  virt-clone fails with: Unknown driver 'iso'

Status in libvirt package in Ubuntu:
  Fix Released
Status in libvirt source package in Xenial:
  Triaged
Status in libvirt source package in Zesty:
  Triaged

Bug description:
  Cloning a uvt VM fails with error: Unknown driver 'iso'

  To reproduce:

  uvt-simplestreams-libvirt sync release=xenial arch=amd64
  uvt-kvm create test-vm release=xenial arch=amd64
  virsh destroy test-vm
  virt-clone -o test-vm -n cloned-vm --auto-clone

  Which results in:

  WARNING  The requested volume capacity will exceed the available pool space 
when the volume is fully allocated. (8192 M requested capacity > 3898 M 
available)
  Allocating 'cloned-vm.qcow'   
   | 
8.0 GB  00:00:01 
  ERRORCouldn't create storage volume 'test-vm-ds-clone.qcow': 'internal 
error: Child process (/usr/bin/qemu-img convert -f iso -O iso 
/var/lib/uvtool/libvirt/images/test-vm-ds.qcow 
/var/lib/uvtool/libvirt/images/test-vm-ds-clone.qcow) unexpected exit status 1: 
qemu-img: Could not open '/var/lib/uvtool/libvirt/images/test-vm-ds.qcow': 
Unknown driver 'iso'
  '

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1729858/+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 1730343] Re: firmware update breaks Ubuntu

[Mario Limonciello]

Yeah I agree it's better avoided.  It should SRU to 16.04's 05-2ubuntu5
too actually.

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

** Bug watch removed: github.com/juju-solutions/charms.reactive/issues #139
   https://github.com/juju-solutions/charms.reactive/issues/139

** Also affects: fwupdate (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Also affects: fwupd (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Also affects: fwupdate (Ubuntu Bionic)
   Importance: High
   Status: New

** Also affects: fwupd (Ubuntu Bionic)
   Importance: Undecided
   Status: Invalid

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

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

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

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

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

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

** Changed in: fwupd (Ubuntu Artful)
   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/1730343

Title:
  firmware update breaks Ubuntu

Status in Fwupd:
  New
Status in fwupd package in Ubuntu:
  Invalid
Status in fwupdate package in Ubuntu:
  New
Status in fwupd source package in Xenial:
  Invalid
Status in fwupdate source package in Xenial:
  New
Status in fwupd source package in Zesty:
  Invalid
Status in fwupdate source package in Zesty:
  New
Status in fwupd source package in Artful:
  Invalid
Status in fwupdate source package in Artful:
  New
Status in fwupd source package in Bionic:
  Invalid
Status in fwupdate source package in Bionic:
  New

Bug description:
  Two users have reported that fwupd breaks their Ubuntu installation
  because the "Ubuntu" EFI boot option disappears after an update.

  It might be best to consider turning off firmware updates until this
  issue is fixed.

  Upstream issue: https://github.com/rhboot/fwupdate/issues/86

To manage notifications about this bug go to:
https://bugs.launchpad.net/fwupd/+bug/1730343/+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 1728935] Re: linux-hwe-edge: 4.13.0-17.20~16.04.1 -proposed tracker

[Brad Figg]

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

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: In Progress => Fix Released

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

** Description changed:

  This bug is for tracking the  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 --
  kernel-stable-master-bug: 1728927
  phase: Packaging
+ kernel-stable-phase:Uploaded
+ kernel-stable-phase-changed:Monday, 06. November 2017 15:02 UTC

** Description changed:

  This bug is for tracking the  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 --
  kernel-stable-master-bug: 1728927
- phase: Packaging
- kernel-stable-phase:Uploaded
- kernel-stable-phase-changed:Monday, 06. November 2017 15:02 UTC
+ phase: Uploaded

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

Title:
  linux-hwe-edge: 4.13.0-17.20~16.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
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:
  New
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:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
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  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 --
  kernel-stable-master-bug: 1728927
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1728935/+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 1709784] Re: KVM on 16.04.3 throws an error

[Andrew Cloke]

Based on comments above, moving to "Fix Released". If this issue re-
occurs, please update with a new comment.

** Changed in: ubuntu-power-systems
   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/1709784

Title:
  KVM on 16.04.3 throws an error

Status in The Ubuntu-power-systems project:
  Fix Released
Status in linux package in Ubuntu:
  Fix Committed
Status in qemu package in Ubuntu:
  Won't Fix
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Zesty:
  Invalid

Bug description:
  Problem Description
  
  KVM on Ubuntu 16.04.3 throws an error when used
   
  ---uname output---
  Linux bastion-1 4.4.0-89-generic #112-Ubuntu SMP Mon Jul 31 19:37:08 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type =  8348-21C Habanero 
   
  ---Steps to Reproduce---
   Install 16.04.3

  install KVM like:

  apt-get install libvirt-bin qemu qemu-slof qemu-system qemu-utils

  then exit and log back in so virsh will work without sudo

  then run my spawn script

  $ cat spawn.sh
  #!/bin/bash

  img=$1
  qemu-system-ppc64 \
  -machine pseries,accel=kvm,usb=off -cpu host -m 512 \
  -display none -nographic \
  -net nic -net user \
  -drive "file=$img"

  with a freshly downloaded ubuntu cloud image

  sudo ./spawn.sh xenial-server-cloudimg-ppc64el-disk1.img

  And I get nothing on the output.

  and errors in dmesg

  
  ubuntu@bastion-1:~$ [  340.180295] Facility 'TM' unavailable, exception at 
0xd000148b7f10, MSR=90009033
  [  340.180399] Oops: Unexpected facility unavailable exception, sig: 6 [#1]
  [  340.180513] SMP NR_CPUS=2048 NUMA PowerNV
  [  340.180547] Modules linked in: xt_CHECKSUM iptable_mangle ipt_MASQUERADE 
nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 
nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp 
bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables 
iptable_filter ip_tables x_tables kvm_hv kvm binfmt_misc joydev input_leds 
mac_hid opal_prd ofpart cmdlinepart powernv_flash ipmi_powernv ipmi_msghandler 
mtd at24 uio_pdrv_genirq uio ibmpowernv powernv_rng vmx_crypto ib_iser rdma_cm 
iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 raid0 multipath 
linear mlx4_en hid_generic usbhid hid uas usb_storage ast i2c_algo_bit bnx2x 
ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops mlx4_core drm 
ahci vxlan libahci ip6_udp_tunnel udp_tunnel mdio libcrc32c
  [  340.181331] CPU: 46 PID: 5252 Comm: qemu-system-ppc Not tainted 
4.4.0-89-generic #112-Ubuntu
  [  340.181382] task: c01e34c30b50 ti: c01e34ce4000 task.ti: 
c01e34ce4000
  [  340.181432] NIP: d000148b7f10 LR: d00014822a14 CTR: 
d000148b7e40
  [  340.181475] REGS: c01e34ce77b0 TRAP: 0f60   Not tainted  
(4.4.0-89-generic)
  [  340.181519] MSR: 90009033   CR: 22024848  
XER: 
  [  340.181629] CFAR: d000148b7ea4 SOFTE: 1 
  GPR00: d00014822a14 c01e34ce7a30 d000148cc018 c01e37bc 
  GPR04: c01db9ac c01e34ce7bc0   
  GPR08: 0001 c01e34c30b50 0001 d000148278f8 
  GPR12: d000148b7e40 cfb5b500  001f 
  GPR16: 3fff91c3 0080 3fffa8e34390 3fff9242f200 
  GPR20: 3fff92430010 01001de5c030 3fff9242eb60 100c1ff0 
  GPR24: 3fffc91fe990 3fff91c10028  c01e37bc 
  GPR28:  c01db9ac c01e37bc c01db9ac 
  [  340.182315] NIP [d000148b7f10] kvmppc_vcpu_run_hv+0xd0/0xff0 [kvm_hv]
  [  340.182357] LR [d00014822a14] kvmppc_vcpu_run+0x44/0x60 [kvm]
  [  340.182394] Call Trace:
  [  340.182413] [c01e34ce7a30] [c01e34ce7ab0] 0xc01e34ce7ab0 
(unreliable)
  [  340.182468] [c01e34ce7b70] [d00014822a14] 
kvmppc_vcpu_run+0x44/0x60 [kvm]
  [  340.182522] [c01e34ce7ba0] [d0001481f674] 
kvm_arch_vcpu_ioctl_run+0x64/0x170 [kvm]
  [  340.182581] [c01e34ce7be0] [d00014813918] 
kvm_vcpu_ioctl+0x528/0x7b0 [kvm]
  [  340.182634] [c01e34ce7d40] [c02fffa0] do_vfs_ioctl+0x480/0x7d0
  [  340.182678] [c01e34ce7de0] [c03003c4] SyS_ioctl+0xd4/0xf0
  [  340.182723] [c01e34ce7e30] [c0009204] system_call+0x38/0xb4
  [  340.182766] Instruction dump:
  [  340.182788] e92d02a0 e9290a50 e9290108 792a07e3 41820058 e92d02a0 e9290a50 
e9290108 
  [  340.182863] 7927e8a4 78e71f87 40820ed8 e92d02a0 <7d4022a6> f9490ee8 
e92d02a0 7d4122a6 
  [  340.182938] ---[ end trace bc5080cb7d18f102 ]---
  [  

[Group.of.nepali.translators] [Bug 1715101] Re: Xenial : installer fails on POWER9

[Manoj Iyer]

** Changed in: ubuntu-power-systems
   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/1715101

Title:
  Xenial : installer fails on POWER9

Status in The Ubuntu-power-systems project:
  Fix Released
Status in debian-installer package in Ubuntu:
  Invalid
Status in debian-installer source package in Xenial:
  Fix Released

Bug description:
  Hi,

  could you please update the installer to use linux-hwe version >=
  4.10.0-29 for POWER9 on Xenial.

  At the moment the kernel/vmlinux in 
http://ports.ubuntu.com/ubuntu-ports/dists/xenial-proposed/main/installer-ppc64el/current/images/hwe-netboot/ubuntu-installer/ppc64el/
 is based on
  linux 4.10.0-28 which doesn't include this ERAT related patch 
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1700521 and other P9 
fixes also) which cause the installer to fail on POWER9.

  A move to hwe kernels with version greater than 4.10.0-29 should work.
  Thanks a lot.

  F.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1715101/+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 1722356] Re: Update google compute-image-packages to 20171006

[Launchpad Bug Tracker]

This bug was fixed in the package gce-compute-image-packages -
20171019+dfsg1-0ubuntu1~16.04.0

---
gce-compute-image-packages (20171019+dfsg1-0ubuntu1~16.04.0) xenial; 
urgency=medium

  [ Balint Reczey ]
  * New upstream version 20171019+dfsg1 (LP: #1726810)
- Add status option for google_oslogin_control
- OS Login activation via the accounts daemon
  * Tidy up d/control with the help of cme fix dpkg-control
  * Update symlink to shared library with updated minor version
  * Change package priority to optional from extra
  * Add debhelper token to prerm

  [ Zach Marano from Google Cloud Team ]
  * Depend on chrony | ntp | time-daemon instead of just ntp
  * Move all service activation handling to
gce-compute-image-packages.{postinst|prerm}
  * Make google-compute-engine depend on google-compute-engine-oslogin

  [ Łukasz 'sil2100' Zemczak ]
  * Backport to xenial.

 -- Balint Reczey   Tue, 24 Oct 2017 16:35:46 +0200

** Changed in: gce-compute-image-packages (Ubuntu Trusty)
   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/1722356

Title:
   Update google compute-image-packages to 20171006

Status in gce-compute-image-packages package in Ubuntu:
  Fix Released
Status in gce-compute-image-packages source package in Trusty:
  Fix Released
Status in gce-compute-image-packages source package in Xenial:
  Fix Released
Status in gce-compute-image-packages source package in Zesty:
  Fix Released

Bug description:
  [Impact]

  compute-image-packages is provided by Google for installation within
  guests that run on Google Compute Engine. It is a collection of tools
  and daemons, packaged as gce-compute-image-packages, that ensure that
  the Ubuntu images published to GCE run properly on their platform.

  Cloud platforms evolve at a rate that can't be handled in six-month
  increments, and they will often develop features that they would like
  to be available to customers who don't want to upgrade from earlier
  Ubuntu releases. As such, updating gce-compute-image-packages to more
  recent upstream releases is required within all Ubuntu releases, so
  they continue to function properly in their environment.

  With this release we also add a new binary package to the suite -
  google-compute-engine-oslogin which is for a future feature of using
  OS Login on GCE VM instances.

  [Test Case]

  When a new version of gce-compute-image-packages is uploaded to
  -proposed, the following will be done:

   * an image based on -proposed will be built for GCE and published to the 
ubuntu-os-cloud-devel project
   * the CPC team will write new automated tests to cover new testable 
functionality (if any) in the new package
   * the automated testing that the CPC team normally runs against GCE images 
before they are published will be run against the -proposed image
   * the GCE team will be asked to validate that the new package addresses the 
issues it is expected to address, and that the image passes their internal 
image validation.

  If all the testing indicates that the image containing the new package
  is acceptable, verification will be considered to be done.

  [Other Information]

  This bug is used for tracking of releasing the new upstream version
  for all supported series, as per the approved policy mentioned in the
  following MRE:

  https://wiki.ubuntu.com/gce-compute-image-packages-Updates

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1722356/+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 1726810] Re: Update google compute-image-packages to 20171019

[Launchpad Bug Tracker]

This bug was fixed in the package gce-compute-image-packages -
20171019+dfsg1-0ubuntu1~17.04.0

---
gce-compute-image-packages (20171019+dfsg1-0ubuntu1~17.04.0) zesty; 
urgency=medium

  [ Balint Reczey ]
  * New upstream version 20171019+dfsg1 (LP: #1726810)
- Add status option for google_oslogin_control
- OS Login activation via the accounts daemon
  * Tidy up d/control with the help of cme fix dpkg-control
  * Update symlink to shared library with updated minor version
  * Change package priority to optional from extra
  * Add debhelper token to prerm

  [ Zach Marano from Google Cloud Team ]
  * Depend on chrony | ntp | time-daemon instead of just ntp
  * Move all service activation handling to
gce-compute-image-packages.{postinst|prerm}
  * Make google-compute-engine depend on google-compute-engine-oslogin

  [ Łukasz 'sil2100' Zemczak ]
  * Backport to zesty.

 -- Balint Reczey   Tue, 24 Oct 2017 16:35:46 +0200

** Changed in: gce-compute-image-packages (Ubuntu Zesty)
   Status: Fix Committed => Fix Released

** Changed in: gce-compute-image-packages (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  Update google compute-image-packages to 20171019

Status in gce-compute-image-packages package in Ubuntu:
  Fix Released
Status in gce-compute-image-packages source package in Trusty:
  Fix Released
Status in gce-compute-image-packages source package in Xenial:
  Fix Released
Status in gce-compute-image-packages source package in Zesty:
  Fix Released
Status in gce-compute-image-packages source package in Artful:
  Fix Released

Bug description:
  [Impact]

  compute-image-packages is provided by Google for installation within
  guests that run on Google Compute Engine. It is a collection of tools
  and daemons, packaged as gce-compute-image-packages, that ensure that
  the Ubuntu images published to GCE run properly on their platform.

  Cloud platforms evolve at a rate that can't be handled in six-month
  increments, and they will often develop features that they would like
  to be available to customers who don't want to upgrade from earlier
  Ubuntu releases. As such, updating gce-compute-image-packages to more
  recent upstream releases is required within all Ubuntu releases, so
  they continue to function properly in their environment.

  With this release we also add a new binary package to the suite -
  google-compute-engine-oslogin which is for a future feature of using
  OS Login on GCE VM instances.

  [Test Case]

  When a new version of gce-compute-image-packages is uploaded to
  -proposed, the following will be done:

   * an image based on -proposed will be built for GCE and published to the 
ubuntu-os-cloud-devel project
   * the CPC team will write new automated tests to cover new testable 
functionality (if any) in the new package
   * the automated testing that the CPC team normally runs against GCE images 
before they are published will be run against the -proposed image
   * the GCE team will be asked to validate that the new package addresses the 
issues it is expected to address, and that the image passes their internal 
image validation.

  If all the testing indicates that the image containing the new package
  is acceptable, verification will be considered to be done.

  [Other Information]

  This bug is used for tracking of releasing the new upstream version
  for all supported series, as per the approved policy mentioned in the
  following MRE:

  https://wiki.ubuntu.com/gce-compute-image-packages-Updates

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1726810/+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 1722356] Re: Update google compute-image-packages to 20171006

[Launchpad Bug Tracker]

This bug was fixed in the package gce-compute-image-packages -
20171019+dfsg1-0ubuntu1~17.04.0

---
gce-compute-image-packages (20171019+dfsg1-0ubuntu1~17.04.0) zesty; 
urgency=medium

  [ Balint Reczey ]
  * New upstream version 20171019+dfsg1 (LP: #1726810)
- Add status option for google_oslogin_control
- OS Login activation via the accounts daemon
  * Tidy up d/control with the help of cme fix dpkg-control
  * Update symlink to shared library with updated minor version
  * Change package priority to optional from extra
  * Add debhelper token to prerm

  [ Zach Marano from Google Cloud Team ]
  * Depend on chrony | ntp | time-daemon instead of just ntp
  * Move all service activation handling to
gce-compute-image-packages.{postinst|prerm}
  * Make google-compute-engine depend on google-compute-engine-oslogin

  [ Łukasz 'sil2100' Zemczak ]
  * Backport to zesty.

 -- Balint Reczey   Tue, 24 Oct 2017 16:35:46 +0200

** Changed in: gce-compute-image-packages (Ubuntu Zesty)
   Status: Fix Committed => Fix Released

** Changed in: gce-compute-image-packages (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
   Update google compute-image-packages to 20171006

Status in gce-compute-image-packages package in Ubuntu:
  Fix Released
Status in gce-compute-image-packages source package in Trusty:
  Fix Released
Status in gce-compute-image-packages source package in Xenial:
  Fix Released
Status in gce-compute-image-packages source package in Zesty:
  Fix Released

Bug description:
  [Impact]

  compute-image-packages is provided by Google for installation within
  guests that run on Google Compute Engine. It is a collection of tools
  and daemons, packaged as gce-compute-image-packages, that ensure that
  the Ubuntu images published to GCE run properly on their platform.

  Cloud platforms evolve at a rate that can't be handled in six-month
  increments, and they will often develop features that they would like
  to be available to customers who don't want to upgrade from earlier
  Ubuntu releases. As such, updating gce-compute-image-packages to more
  recent upstream releases is required within all Ubuntu releases, so
  they continue to function properly in their environment.

  With this release we also add a new binary package to the suite -
  google-compute-engine-oslogin which is for a future feature of using
  OS Login on GCE VM instances.

  [Test Case]

  When a new version of gce-compute-image-packages is uploaded to
  -proposed, the following will be done:

   * an image based on -proposed will be built for GCE and published to the 
ubuntu-os-cloud-devel project
   * the CPC team will write new automated tests to cover new testable 
functionality (if any) in the new package
   * the automated testing that the CPC team normally runs against GCE images 
before they are published will be run against the -proposed image
   * the GCE team will be asked to validate that the new package addresses the 
issues it is expected to address, and that the image passes their internal 
image validation.

  If all the testing indicates that the image containing the new package
  is acceptable, verification will be considered to be done.

  [Other Information]

  This bug is used for tracking of releasing the new upstream version
  for all supported series, as per the approved policy mentioned in the
  following MRE:

  https://wiki.ubuntu.com/gce-compute-image-packages-Updates

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1722356/+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 1726810] Re: Update google compute-image-packages to 20171019

[Launchpad Bug Tracker]

This bug was fixed in the package gce-compute-image-packages -
20171019+dfsg1-0ubuntu1~16.04.0

---
gce-compute-image-packages (20171019+dfsg1-0ubuntu1~16.04.0) xenial; 
urgency=medium

  [ Balint Reczey ]
  * New upstream version 20171019+dfsg1 (LP: #1726810)
- Add status option for google_oslogin_control
- OS Login activation via the accounts daemon
  * Tidy up d/control with the help of cme fix dpkg-control
  * Update symlink to shared library with updated minor version
  * Change package priority to optional from extra
  * Add debhelper token to prerm

  [ Zach Marano from Google Cloud Team ]
  * Depend on chrony | ntp | time-daemon instead of just ntp
  * Move all service activation handling to
gce-compute-image-packages.{postinst|prerm}
  * Make google-compute-engine depend on google-compute-engine-oslogin

  [ Łukasz 'sil2100' Zemczak ]
  * Backport to xenial.

 -- Balint Reczey   Tue, 24 Oct 2017 16:35:46 +0200

** Changed in: gce-compute-image-packages (Ubuntu Trusty)
   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/1726810

Title:
  Update google compute-image-packages to 20171019

Status in gce-compute-image-packages package in Ubuntu:
  Fix Released
Status in gce-compute-image-packages source package in Trusty:
  Fix Released
Status in gce-compute-image-packages source package in Xenial:
  Fix Released
Status in gce-compute-image-packages source package in Zesty:
  Fix Released
Status in gce-compute-image-packages source package in Artful:
  Fix Released

Bug description:
  [Impact]

  compute-image-packages is provided by Google for installation within
  guests that run on Google Compute Engine. It is a collection of tools
  and daemons, packaged as gce-compute-image-packages, that ensure that
  the Ubuntu images published to GCE run properly on their platform.

  Cloud platforms evolve at a rate that can't be handled in six-month
  increments, and they will often develop features that they would like
  to be available to customers who don't want to upgrade from earlier
  Ubuntu releases. As such, updating gce-compute-image-packages to more
  recent upstream releases is required within all Ubuntu releases, so
  they continue to function properly in their environment.

  With this release we also add a new binary package to the suite -
  google-compute-engine-oslogin which is for a future feature of using
  OS Login on GCE VM instances.

  [Test Case]

  When a new version of gce-compute-image-packages is uploaded to
  -proposed, the following will be done:

   * an image based on -proposed will be built for GCE and published to the 
ubuntu-os-cloud-devel project
   * the CPC team will write new automated tests to cover new testable 
functionality (if any) in the new package
   * the automated testing that the CPC team normally runs against GCE images 
before they are published will be run against the -proposed image
   * the GCE team will be asked to validate that the new package addresses the 
issues it is expected to address, and that the image passes their internal 
image validation.

  If all the testing indicates that the image containing the new package
  is acceptable, verification will be considered to be done.

  [Other Information]

  This bug is used for tracking of releasing the new upstream version
  for all supported series, as per the approved policy mentioned in the
  following MRE:

  https://wiki.ubuntu.com/gce-compute-image-packages-Updates

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1726810/+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 1726810] Re: Update google compute-image-packages to 20171019

[Launchpad Bug Tracker]

This bug was fixed in the package gce-compute-image-packages -
20171019+dfsg1-0ubuntu1

---
gce-compute-image-packages (20171019+dfsg1-0ubuntu1) artful; urgency=medium

  [ Balint Reczey ]
  * New upstream version 20171019+dfsg1 (LP: #1726810)
- Add status option for google_oslogin_control
- OS Login activation via the accounts daemon
  * Tidy up d/control with the help of cme fix dpkg-control
  * Update symlink to shared library with updated minor version
  * Change package priority to optional from extra
  * Add debhelper token to prerm

  [ Zach Marano from Google Cloud Team ]
  * Depend on chrony | ntp | time-daemon instead of just ntp
  * Move all service activation handling to
gce-compute-image-packages.{postinst|prerm}
  * Make google-compute-engine depend on google-compute-engine-oslogin

 -- Balint Reczey   Tue, 24 Oct 2017 16:35:46 +0200

** Changed in: gce-compute-image-packages (Ubuntu Artful)
   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/1726810

Title:
  Update google compute-image-packages to 20171019

Status in gce-compute-image-packages package in Ubuntu:
  Fix Released
Status in gce-compute-image-packages source package in Trusty:
  Fix Released
Status in gce-compute-image-packages source package in Xenial:
  Fix Released
Status in gce-compute-image-packages source package in Zesty:
  Fix Released
Status in gce-compute-image-packages source package in Artful:
  Fix Released

Bug description:
  [Impact]

  compute-image-packages is provided by Google for installation within
  guests that run on Google Compute Engine. It is a collection of tools
  and daemons, packaged as gce-compute-image-packages, that ensure that
  the Ubuntu images published to GCE run properly on their platform.

  Cloud platforms evolve at a rate that can't be handled in six-month
  increments, and they will often develop features that they would like
  to be available to customers who don't want to upgrade from earlier
  Ubuntu releases. As such, updating gce-compute-image-packages to more
  recent upstream releases is required within all Ubuntu releases, so
  they continue to function properly in their environment.

  With this release we also add a new binary package to the suite -
  google-compute-engine-oslogin which is for a future feature of using
  OS Login on GCE VM instances.

  [Test Case]

  When a new version of gce-compute-image-packages is uploaded to
  -proposed, the following will be done:

   * an image based on -proposed will be built for GCE and published to the 
ubuntu-os-cloud-devel project
   * the CPC team will write new automated tests to cover new testable 
functionality (if any) in the new package
   * the automated testing that the CPC team normally runs against GCE images 
before they are published will be run against the -proposed image
   * the GCE team will be asked to validate that the new package addresses the 
issues it is expected to address, and that the image passes their internal 
image validation.

  If all the testing indicates that the image containing the new package
  is acceptable, verification will be considered to be done.

  [Other Information]

  This bug is used for tracking of releasing the new upstream version
  for all supported series, as per the approved policy mentioned in the
  following MRE:

  https://wiki.ubuntu.com/gce-compute-image-packages-Updates

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1726810/+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 1729278] Re: linux-raspi2: 4.4.0-1077.85 -proposed tracker

[Po-Hsu Lin]

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

** Changed in: kernel-sru-workflow/regression-testing
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin 
(cypressyew)

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

Title:
  linux-raspi2: 4.4.0-1077.85 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
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 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:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1729273
  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/1729278/+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 1729279] Re: linux-snapdragon: 4.4.0-1079.84 -proposed tracker

[Po-Hsu Lin]

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

** Changed in: kernel-sru-workflow/regression-testing
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin 
(cypressyew)

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

Title:
  linux-snapdragon: 4.4.0-1079.84 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
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 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:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-snapdragon package in Ubuntu:
  Invalid
Status in linux-snapdragon source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1729273
  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/1729279/+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