Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #95782
| From | Cecil Westerhof <Cecil@decebal.nl> |
|---|---|
| Newsgroups | comp.lang.python |
| Subject | Re: pycparser error or openSUSE error |
| Date | 2015-08-31 09:27 +0200 |
| Organization | Decebal Computing |
| Message-ID | <87bndnvrxg.fsf@Equus.decebal.nl> (permalink) |
| References | <87613zf2lu.fsf@Equus.decebal.nl> <201508282322.t7SNMsPg032423@fido.openend.se> <mailman.119.1440804686.11709.python-list@python.org> |
On Saturday 29 Aug 2015 01:30 CEST, Laura Creighton wrote: > In a message of Sat, 29 Aug 2015 01:22:54 +0200, Laura Creighton > writes: >> In a message of Sat, 29 Aug 2015 00:51:57 +0200, Cecil Westerhof >> writes: >>> When doing a ‘zypper update’ on openSUSE I get: Installing: >>> python-pycparser-2.12-8.2 >>> ..........................................................................................................................................................[error] >>> Installation of python-pycparser-2.12-8.2 failed: Error: >>> Subprocess failed. Error: RPM failed: error: unpacking of archive >>> failed on file >>> /usr/lib/python2.7/site-packages/pycparser-2.12-py2.7.egg-info: >>> cpio: rename failed - Is a directory error: >>> python-pycparser-2.12-8.2.noarch: install failed >>> >>> Is this a Python error or an openSUSE error? >>> >>> -- >>> Cecil Westerhof >>> Senior Software Engineer >>> LinkedIn: http://www.linkedin.com/in/cecilwesterhof >> >> SuSe is complaining. >> >> You almost certainly have this problem. >> >> https://joshua.hoblitt.com/rtfm/2013/05/dealing_with_rpm_cpio_rename_package_installupdate_errors/ >> >> Laura > > 'Almost certainly' was overstating it. (Just got home after beers > with friends). The other good way I know to get this one is > for that directory to already be there, or be a symlink to another > device. The packager manager ought to be a lot smarter, but it > defaults to 'panic, panic, die' ... when it sees something it didn't > expect. It looks like they made it more smart: the error went away. ;-) > Laura (more correct though still far from sober) Nothing wrong with letting your hair loose now and then. -- Cecil Westerhof Senior Software Engineer LinkedIn: http://www.linkedin.com/in/cecilwesterhof
Back to comp.lang.python | Previous | Next — Previous in thread | Find similar | Unroll thread
pycparser error or openSUSE error Cecil Westerhof <Cecil@decebal.nl> - 2015-08-29 00:51 +0200
Re: pycparser error or openSUSE error Laura Creighton <lac@openend.se> - 2015-08-29 01:22 +0200
Re: pycparser error or openSUSE error Cecil Westerhof <Cecil@decebal.nl> - 2015-08-31 09:23 +0200
Re: pycparser error or openSUSE error Laura Creighton <lac@openend.se> - 2015-08-29 01:30 +0200
Re: pycparser error or openSUSE error Cecil Westerhof <Cecil@decebal.nl> - 2015-08-31 09:27 +0200
csiph-web