[Rpm-maint] RPM 4.13.1 released!

[Panu Matilainen]

On 03/29/2018 06:00 PM, Michael Schroeder wrote:
> On Wed, Mar 28, 2018 at 04:02:16PM +0300, Panu Matilainen wrote:
>> The reason for the "unexpected" rich dependency backport is that we failed
>> to add a new rpmlib() dependency tracker when adding these new dependencies,
>> and thus rpm 4.13.0* wont refuse to touch packages using them as it should.
> 
> Hmm, I wonder why that is so. It shouldn't be able to parse the new
> rich dependencies and thus fail in the dependency check.

Yes that's actually what happens, but it's not all that helpful for 
identifying the problem, it looks more like there's something wrong with 
the package than missing rpm capability. Not that failing with rpmlib() 
dependencies is terribly helpful either, but at least those are easier 
to google :)

	- Panu -