Thanks for the reply Dominique! I uninstalled the package using `zypper rm python3-pycparser` re-installed it with `zypper in python3-cffi python3-cryptography python3-pycparser python3-pyOpenSSL` (reinstalling packages removed due to it being a dependency) and I still get the following error: (1/4) Installing: python3-pycparser-2.18-1.1.noarch ...................................................................................[error] Installation of python3-pycparser-2.18-1.1.noarch failed: Error: Subprocess failed. Error: RPM failed: error: unpacking of archive failed on file /usr/lib/python3.6/site-packages/pycparser-2.18-py3.6.egg-info: cpio: File from package already exists as a directory in system error: python3-pycparser-2.18-1.1.noarch: install failed Any suggestions for how to proceed with this? On Tue, May 15, 2018 at 10:49 AM, Dominique Leuenberger / DimStar <dimstar@opensuse.org> wrote:

On Tue, 2018-05-15 at 10:37 +0100, Michael Aquilina wrote:

...

Hi there,

I am encountering this issue when running `zypper dup`

The following package is going to be upgraded: python3-pycparser

1 package to upgrade. Overall download size: 0 B. Already cached: 201.0 KiB. After the operation, additional 127.9 KiB will be used. Continue? [y/n/...? shows all options] (y): y In cache python3-pycparser-2.18-1.1.noarch.rpm (1/1), 201.0 KiB ( 1.3 MiB unpacked) Checking for file conflicts: ...........................................................................................................[done] (1/1) Installing: python3-pycparser-2.18-1.1.noarch ...................................................................................[error] Installation of python3-pycparser-2.18-1.1.noarch failed: Error: Subprocess failed. Error: RPM failed: error: unpacking of archive failed on file /usr/lib/python3.6/site-packages/pycparser-2.18-py3.6.egg-info: cpio:

This is a typical error when a package changes an entry from file to directory or vice-versa. This is somethihng RPM does not handle (but also something that should rarely happen in an RPM).

To get over this, you can remove the package (possibly forcing, ignoring deps) and then reinstall it.

Cheers Dominique

-- Michael Aquilina -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Yep that worked. I wonder if I maybe installed this python package through pip install dependency before which is why it wasnt cleaned up? I guess that's the danger between mixing package managers On Tue, May 15, 2018 at 11:00 AM, Dominique Leuenberger / DimStar <dimstar@opensuse.org> wrote:

On Tue, 2018-05-15 at 10:57 +0100, Michael Aquilina wrote:

...

Thanks for the reply Dominique!

I uninstalled the package using

`zypper rm python3-pycparser`

Seems that at this point, the cleanup was not done properly?

Try:

rpm -e --nodeps python3-pycparser rm -rf /usr/lib/python3.6/site-packages/pycparser-2.18-py3.6.egg-info zypper in python3-pycparser

Cheers, Dominique

-- Michael Aquilina -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org