unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Leo Famulari <leo@famulari.name>
Cc: 25752@debbugs.gnu.org, Hank Donnay <hdonnay@gmail.com>,
	Efraim Flashner <efraim@flashner.co.il>
Subject: bug#25752: go incremental builds broken
Date: Wed, 26 Oct 2022 22:42:41 +0200	[thread overview]
Message-ID: <86h6zqb9ku.fsf@gmail.com> (raw)
In-Reply-To: <86zgsftp3c.fsf_-_@gmail.com> (zimoun's message of "Tue, 14 Sep 2021 12:43:03 +0200")

Hi,

On Tue, 14 Sep 2021 at 12:43, zimoun <zimon.toutoune@gmail.com> wrote:
> On Fri, 18 Dec 2020 at 16:31, Leo Famulari <leo@famulari.name> wrote:
>> On Fri, Dec 18, 2020 at 09:00:14PM +0100, zimoun wrote:
>>> I suspect closing this bug had been forgotten.  If yes, feel free to
>>> close it.  Otherwise, I do not understand what is the next actionable
>>> step.
>>
>> I don't think this bug has been fixed, although I have not checked.
>> Currently, Go incremental builds and library re-use is not functional in
>> Guix, unless I missed a new development.
>
> What is the status of this bug?  Since I am not using Go at all, it is
> hard for me to have a reproducer.  Is it possible to provide a
> reproducer?  Thanks.

> PS: I asked the same thing 13 weeks ago.  Therefore, without any answer
> and giving this bug is really old not so much commented, I propose to
> close it.

Date: Wed, 09 Jun 2021 23:38:50 +0200 (1 year, 19 weeks, 5 days ago)
Date: Fri, 26 Nov 2021 02:12:36 +0100 (47 weeks, 5 days, 19 hours ago)

Go incremental is still not functional but is it worth to keep this
report open?

Giving the none activity of this bug and no reply about the status after
waiting a long time, I will close it if no objection.


Cheers,
simon




  reply	other threads:[~2022-10-26 22:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-16 15:05 bug#25752: go incremental builds broken Hank Donnay
     [not found] ` <handler.25752.B.14872575426869.ack@debbugs.gnu.org>
2017-02-24 19:50   ` bug#25752: Acknowledgement (go incremental builds broken) Hank Donnay
2017-02-25 15:58     ` Leo Famulari
2020-12-18 20:00       ` zimoun
2020-12-18 21:31         ` Leo Famulari
2021-01-11 12:46           ` zimoun
2021-01-11 20:01             ` Efraim Flashner
2021-06-09 21:38               ` zimoun
2021-11-26  1:12               ` zimoun
2021-09-14 10:43           ` bug#25752: go incremental builds broken zimoun
2022-10-26 20:42             ` zimoun [this message]
2022-10-27 10:21               ` Maxime Devos
2022-10-28  8:22                 ` zimoun
2023-10-16 22:44                   ` Simon Tournier
2017-03-07 21:50 ` Ludovic Courtès

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=86h6zqb9ku.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=25752@debbugs.gnu.org \
    --cc=efraim@flashner.co.il \
    --cc=hdonnay@gmail.com \
    --cc=leo@famulari.name \
    /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).