On Tue, 27 Mar 2007 12:02:20 +0200, Michael Schwendt wrote:
> On Mon, 26 Mar 2007 22:47:20 -0500, Mike McGrath wrote:
>
>
>> Michael Schwendt wrote:
>>
>>> On Thu, 15 Mar 2007 22:08:12 +0100, Michael Schwendt wrote:
>>>
>>>
>>>
>>>> $ rpm -q python-kid
>>>> python-kid-0.9-2.centos4
>>>>
>>>> on
buildsys.fedoraproject.org would benefit from an update to 0.9.5
which
>>>> includes xml related fixes and makes it possible to create pages that
>>>> don't fail in the w3c validator.
>>>>
>>>> $ rpm -q --whatrequires python-kid
>>>> repoview-0.5.1-1.centos4
>>>>
>>>>
>>>
http://home.arcor.de/ms2002sep/tmp/el4-extras/noarch/python-kid-0.9.5-0.1...
>>>
>>> Source rpms and build requirements here:
>>>
http://home.arcor.de/ms2002sep/tmp/el4-extras/
>>>
>>>
>> I'm not sure I fully understand what problem this solves. Can you give
>> me an example?
>>
> Sure. It's
>
>
http://tinyurl.com/2pc37j
>
> versus
>
>
http://tinyurl.com/2wdk5s
>
> The former was created with unmodified software on buildsys.f.o, while the
> latter was created with my modified repoview including an updated
> python-kid.
>
So, what is the formal procedure for requesting a package update on the
buildsys server like described above and getting an official and final
reply?
Get someone upstream (RHEL) to accept the package changes. buildsys is
going away in days anyway after koji goes live.
-Mike