Why is there no repository for the fedora.us packages that's in sync with fedora development? I've noticed fedora-devel packages tend to update in batches in order not to break dependencies. It becomes a pain to make fedora devel work with fedora.us packages against the last release. Isn't the idea to merge the two anyway? When will that happen?
Ivan Gyurdiev wrote:
Why is there no repository for the fedora.us packages that's in sync with fedora development? I've noticed fedora-devel packages tend to update in batches in order not to break dependencies. It becomes a pain to make fedora devel work with fedora.us packages against the last release. Isn't the idea to merge the two anyway? When will that happen?
What are you talking about? fedora.us has been in sync with development during this entire FC2 cycle. Now we've moved to a version '2' repository in preparation for release, so we can do a mass rebuild of all Extras packages and make sure everything works.
Warren
On Wed, 12 May 2004 20:05:49 -1000, Warren Togami wrote:
Ivan Gyurdiev wrote:
Why is there no repository for the fedora.us packages that's in sync with fedora development? I've noticed fedora-devel packages tend to update in batches in order not to break dependencies. It becomes a pain to make fedora devel work with fedora.us packages against the last release. Isn't the idea to merge the two anyway? When will that happen?
What are you talking about? fedora.us has been in sync with development during this entire FC2 cycle. Now we've moved to a version '2' repository in preparation for release, so we can do a mass rebuild of all Extras packages and make sure everything works.
It sounds like he wants the complete fedora.us extras repository being rebuilt daily against the development tree or something like that.
Warren Togami wrote:
Ivan Gyurdiev wrote:
Why is there no repository for the fedora.us packages that's in sync with fedora development? I've noticed fedora-devel packages tend to update in batches in order not to break dependencies. It becomes a pain to make fedora devel work with fedora.us packages against the last release. Isn't the idea to merge the two anyway? When will that happen?
What are you talking about? fedora.us has been in sync with development during this entire FC2 cycle. Now we've moved to a version '2' repository in preparation for release, so we can do a mass rebuild of all Extras packages and make sure everything works.
Ok. I assumed I don't know what I'm talking about. Then how about this:
This is from the lablgtk maintainer in Fedora.us
------- Additional Comment #2 From Ivan Gyurdiev 2004-06-19 09:42 -------
And the current libcroco is:
libcroco-0.5.1-1
I was told fedora.us was to stay in sync with -devel...anything else is a bug. Is this not so?
------- Additional Comment #3 From Michael Schwendt 2004-06-19 10:01 -------
That is false information. The Extras repositories for Fedora Core 2 stay compatible with Fedora Core 2, of course, and do not follow Fedora Core Development. A separate tree which follows FC Development does not exist. With availability of FC3 Test1, (re)builds will be available in a separate tree.
On Sat, 19 Jun 2004 14:30:21 -0600, Ivan Gyurdiev wrote:
This is from the lablgtk maintainer in Fedora.us
------- Additional Comment #3 From Michael Schwendt 2004-06-19 10:01 -------
As a side note, I'm not the lablgtk maintainer. Gerard Milmeister is. But I query bugzilla for general fedora.us bugs/issues regularly and -- where possible -- like to give bug reporters a response.
Anyway, asking for a package in the FC2 extras repositories to be rebuilt against rawhide is answered with a clear "won't happen". The fedora/2 repositories will stay compatible with FC2.
As a side note, I'm not the lablgtk maintainer. Gerard Milmeister is. But I query bugzilla for general fedora.us bugs/issues regularly and -- where possible -- like to give bug reporters a response.
Ok
Anyway, asking for a package in the FC2 extras repositories to be rebuilt against rawhide is answered with a clear "won't happen". The fedora/2 repositories will stay compatible with FC2.
Hey, it makes sense to me. I'm just wondering why it is that people are saying something different here. Furthermore, I don't see why you can't have it both ways - keep one repository that's compatible, and another that follows -devel.
On Sat, 19 Jun 2004 15:59:29 -0600, Ivan Gyurdiev wrote:
Anyway, asking for a package in the FC2 extras repositories to be rebuilt against rawhide is answered with a clear "won't happen". The fedora/2 repositories will stay compatible with FC2.
Hey, it makes sense to me.
No, it doesn't. FC2 = Fedora Core 2 and not Fedora Core Development.
I'm just wondering why it is that people are saying something different here.
They aren't saying something different. ;)
Your original message was from May 13th
http://www.redhat.com/archives/fedora-devel-list/2004-May/msg00444.html
and Warren's reply was correct in that he referred to the Fedora Core 1.9x extras repositories, which started with a mass rebuild against Test 1 and then were expanded with additional packages built against the current Fedora Core 2 development tree. All this was in preparation of Fedora Core 2.
The key point to understand is that you want a tree of extra packages to stay in sync with Fedora Core Development _always_.
Furthermore, I don't see why you can't have it both ways - keep one repository that's compatible, and another that follows -devel.
It's a matter of resources. You would need an additional monkey to monitor the [probably daily] mass rebuilds, deal with the usual wreckage in rawhide and report failed rebuilds of extra packages to their maintainers. Or even more monkeys to maintain the Fedora Core Development Extras tree independently and fix any problems themselves. The package maintainers are unlikely to follow Fedora Core Development till the first test release, however. And not all follow the test releases either.
On Thu, 2004-05-13 at 04:40, Ivan Gyurdiev wrote:
Why is there no repository for the fedora.us packages that's in sync with fedora development? I've noticed fedora-devel packages tend to update in batches in order not to break dependencies. It becomes a pain to make fedora devel work with fedora.us packages against the last release.
If something needs to be rebuilt due to a changed dependency -> bugzilla.fedora.us.