Launchpad itself

Component mapping for new source packages

Bug #120052 reported by Colin Watson
6
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
Medium
Julian Edwards

Bug Description

When syncing new source packages from Debian, we most commonly want to override packages from Debian's main component into our universe component, and packages from Debian's contrib or non-free components into our multiverse component. At present, we do this by hand. However, this is rather laborious and sometimes results in new packages going into main by mistake; while this isn't harmful long-term since we have automated reports to detect packages that should be demoted, it often wastes time as builds fail due to ogre-model constraints.

When a new source or binary package enters an Ubuntu queue (i.e. at process-upload time, not queue accept), its component should be set based on the following mapping from the component in the .dsc or .deb respectively: {'main': 'universe', 'contrib': 'multiverse', 'non-free': 'multiverse'}. If the component in the .dsc or .deb is not in that mapping, then it should default to universe. The archive administrator may still choose to override this to something else and that choice must not be overridden. None of this should apply to source or binary packages that already have overrides in the archive.

See original description
Tags: lp-soyuz
Revision history for this message
Celso Providelo (cprov) wrote :

it's simple to set default_overrides_map to NEW packages in upload time.

Changed in soyuz:
importance: Undecided → Medium
status: New → Confirmed
Revision history for this message
Sarah Kowalik (hobbsee-deactivatedaccount) wrote :

this means that the UI can't be used for accepting new sources/binaries at all, either, afaik.

Revision history for this message
Colin Watson (cjwatson) wrote : Re: [Bug 120052] Re: Component mapping for new source packages

Binaries are fine (at least, they aren't affected by this bug); they
don't get announced on accept anyway.

Julian Edwards (julian-edwards)
Changed in soyuz:
milestone: 1.1.12 → 1.2.1
Revision history for this message
Sarah Kowalik (hobbsee-deactivatedaccount) wrote :

note to self: for every accepted source package, remember to go back and request an archive admin shove it to universe.

Celso Providelo (cprov)
Changed in soyuz:
assignee: nobody → cprov
Julian Edwards (julian-edwards)
Changed in soyuz:
assignee: cprov → julian-edwards
milestone: 1.2.1 → 1.2.2
Revision history for this message
Sarah Kowalik (hobbsee-deactivatedaccount) wrote :

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I know you want to wait a while to put in the components via the web UI,
due to other more pressing needs, but is there any harm in fixing this
to a more sensible default in the meantime?

It's annoying to have to ask an archive admin almost every time to
demote whatever package i've just accepted from the new queue. In the
grand scope of new packages and synced packages, packages that go to
main are quite rare.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHi47y7/o1b30rzoURAsz0AJ9DLnr31tknGzK9B+R4rWh80VM8zwCghMZ9
YgMVr6wX04jiZIJwEbW8QzA=
=IcX0
-----END PGP SIGNATURE-----

Revision history for this message
Julian Edwards (julian-edwards) wrote :

Sarah

This is a simple matter of too much work to do and not enough people to do it. Unfortunately, other more pressing issues have caused this one to slip.

I'm sorry if this does not meet your expectations, be rest assured we're working hard to fix all the Soyuz bugs.

Julian Edwards (julian-edwards)
Changed in soyuz:
milestone: 1.2.2 → 1.2.1
status: Confirmed → In Progress
Revision history for this message
Julian Edwards (julian-edwards) wrote :

Fixed in RF 5523.

Changed in soyuz:
status: In Progress → Fix Committed
Julian Edwards (julian-edwards)
Changed in soyuz:
status: Fix Committed → Fix Released
Revision history for this message
Colin Watson (cjwatson) wrote :

This doesn't seem to have worked. Here's the result of syncing a package from Debian main just today:

  398053 | S- | manpages-cs | 0.17.20080113-1 | 20 seconds
         | * manpages-cs/0.17.20080113-1 Component: main Section: doc

That should have landed in universe by default, not main. Could you please find out what went wrong?

Changed in soyuz:
status: Fix Released → Confirmed
Colin Watson (cjwatson)
description: updated
Revision history for this message
Julian Edwards (julian-edwards) wrote :

Colin, thanks for the updated description. As discussed on IRC, I'll put a quick fix in that only overrides where the original component is main, for now, and move the override to upload time instead of acceptance time.

Sorry for the confusion.

Changed in soyuz:
milestone: 1.2.1 → 1.2.2
Revision history for this message
Julian Edwards (julian-edwards) wrote :

Quick hack landed in revision 5591, this will be cherry picked today.

Julian Edwards (julian-edwards)
Changed in soyuz:
status: Confirmed → In Progress
Revision history for this message
Julian Edwards (julian-edwards) wrote :

Fix landed in RF 5622.

Changed in soyuz:
status: In Progress → Fix Committed
Julian Edwards (julian-edwards)
Changed in soyuz:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.