---
yum/__init__.py|3 +--
yum/transactioninfo.py | 14 +++---
2 files changed, 12 insertions(+), 5 deletions(-)
diff --git a/yum/__init__.py b/yum/__init__.py
index 8e58124..1d7637f 100644
--- a/yum/__init__.py
+++ b/yum/__init__.py
@@ -1424,8 +1424,7 @@ class YumBase(depso
---
yum/misc.py | 12 +++-
1 files changed, 11 insertions(+), 1 deletions(-)
diff --git a/yum/misc.py b/yum/misc.py
index 921b95c..35b8056 100644
--- a/yum/misc.py
+++ b/yum/misc.py
@@ -899,7 +899,7 @@ def unlink_f(filename):
if e.errno != errno.ENOENT:
raise
-de
---
output.py |1 +
yum/depsolve.py |2 ++
2 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/output.py b/output.py
index 060eaab..05a4e83 100755
--- a/output.py
+++ b/output.py
@@ -1706,6 +1706,7 @@ class DepSolveProgressCallBack:
'u': _('updated'),
---
yum/__init__.py | 24 +++-
1 files changed, 23 insertions(+), 1 deletions(-)
diff --git a/yum/__init__.py b/yum/__init__.py
index fa26e62..8e58124 100644
--- a/yum/__init__.py
+++ b/yum/__init__.py
@@ -1419,7 +1419,29 @@ class YumBase(depsolve.Depsolve):
On Thu, 2010-06-10 at 15:30 -0400, James Antill wrote:
> ---
> yum/depsolve.py | 18 +-
> 1 files changed, 9 insertions(+), 9 deletions(-)
>
> diff --git a/yum/depsolve.py b/yum/depsolve.py
> index 740520f..c197b7f 100644
> --- a/yum/depsolve.py
> +++ b/yum/depsolve.py
> @@ -225
---
yum/depsolve.py | 18 +-
1 files changed, 9 insertions(+), 9 deletions(-)
diff --git a/yum/depsolve.py b/yum/depsolve.py
index 740520f..c197b7f 100644
--- a/yum/depsolve.py
+++ b/yum/depsolve.py
@@ -225,10 +225,10 @@ class Depsolve(object):
self.verbose_logg
---
yum/depsolve.py |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/yum/depsolve.py b/yum/depsolve.py
index 322c412..740520f 100644
--- a/yum/depsolve.py
+++ b/yum/depsolve.py
@@ -794,6 +794,8 @@ class Depsolve(object):
ts_state = txmbr.ts_state
On Thu, 2010-06-10 at 14:50 +0200, Paolo Abeni wrote:
> Hello,
>
> While tracing a memory leak in a simple python program using the yum
> API, I find a possible memory leak in the YumBase constructor;
> apparently a reference to the newly constructed YumBase instance is
> created in yum.packages.b
Hello,
While tracing a memory leak in a simple python program using the yum
API, I find a possible memory leak in the YumBase constructor;
apparently a reference to the newly constructed YumBase instance is
created in yum.packages.base by yum.depsolve.Depsolve.__init__(), and
this reference forbid
On Sun, 6 Jun 2010, James Antill wrote:
On Sun, 2010-06-06 at 11:13 +0300, Ville Skyttä wrote:
On Sunday 06 June 2010, James Antill wrote:
> 2. In a version comparison None can be used for any of EVR to mean
> "don't care". Eg:
>
> Requires: foo = 1
>
> ...is satisfied _equally_ by:
>
> Pro
10 matches
Mail list logo