unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Danny Milosavljevic <dannym@scratchpost.org>
To: zimoun <zimon.toutoune@gmail.com>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Release v1.2 timetable
Date: Wed, 7 Oct 2020 17:39:44 +0200	[thread overview]
Message-ID: <20201007173944.779a51e9@scratchpost.org> (raw)
In-Reply-To: <CAJ3okZ3Jsjyub1Vhm-uQWtHTiXxTzCS=dj=R3nTYx+DCD2=Bkw@mail.gmail.com>

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

Hi,

On Wed, 7 Oct 2020 16:51:46 +0200
zimoun <zimon.toutoune@gmail.com> wrote:

> I have read Bug #43513 and Patch #43591 [1,2] and the table [3] is not
> really encouraging. :-(

This bug has serious repercussions for bootstrapping--and thus for the entire
GNU Guix distribution (not to mention those other distributions which do not
enable large file support).  If I were glibc I would be recalling their
last few releases and would be telling everyone not to use those releases.

> If I understand correctly, the plan is to disable some architectures
> with this Patch #43829 [4], right?

Yes, that is correct.

> BTW, is this Bug #43720 [5] blocking for the release too?
> 
> Well, what is the status and the plan about this armhf topic?

There's a branch wip-file-offset-64-sledgehammer (branched off core-updates)
where I'm trying to fix this bug for good.

I keep running into other problems (which have nothing to do with this bug) on
it--which is why I have to do other commits to fix those OTHER problems (to
core-updates).

Each one of those unrelated bugs delays me for a day each (first I have to
notice that one of the build servers stopped building everything on
wip-file-offset-64-sledgehammer, then I have to build core-updates to
see whether it has the problem too (also, chances are that the build of
core-updates on i686-linux-on-x86_64 and armhf-linux-on-aarch64 hangs because
the readdir problem causes an endless loop!), and then fix the problem on
core-updates, then rebase branch wip-file-offset-64-sledgehammer on that
core-updates, and finally restart the build of everything on all architectures
again).

(For example, I just fixed mesa--but it's not reproducible.  Was it not
reproducible before?  No one knows... WHY NOT?)

(Right now xorg-server has a problem with event (non-)ordering... again,
something that is definitely unrelated to file size.  So there I have to go
test that on core-updates again)

Not to mention that on the aarch64 build server I still don't have a working
home directory.  Otherwise I'd just do crontab -e and add the thing above
by myself.  But crontab -e probably doesn't work either...

This is so frustrating.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2020-10-07 15:40 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-29 12:16 Release v1.2 timetable zimoun
2020-09-29 15:07 ` Danny Milosavljevic
2020-10-07 14:51   ` zimoun
2020-10-07 15:39     ` Danny Milosavljevic [this message]
2020-10-07 15:56       ` Weird things found while fixing basic Guix packages Danny Milosavljevic
2020-10-12 11:53         ` Ludovic Courtès
2020-10-07 16:29       ` Release v1.2 timetable Danny Milosavljevic
2020-10-12 11:52       ` 32-bit builds on 64-bit hardware/VMs Ludovic Courtès
2020-10-12 12:06         ` Andreas Enge
2020-10-13 13:54           ` Ludovic Courtès
2020-10-07 16:31     ` Release v1.2 timetable Danny Milosavljevic
2020-10-05 10:18 ` pelzflorian (Florian Pelz)
2020-10-05 11:16   ` Julien Lepiller
2020-10-05 12:38     ` Miguel Ángel Arruga Vivas
2020-10-05 13:50       ` Julien Lepiller
2020-10-05 13:48     ` Ludovic Courtès
2020-10-05 21:17       ` zimoun
2020-10-06  6:57         ` Mathieu Othacehe
2020-10-07 14:36           ` zimoun
2020-10-21  9:14             ` Ludovic Courtès
2020-10-22  7:55               ` Mathieu Othacehe
2020-10-23  8:39               ` zimoun
2020-10-26 22:52                 ` Ludovic Courtès
2020-10-06  6:59         ` Efraim Flashner
2020-10-06  7:05           ` Mathieu Othacehe
2020-10-06  7:26             ` Efraim Flashner
2020-10-06  7:57               ` Mathieu Othacehe
2020-10-07 14:39                 ` zimoun
2020-10-09 18:25                 ` Andreas Enge
2020-10-09 18:37                   ` Danny Milosavljevic
2020-10-12 11:47                 ` Shipping more installer images? Ludovic Courtès
2020-10-12 13:48                   ` Danny Milosavljevic
2020-10-13 13:51                     ` Ludovic Courtès
2020-10-13 14:19                       ` Mathieu Othacehe
2020-10-13 21:23                         ` Ludovic Courtès
2020-10-13 16:29                       ` Danny Milosavljevic
2020-10-13 15:07                   ` Efraim Flashner
2020-10-13 21:25                     ` Ludovic Courtès
2020-10-19 15:17 ` Update on the timeline for the release v1.2 zimoun
2020-10-19 18:26   ` Miguel Ángel Arruga Vivas
2020-10-19 19:27     ` pelzflorian (Florian Pelz)
2020-10-19 21:57       ` Julien Lepiller
2020-10-21 12:44   ` Ludovic Courtès
2020-10-21 14:14     ` zimoun
2020-10-21 15:57       ` Ludovic Courtès
2020-10-21 18:03         ` Julien Lepiller
2020-10-21 21:27           ` Marius Bakke
2020-10-21 22:16           ` Ludovic Courtès
2020-10-21 22:23             ` zimoun
2020-10-21 22:36             ` zimoun
2020-10-26 22:44               ` Ludovic Courtès
2020-10-31  2:41         ` Maxim Cournoyer
2020-10-31 22:28           ` Branching for v1.2? Ludovic Courtès
2020-11-01  2:21             ` Miguel Ángel Arruga Vivas
2020-11-02 16:56               ` Ludovic Courtès
2020-11-02  8:43             ` zimoun
2020-11-02 13:20               ` Miguel Ángel Arruga Vivas
2020-11-02 15:00                 ` Julien Lepiller
2020-11-02 17:56                   ` pelzflorian (Florian Pelz)
2020-11-03 12:51                     ` Tobias Geerinckx-Rice
2020-11-03 13:46                       ` pelzflorian (Florian Pelz)

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=20201007173944.779a51e9@scratchpost.org \
    --to=dannym@scratchpost.org \
    --cc=guix-devel@gnu.org \
    --cc=zimon.toutoune@gmail.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 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).