Re: [Rpm-maint] [Rpm-announce] RPM 4.14.0 release candidate 2 is out

2017-10-02 Thread Thierry Vignaud
On 28 September 2017 at 16:06, Panu Matilainen wrote: > There aren't that many changes since rc1, but enough to warrant a second > release candidate instead of going for final. The important ones being: > > - Fix a bug of file triggers failing on some packages (MgBug:18797,

Re: [Rpm-maint] [Rpm-announce] RPM 4.14.0 release candidate 2 is out

2017-10-02 Thread Thierry Vignaud
On 2 October 2017 at 15:50, Thierry Vignaud wrote: It's probably this: https://github.com/rpm-software-management/rpm/commit/816c7cf3fdae5c45de02a42a2245549778e2ca80 If so, the following in the spec should work around it: %undefine

Re: [Rpm-maint] [Rpm-announce] RPM 4.14.0 release candidate 2 is out

2017-10-02 Thread Thierry Vignaud
On 2 October 2017 at 23:06, Thierry Vignaud wrote: > Also this new rpm introduced segfault regressions in both RPM4 & urpmi > testsuites > See attached gdb traces in BUG*.txt > valgrind seems to hint about invalid writes/reads > See you The urpmi issue is when checking

Re: [Rpm-maint] [Rpm-announce] RPM 4.14.0 release candidate 2 is out

2017-10-02 Thread Panu Matilainen
On 10/03/2017 12:12 AM, Thierry Vignaud wrote: On 2 October 2017 at 23:06, Thierry Vignaud wrote: Also this new rpm introduced segfault regressions in both RPM4 & urpmi testsuites See attached gdb traces in BUG*.txt valgrind seems to hint about invalid writes/reads

Re: [Rpm-maint] [Rpm-announce] RPM 4.14.0 release candidate 2 is out

2017-10-02 Thread Panu Matilainen
On 10/03/2017 12:12 AM, Thierry Vignaud wrote: On 2 October 2017 at 23:06, Thierry Vignaud wrote: Also this new rpm introduced segfault regressions in both RPM4 & urpmi testsuites See attached gdb traces in BUG*.txt valgrind seems to hint about invalid writes/reads

Re: [Rpm-maint] [Rpm-announce] RPM 4.14.0 release candidate 2 is out

2017-10-02 Thread Thierry Vignaud
On 28 September 2017 at 16:06, Panu Matilainen wrote: > > There aren't that many changes since rc1, but enough to warrant a second > release candidate instead of going for final. The important ones being: > > - Fix a bug of file triggers failing on some packages (MgBug:18797,

Re: [Rpm-maint] [Rpm-announce] RPM 4.14.0 release candidate 2 is out

2017-10-02 Thread Panu Matilainen
On 10/02/2017 12:11 PM, Thierry Vignaud wrote: On 28 September 2017 at 16:06, Panu Matilainen wrote: There aren't that many changes since rc1, but enough to warrant a second release candidate instead of going for final. The important ones being: - Fix a bug of file

Re: [Rpm-maint] [Rpm-announce] RPM 4.14.0 release candidate 2 is out

2017-10-02 Thread Thierry Vignaud
On 28 September 2017 at 16:06, Panu Matilainen wrote: > > There aren't that many changes since rc1, but enough to warrant a second > release candidate instead of going for final. The important ones being: > > - Fix a bug of file triggers failing on some packages (MgBug:18797,

Re: [Rpm-maint] [Rpm-announce] RPM 4.14.0 release candidate 2 is out

2017-10-02 Thread Panu Matilainen
On 10/02/2017 02:14 PM, Thierry Vignaud wrote: On 2 October 2017 at 12:05, Panu Matilainen wrote: It looks like some dep generators are no more run: We've one dep generator carried by another pkg (so unchanged). But since we upgrade to 4.14, those deps are no more run: $

Re: [Rpm-maint] [Rpm-announce] RPM 4.14.0 release candidate 2 is out

2017-10-02 Thread Panu Matilainen
On 10/02/2017 02:05 PM, Thierry Vignaud wrote: On 2 October 2017 at 12:34, Panu Matilainen wrote: On 10/02/2017 12:20 PM, Thierry Vignaud wrote: On 28 September 2017 at 16:06, Panu Matilainen wrote: There aren't that many changes since rc1, but

Re: [Rpm-maint] [Rpm-announce] RPM 4.14.0 release candidate 2 is out

2017-10-02 Thread Thierry Vignaud
On 2 October 2017 at 15:04, Panu Matilainen wrote: >>> It's probably this: >>> >>> https://github.com/rpm-software-management/rpm/commit/816c7cf3fdae5c45de02a42a2245549778e2ca80 >>> >>> If so, the following in the spec should work around it: >>> %undefine

Re: [Rpm-maint] [Rpm-announce] RPM 4.14.0 release candidate 2 is out

2017-10-02 Thread Thierry Vignaud
On 2 October 2017 at 12:05, Panu Matilainen wrote: >> It looks like some dep generators are no more run: >> We've one dep generator carried by another pkg (so unchanged). >> But since we upgrade to 4.14, those deps are no more run: >> >> $ cat

Re: [Rpm-maint] [Rpm-announce] RPM 4.14.0 release candidate 2 is out

2017-10-02 Thread Panu Matilainen
On 10/02/2017 12:20 PM, Thierry Vignaud wrote: On 28 September 2017 at 16:06, Panu Matilainen wrote: There aren't that many changes since rc1, but enough to warrant a second release candidate instead of going for final. The important ones being: - Fix a bug of file

Re: [Rpm-maint] [Rpm-announce] RPM 4.14.0 release candidate 2 is out

2017-10-02 Thread Thierry Vignaud
On 2 October 2017 at 12:34, Panu Matilainen wrote: > On 10/02/2017 12:20 PM, Thierry Vignaud wrote: >> >> On 28 September 2017 at 16:06, Panu Matilainen >> wrote: >>> >>> >>> There aren't that many changes since rc1, but enough to warrant a second >>>