[go: up one dir, main page]

Packaging: add [next] packages apt repository

pietrorequested to merge
nomadic-labs/tezos:abate@add-next-packages-repo into master

What

This MR makes available the NEXT packages through the apt repository.

Depends on !13669 (merged)

Depends on !13951 (merged) to fix a small problem with the next packages.

Why

to enable installation tests of these packages in the CI and prepare to release

How

I added a PREFIX variable in the create_repo.sh script and added a new job in the CI.

Manually testing the MR

On the CI check if the packages are pushed in the repository with the correct prefix ( next )

The packages can be also installed using the same procedure described here : !13420 (merged)

and making sure to specify the correct url including the `next prefix.

Ex:

curl "https://tezos-linux-repo.storage.googleapis.com/abate@add-next-packages-repo/next/debian/octez.asc" | sudo gpg --dearmor -o /etc/apt/trusted.gpg.d/octez.gpg
echo "deb [arch=amd64] https://tezos-linux-repo.storage.googleapis.com/abate@add-next-packages-repo/next/debian bookworm main" | sudo tee /etc/apt/sources.list.d/octez.list
sudo apt-get update
$ apt show octez-node
Package: octez-node
Version: 202407101056+e0171ac0
Priority: optional
Section: devel
Source: octez
Maintainer: Nomadic Labs <pkg@nomadic-labs.com>
Installed-Size: 467 MB
Depends: adduser, logrotate, octez-zcash-params, debconf (>= 0.5) | debconf-2.0, libc6 (>= 2.35), libev4 (>= 1:4.04), libgcc-s1 (>= 4.2), libgmp10 (>= 2:6.2.1+dfsg1), libstdc++6 (>= 10.2), zlib1g (>= 1:1.1.4)
Recommends: octez-client (= 202407101056+e0171ac0)
Suggests: lz4, curl
Homepage: https://gitlab.com/tezos/tezos
Download-Size: 81.5 MB
APT-Sources: https://tezos-linux-repo.storage.googleapis.com/abate@add-next-packages-repo/next/debian bookworm/main amd64 Packages
Description: The Octez node server

Checklist

  • Document the interface of any function added or modified (see the coding guidelines)
  • Document any change to the user interface, including configuration parameters (see node configuration)
  • Provide automatic testing (see the testing guide).
  • For new features and bug fixes, add an item in the appropriate changelog (docs/protocols/alpha.rst for the protocol and the environment, CHANGES.rst at the root of the repository for everything else).
  • Select suitable reviewers using the Reviewers field below.
  • Select as Assignee the next person who should take action on that MR
Edited by pietro

Merge request reports