Differences between revisions 1 and 8 (spanning 7 versions)
Revision 1 as of 2012-11-02 19:17:23
Size: 2853
Editor: ?markus tornow
Comment: Initial setup. Needs to be examined and enhanced.
Revision 8 as of 2012-11-04 13:25:14
Size: 3044
Editor: ?markus tornow
Comment:
Deletions are marked like this. Additions are marked like this.
Line 7: Line 7:
Info are to be found here. Infos are to be found here.
Line 9: Line 9:
 * [[https://wiki.debian.org/ITP|ITP debian wiki]]  * [[ITP|ITP debian wiki]]
Infos about the package reportbug are to be found here:
 * [[reportbug]]
You might want to use that, as it is very comfortable (mainly for block-by and additional-infos).
Line 11: Line 14:
After you have successfully build your package with dpkg-buildpackage and made sure all dependencies are added to debian/control, it is time to send an ITP (intend to package). After you have successfully build your package with dpkg-buildpackage and made sure all dependencies are added to debian/control, it is time to send an ITP (intent to package).
Line 18: Line 21:
ITP: ruby-devise -- Flexible authentication solution for Rails with Warden ITP: ruby-devise -- A gem that offers flexible authentication solution for Rails with Warden
Line 38: Line 41:
You will find the according info in the files oyu already edited (changelog, copyright and control). You will find the according info in the files you already edited (changelog, copyright and control).
Line 50: Line 53:
installable, but already set to ITO installable, but already set to ITP.
Line 76: Line 79:
Re: ITP: ruby-image-magick -- A ruby wrapper for ImageMagick command line Re: ITP: ruby-devise -- A gem that offers flexible authentication solution for Rails with Warden
Line 83: Line 86:
https://gitorious.org/debian-diaspora/ruby-mini-magick https://gitorious.org/debian-diaspora/ruby-devise

Translation(s): none


ITP

Infos are to be found here.

Infos about the package reportbug are to be found here:

You might want to use that, as it is very comfortable (mainly for block-by and additional-infos).

After you have successfully build your package with dpkg-buildpackage and made sure all dependencies are added to debian/control, it is time to send an ITP (intent to package).

Send the email to: submit@bugs.debian.org

The subject line is supposed to have got the following syntax:

ITP: ruby-devise --  A gem that offers flexible authentication solution for Rails with Warden

which means you start with ITP and a colon (ITP:) add one space, then the name of your package (ruby-devise) one space, two hyphens and another space ( -- ) and finally the short description.

The content should look similar to this:

package: wnpp
Severity: wishlist
Owner: Markus Tornow <tornow@riseup.net>

*Package Name : devise
 Version : 2.1.2
 Upstream Author : José Valim, Carlos Antônio
*URL :  https://github.com/plataformatec/devise
*License : Expat
*Description :  Flexible authentication solution for Rails with Warden

I am packaging devise as it is a dependency of devise_invitable
(#691181)  which is a dependency of diaspora (#597093)

You will find the according info in the files you already edited (changelog, copyright and control). Once you get the confirmation for you ITP you can add the bug-number to debian/changelog:

* Initial release (Closes: #692057 )

and get rid of the according lintian error.

block by

Detailed info can be found here:

If your package can't be installed because one of it's dependencies is not installable, but already set to ITP.

Send an email to: control@bugs.debian.org

Give the info in the subject line. Tell which package blocks your package:

devise (691525 ) blocks devise_invitable (691181)

In the body use this syntax (ITP-number block by ITP-number)

block 691181 by 691525

add additional info

Once you added your package as a git repo to * gitorious debian-diaspora you should add the info about the git-repository to the bug.

Send an email to: your_bug_number@bugs.debian.org

Make the subject line look like this:

Re: ITP: ruby-devise --  A gem that offers flexible authentication solution for Rails with Warden

(add an Re: before your original subject line).

And give the info where your git repository is to be found. For example:

The git-repository is to be found here: 
https://gitorious.org/debian-diaspora/ruby-devise

Regards,