pspacek, rpm breaking parallel builds seems unlikely since 4.13.0 consists of very little else than what was already included as patches. A more likely candidate would seem like this change to redhat-rpm-config https://bugzilla.redhat.com/show_bug.cgi?id=1384938:
commit 9a4753b3e469942e4eb29442944838d584f347c0
Author: Jason Tibbitts <tibbs@math.uh.edu>
Date: Mon Oct 17 13:47:22 2016 -0500
Remove hardcoded limit of 16 CPUs for make -j
You'd have to be using redhat-rpm-config from rawhide to hit that though. But please open a bug on the breakage nevertheless, update comments are terrible for tracking bugs.
This update has reached the stable karma threshold and can be pushed to stable now if the maintainer wishes.
The upgrade path from this version to F25 is broken, because rpm-python and rpm-python3 were renamed to python2-rpm and python3-rpm in F25, but the F25 packages' Obsoletes: are not versioned high enough. See https://bodhi.fedoraproject.org/updates/FEDORA-2016-d96e9a5ca0 . Pushing this stable without first resolving that problem will prevent anyone being able to upgrade to F25 without manually downgrading rpm.
This update has been submitted for testing by pmatilai.
works for me
works
No regressions noted.
This update has been pushed to testing.
Looks OK.
works for me
This update has reached the stable karma threshold and can be pushed to stable now if the maintainer wishes.
no regressions noted
This update has reached the stable karma threshold and can be pushed to stable now if the maintainer wishes.
This update has reached the stable karma threshold and can be pushed to stable now if the maintainer wishes.
Look Good to Me
This update has reached the stable karma threshold and can be pushed to stable now if the maintainer wishes.
This update has reached the stable karma threshold and can be pushed to stable now if the maintainer wishes.
This update has reached the stable karma threshold and can be pushed to stable now if the maintainer wishes.
This update has reached the stable karma threshold and can be pushed to stable now if the maintainer wishes.
works for me
This update has reached the stable karma threshold and can be pushed to stable now if the maintainer wishes.
This update broke parallel builds based on recursive make calls.
I have a Makefile which contains target "rpms". This target creates tarball from local sources and executes rpmbuild, which in turn executes sub-make.
Now the sub-make is failing with error "INTERNAL: Exiting with 1 jobserver tokens available; should be 8!"
This used to work with rpm-build-4.13.0-0.rc1.27.fc24.x86_64 and does not work with rpm-build-4.13.0-1.fc24.x86_64.
FYI reproducer is in repo https://github.com/pspacek/freeipa/tree/break-rpmbuild
Just clone the repo and run "MAKEFLAGS=-j16 ./makerpms.sh" script. (Eventually use dnf builddep --spec freeipa.spec.in to get required packages.)
It will blow up in couple of seconds.
This update has reached the stable karma threshold and can be pushed to stable now if the maintainer wishes.
This update has reached the stable karma threshold and can be pushed to stable now if the maintainer wishes.
This update has reached the stable karma threshold and can be pushed to stable now if the maintainer wishes.
Seems good
pspacek, rpm breaking parallel builds seems unlikely since 4.13.0 consists of very little else than what was already included as patches. A more likely candidate would seem like this change to redhat-rpm-config https://bugzilla.redhat.com/show_bug.cgi?id=1384938:
You'd have to be using redhat-rpm-config from rawhide to hit that though. But please open a bug on the breakage nevertheless, update comments are terrible for tracking bugs.
This update has reached the stable karma threshold and can be pushed to stable now if the maintainer wishes.
works for me
This update has reached the stable karma threshold and can be pushed to stable now if the maintainer wishes.
This update has reached the stable karma threshold and can be pushed to stable now if the maintainer wishes.
no issues noticed
This update has reached the stable karma threshold and can be pushed to stable now if the maintainer wishes.
This update has reached the stable karma threshold and can be pushed to stable now if the maintainer wishes.
This update has reached the stable karma threshold and can be pushed to stable now if the maintainer wishes.
This update has reached the stable karma threshold and can be pushed to stable now if the maintainer wishes.
This update has reached the stable karma threshold and can be pushed to stable now if the maintainer wishes.
This update has reached the stable karma threshold and can be pushed to stable now if the maintainer wishes.
This update has reached the stable karma threshold and can be pushed to stable now if the maintainer wishes.
This update has reached the stable karma threshold and can be pushed to stable now if the maintainer wishes.
seems fine
This update has reached the stable karma threshold and can be pushed to stable now if the maintainer wishes.
The upgrade path from this version to F25 is broken, because
rpm-pythonandrpm-python3were renamed topython2-rpmandpython3-rpmin F25, but the F25 packages'Obsoletes:are not versioned high enough. See https://bodhi.fedoraproject.org/updates/FEDORA-2016-d96e9a5ca0 . Pushing this stable without first resolving that problem will prevent anyone being able to upgrade to F25 without manually downgrading rpm.@adamwill: So true. I upgraded a few machines with dnf today and needed allowerasing to get it done.
This update has reached the stable karma threshold and can be pushed to stable now if the maintainer wishes.
This update has reached the stable karma threshold and can be pushed to stable now if the maintainer wishes.
This update has reached the stable karma threshold and can be pushed to stable now if the maintainer wishes.
This update has reached the stable karma threshold and can be pushed to stable now if the maintainer wishes.
This update has reached the stable karma threshold and can be pushed to stable now if the maintainer wishes.
This update has reached the stable karma threshold and can be pushed to stable now if the maintainer wishes.
This update has reached the stable karma threshold and can be pushed to stable now if the maintainer wishes.
This update has reached the stable karma threshold and can be pushed to stable now if the maintainer wishes.
This update has reached the stable karma threshold and can be pushed to stable now if the maintainer wishes.
This update has reached the stable karma threshold and can be pushed to stable now if the maintainer wishes.
This update has reached the stable karma threshold and can be pushed to stable now if the maintainer wishes.
This update has reached the stable karma threshold and can be pushed to stable now if the maintainer wishes.
This update has reached the stable karma threshold and can be pushed to stable now if the maintainer wishes.
This update has reached the stable karma threshold and can be pushed to stable now if the maintainer wishes.
This update has reached the stable karma threshold and can be pushed to stable now if the maintainer wishes.
This update has reached the stable karma threshold and can be pushed to stable now if the maintainer wishes.
This update has reached the stable karma threshold and can be pushed to stable now if the maintainer wishes.
This update has reached the stable karma threshold and can be pushed to stable now if the maintainer wishes.
This update has reached the stable karma threshold and can be pushed to stable now if the maintainer wishes.
This update has reached the stable karma threshold and can be pushed to stable now if the maintainer wishes.
This update has reached the stable karma threshold and can be pushed to stable now if the maintainer wishes.
This update has reached the stable karma threshold and can be pushed to stable now if the maintainer wishes.
This update has reached the stable karma threshold and can be pushed to stable now if the maintainer wishes.
This update has reached the stable karma threshold and can be pushed to stable now if the maintainer wishes.
This update has reached the stable karma threshold and can be pushed to stable now if the maintainer wishes.
This update has reached the stable karma threshold and can be pushed to stable now if the maintainer wishes.
This update has reached the stable karma threshold and can be pushed to stable now if the maintainer wishes.
This update has reached the stable karma threshold and can be pushed to stable now if the maintainer wishes.
This update has reached the stable karma threshold and can be pushed to stable now if the maintainer wishes.
This update has reached the stable karma threshold and can be pushed to stable now if the maintainer wishes.
This update has reached the stable karma threshold and can be pushed to stable now if the maintainer wishes.
This update has reached the stable karma threshold and can be pushed to stable now if the maintainer wishes.
This update has reached the stable karma threshold and can be pushed to stable now if the maintainer wishes.
This update has reached the stable karma threshold and can be pushed to stable now if the maintainer wishes.
This update has reached the stable karma threshold and can be pushed to stable now if the maintainer wishes.
This update has reached the stable karma threshold and can be pushed to stable now if the maintainer wishes.
This update has reached the stable karma threshold and can be pushed to stable now if the maintainer wishes.
This update has reached the stable karma threshold and can be pushed to stable now if the maintainer wishes.
This update has reached the stable karma threshold and can be pushed to stable now if the maintainer wishes.
This update has reached the stable karma threshold and can be pushed to stable now if the maintainer wishes.
This update has been submitted for stable by pmatilai.
This update has been pushed to stable.
@pmatilai, here is the bug: https://bugzilla.redhat.com/show_bug.cgi?id=1398405
Given list of packages in https://bugzilla.redhat.com/show_bug.cgi?id=1398405#c3 , I think it is unrelated to redhat-rpm-config change.