Your message dated Fri, 4 Apr 2025 22:32:37 +1100
with message-id <[email protected]>
and subject line Re: Bug#1101982: libfreetype-dev: freetype2.pc issue with
bzip2 vs bzip3
has caused the Debian Bug report #1101982,
regarding libfreetype-dev: freetype2.pc issue with bzip2 vs bzip3
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1101982: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1101982
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libfreetype-dev
Version: 2.13.3+dfsg-1
Severity: normal
X-Debbugs-Cc: [email protected]
Dear maintainers
When trying to build some package, I ran into the following, which I
think is a bug in libfreetype-dev.
1. some package uses freetype2.pc fails to configure.
2. The config.log reveals problem about missing bzip2.pc
3. $ find /usr/ -name freetype2.pc
/usr/lib/x86_64-linux-gnu/pkgconfig/freetype2.pc
4. $ dpkg -S /usr/lib/x86_64-linux-gnu/pkgconfig/freetype2.pc
libfreetype-dev:amd64: /usr/lib/x86_64-linux-gnu/pkgconfig/freetype2.pc
5. $ grep bzip2 /usr/lib/x86_64-linux-gnu/pkgconfig/freetype2.pc
Requires.private: zlib, bzip2, libpng, libbrotlidec
6. # apt install libbzip2-dev
Error: Unable to locate package libbzip2-dev
7. # apt install libbzip3-dev
[..] OK.
It appears to that libbzip has undergone a version bump that was missed
in freetype2.pc. I could build some package in question after tweaking
the pc files to use bzip3 instead. I did not investigate any further
though.
Best wishes
felix
-- System Information:
Debian Release: trixie/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.12.5-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to en_US.utf8), LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled
Versions of packages libfreetype-dev depends on:
ii libbrotli-dev 1.1.0-2+b4
ii libbz2-dev 1.0.8-5+b1
ii libc6-dev [libc-dev] 2.40-6
ii libfreetype6 2.13.3+dfsg-1
ii libpng-dev 1.6.47-1.1
ii zlib1g-dev [libz-dev] 1:1.2.13.dfsg-3
libfreetype-dev recommends no packages.
Versions of packages libfreetype-dev suggests:
pn freetype2-doc <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
On 4/04/2025 7:29 pm, Felix Salfelder wrote:
Dear Hugh.
On Fri, Apr 04, 2025 at 11:18:36AM +1100, Hugh McMaster wrote:
libbz2-dev is a dependency of libfreetype-dev. libbz2-dev also installs the
pkg-config file bzip2.pc in /usr/share/pkgconfig/bzip2.pc.
[..]
If libbz2-dev is not installed, then your system is misconfigured.
I missed libbz2-dev, because I had expected a package name like
libbzip2-dev. In retrospect, libbzip3-dev got me on the wrong track.
Anyhow, bumping the package fixes all problems.
# apt install libbz2-dev
[..]
Preparing to unpack .../libbz2-dev_1.0.8-6_amd64.deb ...
Unpacking libbz2-dev:amd64 (1.0.8-6) over (1.0.8-5+b1) ...
[..]
$ find /usr/ -name bzip2.pc
/usr/share/pkgconfig/bzip2.pc
(now everything is working as expected)
Excellent.
Clearly the libbz2-dev upgrade was missed, which may be due to
misconfiguration. I wonder how to avoid such misconfiguration, since I
do not remember having configured much.
Trying to reproduce...
# apt install libbz2-dev=1.0.8-5+b1
[..]
Unsatisfied dependencies:
libbz2-dev : Depends: libbz2-1.0 (= 1.0.8-5+b1) but 1.0.8-6 is to be
installed
Error: Unable to correct problems, you have held broken packages.
# apt install libbz2-dev=1.0.8-5+b1 libbz2-1.0=1.0.8-5+b1
[..]
# find /usr/ -name bzip2.pc
(nothing)
What should have triggered the upgrade? Does this not indicate the need
of a dependency on a more recent libbz2-dev in libfreetype-dev?
Your system was using bzip2 1.0.8-5, the second most recent version.
Debian started shipping bzip pkg-config files in 1.0.8-6, released in
August 2024. It's strange that your system did not get the updated package.
Previously, packages linking with freetype would check for and linked
against bzip2 manually. That's no longer necessary, with bzip2 finally
adding support for pkg-config.
If this is considered "normal" in testing, please feel free to close the
bug.
Closing. Thanks for filing this bug and checking in.
Hugh
--- End Message ---
