[Rpm-maint] RPM 4.13.0 rc2 released

Panu Matilainen pmatilai at redhat.com
Fri Oct 21 09:33:24 UTC 2016


On 10/21/2016 12:09 PM, Thierry Vignaud wrote:
> On 21 October 2016 at 08:51, Panu Matilainen <pmatilai at redhat.com> wrote:
>
>>>> Please test and report any anomalies. From rc2 to final only regression fixes will be allowed. Unless of course something really strange comes up, you never know. Or I forgot something absolutely vital. THAT would not count as a strange incident though.
>>>
>>>
>>> Humm.... Testsuite won't pass....
>>> 2 tests are failing because of missing files...
>>> Please apply the attached patch
>>> It fixes:
>>> 84: rpmbuild debuginfo dwz                          FAILED (rpmbuild.at:396)
>>> 86: rpmbuild implicit suid binary                   FAILED (rpmbuild.at:509)
>>
>>
>> Ah, I did run the test-suite but not from the created tarball. One more thing to remember when cutting releases. Or rather *cough* to document *cough*.
>>
>> Applied (with a slightly expanded comments).
>
> If you could cherry-pick in rpm-4.13.x branch too, that would be nice :-)

I will, eventually. Lets see what other things turn up first.

>>> After that, 2 unexpected failures remain:
>>>
>>>  85: rpmbuild debuginfo dwz gnu_debuglink crc        FAILED (rpmbuild.at:468)
>>
>>
>> ...but this I had just missed. It appears to be cured by commit
>> cherry-picking commit 3929ce4d58ab18c810b9a776f5c49d56cb436026.
>
> This commit doen't exist in git
> The attached patch fixes it anyway

Sorry, should've been 41c4dcf507e2208585d6dc0952f59686a3a69d69, which 
commit 4ec7c396fb9464a3fcff006408871f8175ab169b apparently depends on.

>
>>> 277: spec parse                                      FAILED (rpmpython.at:70)
>>
>>
>> ...and this I'm not seeing at all. Please post tests/rpmtests.dir/277/rpmtests.log ... or does it happen to go away if you cherry-pick commit 3c74e34e8d8c5b3db024dbe04a352e807ed2b627 ?
>
> That doesn't help.
> I've attached the relevant logs plus a fix.
>

That's somewhat curious - why am I not seeing that? It suggests 
something outside the testing root is leaking into the tests and 
affecting things. The python tests would be more prone to that than the 
others since it doesn't occur inside the fakechroot of course...

	- Panu -


More information about the Rpm-maint mailing list