Re: Could you sponsor upload the test-framework packages?
Hi. Thank you for your attention on busy time.
On Wed, Oct 19, 2011 at 2:51 AM, Joachim Breitner <firstname.lastname@example.org> wrote:
> I’m a bit busy right now, so I don’t know if I find the time to look at
> the package before the weekend, but at least let me answer your mails.
> Maybe someone else can do the sponsoring.
Thank's a lot.
I am waiting for the sponsor uploading haskell-ansi-terminal......
>> > 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.
> Yes, you still need to depend on the -prof package, but it is enough to
> have the version bound on the -dev package.
I don't know "version bound". What is it?
I have seen haskell-yesod-0.9.3/debian/control file,
but I can't understand meaning of "version bound".
I will talk about the pkg-haskell team process in University of Tsukuba.
I would like to get some people for pkg-haskell team on Tsukuba. :)
Then, I have some question for pkg-haskell team.
[Q1] Can the person as DM (Debian Maintainer) joined pkg-haskell team
have the below process for ITP?
(step 1) maintainer: Create ThePackage with cabal-debian command.
Or by just copying the debian-template/ directory and modifying the
files. That is how I do it, so I cannot vouch for cabal-debian. But if
that tool works equally well, then surely that is fine (and if not, then
feel free to fix it :-)).
Make sure that debian/changelog at this point still says UNRELEASED, as
the package is not yet to be uploaded
$ vi debian/control
Maintainer: Debian Haskell Group
Uploaders: Kiwamu Okabe <email@example.com>
(step 2) maintainer: darcs init and put (But DON'T tag ThePackage's repos.)
casper$ darcs init --darcs-2
casper$ darcs record -a -l -m "Initial Check-In"
Finished recording patch 'Initial Check-In'
casper$ darcs put
(step 3) maintainer: add-hooks.sh
(step 4) maintainer: set "unstable" on changelog
change the distribution field in debian/changelog to
"unstable" and push that change. Then the package is marked as “ready to
upload” on http://pkg-haskell.alioth.debian.org/cgi-bin/pet.cgi.
(step 4) maintainer: Ask sponsor for dput ftp.upload.debian.org.
(step 5) sponsor: darcs get darcs.debian.org:/darcs/pkg-haskell/tools
(step 6) sponsor: tools/pkg-haskell-checkout ThePackage
(step 7) sponsor: cd ThePackage; debuild -i -I; debrelease
(step 8) sponsor: debuild clean; cd ThePackage/debian; darcs tag; darcs push -a
-i -I should not be necessary with source/format 3.0, I use
$ debuild -tc
which includes the clean step. Also, tagging can be done with "debcommit
-r", so my command sequence is
$ debuild -tc # followed by a glance over the result, e.g. with "debc"
$ debcommit -r && debrelease && darcs push --repo=debian
(step 9) maintainer: Close ITP bug.
Should not be necessary if the maintainer puts the correct "Closes:
#12345" message in the changelog.
[Q2] Can the person as not DM (Debian Maintainer) join pkg-haskell team?
Or they should become DM, first?