Change Details

To upload packages to the PureOS archive via the dput tool, use the following `~/.dput.cf` snippet: ``` [pureos-ftp] fqdn = upload.pureos.net method = ftp incoming = ~/incoming/ login = anonymous ``` The upload might take about 20 minutes or so to be processed after the upload is fully complete. See also [[ https://tracker.pureos.net/w/development/new_queue/ | NEW queue ]] and [[ https://tracker.pureos.net/w/development/pureos_archive_layout/ | archive layout ]] If you want to get notification about any new upload that gets submitted to the archive, consider subscribing to the [[ https://lists.puri.sm/listinfo/pureos-changes | pureos-changes ]] mailinglist. Please use source-only uploads (created by passing `-S -sa` to dpkg-buildpackage, e.g. by using `gbp` via `gbp buildpackage -S -sa`) if possible, and only upload binaries directly if absolutely necessary (e.g. for bootstrapping). The autobuild system of the Laniakea archive management system will usually build new packages pretty quickly. Uploads targeted at the current development release of PureOS (currently `byzantium`) will automatically be redirected to `landing`, just like uploads to the `*-updates` suite of a stable release will automatically go to `*-proposed-updates` first. # Tracing the package after the upload * If the package gets accepted a mail is sent to the [pureos-changes mailing list](https://lists.puri.sm/listinfo/pureos-changes) * If the package didn't have any version in the archive before it will be held in [NEW](https://master.pureos.net/raw/web/new.html). If a package is listed there it will need manual processing from one of the archive maintainers. * In case of a source package a build for the binary packages will be scheduled and put to the end of the [build queue](https://master.pureos.net/jobs/queue/1). * If the package got built successfully it will [wait for migration](https://master.pureos.net/migrations/) * The status of a package in a certain suite (including build logs can queried via `https://software.pureos.net/package/src/<suite>/<sourcepackage>`. e.g. for [phosh](https://software.pureos.net/package/src/byzantium/phosh) * Once the (suite dependent) migration period passes it will migrate to the target suite.

To upload packages to the PureOS archive via the dput tool, use the following `~/.dput.cf` snippet: ``` [pureos-ftp] fqdn = upload.pureos.net method = ftp incoming = ~/incoming/ login = anonymous ``` The upload might take about 20 minutes or so to be processed after the upload is fully complete. See also [[ https://tracker.pureos.net/w/development/new_queue/ | NEW queue ]] and [[ https://tracker.pureos.net/w/development/pureos_archive_layout/ | archive layout ]] If you want to get notification about any new upload that gets submitted to the archive, consider subscribing to the [[ https://lists.puri.sm/listinfo/pureos-changes | pureos-changes ]] mailinglist. Please use source-only uploads (created by passing `-S -sa` to dpkg-buildpackage, e.g. by using `gbp` via `gbp buildpackage -S -sa`) if possible, and only upload binaries directly if absolutely necessary (e.g. for bootstrapping). The autobuild system of the Laniakea archive management system will usually build new packages pretty quickly. Uploads targeted at the current development release of PureOS (currently `byzantium`) will automatically be redirected to `landing`, just like uploads to the `*-updates` suite of a stable release will automatically go to `*-proposed-updates` first. # Tracing the package after the upload * If the package gets accepted a mail is sent to the [pureos-changes mailing list](https://lists.puri.sm/listinfo/pureos-changes) * If the package didn't have any version in the archive before it will be held in [NEW](https://master.pureos.net/raw/web/new.html). If a package is listed there it will need manual processing from one of the archive maintainers. * In case of a source package a build for the binary packages will be scheduled and put to the end of the [build queue](https://master.pureos.net/jobs/queue/1). * If the package got built successfully it will [wait for migration](https://master.pureos.net/migrations/) * The status of a package in a certain suite (including build logs can queried via `https://software.pureos.net/package/src/<suite>/<sourcepackage>`. Example: phosh's status in byzantium: https://software.pureos.net/package/src/byzantium/phosh * Once the (suite dependent) migration period passes it will migrate to the target suite.

To upload packages to the PureOS archive via the dput tool, use the following `~/.dput.cf` snippet: ``` [pureos-ftp] fqdn = upload.pureos.net method = ftp incoming = ~/incoming/ login = anonymous ``` The upload might take about 20 minutes or so to be processed after the upload is fully complete. See also [[ https://tracker.pureos.net/w/development/new_queue/ | NEW queue ]] and [[ https://tracker.pureos.net/w/development/pureos_archive_layout/ | archive layout ]] If you want to get notification about any new upload that gets submitted to the archive, consider subscribing to the [[ https://lists.puri.sm/listinfo/pureos-changes | pureos-changes ]] mailinglist. Please use source-only uploads (created by passing `-S -sa` to dpkg-buildpackage, e.g. by using `gbp` via `gbp buildpackage -S -sa`) if possible, and only upload binaries directly if absolutely necessary (e.g. for bootstrapping). The autobuild system of the Laniakea archive management system will usually build new packages pretty quickly. Uploads targeted at the current development release of PureOS (currently `byzantium`) will automatically be redirected to `landing`, just like uploads to the `*-updates` suite of a stable release will automatically go to `*-proposed-updates` first. # Tracing the package after the upload * If the package gets accepted a mail is sent to the [pureos-changes mailing list](https://lists.puri.sm/listinfo/pureos-changes) * If the package didn't have any version in the archive before it will be held in [NEW](https://master.pureos.net/raw/web/new.html). If a package is listed there it will need manual processing from one of the archive maintainers. * In case of a source package a build for the binary packages will be scheduled and put to the end of the [build queue](https://master.pureos.net/jobs/queue/1). * If the package got built successfully it will [wait for migration](https://master.pureos.net/migrations/) * The status of a package in a certain suite (including build logs can queried via `https://software.pureos.net/package/src/<suite>/<sourcepackage>`. e.g. for [Example: phosh]('s status in byzantium: https://software.pureos.net/package/src/byzantium/phosh) * Once the (suite dependent) migration period passes it will migrate to the target suite.