On Fri, Sep 7, 2012 at 8:41 PM, Henning Thielemann wrote:

On Fri, 7 Sep 2012, Henning Thielemann wrote:

...

On Sun, 2 Sep 2012, Ian Lynagh wrote:

...

Dear Haskellers,

I am pleased to announce that a test instance of the Hackage 2 server is now running at http://new-hackage.haskell.org/

The plan is to test the new server for 3 weeks (until Monday 24 September), before switching over to Hackage 2 for real.

I have now tried to upload a package candidate for my 'gnuplot' interface package. The web interface says:

Error: Upload failed Not authorized to upload a candidate for this package

I use the same uploader name for new-hackage and old hackage.

What can I do?

I though Ian turned off the 'maintainers' check on existing packages, but just in case he hasn't, I've added you to the maintainers group for 'gnuplot'. Can you try again? Erik

On Sat, 8 Sep 2012, Henning Thielemann wrote:

On Sat, 8 Sep 2012, Erik Hesselink wrote:

...

I though Ian turned off the 'maintainers' check on existing packages, but just in case he hasn't, I've added you to the maintainers group for 'gnuplot'. Can you try again?

Ok, I can now upload a candidate ...

Another question: Will Hackage try to compile the package and generate Haddock documentation for the candidate and if yes, when?

On Tue, 11 Sep 2012, Ian Lynagh wrote:

On Sat, Sep 08, 2012 at 09:07:40PM +0200, Henning Thielemann wrote:

...

On Sat, 8 Sep 2012, Henning Thielemann wrote:

...

Ok, I can now upload a candidate ...

Another question: Will Hackage try to compile the package and generate Haddock documentation for the candidate and if yes, when?

I'm pretty sure that documentation won't be generated for candidate packages.

Doc building should be attempted for uploaded packages within about an hour.

It would be cool if I could see the compilation and haddock documentation succeeding before a final upload. It is something that I can hardly test locally. I can locally test whether a fresh install of all dependencies on my machine works but I cannot check so easily whether it works with the packages as they are installed on Hackage.

On Sat, 8 Sep 2012, Erik Hesselink wrote:

Ok, so it seems the maintainers check is not off yet, at least not for uploading candidates.

Next test: I have successfully uploaded a package candidate of 'gnuplot'. Now I go to the gnuplot candidate page and click on [maintain]. Then I get a new page with the text "Here, you can delete a candidate, publish it, upload a new one, and edit the maintainer group". Below this text the page is empty. Above this text there are the usual hackage navigation links. It does not look like a can do a lot with the package candidate so far.

On Tue, Sep 11, 2012 at 11:29 PM, Ian Lynagh wrote:

On Mon, Sep 10, 2012 at 09:55:30AM +0200, Henning Thielemann wrote:

...

Next test: I have successfully uploaded a package candidate of 'gnuplot'. Now I go to the gnuplot candidate page and click on [maintain]. Then I get a new page with the text "Here, you can delete a candidate, publish it, upload a new one, and edit the maintainer group". Below this text the page is empty. Above this text there are the usual hackage navigation links. It does not look like a can do a lot with the package candidate so far.

Hackage people, what's the plan here?

My assumption was that "Upload a package candidate" in Hackage 2 was just meant to check for problems in the package (which AFAIK is what "Checking a Cabal package" does in Hackage 1).

It looks like more functionality might be planned, but not implemented? Should we just remove the "maintain" link for now?

It looks like you're correct. I think the simplest thing is indeed to remove the maintain link. The text on upload.html should probably also be changed in that case. Erik

On Tue, Sep 11, 2012 at 06:36:12PM -0400, Matthew Gruen wrote:

One can upload a package directly from candidacy, called publishing. Literally the only thing missing, and it should have be hard to miss (but in any case), is a link to the page. This is an HTML issue.

OK, thanks. I filed a ticket for this here: https://github.com/haskell/cabal/issues/1041 Thanks Ian

On Wed, Sep 12, 2012 at 08:04:10PM -0400, Matthew Gruen wrote:

I think the function controlling this is named something like serveCandidateMaintain. Say, do you prefer patches via darcs or git?

A darcs patch against the central repo: http://code.haskell.org/hackage-server is easiest. Thanks Ian -- Ian Lynagh, Haskell Consultant Well-Typed LLP, http://www.well-typed.com/

On 25 September 2012 12:41, Herbert Valerio Riedel wrote:

Ian Lynagh writes:

...

I am pleased to announce that a test instance of the Hackage 2 server is now running at http://new-hackage.haskell.org/

The plan is to test the new server for 3 weeks (until Monday 24 September), before switching over to Hackage 2 for real.

...as it's now past monday... what's the status? is the switch-over going to happen now?

Hi Herbert, Ian has handed the task over to me, so I'll be leading the switchover, along with the admins we've recruited. We have a few issues we're still working on, mainly to do with importing the old data and making the account switchover smooth. https://github.com/haskell/cabal/issues?labels=hackage2%2Cimportant&state=open I'll post more details on the cabal-devel mailing list in the coming days, so you can follow it there. -- Duncan Coutts, Haskell Consultant Well-Typed LLP, http://www.well-typed.com/