16:31:17 #startmeeting RELENG (2015-02-09) 16:31:17 Meeting started Mon Feb 9 16:31:17 2015 UTC. The chair is dgilmore. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:31:17 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:31:29 #meetingname releng 16:31:29 The meeting name has been set to 'releng' 16:31:29 #chair dgilmore nirik tyll sharkcz bochecha masta pbrobinson 16:31:29 Current chairs: bochecha dgilmore masta nirik pbrobinson sharkcz tyll 16:31:30 #topic init process 16:31:51 who is here? 16:31:56 * pbrobinson is here 16:32:10 hi 16:32:10 I'm here 16:32:35 hi janeznemanic 16:32:55 * masta is here 16:33:41 lets get started 16:33:42 #topic Secondary Architectures updates 16:33:43 #topic Secondary Architectures update - ppc 16:33:51 pbrobinson: how is ppc? 16:34:30 we're building, the secondary team is fixing up some rawhide build issues 16:34:48 stable releases are fine, had updates pushed late last week 16:35:51 ready for branching tomorroew? 16:35:54 tomorrow? 16:36:14 we should be, package state not a major issue there 16:36:20 okay 16:36:35 #topic Secondary Architectures update - s390 16:36:55 sharkcz is on holidays but i believe things are okay 16:37:12 #topic Secondary Architectures update - arm 16:37:15 should be about the same as ppc 16:37:41 we're looking pretty good 16:37:52 there's been a few breakages of late due to features landing like ghc 16:37:59 and likely some issues with gcc5 16:38:10 but other than that it's pretty close to mainline 16:38:46 :) okay 16:39:22 #topic #6016 Use fedpkg-minimal in Fedora buildroots 16:39:38 https://fedorahosted.org/rel-eng/ticket/6016 16:39:54 the package is approved, I'm not sure pbabinca had time to build it already or not 16:40:18 once it is built we can get overrides and make the necessary changes 16:40:23 seems to be build in rawhide 16:40:30 then fedora-packager can be removed from epel5 16:40:40 https://koji.fedoraproject.org/koji/buildinfo?buildID=609961 16:41:25 awesome 16:41:44 #topic #5959 Enable keep-alive connections for koji (primary and secondaries) 16:41:56 https://fedorahosted.org/rel-eng/ticket/5959 16:42:06 we've not seen issues on arm.koji when I enabled it there 16:42:23 seems we should enable it everywhere 16:42:36 I can look at what's needed in ansible and send a patch to infra list 16:42:46 cheers 16:43:08 #action pbrobinson to send patch to infra list enabling keepalive 16:43:39 #topic #6023 allow Peter Robinson to restart sigul bridges 16:43:48 https://fedorahosted.org/rel-eng/ticket/6023 16:44:02 as of last week sysadmin-main members can restart the bridges 16:44:10 I think that solves the issues raised 16:44:16 and this ticket can be closed 16:45:31 #topic #6027 secondary arch old mash trees cleanup 16:45:47 https://fedorahosted.org/rel-eng/ticket/6027 16:46:15 that's been on my todo list as well 16:46:21 this is something that needs done for primary as well 16:46:22 Sorry, I'd forgot about this 16:46:47 yea, I was going to write the script, it fell through the craps 16:46:50 cracks even! 16:46:53 it happens 16:47:42 maybe bconoboy|afk can help you 16:48:52 qa has recently been doing rawhide tests 16:48:59 they point at the mash location 16:49:36 given that rawhide has been failing quite a lot we should make sure that we keep the last full tree 16:49:48 and bochecha can maybe help not bconoboy|afk 16:50:03 sure 16:50:16 ideally we should have a couple of weeks worth of composes 16:51:36 there is also updates tress to clean up 16:51:44 along with branched and rawhide 16:52:06 #topic #6096 add individual email addressses to Fedoras GPG keys 16:52:20 https://fedorahosted.org/rel-eng/ticket/6096 16:52:51 we can not retroactively change anything 16:54:17 but as we will make f23 keys tomorrow we should make a change there if we plan to 16:54:56 We could use something like RPM-GPG-KEY-fedora-22-primary@fedoraproject.org or fedora-22-primary@fedoraproject.org 16:55:03 was in the proposal 16:55:44 I do not know that I like either but I also do not know of anything better 16:55:44 the later looks a little cleaner 16:56:09 fedora-23-primary-gpg@fedoraproject.org maybe? 16:56:20 the later is cleaner 16:56:33 i just wonder if people would be confused 16:58:34 #action will make a choice when making the keys 16:58:40 #undo 16:58:40 Removing item from minutes: ACTION by dgilmore at 16:58:34 : will make a choice when making the keys 16:58:51 #action dgilmore will make a choice when making the keys 16:59:11 #topic #6100 create bsd-style checksum files for CHECKSUM files 16:59:22 https://fedorahosted.org/rel-eng/ticket/6100 17:00:02 I am not opposed to this but we would need to dig into the different places where CHECKSUM's are made and change the command flags 17:01:10 there may be scripts that do other checking that could break 17:01:20 but I am not sure what they would be 17:01:35 if they use xxxsum -c then they should work just fine 17:01:41 right 17:01:46 if they try to parse the stuff on their own, well... 17:01:53 but if they do thier own parsing they may break 17:02:05 so lets attempt it 17:02:12 see how it goes 17:02:44 some of the places we make CHECKSUM's are in the releng git repo 17:02:44 and some is in pungi 17:03:13 #action dgilmore to make this happen 17:03:21 #topic open floor 17:03:33 anyone have anything they want to discuss? 17:03:44 we've made some progress on the move away from md5 for the lookaside cache 17:04:00 one point we need to decide, is the format of the sources file 17:04:32 we could use the BSD style, like in the previous topic 17:04:53 I would be okay with that 17:05:00 one problem though is that a sources file might end up containing both md5 (an existing archive) and sha512 (a newly uploaded archive) 17:05:19 which brzks verification with md5sum -c or sha512sum -c 17:05:35 we were wondering with pavol if we shouldn't instead have the hashtype in the file name 17:05:39 like sources-sha512 17:05:40 or something 17:06:11 I do not like the idea of multiple sources files 17:07:18 me neither, it means painful merging of the files 17:07:26 (e.g if a tarball is present in both, which one do you use?) 17:07:39 or code in fedpkg to update all files when one is updated 17:07:52 right, moving from md5 to sha512 as well 17:08:00 yep 17:11:31 so when we update a file we generate new hashes for the other files already tehre 17:12:41 I would prefer putting all in one 'sources' file, with the BSD-style lines, and not worry about people getting warnings for the sha512 lines when they do « md5sum -c sources », or warnings about md5 lines when they do « sha512sum -c sources » 17:13:34 an option I guess 17:13:50 is it usual that the sources file is updated and not replaced? 17:14:10 sometimes 17:14:27 there is a bunch of packages with multiple tarballs 17:15:01 including packages with multiple tarballs because maintainers never replace the old ones 17:15:13 we are mostly concerned with some corner cases 17:15:18 (so fedpkg ends up downloading them all, even though only the last one is needed) 17:17:42 maybe we should write some docs/blogposts about ways to manage the sources in your package 17:18:50 just a useful reminder on the options and what they do 17:22:11 anyways I think using a standard tool and having the option to verify files using the sha tools would be good 17:24:15 anything else? 17:24:33 branching is tomorrow, right? 17:24:42 yes 17:24:56 tomorrow is branching 17:25:13 which means new keys, new tags/targets, enabling branched 17:25:22 getting ready for a TC 17:25:43 quicyte a few little things that need doing 17:25:47 imho it is good to replace old hashes when files are updated otherwise it will nrver happen 17:26:36 tyll, sure, if maintainer runs new-sources with a few ones, one of which is an existing tarball, that would replace the md5 hash by the sha512 one 17:27:02 tyll, if they just add a new source, that wouldn't do anything to the existing sources, just append the new line 17:27:06 or do you mean it should? 17:28:07 (which means it should first download the old tarball, as it might not be present if the maintainer is uploading an additional one) 17:28:21 bochecha: yes, or maybe just abort if there are different hashes and ask the maintainer to fix it 17:28:48 it depends on how common the problem is 17:29:24 if it happens rarely it is imho ok to ask to fix it manually 17:29:41 well, it would be fairly common, at least at first, as it would happen for every use of « fedpkg upload » after the migration for each package, until the first time someone uses « fedpkg new-sources » for each package 17:30:30 I alwys use new-sources 17:30:47 I generally use new-sources 17:30:54 maybe we should remove the upload command :-° 17:30:57 but sometimes you need to add a tarball 17:31:03 and upload is there for that 17:31:25 I do not thing removing upload is a viable option 17:33:55 only disallowing it if there is a md5 hash might be a good compromise 17:34:31 tyll, true, forcing a new-sources in such a case, to get all archives with sha512 in sources 17:34:54 that's actually a pretty good idea, it completely removes the worry about mixing hashes in a single file :) 17:35:09 I'll talk to pbabinca bout this tomorrow, and rework my patches 17:36:20 at some point we also should enforce that all sources files use sha512, maybe for f23 or so 17:37:09 yeah, I already have a patch that eventually prevents uploading of md5sum when we get there, and we can script a mass-update of the sources file for the onew that never got updated as part of regular maintenance ;) 17:43:13 bochecha: only time we could script updating it is when doinga mass rebuild 17:43:19 but I do not want to do it then 17:43:26 because it will slow it down 17:44:07 not sure we really want fedpkg build forcing it 17:48:16 why does it need a rebuild? 17:48:59 tyll: the sources files updates? 17:49:10 dgilmore: yes 17:49:33 tyll: I was saying the only way to easily force the update of all sources files is at mass rebuild time 17:49:48 but downloading all the tarvballs and computing the sha512 will slow it done 17:50:25 the only thing that could force people update it is to have fedpkg build force it 17:50:32 since you can use git to commit 17:50:39 we can get the sha512 sums from pkgs directly 17:50:43 and the only time you use fedpkg is to build 17:51:04 we can not easily do so 17:52:11 tyll: http://pkgs.fedoraproject.org/lookaside/pkgs/fedora-release/fedora-release-22.tar.bz2/ 17:52:35 how would we know which is the sha512 that matches the tarball we are using? 17:52:59 probably for most we could go and look and get it 17:53:07 but there are cases we can not 17:53:13 dgilmore: i meant computing it there 17:53:29 tyll: it still takes a lot fo time 17:53:53 tyll, we're already going to do that, all the tarballs on the lookaside cache will be present under both their md5sum and sha512sum 17:54:25 i can do it, when this is ready 17:54:43 or fail trying 17:55:48 we could maybe do it when we convert but it may catch people by surprise and cause conflicts 17:56:13 lets discusss this later in #fedora-releng 17:56:18 * dgilmore is getting hungry 17:56:20 we can do it after a while 17:56:28 ok 17:57:21 there is probably a few ways to do it 17:57:26 lets look at the options 17:57:41 if no one has anything else I will wrap up the meeting 17:58:27 #endmeeting