In the following text, replace
applications, depending on what you are building. Replace
$VERSION with the version you wish to build. Replace
$REPOSITORY with the git repository in which
$PRODUCT is located.
See Package chains for information about
For each (combined) release, create a milestone in Chakra › Packages:
- Title: "Frameworks
$VERSION, and Applications
## rsync.chakralinux.org * [ ] Run `pacman-clean-repo -r testing` to remove any packages that aren't in the database * [ ] Include the output of `find /srv/www/rsync.chakralinux.org/packages/testing/x86_64 -type f -name "*.xz" -printf "%f\n" | sort -t \0` in the __#draft__ topic * [ ] [Move](https://code.chakralinux.org/chakra/chakrabuildsystem/wikis/Installation-and-usage#move-a-package-on-rsyncchakralinuxorg) from `[testing]` to stable ## community.chakralinux.org * [ ] Write and complete a __#draft__ 48 hours prior to move, to give translators enough time to translate * [ ] Publish __#draft__ topic to __#news__ (with the __#curated__ tag if it is to show up on planet.kde.org) * [ ] Verify that the RSS feed was fetched by planet.kde.org ## Social networks * [ ] [Reddit](https://www.reddit.com/r/chakra/) * [ ] [Twitter](https://twitter.com/chakralinux) (with the __#chakralinux__ and __#kde__ hashtags)
- Start date: First tagging (pre-release) date
- Due date: Final release date
For each of the three products, submit a new issue in the corresponding project with:
- Title: "
- Description: "Tars available as of YYYY-MM-DD. Public release on YYYY-MM-DD."
- Label: "Outdated package"
- Due date: Release date
$ rm -r ~/chakrabuildsystem/chakra/_sources/*
Download the source tarballs and signatures into your
_sources directory, or copy them from
/srv/archives if you are using our build server:
$ cp -r /srv/archives/kde/$PRODUCT/$VERSION/* ~/chakrabuildsystem/chakra/_sources
Generate the checksums, and redirect the output to a
$ sha256sum ~/chakrabuildsystem/chakra/_sources/*.tar.xz > ~/chakrabuildsystem/chakra/core/$PRODUCT.sums
Enter the chroot:
$ cd ~/chakrabuildsystem $ ./enter_chroot.sh $REPOSITORY
$PRODUCT.conf with a text editor (e.g.
nano) and set
Version to its new value. Reset the
$ pkgrels_reset.sh $PRODUCT.order
Insert the new checksums into each PKGBUILD, either manually or using
$ update_kde_pkgbuilds.sh $PRODUCT
Build the group using
$ build.sh $PRODUCT.order
If something fails and you want to run the build again, edit
$PRODUCT.order and comment out any lines with packages that were successfully built, so you can start the new build from the package that failed.