unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Jakub Kądziołka" <kuba@kadziolka.net>
To: Marius Bakke <marius@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: branch staging updated: gnu: ghc-7: Clean up package definition.
Date: Tue, 2 Jun 2020 21:45:27 +0200	[thread overview]
Message-ID: <20200602194527.czie5ul7r3fzieja@gravity> (raw)
In-Reply-To: <875zc9w9vs.fsf@gnu.org>

[-- 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 --]

  reply	other threads:[~2020-06-02 19:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200601154315.6307.59562@vcs0.savannah.gnu.org>
2020-06-02 19:22 ` branch staging updated: gnu: ghc-7: Clean up package definition Marius Bakke
2020-06-02 19:45   ` Jakub Kądziołka [this message]
2020-06-02 20:19     ` Marius Bakke
2020-06-02 21:13       ` Jakub Kądziołka
2020-06-02 22:10         ` zimoun
2020-06-02 22:02       ` zimoun

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200602194527.czie5ul7r3fzieja@gravity \
    --to=kuba@kadziolka.net \
    --cc=guix-devel@gnu.org \
    --cc=marius@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).