Bug 1423842 - libdb: FTBFS in rawhide
Summary: libdb: FTBFS in rawhide
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: libdb
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Petr Kubat
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F26FTBFS
TreeView+ depends on / blocked
 
Reported: 2017-02-17 14:57 UTC by Fedora Release Engineering
Modified: 2017-02-22 13:05 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-02-22 13:05:54 UTC
Type: ---


Attachments (Terms of Use)
build.log (715.00 KB, text/plain)
2017-02-17 14:57 UTC, Fedora Release Engineering
no flags Details
root.log (88.32 KB, text/plain)
2017-02-17 14:57 UTC, Fedora Release Engineering
no flags Details
state.log (619 bytes, text/plain)
2017-02-17 14:57 UTC, Fedora Release Engineering
no flags Details

Description Fedora Release Engineering 2017-02-17 14:57:29 UTC
Your package libdb failed to build from source in current rawhide.

https://koji.fedoraproject.org/koji/taskinfo?taskID=17731646

For details on mass rebuild see https://fedoraproject.org/wiki/Fedora_26_Mass_Rebuild

Comment 1 Fedora Release Engineering 2017-02-17 14:57:37 UTC
Created attachment 1252868 [details]
build.log

Comment 2 Fedora Release Engineering 2017-02-17 14:57:41 UTC
Created attachment 1252869 [details]
root.log

Comment 3 Fedora Release Engineering 2017-02-17 14:57:45 UTC
Created attachment 1252870 [details]
state.log

Comment 4 Upstream Release Monitoring 2017-02-22 13:04:20 UTC
pkubat's libdb-5.3.28-17.fc26 completed http://koji.fedoraproject.org/koji/buildinfo?buildID=846035

Comment 5 Petr Kubat 2017-02-22 13:05:54 UTC
Segfault during builds happening due to an integer variable overflowing into negative values in the bundled-in lemon parser.
Changed the problematic variable's type to unsigned and the build went through just fine.


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