public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jani Hautakangas <jani.hautakangas@kodegood.com>
To: isar-users <isar-users@googlegroups.com>
Subject: Problem upgrading libpng to 1.6.45 (with APNG) on arm64 builds
Date: Wed, 20 Aug 2025 12:45:26 -0700 (PDT)	[thread overview]
Message-ID: <cd18d3b6-6148-4142-ad13-67b3f1c6d99cn@googlegroups.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2335 bytes --]

Hello all,

I am trying to upgrade libpng_1.6.39 in a Debian Bookworm–based image.
My goal is to get APNG support and a few newer APIs, so I patched libpng
1.6.45 with APNG support and want it to replace the default 1.6.39.

What I did:

* Added a recipe libpng1.6_1.6.45 (with APNG patch).

* All recipes that need it have DEPENDS on libpng1.6_1.6.45 and also
  DEBIAN_DEPENDS/DEBIAN_BUILD_DEPENDS set to libpng (>= 1.6.45).

* Pinned my local Isar repo for libpng* packages in apt conf.

* Set PREFERRED_VERSION_libpng1.6 = "1.6.45".

Results:

* On amd64 builds everything works fine: the new libpng is built, packaged, 
and
  installed.

* On arm64 builds (e.g. rpi5), libpng 1.6.45 is also built and packaged 
fine,
  but system build fails when installing dependencies.

The error always looks like this (excerpt):

The following packages have unmet dependencies:
 libgdk-pixbuf-2.0-0 : Depends: libpng16-16 (>= 1.6.2-1) but it is not 
installable

Or, in the longer resolver log:

sbuild-build-depends-main-dummy:arm64 : Depends: libpng-dev:arm64 (>= 
1.6.45) but it is not going to be installed
...
libgdk-pixbuf-2.0-0 : Depends: libpng16-16 (>= 1.6.2-1) but it is not 
installable


It looks like cross builds handle dependencies differently, and the resolver
doesn’t see my locally built libpng16-16 as satisfiable on arm64 (while 
amd64 works fine).
I verified that the arm64 package itself is fine — when I install it 
manually on an
rpi5 Bookworm image, it installs and works correctly — so the issue seems 
to be
somewhere in Isar’s dependency resolution.

Question:
Has anyone successfully replaced a system library like libpng with a newer 
version on
cross builds in Isar? Is there something extra I need to do so that the 
resolver picks
up my libpng16-16 (1.6.45) package instead of failing with “not 
installable”?

Any hints would be greatly appreciated.

Best regards,
 Jani

-- 
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/cd18d3b6-6148-4142-ad13-67b3f1c6d99cn%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 2791 bytes --]

                 reply	other threads:[~2025-08-20 20:09 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cd18d3b6-6148-4142-ad13-67b3f1c6d99cn@googlegroups.com \
    --to=jani.hautakangas@kodegood.com \
    --cc=isar-users@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox