[Group.of.nepali.translators] [Bug 2024637] Re: apparmor.service tries to load snapd generated apparmor profiles but fails

2023-06-22 Thread Alex Murray
** Also affects: snapd (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/2024637

Title:
  apparmor.service tries to load snapd generated apparmor profiles but
  fails

Status in apparmor package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  New
Status in apparmor source package in Xenial:
  New
Status in snapd source package in Xenial:
  New
Status in apparmor source package in Bionic:
  New
Status in snapd source package in Bionic:
  New

Bug description:
  As of snapd 2.60, when installed as a snap, snapd includes its own
  vendored apparmor_parser and configuration. As such, it generates
  profiles using newer apparmor features than the system installed
  apparmor may support.

  This is seen as a failure to load the apparmor.service at boot once
  this new snapd snap with the vendored apparmor is installed:

  root@sec-bionic-amd64:~# systemctl status apparmor
  ● apparmor.service - AppArmor initialization
 Loaded: loaded (/lib/systemd/system/apparmor.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: exit-code) since Thu 2023-06-22 06:51:32 UTC; 8min 
ago
   Docs: man:apparmor(7)
 http://wiki.apparmor.net/
   Main PID: 1590 (code=exited, status=123)

  Jun 22 06:51:32 sec-bionic-amd64 apparmor[1590]: AppArmor parser error for 
/etc/apparmor.d/usr.lib.snapd.snap-confine.real in 
/var/lib/snapd/apparmor/snap-confine/cap-bpf at line 2: Invalid capability bpf.
  Jun 22 06:51:32 sec-bionic-amd64 apparmor[1590]: Skipping profile in 
/etc/apparmor.d/disable: usr.sbin.rsyslogd
  Jun 22 06:51:32 sec-bionic-amd64 apparmor[1590]: AppArmor parser error for 
/etc/apparmor.d/usr.lib.snapd.snap-confine.real in 
/var/lib/snapd/apparmor/snap-confine/cap-bpf at line 2: Invalid capability bpf.
  Jun 22 06:51:32 sec-bionic-amd64 apparmor[1590]: Skipping profile in 
/etc/apparmor.d/disable: usr.sbin.rsyslogd
  Jun 22 06:51:32 sec-bionic-amd64 apparmor[1590]: AppArmor parser error for 
/var/lib/snapd/apparmor/profiles/snap-confine.snapd.19567 in 
/var/lib/snapd/apparmor/snap-confine/cap-bpf at line 2: Invalid capability bpf.
  Jun 22 06:51:32 sec-bionic-amd64 apparmor[1590]: AppArmor parser error for 
/var/lib/snapd/apparmor/profiles/snap-confine.snapd.19567 in 
/var/lib/snapd/apparmor/snap-confine/cap-bpf at line 2: Invalid capability bpf.
  Jun 22 06:51:32 sec-bionic-amd64 apparmor[1590]:...fail!
  Jun 22 06:51:32 sec-bionic-amd64 systemd[1]: apparmor.service: Main process 
exited, code=exited, status=123/n/a
  Jun 22 06:51:32 sec-bionic-amd64 systemd[1]: apparmor.service: Failed with 
result 'exit-code'.
  Jun 22 06:51:32 sec-bionic-amd64 systemd[1]: Failed to start AppArmor 
initialization.

  root@sec-bionic-amd64:~# snap version
  snap2.60
  snapd   2.60
  series  16
  ubuntu  18.04
  kernel  4.15.0-212-generic
  root@sec-bionic-amd64:~# snap debug sandbox-features --required \
  apparmor:parser:snapd-internal && echo snapd has internal vendored apparmor
  snapd has internal vendored apparmor

  
  In LP: #1871148 apparmor was updated in focal+ to stop loading apparmor 
profiles generated by snapd as since snapd 2.44.3 it has shipped the 
snapd.apparmor.service unit which loads its apparmor profiles on boot.

  apparmor in bionic and xenial should be updated to stop loading snapd
  generated apparmor profiles and instead leave this up to
  snapd.apparmor.service.


  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apparmor 2.12-4ubuntu5.1
  ProcVersionSignature: Ubuntu 4.15.0-212.223-generic 4.15.18
  Uname: Linux 4.15.0-212-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.29
  Architecture: amd64
  Date: Thu Jun 22 06:52:02 2023
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-212-generic 
root=UUID=da79cdd1-11be-4719-8482-46ce30623eaa ro quiet splash console=tty1 
console=ttyS0 vt.handoff=1
  PstreeP: Error: [Errno 2] No such file or directory: '/usr/bin/pstree': 
'/usr/bin/pstree'
  SourcePackage: apparmor
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2024637/+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 2024637] Re: apparmor.service tries to load snapd generated apparmor profiles but fails

2023-06-22 Thread Alex Murray
** Also affects: apparmor (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: apparmor (Ubuntu Bionic)
   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/2024637

Title:
  apparmor.service tries to load snapd generated apparmor profiles but
  fails

Status in apparmor package in Ubuntu:
  New
Status in apparmor source package in Xenial:
  New
Status in apparmor source package in Bionic:
  New

Bug description:
  As of snapd 2.60, when installed as a snap, snapd includes its own
  vendored apparmor_parser and configuration. As such, it generates
  profiles using newer apparmor features than the system installed
  apparmor may support.

  This is seen as a failure to load the apparmor.service at boot once
  this new snapd snap with the vendored apparmor is installed:

  root@sec-bionic-amd64:~# systemctl status apparmor
  ● apparmor.service - AppArmor initialization
 Loaded: loaded (/lib/systemd/system/apparmor.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: exit-code) since Thu 2023-06-22 06:51:32 UTC; 8min 
ago
   Docs: man:apparmor(7)
 http://wiki.apparmor.net/
   Main PID: 1590 (code=exited, status=123)

  Jun 22 06:51:32 sec-bionic-amd64 apparmor[1590]: AppArmor parser error for 
/etc/apparmor.d/usr.lib.snapd.snap-confine.real in 
/var/lib/snapd/apparmor/snap-confine/cap-bpf at line 2: Invalid capability bpf.
  Jun 22 06:51:32 sec-bionic-amd64 apparmor[1590]: Skipping profile in 
/etc/apparmor.d/disable: usr.sbin.rsyslogd
  Jun 22 06:51:32 sec-bionic-amd64 apparmor[1590]: AppArmor parser error for 
/etc/apparmor.d/usr.lib.snapd.snap-confine.real in 
/var/lib/snapd/apparmor/snap-confine/cap-bpf at line 2: Invalid capability bpf.
  Jun 22 06:51:32 sec-bionic-amd64 apparmor[1590]: Skipping profile in 
/etc/apparmor.d/disable: usr.sbin.rsyslogd
  Jun 22 06:51:32 sec-bionic-amd64 apparmor[1590]: AppArmor parser error for 
/var/lib/snapd/apparmor/profiles/snap-confine.snapd.19567 in 
/var/lib/snapd/apparmor/snap-confine/cap-bpf at line 2: Invalid capability bpf.
  Jun 22 06:51:32 sec-bionic-amd64 apparmor[1590]: AppArmor parser error for 
/var/lib/snapd/apparmor/profiles/snap-confine.snapd.19567 in 
/var/lib/snapd/apparmor/snap-confine/cap-bpf at line 2: Invalid capability bpf.
  Jun 22 06:51:32 sec-bionic-amd64 apparmor[1590]:...fail!
  Jun 22 06:51:32 sec-bionic-amd64 systemd[1]: apparmor.service: Main process 
exited, code=exited, status=123/n/a
  Jun 22 06:51:32 sec-bionic-amd64 systemd[1]: apparmor.service: Failed with 
result 'exit-code'.
  Jun 22 06:51:32 sec-bionic-amd64 systemd[1]: Failed to start AppArmor 
initialization.

  root@sec-bionic-amd64:~# snap version
  snap2.60
  snapd   2.60
  series  16
  ubuntu  18.04
  kernel  4.15.0-212-generic
  root@sec-bionic-amd64:~# snap debug sandbox-features --required \
  apparmor:parser:snapd-internal && echo snapd has internal vendored apparmor
  snapd has internal vendored apparmor

  
  In LP: #1871148 apparmor was updated in focal+ to stop loading apparmor 
profiles generated by snapd as since snapd 2.44.3 it has shipped the 
snapd.apparmor.service unit which loads its apparmor profiles on boot.

  apparmor in bionic and xenial should be updated to stop loading snapd
  generated apparmor profiles and instead leave this up to
  snapd.apparmor.service.


  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apparmor 2.12-4ubuntu5.1
  ProcVersionSignature: Ubuntu 4.15.0-212.223-generic 4.15.18
  Uname: Linux 4.15.0-212-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.29
  Architecture: amd64
  Date: Thu Jun 22 06:52:02 2023
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-212-generic 
root=UUID=da79cdd1-11be-4719-8482-46ce30623eaa ro quiet splash console=tty1 
console=ttyS0 vt.handoff=1
  PstreeP: Error: [Errno 2] No such file or directory: '/usr/bin/pstree': 
'/usr/bin/pstree'
  SourcePackage: apparmor
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2024637/+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 1891810] Re: Missing openat2 syscall, causes problems for fuse-overlayfs in nspawn containers

2021-02-28 Thread Alex Murray
** Also affects: libseccomp (Ubuntu Hirsute)
   Importance: Undecided
 Assignee: Alex Murray (alexmurray)
   Status: New

** Changed in: libseccomp (Ubuntu Hirsute)
   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/1891810

Title:
  Missing openat2 syscall, causes problems for fuse-overlayfs in nspawn
  containers

Status in libseccomp package in Ubuntu:
  Fix Released
Status in libseccomp source package in Xenial:
  New
Status in libseccomp source package in Bionic:
  New
Status in libseccomp source package in Focal:
  New
Status in libseccomp source package in Groovy:
  New
Status in libseccomp source package in Hirsute:
  Fix Released

Bug description:
  The version of libseccomp2 in bionic does not know about the openat2
  syscall.

  In my particular usecase, I was trying to run podman/buildah in an
  nspawn container, using fuse-overlayfs. This leads to peculiar failure
  modes as described in this issue:

  https://github.com/containers/fuse-overlayfs/issues/220

  This could well cause other problems, previously issues like that have
  affected snapd, etc.

  Backporting the master branch of libseccomp fixed this for me, but for
  an SRU a cherrypick of
  
https://github.com/seccomp/libseccomp/commit/b3206ad5645dceda89538ea8acc984078ab697ab
  might be sufficient...

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libseccomp2 2.4.3-1ubuntu3.18.04.3
  ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.16
  Architecture: amd64
  Date: Sun Aug 16 17:35:09 2020
  Dependencies:
   gcc-8-base 8.4.0-1ubuntu1~18.04
   libc6 2.27-3ubuntu1.2
   libgcc1 1:8.4.0-1ubuntu1~18.04
  ProcEnviron:
   TERM=screen.xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: libseccomp
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1891810/+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 1885248] Re: Update intel-microcode to latest upstream release 20200616 to fix possible regression in 06-5e-03/0x000506e3

2020-11-11 Thread Alex Murray
This is now obsolete - we recently updated intel-microcode to the most
recent 20201110 release.

** Changed in: intel-microcode (Ubuntu)
   Status: New => Fix Released

** Changed in: intel-microcode (Ubuntu Xenial)
   Status: New => Fix Released

** Changed in: intel-microcode (Ubuntu Bionic)
   Status: New => Fix Released

** Changed in: intel-microcode (Ubuntu Focal)
   Status: New => Fix Released

** Changed in: intel-microcode (Ubuntu Groovy)
   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/1885248

Title:
  Update intel-microcode to latest upstream release 20200616 to fix
  possible regression in 06-5e-03/0x000506e3

Status in OEM Priority Project:
  New
Status in intel-microcode package in Ubuntu:
  Fix Released
Status in intel-microcode source package in Xenial:
  Fix Released
Status in intel-microcode source package in Bionic:
  Fix Released
Status in intel-microcode source package in Eoan:
  Won't Fix
Status in intel-microcode source package in Focal:
  Fix Released
Status in intel-microcode source package in Groovy:
  Fix Released

Bug description:
  As a result of https://bugs.launchpad.net/ubuntu/+source/intel-
  microcode/+bug/1882890 the microcode for 06-4e-03 was reverted from
  the most recent intel-microcode release to the previous one - Intel
  has subsequently released a new upstream release
  https://github.com/intel/Intel-Linux-Processor-Microcode-Data-
  Files/releases/tag/microcode-20200616 which includes this revert *as
  well as a revert for the 06-5e-03/0x000506e3 microcode too*. This
  should also be updated in Ubuntu to ensure we do not suffer any
  unexpected regressions on these platforms too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1885248/+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 1885248] [NEW] Update intel-microcode to latest upstream release 20200616 to fix possible regression in 06-5e-03/0x000506e3

2020-06-26 Thread Alex Murray
*** This bug is a security vulnerability ***

Public security bug reported:

As a result of https://bugs.launchpad.net/ubuntu/+source/intel-
microcode/+bug/1882890 the microcode for 06-4e-03 was reverted from the
most recent intel-microcode release to the previous one - Intel has
subsequently released a new upstream release https://github.com/intel
/Intel-Linux-Processor-Microcode-Data-
Files/releases/tag/microcode-20200616 which includes this revert *as
well as a revert for the 06-5e-03/0x000506e3 microcode too*. This should
also be updated in Ubuntu to ensure we do not suffer any unexpected
regressions on these platforms too.

** Affects: intel-microcode (Ubuntu)
 Importance: Undecided
 Assignee: Ubuntu Security Team (ubuntu-security)
 Status: New

** Affects: intel-microcode (Ubuntu Xenial)
 Importance: Undecided
 Status: New

** Affects: intel-microcode (Ubuntu Bionic)
 Importance: Undecided
 Status: New

** Affects: intel-microcode (Ubuntu Eoan)
 Importance: Undecided
 Status: New

** Affects: intel-microcode (Ubuntu Focal)
 Importance: Undecided
 Status: New

** Affects: intel-microcode (Ubuntu Groovy)
 Importance: Undecided
 Assignee: Ubuntu Security Team (ubuntu-security)
 Status: New

** Also affects: intel-microcode (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: intel-microcode (Ubuntu Groovy)
   Importance: Undecided
 Assignee: Ubuntu Security Team (ubuntu-security)
   Status: New

** Also affects: intel-microcode (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: intel-microcode (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: intel-microcode (Ubuntu Eoan)
   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/1885248

Title:
  Update intel-microcode to latest upstream release 20200616 to fix
  possible regression in 06-5e-03/0x000506e3

Status in intel-microcode package in Ubuntu:
  New
Status in intel-microcode source package in Xenial:
  New
Status in intel-microcode source package in Bionic:
  New
Status in intel-microcode source package in Eoan:
  New
Status in intel-microcode source package in Focal:
  New
Status in intel-microcode source package in Groovy:
  New

Bug description:
  As a result of https://bugs.launchpad.net/ubuntu/+source/intel-
  microcode/+bug/1882890 the microcode for 06-4e-03 was reverted from
  the most recent intel-microcode release to the previous one - Intel
  has subsequently released a new upstream release
  https://github.com/intel/Intel-Linux-Processor-Microcode-Data-
  Files/releases/tag/microcode-20200616 which includes this revert *as
  well as a revert for the 06-5e-03/0x000506e3 microcode too*. This
  should also be updated in Ubuntu to ensure we do not suffer any
  unexpected regressions on these platforms too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1885248/+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 1876055] Re: SRU: Backport 2.4.3-1ubuntu3 from groovy to focal/eoan/bionic/xenial for newer syscalls for core20 base and test suite robustness

2020-06-14 Thread Alex Murray
** Also affects: systemd (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: systemd (Ubuntu Xenial)

** No longer affects: systemd (Ubuntu Bionic)

** No longer affects: systemd (Ubuntu Focal)

** No longer affects: systemd (Ubuntu Groovy)

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

Title:
  SRU: Backport 2.4.3-1ubuntu3 from groovy to focal/eoan/bionic/xenial
  for newer syscalls for core20 base and test suite robustness

Status in libseccomp package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  New
Status in libseccomp source package in Xenial:
  Fix Committed
Status in libseccomp source package in Bionic:
  Fix Committed
Status in libseccomp source package in Eoan:
  Fix Committed
Status in systemd source package in Eoan:
  New
Status in libseccomp source package in Focal:
  Fix Committed
Status in libseccomp source package in Groovy:
  Fix Released

Bug description:
  [Impact]

  The combination of snap-confine and snap-seccomp from snapd uses
  libseccomp to filter various system calls for confinement. The current
  version in eoan/bionic/xenial (2.4.1) is missing knowledge of various
  system calls for various architectures. As such this causes strange
  issues like python snaps segfaulting
  (https://github.com/snapcore/core20/issues/48) or the inadvertent
  denial of system calls which should be permitted by the base policy
  (https://forum.snapcraft.io/t/getrlimit-blocked-by-seccomp-on-focal-
  arm64/17237).

  libseccomp in groovy is using the latest upstream base release (2.4.3)
  plus it includes a patch to add some missing aarch64 system calls
  (https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1877633).

  SRUing this version back to older stable releases allows libseccomp to
  operate correctly on all supported architectures.

  
  Included as part of this SRU are test-suite reliability improvements - 
currently the xenial libseccomp package overrides test-suite failures at build 
time to ignore failures. This masks the fact that on ppc64el and s390x there 
are currently test suite failures at build time for xenial - these failures 
occur since libseccomp now includes knowledge of system calls for these 
architectures but which the linux-libc-dev package for xenial does not actually 
define (since this is based of the 4.4 kernel in xenial whereas libseccomp 
2.4.1 in xenial has knowledge of all system calls up to 5.4). 

  In this SRU I have instead fixed the test suite failures for xenial by
  including a local (test-suite specific) set of architecture specific
  kernel headers from the linux-libc-dev in focal for all releases.
  These are just the headers which define the system call numbers for
  each architecture *and* these are added to tests/include/$ARCH in the
  source package (and tests/Makefile.am is then updated to include these
  new headers only).  As such this ensures the actual build of
  libseccomp or any of the tools does not reference these headers. This
  allows the test suite in libseccomp to then be aware of theses system
  calls and so all unit tests for all architectures now pass.

  In any future updates for libseccomp to add new system calls, we can
  then similarly update these local headers to ensure the unit tests
  continue to work as expected.

  
  [Test Case]

  libseccomp includes a significant unit test suite that is run during
  the build and as part of autopkgtests. To verify the new aarch64
  system calls are resolved as expected the scmp_sys_resolver command
  can be used as well:

  $ scmp_sys_resolver -a aarch64 getrlimit
  163

  (whereas in the current version in focal this returns -10180 as
  libseccomp was not aware of this system-call at compile-time).

  As part of this SRU, the test suite in libseccomp has been patched to
  include a local copy of the architecture-specific kernel headers from
  the 5.4 kernel in focal *for all releases*, so that all system calls
  which are defined for the 5.4 kernel are known about *for the
  libseccomp test suite*. This allows all unit tests to pass on older
  releases as well and defaults the build to fail on unit test failures
  (whereas currently in xenial this has been overridden to ignore
  failures).

  
  [Regression Potential]

  This has a low regression potential due to significant testing with
  many packages that depend on libseccomp (lxc, qemu, snapd, apt, man
  etc) and none have shown any regression using this new version. The
  re-enablement of build failure on test failure at build time also
  ensures that we can reliably detect FTBFS issues in the future.

  No symbols have been removed (or added) with this update in version so
  there is no chance of regression due to ABI change etc. In the past,
  the security team has performed more significant version upgrades for
  

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

2019-11-29 Thread Alex Murray
** Changed in: kernel-sru-workflow/security-signoff
   Status: In Progress => Fix Released

** Changed in: kernel-sru-workflow/security-signoff
 Assignee: Steve Beattie (sbeattie) => Alex Murray (alexmurray)

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

Title:
  xenial/linux-hwe: 4.15.0-72.81~16.04.1 -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:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow 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:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-hwe package in Ubuntu:
  Invalid
Status in linux-hwe source package in Xenial:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1854027
  packages:
main: linux-hwe
meta: linux-meta-hwe
signed: linux-signed-hwe
  phase: Testing
  phase-changed: Wednesday, 27. November 2019 12:16 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress
  trackers:
xenial/linux-deeplens: bug 1852287
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854026/+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 1854030] Re: xenial/linux-aws-hwe: 4.15.0-1056.58~16.04.1 -proposed tracker

2019-11-29 Thread Alex Murray
** Changed in: kernel-sru-workflow/security-signoff
   Status: In Progress => Fix Released

** Changed in: kernel-sru-workflow/security-signoff
 Assignee: Steve Beattie (sbeattie) => Alex Murray (alexmurray)

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

Title:
  xenial/linux-aws-hwe: 4.15.0-1056.58~16.04.1 -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:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-aws-hwe package in Ubuntu:
  Invalid
Status in linux-aws-hwe source package in Xenial:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1854029
  packages:
main: linux-aws-hwe
meta: linux-meta-aws-hwe
  phase: Testing
  phase-changed: Wednesday, 27. November 2019 11:07 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
verification-testing: Ongoing -- testing in progress
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854030/+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 1852306] Re: xenial/linux: 4.4.0-170.199 -proposed tracker

2019-11-29 Thread Alex Murray
** Changed in: kernel-sru-workflow/security-signoff
   Status: In Progress => Fix Released

** Changed in: kernel-sru-workflow/security-signoff
 Assignee: Steve Beattie (sbeattie) => Alex Murray (alexmurray)

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

Title:
  xenial/linux: 4.4.0-170.199 -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:
  Incomplete
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:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  packages:
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Thursday, 14. November 2019 18:50 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Stalled -- testing FAILED
  trackers:
trusty/linux-aws: bug 1852304
trusty/linux-lts-xenial: bug 1852305
xenial/linux-aws: bug 1852296
xenial/linux-cascade: bug 1852297
xenial/linux-fips: bug 1852303
xenial/linux-kvm: bug 1852298
xenial/linux-raspi2: bug 1852300
xenial/linux-snapdragon: bug 1852302
xenial/linux/caracalla-kernel: bug 1852291
xenial/linux/pc-kernel: bug 1852292
xenial/linux/stlouis-kernel: bug 1852293
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852306/+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 1852302] Re: xenial/linux-snapdragon: 4.4.0-1130.138 -proposed tracker

2019-11-29 Thread Alex Murray
** Changed in: kernel-sru-workflow/security-signoff
   Status: In Progress => Fix Released

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

Title:
  xenial/linux-snapdragon: 4.4.0-1130.138 -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:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  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:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-snapdragon package in Ubuntu:
  Invalid
Status in linux-snapdragon source package in Xenial:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1852306
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
  phase: Holding before Promote to Updates
  phase-changed: Friday, 29. November 2019 10:21 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Holding -- cycle not ready to release
  trackers:
xenial/linux-snapdragon/dragonboard-kernel: bug 1852301
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852302/+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 1852300] Re: xenial/linux-raspi2: 4.4.0-1126.135 -proposed tracker

2019-11-29 Thread Alex Murray
** Changed in: kernel-sru-workflow/security-signoff
   Status: In Progress => Fix Released

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

Title:
  xenial/linux-raspi2: 4.4.0-1126.135 -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:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  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:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Xenial:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1852306
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Holding before Promote to Updates
  phase-changed: Friday, 29. November 2019 10:16 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Holding -- cycle not ready to release
  trackers:
xenial/linux-raspi2/pi2-kernel: bug 1852299
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852300/+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 1852298] Re: xenial/linux-kvm: 4.4.0-1063.70 -proposed tracker

2019-11-29 Thread Alex Murray
** Changed in: kernel-sru-workflow/security-signoff
   Status: In Progress => Fix Released

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

Title:
  xenial/linux-kvm: 4.4.0-1063.70 -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:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm source package in Xenial:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1852306
  packages:
main: linux-kvm
meta: linux-meta-kvm
  phase: Holding before Promote to Updates
  phase-changed: Friday, 29. November 2019 10:10 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Holding -- cycle not ready to release
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852298/+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 1852296] Re: xenial/linux-aws: 4.4.0-1099.110 -proposed tracker

2019-11-29 Thread Alex Murray
** Changed in: kernel-sru-workflow/security-signoff
   Status: In Progress => Fix Released

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

Title:
  xenial/linux-aws: 4.4.0-1099.110 -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:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1852306
  packages:
main: linux-aws
meta: linux-meta-aws
  phase: Holding before Promote to Updates
  phase-changed: Friday, 29. November 2019 10:10 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Holding -- cycle not ready to release
  trackers:
xenial/linux-aws/aws-kernel: bug 1852295
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852296/+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 1852285] Re: xenial/linux-gcp: 4.15.0-1050.53 -proposed tracker

2019-11-29 Thread Alex Murray
** Changed in: kernel-sru-workflow/security-signoff
   Status: In Progress => Fix Released

** Changed in: kernel-sru-workflow/security-signoff
 Assignee: Steve Beattie (sbeattie) => Alex Murray (alexmurray)

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

Title:
  xenial/linux-gcp: 4.15.0-1050.53 -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:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Xenial:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1854027
  packages:
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Testing
  phase-changed: Thursday, 14. November 2019 22:13 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
verification-testing: Ongoing -- testing in progress
  trackers:
xenial/linux-gcp/gcp-kernel: bug 1852283
xenial/linux-gcp/gke-kernel: bug 1852284
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852285/+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 1852275] Re: xenial/linux-oracle: 4.15.0-1030.33~16.04.1 -proposed tracker

2019-11-28 Thread Alex Murray
** Changed in: kernel-sru-workflow/security-signoff
   Status: In Progress => Fix Released

** Changed in: kernel-sru-workflow/security-signoff
 Assignee: Steve Beattie (sbeattie) => Alex Murray (alexmurray)

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

Title:
  xenial/linux-oracle: 4.15.0-1030.33~16.04.1 -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:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-oracle package in Ubuntu:
  Invalid
Status in linux-oracle source package in Xenial:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1852277
  packages:
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
  phase: Testing
  phase-changed: Wednesday, 20. November 2019 09:32 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
verification-testing: Ongoing -- testing in progress
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852275/+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 1852282] Re: xenial/linux-azure: 4.15.0-1064.69 -proposed tracker

2019-11-28 Thread Alex Murray
** Changed in: kernel-sru-workflow/security-signoff
   Status: In Progress => Fix Released

** Changed in: kernel-sru-workflow/security-signoff
 Assignee: Steve Beattie (sbeattie) => Alex Murray (alexmurray)

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

Title:
  xenial/linux-azure: 4.15.0-1064.69 -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:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Xenial:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1854027
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Monday, 25. November 2019 12:36 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
stakeholder-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
trusty/linux-azure: bug 1852281
xenial/linux-azure-edge: bug 1852280
xenial/linux-azure/azure-kernel: bug 1852279
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852282/+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 1834315] [NEW] Revert x86/vdso linker changes from #1830890 as this causes glibc 2.29-0ubuntu3 FTBFS on eoan

2019-06-26 Thread Alex Murray
Public bug reported:

[Impact]
As reported in #1833067 and 
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1830890/comments/7 some 
glibc testcases are still regressing on i386 after applying both the following 
commits:

commit 379d98ddf41344273d9718556f761420f4dc80b3
Author: Alistair Strachan 
Date: Fri Aug 3 10:39:31 2018 -0700

x86: vdso: Use $LD instead of $CC to link

commit cd01544a268ad8ee5b1dfe42c4393f1095f86879
Author: Alistair Strachan 
Date: Fri Dec 14 14:36:37 2018 -0800

x86/vdso: Pass --eh-frame-hdr to the linker


[Fix]
Revert both these patches to restore the original behaviour.

[Test]
ADT tests for glibc.

[Regression Potential]
Low. This restores the status quo before the original change to 
vdso/x86/Makefile to restore the original linker behaviour.

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

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

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

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

Title:
  Revert x86/vdso linker changes from #1830890 as this causes glibc
  2.29-0ubuntu3 FTBFS on eoan

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

Bug description:
  [Impact]
  As reported in #1833067 and 
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1830890/comments/7 some 
glibc testcases are still regressing on i386 after applying both the following 
commits:

  commit 379d98ddf41344273d9718556f761420f4dc80b3
  Author: Alistair Strachan 
  Date: Fri Aug 3 10:39:31 2018 -0700

  x86: vdso: Use $LD instead of $CC to link

  commit cd01544a268ad8ee5b1dfe42c4393f1095f86879
  Author: Alistair Strachan 
  Date: Fri Dec 14 14:36:37 2018 -0800

  x86/vdso: Pass --eh-frame-hdr to the linker

  
  [Fix]
  Revert both these patches to restore the original behaviour.

  [Test]
  ADT tests for glibc.

  [Regression Potential]
  Low. This restores the status quo before the original change to 
vdso/x86/Makefile to restore the original linker behaviour.

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