Make libutfcpp-dev arch-indep to allow dependent package i386 builds

Bug #1932094 reported by Rob Savoury
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
utfcpp (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Due libutfcpp-dev from utfcpp source being architecture dependent and not on the Launchpad i386 whitelist other software that depends on libutfcpp-dev cannot build i386 binaries for Focal and newer series. This includes software that is on the i386 whitelist such as taglib, which as of version 1.12~beta (currently in Debian experimental) build-depends on libutfcpp-dev.

Various other software on the i386 whitelist such as VLC then build-depends on libtag1-dev from taglib source. So for example the future builds once taglib 1.12 has been released to Debian/Ubuntu archives will require libutfcpp-dev be arch-independent to allow successful builds of i386 binaries of other dependent packages. As utfcpp provides four headers only there should be no issue with making libutfcpp-dev arch-independent.

Revision history for this message
Boyuan Yang (hosiet) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package utfcpp - 3.2.5-1

---------------
utfcpp (3.2.5-1) unstable; urgency=medium

  * New upstream release.
  * debian/control: Mark binary packages as arch:all and M-A: foreign
    since architecture-independent build is supported in this project
    since CMake 3.14. (LP: #1932094)
  * debian/rules: Do not explicitly disable tests anymore.
  * debian/patches/0001-Add-back-vendor-ftest-test-framework.patch:
    Add back upstream-vendored ftest test framework (as git submodule)
    as a patch to allow post-build testing.
  * debian/patches/:
    + 0002-Install-CMake-files-to-arch-indep-location-when-ARCH.patch:
      Correctly install CMake files to arch-indep location when
      CMake files are architecture-independent.

 -- Boyuan Yang <email address hidden> Wed, 27 Sep 2023 14:57:50 -0400

Changed in utfcpp (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.