Re: Can't upload a package named "oath" to Hackage

Seem like hvr had a candidate: https://hackage.haskell.org/package/oath/maintainers/ I got a similar effect with `hackage-cli`, see https://github.com/hackage-trustees/hackage-cli/issues/14#issuecomment-97341... Maybe names that have no accessible candidate anymore should be "freed" on hackage... This would be a feature request to hackage-server. On 2021-12-03 14:57, Edward Kmett wrote:

Did someone else upload a candidate package and then not follow up with a release?

On Fri, Dec 3, 2021 at 7:22 AM Fumiaki Kinoshita mailto:fumiexcel@gmail.com> wrote:

I tried to upload a package called "oath". However I got the following error message:

cabal upload --publish dist-newstyle/sdist/oath-0.0.tar.gz hackage.haskell.org http://hackage.haskell.org username: FumiakiKinoshita hackage.haskell.org http://hackage.haskell.org password: Uploading dist-newstyle/sdist/oath-0.0.tar.gz... Error uploading dist-newstyle/sdist/oath-0.0.tar.gz: http code 403 Error: Upload failed

You are not authorised to upload new versions of this package. The package 'oath' exists already and you are not a member of the maintainer group for this package.

If you believe you should be a member of the maintainer group for this package, then ask an existing maintainer to add you to the group. If this is a package name clash, please pick another name or talk to the maintainers of the existing package.

However, https://hackage.haskell.org/package/oath https://hackage.haskell.org/package/oath does not exist. I'm not sure what is going on