Version 1 vs 3
Version 1 vs 3
Edits
Edits
- Move Away by mladen, Version 3
- Jun 20 2017 09:40
- ·Place the article under its category
- Edit by mak, Version 1
- Mar 14 2017 15:13
Edit Older Version 1... |
Content Changes
Content Changes
= Prerequisites =
To build packages, install the `devscripts` package: `sudo apt install devscripts`, which contains a lot of useful helpers for building Debian packages.
Having `gbp` available is also a good idea: `sudo apt install git-buildpackage`
= Building packages ==
All packages have to be built in a pristine PureOS `landing` chroot before being uploaded to PureOS. The preferred method to do that is by using pbuilder.
For packages not managed in Git, pbuilder can be invoked via
```
DIST=landing pdebuild --auto-debsign
```
For Git-managed packages, `gbp` provides options to build with pbuilder directly. Alternatively, `pdebuild` can be passed in like `gbp buildpackage --git-builder='DIST=landing pdebuild --auto-debsign'`
= Validating packages =
Use `lintian -IE --pedantic <changes-file>` to check a package for compliance with the Debian policy. Ensure it is warning and error-free.
Currently, all warnings related to NMUs and invalid suites can be ignored, as those are different or don't exist in PureOS (Lintian does not know about the existence of PureOS yet).
= Prerequisites =
To build packages, install the `devscripts` package: `sudo apt install devscripts`, which contains a lot of useful helpers for building Debian packages.
Having `gbp` available is also a good idea: `sudo apt install git-buildpackage`
= Building packages ==
All packages have to be built in a pristine PureOS `landing` chroot before being uploaded to PureOS. The preferred method to do that is by using pbuilder.
For packages not managed in Git, pbuilder can be invoked via
```
DIST=landing pdebuild --auto-debsign
```
For Git-managed packages, `gbp` provides options to build with pbuilder directly. Alternatively, `pdebuild` can be passed in like `gbp buildpackage --git-builder='DIST=landing pdebuild --auto-debsign'`
= Validating packages =
Use `lintian -IE --pedantic <changes-file>` to check a package for compliance with the Debian policy. Ensure it is warning and error-free.
Currently, all warnings related to NMUs and invalid suites can be ignored, as those are different or don't exist in PureOS (Lintian does not know about the existence of PureOS yet).