SyncRequestProcess

Differences between revisions 1 and 14 (spanning 13 versions)
Revision 1 as of 2007-01-26 09:36:35
Size: 2431
Editor: scandic759
Comment:
Revision 14 as of 2007-10-27 08:32:41
Size: 3684
Editor: 249-107
Comment: removed report line of old requests sync
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
== Before requesting a sync === == Before requesting a sync ==
Line 5: Line 5:
After UpstreamVersionFreeze, syncs of a newer upstream version require a [UbuntuDevelopment#Freezes freeze exception]. After UpstreamVersionFreeze, syncs of a newer upstream version require a [:UbuntuDevelopment#Freezes:freeze exception].
Line 8: Line 8:

After DebianImportFreeze, it's a good idea to review the Debian changes to make sure that the fixes will improve Ubuntu: some changes (maintainer change, new uploader, NMU acknowledgement with no additional fixes, etc.) may be better left for the next cycle.
Line 27: Line 29:
To request a sync, [https://launchpad.net/ubuntu/+filebug file a bug in Launchpad] with the above information, and subscribe (NOT assign) the `ubuntu-archive` team to the bug. This team will process the request and close the bug when it is complete. Please only subscribe ubuntu-archive to a bug once you have a '''clear action''' for the archive team to perform. Do not ask ubuntu-archive to help you decide what to do. To request a sync, [https://launchpad.net/ubuntu/+filebug file a bug in Launchpad] with the above information. Once the bug is complete and correct, if you are not an Ubuntu developer, subscribe (NOT assign) `ubuntu-main-sponsors` for packages in Main/Restricted and `ubuntu-universe-sponsors` for packages in Universe/Multiverse. They will review the request and subscribe `ubuntu-archive`. Ubuntu developers should subscribe (NOT assign) the `ubuntu-archive` team to the bug directly. This team will process the request and close the bug when it is complete. Please only subscribe ubuntu-archive to a bug once you have a '''clear action''' for the archive team to perform. Do not ask ubuntu-archive to help you decide what to do.
Line 29: Line 31:
 * Martin Pitt has written a [http://people.ubuntu.com/~pitti/scripts/requestsync script to file sync requests].
 * The list of outstanding archive administration requests can be found here: https://launchpad.net/~ubuntu-archive/+subscribedbugs
Do not change the Status of the bug as package sponsors and the archive administrators use this field. Do track the status of the sync. You will be notified via bug mail when the package has been published. Once you see (in Launchpad) that the updated packaged has been successfully built, if the archive admin has not, then you may mark the bug Status as 'Fix Released' (primarily for Universe/Multiverse).

 * Martin Pitt and Steve Kowalik written a script to file sync requests which is available in the [https://launchpad.net/ubuntu/+source/ubuntu-dev-tools ubuntu-dev-tools] package.

If you are in gutsy, and not in ~ubuntu-dev, you will need to use the '-s' option when running requestsync, to subscribe to `ubuntu-universe-sponsors` to review your request.

 * The list of outstanding archive administration requests can be found at: https://bugs.launchpad.net/~ubuntu-archive/+bugs

----
CategoryProcess

Before requesting a sync

Syncs (like uploads) cannot be reversed or undone. ALWAYS thoroughly check a package before asking for a sync. In particular, if there are Ubuntu changes in the current package, you must ensure the Ubuntu changes have been merged or are no longer relevant.

After UpstreamVersionFreeze, syncs of a newer upstream version require a [:UbuntuDevelopment#Freezes:freeze exception].

You should always sync a package rather than upload the unmodified source by hand, as it is safer and more accurate. If you know you will upload modified source immediately, modify the package and make an -<n>ubuntu<n> upload rather than requesting a sync. However, be sure to always use the exact same .orig.tar.gz as Debian (or whomever).

After DebianImportFreeze, it's a good idea to review the Debian changes to make sure that the fixes will improve Ubuntu: some changes (maintainer change, new uploader, NMU acknowledgement with no additional fixes, etc.) may be better left for the next cycle.

Packages can be synced from any Debian-format package archive, i.e. something with a Sources file.

Content of a sync request

When requesting a 'sync', please include the following information:

  • Source package name
  • Source package version number to sync
  • Where to sync from (e.g. 'Debian sid main', 'Debian experimental non-free')
  • If there are Ubuntu changes apart from debian/changelog or if UpstreamVersionFreeze is in effect:

    • A copy of the entries from debian/changelog corresponding to the changes relative to the current version in Ubuntu
  • If there are Ubuntu changes:
    • a description of each of the Ubuntu changes (a bullet point list is fine, but copies of debian/changelog aren't)
    • a brief explanation of why each one may be dropped (e.g., it's been merged into Debian, is no longer appropriate, etc.)
    • an explicit confirmation that the Ubuntu changes should be overridden

Submitting your request

To request a sync, [https://launchpad.net/ubuntu/+filebug file a bug in Launchpad] with the above information. Once the bug is complete and correct, if you are not an Ubuntu developer, subscribe (NOT assign) ubuntu-main-sponsors for packages in Main/Restricted and ubuntu-universe-sponsors for packages in Universe/Multiverse. They will review the request and subscribe ubuntu-archive. Ubuntu developers should subscribe (NOT assign) the ubuntu-archive team to the bug directly. This team will process the request and close the bug when it is complete. Please only subscribe ubuntu-archive to a bug once you have a clear action for the archive team to perform. Do not ask ubuntu-archive to help you decide what to do.

Do not change the Status of the bug as package sponsors and the archive administrators use this field. Do track the status of the sync. You will be notified via bug mail when the package has been published. Once you see (in Launchpad) that the updated packaged has been successfully built, if the archive admin has not, then you may mark the bug Status as 'Fix Released' (primarily for Universe/Multiverse).

If you are in gutsy, and not in ~ubuntu-dev, you will need to use the '-s' option when running requestsync, to subscribe to ubuntu-universe-sponsors to review your request.


CategoryProcess

SyncRequestProcess (last edited 2012-01-23 12:20:22 by mitya57)