 
| Subject: | |
| From: | |
| Reply To: | |
| Date: | Wed, 7 Nov 2018 16:10:47 -0600 |
| Content-Type: | text/plain |
| Parts/Attachments: |
|
|
Good catch!
I've got those fixed up and rebuilding the repodata now.
Pat
On 11/7/18 3:44 PM, Kraus, Dave (GE Healthcare) wrote:
> Top-posting because this may be long...
>
> I merged this repo with our 7.5+updates through yesterday, minus our excludes. Still working through obsoleted packages vs. missing updates, so bear with me.
>
> And as it turns out, it got much better as I was writing this, investigating, and working through possibly broken proxies.
>
> From repoclosure:
>
> package: ctdb-4.7.1-9.el7_5.x86_64
> unresolved deps:
> samba-client-libs = 0:4.7.1-9.el7_5
> libtime-basic-samba4.so(SAMBA_4.7.1)(64bit)
> libtdb-wrap-samba4.so(SAMBA_4.7.1)(64bit)
> libtalloc-report-samba4.so(SAMBA_4.7.1)(64bit)
> libsys-rw-samba4.so(SAMBA_4.7.1)(64bit)
> libsocket-blocking-samba4.so(SAMBA_4.7.1)(64bit)
> libsamba-debug-samba4.so(SAMBA_4.7.1)(64bit)
> libreplace-samba4.so(SAMBA_4.7.1)(64bit)
> libiov-buf-samba4.so(SAMBA_4.7.1)(64bit)
>
> package: ctdb-tests-4.7.1-9.el7_5.x86_64
> unresolved deps:
> samba-client-libs = 0:4.7.1-9.el7_5
> libtime-basic-samba4.so(SAMBA_4.7.1)(64bit)
> libtdb-wrap-samba4.so(SAMBA_4.7.1)(64bit)
> libsys-rw-samba4.so(SAMBA_4.7.1)(64bit)
> libsocket-blocking-samba4.so(SAMBA_4.7.1)(64bit)
> libsamba-debug-samba4.so(SAMBA_4.7.1)(64bit)
> libreplace-samba4.so(SAMBA_4.7.1)(64bit)
> libiov-buf-samba4.so(SAMBA_4.7.1)(64bit)
>
> # ctdb* comes from the samba package, so may be obsoleted as samba is updated from 4.7.1-9 to 4.8.3-4
>
> package: glusterfs-geo-replication-3.8.4-54.15.sl7.x86_64
> unresolved deps:
> glusterfs(x86-64) = 0:3.8.4-54.15.sl7
> package: glusterfs-server-3.8.4-54.15.sl7.x86_64
> unresolved deps:
> glusterfs-libs(x86-64) = 0:3.8.4-54.15.sl7
> glusterfs-fuse(x86-64) = 0:3.8.4-54.15.sl7
> glusterfs-client-xlators(x86-64) = 0:3.8.4-54.15.sl7
> glusterfs-cli(x86-64) = 0:3.8.4-54.15.sl7
> glusterfs-api(x86-64) = 0:3.8.4-54.15.sl7
> glusterfs(x86-64) = 0:3.8.4-54.15.sl7
>
> # gluster seems to have been updated from 3.8.4-54 to 3.12.2-18. Glusterfs-geo-replication may be obsoleted? Pat, I know you're patching to enable building glusterfs-server, so maybe that got missed?
>
> package: kmod-kvdo-6.1.0.181-17.el7_5.x86_64
> unresolved deps:
> kernel(dm_unregister_target) = 0:0x35ba4186
> kernel(dm_register_target) = 0:0xd3f9ecc7
> kernel(dm_put_device) = 0:0xe484e3b5
> kernel(dm_get_device) = 0:0x602cd186
>
> # Not sure on this one. Other kmods had explicit kernels they needed. This may be obsolete or at least needs rebuild. I may remove it from our distro either way at this point.
>
> So, a couple more for you to look at or tell me I have obsoletes.
>
> Looking good otherwise.
>
> On 11/7/18, 12:54 PM, "[log in to unmask] on behalf of Pat Riehecky" <[log in to unmask] on behalf of [log in to unmask]> wrote:
>
> On 11/7/18 12:30 PM, Orion Poplawski wrote:
> > On 11/07/2018 09:01 AM, Pat Riehecky wrote:
> >> Thanks to everyone who reported missing packages.
> >>
> >> I believe the dependencies are now resolved and additional security packages
> >> are added.
> >>
> >> Pat
> > I think you are still missing pytalloc 2.1.13:
> >
> > # yum --enablerepo=sl-testing upgrade libtalloc libuuid pytalloc
> > Loaded plugins: versionlock
> > sl-testing |
> > 3.0 kB 00:00:00
> > Resolving Dependencies
> > --> Running transaction check
> > ---> Package libtalloc.x86_64 0:2.1.10-1.el7 will be updated
> > --> Processing Dependency: libtalloc = 2.1.10-1.el7 for package:
> > pytalloc-2.1.10-1.el7.x86_64
> > ---> Package libtalloc.x86_64 0:2.1.13-1.el7 will be an update
> > --> Running transaction check
> > ---> Package libtalloc.i686 0:2.1.10-1.el7 will be installed
> > ---> Package libtalloc.x86_64 0:2.1.10-1.el7 will be updated
> > --> Finished Dependency Resolution
> > Error: Multilib version problems found. This often means that the root
> > cause is something else and multilib version checking is just
> > pointing out that there is a problem. Eg.:
> >
> > 1. You have an upgrade for libtalloc which is missing some
> > dependency that another package requires. Yum is trying to
> > solve this by installing an older version of libtalloc of the
> > different architecture. If you exclude the bad architecture
> > yum will tell you what the root cause is (which package
> > requires what). You can try redoing the upgrade with
> > --exclude libtalloc.otherarch ... this should give you an error
> > message showing the root cause of the problem.
> >
> > 2. You have multiple architectures of libtalloc installed, but
> > yum can only see an upgrade for one of those architectures.
> > If you don't want/need both architectures anymore then you
> > can remove the one with the missing update and everything
> > will work.
> >
> > 3. You have duplicate versions of libtalloc installed already.
> > You can use "yum check" to get yum show these errors.
> >
> > ...you can also use --setopt=protected_multilib=false to remove
> > this checking, however this is almost never the correct thing to
> > do as something else is very likely to go wrong (often causing
> > much more problems).
> >
> > Protected multilib versions: libtalloc-2.1.10-1.el7.i686 !=
> > libtalloc-2.1.13-1.el7.x86_64
> >
>
> That will teach me to multi-task....
>
> Thanks for finding these so quickly!
>
> In theory now each update id is fully complete within the testing repo
> and installable for SL7.0+
>
> Pat
>
> --
> Pat Riehecky
>
> Fermi National Accelerator Laboratory
> http://www.fnal.gov
> https://urldefense.proofpoint.com/v2/url?u=http-3A__www.scientificlinux.org&d=DwIGaQ&c=gRgGjJ3BkIsb5y6s49QqsA&r=OAMtP0DWou0nlXG7Kmxo2enjXJfwb1DXS9fwcaESuTE&m=P17V0S4sGQn9a7zmz7HMM4xL13NIOACi90150PlSXAI&s=VEfFO-CcsAycv_pyxApXENi8JLZzuqvtvBMJesfMtDw&e=
>
>
--
Pat Riehecky
Fermi National Accelerator Laboratory
www.fnal.gov
www.scientificlinux.org
|
|
|
