[SRU] FTBFS nfs-ganesha fails to build from source on Ubuntu Groovy (gcc-10)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nfs-ganesha (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Groovy |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Impact]
When trying to build nfs-ganesha, it fails to build with many instances of:
> /usr/bin/ld: CMakeFiles/
> /usr/bin/ld: CMakeFiles/
Debian has already landed a fix at https:/
The fix linked above is an upstream patch to resolve the build on gcc-10
[Test Plan]
Reproducing the bug is as easy as attempting to build the package:
pull-lp-source nfs-ganesha groovy
sbuild -A -d groovy-amd64 nfs-ganesha_
[Where problems could occur]
The SRU shouldn't change the current behaviour as it's just aligning compiler support to gcc-10.
Upstream nfs-ganesha and Debian have already included this patch so I expect the risk to be low.
Changed in nfs-ganesha (Ubuntu): | |
status: | New → Fix Released |
Hello Chris, or anyone else affected,
Accepted nfs-ganesha into groovy-proposed. The package will build now and be available at https:/ /launchpad. net/ubuntu/ +source/ nfs-ganesha/ 3.2-2ubuntu2 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https:/ /wiki.ubuntu. com/Testing/ EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification- needed- groovy to verification- done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed- groovy. In either case, without details of your testing we will not be able to proceed.
Further information regarding the verification process can be found at https:/ /wiki.ubuntu. com/QATeam/ PerformingSRUVe rification . Thank you in advance for helping!
N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.