diff options
| author | Samuel Thibault <samuel.thibault@ens-lyon.org> | 2024-11-12 02:05:43 +0100 |
|---|---|---|
| committer | Samuel Thibault <samuel.thibault@ens-lyon.org> | 2024-11-12 02:05:43 +0100 |
| commit | da4a53acb9b4c1635c20a723d3be5282c3c2fa1b (patch) | |
| tree | 826e90681b34091ba1d62aa22aa0200f7c55af1e | |
| parent | e7f31e430570e182b64a646efcbe35dd0b0b42b8 (diff) | |
note about new packages building bugs
| -rw-r--r-- | contributing.mdwn | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/contributing.mdwn b/contributing.mdwn index aef58712..a771c3cf 100644 --- a/contributing.mdwn +++ b/contributing.mdwn @@ -168,7 +168,7 @@ This is the list of tasks that we *want* to address soon, starting with the most [discussion](https://lists.gnu.org/archive/html/bug-hurd/2023-10/msg00062.html). - This means adding an `i386x_float_state` and `i386_XFLOAT_STATE` thread status, that glibc would be able to use along `i386_REGS_SEGS_STATE` and `i386_FLOAT_STATE` in `_hurd_setup_sighandler` and `sigtreturn.c`. The structure would contain the `fp_save_kind`. That'll actually be needed both on `i386` and `x86_64` actually, to fix SSE use against signals in general. * Compare testsuite results of python on hurd-i386 and hurd-amd64, to fix regressions between the former and the latter. -* Check the [failure differences](https://people.debian.org/~sthibault/hurd-amd64/failed_diff.txt) between hurd-i386 and hurd-amd64: they are failing on hurd-amd64 but are successful on hurd-i386. Possibly it's just a mere missing `s/hurd-i386/hurd-any/` in the debian/ directory, but possibly it's a more profound issue in the amd64 port. +* Check the [packages build failures differences](https://people.debian.org/~sthibault/hurd-amd64/failed_diff.txt) between hurd-i386 and hurd-amd64: they are failing on hurd-amd64 but are successful on hurd-i386. Possibly it's just a mere missing `s/hurd-i386/hurd-any/` in the debian/ directory, or a new bug that actually also affects hurd-i386 if you rebuild the package there now, but possibly it's a more profound issue in the amd64 port. * On amd64, fix memcpy (> 16 bytes) from `/dev/mem` (makes hurd-console crash) * Settle CI for mig+gnumach+hurd+glibc. * Port `dhcpcd`, see [call for help](https://lists.debian.org/debian-hurd/2023/11/msg00030.html) |