problems with upgrade of kde

Harald Sitter apachelogger at
Thu May 21 17:56:30 BST 2009

On Donnerstag, 21. Mai 2009 01:33:03 Richard JOHNSON wrote:
> On Thu, May 21, 2009 at 01:20:29AM +0200, Harald Sitter wrote:
> > Also, that kind of stuff should probably be done over at KDE, Kubuntu, at
> > most, can do a second run every once in a while to ensure that Kubuntu
> > specific patches don't cause regressions.
> I think that once we get settled into a release we would go for the
> automated testing and really get into the regression testing. We should at
> least make sure right now that packages build and install correctly,
> because we don't need more grumpy developers, I think I am all you can
> handle :p 

True :P

> > Nope, this will be done based on debs built in $PPA (or eventually as
> > provided by the developer). In any case the server will also do automatic
> > uploading of packages if a new revision was pushed, so it probably makes
> > sense to just check for newly built debs and compare it's content to an
> > established database of previous versions.
> So we will in essence have 2 buildd's? We will push to this server which
> will do some testing, and then if all goes well it will go to the PPA?

Nah, the server just acts as proxy creating the source packages by merging it 
with the branch and pushing that to the PPA. Then it grabs the deb (assuming 
it built, if not we get spam from soyuz anyway) and does the testing.

More information about the kubuntu-devel mailing list