6:36 p.m.
Greetings.
I have just done some clean up on the EPEL stable repositories.
In epel-4 (stable):
perl-XML-DOM Removed (Removed because it provides perl-libxml-enno,
which is already provided by a "core" RHEL package). bug #249901
The ctapi-cyberjack Removed (removed because it requires a dependency
from ctapi-common thats not in stable). bug #279991
In epel-5 (stable):
lapack Removed. (Removed because it conflicts with the RHEL "core"
lapack package, and is even newer). Bug #279821
php-pear-PhpDocumentor Removed (Broken dependencies). Bug #280001.
ctapi-cyberjack Removed. (removed because they require a dependency
from ctapi-common thats not in stable). bug #279991
Also, lighttpd was pushed into EPEL-5 stable (Security update).
NOTE: If anyone has security updates, please do notify the list and/or
mail epel_signers-members(a)fedoraproject.org asking for your update to
be pushed ASAP.
Please let me know if anyone spots any problems with the current
repositories.
kevin
3:19 a.m.
On 13.09.2007 01:36, Kevin Fenzi wrote:
Greetings.
I have just done some clean up on the EPEL stable repositories.
[...]
Many thx for that kevin!
Please let me know if anyone spots any problems with the current
repositories.
That reminds me of something else: I haven't seen any "broken deps"
report recently. Mike, Dennis, are they still running regularly? Are
they running only for EPEL stable or also for EPEL testing (whcih they
should IMHO)?
Cu
knurd
8:11 a.m.
Thorsten Leemhuis wrote:
On 13.09.2007 01:36, Kevin Fenzi wrote:
> Greetings.
>
> I have just done some clean up on the EPEL stable repositories.
> [...]
>
Many thx for that kevin!
> Please let me know if anyone spots any problems with the current
> repositories.
>
That reminds me of something else: I haven't seen any "broken deps"
report recently. Mike, Dennis, are they still running regularly? Are
they running only for EPEL stable or also for EPEL testing (whcih they
should IMHO)?
Right now only EPEL stable and they are running there are a couple
broken deps in EPEL-[4-5] IIRC.
-Mike
9:01 a.m.
On Sep 13, 2007, at 9:11 AM, Mike McGrath wrote:
Thorsten Leemhuis wrote:
> That reminds me of something else: I haven't seen any "broken deps"
> report recently. Mike, Dennis, are they still running regularly? Are
> they running only for EPEL stable or also for EPEL testing (whcih
> they
> should IMHO)?
>
Right now only EPEL stable and they are running there are a couple
broken deps in EPEL-[4-5] IIRC.
-Mike
Some people may hate me for this, but I think running the deps check
on testing would be a good idea. Otherwise people may have broken
packages there and not know it. Plus, if people get nagged enough,
they may get motivated to fix things, import needed packages, etc. :)
-Jeff
9:43 a.m.
Jeff Sheltren wrote:
On Sep 13, 2007, at 9:11 AM, Mike McGrath wrote:
> Thorsten Leemhuis wrote:
>> That reminds me of something else: I haven't seen any "broken
deps"
>> report recently. Mike, Dennis, are they still running regularly? Are
>> they running only for EPEL stable or also for EPEL testing (whcih they
>> should IMHO)?
>>
>
> Right now only EPEL stable and they are running there are a couple
> broken deps in EPEL-[4-5] IIRC.
>
> -Mike
>
Some people may hate me for this, but I think running the deps check
on testing would be a good idea. Otherwise people may have broken
packages there and not know it. Plus, if people get nagged enough,
they may get motivated to fix things, import needed packages, etc. :)
So we're doing two runs against EPEL-5 and EPEL-4
EPEL5-testing: Merges RHEL5, EPEL-5, EPEL-5-Testing
EPEL5: Merges RHEL5, EPEL-5
EPEL4-testing: Merges RHEL4, EPEL-4, EPEL-4-Testing
EPEL4: Merges RHEL4, EPEL-4
That seem sane to everyone?
-Mike
10:14 a.m.
On 13.09.2007 16:43, Mike McGrath wrote:
> Jeff Sheltren wrote:
>> On Sep 13, 2007, at 9:11 AM, Mike McGrath wrote:
>>> Thorsten Leemhuis wrote:
>> Some people may hate me for this, but I think running the deps check
>> on testing would be a good idea. Otherwise people may have broken
>> packages there and not know it.
Exactly (and that's why I brought the topic up).
>> Plus, if people get nagged enough,
>> they may get motivated to fix things, import needed packages, etc. :)
+1 -- we also in the future try to keep the broken deps even in testing
to a minimum. E.g. something like "if there is a package in testing that
has broken deps for more then 7 days it's going to be removed."
Where may I see what's in testing? I have a package that was moved there
from broken deps but I've since resolved them for EPEL-5, and I'm curious
where it sits.
> So we're doing two runs against EPEL-5 and EPEL-4
>
> EPEL5-testing: Merges RHEL5, EPEL-5, EPEL-5-Testing
> EPEL5: Merges RHEL5, EPEL-5
>
> EPEL4-testing: Merges RHEL4, EPEL-4, EPEL-4-Testing
> EPEL4: Merges RHEL4, EPEL-4
>
> That seem sane to everyone?
Yes -- I think that's a must-have.
BTW, how often do they run? Once a week iirc? Would it be much work to
let cron them at least twice a week?
Cu
knurd
_______________________________________________
epel-devel-list mailing list
epel-devel-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/epel-devel-list
--
novus ordo absurdum
10:37 a.m.
On 13.09.2007 16:43, Mike McGrath wrote:
Jeff Sheltren wrote:
> On Sep 13, 2007, at 9:11 AM, Mike McGrath wrote:
>> Thorsten Leemhuis wrote:
> Some people may hate me for this, but I think running the deps check
> on testing would be a good idea. Otherwise people may have broken
> packages there and not know it.
Exactly (and that's why I brought the topic up).
> Plus, if people get nagged enough,
> they may get motivated to fix things, import needed packages, etc. :)
+1 -- we also in the future try to keep the broken deps even in testing
to a minimum. E.g. something like "if there is a package in testing that
has broken deps for more then 7 days it's going to be removed."
So we're doing two runs against EPEL-5 and EPEL-4
EPEL5-testing: Merges RHEL5, EPEL-5, EPEL-5-Testing
EPEL5: Merges RHEL5, EPEL-5
EPEL4-testing: Merges RHEL4, EPEL-4, EPEL-4-Testing
EPEL4: Merges RHEL4, EPEL-4
That seem sane to everyone?
Yes -- I think that's a must-have.
BTW, how often do they run? Once a week iirc? Would it be much work to
let cron them at least twice a week?
Cu
knurd
11:40 a.m.
On Thu, 13 Sep 2007 08:11:14 -0500
mmcgrath(a)redhat.com (Mike McGrath) wrote:
Thorsten Leemhuis wrote:
> On 13.09.2007 01:36, Kevin Fenzi wrote:
>
>> Greetings.
>>
>> I have just done some clean up on the EPEL stable repositories.
>> [...]
>>
>
> Many thx for that kevin!
>
>
>> Please let me know if anyone spots any problems with the current
>> repositories.
>>
>
> That reminds me of something else: I haven't seen any "broken deps"
> report recently. Mike, Dennis, are they still running regularly? Are
> they running only for EPEL stable or also for EPEL testing (whcih
> they should IMHO)?
>
Right now only EPEL stable and they are running there are a couple
broken deps in EPEL-[4-5] IIRC.
From what I can see there should now only be 1 broken dep in stable.
I will try and take care of that very soon.
It's graphviz, and I think it just needs to be blacklisted from being
multilib in epel-4, since perl in RHEL4 is not multilib.
-Mike
kevin
11:43 a.m.
On Thu, 13 Sep 2007 10:14:43 -0500 (CDT)
limb(a)jcomserv.net ("Jon Ciesla") wrote:
> On 13.09.2007 16:43, Mike McGrath wrote:
>> Jeff Sheltren wrote:
>>> On Sep 13, 2007, at 9:11 AM, Mike McGrath wrote:
>>>> Thorsten Leemhuis wrote:
>>> Some people may hate me for this, but I think running the deps
>>> check on testing would be a good idea. Otherwise people may have
>>> broken packages there and not know it.
>
> Exactly (and that's why I brought the topic up).
>
>>> Plus, if people get nagged enough,
>>> they may get motivated to fix things, import needed packages,
>>> etc. :)
>
> +1 -- we also in the future try to keep the broken deps even in
> testing to a minimum. E.g. something like "if there is a package in
> testing that has broken deps for more then 7 days it's going to be
> removed."
Yeah, I would like to see runs against testing as well.
In addition to the other reasons, it would be very nice to get
everything fixed before 5.1 comes out so we can cleanly move things
over to the stable repo.
Where may I see what's in testing? I have a package that was moved
there from broken deps but I've since resolved them for EPEL-5, and
I'm curious where it sits.
You should be able to look in
http://download.fedora.redhat.com/pub/epel/testing/
kevin
6069
days inactive
6070
days old
epel-devel@lists.fedoraproject.org
8 comments
5 participants
participants (5)
-
Jeff Sheltren -
Jon Ciesla -
Kevin Fenzi -
Mike McGrath -
Thorsten Leemhuis