
A few minor issues: In Hackage 1 packages can be deprecated, optionally indicating a recommended replacement (the "deprecated" and "superseded by" fields of the per-package "tags" file), e.g. partial-lens and binary-strict-0.3.1. These don't seem to be in Hackage 2. Several packages lack documentation. They don't say why (an issue in itself), but it appears to be libraries that interface to C libraries, and libraries included with GHC. There's little to be done about the former, but it's really useful to have the documentation of the GHC libraries there too. The base package can't be built outside the GHC tree, but I think it warrants special treatment. The package her-lexer-0.1 shows links to documentation, but they lead to an error message.

On Mon, Sep 3, 2012 at 4:38 PM, Ross Paterson
In Hackage 1 packages can be deprecated, optionally indicating a recommended replacement (the "deprecated" and "superseded by" fields of the per-package "tags" file), e.g. partial-lens and binary-strict-0.3.1. These don't seem to be in Hackage 2.
I think you can reach this functionality by going to a package and clicking 'maintain'. There, you can edit deprecation and preferred versions. I haven't tested if this works, though. Erik

On Mon, Sep 03, 2012 at 03:52:32PM +0100, Erik Hesselink wrote:
On Mon, Sep 3, 2012 at 4:38 PM, Ross Paterson
wrote: In Hackage 1 packages can be deprecated, optionally indicating a recommended replacement (the "deprecated" and "superseded by" fields of the per-package "tags" file), e.g. partial-lens and binary-strict-0.3.1. These don't seem to be in Hackage 2.
I think you can reach this functionality by going to a package and clicking 'maintain'. There, you can edit deprecation and preferred versions. I haven't tested if this works, though.
OK, but it would be useful to migrate the existing deprecations of 870 uploads.

On Mon, Sep 03, 2012 at 04:32:16PM +0100, Ross Paterson wrote:
On Mon, Sep 03, 2012 at 03:52:32PM +0100, Erik Hesselink wrote:
On Mon, Sep 3, 2012 at 4:38 PM, Ross Paterson
wrote: In Hackage 1 packages can be deprecated, optionally indicating a recommended replacement (the "deprecated" and "superseded by" fields of the per-package "tags" file), e.g. partial-lens and binary-strict-0.3.1. These don't seem to be in Hackage 2.
I think you can reach this functionality by going to a package and clicking 'maintain'. There, you can edit deprecation and preferred versions. I haven't tested if this works, though.
OK, but it would be useful to migrate the existing deprecations of 870 uploads.
Filed as https://github.com/haskell/cabal/issues/1027 Thanks Ian

On Mon, Sep 03, 2012 at 03:38:19PM +0100, Ross Paterson wrote:
A few minor issues:
Thanks for the feedback!
Several packages lack documentation. They don't say why (an issue in itself),
I've made a ticket for this: https://github.com/haskell/cabal/issues/1024
but it appears to be libraries that interface to C libraries, and libraries included with GHC. There's little to be done about the former, but it's really useful to have the documentation of the GHC libraries there too.
I think it is possible for uploaders to upload missing docs. I've filed https://github.com/haskell/cabal/issues/1025 for us to document how.
The package her-lexer-0.1 shows links to documentation, but they lead to an error message.
Hmm, curious. I'll take a look, and also do a linkcheck of new-hackage, to see if any other packages are affected. I've filed https://github.com/haskell/cabal/issues/1026 so that we don't forget about it. Thanks Ian

The User accounts page, echoing the Hackage 1 version, says "Passwords are stored encrypted, so if you forget yours we can't recover it, but will need to assign a new one. Just ask." But the account registration page doesn't even ask for an email address, so it would be difficult for administrators to action a request for a password reset safely. If you store the email address, an automatic reset would be feasible, as is common elsewhere.
participants (3)
-
Erik Hesselink
-
Ian Lynagh
-
Ross Paterson