Incidencia #44555

stub.serv not in the tarball

Abrir Fecha: 2022-05-10 10:13 Última actualización: 2022-05-12 22:05

Informador:
Propietario:
Tipo:
Estado:
Cerrado
Componente:
Prioridad:
5 - Medium
Gravedad:
5 - Medium
Resolución:
Fixed
Fichero:
6

Details

Mason build from a S3_1 tarball fails with: "ERROR: File data/stub.serv does not exist."

master no longer needs stub.serv, but data/Makefile.am there seems to do the same omission with stub.modpack.

Ticket History (3/13 Histories)

2022-05-10 10:13 Updated by: cazfi
  • New Ticket "stub.serv not in the tarball" created
2022-05-10 10:21 Updated by: cazfi
  • Propietario Update from (Ninguno) to cazfi
  • Resolución Update from Ninguno to Accepted
Comentario

Reply To cazfi

master no longer needs stub.serv, but data/Makefile.am there seems to do the same omission with stub.modpack.

Actually it needs both (.serv & .modpack) in case of stub ruleset.

2022-05-10 10:35 Updated by: cazfi
Comentario

- New version for S3_1, where the file added to SRV_RE_FILES was not automatically added also to EXTRA_DIST. Changed EXTRA_DIST to contain all of SRV_RE_FILES instead of each and every member separately.

2022-05-10 10:48 Updated by: cazfi
  • Resolución Update from Accepted to Ninguno
Comentario

Actually I've been approaching this wrong way altogether. We've intentionally left stub.serv (and .modpack) out from the release, so that it would not appear in the ruleset list of a release build client. The bug is that meson build tries to make it available.

2022-05-10 11:01 Updated by: cazfi
  • Resolución Update from Ninguno to Accepted
Comentario

Reply To cazfi

The bug is that meson build tries to make it available.

Largely untested patches attached.

2022-05-11 02:14 Updated by: cazfi
Comentario

- New master version where also the stub.modpack change in meson.build

2022-05-12 22:05 Updated by: cazfi
  • Estado Update from Open to Cerrado
  • Resolución Update from Accepted to Fixed

Editar

Please login to add comment to this ticket » Entrar