Jump to content

Kubuntu/PPAs: Difference between revisions

From KDE Community Wiki
← Older editNewer edit →
Mparillo (talk | contribs)
16 edits
Valoriez (talk | contribs)
KDEDevelopers, Bureaucrats, spam-ninja, Administrators, trusted
498 edits
→Kubuntu's PPA Repositories: removed all unused PPAs and the CI system
Line 11: Line 11:
This is the official Ubuntu [https://help.ubuntu.com/community/UbuntuBackports Backports] repository. this ''unsupported'' channel mostly contains individual packages "backported' from a newer Ubuntu release, but will usually provide a minor KDE software "point" release if it provides significant bug fixes and stability.
This is the official Ubuntu [https://help.ubuntu.com/community/UbuntuBackports Backports] repository. this ''unsupported'' channel mostly contains individual packages "backported' from a newer Ubuntu release, but will usually provide a minor KDE software "point" release if it provides significant bug fixes and stability.


= Kubuntu's PPA Repositories =
Original Treatment
[[File:KubuntuPPAs.png]]
Proposed Alternative Treatment
[[File:KubuntuPPAs1.png]]
https://launchpad.net/~kubuntu-ppa


=== Kubuntu Updates ===
=== Kubuntu Updates ===
Line 22: Line 16:


Example:
Example:
Kubuntu Wily 15.10 users would be able to test out upgrading from Plasma 5.4 '''1''' to 5.4.'''2''' before those packages were moved to Ubuntu Updates.
Kubuntu Wily 15.10 users were able to test out upgrading from Plasma 5.4 '''1''' to 5.4.'''2''' before those packages were moved to Ubuntu Updates.


Use Case:
Use Case:
Line 42: Line 36:


Example:
Example:
Wily users would be able to try out upgrading Kubuntu Wily's Plasma from 5.'''4'''.x to 5.'''5'''.0 without having to wait for Xenial's release.
Wily users were able to try out upgrading Kubuntu Wily's Plasma from 5.'''4'''.x to 5.'''5'''.0 without having to wait for Xenial's release.


Use Case:
Use Case:
Line 57: Line 51:


sudo apt update && sudo apt full-upgrade -y
sudo apt update && sudo apt full-upgrade -y
=== Kubuntu Beta Backports ===
Backports of '''pre-release''' versions of KDE SC, Plasma and major KDE apps, not suitable for production environments but good for those wishing to help test upcoming KDE features and software.
Use Case:
* Any kind of pre-release that is suited for general testing
* Any kind of release that is expected to be imperfect and requires (more) testing
* Plasma alpha/beta/rc releases
* Amarok alpha/beta/rc releases
* Calligra alpha/beta/rc releases
* Note that backports also suites pre-release software that cannot be included in the current dev series (so for example if lucid is in feature freeze, kdevelop's unstable version would land for both karmic and lucid in beta-backports)
=== Kubuntu Experimental ===
Experimental software or experimental packages, not suitable for production environments nor for those wishing to help doing regular testing. This PPA should only be used by people who know how to recover a system and are well instructed by the developers.
Example:
The Kubuntu tool software-properties gets ported to C++, for initial testing it gets published to Kubuntu Experimental to ensure there are no grave issues that render sources.list unusable.
Use Case:
* Any kind of untested software that might break the system gravely
* Packages that might break the system gravely
* Anything that is endangering the user's system and does not fit any other PPA


=== Kubuntu Package Staging ===
=== Kubuntu Package Staging ===
Line 90: Line 62:
Use Case:
Use Case:
* Staging only (PPA must be cleaned first to ensure coherent stacks)
* Staging only (PPA must be cleaned first to ensure coherent stacks)
== Kubuntu Continuous Integration (CI) ==
[[Image:Kubuntu-ci.png]]
The Kubuntu CI system does builds from KDE Git master along with Kubuntu packaging.  It is useful for developing and testing KDE software as well as Kubuntu packaging.  ''It replaces Project Neon.''
For a more indepth description of KCI see: [https://www.youtube.com/watch?v=zhJQSpy3Luc Youtube link]
KCI supports Kubuntu versions after 14.10.
=== Weekly Snapshot (pretty stable) ===
[https://launchpad.net/~kubuntu-ci/+archive/ubuntu/unstable-weekly Kubuntu CI Unstable Weekly] packages from unstable-daily are moved here after manual weekly testing.  These packages are used to build the Kubuntu CI images.
To use this run:
<pre>
sudo add-apt-repository ppa:kubuntu-ci/unstable-weekly
sudo apt update
sudo apt install kubuntu-desktop
sudo apt dist-upgrade
</pre>
=== Daily Snapshot (somewhat stable) ===
[https://launchpad.net/~kubuntu-ci/+archive/ubuntu/unstable-daily Kubuntu CI Unstable Daily] daily builds of KDE Git master with Kubuntu packaging. Packages are moved here from unstable if they build properly, can be installed over the previous build and if they can be purged again. This makes daily a suitable choice for most people who are not afraid of the odd breakage every now and then.
To use this run:
<pre>
sudo add-apt-repository ppa:kubuntu-ci/unstable-daily
sudo apt update
sudo apt install kubuntu-desktop
sudo apt dist-upgrade
</pre>
=== Live (might eat kittens) ===
[https://launchpad.net/~kubuntu-ci/+archive/ubuntu/unstable Kubuntu CI Unstable] daily builds of KDE Git master, also updated every time Kubuntu packaging is updated. This is the closest you can get to the tip of development. Also unfortunately the most unreliable as things break on a daily basis.
To use this run:
<pre>
sudo add-apt-repository ppa:kubuntu-ci/unstable
sudo apt update
sudo apt install kubuntu-desktop
sudo apt dist-upgrade
</pre>
=== Package Build Reports ===
[http://kci.pangea.pub/ Kubuntu CI Jenkins] has the output from the builds along with their status, useful for packagers and to catch compiler problems that are not caught by KDE CI such as symbol changes.
=== Kubuntu CI Unstable Weekly ISO Installable Images ===
[http://files.kde.org/snapshots/ Kubuntu CI Weekly ISO Installable Images] use the packages from Kubuntu CI Unstable Weekly to give you an installable image with packages made from KDE Git. These images have been tested manually as well as with automated checks.  Download '''unstable-i386-latest.iso'''.  They replace the Neon5 weekly images.
=== Kubuntu CI Tooling ===
This includes scripts and tools which apply the debian packaging information to the source code pulled from KDE to create the packages uploaded to launchpad. These can be found at [http://anonscm.debian.org/cgit/pkg-kde/].

Revision as of 20:25, 30 April 2016

While Ubuntu does have a wide selection of software in their official apt repositories, as well as what is available in the official (but unsupported) Backports repository, providing packages for newer KDE software versions (as well as some major applications) is often beyond the scope of these official software channels.

This is why Kubuntu use the Launchpad PPA system for their KDE technology upgrades.

Standard Ubuntu Repository Overview

Important Security Updates

This is where all your security fixes come from.

Recommended Updates

Normal package updates come from here. Note that you will not always get every new KDE software version.

Unsupported Updates

This is the official Ubuntu Backports repository. this unsupported channel mostly contains individual packages "backported' from a newer Ubuntu release, but will usually provide a minor KDE software "point" release if it provides significant bug fixes and stability.


Kubuntu Updates

Updates for Kubuntu releases which are due to go to Ubuntu Updates. Mostly KDE point releases.

Example: Kubuntu Wily 15.10 users were able to test out upgrading from Plasma 5.4 1 to 5.4.2 before those packages were moved to Ubuntu Updates.

Use Case:

  • Releases that are supposed and qualify to go to Ubuntu Updates
  • Releases that do not qualify for Ubuntu Updates but have low risk of regression
  • KDE Applications point releases
  • Amarok point releases
  • Calligra point releases


To add:

sudo add-apt-repository ppa:kubuntu-ppa/ppa

sudo apt update && sudo apt full-upgrade -y

Kubuntu Backports

Backports of new major versions of Plasma, Frameworks and major KDE apps for Kubuntu which are not yet tested enough to go to Ubuntu Backports.

Example: Wily users were able to try out upgrading Kubuntu Wily's Plasma from 5.4.x to 5.5.0 without having to wait for Xenial's release.

Use Case:

  • Releases of new major versions
  • Releases that are tested but still present a considerable risk of regression (for example due to a large change in the dependency stack, such as requirement bump from Qt 4.5 to 4.6)
  • Plasma major releases and such that imply major stack changes
  • Amarok major releases and such that imply major stack changes
  • Calligra major releases and such that imply major stack changes


To add:

sudo add-apt-repository ppa:kubuntu-ppa/backports

sudo apt update && sudo apt full-upgrade -y

Kubuntu Package Staging

DO NOT USE THIS PPA!

The staging PPA is a build ground for new packages and whole package stacks (such as Plasma), once they are staged they get moved to the most appropriate PPA from above. In consequence this means that staging can contain anything from an update to an experimental package and thus might very easily break your system.

Example: Before a new Plasma version gets published to the Kubuntu Backports PPA, it gets built in the clean environment of the staging PPA, once all packages are built and upgrade testing is done, all of staging gets moved to Kubuntu Backports.

Use Case:

  • Staging only (PPA must be cleaned first to ensure coherent stacks)
Retrieved from "https://community.kde.org/index.php?title=Kubuntu/PPAs&oldid=66861"