emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[debbugs-tracker] bug#33186: closed ([PATCH 0/7] Preliminary installer w


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#33186: closed ([PATCH 0/7] Preliminary installer work)
Date: Tue, 27 Nov 2018 10:28:02 +0000

Your message dated Tue, 27 Nov 2018 11:27:07 +0100
with message-id <address@hidden>
and subject line Re: [bug#33186] [PATCH 7/7] gnu: python-3.6: Disable 
congestion test.
has caused the debbugs.gnu.org bug report #33186,
regarding [PATCH 0/7] Preliminary installer work
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
33186: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=33186
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: [PATCH 0/7] Preliminary installer work Date: Sun, 28 Oct 2018 21:35:11 +0900
Hello!

Here are some patches required for the upcoming graphical installer.  As I
patched the glibc they require to rebuild the world, thus I would like to push
them on a wip-newt-installer branch.

By the way, is this approach (sending series to review and push them on a wip
branch) ok, or should I proceed differently ?

Another precision, I'd like the installer to support internationalization.
So working with raw linux terminal is excluded. After some resarchs, I see
only two options:

* Using bterm[1] like D-I (Debian Installer) and Anaconda. It is a framebuffer
  terminal supporting multibyte locales.
* Use kmscon[2], a terminal emulator based on linux KMS.

Even if both of them are unmaintained, I prefer kmscon which seems stable
enough and has nice features, such as font rendering with pango,
internationalized keyboard handling with libxkbcommon, hardware accelerated
rendering and is already packaged as a service for GuixSD.

What do you think of this choice?

Thank you,

Mathieu

[1]: https://packages.debian.org/en/jessie/bogl-bterm
[2]: https://wiki.archlinux.org/index.php/KMSCON

Mathieu Othacehe (7):
  gnu: Add guile-newt.
  services: kmscon: Do not switch to vt at start.
  services: kmscon: Add an auto-login option.
  gnu: glibc: Export supported locales.
  gnu: terminals: Change libtsm and kmscon repositories.
  gnu: slang: Use a correct location for terminfo dirs.
  gnu: python-3.6: Disable congestion test.

 doc/guix.texi                                 |   6 +-
 gnu/local.mk                                  |   2 +
 gnu/packages/base.scm                         |   6 +-
 gnu/packages/guile.scm                        |  43 ++++-
 .../patches/glibc-supported-locales.patch     |  31 +++
 .../python-disable-congestion-test.patch      |  60 ++++++
 gnu/packages/python.scm                       |   1 +
 gnu/packages/slang.scm                        |  14 +-
 gnu/packages/terminals.scm                    | 176 ++++++++++--------
 gnu/services/base.scm                         |  10 +-
 10 files changed, 260 insertions(+), 89 deletions(-)
 create mode 100644 gnu/packages/patches/glibc-supported-locales.patch
 create mode 100644 gnu/packages/patches/python-disable-congestion-test.patch

-- 
2.17.1




--- End Message ---
--- Begin Message --- Subject: Re: [bug#33186] [PATCH 7/7] gnu: python-3.6: Disable congestion test. Date: Tue, 27 Nov 2018 11:27:07 +0100 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux)
Hello,

Marius Bakke <address@hidden> skribis:

> address@hidden (Ludovic Courtès) writes:
>
>> Mathieu Othacehe <address@hidden> skribis:
>>
>>> The socket congestion test is known to hang or fail randomly. It is disabled
>>> on python 3.6 branch upstream.
>>>
>>> * gnu/packages/patches/python-disable-congestion-test.patch: New file.
>>> * gnu/packages/python.scm (python-3.6)[patches]: Add the previous patch.
>>> * gnu/local.mk (dist_patch_DATA): Add it.
>>
>> Does this have anything to do with https://issues.guix.info/issue/33248
>> and https://issues.guix.info/issue/33213 and related issues?
>>
>> If so please add a “Fixes” tag and close all these bugs.  :-)
>>
>> Now, in which branch should it go?  Would be nice in ‘core-updates’, but
>> it would again delay merging that branch.  What do people think?
>> Marius?  Gábor?
>
> The faulty test is already removed on 'core-updates' (albeit more
> heavy-handedly).  So I don't think there's anything to do here.

So Mathieu, I’m closing this issue.

  https://issues.guix.info/issue/33186

Thanks,
Ludo’.


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]