Re: [CentOS] md5sum mismatch between CentOS 6.4 and 6.5 repository

2013-12-09 Thread Ralf Aumüller
Hello,

On 12/09/2013 03:16 PM, Johnny Hughes wrote:
> Yes, it is signed by the same key ... but the rpm is not identical. (The
> difference being a different md5sum because rpm metadata (signature
> time) is different).
> 
> He does not say HOW the installation fails ... one would have to look at
> the kickstart file to see.

anaconda crashes while installing packages. Checking the log-files of the
traceback I found something about wrong md5sum of package python-slip-dbus.

> If the ks install is looking at a real 6.5 and pointing at it, it should
> work fine.  If he is pointing at something else, maybe not.  I would
> personally just delete the files in question and rsync again to make
> sure they are replaced.
> 
> Rsync, if it sees the same file and the same date, will not validate the
> crc without a -c switch ... that would take forever for a whole tree, so
> I would delete the files in question and sync again from a 6.5 tree.

That was the way I fixed the kickstart installation.

Thank You very much for Your explanation of the md5sum difference and best 
regards,

Ralf
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Centos6.5 Intel Corporation Centrino Advanced-N 6235 not working

2013-12-09 Thread Tom G. Christensen
On 10/12/13 07:02, Johan Vermeulen wrote:
> [root@jvermeulen ~]# dmesg | grep iwlwifi
> iwlwifi :03:00.0: PCI INT A ->  GSI 17 (level, low) ->  IRQ 17
> iwlwifi :03:00.0: setting latency timer to 64
> iwlwifi :03:00.0: irq 32 for MSI/MSI-X
> iwlwifi :03:00.0: firmware: requesting iwlwifi-6000g2b-6.ucode
> iwlwifi :03:00.0: request for firmware file 'iwlwifi-6000g2b-6.ucode' 
> failed.
> iwlwifi :03:00.0: no suitable firmware found!
> iwlwifi :03:00.0: PCI INT A disabled
>
$ rpm -qf /lib/firmware/iwlwifi-6000g2b-6.ucode
kernel-firmware-2.6.32-431.el6.noarch

Did you verify that the firmware file is available?

-tgc

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Centos6.5 Intel Corporation Centrino Advanced-N 6235 not working

2013-12-09 Thread Johan Vermeulen

Op 09-12-13 22:28, Andrew Holway schreef:
> Sorry :) not paying attention.
>
> modinfo iwlwifi and
>
> dmesg /var/log/messages "iwlwifi" (I think this is how it appears in dmesg)
>
> I have a feeling you will need the more recent drivers from elrepo.
>
> On 9 December 2013 21:20, Andrew Holway  wrote:
>> lspci -k pls.
>>
>> On 9 December 2013 21:20, Johan Vermeulen  wrote:
>>> Dear All,
>>>
>>> i'm working on this Centos6.5 laptop, fully updated
>>>
>>> *# uname -a**
>>> **Linux jvermeulen.ict 2.6.32-431.el6.x86_64 #1 SMP Fri Nov 22 03:15:09
>>> UTC 2013 x86_64 x86_64 x86_64 GNU/Linux*
>>>
>>> It's an Acer Aspire E1-571.
>>>
>>> I can't get the Intel Centrino N 6235 to work. I've used this card on
>>> several different types of  laptops and never
>>> had any trouble.
>>>
>>> I think I have the packages installed for this card :
>>>
>>> *[root@jvermeulen jvermeulen]# yum list installed | grep wireless**
>>> **wireless-tools.x86_64 1:29-5.1.1.el6   @base **
>>> **[root@jvermeulen jvermeulen]# yum list installed | grep iwl**
>>> **iwl100-firmware.noarch 39.31.5.1-1.el6
>>> @anaconda-CentOS-201207061011.x86_64/6.3**
>>> **iwl1000-firmware.noarch 1:39.31.5.1-1.el6
>>> @anaconda-CentOS-201207061011.x86_64/6.3**
>>> **iwl3945-firmware.noarch 15.32.2.9-4.el6
>>> @anaconda-CentOS-201207061011.x86_64/6.3**
>>> **iwl4965-firmware.noarch 228.61.2.24-2.1.el6
>>> @anaconda-CentOS-201207061011.x86_64/6.3**
>>> **iwl5000-firmware.noarch 8.83.5.1_1-1.el6_1.1
>>> @anaconda-CentOS-201207061011.x86_64/6.3**
>>> **iwl5150-firmware.noarch 8.24.2.2-1.el6
>>> @anaconda-CentOS-201207061011.x86_64/6.3**
>>> **iwl6000-firmware.noarch 9.221.4.1-1.el6  @base **
>>> **iwl6000g2a-firmware.noarch 17.168.5.3-1.el6
>>> @anaconda-CentOS-201207061011.x86_64/6.3**
>>> **iwl6050-firmware.noarch 41.28.5.1-2.el6
>>> @anaconda-CentOS-201207061011.x86_64/6.3**
>>> **python-iwlib.x86_64 0.1-1.2.el6  @base*
>>>
>>> and I see no EM:
>>>
>>> *03:00.0 Network controller: Intel Corporation Centrino Advanced-N 6235
>>> (rev 24)**
>>> **Subsystem: Intel Corporation Centrino Advanced-N 6235 AGN**
>>> **Flags: fast devsel, IRQ 17**
>>> **Memory at c050 (64-bit, non-prefetchable) [size=8K]**
>>> **Capabilities: [c8] Power Management version 3**
>>> **Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+**
>>> **Capabilities: [e0] Express Endpoint, MSI 00**
>>> **Capabilities: [100] Advanced Error Reporting**
>>> **Capabilities: [140] Device Serial Number b4-b6-76-ff-ff-5f-fc-cb**
>>> **Kernel modules: iwlwifi**
>>> **
>>> **[root@jvermeulen jvermeulen]# modprobe -v iwlwifi**
>>> **[root@jvermeulen jvermeulen]#*
>>>
>>> Still wireless is not showing up.
>>>
>>> *[root@jvermeulen jvermeulen]# iwconfig**
>>> **lono wireless extensions.**
>>> **
>>> **eth0  no wireless extensions.**
>>> **
>>> **virbr0no wireless extensions.**
>>> **
>>> **virbr0-nic  no wireless extensions.**
>>> **
>>> **ppp0  no wireless extensions.**
>>> **
>>> **tun0  no wireless extensions.*
>>>
>>> What am I doing wrong?
>>>
>>> Friendly regards, J.
>>>
>>> --
>>> Johan Vermeulen
>>> IT-medewerker
>>>
>>>
>>> Opensource Software is the future.
>>>
>>> ___
>>> CentOS mailing list
>>> CentOS@centos.org
>>> http://lists.centos.org/mailman/listinfo/centos
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos

Andrew,

thanks for helping me out.

[root@jvermeulen ~]# modinfo iwlwifi
filename: 
/lib/modules/2.6.32-431.el6.x86_64/kernel/drivers/net/wireless/iwlwifi/iwlwifi.ko
license:GPL
author: Copyright(c) 2003-2013 Intel Corporation 

version:in-tree:
description:Intel(R) Wireless WiFi driver for Linux
firmware:   iwlwifi-100-5.ucode
firmware:   iwlwifi-1000-5.ucode
firmware:   iwlwifi-135-6.ucode
firmware:   iwlwifi-105-6.ucode
firmware:   iwlwifi-2030-6.ucode
firmware:   iwlwifi-2000-6.ucode
firmware:   iwlwifi-5150-2.ucode
firmware:   iwlwifi-5000-5.ucode
firmware:   iwlwifi-6000g2b-6.ucode
firmware:   iwlwifi-6000g2a-5.ucode
firmware:   iwlwifi-6050-5.ucode
firmware:   iwlwifi-6000-4.ucode
firmware:   iwlwifi-3160-7.ucode
firmware:   iwlwifi-7260-7.ucode
srcversion: 10D42FE336952A12F17F028
alias:  pci:v8086d08B3sv*sd8570bc*sc*i*
alias:  pci:v8086d08B3sv*sd8470bc*sc*i*
alias:  pci:v8086d08B4sv*sd8270bc*sc*i*



depends:cfg80211
vermagic:   2.6.32-431.el6.x86_64 SMP mod_unload modversions
parm:   swcrypto:using crypto in software (default 0 [hardware]) 
(int)
parm:   11n_disable:disable 11n functionality, bitmap: 1: full, 
2: agg TX, 4: agg RX (uint)
parm:   amsdu_size_8K:enable 8K amsdu size (default 0) (int)
parm:  

Re: [CentOS] Centos6.5 Intel Corporation Centrino Advanced-N 6235 not working

2013-12-09 Thread Andrew Holway
Sorry :) not paying attention.

modinfo iwlwifi and

dmesg /var/log/messages "iwlwifi" (I think this is how it appears in dmesg)

I have a feeling you will need the more recent drivers from elrepo.

On 9 December 2013 21:20, Andrew Holway  wrote:
> lspci -k pls.
>
> On 9 December 2013 21:20, Johan Vermeulen  wrote:
>> Dear All,
>>
>> i'm working on this Centos6.5 laptop, fully updated
>>
>> *# uname -a**
>> **Linux jvermeulen.ict 2.6.32-431.el6.x86_64 #1 SMP Fri Nov 22 03:15:09
>> UTC 2013 x86_64 x86_64 x86_64 GNU/Linux*
>>
>> It's an Acer Aspire E1-571.
>>
>> I can't get the Intel Centrino N 6235 to work. I've used this card on
>> several different types of  laptops and never
>> had any trouble.
>>
>> I think I have the packages installed for this card :
>>
>> *[root@jvermeulen jvermeulen]# yum list installed | grep wireless**
>> **wireless-tools.x86_64 1:29-5.1.1.el6   @base **
>> **[root@jvermeulen jvermeulen]# yum list installed | grep iwl**
>> **iwl100-firmware.noarch 39.31.5.1-1.el6
>> @anaconda-CentOS-201207061011.x86_64/6.3**
>> **iwl1000-firmware.noarch 1:39.31.5.1-1.el6
>> @anaconda-CentOS-201207061011.x86_64/6.3**
>> **iwl3945-firmware.noarch 15.32.2.9-4.el6
>> @anaconda-CentOS-201207061011.x86_64/6.3**
>> **iwl4965-firmware.noarch 228.61.2.24-2.1.el6
>> @anaconda-CentOS-201207061011.x86_64/6.3**
>> **iwl5000-firmware.noarch 8.83.5.1_1-1.el6_1.1
>> @anaconda-CentOS-201207061011.x86_64/6.3**
>> **iwl5150-firmware.noarch 8.24.2.2-1.el6
>> @anaconda-CentOS-201207061011.x86_64/6.3**
>> **iwl6000-firmware.noarch 9.221.4.1-1.el6  @base **
>> **iwl6000g2a-firmware.noarch 17.168.5.3-1.el6
>> @anaconda-CentOS-201207061011.x86_64/6.3**
>> **iwl6050-firmware.noarch 41.28.5.1-2.el6
>> @anaconda-CentOS-201207061011.x86_64/6.3**
>> **python-iwlib.x86_64 0.1-1.2.el6  @base*
>>
>> and I see no EM:
>>
>> *03:00.0 Network controller: Intel Corporation Centrino Advanced-N 6235
>> (rev 24)**
>> **Subsystem: Intel Corporation Centrino Advanced-N 6235 AGN**
>> **Flags: fast devsel, IRQ 17**
>> **Memory at c050 (64-bit, non-prefetchable) [size=8K]**
>> **Capabilities: [c8] Power Management version 3**
>> **Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+**
>> **Capabilities: [e0] Express Endpoint, MSI 00**
>> **Capabilities: [100] Advanced Error Reporting**
>> **Capabilities: [140] Device Serial Number b4-b6-76-ff-ff-5f-fc-cb**
>> **Kernel modules: iwlwifi**
>> **
>> **[root@jvermeulen jvermeulen]# modprobe -v iwlwifi**
>> **[root@jvermeulen jvermeulen]#*
>>
>> Still wireless is not showing up.
>>
>> *[root@jvermeulen jvermeulen]# iwconfig**
>> **lono wireless extensions.**
>> **
>> **eth0  no wireless extensions.**
>> **
>> **virbr0no wireless extensions.**
>> **
>> **virbr0-nic  no wireless extensions.**
>> **
>> **ppp0  no wireless extensions.**
>> **
>> **tun0  no wireless extensions.*
>>
>> What am I doing wrong?
>>
>> Friendly regards, J.
>>
>> --
>> Johan Vermeulen
>> IT-medewerker
>>
>>
>> Opensource Software is the future.
>>
>> ___
>> CentOS mailing list
>> CentOS@centos.org
>> http://lists.centos.org/mailman/listinfo/centos
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Centos6.5 Intel Corporation Centrino Advanced-N 6235 not working

2013-12-09 Thread Andrew Holway
lspci -k pls.

On 9 December 2013 21:20, Johan Vermeulen  wrote:
> Dear All,
>
> i'm working on this Centos6.5 laptop, fully updated
>
> *# uname -a**
> **Linux jvermeulen.ict 2.6.32-431.el6.x86_64 #1 SMP Fri Nov 22 03:15:09
> UTC 2013 x86_64 x86_64 x86_64 GNU/Linux*
>
> It's an Acer Aspire E1-571.
>
> I can't get the Intel Centrino N 6235 to work. I've used this card on
> several different types of  laptops and never
> had any trouble.
>
> I think I have the packages installed for this card :
>
> *[root@jvermeulen jvermeulen]# yum list installed | grep wireless**
> **wireless-tools.x86_64 1:29-5.1.1.el6   @base **
> **[root@jvermeulen jvermeulen]# yum list installed | grep iwl**
> **iwl100-firmware.noarch 39.31.5.1-1.el6
> @anaconda-CentOS-201207061011.x86_64/6.3**
> **iwl1000-firmware.noarch 1:39.31.5.1-1.el6
> @anaconda-CentOS-201207061011.x86_64/6.3**
> **iwl3945-firmware.noarch 15.32.2.9-4.el6
> @anaconda-CentOS-201207061011.x86_64/6.3**
> **iwl4965-firmware.noarch 228.61.2.24-2.1.el6
> @anaconda-CentOS-201207061011.x86_64/6.3**
> **iwl5000-firmware.noarch 8.83.5.1_1-1.el6_1.1
> @anaconda-CentOS-201207061011.x86_64/6.3**
> **iwl5150-firmware.noarch 8.24.2.2-1.el6
> @anaconda-CentOS-201207061011.x86_64/6.3**
> **iwl6000-firmware.noarch 9.221.4.1-1.el6  @base **
> **iwl6000g2a-firmware.noarch 17.168.5.3-1.el6
> @anaconda-CentOS-201207061011.x86_64/6.3**
> **iwl6050-firmware.noarch 41.28.5.1-2.el6
> @anaconda-CentOS-201207061011.x86_64/6.3**
> **python-iwlib.x86_64 0.1-1.2.el6  @base*
>
> and I see no EM:
>
> *03:00.0 Network controller: Intel Corporation Centrino Advanced-N 6235
> (rev 24)**
> **Subsystem: Intel Corporation Centrino Advanced-N 6235 AGN**
> **Flags: fast devsel, IRQ 17**
> **Memory at c050 (64-bit, non-prefetchable) [size=8K]**
> **Capabilities: [c8] Power Management version 3**
> **Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+**
> **Capabilities: [e0] Express Endpoint, MSI 00**
> **Capabilities: [100] Advanced Error Reporting**
> **Capabilities: [140] Device Serial Number b4-b6-76-ff-ff-5f-fc-cb**
> **Kernel modules: iwlwifi**
> **
> **[root@jvermeulen jvermeulen]# modprobe -v iwlwifi**
> **[root@jvermeulen jvermeulen]#*
>
> Still wireless is not showing up.
>
> *[root@jvermeulen jvermeulen]# iwconfig**
> **lono wireless extensions.**
> **
> **eth0  no wireless extensions.**
> **
> **virbr0no wireless extensions.**
> **
> **virbr0-nic  no wireless extensions.**
> **
> **ppp0  no wireless extensions.**
> **
> **tun0  no wireless extensions.*
>
> What am I doing wrong?
>
> Friendly regards, J.
>
> --
> Johan Vermeulen
> IT-medewerker
>
>
> Opensource Software is the future.
>
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


[CentOS] Centos6.5 Intel Corporation Centrino Advanced-N 6235 not working

2013-12-09 Thread Johan Vermeulen
Dear All,

i'm working on this Centos6.5 laptop, fully updated

*# uname -a**
**Linux jvermeulen.ict 2.6.32-431.el6.x86_64 #1 SMP Fri Nov 22 03:15:09 
UTC 2013 x86_64 x86_64 x86_64 GNU/Linux*

It's an Acer Aspire E1-571.

I can't get the Intel Centrino N 6235 to work. I've used this card on 
several different types of  laptops and never
had any trouble.

I think I have the packages installed for this card :

*[root@jvermeulen jvermeulen]# yum list installed | grep wireless**
**wireless-tools.x86_64 1:29-5.1.1.el6   @base **
**[root@jvermeulen jvermeulen]# yum list installed | grep iwl**
**iwl100-firmware.noarch 39.31.5.1-1.el6 
@anaconda-CentOS-201207061011.x86_64/6.3**
**iwl1000-firmware.noarch 1:39.31.5.1-1.el6 
@anaconda-CentOS-201207061011.x86_64/6.3**
**iwl3945-firmware.noarch 15.32.2.9-4.el6 
@anaconda-CentOS-201207061011.x86_64/6.3**
**iwl4965-firmware.noarch 228.61.2.24-2.1.el6 
@anaconda-CentOS-201207061011.x86_64/6.3**
**iwl5000-firmware.noarch 8.83.5.1_1-1.el6_1.1 
@anaconda-CentOS-201207061011.x86_64/6.3**
**iwl5150-firmware.noarch 8.24.2.2-1.el6 
@anaconda-CentOS-201207061011.x86_64/6.3**
**iwl6000-firmware.noarch 9.221.4.1-1.el6  @base **
**iwl6000g2a-firmware.noarch 17.168.5.3-1.el6 
@anaconda-CentOS-201207061011.x86_64/6.3**
**iwl6050-firmware.noarch 41.28.5.1-2.el6 
@anaconda-CentOS-201207061011.x86_64/6.3**
**python-iwlib.x86_64 0.1-1.2.el6  @base*

and I see no EM:

*03:00.0 Network controller: Intel Corporation Centrino Advanced-N 6235 
(rev 24)**
**Subsystem: Intel Corporation Centrino Advanced-N 6235 AGN**
**Flags: fast devsel, IRQ 17**
**Memory at c050 (64-bit, non-prefetchable) [size=8K]**
**Capabilities: [c8] Power Management version 3**
**Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+**
**Capabilities: [e0] Express Endpoint, MSI 00**
**Capabilities: [100] Advanced Error Reporting**
**Capabilities: [140] Device Serial Number b4-b6-76-ff-ff-5f-fc-cb**
**Kernel modules: iwlwifi**
**
**[root@jvermeulen jvermeulen]# modprobe -v iwlwifi**
**[root@jvermeulen jvermeulen]#*

Still wireless is not showing up.

*[root@jvermeulen jvermeulen]# iwconfig**
**lono wireless extensions.**
**
**eth0  no wireless extensions.**
**
**virbr0no wireless extensions.**
**
**virbr0-nic  no wireless extensions.**
**
**ppp0  no wireless extensions.**
**
**tun0  no wireless extensions.*

What am I doing wrong?

Friendly regards, J.

-- 
Johan Vermeulen
IT-medewerker


Opensource Software is the future.

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] compat-openmpi issues after upgrade to CentOS 6.5

2013-12-09 Thread Tru Huynh
On Mon, Dec 09, 2013 at 04:23:47PM +0100, Tru Huynh wrote:
...
> 
> so the support for 1.5.3 is on purpose, no idea if both 1.4.3 and 1.5.3 should
> be both available at the same time, or if the support for 1.5.3 is also 
> backward
> compatible with 1.4.3. I would need to search ;)

I was too slow ;)

http://upstream-tracker.org/versions/openmpi.html
and 
http://upstream-tracker.org/compat_reports/openmpi/1.4.5_to_1.5/abi_compat_report.html
has the details on the ABI coverage between the 1.4/1.5 series.

Cheers,

Tru
-- 
Tru Huynh (mirrors, CentOS i386/x86_64 Package Maintenance)
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xBEFA581B


pgpmlcJ14ZvOW.pgp
Description: PGP signature
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] making a script into a service

2013-12-09 Thread Larry Martell
On Mon, Dec 9, 2013 at 9:05 AM, John Doe  wrote:
> From: Larry Martell 
>
>> We have a python script that is currently run from cron. We want to
>> make it into a service so it can be controlled with service
>> start/stop/restart. Can anyone point me at site that has instructions
>> on how to do this? I've googled but haven't found anything.
>
> http://fedoraproject.org/wiki/Packaging:SysVInitScript


Thanks!
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] making a script into a service

2013-12-09 Thread Larry Martell
On Mon, Dec 9, 2013 at 8:40 AM, Liam O'Toole  wrote:
> On 2013-12-09, Larry Martell  wrote:
>> On Mon, Dec 9, 2013 at 8:00 AM, Fabrizio Di Carlo
>> wrote:
>>> Try to use this
>>> http://www.jejik.com/articles/2007/02/a_simple_unix_linux_daemon_in_python/ 
>>> it
>>> allows you start/stop/restart the script using the following commands.
>>>
>>> python myscript.py start
>>> python myscript.py stop
>>> python myscript.py restart
>>>
>>>
>>> Source:
>>> http://stackoverflow.com/questions/16420092/how-to-make-python-script-run-as-service
>>
>>
>> Yes, I've seen that question and site. I want to be able to control it
>> with the service command. The technique on this site makes the script
>> a daemon, but that does not make it controllable with service.
>>
>>
>
> Assuming the first line of your script is
>
> #!/usr/bin/env python
>
> and the script is executable, then you can invoke it like this:
>
> myscript start
> myscript stop
> myscript restart
>
> If you then place the script in /etc/init.d/, you have yourself a
> service. See the 'service' man page.

Thanks!
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] compat-openmpi issues after upgrade to CentOS 6.5

2013-12-09 Thread Tru Huynh
On Mon, Dec 09, 2013 at 03:21:23PM +0100, Tor Halsan wrote:
> Just wondering if anyone can shed some light into an issue we are having 
> with compat-openmpi after upgrading CentOS to version 6.5
> 
> Some of our cluster applications are dependent on an older version of 
> OpenMPI, so we are using compat-openmpi. Up to CentOS 6.4 this was 
> version 1.4.3:
> 
> % /usr/lib64/compat-openmpi/bin/mpirun -V
> mpirun (Open MPI) 1.4.3
> 
> but after the upgrade to CentOS 6.5 it suddenly reports version 1.5.3:
> % /usr/lib64/compat-openmpi/bin/mpirun -V
> mpirun (Open MPI) 1.5.3
> 
> But rpm/yum still reports that version 1.4.3 is installed:
> 
> % rpm -qv compat-openmpi
> compat-openmpi-1.4.3-1.1.el6.x86_64
> 
> Is this deliberate, or has someone erred?

from the changelog:
* Wed Aug 14 2013 Jay Fenlason  1.4.3-2
* Also include 1.5.3 libraries so users of RHEL-6.5+ can run
  programs compiled on RHEL-6.2-
  Resolves: rhbz876315

* Thu Oct 13 2011 Jay Fenlason  1.4.3-1
- New compat package to make users of openmpi-1.4 on RHEL-6 happy.
  Resolves: rhbz741009

so the support for 1.5.3 is on purpose, no idea if both 1.4.3 and 1.5.3 should
be both available at the same time, or if the support for 1.5.3 is also backward
compatible with 1.4.3. I would need to search ;)

https://bugzilla.redhat.com/show_bug.cgi?id=876315 is not public :(

Cheers,

Tru

-- 
Tru Huynh (mirrors, CentOS i386/x86_64 Package Maintenance)
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xBEFA581B


pgp8wTVbeujpf.pgp
Description: PGP signature
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] compat-openmpi issues after upgrade to CentOS 6.5

2013-12-09 Thread Tor Halsan
On 09/12/13 16:11, Johnny Hughes wrote:
[...]
> The changelog contains this:
>
> compat-openmpi-1.4.3-1.1.el6.x86_64 [2.6 MiB] Changelog by Jay
> Fenlason (2013-08-14):
>
> * Also include 1.5.3 libraries so users of RHEL-6.5+ can run
>programs compiled on RHEL-6.2-
>Resolves: rhbz876315
>
>
> So, I would say that, yes, it is on purpose.

Thanks. Sorry for posting before reading the changelog properly.

-- 
Tor Halsan
Senior System Administrator
m: +47 900 25 135
tor.hal...@lithicon.com

Lithicon
- The integration of Digitalcore and Numerical Rocks

Lithicon Norway AS
Stiklestadveien 1
N‐7041 Trondheim, Norway

http://www.lithicon.com
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] compat-openmpi issues after upgrade to CentOS 6.5

2013-12-09 Thread Johnny Hughes
On 12/09/2013 08:21 AM, Tor Halsan wrote:
> Just wondering if anyone can shed some light into an issue we are having 
> with compat-openmpi after upgrading CentOS to version 6.5
>
> Some of our cluster applications are dependent on an older version of 
> OpenMPI, so we are using compat-openmpi. Up to CentOS 6.4 this was 
> version 1.4.3:
>
> % /usr/lib64/compat-openmpi/bin/mpirun -V
> mpirun (Open MPI) 1.4.3
>
> but after the upgrade to CentOS 6.5 it suddenly reports version 1.5.3:
> % /usr/lib64/compat-openmpi/bin/mpirun -V
> mpirun (Open MPI) 1.5.3
>
> But rpm/yum still reports that version 1.4.3 is installed:
>
> % rpm -qv compat-openmpi
> compat-openmpi-1.4.3-1.1.el6.x86_64
>
> Is this deliberate, or has someone erred?
>
> - Tor
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos
>

The changelog contains this:

compat-openmpi-1.4.3-1.1.el6.x86_64 [2.6 MiB] Changelog by Jay
Fenlason (2013-08-14):

* Also include 1.5.3 libraries so users of RHEL-6.5+ can run
  programs compiled on RHEL-6.2-
  Resolves: rhbz876315


So, I would say that, yes, it is on purpose.



signature.asc
Description: OpenPGP digital signature
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


[CentOS] compat-openmpi issues after upgrade to CentOS 6.5

2013-12-09 Thread Tor Halsan
Just wondering if anyone can shed some light into an issue we are having 
with compat-openmpi after upgrading CentOS to version 6.5

Some of our cluster applications are dependent on an older version of 
OpenMPI, so we are using compat-openmpi. Up to CentOS 6.4 this was 
version 1.4.3:

% /usr/lib64/compat-openmpi/bin/mpirun -V
mpirun (Open MPI) 1.4.3

but after the upgrade to CentOS 6.5 it suddenly reports version 1.5.3:
% /usr/lib64/compat-openmpi/bin/mpirun -V
mpirun (Open MPI) 1.5.3

But rpm/yum still reports that version 1.4.3 is installed:

% rpm -qv compat-openmpi
compat-openmpi-1.4.3-1.1.el6.x86_64

Is this deliberate, or has someone erred?

- Tor
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] md5sum mismatch between CentOS 6.4 and 6.5 repository

2013-12-09 Thread Johnny Hughes
On 12/09/2013 07:03 AM, Mogens Kjaer wrote:
> On 12/09/2013 01:43 PM, Johnny Hughes wrote:
>> Therefore the only difference is the signatures, and that difference is
>> the time being 1 second different in the rpm metadata ...
> A part from the timestamps being different, is it the same key that
> is used for signing i386 and x86_64 packages?
>
> And why does the OP get an error message?
>
> Is running hardlinkpy on the mirror tree a bad idea in general?
>
> Mogens
>

Yes, it is signed by the same key ... but the rpm is not identical. (The
difference being a different md5sum because rpm metadata (signature
time) is different).

He does not say HOW the installation fails ... one would have to look at
the kickstart file to see.

If the ks install is looking at a real 6.5 and pointing at it, it should
work fine.  If he is pointing at something else, maybe not.  I would
personally just delete the files in question and rsync again to make
sure they are replaced.

Rsync, if it sees the same file and the same date, will not validate the
crc without a -c switch ... that would take forever for a whole tree, so
I would delete the files in question and sync again from a 6.5 tree.



signature.asc
Description: OpenPGP digital signature
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] making a script into a service

2013-12-09 Thread John Doe
From: Larry Martell 

> We have a python script that is currently run from cron. We want to
> make it into a service so it can be controlled with service
> start/stop/restart. Can anyone point me at site that has instructions
> on how to do this? I've googled but haven't found anything.

http://fedoraproject.org/wiki/Packaging:SysVInitScript

JD
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] making a script into a service

2013-12-09 Thread Liam O'Toole
On 2013-12-09, Larry Martell  wrote:
> On Mon, Dec 9, 2013 at 8:00 AM, Fabrizio Di Carlo
> wrote:
>> Try to use this
>> http://www.jejik.com/articles/2007/02/a_simple_unix_linux_daemon_in_python/ 
>> it
>> allows you start/stop/restart the script using the following commands.
>>
>> python myscript.py start
>> python myscript.py stop
>> python myscript.py restart
>>
>>
>> Source:
>> http://stackoverflow.com/questions/16420092/how-to-make-python-script-run-as-service
>
>
> Yes, I've seen that question and site. I want to be able to control it
> with the service command. The technique on this site makes the script
> a daemon, but that does not make it controllable with service.
>
>

Assuming the first line of your script is

#!/usr/bin/env python

and the script is executable, then you can invoke it like this:

myscript start
myscript stop
myscript restart

If you then place the script in /etc/init.d/, you have yourself a
service. See the 'service' man page.

-- 

Liam


___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] making a script into a service

2013-12-09 Thread Matt Garman
Turn it into a daemon as described, then take a look at the existing
scripts in /etc/init.d/. There might even be a template in there iirc.
Your script will likely be a simple wrapper around your daemonized python
program.

After that, just do a "chkconfig --add “ where myscript is the
name of your script in /etc/init.d.
On Dec 9, 2013 7:05 AM, "Larry Martell"  wrote:

> On Mon, Dec 9, 2013 at 8:00 AM, Fabrizio Di Carlo
>  wrote:
> > Try to use this
> >
> http://www.jejik.com/articles/2007/02/a_simple_unix_linux_daemon_in_python/it
> > allows you start/stop/restart the script using the following commands.
> >
> > python myscript.py start
> > python myscript.py stop
> > python myscript.py restart
> >
> >
> > Source:
> >
> http://stackoverflow.com/questions/16420092/how-to-make-python-script-run-as-service
>
>
> Yes, I've seen that question and site. I want to be able to control it
> with the service command. The technique on this site makes the script
> a daemon, but that does not make it controllable with service.
>
>
> >
> > On Mon, Dec 9, 2013 at 1:54 PM, Larry Martell  >wrote:
> >
> >> We have a python script that is currently run from cron. We want to
> >> make it into a service so it can be controlled with service
> >> start/stop/restart. Can anyone point me at site that has instructions
> >> on how to do this? I've googled but haven't found anything.
> >> ___
> >> CentOS mailing list
> >> CentOS@centos.org
> >> http://lists.centos.org/mailman/listinfo/centos
> >>
> >
> >
> >
> > --
> > "The intuitive mind is a sacred gift and the rational mind is a faithful
> > servant. We have created a society that honors the servant and has
> > forgotten the gift." (A. Einstein)
> >
> > "La mente intuitiva è un dono sacro e la mente razionale è un fedele
> servo.
> > Noi abbiamo creato una società che onora il servo e ha dimenticato il
> > dono."  (A. Einstein)
> >
> > Fabrizio Di Carlo
> > ___
> > CentOS mailing list
> > CentOS@centos.org
> > http://lists.centos.org/mailman/listinfo/cento
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos
>
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] making a script into a service

2013-12-09 Thread Larry Martell
On Mon, Dec 9, 2013 at 8:00 AM, Fabrizio Di Carlo
 wrote:
> Try to use this
> http://www.jejik.com/articles/2007/02/a_simple_unix_linux_daemon_in_python/ it
> allows you start/stop/restart the script using the following commands.
>
> python myscript.py start
> python myscript.py stop
> python myscript.py restart
>
>
> Source:
> http://stackoverflow.com/questions/16420092/how-to-make-python-script-run-as-service


Yes, I've seen that question and site. I want to be able to control it
with the service command. The technique on this site makes the script
a daemon, but that does not make it controllable with service.


>
> On Mon, Dec 9, 2013 at 1:54 PM, Larry Martell wrote:
>
>> We have a python script that is currently run from cron. We want to
>> make it into a service so it can be controlled with service
>> start/stop/restart. Can anyone point me at site that has instructions
>> on how to do this? I've googled but haven't found anything.
>> ___
>> CentOS mailing list
>> CentOS@centos.org
>> http://lists.centos.org/mailman/listinfo/centos
>>
>
>
>
> --
> "The intuitive mind is a sacred gift and the rational mind is a faithful
> servant. We have created a society that honors the servant and has
> forgotten the gift." (A. Einstein)
>
> "La mente intuitiva è un dono sacro e la mente razionale è un fedele servo.
> Noi abbiamo creato una società che onora il servo e ha dimenticato il
> dono."  (A. Einstein)
>
> Fabrizio Di Carlo
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/cento
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] making a script into a service

2013-12-09 Thread Larry Martell
On Mon, Dec 9, 2013 at 8:00 AM, Andrew Holway  wrote:
> The keyword your looking for here is "daemonize".

I don't just want to make it into a daemon - I want to control it with
the service command.

>
>
>
> On 9 December 2013 12:54, Larry Martell  wrote:
>> We have a python script that is currently run from cron. We want to
>> make it into a service so it can be controlled with service
>> start/stop/restart. Can anyone point me at site that has instructions
>> on how to do this? I've googled but haven't found anything.
>> ___
>> CentOS mailing list
>> CentOS@centos.org
>> http://lists.centos.org/mailman/listinfo/centos
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] md5sum mismatch between CentOS 6.4 and 6.5 repository

2013-12-09 Thread Mogens Kjaer
On 12/09/2013 01:43 PM, Johnny Hughes wrote:
> Therefore the only difference is the signatures, and that difference is
> the time being 1 second different in the rpm metadata ...

A part from the timestamps being different, is it the same key that
is used for signing i386 and x86_64 packages?

And why does the OP get an error message?

Is running hardlinkpy on the mirror tree a bad idea in general?

Mogens

-- 
Mogens Kjaer, m...@lemo.dk
http://www.lemo.dk
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Build environment for totem-2.16.7-7.el5_6.1.src.rpm

2013-12-09 Thread Johnny Hughes
On 12/07/2013 11:09 AM, Michael Lampe wrote:
> This package has a build requirement 'gecko-devel' which is fulfilled by 
> 'xulrunner-devel'. But in the process of building the browser plugins 
> two tools named 'xpidl' and 'xpt_link' are necessary. They werde once 
> part of 'gecko-devel' but are now replaced by other tools. I haven't 
> found any package that has these tools all the way back to 5.0.
>
> Maybe the makers of CentOS can give a hint. After all this package was 
> build for C5.

The hint would be to use tree(s) as they existed at the build time of
the package to build them ... that is what we did and what Red Hat did.

If you look at the build date on the SRPM (rpm -qpi ), it is:
Build Date: Wed 30 Mar 2011 02:31:12 PM CDT

There is no rocket science here ... you can see there are a bunch of
xulrunner and other things that happened near that time ... you will
have to figure out which ones make it build (just like we do :D ).

I will do this for you ... here is a copy of the exact content of the
packages in the buildroot at the time we built it (attached)

Thanks,
Johnny Hughes

 Package   Arch Version   Repository   Size

Installing:
 buildsys-buildnoarch   0.5-6.el5.centos.7buildsys2.6 k
Installing for dependencies:
 MAKEDEV   x86_64   3.23-1.2  os  135 k
 SysVinit  x86_64   2.86-15.el5   os  117 k
 audit-libsx86_64   1.7.18-2.el5  os   78 k
 basesystemnoarch   8.0-5.1.1.el5.centos  os  2.8 k
 bash  x86_64   3.2-24.el5os  1.9 M
 binutils  x86_64   2.17.50.0.6-14.el5os  2.9 M
 bzip2 x86_64   1.0.3-6.el5_5 os   50 k
 bzip2-libsx86_64   1.0.3-6.el5_5 os   35 k
 centos-releasex86_64   10:5-6.el5.centos.1   os   20 k
 centos-release-notes  x86_64   5.6-0 os   40 k
 chkconfig x86_64   1.3.30.2-2.el5os  159 k
 coreutils x86_64   5.97-23.el5_6.4   c5-staged   3.5 M
 cpio  x86_64   2.6-23.el5_4.1os  122 k
 cpp   x86_64   4.1.2-50.el5  os  2.9 M
 cracklib  x86_64   2.8.9-3.3 os   63 k
 cracklib-dictsx86_64   2.8.9-3.3 os  3.3 M
 crontabs  noarch   1.10-8os  5.0 k
 db4   x86_64   4.3.29-10.el5_5.2 os  899 k
 device-mapper x86_64   1.02.55-2.el5 os  797 k
 device-mapper-event   x86_64   1.02.55-2.el5 os   21 k
 device-mapper-multipath   x86_64   0.4.7-42.el5  os  3.0 M
 diffutils x86_64   2.8.1-15.2.3.el5  os  211 k
 dmraidx86_64   1.0.0.rc13-63.el5 os  741 k
 dmraid-events x86_64   1.0.0.rc13-63.el5 os   24 k
 e2fsprogs x86_64   1.39-23.el5_5.1   os  995 k
 e2fsprogs-libsx86_64   1.39-23.el5_5.1   os  118 k
 elfutils  x86_64   0.137-3.el5   os  215 k
 elfutils-libelf   x86_64   0.137-3.el5   os   53 k
 elfutils-libs x86_64   0.137-3.el5   os  183 k
 ethtool   x86_64   6-4.el5   os   64 k
 expat x86_64   1.95.8-8.3.el5_5.3os   76 k
 file  x86_64   4.17-15.el5_3.1   os  318 k
 filesystemx86_64   2.4.0-3.el5   os  1.0 M
 findutils x86_64   1:4.2.27-6.el5os  294 k
 gawk  x86_64   3.1.5-14.el5  os  1.8 M
 gcc   x86_64   4.1.2-50.el5  os  5.3 M
 gcc-c++   x86_64   4.1.2-50.el5  os  3.8 M
 gdbm  x86_64   1.8.0-26.2.1  os   27 k
 glib2 x86_64   2.12.3-4.el5_3.1  os  693 k
 glibc x86_64   2.5-58os  4.8 M
 glibc-common  x86_64   2.5-58os   16 M
 glibc-devel   x86_64   2.5-58os  2.4 M
 glibc-headers x86_64   2.5-58os  593 k
 grep  x86_64   2.5.1-55.el5  os  176 k
 gzip   

Re: [CentOS] making a script into a service

2013-12-09 Thread Fabrizio Di Carlo
Try to use this
http://www.jejik.com/articles/2007/02/a_simple_unix_linux_daemon_in_python/ it
allows you start/stop/restart the script using the following commands.

python myscript.py start
python myscript.py stop
python myscript.py restart


Source:
http://stackoverflow.com/questions/16420092/how-to-make-python-script-run-as-service

On Mon, Dec 9, 2013 at 1:54 PM, Larry Martell wrote:

> We have a python script that is currently run from cron. We want to
> make it into a service so it can be controlled with service
> start/stop/restart. Can anyone point me at site that has instructions
> on how to do this? I've googled but haven't found anything.
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos
>



-- 
"The intuitive mind is a sacred gift and the rational mind is a faithful
servant. We have created a society that honors the servant and has
forgotten the gift." (A. Einstein)

"La mente intuitiva è un dono sacro e la mente razionale è un fedele servo.
Noi abbiamo creato una società che onora il servo e ha dimenticato il
dono."  (A. Einstein)

Fabrizio Di Carlo
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] making a script into a service

2013-12-09 Thread Andrew Holway
The keyword your looking for here is "daemonize".



On 9 December 2013 12:54, Larry Martell  wrote:
> We have a python script that is currently run from cron. We want to
> make it into a service so it can be controlled with service
> start/stop/restart. Can anyone point me at site that has instructions
> on how to do this? I've googled but haven't found anything.
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


[CentOS] making a script into a service

2013-12-09 Thread Larry Martell
We have a python script that is currently run from cron. We want to
make it into a service so it can be controlled with service
start/stop/restart. Can anyone point me at site that has instructions
on how to do this? I've googled but haven't found anything.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] md5sum mismatch between CentOS 6.4 and 6.5 repository

2013-12-09 Thread Johnny Hughes
On 12/09/2013 06:21 AM, Johnny Hughes wrote:
> On 12/07/2013 09:07 AM, Mogens Kjaer wrote:
>> On 12/06/2013 12:49 PM, Lars Hecking wrote:
>>> Something got mixed up somewhere. The first one (md5 20bb...) is from the 
>>> x86_64
>>>   branch, both 6.4 and 6.5, and the second one (md5 d37f...) is from the 
>>> i386
>>>   branch, also 6.4 and 6.5.
>>>
>>> d37fe4404a7a5fdb27b29f9b5ed09c73  
>>> ./6.4/os/i386/Packages/python-slip-dbus-0.2.20-1.el6_2.noarch.rpm
>>> 20bb02e6f3b7b71e09dcaff7f3b0ca02  
>>> ./6.4/os/x86_64/Packages/python-slip-dbus-0.2.20-1.el6_2.noarch.rpm
>>> d37fe4404a7a5fdb27b29f9b5ed09c73  
>>> ./6.5/os/i386/Packages/python-slip-dbus-0.2.20-1.el6_2.noarch.rpm
>>> 20bb02e6f3b7b71e09dcaff7f3b0ca02  
>>> ./6.5/os/x86_64/Packages/python-slip-dbus-0.2.20-1.el6_2.noarch.rpm
>> Hm, am I the only mirror maintainer that runs hardlinkpy on the tree
>> after each mirror?
>>
>> Why are there different md5sum's on these files?
>>
>> They are noarch rpms, so they should be identical in i386 and x86_64?
>>
>> I get the following:
>>
>> # md5sum `locate python-slip-dbus-0.2.20-1.el6_2.noarch.rpm`
>> d37fe4404a7a5fdb27b29f9b5ed09c73 
>> /var/ftp/pub/mirrors/centos/6.4/os/i386/Packages/python-slip-dbus-0.2.20-1.el6_2.noarch.rpm
>> 20bb02e6f3b7b71e09dcaff7f3b0ca02 
>> /var/ftp/pub/mirrors/centos/6.4/os/x86_64/Packages/python-slip-dbus-0.2.20-1.el6_2.noarch.rpm
>> d37fe4404a7a5fdb27b29f9b5ed09c73 
>> /var/ftp/pub/mirrors/centos/6.5/os/i386/Packages/python-slip-dbus-0.2.20-1.el6_2.noarch.rpm
>> d37fe4404a7a5fdb27b29f9b5ed09c73 
>> /var/ftp/pub/mirrors/centos/6.5/os/x86_64/Packages/python-slip-dbus-0.2.20-1.el6_2.noarch.rpm
>>
>> and:
>> # ls -li `locate python-slip-dbus-0.2.20-1.el6_2.noarch.rpm`
>> 98845547 -rw-rw-r-- 3 mk 500 30844 Mar 26  2012 
>> /var/ftp/pub/mirrors/centos/6.4/os/i386/Packages/python-slip-dbus-0.2.20-1.el6_2.noarch.rpm
>> 98315857 -rw-rw-r-- 1 mk 500 30844 Mar 26  2012 
>> /var/ftp/pub/mirrors/centos/6.4/os/x86_64/Packages/python-slip-dbus-0.2.20-1.el6_2.noarch.rpm
>> 98845547 -rw-rw-r-- 3 mk 500 30844 Mar 26  2012 
>> /var/ftp/pub/mirrors/centos/6.5/os/i386/Packages/python-slip-dbus-0.2.20-1.el6_2.noarch.rpm
>> 98845547 -rw-rw-r-- 3 mk 500 30844 Mar 26  2012 
>> /var/ftp/pub/mirrors/centos/6.5/os/x86_64/Packages/python-slip-dbus-0.2.20-1.el6_2.noarch.rpm
>>
>> Mogens
>>
> They would not necessarily have the exact same md5sum just because they
> are noarch.  The way mock compiles RPMs, it would be built on each
> builder separately.  The possibility exists that something very minor
> can (and sometimes does) happen to make things not exact.  I will
> analyze these an tell you the difference in an upcoming e-mail.
>
> We have changed our policy and now we will use the same noarch file,
> from one of the arches, on both if it exist in the arches.  That policy
> did indeed cause a change in the MD5SUM as they were different before. 
> Again, I'll post in another e-mail what is different between the two,
> but this is as expected.
>
> It should not happen any more moving forward though, as we will only
> ever release ONE noarch file in future, regardless of it they built
> slightly differently from the builders.
>

OK, the only difference on these RPMs is the signature (it happened at a
different time, by one second).

If you look at "rpm -qpi" you will see one of them was signed at:

Signature   : RSA/SHA1, Mon 26 Mar 2012 08:36:33 AM CDT, Key ID
0946fca2c105b9de

the other:

Signature   : RSA/SHA1, Mon 26 Mar 2012 08:36:32 AM CDT, Key ID
0946fca2c105b9de

(they were 2 separate files, produced in two separate build trees, and
therefore have 2 separate signature times)

However, if you do this to each of the files to remove the signatures:

rpm --delsign python-slip-dbus-0.2.20-1.el6_2.noarch.rpm

then do an md5sum, you will see that underlying (and unsigned) rpms have
identical md5sums of:

[johnny@m4500n 6.5]$ md5sum python-slip-dbus-0.2.20-1.el6_2.noarch.rpm
8cb0c87fd4942673c79c304d3c29aedb  python-slip-dbus-0.2.20-1.el6_2.noarch.rpm

[johnny@m4500n 6.5]$ cd ../6.4/

[johnny@m4500n 6.4]$ md5sum python-slip-dbus-0.2.20-1.el6_2.noarch.rpm
8cb0c87fd4942673c79c304d3c29aedb  python-slip-dbus-0.2.20-1.el6_2.noarch.rpm

Also, the content of each RPM is identical at these values:

511a4571af6e42e130c43bfff2507863 
./usr/lib/python2.6/site-packages/slip.dbus-0.2.20-py2.6.egg-info
01bb823d18266732b2cb24d7ea1d693b 
./usr/lib/python2.6/site-packages/slip/dbus/__init__.pyc
77ec375c396560fc4dd8bf0160831cfa 
./usr/lib/python2.6/site-packages/slip/dbus/bus.pyo
426ba8cb64e3ce60a40042ce961faebc 
./usr/lib/python2.6/site-packages/slip/dbus/proxies.pyo
5d5bab55941cb57d18bddb09dc1993bb 
./usr/lib/python2.6/site-packages/slip/dbus/proxies.py
01bb823d18266732b2cb24d7ea1d693b 
./usr/lib/python2.6/site-packages/slip/dbus/__init__.pyo
89073c18b01d301eefd7169fc08360fa 
./usr/lib/python2.6/site-packages/slip/dbus/bus.py
dc7e59367bab048fc3bca4fc94e2f5fc 
./usr/lib/python2.6/site-packages/slip/dbus/mainloop.pyc
3010ee109154

Re: [CentOS] md5sum mismatch between CentOS 6.4 and 6.5 repository

2013-12-09 Thread Johnny Hughes
On 12/07/2013 09:07 AM, Mogens Kjaer wrote:
> On 12/06/2013 12:49 PM, Lars Hecking wrote:
>> Something got mixed up somewhere. The first one (md5 20bb...) is from the 
>> x86_64
>>   branch, both 6.4 and 6.5, and the second one (md5 d37f...) is from the i386
>>   branch, also 6.4 and 6.5.
>>
>> d37fe4404a7a5fdb27b29f9b5ed09c73  
>> ./6.4/os/i386/Packages/python-slip-dbus-0.2.20-1.el6_2.noarch.rpm
>> 20bb02e6f3b7b71e09dcaff7f3b0ca02  
>> ./6.4/os/x86_64/Packages/python-slip-dbus-0.2.20-1.el6_2.noarch.rpm
>> d37fe4404a7a5fdb27b29f9b5ed09c73  
>> ./6.5/os/i386/Packages/python-slip-dbus-0.2.20-1.el6_2.noarch.rpm
>> 20bb02e6f3b7b71e09dcaff7f3b0ca02  
>> ./6.5/os/x86_64/Packages/python-slip-dbus-0.2.20-1.el6_2.noarch.rpm
> Hm, am I the only mirror maintainer that runs hardlinkpy on the tree
> after each mirror?
>
> Why are there different md5sum's on these files?
>
> They are noarch rpms, so they should be identical in i386 and x86_64?
>
> I get the following:
>
> # md5sum `locate python-slip-dbus-0.2.20-1.el6_2.noarch.rpm`
> d37fe4404a7a5fdb27b29f9b5ed09c73 
> /var/ftp/pub/mirrors/centos/6.4/os/i386/Packages/python-slip-dbus-0.2.20-1.el6_2.noarch.rpm
> 20bb02e6f3b7b71e09dcaff7f3b0ca02 
> /var/ftp/pub/mirrors/centos/6.4/os/x86_64/Packages/python-slip-dbus-0.2.20-1.el6_2.noarch.rpm
> d37fe4404a7a5fdb27b29f9b5ed09c73 
> /var/ftp/pub/mirrors/centos/6.5/os/i386/Packages/python-slip-dbus-0.2.20-1.el6_2.noarch.rpm
> d37fe4404a7a5fdb27b29f9b5ed09c73 
> /var/ftp/pub/mirrors/centos/6.5/os/x86_64/Packages/python-slip-dbus-0.2.20-1.el6_2.noarch.rpm
>
> and:
> # ls -li `locate python-slip-dbus-0.2.20-1.el6_2.noarch.rpm`
> 98845547 -rw-rw-r-- 3 mk 500 30844 Mar 26  2012 
> /var/ftp/pub/mirrors/centos/6.4/os/i386/Packages/python-slip-dbus-0.2.20-1.el6_2.noarch.rpm
> 98315857 -rw-rw-r-- 1 mk 500 30844 Mar 26  2012 
> /var/ftp/pub/mirrors/centos/6.4/os/x86_64/Packages/python-slip-dbus-0.2.20-1.el6_2.noarch.rpm
> 98845547 -rw-rw-r-- 3 mk 500 30844 Mar 26  2012 
> /var/ftp/pub/mirrors/centos/6.5/os/i386/Packages/python-slip-dbus-0.2.20-1.el6_2.noarch.rpm
> 98845547 -rw-rw-r-- 3 mk 500 30844 Mar 26  2012 
> /var/ftp/pub/mirrors/centos/6.5/os/x86_64/Packages/python-slip-dbus-0.2.20-1.el6_2.noarch.rpm
>
> Mogens
>

They would not necessarily have the exact same md5sum just because they
are noarch.  The way mock compiles RPMs, it would be built on each
builder separately.  The possibility exists that something very minor
can (and sometimes does) happen to make things not exact.  I will
analyze these an tell you the difference in an upcoming e-mail.

We have changed our policy and now we will use the same noarch file,
from one of the arches, on both if it exist in the arches.  That policy
did indeed cause a change in the MD5SUM as they were different before. 
Again, I'll post in another e-mail what is different between the two,
but this is as expected.

It should not happen any more moving forward though, as we will only
ever release ONE noarch file in future, regardless of it they built
slightly differently from the builders.

Thanks,
Johnny Hughes





signature.asc
Description: OpenPGP digital signature
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos