---
cli.py | 14 +-
output.py | 47 +++
yum/__init__.py |2 +-
3 files changed, 61 insertions(+), 2 deletions(-)
diff --git a/cli.py b/cli.py
index ba2e343..acaecba 100755
--- a/cli.py
+++ b/cli.py
@@ -529,6 +529,11 @@
> Cleaner IMO, upstream supported way, and one subshell + pkg-config
> invocation less.
Yes, it's cleaner. Can we use _xfunc in rhel7? Anyway, I'd rather
just add a "_xfunc yum :" one-liner and not touch anything else.
> if it's about >= 2.0 note that
> the one-liner your original patch adds wi
On 22/04/13 14:36, James Antill wrote:
> On Thu, 2013-04-18 at 17:08 +0100, John Haxby wrote:
>> Hello All,
>>
>> I've been tinkering with a old sparc box recently and noticed an odd
>> problem when yum updating the kernel. If I have two kernels currently
>> installed and use yum update to pick up
On Thu, 2013-04-18 at 17:08 +0100, John Haxby wrote:
> Hello All,
>
> I've been tinkering with a old sparc box recently and noticed an odd
> problem when yum updating the kernel. If I have two kernels currently
> installed and use yum update to pick up a third, it's ignored. Turning
> on debug
Also allow more flexible testing. In particular, setting
rpmUtils.arch.canonArch=\'sparc64v\' illustrated a problem with
complex update for kernel.sparc64.
---
rpmUtils/tests/updates-test.py | 64 +-
1 file changed, 39 insertions(+), 25 deletions(-)
diff -
Hello All,
I sent a message about this last week and I know it hit the archives (I can
see it) but I never saw the actual message. Is there a problem with
attachments or possibly some other problem?
The subject of that message was the same as this: a complex update under
some circumstances will
