Part of lp.soyuz.interfaces.queue View In Hierarchy
Stores anything else than source and binaries that needs publication. It is essentially a map between DistroSeries/Pocket/LibrarianFileAlias. The LibrarianFileAlias usually is a TGZ containing an specific format. Currently we support: [Debian-Installer, Rosetta-Translation, Dist-Upgrader, DDTP-Tarball] Each one has an processor which is invoked by the publish method.
Int | id | Undocumented |
Int | packageupload | Undocumented |
Int | customformat | Undocumented |
Int | libraryfilealias | Undocumented |
Method | publish | Publish this custom item directly into the filesystem. |
Method | publishDebianInstaller | Publish this custom item as a raw installer tarball. |
Method | publishDistUpgrader | Publish this custom item as a raw dist-upgrader tarball. |
Method | publishDdtpTarball | Publish this custom item as a raw ddtp-tarball. |
Method | publishRosettaTranslations | Publish this custom item as a rosetta tarball. |
Method | publishStaticTranslations | Publish this custom item as a static translations tarball. |
Method | publishMetaData | Publish this custom item as a meta-data file. |
This can only be run by a process which has filesystem access to the archive (or wherever else the content will go).
If a logger is provided, information pertaining to the publishing process will be logged to it.
This will write the installer tarball out to the right part of the archive.
If a logger is provided, information pertaining to the publishing process will be logged to it.
This will write the dist-upgrader tarball out to the right part of the archive.
If a logger is provided, information pertaining to the publishing process will be logged to it.
This will write the ddtp-tarball out to the right part of the archive.
If a logger is provided, information pertaining to the publishing process will be logged to it.
Essentially this imports the tarball into rosetta.
If a logger is provided, information pertaining to the publishing process will be logged to it.
This is currently a no-op as we don't publish these files, they only reside in the librarian for later retrieval using the webservice.
This method writes the meta-data custom file to the archive in the location matching this schema: /<person>/meta/<ppa_name>/<filename>
It's not written to the main archive location because that could be protected by htaccess in the case of private archives.