17:58:08 #startmeeting 17:58:08 Meeting started Tue Aug 8 17:58:08 2023 UTC. The chair is spwhitton. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:58:08 Useful Commands: #action #agreed #help #info #idea #link #topic. 17:58:13 #topic Roll Call 17:58:14 Sean Whitton 17:58:17 Matthew Vernon 17:58:20 Timo Röhling 17:58:20 Christoph Berg 17:58:25 Stefano Rivera 17:59:07 Don't think we received any apologies. Let's leave it 5m. 17:59:29 Helmut Grohne 18:00:00 smcv: ping 18:00:03 mjg59: ping 18:02:23 Matthew Garrett 18:03:02 #topic Review of previous meeting's AIs 18:03:11 Emperor: you filed your bug, thank you -- any follow-up needed? 18:03:15 I asusme not, just asking to be sure. 18:03:35 I don't think so; I don't know if the release-notes will take the suggestion or not. 18:03:53 okay. well it was just an aid, not a necessity. thanks again. 18:03:58 I updated the slides. 18:04:02 For the minutes, the bug is #1041072 18:04:05 tumbleweed: how are we doing with all being co-presernters on the session? 18:04:20 #link https://bugs.debian.org/1041072 18:04:26 I'll not be there, missed the registration deadline :-/ 18:04:29 * smcv is here, sorry I'm late 18:04:33 hello smcv 18:04:47 to be clear, ideally we are all co-presernters even if we'r enot attending 18:04:55 ok with me 18:04:56 spwhitton: I got an email about the talk, which suggests the system thinks I'm a co-presenter 18:05:05 spwhitton: checking... 18:05:30 registered speakers: Stefano Rivera & Sean Whitton & Matthew Vernon & Timo Röhling & Helmut Grohne 18:05:58 mjg59, Myon: Please sign up on https://debconf23.debconf.org/ and I can add you 18:06:01 okay, can smcv, mjg59 and Myon go and SSO login there 18:06:12 just logging in ought to be sufficient. 18:06:13 smcv is added 18:06:17 tumbleweed: On it 18:06:25 I'm logged in 18:06:33 #topic Any remaining DebConf23 presentation arrangements 18:06:42 we haven't talked much about this 18:06:46 tumbleweed: Ok should be there 18:06:49 but, it's a BoF, so that's not in itself a problem 18:06:56 everybody added, thanks 18:07:00 nice, thanks. 18:07:04 ta 18:07:06 tumbleweed: have you had a chance to look at the slides? 18:07:23 spwhitton: had not, will do 18:07:27 "WARNING: Talk proposal submitted, but speaker hasn't registered to attend. Register now!" 18:07:39 :) 18:07:45 we don't actually have another meeting before debconf 18:08:01 so ... any remaining tasks? 18:08:13 tumbleweed: do you feel ready? :) 18:08:30 sure 18:09:23 okay then. well, post mail or here on IRC if you find any issues after reviewing the slides. 18:09:31 we have a meeting during debconf, no? do we delay or reschedule that? 18:09:47 good question. thoughts? 18:09:54 OK, skimmed them 18:10:11 you'll likely have better things to do there than talking to me via IRC 18:10:18 that seems straightforward enough. I'll do some skimming and thinking about anything else to cover 18:10:29 (skimming the related bugs I mean) 18:10:42 tumbleweed: cool. it is down as a BoF, so, presentation should be ~10m or so 18:10:43 so move (or skip?) it 18:10:54 spwhitton: right 18:10:58 I suggest we skip it unless we get bugs filed, in which case we move it 18:11:05 +1 18:11:06 ack 18:11:16 thank you again Stefano. 18:11:20 #topic merged-/usr 18:11:37 helmut: I think things are quiet but maybe you have things to discuss? 18:11:53 not much has happened here. it mostly seems like a one-man show at this time and I had a nice vacation :) 18:12:07 one thing seems worthy reporting though. 18:12:32 if you move an empty directory from / to /usr as part of a package upgrade (i.e. no move between packages), it gets lost reliably 18:12:52 (I have a thing to add when helmut is finished, if he doesn't cover it) 18:13:34 https://subdivi.de/~helmut/dumat.yaml has been improved a bit and is updated 4 times a day. it now associates bugs usertagged fileconflict for instance 18:13:57 I've also spent quite some time filing bugs (for file conflicts and for empty directories that should be deleted) 18:14:04 and that's about it. smcv? 18:14:12 helmut: have you been getting constructive responses to your filings? 18:14:49 not universally, but mostly. some people argued about severities when they couldn't reproduce my unpack errors 18:15:06 well, they're mainly for tracking so I guess severities don't matter too much? 18:15:20 I tend to send file conflict bugs without patches at rc severity 18:15:30 that tends to annoy some people 18:15:41 yeah. well good that most responses have been good. 18:15:54 smcv: please go ahead 18:16:07 helmut: I'm still seeing unsupported upgrades listed in that file, like bullseye to unstable. would it be possible to have a filtered output that only covers the supported/supportable scenarios? 18:16:42 smcv: I consider that details. can we defer that outside the meeting rather than taking everyones time for this aspect? 18:16:52 of course 18:16:57 so the thing I wanted to mention 18:17:02 smcv: do you have time after the meeting? 18:17:38 smcv: do note though that "bullseye to unstable" often is a version range 18:17:39 I got a MR merged into debootstrap to teach it to /usr-merge all suites >= trixie even for the buildd profile, as we discussed before 18:17:59 coolio. a stable update is required to switch over the buildds, right? 18:18:31 which Luca NMU'd, and promptly had hostile-NMU'd away by a developer who no longer has upload rights as a result 18:18:39 oh, right, 18:18:45 where were things left? 18:18:45 spwhitton: do note that DSA does not upgrade to bookworm yet, so we need an oldstable update 18:18:56 things were left with Luca's NMU being reinstated 18:18:58 helmut: ah good point. 18:19:24 Hideki has traditionally been the debootstrap maintainer, but he seems inactive 18:19:29 so now we have merged-/usr for sufficiently new suites' buildds, but only if either DSA upgrades to a suitable version, or "larger" infra replicates the change 18:19:37 to be precise, luca quickly reverted the revert 18:19:42 right 18:20:02 smcv: do you think something should happen imminently? have you asked DSA if they have plans to upgrade? 18:20:40 From my pov, we can leave things as is for now. We want buildds merged once we lift the moratorium 18:20:41 I have not, but I'm getting concerned that trixie was meant to be the point at which maintainers can start relying on merged-/usr, and that kinda conflicts with official buildds not having it 18:21:13 smcv: could we action you to find out DSA's plans, at least? 18:21:20 and, do you agree with what helmut just said? 18:21:22 ok, rough sketch of my plans may help here maybe 18:21:35 "we can rely on merged-/usr now[1]" [1] but if it makes a package FTBFS then it's still RC 18:21:41 seems not entirely helpful 18:21:44 at this time, I'm ironing out issues in the detector and filing patches for actionable things 18:22:16 I also need to update dep17 with the consensus achieved thus far and propose a concrete combination of mitigations 18:22:47 then, I'll arm dumat to automatically file rc bugs and once that has happend and we have /usr-merged buildds, we can lift the moratorium and mass migrate files 18:23:31 that bug filing part totally is not implemented at all yet and I want to be really careful not to file lots of bogus rc bugs 18:23:36 helmut: is there any reason for smcv not to pursue the buildd chang ein the meantime? 18:24:31 spwhitton: there just isn't that much urgency yet, but I'm ok with moving forward on that side 18:24:33 it's not just buildds I'm concerned about, but also autopkgtest, piuparts, all similar things 18:24:54 if smcv has the time to work on it, then doing it in parallel seems like a good idea 18:24:59 to avoid random hold ups later 18:25:00 +1 18:25:18 last time we said "too soon", do we have consensus that it is not too soon now? 18:25:52 I think I said too soon, because we didn't have consensus on the primary mitigation. We do have that consensus now. 18:26:26 oh yeah you weren't sure whether you needed to change the bootstrapping protocol, which would have also required a stable update 18:26:31 is that mitigation summarized anywhere? (sorry I didn't follow closer) 18:26:38 My last consensus call said that we do not want to rely on dpkg changes as the primary vehicle for finishing the transition and that generally resulted in agreement 18:26:54 nod 18:26:59 yes. 18:26:59 smcv: Can we piggy back my debootstrap change on the stable update? 18:27:28 https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/96 18:27:44 With current consensus, we also need that MR in stable 18:28:39 and oldstable if DSA haven't upgraded yet? 18:28:53 Unsure about process here. If Hideki is MIA here, should I merge and NMU it? 18:28:56 smcv: yes 18:29:26 so yeah, can we get that change into unstable and backport both changes at once rather than having to pester SRM four times? 18:29:28 helmut: just use DELAYED etc. in the usual way I think 18:29:46 shall I action you to do that? 18:30:04 I'd appreciate more eyeballs on that change though. I'll probably have to highlight it to d-devel 18:30:07 smcv: and can I action you to prepare stable or oldstable updates after helmut's update reaches unstable? 18:30:23 it's not really TC business but having action items to check up on next meeting may help jog our memories. 18:30:27 spwhitton: ok 18:30:32 please give that change at least 3 weeks in trixie before migrating to stable. 18:30:50 #action helmut to get all changes that need to go to stable debootstrap into sid 18:30:53 I hope it doesn't break anything, but I kinda fear otherwise 18:31:04 #action smcv to prepare (old)stable update for debootstrap once helmut's upload has been in sid for three weeks 18:31:10 okay. shall we move on? 18:31:18 thanks to both of you. 18:31:31 sure, we've lost ourselves in details anyway and this all is design and implementation work rather than ctte matter 18:32:26 I find all this quite helpful for retaining enough of this in my head. 18:32:29 #topic Any Other Business 18:32:32 is anyone aware of anything? 18:32:48 not me 18:33:02 the tzdata vs UTC one Myon mentioned seems to have resolved itself peacefully 18:33:19 yes 18:33:43 same for the cmake/meson/python install layout 18:33:49 great! 18:33:57 I didn't expect it to become an issue, just wanted to ask for more opinions while it wasn't clear yet 18:34:57 (I spent most of the morning on debugging the fallout, only to realize that installing tzdata-legacy from *unstable* instead of from trixie made the remaining PostgreSQL testsuite problems go away) 18:35:11 the cmake/meson/python install layout I have proposed a debhelper patch, interested people please take a look 18:35:36 likewise for meson packages regressing by compiling bytecode when previously they didn't 18:36:06 I had a look at the dh patch and it looked fine, but my Perl skills are very limited 18:36:24 #endmeeting