On Thu, Sep 8, 2016 at 11:21 AM, Stephen Gallagher <sgallagh@xxxxxxxxxx> wrote: > Recently, I updated http-parser from a 2.1 git prerelease snapshot to the latest > stable release 2.7.1 in all supported Fedora branches. I didn't anticipate any > issues because 1) the soname didn't change and 2) the project upstream uses > semantic versioning, which should imply that 2.7.x should be fully > backwards-compatible with 2.0. > > Unfortunately, it looks like this is not perfectly true[1]. My suspicion is that > the git snapshot my predecessor selected was not perfectly compatible (which was > likely fixed before the official 2.1 release happened). > > However, so far it *does* appear that a trivial rebuild is all that is needed to > get things working again in client software. > > There are two approaches that I can take: > > 1) I can bump epoch and revert the version of http-parser in F23 back to the git > snapshot. You'd need epochs on all releases to ensure upgrade paths. > 2) I can fire off a rebuild of the affected packages within Fedora, which appear > to be: > > * libgit2 > * mesos > * nodejs > * ocserv (already rebuilt since) > * sssd (already rebuilt since) > > > Given how few packages this appears to affect, I'm leaning towards taking option > 2. I strongly suspect that whichever component was broken is not heavily-used, > else I imagine I'd be hearing about considerably greater breakage (particularly > in nodejs) > > I was comfortable pushing it in F23 because the SSSD team tested that it didn't > break their code and provided Bodhi karma to that effect. > > > > > I'm aware that option 2) is technically in violation of the stable updates > policy, however given the age of the older snapshot and the fact that it was > clearly not properly compatible with the 2.x release series, I feel that if I > had to provide any patches, they would be beyond my ability to backport. I think 2) makes sense in this case. -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://lists.fedoraproject.org/admin/lists/devel@xxxxxxxxxxxxxxxxxxxxxxx
