将您自己的错误骇客发布列入黑名单 [英] Blacklisting your own faulty hackage release

查看:144
本文介绍了将您自己的错误骇客发布列入黑名单的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我偶然上传了一个错误的发行版,并试图立即重新上传,但是 cabal 回答了:

 该版本的软件包已经上传。 

根据政策,我们不允许在
发行后更改软件包tarball(所以我们可以保证稳定的md5sum等)。通常的建议是上传新版本的
,如果有必要,将现有的版本列入黑名单。在
特殊情况下,请联系管理员。

好的,我已经增加了版本并上传了正确的发行版,但现在我对黑名单感兴趣正如所建议的那样,错误的释放。然而,对于如何在任何地方做到这一点没有概念。怎么做?他们在黑名单一词中暗含的含义是什么? 。向下滚动到维护人员角落并点击编辑包信息。然后你可以选择点击首选版本



此页面允许您指定版本范围弃用单个软件包版本

弃用的版本不会完全消失,但 cabal-install 会尝试尊重尝试解决依赖关系时的首选项。


I've accidentally uploaded a faulty distribution and tried to reupload it right away, but cabal replied with:

This version of the package has already been uploaded.

As a matter of policy we do not allow package tarballs to be changed after a
release (so we can guarantee stable md5sums etc). The usual recommendation is
to upload a new version, and if necessary blacklist the existing one. In
extraordinary circumstances, contact the administrators.

Okay, I've incremented the version and uploaded the correct distro, but now I am interested in blacklisting the faulty release, as suggested. However there is no notion about how to do that anywhere whatsoever. How to do that? And what do they actually imply by the term "blacklisting"?

解决方案

Go to your package page on Hackage. Scroll down to Maintainers' corner and click on edit package information. Then you'll have an option to click on Preferred versions.

This page allows you to specify version ranges or deprecate individual package versions.

Deprecated versions won't be completely gone, but cabal-install will try to respect the preferences when trying to resolve dependencies.

这篇关于将您自己的错误骇客发布列入黑名单的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆