From fumiexcel at gmail.com  Fri Dec  3 12:22:17 2021
From: fumiexcel at gmail.com (Fumiaki Kinoshita)
Date: Fri, 3 Dec 2021 21:22:17 +0900
Subject: Can't upload a package named "oath" to Hackage
Message-ID: <CAATCwUkhC5b2p4x8TugJfnhxcPgQWc+3N-4yLhrMaTMin4sWDg@mail.gmail.com>

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 username: FumiakiKinoshita
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 does not exist. I'm not
sure what is going on
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/libraries/attachments/20211203/9e475dc5/attachment.html>

From ekmett at gmail.com  Fri Dec  3 13:57:27 2021
From: ekmett at gmail.com (Edward Kmett)
Date: Fri, 3 Dec 2021 08:57:27 -0500
Subject: Can't upload a package named "oath" to Hackage
In-Reply-To: <CAATCwUkhC5b2p4x8TugJfnhxcPgQWc+3N-4yLhrMaTMin4sWDg@mail.gmail.com>
References: <CAATCwUkhC5b2p4x8TugJfnhxcPgQWc+3N-4yLhrMaTMin4sWDg@mail.gmail.com>
Message-ID: <CAJumaK_EPAaCQgAG6PRb3F3ZgYbk=QTwoSx3h0-sv+dGX=VOpg@mail.gmail.com>

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 <fumiexcel at 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 username: FumiakiKinoshita
> 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 does not exist. I'm not
> sure what is going on
> _______________________________________________
> Libraries mailing list
> Libraries at haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/libraries
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/libraries/attachments/20211203/c1761b80/attachment.html>

From lemming at henning-thielemann.de  Fri Dec  3 14:02:35 2021
From: lemming at henning-thielemann.de (Henning Thielemann)
Date: Fri, 3 Dec 2021 15:02:35 +0100 (CET)
Subject: Can't upload a package named "oath" to Hackage
In-Reply-To: <CAJumaK_EPAaCQgAG6PRb3F3ZgYbk=QTwoSx3h0-sv+dGX=VOpg@mail.gmail.com>
References: <CAATCwUkhC5b2p4x8TugJfnhxcPgQWc+3N-4yLhrMaTMin4sWDg@mail.gmail.com>
 <CAJumaK_EPAaCQgAG6PRb3F3ZgYbk=QTwoSx3h0-sv+dGX=VOpg@mail.gmail.com>
Message-ID: <bc2f83c0-5d87-b5-3289-668ddeadae4@henning-thielemann.de>


On Fri, 3 Dec 2021, Edward Kmett wrote:

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

https://hackage.haskell.org/package/oath/candidates/

Package not found
No such package in package index

From adam at well-typed.com  Fri Dec  3 14:04:34 2021
From: adam at well-typed.com (Adam Gundry)
Date: Fri, 3 Dec 2021 14:04:34 +0000
Subject: Can't upload a package named "oath" to Hackage
In-Reply-To: <CAJumaK_EPAaCQgAG6PRb3F3ZgYbk=QTwoSx3h0-sv+dGX=VOpg@mail.gmail.com>
References: <CAATCwUkhC5b2p4x8TugJfnhxcPgQWc+3N-4yLhrMaTMin4sWDg@mail.gmail.com>
 <CAJumaK_EPAaCQgAG6PRb3F3ZgYbk=QTwoSx3h0-sv+dGX=VOpg@mail.gmail.com>
Message-ID: <925c69e2-a215-b1ae-c75c-da608c6a9683@well-typed.com>

On 03/12/2021 13:57, Edward Kmett wrote:
> Did someone else upload a candidate package and then not follow up with
> a release?

It looks like it: https://hackage.haskell.org/package/oath/maintainers/
lists hvr as maintainer. But there doesn't seem to be a candidate there
any more (perhaps they can be deleted?).


> On Fri, Dec 3, 2021 at 7:22 AM Fumiaki Kinoshita <fumiexcel at gmail.com
> <mailto:fumiexcel at 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


-- 
Adam Gundry, Haskell Consultant
Well-Typed LLP, https://www.well-typed.com/

Registered in England & Wales, OC335890
118 Wymering Mansions, Wymering Road, London W9 2NF, England

From jaro.reinders at gmail.com  Fri Dec  3 14:06:00 2021
From: jaro.reinders at gmail.com (J. Reinders)
Date: Fri, 3 Dec 2021 15:06:00 +0100
Subject: Can't upload a package named "oath" to Hackage
In-Reply-To: <925c69e2-a215-b1ae-c75c-da608c6a9683@well-typed.com>
References: <CAATCwUkhC5b2p4x8TugJfnhxcPgQWc+3N-4yLhrMaTMin4sWDg@mail.gmail.com>
 <CAJumaK_EPAaCQgAG6PRb3F3ZgYbk=QTwoSx3h0-sv+dGX=VOpg@mail.gmail.com>
 <925c69e2-a215-b1ae-c75c-da608c6a9683@well-typed.com>
Message-ID: <EF714F2B-610C-40EA-90AA-1A67FC00CEF5@gmail.com>

There is a candidate:
https://hackage.haskell.org/package/oath-0/candidate

> On 3 Dec 2021, at 15:04, Adam Gundry <adam at well-typed.com> wrote:
> 
> On 03/12/2021 13:57, Edward Kmett wrote:
>> Did someone else upload a candidate package and then not follow up with
>> a release?
> 
> It looks like it: https://hackage.haskell.org/package/oath/maintainers/
> lists hvr as maintainer. But there doesn't seem to be a candidate there
> any more (perhaps they can be deleted?).
> 
> 
>> On Fri, Dec 3, 2021 at 7:22 AM Fumiaki Kinoshita <fumiexcel at gmail.com
>> <mailto:fumiexcel at 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
> 
> 
> -- 
> Adam Gundry, Haskell Consultant
> Well-Typed LLP, https://www.well-typed.com/
> 
> Registered in England & Wales, OC335890
> 118 Wymering Mansions, Wymering Road, London W9 2NF, England
> _______________________________________________
> Libraries mailing list
> Libraries at haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/libraries


From andreas.abel at ifi.lmu.de  Fri Dec  3 14:06:37 2021
From: andreas.abel at ifi.lmu.de (Andreas Abel)
Date: Fri, 3 Dec 2021 15:06:37 +0100
Subject: Can't upload a package named "oath" to Hackage
In-Reply-To: <CAJumaK_EPAaCQgAG6PRb3F3ZgYbk=QTwoSx3h0-sv+dGX=VOpg@mail.gmail.com>
References: <CAATCwUkhC5b2p4x8TugJfnhxcPgQWc+3N-4yLhrMaTMin4sWDg@mail.gmail.com>
 <CAJumaK_EPAaCQgAG6PRb3F3ZgYbk=QTwoSx3h0-sv+dGX=VOpg@mail.gmail.com>
Message-ID: <f2c281cd-d656-3960-31e3-0c5a8e7d8446@ifi.lmu.de>

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-973413297

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 <fumiexcel at gmail.com 
> <mailto:fumiexcel at 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

From andreas.abel at ifi.lmu.de  Fri Dec  3 14:10:37 2021
From: andreas.abel at ifi.lmu.de (Andreas Abel)
Date: Fri, 3 Dec 2021 15:10:37 +0100
Subject: Can't upload a package named "oath" to Hackage
In-Reply-To: <EF714F2B-610C-40EA-90AA-1A67FC00CEF5@gmail.com>
References: <CAATCwUkhC5b2p4x8TugJfnhxcPgQWc+3N-4yLhrMaTMin4sWDg@mail.gmail.com>
 <CAJumaK_EPAaCQgAG6PRb3F3ZgYbk=QTwoSx3h0-sv+dGX=VOpg@mail.gmail.com>
 <925c69e2-a215-b1ae-c75c-da608c6a9683@well-typed.com>
 <EF714F2B-610C-40EA-90AA-1A67FC00CEF5@gmail.com>
Message-ID: <ee0437c2-c3a0-724c-0860-1f039b9ae01f@ifi.lmu.de>

Why isn't such a candidate listed under .../candidates ?

See the candidate here:

   https://hackage.haskell.org/package/oath-0/candidate/oath.cabal

Is such name reservation in the spirit of hackage?
```
name:                oath
version:             0
license:             BSD3
license-file:        LICENSE
maintainer:          hvr at gnu.org
build-type:          Simple
cabal-version:       >=1.10
synopsis: reserved package name
```

I'd hardly believe this, given the hackage trustee practice to only give 
out accounts if there is also a serious package to be uploaded.

On 2021-12-03 15:06, J. Reinders wrote:
> There is a candidate:
> https://hackage.haskell.org/package/oath-0/candidate
> 
>> On 3 Dec 2021, at 15:04, Adam Gundry <adam at well-typed.com> wrote:
>>
>> On 03/12/2021 13:57, Edward Kmett wrote:
>>> Did someone else upload a candidate package and then not follow up with
>>> a release?
>>
>> It looks like it: https://hackage.haskell.org/package/oath/maintainers/
>> lists hvr as maintainer. But there doesn't seem to be a candidate there
>> any more (perhaps they can be deleted?).
>>
>>
>>> On Fri, Dec 3, 2021 at 7:22 AM Fumiaki Kinoshita <fumiexcel at gmail.com
>>> <mailto:fumiexcel at 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
>>
>>
>> -- 
>> Adam Gundry, Haskell Consultant
>> Well-Typed LLP, https://www.well-typed.com/
>>
>> Registered in England & Wales, OC335890
>> 118 Wymering Mansions, Wymering Road, London W9 2NF, England
>> _______________________________________________
>> Libraries mailing list
>> Libraries at haskell.org
>> http://mail.haskell.org/cgi-bin/mailman/listinfo/libraries
> 
> _______________________________________________
> Libraries mailing list
> Libraries at haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/libraries
> 

From jaro.reinders at gmail.com  Fri Dec  3 14:12:15 2021
From: jaro.reinders at gmail.com (J. Reinders)
Date: Fri, 3 Dec 2021 15:12:15 +0100
Subject: Can't upload a package named "oath" to Hackage
In-Reply-To: <ee0437c2-c3a0-724c-0860-1f039b9ae01f@ifi.lmu.de>
References: <CAATCwUkhC5b2p4x8TugJfnhxcPgQWc+3N-4yLhrMaTMin4sWDg@mail.gmail.com>
 <CAJumaK_EPAaCQgAG6PRb3F3ZgYbk=QTwoSx3h0-sv+dGX=VOpg@mail.gmail.com>
 <925c69e2-a215-b1ae-c75c-da608c6a9683@well-typed.com>
 <EF714F2B-610C-40EA-90AA-1A67FC00CEF5@gmail.com>
 <ee0437c2-c3a0-724c-0860-1f039b9ae01f@ifi.lmu.de>
Message-ID: <97B48D9F-9CC6-4F68-A68F-8892E3FDC414@gmail.com>

I found the candidate listed here: https://hackage.haskell.org/packages/candidates/

You have to click the version number “0”, not the name “oath”.

> On 3 Dec 2021, at 15:10, Andreas Abel <andreas.abel at ifi.lmu.de> wrote:
> 
> Why isn't such a candidate listed under .../candidates ?
> 
> See the candidate here:
> 
>  https://hackage.haskell.org/package/oath-0/candidate/oath.cabal
> 
> Is such name reservation in the spirit of hackage?
> ```
> name:                oath
> version:             0
> license:             BSD3
> license-file:        LICENSE
> maintainer:          hvr at gnu.org
> build-type:          Simple
> cabal-version:       >=1.10
> synopsis: reserved package name
> ```
> 
> I'd hardly believe this, given the hackage trustee practice to only give out accounts if there is also a serious package to be uploaded.
> 
> On 2021-12-03 15:06, J. Reinders wrote:
>> There is a candidate:
>> https://hackage.haskell.org/package/oath-0/candidate
>>> On 3 Dec 2021, at 15:04, Adam Gundry <adam at well-typed.com> wrote:
>>> 
>>> On 03/12/2021 13:57, Edward Kmett wrote:
>>>> Did someone else upload a candidate package and then not follow up with
>>>> a release?
>>> 
>>> It looks like it: https://hackage.haskell.org/package/oath/maintainers/
>>> lists hvr as maintainer. But there doesn't seem to be a candidate there
>>> any more (perhaps they can be deleted?).
>>> 
>>> 
>>>> On Fri, Dec 3, 2021 at 7:22 AM Fumiaki Kinoshita <fumiexcel at gmail.com
>>>> <mailto:fumiexcel at 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
>>> 
>>> 
>>> -- 
>>> Adam Gundry, Haskell Consultant
>>> Well-Typed LLP, https://www.well-typed.com/
>>> 
>>> Registered in England & Wales, OC335890
>>> 118 Wymering Mansions, Wymering Road, London W9 2NF, England
>>> _______________________________________________
>>> Libraries mailing list
>>> Libraries at haskell.org
>>> http://mail.haskell.org/cgi-bin/mailman/listinfo/libraries
>> _______________________________________________
>> Libraries mailing list
>> Libraries at haskell.org
>> http://mail.haskell.org/cgi-bin/mailman/listinfo/libraries


From allbery.b at gmail.com  Fri Dec  3 14:22:33 2021
From: allbery.b at gmail.com (Brandon Allbery)
Date: Fri, 3 Dec 2021 09:22:33 -0500
Subject: Can't upload a package named "oath" to Hackage
In-Reply-To: <97B48D9F-9CC6-4F68-A68F-8892E3FDC414@gmail.com>
References: <CAATCwUkhC5b2p4x8TugJfnhxcPgQWc+3N-4yLhrMaTMin4sWDg@mail.gmail.com>
 <CAJumaK_EPAaCQgAG6PRb3F3ZgYbk=QTwoSx3h0-sv+dGX=VOpg@mail.gmail.com>
 <925c69e2-a215-b1ae-c75c-da608c6a9683@well-typed.com>
 <EF714F2B-610C-40EA-90AA-1A67FC00CEF5@gmail.com>
 <ee0437c2-c3a0-724c-0860-1f039b9ae01f@ifi.lmu.de>
 <97B48D9F-9CC6-4F68-A68F-8892E3FDC414@gmail.com>
Message-ID: <CAKFCL4UxV1KoF7aVWhn3p51jfA_RdECamH74M-82zkf2B9SV2A@mail.gmail.com>

I think the problem here might be the immutable (append-only) index,
which makes it difficult to remove and reuse names?

On Fri, Dec 3, 2021 at 9:13 AM J. Reinders <jaro.reinders at gmail.com> wrote:
>
> I found the candidate listed here: https://hackage.haskell.org/packages/candidates/
>
> You have to click the version number “0”, not the name “oath”.
>
> > On 3 Dec 2021, at 15:10, Andreas Abel <andreas.abel at ifi.lmu.de> wrote:
> >
> > Why isn't such a candidate listed under .../candidates ?
> >
> > See the candidate here:
> >
> >  https://hackage.haskell.org/package/oath-0/candidate/oath.cabal
> >
> > Is such name reservation in the spirit of hackage?
> > ```
> > name:                oath
> > version:             0
> > license:             BSD3
> > license-file:        LICENSE
> > maintainer:          hvr at gnu.org
> > build-type:          Simple
> > cabal-version:       >=1.10
> > synopsis: reserved package name
> > ```
> >
> > I'd hardly believe this, given the hackage trustee practice to only give out accounts if there is also a serious package to be uploaded.
> >
> > On 2021-12-03 15:06, J. Reinders wrote:
> >> There is a candidate:
> >> https://hackage.haskell.org/package/oath-0/candidate
> >>> On 3 Dec 2021, at 15:04, Adam Gundry <adam at well-typed.com> wrote:
> >>>
> >>> On 03/12/2021 13:57, Edward Kmett wrote:
> >>>> Did someone else upload a candidate package and then not follow up with
> >>>> a release?
> >>>
> >>> It looks like it: https://hackage.haskell.org/package/oath/maintainers/
> >>> lists hvr as maintainer. But there doesn't seem to be a candidate there
> >>> any more (perhaps they can be deleted?).
> >>>
> >>>
> >>>> On Fri, Dec 3, 2021 at 7:22 AM Fumiaki Kinoshita <fumiexcel at gmail.com
> >>>> <mailto:fumiexcel at 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
> >>>
> >>>
> >>> --
> >>> Adam Gundry, Haskell Consultant
> >>> Well-Typed LLP, https://www.well-typed.com/
> >>>
> >>> Registered in England & Wales, OC335890
> >>> 118 Wymering Mansions, Wymering Road, London W9 2NF, England
> >>> _______________________________________________
> >>> Libraries mailing list
> >>> Libraries at haskell.org
> >>> http://mail.haskell.org/cgi-bin/mailman/listinfo/libraries
> >> _______________________________________________
> >> Libraries mailing list
> >> Libraries at haskell.org
> >> http://mail.haskell.org/cgi-bin/mailman/listinfo/libraries
>
> _______________________________________________
> Libraries mailing list
> Libraries at haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/libraries



-- 
brandon s allbery kf8nh
allbery.b at gmail.com

From lemming at henning-thielemann.de  Fri Dec  3 14:26:40 2021
From: lemming at henning-thielemann.de (Henning Thielemann)
Date: Fri, 3 Dec 2021 15:26:40 +0100 (CET)
Subject: Can't upload a package named "oath" to Hackage
In-Reply-To: <CAKFCL4UxV1KoF7aVWhn3p51jfA_RdECamH74M-82zkf2B9SV2A@mail.gmail.com>
References: <CAATCwUkhC5b2p4x8TugJfnhxcPgQWc+3N-4yLhrMaTMin4sWDg@mail.gmail.com>
 <CAJumaK_EPAaCQgAG6PRb3F3ZgYbk=QTwoSx3h0-sv+dGX=VOpg@mail.gmail.com>
 <925c69e2-a215-b1ae-c75c-da608c6a9683@well-typed.com>
 <EF714F2B-610C-40EA-90AA-1A67FC00CEF5@gmail.com>
 <ee0437c2-c3a0-724c-0860-1f039b9ae01f@ifi.lmu.de>
 <97B48D9F-9CC6-4F68-A68F-8892E3FDC414@gmail.com>
 <CAKFCL4UxV1KoF7aVWhn3p51jfA_RdECamH74M-82zkf2B9SV2A@mail.gmail.com>
Message-ID: <116c3f68-c1fc-157c-6dd6-cc156a107adc@henning-thielemann.de>


On Fri, 3 Dec 2021, Brandon Allbery wrote:

> I think the problem here might be the immutable (append-only) index,
> which makes it difficult to remove and reuse names?

If hvr does not want to do anything with the 'oath' name anymore, he could 
add Fumiaki as maintainer.

From allbery.b at gmail.com  Fri Dec  3 14:27:22 2021
From: allbery.b at gmail.com (Brandon Allbery)
Date: Fri, 3 Dec 2021 09:27:22 -0500
Subject: Can't upload a package named "oath" to Hackage
In-Reply-To: <116c3f68-c1fc-157c-6dd6-cc156a107adc@henning-thielemann.de>
References: <CAATCwUkhC5b2p4x8TugJfnhxcPgQWc+3N-4yLhrMaTMin4sWDg@mail.gmail.com>
 <CAJumaK_EPAaCQgAG6PRb3F3ZgYbk=QTwoSx3h0-sv+dGX=VOpg@mail.gmail.com>
 <925c69e2-a215-b1ae-c75c-da608c6a9683@well-typed.com>
 <EF714F2B-610C-40EA-90AA-1A67FC00CEF5@gmail.com>
 <ee0437c2-c3a0-724c-0860-1f039b9ae01f@ifi.lmu.de>
 <97B48D9F-9CC6-4F68-A68F-8892E3FDC414@gmail.com>
 <CAKFCL4UxV1KoF7aVWhn3p51jfA_RdECamH74M-82zkf2B9SV2A@mail.gmail.com>
 <116c3f68-c1fc-157c-6dd6-cc156a107adc@henning-thielemann.de>
Message-ID: <CAKFCL4W5m75B23Cbpogng7H-fMyYK7T0_owvb0MGvUd-tm0pGw@mail.gmail.com>

hvr's kinda disappeared, though.

On Fri, Dec 3, 2021 at 9:26 AM Henning Thielemann
<lemming at henning-thielemann.de> wrote:
>
>
> On Fri, 3 Dec 2021, Brandon Allbery wrote:
>
> > I think the problem here might be the immutable (append-only) index,
> > which makes it difficult to remove and reuse names?
>
> If hvr does not want to do anything with the 'oath' name anymore, he could
> add Fumiaki as maintainer.



-- 
brandon s allbery kf8nh
allbery.b at gmail.com

From fumiexcel at gmail.com  Fri Dec  3 14:33:30 2021
From: fumiexcel at gmail.com (Fumiaki Kinoshita)
Date: Fri, 3 Dec 2021 23:33:30 +0900
Subject: Can't upload a package named "oath" to Hackage
In-Reply-To: <116c3f68-c1fc-157c-6dd6-cc156a107adc@henning-thielemann.de>
References: <CAATCwUkhC5b2p4x8TugJfnhxcPgQWc+3N-4yLhrMaTMin4sWDg@mail.gmail.com>
 <CAJumaK_EPAaCQgAG6PRb3F3ZgYbk=QTwoSx3h0-sv+dGX=VOpg@mail.gmail.com>
 <925c69e2-a215-b1ae-c75c-da608c6a9683@well-typed.com>
 <EF714F2B-610C-40EA-90AA-1A67FC00CEF5@gmail.com>
 <ee0437c2-c3a0-724c-0860-1f039b9ae01f@ifi.lmu.de>
 <97B48D9F-9CC6-4F68-A68F-8892E3FDC414@gmail.com>
 <CAKFCL4UxV1KoF7aVWhn3p51jfA_RdECamH74M-82zkf2B9SV2A@mail.gmail.com>
 <116c3f68-c1fc-157c-6dd6-cc156a107adc@henning-thielemann.de>
Message-ID: <CAATCwUnQi3FmehTjutt8sGQHy+OPUCu1oUzDG-xfUES_it8MEw@mail.gmail.com>

Looking at other "reserved package names in the list, "all", "project",
"test" are understandable but it's hard to think of any reason why oath
should be reserved. I'd like to get myself added to the maintainers if
possible.

2021年12月3日(金) 23:28 Henning Thielemann <lemming at henning-thielemann.de>:

>
> On Fri, 3 Dec 2021, Brandon Allbery wrote:
>
> > I think the problem here might be the immutable (append-only) index,
> > which makes it difficult to remove and reuse names?
>
> If hvr does not want to do anything with the 'oath' name anymore, he could
> add Fumiaki as maintainer.
> _______________________________________________
> Libraries mailing list
> Libraries at haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/libraries
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/libraries/attachments/20211203/acb0e3c8/attachment.html>

From davean at xkcd.com  Fri Dec  3 17:00:49 2021
From: davean at xkcd.com (davean)
Date: Fri, 3 Dec 2021 12:00:49 -0500
Subject: Can't upload a package named "oath" to Hackage
In-Reply-To: <CAATCwUnQi3FmehTjutt8sGQHy+OPUCu1oUzDG-xfUES_it8MEw@mail.gmail.com>
References: <CAATCwUkhC5b2p4x8TugJfnhxcPgQWc+3N-4yLhrMaTMin4sWDg@mail.gmail.com>
 <CAJumaK_EPAaCQgAG6PRb3F3ZgYbk=QTwoSx3h0-sv+dGX=VOpg@mail.gmail.com>
 <925c69e2-a215-b1ae-c75c-da608c6a9683@well-typed.com>
 <EF714F2B-610C-40EA-90AA-1A67FC00CEF5@gmail.com>
 <ee0437c2-c3a0-724c-0860-1f039b9ae01f@ifi.lmu.de>
 <97B48D9F-9CC6-4F68-A68F-8892E3FDC414@gmail.com>
 <CAKFCL4UxV1KoF7aVWhn3p51jfA_RdECamH74M-82zkf2B9SV2A@mail.gmail.com>
 <116c3f68-c1fc-157c-6dd6-cc156a107adc@henning-thielemann.de>
 <CAATCwUnQi3FmehTjutt8sGQHy+OPUCu1oUzDG-xfUES_it8MEw@mail.gmail.com>
Message-ID: <CABFs2VjBePnBg+Lzh2vMLraUbYsrb=GVvZznZkDZEfC=UZhZUg@mail.gmail.com>

A package takeover request would handle this issue.

On Fri, Dec 3, 2021 at 9:33 AM Fumiaki Kinoshita <fumiexcel at gmail.com>
wrote:

> Looking at other "reserved package names in the list, "all", "project",
> "test" are understandable but it's hard to think of any reason why oath
> should be reserved. I'd like to get myself added to the maintainers if
> possible.
>
> 2021年12月3日(金) 23:28 Henning Thielemann <lemming at henning-thielemann.de>:
>
>>
>> On Fri, 3 Dec 2021, Brandon Allbery wrote:
>>
>> > I think the problem here might be the immutable (append-only) index,
>> > which makes it difficult to remove and reuse names?
>>
>> If hvr does not want to do anything with the 'oath' name anymore, he
>> could
>> add Fumiaki as maintainer.
>> _______________________________________________
>> Libraries mailing list
>> Libraries at haskell.org
>> http://mail.haskell.org/cgi-bin/mailman/listinfo/libraries
>>
> _______________________________________________
> Libraries mailing list
> Libraries at haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/libraries
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/libraries/attachments/20211203/72137c5d/attachment.html>

From evincarofautumn at gmail.com  Wed Dec  8 19:59:33 2021
From: evincarofautumn at gmail.com (Jon Purdy)
Date: Wed, 8 Dec 2021 11:59:33 -0800
Subject: Can't upload a package named "oath" to Hackage
In-Reply-To: <CAATCwUnQi3FmehTjutt8sGQHy+OPUCu1oUzDG-xfUES_it8MEw@mail.gmail.com>
References: <CAATCwUkhC5b2p4x8TugJfnhxcPgQWc+3N-4yLhrMaTMin4sWDg@mail.gmail.com>
 <CAJumaK_EPAaCQgAG6PRb3F3ZgYbk=QTwoSx3h0-sv+dGX=VOpg@mail.gmail.com>
 <925c69e2-a215-b1ae-c75c-da608c6a9683@well-typed.com>
 <EF714F2B-610C-40EA-90AA-1A67FC00CEF5@gmail.com>
 <ee0437c2-c3a0-724c-0860-1f039b9ae01f@ifi.lmu.de>
 <97B48D9F-9CC6-4F68-A68F-8892E3FDC414@gmail.com>
 <CAKFCL4UxV1KoF7aVWhn3p51jfA_RdECamH74M-82zkf2B9SV2A@mail.gmail.com>
 <116c3f68-c1fc-157c-6dd6-cc156a107adc@henning-thielemann.de>
 <CAATCwUnQi3FmehTjutt8sGQHy+OPUCu1oUzDG-xfUES_it8MEw@mail.gmail.com>
Message-ID: <CAE3FWBsuB536wprBQz+qWRpUNXQ1vcLoxrt0s+c4NEZ=L934dg@mail.gmail.com>

On Fri, Dec 3, 2021 at 6:34 AM Fumiaki Kinoshita <fumiexcel at gmail.com>
wrote:

> Looking at other "reserved package names in the list, "all", "project",
> "test" are understandable but it's hard to think of any reason why oath
> should be reserved.
>

When I first saw this thread, I guessed that it was reserved to prevent
typosquatting for “oauth” (OAuth <https://en.wikipedia.org/wiki/OAuth>).
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/libraries/attachments/20211208/f2ce842a/attachment.html>

From carter.schonwald at gmail.com  Wed Dec  8 21:52:42 2021
From: carter.schonwald at gmail.com (Carter Schonwald)
Date: Wed, 8 Dec 2021 16:52:42 -0500
Subject: Can't upload a package named "oath" to Hackage
In-Reply-To: <CAE3FWBsuB536wprBQz+qWRpUNXQ1vcLoxrt0s+c4NEZ=L934dg@mail.gmail.com>
References: <CAATCwUkhC5b2p4x8TugJfnhxcPgQWc+3N-4yLhrMaTMin4sWDg@mail.gmail.com>
 <CAJumaK_EPAaCQgAG6PRb3F3ZgYbk=QTwoSx3h0-sv+dGX=VOpg@mail.gmail.com>
 <925c69e2-a215-b1ae-c75c-da608c6a9683@well-typed.com>
 <EF714F2B-610C-40EA-90AA-1A67FC00CEF5@gmail.com>
 <ee0437c2-c3a0-724c-0860-1f039b9ae01f@ifi.lmu.de>
 <97B48D9F-9CC6-4F68-A68F-8892E3FDC414@gmail.com>
 <CAKFCL4UxV1KoF7aVWhn3p51jfA_RdECamH74M-82zkf2B9SV2A@mail.gmail.com>
 <116c3f68-c1fc-157c-6dd6-cc156a107adc@henning-thielemann.de>
 <CAATCwUnQi3FmehTjutt8sGQHy+OPUCu1oUzDG-xfUES_it8MEw@mail.gmail.com>
 <CAE3FWBsuB536wprBQz+qWRpUNXQ1vcLoxrt0s+c4NEZ=L934dg@mail.gmail.com>
Message-ID: <CAHYVw0z-uYzF7T4f6aoYopcS6ZzmGcLhHAqsaOhGsD+f=mGf-Q@mail.gmail.com>

Yeah. Typo squatting is or case squatting in helping preventing weird
security / bug issues sounds sane to me

On Wed, Dec 8, 2021 at 3:00 PM Jon Purdy <evincarofautumn at gmail.com> wrote:

>
> On Fri, Dec 3, 2021 at 6:34 AM Fumiaki Kinoshita <fumiexcel at gmail.com>
> wrote:
>
>> Looking at other "reserved package names in the list, "all", "project",
>> "test" are understandable but it's hard to think of any reason why oath
>> should be reserved.
>>
>
> When I first saw this thread, I guessed that it was reserved to prevent
> typosquatting for “oauth” (OAuth <https://en.wikipedia.org/wiki/OAuth>).
>
> _______________________________________________
> Libraries mailing list
> Libraries at haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/libraries
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/libraries/attachments/20211208/6ddc122e/attachment.html>

From david.feuer at gmail.com  Wed Dec  8 21:58:39 2021
From: david.feuer at gmail.com (David Feuer)
Date: Wed, 8 Dec 2021 16:58:39 -0500
Subject: Can't upload a package named "oath" to Hackage
In-Reply-To: <CAHYVw0z-uYzF7T4f6aoYopcS6ZzmGcLhHAqsaOhGsD+f=mGf-Q@mail.gmail.com>
References: <CAATCwUkhC5b2p4x8TugJfnhxcPgQWc+3N-4yLhrMaTMin4sWDg@mail.gmail.com>
 <CAJumaK_EPAaCQgAG6PRb3F3ZgYbk=QTwoSx3h0-sv+dGX=VOpg@mail.gmail.com>
 <925c69e2-a215-b1ae-c75c-da608c6a9683@well-typed.com>
 <EF714F2B-610C-40EA-90AA-1A67FC00CEF5@gmail.com>
 <ee0437c2-c3a0-724c-0860-1f039b9ae01f@ifi.lmu.de>
 <97B48D9F-9CC6-4F68-A68F-8892E3FDC414@gmail.com>
 <CAKFCL4UxV1KoF7aVWhn3p51jfA_RdECamH74M-82zkf2B9SV2A@mail.gmail.com>
 <116c3f68-c1fc-157c-6dd6-cc156a107adc@henning-thielemann.de>
 <CAATCwUnQi3FmehTjutt8sGQHy+OPUCu1oUzDG-xfUES_it8MEw@mail.gmail.com>
 <CAE3FWBsuB536wprBQz+qWRpUNXQ1vcLoxrt0s+c4NEZ=L934dg@mail.gmail.com>
 <CAHYVw0z-uYzF7T4f6aoYopcS6ZzmGcLhHAqsaOhGsD+f=mGf-Q@mail.gmail.com>
Message-ID: <CAMgWh9uE93hG3jfh8XXzz6U9nsxsUHv0Ta-zpob__odQv1ip5A@mail.gmail.com>

How are the trustees to know whether someone "deserves" to take a security
sensitive name? And "typos" can often be intentional when two packages each
deserve similar names. I think it's reasonable for trustees to step in if a
name is actually abused, but I don't support squatting.

On Wed, Dec 8, 2021, 4:53 PM Carter Schonwald <carter.schonwald at gmail.com>
wrote:

> Yeah. Typo squatting is or case squatting in helping preventing weird
> security / bug issues sounds sane to me
>
> On Wed, Dec 8, 2021 at 3:00 PM Jon Purdy <evincarofautumn at gmail.com>
> wrote:
>
>>
>> On Fri, Dec 3, 2021 at 6:34 AM Fumiaki Kinoshita <fumiexcel at gmail.com>
>> wrote:
>>
>>> Looking at other "reserved package names in the list, "all", "project",
>>> "test" are understandable but it's hard to think of any reason why oath
>>> should be reserved.
>>>
>>
>> When I first saw this thread, I guessed that it was reserved to prevent
>> typosquatting for “oauth” (OAuth <https://en.wikipedia.org/wiki/OAuth>).
>>
>> _______________________________________________
>> Libraries mailing list
>> Libraries at haskell.org
>> http://mail.haskell.org/cgi-bin/mailman/listinfo/libraries
>>
> _______________________________________________
> Libraries mailing list
> Libraries at haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/libraries
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/libraries/attachments/20211208/736cb998/attachment.html>

From fumiexcel at gmail.com  Thu Dec  9 01:15:13 2021
From: fumiexcel at gmail.com (Fumiaki Kinoshita)
Date: Thu, 9 Dec 2021 10:15:13 +0900
Subject: Can't upload a package named "oath" to Hackage
In-Reply-To: <CAMgWh9uE93hG3jfh8XXzz6U9nsxsUHv0Ta-zpob__odQv1ip5A@mail.gmail.com>
References: <CAATCwUkhC5b2p4x8TugJfnhxcPgQWc+3N-4yLhrMaTMin4sWDg@mail.gmail.com>
 <CAJumaK_EPAaCQgAG6PRb3F3ZgYbk=QTwoSx3h0-sv+dGX=VOpg@mail.gmail.com>
 <925c69e2-a215-b1ae-c75c-da608c6a9683@well-typed.com>
 <EF714F2B-610C-40EA-90AA-1A67FC00CEF5@gmail.com>
 <ee0437c2-c3a0-724c-0860-1f039b9ae01f@ifi.lmu.de>
 <97B48D9F-9CC6-4F68-A68F-8892E3FDC414@gmail.com>
 <CAKFCL4UxV1KoF7aVWhn3p51jfA_RdECamH74M-82zkf2B9SV2A@mail.gmail.com>
 <116c3f68-c1fc-157c-6dd6-cc156a107adc@henning-thielemann.de>
 <CAATCwUnQi3FmehTjutt8sGQHy+OPUCu1oUzDG-xfUES_it8MEw@mail.gmail.com>
 <CAE3FWBsuB536wprBQz+qWRpUNXQ1vcLoxrt0s+c4NEZ=L934dg@mail.gmail.com>
 <CAHYVw0z-uYzF7T4f6aoYopcS6ZzmGcLhHAqsaOhGsD+f=mGf-Q@mail.gmail.com>
 <CAMgWh9uE93hG3jfh8XXzz6U9nsxsUHv0Ta-zpob__odQv1ip5A@mail.gmail.com>
Message-ID: <CAATCwUmw58z92ha8y0Cid9UW4PRL9GBkysBDDrj3cWSGZyBAAQ@mail.gmail.com>

If typo-squatting is a thing, they should be done against existing
packages, not for non-existing ones... I don't think it should prevent
uploading an innocent package anyway.

Btw there are way more confusing ones, like promise vs. promises, future
vs. futures...

2021年12月9日(木) 6:59 David Feuer <david.feuer at gmail.com>:

> How are the trustees to know whether someone "deserves" to take a security
> sensitive name? And "typos" can often be intentional when two packages each
> deserve similar names. I think it's reasonable for trustees to step in if a
> name is actually abused, but I don't support squatting.
>
> On Wed, Dec 8, 2021, 4:53 PM Carter Schonwald <carter.schonwald at gmail.com>
> wrote:
>
>> Yeah. Typo squatting is or case squatting in helping preventing weird
>> security / bug issues sounds sane to me
>>
>> On Wed, Dec 8, 2021 at 3:00 PM Jon Purdy <evincarofautumn at gmail.com>
>> wrote:
>>
>>>
>>> On Fri, Dec 3, 2021 at 6:34 AM Fumiaki Kinoshita <fumiexcel at gmail.com>
>>> wrote:
>>>
>>>> Looking at other "reserved package names in the list, "all", "project",
>>>> "test" are understandable but it's hard to think of any reason why oath
>>>> should be reserved.
>>>>
>>>
>>> When I first saw this thread, I guessed that it was reserved to prevent
>>> typosquatting for “oauth” (OAuth <https://en.wikipedia.org/wiki/OAuth>).
>>>
>>> _______________________________________________
>>> Libraries mailing list
>>> Libraries at haskell.org
>>> http://mail.haskell.org/cgi-bin/mailman/listinfo/libraries
>>>
>> _______________________________________________
>> Libraries mailing list
>> Libraries at haskell.org
>> http://mail.haskell.org/cgi-bin/mailman/listinfo/libraries
>>
> _______________________________________________
> Libraries mailing list
> Libraries at haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/libraries
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/libraries/attachments/20211209/e0207f4f/attachment.html>

From hecate at glitchbra.in  Thu Dec  9 08:10:44 2021
From: hecate at glitchbra.in (=?UTF-8?Q?H=c3=a9cate?=)
Date: Thu, 9 Dec 2021 09:10:44 +0100
Subject: Can't upload a package named "oath" to Hackage
In-Reply-To: <CAATCwUmw58z92ha8y0Cid9UW4PRL9GBkysBDDrj3cWSGZyBAAQ@mail.gmail.com>
References: <CAATCwUkhC5b2p4x8TugJfnhxcPgQWc+3N-4yLhrMaTMin4sWDg@mail.gmail.com>
 <CAJumaK_EPAaCQgAG6PRb3F3ZgYbk=QTwoSx3h0-sv+dGX=VOpg@mail.gmail.com>
 <925c69e2-a215-b1ae-c75c-da608c6a9683@well-typed.com>
 <EF714F2B-610C-40EA-90AA-1A67FC00CEF5@gmail.com>
 <ee0437c2-c3a0-724c-0860-1f039b9ae01f@ifi.lmu.de>
 <97B48D9F-9CC6-4F68-A68F-8892E3FDC414@gmail.com>
 <CAKFCL4UxV1KoF7aVWhn3p51jfA_RdECamH74M-82zkf2B9SV2A@mail.gmail.com>
 <116c3f68-c1fc-157c-6dd6-cc156a107adc@henning-thielemann.de>
 <CAATCwUnQi3FmehTjutt8sGQHy+OPUCu1oUzDG-xfUES_it8MEw@mail.gmail.com>
 <CAE3FWBsuB536wprBQz+qWRpUNXQ1vcLoxrt0s+c4NEZ=L934dg@mail.gmail.com>
 <CAHYVw0z-uYzF7T4f6aoYopcS6ZzmGcLhHAqsaOhGsD+f=mGf-Q@mail.gmail.com>
 <CAMgWh9uE93hG3jfh8XXzz6U9nsxsUHv0Ta-zpob__odQv1ip5A@mail.gmail.com>
 <CAATCwUmw58z92ha8y0Cid9UW4PRL9GBkysBDDrj3cWSGZyBAAQ@mail.gmail.com>
Message-ID: <420e7cba-571b-066f-a02b-5968a27e9345@glitchbra.in>

It seems like we're extrapolating quite a bit without actual input from 
the Hackage Admins/Trustees on that one. I'd rather have Gershom's 
opinion on that topic.

Le 09/12/2021 à 02:15, Fumiaki Kinoshita a écrit :
> If typo-squatting is a thing, they should be done against existing 
> packages, not for non-existing ones... I don't think it should prevent 
> uploading an innocent package anyway.
>
> Btw there are way more confusing ones, like promise vs. promises, 
> future vs. futures...
>
> 2021年12月9日(木) 6:59 David Feuer <david.feuer at gmail.com>:
>
>     How are the trustees to know whether someone "deserves" to take a
>     security sensitive name? And "typos" can often be intentional when
>     two packages each deserve similar names. I think it's reasonable
>     for trustees to step in if a name is actually abused, but I don't
>     support squatting.
>
>     On Wed, Dec 8, 2021, 4:53 PM Carter Schonwald
>     <carter.schonwald at gmail.com> wrote:
>
>         Yeah. Typo squatting is or case squatting in helping
>         preventing weird security / bug issues sounds sane to me
>
>         On Wed, Dec 8, 2021 at 3:00 PM Jon Purdy
>         <evincarofautumn at gmail.com> wrote:
>
>
>             On Fri, Dec 3, 2021 at 6:34 AM Fumiaki Kinoshita
>             <fumiexcel at gmail.com> wrote:
>
>                 Looking at other "reserved package names in the list,
>                 "all", "project", "test" are understandable but it's
>                 hard to think of any reason why oath should be reserved.
>
>
>             When I first saw this thread, I guessed that it was
>             reserved to prevent typosquatting for “oauth” (OAuth
>             <https://en.wikipedia.org/wiki/OAuth>).
>
>             _______________________________________________
>             Libraries mailing list
>             Libraries at haskell.org
>             http://mail.haskell.org/cgi-bin/mailman/listinfo/libraries
>
>         _______________________________________________
>         Libraries mailing list
>         Libraries at haskell.org
>         http://mail.haskell.org/cgi-bin/mailman/listinfo/libraries
>
>     _______________________________________________
>     Libraries mailing list
>     Libraries at haskell.org
>     http://mail.haskell.org/cgi-bin/mailman/listinfo/libraries
>
>
> _______________________________________________
> Libraries mailing list
> Libraries at haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/libraries

-- 
Hécate ✨
🐦: @TechnoEmpress
IRC: Hecate
WWW:https://glitchbra.in
RUN: BSD
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/libraries/attachments/20211209/228b38b6/attachment.html>

From andreas.abel at ifi.lmu.de  Thu Dec  9 09:47:41 2021
From: andreas.abel at ifi.lmu.de (Andreas Abel)
Date: Thu, 9 Dec 2021 10:47:41 +0100
Subject: Can't upload a package named "oath" to Hackage
In-Reply-To: <420e7cba-571b-066f-a02b-5968a27e9345@glitchbra.in>
References: <CAATCwUkhC5b2p4x8TugJfnhxcPgQWc+3N-4yLhrMaTMin4sWDg@mail.gmail.com>
 <CAJumaK_EPAaCQgAG6PRb3F3ZgYbk=QTwoSx3h0-sv+dGX=VOpg@mail.gmail.com>
 <925c69e2-a215-b1ae-c75c-da608c6a9683@well-typed.com>
 <EF714F2B-610C-40EA-90AA-1A67FC00CEF5@gmail.com>
 <ee0437c2-c3a0-724c-0860-1f039b9ae01f@ifi.lmu.de>
 <97B48D9F-9CC6-4F68-A68F-8892E3FDC414@gmail.com>
 <CAKFCL4UxV1KoF7aVWhn3p51jfA_RdECamH74M-82zkf2B9SV2A@mail.gmail.com>
 <116c3f68-c1fc-157c-6dd6-cc156a107adc@henning-thielemann.de>
 <CAATCwUnQi3FmehTjutt8sGQHy+OPUCu1oUzDG-xfUES_it8MEw@mail.gmail.com>
 <CAE3FWBsuB536wprBQz+qWRpUNXQ1vcLoxrt0s+c4NEZ=L934dg@mail.gmail.com>
 <CAHYVw0z-uYzF7T4f6aoYopcS6ZzmGcLhHAqsaOhGsD+f=mGf-Q@mail.gmail.com>
 <CAMgWh9uE93hG3jfh8XXzz6U9nsxsUHv0Ta-zpob__odQv1ip5A@mail.gmail.com>
 <CAATCwUmw58z92ha8y0Cid9UW4PRL9GBkysBDDrj3cWSGZyBAAQ@mail.gmail.com>
 <420e7cba-571b-066f-a02b-5968a27e9345@glitchbra.in>
Message-ID: <67b969fe-e92c-14de-b4ad-699cefb13a8c@ifi.lmu.de>

Looks like there is no policy yet for name reservation/squatting on 
hackage but I think something is needed.  There are some questions we 
should answer.  As usual, such questions were irrelevant in the pioneer 
days but are gaining importance as the community grows:

1. Is name reservation a thing that should be allowed?
    If yes it would have to be open to everyone, not just to an elite.
    Currently, if you want to become a hackage "uploader", you have to 
have a reasonable package, not just a name you want to reserve.

2. When do reserved names expire?
    A reasonable time span would be say 1-3 years.
    After that, continued reservation should only be granted exceptionally.
    Connected to this question is:  When are dead packages removed from 
hackage?  When is a package dead?
    A dead package squats a name in the same way as a reservation.

3. Who decides on name disputes?
    Are the hackage trustees the arbitration panel?
    What is the process for solving a dispute?

I think the package names on hackage are like brands or domain names in 
business.  These are the only non-duplicable resource; source code and 
its hosting can always be duplicated (granted an open-source license).
In larger societies where not everyone knows everyone, common resources 
need some government.

Cheers,
Andreas

On 2021-12-09 09:10, Hécate wrote:
> It seems like we're extrapolating quite a bit without actual input from 
> the Hackage Admins/Trustees on that one. I'd rather have Gershom's 
> opinion on that topic.
> 
> Le 09/12/2021 à 02:15, Fumiaki Kinoshita a écrit :
>> If typo-squatting is a thing, they should be done against existing 
>> packages, not for non-existing ones... I don't think it should prevent 
>> uploading an innocent package anyway.
>>
>> Btw there are way more confusing ones, like promise vs. promises, 
>> future vs. futures...
>>
>> 2021年12月9日(木) 6:59 David Feuer <david.feuer at gmail.com>:
>>
>>     How are the trustees to know whether someone "deserves" to take a
>>     security sensitive name? And "typos" can often be intentional when
>>     two packages each deserve similar names. I think it's reasonable
>>     for trustees to step in if a name is actually abused, but I don't
>>     support squatting.
>>
>>     On Wed, Dec 8, 2021, 4:53 PM Carter Schonwald
>>     <carter.schonwald at gmail.com> wrote:
>>
>>         Yeah. Typo squatting is or case squatting in helping
>>         preventing weird security / bug issues sounds sane to me
>>
>>         On Wed, Dec 8, 2021 at 3:00 PM Jon Purdy
>>         <evincarofautumn at gmail.com> wrote:
>>
>>
>>             On Fri, Dec 3, 2021 at 6:34 AM Fumiaki Kinoshita
>>             <fumiexcel at gmail.com> wrote:
>>
>>                 Looking at other "reserved package names in the list,
>>                 "all", "project", "test" are understandable but it's
>>                 hard to think of any reason why oath should be reserved.
>>
>>
>>             When I first saw this thread, I guessed that it was
>>             reserved to prevent typosquatting for “oauth” (OAuth
>>             <https://en.wikipedia.org/wiki/OAuth>).

From andrew.lelechenko at gmail.com  Sat Dec 11 01:35:12 2021
From: andrew.lelechenko at gmail.com (Andrew Lelechenko)
Date: Sat, 11 Dec 2021 01:35:12 +0000
Subject: bytestring-0.11.2.0
Message-ID: <ACD4B252-8E52-45C6-BA42-905FA3C780FE@gmail.com>

On behalf of maintainers I'm happy to announce that bytestring-0.11.2.0 (http://hackage.haskell.org/package/bytestring-0.11.2.0) is finally released.

Highlights from the changelog (https://github.com/haskell/bytestring/blob/0.11.2.0/Changelog.md):

* New functions:
   * ultra-fast SIMD-based `isValidUtf8` validator,
   * `foldr'`, `foldr1'`, `scanl1`, `scanr`, `scanr1`, `takeEnd`, `dropEnd`, `takeWhileEnd`, `dropWhileEnd`, `spanEnd`, `breakEnd` for lazy `ByteString`,
   * `writeFile` to dump `Builder` directly,
   * `fromFilePath` and `toFilePath` for locale-aware conversions.
* Performance improvements:
   * speed up `floatDec` and `doubleDec` up to 10x using Ryu algorithm,
   * new SIMD-based `count` is up to 5x faster,
   * improve inlining of `foldl`, `foldl'`, `foldr`, `foldr'`, `mapAccumL`, `mapAccumR`, `scanl`, `scanr` and `filter`,
   * faster internal loop in `unfoldrN`,
   * use a static lookup table for Base16 `Builder`s.
* Add `Lift` instances for `ByteString` and `ShortByteString`.
* Put `HasCallStack` constraints onto partial functions.

Many people contributed their time and effort to make this release happen. Just to name a few in no particular order, mostly according to `git log`:

* Koz Ross
* Lawrence Wu
* Sylvain Henry
* Andreas Abel
* Ignat Insarov
* Luke Clifton
* Kyriakos Papachrysanthou
* Oleg Grenrus
* Simon Jakobi
* Cameron SkamDart
* Callan McGill
* Georg Rudoy
* Nanami Yokodake
* Hécate Kleidukos
* Viktor Dukhovni
* me

Best regards,
Andrew

From justksqsf at gmail.com  Sun Dec 19 09:53:47 2021
From: justksqsf at gmail.com (Kai Ma)
Date: Sun, 19 Dec 2021 17:53:47 +0800
Subject: Add non-escaping show functions
Message-ID: <CDE72F35-F2A8-46F6-99B9-D37A3FEEAF30@gmail.com>

Hi all!

A few months ago I proposed to change the escaping behavior of `show`. The general consensus is that it will introduce hard-to-find and unpredictable amount of breakage.

However, I still think there should be a standard (i.e. living in base) solution to that problem. Instead of changing existing instances, we can add new functions. Therefore, I propose:

1. Add `showNE` [1] to `Show`, with a default implementation `showNE = show`.
2. Add `printNE x = putStrLn (showNE x)`.
3. Change ghci’s default print function to `printNE`.
4. Document that `show` escapes strings so its output will support ASCII terminals, where `showNE` is limited to only terminals that support Unicode.

This proposal benefits ghci without breaking any existing code, and the older behavior can be restored by `:set -interactive-print print`.

Q&A:

- Why not just use existing packages, like pretty-simple, for this purpose?

  I believe ghci should support this behavior (non-escaping) out of box without installing any third-party packages.

- Why not just add `printNE` which undoes escaping?

  Definitely doable. However, it feels more like a hack than a solution.

According to the new CLC process, this proposal should be submitted to https://github.com/haskell/core-libraries-committee/issues. But I’d like to hear some early feedback, and I will implement this proposal.

[1] “NE” stands for non-escaping. This is only a temporary name in order to avoid bike-shedding.

Regards,
Kai

From fa-ml at ariis.it  Sun Dec 19 11:05:22 2021
From: fa-ml at ariis.it (Francesco Ariis)
Date: Sun, 19 Dec 2021 12:05:22 +0100
Subject: Add non-escaping show functions
In-Reply-To: <CDE72F35-F2A8-46F6-99B9-D37A3FEEAF30@gmail.com>
References: <CDE72F35-F2A8-46F6-99B9-D37A3FEEAF30@gmail.com>
Message-ID: <Yb8R8oeWTRUqZJf+@mkiii.casa>

Hello Kai,

Il 19 dicembre 2021 alle 17:53 Kai Ma ha scritto:
> This proposal benefits ghci without breaking any existing code, and the
> older behavior can be restored by `:set -interactive-print print`.

Just to check if I understood correctly: only ghci will benefit from this
proposal, right? Are there other place where printNE/showNE could be useful?
Why not a new typeclass instead of modifying the venerable `Show`?

From justksqsf at gmail.com  Sun Dec 19 14:38:09 2021
From: justksqsf at gmail.com (Kai Ma)
Date: Sun, 19 Dec 2021 22:38:09 +0800
Subject: Add non-escaping show functions
In-Reply-To: <Yb8R8oeWTRUqZJf+@mkiii.casa>
References: <CDE72F35-F2A8-46F6-99B9-D37A3FEEAF30@gmail.com>
 <Yb8R8oeWTRUqZJf+@mkiii.casa>
Message-ID: <F160E31D-2034-4238-9800-EE4120BBCC74@gmail.com>

Hello Francesco,

> Just to check if I understood correctly: only ghci will benefit from this
> proposal, right? Are there other place where printNE/showNE could be useful?

The motivation is to enhance the experience of ghci, but IMO there are a few other places it can be useful. Off the top of my head are:

1. Some development tools, like IHP’s tool, can use `showNE` in place of `show` to directly output Unicode strings.
2. At least Text (and perhaps ByteString) can make use of `showNE`.

> Why not a new typeclass instead of modifying the venerable `Show`?


People are deriving Show for their types today, so adding methods to Show is a non-intrusive and backward-compatible way to update old code smoothly.

Of course, an alternative way is to make GHC derive two instances simultaneously, for Show and for (say) ShowNE, but I’m not entirely sure whether it’s good practice. I agree adding a new class is better if deriving two instances is allowed.


Kai

From hecate at glitchbra.in  Sun Dec 19 18:33:07 2021
From: hecate at glitchbra.in (=?UTF-8?Q?H=c3=a9cate?=)
Date: Sun, 19 Dec 2021 19:33:07 +0100
Subject: Add non-escaping show functions
In-Reply-To: <F160E31D-2034-4238-9800-EE4120BBCC74@gmail.com>
References: <CDE72F35-F2A8-46F6-99B9-D37A3FEEAF30@gmail.com>
 <Yb8R8oeWTRUqZJf+@mkiii.casa>
 <F160E31D-2034-4238-9800-EE4120BBCC74@gmail.com>
Message-ID: <caffc759-7695-7e56-9d19-ab53ee9dd3d5@glitchbra.in>

I would be very interested to integrate this in my text-display¹ library!


¹ https://github.com/haskell-text/text-display

Le 19/12/2021 à 15:38, Kai Ma a écrit :
> Hello Francesco,
>
>> Just to check if I understood correctly: only ghci will benefit from this
>> proposal, right? Are there other place where printNE/showNE could be useful?
> The motivation is to enhance the experience of ghci, but IMO there are a few other places it can be useful. Off the top of my head are:
>
> 1. Some development tools, like IHP’s tool, can use `showNE` in place of `show` to directly output Unicode strings.
> 2. At least Text (and perhaps ByteString) can make use of `showNE`.
>
>> Why not a new typeclass instead of modifying the venerable `Show`?
>
> People are deriving Show for their types today, so adding methods to Show is a non-intrusive and backward-compatible way to update old code smoothly.
>
> Of course, an alternative way is to make GHC derive two instances simultaneously, for Show and for (say) ShowNE, but I’m not entirely sure whether it’s good practice. I agree adding a new class is better if deriving two instances is allowed.
>
>
> Kai
> _______________________________________________
> Libraries mailing list
> Libraries at haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/libraries

-- 
Hécate ✨
🐦: @TechnoEmpress
IRC: Hecate
WWW: https://glitchbra.in
RUN: BSD


From justksqsf at gmail.com  Mon Dec 20 04:26:39 2021
From: justksqsf at gmail.com (Kai Ma)
Date: Mon, 20 Dec 2021 12:26:39 +0800
Subject: Add non-escaping show functions
In-Reply-To: <CDE72F35-F2A8-46F6-99B9-D37A3FEEAF30@gmail.com>
References: <CDE72F35-F2A8-46F6-99B9-D37A3FEEAF30@gmail.com>
Message-ID: <1C6CECFD-A193-438F-9818-D61FDC7BCFED@gmail.com>

I have opened an issue here [1], with modifications based on my experience of implementation.

[1] https://github.com/haskell/core-libraries-committee/issues/25

Kai

From ekmett at gmail.com  Mon Dec 20 16:02:35 2021
From: ekmett at gmail.com (Edward Kmett)
Date: Mon, 20 Dec 2021 11:02:35 -0500
Subject: Add non-escaping show functions
In-Reply-To: <1C6CECFD-A193-438F-9818-D61FDC7BCFED@gmail.com>
References: <CDE72F35-F2A8-46F6-99B9-D37A3FEEAF30@gmail.com>
 <1C6CECFD-A193-438F-9818-D61FDC7BCFED@gmail.com>
Message-ID: <CAJumaK-t-JrfbyTu-86k=WH3hT4ZOEAPpaTavVd9ZtLMqsoTmQ@mail.gmail.com>

I have some concerns that this is not as general as it could be and that it
is more invasive than one might think to "do this right."

e.g. One usecase where custom Show instances are often written is to take a
record type and transform it into something that shows with just a
positional constructor. This typically delegates to the existing showsPrec
of the fields.

I'd kind of expect "showNE" to do something sensible for such a record, but
here it'll get delegated away by default to the normal implementation,
which will delegate to showsPrec not something that tries to preserve this
property for its part.

You could move to using a 'showsPrecNE' instead of 'showNE' to enable you
to walk down to those leaf level strings you want to escape, but now
anything with a non-trivial Show instance is going to require two copies of
that non-trivial showsPrec code to be put in place.

Without something like that, as written, this proposal would make it so you
get very different output for "some unicode string" and ("some unicode
string","some other unicode string"), which seems less than optimal.

On the other hand, duplicating all the work in custom Show instances also
seems suboptimal.

I don't have a solution that I like, though several options present
themselves, but I did want to throw up this concern before folks ran away
and pushed this into base.

-Edward



On Sun, Dec 19, 2021 at 11:26 PM Kai Ma <justksqsf at gmail.com> wrote:

> I have opened an issue here [1], with modifications based on my experience
> of implementation.
>
> [1] https://github.com/haskell/core-libraries-committee/issues/25
>
> Kai
> _______________________________________________
> Libraries mailing list
> Libraries at haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/libraries
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/libraries/attachments/20211220/499a64f7/attachment.html>

From andrew.lelechenko at gmail.com  Fri Dec 24 19:01:46 2021
From: andrew.lelechenko at gmail.com (Andrew Lelechenko)
Date: Fri, 24 Dec 2021 19:01:46 +0000
Subject: CLC Election January 2022
Message-ID: <05348F6C-0CDC-499B-97C8-3C89E63AA3BE@gmail.com>

The Core Libraries Committee is seeking for a new member!

# Who should apply?

Anyone who meets the following criteria should apply:

* Candidates should have enough bandwidth to review merge requests to `base` on a semi-frequent basis (2 to 3 per month), and sustain this for their 3 years term in a healthy manner.
* Candidates should be able to contribute opinions and analysis to issues raised by the community as a part of the CLC proposal process on a semi-frequent basis (2 to 3 per month).
* Candidates should be good communicators, and at least be able to articulate to the CLC team when they will be available vs. unavailable.
* Candidates should be productive, and be able to follow through on merge requests and conversations to their completion in a diligent and timely manner.

We encourage any and all who satisfy these requirements to apply. Please note that we are not looking for the biggest galaxy brain in the room - quite the opposite. We are looking for productive, motivated individuals who want to help support the ecosystem that we love. As such, we hope to build a broad sample of the community.

Candidates, who stand for CLC Elections back in September, are most welcome to apply again.

# How can I apply?

To apply for one of these positions, send an email to core-libraries-committee at haskell.org that consists of the following data:

* The header "CLC Election January 2022 - {your name}".
* Why you think you’re a good fit given the above criteria.
* If applicable, please point us to some code you’ve written.

Please apply before Feb 1. 

Best regards,
Andrew

From andrew.lelechenko at gmail.com  Fri Dec 24 19:17:30 2021
From: andrew.lelechenko at gmail.com (Andrew Lelechenko)
Date: Fri, 24 Dec 2021 19:17:30 +0000
Subject: text-2.0 with UTF8 is finally released!
Message-ID: <05104C77-5B72-4BC6-BBC1-6E8A01EF0D55@gmail.com>

I’m happy to announce that text-2.0 with UTF-8 underlying representation has been finally released: https://hackage.haskell.org/package/text-2.0. The release is identical to rc2, circulated earlier.

Changelog: https://hackage.haskell.org/package/text-2.0/changelog

Please give it a try. Here is a cabal.project template: https://gist.github.com/Bodigrim/9834568f075be36a1c65e7aaba6a15db

This work would not be complete without a blazingly-fast UTF-8 validator, submitted by Koz Ross into bytestring-0.11.2.0, whose contributions were sourced via HF as an in-kind donation from MLabs. I would like to thank Emily Pillmore for encouraging me to take on this project, helping with the proposal and permissions. I’m grateful to my fellow text maintainers, who’ve been carefully reviewing my work in course of the last six months, as well as helpful and responsive maintainers of downstream packages and GHC developers. Thanks all, it was a pleasant journey!

Best regards,
Andrew

From tom-lists-haskell-cafe-2017 at jaguarpaw.co.uk  Fri Dec 24 19:24:50 2021
From: tom-lists-haskell-cafe-2017 at jaguarpaw.co.uk (Tom Ellis)
Date: Fri, 24 Dec 2021 19:24:50 +0000
Subject: [Haskell-cafe] text-2.0 with UTF8 is finally released!
In-Reply-To: <05104C77-5B72-4BC6-BBC1-6E8A01EF0D55@gmail.com>
References: <05104C77-5B72-4BC6-BBC1-6E8A01EF0D55@gmail.com>
Message-ID: <20211224192450.GD17923@cloudinit-builder>

This is great news.  Congratulations to Andrew and everyone else who
contributed!

On Fri, Dec 24, 2021 at 07:17:30PM +0000, Andrew Lelechenko wrote:
> I’m happy to announce that text-2.0 with UTF-8 underlying representation has been finally released: https://hackage.haskell.org/package/text-2.0. The release is identical to rc2, circulated earlier.
> 
> Changelog: https://hackage.haskell.org/package/text-2.0/changelog
> 
> Please give it a try. Here is a cabal.project template: https://gist.github.com/Bodigrim/9834568f075be36a1c65e7aaba6a15db
> 
> This work would not be complete without a blazingly-fast UTF-8 validator, submitted by Koz Ross into bytestring-0.11.2.0, whose contributions were sourced via HF as an in-kind donation from MLabs. I would like to thank Emily Pillmore for encouraging me to take on this project, helping with the proposal and permissions. I’m grateful to my fellow text maintainers, who’ve been carefully reviewing my work in course of the last six months, as well as helpful and responsive maintainers of downstream packages and GHC developers. Thanks all, it was a pleasant journey!

From hecate at glitchbra.in  Sat Dec 25 21:37:58 2021
From: hecate at glitchbra.in (=?UTF-8?Q?H=c3=a9cate?=)
Date: Sat, 25 Dec 2021 22:37:58 +0100
Subject: text-2.0 with UTF8 is finally released!
In-Reply-To: <05104C77-5B72-4BC6-BBC1-6E8A01EF0D55@gmail.com>
References: <05104C77-5B72-4BC6-BBC1-6E8A01EF0D55@gmail.com>
Message-ID: <0a301b0c-2cd8-db0e-5022-2bde171b3b7e@glitchbra.in>

Congratulations!! I'm excited to see this in use. :)
Thank you for the Christmas present!

Le 24/12/2021 à 20:17, Andrew Lelechenko a écrit :
> I’m happy to announce that text-2.0 with UTF-8 underlying representation has been finally released: https://hackage.haskell.org/package/text-2.0. The release is identical to rc2, circulated earlier.
>
> Changelog: https://hackage.haskell.org/package/text-2.0/changelog
>
> Please give it a try. Here is a cabal.project template: https://gist.github.com/Bodigrim/9834568f075be36a1c65e7aaba6a15db
>
> This work would not be complete without a blazingly-fast UTF-8 validator, submitted by Koz Ross into bytestring-0.11.2.0, whose contributions were sourced via HF as an in-kind donation from MLabs. I would like to thank Emily Pillmore for encouraging me to take on this project, helping with the proposal and permissions. I’m grateful to my fellow text maintainers, who’ve been carefully reviewing my work in course of the last six months, as well as helpful and responsive maintainers of downstream packages and GHC developers. Thanks all, it was a pleasant journey!
>
> Best regards,
> Andrew
> _______________________________________________
> Libraries mailing list
> Libraries at haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/libraries

-- 
Hécate ✨
🐦: @TechnoEmpress
IRC: Hecate
WWW: https://glitchbra.in
RUN: BSD


From emilypi at cohomolo.gy  Sat Dec 25 23:02:15 2021
From: emilypi at cohomolo.gy (Emily Pillmore)
Date: Sat, 25 Dec 2021 23:02:15 +0000
Subject: text-2.0 with UTF8 is finally released!
In-Reply-To: <0a301b0c-2cd8-db0e-5022-2bde171b3b7e@glitchbra.in>
References: <05104C77-5B72-4BC6-BBC1-6E8A01EF0D55@gmail.com>
 <0a301b0c-2cd8-db0e-5022-2bde171b3b7e@glitchbra.in>
Message-ID: <kxmfge3u.291e0685-a9c7-4e1a-b5ca-0a760f91bce9@we.are.superhuman.com>

Great work Bodigrim! Congratulations and thank you for all of your hard work :)

On Sat, Dec 25, 2021 at 2:37 PM, Hécate < hecate at glitchbra.in > wrote:

> 
> 
> 
> Congratulations!! I'm excited to see this in use. :) Thank you for the
> Christmas present!
> 
> 
> 
> Le 24/12/2021 à 20:17, Andrew Lelechenko a écrit :
> 
> 
>> 
>> 
>> I’m happy to announce that text-2.0 with UTF-8 underlying representation
>> has been finally released: https:/ / hackage. haskell. org/ package/ text-2.
>> 0 ( https://hackage.haskell.org/package/text-2.0 ). The release is
>> identical to rc2, circulated earlier.
>> 
>> 
>> 
>> Changelog: https:/ / hackage. haskell. org/ package/ text-2. 0/ changelog (
>> https://hackage.haskell.org/package/text-2.0/changelog )
>> 
>> 
>> 
>> Please give it a try. Here is a cabal.project template: https:/ / gist. github.
>> com/ Bodigrim/ 9834568f075be36a1c65e7aaba6a15db (
>> https://gist.github.com/Bodigrim/9834568f075be36a1c65e7aaba6a15db )
>> 
>> 
>> 
>> This work would not be complete without a blazingly-fast UTF-8 validator,
>> submitted by Koz Ross into bytestring-0.11.2.0, whose contributions were
>> sourced via HF as an in-kind donation from MLabs. I would like to thank
>> Emily Pillmore for encouraging me to take on this project, helping with
>> the proposal and permissions. I’m grateful to my fellow text maintainers,
>> who’ve been carefully reviewing my work in course of the last six months,
>> as well as helpful and responsive maintainers of downstream packages and
>> GHC developers. Thanks all, it was a pleasant journey!
>> 
>> 
>> 
>> Best regards,
>> Andrew
>> _______________________________________________
>> Libraries mailing list
>> Libraries@ haskell. org ( Libraries at haskell.org )
>> http:/ / mail. haskell. org/ cgi-bin/ mailman/ listinfo/ libraries (
>> http://mail.haskell.org/cgi-bin/mailman/listinfo/libraries )
>> 
>> 
> 
> 
> 
> --
> Hécate ✨
> 🐦: @TechnoEmpress
> IRC: Hecate
> WWW: https:/ / glitchbra. in ( https://glitchbra.in/ )
> RUN: BSD
> 
> 
> 
> _______________________________________________
> Libraries mailing list
> Libraries@ haskell. org ( Libraries at haskell.org )
> http:/ / mail. haskell. org/ cgi-bin/ mailman/ listinfo/ libraries (
> http://mail.haskell.org/cgi-bin/mailman/listinfo/libraries )
> 
> 
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/libraries/attachments/20211225/90dbd06a/attachment.html>

From harendra.kumar at gmail.com  Sun Dec 26 07:14:41 2021
From: harendra.kumar at gmail.com (Harendra Kumar)
Date: Sun, 26 Dec 2021 12:44:41 +0530
Subject: [Haskell-cafe] text-2.0 with UTF8 is finally released!
In-Reply-To: <05104C77-5B72-4BC6-BBC1-6E8A01EF0D55@gmail.com>
References: <05104C77-5B72-4BC6-BBC1-6E8A01EF0D55@gmail.com>
Message-ID: <CAPW+kkYCP6_xuXAGPwnLaAh25L6hz83r2Z=sBZGDNB0i37dXCw@mail.gmail.com>

Amazing work. Thanks Andrew and all others involved!

On Sat, 25 Dec 2021 at 00:48, Andrew Lelechenko <andrew.lelechenko at gmail.com>
wrote:

> I’m happy to announce that text-2.0 with UTF-8 underlying representation
> has been finally released: https://hackage.haskell.org/package/text-2.0.
> The release is identical to rc2, circulated earlier.
>
> Changelog: https://hackage.haskell.org/package/text-2.0/changelog
>
> Please give it a try. Here is a cabal.project template:
> https://gist.github.com/Bodigrim/9834568f075be36a1c65e7aaba6a15db
>
> This work would not be complete without a blazingly-fast UTF-8 validator,
> submitted by Koz Ross into bytestring-0.11.2.0, whose contributions were
> sourced via HF as an in-kind donation from MLabs. I would like to thank
> Emily Pillmore for encouraging me to take on this project, helping with the
> proposal and permissions. I’m grateful to my fellow text maintainers,
> who’ve been carefully reviewing my work in course of the last six months,
> as well as helpful and responsive maintainers of downstream packages and
> GHC developers. Thanks all, it was a pleasant journey!
>
> Best regards,
> Andrew
> _______________________________________________
> Haskell-Cafe mailing list
> To (un)subscribe, modify options or view archives go to:
> http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe
> Only members subscribed via the mailman list are allowed to post.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/libraries/attachments/20211226/efb57390/attachment.html>

From andreas.abel at ifi.lmu.de  Mon Dec 27 00:19:39 2021
From: andreas.abel at ifi.lmu.de (Andreas Abel)
Date: Mon, 27 Dec 2021 01:19:39 +0100
Subject: text-2.0 with UTF8 is finally released!
In-Reply-To: <05104C77-5B72-4BC6-BBC1-6E8A01EF0D55@gmail.com>
References: <05104C77-5B72-4BC6-BBC1-6E8A01EF0D55@gmail.com>
Message-ID: <cf78f184-309f-f580-ea83-2fc63b6e9f78@ifi.lmu.de>

Great, Andrew!
Thanks for maintaining backwards-compatibility.

> Please give it a try. Here is a cabal.project template: 
https://gist.github.com/Bodigrim/9834568f075be36a1c65e7aaba6a15db

I revised text upper bounds for

- Agda
- HsYAML
- blaze-builder
- cassava
- regex-tdfa

Cheers,
Andresa

On 2021-12-24 20:17, Andrew Lelechenko wrote:
> I’m happy to announce that text-2.0 with UTF-8 underlying representation has been finally released: https://hackage.haskell.org/package/text-2.0. The release is identical to rc2, circulated earlier.
> 
> Changelog: https://hackage.haskell.org/package/text-2.0/changelog
> 
> Please give it a try. Here is a cabal.project template: https://gist.github.com/Bodigrim/9834568f075be36a1c65e7aaba6a15db
> 
> This work would not be complete without a blazingly-fast UTF-8 validator, submitted by Koz Ross into bytestring-0.11.2.0, whose contributions were sourced via HF as an in-kind donation from MLabs. I would like to thank Emily Pillmore for encouraging me to take on this project, helping with the proposal and permissions. I’m grateful to my fellow text maintainers, who’ve been carefully reviewing my work in course of the last six months, as well as helpful and responsive maintainers of downstream packages and GHC developers. Thanks all, it was a pleasant journey!
> 
> Best regards,
> Andrew
> _______________________________________________
> Libraries mailing list
> Libraries at haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/libraries