but this still should be reflected in local macros,
we should not have to man-change this macro for each rpm
package rebuild
it's not how it used to be as far as I can remember
if packages from the repos come 6_5 system-wide relevant
macro should match it
any specific reason why it should not?
On 11/21/2012 12:16 PM, Pat Riehecky wrote:
On 11/21/2012 01:02 PM, Orion Poplawski wrote:
On 11/21/2012 11:49 AM, Pat Riehecky wrote:
On 11/21/2012 12:44 PM, Orion Poplawski wrote:
It appears that SL packages are being built with a different "dist" rpm
macro than is in the sl-release package.
On 11/21/2012 01:02 PM, Orion Poplawski wrote:
On 11/21/2012 11:49 AM, Pat Riehecky wrote:
On 11/21/2012 12:44 PM, Orion Poplawski wrote:
It appears that SL packages are being built with a different "dist" rpm
macro than is in the sl-release package. e.g.:
postgresql.x86_648.4.13-1.el6_3
On 11/21/2012 11:49 AM, Pat Riehecky wrote:
On 11/21/2012 12:44 PM, Orion Poplawski wrote:
It appears that SL packages are being built with a different "dist" rpm
macro than is in the sl-release package. e.g.:
postgresql.x86_648.4.13-1.el6_3 sl-security
But the dist macro in sl-rele
On 11/21/2012 12:44 PM, Orion Poplawski wrote:
It appears that SL packages are being built with a different "dist"
rpm macro than is in the sl-release package. e.g.:
postgresql.x86_648.4.13-1.el6_3 sl-security
But the dist macro in sl-release-6.3-1 is still "el6", not "el6_3".
So
