Your message dated Fri, 8 Mar 2019 12:54:45 -0800
with message-id <[email protected]>
and subject line Bug#697222: fixed in yum/3.4.3-1
has caused the Debian Bug report #697222,
regarding yum exists when printing certain errors: 'rpm.prob' object has no 
attribute 'startswith'
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
697222: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697222
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: yum
Version: 3.2.25-2
Severity: normal
Tags: patch

Dear Maintainer,

I tried running:

/usr/bin/yum --installroot /srv/mock/root/epel-6-x86_64/root/ groupinstall 
buildsys-build

It starts updating sources and locating packages. Then it gives the
following (given here with a PoC patch): 

--- /usr/share/yum-cli/cli.py   2013-01-02 22:31:43.000000000 +0200
+++ /usr/share/yum-cli/cli.py_new       2013-01-02 22:23:47.000000000 +0200
@@ -420,7 +420,7 @@ class YumBaseCli(yum.YumBase, output.Yum
             if msgs:
                 rpmlib_only = True
                 for msg in msgs:
-                    if msg.startswith('rpmlib('):
+                    if isinstance(msg, rpm.prob) or msg.startswith('rpmlib('):
                         continue
                     rpmlib_only = False
                 if rpmlib_only:

With this I could see the hidden problem of:

  ERROR You need to update rpm to handle:
  libfreebl3.so()(64bit) is needed by glibc-2.12-1.80.el6_3.6.x86_64
  libfreebl3.so(NSSRAWHASH_3.12.3)(64bit) is needed by 
glibc-2.12-1.80.el6_3.6.x86_64
  libz.so.1()(64bit) is needed by file-5.04-13.el6.x86_64
  ...

but this is an issue for a different bug report, if any. This was because
I was foolish enough to run that from a 32bit system.

-- 
Tzafrir Cohen         | [email protected] | VIM is
http://tzafrir.org.il |                    | a Mutt's
[email protected] |                    |  best
[email protected]    |                    | friend

--- End Message ---
--- Begin Message ---
No activity, assume this was indeed fixed in yum 3.4.3-1.

-- 
mike

--- End Message ---

Reply via email to