Migrate deprecations from Hackage1 #1027

Closed
igfoo opened this Issue Sep 4, 2012 · 3 comments

Comments

Projects
None yet
3 participants
@igfoo
Contributor

igfoo commented Sep 4, 2012

See http://www.haskell.org/pipermail/cabal-devel/2012-September/009035.html for details

Urgent, as if we're going to do this then we need to do it before the Hackage2 switchover.

Ideally, It would be a self-contained phase of the mirroring process, so that we can run that phase only on the existing new-hackage test site.

@gracenotes

This comment has been minimized.

Show comment
Hide comment
@gracenotes

gracenotes Sep 7, 2012

This alternatively could be stored in the export tarball as part of the bulk legacy import process.

This alternatively could be stored in the export tarball as part of the bulk legacy import process.

@dcoutts

This comment has been minimized.

Show comment
Hide comment
@dcoutts

dcoutts Sep 20, 2012

Member

Right, either bulk import to just done ad-hoc via http PUT using curl and a script.

Member

dcoutts commented Sep 20, 2012

Right, either bulk import to just done ad-hoc via http PUT using curl and a script.

@dcoutts

This comment has been minimized.

Show comment
Hide comment
@dcoutts

dcoutts Nov 21, 2012

Member

I have extended the new hackage-import client so it does now support uploading the deprecated info about packages.

Member

dcoutts commented Nov 21, 2012

I have extended the new hackage-import client so it does now support uploading the deprecated info about packages.

@dcoutts dcoutts closed this Dec 13, 2012

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment