Merge lp:~csurbhi/ubuntu/maverick/redhat-cluster/redhat-cluster-fix.600984 into lp:ubuntu/maverick/redhat-cluster
Status: | Rejected |
---|---|
Rejected by: | Benjamin Drung |
Proposed branch: | lp:~csurbhi/ubuntu/maverick/redhat-cluster/redhat-cluster-fix.600984 |
Merge into: | lp:ubuntu/maverick/redhat-cluster |
Diff against target: |
99 lines (+81/-0) 3 files modified
debian/changelog (+10/-0) debian/patches/02-compilation-err-fix.patch (+70/-0) debian/patches/series (+1/-0) |
To merge this branch: | bzr merge lp:~csurbhi/ubuntu/maverick/redhat-cluster/redhat-cluster-fix.600984 |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Benjamin Drung | Disapprove | ||
Ubuntu branches | Pending | ||
Review via email: mp+29848@code.launchpad.net |
Description of the change
This patch fixes the bug #600984 on LP. It makes the following changes to fix the compilation error(s) while building redhat-cluster package:
1) changes bdev_hardsect_
2) changes generic_
3) changes the default include dir for nss and nspr to be /usr/include/nss and /usr/include/nspr respectively
Please do consider merging this for maverick.
Unmerged revisions
- 33. By Surbhi Palande
-
* Fixed a compilation error by doing the following changes:
- changed bdev_hardsect_size() to bdev_logical_ block_size( )
- changed generic_file_aio_ write_nolock( ) to generic_ file_aio_ write()
- changed the default include dir for nss and nspr to be /usr/include/nss
and /usr/include/nspr respectively (LP: #600984)
Thanks for this.
This merge doesn't seem to fix the build failure bug. I get the same
failure when test-building it as I do when test-building the package in
the archive.
As a matter of convention, we usually put Ubuntu patches at the end of
the patch queue, i.e. run 'quilt push -a' before creating the patch, and
I'd suggest using some kind of similar numbering scheme rather than
having the Debian patch have four digits at the start and the Ubuntu
patch have two. (You can just edit the series file when in the 'quilt
pop -a' state to move the existing patch around.)
Why does configure need to be patched? debian/rules already passes
--nssincdir and --nsprincdir, so it shouldn't matter what their defaults
are.