seth vidal wrote:
But this makes me think about, what is supposed to be API, i have never
expected this to be considered as API.
In my world it was just an internal repoclosure class, not supposed to be API
stable.
It's not a stable api, necessarily. It's just something folks are going
to u
Hi all,
leading up to the F11 feature freeze we'd like to have a yum bug day.
A bug day is where we sift the currently open bugs against yum,
yum-utils and createrepo and try to kill all of them that we can.
We'll start in the morning (whenever morning is for you) on Friday March
6th and end ev
On Wed, 2009-03-04 at 10:16 +0100, Tim Lauridsen wrote:
> James Antill wrote:
> > repoclosure.py |4 +++-
> > 1 file changed, 3 insertions(+), 1 deletion(-)
> >
> > New commits:
> > commit f7a73716cf9e0ec248eb06992378d60a779a1fd4
> > Author: James Antill
> > Date: Tue Mar 3 11:55:59 2009 -
James Antill wrote:
repoclosure.py |4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
New commits:
commit f7a73716cf9e0ec248eb06992378d60a779a1fd4
Author: James Antill
Date: Tue Mar 3 11:55:59 2009 -0500
Fix RepoClosure() API for spam-o-matic, and other users
diff --git a/repo
