15:12:51 #startmeeting 15:12:51 Meeting started Thu May 27 15:12:51 2021 UTC. The chair is h01ger. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:12:51 Useful Commands: #action #agreed #help #info #idea #link #topic. 15:12:56 lets log this 15:13:06 anyone wants to chair this? :) 15:14:33 gladk: you are maintainer there 15:14:41 * h01ger found it like this 15:16:32 h01ger, ok, thanks. Somebody probably removed those repos. Sorry for false alarm. 15:19:18 * ta finally also arrived ... 15:19:35 gladk, btw packages are often painful to work with, so I find that adding git-build-package on top of that is just a hassle with no benefits, hence why I don't use Git 15:20:55 Interesting. It is the opposite for me. Trying to work with packages outside of Git tends to be a much bigger pain for me. 15:21:10 With firefox and thunderbird being notable exceptions 15:21:23 Beuc, well, I am using mostly it for running salsa-ci pipelines on packages, which I am working on. It is just a part of testing strategy 15:21:25 Those are really huge indeed. 15:22:05 Well I test things in my working VM, and usually when something fails at Salsa I just have to run the tests locally, so that sounds like duplicate work for me 15:22:36 The only pro I see is that there's 3rd-party trace running the tests. 15:23:41 #topic no real meeting today, though this is being logged with meetbot in case something useful is said 15:24:22 @Beuc, Sure, it is just a personal preferences. 15:24:50 If it's just a matter of preference I'll stick with no-git then. 15:25:22 for me, I just get the dsc -> convert to git via gbp import-dsc [...] -> do work & upload -> sleep like a baby, heh 15:25:51 I don't find it beneficial to push the repository under the salsa namespace, really 15:26:08 unless, there's something that's worth keeping; for eg: enabled tests for curl, etc. 15:26:31 If the meeting is cancelled for today, could we please then set a date for the next meeting? 15:26:55 It should already be set for June 24th 15:26:59 gladk: last Thursday of the next month 15:27:01 https://wiki.debian.org/LTS/Meetings 15:27:52 OK, thank you for information 15:28:35 its always last thursday of the month, 15 UTC. until someone is unhappy and we make a new poll... 15:29:07 and every other meeting is video and every other is irc 15:30:50 h01ger: may I set the dates till the end of the year on Wiki or it is too over-engineered? 15:31:57 sure 15:32:15 gladk, I'd say over-engineered, but copy/pasting h01ger's rationale would be useful 15:33:31 * h01ger nods 15:39:13 Do we need to anticipate something with the bullseye release, when oldstable becomes oldoldstable and so on? 15:39:58 not until next year 15:40:18 buster (oldstable) will still be supported by the sec team for another year 15:40:53 sure but I was wondering if some old*stable aliases needed updating or something 15:40:55 so next year onward, the change will reflect on us; jessie -> completely EOL'ed; stretch -> ELTS; buster -> LTS 15:41:42 ooh, interesting but none I can think of 15:41:53 maybe others might have something 15:41:54 I'm aware of https://wiki.debian.org/LTS/Development#Switching_to_the_next_LTS_release for next year, just wondered if there's something on bullseye release specifically 15:42:50 OK, I have added a couple of new dates. and a general rule "Last Thursday of the month, 15 UTC" 15:43:46 nice 15:50:31 gladk: I did remove the various "foo_please_remove_me" repositories, yes 15:57:20 buxy: the security tracker needs updates (when stable becomes oldstable and oldstable becomes oldoldstable and so on) and there's some work on the ftp master side. that's like for every other debian release, there's nothing bullseye specific. 15:57:27 Beuc: not buxy :) 15:58:29 the security team does it for the main security tracker, we might have to do something for the ELTS one 15:58:49 buxy: thank you 15:59:06 ah ok 16:09:27 OK time to wrap. 16:09:33 #endmeeting 16:09:39 good meeting! 16:09:45 :P 16:10:06 Beuc: you snatched away 1 minute from the meeting :( 16:10:10 hehe 16:10:15 #endmeeting