Thanks, commited.
Tim
___
Yum-devel mailing list
Yum-devel@linux.duke.edu
https://lists.dulug.duke.edu/mailman/listinfo/yum-devel
Forwarded from Thomas.
Tim, Panu - your thoughts?
-sv
Forwarded Message
From: Thomas Vander Stichele [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: yum patch
Date: Fri, 31 Aug 2007 18:23:33 +0200
Hey,
so the attached patch mixes docs and adding a --recursive option,
Hi,
Just spotted this little typo ... clearly, what was intended here was
to check YumBase.plugins rather than the module plugins.
(Sent to the yum user list earlier by mistake)
Cheers,
Mark.
diff --git a/yum/__init__.py b/yum/__init__.py
index f7d6946..ace382c 100644
---
So, looking for the solution to a different bug yesterday I figured out
why we're populating the package sacks any time we run any transaction.
in depsolve.py we have:
def _getTs(self):
setup all the transaction set storage items we'll need
This can't happen in __init__ b/c
On Wed, 2007-09-05 at 00:36 -0400, James Antill wrote:
1. I want to enable an acroread/picasa/whatever specific repo. but I
_probably_ don't want that repo. feeding me their glibc update or
something else outside of that specific application.
we have a mechanism for that, though:
On Wed, 2007-09-05 at 08:27 +0200, Tim Lauridsen wrote:
simple-local-repo-priority - allows you to setup a local repo that has
SOME of the pkgs from another repo and know that the ones in the local
(or better priority repo) will be used. This only works for nevra-exact
pkgs from one to
