| * RAOF learns about using "--version" when accepting from -rejected. | 05:27 | |
| Skia | if anyone wants to follow the archive opening, it's tracked here: https://warthogs.atlassian.net/browse/RTMP-2068 | 09:01 |
|---|---|---|
| ravikant_ | Skia: do you have permissions to pin it? | 09:04 |
| Skia | no | 09:04 |
| Skia | or I'm not aware of that | 09:04 |
| adrien | if you /msg chanserv flags #ubuntu-release | 09:06 |
| adrien | you see that every ubuntu member can set the topic (I hope there isn't another freenode mechanism in place) and that's probably your best bet without having to rely on a small set of specific people | 09:07 |
| sudip | wow, there are those many tasks for archive opening, I used to think someone from release team will go and run a script | 09:07 |
| Skia | adrien: even messaging ChanServ, I don't have permission | 09:09 |
| Skia | I've tried to become an Ubuntu Contributing Developer a while ago, but didn't get much support, and got sidetracked :-) | 09:10 |
| Skia | (https://discourse.ubuntu.com/t/florent-skia-jacquet-membership-application/45913) | 09:11 |
| Skia | (not to reduce to support of p_aride and j_uliank, but I was told one or two more would be good) | 09:12 |
| ravikant_ | paride: I just noticed you are a Ubuntu Release Team member now https://launchpad.net/~ubuntu-release/+members#active. Congratulations! | 09:18 |
| paride | ravikant_, thanks! | 09:19 |
| paride | ravikant_, that happened about 16 hours ago :) | 09:20 |
| ravikant_ | sudip: we are in the process of identifying what can be scripted. The source for jira tasks is here if you are curious https://code.launchpad.net/~ubuntu-release/ubuntu-release-tools/+git/templates | 09:33 |
| sudip | congrats paride | 09:36 |
| sudip | ravikant_: not sure if you are opening all those jira manually or not, but Atlassian has some API and you should be able to script the subtask creations | 09:40 |
| Skia | sudip: yes, there is a script to open them, thankfully :-) | 09:41 |
| Skia | https://git.launchpad.net/ubuntu-release-tools/tree/generate-milestone-jira-cards | 09:43 |
| tjaalton | rbasak: hi, there's a new attempt for the ubuntu-drivers-common sru for jammy if you have time to have a look | 09:43 |
| Skia | ubuntu-sru: could somebody have a look at the autopkgtest upload for Jammy and Noble, so that we can start working on the verification? Thanks :-) | 09:46 |
| === ChanServ changed the topic of #ubuntu-release to: Released: 24.04 LTS Noble Numbat, 24.10 Oracular Oriole | Archive: 25.04 archive opening in progress: https://warthogs.atlassian.net/browse/RTMP-2068 | Highlight ubuntu-archive for archive admin help | We accept payment in cash, cheque or mezcal | melius malum quod cognoscis | infinity, you are missed | ||
| doko | can first packages already be uploaded to the unapproved queue? | 09:54 |
| paride | doko, I don't believe so, please wait a bit | 09:59 |
| paride | doko, launchpad has no awareness of plucky yet, so I guess uploads will be rejected | 10:00 |
| paride | seb128, hi, https://warthogs.atlassian.net/browse/RTMP-2077 requires an AA to be done, is that something you can do? | 10:04 |
| paride | tasks in the jira checklist have to be executed in order (mostly), so that's where we currently are | 10:06 |
| doko | paride: I don't see "asking toolchain maintainer's for new changes for the opening a few weeks before opening" on this list ... | 10:14 |
| paride | doko, is that a wishlist item, or something you actually used to get? | 10:15 |
| doko | the latter | 10:15 |
| seb128 | paride, I'm in a meeting but will poke at it after | 10:15 |
| paride | seb128, thanks, then I'll assign the card to you, and then there will be another one requiring AA powers (I'll prepare a MP, to be reviewed && merged) | 10:16 |
| seb128 | paride, thanks | 10:16 |
| paride | doko, I can see it: RTMP-2107 | 10:21 |
| paride | doko, I assigned the card to you. We are not ready for that card yet, as too many of the above cards are missing, please monitor progress | 10:24 |
| doko | paride: no, there should be a card that is asking for preparation in advance | 10:25 |
| doko | btw, are these cards visible for the community? | 10:25 |
| paride | doko, they should be | 10:26 |
| Skia | yes they are | 10:26 |
| paride | doko, there I see no such card in the cards templates repo (including history) | 10:26 |
| doko | see the old wiki page for that item | 10:27 |
| paride | doko, found it, we'll figure out where to re-add it, the easiest would be to have that reminder together with the "prepare final release" tasks | 10:31 |
| -queuebot:#ubuntu-release- Unapproved: accepted lxml [source] (noble-proposed) [5.2.1-1ubuntu0.1] | 10:44 | |
| paride | seb128, I need AA permissions for https://code.launchpad.net/~paride/ubuntu-archive-tools/+git/ubuntu-archive-tools/+merge/475197 | 11:14 |
| paride | rbasak, o/ | 11:18 |
| paride | rbasak, as a tech board member, is https://warthogs.atlassian.net/jira/core/projects/RTMP/board?selectedIssue=RTMP-2082 something you can help with? | 11:18 |
| paride | rbasak, that can't be acted on right now because plucky does not exist on LP yet, but hopefully we'll be unblocked soon | 11:20 |
| rbasak | Happy to help. Specific instructions would be nice! I think I understand what that means though. Let me see... | 11:25 |
| rbasak | paride: I don't see the new series in Launchpad, so I'm not sure how to interpret that instruction, sorry. I thought I'd look at the release manager setting for Oracular and apply the same setting to the new series. But I don't see the new series to change the "Release manager" setting for. | 11:27 |
| rbasak | Is there a dependency here on something else? | 11:27 |
| rbasak | paride: ah I think it's blocked on RTMP-2081. But when that's done, I think I understand what I need to do. | 11:29 |
| rbasak | Oh. You said all that already. Sorry. Yes. | 11:29 |
| paride | rbasak, great, thanks! I'll ping you once RTMP-2081 is done | 11:35 |
| paride | rbasak, on more specific instructions: I can't see relevant UI, so I can't be more specific, but if you can provide a better description for the task after doing it I can improve that card. Or you can open a MP to expand | 11:37 |
| paride | https://git.launchpad.net/~ubuntu-release/ubuntu-release-tools/+git/templates/tree/jira-milestones/devel-release/new-cycle-opening.yaml#n67 | 11:37 |
| rbasak | paride: I think it can probably be changed to "Ask a Tech Board member to go to https://launchpad.net/$new_release/+driver and set the Driver to "ubuntu-release". | 11:41 |
| rbasak | " | 11:41 |
| rbasak | Probably the carrying forward part is unnecessary. | 11:41 |
| rbasak | Sorry the URL is wrong. | 11:41 |
| rbasak | https://launchpad.net/ubuntu/$new_release/+driver | 11:41 |
| bdrung | for the distro-info-data release, I need the EOL date. See https://bugs.launchpad.net/ubuntu/+source/distro-info-data/+bug/2084572 | 11:49 |
| -ubottu:#ubuntu-release- Launchpad bug 2084572 in distro-info-data (Ubuntu Oracular) "Please add a new entry for Ubuntu 25.04 Plucky Puffin" [Undecided, Confirmed] | 11:49 | |
| paride | rbasak, https://code.launchpad.net/~paride/ubuntu-release-tools/+git/templates/+merge/475202 | 11:49 |
| seb128 | paride, so I'm a bit unclear on what change to do for RTMP-2077 the card states | 11:57 |
| seb128 | "to disable proposed-migration for the new series (add an exit 0 to the ubuntu/$DEFAULT_SERIES case branch)" | 11:57 |
| seb128 | the corresponding script is http://bazaar.launchpad.net/~ubuntu-archive/ubuntu-archive-scripts/trunk/view/head:/run-proposed-migration | 11:57 |
| seb128 | is 'proposed-migration' in that context the command 'generate-team-p-m'? | 11:57 |
| seb128 | like should the exit 0 be added line 55? | 11:58 |
| paride | bdrung, `date -date="2024-10-10 + 27 weeks"` says Thu, 17 Apr 2025, *however* I think ginggs computed release/eol dates recently | 11:59 |
| paride | ginggs, o/, do I remember right? | 11:59 |
| seb128 | or is proposed-migration the call to `code/b1/britney $actions` l53? | 11:59 |
| paride | seb128, looking | 11:59 |
| seb128 | but in that case that's outside of the case branch mentioned | 11:59 |
| paride | bdrung, forget the +27 weeks, that's a cycle, not the EOL date | 12:01 |
| bdrung | paride, the EOL is around 9 month, but the history data are not clear if rounded up or down. | 12:01 |
| paride | let's see if ginggs remembers us having a date set already | 12:01 |
| paride | (apparently there is a partial git conversion of ubuntu-archive-scripts, which double-confused me: https://code.launchpad.net/ubuntu-archive-scripts/+git) | 12:13 |
| paride | seb128, AIUI the "real" proposed migration is the `code/b1/britney` command. By adding an `exit 0` in the earlier `case`, we prevent that to be reached | 12:15 |
| seb128 | paride, ah, so line 26 ? | 12:15 |
| paride | seb128, yes, I would add it before the actions= | 12:16 |
| paride | so we do nothing for oracular | 12:16 |
| seb128 | paride, done, thanks | 12:16 |
| paride | seb128, thanks! now, can you please review https://code.launchpad.net/~paride/ubuntu-archive-scripts/plucky/+merge/475204 and merge if looking good? | 12:32 |
| paride | and https://code.launchpad.net/~paride/ubuntu-archive-tools/+git/ubuntu-archive-tools/+merge/475197 (not a blocker for archive opening I believe, but needs to be done at some point) | 12:35 |
| seb128 | paride, reviewed and merged the -scripts one | 12:36 |
| Skia | bdrung: https://discourse.ubuntu.com/t/plucky-puffin-release-schedule/36461 | 13:25 |
| doko | you'r optimistic about the toolchain upload tomorrow ;p | 13:26 |
| bdrung | Skia, that page says nothing about the EOL date. | 13:26 |
| Skia | I thought it did, sorry | 13:27 |
| doko | please make that page editable | 13:28 |
| Skia | https://wiki.ubuntu.com/Releases says January 2026, but without a specific day | 13:28 |
| Skia | doko: it is for me for some reason, but I don't know what gives me that power, and I can't edit the page properties or whatever, sorry | 13:29 |
| bdrung | Skia, yes. that is the 9 month of support. | 13:30 |
| doko | Skia: probably community member bdmurray denying some rights ... ;p | 13:31 |
| Skia | XD | 13:32 |
| sudip | isn't that "ubuntu-wiki-editors" group? I do see Skia in the members list | 13:33 |
| Skia | I thought that was only for the wiki, but maybe it works for Discourse too | 13:35 |
| sudip | ahh.. ok | 13:36 |
| tsimonq2 | o/ I'll claim vim, devscripts, and a few other of the usual ones. | 14:11 |
| tsimonq2 | https://warthogs.atlassian.net/browse/RTMP-2140 claiming | 14:13 |
| fheimes | highlighting ubuntu-sru - can someone from the SRU team please approve the jammy s390-tools build for s390x; it needs an approval: https://launchpad.net/ubuntu/+source/s390-tools/2.20.0-0ubuntu3.4 --> Jammy: s390x (Unapproved) | 14:40 |
| ahasenack | I don't understand that state. It's built in proposed already | 14:41 |
| ahasenack | is it because of the other "signed" packages that are in unapproved? | 14:41 |
| rbasak | You need an AA for that I believe. | 14:43 |
| fheimes | @hasenack the src is in -proposed, but due to the signature job building the binaries req. add. approval | 14:44 |
| rbasak | At least the SRU team don't usually handle this case, whether because of signatures or new binaries. | 14:44 |
| rbasak | ubuntu-archive: ^ | 14:44 |
| fheimes | I can try to ask sil2100, he did that a few times in the past ... | 14:44 |
| rbasak | This is essentially the same case as https://wiki.ubuntu.com/StableReleaseUpdates/Grub | 14:45 |
| rbasak | And that's underdocumented :( | 14:45 |
| rbasak | I couldn't complete the rest since I don't know what the process actually is. | 14:45 |
| ahasenack | https://launchpad.net/ubuntu/jammy/+queue?queue_state=1&queue_text=s390-tools | 14:45 |
| ahasenack | top most is recent, from two days ago, but there are also older uploads | 14:45 |
| ahasenack | those are tarballs? | 14:46 |
| seb128 | ahasenack, rbasak , I don't know about the old tarballs but I've accepted the recent upload now | 14:48 |
| rbasak | Thanks! | 14:48 |
| fheimes | yes, it always looks like this in this case; technically an SRU team member should have enough power to approve in this case, but like rbasak said it's relatively unknown how and not documented ... | 14:48 |
| -queuebot:#ubuntu-release- Unapproved: accepted s390-tools [s390x] (jammy-proposed) [2.20.0-0ubuntu3.4] | 14:48 | |
| fheimes | @seb128: oh cool, just see it >"accepted" - thx ! | 14:49 |
| seb128 | np! | 14:49 |
| ahasenack | thanks seb128 | 14:51 |
| tsimonq2 | https://salsa.debian.org/lintian/lintian/-/merge_requests/537 | 15:20 |
| -ubottu:#ubuntu-release- Merge 537 in lintian/lintian "Add 'plucky' as a known Ubuntu distribution." [Opened] | 15:20 | |
| -queuebot:#ubuntu-release- Unapproved: s390-tools-signed (jammy-proposed/main) [2.20.0-0ubuntu3.3 => 2.20.0-0ubuntu3.4] (core) | 16:00 | |
| vorlon | ahasenack, jamespage: impossible> I've had requests before for no-change rebuilds for component changes instead of pocket copies (I think from the security team?), but it has certainly always been possible at the archive level | 16:12 |
| tsimonq2 | https://github.com/vim/vim/pull/15882 | 16:38 |
| -ubottu:#ubuntu-release- Pull 15882 in vim/vim "runtime(debversions): Add plucky (25.04) as Ubuntu release name" [Open] | 16:38 | |
| -queuebot:#ubuntu-release- Unapproved: accepted s390-tools-signed [source] (jammy-proposed) [2.20.0-0ubuntu3.4] | 17:17 | |
| === pushkarnk1 is now known as pushkarnk | ||
| -queuebot:#ubuntu-release- Unapproved: lintian (focal-proposed/main) [2.62.0ubuntu2.4 => 2.62.0ubuntu2.5] (core, i386-whitelist) | 17:46 | |
| -queuebot:#ubuntu-release- Unapproved: lintian (noble-proposed/main) [2.117.0ubuntu1.1 => 2.117.0ubuntu1.2] (core) | 17:46 | |
| -queuebot:#ubuntu-release- Unapproved: lintian (jammy-proposed/main) [2.114.0ubuntu1.4 => 2.114.0ubuntu1.5] (core) | 17:46 | |
| -queuebot:#ubuntu-release- Unapproved: lintian (oracular-proposed/main) [2.118.2ubuntu1 => 2.118.2ubuntu1.1] (core) | 17:46 | |
| -queuebot:#ubuntu-release- Unapproved: vim (focal-proposed/main) [2:8.1.2269-1ubuntu5.25 => 2:8.1.2269-1ubuntu5.26] (core, i386-whitelist) | 17:47 | |
| -queuebot:#ubuntu-release- Unapproved: vim (jammy-proposed/main) [2:8.2.3995-1ubuntu2.19 => 2:8.2.3995-1ubuntu2.20] (core, i386-whitelist) | 17:47 | |
| -queuebot:#ubuntu-release- Unapproved: vim (oracular-proposed/main) [2:9.1.0496-1ubuntu6 => 2:9.1.0496-1ubuntu6.1] (core, i386-whitelist) | 17:48 | |
| doko | ahasenack, jamespage, vorlon: are you talking about ceph? there's now a boost1.83 upload in noble-proposed, which fixes that issue (if that is your issue) | 17:57 |
| ahasenack | it does, by the nature of being an updated version | 17:57 |
| ahasenack | it was ftbfs'ing yesterday, today it's fine | 17:57 |
| ahasenack | excuses still thinks ceph is entangled with boost1.83, though. I retried the failed dep8 test in libreoffice, that will be a while, | 17:58 |
| ahasenack | I was wondering if ceph should land in updates together with the new boost or not. ceph was built with boost from updates, not the new one in proposed | 17:58 |
| doko | feel free to accept boost1.83 once it has autopkg tests passed. this is just a no-change upload | 17:59 |
| ahasenack | doko: what is the verification for boost, check the gcc build flags? | 17:59 |
| doko | yes, have a look at the build logs on ppc64el and s390x, and let all the autopkg tests pass | 18:00 |
| ahasenack | ok | 18:00 |
| ahasenack | noble has 2261@armhf queued tests, and 3036@ppc64el ones :/ | 18:07 |
| -queuebot:#ubuntu-release- Unapproved: vim (noble-proposed/main) [2:9.1.0016-1ubuntu7.3 => 2:9.1.0016-1ubuntu7.4] (core, i386-whitelist) | 18:08 | |
| ahasenack | I see perl happened in noble | 18:08 |
| ahasenack | and armhf test runners are having trouble (tons of tests with "unknown" as the version in excuses) | 18:09 |
| === sudip_ is now known as sudip | ||
| -queuebot:#ubuntu-release- Unapproved: adasockets (noble-proposed/universe) [1.14-1build2 => 1.14-1build2.1] (no packageset) (sync) | 18:17 | |
| -queuebot:#ubuntu-release- Unapproved: libgmpada (noble-proposed/universe) [1.6-2build2 => 1.6-2build2.1] (no packageset) (sync) | 18:17 | |
| -queuebot:#ubuntu-release- Unapproved: music123 (noble-proposed/universe) [16.6-6build2 => 16.6-6build2.1] (no packageset) (sync) | 18:17 | |
| -queuebot:#ubuntu-release- Unapproved: ghdl (noble-proposed/universe) [4.1.0+dfsg-0ubuntu2 => 4.1.0+dfsg-0ubuntu2.1] (no packageset) (sync) | 18:18 | |
| -queuebot:#ubuntu-release- Unapproved: libxmlada (noble-proposed/universe) [24.0.0-2build2 => 24.0.0-2build2.1] (no packageset) (sync) | 18:18 | |
| -queuebot:#ubuntu-release- Unapproved: adacgi (noble-proposed/universe) [1.6-34build1 => 1.6-34build1.1] (no packageset) (sync) | 18:18 | |
| -queuebot:#ubuntu-release- Unapproved: gprbuild (noble-proposed/universe) [2024.1.20231009-4build2 => 2024.1.20231009-5~24.04] (no packageset) (sync) | 18:18 | |
| -queuebot:#ubuntu-release- Unapproved: plplot (noble-proposed/universe) [5.15.0+dfsg2-9build1 => 5.15.0+dfsg2-9build1.1] (no packageset) (sync) | 18:18 | |
| -queuebot:#ubuntu-release- Unapproved: ahven (noble-proposed/universe) [2.8-9ubuntu2 => 2.8-9ubuntu2.1] (no packageset) (sync) | 18:18 | |
| -queuebot:#ubuntu-release- Unapproved: topal (noble-proposed/universe) [81-2ubuntu2 => 81-2ubuntu2.1] (no packageset) (sync) | 18:18 | |
| -queuebot:#ubuntu-release- Unapproved: libaunit (noble-proposed/universe) [24.0.0-2build1 => 24.0.0-2build1.1] (no packageset) (sync) | 18:18 | |
| -queuebot:#ubuntu-release- Unapproved: libflorist (noble-proposed/universe) [2022.0.1~20220616-5ubuntu2 => 2022.0.1~20220616-6~24.04] (no packageset) (sync) | 18:18 | |
| -queuebot:#ubuntu-release- Unapproved: libgtkada (noble-proposed/universe) [24.0.0-2build1 => 24.0.0-3~24.04] (no packageset) (sync) | 18:18 | |
| -queuebot:#ubuntu-release- Unapproved: libtemplates-parser (noble-proposed/universe) [24.0.0-2build1 => 24.0.0-2build1.1] (no packageset) (sync) | 18:19 | |
| -queuebot:#ubuntu-release- Unapproved: libxmlezout (noble-proposed/universe) [1.06.2-14build1 => 1.06.2-14build1.1] (no packageset) (sync) | 18:19 | |
| -queuebot:#ubuntu-release- Unapproved: libgnatcoll (noble-proposed/universe) [24.1.20230921-4build2 => 24.1.20230921-4build2.1] (no packageset) (sync) | 18:19 | |
| -queuebot:#ubuntu-release- Unapproved: libtexttools (noble-proposed/universe) [2.1.0-28build1 => 2.1.0-28build1.1] (no packageset) (sync) | 18:19 | |
| -queuebot:#ubuntu-release- Unapproved: libncursesada (noble-proposed/universe) [6.3.20211021-11build1 => 6.3.20211021-11build1.1] (no packageset) (sync) | 18:19 | |
| -queuebot:#ubuntu-release- Unapproved: alire (noble-proposed/universe) [1.2.1-1.1build1 => 1.2.1-1.1build1.1] (no packageset) (sync) | 18:19 | |
| -queuebot:#ubuntu-release- Unapproved: dbusada (noble-proposed/universe) [0.6.2-6build1 => 0.6.2-6build1.1] (no packageset) (sync) | 18:19 | |
| -queuebot:#ubuntu-release- Unapproved: libgnatcoll-bindings (noble-proposed/universe) [24.0.0-2build2 => 24.0.0-2build2.1] (no packageset) (sync) | 18:19 | |
| -queuebot:#ubuntu-release- Unapproved: phcpack (noble-proposed/universe) [2.4.90+dfsg-1build1 => 2.4.90+dfsg-1build1.1] (no packageset) (sync) | 18:19 | |
| -queuebot:#ubuntu-release- Unapproved: anet (noble-proposed/universe) [0.5.0-3build1 => 0.5.0-3build1.1] (no packageset) (sync) | 18:19 | |
| -queuebot:#ubuntu-release- Unapproved: liblog4ada (noble-proposed/universe) [1.3.1.b6dafb49-13build2 => 1.3.1.b6dafb49-13build2.1] (no packageset) (sync) | 18:19 | |
| -queuebot:#ubuntu-release- Unapproved: libalog (noble-proposed/universe) [0.6.2-5build1 => 0.6.2-5build1.1] (no packageset) (sync) | 18:19 | |
| -queuebot:#ubuntu-release- Unapproved: libgnatcoll-db (noble-proposed/universe) [23.0.0-6build1 => 23.0.0-6build1.1] (no packageset) (sync) | 18:19 | |
| -queuebot:#ubuntu-release- Unapproved: pcscada (noble-proposed/universe) [0.7.7-6build1 => 0.7.7-6build1.1] (no packageset) (sync) | 18:19 | |
| -queuebot:#ubuntu-release- Unapproved: accepted adasockets [sync] (noble-proposed) [1.14-1build2.1] | 18:22 | |
| -queuebot:#ubuntu-release- Unapproved: accepted ghdl [sync] (noble-proposed) [4.1.0+dfsg-0ubuntu2.1] | 18:23 | |
| -queuebot:#ubuntu-release- Unapproved: accepted libgmpada [sync] (noble-proposed) [1.6-2build2.1] | 18:23 | |
| -queuebot:#ubuntu-release- Unapproved: accepted libxmlada [sync] (noble-proposed) [24.0.0-2build2.1] | 18:31 | |
| -queuebot:#ubuntu-release- Unapproved: accepted music123 [sync] (noble-proposed) [16.6-6build2.1] | 18:37 | |
| -queuebot:#ubuntu-release- Unapproved: accepted plplot [sync] (noble-proposed) [5.15.0+dfsg2-9build1.1] | 18:39 | |
| -queuebot:#ubuntu-release- Unapproved: accepted topal [sync] (noble-proposed) [81-2ubuntu2.1] | 18:39 | |
| -queuebot:#ubuntu-release- Unapproved: accepted gprbuild [sync] (noble-proposed) [2024.1.20231009-5~24.04] | 18:41 | |
| -queuebot:#ubuntu-release- Unapproved: accepted adacgi [sync] (noble-proposed) [1.6-34build1.1] | 18:43 | |
| -queuebot:#ubuntu-release- Unapproved: accepted ahven [sync] (noble-proposed) [2.8-9ubuntu2.1] | 18:49 | |
| -queuebot:#ubuntu-release- Unapproved: accepted libaunit [sync] (noble-proposed) [24.0.0-2build1.1] | 18:50 | |
| -queuebot:#ubuntu-release- Unapproved: accepted libflorist [sync] (noble-proposed) [2022.0.1~20220616-6~24.04] | 18:56 | |
| -queuebot:#ubuntu-release- Unapproved: accepted libgnatcoll [sync] (noble-proposed) [24.1.20230921-4build2.1] | 18:58 | |
| -queuebot:#ubuntu-release- Unapproved: accepted libgtkada [sync] (noble-proposed) [24.0.0-3~24.04] | 19:02 | |
| -queuebot:#ubuntu-release- Unapproved: accepted libncursesada [sync] (noble-proposed) [6.3.20211021-11build1.1] | 19:03 | |
| -queuebot:#ubuntu-release- Unapproved: accepted libtemplates-parser [sync] (noble-proposed) [24.0.0-2build1.1] | 19:08 | |
| -queuebot:#ubuntu-release- Unapproved: accepted libtexttools [sync] (noble-proposed) [2.1.0-28build1.1] | 19:09 | |
| -queuebot:#ubuntu-release- Unapproved: accepted libxmlezout [sync] (noble-proposed) [1.06.2-14build1.1] | 19:10 | |
| -queuebot:#ubuntu-release- Unapproved: accepted phcpack [sync] (noble-proposed) [2.4.90+dfsg-1build1.1] | 19:11 | |
| -queuebot:#ubuntu-release- Unapproved: accepted alire [sync] (noble-proposed) [1.2.1-1.1build1.1] | 19:13 | |
| -queuebot:#ubuntu-release- Unapproved: accepted anet [sync] (noble-proposed) [0.5.0-3build1.1] | 19:16 | |
| -queuebot:#ubuntu-release- Unapproved: accepted dbusada [sync] (noble-proposed) [0.6.2-6build1.1] | 19:19 | |
| -queuebot:#ubuntu-release- Unapproved: accepted libalog [sync] (noble-proposed) [0.6.2-5build1.1] | 19:21 | |
| vorlon | bdmurray: do you know why distro-info-data enforces that Ubuntu EOL dates can only fall on Tue-Thu? I do not know / have not discussed such a rule | 19:24 |
| -queuebot:#ubuntu-release- Unapproved: accepted libgnatcoll-bindings [sync] (noble-proposed) [24.0.0-2build2.1] | 19:25 | |
| -queuebot:#ubuntu-release- Unapproved: accepted liblog4ada [sync] (noble-proposed) [1.3.1.b6dafb49-13build2.1] | 19:26 | |
| -queuebot:#ubuntu-release- Unapproved: accepted pcscada [sync] (noble-proposed) [0.7.7-6build1.1] | 19:28 | |
| -queuebot:#ubuntu-release- Unapproved: accepted libgnatcoll-db [sync] (noble-proposed) [23.0.0-6build1.1] | 19:29 | |
| -queuebot:#ubuntu-release- Unapproved: systemd (oracular-proposed/main) [256.5-2ubuntu3 => 256.5-2ubuntu3.1] (core, i386-whitelist) | 20:29 | |
| -queuebot:#ubuntu-release- Unapproved: xfsprogs (noble-proposed/main) [6.6.0-1ubuntu2 => 6.6.0-1ubuntu2.1] (core, i386-whitelist) | 20:46 | |
| -queuebot:#ubuntu-release- New: accepted oem-somerville-magmar-meta [amd64] (jammy-proposed) [22.04~ubuntu1] | 22:36 | |
| tumbleweed | vorlon: IIRC it was originally weekdays and got limited to mid-week later | 23:04 |
| tumbleweed | (originally = when we introduced that check) | 23:04 |
| vorlon | tumbleweed: ok but why was it limited? | 23:06 |
| * tumbleweed can't find anything canonical | 23:14 | |
| tumbleweed | closest is https://bugs.launchpad.net/ubuntu/+source/distro-info-data/+bug/1939457 | 23:14 |
| -ubottu:#ubuntu-release- Launchpad bug 1939457 in distro-info-data (Ubuntu Hirsute) "Update EoL dates for 16.04 LTS and 21.04 so they are not on weekends" [Low, Fix Released] | 23:14 | |
| tumbleweed | but that's really just an SRU | 23:15 |
| tumbleweed | I seem to recall that before we had those checks, the date would change once the peolpe who are responsible for closing out releases saw what the final date was | 23:17 |
| vorlon | well I am sometimes among those people, and I don't remember this ever being discussed within the release team, which is why I'm trying to get clarification ;) because as far as I'm concerned, the EOL date should be driven by the Security Team, not by the Release Team whose only responsibility to be completed on the EOL date itself is to send an email :) | 23:19 |
| tumbleweed | yes, I think it was a security team request | 23:21 |
| vorlon | so if it can be confirmed that this is what the Security Team wants, I'm fine with it | 23:30 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!