Skip to content

build(acbr): as libs publicadas passam a levar os patches locais #23

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
rodrigofs merged 1 commit into from
Sep 16, 2026
Merged

build(acbr): as libs publicadas passam a levar os patches locais #23

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion Makefile
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ ACBR_FRCE_REF ?= 9c29ee7152a6293d3920ff44a2bf3cd384d7b081
# próprio: a aba de Releases passa a ter só versões deste serviço. O arquivo
# revisao.txt vai junto dos .so e precisa bater com ACBR_REV, senão o download
# recusa: sem o nome da revisão na tag, nada mais amarraria as duas coisas.
ACBR_LIBS_RELEASE ?= v1.1.0
ACBR_LIBS_RELEASE ?= v1.3.0
OUT := out
PKGS := ./...
ACBRLIBS ?= ./acbr-libs
Expand Down
6 changes: 6 additions & 0 deletions docs/ACBRLIB.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -108,6 +108,12 @@ Isso importa na hora de trocar a `.so`. Compilada **sem** os patches, a lib
aceita o mesmo INI e descarta em silêncio as chaves da primeira linha: a nota
sai, e sai errada.

As `.so` anexadas ao release v1.3.0 são a r48100 compilada com estes três
patches, e a imagem as usa a partir da v1.3.1. O `revisao.txt` continua dizendo
só `48100`, porque o download compara esse valor exato: o que distingue esses
binários dos oficiais é o `SHA256SUMS` do release e o conteúdo de
`docker/acbr-patches/` na tag.

O gate de lockstep não protege contra isso, e é bom saber por quê. O
`acbr-source/` em disco é o fonte **sem** os patches, que só existem dentro do
container de build, e o `scripts/gerar-chaves-lerini.py` extrai seção e chave
Expand Down