Responses

Differences between revisions 2 and 4 (spanning 2 versions)
⇤ ← Revision 2 as of 2012-01-31 20:17:38 →
Size: 1994
Editor: vps
Comment:
← Revision 4 as of 2012-02-08 20:50:56 → ⇥
Size: 2007
Editor: stgraber
Comment:
Deletions are marked like this. Additions are marked like this.
Line 18: Line 18:
Could you submit this as a source package rather than a binary package? You can create this by running 'debuild -S', and send us the .orig.tar.gz, .diff.gz, and .dsc files. For more information, see: Could you submit this as a source package rather than a binary package? You can create this by running 'debuild -S', and send us (in a tarball) the .orig.tar.gz, .diff.gz, and .dsc files. For more information, see:
Line 37: Line 37:
=== Application touches system files ===  === Application touches system files ===
Line 40: Line 40:
Your application appears to touch system files as part of its operation, however we do not allow apps to do this as part of a security policy for extras.ubuntu.com. For these applications, we recommend that you folloow the steps on https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages for submitting your package to Debian or Ubuntu. Your application appears to touch system files as part of its operation, however we do not allow apps to do this as part of a security policy for extras.ubuntu.com. For these applications, we recommend that you follow the steps on https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages for submitting your package to Debian or Ubuntu.

This page provides some stock responses to common scenarios in ARB application reviews. It is inspired by Bugs/Responses, the Bug Squad's archive of stock responses.

Contents

  1. Content
    1. Wrong license or proprietary license
  2. Packaging
    1. Submitted binary package
    2. Submitted binary tarball
    3. Submitted without build instructions or dependency information
  3. Running
    1. Application touches system files

Content

Wrong license or proprietary license

This app was submitted with the license <license name>, but looking at your <files|website> it seems to be licensed as <other license name>. Please select the appropriate license for your app, and resubmit it.

Packaging

Submitted binary package

Could you submit this as a source package rather than a binary package? You can create this by running 'debuild -S', and send us (in a tarball) the .orig.tar.gz, .diff.gz, and .dsc files. For more information, see:

https://wiki.ubuntu.com/PackagingGuide/Complete#Building_the_Package_.28Source_and_Binary.29

Submitted binary tarball

Could you submit this as a source tarball rather than a binary tarball? That is, bundle up the files before you run the build/install process, so we get the full source. If you have questions about how to do this, we can walk you through it. Contact us here, or on the ubuntu-app-devel@lists.ubuntu.com mailing list or #ubuntu-app-devel IRC channel on Freenode.

Submitted without build instructions or dependency information

Could you submit instructions for building, installing, and running the app? It looks like this will depend on the <package name> package, which is available in Ubuntu. The version of <package name> shipped in Oneiric is <package version>.

Running

Application touches system files

Your application appears to touch system files as part of its operation, however we do not allow apps to do this as part of a security policy for extras.ubuntu.com. For these applications, we recommend that you follow the steps on https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages for submitting your package to Debian or Ubuntu.

AppReviewBoard/Review/Responses (last edited 2012-06-29 16:35:58 by dholbach)