Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

qmmp: UI translations missing due to post_patch removing .qm files

Abierto Apto para principiantes
#63,041 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
82/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
cmake, shell
Área
build-system

Línea de trabajo

El problema está en la función post_patch() de srcpkgs/qmmp/template, que elimina las referencias a .qm de los archivos .qrc bajo src. Lee esa función y el campo revision, y luego comprueba si la compilación con CMake y Qt6LinguistTools genera los archivos .qm una vez eliminada esa parte. Está terminado cuando ./xbps-src pkg qmmp se completa correctamente y el paquete generado contiene archivos .qm en /usr/share/qmmp/translations, con el revision incrementado.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

AI 🤖 bug needs-testing
Is this a new report?

Yes

System Info

Void x86_64 glibc Linux 6.16.56

Package(s) Affected

qmmp 2.4.2_1

Does a report exist for this bug with the project's home (upstream) and/or another distro?

Description

qmmp package (version 2.4.2_1) does not load any translation. The language selector in Settings -> Appearance -> Language lists all supported languages, but selecting any language other than English (e.g. it, es, fr, de) has no effect. After restart, the UI remains in English.

Reproduction

  1. xbps-install qmmp
  2. Open qmmp (simple UI)
  3. Go to Settings -> Appearance -> Language
  4. Select Italiano or Español
  5. Click OK and restart qmmp

Expected: UI in Italian/Spanish
Actual: UI still in English

Checked with strings on binary and inside /usr/share/qmmp/translations - no .qm files are installed. Qt translation loader fails silently.

Root Cause

In srcpkgs/qmmp/template:

# Remove references to prebuilt Qt translation files (.qm) that are
# missing from the source tarball and not generated by the CMake build.
post_patch() {
	find src -name "*.qrc" -exec sed -i '/\.qm/d' {} +
}

## Fix

Remove post_patch() entirely. qt6-tools is already in hostmakedepends, CMake with Qt6LinguistTools will generate .qm from .ts.

Tested locally:
- Removed post_patch
- revision=1 -> revision=2
- ./xbps-src pkg qmmp
- Translations it/es now work.

Suggested diff:
- revision=1
+ revision=2
- post_patch() { find src -name "*.qrc" -exec sed -i '/\.qm/d' {} + }

### Expected behaviour

When I select a language (e.g. Italian, Spanish) in Settings -> Appearance -> Language and restart qmmp, the UI should be translated to that language. The package should include the compiled .qm translation files.

### Actual behaviour

Selecting any language other than English has no effect. The UI always stays in English after restart. 

The template contains:

post_patch() {
    find src -name "*.qrc" -exec sed -i '/\.qm/d' {} +
}

This removes all .qm file references from the .qrc resources because upstream tarball doesn't ship prebuilt .qm files. As a result, no translations are built or installed, even though qt6-tools (which provides lrelease) is already in hostmakedepends and CMake would generate them correctly if not deleted.

Steps to reproduce:
1. xbps-install qmmp
2. Settings -> Appearance -> Language -> select Italiano
3. Restart qmmp
4. UI still in English

### Steps to reproduce

1. Install qmmp: `sudo xbps-install -S qmmp`
2. Open qmmp (simple UI is default)
3. Go to Settings -> Appearance (or Ctrl+P -> Appearance)
4. In Language dropdown, select Italiano [it] or Español [es]
5. Click OK and restart qmmp when prompted
6. Observe: UI is still in English, not translated
Lenguaje dominante
Shell
Estrellas
3.5k
Forks
2.8k
Merge medio
1 d 9 h
PR fusionados (30 d)
300

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de void-linux/void-packages

Todos los issues de void-linux/void-packages

Issues similares

Más issues de Shell/Bash

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.