Lubuntu/new-release
8
0
Fork 0
mirror of https://github.com/lubuntu-team/new-release.git synced 2025-03-10 14:41:09 +00:00
Code Issues Packages Projects Releases Wiki Activity

Manually nuke obsolete packages.

Browse Source
This commit is contained in:
Simon Quigley 2019-10-17 14:11:48 -05:00
parent bd76ce0e76
commit 357eee20df
1 changed files with 1 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
README.md
View File

@ -49,6 +49,7 @@ After the codename is announced and `base-files` is uploaded:
1. Run [jobgenerator](https://ci.lubuntu.me/job/jobgenerator/) and then look over the builds triggered. Did you miss a step?
1. Add the new release to [the Britney job](https://ci.lubuntu.me/view/mgmt/job/Britney/configure) so builds can migrate.
1. SSH into the Jenkins container, `su` to the `jenkins` user, go to `~/jobs` and remove old jobs (e.g. from an old release), and in the Jenkins settings, `Reload Configuration from Disk`.
1. Manually review and clean up packages in the PPAs.
1. If `lintian` and `devscripts` have not been updated, cherry-pick the `lintian` patch adding the new release as known if there is one, and no-change rebuild `devscripts`.
1. Lintian needs a patch because all of the Ubuntu releases are hardcoded in `vendors/ubuntu/main/data/changes-file/known-dists`.
1. `devscripts` needs a no-change rebuild because it gets the value grabbed by `dch -r` on build time. This is in line 47 of `scripts/Makefile`.