17:00:11 #startmeeting fpc 17:00:11 Meeting started Thu Dec 2 17:00:11 2021 UTC. 17:00:11 This meeting is logged and archived in a public location. 17:00:11 The chair is geppetto. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 17:00:11 Useful Commands: #action #agreed #halp #info #idea #link #topic. 17:00:11 The meeting name has been set to 'fpc' 17:00:11 #meetingname fpc 17:00:11 The meeting name has been set to 'fpc' 17:00:11 #topic Roll Call 17:00:17 * GwynCieslasheher here 17:00:28 #chair GwynCieslasheher 17:00:28 Current chairs: GwynCieslasheher geppetto 17:01:46 Hey 17:01:52 #chair tibbs 17:01:52 Current chairs: GwynCieslasheher geppetto tibbs 17:02:04 Didn't realize we were on for today. 17:02:40 I don't think it's 100% even now :) 17:04:43 And imediately after I typed that, my X server died. 17:05:43 Nice 17:09:26 There has been a bit of new activity but I haven't had a time to look over it. 17:09:50 #topic Open Floor 17:09:58 Yeh, the only real thing I had was: https://pagure.io/packaging-committee/issue/1132 17:10:12 Which confused me at least as much as it confused tibbs 17:10:26 * GwynCieslasheher reads 17:11:01 I think what they want is something that can be read and used by automation. 17:11:44 I think I grok what they want but it seems more complex than what we currently do with scripts. 17:11:54 I wouldn't really object to actually recommending that a shell script be used if possible, and that it have a fixed name. 17:12:08 That's a good idea. 17:13:03 But I don't know how far you go with it. Because they still wouldn't know how to get the unmodified source. 17:13:46 Mandate a comment in the script with a URL? 17:13:59 Yeah, that's all I can think of. 17:14:13 Unmodified source: https://whatever.tgz 17:14:28 I'll add those thoughts to the ticket 17:14:50 Yeh, I'm +1 on comments for people … but comments for automation seem like a bad idea 17:15:15 Sadly you can't reference it with a Source: tag. 17:15:19 NoSource, maybe? 17:15:37 Do those still exist? 17:16:36 Seems to, but that may be a bit out there. 17:18:07 I'd want to think long and hard about that, so we don't push packagers from something was simple as a bicycle onto what might turn out to be an electrified penny farthing with a spoiler but no tires. 17:18:38 So to speak. 17:19:03 Right, that's the problem. Making it suitable for automation is great, but that might just add complexity and push it onto the packager. 17:19:11 yeh, I think I'm -1 on using nosource for things that have source generated 17:19:43 like if they want automation things I'd heavily prefer them to speak to rpm people about adding a new tag 17:20:01 Thinking further, if we had that, the build process would require network access beyond SCM and lookaside. Which changes tons of assumptions. 17:20:08 and I realize that might be a black hole of nothing … but I still can't think of a better solution 17:20:23 The problem with nosource is that if you leave it out then you end up with stuff in the srpm that shouldn't be there. 17:20:37 Bingo. Or requiring net access. 17:20:51 The first is a hard no, the second something of a PITA. 17:20:56 Because it you don't do NoSource: https://whatever.tgz, you have a regular Source: URL and then say "don't put it in the SRPM" with NoSource: 2 or whatever. 17:21:11 Yeh, I think maven kind of works like that for java things? 17:21:17 I don't see how any of this would require network access, though. 17:21:34 You have to run this automation before you can even generate the SRPM. 17:21:36 So it's possible … just a giant PITA 17:22:07 Ah, so the packager runs the automation and the products go in lookaside just like now. 17:22:16 Yeah. 17:22:20 Ick 17:24:57 hey o/ sorry for being late, I didn't get IRC notifications for some reason, and I didn't know there'd be a meeting today 17:24:59 I mean, it would be simpler for everyone (except the person who has to initially implement the thing) if there was one script that took a version, downloaded the unshippable tarball and generated the shippable one. 17:25:51 That's what I have done in the past, because it makes maintenance super easy. But mandating that for all packages that need to do this seems to be too much, even if there aren't that many. 17:27:34 RIght. And it can take the new version number as an argument. 17:27:49 yeh, certainly sometimes you can't easily get any version … only the latest etc. 17:28:01 #chair decathorpe 17:28:01 Current chairs: GwynCieslasheher decathorpe geppetto tibbs 17:28:39 I just think that doing it in a way that can be completely automated gets far more complicated than anyone would really want. 17:28:47 But, again, I'm happy to +1 almost any best practice on comments … but much less so on anything that should be read by automation 17:28:59 Agreed 17:29:09 So depending on what they want is going to depend on how hard they need to work to convince me 17:29:19 But maybe the people who would want this would have better ideas. It just feels to me like it wasn't really thought through all the way. 17:29:49 ¯\_(ツ)_/¯ 17:30:17 Anyway … we've been here 30 mins. … so I feel like I shoud give everyone 30 mins. back 17:30:39 I can use that to finish typing this comment in the ticket. 17:30:42 I should find time to do an email schedule etc. for next week, so hopefully more people will realize they'll be a meeting :) 17:30:48 * geppetto nods 17:32:01 geppetto: I realize sending out the email is more work, but it gives people more than 5 minutes of prior notice ;) 17:32:34 I know, I've just been busy and let it slide 17:33:02 We're all busy; it's no big deal. 17:33:15 I have Element set to notify on #meetingname fpc 17:33:16 100% my fault, but should be fixed for next week. 17:34:08 You know, I wonder if fedpkg could somehow become responsible for generating safe versions of unshippable tarballs. 17:34:20 lol 17:34:38 That would be a logical spot for it but I'm not volunteering to write that code. 17:35:14 Maybe rephrase as asking the people who want this to leverage fedpkg. 17:35:45 If fedpkg requires some kind of metadata or helper scripts or whatever, it would be outside of the specfile and Not Our Problem (TM). 17:35:48 If they can get something into fedpkg I'm happy with it … if only because it's not my problem ;) 17:36:04 * geppetto hi5 tibbs 17:36:06 We'd merely document what fedpkg needs and be happy. 17:36:24 And on that note... 17:36:27 #endmeeting