Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Notification for deprecated versions of packages #372

Closed
lspitzner opened this issue Jun 5, 2015 · 8 comments · Fixed by #1123
Closed

Notification for deprecated versions of packages #372

lspitzner opened this issue Jun 5, 2015 · 8 comments · Fixed by #1123

Comments

@lspitzner
Copy link

lspitzner commented Jun 5, 2015

When browsing the versions of a package, if the currently viewed package is deprecated, there should be a warning (similar to the warning for entirely deprecated packages).

@dcoutts
Copy link
Contributor

dcoutts commented Jul 19, 2015

@dzackgarza maybe?

@gbaz gbaz changed the title Notification for deprecated packages Notification for deprecated versions of packages Mar 20, 2018
@gbaz gbaz self-assigned this Mar 20, 2018
@chreekat
Copy link

Since this is listed as a "good first issue", could someone with know-how quickly sketch an implementation plan for someone to follow?

Wait, maybe I can do it after 30 seconds of digging:

  • Note that there are now two forms of deprecation:
    • whole-package deprecation (see e.g. accelerate-cuda, which does have a deprecation notice)
    • per-version deprecation. See network's deprecation information, and notice that the deprecated version is highlighted as such in the version list, but the deprecated version's specific page still has no notice (that's why this issue should remain open, although I presume it should have been "closed" for some decent portion of its life).
  • Extend this use of isDeprecated, or rename to isPackageDeprecated and introduce isVersionDeprecated
  • Find where is[Package]Deprecated is defined, and make a similar definition for isVersionDeprecated
  • Consider making the deprecation notice stand out more in the design and layout!

@gbaz
Copy link
Contributor

gbaz commented Mar 28, 2018

@gbaz gbaz removed their assignment Mar 28, 2018
@hvr
Copy link
Member

hvr commented Mar 28, 2018

Consider making the deprecation notice stand out more in the design and layout!

Fwiw, I wanted to try to use a colored box like e.g. the light red one used for the warnings at e.g.

http://hackage.haskell.org/package/bad-package-example-0/candidate

or something like that...

@chreekat
Copy link

WIP is here: chreekat#1

As the commit mentions, I'm having trouble with a Hackage mirror, so I haven't test-compiled the changes yet. :)

@chreekat
Copy link

chreekat commented Apr 3, 2018

Trouble persists:

Resolving dependencies...
Notice: installing into a sandbox located at
/home/b/src/hackage-server/.cabal-sandbox
Downloading Cabal-2.2.0.1...
Downloading aeson-1.1.2.0...
Downloading safecopy-0.9.4.1...
Configuring aeson-1.1.2.0...
Configuring safecopy-0.9.4.1...
Downloading xss-sanitize-0.3.5.7...
Unexpected response 503for http://objects-us-west-1.dream.io/hackage-mirror/package/xss-sanitize-0.3.5.7.tar.gz

@gbaz
Copy link
Contributor

gbaz commented Apr 3, 2018

can't you just set your config to use the main server instead of a mirror?

@chreekat
Copy link

chreekat commented Apr 3, 2018

Since this is offtopic (oops, my fault) I'll follow up elsewhere.

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

Successfully merging a pull request may close this issue.

5 participants