Re: coprs and personal repos: [Was: Re: Firefox 4 for Fedora 14?]
It looks that copr will come soon. I have a question about it. Could we add some dependencies from other copr repo? Fedora official repo sometimes could not offer the latest one but some packages need them. On Thu, Jul 29, 2010 at 4:14 AM, seth vidal skvi...@fedoraproject.orgwrote: On Wed, 2010-07-28 at 15:10 -0700, Dan Williams wrote: Item 4 is the main point that has been the big ticket item that things like Canonical's PPAs have hit. They also hit the Staples Easy Button about 1000 times. If there's a case to be made that this should be easy to do, then we should add tolling to common/Makefile to: 1) make an srpm check 2) build it as a scratch build in koji check 3) automatically download the built packages check 3.5) Sign the pkgs with your (or someone's) gpg key not-so-check 4) scp them to your fedorapeople account unchecked 5) run createrepo remotely on the fp account createrepo is not fp, on purpose, this could be changed - but it's better to run it locally, if only b/c of whatever arbitrary arguments you may want to add to it - not to mention the memory constraints. 6) generate a yum .repo file for the repo and print out a link to it or something sure. - though we'd be better off generating an rpm which contains the .repo file - so people could 'install' the repositories in the strictest sense. -sv -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel -- Fedora Debian User, former Ubuntu User My Page: http://www.liangsuilong.info Fedora Project Contributor -- Packager Ambassador https://fedoraproject.org/wiki/User:Liangsuilong -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: coprs and personal repos: [Was: Re: Firefox 4 for Fedora 14?]
On Thu, Jul 29, 2010 at 03:21:51PM +0800, Liang Suilong wrote: It looks that copr will come soon. I have a question about it. Could we add some dependencies from other copr repo? Fedora official repo sometimes could not offer the latest one but some packages need them. yes. The idea is that when you create a copr repo you'll specify what other repositories to target. The minimum would likely be Fedora-VER + Fedora-VER-updates. In addition you will be able to specify other copr repositories that target the same Fedora-VER and possibly Fedora-VER-updates-testing (not precisely sure about that last one yet.) -Toshio On Thu, Jul 29, 2010 at 4:14 AM, seth vidal skvi...@fedoraproject.org wrote: On Wed, 2010-07-28 at 15:10 -0700, Dan Williams wrote: Item 4 is the main point that has been the big ticket item that things like Canonical's PPAs have hit. They also hit the Staples Easy Button about 1000 times. If there's a case to be made that this should be easy to do, then we should add tolling to common/Makefile to: 1) make an srpm check 2) build it as a scratch build in koji check 3) automatically download the built packages check 3.5) Sign the pkgs with your (or someone's) gpg key not-so-check 4) scp them to your fedorapeople account unchecked 5) run createrepo remotely on the fp account createrepo is not fp, on purpose, this could be changed - but it's better to run it locally, if only b/c of whatever arbitrary arguments you may want to add to it - not to mention the memory constraints. 6) generate a yum .repo file for the repo and print out a link to it or something sure. - though we'd be better off generating an rpm which contains the .repo file - so people could 'install' the repositories in the strictest sense. -sv -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel -- Fedora Debian User, former Ubuntu User My Page: http://www.liangsuilong.info Fedora Project Contributor -- Packager Ambassador https://fedoraproject.org/wiki/User:Liangsuilong -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel pgpvB1McmzMiY.pgp Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
coprs and personal repos: [Was: Re: Firefox 4 for Fedora 14?]
On Wed, 2010-07-28 at 14:12 -0500, Mike McGrath wrote: Maybe baby steps? Small incremental changes. Sure some features will be missing that kopers will provide. But perhaps we could just create a Fedora-13-devel tag in koji, push it to it's own repo or to individual fedora-13-spot / fedora-13-mmcgrath repos. One that doesn't migrate to updates-testing or updates. It just sits there. We're going to need something like this when kopers comes out anyway right? I figure smaller steps towards that goal is better then one big one. Toshio and I have talked about the targets of coprs and what the problems are we're trying to solve. Here are the problems: 1. I want to build these pkgs which have small patches to what's in fedora but I don't have the archs to build them on :solved by scratch builds in koji 2. I want to build these pkgs which have patches/changes to what's in fedora but I don't have the machines to build them on :solved by scratch builds in koji 3. I want to build these pkgs which have patches/changes to what's in fedora but I don't have a place to host them :provided, but not explicitly encouraged or endorsed by fedorapeople.org 4. I want to build these pkgs and they have new deps on pkgs which are not in fedora and I need to chain-build them from arbitrary :not provided by anything currently since you cannot build pkgs in koji with arbitrary deps from arbitrary repos. Item 4 is the main point that has been the big ticket item that things like Canonical's PPAs have hit. Since the other 3 had some relatively-possible solution Toshio and I started down the path of solving #4 since that was the only explicitly unsolved problem. Now - I think it would be perfectly reasonable for us to come up with a better/more official solution for #3. It's pretty simple to implement. We could setup a: http://repos.fedoraproject.org/$username/reponame/ it would be as simple as a subdir/path on the current fedorapeople (but using the repos hostname so we could move it later if needs demanded it) so - in theory we could have repos like: http://repos.fp.o/skvidal/func-future/ or http://repos.fp.o/func-group/func-future/ and extend out from there. then when item #4 is fully solved we could move this hierarchy to be used by coprs. It's a good place to start. -sv -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: coprs and personal repos: [Was: Re: Firefox 4 for Fedora 14?]
On Wed, Jul 28, 2010 at 9:37 PM, seth vidal skvi...@fedoraproject.org wrote: On Wed, 2010-07-28 at 14:12 -0500, Mike McGrath wrote: Maybe baby steps? Small incremental changes. Sure some features will be missing that kopers will provide. But perhaps we could just create a Fedora-13-devel tag in koji, push it to it's own repo or to individual fedora-13-spot / fedora-13-mmcgrath repos. One that doesn't migrate to updates-testing or updates. It just sits there. We're going to need something like this when kopers comes out anyway right? I figure smaller steps towards that goal is better then one big one. Toshio and I have talked about the targets of coprs and what the problems are we're trying to solve. Here are the problems: 1. I want to build these pkgs which have small patches to what's in fedora but I don't have the archs to build them on :solved by scratch builds in koji 2. I want to build these pkgs which have patches/changes to what's in fedora but I don't have the machines to build them on :solved by scratch builds in koji 3. I want to build these pkgs which have patches/changes to what's in fedora but I don't have a place to host them :provided, but not explicitly encouraged or endorsed by fedorapeople.org 4. I want to build these pkgs and they have new deps on pkgs which are not in fedora and I need to chain-build them from arbitrary :not provided by anything currently since you cannot build pkgs in koji with arbitrary deps from arbitrary repos. 5. Some easy way to enable/disable such repos other than messing with config files? -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: coprs and personal repos: [Was: Re: Firefox 4 for Fedora 14?]
On Wed, 2010-07-28 at 21:49 +0200, drago01 wrote: On Wed, Jul 28, 2010 at 9:37 PM, seth vidal skvi...@fedoraproject.org wrote: On Wed, 2010-07-28 at 14:12 -0500, Mike McGrath wrote: Maybe baby steps? Small incremental changes. Sure some features will be missing that kopers will provide. But perhaps we could just create a Fedora-13-devel tag in koji, push it to it's own repo or to individual fedora-13-spot / fedora-13-mmcgrath repos. One that doesn't migrate to updates-testing or updates. It just sits there. We're going to need something like this when kopers comes out anyway right? I figure smaller steps towards that goal is better then one big one. Toshio and I have talked about the targets of coprs and what the problems are we're trying to solve. Here are the problems: 1. I want to build these pkgs which have small patches to what's in fedora but I don't have the archs to build them on :solved by scratch builds in koji 2. I want to build these pkgs which have patches/changes to what's in fedora but I don't have the machines to build them on :solved by scratch builds in koji 3. I want to build these pkgs which have patches/changes to what's in fedora but I don't have a place to host them :provided, but not explicitly encouraged or endorsed by fedorapeople.org 4. I want to build these pkgs and they have new deps on pkgs which are not in fedora and I need to chain-build them from arbitrary :not provided by anything currently since you cannot build pkgs in koji with arbitrary deps from arbitrary repos. 5. Some easy way to enable/disable such repos other than messing with config files? yum-config-manager --enable repo1 repo2 repo3 -sv -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: coprs and personal repos: [Was: Re: Firefox 4 for Fedora 14?]
drago01 (drag...@gmail.com) said: 5. Some easy way to enable/disable such repos other than messing with config files? yum-plugin-tmprepo? (This may not fit your definition of 'easy'.) Bill -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: coprs and personal repos: [Was: Re: Firefox 4 for Fedora 14?]
On 28/07/10 20:49, drago01 wrote: 5. Some easy way to enable/disable such repos other than messing with config files? gnome-packagekit-extra tick what you need. -- Regards, Frank Murphy UTF_8 Encoded Friend of Fedora -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: coprs and personal repos: [Was: Re: Firefox 4 for Fedora 14?]
On Wed, 2010-07-28 at 15:37 -0400, seth vidal wrote: On Wed, 2010-07-28 at 14:12 -0500, Mike McGrath wrote: Maybe baby steps? Small incremental changes. Sure some features will be missing that kopers will provide. But perhaps we could just create a Fedora-13-devel tag in koji, push it to it's own repo or to individual fedora-13-spot / fedora-13-mmcgrath repos. One that doesn't migrate to updates-testing or updates. It just sits there. We're going to need something like this when kopers comes out anyway right? I figure smaller steps towards that goal is better then one big one. Toshio and I have talked about the targets of coprs and what the problems are we're trying to solve. Here are the problems: 1. I want to build these pkgs which have small patches to what's in fedora but I don't have the archs to build them on :solved by scratch builds in koji 2. I want to build these pkgs which have patches/changes to what's in fedora but I don't have the machines to build them on :solved by scratch builds in koji 3. I want to build these pkgs which have patches/changes to what's in fedora but I don't have a place to host them :provided, but not explicitly encouraged or endorsed by fedorapeople.org 4. I want to build these pkgs and they have new deps on pkgs which are not in fedora and I need to chain-build them from arbitrary :not provided by anything currently since you cannot build pkgs in koji with arbitrary deps from arbitrary repos. Item 4 is the main point that has been the big ticket item that things like Canonical's PPAs have hit. They also hit the Staples Easy Button about 1000 times. If there's a case to be made that this should be easy to do, then we should add tolling to common/Makefile to: 1) make an srpm 2) build it as a scratch build in koji 3) automatically download the built packages 4) scp them to your fedorapeople account 5) run createrepo remotely on the fp account 6) generate a yum .repo file for the repo and print out a link to it or something ie, enable doing this with *one* command in the dist-cvs/git checkout, like 'make ppa' or 'fedpkg ppa' that will do all these steps for you. Dan Since the other 3 had some relatively-possible solution Toshio and I started down the path of solving #4 since that was the only explicitly unsolved problem. Now - I think it would be perfectly reasonable for us to come up with a better/more official solution for #3. It's pretty simple to implement. We could setup a: http://repos.fedoraproject.org/$username/reponame/ it would be as simple as a subdir/path on the current fedorapeople (but using the repos hostname so we could move it later if needs demanded it) so - in theory we could have repos like: http://repos.fp.o/skvidal/func-future/ or http://repos.fp.o/func-group/func-future/ and extend out from there. then when item #4 is fully solved we could move this hierarchy to be used by coprs. It's a good place to start. -sv -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: coprs and personal repos: [Was: Re: Firefox 4 for Fedora 14?]
On Wed, Jul 28, 2010 at 9:51 PM, seth vidal skvi...@fedoraproject.org wrote: On Wed, 2010-07-28 at 21:49 +0200, drago01 wrote: On Wed, Jul 28, 2010 at 9:37 PM, seth vidal skvi...@fedoraproject.org wrote: On Wed, 2010-07-28 at 14:12 -0500, Mike McGrath wrote: Maybe baby steps? Small incremental changes. Sure some features will be missing that kopers will provide. But perhaps we could just create a Fedora-13-devel tag in koji, push it to it's own repo or to individual fedora-13-spot / fedora-13-mmcgrath repos. One that doesn't migrate to updates-testing or updates. It just sits there. We're going to need something like this when kopers comes out anyway right? I figure smaller steps towards that goal is better then one big one. Toshio and I have talked about the targets of coprs and what the problems are we're trying to solve. Here are the problems: 1. I want to build these pkgs which have small patches to what's in fedora but I don't have the archs to build them on :solved by scratch builds in koji 2. I want to build these pkgs which have patches/changes to what's in fedora but I don't have the machines to build them on :solved by scratch builds in koji 3. I want to build these pkgs which have patches/changes to what's in fedora but I don't have a place to host them :provided, but not explicitly encouraged or endorsed by fedorapeople.org 4. I want to build these pkgs and they have new deps on pkgs which are not in fedora and I need to chain-build them from arbitrary :not provided by anything currently since you cannot build pkgs in koji with arbitrary deps from arbitrary repos. 5. Some easy way to enable/disable such repos other than messing with config files? yum-config-manager --enable repo1 repo2 repo3 My wording might not have been the best with enable I actually meant install. something like copers --enable foo copers --disable foo which would download and set up the repo. (Shouldn't be really hard to do though) -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
