[Kernel-packages] [Bug 1886188] Re: linux-libc-dev broken for crossbuilding, Multi-Arch:same violation

2020-09-03 Thread Launchpad Bug Tracker 
This bug was fixed in the package linux-riscv - 5.8.0-1.1

---
linux-riscv (5.8.0-1.1) groovy; urgency=medium

  * groovy/linux-riscv: 5.8.0-1.1 -proposed tracker (LP: #1892958)

  * Packaging resync (LP: #1786013)
- [Packaging] update variants
- [Packaging] update update.conf
- [Packaging] update variants
- [Packaging] update update.conf

  * linux-libc-dev broken for crossbuilding, Multi-Arch:same violation
(LP: #1886188)
- [Config] Move build of linux-libc-dev to primary kernel

  * Miscellaneous Ubuntu changes
- [Packaging] Update debhelper build-depends for compat 10
- [Packaging] Updates for using upstream wireguard driver
- [Config] Update configs for 5.8
- [Config] Update annotations for 5.8
- [Config] Update configs after rebase to 5.8.0-18.19
- [Config] Enable CONFIG_DEBUG_INFO_BTF
- [Config] Update toolchain versions in configs
- [Config] CONFIG_SECURITY_DMESG_RESTRICT=y
- [Config] Update toolchain versions in configs
- [Config] Remove stale enforcements from annotations

 -- Seth Forshee   Thu, 27 Aug 2020 13:42:40
-0500

** Changed in: linux-riscv (Ubuntu Groovy)
   Status: Invalid => Fix Released

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

Title:
  linux-libc-dev broken for crossbuilding, Multi-Arch:same violation

Status in linux package in Ubuntu:
  Fix Released
Status in linux-riscv package in Ubuntu:
  Fix Released
Status in linux source package in Focal:
  Fix Released
Status in linux-riscv source package in Focal:
  Fix Released
Status in linux source package in Groovy:
  Fix Released
Status in linux-riscv source package in Groovy:
  Fix Released

Bug description:
  SRU Justificatoin

  Impact: Building linux-libc-dev for riscv64 from the linux-riscv
  package means that it can have a different version from the package on
  other architectures. This makes it uninstallable for cross building.

  Fix: Move the riscv64 linux-libc-dev build back to the main kernel
  package so that the version will match.

  Test Case: See below.

  Regression Potential: This could cause trouble if the main kernel
  package version is behind the linux-riscv package version, and may
  require artificially inflating the version of the linux package.
  Currently this is not necessary, but it needs to be kept in mind when
  preparing packages for upload with the fixes applied.

  ---

  # apt install linux-libc-dev:amd64 linux-libc-dev:riscv64
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  linux-libc-dev is already the newest version (5.4.0-26.30).
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   linux-libc-dev : Breaks: linux-libc-dev:riscv64 (!= 5.4.0-26.30) but 
5.4.0-27.31 is to be installed
   linux-libc-dev:riscv64 : Breaks: linux-libc-dev (!= 5.4.0-27.31) but 
5.4.0-26.30 is to be installed
  E: Unable to correct problems, you have held broken packages.

  $ rmadison -S linux-libc-dev | grep -e riscv64 -e amd64 | grep -e focal -e 
groovy
   linux-libc-dev | 5.4.0-24.28| focal| riscv64
   linux-libc-dev | 5.4.0-26.30| focal| amd64, arm64, armhf, 
i386, ppc64el, s390x
   linux-libc-dev | 5.4.0-26.30| groovy   | amd64, arm64, armhf, 
i386, ppc64el, s390x
   linux-libc-dev | 5.4.0-27.31| groovy   | riscv64
   linux-libc-dev | 5.4.0-28.32| focal-security   | riscv64
   linux-libc-dev | 5.4.0-28.32| focal-updates| riscv64
   linux-libc-dev | 5.4.0-40.44| focal-security   | amd64, arm64, armhf, 
i386, ppc64el, s390x
   linux-libc-dev | 5.4.0-40.44| focal-updates| amd64, arm64, armhf, 
i386, ppc64el, s390x
   linux-libc-dev | 5.4.0-40.44| groovy-proposed  | amd64, arm64, armhf, 
i386, ppc64el, s390x

  This is broken.

  linux-libc-dev must have identical content for common files, across
  all architectures, and must have identical version number.

  A few ways to fix this:

  * Either enforce that src:linux & src:linux-riscv are at the same
  version number. But then reasons for splitting riscv into a separate
  build dissappear

  * Make src:linux build _just_ the headers linux-libc-dev for risv64,
  and nothing else. And stop bulding linux-libc-dev form the src:linux-
  riscv package. Just like it does for i386.

  * Or create new src:linux-headers that only builds linux-libc-dev for
  all architectures, without building any kernels. This way for example,
  we could rev userspace headers to v5.8/v5.9 ahead of said kernel
  landing, to shake out build-failures / userspace

[Kernel-packages] [Bug 1886188] Re: linux-libc-dev broken for crossbuilding, Multi-Arch:same violation

2020-08-31 Thread Launchpad Bug Tracker 
This bug was fixed in the package linux-riscv - 5.4.0-31.35

---
linux-riscv (5.4.0-31.35) focal; urgency=medium

  * focal/linux-riscv: 5.4.0-31.35 -proposed tracker (LP: #1890743)

  * Focal update: v5.4.53 upstream stable release (LP: #1888560)
- [Config] updateconfigs for BLK_DEV_SR_VENDOR

  * Packaging resync (LP: #1786013)
- [Packaging] update update.conf

  * linux-libc-dev broken for crossbuilding, Multi-Arch:same violation
(LP: #1886188)
- [Config] Move build of linux-libc-dev to primary kernel

  [ Ubuntu: 5.4.0-44.48 ]

  * focal/linux: 5.4.0-44.48 -proposed tracker (LP: #1891049)
  * Packaging resync (LP: #1786013)
- [Packaging] update helper scripts
  * ipsec: policy priority management is broken (LP: #1890796)
- xfrm: policy: match with both mark and mask on user interfaces

  [ Ubuntu: 5.4.0-43.47 ]

  * focal/linux: 5.4.0-43.47 -proposed tracker (LP: #1890746)
  * Packaging resync (LP: #1786013)
- update dkms package versions
  * Devlink -  add RoCE disable kernel support  (LP: #1877270)
- devlink: Add new "enable_roce" generic device param
- net/mlx5: Document flow_steering_mode devlink param
- net/mlx5: Handle "enable_roce" devlink param
- IB/mlx5: Rename profile and init methods
- IB/mlx5: Load profile according to RoCE enablement state
- net/mlx5: Remove unneeded variable in mlx5_unload_one
- net/mlx5: Add devlink reload
- IB/mlx5: Do reverse sequence during device removal
  * msg_zerocopy.sh in net from ubuntu_kernel_selftests failed (LP: #1812620)
- selftests/net: relax cpu affinity requirement in msg_zerocopy test
  * Enlarge hisi_sec2 capability (LP: #1890222)
- Revert "UBUNTU: [Config] Disable hisi_sec2 temporarily"
- crypto: hisilicon - update SEC driver module parameter
  * Fix missing HDMI/DP Audio on an HP Desktop (LP: #1890441)
- ALSA: hda/hdmi: Add quirk to force connectivity
  * Fix IOMMU error on AMD Radeon Pro W5700 (LP: #1890306)
- PCI: Mark AMD Navi10 GPU rev 0x00 ATS as broken
  * ASoC:amd:renoir:  the dmic can't record sound after suspend and resume
(LP: #1890220)
- SAUCE: ASoC: amd: renoir: restore two more registers during resume
  * No sound, Dummy output on Acer Swift 3 SF314-57G with Ice Lake core-i7  CPU
(LP: #1877757)
- ASoC: SOF: Intel: hda: fix generic hda codec support
  * Fix right speaker of HP laptop (LP: #1889375)
- SAUCE: hda/realtek: Fix right speaker of HP laptop
  * blk_update_request error when mount nvme partition (LP: #1872383)
- SAUCE: nvme-pci: prevent SK hynix PC400 from using Write Zeroes command
  * soc/amd/renoir: detect dmic from acpi table (LP: #1887734)
- ASoC: amd: add logic to check dmic hardware runtime
- ASoC: amd: add ACPI dependency check
- ASoC: amd: fixed kernel warnings
  * soc/amd/renoir: change the module name to make it work with ucm3
(LP: #1888166)
- AsoC: amd: add missing snd- module prefix to the acp3x-rn driver kernel
  module
- SAUCE: remove a kernel module since its name is changed
  * Focal update: v5.4.55 upstream stable release (LP: #1890343)
- AX.25: Fix out-of-bounds read in ax25_connect()
- AX.25: Prevent out-of-bounds read in ax25_sendmsg()
- dev: Defer free of skbs in flush_backlog
- drivers/net/wan/x25_asy: Fix to make it work
- ip6_gre: fix null-ptr-deref in ip6gre_init_net()
- net-sysfs: add a newline when printing 'tx_timeout' by sysfs
- net: udp: Fix wrong clean up for IS_UDPLITE macro
- qrtr: orphan socket in qrtr_release()
- rtnetlink: Fix memory(net_device) leak when ->newlink fails
- rxrpc: Fix sendmsg() returning EPIPE due to recvmsg() returning ENODATA
- tcp: allow at most one TLP probe per flight
- AX.25: Prevent integer overflows in connect and sendmsg
- sctp: shrink stream outq only when new outcnt < old outcnt
- sctp: shrink stream outq when fails to do addstream reconf
- udp: Copy has_conns in reuseport_grow().
- udp: Improve load balancing for SO_REUSEPORT.
- regmap: debugfs: check count when read regmap file
- PM: wakeup: Show statistics for deleted wakeup sources again
- Revert "dpaa_eth: fix usage as DSA master, try 3"
- Linux 5.4.55
  * Add support for Atlantic NIC firmware v4 (LP: #1886908)
- net: atlantic: simplify hw_get_fw_version() usage
- net: atlantic: align return value of ver_match function with function name
- net: atlantic: add support for FW 4.x
  * perf vendor events s390: Add new deflate counters for IBM z15 (LP: #1888551)
- perf vendor events s390: Add new deflate counters for IBM z15
  * Focal update: v5.4.54 upstream stable release (LP: #1889669)
- soc: qcom: rpmh: Dirt can only make you dirtier, not cleaner
- gpio: arizona: handle pm_runtime_get_sync failure case
- gpio: arizona: put pm_runtime in case of failure
- pinctrl: amd: fix npins for uart0 in kerncz_groups
- mac80211: allow rx of mesh eapol frames with default

[Kernel-packages] [Bug 1886188] Re: linux-libc-dev broken for crossbuilding, Multi-Arch:same violation

2020-08-31 Thread Launchpad Bug Tracker 
This bug was fixed in the package linux - 5.4.0-45.49

---
linux (5.4.0-45.49) focal; urgency=medium

  * focal/linux: 5.4.0-45.49 -proposed tracker (LP: #1893050)

  * [Potential Regression] dscr_inherit_exec_test from powerpc in
ubuntu_kernel_selftests failed on B/E/F (LP: #1888332)
- powerpc/64s: Don't init FSCR_DSCR in __init_FSCR()

linux (5.4.0-44.48) focal; urgency=medium

  * focal/linux: 5.4.0-44.48 -proposed tracker (LP: #1891049)

  * Packaging resync (LP: #1786013)
- [Packaging] update helper scripts

  * ipsec: policy priority management is broken (LP: #1890796)
- xfrm: policy: match with both mark and mask on user interfaces

linux (5.4.0-43.47) focal; urgency=medium

  * focal/linux: 5.4.0-43.47 -proposed tracker (LP: #1890746)

  * Packaging resync (LP: #1786013)
- update dkms package versions

  * Devlink -  add RoCE disable kernel support  (LP: #1877270)
- devlink: Add new "enable_roce" generic device param
- net/mlx5: Document flow_steering_mode devlink param
- net/mlx5: Handle "enable_roce" devlink param
- IB/mlx5: Rename profile and init methods
- IB/mlx5: Load profile according to RoCE enablement state
- net/mlx5: Remove unneeded variable in mlx5_unload_one
- net/mlx5: Add devlink reload
- IB/mlx5: Do reverse sequence during device removal

  * msg_zerocopy.sh in net from ubuntu_kernel_selftests failed (LP: #1812620)
- selftests/net: relax cpu affinity requirement in msg_zerocopy test

  * Enlarge hisi_sec2 capability (LP: #1890222)
- Revert "UBUNTU: [Config] Disable hisi_sec2 temporarily"
- crypto: hisilicon - update SEC driver module parameter

  * Fix missing HDMI/DP Audio on an HP Desktop (LP: #1890441)
- ALSA: hda/hdmi: Add quirk to force connectivity

  * Fix IOMMU error on AMD Radeon Pro W5700 (LP: #1890306)
- PCI: Mark AMD Navi10 GPU rev 0x00 ATS as broken

  * ASoC:amd:renoir:  the dmic can't record sound after suspend and resume
(LP: #1890220)
- SAUCE: ASoC: amd: renoir: restore two more registers during resume

  * No sound, Dummy output on Acer Swift 3 SF314-57G with Ice Lake core-i7  CPU
(LP: #1877757)
- ASoC: SOF: Intel: hda: fix generic hda codec support

  * Fix right speaker of HP laptop (LP: #1889375)
- SAUCE: hda/realtek: Fix right speaker of HP laptop

  * blk_update_request error when mount nvme partition (LP: #1872383)
- SAUCE: nvme-pci: prevent SK hynix PC400 from using Write Zeroes command

  * soc/amd/renoir: detect dmic from acpi table (LP: #1887734)
- ASoC: amd: add logic to check dmic hardware runtime
- ASoC: amd: add ACPI dependency check
- ASoC: amd: fixed kernel warnings

  * soc/amd/renoir: change the module name to make it work with ucm3
(LP: #1888166)
- AsoC: amd: add missing snd- module prefix to the acp3x-rn driver kernel
  module
- SAUCE: remove a kernel module since its name is changed

  * Focal update: v5.4.55 upstream stable release (LP: #1890343)
- AX.25: Fix out-of-bounds read in ax25_connect()
- AX.25: Prevent out-of-bounds read in ax25_sendmsg()
- dev: Defer free of skbs in flush_backlog
- drivers/net/wan/x25_asy: Fix to make it work
- ip6_gre: fix null-ptr-deref in ip6gre_init_net()
- net-sysfs: add a newline when printing 'tx_timeout' by sysfs
- net: udp: Fix wrong clean up for IS_UDPLITE macro
- qrtr: orphan socket in qrtr_release()
- rtnetlink: Fix memory(net_device) leak when ->newlink fails
- rxrpc: Fix sendmsg() returning EPIPE due to recvmsg() returning ENODATA
- tcp: allow at most one TLP probe per flight
- AX.25: Prevent integer overflows in connect and sendmsg
- sctp: shrink stream outq only when new outcnt < old outcnt
- sctp: shrink stream outq when fails to do addstream reconf
- udp: Copy has_conns in reuseport_grow().
- udp: Improve load balancing for SO_REUSEPORT.
- regmap: debugfs: check count when read regmap file
- PM: wakeup: Show statistics for deleted wakeup sources again
- Revert "dpaa_eth: fix usage as DSA master, try 3"
- Linux 5.4.55

  * Add support for Atlantic NIC firmware v4 (LP: #1886908)
- net: atlantic: simplify hw_get_fw_version() usage
- net: atlantic: align return value of ver_match function with function name
- net: atlantic: add support for FW 4.x

  * perf vendor events s390: Add new deflate counters for IBM z15 (LP: #1888551)
- perf vendor events s390: Add new deflate counters for IBM z15

  * Focal update: v5.4.54 upstream stable release (LP: #1889669)
- soc: qcom: rpmh: Dirt can only make you dirtier, not cleaner
- gpio: arizona: handle pm_runtime_get_sync failure case
- gpio: arizona: put pm_runtime in case of failure
- pinctrl: amd: fix npins for uart0 in kerncz_groups
- mac80211: allow rx of mesh eapol frames with default rx key
- scsi: scsi_transport_spi: Fix function pointer check
- xtensa: fix __sync_fetch_and_{and,or}_4 declarations

[Kernel-packages] [Bug 1886188] Re: linux-libc-dev broken for crossbuilding, Multi-Arch:same violation

2020-08-26 Thread Launchpad Bug Tracker 
This bug was fixed in the package linux - 5.8.0-16.17

---
linux (5.8.0-16.17) groovy; urgency=medium

  * groovy/linux: 5.8.0-16.17 -proposed tracker (LP: #1891233)

  * Miscellaneous Ubuntu changes
- hio -- Update to use bio_{start,end}_io_acct with 5.8+
- Enable hio driver
- [Packaging] Temporarily disable building doc package contents

linux (5.8.0-15.16) groovy; urgency=medium

  * groovy/linux: 5.8.0-15.16 -proposed tracker (LP: #1891177)

  * Miscellaneous Ubuntu changes
- SAUCE: Documentation: import error c_funcptr_sig_re, c_sig_re (sphinx-
  doc/sphinx@0f49e30c)

linux (5.8.0-14.15) groovy; urgency=medium

  * groovy/linux: 5.8.0-14.15 -proposed tracker (LP: #1891085)

  * Packaging resync (LP: #1786013)
- [Packaging] update helper scripts

  * msg_zerocopy.sh in net from ubuntu_kernel_selftests failed (LP: #1812620)
- selftests/net: relax cpu affinity requirement in msg_zerocopy test

  * Fix missing HDMI/DP Audio on an HP Desktop (LP: #1890441)
- ALSA: hda/hdmi: Add quirk to force connectivity

  * Add initial audio support for Lenovo ThinkStation P620 (LP: #1890317)
- ALSA: usb-audio: Add support for Lenovo ThinkStation P620

  * Fix IOMMU error on AMD Radeon Pro W5700 (LP: #1890306)
- PCI: Mark AMD Navi10 GPU rev 0x00 ATS as broken

  * Enlarge hisi_sec2 capability (LP: #1890222)
- crypto: hisilicon - update SEC driver module parameter

  * Miscellaneous Ubuntu changes
- [Config] Re-enable signing for ppc64el

 -- Seth Forshee   Tue, 11 Aug 2020 15:32:58
-0500

** Changed in: linux (Ubuntu Groovy)
   Status: Fix Committed => Fix Released

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

Title:
  linux-libc-dev broken for crossbuilding, Multi-Arch:same violation

Status in linux package in Ubuntu:
  Fix Released
Status in linux-riscv package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in linux-riscv source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  Fix Released
Status in linux-riscv source package in Groovy:
  Invalid

Bug description:
  SRU Justificatoin

  Impact: Building linux-libc-dev for riscv64 from the linux-riscv
  package means that it can have a different version from the package on
  other architectures. This makes it uninstallable for cross building.

  Fix: Move the riscv64 linux-libc-dev build back to the main kernel
  package so that the version will match.

  Test Case: See below.

  Regression Potential: This could cause trouble if the main kernel
  package version is behind the linux-riscv package version, and may
  require artificially inflating the version of the linux package.
  Currently this is not necessary, but it needs to be kept in mind when
  preparing packages for upload with the fixes applied.

  ---

  # apt install linux-libc-dev:amd64 linux-libc-dev:riscv64
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  linux-libc-dev is already the newest version (5.4.0-26.30).
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   linux-libc-dev : Breaks: linux-libc-dev:riscv64 (!= 5.4.0-26.30) but 
5.4.0-27.31 is to be installed
   linux-libc-dev:riscv64 : Breaks: linux-libc-dev (!= 5.4.0-27.31) but 
5.4.0-26.30 is to be installed
  E: Unable to correct problems, you have held broken packages.

  $ rmadison -S linux-libc-dev | grep -e riscv64 -e amd64 | grep -e focal -e 
groovy
   linux-libc-dev | 5.4.0-24.28| focal| riscv64
   linux-libc-dev | 5.4.0-26.30| focal| amd64, arm64, armhf, 
i386, ppc64el, s390x
   linux-libc-dev | 5.4.0-26.30| groovy   | amd64, arm64, armhf, 
i386, ppc64el, s390x
   linux-libc-dev | 5.4.0-27.31| groovy   | riscv64
   linux-libc-dev | 5.4.0-28.32| focal-security   | riscv64
   linux-libc-dev | 5.4.0-28.32| focal-updates| riscv64
   linux-libc-dev | 5.4.0-40.44| focal-security   | amd64, arm64, armhf, 
i386, ppc64el, s390x
   linux-libc-dev | 5.4.0-40.44| focal-updates| amd64, arm64, armhf, 
i386, ppc64el, s390x
   linux-libc-dev | 5.4.0-40.44| groovy-proposed  | amd64, arm64, armhf, 
i386, ppc64el, s390x

  This is broken.

  linux-libc-dev must have identical content for common files, across
  all architectures, and must have identical version number.

  A few ways to fix this:

  * Either enforce that src:linux & src:linux-riscv are at the same
  version number. But then reasons for splitting riscv into a separate
  build dissappear

  * Make src:linux build

[Kernel-packages] [Bug 1886188] Re: linux-libc-dev broken for crossbuilding, Multi-Arch:same violation

2020-08-25 Thread Dimitri John Ledkov 
I've already bootstrapped rustc using these changes. In both focal &
groovy. This is really good!

For me it was enough to have it just in -proposed. But yeah, we do need
this in -updates too.

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

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

Title:
  linux-libc-dev broken for crossbuilding, Multi-Arch:same violation

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-riscv package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in linux-riscv source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  Fix Committed
Status in linux-riscv source package in Groovy:
  Invalid

Bug description:
  SRU Justificatoin

  Impact: Building linux-libc-dev for riscv64 from the linux-riscv
  package means that it can have a different version from the package on
  other architectures. This makes it uninstallable for cross building.

  Fix: Move the riscv64 linux-libc-dev build back to the main kernel
  package so that the version will match.

  Test Case: See below.

  Regression Potential: This could cause trouble if the main kernel
  package version is behind the linux-riscv package version, and may
  require artificially inflating the version of the linux package.
  Currently this is not necessary, but it needs to be kept in mind when
  preparing packages for upload with the fixes applied.

  ---

  # apt install linux-libc-dev:amd64 linux-libc-dev:riscv64
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  linux-libc-dev is already the newest version (5.4.0-26.30).
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   linux-libc-dev : Breaks: linux-libc-dev:riscv64 (!= 5.4.0-26.30) but 
5.4.0-27.31 is to be installed
   linux-libc-dev:riscv64 : Breaks: linux-libc-dev (!= 5.4.0-27.31) but 
5.4.0-26.30 is to be installed
  E: Unable to correct problems, you have held broken packages.

  $ rmadison -S linux-libc-dev | grep -e riscv64 -e amd64 | grep -e focal -e 
groovy
   linux-libc-dev | 5.4.0-24.28| focal| riscv64
   linux-libc-dev | 5.4.0-26.30| focal| amd64, arm64, armhf, 
i386, ppc64el, s390x
   linux-libc-dev | 5.4.0-26.30| groovy   | amd64, arm64, armhf, 
i386, ppc64el, s390x
   linux-libc-dev | 5.4.0-27.31| groovy   | riscv64
   linux-libc-dev | 5.4.0-28.32| focal-security   | riscv64
   linux-libc-dev | 5.4.0-28.32| focal-updates| riscv64
   linux-libc-dev | 5.4.0-40.44| focal-security   | amd64, arm64, armhf, 
i386, ppc64el, s390x
   linux-libc-dev | 5.4.0-40.44| focal-updates| amd64, arm64, armhf, 
i386, ppc64el, s390x
   linux-libc-dev | 5.4.0-40.44| groovy-proposed  | amd64, arm64, armhf, 
i386, ppc64el, s390x

  This is broken.

  linux-libc-dev must have identical content for common files, across
  all architectures, and must have identical version number.

  A few ways to fix this:

  * Either enforce that src:linux & src:linux-riscv are at the same
  version number. But then reasons for splitting riscv into a separate
  build dissappear

  * Make src:linux build _just_ the headers linux-libc-dev for risv64,
  and nothing else. And stop bulding linux-libc-dev form the src:linux-
  riscv package. Just like it does for i386.

  * Or create new src:linux-headers that only builds linux-libc-dev for
  all architectures, without building any kernels. This way for example,
  we could rev userspace headers to v5.8/v5.9 ahead of said kernel
  landing, to shake out build-failures / userspace issues, whilst the
  kernel itself is still baking in bootstrap/proposed PPA.

  This must be address in Focal and Groovy

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886188/+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 1886188] Re: linux-libc-dev broken for crossbuilding, Multi-Arch:same violation

2020-08-10 Thread Ubuntu Kernel Bot 
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag 'verification-needed-focal' to 'verification-failed-focal'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-focal

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

Title:
  linux-libc-dev broken for crossbuilding, Multi-Arch:same violation

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-riscv package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in linux-riscv source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  Fix Committed
Status in linux-riscv source package in Groovy:
  Invalid

Bug description:
  SRU Justificatoin

  Impact: Building linux-libc-dev for riscv64 from the linux-riscv
  package means that it can have a different version from the package on
  other architectures. This makes it uninstallable for cross building.

  Fix: Move the riscv64 linux-libc-dev build back to the main kernel
  package so that the version will match.

  Test Case: See below.

  Regression Potential: This could cause trouble if the main kernel
  package version is behind the linux-riscv package version, and may
  require artificially inflating the version of the linux package.
  Currently this is not necessary, but it needs to be kept in mind when
  preparing packages for upload with the fixes applied.

  ---

  # apt install linux-libc-dev:amd64 linux-libc-dev:riscv64
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  linux-libc-dev is already the newest version (5.4.0-26.30).
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   linux-libc-dev : Breaks: linux-libc-dev:riscv64 (!= 5.4.0-26.30) but 
5.4.0-27.31 is to be installed
   linux-libc-dev:riscv64 : Breaks: linux-libc-dev (!= 5.4.0-27.31) but 
5.4.0-26.30 is to be installed
  E: Unable to correct problems, you have held broken packages.

  $ rmadison -S linux-libc-dev | grep -e riscv64 -e amd64 | grep -e focal -e 
groovy
   linux-libc-dev | 5.4.0-24.28| focal| riscv64
   linux-libc-dev | 5.4.0-26.30| focal| amd64, arm64, armhf, 
i386, ppc64el, s390x
   linux-libc-dev | 5.4.0-26.30| groovy   | amd64, arm64, armhf, 
i386, ppc64el, s390x
   linux-libc-dev | 5.4.0-27.31| groovy   | riscv64
   linux-libc-dev | 5.4.0-28.32| focal-security   | riscv64
   linux-libc-dev | 5.4.0-28.32| focal-updates| riscv64
   linux-libc-dev | 5.4.0-40.44| focal-security   | amd64, arm64, armhf, 
i386, ppc64el, s390x
   linux-libc-dev | 5.4.0-40.44| focal-updates| amd64, arm64, armhf, 
i386, ppc64el, s390x
   linux-libc-dev | 5.4.0-40.44| groovy-proposed  | amd64, arm64, armhf, 
i386, ppc64el, s390x

  This is broken.

  linux-libc-dev must have identical content for common files, across
  all architectures, and must have identical version number.

  A few ways to fix this:

  * Either enforce that src:linux & src:linux-riscv are at the same
  version number. But then reasons for splitting riscv into a separate
  build dissappear

  * Make src:linux build _just_ the headers linux-libc-dev for risv64,
  and nothing else. And stop bulding linux-libc-dev form the src:linux-
  riscv package. Just like it does for i386.

  * Or create new src:linux-headers that only builds linux-libc-dev for
  all architectures, without building any kernels. This way for example,
  we could rev userspace headers to v5.8/v5.9 ahead of said kernel
  landing, to shake out build-failures / userspace issues, whilst the
  kernel itself is still baking in bootstrap/proposed PPA.

  This must be address in Focal and Groovy

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886188/+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 1886188] Re: linux-libc-dev broken for crossbuilding, Multi-Arch:same violation

2020-08-03 Thread Kelsey Margarete Skunberg 
** Changed in: linux (Ubuntu Focal)
   Status: In Progress => Fix Committed

** Changed in: linux-riscv (Ubuntu Focal)
   Status: In Progress => Fix Committed

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

Title:
  linux-libc-dev broken for crossbuilding, Multi-Arch:same violation

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-riscv package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in linux-riscv source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  Fix Committed
Status in linux-riscv source package in Groovy:
  Invalid

Bug description:
  SRU Justificatoin

  Impact: Building linux-libc-dev for riscv64 from the linux-riscv
  package means that it can have a different version from the package on
  other architectures. This makes it uninstallable for cross building.

  Fix: Move the riscv64 linux-libc-dev build back to the main kernel
  package so that the version will match.

  Test Case: See below.

  Regression Potential: This could cause trouble if the main kernel
  package version is behind the linux-riscv package version, and may
  require artificially inflating the version of the linux package.
  Currently this is not necessary, but it needs to be kept in mind when
  preparing packages for upload with the fixes applied.

  ---

  # apt install linux-libc-dev:amd64 linux-libc-dev:riscv64
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  linux-libc-dev is already the newest version (5.4.0-26.30).
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   linux-libc-dev : Breaks: linux-libc-dev:riscv64 (!= 5.4.0-26.30) but 
5.4.0-27.31 is to be installed
   linux-libc-dev:riscv64 : Breaks: linux-libc-dev (!= 5.4.0-27.31) but 
5.4.0-26.30 is to be installed
  E: Unable to correct problems, you have held broken packages.

  $ rmadison -S linux-libc-dev | grep -e riscv64 -e amd64 | grep -e focal -e 
groovy
   linux-libc-dev | 5.4.0-24.28| focal| riscv64
   linux-libc-dev | 5.4.0-26.30| focal| amd64, arm64, armhf, 
i386, ppc64el, s390x
   linux-libc-dev | 5.4.0-26.30| groovy   | amd64, arm64, armhf, 
i386, ppc64el, s390x
   linux-libc-dev | 5.4.0-27.31| groovy   | riscv64
   linux-libc-dev | 5.4.0-28.32| focal-security   | riscv64
   linux-libc-dev | 5.4.0-28.32| focal-updates| riscv64
   linux-libc-dev | 5.4.0-40.44| focal-security   | amd64, arm64, armhf, 
i386, ppc64el, s390x
   linux-libc-dev | 5.4.0-40.44| focal-updates| amd64, arm64, armhf, 
i386, ppc64el, s390x
   linux-libc-dev | 5.4.0-40.44| groovy-proposed  | amd64, arm64, armhf, 
i386, ppc64el, s390x

  This is broken.

  linux-libc-dev must have identical content for common files, across
  all architectures, and must have identical version number.

  A few ways to fix this:

  * Either enforce that src:linux & src:linux-riscv are at the same
  version number. But then reasons for splitting riscv into a separate
  build dissappear

  * Make src:linux build _just_ the headers linux-libc-dev for risv64,
  and nothing else. And stop bulding linux-libc-dev form the src:linux-
  riscv package. Just like it does for i386.

  * Or create new src:linux-headers that only builds linux-libc-dev for
  all architectures, without building any kernels. This way for example,
  we could rev userspace headers to v5.8/v5.9 ahead of said kernel
  landing, to shake out build-failures / userspace issues, whilst the
  kernel itself is still baking in bootstrap/proposed PPA.

  This must be address in Focal and Groovy

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886188/+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 1886188] Re: linux-libc-dev broken for crossbuilding, Multi-Arch:same violation

2020-07-14 Thread Seth Forshee 
** Changed in: linux (Ubuntu Groovy)
   Status: In Progress => Fix Committed

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

Title:
  linux-libc-dev broken for crossbuilding, Multi-Arch:same violation

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-riscv package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  In Progress
Status in linux-riscv source package in Focal:
  In Progress
Status in linux source package in Groovy:
  Fix Committed
Status in linux-riscv source package in Groovy:
  Invalid

Bug description:
  SRU Justificatoin

  Impact: Building linux-libc-dev for riscv64 from the linux-riscv
  package means that it can have a different version from the package on
  other architectures. This makes it uninstallable for cross building.

  Fix: Move the riscv64 linux-libc-dev build back to the main kernel
  package so that the version will match.

  Test Case: See below.

  Regression Potential: This could cause trouble if the main kernel
  package version is behind the linux-riscv package version, and may
  require artificially inflating the version of the linux package.
  Currently this is not necessary, but it needs to be kept in mind when
  preparing packages for upload with the fixes applied.

  ---

  # apt install linux-libc-dev:amd64 linux-libc-dev:riscv64
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  linux-libc-dev is already the newest version (5.4.0-26.30).
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   linux-libc-dev : Breaks: linux-libc-dev:riscv64 (!= 5.4.0-26.30) but 
5.4.0-27.31 is to be installed
   linux-libc-dev:riscv64 : Breaks: linux-libc-dev (!= 5.4.0-27.31) but 
5.4.0-26.30 is to be installed
  E: Unable to correct problems, you have held broken packages.

  $ rmadison -S linux-libc-dev | grep -e riscv64 -e amd64 | grep -e focal -e 
groovy
   linux-libc-dev | 5.4.0-24.28| focal| riscv64
   linux-libc-dev | 5.4.0-26.30| focal| amd64, arm64, armhf, 
i386, ppc64el, s390x
   linux-libc-dev | 5.4.0-26.30| groovy   | amd64, arm64, armhf, 
i386, ppc64el, s390x
   linux-libc-dev | 5.4.0-27.31| groovy   | riscv64
   linux-libc-dev | 5.4.0-28.32| focal-security   | riscv64
   linux-libc-dev | 5.4.0-28.32| focal-updates| riscv64
   linux-libc-dev | 5.4.0-40.44| focal-security   | amd64, arm64, armhf, 
i386, ppc64el, s390x
   linux-libc-dev | 5.4.0-40.44| focal-updates| amd64, arm64, armhf, 
i386, ppc64el, s390x
   linux-libc-dev | 5.4.0-40.44| groovy-proposed  | amd64, arm64, armhf, 
i386, ppc64el, s390x

  This is broken.

  linux-libc-dev must have identical content for common files, across
  all architectures, and must have identical version number.

  A few ways to fix this:

  * Either enforce that src:linux & src:linux-riscv are at the same
  version number. But then reasons for splitting riscv into a separate
  build dissappear

  * Make src:linux build _just_ the headers linux-libc-dev for risv64,
  and nothing else. And stop bulding linux-libc-dev form the src:linux-
  riscv package. Just like it does for i386.

  * Or create new src:linux-headers that only builds linux-libc-dev for
  all architectures, without building any kernels. This way for example,
  we could rev userspace headers to v5.8/v5.9 ahead of said kernel
  landing, to shake out build-failures / userspace issues, whilst the
  kernel itself is still baking in bootstrap/proposed PPA.

  This must be address in Focal and Groovy

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886188/+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 1886188] Re: linux-libc-dev broken for crossbuilding, Multi-Arch:same violation

2020-07-08 Thread Seth Forshee 
https://lists.ubuntu.com/archives/kernel-team/2020-July/111881.html
https://lists.ubuntu.com/archives/kernel-team/2020-July/111884.html

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

Title:
  linux-libc-dev broken for crossbuilding, Multi-Arch:same violation

Status in linux package in Ubuntu:
  In Progress
Status in linux-riscv package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  In Progress
Status in linux-riscv source package in Focal:
  In Progress
Status in linux source package in Groovy:
  In Progress
Status in linux-riscv source package in Groovy:
  Invalid

Bug description:
  SRU Justificatoin

  Impact: Building linux-libc-dev for riscv64 from the linux-riscv
  package means that it can have a different version from the package on
  other architectures. This makes it uninstallable for cross building.

  Fix: Move the riscv64 linux-libc-dev build back to the main kernel
  package so that the version will match.

  Test Case: See below.

  Regression Potential: This could cause trouble if the main kernel
  package version is behind the linux-riscv package version, and may
  require artificially inflating the version of the linux package.
  Currently this is not necessary, but it needs to be kept in mind when
  preparing packages for upload with the fixes applied.

  ---

  # apt install linux-libc-dev:amd64 linux-libc-dev:riscv64
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  linux-libc-dev is already the newest version (5.4.0-26.30).
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   linux-libc-dev : Breaks: linux-libc-dev:riscv64 (!= 5.4.0-26.30) but 
5.4.0-27.31 is to be installed
   linux-libc-dev:riscv64 : Breaks: linux-libc-dev (!= 5.4.0-27.31) but 
5.4.0-26.30 is to be installed
  E: Unable to correct problems, you have held broken packages.

  $ rmadison -S linux-libc-dev | grep -e riscv64 -e amd64 | grep -e focal -e 
groovy
   linux-libc-dev | 5.4.0-24.28| focal| riscv64
   linux-libc-dev | 5.4.0-26.30| focal| amd64, arm64, armhf, 
i386, ppc64el, s390x
   linux-libc-dev | 5.4.0-26.30| groovy   | amd64, arm64, armhf, 
i386, ppc64el, s390x
   linux-libc-dev | 5.4.0-27.31| groovy   | riscv64
   linux-libc-dev | 5.4.0-28.32| focal-security   | riscv64
   linux-libc-dev | 5.4.0-28.32| focal-updates| riscv64
   linux-libc-dev | 5.4.0-40.44| focal-security   | amd64, arm64, armhf, 
i386, ppc64el, s390x
   linux-libc-dev | 5.4.0-40.44| focal-updates| amd64, arm64, armhf, 
i386, ppc64el, s390x
   linux-libc-dev | 5.4.0-40.44| groovy-proposed  | amd64, arm64, armhf, 
i386, ppc64el, s390x

  This is broken.

  linux-libc-dev must have identical content for common files, across
  all architectures, and must have identical version number.

  A few ways to fix this:

  * Either enforce that src:linux & src:linux-riscv are at the same
  version number. But then reasons for splitting riscv into a separate
  build dissappear

  * Make src:linux build _just_ the headers linux-libc-dev for risv64,
  and nothing else. And stop bulding linux-libc-dev form the src:linux-
  riscv package. Just like it does for i386.

  * Or create new src:linux-headers that only builds linux-libc-dev for
  all architectures, without building any kernels. This way for example,
  we could rev userspace headers to v5.8/v5.9 ahead of said kernel
  landing, to shake out build-failures / userspace issues, whilst the
  kernel itself is still baking in bootstrap/proposed PPA.

  This must be address in Focal and Groovy

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886188/+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 1886188] Re: linux-libc-dev broken for crossbuilding, Multi-Arch:same violation

2020-07-08 Thread Seth Forshee 
linux-riscv in groovy is still copied forward from focal and will pick
up the change applied from focal when it is updated. Therefore I'm
marking that task invalid.

** Changed in: linux (Ubuntu Focal)
   Status: Incomplete => In Progress

** Changed in: linux (Ubuntu Focal)
 Assignee: (unassigned) => Seth Forshee (sforshee)

** Changed in: linux (Ubuntu Groovy)
   Status: Incomplete => In Progress

** Changed in: linux (Ubuntu Groovy)
 Assignee: (unassigned) => Seth Forshee (sforshee)

** Changed in: linux-riscv (Ubuntu Focal)
   Status: New => In Progress

** Changed in: linux-riscv (Ubuntu Focal)
 Assignee: (unassigned) => Seth Forshee (sforshee)

** Changed in: linux-riscv (Ubuntu Groovy)
   Status: New => Invalid

** Description changed:

+ SRU Justificatoin
+ 
+ Impact: Building linux-libc-dev for riscv64 from the linux-riscv package
+ means that it can have a different version from the package on other
+ architectures. This makes it uninstallable for cross building.
+ 
+ Fix: Move the riscv64 linux-libc-dev build back to the main kernel
+ package so that the version will match.
+ 
+ Test Case: See below.
+ 
+ Regression Potential: This could cause trouble if the main kernel
+ package version is behind the linux-riscv package version, and may
+ require artificially inflating the version of the linux package.
+ Currently this is not necessary, but it needs to be kept in mind when
+ preparing packages for upload with the fixes applied.
+ 
+ ---
+ 
  # apt install linux-libc-dev:amd64 linux-libc-dev:riscv64
  Reading package lists... Done
- Building dependency tree   
+ Building dependency tree
  Reading state information... Done
  linux-libc-dev is already the newest version (5.4.0-26.30).
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:
  
  The following packages have unmet dependencies:
-  linux-libc-dev : Breaks: linux-libc-dev:riscv64 (!= 5.4.0-26.30) but 
5.4.0-27.31 is to be installed
-  linux-libc-dev:riscv64 : Breaks: linux-libc-dev (!= 5.4.0-27.31) but 
5.4.0-26.30 is to be installed
+  linux-libc-dev : Breaks: linux-libc-dev:riscv64 (!= 5.4.0-26.30) but 
5.4.0-27.31 is to be installed
+  linux-libc-dev:riscv64 : Breaks: linux-libc-dev (!= 5.4.0-27.31) but 
5.4.0-26.30 is to be installed
  E: Unable to correct problems, you have held broken packages.
  
  $ rmadison -S linux-libc-dev | grep -e riscv64 -e amd64 | grep -e focal -e 
groovy
-  linux-libc-dev | 5.4.0-24.28| focal| riscv64
-  linux-libc-dev | 5.4.0-26.30| focal| amd64, arm64, armhf, 
i386, ppc64el, s390x
-  linux-libc-dev | 5.4.0-26.30| groovy   | amd64, arm64, armhf, 
i386, ppc64el, s390x
-  linux-libc-dev | 5.4.0-27.31| groovy   | riscv64
-  linux-libc-dev | 5.4.0-28.32| focal-security   | riscv64
-  linux-libc-dev | 5.4.0-28.32| focal-updates| riscv64
-  linux-libc-dev | 5.4.0-40.44| focal-security   | amd64, arm64, armhf, 
i386, ppc64el, s390x
-  linux-libc-dev | 5.4.0-40.44| focal-updates| amd64, arm64, armhf, 
i386, ppc64el, s390x
-  linux-libc-dev | 5.4.0-40.44| groovy-proposed  | amd64, arm64, armhf, 
i386, ppc64el, s390x
+  linux-libc-dev | 5.4.0-24.28| focal| riscv64
+  linux-libc-dev | 5.4.0-26.30| focal| amd64, arm64, armhf, 
i386, ppc64el, s390x
+  linux-libc-dev | 5.4.0-26.30| groovy   | amd64, arm64, armhf, 
i386, ppc64el, s390x
+  linux-libc-dev | 5.4.0-27.31| groovy   | riscv64
+  linux-libc-dev | 5.4.0-28.32| focal-security   | riscv64
+  linux-libc-dev | 5.4.0-28.32| focal-updates| riscv64
+  linux-libc-dev | 5.4.0-40.44| focal-security   | amd64, arm64, armhf, 
i386, ppc64el, s390x
+  linux-libc-dev | 5.4.0-40.44| focal-updates| amd64, arm64, armhf, 
i386, ppc64el, s390x
+  linux-libc-dev | 5.4.0-40.44| groovy-proposed  | amd64, arm64, armhf, 
i386, ppc64el, s390x
  
  This is broken.
  
  linux-libc-dev must have identical content for common files, across all
  architectures, and must have identical version number.
  
  A few ways to fix this:
  
  * Either enforce that src:linux & src:linux-riscv are at the same
  version number. But then reasons for splitting riscv into a separate
  build dissappear
  
  * Make src:linux build _just_ the headers linux-libc-dev for risv64, and
  nothing else. And stop bulding linux-libc-dev form the src:linux-riscv
  package. Just like it does for i386.
  
  * Or create new src:linux-headers that only builds linux-libc-dev for
  all architectures, without building any kernels. This way for example,
  we could rev userspace headers to v5.8/v5.9 ahead of said kernel
  landing, to shake out build-failures / userspace issues, whilst

[Kernel-packages] [Bug 1886188] Re: linux-libc-dev broken for crossbuilding, Multi-Arch:same violation

2020-07-08 Thread Matthias Klose 
** Changed in: linux (Ubuntu Focal)
   Status: Incomplete => New

** Changed in: linux (Ubuntu Groovy)
   Status: Incomplete => New

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

Title:
  linux-libc-dev broken for crossbuilding, Multi-Arch:same violation

Status in linux package in Ubuntu:
  Incomplete
Status in linux-riscv package in Ubuntu:
  New
Status in linux source package in Focal:
  Incomplete
Status in linux-riscv source package in Focal:
  New
Status in linux source package in Groovy:
  Incomplete
Status in linux-riscv source package in Groovy:
  New

Bug description:
  # apt install linux-libc-dev:amd64 linux-libc-dev:riscv64
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  linux-libc-dev is already the newest version (5.4.0-26.30).
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   linux-libc-dev : Breaks: linux-libc-dev:riscv64 (!= 5.4.0-26.30) but 
5.4.0-27.31 is to be installed
   linux-libc-dev:riscv64 : Breaks: linux-libc-dev (!= 5.4.0-27.31) but 
5.4.0-26.30 is to be installed
  E: Unable to correct problems, you have held broken packages.

  $ rmadison -S linux-libc-dev | grep -e riscv64 -e amd64 | grep -e focal -e 
groovy
   linux-libc-dev | 5.4.0-24.28| focal| riscv64
   linux-libc-dev | 5.4.0-26.30| focal| amd64, arm64, armhf, 
i386, ppc64el, s390x
   linux-libc-dev | 5.4.0-26.30| groovy   | amd64, arm64, armhf, 
i386, ppc64el, s390x
   linux-libc-dev | 5.4.0-27.31| groovy   | riscv64
   linux-libc-dev | 5.4.0-28.32| focal-security   | riscv64
   linux-libc-dev | 5.4.0-28.32| focal-updates| riscv64
   linux-libc-dev | 5.4.0-40.44| focal-security   | amd64, arm64, armhf, 
i386, ppc64el, s390x
   linux-libc-dev | 5.4.0-40.44| focal-updates| amd64, arm64, armhf, 
i386, ppc64el, s390x
   linux-libc-dev | 5.4.0-40.44| groovy-proposed  | amd64, arm64, armhf, 
i386, ppc64el, s390x

  This is broken.

  linux-libc-dev must have identical content for common files, across
  all architectures, and must have identical version number.

  A few ways to fix this:

  * Either enforce that src:linux & src:linux-riscv are at the same
  version number. But then reasons for splitting riscv into a separate
  build dissappear

  * Make src:linux build _just_ the headers linux-libc-dev for risv64,
  and nothing else. And stop bulding linux-libc-dev form the src:linux-
  riscv package. Just like it does for i386.

  * Or create new src:linux-headers that only builds linux-libc-dev for
  all architectures, without building any kernels. This way for example,
  we could rev userspace headers to v5.8/v5.9 ahead of said kernel
  landing, to shake out build-failures / userspace issues, whilst the
  kernel itself is still baking in bootstrap/proposed PPA.

  This must be address in Focal and Groovy

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886188/+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 1886188] Re: linux-libc-dev broken for crossbuilding, Multi-Arch:same violation

2020-07-03 Thread Dimitri John Ledkov 
** Tags added: bot-stop-nagging

** Changed in: linux (Ubuntu Focal)
   Status: Incomplete => Triaged

** Changed in: linux (Ubuntu Focal)
   Status: Triaged => New

** Changed in: linux (Ubuntu Groovy)
   Status: Incomplete => New

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

Title:
  linux-libc-dev broken for crossbuilding, Multi-Arch:same violation

Status in linux package in Ubuntu:
  Incomplete
Status in linux-riscv package in Ubuntu:
  New
Status in linux source package in Focal:
  Incomplete
Status in linux-riscv source package in Focal:
  New
Status in linux source package in Groovy:
  Incomplete
Status in linux-riscv source package in Groovy:
  New

Bug description:
  # apt install linux-libc-dev:amd64 linux-libc-dev:riscv64
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  linux-libc-dev is already the newest version (5.4.0-26.30).
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   linux-libc-dev : Breaks: linux-libc-dev:riscv64 (!= 5.4.0-26.30) but 
5.4.0-27.31 is to be installed
   linux-libc-dev:riscv64 : Breaks: linux-libc-dev (!= 5.4.0-27.31) but 
5.4.0-26.30 is to be installed
  E: Unable to correct problems, you have held broken packages.

  $ rmadison -S linux-libc-dev | grep -e riscv64 -e amd64 | grep -e focal -e 
groovy
   linux-libc-dev | 5.4.0-24.28| focal| riscv64
   linux-libc-dev | 5.4.0-26.30| focal| amd64, arm64, armhf, 
i386, ppc64el, s390x
   linux-libc-dev | 5.4.0-26.30| groovy   | amd64, arm64, armhf, 
i386, ppc64el, s390x
   linux-libc-dev | 5.4.0-27.31| groovy   | riscv64
   linux-libc-dev | 5.4.0-28.32| focal-security   | riscv64
   linux-libc-dev | 5.4.0-28.32| focal-updates| riscv64
   linux-libc-dev | 5.4.0-40.44| focal-security   | amd64, arm64, armhf, 
i386, ppc64el, s390x
   linux-libc-dev | 5.4.0-40.44| focal-updates| amd64, arm64, armhf, 
i386, ppc64el, s390x
   linux-libc-dev | 5.4.0-40.44| groovy-proposed  | amd64, arm64, armhf, 
i386, ppc64el, s390x

  This is broken.

  linux-libc-dev must have identical content for common files, across
  all architectures, and must have identical version number.

  A few ways to fix this:

  * Either enforce that src:linux & src:linux-riscv are at the same
  version number. But then reasons for splitting riscv into a separate
  build dissappear

  * Make src:linux build _just_ the headers linux-libc-dev for risv64,
  and nothing else. And stop bulding linux-libc-dev form the src:linux-
  riscv package. Just like it does for i386.

  * Or create new src:linux-headers that only builds linux-libc-dev for
  all architectures, without building any kernels. This way for example,
  we could rev userspace headers to v5.8/v5.9 ahead of said kernel
  landing, to shake out build-failures / userspace issues, whilst the
  kernel itself is still baking in bootstrap/proposed PPA.

  This must be address in Focal and Groovy

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886188/+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 1886188] Re: linux-libc-dev broken for crossbuilding, Multi-Arch:same violation

2020-07-03 Thread Dimitri John Ledkov 
Should kernel team even own linux-libc-dev ? Maybe foundations should
hijack linux-libc-dev away from kernel team, and let us handle it?

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

Title:
  linux-libc-dev broken for crossbuilding, Multi-Arch:same violation

Status in linux package in Ubuntu:
  Incomplete
Status in linux-riscv package in Ubuntu:
  New
Status in linux source package in Focal:
  Incomplete
Status in linux-riscv source package in Focal:
  New
Status in linux source package in Groovy:
  Incomplete
Status in linux-riscv source package in Groovy:
  New

Bug description:
  # apt install linux-libc-dev:amd64 linux-libc-dev:riscv64
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  linux-libc-dev is already the newest version (5.4.0-26.30).
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   linux-libc-dev : Breaks: linux-libc-dev:riscv64 (!= 5.4.0-26.30) but 
5.4.0-27.31 is to be installed
   linux-libc-dev:riscv64 : Breaks: linux-libc-dev (!= 5.4.0-27.31) but 
5.4.0-26.30 is to be installed
  E: Unable to correct problems, you have held broken packages.

  $ rmadison -S linux-libc-dev | grep -e riscv64 -e amd64 | grep -e focal -e 
groovy
   linux-libc-dev | 5.4.0-24.28| focal| riscv64
   linux-libc-dev | 5.4.0-26.30| focal| amd64, arm64, armhf, 
i386, ppc64el, s390x
   linux-libc-dev | 5.4.0-26.30| groovy   | amd64, arm64, armhf, 
i386, ppc64el, s390x
   linux-libc-dev | 5.4.0-27.31| groovy   | riscv64
   linux-libc-dev | 5.4.0-28.32| focal-security   | riscv64
   linux-libc-dev | 5.4.0-28.32| focal-updates| riscv64
   linux-libc-dev | 5.4.0-40.44| focal-security   | amd64, arm64, armhf, 
i386, ppc64el, s390x
   linux-libc-dev | 5.4.0-40.44| focal-updates| amd64, arm64, armhf, 
i386, ppc64el, s390x
   linux-libc-dev | 5.4.0-40.44| groovy-proposed  | amd64, arm64, armhf, 
i386, ppc64el, s390x

  This is broken.

  linux-libc-dev must have identical content for common files, across
  all architectures, and must have identical version number.

  A few ways to fix this:

  * Either enforce that src:linux & src:linux-riscv are at the same
  version number. But then reasons for splitting riscv into a separate
  build dissappear

  * Make src:linux build _just_ the headers linux-libc-dev for risv64,
  and nothing else. And stop bulding linux-libc-dev form the src:linux-
  riscv package. Just like it does for i386.

  * Or create new src:linux-headers that only builds linux-libc-dev for
  all architectures, without building any kernels. This way for example,
  we could rev userspace headers to v5.8/v5.9 ahead of said kernel
  landing, to shake out build-failures / userspace issues, whilst the
  kernel itself is still baking in bootstrap/proposed PPA.

  This must be address in Focal and Groovy

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886188/+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 1886188] Re: linux-libc-dev broken for crossbuilding, Multi-Arch:same violation

2020-07-03 Thread Matthias Klose 
to avoid that, please build linux-libc-dev from a separate source
package.  That would also allow providing an early user space package,
while the various linux packages are still in the works

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

Title:
  linux-libc-dev broken for crossbuilding, Multi-Arch:same violation

Status in linux package in Ubuntu:
  New
Status in linux-riscv package in Ubuntu:
  New
Status in linux source package in Focal:
  New
Status in linux-riscv source package in Focal:
  New
Status in linux source package in Groovy:
  New
Status in linux-riscv source package in Groovy:
  New

Bug description:
  # apt install linux-libc-dev:amd64 linux-libc-dev:riscv64
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  linux-libc-dev is already the newest version (5.4.0-26.30).
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   linux-libc-dev : Breaks: linux-libc-dev:riscv64 (!= 5.4.0-26.30) but 
5.4.0-27.31 is to be installed
   linux-libc-dev:riscv64 : Breaks: linux-libc-dev (!= 5.4.0-27.31) but 
5.4.0-26.30 is to be installed
  E: Unable to correct problems, you have held broken packages.

  $ rmadison -S linux-libc-dev | grep -e riscv64 -e amd64 | grep -e focal -e 
groovy
   linux-libc-dev | 5.4.0-24.28| focal| riscv64
   linux-libc-dev | 5.4.0-26.30| focal| amd64, arm64, armhf, 
i386, ppc64el, s390x
   linux-libc-dev | 5.4.0-26.30| groovy   | amd64, arm64, armhf, 
i386, ppc64el, s390x
   linux-libc-dev | 5.4.0-27.31| groovy   | riscv64
   linux-libc-dev | 5.4.0-28.32| focal-security   | riscv64
   linux-libc-dev | 5.4.0-28.32| focal-updates| riscv64
   linux-libc-dev | 5.4.0-40.44| focal-security   | amd64, arm64, armhf, 
i386, ppc64el, s390x
   linux-libc-dev | 5.4.0-40.44| focal-updates| amd64, arm64, armhf, 
i386, ppc64el, s390x
   linux-libc-dev | 5.4.0-40.44| groovy-proposed  | amd64, arm64, armhf, 
i386, ppc64el, s390x

  This is broken.

  linux-libc-dev must have identical content for common files, across
  all architectures, and must have identical version number.

  A few ways to fix this:

  * Either enforce that src:linux & src:linux-riscv are at the same
  version number. But then reasons for splitting riscv into a separate
  build dissappear

  * Make src:linux build _just_ the headers linux-libc-dev for risv64,
  and nothing else. And stop bulding linux-libc-dev form the src:linux-
  riscv package. Just like it does for i386.

  * Or create new src:linux-headers that only builds linux-libc-dev for
  all architectures, without building any kernels. This way for example,
  we could rev userspace headers to v5.8/v5.9 ahead of said kernel
  landing, to shake out build-failures / userspace issues, whilst the
  kernel itself is still baking in bootstrap/proposed PPA.

  This must be address in Focal and Groovy

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