Bug 1346451 - iniparser-4.0 is available
Summary: iniparser-4.0 is available
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: iniparser
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jaromír Cápík
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-06-14 20:45 UTC by Upstream Release Monitoring
Modified: 2016-09-10 15:26 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-09-10 15:26:59 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
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. (5.15 KB, patch)
2016-06-14 20:46 UTC, Upstream Release Monitoring
no flags Details | Diff

Description Upstream Release Monitoring 2016-06-14 20:45:49 UTC
Latest upstream release: 4.0
Current version/release in rawhide: 3.1-7.fc24
URL: http://ndevilla.free.fr/iniparser/

Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy

More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring

Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.

Based on the information from anitya:  https://release-monitoring.org/project/1380/

Comment 1 Upstream Release Monitoring 2016-06-14 20:46:04 UTC
Patching or scratch build for iniparser-3.1 failed.

Comment 2 Upstream Release Monitoring 2016-06-14 20:46:05 UTC
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.

Comment 3 Upstream Release Monitoring 2016-06-14 20:46:06 UTC
Patches were not touched. All were applied properly

Comment 4 Raphael Groner 2016-06-14 20:48:07 UTC
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.

Comment 5 Raphael Groner 2016-06-14 21:29:00 UTC
Update to version 4.0 introduces a soname bump with propably ABI/API breakage.

Comment 6 Christos Triantafyllidis 2016-07-21 20:41:39 UTC
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

Comment 7 Raphael Groner 2016-07-29 14:10:41 UTC
Friendly ping. Any news here?

Comment 8 Christos Triantafyllidis 2016-08-07 14:57:53 UTC
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

Comment 9 Raphael Groner 2016-08-07 15:28:04 UTC
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

Comment 10 Jaromír Cápík 2016-08-20 17:22:47 UTC
Hello guys.

I'm going to look at the new version shortly.

Comment 11 Jaromír Cápík 2016-08-21 11:42:16 UTC
(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.

Comment 12 Jaromír Cápík 2016-08-21 11:47:46 UTC
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.

Comment 13 Jaromír Cápík 2016-08-21 11:52:06 UTC
Even when the spindown is rebuilt against iniparser v4.0, it still crashes. That means the problem doesn't look like interface related.

Comment 14 Jaromír Cápík 2016-08-21 12:17:01 UTC
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.

Comment 15 Upstream Release Monitoring 2016-08-21 12:38:37 UTC
jcapik's iniparser-4.0-1.20160821git.fc26 completed http://koji.fedoraproject.org/koji/buildinfo?buildID=793383

Comment 16 Jaromír Cápík 2016-08-21 13:01:36 UTC
Built for rawhide.

And sorry for the delay. I have a bad period in my life.

Comment 17 Christos Triantafyllidis 2016-08-21 16:19:48 UTC
Thank you Jaromir!

Comment 18 Raphael Groner 2016-08-28 15:00:40 UTC
@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.

Comment 19 Jaromír Cápík 2016-09-04 10:52:53 UTC
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.

Comment 20 Jaromír Cápík 2016-09-04 10:56:06 UTC
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.

Comment 21 Raphael Groner 2016-09-10 15:26:59 UTC
Upstream of cava supports in recent snapshot also iniparser version 3. There's no need to update iniparser. Sorry for the noise.


Note You need to log in before you can comment on or make changes to this bug.