Discussion:
[users] php-pecl-apc-3.1.9-1.el6.rf.i686
Alfred Ganz
2011-09-03 02:46:53 UTC
Permalink
Gentlemen,

I just noticed that the introduction of php-pecl-apc-3.1.9-1.el6.rf.i686
looks like a newer version of a package (php-pecl-apc-3.1.3p1-1.2.el6.1.i686
to be specific) in the Centos-6 base. I thought that a while ago there was
a major effort to move newer versions of packages that existed in the
Centos/Rhel context to the extras repository.

What makes this case different?

Thanks, AG
--
----------------------------------------------------------------------
Alfred Ganz alfred-ganz:at:agci.com
AG Consulting, Inc. (203) 624-9667
440 Prospect Street # 11
New Haven, CT 06511
----------------------------------------------------------------------
Yury V. Zaytsev
2011-09-03 10:37:52 UTC
Permalink
Hi!
Post by Alfred Ganz
What makes this case different?
Nothing in particular, it's just an oversight on our part.

I RFX'ed the last couple of dozens of conflicting packages, but this was
a new one and since we don't have automated checks for it, it just
slipped through.

I have RFX'ed it on RHEL6, cleaned the package up and introduced proper
ABI tracking. It's up to Dag to rebuild and remove the old ones:

https://github.com/repoforge/rpms/issues/51
--
Sincerely yours,
Yury V. Zaytsev
Alfred Ganz
2011-09-03 02:46:53 UTC
Permalink
Gentlemen,

I just noticed that the introduction of php-pecl-apc-3.1.9-1.el6.rf.i686
looks like a newer version of a package (php-pecl-apc-3.1.3p1-1.2.el6.1.i686
to be specific) in the Centos-6 base. I thought that a while ago there was
a major effort to move newer versions of packages that existed in the
Centos/Rhel context to the extras repository.

What makes this case different?

Thanks, AG
--
----------------------------------------------------------------------
Alfred Ganz alfred-ganz:at:agci.com
AG Consulting, Inc. (203) 624-9667
440 Prospect Street # 11
New Haven, CT 06511
----------------------------------------------------------------------
Yury V. Zaytsev
2011-09-03 10:37:52 UTC
Permalink
Hi!
Post by Alfred Ganz
What makes this case different?
Nothing in particular, it's just an oversight on our part.

I RFX'ed the last couple of dozens of conflicting packages, but this was
a new one and since we don't have automated checks for it, it just
slipped through.

I have RFX'ed it on RHEL6, cleaned the package up and introduced proper
ABI tracking. It's up to Dag to rebuild and remove the old ones:

https://github.com/repoforge/rpms/issues/51
--
Sincerely yours,
Yury V. Zaytsev
Loading...