[Wolfi Package Update]: libvips

Open Beginner friendly
#77,678 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
68/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
yaml
Domain
build-system

Research direction

Start with libvips.yaml, especially its packages list, and review the existing libvips package recipe. Build or install the package, then run vips --vips-config and verify that HEIC/AVIF support through libheif is enabled. Done means the package exposes libheif-backed HEIC/AVIF load and save support.

Written by the indexing model from the issue text.

Description

needs-triage
Package name

libvips

Current version in Wolfi

8.18.0

Requested version

No response

Upstream project URL

https://github.com/libvips/libvips

Problem

The current version of libvips provided by Wolfi does not support HEIC/AVIF.

Steps to reproduce
  1. apk add libvips

  2. vips --vips-config

  3. observe: HEIC/AVIF load/save with libheif: false (dynamic module: false)

Root cause (if known)

libheif-dev is not listed under https://github.com/wolfi-dev/os/blob/7fbf9714e4a58e5548c42162c3b2421400b7fc7d/libvips.yaml#L11-L22

Proposed solution

add libheif-dev to the packages list in libvips.yaml

Testing performed

No response

Acceptance criteria
  • The requested version is the latest stable upstream release (no pre-releases or RCs)
  • The upstream project uses an OSI-approved license
  • The change aligns with Wolfi’s packaging and security model
  • The package can be reasonably maintained over time
  • There are no known unresolved security or supply-chain concerns
Dominant language
Shell
Stars
1.3k
Forks
443
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from wolfi-dev/os

All issues in wolfi-dev/os

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.