# How to request an upload After fixing a bug in a package or when introducing a new package to the distribution, the updated package needs to be uploaded to the Ubuntu Archive. If you don’t have upload rights to the Archive, find a sponsor who does to upload your changes. This article describes, how to request an upload. Follow the general [guidance for contributors](https://documentation.ubuntu.com/project/contributors.md#guides-for-contributors) to have your changes properly prepared for sponsorship. Remember that someone else needs to understand what you’ve done. For any non-trivial change, it’s good practice to discuss your plans with a potential sponsor (ask in [#devel:ubuntu.com](https://matrix.to/#/#devel:ubuntu.com)) *after* you think you know what needs to be done, but *before* you’ve actually done it. Often, an experienced developer can offer alternative approaches that may save you time or provide better results. ## Seek upload sponsorship Submit a [Merge Proposal (MP)](https://documentation.ubuntu.com/project/contributors/updating/submit-a-merge-proposal.md#how-to-submit-a-merge-proposal) with your changes. Ensure to: * Include the Launchpad bug that is to be fixed by this upload in the `changelog` file in the form `LP: #123456` (see [Write the changelog entry](https://documentation.ubuntu.com/project/contributors/updating/commit-changes.md#write-the-changelog-entry)). * Select the `ubuntu-sponsors` team as the reviewer for the MP. * Link the Launchpad bug to the MP (using the Link a bug report link). ## Signed-package companions Some packages need to be cryptographically signed by Launchpad and thus have both a main source package and a companion `-signed` source package (for example, `s390-tools` and `s390-tools-signed`). Before uploading, ensure that: - Both the main and `-signed` source packages have the **exact same version**. - Any versioned build-dependency in the `-signed` source package is correctly generated.