Arch Linux User Repository

if we are ever more than 1 day out of date - its best to notify me by opening an issue here - https://github.com/erigontech/erigon-pkg

the script which updates both this repo & erigon-bin runs every 4 hours, so if it misses an update, it is probably due to a bug somewhere.

thanks.

thanks for reporting outdated. (2.60.7)

im working with the team to either unarchive the repo, or i will fork the repo to a different account and continue running the pipelines there.

regardless, i will try to get this resolved by the end of the month. sorry for the inconvenience.

update- it should be good now

if we are ever more than 1 day out of date - its best to notify me by opening an issue here - https://github.com/erigontech/erigon-pkg

the script which updates both this repo & erigon-bin runs every 4 hours, so if it misses an update, it is probably due to a bug somewhere.

thanks.

Watch out 2.53 is out of date.

This is included is 2.54 release note : Attention Polygon users: You must upgrade to this release or higher before the Agra Hardfork at block 50523000 (Nov 28).

As long as https://github.com/ledgerwatch/erigon/issues/7984 is not solved, you should keep go-2:1.20.7-1-x86_64.pkg.tar.zst somewhere and run sudo pacman -U go-2:1.20.7-1-x86_64.pkg.tar.zst before building erigon, and updating go (pacman -Syu) afterwards is OK. (running git_branch=master git_tag=v2.49.2 git_commit=817d9ee29d53, with no problem identified)

https://github.com/ledgerwatch/erigon/releases/tag/v2.42.0 is needed for compatibility with Lighthouse after their v4

Anyone here planning to create erigon-bin? I will probably do it in a few days if nobody else has.

@xrchz When there are binaries upstream, it is typical to have the following:

• $pkg downloads the source and compiles the binaries
• $pkg-bin downloads the binary and simply installs them

An example of this can be found with ungoogled-chromium-bin and ungoogled-chromium.

As such, this package should continue to download the source, and a new erigon-bin AUR package should be created which downloads the binaries.

v2.39.0 introduces binary releases, so should we switch to that here, or make another package for the binary version?

This is now two releases out of date (https://github.com/ledgerwatch/erigon/releases/tag/v2.32.0)

With the recent change of versioning scheme from YYYY.mm.int to (what appears to be) semver, you need to set epoch=1 in the PKGBUILD; otherwise, the checks for upgrade will not update since 2022.X.Y is deemed 'newer' than 2.27.0.