Fedora 18 will EOL very soon. How will it affect building for F18 in Copr?
It is first time event. So we have to define the default behavior.
My proposal is to keep it little bit longer available. Is 3 months enough? And then remove it from available chroots. I.e. you will not be able to build new package for Fedora 18. But I would preserve all old builds for F18.
Do you agree? Or you have objections? If no one answers with objections or better idea, I would stick to this plan.
On Thu, 09 Jan 2014 14:27:28 +0100 Miroslav Suchý msuchy@redhat.com wrote:
Fedora 18 will EOL very soon. How will it affect building for F18 in Copr?
It is first time event. So we have to define the default behavior.
My proposal is to keep it little bit longer available. Is 3 months enough? And then remove it from available chroots. I.e. you will not be able to build new package for Fedora 18. But I would preserve all old builds for F18.
Do you agree? Or you have objections? If no one answers with objections or better idea, I would stick to this plan.
I'd prefer it just be disabled on fedora 18 eol day... people shouldn't be producing new coprs against old eol releases.
I agree with keeping existing ones around for a while though, perhaps those could live another month or three.
kevin
On Thu, Jan 09, 2014 at 07:49:08AM -0700, Kevin Fenzi wrote:
On Thu, 09 Jan 2014 14:27:28 +0100 Miroslav Suchý msuchy@redhat.com wrote:
Fedora 18 will EOL very soon. How will it affect building for F18 in Copr?
It is first time event. So we have to define the default behavior.
My proposal is to keep it little bit longer available. Is 3 months enough? And then remove it from available chroots. I.e. you will not be able to build new package for Fedora 18. But I would preserve all old builds for F18.
Do you agree? Or you have objections? If no one answers with objections or better idea, I would stick to this plan.
I'd prefer it just be disabled on fedora 18 eol day... people shouldn't be producing new coprs against old eol releases.
+1
I agree with keeping existing ones around for a while though, perhaps those could live another month or three.
I disagree with this one, though -- built packages should remain "forver". Packages for EOL fedora releases are still available and repositories on repos.fedororapeople.org for EOL releases are not pruned. Those are the precedents that we should be following.
We may want to move them out of copr (similar to how EOL fedora releases get moved to archives.fedoraproject.org)
Are repos.fedorapeople.org packages under the user's quota? If so, we may want to establish a quota for EOL packages as well so that the user is encouraged to self-prune EOL or no longer needed builds (package has been merged into newer fedora or etc).
-Toshio
On Thu, 9 Jan 2014 07:24:54 -0800 Toshio Kuratomi a.badger@gmail.com wrote:
I'd prefer it just be disabled on fedora 18 eol day... people shouldn't be producing new coprs against old eol releases.
+1
I agree with keeping existing ones around for a while though, perhaps those could live another month or three.
I disagree with this one, though -- built packages should remain "forver". Packages for EOL fedora releases are still available and repositories on repos.fedororapeople.org for EOL releases are not pruned. Those are the precedents that we should be following.
True...
We may want to move them out of copr (similar to how EOL fedora releases get moved to archives.fedoraproject.org)
Are repos.fedorapeople.org packages under the user's quota? If so, we may want to establish a quota for EOL packages as well so that the user is encouraged to self-prune EOL or no longer needed builds (package has been merged into newer fedora or etc).
They are under the users quota on fedorapeople.
I personally remove my old ones right after EOL, but I'm sure some people keep them around.
kevin
On 09/01/14 14:27, Miroslav Suchý wrote:
Fedora 18 will EOL very soon. How will it affect building for F18 in Copr?
It is first time event. So we have to define the default behavior.
My proposal is to keep it little bit longer available. Is 3 months enough? And then remove it from available chroots. I.e. you will not be able to build new package for Fedora 18. But I would preserve all old builds for F18.
I actually agree with keeping it around for little longer - 3 months seems to be fine. This would allow individuals to rebuild certain packages from newer fedoras and effectively prolong the lifecycle of the distro. If we're not running out of space or resources let's keep it alive for those 3 months.
Radek
Do you agree? Or you have objections? If no one answers with objections or better idea, I would stick to this plan.
On Thu, 2014-01-09 at 14:27 +0100, Miroslav Suchý wrote:
Fedora 18 will EOL very soon. How will it affect building for F18 in Copr?
It is first time event. So we have to define the default behavior.
My proposal is to keep it little bit longer available. Is 3 months enough? And then remove it from available chroots. I.e. you will not be able to build new package for Fedora 18. But I would preserve all old builds for F18.
Do you agree? Or you have objections? If no one answers with objections or better idea, I would stick to this plan.
I would run some DB script so that F18 builds are turned off for everyone, on the day of EOL ... but let people turn them back on for at least 1-3 months. That should be a nice compromise between getting the resources back for the majority but still letting people rely on coprs for builds.
copr-devel@lists.stg.fedorahosted.org