Bug 1346451
| Summary: | iniparser-4.0 is available | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Upstream Release Monitoring <upstream-release-monitoring> | ||||
| Component: | iniparser | Assignee: | Jaromír Cápík <jaromir.capik> | ||||
| Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | rawhide | CC: | asn, christos.triantafyllidis, jaromir.capik, projects.rg, ssorce | ||||
| Target Milestone: | --- | Keywords: | FutureFeature, Reopened, Triaged | ||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Enhancement | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2016-09-10 15:26:59 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Upstream Release Monitoring
2016-06-14 20:45:49 UTC
Patching or scratch build for iniparser-3.1 failed. Created attachment 1167966 [details] Rebase-helper rebase-helper-debug.log log file. See for details and report the eventual error to rebase-helper https://github.com/phracek/rebase-helper/issues. Patches were not touched. All were applied properly Upstream moved to GitHub, see the note on its homepage. I've modified Anitya configuration. cava bundles iniparser version 4, so please update to let me unbundle. Update to version 4.0 introduces a soname bump with propably ABI/API breakage. Hello Jaromir, I wanted to check (as part of the review of the new package "cava") whether the upgrade of iniparser to 4.0 is a possible upgrade we can have. I'd like to avoid introducing a bundled version if that is possible. Cheers, Christos Friendly ping. Any news here? Hello, It's more than 1.5 months since this ticket was raised. Jaromir can you please reply whether this is something we can have (updated iniparser)? Adding Andreas and Simo as they seem to have had commit access to this package. Cheers, Christos Please feel free to start with the nonresponsive maintainer process, we've asked now for several times. https://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers Hello guys. I'm going to look at the new version shortly. (In reply to Raphael Groner from comment #5) > Update to version 4.0 introduces a soname bump with propably ABI/API > breakage. iniparser v4.0 (the tagged commit) doesn't introduce a soname bump. I tried to run the dependent software with v4.0 and it seems to runs correctly. Hmmm ... nsnake runs, but spindownd crashes ... so, there's apparently something wrong with it. Maybe the tagget version should really bump the soname. Gonna check. Even when the spindown is rebuilt against iniparser v4.0, it still crashes. That means the problem doesn't look like interface related. Ok. It seems the commit e24843b is good and keeps the soname at 0. Gonna build that version as both apps run with that version like expected. jcapik's iniparser-4.0-1.20160821git.fc26 completed http://koji.fedoraproject.org/koji/buildinfo?buildID=793383 Built for rawhide. And sorry for the delay. I have a bad period in my life. Thank you Jaromir! @Jaromir, thanks for the update in rawhide. Can you also update in F25 and F24? (In reply to Raphael Groner from comment #5) > Update to version 4.0 introduces a soname bump with propably ABI/API > breakage. Please comment on the ABI/API breakage. https://fedoraproject.org/wiki/Updates_Policy#Rawhide_.2F_devel_.2F_master Maybe we need a compatibility package for cava unbundling, rhbz#1346457. Hello Raphael. Updates should only aim to fix bugs. I don't think we should touch F24 and F25. Fedora users often build their own packages against system libraries and even when there's no soname bump, there's a chance we could break something. I looked at #1346457 and unless cava necessarilly requires features from iniparser 4, you could try to build it against 3.1. I see no problem with that. Upstream of cava supports in recent snapshot also iniparser version 3. There's no need to update iniparser. Sorry for the noise. |