ubuntu-desktop team members can now upload

Colin Watson cjwatson at ubuntu.com
Thu Nov 26 12:16:44 GMT 2009

On Wed, Nov 25, 2009 at 11:33:43PM -0500, Scott Kitterman wrote:
> It may be I'm unclear on the concept, but it was my recollection that
> packages for each specialist team were supposed to be unique and that
> packages that landed in multiple team areas were supposed to be uploaded
> by whatever core-dev turns into?

In some cases it is appropriate to seed things somewhere core (e.g. the
desktop-common seed) when they're in an intersection. We didn't specify
a rule like that, though - it was mooted at one point but I didn't think
it was feasible to make it anything but a judgement call. That would
mean that the presence of any two flavours of Ubuntu that used the same
desktop environment would cause all of that desktop environment to land
in core.

> Looking at the intersection of the ubuntu-desktop and kubuntu sets (less
> language pack stuff that made the list even more unwieldy) I get the
> attached list of packages in both sets.
> First, I'd thought the intersection was supposed to be null and some of
> them seem distinctly odd (ubuntu-artwork in the kubuntu set

Some of this is due to build-dependencies (e.g. xscreensaver) and the
rest is due to the education seed which generally makes analysis
difficult. Suggestions for what to do with the latter welcome.

> and kdebindings in the ubuntu set, for example).

Bindings, and other core libraries, tend to end up all over the place.
ubiquity is core but ships binaries that depend on python-kde4.

> Is this what was intended?

I'd like to have facilities for manual overrides of some kind, but it's
a bit unwieldy while we're still manually moving stuff back and forward
between main and universe *as well*, and while those moves have to be
done using shell access on the master archive system whereas package
sets need to be manipulated using the Launchpad API and therefore on a
client system. Right now I'm just checking the package set changes every
so often by eye to make sure that specialist teams aren't gaining access
to things that I think should be in core instead. Obviously this doesn't

If overrides could be changed using the Launchpad API, then that would
help a lot because we'd be able to put all the logic in one place in
ubuntu-archive-tools and then manual overrides would be more feasible.

Colin Watson                                       [cjwatson at ubuntu.com]

More information about the ubuntu-devel mailing list