Bug 1604602
| Summary: | libiptcdata: FTBFS in Fedora rawhide | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Mohan Boddu <mboddu> | ||||||||||||
| Component: | libiptcdata | Assignee: | David Moore <david.moore> | ||||||||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||||
| Priority: | unspecified | ||||||||||||||
| Version: | rawhide | CC: | david.moore, hobbes1069, jchaloup, mhroncok, mtasaka, rosset.filipe | ||||||||||||
| Target Milestone: | --- | ||||||||||||||
| Target Release: | --- | ||||||||||||||
| Hardware: | Unspecified | ||||||||||||||
| OS: | Unspecified | ||||||||||||||
| Whiteboard: | |||||||||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||
| Clone Of: | Environment: | ||||||||||||||
| Last Closed: | 2019-07-19 12:50:09 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: | |||||||||||||||
| Bug Depends On: | |||||||||||||||
| Bug Blocks: | 1700317, 1585626, 1602938, 1628188, 1674516, 1732841 | ||||||||||||||
| Attachments: |
|
||||||||||||||
|
Description
Mohan Boddu
2018-07-19 23:32:13 UTC
Created attachment 1463646 [details]
build.log
Created attachment 1463647 [details]
root.log
file root.log too big, will only attach last 32768 bytes
Created attachment 1463648 [details]
state.log
This bug appears to have been reported against 'rawhide' during the Fedora 29 development cycle. Changing version to '29'. Still valid for F30 https://koji.fedoraproject.org/koji/buildinfo?buildID=1210341 And F31 https://koji.fedoraproject.org/koji/buildinfo?buildID=1216288 Created attachment 1540889 [details]
build.log from f31
Created attachment 1540890 [details]
root.log from f31
New upstream: https://github.com/ianw/libiptcdata Debian package: https://salsa.debian.org/debian/libiptcdata/commits/master https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/ David, please either fix this or orphan the package. THe sourceforge page hasn't had a release since 2009 but it looks like it has moved to github: https://github.com/ianw/libiptcdata/releases Still don't see any evidence it's been updated for Python 3 so probably best to keep the python module disabled. $ sudo dnf repoquery --whatrequires "libiptcdata.so.0()(64bit)" ... libiptcdata-devel-0:1.0.4-20.fc28.x86_64 python2-libiptcdata-0:1.0.4-20.fc28.x86_64 rawtherapee-0:5.5-4.fc31.x86_64 tracker-miners-0:2.2.1-1.fc30.x86_64 I don't necessarily want to own the package but as a member of the stewardship SIG, I have fix the package. Upgrading to 1.0.5 fixed the build issue. Additionally I built the python module as python 3 and added an obsolete for the python2 module. Any objection to building? A minimal fix for FTBFS is:
================================================
diff --git a/libiptcdata.spec b/libiptcdata.spec
index 3e581ad..5346346 100644
--- a/libiptcdata.spec
+++ b/libiptcdata.spec
@@ -37,6 +37,10 @@ that you can use to develop libiptcdata applications.
gtkdocize
autoreconf -fiv
+env LANG=C \
+ grep -bPl '\xa9' libiptcdata/*.{c,h} | \
+ xargs sed -i -e 's|\xa9|(c)|'
+
%build
%configure --enable-gtk-doc --disable-python --disable-static
make %{?_smp_mflags}
================================================
i.e. changing ISO-8859-1 copyright charactor to (C) to help gtk-doc
ref:
https://github.com/ianw/libiptcdata/commit/c1a145bb75ff40610d128faedf9ac1752ede6510
Ok, never mind, it looks like python2-libiptcdata was taken care of by the fedora obsoletes package. I'll build for f28->Rawhide since it's a new version. libiptcdata-1.0.5-1.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2019-b042a87a74 libiptcdata-1.0.5-1.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2019-e82a0a5f88 libiptcdata-1.0.5-1.fc30 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-d1d54444ac Ok, I set bodhi not to close the bugs. We still need to hear from the maintainers or we should orphan the package and/or turn it over to the stewardship SIG. Okay, I've orphaned the package because I don't have time to maintain it anymore. libiptcdata-1.0.5-1.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-d1d54444ac libiptcdata-1.0.5-1.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-b042a87a74 libiptcdata-1.0.5-1.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-e82a0a5f88 libiptcdata-1.0.5-1.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report. libiptcdata-1.0.5-1.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report. libiptcdata-1.0.5-1.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report. |