!NLyoXfybQSfvkVRUFB:matrix.org

pulp-rpm

30 Members
4 Servers

Load older messages


SenderMessageTime
28 Mar 2024
@ggainey:matrix.orgggaineywe thought you might still be having Internet Issues 15:34:46
@ipanova:matrix.orgipanovayeah i figured, i joined half past15:57:11
4 Apr 2024
@dkliban:matrix.orgdkliban joined the room.13:18:27
@dralley:matrix.orgdralleyI canceled today's meeting, there's conflicts13:34:37
@dralley:matrix.orgdralleycan reschedule it if someone has something to bring up13:34:48
@ggainey:matrix.orgggaineyI'm good, thanks Daniel13:55:30
10 Apr 2024
@bmbouter:matrix.orgbmbouter joined the room.13:17:55
11 Apr 2024
@dralley:matrix.orgdralley ipanova: do you think we could get COPR folks to come to the RPM meeting today 13:50:44
@dralley:matrix.orgdralleyor set up a new timeslot with them?13:51:07
@dralley:matrix.orgdralley ggainey: Pedro Pessoa 13:51:20
@ipanova:matrix.orgipanovathat probably be too short notice so i would reccomend setting up new time with them13:53:17
@dralley:matrix.orgdralleyok. since there's an overlap with some career development sessions that aren't going to be recorded, I think I will try to move the meeting to tomorrow during an earlier timeslot, and I'll invite them14:52:29
@pedro-brochado:matrix.orgPedro PessoaCan we accept this? https://github.com/pulp/pulp_rpm/issues/349518:39:07
@ggainey:matrix.orgggaineyjust did some digging - yes. Looks like we're setting it on sync here https://github.com/pulp/pulp_rpm/blob/main/pulp_rpm/app/modulemd.py#L150 , but the upload-path never does18:59:14
@ggainey:matrix.orgggaineywill def need a migration to fix any snippets currently missing one18:59:40
@ggainey:matrix.orgggaineysigh, fun18:59:43
12 Apr 2024
@dralley:matrix.orgdralleyyup15:04:57
16 Apr 2024
@mgu:matrix.orgMagnus Gustavsson joined the room.10:03:06
@maggu04:liu.seMagnus Gustavsson joined the room.12:22:05
17 Apr 2024
@dralley:matrix.orgdralley Pedro Pessoa: I was thinking that we should probably backport https://github.com/pulp/pulp_rpm/pull/3503 to at least the latest stable release, but I think the fact that the PR is 3 commits (even though it got squashed on merge) might break our backport automation (which only supports one commit PR last I checked) 15:36:08
@dralley:matrix.orgdralley we could just git cherrypick -x that commit manually though 15:36:29
@dralley:matrix.orgdralleyactually we would have to do it manually anyway, because we can't backport the migration15:37:08
@dralley:matrix.orgdralleyonly fix the uploads15:37:22
@dralley:matrix.orgdralley * only fix future uploads15:37:41
@pedro-brochado:matrix.orgPedro Pessoa So I need to add one commit with test+fix only for the backport PRs right? Are these the backport target branches? 16:26:38
@dralley:matrix.orgdralleyyou can backport to only the latest one, I think that would be fine17:46:09
@dralley:matrix.orgdralley3.23 too if you want17:46:27
@dralley:matrix.orgdralleyI wouldn't bother with the rest17:46:38
18 Apr 2024
@dralley:matrix.orgdralley ggainey: mtg? 15:03:58
@pedro-brochado:matrix.orgPedro Pessoa Hey x9c4 , just want to let you know that after RPM last meeting with COPR and our today's meeting, we have concluded that we dont need to use the proposed PGP models yet. One of the main benefits of using those would be to better track package signatures for handling post-upload signing/re-signing, but tracking that would introduce too much complexity without enough benefits, as the post-upload signing is not the main workflow for COPR (they don't need to do that so often as they do uploads). 17:13:17

There are no newer messages yet.


Back to Room ListRoom Version: 6