Re: branch staging updated: gnu: ghc-7: Clean up package definition.

Re: branch staging updated: gnu: ghc-7: Clean up package definition.

[Marius Bakke]

[-- Attachment #1: Type: text/plain, Size: 1192 bytes --]

guix-commits@gnu.org writes:

> This is an automated email from the git hooks/post-receive script.
>
> niedzejkob pushed a commit to branch staging
> in repository guix.
>
> The following commit(s) were added to refs/heads/staging by this push:
>      new f20d1cf  gnu: ghc-7: Clean up package definition.
> f20d1cf is described below
>
> commit f20d1cfb51ed14f325da000406807076323f70bc
> Author: Jakub Kądziołka <kuba@kadziolka.net>
> AuthorDate: Wed Apr 8 12:21:42 2020 +0200
>
>     gnu: ghc-7: Clean up package definition.
>     
>     * gnu/packages/haskell.scm (ghc-7)[modules, imported-modules]: Remove
>       the unused rpath module.
>       [phases]: Use invoke instead of system*.

Thanks!  Unfortunately the staging branch was recently 'frozen':

  https://lists.gnu.org/archive/html/guix-devel/2020-05/msg00373.html

I was about to revert the commit, but as GHC currently only builds on
i686 and x86_64 and the CI is "half way there" already, perhaps we can
let it slide:

  https://ci.guix.gnu.org/eval/13961?status=failed

We should have a better way to poll branch status other than "read all
messages on guix-devel" or "ask Marius on IRC".

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

Re: branch staging updated: gnu: ghc-7: Clean up package definition.

[Jakub Kądziołka]

[-- Attachment #1: Type: text/plain, Size: 1620 bytes --]

On Tue, Jun 02, 2020 at 09:22:31PM +0200, Marius Bakke wrote:
> guix-commits@gnu.org writes:
> 
> > This is an automated email from the git hooks/post-receive script.
> >
> > niedzejkob pushed a commit to branch staging
> > in repository guix.
> >
> > The following commit(s) were added to refs/heads/staging by this push:
> >      new f20d1cf  gnu: ghc-7: Clean up package definition.
> > f20d1cf is described below
> >
> > commit f20d1cfb51ed14f325da000406807076323f70bc
> > Author: Jakub Kądziołka <kuba@kadziolka.net>
> > AuthorDate: Wed Apr 8 12:21:42 2020 +0200
> >
> >     gnu: ghc-7: Clean up package definition.
> >     
> >     * gnu/packages/haskell.scm (ghc-7)[modules, imported-modules]: Remove
> >       the unused rpath module.
> >       [phases]: Use invoke instead of system*.
> 
> Thanks!  Unfortunately the staging branch was recently 'frozen':
> 
>   https://lists.gnu.org/archive/html/guix-devel/2020-05/msg00373.html
> 
> I was about to revert the commit, but as GHC currently only builds on
> i686 and x86_64 and the CI is "half way there" already, perhaps we can
> let it slide:
> 
>   https://ci.guix.gnu.org/eval/13961?status=failed
> 
> We should have a better way to poll branch status other than "read all
> messages on guix-devel" or "ask Marius on IRC".

Ouch, sorry for that! I see two potential solutions:

1. Have a guix-devel-announce mailing list, to which we would post
   things concerning all Guix developers.
2. Configure the git server to reject pushes to frozen branches when
   unless --force is used.

Thoughts?
Jakub Kądziołka

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: branch staging updated: gnu: ghc-7: Clean up package definition.

[Marius Bakke]

[-- Attachment #1: Type: text/plain, Size: 1170 bytes --]

Jakub Kądziołka <kuba@kadziolka.net> writes:

> On Tue, Jun 02, 2020 at 09:22:31PM +0200, Marius Bakke wrote:
>> We should have a better way to poll branch status other than "read all
>> messages on guix-devel" or "ask Marius on IRC".
>
> Ouch, sorry for that! I see two potential solutions:
>
> 1. Have a guix-devel-announce mailing list, to which we would post
>    things concerning all Guix developers.

Actually we already have an underutilized 'info-guix' list.  I suppose
that can work.

> 2. Configure the git server to reject pushes to frozen branches when
>    unless --force is used.

It will be difficult for the server to distinguish between 'bug fixes'
and 'huge rebuilds'.  Not sure if the --force flag propagates to servers
the way you are thinking of, but perhaps it can work (not a great habit
though!).

Also, we'd have to bother the Savannah admins every time we 'freeze' a
branch.

Another option could be to create a tracking bug with a special tag that
can be displayed by issues.guix.gnu.org.  It could also show any merge
blockers such as <https://issues.guix.gnu.org/issue/41598> to make it
easier to contribute.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

Re: branch staging updated: gnu: ghc-7: Clean up package definition.

[Jakub Kądziołka]

[-- Attachment #1: Type: text/plain, Size: 1616 bytes --]

On Tue, Jun 02, 2020 at 10:19:20PM +0200, Marius Bakke wrote:
> Jakub Kądziołka <kuba@kadziolka.net> writes:
> 
> > On Tue, Jun 02, 2020 at 09:22:31PM +0200, Marius Bakke wrote:
> >> We should have a better way to poll branch status other than "read all
> >> messages on guix-devel" or "ask Marius on IRC".
> >
> > Ouch, sorry for that! I see two potential solutions:
> >
> > 1. Have a guix-devel-announce mailing list, to which we would post
> >    things concerning all Guix developers.
> 
> Actually we already have an underutilized 'info-guix' list.  I suppose
> that can work.

Huh, I thought this was for communicating to Guix users.

> > 2. Configure the git server to reject pushes to frozen branches when
> >    unless --force is used.
> 
> It will be difficult for the server to distinguish between 'bug fixes'
> and 'huge rebuilds'.  Not sure if the --force flag propagates to servers
> the way you are thinking of, but perhaps it can work (not a great habit
> though!).

From the various behaviors of git servers I have observed, I would be
really surprised if it wasn't...

> Also, we'd have to bother the Savannah admins every time we 'freeze' a
> branch.

I suppose we could have a dotfile in the repository...

> Another option could be to create a tracking bug with a special tag that
> can be displayed by issues.guix.gnu.org.  It could also show any merge
> blockers such as <https://issues.guix.gnu.org/issue/41598> to make it
> easier to contribute.

Makes sense. We'd need to update the Commit Access section accordingly.

Regards,
Jakub Kądziołka

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: branch staging updated: gnu: ghc-7: Clean up package definition.

[zimoun]

On Tue, 2 Jun 2020 at 23:13, Jakub Kądziołka <kuba@kadziolka.net> wrote:

> > > 1. Have a guix-devel-announce mailing list, to which we would post
> > >    things concerning all Guix developers.
> >
> > Actually we already have an underutilized 'info-guix' list.  I suppose
> > that can work.
>
> Huh, I thought this was for communicating to Guix users.

Yes, it is currently titled "Low-traffic mailing list for
announcements to Guix users."
I think the point of such mailing list to stay low-traffic but it
could be "announcements about Guix".  For example, post freeze, new
blog entry and core-updates merge.


All the best,
simon

Re: branch staging updated: gnu: ghc-7: Clean up package definition.

[zimoun]

Dear,

On Tue, 2 Jun 2020 at 22:19, Marius Bakke <marius@gnu.org> wrote:

> Also, we'd have to bother the Savannah admins every time we 'freeze' a
> branch.

However, we could ask to extend the list of tags used by Debbugs.  For
example, by adding the tag 'release-critical' or any other
well-chosen.


> Another option could be to create a tracking bug with a special tag that
> can be displayed by issues.guix.gnu.org.  It could also show any merge
> blockers such as <https://issues.guix.gnu.org/issue/41598> to make it
> easier to contribute.

Yes.  And similar thing could be done for release.  Special subject
string that Mumi could parse to report accordingly on
issues.guix.gnu.org and blocking tags to synchronize.  I already
thought loud like that [1]. :-)

[1] https://lists.gnu.org/archive/html/guix-devel/2020-04/msg00380.html


All the best,
simon