[PATCH] update Hurd packages

  • Done
  • quality assurance status badge
Details
4 participants
  • Josselin Poiret
  • Joshua Branson
  • Maxim Cournoyer
  • zamfofex
Owner
unassigned
Submitted by
zamfofex
Severity
normal
Merged with
Z
Z
zamfofex wrote on 11 Nov 2021 16:51
(name . guix-patches@gnu.org)(address . guix-patches@gnu.org)
1850188127.399847.1636645881998@privateemail.com
I have been working on updating the Hurd packages for quite a while now. My goal was to use netdde (which wasn’t previously working well) so that I could install Guix GNU/Hurd on my computer and use it.

I was asked (in IRC) to say that my changes are necessary to be able to get netdde to a working state, since non-release updates are generally not accepted. However, I will note that all packages I updated (as far as I can tell) were already in a non-release commit.

I have applied my changes over the 'core-update-frozen' branch because it seems like the newer version of glibc therein is necessary for these newer package commit versions to build successfully.

I will send the patch file generated by 'git format-patch' as an attachment.

If I have done anything wrong while sending this email, please let me know and apologies in advance.
M
M
Maxim Cournoyer wrote on 4 Jan 2023 02:14
(name . zamfofex)(address . zamfofex@twdb.moe)(address . 51770@debbugs.gnu.org)
87r0wbw17b.fsf@gmail.com
Hello!

zamfofex <zamfofex@twdb.moe> writes:

Toggle quote (13 lines)
> I have been working on updating the Hurd packages for quite a while
> now. My goal was to use netdde (which wasn’t previously working well)
> so that I could install Guix GNU/Hurd on my computer and use it.

> I was asked (in IRC) to say that my changes are necessary to be able
> to get netdde to a working state, since non-release updates are
> generally not accepted. However, I will note that all packages I
> updated (as far as I can tell) were already in a non-release commit.
>
> I have applied my changes over the 'core-update-frozen' branch because
> it seems like the newer version of glibc therein is necessary for
> these newer package commit versions to build successfully.

Thanks for this contribution!

Toggle quote (4 lines)
> I will send the patch file generated by 'git format-patch' as an attachment.
>
> If I have done anything wrong while sending this email, please let me know and apologies in advance.

Changes to packages are usually made each in their own commit; also, the
one line .patch file would better be implemented as a substitution phase
(using substitute*).

Could you please send an updated patch series with the above changes?

--
Thanks,
Maxim
M
M
Maxim Cournoyer wrote on 4 Jan 2023 02:14
control message for bug #51770
(address . control@debbugs.gnu.org)
87pmbvw175.fsf@gmail.com
tags 51770 + moreinfo
quit
J
J
Joshua Branson wrote on 24 Feb 2023 13:57
Re: progress report on updating the Hurd packages
(name . zamfofex)(address . zamfofex@twdb.moe)
87pm9z8blp.fsf@dismail.de
zamfofex <zamfofex@twdb.moe> writes:

Toggle quote (24 lines)
> Hello, everyone! I just wanted to be able to report my progress with updating the Hurd packages.
>
> I have been able to get past my previous issues with building GMP, I think, but
> it seems that the glibc in Guix is still too outdated for the whole endeavor to
> succeed.
>
> I could either update the glibc package again or simply apply a patch to it
> (since the change needed seems to be small enough), but that would take quite a
> while waiting for things to build, and I’m not sure I’m up for it at the moment.
>
> I plan to pick this effort back up again at some point, but at the moment I’m a
> bit tired of having to wait for packages to build for multiple days. But if
> anyone wants to pick up where I left off, I will upload a ‘git diff’ with my
> current changes. (Applicable to ‘core-updates’.)
>
> Here is some more insight based on my conversations on #hurd:
>
> - https://logs.guix.gnu.org/hurd/2023-02-20.log
> - https://logs.guix.gnu.org/hurd/2023-02-21.log
>
> If anyone wants to take this work meanwhile, please do let me know somehow so that we don’t end up duplicating effort!
>
> Thanks for everyone’s amazing work on the Hurd and on Guix!

Here is an email that was send in the bug-hurd archives recently that
talked about how to build the Hurd on GNU/Linux. Hopefully this will
help others to update our Hurd packages:


Here are some scripts that automate this process:


The hurd was a wiki page for this as well (probably outdated):


Also for those of you who don't know, the Hurd is getting a ton of
developer attention right now. Work in progress includes SMP work, 64
bit kernel (with 32 bit address space), some re-using netBSD's driver's
work, etc. Now's a great time get subscribed to the Hurd's mail
developmental email list: bug-hurd:

J
J
Joshua Branson wrote on 26 May 2023 16:26
control message for bug #51770
(address . control@debbugs.gnu.org)
858927381f2a6df60e0525a8dd8ea45c.jbranso@dismail.de
merge 51770 63641
quit
J
J
Josselin Poiret wrote on 13 Jul 2023 19:15
Re: [PATCH 0/8] Add libc specific to Hurd and update components
(address . control@debbugs.gnu.org)
875y6n91hk.fsf@jpoiret.xyz
close 63641
thankyou
--
Josselin Poiret
-----BEGIN PGP SIGNATURE-----

iQHEBAEBCgAuFiEEOSSM2EHGPMM23K8vUF5AuRYXGooFAmSwMTcQHGRldkBqcG9p
cmV0Lnh5egAKCRBQXkC5FhcaikhjC/9JmiT9IZCZ2lKcAD+V+Wvd6fC1EE88PlOQ
RamnsrzKAATomGpV55HEwUvKG3idSmuUF5JFbHbRfb/EQRw8ZfWM9eIXwxV/5kT6
iThCr4SVe71kgS47p9Mru8yvYSKcBOkJPDjEbeVoeH0vRYnRup5YxmHs+1FnQcsa
fXYa3A1rwiRdvXG+RXUuEhlCzOpSKCpHGbOxQFltH6fe6MpOJQG8Ta7nSyUMQyPf
m5AeGMH+zuxyLcneOJhm7brQ22GjNp7cMpM1L95sbFm2CECDIb/mIHLq8JXmAGwc
EMO2HGi6cQma/N4wCo4xb6ny5FfYTdbDFxNa7+D9FDlp23x5gZPGIZaG7ub4ZMb2
rfpZytMswOBUZorjoMCGKWUIUVKtnCwfUnePFjcDAGJpUclRPIK0fsB7TcvBqLJz
nHoljw+btKwu5cLvxJ/UjKapSSLULjPHTCbI6d/NW52flbHP4HMtGVehff5mp7yw
VvP6NJn2vmzx5/avB6ZZ98nUQIOJWc0=
=bS4P
-----END PGP SIGNATURE-----

?