Bug 1676036
Summary: | squashfs-tools: FTBFS in Fedora rawhide/f30 | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Fedora Release Engineering <releng> | ||||||||
Component: | squashfs-tools | Assignee: | Bruno Wolff III <bruno> | ||||||||
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
Severity: | unspecified | Docs Contact: | |||||||||
Priority: | unspecified | ||||||||||
Version: | rawhide | CC: | bruno, katzj, kyle, swt | ||||||||
Target Milestone: | --- | ||||||||||
Target Release: | --- | ||||||||||
Hardware: | Unspecified | ||||||||||
OS: | Unspecified | ||||||||||
Whiteboard: | |||||||||||
Fixed In Version: | squashfs-tools-4.3-20.fc30 | Doc Type: | If docs needed, set a value | ||||||||
Doc Text: | Story Points: | --- | |||||||||
Clone Of: | Environment: | ||||||||||
Last Closed: | 2019-05-23 17:48:47 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: | 1674516 | ||||||||||
Attachments: |
|
Description
Fedora Release Engineering
2019-02-11 22:03:33 UTC
Created attachment 1533070 [details]
build.log
file build.log too big, will only attach last 1024 bytes
Created attachment 1533071 [details]
root.log
file root.log too big, will only attach last 1024 bytes
Created attachment 1533072 [details]
state.log
Dear Maintainer, your package has not been built successfully in f30. Action is required from you. If you can fix your package to build, perform a build in koji, and either create an update in bodhi, or close this bug without creating an update, if updating is not appropriate [1]. If you are working on a fix, set the status to ASSIGNED to acknowledge this. Following the latest policy for such packages [2], your package can be orphaned if this bug remains in NEW state more than 8 weeks. [1] https://fedoraproject.org/wiki/Updates_Policy [2] https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/ It looks like this is due to a glibc change. There is a pull request with the fix in the new github upstream. I probably don't want to track that for f30 and lower, but the change is a one liner (assuming that is the only thing blocking things). squashfs-tools-4.3-19.fc30 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-c1e73feb7d squashfs-tools-4.3-20.fc30 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-accdc3a5f3 (In reply to Bruno Wolff III from comment #6) > It looks like this is due to a glibc change. There is a pull request with > the fix in the new github upstream. I probably don't want to track that for > f30 and lower, but the change is a one liner (assuming that is the only > thing blocking things). Any particular reason you didn't just merge my pull request? Your pull request to Philip's repo? If there is one in Fedora, I missed it. I'm still catching up on stuff. In rawhide I plan to switch to Philip's github tree as the source. If your request there gets included by Philip, then I would get it automatically. If not it wouldn't make sense to pull from there for Fedora. If there is a place to check on pull requests for Fedora packages, I'd be interested in a pointer to documentation for this. I reread some of the maintainer documentation to get caught up on current practices but didn't see that. Are all packages in pagure, even if their upstream source isn't? Nevermind, I see the link above and it does look like there is a probably pagure instance for each package. Presumably there are docs on that that I missed. (In reply to Bruno Wolff III from comment #10) > Your pull request to Philip's repo? If there is one in Fedora, I missed it. > I'm still catching up on stuff. In rawhide I plan to switch to Philip's > github tree as the source. If your request there gets included by Philip, > then I would get it automatically. If not it wouldn't make sense to pull > from there for Fedora. If there is a place to check on pull requests for > Fedora packages, I'd be interested in a pointer to documentation for this. I > reread some of the maintainer documentation to get caught up on current > practices but didn't see that. Are all packages in pagure, even if their > upstream source isn't? No, my pull request to the Fedora packaging that I provided a link to in Comment #5. :-) Every Fedora dist-git repo is in pagure. You should have gotten an email from Pagure when I submitted the pull request anyway. You can view the pull requests for any package by going to https://src.fedoraproject.org/rpms/<packagename>. Thanks. I get a lot of mail and probably didn't realize what it was. For a two line change it didn't take too long to do and I needed to practice using the newer tools. I'd be less happy if I duplicated a lot of work. Thanks. I closed the PR, but thanks for showing me something new. I would have used it if I realized it was there. I also missed something in that I was expecting to be able to comment on the close action. It looks like I need to find a way to comment before closing. I'm going to see if I can find a way to get a comment added to it now for other people wondering why it wasn't used. squashfs-tools-4.3-20.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-accdc3a5f3 squashfs-tools-4.3-20.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report. |