15:05:44 #startmeeting Fedora Packaging Committee 15:05:44 Meeting started Wed Apr 27 15:05:44 2011 UTC. The chair is spot. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:05:44 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:05:49 #meetingname fpc 15:05:49 The meeting name has been set to 'fpc' 15:06:13 #topic roll call 15:06:20 * limburgher here 15:06:25 Howdy. 15:06:40 here 15:06:46 * geppetto is here 15:07:16 * spot suspects abadger1999 might still be on vacation 15:07:27 Hey, 15:07:29 * abadger1999 here 15:07:33 no, he's back! 15:07:36 was catching up on email. 15:07:50 rdieter, SmootherFrOgZ: ping 15:09:53 okay, we have 6 15:09:55 lets go ahead 15:10:07 #topic Systemd 15:10:13 Pikachu_2015 15:10:23 notting has been commenting on ticket #31 15:10:56 he seems very strongly in the "don't package sysv initscripts at all" camp 15:11:31 as opposed to putting them in subpackages (which is what we already approved in the base guidelines) 15:11:51 I have no problem either way, honestly. I'm not sure what benefit they have now. 15:11:58 So -- if the direction we're taking is that the sysvinit to systemd transition is wiping the slate clean, I can see not telling people to run the state-saving script. 15:12:37 But telling people they can't package the scriptlets at all doesn't seem right (and I don't think he's saying that). 15:12:51 But "wiping the slate clean" can mean breaking people's machines during the transition. 15:12:57 15:13:00 oh hi, here now 15:13:02 So certainly not during a release. 15:13:03 I think that's already the case. 15:13:33 Yeah -- ideally we'd convert every sysv script to systemd during one release cycle. 15:13:49 abadger1999: 15:13:57 Sure, F16 seems a good time. Some folks are trying to do that before F15. 15:14:11 Witness the volume of bugs filed on it. 15:14:40 bochecha has been testing the migration scriptlets and reported that everything worked 15:14:58 But sgallagh reported that they were completely broken. 15:15:15 and some want to migrate asap due to pain around sysv emulation (bugs, need for added deps, yada yada) 15:15:16 And that Lennart told him to ignore what we had written entirely. 15:15:41 that's nice 15:15:53 15:16:13 I'm somewhat at a loss. 15:16:41 Why are we here? Gridlock! 15:17:01 I only waded into that because my F15 machines broke when sssd migrated. 15:17:27 Well, I don't mind saying "no sysv scripts" and "moving to systemd resets what's running" … which should help the migration 15:17:34 tibbs|h: Why did it break? 15:17:56 I had to enable the service manually. 15:18:07 I mean, no huge deal, but.... 15:18:22 * geppetto nods … so it wasn't broken, just defaulted badck to turned off 15:18:48 Well, the machine was broken, becuase it doesn't do much without a user database. 15:18:54 * geppetto shrugs … I guess I can live … assuming most of the services are converted at once 15:19:10 The whole point of our work here is to prevent that. 15:19:22 Otherwise we can ignore any concept of migration altogether. 15:19:55 hi folks 15:19:59 sorry for running late 15:20:19 but I'm on afternoon shift at work 15:20:35 also my connection is flaky, so forgive the drop-outs 15:20:38 Rathann: np. We're talking about: https://fedorahosted.org/fpc/ticket/31 15:20:47 tibbs|h: Well, if the set of running services being reset to default is the only problem … I'm pretty sure I'd call that success of migration to systemd :) 15:21:07 tibbs|h: But, as I said, I'd want it to be a one time thing … so everyone converts for F16 or something 15:21:21 So it's easly release-noteable in Bold, with blink tags. 15:21:27 yeh 15:22:24 Personally I'd prefer a much better/smoother migration … but unless anyone knows how to do "invasion of the body snatchers" on lennert, then I'll settle for this 15:22:34 i tell you, this systemd stuff just makes me exhausted 15:22:36 How long do I have? 15:23:15 maybe it's just not worth blocking on migration (for now, at least). ? 15:23:29 Folks have already put significant effort into migration. Some folks say it works. 15:23:33 rdieter: I think we've already approved the non-migratin case. 15:23:34 We could ask FESCo for guidance on whether they want sysv scripts to be packaged and if they want settings to be saved. 15:23:40 no. 15:23:45 I only have one report that it doesn't work, but that comes with no details at all. 15:23:47 Well... 15:23:51 * abadger1999 ponders 15:25:27 spot: There's multiple issues if we ask that... some of them may be FESCo material some may not. Many of them seem like governance body vs maintainer pergoative issues which are always thorny. 15:26:18 spot: The main one would be "Can we have alternate versions of core system services (examples: init systems, X Windows, cron,)" 15:27:38 I suppose we could ask FESCo but I don't know that it would lead anywhere good anywhere fast. 15:28:13 the answer(s) may simplify or complicate our lives (but I'd hope the former) 15:28:32 The thing is I think we've already answered that question long ago. 15:28:46 The answer is yes, if a maintainer is there. 15:29:34 But the out-of-box "support" in particular packages may not be there depending on how we've implemented them. 15:29:47 Bottom line is that we're certainly not going to require continued packaging of sysv scripts. 15:29:55 So anyone who wants that has their own uphill battle. 15:30:09 okay, so if we're operating on that assumption 15:30:11 Including simply maintaining their own packages containing such scripts. 15:30:21 lets use scriptlets that assume the sysv initscripts are no longer being packaged 15:30:43 that fact should simplify the scriptlets 15:31:04 How is that different from what we already have, really? 15:31:43 abadger1999: well, we have scriptlets for the subpackage containing the sysvinit script 15:32:07 notting pointed out concerns with those scriptlets specifically 15:32:08 spot: That could be moved out of the systemd guideline page but it's still good to exist. 15:32:30 spot: because we do allow people to package for initng, minit, upstart... 15:32:54 abadger1999: yes, but as pointed out "the out-of-box "support" in particular packages may not be there depending on how we've implemented them" 15:32:55 spot: It's information relevant to those alternative init systems. 15:33:44 * spot is just so tired of looking and arguing about systemd 15:34:31 i think systemd-sysv-convert is useful. i want to keep it. 15:35:27 I agree. 15:35:31 abadger1999: look over nottings comments in that ticket, starting at #56 15:35:32 spot: What data does that script save exactly? 15:35:52 But simply keep it (which wouldn't be our business) or mandate it? 15:35:59 Yeah, I read them this morning... a lot of the things he's arguing about were already decided when we passed the non-migration guidelines. 15:37:29 abadger1999: its python and short, so it should be easy for you to parse 15:37:49 abadger1999: but it basically stores the runlevels that a sysv service is enabled for 15:38:25 spot: Okay... so one thing we could take from notting's critique is to separate that from systemd. 15:38:26 abadger1999: and if prompted later, restores them (across mappings) into systemd 15:38:40 spot: And keep the saving of data separate from the restoring of data. 15:38:54 abadger1999: well, none of the scriptlets actually do the restoring 15:39:05 abadger1999: so we're already separating the saving from the restoring 15:39:13 spot: Since we're only using the saving functionality in the scriptleets.. (Yeah, I think you're seeing the same thing I am). 15:39:47 at this point, my instinct is to do the following: 15:40:11 A) Separate out the scriptlet relating to a subpackage containing sysvinit script and considering it separately 15:40:22 Really, we're just using a tool to save data that a sysadmin might want to use to configure their system.... whether it's restored to systemd or some other init system isn't part of the guidelines. 15:40:37 B) Vote on the rest of the scriptlets as is and address any tangible problems that arise 15:42:29 thoughts on that approach? 15:43:01 Sure. 15:43:02 C) Whether to save the old settings. 15:43:26 I guess that only applies if B) doesn't pass. 15:43:53 * abadger1999 +1's the (A), (B) approach 15:44:01 +1 from me 15:44:17 * rdieter likes 15:44:34 +1 15:45:04 (for the record, we are voting on (A) and (B) together) 15:45:35 That's five, isn't it? 15:45:46 well, if "likes" and "sure" map up to "+1"... 15:45:51 +1 15:45:53 :) 15:45:56 0 15:45:57 thanks. ;) 15:45:59 +1 15:46:09 geppetto: wanna jump in here? 15:46:24 Rathann too, if you're with us 15:46:25 I would dearly love to get at least some guidelines written down. 15:46:30 +1 15:47:13 #action Migration scriptlets, with the subpackage scriptlet removed are approved (+1:6, 0:1, -1:0) 15:47:17 err... I was just voting on whether to vote on A and B separately... I vote +1 to A .. What does B look like? 15:47:39 abadger1999: one sec 15:48:30 B looked like https://fedoraproject.org/wiki/User:Toshio/Systemd_scriptlet_options#Start_over_fresh 15:48:34 looks, rather 15:48:45 without the Subpackage with sysv initscripts section 15:49:06 +1 B 15:49:24 okay. if this information changes anyone's vote, you have a minute or two to speak up 15:50:21 Looks good to me. 15:50:56 okay. the approval stands 15:51:16 we'll discuss the sysv subpackage handling next week. i'll open a separate ticket. 15:51:55 We'll probably want to implement it by updating: https://fedoraproject.org/wiki/Packaging:SysVInitScript 15:52:01 abadger1999: *nod* 15:52:32 Are the regular systemd packaging guidelines written up yet? 15:52:42 tibbs|h: no, but i will write them both up today 15:52:45 OK. 15:52:47 right after this meeting 15:53:10 #topic %find_lang for packages that are dumb - https://fedorahosted.org/fpc/ticket/79 15:53:34 So, i have a package that is dumb, but uses locales. 15:53:47 Oh, you too? 15:53:50 IMHO, if %find_lang doesn't work, you need to %lang tag the files manually. 15:53:54 yes, it is a pain. 15:54:04 I do not see the benefit, honestly. 15:54:32 But if someone can actually figure out how to do that for django, I'd live to see it. 15:54:36 Alternative is to patch the code to find the lang files under /usr/share/locale 15:54:44 its the same benefit of enabling %find_lang, either we care about permitting people to drop locale specific files they don't care about or we don't. 15:54:52 which notting told me was preferable at one point. 15:54:58 I don't remember the rationale though. 15:55:07 Well, there's the question of whether the code actually works with lang files not installed. 15:55:46 tibbs|h: hold your nose. 15:55:48 http://pkgs.fedoraproject.org/gitweb/?p=gambas2.git;a=blob;f=gambas2.spec;h=e20cf683988697403eb851e8cc8b31b83309958a;hb=HEAD 15:56:37 or, perhaps less horrifying: http://pkgs.fedoraproject.org/gitweb/?p=R.git;a=blob;f=R.spec;h=66f6c92c1320a0d2d2bdbe6d188b3fc11adbe508;hb=89573dec366780575a6034a154a03f904305b987 15:57:34 I just don't see the benefit versus the unmaintainability of that approach. 15:57:45 well, its not unmaintainable. 15:57:56 It gets that way the more files you have. 15:58:46 %find_lang isn't very bright. someone could probably either improve it or write a better one for specific cases like django 15:59:02 spot: So … what does marking files %lang do, rpm wise? 15:59:51 django puts the lang files in with the python files for each application. 16:00:11 It allows the sys admin to exclude languages from installation. 16:00:17 geppetto: ^ 16:00:24 abadger1999: yes, but how? 16:00:35 And the django package has over 6000 files. 16:00:38 * spot wonders if modern rpm even supports that 16:00:45 That's an awfully long files list. 16:00:56 tibbs|h: they're not broken out by dir? 16:00:57 find_lang makes it easy to not include the directories you shouldn't include. 16:01:10 abadger1999: --excludedocs is barely usable/supported … I don't see a --excludelang or anything 16:01:22 spot: There's not one directory containing the lang files, no. 16:01:25 And the text at: http://fedoraproject.org/wiki/PackagingGuidelines#Why_do_we_need_to_use_.25find_lang.3F … doesn't say anything about that ability 16:01:32 geppetto: It's a configuration file option, I don't think there's a command line switch 16:01:56 Ahh … %_install_langs … hmm 16:02:32 Honestly I think that find_lang is fine and should be used for packages that put their lang files in the usual place. 16:02:40 spot: repoquery -ql Django |grep locale 16:03:37 But for other packages, it doesn't help at all, so our guideline that mandates its use is broken. 16:03:51 Does it even find lang files outside of /usr/share/locale? 16:04:04 yes 16:04:24 find_lang.sh is a fun mess of regex 16:04:25 Where does it look? Anywhere? 16:04:48 Does it exclude the directories when it looks outside of /usr/share/locale? 16:04:54 Because if it does, then it's completely useless. 16:05:08 You have to go back in with a bunch of %dir whatever in your %files list. 16:05:29 Or you live with huge numbers of "file listed twice" complaints. 16:05:51 find-lang.sh is 12 year old shell script 16:06:03 it predates my involvement at that level 16:06:27 ... or you generate *.lang replacement files from inside of a custom scripts inside of the spec 16:06:32 Anyway, I tried for a couple of days to make a spec that properly %lang-tagged Django and had no file-listed-twice complaints, but it wasn't easy. 16:07:01 racor: I tried, but it gets really difficult because rpm post-processing generates more files (.pyc). 16:07:38 tibbs|h: But your problem is that the "lang" files are actually .py files, yeh? 16:07:41 tibbs|h: my sed-fu is not strong enough to really understand what find-lang.sh is doing 16:07:46 No, they're .mo files. 16:07:52 tibbs|h: Dunno about python, but I used this approach with non-python packages. 16:07:54 Oh, ok 16:08:04 tibbs|h: i suspect there is a way to trick find-lang.sh into working on django 16:08:39 Here's one django app in its installed state: http://fpaste.org/hg72/ 16:09:35 possibly setting TOP_DIR to %{buildroot}%{python_sitelib}/django 16:10:06 Anyway, brainstorming over how to make django work wasn't really the intent of filing that ticket. 16:10:15 The problem is that %find_lang itself does not work. 16:10:27 So our mandating that it be used isn't the right thing to do. 16:10:44 I mean, to satisfy the guideline you could call it but not use the list it produces. 16:11:11 And I'm not sure that we actually have a guideline requiring that things be properly %lang-tagged. 16:11:16 Just that you use %find_lang. 16:11:20 my instinct is to say that the package should either manually %lang tag (either via a script or via human) or fix find_lang to handle the case. 16:11:32 I'd guess that's implied though, by the %find_lang text 16:11:47 I wouldn't guess. 16:11:51 But I'm not a lawyer. 16:11:54 fair enough :) 16:12:06 And fixing find_lang.sh goes back to us not being able to fix rpm. 16:12:22 that's not really true anymore 16:12:26 * spot isn't sure why find_lang doesn't work though 16:12:41 the django structure is pretty sane, just tiered out 16:12:53 and find-lang.sh doesn't have /usr/share/locale hardcoded in it 16:12:57 find_lang doesn't do directories. 16:13:05 i think it does 16:13:13 Because in the /usr/share/locale case, you aren't supposed to own the directories, just the files in them. 16:13:22 oh, i see 16:13:29 you mean directory ownership 16:13:42 # Packages that use %{_datadir}/* to grab all the locale files in one line also grab ownership of the locale directories, which is not permitted. 16:13:47 i don't think i lose sleep over lang tagging directories as opposed to the .mo 16:15:06 I guess I'll experiment more. 16:15:13 tibbs|h: i think if you pass --all-name to find-lang.sh 16:15:16 spot: I think that tibbs|h is saying that the directories won't be owned if %find_lang is used. 16:15:18 it will "just work" 16:15:32 you'll have to manually invoke it as opposed to calling %find_lang 16:16:07 That script is so horrible. 16:16:13 tibbs|h: yes. yes it is. 16:17:00 Anyway, I'll mess with it more. 16:17:03 ok 16:17:10 i don't see any other items for today 16:17:20 (I still havent talked to upstream Perl) 16:17:45 #topic Open Floor 16:17:53 Nothing from me. 16:17:56 ditto 16:19:10 alright then. thanks everyone. 16:19:14 #endmeeting