SCIENTIFIC-LINUX-USERS Archives

October 2020

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Patrick Riehecky <[log in to unmask]>
Reply To:
Patrick Riehecky <[log in to unmask]>
Date:
Tue, 27 Oct 2020 15:03:24 +0000
Content-Type:
text/plain
Parts/Attachments:
text/plain (1 lines)
Interesting, I'll take a look and see what I can determine.



Pat



On Tue, 2020-10-27 at 07:53 -0700, Adam Mercer wrote:

> Hi

> 

> We are currently running Scientific Linux on our cluster and use the

> sl:7 docker container for a lot of CI testing, a few days ago a lot

> of our CI tests started failing due to the inability to install the

> python-devel package. I did some testing and managed to find a

> simple test case that reproduces the problem:

> 

> -> % podman run --pull=always -it sl:7

> Trying to pull docker.io/library/sl:7...

> Getting image source signatures

> Copying blob 59be490dd3b4 [--------------------------------------]

> 0.0b / 0.0b

> Copying config 7a1ff3f0bf done

> Writing manifest to image destination

> Storing signatures

> [root@73f9ce4412a7 /]# yum install python-devel

> Loaded plugins: ovl

> repos                                                    | 2.6 kB

>   00:00

> sl                                                       | 3.8 kB

>   00:00

> sl-fastbugs                                              | 2.9 kB

>   00:00

> sl-security                                              | 2.9 kB

>   00:00

> (1/8): repos/x86_64/primary_db                             | 8.2 kB

>   00:00

> (2/8): sl-fastbugs/x86_64/updateinfo                       | 6.3 kB

>   00:00

> (3/8): sl-security/x86_64/updateinfo                       | 8.8 kB

>   00:00

> (4/8): sl-fastbugs/x86_64/primary_db                       | 131 kB

>   00:00

> (5/8): sl/x86_64/group_gz                                  | 107 kB

>   00:00

> (6/8): sl-security/x86_64/primary_db                       | 1.1 MB

>   00:00

> (7/8): sl/x86_64/primary_db                                | 4.6 MB

>   00:01

> (8/8): sl/x86_64/updateinfo                                | 3.4 MB

>   00:01

> Resolving Dependencies

> --> Running transaction check

> ---> Package python-devel.x86_64 0:2.7.5-89.el7 will be installed

> --> Processing Dependency: python(x86-64) = 2.7.5-89.el7 for

> package: python-devel-2.7.5-89.el7.x86_64

> --> Processing Dependency: python-rpm-macros > 3-30 for package:

> python-devel-2.7.5-89.el7.x86_64

> --> Processing Dependency: python2-rpm-macros > 3-30 for package:

> python-devel-2.7.5-89.el7.x86_64

> --> Running transaction check

> ---> Package python-devel.x86_64 0:2.7.5-89.el7 will be installed

> --> Processing Dependency: python(x86-64) = 2.7.5-89.el7 for

> package: python-devel-2.7.5-89.el7.x86_64

> ---> Package python-rpm-macros.noarch 0:3-34.el7 will be installed

> --> Processing Dependency: python-srpm-macros for package:

> python-rpm-macros-3-34.el7.noarch

> ---> Package python2-rpm-macros.noarch 0:3-34.el7 will be installed

> --> Running transaction check

> ---> Package python-devel.x86_64 0:2.7.5-89.el7 will be installed

> --> Processing Dependency: python(x86-64) = 2.7.5-89.el7 for

> package: python-devel-2.7.5-89.el7.x86_64

> ---> Package python-srpm-macros.noarch 0:3-34.el7 will be installed

> --> Finished Dependency Resolution

> Error: Package: python-devel-2.7.5-89.el7.x86_64 (sl)

>            Requires: python(x86-64) = 2.7.5-89.el7

>            Installed: python-2.7.18-2.el7.x86_64 (installed)

>                python(x86-64) = 2.7.18-2.el7

>            Available: python-2.7.5-89.el7.x86_64 (sl)

>                python(x86-64) = 2.7.5-89.el7

>  You could try using --skip-broken to work around the problem

>  You could try running: rpm -Va --nofiles --nodigest

> [root@73f9ce4412a7 /]#

> 

> it looks like the python-devel package is not from the same build as

> the python package so therefore can't be installed.

> 

> I know that Python2 is no longer supported upstream, we are actively

> working on our port to Python3 but it's not quite there yet.

> 

> When can we expect the python-devel package to be updated?

> 

> Cheers

> 

> Adam


ATOM RSS1 RSS2