copr-devel July 2013

copr-devel@lists.fedorahosted.org

3 participants
5 discussions

Copr URLs
by Pierre-Yves Chibon 13 Sep '13

13 Sep '13

Hi all, Something, I have been discussing with Tomas last week but not with Slavek or the list, is the URLs we have in copr. For example: front page: / detail of a copr: /coprs/detail/toshio/packagedb/ copr's permissions: /coprs/detail/toshio/packagedb/permissions/ copr's builds: /coprs/detail/toshio/packagedb/builds/ someone's copr: /coprs/owned/toshio/ I basically would like to change a couple of things. At the moment when I'm looking at toshio's packagedb repos there is no way to (from the url) easily go back to the list of toshio's copr. So I would like to propose: / > home /coprs/ > list all the repos (same as home, atm) /coprs/<user>/ > list someone's copr /coprs/<user>/<repo>/ > the detail of this copr /coprs/<user>/<repo>/{permissions,builds,...}/ > same as now the permissions, builds or other page for this repo (the repo file for yum could end up here as /coprs/<user>/<repo>/repo/ ) It's something I have in mind but would like to discuss before doing (unless someone beats me to it). So, what do you think? Pierre

4 9

Network setup of builders
by Miroslav Suchý 02 Jul '13

02 Jul '13

Seth, is is possible to set up builders that the they will have very limited network connections? Probably just to copr-be or copr-fe? I'm asking because currently you can do nearly everything on builder. For example I made evil.spec, which have %prep wget http://www.googl.com -O index.html cat index.html Which is executed without problem: http://copr-be.cloud.fedoraproject.org/results/msuchy/copr/fedora-18-x86_64… Of course instead wget I can e.g start my own ssh server or botnet. And I will own that machine until our timeout expire. On Koji we do not have such problem because builders are configured to not allow any internet connections. Right now we need internet connection on builders, because they need to download src.rpm. But this can be fixed that user will not provide url to src.rpm, but they will upload it to cloud-fe. This will be save, because we will store and behave to src.rpm just as binary file and only store it in some directory and not parse it. Builder can then pick it up from copr-fe. Either by downloading from some http export or via nfs read only share. Opinions? Mirek

4 10

Restricted vs. allowed content
by Miroslav Suchý 02 Jul '13

02 Jul '13

Was there already some discussion which content will be allowed? Or more precisely: which will not be allowed? -- Miroslav Suchy Red Hat

3 3

opening up and expanding.
by Seth Vidal 02 Jul '13

02 Jul '13

Sgallagh suggested opening up the current functionality of coprs to proven packagers - to discover more bugs and to help us figure out what else is needed. I'd like to suggest two things: 1. open up what we have to provenpackagers as sgallagh suggested 2. setting up a second 'dev' instance so we can test there before rolling over into the more public instance. - Also it will help us verify the setup process. I can easily setup a be and fe dev instances in the private openstack cloud we have setup. It would also let us refresh those instances and be sure we're still functional. -sv

3 7

[copr] master: lightweight is the word and buildsystem has more meaning than 'koji'. (910aebb)
by Seth Vidal 01 Jul '13

01 Jul '13

Repository : http://git.fedorahosted.org/cgit/copr.git On branch : master >--------------------------------------------------------------- commit 910aebb1228c72049d4db77e337bd9c02010518b Author: Seth Vidal <skvidal(a)fedoraproject.org> Date: Mon Jul 1 22:52:34 2013 -0400 lightweight is the word and buildsystem has more meaning than 'koji'. >--------------------------------------------------------------- copr.spec | 10 +++++----- 1 files changed, 5 insertions(+), 5 deletions(-) diff --git a/copr.spec b/copr.spec index 3d2e009..86ba7c6 100644 --- a/copr.spec +++ b/copr.spec @@ -19,12 +19,12 @@ BuildRequires: python-argparse %endif %description -COPR is lightway Koji. It allows you to create new project in WebUI, and +COPR is lightweight buildsystem. It allows you to create new project in WebUI, and submit new builds and COPR will create yum repository from latest builds. %package backend Summary: Backend for COPR -Requires: ansible >= 0.9 +Requires: ansible >= 1.2 Requires: lighttpd Requires: euca2ools Requires: rsync @@ -36,7 +36,7 @@ Requires: python-bunch Requires: python-requests %description backend -COPR is lightway Koji. It allows you to create new project in WebUI, and +COPR is lightweight buildsystem. It allows you to create new project in WebUI, and submit new builds and COPR will create yum repository from latest builds. This package contains backend. @@ -61,7 +61,7 @@ Requires: pytest Requires: python-flexmock %description frontend -COPR is lightway Koji. It allows you to create new project in WebUI, and +COPR is lightweight buildsystem. It allows you to create new project in WebUI, and submit new builds and COPR will create yum repository from latests builds. This package contains frontend. @@ -74,7 +74,7 @@ Requires: python-argparse %endif %description cli -COPR is lightway Koji. It allows you to create new project in WebUI, and +COPR is lightweight buildsystem. It allows you to create new project in WebUI, and submit new builds and COPR will create yum repository from latests builds. This package contains command line interface.

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

copr-devel July 2013