You will need to sign up for access to alioth and then request a Debian Developer sponsor your access. Check out https://wiki.debian.org/Alioth/PackagingProject for more information.
On Mon, Oct 13, 2014 at 2:59 PM, whey bags <wheyb...@wheybags.com> wrote: > How do I get access to the collab maint project? > > On Tue, Oct 7, 2014 at 3:13 AM, Harlan Lieberman-Berg > <h.liebermanb...@gmail.com> wrote: > > Hi Tom! > > > > Thanks for packaging librocket for Debian. I've got a couple things for > > you to fix as the next steps. > > > > 1. You should delete all of those .ex files in the debian directory. > > Those are just examples of things that you might need to do. > > > > 2. Your changelog should close an ITP bug - in your case, #764252. > > > > 3. If you are using compat = 9 (which you should!), you need to depend > > on debhelper >= 9. > > > > 4. Your VCS fields contain a repository which doesn't exist. You should > > setup the collab-maint repository and push the packaging's git > > repository there. > > > > 5. Your standards version isn't the latest version - you should update > > it to 3.9.6. > > > > 6. Your packages should have a short description and a longer > > description that should be enough information for a user to decide > > whether they want to install the package. Check out Debian Policy 3.4 > > for more details there. > > > > 7. Your patches are missing DEP-3 headers; check out the patch tagging > > guidelines at http://dep.debian.net/deps/dep3/. > > > > Lintian is a very helpful tool for finding some of these problems, and > > has more than I detailed above, as well as some general warnings that > > might point to bigger problems. I recommend it highly; it's saved my > > butt on many an occasion! > > > > Thanks again for your help packaging librocket for Debian; when you've > > got another upload that fixes the problems, send the bug a mail and > > someone will swing by and take another look. > > > > Sincerely, > > > > -- > > Harlan Lieberman-Berg > > ~hlieberman > > >
