Why can't we re-install the template-haskell package?

[Moritz Angermann]

Dear friends,

as I'm working on making lib:ghc re-installable [1][2].

Ideally I'd prefer we only had to freeze rts + ghc-prim
and maybe base (which would implicate the integer library).

However, we apparently can't re-install Template Haskell
I'm told.  Not just not upgrade it, but not even re-install
it (same version). I've attached some rough dependency graph
(which I hope is correct for ghc 8.8). Fixing template-haskell
implies ghc-boot-th, pretty, deepseq and array.

Can someone shed some light onto the details here? What
are the fundamental issues we can't reinstall template-haskell?

Cheers,
 Moritz

--
[1]: https://gitlab.haskell.org/ghc/ghc/merge_requests/490
[2]: https://gitlab.haskell.org/ghc/ghc/merge_requests/506

ghc-8.8-deps.pdf
Description: Adobe PDF document


signature.asc
Description: Message signed with OpenPGP
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: Haddock tree spongled

[Alec Theriault]

Merging Haddock into GHC’s subtree would undoubtedly simplify the GHC workflow 
for patches affecting Haddock. There are a couple other considerations though:
Haddock currently sees the bulk of its contributions and bug fixes on its 
stable branches, not the ghc-head branch (which is the one GHC tracks). Not 
only is this exactly the opposite of GHC, but it also makes outside 
contributions and CI much simpler.
The Haddock project is actually 3 packages, two of which are libraries, one of 
which is expected to build on GHC going all the way back to the 7.4.* series. 
AFAICT, the packages kept in GHC’s source tree usually advance in lockstep with 
GHC.
Running the full GHC CI for most of Haddock’s changes seems a waste of 
resources and an unnecessary delay. Besides, Haddock actually has a larger test 
suite, which is only expected to compile on the stable branch (although I try 
to keep it running on ghc-head with the help of head.hackage). I recently 
incorporated the other part of Haddock’s testsuite into GHC’s testsuite, so I’m 
hoping there will be less breakage coming from ghc-head.
Interleaving git histories would (mostly) just make bisecting both GHC and 
Haddock more of a pain.
The right way to solve this problem is probably to find a better way of 
factoring GHC-specific functionality out and putting only that in the GHC tree. 
This is a good long term goal, but I don’t think we are quite there yet. Some 
other ongoing changes in both GHC and Haddock are blocking the way forward on 
this front…

Thanks,
Alec

> On Mar 6, 2019, at 1:26 PM, Boespflug, Mathieu  wrote:
> 
> If the status quo is poor, then why not merge the two? git-subtree won't fix 
> the problem and will arguably be even harder to manage than submodules.
> 
> Best,
> 
> On Wed, 6 Mar 2019 at 15:59, Ben Gamari  > wrote:
> Sylvain Henry mailto:sylv...@haskus.fr>> writes:
> 
> > Why don't we just put Haddock into GHC's repository? It was proposed in 
> > a previous discussion in February [1] and it would avoid the bad 
> > experience of having it as a submodule while keeping it in sync.
> >
> I'm reluctant to keep it in the GHC tree; it really is a separate
> project with separate maintainership, dependencies, and contributors.
> 
> That being said, I do agree that the status quo is pretty poor. I was
> going to suggest managing it with git-subtree instead, but I'm not sure
> this would be much of an improvement.
> 
> Cheers,
> 
>  - Ben
> ___
> ghc-devs mailing list
> ghc-devs@haskell.org 
> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs 
> 
> ___
> ghc-devs mailing list
> ghc-devs@haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: Haddock tree spongled

[Ben Gamari]

"Boespflug, Mathieu"  writes:

> If the status quo is poor, then why not merge the two? git-subtree won't
> fix the problem and will arguably be even harder to manage than submodules.
>
The status quo is indeed awkward at times. However, merging Haddock into
GHC would only serve to shuffle this awkwardness to be felt by a
different group of people.

Currently the awkward workflow is contributing a GHC patch that affects
the subset of GHC's AST that Haddock cares about. This is unfortunate
but not unexpected; working with coupled systems always brings
challenges. However, this is not the common case.

If we were to merge Haddock into GHC then we make harder the lives of
those who work on Haddock independently from GHC. All Haddock changes
would need to go through the GHC tree, we would need to setup special CI
rules to run only the haddock testsuite, and the histories of the two
orthogonal projects would be awkwardly coupled. Given that most of the
commits in the haddock repository are independent from GHC this seems
like a poor trade-off.

As a general rule I think we would be better off trying to loosen GHC's
coupling to other projects than further entrench them.

Cheers,

- Ben


signature.asc
Description: PGP signature
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: Haddock tree spongled

[Boespflug, Mathieu]

If the status quo is poor, then why not merge the two? git-subtree won't
fix the problem and will arguably be even harder to manage than submodules.

Best,

On Wed, 6 Mar 2019 at 15:59, Ben Gamari  wrote:

> Sylvain Henry  writes:
>
> > Why don't we just put Haddock into GHC's repository? It was proposed in
> > a previous discussion in February [1] and it would avoid the bad
> > experience of having it as a submodule while keeping it in sync.
> >
> I'm reluctant to keep it in the GHC tree; it really is a separate
> project with separate maintainership, dependencies, and contributors.
>
> That being said, I do agree that the status quo is pretty poor. I was
> going to suggest managing it with git-subtree instead, but I'm not sure
> this would be much of an improvement.
>
> Cheers,
>
>  - Ben
> ___
> ghc-devs mailing list
> ghc-devs@haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
>
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: [Haskell-cafe] Final steps in GHC's Trac-to-GitLab migration

[Phyx]

Can they be sent from a different email address than the main.
Gitlab+margebot are quite. Ahum, noisy.. and filtering based on message
content has a potential for false positives.

Kind regards,
Tamar

On Wed, Mar 6, 2019, 12:33 Matthew Pickering 
wrote:

> I think gitlab can be configured so notifications are sent for new issues
> and comments on issues which should achieve the same thing as the mailing
> list did?
>
>
>
> On Wed, Mar 6, 2019 at 12:00 PM Sylvain Henry  wrote:
>
>> I use it to track tickets and I would also like to see it continued.
>>
>> Sylvain
>>
>> On 06/03/2019 12:33, Ara Adkins wrote:
>> > Personally I would like to see it continued, but it may not be worth
>> the work if I’m in a minority here.
>> >
>> > A potential stopgap would be to ‘watch’ the GHC project on our gitlab
>> instance, but I can’t see any way to decide to get emails for notifications
>> rather than having to check in at GitLab all the time.
>> >
>> > _ara
>> >
>> >> On 6 Mar 2019, at 11:21, Ben Gamari  wrote:
>> >>
>> >>
>> >>
>> >>> On March 6, 2019 6:11:49 AM EST, Ara Adkins  wrote:
>> >>> Super excited for this! Thank you to everyone whose put in so much
>> hard
>> >>> work to get it done!
>> >>>
>> >>> One question: what is happening with the trac tickets mailing list? I
>> >>> imagine it’ll be going away, but for those of us that use it to keep
>> >>> track of things is there a recommended alternative?
>> >>>
>> >> The ghc-commits list will continue to work.
>> >>
>> >> The ghc-tickets list is a good question. I suspect that under gitlab
>> there will be less need for this list but we may still want to continue
>> maintaining it regardless for continuity's sake. Thoughts?
>> >>
>> >> Cheers,
>> >>
>> >> - Ben
>> >>
>> >>
>> >>
>> >>> Best,
>> >>> _ara
>> >>>
>>  On 6 Mar 2019, at 01:21, Ben Gamari  wrote:
>> 
>>  Hi everyone,
>> 
>>  Over the past few weeks we have been hard at work sorting out the
>>  last batch of issues in GHC's Trac-to-GitLab import [1]. At this
>> >>> point I
>>  believe we have sorted out the issues which are necessary to perform
>> >>> the
>>  final migration:
>> 
>>  * We are missing only two tickets (#1436 and #2074 which will require
>> >>> a
>>    bit of manual intervention to import due to extremely large
>>    description lengths)
>> 
>>  * A variety of markup issues have been resolved
>> 
>>  * More metadata is now preserved via labels. We may choose to
>>    reorganize or eliminate some of these labels in time but it's
>> >>> easier
>>    to remove metadata after import than it is to reintroduce it. The
>>    logic which maps Trac metadata to GitLab labels can be found here
>> >>> [2]
>>  * We now generate a Wiki table of contents [3] which is significantly
>>    more readable than GitLab's default page list. This will be updated
>>    by a cron job until underlying GitLab pages list becomes more
>>    readable.
>> 
>>  * We now generate redirects for Trac ticket and Wiki links (although
>>    this isn't visible in the staging instance)
>> 
>>  * Milestones are now properly closed when closed in Trac
>> 
>>  * Mapping between Trac and GitLab usernames is now a bit more robust
>> 
>>  As in previous test imports, we would appreciate it if you could have
>> >>> a
>>  look over the import and let us know of any problems your encounter.
>> 
>>  If no serious issues are identified with the staging site we plan to
>>  proceed with the migration this coming weekend. The current migration
>>  plan is to perform the final import on gitlab.haskell.org on
>> >>> Saturday, 9
>>  March 2019.
>> 
>>  This will involve both gitlab.haskell.org and ghc.haskell.org being
>> >>> down
>>  for likely the entirety of the day Saturday and likely some of Sunday
>>  (EST time zone). Read-only access will be available to
>>  gitlab.staging.haskell.org for ticket lookup while the import is
>>  underway.
>> 
>>  After the import we will wait at least a week or so before we begin
>> >>> the
>>  process of decommissioning Trac, which will be kept in read-only mode
>>  for the duration.
>> 
>>  Do let me know if the 9 March timing is problematic.
>> 
>>  Cheers,
>> 
>>  - Ben
>> 
>> 
>>  [1] https://gitlab.staging.haskell.org/ghc/ghc
>>  [2]
>> >>>
>> https://github.com/bgamari/trac-to-remarkup/blob/master/TicketImport.hs#L227
>>  [3] https://gitlab.staging.haskell.org/ghc/ghc/wikis/index
>>  ___
>>  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.
>> >> --
>> >> Sent from my Android device with K-9 Mail. Please excuse my brevity.
>> > 

Re: [Haskell-cafe] Final steps in GHC's Trac-to-GitLab migration

[Ara Adkins]

I think that's a reliable replacement for the ghc-tickets mailing list if
it works well. I'll have to see once the cut-over happens!

On Wed, 6 Mar 2019 at 16:44, Ben Gamari  wrote:

> Ara Adkins  writes:
>
> > That would be perfect if so. I couldn't find a way to do it when I looked
> > earlier, but I may well have missed something!
> >
> If you navigate to the GHC project page [1] while logged in you should
> find a little bell [2] button to the right of the "GHC" heading. If you
> click on this and select "Custom" from the drop-down you can choose
> precisely which notifications you want sent.
>
> Cheers,
>
> - Ben
>
>
> [1] https://gitlab.haskell.org/ghc/ghc
> [2]
> https://docs.gitlab.com/ee/workflow/notifications.html#project-settings
> ___
> ghc-devs mailing list
> ghc-devs@haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
>
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: [ANNOUNCE] GHC 8.6.4 is now available

[Shayne Fletcher via ghc-devs]

On Wed, Mar 6, 2019 at 11:39 AM Ben Gamari  wrote:

> Shayne Fletcher via ghc-devs  writes:
>
> > On Wed, Mar 6, 2019 at 11:09 AM Shayne Fletcher <
> > shayne.fletc...@digitalasset.com> wrote:
> >
> >>
> >>
> >>> On Tue, Mar 5, 2019 at 3:53 PM Ben Gamari  wrote:
> >>>
> 
>  Hello everyone,
> 
>  The GHC team is very happy to announce the availability of GHC 8.6.4,
> a
>  bugfix release in the GHC 8.6 series.
> 
> >>>
> >>> There doesn't seem to be a  ghc-8.6.4-release tag of
> >>> http://git.haskell.org/ghc.git? Can you advise me on a magic
> invocation
> >>> that would let me get a checkout of the repository at the release SHA?
> >>>
> [...]
> > Related : the `ANNOUNCE` file at least seems very out-of-date.
> >
> Hi Shayne,
>
> You should find the tag on https://gitlab.haskell.org/ghc/ghc, which is
> now the official upstream. That being said, I am a bit
> surprised that it wasn't mirrored to git.haskell.org.
>
>
Yep, thanks Ben and Matt. Got it.

> That being said, I am a bit surprised that it wasn't mirrored to
git.haskell.org.

Yes! Kind of worrying ... Will you be following through on that?


> Cheers,
>
> - Ben
>

-- 
Shayne Fletcher
Language Engineer
c: +1 917 699 7763
e: em...@digitalasset.com  
Digital Asset Holdings, LLC
4 World Trade Center150
Greenwich Street, 47th Floor

New York, NY 10007, USA

digitalasset.com 

-- 
This message, and any attachments, is for the intended recipient(s) only, 
may contain information that is privileged, confidential and/or proprietary 
and subject to important terms and conditions available at 
http://www.digitalasset.com/emaildisclaimer.html 
. If you are not the 
intended recipient, please delete this message.
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: [Haskell-cafe] Final steps in GHC's Trac-to-GitLab migration

[Ben Gamari]

Ara Adkins  writes:

> That would be perfect if so. I couldn't find a way to do it when I looked
> earlier, but I may well have missed something!
>
If you navigate to the GHC project page [1] while logged in you should
find a little bell [2] button to the right of the "GHC" heading. If you
click on this and select "Custom" from the drop-down you can choose
precisely which notifications you want sent.

Cheers,

- Ben


[1] https://gitlab.haskell.org/ghc/ghc
[2] https://docs.gitlab.com/ee/workflow/notifications.html#project-settings


signature.asc
Description: PGP signature
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: [ANNOUNCE] GHC 8.6.4 is now available

[Ben Gamari]

Shayne Fletcher via ghc-devs  writes:

> On Wed, Mar 6, 2019 at 11:09 AM Shayne Fletcher <
> shayne.fletc...@digitalasset.com> wrote:
>
>>
>>
>>> On Tue, Mar 5, 2019 at 3:53 PM Ben Gamari  wrote:
>>>

 Hello everyone,

 The GHC team is very happy to announce the availability of GHC 8.6.4, a
 bugfix release in the GHC 8.6 series.

>>>
>>> There doesn't seem to be a  ghc-8.6.4-release tag of
>>> http://git.haskell.org/ghc.git? Can you advise me on a magic invocation
>>> that would let me get a checkout of the repository at the release SHA?
>>>
>>
>> Oh wait! Is it the SHA in the file `GIT_COMMIT_ID`?
>>
>>
> No, apparently not:
> ```
> fatal: reference is not a tree: aac18e9a08e6de9648e1a62d849dcd409f407df8
> ```
> Related : the `ANNOUNCE` file at least seems very out-of-date.
>
Hi Shayne,

You should find the tag on https://gitlab.haskell.org/ghc/ghc, which is
now the official upstream. That being said, I am a bit
surprised that it wasn't mirrored to git.haskell.org.

Cheers,

- Ben


signature.asc
Description: PGP signature
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: [ANNOUNCE] GHC 8.6.4 is now available

[Matthew Pickering]

You probably want to use the gitlab remote rather than the git.haskell.org
one.

Matt

On Wed, Mar 6, 2019 at 4:16 PM Shayne Fletcher via ghc-devs <
ghc-devs@haskell.org> wrote:

>
> On Wed, Mar 6, 2019 at 11:09 AM Shayne Fletcher <
> shayne.fletc...@digitalasset.com> wrote:
>
>>
>>
>>> On Tue, Mar 5, 2019 at 3:53 PM Ben Gamari  wrote:
>>>

 Hello everyone,

 The GHC team is very happy to announce the availability of GHC 8.6.4, a
 bugfix release in the GHC 8.6 series.

>>>
>>> There doesn't seem to be a ghc-8.6.4-release tag of
>>> http://git.haskell.org/ghc.git? Can you advise me on a magic invocation
>>> that would let me get a checkout of the repository at the release SHA?
>>>
>>
>> Oh wait! Is it the SHA in the file `GIT_COMMIT_ID`?
>>
>>
> No, apparently not:
> ```
> fatal: reference is not a tree: aac18e9a08e6de9648e1a62d849dcd409f407df8
> ```
> Related : the `ANNOUNCE` file at least seems very out-of-date.
>
> --
> Shayne Fletcher
> Language Engineer
> c: +1 917 699 7763
> e: em...@digitalasset.com  
> Digital Asset Holdings, LLC
> 4 World Trade Center
>   150 Greenwich Street, 47th Floor
> 
> New York, NY 10007, USA
> 
> digitalasset.com 
>
>
>
> This message, and any attachments, is for the intended recipient(s) only,
> may contain information that is privileged, confidential and/or proprietary
> and subject to important terms and conditions available at
> http://www.digitalasset.com/emaildisclaimer.html. If you are not the
> intended recipient, please delete this message.
> ___
> ghc-devs mailing list
> ghc-devs@haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
>
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: [ANNOUNCE] GHC 8.6.4 is now available

[Shayne Fletcher via ghc-devs]

On Wed, Mar 6, 2019 at 11:09 AM Shayne Fletcher <
shayne.fletc...@digitalasset.com> wrote:

>
>
>> On Tue, Mar 5, 2019 at 3:53 PM Ben Gamari  wrote:
>>
>>>
>>> Hello everyone,
>>>
>>> The GHC team is very happy to announce the availability of GHC 8.6.4, a
>>> bugfix release in the GHC 8.6 series.
>>>
>>
>> There doesn't seem to be a  ghc-8.6.4-release tag of
>> http://git.haskell.org/ghc.git? Can you advise me on a magic invocation
>> that would let me get a checkout of the repository at the release SHA?
>>
>
> Oh wait! Is it the SHA in the file `GIT_COMMIT_ID`?
>
>
No, apparently not:
```
fatal: reference is not a tree: aac18e9a08e6de9648e1a62d849dcd409f407df8
```
Related : the `ANNOUNCE` file at least seems very out-of-date.

-- 
Shayne Fletcher
Language Engineer
c: +1 917 699 7763
e: em...@digitalasset.com  
Digital Asset Holdings, LLC
4 World Trade Center150
Greenwich Street, 47th Floor

New York, NY 10007, USA

digitalasset.com 

-- 
This message, and any attachments, is for the intended recipient(s) only, 
may contain information that is privileged, confidential and/or proprietary 
and subject to important terms and conditions available at 
http://www.digitalasset.com/emaildisclaimer.html 
. If you are not the 
intended recipient, please delete this message.
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: [ANNOUNCE] GHC 8.6.4 is now available

[Shayne Fletcher via ghc-devs]

On Wed, Mar 6, 2019 at 10:59 AM Shayne Fletcher <
shayne.fletc...@digitalasset.com> wrote:

> Sorry if you get two of these messages (having some email client problems
> :) )!
>
> Hi Ben,
>
> On Tue, Mar 5, 2019 at 3:53 PM Ben Gamari  wrote:
>
>>
>> Hello everyone,
>>
>> The GHC team is very happy to announce the availability of GHC 8.6.4, a
>> bugfix release in the GHC 8.6 series.
>>
>
> There doesn't seem to be a  ghc-8.6.4-release tag of
> http://git.haskell.org/ghc.git? Can you advise me on a magic invocation
> that would let me get a checkout of the repository at the release SHA?
>

Oh wait! Is it the SHA in the file `GIT_COMMIT_ID`?

-- 
Shayne Fletcher
Language Engineer
c: +1 917 699 7763
e: em...@digitalasset.com  
Digital Asset Holdings, LLC
4 World Trade Center150
Greenwich Street, 47th Floor

New York, NY 10007, USA

digitalasset.com 

-- 
This message, and any attachments, is for the intended recipient(s) only, 
may contain information that is privileged, confidential and/or proprietary 
and subject to important terms and conditions available at 
http://www.digitalasset.com/emaildisclaimer.html 
. If you are not the 
intended recipient, please delete this message.
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Fwd: [ANNOUNCE] GHC 8.6.4 is now available

[Shayne Fletcher via ghc-devs]

Sorry if you get two of these messages (having some email client problems
:) )!

Hi Ben,

On Tue, Mar 5, 2019 at 3:53 PM Ben Gamari  wrote:

>
> Hello everyone,
>
> The GHC team is very happy to announce the availability of GHC 8.6.4, a
> bugfix release in the GHC 8.6 series.
>

There doesn't seem to be a  ghc-8.6.4-release tag of
http://git.haskell.org/ghc.git? Can you advise me on a magic invocation
that would let me get a checkout of the repository at the release SHA?

-- 
This message, and any attachments, is for the intended recipient(s) only, 
may contain information that is privileged, confidential and/or proprietary 
and subject to important terms and conditions available at 
http://www.digitalasset.com/emaildisclaimer.html 
. If you are not the 
intended recipient, please delete this message.
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: [ANNOUNCE] GHC 8.6.4 is now available

[Shayne Fletcher via ghc-devs]

Hi Ben,

On Tue, Mar 5, 2019 at 3:53 PM Ben Gamari  wrote:

>
> Hello everyone,
>
> The GHC team is very happy to announce the availability of GHC 8.6.4, a
> bugfix release in the GHC 8.6 series.
>

There doesn't seem to be a  ghc-8.6.4-release tag of
http://git.haskell.org/ghc.git? Can you advise me on a magic invocation
that would let me get a checkout of the repository at the release SHA?

-- 
This message, and any attachments, is for the intended recipient(s) only, 
may contain information that is privileged, confidential and/or proprietary 
and subject to important terms and conditions available at 
http://www.digitalasset.com/emaildisclaimer.html 
. If you are not the 
intended recipient, please delete this message.
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: Haddock tree spongled

[Ben Gamari]

Sylvain Henry  writes:

> Why don't we just put Haddock into GHC's repository? It was proposed in 
> a previous discussion in February [1] and it would avoid the bad 
> experience of having it as a submodule while keeping it in sync.
>
I'm reluctant to keep it in the GHC tree; it really is a separate
project with separate maintainership, dependencies, and contributors.

That being said, I do agree that the status quo is pretty poor. I was
going to suggest managing it with git-subtree instead, but I'm not sure
this would be much of an improvement.

Cheers,

 - Ben


signature.asc
Description: PGP signature
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: Haddock tree spongled

[Sylvain Henry]

Why don't we just put Haddock into GHC's repository? It was proposed in 
a previous discussion in February [1] and it would avoid the bad 
experience of having it as a submodule while keeping it in sync.


With the following commands we can keep the whole commit history:

In Haddock repo:
> mkdir -p utils/haddock
> git rm .arcconfig .arclint .ghci .gitignore .travis.yml
> git mv -k * utils/haddock
> git commit -a -m "Prepare Haddock merge"

In GHC repo:
> git rm -rf utils/haddock
> git commit -a -m "Prepare Haddock merge"
> git remote add haddock https://gitlab.haskell.org/ghc/haddock
> git fetch haddock
> git merge --allow-unrelated-histories haddock/ghc-8.6 -m "Merge haddock"
> git remote remove haddock

[1] https://mail.haskell.org/pipermail/ghc-devs/2019-February/017120.html

Cheers,
Sylvain

On 06/03/2019 13:08, Ben Gamari wrote:

Ryan Scott  writes:


I do think something is afoot here. The current Haddock submodule commit is
at 07f2ca [1], but the ghc-head branch of Haddock is still at commit 8459c6
[2]. It would be good if someone could update the ghc-head branch
accordingly.


Indeed. Done.

It would be nice if we had a better way to handle this. Ideally Marge or
someone similar would land any relevant haddock patches to ghc-head when
landing a GHC MR.

Cheers,

- Ben


___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: [ANNOUNCE] GHC 8.6.4 is now available

[Takenobu Tani]

> I've opened #16398 to track this. We'll try to fix this before 8.8.1.

Thanks for doing that!

Regards,
Takenobu
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: [Haskell-cafe] Final steps in GHC's Trac-to-GitLab migration

[Tobias Dammers]

For context: there is a total of 22 pages that use the redirect feature.

So it may actually be feasible to just do this manually.

On Wed, Mar 06, 2019 at 01:05:28PM +0100, Tobias Dammers wrote:
> On Wed, Mar 06, 2019 at 06:09:35AM -0500, Ben Gamari wrote:
> > The lacking redirect support is unfortunate. In my opinion this is 
> > something we will need to handle going forward as well; a one time solution 
> > like adding nginx redirects doesn't seem like the right approach to me. 
> > 
> > I would rather advocate either option 3 or one of the following options:
> > 
> >  5. Detect redirects and convert them to symbolic links in the repo
> >  6. Request redirect support in the gitlab wiki.
> 
> OK, I'll see what I can do about option 3. Option 5 is something that I
> believe we can still do after the fact if need be. Option 6, I think, we
> should do anyway, because we will want that feature for future pages,
> and the solutions outlined so far only take care of existing pages.
> 

-- 
Tobias Dammers - tdamm...@gmail.com
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: [Haskell-cafe] Final steps in GHC's Trac-to-GitLab migration

[Ara Adkins]

That would be perfect if so. I couldn't find a way to do it when I looked
earlier, but I may well have missed something!

On Wed, 6 Mar 2019 at 12:33, Matthew Pickering 
wrote:

> I think gitlab can be configured so notifications are sent for new issues
> and comments on issues which should achieve the same thing as the mailing
> list did?
>
>
>
> On Wed, Mar 6, 2019 at 12:00 PM Sylvain Henry  wrote:
>
>> I use it to track tickets and I would also like to see it continued.
>>
>> Sylvain
>>
>> On 06/03/2019 12:33, Ara Adkins wrote:
>> > Personally I would like to see it continued, but it may not be worth
>> the work if I’m in a minority here.
>> >
>> > A potential stopgap would be to ‘watch’ the GHC project on our gitlab
>> instance, but I can’t see any way to decide to get emails for notifications
>> rather than having to check in at GitLab all the time.
>> >
>> > _ara
>> >
>> >> On 6 Mar 2019, at 11:21, Ben Gamari  wrote:
>> >>
>> >>
>> >>
>> >>> On March 6, 2019 6:11:49 AM EST, Ara Adkins  wrote:
>> >>> Super excited for this! Thank you to everyone whose put in so much
>> hard
>> >>> work to get it done!
>> >>>
>> >>> One question: what is happening with the trac tickets mailing list? I
>> >>> imagine it’ll be going away, but for those of us that use it to keep
>> >>> track of things is there a recommended alternative?
>> >>>
>> >> The ghc-commits list will continue to work.
>> >>
>> >> The ghc-tickets list is a good question. I suspect that under gitlab
>> there will be less need for this list but we may still want to continue
>> maintaining it regardless for continuity's sake. Thoughts?
>> >>
>> >> Cheers,
>> >>
>> >> - Ben
>> >>
>> >>
>> >>
>> >>> Best,
>> >>> _ara
>> >>>
>>  On 6 Mar 2019, at 01:21, Ben Gamari  wrote:
>> 
>>  Hi everyone,
>> 
>>  Over the past few weeks we have been hard at work sorting out the
>>  last batch of issues in GHC's Trac-to-GitLab import [1]. At this
>> >>> point I
>>  believe we have sorted out the issues which are necessary to perform
>> >>> the
>>  final migration:
>> 
>>  * We are missing only two tickets (#1436 and #2074 which will require
>> >>> a
>>    bit of manual intervention to import due to extremely large
>>    description lengths)
>> 
>>  * A variety of markup issues have been resolved
>> 
>>  * More metadata is now preserved via labels. We may choose to
>>    reorganize or eliminate some of these labels in time but it's
>> >>> easier
>>    to remove metadata after import than it is to reintroduce it. The
>>    logic which maps Trac metadata to GitLab labels can be found here
>> >>> [2]
>>  * We now generate a Wiki table of contents [3] which is significantly
>>    more readable than GitLab's default page list. This will be updated
>>    by a cron job until underlying GitLab pages list becomes more
>>    readable.
>> 
>>  * We now generate redirects for Trac ticket and Wiki links (although
>>    this isn't visible in the staging instance)
>> 
>>  * Milestones are now properly closed when closed in Trac
>> 
>>  * Mapping between Trac and GitLab usernames is now a bit more robust
>> 
>>  As in previous test imports, we would appreciate it if you could have
>> >>> a
>>  look over the import and let us know of any problems your encounter.
>> 
>>  If no serious issues are identified with the staging site we plan to
>>  proceed with the migration this coming weekend. The current migration
>>  plan is to perform the final import on gitlab.haskell.org on
>> >>> Saturday, 9
>>  March 2019.
>> 
>>  This will involve both gitlab.haskell.org and ghc.haskell.org being
>> >>> down
>>  for likely the entirety of the day Saturday and likely some of Sunday
>>  (EST time zone). Read-only access will be available to
>>  gitlab.staging.haskell.org for ticket lookup while the import is
>>  underway.
>> 
>>  After the import we will wait at least a week or so before we begin
>> >>> the
>>  process of decommissioning Trac, which will be kept in read-only mode
>>  for the duration.
>> 
>>  Do let me know if the 9 March timing is problematic.
>> 
>>  Cheers,
>> 
>>  - Ben
>> 
>> 
>>  [1] https://gitlab.staging.haskell.org/ghc/ghc
>>  [2]
>> >>>
>> https://github.com/bgamari/trac-to-remarkup/blob/master/TicketImport.hs#L227
>>  [3] https://gitlab.staging.haskell.org/ghc/ghc/wikis/index
>>  ___
>>  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.
>> >> --
>> >> Sent from my Android device with K-9 Mail. Please excuse my brevity.
>> > ___
>> > ghc-devs mailing list
>> > 

Re: [Haskell-cafe] Final steps in GHC's Trac-to-GitLab migration

[Matthew Pickering]

I think gitlab can be configured so notifications are sent for new issues
and comments on issues which should achieve the same thing as the mailing
list did?



On Wed, Mar 6, 2019 at 12:00 PM Sylvain Henry  wrote:

> I use it to track tickets and I would also like to see it continued.
>
> Sylvain
>
> On 06/03/2019 12:33, Ara Adkins wrote:
> > Personally I would like to see it continued, but it may not be worth the
> work if I’m in a minority here.
> >
> > A potential stopgap would be to ‘watch’ the GHC project on our gitlab
> instance, but I can’t see any way to decide to get emails for notifications
> rather than having to check in at GitLab all the time.
> >
> > _ara
> >
> >> On 6 Mar 2019, at 11:21, Ben Gamari  wrote:
> >>
> >>
> >>
> >>> On March 6, 2019 6:11:49 AM EST, Ara Adkins  wrote:
> >>> Super excited for this! Thank you to everyone whose put in so much hard
> >>> work to get it done!
> >>>
> >>> One question: what is happening with the trac tickets mailing list? I
> >>> imagine it’ll be going away, but for those of us that use it to keep
> >>> track of things is there a recommended alternative?
> >>>
> >> The ghc-commits list will continue to work.
> >>
> >> The ghc-tickets list is a good question. I suspect that under gitlab
> there will be less need for this list but we may still want to continue
> maintaining it regardless for continuity's sake. Thoughts?
> >>
> >> Cheers,
> >>
> >> - Ben
> >>
> >>
> >>
> >>> Best,
> >>> _ara
> >>>
>  On 6 Mar 2019, at 01:21, Ben Gamari  wrote:
> 
>  Hi everyone,
> 
>  Over the past few weeks we have been hard at work sorting out the
>  last batch of issues in GHC's Trac-to-GitLab import [1]. At this
> >>> point I
>  believe we have sorted out the issues which are necessary to perform
> >>> the
>  final migration:
> 
>  * We are missing only two tickets (#1436 and #2074 which will require
> >>> a
>    bit of manual intervention to import due to extremely large
>    description lengths)
> 
>  * A variety of markup issues have been resolved
> 
>  * More metadata is now preserved via labels. We may choose to
>    reorganize or eliminate some of these labels in time but it's
> >>> easier
>    to remove metadata after import than it is to reintroduce it. The
>    logic which maps Trac metadata to GitLab labels can be found here
> >>> [2]
>  * We now generate a Wiki table of contents [3] which is significantly
>    more readable than GitLab's default page list. This will be updated
>    by a cron job until underlying GitLab pages list becomes more
>    readable.
> 
>  * We now generate redirects for Trac ticket and Wiki links (although
>    this isn't visible in the staging instance)
> 
>  * Milestones are now properly closed when closed in Trac
> 
>  * Mapping between Trac and GitLab usernames is now a bit more robust
> 
>  As in previous test imports, we would appreciate it if you could have
> >>> a
>  look over the import and let us know of any problems your encounter.
> 
>  If no serious issues are identified with the staging site we plan to
>  proceed with the migration this coming weekend. The current migration
>  plan is to perform the final import on gitlab.haskell.org on
> >>> Saturday, 9
>  March 2019.
> 
>  This will involve both gitlab.haskell.org and ghc.haskell.org being
> >>> down
>  for likely the entirety of the day Saturday and likely some of Sunday
>  (EST time zone). Read-only access will be available to
>  gitlab.staging.haskell.org for ticket lookup while the import is
>  underway.
> 
>  After the import we will wait at least a week or so before we begin
> >>> the
>  process of decommissioning Trac, which will be kept in read-only mode
>  for the duration.
> 
>  Do let me know if the 9 March timing is problematic.
> 
>  Cheers,
> 
>  - Ben
> 
> 
>  [1] https://gitlab.staging.haskell.org/ghc/ghc
>  [2]
> >>>
> https://github.com/bgamari/trac-to-remarkup/blob/master/TicketImport.hs#L227
>  [3] https://gitlab.staging.haskell.org/ghc/ghc/wikis/index
>  ___
>  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.
> >> --
> >> Sent from my Android device with K-9 Mail. Please excuse my brevity.
> > ___
> > ghc-devs mailing list
> > ghc-devs@haskell.org
> > http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
> ___
> ghc-devs mailing list
> ghc-devs@haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
>
___
ghc-devs mailing list

Re: [ANNOUNCE] GHC 8.6.4 is now available

[Ben Gamari]

Takenobu Tani  writes:

> Hi,
>
> I always appreciate your hard work.
>
> Perhaps you may know, but the following html documents are not included in
> the windows tarball [1]:
>
>   * doc/html/index.html
>   * doc/html/users_guide/index.html
>   * doc/html/libraries/index.html
>
Thanks Takenobu! I hadn't noticed this. I've opened #16398 to track
this. We'll try to fix this before 8.8.1.

Cheers,

- Ben


signature.asc
Description: PGP signature
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: [ANNOUNCE] GHC 8.6.4 is now available

[Takenobu Tani]

Hi,

I always appreciate your hard work.

Perhaps you may know, but the following html documents are not included in
the windows tarball [1]:

  * doc/html/index.html
  * doc/html/users_guide/index.html
  * doc/html/libraries/index.html

These files were included in ghc-8.6.3 tarball [2].

These are very useful in offline or slow network environment :)


[1]:
https://downloads.haskell.org/ghc/8.6.4/ghc-8.6.4-x86_64-unknown-mingw32.tar.xz
[2]:
https://downloads.haskell.org/ghc/8.6.3/ghc-8.6.3-x86_64-unknown-mingw32.tar.xz

Regards,
Takenobu



On Wed, Mar 6, 2019 at 5:53 AM Ben Gamari  wrote:

>
> Hello everyone,
>
> The GHC team is very happy to announce the availability of GHC 8.6.4, a
> bugfix release in the GHC 8.6 series. The source distribution, binary
> distributions, and documentation for this release are available at
>
> https://downloads.haskell.org/~ghc/8.6.4
>
> The 8.6.4 release fixes several regressions present in 8.6.3 including:
>
>  - A regression resulting in segmentation faults on Windows introduced
>by the fix for #16071 backported in 8.6.3. This fix has been reverted,
>meaning that 8.6.4 is once again susceptible to #16071. #16071 will
>be fixed in GHC 8.8.1.
>
>  - A bug resulting in incorrect locking on Darwin, potentially resulting
>in hangs at shutdown (#16150)
>
>  - A few bugs in the profiled runtime resulting in the potential for
>memory unsafety has been fixed (#15508).
>
>  - The `process` and `transformers` libraries shipped now properly
>reflect released Hackage releases (#16199)
>
>  - A bug where TH name resolution would break in a plugin context has
>been fixed (#16104)
>
>  - Compilers that do not support TemplateHaskell no longer advertise
>such support in `--supported-languages` (#16331)
>
> As a few of these issues are rather serious users are strongly
> encouraged to upgrade. See Trac [1] for a full list of issues resolved
> in this release.
>
> Note that this release ships with one significant but long-standing bug
> (#14251): Calls to functions taking both Float# and Double# may result
> in incorrect code generation when compiled using the LLVM code generator.
> This is not a new issue, it has existed as long as the LLVM code
> generator has existed; however, changes in code generation in 8.6 made
> it more likely that user code using only lifted types will trigger it.
>
> Note also that this is the first release cut from our (yet again)
> revamped continuous integration infrastructure. While we have done a
> great deal of checking to ensure that the build configuration reflects
> that of previous releases, do let us know if something looks off.
>
> Happy compiling!
>
> Cheers,
>
> - Ben
>
> [1]
> https://ghc.haskell.org/trac/ghc/query?status=closed=8.6.4=id=summary=status=type=priority=milestone=component=priority
> ___
> ghc-devs mailing list
> ghc-devs@haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
>
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: Haddock tree spongled

[Ben Gamari]

Ryan Scott  writes:

> I do think something is afoot here. The current Haddock submodule commit is
> at 07f2ca [1], but the ghc-head branch of Haddock is still at commit 8459c6
> [2]. It would be good if someone could update the ghc-head branch
> accordingly.
>
Indeed. Done.

It would be nice if we had a better way to handle this. Ideally Marge or
someone similar would land any relevant haddock patches to ghc-head when
landing a GHC MR.

Cheers,

- Ben



signature.asc
Description: PGP signature
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: [Haskell-cafe] Final steps in GHC's Trac-to-GitLab migration

[Tobias Dammers]

On Wed, Mar 06, 2019 at 06:09:35AM -0500, Ben Gamari wrote:
> The lacking redirect support is unfortunate. In my opinion this is something 
> we will need to handle going forward as well; a one time solution like adding 
> nginx redirects doesn't seem like the right approach to me. 
> 
> I would rather advocate either option 3 or one of the following options:
> 
>  5. Detect redirects and convert them to symbolic links in the repo
>  6. Request redirect support in the gitlab wiki.

OK, I'll see what I can do about option 3. Option 5 is something that I
believe we can still do after the fact if need be. Option 6, I think, we
should do anyway, because we will want that feature for future pages,
and the solutions outlined so far only take care of existing pages.

___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: [Haskell-cafe] Final steps in GHC's Trac-to-GitLab migration

[Sylvain Henry]

I use it to track tickets and I would also like to see it continued.

Sylvain

On 06/03/2019 12:33, Ara Adkins wrote:

Personally I would like to see it continued, but it may not be worth the work 
if I’m in a minority here.

A potential stopgap would be to ‘watch’ the GHC project on our gitlab instance, 
but I can’t see any way to decide to get emails for notifications rather than 
having to check in at GitLab all the time.

_ara


On 6 Mar 2019, at 11:21, Ben Gamari  wrote:




On March 6, 2019 6:11:49 AM EST, Ara Adkins  wrote:
Super excited for this! Thank you to everyone whose put in so much hard
work to get it done!

One question: what is happening with the trac tickets mailing list? I
imagine it’ll be going away, but for those of us that use it to keep
track of things is there a recommended alternative?


The ghc-commits list will continue to work.

The ghc-tickets list is a good question. I suspect that under gitlab there will 
be less need for this list but we may still want to continue maintaining it 
regardless for continuity's sake. Thoughts?

Cheers,

- Ben




Best,
_ara


On 6 Mar 2019, at 01:21, Ben Gamari  wrote:

Hi everyone,

Over the past few weeks we have been hard at work sorting out the
last batch of issues in GHC's Trac-to-GitLab import [1]. At this

point I

believe we have sorted out the issues which are necessary to perform

the

final migration:

* We are missing only two tickets (#1436 and #2074 which will require

a

  bit of manual intervention to import due to extremely large
  description lengths)

* A variety of markup issues have been resolved

* More metadata is now preserved via labels. We may choose to
  reorganize or eliminate some of these labels in time but it's

easier

  to remove metadata after import than it is to reintroduce it. The
  logic which maps Trac metadata to GitLab labels can be found here

[2]

* We now generate a Wiki table of contents [3] which is significantly
  more readable than GitLab's default page list. This will be updated
  by a cron job until underlying GitLab pages list becomes more
  readable.

* We now generate redirects for Trac ticket and Wiki links (although
  this isn't visible in the staging instance)

* Milestones are now properly closed when closed in Trac

* Mapping between Trac and GitLab usernames is now a bit more robust

As in previous test imports, we would appreciate it if you could have

a

look over the import and let us know of any problems your encounter.

If no serious issues are identified with the staging site we plan to
proceed with the migration this coming weekend. The current migration
plan is to perform the final import on gitlab.haskell.org on

Saturday, 9

March 2019.

This will involve both gitlab.haskell.org and ghc.haskell.org being

down

for likely the entirety of the day Saturday and likely some of Sunday
(EST time zone). Read-only access will be available to
gitlab.staging.haskell.org for ticket lookup while the import is
underway.

After the import we will wait at least a week or so before we begin

the

process of decommissioning Trac, which will be kept in read-only mode
for the duration.

Do let me know if the 9 March timing is problematic.

Cheers,

- Ben


[1] https://gitlab.staging.haskell.org/ghc/ghc
[2]

https://github.com/bgamari/trac-to-remarkup/blob/master/TicketImport.hs#L227

[3] https://gitlab.staging.haskell.org/ghc/ghc/wikis/index
___
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.

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.

___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: [Haskell-cafe] Final steps in GHC's Trac-to-GitLab migration

[Ara Adkins]

Personally I would like to see it continued, but it may not be worth the work 
if I’m in a minority here.

A potential stopgap would be to ‘watch’ the GHC project on our gitlab instance, 
but I can’t see any way to decide to get emails for notifications rather than 
having to check in at GitLab all the time. 

_ara

> On 6 Mar 2019, at 11:21, Ben Gamari  wrote:
> 
> 
> 
>> On March 6, 2019 6:11:49 AM EST, Ara Adkins  wrote:
>> Super excited for this! Thank you to everyone whose put in so much hard
>> work to get it done!
>> 
>> One question: what is happening with the trac tickets mailing list? I
>> imagine it’ll be going away, but for those of us that use it to keep
>> track of things is there a recommended alternative? 
>> 
> The ghc-commits list will continue to work.
> 
> The ghc-tickets list is a good question. I suspect that under gitlab there 
> will be less need for this list but we may still want to continue maintaining 
> it regardless for continuity's sake. Thoughts? 
> 
> Cheers, 
> 
> - Ben 
> 
> 
> 
>> Best,
>> _ara
>> 
>>> On 6 Mar 2019, at 01:21, Ben Gamari  wrote:
>>> 
>>> Hi everyone,
>>> 
>>> Over the past few weeks we have been hard at work sorting out the
>>> last batch of issues in GHC's Trac-to-GitLab import [1]. At this
>> point I
>>> believe we have sorted out the issues which are necessary to perform
>> the
>>> final migration:
>>> 
>>> * We are missing only two tickets (#1436 and #2074 which will require
>> a
>>>  bit of manual intervention to import due to extremely large
>>>  description lengths)
>>> 
>>> * A variety of markup issues have been resolved
>>> 
>>> * More metadata is now preserved via labels. We may choose to
>>>  reorganize or eliminate some of these labels in time but it's
>> easier
>>>  to remove metadata after import than it is to reintroduce it. The
>>>  logic which maps Trac metadata to GitLab labels can be found here
>> [2]
>>> 
>>> * We now generate a Wiki table of contents [3] which is significantly
>>>  more readable than GitLab's default page list. This will be updated
>>>  by a cron job until underlying GitLab pages list becomes more
>>>  readable.
>>> 
>>> * We now generate redirects for Trac ticket and Wiki links (although
>>>  this isn't visible in the staging instance)
>>> 
>>> * Milestones are now properly closed when closed in Trac
>>> 
>>> * Mapping between Trac and GitLab usernames is now a bit more robust
>>> 
>>> As in previous test imports, we would appreciate it if you could have
>> a
>>> look over the import and let us know of any problems your encounter.
>>> 
>>> If no serious issues are identified with the staging site we plan to
>>> proceed with the migration this coming weekend. The current migration
>>> plan is to perform the final import on gitlab.haskell.org on
>> Saturday, 9
>>> March 2019.
>>> 
>>> This will involve both gitlab.haskell.org and ghc.haskell.org being
>> down
>>> for likely the entirety of the day Saturday and likely some of Sunday
>>> (EST time zone). Read-only access will be available to
>>> gitlab.staging.haskell.org for ticket lookup while the import is
>>> underway.
>>> 
>>> After the import we will wait at least a week or so before we begin
>> the
>>> process of decommissioning Trac, which will be kept in read-only mode
>>> for the duration.
>>> 
>>> Do let me know if the 9 March timing is problematic.
>>> 
>>> Cheers,
>>> 
>>> - Ben
>>> 
>>> 
>>> [1] https://gitlab.staging.haskell.org/ghc/ghc
>>> [2]
>> https://github.com/bgamari/trac-to-remarkup/blob/master/TicketImport.hs#L227
>>> [3] https://gitlab.staging.haskell.org/ghc/ghc/wikis/index
>>> ___
>>> 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.
> 
> -- 
> Sent from my Android device with K-9 Mail. Please excuse my brevity.
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: [Haskell-cafe] Final steps in GHC's Trac-to-GitLab migration

[Ben Gamari]

On March 6, 2019 6:11:49 AM EST, Ara Adkins  wrote:
>Super excited for this! Thank you to everyone whose put in so much hard
>work to get it done!
>
>One question: what is happening with the trac tickets mailing list? I
>imagine it’ll be going away, but for those of us that use it to keep
>track of things is there a recommended alternative? 
>
The ghc-commits list will continue to work.

The ghc-tickets list is a good question. I suspect that under gitlab there will 
be less need for this list but we may still want to continue maintaining it 
regardless for continuity's sake. Thoughts? 

Cheers, 

- Ben 



>Best,
>_ara
>
>> On 6 Mar 2019, at 01:21, Ben Gamari  wrote:
>> 
>> Hi everyone,
>> 
>> Over the past few weeks we have been hard at work sorting out the
>> last batch of issues in GHC's Trac-to-GitLab import [1]. At this
>point I
>> believe we have sorted out the issues which are necessary to perform
>the
>> final migration:
>> 
>> * We are missing only two tickets (#1436 and #2074 which will require
>a
>>   bit of manual intervention to import due to extremely large
>>   description lengths)
>> 
>> * A variety of markup issues have been resolved
>> 
>> * More metadata is now preserved via labels. We may choose to
>>   reorganize or eliminate some of these labels in time but it's
>easier
>>   to remove metadata after import than it is to reintroduce it. The
>>   logic which maps Trac metadata to GitLab labels can be found here
>[2]
>> 
>> * We now generate a Wiki table of contents [3] which is significantly
>>   more readable than GitLab's default page list. This will be updated
>>   by a cron job until underlying GitLab pages list becomes more
>>   readable.
>> 
>> * We now generate redirects for Trac ticket and Wiki links (although
>>   this isn't visible in the staging instance)
>> 
>> * Milestones are now properly closed when closed in Trac
>> 
>> * Mapping between Trac and GitLab usernames is now a bit more robust
>> 
>> As in previous test imports, we would appreciate it if you could have
>a
>> look over the import and let us know of any problems your encounter.
>> 
>> If no serious issues are identified with the staging site we plan to
>> proceed with the migration this coming weekend. The current migration
>> plan is to perform the final import on gitlab.haskell.org on
>Saturday, 9
>> March 2019.
>> 
>> This will involve both gitlab.haskell.org and ghc.haskell.org being
>down
>> for likely the entirety of the day Saturday and likely some of Sunday
>> (EST time zone). Read-only access will be available to
>> gitlab.staging.haskell.org for ticket lookup while the import is
>> underway.
>> 
>> After the import we will wait at least a week or so before we begin
>the
>> process of decommissioning Trac, which will be kept in read-only mode
>> for the duration.
>> 
>> Do let me know if the 9 March timing is problematic.
>> 
>> Cheers,
>> 
>> - Ben
>> 
>> 
>> [1] https://gitlab.staging.haskell.org/ghc/ghc
>> [2]
>https://github.com/bgamari/trac-to-remarkup/blob/master/TicketImport.hs#L227
>> [3] https://gitlab.staging.haskell.org/ghc/ghc/wikis/index
>> ___
>> 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.

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: Haddock tree spongled

[Ryan Scott]

I do think something is afoot here. The current Haddock submodule commit is
at 07f2ca [1], but the ghc-head branch of Haddock is still at commit 8459c6
[2]. It would be good if someone could update the ghc-head branch
accordingly.

Ryan S.
-
[1]
https://github.com/haskell/haddock/commit/07f2ca98fd4249dc6ebad053bd6aef90c814efe0
[2]
https://github.com/haskell/haddock/commit/8459c600e0f6da3f85abefdefe651bbe3ed3da4a
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: [Haskell-cafe] Final steps in GHC's Trac-to-GitLab migration

[Ara Adkins]

Super excited for this! Thank you to everyone whose put in so much hard work to 
get it done!

One question: what is happening with the trac tickets mailing list? I imagine 
it’ll be going away, but for those of us that use it to keep track of things is 
there a recommended alternative? 

Best,
_ara

> On 6 Mar 2019, at 01:21, Ben Gamari  wrote:
> 
> Hi everyone,
> 
> Over the past few weeks we have been hard at work sorting out the
> last batch of issues in GHC's Trac-to-GitLab import [1]. At this point I
> believe we have sorted out the issues which are necessary to perform the
> final migration:
> 
> * We are missing only two tickets (#1436 and #2074 which will require a
>   bit of manual intervention to import due to extremely large
>   description lengths)
> 
> * A variety of markup issues have been resolved
> 
> * More metadata is now preserved via labels. We may choose to
>   reorganize or eliminate some of these labels in time but it's easier
>   to remove metadata after import than it is to reintroduce it. The
>   logic which maps Trac metadata to GitLab labels can be found here [2]
> 
> * We now generate a Wiki table of contents [3] which is significantly
>   more readable than GitLab's default page list. This will be updated
>   by a cron job until underlying GitLab pages list becomes more
>   readable.
> 
> * We now generate redirects for Trac ticket and Wiki links (although
>   this isn't visible in the staging instance)
> 
> * Milestones are now properly closed when closed in Trac
> 
> * Mapping between Trac and GitLab usernames is now a bit more robust
> 
> As in previous test imports, we would appreciate it if you could have a
> look over the import and let us know of any problems your encounter.
> 
> If no serious issues are identified with the staging site we plan to
> proceed with the migration this coming weekend. The current migration
> plan is to perform the final import on gitlab.haskell.org on Saturday, 9
> March 2019.
> 
> This will involve both gitlab.haskell.org and ghc.haskell.org being down
> for likely the entirety of the day Saturday and likely some of Sunday
> (EST time zone). Read-only access will be available to
> gitlab.staging.haskell.org for ticket lookup while the import is
> underway.
> 
> After the import we will wait at least a week or so before we begin the
> process of decommissioning Trac, which will be kept in read-only mode
> for the duration.
> 
> Do let me know if the 9 March timing is problematic.
> 
> Cheers,
> 
> - Ben
> 
> 
> [1] https://gitlab.staging.haskell.org/ghc/ghc
> [2] 
> https://github.com/bgamari/trac-to-remarkup/blob/master/TicketImport.hs#L227
> [3] https://gitlab.staging.haskell.org/ghc/ghc/wikis/index
> ___
> 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.
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: [Haskell-cafe] Final steps in GHC's Trac-to-GitLab migration

[Ben Gamari]

The lacking redirect support is unfortunate. In my opinion this is something we 
will need to handle going forward as well; a one time solution like adding 
nginx redirects doesn't seem like the right approach to me. 

I would rather advocate either option 3 or one of the following options:

 5. Detect redirects and convert them to symbolic links in the repo
 6. Request redirect support in the gitlab wiki.

On March 6, 2019 5:55:15 AM EST, Tobias Dammers  wrote:
>On Wed, Mar 06, 2019 at 09:32:44AM +0300, Ömer Sinan Ağacan wrote:
>> - Redirects don't seem to work:
>>  
>https://gitlab.staging.haskell.org/ghc/ghc/wikis/commentary/rts/heap-objects
>
>I believe this is an unfortunate result of the way we migrate wiki
>pages. The way that works is that we don't actually parse the original
>Trac markup; instead, we scrape the rendered HTML directly from the
>live
>Trac instance, and massage that into GitLab markup.
>
>This has a few interesting consequences:
>
>1. "Wiki processors", such as for example dynamically-generated TOCs
>and
>issue lists, get to run on the Trac instance as we request the page,
>and
>thus capture a snapshot of the dynamic data at the time of migration.
>2. Redirects, being implemented as such wiki processors, cause
>client-side redirects, which our scraper will not follow. Hence, the
>converted page is based on an HTML page body that you don't normally
>get
>to see, and no actual redirect is generated on the GitLab side of
>things.
>3. The scraper only looks at what is normally the actual page content;
>any additional UI generated outside of the main content element is
>ignored. Hence, when Trac generates links to the redirect target for
>clients that do not support client-side redirects, those links don't
>make it into the converted page.
>4. Because redirects are usually the last thing to be added to a page,
>that page's history ends there, and becomes the "current" version on
>the
>GitLab side. So we end up with what you're seeing: a nonsensical page
>that contains the fallback content, a somewhat cryptic question asking
>whether it should redirect, and no way to answer that question.
>
>Since GitLab doesn't have an equivalent to those "wiki processors", and
>AFAIK does not cater for such redirects, the question is how we should
>handle these. I can think of several options:
>
>1. Do nothing; when anyone complains, fix the offending pages manually
>(either by converting the useless redirect message into a proper
>hyperlink, or by manually adding a rewrite entry to the nginx
>configuration).
>2. Generate a list of redirecting pages from the Trac dataset, either
>as
>part of the import (2a), or with some grep/sed/awk magic based on the
>converted git repo after the fact (2b); then use that list to generate
>suitable nginx redirects.
>3. Extend the import script to detect redirects, and special-case those
>so that they render as proper links to the redirect target.
>4. Do more research and see if there is a way to make GitLab redirect
>based on wiki content, then extend the import script like in step 3,
>but
>render redirecting pages to use the (currently hypothetical) redirect
>feature.
>
>Personally, I'm inclined to say let's go with option 2b: run the
>import,
>then grep for 'redirect(wiki:', and massage that into nginx redirects.
>
>TL;DR: the import currently ignores Trac wiki redirects, and I'm not
>sure what the best way is to deal with this.
>___
>ghc-devs mailing list
>ghc-devs@haskell.org
>http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: [Haskell-cafe] Final steps in GHC's Trac-to-GitLab migration

[Ben Gamari]

On March 6, 2019 1:32:44 AM EST, "Ömer Sinan Ağacan"  
wrote:
>This look great, thanks to everyone involved!
>
>Some feedback:
>
>- When I click to the "Wiki" link on the left it opens "Home" page and
>I don't
>know how to go to the index from there. I think we may want index to be
>the
>  home page for the wiki?
>

Yes, I do think we at least want to link to the index from the wiki home page. 


>- Redirects don't seem to work:
>https://gitlab.staging.haskell.org/ghc/ghc/wikis/commentary/rts/heap-objects
>
Yes this needs to be fixed. 


-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

RE: [GHC] #16348: GHC HEAD regression: tyConAppArgs

[Ben Gamari]

On March 6, 2019 4:23:37 AM EST, Simon Peyton Jones  
wrote:
>|   * Tickets will have notes added when they are mentioned by a commit
>| message. As we discussed earlier, messages won't include the
>commit
>| message text but rather only a reference to the referring commit
>SHA.
>| For instance, this looks like [1].
>
>I thought we'd decided, for now anyway, to /include/ the commit message
>text.  (Matthew dissented.)  Is that hard to do?
>
>Simon
>
>
Oh dear, I will need to look back over my notes. I suspect my memory has failed 
me here.

Regardless, it is not particularly hard to include commit messages. 

Cheers, 

- Ben 


-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: [GHC] #16348: GHC HEAD regression: tyConAppArgs

[Ben Gamari]

On March 6, 2019 2:06:25 AM EST, Bryan Richter  wrote:
>Ben wrote:
>>  Unfortunately a mention of a ticket from a commit does not produce
>a notification email. This is in my opinion a rather serious issue that
>we will need to work around since it makes closing tickets after merge
>far
>more painful than necessary.
>
>Is there something in the GHC workflow that precludes the normal Gitlab
>behavior of automatically closing issues after a merge? There just
>needs to
>be a commit message or MR description with the words "Closes #xxx" [1].
>
>Or perhaps you were talking specifically about Trac?
>
>I'm just spectating this from a distance so might have misunderstood
>the
>problem.
>
>[1]: Full details at
>https://docs.gitlab.com/ee/user/project/issues/closing_issues.html#via-merge-request
>

The problem is that you very often want to review the ticket before closing it. 
There might be several reasons for this:

 - You might believe that your commit closes the ticket but perhaps there is a 
facet of the problem that you are forgetting

 - You might want to write a final summary of the solution

 - Perhaps there is an additional refactoring that you thought of while writing 
your patch that you would like to open a new ticket to track.

- Maybe you just want to mark the patch to be back ported to the stable branch. 

The general theme here is that looking over the ticket one last time before 
closing is a helpful practice that allows us to catch problems early and keep 
our issue tracker tidy. It would be quite unfortunate to lose this ability. 

Cheers, 

- Ben 


>On Wed, 6 Mar 2019, 5.57 Ben Gamari,  wrote:
>
>> Simon Peyton Jones via ghc-devs  writes:
>>
>> > Matthew, Ben
>> >
>> > I've just received 40-odd messages like this one. It looks as if
>Marge
>> > is now sending commit messages at Trac ticket messages, which is
>> > great. Will that happen after the move to GitLab.
>> >
>> > Also, is this sudden wave because a whole lot of commits have now
>> > landed in master? Or is it somehow an old backlog stuck in a mail
>> > queue?
>> >
>> This happened because the GitLab -> git.haskell.org mirroring
>> process was stuck. Yesterday I un-stuck it which then triggered the
>push
>> of approximately 40 commits, triggering the old Trac commit notifier
>> which produced the messages you received.
>>
>> Regarding commit notifications after we migrate:
>>
>>  * Tickets will have notes added when they are mentioned by a commit
>>message. As we discussed earlier, messages won't include the
>commit
>>message text but rather only a reference to the referring commit
>SHA.
>>For instance, this looks like [1].
>>
>>If we find the indirection between the ticket and the mentioning
>>commit message to be problematic we can certainly revisit this.
>>
>>  * Commit notifications will be sent to ghc-comm...@haskell.org; the
>>format will change a bit but the overall content won't change.
>>
>>  * Unfortunately a mention of a ticket from a commit does not produce
>a
>>notification email. This is in my opinion a rather serious issue
>that
>>we will need to work around since it makes closing tickets after
>>merge far more painful than necessary.
>>
>>
>> > There may be some housekeeping to do, to close tickets, check
>> > regression tests and add pointers to the appropriate tests. Is
>anyone
>> > up for doing that?
>> >
>> Yes, I have been accumulating a sizeable queue of tickets to
>> sort through. I've started working through this but certainly won't
>> finish tonight. I have a few other obligations tomorrow but I'll try
>to
>> pick it up again later in the day.
>>
>> Cheers,
>>
>> - Ben
>>
>>
>>
>> [1]
>https://gitlab.staging.haskell.org/ghc/ghc/issues/16260#note_173847
>> ___
>> ghc-devs mailing list
>> ghc-devs@haskell.org
>> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
>>

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

RE: Haddock tree spongled

[Simon Peyton Jones via ghc-devs]

Yes I'm pointing to gitlab.

[remote "origin"]
fetch = +refs/heads/*:refs/remotes/origin/*
url = https://gitlab.haskell.org/ghc/ghc.git
pushurl = g...@gitlab.haskell.org:ghc/ghc

I have done
git submodule sync
git submodule init
git submodule update

The latter elicits this odd message.

Simon

|  -Original Message-
|  From: Ömer Sinan Ağacan 
|  Sent: 06 March 2019 10:05
|  To: Simon Peyton Jones 
|  Cc: ghc-devs@haskell.org
|  Subject: Re: Haddock tree spongled
|  
|  I just pulled master and `git submodule update` worked. Have you done `git
|  submodule sync` after updating your remotes to point to Gitlab? I'd try
|  doing that and then `git submodule update --init` again afterwards.
|  
|  Ömer
|  
|  Simon Peyton Jones via ghc-devs , 6 Mar 2019 Çar,
|  12:57 tarihinde şunu yazdı:
|  >
|  > Devs
|  >
|  >
|  >
|  > In a clean, up-to-date master I try to say
|  >
|  > Bash$ git submodule update
|  >
|  > fatal: reference is not a tree:
|  > 07f2ca98fd4249dc6ebad053bd6aef90c814efe0
|  >
|  > Unable to checkout '07f2ca98fd4249dc6ebad053bd6aef90c814efe0' in
|  submodule path 'utils/haddock'
|  >
|  >
|  >
|  > What should I do?
|  >
|  >
|  >
|  > Thanks
|  >
|  >
|  >
|  > Simon
|  >
|  > ___
|  > ghc-devs mailing list
|  > ghc-devs@haskell.org
|  > https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmail.
|  > haskell.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fghc-devsdata=02%7C01
|  > %7Csimonpj%40microsoft.com%7Cc8487e1fe20546d89ada08d6a21b4bd8%7C72f988
|  > bf86f141af91ab2d7cd011db47%7C1%7C0%7C636874635457691388sdata=q%2F
|  > Fex6QsoPl9IkBydNUGcWLbf2dlrgbzltMAkTHtA5g%3Dreserved=0
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: Haddock tree spongled

[Ömer Sinan Ağacan]

I just pulled master and `git submodule update` worked. Have you done `git
submodule sync` after updating your remotes to point to Gitlab? I'd try doing
that and then `git submodule update --init` again afterwards.

Ömer

Simon Peyton Jones via ghc-devs , 6 Mar 2019
Çar, 12:57 tarihinde şunu yazdı:
>
> Devs
>
>
>
> In a clean, up-to-date master I try to say
>
> Bash$ git submodule update
>
> fatal: reference is not a tree: 07f2ca98fd4249dc6ebad053bd6aef90c814efe0
>
> Unable to checkout '07f2ca98fd4249dc6ebad053bd6aef90c814efe0' in submodule 
> path 'utils/haddock'
>
>
>
> What should I do?
>
>
>
> Thanks
>
>
>
> Simon
>
> ___
> ghc-devs mailing list
> ghc-devs@haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Haddock tree spongled

[Simon Peyton Jones via ghc-devs]

Devs

In a clean, up-to-date master I try to say

Bash$ git submodule update

fatal: reference is not a tree: 07f2ca98fd4249dc6ebad053bd6aef90c814efe0

Unable to checkout '07f2ca98fd4249dc6ebad053bd6aef90c814efe0' in submodule path 
'utils/haddock'

What should I do?

Thanks

Simon
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

RE: [GHC] #16348: GHC HEAD regression: tyConAppArgs

[Simon Peyton Jones via ghc-devs]

|   * Tickets will have notes added when they are mentioned by a commit
| message. As we discussed earlier, messages won't include the commit
| message text but rather only a reference to the referring commit SHA.
| For instance, this looks like [1].

I thought we'd decided, for now anyway, to /include/ the commit message text.  
(Matthew dissented.)  Is that hard to do?

Simon




|  -Original Message-
|  From: Ben Gamari 
|  Sent: 06 March 2019 03:58
|  To: Simon Peyton Jones ; Matthew Pickering
|  
|  Cc: ghc-devs@haskell.org
|  Subject: RE: [GHC] #16348: GHC HEAD regression: tyConAppArgs
|  
|  Simon Peyton Jones via ghc-devs  writes:
|  
|  > Matthew, Ben
|  >
|  > I've just received 40-odd messages like this one. It looks as if Marge
|  > is now sending commit messages at Trac ticket messages, which is
|  > great. Will that happen after the move to GitLab.
|  >
|  > Also, is this sudden wave because a whole lot of commits have now
|  > landed in master? Or is it somehow an old backlog stuck in a mail
|  > queue?
|  >
|  This happened because the GitLab -> git.haskell.org mirroring process
|  was stuck. Yesterday I un-stuck it which then triggered the push of
|  approximately 40 commits, triggering the old Trac commit notifier which
|  produced the messages you received.
|  
|  Regarding commit notifications after we migrate:
|  
|   * Tickets will have notes added when they are mentioned by a commit
| message. As we discussed earlier, messages won't include the commit
| message text but rather only a reference to the referring commit SHA.
| For instance, this looks like [1].
|  
| If we find the indirection between the ticket and the mentioning
| commit message to be problematic we can certainly revisit this.
|  
|   * Commit notifications will be sent to ghc-comm...@haskell.org; the
| format will change a bit but the overall content won't change.
|  
|   * Unfortunately a mention of a ticket from a commit does not produce a
| notification email. This is in my opinion a rather serious issue that
| we will need to work around since it makes closing tickets after
| merge far more painful than necessary.
|  
|  
|  > There may be some housekeeping to do, to close tickets, check
|  > regression tests and add pointers to the appropriate tests. Is anyone
|  > up for doing that?
|  >
|  Yes, I have been accumulating a sizeable queue of tickets to sort
|  through. I've started working through this but certainly won't finish
|  tonight. I have a few other obligations tomorrow but I'll try to pick it
|  up again later in the day.
|  
|  Cheers,
|  
|  - Ben
|  
|  
|  
|  [1] https://gitlab.staging.haskell.org/ghc/ghc/issues/16260#note_173847
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs