Re: Python-urllib3 package is corrupt on rsync

[Maarten]

Bill,

Just saw this thread now,  had this same problem a couple days ago. Did the

exact same thing as you did. removed the rpm package with 
ssl_match_hostname


in it, then manually removed those same dirs. Then reinstalled 
python-urllib3, then


after that I reinstalled python-backports-ssl_match_hostname. Was having 
problems


with certbot because of this problem.


On 26-05-18 17:16, Akemi Yagi wrote:

On Sat, May 26, 2018 at 3:45 AM, Bill Maidment  wrote:

But first.
I found a pile of directories from the attempts to install python-urllib3. I 
deleted them all
rm -fr /usr/lib/python2.7/site-packages/urllib3/packages/ssl_match_hostname*
(dangerous, I know)
and the rpm then installed OK.

Hopefully, that is the end of that problem. Now for the other one.
Cheers
Bill

Turns out this is a known issue. See this RHEL users' discussion thread:

https://access.redhat.com/discussions/3411171#comment-1300851

and a solution article:

https://access.redhat.com/solutions/3440171
(basically saying the same thing as in the discussion post: issues
with python backports files)

Akemi

Re: Python-urllib3 package is corrupt on rsync

[Akemi Yagi]

On Sat, May 26, 2018 at 3:45 AM, Bill Maidment  wrote:
> But first.
> I found a pile of directories from the attempts to install python-urllib3. I 
> deleted them all
> rm -fr /usr/lib/python2.7/site-packages/urllib3/packages/ssl_match_hostname*
> (dangerous, I know)
> and the rpm then installed OK.
>
> Hopefully, that is the end of that problem. Now for the other one.
> Cheers
> Bill

Turns out this is a known issue. See this RHEL users' discussion thread:

https://access.redhat.com/discussions/3411171#comment-1300851

and a solution article:

https://access.redhat.com/solutions/3440171
(basically saying the same thing as in the discussion post: issues
with python backports files)

Akemi

RE: Python-urllib3 package is corrupt on rsync

[Bill Maidment]

But first.
I found a pile of directories from the attempts to install python-urllib3. I 
deleted them all
rm -fr /usr/lib/python2.7/site-packages/urllib3/packages/ssl_match_hostname*
(dangerous, I know)
and the rpm then installed OK.

Hopefully, that is the end of that problem. Now for the other one.
Cheers
Bill
 
-Original message-
> From:Bill Maidment 
> Sent: Saturday 26th May 2018 16:52
> To: Akemi Yagi ; SCIENTIFIC-LINUX-USERS@FNAL.GOV 
> 
> Subject: RE: Python-urllib3 package is corrupt on rsync
> 
> Thanks Akemi
> I am getting the same hash value as you, so it doesn't appear to be the rpm 
> that is at fault.
> I have tried yum reinstall of yum* and rpm* without solving the issue.
> As this is on another KVM guest on the machine on which I had an unrelated 
> unsolved error, I think I may have a hardware problem.
> Time for the memory test.
> Cheers
> Bill
>  
> -Original message-
> > From:Akemi Yagi 
> > Sent: Saturday 26th May 2018 15:03
> > To: SCIENTIFIC-LINUX-USERS@FNAL.GOV 
> > Subject: Re: Python-urllib3 package is corrupt on rsync
> > 
> > On Fri, May 25, 2018 at 8:53 PM, Bill Maidment  wrote:
> > > In SL7x I tried to install python-urllib3 and got this error, even after 
> > > deleting it from my repository and rsyncing again.
> > >
> > >   Installing : python-urllib3-1.10.2-5.el7.noarch 
> > >  1/1
> > > Error unpacking rpm package python-urllib3-1.10.2-5.el7.noarch
> > > error: unpacking of archive failed on file 
> > > /usr/lib/python2.7/site-packages/urllib3/packages/ssl_match_hostname: 
> > > cpio: rename
> > >   Verifying  : python-urllib3-1.10.2-5.el7.noarch 
> > >  1/1
> > >
> > > Failed:
> > >   python-urllib3.noarch 0:1.10.2-5.el7
> > >
> > > Cheers
> > > Bill Maidment
> > 
> > I just tried and was able to install
> > python-urllib3-1.10.2-5.el7.noarch without any issue.
> > 
> > You may want to check the file you have rsynced by comparing it
> > against the original file. For example:
> > 
> > $ sha256sum python-urllib3-1.10.2-5.el7.noarch.rpm
> > ef4067425a59ec50a9a201a94e408f13dc7b021ca8950249eaf047f084b1e606
> > python-urllib3-1.10.2-5.el7.noarch.rpm
> > 
> > Checking the hash value is one way to verify the file's integrity.
> > 
> > Akemi
> > 
> > 
> 
> 

RE: Python-urllib3 package is corrupt on rsync

[Bill Maidment]

Thanks Akemi
I am getting the same hash value as you, so it doesn't appear to be the rpm 
that is at fault.
I have tried yum reinstall of yum* and rpm* without solving the issue.
As this is on another KVM guest on the machine on which I had an unrelated 
unsolved error, I think I may have a hardware problem.
Time for the memory test.
Cheers
Bill
 
-Original message-
> From:Akemi Yagi 
> Sent: Saturday 26th May 2018 15:03
> To: SCIENTIFIC-LINUX-USERS@FNAL.GOV 
> Subject: Re: Python-urllib3 package is corrupt on rsync
> 
> On Fri, May 25, 2018 at 8:53 PM, Bill Maidment  wrote:
> > In SL7x I tried to install python-urllib3 and got this error, even after 
> > deleting it from my repository and rsyncing again.
> >
> >   Installing : python-urllib3-1.10.2-5.el7.noarch   
> >1/1
> > Error unpacking rpm package python-urllib3-1.10.2-5.el7.noarch
> > error: unpacking of archive failed on file 
> > /usr/lib/python2.7/site-packages/urllib3/packages/ssl_match_hostname: cpio: 
> > rename
> >   Verifying  : python-urllib3-1.10.2-5.el7.noarch   
> >1/1
> >
> > Failed:
> >   python-urllib3.noarch 0:1.10.2-5.el7
> >
> > Cheers
> > Bill Maidment
> 
> I just tried and was able to install
> python-urllib3-1.10.2-5.el7.noarch without any issue.
> 
> You may want to check the file you have rsynced by comparing it
> against the original file. For example:
> 
> $ sha256sum python-urllib3-1.10.2-5.el7.noarch.rpm
> ef4067425a59ec50a9a201a94e408f13dc7b021ca8950249eaf047f084b1e606
> python-urllib3-1.10.2-5.el7.noarch.rpm
> 
> Checking the hash value is one way to verify the file's integrity.
> 
> Akemi
> 
> 

good bye

[ToddAndMargo]

Hi All,

So many of you guys have helped me over the years that I feel
I should jot down a quick note of thanks before I unsubscribe.

I am now on Fedora everywhere and no longer have any RHEL clones
anywhere.  RHEL is out of date deliberately and I was trying
to force the issue, which about drove me insane.

So, so many bugs have been fixed in Fedora that I am still
gitty after upgrading in December.

And the irony of KVM being a Red Hat project and KVM not
being able to run its fixed and improvements under RHEL
has not escaped me.  (qemu-kvm runs really sweet under
Fedora and the USB redirection actually works!)

So, I guess this is goodby.  Thank you for all the
help all these years!

If anyone wishes to write me, please write directly to
my eMail address

-T