15:01:39 #startmeeting Env and Stacks (2014-04-22) 15:01:39 Meeting started Tue Apr 22 15:01:39 2014 UTC. The chair is mmaslano. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:01:39 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:01:43 #meetingname env-and-stacks 15:01:43 The meeting name has been set to 'env-and-stacks' 15:01:48 #chair abadger1999 pkovar tjanez samkottler bkabrda drieden hhorak juhp mmaslano 15:01:48 Current chairs: abadger1999 bkabrda drieden hhorak juhp mmaslano pkovar samkottler tjanez 15:01:54 Hello guys! 15:01:57 hi, is anybody here today? 15:01:57 hi! 15:02:00 ah great 15:02:02 Hello! 15:02:21 I'm sorry for very late meeting invitation. 15:02:49 I don't have much for agenda, only if you want to discuss responses on mailing lists 15:03:19 #topic init process 15:05:32 #topic Allow to delete builds/coprs from playground? 15:05:56 #url https://lists.fedoraproject.org/pipermail/env-and-stacks/2014-April/000381.html 15:06:24 hhorak: how did you understand Richard's reply about providing of srpm? 15:06:32 hhorak: I'm not so sure it's not needed 15:07:06 random observation from the audience: it would be nice for the user to have an easy way to exclude a copr from their view of the playground (via dnf plugin?) without escalating for complete removal 15:07:41 mmaslano: I undertand that we can delete the srpm but only at the same time as other binary rpm files. 15:08:39 #info feature request - dnf plugin should be able to block view of some copr repositories in Playground 15:08:45 hhorak: then we might have a problem 15:09:11 randomuser: that seems like the same functionality as --exclude is for, worth trying if something like --exclude=user/copr* could work here, or if it needs to be implemented in the plugin 15:09:49 mmaslano: why? if we delete a copr, we delete everything, srpm and rpms 15:10:32 hhorak, sure, that works, as long as it can be persistent. Just wanted to get the idea out there :) 15:10:37 hhorak: because we don't control copr srpm, they are on user url, and he can remove them when he wish 15:10:59 randomuser: no problem, I'll forward it to msuchy ;-) 15:12:00 randomuser: I don't believe dnf will be inconsistent with yum in this regard and I remember it was possible in yum to use exclude in yum.conf, so it should work persistently as well 15:12:47 great, thanks for being patient with my interruption :) 15:14:32 mmaslano: copr builds its own srpm (again), which is the package we should care. Or I might say it not correctly, I think it is OK to remove rpm and still provide srpm.. what would be problem is if we provided rpms and not srpm 15:16:57 hhorak: ah you are right, it's there 15:17:11 fine so back to deleting coprs :) 15:18:56 I guess the original question was if we can remove copr content, when it's already installed on users machine 15:19:41 mmaslano: exactly, because we may want to reproduce users' issues 15:20:20 hhorak: if it's in Playground, then I would remove it after end of Fedora X 15:20:34 I would remove it immediately if there were some legal issue 15:22:31 that makes sense as far as we (as playground maintainers) are those who remove them. But there is still the owner who can remove all builds at any time -- that was what I was worried. 15:22:44 um 15:23:27 I would close it today because I don't have any new data from msuch (copr devel) 15:23:57 I agree, we should discuss this topic with him 15:24:05 fine ) 15:24:08 #endmeeting