fix patch build failure in trusty
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
patch (Debian) |
Fix Released
|
Unknown
|
|||
patch (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Trusty |
Fix Released
|
High
|
Unassigned |
Bug Description
seen in a test rebuild with a modified toolchain, and in a clean trusty environment
=======
All 34 tests behaved as expected (1 expected failure)
=======
make[5]: Leaving directory `/build/
make[4]: Leaving directory `/build/
make[3]: Leaving directory `/build/
make[3]: Entering directory `/build/
make[3]: Leaving directory `/build/
make[2]: Leaving directory `/build/
make[1]: Leaving directory `/build/
# make sure we call ed as "ed"
[ "$(strings -n 2 src/patch | grep -w 'ed$')" = "ed" ]
make: *** [build-stamp] Error 1
dpkg-buildpackage: error: debian/rules build gave error exit status 2
As pointed out in https:/
The fix is already in current Ubuntu releases
To validate; Check that the package builds, and passes the tests.
Related branches
Changed in patch (Ubuntu Trusty): | |
milestone: | none → trusty-updates |
status: | New → Confirmed |
Changed in patch (Ubuntu): | |
milestone: | trusty-updates → none |
status: | Confirmed → Fix Released |
Changed in patch (Ubuntu): | |
importance: | Undecided → Critical |
Changed in patch (Ubuntu Trusty): | |
importance: | Undecided → Critical |
Changed in patch (Ubuntu): | |
importance: | Critical → High |
Changed in patch (Ubuntu Trusty): | |
importance: | Critical → High |
Changed in patch (Debian): | |
status: | Unknown → Fix Released |
Hello Matthias, or anyone else affected,
Accepted patch into trusty-proposed. The package will build now and be available at https:/ /launchpad. net/ubuntu/ +source/ patch/2. 7.1-4ubuntu2 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 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, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed. In either case, details of your testing will help us make a better decision.
Further information regarding the verification process can be found at https:/ /wiki.ubuntu. com/QATeam/ PerformingSRUVe rification . Thank you in advance!