Add today meeting notes for 20240918 meeting authored by Salvatore Bonaccorso's avatar Salvatore Bonaccorso


Signed-off-by: default avatarSalvatore Bonaccorso <carnil@debian.org>
......@@ -2,7 +2,7 @@
Meeting is to take place on [Jitsi](https://jitsi.debian.social/dkt) on 2024-09-18 19:00 UTC.
Chair: @benh
Chair: @benh
## Agenda
......@@ -61,3 +61,50 @@ Chair: @benh
|linux|[\#1178](https://salsa.debian.org/kernel-team/linux/-/merge_requests/1178)|🟢|[mm: set CONFIG\_ZONE\_DEVICE=y on most 64-bit architectures, not only amd64](https://salsa.debian.org/kernel-team/linux/-/merge_requests/1178)|
|linux|[\#1038](https://salsa.debian.org/kernel-team/linux/-/merge_requests/1038)|🟢|[debian/rules.real: export LANG = C.UTF-8 for sphinx](https://salsa.debian.org/kernel-team/linux/-/merge_requests/1038)|
|linux|[\#741](https://salsa.debian.org/kernel-team/linux/-/merge_requests/741)|🟢|[Fix most reproducibility issues](https://salsa.debian.org/kernel-team/linux/-/merge_requests/741)|
## Minutes
### Review of Bugs
* [\#1063754](https://bugs.debian.org/1063754): bwh mentioned he will reply soon to the bug.
* [\#1076372](https://bugs.debian.org/1076372): Short discussion about the bug. After reporter feedback this looks more to be a specific driver bug, but not to be associated with a ext4 regression. bwh will change the bug title to match the finding. Still need to wait for reporter for feedback.
* [\#1081546](https://bugs.debian.org/1081546): Similar bugs are linked upstream. carnil takes care to review those and try to match the current downstream reported issue to an upstream issue. Otherwise ask reporter to fill a new bug upstream.
* [\#1081705](https://bugs.debian.org/1081705): We have to sort out what the actual error message is. Error logs are yet incomplete and issue is cross-referencing other bugs. bwh will adjust the title of the bug and ask reporter to report upstream.
* [\#1082081](https://bugs.debian.org/1082081): carnil taking action on it.
* [\#1081826](https://bugs.debian.org/1081826): Has been noted that Helmut pointed out problems with bootstraping new architectures in Debian with current situation around `linux-libc-dev`. Action is to discuss the topic with waldi in one of the next meetings. Additionally we can downgrade the severity of the reported bug, as it rather not important.
* [\#1072573](https://bugs.debian.org/1072573): carnil follows upstream thread and inclusion of commit.
* [\#711021](https://bugs.debian.org/711021): bwh will have a look at the issue again.
* [\#1041484](https://bugs.debian.org/1041484): bwh will investigate this issue. Issues with `printk` calls?
* [\#1081833](https://bugs.debian.org/1081833): carnil takes action to contact the reporter, ideally tro to get the changes bisect to isolate the problem. Do first an analysis of upstream commit for potential culprits.
* [\#1081550](https://bugs.debian.org/1081550): bwh will take action to look at the issue. We have first missing support in unstable for `armhf` (it is enabled for `arm64`). It make sense to have it enabled as well for `armhf`. We might later look at stable.
* [\#1082001](https://bugs.debian.org/1082001): bwh takes action ot investigate it, if reproducible try to write patch.
* [\#857043](https://bugs.debian.org/857043): carnil: downgrade the severity to wishlist, try to get reporter to report the issue to upstream on linux-nfs mailinglist.
* [\#894906](https://bugs.debian.org/894906): carnil: Tell Federico that patch is probbly not generic enough to be included. Bastian was aiming toreply in more details to the bug, thus postponing more detailed answer.
### Migration excuses
* `nfs-tuils` will migrate the day after the meeting regularly to testing. Discussion to put `nfs-utils` on allowlist to be able to run autopkgtest with restrictions. carnil will contact ci.debian.net folks for adding `nfs-utils` to allow list. This was done after the meeting.
### New upstream versions
* `firemware-nonfree`: bwh will review merge request for new upstream version import and then do the followup update himself.
* `firmware-free`: bwh will have a look to rebase the version as needed.
### Merge requests
* [\#24](https://salsa.debian.org/kernel-team/kernel-sec/-/merge_requests/24): bwh will further work on the automating task from the MR. Might have LTS paid resourced to handle further work next week. Short discussion about current state of the `dyad` files imported upstream.
bwh will have a look at the MR targetting master before uploading 6.11 or 6.11.y to experimental next.
* [\#1214](https://salsa.debian.org/kernel-team/linux/-/merge_requests/1214): straightforward.
* [\#1210](https://salsa.debian.org/kernel-team/linux/-/merge_requests/1210): We want to have the MR done properly. bwh will have a look.
* [\#1200](https://salsa.debian.org/kernel-team/linux/-/merge_requests/1200): Merged already
* [\#1196](https://salsa.debian.org/kernel-team/linux/-/merge_requests/1196): Might close it. No need for sid.
* [\#1195](https://salsa.debian.org/kernel-team/linux/-/merge_requests/1195): The additional patch is not applied upstream yet. We wil lwait until the change has applied there.
* [\#1178](https://salsa.debian.org/kernel-team/linux/-/merge_requests/1178): Probably ok to merge.
* [\#1038](https://salsa.debian.org/kernel-team/linux/-/merge_requests/1038): We can close this MR and apply Ben's fix.
* [\#741](https://salsa.debian.org/kernel-team/linux/-/merge_requests/741): Give others a change to review it after the rebase. carnil will try if time permits.
### Misc / AOB
* Nothing special, acknowledge that next chair will be carnil and meeting takes place on IRC.