Skip to content
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.

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

upgrading bor-*-*-config_v*.deb deletes provided files #946

Closed
etam opened this issue Aug 2, 2023 · 2 comments
Closed

upgrading bor-*-*-config_v*.deb deletes provided files #946

etam opened this issue Aug 2, 2023 · 2 comments

Comments

@etam
Copy link

etam commented Aug 2, 2023

System information

Bor client version: 0.4.0

Heimdall client version: not relevant

OS & Version: Linux Ubuntu 20.04

Environment: Polygon Mainnet

Type of node: Sentry

Overview of the problem

The postrm script in bor-mainnet-sentry-config_v0.4.0-amd64.deb deletes files managed by dpkg.

Reproduction Steps

  • Install latest 0.3.* config package (for example dpkg -i bor-mainnet-sentry-config_v0.3.9-amd64.deb)
  • Update to 0.4.0 (dpkg -i bor-mainnet-sentry-config_v0.4.0-amd64.deb)

Logs / Traces / Output / Error Messages

The result is that files

  • /lib/systemd/system/bor.service
  • /var/lib/bor/config.toml

do not exist

Additional Information

The bor-mainnet-sentry-config_v0.4.0-amd64.deb package contains a postrm script that contains

sudo rm -rf /var/lib/bor/config.toml
sudo rm -rf /lib/systemd/system/bor.service

Those files are provided by the package itself and are managed by dpkg.

The man dpkg under -i, --install package-file... says

  1. Unpack the new files [...]
  2. If another version of the same package was installed before the new installation, execute the postrm script of the old package. [...]

So when upgrading the package:

  • dpkg unpacks the files
  • the postrm script deletes them
@cffls
Copy link
Contributor

cffls commented Aug 10, 2023

Hi @etam , thanks for reporting this. The issue will be fixed by this PR: #951

@0xsharma
Copy link
Member

This issue was fixed in #951 .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants
@etam @0xsharma @cffls and others