[Kernel-packages] [Bug 1836100] Re: Was able to migrate out of proposed despite breaking dkms

2019-07-10 Thread Steve Langasek
$ dpkg -l gcc | grep ^ii
ii  gcc4:8.3.0-1ubuntu3 amd64GNU C compiler
$ sudo apt install linux-headers-generic
[...]
$ sudo apt install openafs-modules-dkms
[...]
Building for 5.0.0-20-generic
Building initial module for 5.0.0-20-generic
Done.

openafs.ko:
Running module version sanity check.
modinfo: ERROR: missing module or filename.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/5.0.0-20-generic/updates/dkms/

depmod...

DKMS: install completed.
$ sudo apt purge openafs-modules-dkms
[...]
$ sudo apt install gcc
[...]
$ dpkg -l gcc | grep ^ii
ii  gcc4:9.1.0-1ubuntu4 amd64GNU C compiler
$ sudo apt install openafs-modules-dkms
[...]
Building for 5.0.0-20-generic
Building initial module for 5.0.0-20-generic
Error! Bad return status for module build on kernel: 5.0.0-20-generic (x86_64)
Consult /var/lib/dkms/openafs/1.8.2/build/make.log for more information.
dpkg: error processing package openafs-modules-dkms (--configure):
 installed openafs-modules-dkms package post-installation script subprocess 
returned error exit status 10
Errors were encountered while processing:
 openafs-modules-dkms
E: Sub-process /usr/bin/dpkg returned an error code (1)
$

This is a regression in buildability introduced *precisely* by the
change in the gcc metapackage.

** No longer affects: linux (Ubuntu)

** Changed in: auto-package-testing
   Status: Triaged => In Progress

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

Title:
  Was able to migrate out of proposed despite breaking dkms

Status in Auto Package Testing:
  In Progress

Bug description:
  The recent gcc update in eoan migrated out of proposed despite the
  fact that it was breaking dmks/nvidia users, could we have some sort
  of autopkgtest added to make sure that gcc gets blocked in proposed
  the next time we have a such situation?

  (see bug #1830961)

To manage notifications about this bug go to:
https://bugs.launchpad.net/auto-package-testing/+bug/1836100/+subscriptions

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


[Kernel-packages] [Bug 1836100] Re: Was able to migrate out of proposed despite breaking dkms

2019-07-10 Thread Matthias Klose
and your reasoning seems to be flawed.  The hardening flags were already
enabled in gcc-8 long before.

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

Title:
  Was able to migrate out of proposed despite breaking dkms

Status in Auto Package Testing:
  Triaged
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The recent gcc update in eoan migrated out of proposed despite the
  fact that it was breaking dmks/nvidia users, could we have some sort
  of autopkgtest added to make sure that gcc gets blocked in proposed
  the next time we have a such situation?

  (see bug #1830961)

To manage notifications about this bug go to:
https://bugs.launchpad.net/auto-package-testing/+bug/1836100/+subscriptions

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


[Kernel-packages] [Bug 1836100] Re: Was able to migrate out of proposed despite breaking dkms

2019-07-10 Thread Matthias Klose
I disagree.  user space migrations should not be blocked by kernel
changes.  We know that the kernel is sensible to compiler changes, so it
probably should build-depend on an explicit GCC version.  And no, we
should not block migrations on build failures, just for this case.  So
the kernel needs to have an explicit switch to a new GCC version once
it's supported by the kernel.


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

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

Title:
  Was able to migrate out of proposed despite breaking dkms

Status in Auto Package Testing:
  Triaged
Status in linux package in Ubuntu:
  New

Bug description:
  The recent gcc update in eoan migrated out of proposed despite the
  fact that it was breaking dmks/nvidia users, could we have some sort
  of autopkgtest added to make sure that gcc gets blocked in proposed
  the next time we have a such situation?

  (see bug #1830961)

To manage notifications about this bug go to:
https://bugs.launchpad.net/auto-package-testing/+bug/1836100/+subscriptions

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