mirror of
https://github.com/flatcar/scripts.git
synced 2026-05-04 11:51:14 +02:00
pkg-auto: Update README
This commit is contained in:
parent
04b78d9657
commit
7d72d5d8a0
@ -8,9 +8,6 @@ A quick start from blank state:
|
||||
- `cd scripts/main`
|
||||
- `PKG_AUTO="${PWD}/pkg_auto"`
|
||||
- `git worktree add --branch weekly-updates ../weekly-updates origin/buildbot/weekly-portage-stable-package-updates-2024-09-23`
|
||||
- if package automation is still not merged into the `main` branch then:
|
||||
- `git worktree add --branch pkg-auto ../pkg-auto origin/krnowak/pkg-auto`
|
||||
- `PKG_AUTO="${PWD}/../pkg-auto/pkg_auto"`
|
||||
- prepare for generating reports (create a directory, download necessary stuff, create config):
|
||||
- `mkdir ../../weekly-updates`
|
||||
- `cd ../../weekly-updates`
|
||||
@ -53,6 +50,8 @@ The entries in `changelog_stubs` should be reviewed about relevancy (minor SDK-o
|
||||
|
||||
There may be also entries in `manual-work-needed` which may need addressing. Most often the reason is that the new package was added, or an existing package stopped being pulled in. This would need adding an entry to the `summary_stubs`.
|
||||
|
||||
Another thing that to do is to check [the security reports](https://github.com/flatcar/Flatcar/issues?q=is%3Aopen+is%3Aissue+label%3Aadvisory). If the updated package brings a fix for a security issue, it should be mentioned in the summary and an entry in a separate security changelog should be added.
|
||||
|
||||
Other scripts
|
||||
=============
|
||||
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user