Hi. Thank you for your kindly mail. Sorry for your confusing. Now we should start from creating new darcs repos.
Could you remove the below repos from darcs.debian.org/pkg-haskell? haskell-ansi-terminal haskell-ansi-wl-pprint haskell-hostname haskell-language-haskell-extract haskell-test-framework-hunit haskell-test-framework-quickcheck2 haskell-test-framework-th haskell-test-framework On Thu, Oct 13, 2011 at 11:44 PM, Joachim Breitner <[email protected]> wrote: >> > Could you sponsor upload the test-framework >> > <http://batterseapower.github.com/test-framework/> package >> > and the others needed by it? >> >> The Vcs repositories are moved to Darcs with Joachim's advice. >> Then,,, Could you dput the below packages to Debian? >> >> http://mentors.debian.net/packages/uploader/kiwamu%40debian.or.jp > > I’m confused, http://pkg-haskell.alioth.debian.org/cgi-bin/pet.cgi lists > these already as tagged, which should indicate that someone uploaded > these already, as described in > http://wiki.debian.org/Haskell/CollabMaint/Processes. Is that > intentional? I had tagged my packages by me on dputting to mentors.debian.net. Sorry, I didn't understand Haskell CollabMaint Process. Now I think it's below. Is it correct? (step 1) maintainer: Create ThePackage with cabal-debian command. (step 2) maintainer: darcs init; darcs record; darcs put darcs.debian.org... But DON'T tag ThePackage's darcs repos. (step 3) maintainer: ssh alioth.debian.org /darcs/pkg-haskell/tools/add-hooks.sh (step 4) maintainer: Add below to ThePackage/debian/control file. Maintainer: Debian Haskell Group <[email protected]> Vcs-Darcs: http://darcs.debian.org/darcs/pkg-haskell/ThePackage Vcs-Browser: http://darcs.debian.org/cgi-bin/darcsweb.cgi?r=pkg-haskell/ThePackage (step 5) darcs record -a; darcs push (step 6) maintainer: Ask sponsor for dput. (step 7) sponsor: darcs get darcs.debian.org:/darcs/pkg-haskell/tools (step 8) sponsor: tools/pkg-haskell-checkout ThePackage (step 9) sponsor: cd ThePackage; debuild -i -I; debrelease (step a) sponsor: debuild clean; cd ThePackage/debian; darcs tag; darcs push -a (step b) maintainer: Close ITP bug. > Also, I did not see any commit messages on pkg-haskell-commits. Did you > set up the commit hooks, as described in > http://wiki.debian.org/Haskell/CollabMaint/DarcsBasic? No. I had skip the set up hooks step. I will not forget the step in next time. > As for the packaging itself: > * Specifying version bounds on -prof packages is not required, as > they are always tight to the -dev package. This makes > debian/control slightly more concise. I think the test-framework* packages need -prof packages. Because Haskell program need ghc profile, on unit testing. > * Usually, we put the DHG as the maintainer and ourself as the > Uploader. Any specific reason to not do that with > test-framework? OK. I will change debian/control Maintainer name to [email protected]. But is my e-mail address in debian/control Uploaders? If it's deleted in Uploaders line, I can't dput ftp.upload.debian.org. > * The debian/copyright is usually not just a copy of LICENSE. > Please see > http://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile > and http://www.debian.org/doc/manuals/maint-guide/dreq.en.html#copyright, and > if you want to support the latest trends in Debian packaging, > http://dep.debian.net/deps/dep5/. I will fix it, next time. > * When writing the control file, please keep the slightly > different audience in mind. While code example are great on > hackage, I’m not sure if the Debian package description for > libghc-language-haskell-extract-dev needs them. OK. I will remove code example from debian/control file. > * You could remove the commented example lines from debian/rules. OK. > I hope you don’t mind me being a bit more pedantic here, but that is > required with a new contributor. You don’t need to upload to mentors to > get them sponsored via the DHG, as we fetch the source from Darcs and > build it then. OK. I forget http://mentors.debian.net/, while I am in DHG. > If you want to help out with the hakyll server dependencies, that’d be > great, of course. OK. I will try to pack snap and the others for hakyll, after ITP bug of test-framework closed. Best regards, -- Kiwamu Okabe -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/CAEvX6dk3SRWnJRKgU905q=qo7gvvbtzg+wdmbxgwbjsctgo...@mail.gmail.com
