Re: [Rpm-maint] RPM 4.13.1 released!

2018-04-03 Thread 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 -
___
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint

Re: [Rpm-maint] RPM 4.13.1 released!

2018-03-30 Thread Neal Gompa 
On Thu, Mar 29, 2018 at 11:00 AM, 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.
>
> I don't mind them being backported, though. ;)
>

I certainly don't mind it either! It'll be nice having the feature in
Mageia 6's RPM package. :)


-- 
真実はいつも一つ！/ Always, there's only one truth!
___
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint

Re: [Rpm-maint] RPM 4.13.1 released!

2018-03-29 Thread Michael Schroeder 
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.

I don't mind them being backported, though. ;)

Cheers,
  Michael.

-- 
Michael Schroeder   m...@suse.de
SUSE LINUX GmbH,   GF Jeff Hawn, HRB 16746 AG Nuernberg
main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
___
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint

[Rpm-maint] RPM 4.13.1 released!

2018-03-28 Thread Panu Matilainen 
This is a bug fix and enhancement update to the stable 4.13.x branch. In 
particular, several file trigger related bugs (previously addressed in 
4.14.x) are fixed in this release. Additionally, support for 
with/without/unless rich dependencies has been backported in this release.


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. We cannot fix what happened after the fact, but this 
is our attempt to make up for it.


For details and download information, see

http://rpm.org/wiki/Releases/4.13.1

On behalf of the rpm-team,

- Panu -
___
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint