[CentOS-devel] Pam x86_64 and i686 have conflicting man pages

Tue Jun 24 10:24:02 UTC 2014
Ljubomir Ljubojevic <centos at plnet.rs>

On 06/24/2014 11:24 AM, Karanbir Singh wrote:
> On 06/24/2014 10:17 AM, Anssi Johansson wrote:
>> 24.6.2014 10.50, Ljubomir Ljubojevic kirjoitti:
>>> I tried to install qt-mobility.i686 and qtwebkit.i686 from Fedora so I
>>> can install Skype.
>>>
>>> It demanded a ton of packages and among them was pam.i686. Transaction
>>> stopped with error:
>>>
>>>
>>> Transaction check error:
>>>      file /usr/share/man/man8/faillock.8.gz from install of
>>> pam-1.1.8-9.el7.i686 conflicts with file from package pam-1.1.8-9.el7.x86_64
>>>      file /usr/share/man/man8/pam_env.8.gz from install of
>>> pam-1.1.8-9.el7.i686 conflicts with file from package pam-1.1.8-9.el7.x86_64
>>>      file /usr/share/man/man8/pam_faillock.8.gz from install of
>>> pam-1.1.8-9.el7.i686 conflicts with file from package pam-1.1.8-9.el7.x86_64
>>>      file /usr/share/man/man8/pam_unix.8.gz from install of
>>> pam-1.1.8-9.el7.i686 conflicts with file from package pam-1.1.8-9.el7.x86_64
>>>      file /usr/share/man/man8/pwhistory_helper.8.gz from install of
>>> pam-1.1.8-9.el7.i686 conflicts with file from package pam-1.1.8-9.el7.x86_64
>>
>> See http://bugs.centos.org/view.php?id=7182
>>
>
> i wonder why people are still using older tree's :(
>
> going to go remove those..
>
>

I actually used CentOS Blog post: 
http://seven.centos.org/2014/06/centos-7-public-qa-release/ to install C7.

It says:

  Edit: Even though we don’t yet have an installable tree in place, you 
can point an existing el7beta/el7rc install to the buildlogs repo with 
the following yum repo definitions (for example 
/etc/yum.repos.d/centos-buildlogs.repo) :


[centos-qa-03]
name=CentOS Open QA – c7.00.03
baseurl=http://buildlogs.centos.org/c7.00.03/
enabled=1
gpgcheck=0

[centos-qa-04]
name=CentOS Open QA – c7.00.04
baseurl=http://buildlogs.centos.org/c7.00.04/
enabled=1
gpgcheck=0


Since I read something about some later trees needing older tree (can't 
remember when and for what), and seeing on official Blog that I should 
use both tree's, I just followed instructions. That, and I guess my 
admin brain kicked in and (in subconsciousness) rationalizes that 04 is 
newer then 03 and I will get latest version of packages.


Then I used post on the same Blog: 
http://seven.centos.org/2014/06/centos-7-nightly-builds-and-live-media-iso-images/ 
  to add
Repo for "latest":
http://buildlogs.centos.org/centos/7/os/x86_64-latest


Since it was late last night, and I was busy doing other things, and 
since no mention of
"These packages should ABSOLUTELY NOT be used on anything that is even
slightly important .. although, you may be able to point to a newer repo
and do something like "yum distro-sync full" to get all the new packages.

That said, be careful with these packages and don't keep/use them except
for this testing.  Once we get a stabilized tree and that is released,
then we can use that for real production things." was on official Blog, 
even tho I posted this same text on facebook post, I FORGOT ALL about it 
until I started to read these responses.

So I patched it up really quickly and my consciousness did not think 
about distro-sync.


-- 
Ljubomir Ljubojevic
(Love is in the Air)
PL Computers
Serbia, Europe

StarOS, Mikrotik and CentOS/RHEL/Linux consultant