all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Leo Famulari" <leo@famulari.name>
To: "Felix Lechner" <felix.lechner@lease-up.com>
Cc: 61989@debbugs.gnu.org
Subject: [bug#61989] [PATCH 00/11] Adding Gocryptfs (feature branch)
Date: Thu, 16 Mar 2023 19:59:41 -0400	[thread overview]
Message-ID: <5fad9502-2744-4f5c-8056-cb7088b6cee0@app.fastmail.com> (raw)
In-Reply-To: <CAFHYt55Q8qnhA_LfqFo9EvNAs06Zb+i=yoTUf4KUsRDTGki2AQ@mail.gmail.com>

On Thu, Mar 16, 2023, at 15:44, Felix Lechner wrote:
> Hi Leo,
>
> On Wed, Mar 15, 2023 at 6:21 PM Leo Famulari <leo@famulari.name> wrote:
>>
>> On Mon, Mar 13, 2023 at 07:05:25PM -0700, Felix Lechner wrote:
>> > I am not sure how to read the Cuirass derivations, but the file
>> > missing for powerpc64le-linux [1] called libgcc_s.so.1 is present on
>> > x86_64:
>> >
>> >     gcc-10.3.0-lib
>> >     gcc-12.1.0-lib
>> >     gcc-12.2.0-lib
>> >     gcc-mesboot-4.9.4
>> >     gfortran-10.3.0-lib
>> >     libgccjit-10.3.0
>>
>> Are you saying that something is broken on powerpc64le-linux? Is it a
>> regression from this branch? Or a pre-existing problem?
>
> I do not know the answers to your questions. With my message, I merely
> tried to address what seemed like a remaining issue in this jobset:
>
>     https://ci.guix.gnu.org/jobset/go-team
>
> The failed build #547772 I references was part of the latest
> evaluation #283979, but I am not sure how to read those reports.
>
> Most significantly, I do not know if the reports are
> cumulative—meaning that fewer errors later signify that earlier errors
> have been resolved.

Okay. Then your next steps should be identifying Guix developers who have a history of working on the PowerPC port and asking them to take a look. This kind of outreach to the Guix developer community is a critical part of landing big changes like this one.

If you can't find anyone to respond, then it's safe to say we can ignore this problem.




  reply	other threads:[~2023-03-17  0:01 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-05 20:52 [bug#61989] [PATCH 00/11] Adding Gocryptfs (feature branch) Felix Lechner via Guix-patches via
2023-03-05 20:54 ` [bug#61989] [PATCH 01/11] gnu: go-golang-org-x-sys: Update to 0.4.0 Felix Lechner via Guix-patches via
2023-03-05 20:54 ` [bug#61989] [PATCH 02/11] gnu: go-golang-org-x-net: Update to 0.5.0 Felix Lechner via Guix-patches via
2023-03-05 20:54 ` [bug#61989] [PATCH 03/11] gnu: Add go-github-com-hanwen-go-fuse-v2 Felix Lechner via Guix-patches via
2023-03-05 20:54 ` [bug#61989] [PATCH 04/11] gnu: Add go-github-com-aperturerobotics-jacobsa-crypto Felix Lechner via Guix-patches via
2023-03-05 20:54 ` [bug#61989] [PATCH 05/11] gnu: Add go-github-com-jacobsa-oglematchers Felix Lechner via Guix-patches via
2023-03-05 20:54 ` [bug#61989] [PATCH 06/11] gnu: Add go-github-com-jacobsa-oglemock Felix Lechner via Guix-patches via
2023-03-05 20:54 ` [bug#61989] [PATCH 07/11] gnu: Add go-github-com-jacobsa-ogletest Felix Lechner via Guix-patches via
2023-03-05 20:54 ` [bug#61989] [PATCH 08/11] gnu: Add go-github-com-jacobsa-reqtrace Felix Lechner via Guix-patches via
2023-03-05 20:54 ` [bug#61989] [PATCH 09/11] gnu: Add go-github-com-pkg-xattr Felix Lechner via Guix-patches via
2023-03-05 20:54 ` [bug#61989] [PATCH 10/11] gnu: Add go-github-com-rfjakob-eme Felix Lechner via Guix-patches via
2023-03-05 20:54 ` [bug#61989] [PATCH 11/11] gnu: Add gocryptfs Felix Lechner via Guix-patches via
2023-03-06 16:42 ` [bug#61989] [PATCH 00/11] Adding Gocryptfs (feature branch) Leo Famulari
2023-03-07 23:06   ` Leo Famulari
2023-03-08  0:02     ` Felix Lechner via Guix-patches via
2023-03-08 15:10       ` Leo Famulari
2023-03-10  0:21         ` Felix Lechner via Guix-patches via
2023-03-10  1:54           ` Leo Famulari
2023-03-11 16:17             ` Leo Famulari
2023-03-12  5:27               ` Felix Lechner via Guix-patches via
2023-03-14  2:05               ` Felix Lechner via Guix-patches via
2023-03-16  1:21                 ` Leo Famulari
2023-03-16 19:44                   ` Felix Lechner via Guix-patches via
2023-03-16 23:59                     ` Leo Famulari [this message]
2023-03-17 19:02                       ` Felix Lechner via Guix-patches via
2023-03-19  8:51                         ` Efraim Flashner
2023-03-19 17:17                           ` Leo Famulari
2023-03-19 17:22                             ` Leo Famulari
2023-03-19 17:25                               ` Felix Lechner via Guix-patches via
2023-03-19 20:38                                 ` Leo Famulari
2023-03-19 20:46                                   ` Leo Famulari
2023-03-19 20:48                                     ` Felix Lechner via Guix-patches via
2023-03-19 20:51                                       ` Leo Famulari
2023-03-19 20:54                                         ` Felix Lechner via Guix-patches via
2023-03-19 21:04                                           ` Leo Famulari
2023-03-19 21:31                                     ` Felix Lechner via Guix-patches via
2023-03-28 20:37                                       ` bug#61989: " Leo Famulari
2023-03-28 20:54                                         ` [bug#61989] " Felix Lechner via Guix-patches via
2023-03-13 17:53             ` Leo Famulari
2023-03-13 20:37               ` Felix Lechner via Guix-patches via

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

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

  git send-email \
    --in-reply-to=5fad9502-2744-4f5c-8056-cb7088b6cee0@app.fastmail.com \
    --to=leo@famulari.name \
    --cc=61989@debbugs.gnu.org \
    --cc=felix.lechner@lease-up.com \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.